From: Christoph Hellwig Date: Thu, 7 Jul 2022 16:10:29 +0000 (+0200) Subject: fix up a non-requirements and bits in the security considerations X-Git-Tag: draft-hellwig-nfsv4-scsi-layout-nvme-03~1 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=1d99b9b277e05cd8926f89f0dce154fb311b36f8;p=users%2Fhch%2Fscsi-layout-nvme.git fix up a non-requirements and bits in the security considerations Mostly from David Black --- diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml index f140bcf..4d89356 100644 --- a/scsi_nvme_middle.xml +++ b/scsi_nvme_middle.xml @@ -278,12 +278,12 @@ NOT be deployed. - As with other block-oriented pNFS layout types, the metadata - server MUST be able to fence off a client's access to the data - on an NVMe storage device. When it revokes the layout, the - client's access MUST be terminated at the storage devices. The - client has a subsequent opportunity to perform fresh security - checks and then reacquire a new layout. + As with other block-oriented pNFS layout types, the metadata server + is able to fence off a client's access to the data on an NVMe namespace + used as a storage device. If a metadata server revokes a layout, the + client's access MUST be terminated at the storage devices via fencing + as specified in . The client has a + subsequent opportunity to acquire a new layout.