| < draft-ietf-imss-ip-over-fibre-channel-02.txt | draft-ietf-imss-ip-over-fibre-channel-03.txt > | |||
|---|---|---|---|---|
| IMSS Working Group C. DeSanti | IMSS Working Group C. DeSanti | |||
| Internet Draft Cisco Systems | Internet Draft Cisco Systems | |||
| draft-ietf-imss-ip-over-fibre-channel-02.txt C. Carlson | draft-ietf-imss-ip-over-fibre-channel-03.txt C. Carlson | |||
| Category: Standards Track QLogic Corporation | Category: Standards Track QLogic Corporation | |||
| Replaces: RFC 2625, RFC 3831 R. Nixon | Obsoletes: RFC 2625, RFC 3831 R. Nixon | |||
| Expires: April 2006 Emulex | Expires: May 2006 Emulex | |||
| October 2005 | November 2005 | |||
| Transmission of IPv6, IPv4 and ARP Packets over Fibre Channel | Transmission of IPv6, IPv4 and ARP Packets over Fibre Channel | |||
| Status of this Memo | Status of this Memo | |||
| By submitting this Internet-Draft, each author represents that any | By submitting this Internet-Draft, each author represents that any | |||
| applicable patent or other IPR claims of which he or she is aware | applicable patent or other IPR claims of which he or she is aware | |||
| have been or will be disclosed, and any of which he or she becomes | have been or will be disclosed, and any of which he or she becomes | |||
| aware will be disclosed, in accordance with Section 6 of BCP 79. | aware will be disclosed, in accordance with Section 6 of BCP 79. | |||
| skipping to change at page 3, line 16 ¶ | skipping to change at page 3, line 16 ¶ | |||
| Fibre Channel (FC) is a high speed serial interface technology that | Fibre Channel (FC) is a high speed serial interface technology that | |||
| supports several Upper Layer Protocols including Small Computer | supports several Upper Layer Protocols including Small Computer | |||
| System Interface (SCSI), IPv6 [IPv6] and IPv4 [IPv4]. | System Interface (SCSI), IPv6 [IPv6] and IPv4 [IPv4]. | |||
| [RFC-2625] defined how to encapsulate IPv4 and ARP packets over Fibre | [RFC-2625] defined how to encapsulate IPv4 and ARP packets over Fibre | |||
| Channel for a subset of Fibre Channel devices. This specification | Channel for a subset of Fibre Channel devices. This specification | |||
| enables the support of IPv4 for a broader category of Fibre Channel | enables the support of IPv4 for a broader category of Fibre Channel | |||
| devices. In addition, this specification simplifies [RFC-2625] by | devices. In addition, this specification simplifies [RFC-2625] by | |||
| removing unused options and clarifying what is currently implemented. | removing unused options and clarifying what is currently implemented. | |||
| This document replaces [RFC-2625]. | This document obsoletes [RFC-2625]. | |||
| Specific [RFC-2625] limitations that this document aims to resolve | Specific [RFC-2625] limitations that this document aims to resolve | |||
| are: | are: | |||
| - N_Port_Name format restriction. [RFC-2625] restricts the use of | - N_Port_Name format restriction. [RFC-2625] restricts the use of | |||
| IPv4 to Fibre Channel devices having format 0x1 N_Port_Name, but | IPv4 to Fibre Channel devices having format 0x1 N_Port_Name, but | |||
| many current implementations use other N_Port_Name formats; | many current implementations use other N_Port_Name formats; | |||
| - Use of FARP. [RFC-2625] requires the support of FARP to map | - Use of FARP. [RFC-2625] requires the support of FARP to map | |||
| N_Port_Names to N_Port_IDs, but many current implementations use | N_Port_Names to N_Port_IDs, but many current implementations use | |||
| other methods, such as the Fibre Channel Name Server; | other methods, such as the Fibre Channel Name Server; | |||
| - Missing support for IPv4 multicast. [RFC-2625] does not specify | - Missing support for IPv4 multicast. [RFC-2625] does not specify | |||
| how to transmit IPv4 packets with a multicast destination address | how to transmit IPv4 packets with a multicast destination address | |||
| over Fibre Channel. | over Fibre Channel. | |||
| [RFC-3831] defines how to encapsulate IPv6 over Fibre Channel and a | [RFC-3831] defines how to encapsulate IPv6 over Fibre Channel and a | |||
| method of forming IPv6 link-local addresses [AARCH] and statelessly | method of forming IPv6 link-local addresses [AARCH] and statelessly | |||
| autoconfigured IPv6 addresses on Fibre Channel networks. [RFC-3831] | autoconfigured IPv6 addresses on Fibre Channel networks. [RFC-3831] | |||
| describes also the content of the Source/Target Link-layer Address | describes also the content of the Source/Target Link-layer Address | |||
| option used in Neighbor Discovery [DISC] when the messages are | option used in Neighbor Discovery [DISC] when the messages are | |||
| transmitted on a Fibre Channel network. This document replaces | transmitted on a Fibre Channel network. This document obsoletes | |||
| [RFC-3831]. | [RFC-3831]. | |||
| Warning to readers familiar with Fibre Channel: both Fibre Channel | Warning to readers familiar with Fibre Channel: both Fibre Channel | |||
| and IETF standards use the same byte transmission order. However, | and IETF standards use the same byte transmission order. However, | |||
| the bit numbering is different. See Appendix C for guidance. | the bit numbering is different. See Appendix C for guidance. | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | |||
| document are to be interpreted as described in [KEYWORDS]. | document are to be interpreted as described in [KEYWORDS]. | |||
| skipping to change at page 13, line 29 ¶ | skipping to change at page 13, line 29 ¶ | |||
| of each Nx_Port or by the Path MTU Discovery technique [PMTUD4]. | of each Nx_Port or by the Path MTU Discovery technique [PMTUD4]. | |||
| 5. IPv6 Stateless Address Autoconfiguration | 5. IPv6 Stateless Address Autoconfiguration | |||
| 5.1. IPv6 Interface Identifier and Address Prefix | 5.1. IPv6 Interface Identifier and Address Prefix | |||
| The IPv6 Interface ID [AARCH] for an Nx_Port is based on the EUI-64 | The IPv6 Interface ID [AARCH] for an Nx_Port is based on the EUI-64 | |||
| address [EUI64] derived from the Nx_Port's N_Port_Name. The IPv6 | address [EUI64] derived from the Nx_Port's N_Port_Name. The IPv6 | |||
| Interface Identifier is obtained by complementing the Universal/Local | Interface Identifier is obtained by complementing the Universal/Local | |||
| (U/L) bit of the OUI field of the derived EUI-64 address. The U/L | (U/L) bit of the OUI field of the derived EUI-64 address. The U/L | |||
| bit has no function in Fibre Channel (because an N_Port_Name is used | bit has no function in Fibre Channel, however it has to be properly | |||
| only as an identifier, not as an address to which frames are | handled when a Name_Identifier is converted to an EUI-64 address. | |||
| forwarded), however it has to be properly handled when a | ||||
| Name_Identifier is converted to an EUI-64 address. | ||||
| [FC-FS] specifies a method to map format 0x1 (IEEE 48 bit address), | [FC-FS] specifies a method to map format 0x1 (IEEE 48 bit address), | |||
| or 0x2 (IEEE Extended), or 0x5 (IEEE Registered) FC Name_Identifiers | or 0x2 (IEEE Extended), or 0x5 (IEEE Registered) FC Name_Identifiers | |||
| in EUI-64 addresses. This allows the usage of these Name_Identifiers | in EUI-64 addresses. This allows the usage of these Name_Identifiers | |||
| to support IPv6. [FC-FS] also defines EUI-64 mapped FC | to support IPv6. [FC-FS] also defines EUI-64 mapped FC | |||
| Name_Identifiers (formats 0xC, 0xD, 0xE, and 0xF), that are derived | Name_Identifiers (formats 0xC, 0xD, 0xE, and 0xF), that are derived | |||
| from an EUI-64 address. It is possible to reverse this address | from an EUI-64 address. It is possible to reverse this address | |||
| mapping to obtain the original EUI-64 address in order to support | mapping to obtain the original EUI-64 address in order to support | |||
| IPv6. | IPv6. | |||
| skipping to change at page 25, line 49 ¶ | skipping to change at page 25, line 49 ¶ | |||
| the IP layer may be used in a Fibre Channel environment. | the IP layer may be used in a Fibre Channel environment. | |||
| 15. IANA Considerations | 15. IANA Considerations | |||
| The directory of ARP parameters should reference this document, when | The directory of ARP parameters should reference this document, when | |||
| published, for hardware type 18. | published, for hardware type 18. | |||
| 16. Acknowledgments | 16. Acknowledgments | |||
| The authors would like to acknowledge the ANSI INCITS T11.3 Task | The authors would like to acknowledge the ANSI INCITS T11.3 Task | |||
| Group members who reviewed this document. | Group members who reviewed this document as well as the authors of | |||
| [RFC-2625] and [RFC-3831]. | ||||
| 17. Normative References | 17. Normative References | |||
| [FC-FS] ANSI INCITS 373-2003, "Fibre Channel - Framing and | [FC-FS] ANSI INCITS 373-2003, "Fibre Channel - Framing and | |||
| Signaling (FC-FS)". | Signaling (FC-FS)". | |||
| [FC-AL-2] ANSI INCITS 332-1999, "Fibre Channel - Arbitrated Loop-2 | [FC-AL-2] ANSI INCITS 332-1999, "Fibre Channel - Arbitrated Loop-2 | |||
| (FC-AL-2)". | (FC-AL-2)". | |||
| [IPv6] Deering, S. and R. Hinden, "Internet Protocol, Version 6 | [IPv6] Deering, S. and R. Hinden, "Internet Protocol, Version 6 | |||
| End of changes. 6 change blocks. | ||||
| 11 lines changed or deleted | 10 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||