From 807e33b3c557a772a0927eb00a8d9c0d26eaefd1 Mon Sep 17 00:00:00 2001 From: Christoph Hellwig Date: Tue, 10 Oct 2023 11:46:05 +0200 Subject: [PATCH] expand acronyms on first use --- scsi-nvme.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/scsi-nvme.md b/scsi-nvme.md index a8ab04a..ef2d2b0 100644 --- a/scsi-nvme.md +++ b/scsi-nvme.md @@ -90,10 +90,9 @@ informative: --- abstract -This document specifies how to use the Parallel Network File System -(pNFS) SCSI Layout Type to access storage devices using the NVMe -protocol family. - +This document specifies how to use the Parallel Network File System (pNFS) +Small Computer System Interface (SCSI) Layout Type to access storage devices +using the Non-Volatile Memory Express (NVMe) protocol family. --- middle @@ -170,15 +169,16 @@ when using the pNFS SCSI layout with NVMe namespaces. ## Volume Identification {#ssc:volident} -The pNFS SCSI layout uses the Device Identification VPD page (page code -0x83) from {{SPC5}} to identify the devices used by +The pNFS SCSI layout uses the Device Identification Vital Product Data (VPD) +page (page code 0x83) from {{SPC5}} to identify the devices used by a layout. Implementations that use NVMe namespaces as storage devices map NVMe namespace identifiers to a subset of the identifiers that the Device Identification VPD page supports for SCSI logical units. To be used as storage devices for the pNFS SCSI layout, NVMe namespaces -MUST support either the EUI64 or NGUID value reported in a Namespace +MUST support either the IEEE Extended Unique Identifier (EUI64) or +Namespace Globally Unique Identifier (NGUID) value reported in a Namespace Identification Descriptor, the I/O Command Set Independent Identify Namespace Data Structure, and the Identify Namespace Data Structure, NVM Command Set. If available, use of the NGUID value is preferred @@ -331,8 +331,8 @@ deployed to that protocol. When using IP-based storage protocols such as NVMe over TCP, data confidentiality and integrity SHOULD be provided for traffic between pNFS clients and NVMe storage devices by using a secure communication -protocol such as TLS {{RFC8446}}. For NVMe over TCP, -TLS SHOULD be used as described in {{NVME-TCP}} to +protocol such as Transport Layer Security (TLS) {{RFC8446}}. For NVMe +over TCP, TLS SHOULD be used as described in {{NVME-TCP}} to protect traffic between pNFS clients and NVMe namespaces used as storage devices. -- 2.50.1