IP Storage Working Group Internet Draft M. Krueger M. Chadalapaka R. Elliott Document: Hewlett-Packard draft-ietf-ips-iSCSI-name-ext-03.txt Corp. Expires: December 2004 June 2004 NAA naming format for iSCSI Node Names Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress". The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt . The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html . This Internet-Draft will expire on December 30, 2004. Abstract iSCSI [RFC3720] is a SCSI transport protocol that maps the SCSI family of protocols onto TCP/IP. This document defines an additional iSCSI node name type format to enable use of the "Network Address Authority" (NAA) world wide naming format defined by ANSI T11 Fibre Channel (FC) protocols and used by SAS. This document updates RFC 3720. Krueger Expires - December 2004 [Page 1] iSCSI NAA Naming Format June 2004 Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [i]. Table of Contents 1. Introduction...................................................2 2. Background.....................................................2 3. Motivation.....................................................3 4. iSCSI Name Structure...........................................4 4.1 Type "naa." - Network Address Authority....................4 5. Terminology....................................................4 5.1 IQN........................................................4 5.2 SRP........................................................5 5.3 SAS........................................................5 5.4 NAA........................................................5 5.5 InfiniBand.................................................5 6. Security Considerations........................................5 7. IANA Considerations............................................5 8. References.....................................................5 8.1 Normative References.......................................5 8.2 Informative References.....................................5 9. Author Addresses...............................................6 10. Full Copyright Statement......................................6 11. Intellectual Property Statement...............................7 1. Introduction This document discusses the motivation for adding an NAA type format as an iSCSI node name format and defines this format in accordance with the iSCSI naming conventions [RFC3720]. Defining this format will enable storage devices containing both iSCSI ports and SAS ports to use the same NAA-based SCSI device name. 2. Background To date, there are a number of networked transports providing port abstractions to the SCSI protocol. These transports all incorporate some form of world-wide unique name construction format. The following table summarizes the current protocols and their name formats. Krueger Expires - December 2004 [Page 2] iSCSI NAA Naming Format June 2004 SCSI transport protocol Name Format ----------------------------------------------- | | EUI-64| NAA |IQN | |----------------------------|-------|-----|----| | iSCSI (Internet SCSI) | X | | X | |----------------------------|-------|-----|----| | FCP (Fibre Channel) | | X | | |----------------------------|-------|-----|----| | SAS (Serial Attached SCSI) | | X | | |----------------------------|-------|-----|----| | SRP (for InfiniBand) | X | | | ----------------------------------------------- The NAA format is used by the Fibre Channel and SAS protocols. This makes the NAA format the most commonly used identifier format for SCSI transports. Although one of the T11-defined NAA formats contains a mapping of EUI-64 numbers, it requires some mathematical manipulation to extract the EUI-64 identifier out of this format and the NAA EUI-64 mapping reserves 2 bits in the EUI-64 identifier, thereby reducing the EUI-64 namespace. 3. Motivation If iSCSI included a naming format that allowed direct representation of an NAA-format name, it would facilitate construction of a target device name that translates easily across multiple namespaces for a storage device containing ports served by different transports. This document defines an NAA type iSCSI naming format. One NAA identifier can be assigned as the basis for the SCSI device name for a target having SAS SCSI ports and iSCSI SCSI ports. T10 has defined a string format SCSI target device name in [SPC3] that is reported in the VPD page 83 device identifier page. [SAM3] specifies that a SCSI device shall have no more than one (i.e., zero or one) SCSI device name in the SCSI name string format regardless of the number of SCSI transport protocols supported by the SCSI device. Addition of the ANSI T11-defined NAA format as an defined type for iSCSI device names would make the iSCSI device naming format more consistent across all current SCSI networked transports which define an NAA format SCSI device name, facilitating the creation of SCSI device names that are transport-independent. This would also contribute to the creation of LU names based on this SCSI device name. Krueger Expires - December 2004 [Page 3] iSCSI NAA Naming Format June 2004 The T11 NAA formatted as an ASCII-hexadecimal representation has a maximum size of 32 characters (128 bit formats) - as a result there is no issue with this name format exceeding the maximum size for iSCSI node names. 4. iSCSI Name Structure This document defines an additional iSCSI name type: type "naa." - the remainder of the string is an ANSI T11 defined Network Address Authority identifier in ASCII-encoded hexadecimal. 4.1 Type "naa." - Network Address Authority The ANSI T11 FC-FS specification defines a format for constructing globally unique identifiers [FC-FS] referred to as a Network Address Authority (NAA) format. The iSCSI name format is "naa." followed by an NAA identifier (ASCII-encoded hexadecimal digits). Example iSCSI name with a 64-bit NAA value: Type NAA identifier (ASCII-encoded hexadecimal) +--++--------------+ | || | naa.52004567BA64678D Example iSCSI name with a 128-bit NAA value: Type NAA identifier (ASCII-encoded hexadecimal) +--++------------------------------+ | || | naa.62004567BA64678D0123456789ABCDEF The NAA iSCSI name format might be used in an implementation where the structure for generating FC NAA worldwide unique names is already in place because the device contains both Fibre Channel and iSCSI SCSI ports. 5. Terminology 5.1 IQN iSCSI qualified name, an identifier format defined by the iSCSI protocol [RFC3720]. Krueger Expires - December 2004 [Page 4] iSCSI NAA Naming Format June 2004 5.2 SRP SCSI RDMA Protocol. SRP defines a SCSI protocol mapping onto the InfiniBand (tm) Architecture and/or functionally similar cluster protocols [SRP]. 5.3 SAS Serial Attached SCSI. The Serial Attached SCSI (SAS) standard contains both a physical Layer that is compatible with Serial ATA and protocols for transporting SCSI commands to SAS devices and for transporting ATA commands to SATA devices [SAS]. 5.4 NAA Network Address Authority - a naming format defined by the ANSI T11 Fibre Channel protocols [FC-FS]. 5.5 InfiniBand An I/O architecture intended to replace PCI and address high performance server interconnect [IB]. 6. Security Considerations This iSCSI name format does not introduce any new security concerns for the iSCSI protocol beyond the other iSCSI naming formats. Please refer to RFC 3720, section 8 for information on the security considerations for the iSCSI protocol. 7. IANA Considerations This document has no actions for IANA. 8. References 8.1 Normative References [RFC 2026] Bradner, S., Ed, "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [RFC 3668] Bradner, S., Ed., "Intellectual Property Rights in IETF Technology", BCP 79, RFC 3668, February 2004. [RFC 3720] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M., Zeidner, E., "Internet Small Computer Systems Interface (iSCSI)", RFC 3720, April 2004. 8.2 Informative References [SPC3] T10/1416-D, SCSI Primary Commands - 3 (SPC-3). Krueger Expires - December 2004 [Page 5] iSCSI NAA Naming Format June 2004 [SAM3] T10/1561-D, SCSI Architecture Model - 3 (SAM-3). [FC-FS] INCITS 373:2003, Fibre Channel Framing and Signaling Interface (FC-FS). [IB] InfiniBand{tm} Architecture Specification, Vol. 1, Rel. 1.0.a, InfiniBand Trade Association (www.infinibandta.org). [SRP] INCITS.365:2002, SCSI RDMA Protocol (SRP). [SAS] INCITS.376:2003, Serial Attached SCSI (SAS). 9. Author Addresses Note: Email addresses are spelled out to attempt to protect the authors against ôemail address harvestingö programs. Marjorie Krueger Hewlett-Packard Company 8000 Foothills Blvd. Roseville, CA 95747-5668, USA E-mail: marjorie dot krueger at hp dot com Mallikarjun Chadalapaka Hewlett-Packard Company 8000 Foothills Blvd. Roseville, CA 95747-5668, USA E-mail: cbm at rose dot hp dot com Rob Elliott Hewlett-Packard Company MC 140801 PO Box 692000 Houston, TX 77269-2000 USA E-mail: elliott at hp dot com 10. Full Copyright Statement Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY Krueger Expires - December 2004 [Page 6] iSCSI NAA Naming Format June 2004 THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 11. Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Krueger Expires - December 2004 [Page 7]