Network Working Group M. Krueger
Request for Comments: 3980 M. Chadalapaka
Updates: 3720 R. Elliott
Category: Standards Track Hewlett-Packard Corp.
February 2005
Network Working Group M. Krueger
Request for Comments: 3980 M. Chadalapaka
Updates: 3720 R. Elliott
Category: Standards Track Hewlett-Packard Corp.
February 2005
T11 Network Address Authority (NAA) Naming Format for iSCSI Node Names
T11 iSCSI节点名称的网络地址授权（NAA）命名格式
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（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 format to enable use of the "Network Address Authority" (NAA) worldwide naming format defined by the InterNational Committee for Information Technology Standards (INCITS) T11 - Fibre Channel (FC) protocols and used by Serial Attached SCSI (SAS). This document updates RFC 3720.
Internet小型计算机系统接口（iSCSI）是一种SCSI传输协议，它将SCSI系列协议映射到TCP/IP。本文档定义了一种附加的iSCSI节点名称类型格式，以便能够使用由国际信息技术标准委员会（INCITS）T11-光纤通道（FC）协议定义并由串行连接SCSI（SAS）使用的“网络地址管理机构”（NAA）全球命名格式。本文档更新了RFC 3720。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. iSCSI NAA Name Structure . . . . . . . . . . . . . . . . . . . 3
4.1. Type "naa." - Network Address Authority. . . . . . . . . 3
5. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. IQN. . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.2. SRP. . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.3. SAS. . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.4. NAA. . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.5. InfiniBand . . . . . . . . . . . . . . . . . . . . . . . 5
5.6. INCITS . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.7. T10. . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.8. T11. . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. iSCSI NAA Name Structure . . . . . . . . . . . . . . . . . . . 3
4.1. Type "naa." - Network Address Authority. . . . . . . . . 3
5. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.1. IQN. . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.2. SRP. . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.3. SAS. . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.4. NAA. . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.5. InfiniBand . . . . . . . . . . . . . . . . . . . . . . . 5
5.6. INCITS . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.7. T10. . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.8. T11. . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations. . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations. . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 8
This document discusses the motivation for adding an NAA type format as an iSCSI node naming 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.
本文档讨论了添加NAA类型格式作为iSCSI节点命名格式的动机，并根据iSCSI命名约定定义了此格式[RFC3720]。定义此格式将使同时包含iSCSI端口和SAS端口的SCSI存储设备能够使用相同的基于NAA的SCSI设备名称。
A number of networked transports currently provide 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 naming formats.
许多网络传输目前为SCSI协议提供端口抽象。这些传输都包含某种形式的全球唯一名称构造格式。下表总结了当前协议及其命名格式。
SCSI Transport Protocol Naming Format
-----------------------------------------------
| | EUI-64| NAA |IQN |
|----------------------------|-------|-----|----|
| iSCSI (Internet SCSI) | X | | X |
|----------------------------|-------|-----|----|
| FCP (Fibre Channel) | | X | |
|----------------------------|-------|-----|----|
| SAS (Serial Attached SCSI) | | X | |
|----------------------------|-------|-----|----|
| SRP (for InfiniBand) | X | | |
-----------------------------------------------
SCSI Transport Protocol Naming 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 that use various identifier registration authorities. This identifier format is used by the Fibre Channel and SAS SCSI transport protocols. As most existing networked SCSI ports today are either FC or SAS, the NAA format is the most commonly used identifier format for SCSI transports.
INCITS T11帧和信令规范[FC-FS]定义了一种称为网络地址授权（NAA）格式的格式，用于构造使用各种标识符注册授权的全球唯一标识符。此标识符格式由光纤通道和SAS SCSI传输协议使用。由于目前大多数现有的网络SCSI端口是FC或SAS，NAA格式是SCSI传输最常用的标识符格式。
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 SCSI storage device containing ports served by different transports.
如果iSCSI包含一种允许直接表示NAA格式名称的命名格式，那么它将有助于构建目标设备名称，该名称可以轻松地跨多个名称空间转换为包含由不同传输服务的端口的SCSI存储设备的名称。
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.
本文档定义了NAA类型的iSCSI命名格式，以便可以为同时具有SAS端口和iSCSI端口的SCSI目标分配一个NAA标识符作为SCSI设备名称的基础。
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. Adding 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 that define an NAA format SCSI device name. This would facilitate the creation of SCSI device names that are transport-independent. It would also contribute to the creation of SCSI Logical Unit (LU) names based on this SCSI device name.
INCITS T10 SCSI在[SPC3]中定义了字符串格式的SCSI目标设备名称，该名称在VPD第83页设备标识符页中报告。[SAM3]指定一个SCSI设备的SCSI名称字符串格式不得超过一个（即零个或一个）SCSI设备名称，无论SCSI设备支持的SCSI传输协议的数量如何。将INCITS T11定义的NAA格式添加为iSCSI设备名称的定义类型将使iSCSI设备命名格式在定义NAA格式SCSI设备名称的所有当前SCSI网络传输中更加一致。这将有助于创建独立于传输的SCSI设备名称。它还将有助于基于此SCSI设备名称创建SCSI逻辑单元（LU）名称。
This document defines an additional iSCSI name type:
本文档定义了另一种iSCSI名称类型：
type "naa." - the remainder of the string is an INCITS T11 defined Network Address Authority identifier in ASCII-encoded hexadecimal.
键入“naa”-字符串的其余部分是INCITS T11定义的网络地址授权标识符，采用ASCII编码的十六进制。
[FC-FS] defines a format for constructing globally unique identifiers, referred to as the Network Address Authority (NAA) format.
[FC-FS]定义了一种用于构造全局唯一标识符的格式，称为网络地址授权（NAA）格式。
The iSCSI NAA naming format is "naa.", followed by an NAA identifier represented in ASCII-encoded hexadecimal digits.
iSCSI NAA命名格式为“NAA”，后跟以ASCII编码的十六进制数字表示的NAA标识符。
An example of an iSCSI name with a 64-bit NAA value follows:
具有64位NAA值的iSCSI名称示例如下：
Type NAA identifier (ASCII-encoded hexadecimal)
+--++--------------+
| || |
Type NAA identifier (ASCII-encoded hexadecimal)
+--++--------------+
| || |
naa.52004567BA64678D
naa.52004567BA64678D
An example of an iSCSI name with a 128-bit NAA value follows:
具有128位NAA值的iSCSI名称示例如下：
Type NAA identifier (ASCII-encoded hexadecimal)
+--++------------------------------+
| || |
Type NAA identifier (ASCII-encoded hexadecimal)
+--++------------------------------+
| || |
naa.62004567BA64678D0123456789ABCDEF
naa.62004567BA64678D0123456789ABCDEF
The iSCSI NAA naming format might be used in an implementation when the infrastructure for generating NAA worldwide unique names is already in place because the device contains both SAS and iSCSI SCSI ports.
当用于生成NAA全球唯一名称的基础结构已经就绪时，可以在实现中使用iSCSI NAA命名格式，因为该设备同时包含SAS和iSCSI SCSI端口。
The NAA identifier 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 naming format exceeding the maximum size for iSCSI node names.
以ASCII十六进制表示形式格式化的NAA标识符的最大大小为32个字符（128位NAA格式）。因此，此命名格式不会超过iSCSI节点名称的最大大小。
iSCSI qualified name, an identifier format defined by the iSCSI protocol [RFC3720].
iSCSI限定名称，由iSCSI协议[RFC3720]定义的标识符格式。
SCSI RDMA Protocol. SRP defines a SCSI protocol mapping onto the InfiniBand (tm) Architecture and/or functionally similar cluster protocols [SRP].
SCSI RDMA协议。SRP定义了到InfiniBand（tm）体系结构和/或功能类似的群集协议[SRP]的SCSI协议映射。
Serial Attached SCSI. The Serial Attached SCSI (SAS) standard contains both a physical layer compatible with Serial ATA, and protocols for transporting SCSI commands to SAS devices and ATA commands to SATA devices [SAS].
串行连接SCSI。串行连接SCSI（SAS）标准包含与串行ATA兼容的物理层，以及用于将SCSI命令传输到SAS设备和将ATA命令传输到SATA设备[SAS]的协议。
Network Address Authority, a naming format defined by the INCITS T11 Fibre Channel protocols [FC-FS].
网络地址授权，由INCITS T11光纤通道协议[FC-FS]定义的命名格式。
An I/O architecture originally intended to replace PCI and to address high performance server interconnectivity [IB].
一种I/O体系结构，最初用于取代PCI并解决高性能服务器互连问题[IB]。
INCITS stands for InterNational Committee of Information Technology Standards. The INCITS has a broad standardization scope within the field of Information and Communications Technologies (ICT), encompassing storage, processing, transfer, display, management, organization, and retrieval of information. INCITS serves as ANSI's Technical Advisory Group for the ISO/IEC Joint Technical Committee 1 (JTC 1). See http://www.incits.org.
INCITS代表国际信息技术标准委员会。INCITS在信息和通信技术（ICT）领域具有广泛的标准化范围，包括信息的存储、处理、传输、显示、管理、组织和检索。INCITS作为ANSI的ISO/IEC联合技术委员会1（JTC 1）技术咨询小组。看见http://www.incits.org.
A technical committee within INCITS that develops standards and technical reports on I/O interfaces, particularly the series of SCSI (Small Computer Systems Interface) standards. See http://www.t10.org.
INCITS内部的一个技术委员会，负责制定I/O接口的标准和技术报告，特别是SCSI（小型计算机系统接口）系列标准。看见http://www.t10.org.
A technical committee within INCITS responsible for standards development in the areas of Intelligent Peripheral Interface (IPI), High-Performance Parallel Interface (HIPPI) and Fibre Channel (FC). See http://www.t11.org.
INCITS内部的一个技术委员会，负责智能外围接口（IPI）、高性能并行接口（HIPPI）和光纤通道（FC）领域的标准开发。看见http://www.t11.org.
This iSCSI naming format does not introduce any new security concerns for the iSCSI protocol beyond those of the other iSCSI naming formats. Please refer to [RFC3720], Section 8, for information on the security considerations for the iSCSI protocol.
除了其他iSCSI命名格式之外，此iSCSI命名格式不会为iSCSI协议带来任何新的安全问题。有关iSCSI协议安全注意事项的信息，请参阅[RFC3720]第8节。
[RFC3720] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M., and E. Zeidner, "Internet Small Computer Systems Interface (iSCSI)", RFC 3720, April 2004.
[RFC3720]Satran，J.，Meth，K.，Sapuntzakis，C.，Chadalapaka，M.，和E.Zeidner，“互联网小型计算机系统接口（iSCSI）”，RFC 3720，2004年4月。
[FC-FS] INCITS 373-2003, Fibre Channel Framing and Signaling Interface (FC-FS).
[FC-FS]INCITS 373-2003，光纤通道成帧和信令接口（FC-FS）。
[SPC3] T10/1416-D, SCSI Primary Commands - 3 (SPC-3).
[SPC3]T10/1416-D，SCSI主命令-3（SPC-3）。
[SAM3] T10/1561-D, SCSI Architecture Model - 3 (SAM-3).
[SAM3]T10/1561-D，SCSI体系结构模型-3（SAM-3）。
[IB] InfiniBand{tm} Architecture Specification, Vol. 1, Rel. 1.0.a, InfiniBand Trade Association (http://www.infinibandta.org).
[IB]InfiniBand{tm}体系结构规范，第1卷，Rel。1.0.a，InfiniBand贸易协会(http://www.infinibandta.org).
[SRP] INCITS 365-2002, SCSI RDMA Protocol (SRP).
[SRP]INCITS 365-2002，SCSI RDMA协议（SRP）。
[SAS] INCITS 376-2003, Serial Attached SCSI (SAS).
[SAS]INCITS 376-2003，串行连接SCSI（SAS）。
Authors' Addresses
作者地址
Marjorie Krueger Hewlett-Packard Company 8000 Foothills Blvd. Roseville, CA 95747-5668, USA
马乔里·克鲁格·惠普公司8000山麓大道。美国加利福尼亚州罗斯维尔95747-5668
EMail: marjorie_krueger@hp.com
EMail: marjorie_krueger@hp.com
Mallikarjun Chadalapaka Hewlett-Packard Company 8000 Foothills Blvd. Roseville, CA 95747-5668, USA
Mallikarjun Chadalapaka Hewlett-Packard Company 8000 Foothills Blvd。美国加利福尼亚州罗斯维尔95747-5668
EMail: cbm@rose.hp.com
EMail: cbm@rose.hp.com
Rob Elliott Hewlett-Packard Company MC 140801 PO Box 692000 Houston, TX 77269-2000, USA
Rob Elliott Hewlett-Packard Company MC 140801邮箱692000德克萨斯州休斯顿77269-2000
EMail: elliott@hp.com
EMail: elliott@hp.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
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.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
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 IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关IETF文件中权利的IETF程序信息，请参见BCP 78和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.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为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.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。