From: Christoph Hellwig Date: Tue, 23 May 2017 17:48:43 +0000 (+0200) Subject: make EUI64 or NGUID support a requirement instead of a SHOULD X-Git-Tag: draft-hellwig-nfsv4-scsi-layout-nvme-01~1 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=d633eb315b6ad550a3e0623b70bbc50023efeb17;p=users%2Fhch%2Fscsi-layout-nvme.git make EUI64 or NGUID support a requirement instead of a SHOULD As suggested by David Black. --- diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml index f5e9b8b..36f589f 100644 --- a/scsi_nvme_middle.xml +++ b/scsi_nvme_middle.xml @@ -71,15 +71,19 @@
- The SCSI layout uses the Device Identification VPD page (page code + The pNFS SCSI layout uses the Device Identification VPD page (page code 0x83) from to identify the devices used by - a layout. Section 6.1.4 of explains - how an an implementation SHOULD construct a valid Device - Identification VPD page based on the NVMe Identify data. - Only NVMe devices that support either the EUI64 or NGUID value in the - Identify Namespace data SHOULD be used as storage devices for the - pNFS SCSI layout, as the methods based on the Serial Number for - legacy devices might not be suitable for unique addressing needs. + a layout. Section 6.1.4 of lists ways + to build SCSI Device Identification descriptors from NVMe Identify + data. + + To be used as storage devices for the pNFS SCSI layout, NVMe devices + MUST support either the EUI64 or NGUID value in the + Identify Namespace data, as the methods based on the Serial Number for + legacy devices might not be suitable for unique addressing needs and + thus MUST NOT be used. If possible NVMe devices uses as storage + devices for the pNFS SCSI layout SHOULD support the NGUID value as + it is the larger identifier.