Skip to main content

T11 Network Address Authority (NAA) Naming Format for iSCSI Node Names
draft-ietf-ips-iscsi-name-ext-05

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3980.
Authors Marjorie Krueger , Robert Elliott , Mallikarjun Chadalapaka
Last updated 2015-10-14 (Latest revision 2004-08-10)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3980 (Proposed Standard)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
Send notices to Elizabeth.Rodriguez@DotHill.com
draft-ietf-ips-iscsi-name-ext-05
IP Storage Working Group                                          
   Internet Draft                                         M. Krueger 
                                                      M. Chadalapaka 
                                                          R. Elliott 
   Document:                                         Hewlett-Packard 
   draft-ietf-ips-iscsi-name-ext-05.txt                        Corp. 

   Updates: 3720                                                     
                                                                     
   Expires: January 2005                                August 2004 
    
    
   T11 Network Address Authority (NAA) naming format for iSCSI Node 
                                 Names 
    
    
 Status of this Memo 
    
    
   By submitting this Internet-Draft, we certify that any applicable 
   patent or other IPR claims of which we are aware have been 
   disclosed, and any of which we 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 January 30, 2005. 
    
 Abstract 
    
   Internet Small Computer Systems Interface (iSCSI) is a SCSI 
   transport protocol that maps the SCSI family of protocols onto 
   TCP/IP.  This document defines an additional iSCSI node name type 
 
 
 Krueger                Expires - January 2005                [Page 1] 

                       iSCSI NAA Naming Format            August 2004 
 
 
   format to enable use of the "Network Address Authority" (NAA) 
   world wide naming format defined by InterNational Committee for 
   Information Technology Standards (INCITS) T11 - Fibre Channel 
   (FC) protocols and used by Serial Attached SCSI (SAS). This 
   document updates RFC 3720. 
    
 Table of Contents 
    
   1. Introduction...................................................2 
   2. Background.....................................................2 
   3. Motivation.....................................................3 
   4. iSCSI NAA Name Structure.......................................4 
      4.1 Type "naa." - Network Address Authority....................4 
   5. Terminology....................................................5 
      5.1 IQN........................................................5 
      5.2 SRP........................................................5 
      5.3 SAS........................................................5 
      5.4 NAA........................................................5 
      5.5 InfiniBand.................................................5 
      5.6 INCITS.....................................................5 
      5.7 T10........................................................5 
      5.8 T11........................................................5 
   6. Security Considerations........................................6 
   7. IANA Considerations............................................6 
   8. References.....................................................6 
      8.1 Normative References.......................................6 
      8.2 Informative References.....................................6 
   9. Authors' Addresses.............................................7 
   10. Full Copyright Statement......................................8 
   11. Intellectual Property Statement...............................8 
    
    
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 SCSI 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 - January 2005                [Page 2] 

                       iSCSI NAA Naming Format            August 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 INCITS T11 Framing and Signaling Specification [FC-FS] 
   defines a format called the Network Address Authority (NAA) 
   format for constructing worldwide unique identifiers using 
   various identifier registration authorities.  This identifier 
   format is used by the Fibre Channel and SAS SCSI transport 
   protocols.  Since most existing networked SCSI ports today are 
   either FC or SAS, the NAA format is the most commonly used 
   identifier format for SCSI transports. 
     
3.   Motivation 
    
   If iSCSI included a naming format that allowed direct 
   representation of a NAA-format name, it would facilitate 
   construction of a target device name that translates easily 
   across multiple namespaces for a SCSI storage device containing 
   ports served by different transports. 
    
   This document defines an NAA type iSCSI naming format so that one 
   NAA identifier can be assigned as the basis for the SCSI device 
   name for a SCSI target with both SAS ports and iSCSI ports. 
    
   INCITS T10 SCSI 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 INCITS 
   T11-defined NAA format as a 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 - January 2005                [Page 3] 

                       iSCSI NAA Naming Format            August 2004 
 
 
4.   iSCSI NAA Name Structure  
    
   This document defines an additional iSCSI name type: 
    
     type "naa." - the remainder of the string is an INCITS T11 
                  defined Network Address Authority identifier in 
                  ASCII-encoded hexadecimal.  
    
