IP over InfiniBand: Connected Mode
RFC 4755
|
Document |
Type |
|
RFC - Proposed Standard
(December 2006; No errata)
|
|
Author |
|
Vivek Kashyap
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
RFC 4755 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Margaret Cullen
|
|
Send notices to |
|
(None)
|
Network Working Group V. Kashyap
Request for Comments: 4755 IBM
Category: Standards Track December 2006
IP over InfiniBand: Connected Mode
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.
Copyright Notice
Copyright (C) The IETF Trust (2006).
Abstract
This document specifies transmission of IPv4/IPv6 packets and address
resolution over the connected modes of InfiniBand.
Kashyap Standards Track [Page 1]
RFC 4755 Connected Mode IPoIB December 2006
Table of Contents
1. Introduction ....................................................2
2. IPoIB-connected Mode ............................................3
2.1. Multicasting ...............................................3
2.2. Outline of Address Resolution ..............................4
2.3. Outline of Connection Setup ................................4
3. Address Resolution ..............................................4
3.1. Link-layer Address .........................................4
3.2. IB Connection Setup ........................................6
3.3. Simultaneous IB Connections ................................6
3.4. IPoIB-CM IB Connection Teardown ............................7
3.5. Service-ID .................................................7
4. Frame Format ....................................................8
5. Maximum Transmission Unit .......................................8
5.1. Per-Connection MTU .........................................9
6. Private-Data Format .............................................9
7. IPoIB-CM Considerations ........................................10
7.1. A Cautionary Note on IPoIB-RC .............................10
7.2. IPoIB-CM Per-Destination MTU ..............................10
8. Security Considerations ........................................11
9. IANA Considerations ............................................11
10. Acknowledgements ..............................................11
11. Normative References ..........................................11
12. Informative References ........................................11
1. Introduction
The InfiniBand specification [IB_ARCH] can be found at
www.infinibandta.org. The document [RFC4392] provides a short
overview of InfiniBand architecture along with consideration for
specifying IP over InfiniBand networks.
The InfiniBand Architecture (IBA) defines multiple modes of
transports. Of these the unreliable datagram (UD) transport method
best matches the needs of IP. IP over InfiniBand (IPoIB) over UD is
described in [RFC4391]. This document describes IP transmission over
the connected modes of IBA.
IBA defines two connected modes:
1. Reliable Connected (RC)
2. Unreliable Connected (UC)
As is evident from the nomenclature, the two modes differ mainly in
providing reliability of data delivery across the connection. This
document applies equally to both the connected modes. IPoIB over
these two modes is referred to as IPoIB-CM (connected mode) in this
Kashyap Standards Track [Page 2]
RFC 4755 Connected Mode IPoIB December 2006
document. For clarity, IPoIB over the unreliable datagram mode as
described in [RFC4391] is referred to as IPoIB-UD.
IBA requires that all Host Channel Adapters (HCAs) support the
reliable and unreliable connected modes [IB_ARCH]. It is optional
for Target Channel Adapters (TCAs) to support the connected modes.
The connected modes offer link MTUs of up to 2^31 octets in length.
Thus, the use of connected modes can offer significant benefits by
supporting reasonably large MTUs. The datagram modes of InfiniBand
Architecture (IBA) are limited to 4096 octets.
Reliability is also enhanced if the underlying feature of "automatic
path migration" supported by the connected modes is utilized.
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 RFC 2119 [RFC2119].
2. IPoIB-connected Mode
IPoIB over connected mode is an OPTIONAL extension to IPoIB-UD.
Every IPoIB implementation MUST support [RFC4391] and MAY support the
extensions described in this document.
Therefore, IP encapsulation, default MTU, link-layer address format,
Show full document text