Internet Engineering Task Force (IETF) D. Black
Request for Comments: 6172 EMC
Updates: 4172 D. Peterson
Category: Standards Track Brocade
ISSN: 2070-1721 March 2011
Internet Engineering Task Force (IETF) D. Black
Request for Comments: 6172 EMC
Updates: 4172 D. Peterson
Category: Standards Track Brocade
ISSN: 2070-1721 March 2011
Deprecation of the Internet Fibre Channel Protocol (iFCP) Address Translation Mode
Internet光纤通道协议（iFCP）地址转换模式的弃用
Abstract
摘要
Changes to Fibre Channel have caused the specification of the Internet Fibre Channel Protocol (iFCP) address translation mode to become incorrect. Due to the absence of usage of iFCP address translation mode, it is deprecated by this document. iFCP address transparent mode remains correctly specified.
光纤通道的更改导致Internet光纤通道协议（iFCP）地址转换模式的规范变得不正确。由于没有使用iFCP地址转换模式，本文档不推荐使用该模式。iFCP地址透明模式保持正确指定。
iFCP address transparent mode has been implemented and is in current use; therefore, it is not affected by this document.
iFCP地址透明模式已实施，目前正在使用中；因此，它不受本文件的影响。
This document also records the state of Protocol Number 133, which was allocated for a pre-standard version of the Fibre Channel Internet Protocol (FCIP).
本文档还记录了为光纤通道互联网协议（FCIP）的预标准版本分配的协议编号133的状态。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6172.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6172.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction...................................................3
2. Conventions Used in This Document..............................3
3. iFCP Address Translation Mode..................................3
3.1. Problem Discussion........................................4
3.2. iFCP Address Translation Mode Deprecation.................4
4. FCIP and Protocol Number 133...................................5
5. Security Considerations........................................5
6. IANA Considerations............................................5
7. Conclusions....................................................5
8. References.....................................................5
8.1. Normative References......................................5
8.2. Informative References....................................6
9. Acknowledgments ...............................................6
1. Introduction...................................................3
2. Conventions Used in This Document..............................3
3. iFCP Address Translation Mode..................................3
3.1. Problem Discussion........................................4
3.2. iFCP Address Translation Mode Deprecation.................4
4. FCIP and Protocol Number 133...................................5
5. Security Considerations........................................5
6. IANA Considerations............................................5
7. Conclusions....................................................5
8. References.....................................................5
8.1. Normative References......................................5
8.2. Informative References....................................6
9. Acknowledgments ...............................................6
See Section 3 of [RFC4172] for introductory material on Fibre Channel concepts.
有关光纤通道概念的介绍材料，请参见[RFC4172]的第3节。
The Internet Fibre Channel Protocol (iFCP) [RFC4172] operates in two modes with respect to Fibre Channel N_PORT fabric addresses (24-bit N_PORT_IDs): address transparent mode and address translation mode (both modes are specified in [RFC4172]):
对于光纤通道N_端口结构地址（24位N_端口ID），Internet光纤通道协议（iFCP）[RFC4172]在两种模式下运行：地址透明模式和地址转换模式（这两种模式在[RFC4172]中指定）：
o Address transparent mode is a pass-through mode that preserves Fibre Channel N_PORT fabric addresses.
o 地址透明模式是一种传递模式，它保留光纤通道N_端口结构地址。
o Address translation mode is a Fibre Channel analog to Network Address Translation (NAT) in which iFCP gateways change Fibre Channel N_PORT fabric addresses at the boundary between Fibre Channel and the Internet. Both the source (S_ID) and destination (D_ID) N_PORT fabric addresses may be changed by the iFCP gateways.
o 地址转换模式是一种光纤通道模拟到网络地址转换（NAT），其中iFCP网关在光纤通道和Internet之间的边界处更改光纤通道N_端口结构地址。iFCP网关可以更改源（S_ID）和目标（D_ID）N_端口结构地址。
This document deprecates iFCP address translation mode because the specification has not tracked changes in Fibre Channel and because there are no known implementations.
本文档不推荐iFCP地址转换模式，因为该规范没有跟踪光纤通道中的更改，并且没有已知的实现。
Protocol Number 133 was allocated for a pre-standard version of the Fibre Channel Internet Protocol (FCIP) that encapsulated FC frames directly in IP packets. That protocol number is not used by the standard FCIP protocol [RFC3821] [FC-BB-3], but implementations of the pre-standard protocol were deployed. Therefore, this document makes no change to the current allocation of Protocol Number 133.
为光纤通道互联网协议（FCIP）的预标准版本分配了133号协议，该协议将FC帧直接封装在IP数据包中。标准FCIP协议[RFC3821][FC-BB-3]未使用该协议编号，但部署了预标准协议的实现。因此，本文件不对协议编号133的当前分配进行更改。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
iFCP address translation mode has to translate addresses embedded in transmitted data. This is analogous to NAT translation of IP addresses embedded in IP packets. Fibre Channel restricts the occurrence of embedded fabric addresses to control messages (frames); N_PORTs send and receive two types of control frames that may contain embedded fabric addresses:
iFCP地址转换模式必须转换嵌入传输数据中的地址。这类似于IP包中嵌入的IP地址的NAT转换。光纤通道限制嵌入式结构地址的出现以控制消息（帧）；N_端口发送和接收可能包含嵌入式结构地址的两种类型的控制帧：
o Extended Link Services (ELSs); and
o 扩展链接服务（ELSs）；和
o FC-4 Link Services (FC-4 LSs) for the Small Computer System Interface (SCSI) over Fibre Channel Protocol (FCP).
o 光纤通道协议（FCP）上小型计算机系统接口（SCSI）的FC-4链路服务（FC-4 LSs）。
The embedded fabric address translations for N_PORT control frames are specified in Section 7.3 of [RFC4172]. These translations were correct as specified for Fibre Channel as of approximately 2003, based on the [FC-FS] standard for ELSs and the [FCP] standard for FCP FC-4 LSs.
[RFC4172]第7.3节规定了N_端口控制帧的嵌入式结构地址转换。根据ELS的[FC-FS]标准和FCP FC-4 LSs的[FCP]标准，这些转换大约在2003年针对光纤通道的规定是正确的。
Significant changes have been made to FC control frames since the iFCP specification [RFC4172] was published; the currently applicable FC standards are [FC-LS] and [FCP-3], and additional changes are forthcoming in the [FC-LS-2] and [FCP-4] standards projects, which are nearing completion. These changes have caused Section 7.3 of [RFC4172] to become incorrect.
自iFCP规范[RFC4172]发布以来，FC控制框架发生了重大变化；目前适用的FC标准为[FC-LS]和[FCP-3]，即将完成的[FC-LS-2]和[FCP-4]标准项目也将进行其他变更。这些变更导致[RFC4172]第7.3节变得不正确。
Actual iFCP deployment has diverged significantly from that anticipated during the development of [RFC4172]. All deployments of iFCP known to the authors of this document use iFCP address transparent mode and are used only for FC inter-switch links. iFCP address translation mode as specified in [RFC4172] cannot be used for FC inter-switch links because the necessary embedded fabric address translations for FC inter-switch control messages (Switch Fabric Internal Link Services (ILSs)) have not been specified.
实际的iFCP部署与[RFC4172]开发过程中预期的部署有很大差异。本文档作者已知的所有iFCP部署都使用iFCP地址透明模式，并且仅用于FC交换机间链路。[RFC4172]中指定的iFCP地址转换模式不能用于FC交换机间链路，因为尚未指定FC交换机间控制消息（交换机结构内部链路服务（ILS））所需的嵌入式结构地址转换。
For the reasons described above, it is prudent to deprecate iFCP address translation mode in preference to updating it to the current state of Fibre Channel standards. Updating iFCP address translation mode would create a continuing requirement to update an unused protocol mode to match future changes to FC control frames.
出于上述原因，谨慎的做法是不推荐iFCP地址转换模式，而不是将其更新为光纤通道标准的当前状态。更新iFCP地址转换模式将持续要求更新未使用的协议模式，以匹配未来对FC控制帧的更改。
Therefore, this document deprecates iFCP address translation mode:
因此，本文档不推荐iFCP地址转换模式：
o iFCP address translation mode [RFC4172] SHOULD NOT be implemented and SHOULD NOT be used.
o 不应实施且不应使用iFCP地址转换模式[RFC4172]。
o The status of [RFC4172] remains Proposed Standard RFC in order to retain the specification of iFCP address transparent mode.
o [RFC4172]的状态仍然是建议的标准RFC，以保留iFCP地址透明模式的规范。
o The [RFC4172] specification of iFCP address translation mode should be treated as Historic [RFC2026].
o iFCP地址转换模式的[RFC4172]规范应视为历史[RFC2026]。
Protocol Number 133 was allocated for Fibre Channel (FC) [IANA-IP] and used by a pre-standard version of the FCIP protocol that encapsulates FC frames directly in IP packets. The standard FCIP protocol [RFC3821] [FC-BB-3] encapsulates FC frames in TCP and hence does not use Protocol Number 133, but implementations of the pre-standard version of the FCIP protocol were deployed [MR]. Based on this deployment, the protocol number needs to remain allocated.
协议编号133分配给光纤通道（FC）[IANA-IP]，并由FCIP协议的预标准版本使用，该协议将FC帧直接封装在IP数据包中。标准FCIP协议[RFC3821][FC-BB-3]将FC帧封装在TCP中，因此不使用协议编号133，但部署了FCIP协议的预标准版本的实现[MR]。基于此部署，协议号需要保持分配状态。
The security considerations for iFCP continue to apply; see Section 10 of [RFC4172].
iFCP的安全考虑继续适用；参见[RFC4172]第10节。
IANA has added this document as a supplemental reference for the allocation of Protocol Number 133 but hasn't changed that allocation.
IANA已添加本文件作为133号协议分配的补充参考，但未更改该分配。
For the reasons described in this document, iFCP Address Translation mode is deprecated, and the allocation of Protocol Number 133 remains unchanged at this time.
由于本文件所述原因，不推荐使用iFCP地址转换模式，协议编号133的分配此时保持不变。
[FC-FS] Fibre Channel Framing and Signaling Interface (FC-FS), ANSI INCITS 373-2003, October 2003.
[FC-FS]光纤通道成帧和信令接口（FC-FS），ANSI INCITS 373-2003，2003年10月。
[FC-LS] Fibre Channel - Link Services (FC-LS), ANSI INCITS 433-2007, July 2007.
[FC-LS]光纤通道-链路服务（FC-LS），ANSI INCITS 433-2007，2007年7月。
[FCP] Fibre Channel Protocol (FCP), ANSI INCITS 269-1996, April 1996.
[FCP]光纤通道协议（FCP），ANSI INCITS 269-1996，1996年4月。
[FCP-3] Fibre Channel Protocol - 3 (FCP-3), ISO/IEC 14776-223:2008, June 2008.
[FCP-3]光纤通道协议-3（FCP-3），ISO/IEC 14776-223:2008，2008年6月。
[IANA-IP] Assigned Internet Protocol Numbers, IANA Registry, http://www.iana.org, visited October 2010.
[IANA-IP]分配的互联网协议编号、IANA注册表、，http://www.iana.org，于2010年10月访问。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC4172] Monia, C., Mullendore, R., Travostino, F., Jeong, W., and M. Edwards, "iFCP - A Protocol for Internet Fibre Channel Storage Networking", RFC 4172, September 2005.
[RFC4172]Monia，C.，Mullendore，R.，Travostino，F.，Jeong，W.，和M.Edwards，“iFCP-互联网光纤通道存储网络协议”，RFC 4172，2005年9月。
[FC-BB-3] Fibre Channel Backbone - 3 (FC-BB-3), ANSI INCITS 414-2006, July 2006.
[FC-BB-3]光纤通道主干-3（FC-BB-3），ANSI INCITS 414-2006，2006年7月。
[FC-LS-2] Fibre Channel - Link Services - 2 (FC-LS-2), INCITS Project 2103-D, Technical Committee T11 (www.t11.org).
[FC-LS-2]光纤通道-链路服务-2（FC-LS-2），INCITS项目2103-D，技术委员会T11（www.T11.org）。
[FCP-4] Fibre Channel Protocol - 4 (FCP-4), INCITS Project 1828-D, Technical Committee T10 (www.t10.org).
[FCP-4]光纤通道协议-4（FCP-4），INCITS项目1828-D，技术委员会T10（www.T10.org）。
[MR] Rajagopal, M., Private email communication, June 2009.
[Rajagopal先生，M.，私人电子邮件通信，2009年6月。
[RFC3821] Rajagopal, M., Rodriguez, E., and R. Weber, "Fibre Channel Over TCP/IP (FCIP)", RFC 3821, July 2004.
[RFC3821]Rajagopal，M.，Rodriguez，E.，和R.Weber，“TCP/IP上的光纤通道（FCIP）”，RFC 38212004年7月。
The authors would like to thank Tom Talpey, David Harrington, Joe Touch, Paul Hoffman, and Pekka Savola for helpful comments on this document.
作者要感谢Tom Talpey、David Harrington、Joe Touch、Paul Hoffman和Pekka Savola对本文件的有益评论。
Authors' Addresses
作者地址
David L. Black EMC Corporation 176 South Street Hopkinton, MA 01748
David L.Black EMC Corporation马萨诸塞州霍普金顿南街176号01748
Phone: +1 (508) 293-7953
EMail: david.black@emc.com
Phone: +1 (508) 293-7953
EMail: david.black@emc.com
David Peterson Brocade Communications 6000 Nathan Lane North Plymouth, MN 55442
David Peterson Brocade Communications 6000明尼苏达州北普利茅斯内森巷55442
Phone: +1 (612) 802-3299
EMail: david.peterson@brocade.com
Phone: +1 (612) 802-3299
EMail: david.peterson@brocade.com