4.1     Type "naa." - Network Address Authority 
    
   [FC-FS] defines a format for constructing globally unique 
   identifiers referred to as the Network Address Authority (NAA) 
   format. 
     
   The iSCSI NAA name format is "naa." followed by an NAA identifier 
   represented in 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 iSCSI NAA name format might be used in an implementation 
   where the infrastructure for generating NAA worldwide unique 
   names is already in place because the device contains both SAS 
   and iSCSI SCSI ports. 
    
   The NAA name formatted in an ASCII-hexadecimal representation has 
   a maximum size of 32 characters (128 bit NAA format) - as a 
   result there is no issue with this name format exceeding the 
   maximum size for iSCSI node names. 

 
 
 Krueger                Expires - January 2005                [Page 4] 

                       iSCSI NAA Naming Format            August 2004 
 
 
    
5.   Terminology 
5.1    IQN 
   iSCSI qualified name, an identifier format defined by the iSCSI 
   protocol [RFC3720]. 
    
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 INCITS 
   T11 Fibre Channel protocols [FC-FS]. 
    
5.5    InfiniBand 
   An I/O architecture intended to replace PCI and address high 
   performance server interconnect [IB]. 
    
5.6    INCITS 
   InterNational Committee of Information Technology Standards is 
   the primary U.S. focus of standardization in the field of 
   Information and Communications Technologies (ICT), encompassing 
   storage, processing, transfer, display, management, organization, 
   and retrieval of information. As such, INCITS also serves as 
   ANSI's Technical Advisory Group for ISO/IEC Joint Technical 
   Committee 1. JTC 1 is responsible for International 
   standardization in the field of Information Technology.  See 
   www.incits.org 
    
5.7     T10 
   A technical committee within INCITS responsible for I/O 
   Interfaces, especially SCSI, SCSI-2, and SCSI-3 including SPI-2 
   (Fast-40 or Ultra2 SCSI), Low Voltage Differential (LVD), SPI-3 
   (Ultra3 SCSI or Ultra160), SPI-4 (Ultra320), SPI-5 (Ultra640), 
   Serial Attached SCSI (SAS).  See www.t10.org 
    
5.8     T11 
   A technical committee within INCITS responsible for Device Level 
   Interfaces. T11 (previously known as X3T9.3) has been producing 
   interface standards for high-performance and mass storage 
   applications.  See www.t11.org 
    
 
 
 Krueger                Expires - January 2005                [Page 5] 

                       iSCSI NAA Naming Format            August 2004 
 
 
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 3667] Bradner, S., Ed, "IETF Rights in Contributions", BCP 
              78, RFC 3667, February 2004. 
 
   [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. 
    
   [FC-FS]    INCITS 373:2003, Fibre Channel Framing and Signaling 
              Interface (FC-FS). 
    
8.2     Informative References 
    
   [SPC3]     T10/1416-D, SCSI Primary Commands - 3 (SPC-3). 
    
   [SAM3]     T10/1561-D, SCSI Architecture Model - 3 (SAM-3). 
    
    [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). 

 
 
 Krueger                Expires - January 2005                [Page 6] 

                       iSCSI NAA Naming Format            August 2004 
 
 
    
9.   Authors' Addresses 
    
   Marjorie Krueger 
   Hewlett-Packard Company 
   8000 Foothills Blvd. 
   Roseville, CA 95747-5668, USA 
   E-mail: marjorie_krueger@hp.com  
    
   Mallikarjun Chadalapaka 
   Hewlett-Packard Company 
   8000 Foothills Blvd. 
   Roseville, CA 95747-5668, USA 
   E-mail: cbm@rose.hp.com  
    
   Rob Elliott  
   Hewlett-Packard Company 
   MC 140801 
   PO Box 692000 
   Houston, TX 77269-2000  USA 
   E-mail: elliott@hp.com 

 
 
 Krueger                Expires - January 2005                [Page 7] 

                       iSCSI NAA Naming Format            August 2004 
 
 
    
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 
   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 - January 2005                [Page 8]