INTERNET-DRAFT: draft-krueger-iscsi-name-ext-00.txt Marjorie Krueger Catagory: standards-track Mallikarjun Chadalapaka Rob Elliott Hewlett-Packard October 23, 2002 Definition of an NAA naming format for iSCSI Node Names 1 Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [1]. 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. 2 Abstract iSCSI is a SCSI transport protocol that maps the SCSI family of protocols onto TCP/IP [iSCSI]. This document defines an additional iSCSI node name type format to enable use of the NAA world wide naming format used by ANSI T11 Fibre Channel protocols. It is hoped that this definition would enable storage devices containing both iSCSI and FC ports to use the same NAA-based SCSI device name. Krueger, et.al. Expires April 2003 [Page 1] Internet Draft iSCSI-name-ext 24 Oct 2002 Table of Contents 1 Status of this Memo 1 2 Abstract 1 3 Introduction 2 4 Motivation 2 5 iSCSI Name Structure 4 5.1 Type "naa." - Network Address Authority 4 6 Terminology 4 6.1 IQN 4 6.2 SRP 4 6.3 SAS 4 6.4 NAA 5 6.5 Infiniband 5 7 Security Considerations 5 8 References and Bibliography 5 8.1 Normative References 5 8.2 Informative References: 6 9 Authors' Addresses 7 3 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. 4 Motivation To date, there are a number of networked transports providing port services to SCSI. These transports all incorporate some form of world- wide unique name construction format. EUI-64 NAA IQN iSCSI X X FC X SAS X Infiniband(SRP) X The NAA format is used by the Fibre Channel transport, the SAS protocol made a recent decision to use NAA identifier formats. This makes the NAA format the most commonly used identifier format for SCSI transports. Although one of the FC-defined NAA formats contains a mapping of EUI-64 Krueger, et.al. Expires April, 2003 [Page 2] Internet Draft iSCSI-name-ext 24 Oct 2002 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, therefore reducing the EUI-64 namespace. If iSCSI included a naming format that allowed direct representation of an NAA-format name, it would facilitate ease of construction of a target device name that translates easily across multiple namespaces for a storage device containing ports served by different transports. This document proposes adding an NAA type to the iSCSI naming formats in order to enable economy of worldwide-unique identifier assignment for multi-transport-enabled target devices: One NAA-type SCSI device name can be chosen for a target having SAS SCSI ports, FC SCSI ports and iSCSI SCSI ports. [Note: Today, FCP-2 does not have a dependable notion of SCSI device name. It is however expected that FCP-3 is likely to incorporate the idea of a device name, or platform name, subject to T10Æs decisions. If it does embrace the device name notion, the same NAA format could then form the basis for targets with SAS/FCP-3/iSCSI ports.] In addition, there is a movement afoot in T10 to define and report a single SCSI target device name (based on iSCSI's naming formats), especially when the SCSI device has multiple transports attached. This discussion arose as a result of a proposed change to SPC-3 (T10/02- 419r0: SPC-3 iSCSI device identifiers) that adds a device name to VPD page 83 device identifier page. Addition of the ANSI T11-defined NAA format as an allowed type for iSCSI name creation would make the iSCSI device naming format more palatable across all current SCSI networked transports, allowing the creation of SCSI device names that are transport-independent. A single SCSI device name would allow creation of LU names based on the SCSI device name - a converged string naming architecture across transports helps to build LU names that are in turn uniform. The FC NAA formatted as an ASCII-hexidecimal representation has a maximum size of 32 characters (128 bit formats) - as a result there is no issue with this name format exceeding the maximimum size for iSCSI node names. Krueger, et.al. Expires April, 2003 [Page 3] Internet Draft iSCSI-name-ext 24 Oct 2002 5 iSCSI Name Structure In addition to the iSCSI name types of "iqn." and "eui." type "naa." - the remainder of the string is an ANSI T10 defined Network Address Authority identifier in ASCII-encoded hexadecimal. 5.1 Type "naa." - Network Address Authority The ANSI T10 FC-FS specification defines a format for constructing globally unique identifiers [FC-FS]. The iSCSI name format is "naa." followed by an NAA identifier (ASCII- encoded hexadecimal digits). Example iSCSI name: Type NAA identifier (ASCII-encoded hexadecimal) +--++--------------+ | || | naa.02004567BA64678D 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. 6 Terminology 6.1 IQN iSCSI qualified name, an identifier format defined by the iSCSI protocol [iSCSI]. 6.2 SRP SCSI RDMA Protocol. SRP defines a SCSI protocol mapping onto the InfiniBand (tm) Architecture and/or functionally similar cluster protocols. [SRP] 6.3 SAS Serial Attached SCSI. The Serial Attached SCSI (SAS) draft 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] Krueger, et.al. Expires April, 2003 [Page 4] Internet Draft iSCSI-name-ext 24 Oct 2002 6.4 NAA Network Address Authority - a naming format defined by the ANSI T11 Fibre Channel protocols [FC-FS]. 6.5 Infiniband An I/O architecture intended to replace PCI and address high performance server interconnect. [IB] 7 Security Considerations Because this document does not define any new wire protocol, there are no additional security considerations from that of using the iSCSI protocol. 8 References and Bibliography 8.1 Normative References [ISP] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [iSCSI] J. Satran, K. Meth, C. Sapuntzakis, M. Chadalapaka, E. Zeidner, "iSCSI", Internet draft (work in progress), draft- ietf-ips-iscsi- 18.txt, September 2002. [RFC2026] Bradner, S., "The Internet Standards Process û Revision 3", RFC 2026, October 1996. [RFC2119] Bradner, S. "Key Words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [SAM2] T10/1157D, SCSI Architecture Model - 2 (SAM-2). [SPC] T10/1416-D, SCSI-3 Primary Commands. [FC-FS] T11/02-018v1 - dpANS - Fibre Channel Framing and Signaling Interface. [IB] Infiniband{tm} Architecture Specification, Vol. 1, Rel. 1.0.a, Infiniband Trade Association (www.infinibandta.org). [SRP] T10/1524D, SCSI RDMA Protocol-2. [SAS] T10/1562D, Serial Attached SCSI Protocol. Krueger, et.al. Expires April, 2003 [Page 5] Internet Draft iSCSI-name-ext 24 Oct 2002 8.2 Informative References: [SAM] ANSI X3.270-1998, SCSI-3 Architecture Model (SAM). [SPC3]T10/1416-D, SCSI Primary Commands-3. Krueger, et.al. Expires April, 2003 [Page 6] Internet Draft iSCSI-name-ext 24 Oct 2002 9 Authors' Addresses Comments may be sent to Marjorie Krueger. Mallikarjun Chadalapaka Hewlett-Packard Company 8000 Foothills Blvd. Roseville, CA 95747-5668, USA E-mail: cbm@rose.hp.com Marjorie Krueger Hewlett-Packard Company 8000 Foothills Blvd. Roseville, CA 95747-5668, USA E-mail: marjorie.krueger@hp.com Rob Elliot Hewlett-Packard Company E-mail: Elliot@hp.com Krueger, et.al. Expires April, 2003 [Page 7]