Update the Security Considerations section

Based on material from draft-faibish-nfsv4-scsi-nvme-layout-00.

Signed-off-by: Christoph Hellwig <hch@lst.de>

diff --git a/scsi_nvme_middle.xml b/scsi_nvme_middle.xml
index 0e960b098efc80e3397ec2ba04a1be5df6236767..4d10ceaddc55d1e036583e420456cc88b3a0a760 100644 (file)
--- a/scsi_nvme_middle.xml
+++ b/scsi_nvme_middle.xml
@@ -122,8 +122,20 @@
 
 <section anchor="sec:security" title="Security Considerations">
   <t>
-   Since no protocol changes are proposed here, no security
-   considerations apply.
+   The new layout type described in the current document assumes
+   that NVMe Authentication commands are implemented in the NVMe
+   Security Protocol, as the format of the data to be transferred is
+   dependent on the Security Protocol. Authentication Receive/Response
+   commands return data corresponding to an Authentication Send command
+   as defined by the rules of the Security Protocol.
+  </t>
+  <t>
+   As the layout type described in the current document supports only
+   the NVMe-over-Fabrics In-band protocol, the Authentication requirements
+   for security commands are based on the security protocol indicated
+   by the SECP field in the command and MUST NOT require authentication
+   when used for NVMe in-band authentication. When used for other
+   purposes, in-band authentication of the commands is REQUIRED.
   </t>
 </section>