Difference between revisions of "RFC1294"
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Network Working Group T. Bradley | Network Working Group T. Bradley | ||
Request for Comments: 1294 C. Brown | Request for Comments: 1294 C. Brown | ||
| Line 10: | Line 5: | ||
BBN Communications | BBN Communications | ||
January 1992 | January 1992 | ||
| + | |||
Multiprotocol Interconnect over Frame Relay | Multiprotocol Interconnect over Frame Relay | ||
| − | == | + | |
| + | == Status of this Memo == | ||
| + | |||
This RFC specifies an IAB standards track protocol for the Internet | This RFC specifies an IAB standards track protocol for the Internet | ||
community, and requests discussion and suggestions for improvements. | community, and requests discussion and suggestions for improvements. | ||
| Line 17: | Line 15: | ||
Standards" for the standardization state and status of this protocol. | Standards" for the standardization state and status of this protocol. | ||
Distribution of this memo is unlimited. | Distribution of this memo is unlimited. | ||
| − | == | + | |
| + | == Abstract == | ||
| + | |||
This memo describes an encapsulation method for carrying network | This memo describes an encapsulation method for carrying network | ||
interconnect traffic over a Frame Relay backbone. It covers aspects | interconnect traffic over a Frame Relay backbone. It covers aspects | ||
| Line 25: | Line 25: | ||
method and this encapsulation must only be used over virtual circuits | method and this encapsulation must only be used over virtual circuits | ||
that have been explicitly configured for its use. | that have been explicitly configured for its use. | ||
| − | == | + | |
| + | == Acknowledgements == | ||
| + | |||
Comments and contributions from many sources, especially those from | Comments and contributions from many sources, especially those from | ||
Ray Samora of Proteon, Ken Rehbehn of Netrix Corporation, Fred Baker | Ray Samora of Proteon, Ken Rehbehn of Netrix Corporation, Fred Baker | ||
| Line 34: | Line 36: | ||
have been completed without the expertise of the IP over Large Public | have been completed without the expertise of the IP over Large Public | ||
Data Networks working group of the IETF. | Data Networks working group of the IETF. | ||
| − | == | + | |
| + | == Conventions == | ||
| + | |||
The following language conventions are used in the items of | The following language conventions are used in the items of | ||
specification in this document: | specification in this document: | ||
| + | |||
o Must, Shall or Mandatory -- the item is an absolute | o Must, Shall or Mandatory -- the item is an absolute | ||
requirement of the specification. | requirement of the specification. | ||
| + | |||
o Should or Recommended -- the item should generally be | o Should or Recommended -- the item should generally be | ||
followed for all but exceptional circumstances. | followed for all but exceptional circumstances. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
o May or Optional -- the item is truly optional and may be | o May or Optional -- the item is truly optional and may be | ||
followed or ignored according to the needs of the | followed or ignored according to the needs of the | ||
implementor. | implementor. | ||
| − | == | + | |
| + | == Introduction == | ||
| + | |||
The following discussion applies to those devices which serve as end | The following discussion applies to those devices which serve as end | ||
stations (DTEs) on a public or private Frame Relay network (for | stations (DTEs) on a public or private Frame Relay network (for | ||
| Line 58: | Line 60: | ||
Frame Relay network (DCEs) other than to explain situations in which | Frame Relay network (DCEs) other than to explain situations in which | ||
the DTE must react. | the DTE must react. | ||
| + | |||
The Frame Relay network provides a number of virtual circuits that | The Frame Relay network provides a number of virtual circuits that | ||
form the basis for connections between stations attached to the same | form the basis for connections between stations attached to the same | ||
| Line 67: | Line 70: | ||
Connection Identifier (DLCI). In most circumstances DLCIs have | Connection Identifier (DLCI). In most circumstances DLCIs have | ||
strictly local significance at each Frame Relay interface. | strictly local significance at each Frame Relay interface. | ||
| + | |||
The specifications in this document are intended to apply to both | The specifications in this document are intended to apply to both | ||
switched and permanent virtual circuits. | switched and permanent virtual circuits. | ||
| − | == | + | |
| + | == Frame Format == | ||
| + | |||
All protocols must encapsulate their packets within a Q.922 Annex A | All protocols must encapsulate their packets within a Q.922 Annex A | ||
frame [1,2]. Additionally, frames shall contain information | frame [1,2]. Additionally, frames shall contain information | ||
| Line 75: | Line 81: | ||
Unit (PDU), thus allowing the receiver to properly process the | Unit (PDU), thus allowing the receiver to properly process the | ||
incoming packet. The format shall be as follows: | incoming packet. The format shall be as follows: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
+-----------------------------+ | +-----------------------------+ | ||
| Line 123: | Line 108: | ||
| flag (7E hexadecimal) | | | flag (7E hexadecimal) | | ||
+-----------------------------+ | +-----------------------------+ | ||
| + | |||
* Q.922 addresses, as presently defined, are two octets and | * Q.922 addresses, as presently defined, are two octets and | ||
contain a 10-bit DLCI. In some networks Q.922 addresses may | contain a 10-bit DLCI. In some networks Q.922 addresses may | ||
optionally be increased to three or four octets. | optionally be increased to three or four octets. | ||
| + | |||
The control field is the Q.922 control field. The UI (0x03) value is | The control field is the Q.922 control field. The UI (0x03) value is | ||
used unless it is negotiated otherwise. The use of XID (0xAF or | used unless it is negotiated otherwise. The use of XID (0xAF or | ||
0xBF) is permitted and is discussed later. | 0xBF) is permitted and is discussed later. | ||
| + | |||
The pad field is an optional field used to align the remainder of the | The pad field is an optional field used to align the remainder of the | ||
frame to a convenient boundary for the sender. There may be zero or | frame to a convenient boundary for the sender. There may be zero or | ||
more pad octets within the pad field and all must have a value of | more pad octets within the pad field and all must have a value of | ||
zero. | zero. | ||
| + | |||
The Network Level Protocol ID (NLPID) field is administered by ISO | The Network Level Protocol ID (NLPID) field is administered by ISO | ||
and CCITT. It contains values for many different protocols including | and CCITT. It contains values for many different protocols including | ||
| Line 141: | Line 130: | ||
Layer or Inactive Set. Since it cannot be distinguished from a pad | Layer or Inactive Set. Since it cannot be distinguished from a pad | ||
field, and because it has no significance within the context of this | field, and because it has no significance within the context of this | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
encapsulation scheme, a NLPID value of 0x00 is invalid under the | encapsulation scheme, a NLPID value of 0x00 is invalid under the | ||
Frame Relay encapsulation. The known NLPID values are listed in the | Frame Relay encapsulation. The known NLPID values are listed in the | ||
Appendix. | Appendix. | ||
| + | |||
For full interoperability with older Frame Relay encapsulation | For full interoperability with older Frame Relay encapsulation | ||
formats, a station may implement section 15, Backward Compatibility. | formats, a station may implement section 15, Backward Compatibility. | ||
| + | |||
There is no commonly implemented maximum frame size for Frame Relay. | There is no commonly implemented maximum frame size for Frame Relay. | ||
A network must, however, support at least a 262 octet maximum. | A network must, however, support at least a 262 octet maximum. | ||
| Line 159: | Line 144: | ||
its network. A Frame Relay DTE, therefore, must allow the maximum | its network. A Frame Relay DTE, therefore, must allow the maximum | ||
acceptable frame size to be configurable. | acceptable frame size to be configurable. | ||
| + | |||
The minimum frame size allowed for Frame Relay is five octets between | The minimum frame size allowed for Frame Relay is five octets between | ||
the opening and closing flags. | the opening and closing flags. | ||
| − | == | + | |
| + | == Interconnect Issues == | ||
| + | |||
There are two basic types of data packets that travel within the | There are two basic types of data packets that travel within the | ||
Frame Relay network, routed packets and bridged packets. These | Frame Relay network, routed packets and bridged packets. These | ||
| Line 168: | Line 156: | ||
contents of the frame. This indication is embedded within the NLPID | contents of the frame. This indication is embedded within the NLPID | ||
and SNAP header information. | and SNAP header information. | ||
| + | |||
For those protocols that do not have a NLPID already assigned, it is | For those protocols that do not have a NLPID already assigned, it is | ||
necessary to provide a mechanism to allow easy protocol | necessary to provide a mechanism to allow easy protocol | ||
identification. There is a NLPID value defined indicating the | identification. There is a NLPID value defined indicating the | ||
presence of a SNAP header. | presence of a SNAP header. | ||
| + | |||
A SNAP header is of the form | A SNAP header is of the form | ||
| + | |||
+-------------------------------+ | +-------------------------------+ | ||
| Organizationally Unique | | | Organizationally Unique | | ||
| Line 180: | Line 171: | ||
| Identifier | | | Identifier | | ||
+---------------+ | +---------------+ | ||
| + | |||
All stations must be able to accept and properly interpret both the | All stations must be able to accept and properly interpret both the | ||
NLPID encapsulation and the SNAP header encapsulation for a routed | NLPID encapsulation and the SNAP header encapsulation for a routed | ||
packet. | packet. | ||
| + | |||
The three-octet Organizationally Unique Identifier (OUI) identifies | The three-octet Organizationally Unique Identifier (OUI) identifies | ||
an organization which administers the meaning of the Protocol | an organization which administers the meaning of the Protocol | ||
Identifier (PID) which follows. Together they identify a distinct | Identifier (PID) which follows. Together they identify a distinct | ||
| + | protocol. Note that OUI 0x00-00-00 specifies that the following PID | ||
| + | is an EtherType. | ||
| + | === Routed Frames === | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Some protocols will have an assigned NLPID, but because the NLPID | Some protocols will have an assigned NLPID, but because the NLPID | ||
numbering space is so limited many protocols do not have a specific | numbering space is so limited many protocols do not have a specific | ||
| Line 202: | Line 191: | ||
indicates a SNAP follows), OUI 0x00-00-00 (which indicates an | indicates a SNAP follows), OUI 0x00-00-00 (which indicates an | ||
EtherType follows), and the EtherType of the protocol in use. | EtherType follows), and the EtherType of the protocol in use. | ||
| + | |||
Format of Routed Frames | Format of Routed Frames | ||
+-------------------------------+ | +-------------------------------+ | ||
| Line 218: | Line 208: | ||
| FCS | | | FCS | | ||
+-------------------------------+ | +-------------------------------+ | ||
| + | |||
In the few cases when a protocol has an assigned NLPID (see | In the few cases when a protocol has an assigned NLPID (see | ||
appendix), 48 bits can be saved using the format below: | appendix), 48 bits can be saved using the format below: | ||
| + | |||
Format of Routed NLPID Protocol | Format of Routed NLPID Protocol | ||
+-------------------------------+ | +-------------------------------+ | ||
| Line 231: | Line 223: | ||
+-------------------------------+ | +-------------------------------+ | ||
| + | In the particular case of an Internet IP datagram, the NLPID is 0xCC. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Format of Routed IP Datagram | Format of Routed IP Datagram | ||
+-------------------------------+ | +-------------------------------+ | ||
| Line 254: | Line 235: | ||
| FCS | | | FCS | | ||
+-------------------------------+ | +-------------------------------+ | ||
| − | === | + | |
| + | === Bridged Frames === | ||
| + | |||
The second type of Frame Relay traffic is bridged packets. These | The second type of Frame Relay traffic is bridged packets. These | ||
packets are encapsulated using the NLPID value of 0x80 indicating | packets are encapsulated using the NLPID value of 0x80 indicating | ||
| Line 263: | Line 246: | ||
SNAP header. Additionally, the PID indicates whether the original | SNAP header. Additionally, the PID indicates whether the original | ||
FCS is preserved within the bridged frame. | FCS is preserved within the bridged frame. | ||
| + | |||
The 802.1 organization has reserved the following values to be used | The 802.1 organization has reserved the following values to be used | ||
with Frame Relay: | with Frame Relay: | ||
| + | |||
PID Values for OUI 0x00-80-C2 | PID Values for OUI 0x00-80-C2 | ||
| + | |||
with preserved FCS w/o preserved FCS Media | with preserved FCS w/o preserved FCS Media | ||
------------------ ----------------- ---------------- | ------------------ ----------------- ---------------- | ||
| Line 273: | Line 259: | ||
0x00-04 0x00-0A FDDI | 0x00-04 0x00-0A FDDI | ||
0x00-05 0x00-0B 802.6 | 0x00-05 0x00-0B 802.6 | ||
| + | |||
In addition, the PID value 0x00-0E, when used with OUI 0x00-80-C2, | In addition, the PID value 0x00-0E, when used with OUI 0x00-80-C2, | ||
identifies Bridged Protocol Data Units (BPDUs). | identifies Bridged Protocol Data Units (BPDUs). | ||
| + | |||
A packet bridged over Frame Relay will, therefore, have one of the | A packet bridged over Frame Relay will, therefore, have one of the | ||
following formats: | following formats: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Format of Bridged Ethernet/802.3 Frame | Format of Bridged Ethernet/802.3 Frame | ||
| Line 310: | Line 286: | ||
| FCS | | | FCS | | ||
+-------------------------------+ | +-------------------------------+ | ||
| + | |||
Format of Bridged 802.4 Frame | Format of Bridged 802.4 Frame | ||
+-------------------------------+ | +-------------------------------+ | ||
| Line 332: | Line 309: | ||
| FCS | | | FCS | | ||
+-------------------------------+ | +-------------------------------+ | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Format of Bridged 802.5 Frame | Format of Bridged 802.5 Frame | ||
| Line 369: | Line 335: | ||
| FCS | | | FCS | | ||
+-------------------------------+ | +-------------------------------+ | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Format of Bridged FDDI Frame | Format of Bridged FDDI Frame | ||
| Line 424: | Line 361: | ||
| FCS | | | FCS | | ||
+-------------------------------+ | +-------------------------------+ | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Format of Bridged 802.6 Frame | Format of Bridged 802.6 Frame | ||
| Line 479: | Line 387: | ||
| FCS | | | FCS | | ||
+-------------------------------+ | +-------------------------------+ | ||
| + | |||
The Common Protocol Data Unit (PDU) Header and Trailer are | The Common Protocol Data Unit (PDU) Header and Trailer are | ||
conveyed to allow pipelining at the egress bridge to an 802.6 | conveyed to allow pipelining at the egress bridge to an 802.6 | ||
| Line 492: | Line 401: | ||
subnetwork. Thus, the bridge can begin transmitting the 802.6 PDU | subnetwork. Thus, the bridge can begin transmitting the 802.6 PDU | ||
before it has received the complete PDU. | before it has received the complete PDU. | ||
| + | |||
One should note that the Common PDU Header and Trailer of the | One should note that the Common PDU Header and Trailer of the | ||
encapsulated frame should not be simply copied to the outgoing | encapsulated frame should not be simply copied to the outgoing | ||
802.6 subnetwork because the encapsulated BEtag value may conflict | 802.6 subnetwork because the encapsulated BEtag value may conflict | ||
with the previous BEtag value transmitted by that bridge. | with the previous BEtag value transmitted by that bridge. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Format of BPDU Frame | Format of BPDU Frame | ||
| Line 527: | Line 427: | ||
| FCS | | | FCS | | ||
+-------------------------------+ | +-------------------------------+ | ||
| − | == | + | |
| + | == Data Link Layer Parameter Negotiation == | ||
| + | |||
Frame Relay stations may choose to support the Exchange | Frame Relay stations may choose to support the Exchange | ||
Identification (XID) specified in Appendix III of Q.922 [1]. This | Identification (XID) specified in Appendix III of Q.922 [1]. This | ||
| Line 534: | Line 436: | ||
retransmission timer T200, and the maximum number of outstanding I | retransmission timer T200, and the maximum number of outstanding I | ||
frames K. | frames K. | ||
| + | |||
A station may indicate its unwillingness to support acknowledged mode | A station may indicate its unwillingness to support acknowledged mode | ||
multiple frame operation by specifying a value of zero for the | multiple frame operation by specifying a value of zero for the | ||
maximum window size, K. | maximum window size, K. | ||
| + | |||
If this exchange is not used, these values must be statically | If this exchange is not used, these values must be statically | ||
configured by mutual agreement of Data Link Connection (DLC) | configured by mutual agreement of Data Link Connection (DLC) | ||
endpoints, or must be defaulted to the values specified in Section | endpoints, or must be defaulted to the values specified in Section | ||
5.9 of Q.922: | 5.9 of Q.922: | ||
| + | |||
N201: 260 octets | N201: 260 octets | ||
| + | |||
K: 3 for a 16 Kbps link, | K: 3 for a 16 Kbps link, | ||
7 for a 64 Kbps link, | 7 for a 64 Kbps link, | ||
32 for a 384 Kbps link, | 32 for a 384 Kbps link, | ||
40 for a 1.536 Mbps or above link | 40 for a 1.536 Mbps or above link | ||
| + | |||
T200: 1.5 seconds [see Q.922 for further details] | T200: 1.5 seconds [see Q.922 for further details] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
If a station supporting XID receives an XID frame, it shall respond | If a station supporting XID receives an XID frame, it shall respond | ||
| Line 561: | Line 461: | ||
specified value. Note that this shall be done before generating a | specified value. Note that this shall be done before generating a | ||
response XID. | response XID. | ||
| + | |||
The following diagram describes the use of XID to specify non-use of | The following diagram describes the use of XID to specify non-use of | ||
acknowledged mode multiple frame operation. | acknowledged mode multiple frame operation. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Non-use of Acknowledged Mode Multiple Frame Operation | Non-use of Acknowledged Mode Multiple Frame Operation | ||
| Line 653: | Line 509: | ||
+---------------+ | +---------------+ | ||
| + | == Fragmentation Issues == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Fragmentation allows the exchange of packets that are greater than | Fragmentation allows the exchange of packets that are greater than | ||
the maximum frame size supported by the underlying network. In the | the maximum frame size supported by the underlying network. In the | ||
| Line 670: | Line 516: | ||
small as 262 octets. Because of this small maximum size, it is | small as 262 octets. Because of this small maximum size, it is | ||
advantageous to support fragmentation and reassembly. | advantageous to support fragmentation and reassembly. | ||
| + | |||
Unlike IP fragmentation procedures, the scope of Frame Relay | Unlike IP fragmentation procedures, the scope of Frame Relay | ||
fragmentation procedure is limited to the boundary (or DTEs) of the | fragmentation procedure is limited to the boundary (or DTEs) of the | ||
Frame Relay network. | Frame Relay network. | ||
| + | |||
The general format of fragmented packets is the same as any other | The general format of fragmented packets is the same as any other | ||
encapsulated protocol. The most significant difference being that | encapsulated protocol. The most significant difference being that | ||
| Line 683: | Line 531: | ||
the reassembled packet through the same processing path as a packet | the reassembled packet through the same processing path as a packet | ||
that had not been fragmented. | that had not been fragmented. | ||
| + | |||
Within Frame Relay fragments are encapsulated using the SNAP format | Within Frame Relay fragments are encapsulated using the SNAP format | ||
with an OUI of 0x00-80-C2 and a PID of 0x00-0D. Individual fragments | with an OUI of 0x00-80-C2 and a PID of 0x00-0D. Individual fragments | ||
will, therefore, have the following format: | will, therefore, have the following format: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
+---------------+---------------+ | +---------------+---------------+ | ||
| Line 737: | Line 558: | ||
| FCS | | | FCS | | ||
+---------------+---------------+ | +---------------+---------------+ | ||
| + | |||
The sequence field is a two octet identifier that is incremented | The sequence field is a two octet identifier that is incremented | ||
every time a new complete message is fragmented. It allows detection | every time a new complete message is fragmented. It allows detection | ||
of lost frames and is set to a random value at initialization. | of lost frames and is set to a random value at initialization. | ||
| + | |||
The reserved field is 4 bits long and is not currently defined. It | The reserved field is 4 bits long and is not currently defined. It | ||
must be set to 0. | must be set to 0. | ||
| + | |||
The final bit is a one bit field set to 1 on the last fragment and | The final bit is a one bit field set to 1 on the last fragment and | ||
set to 0 for all other fragments. | set to 0 for all other fragments. | ||
| + | |||
The offset field is an 11 bit value representing the logical offset | The offset field is an 11 bit value representing the logical offset | ||
of this fragment in bytes divided by 32. The first fragment must have | of this fragment in bytes divided by 32. The first fragment must have | ||
an offset of zero. | an offset of zero. | ||
| + | |||
The following figure shows how a large IP datagram is fragmented over | The following figure shows how a large IP datagram is fragmented over | ||
Frame Relay. In this example, the complete datagram is fragmented | Frame Relay. In this example, the complete datagram is fragmented | ||
into two Frame Relay frames. | into two Frame Relay frames. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Frame Relay Fragmentation Example | Frame Relay Fragmentation Example | ||
| Line 810: | Line 622: | ||
| FCS | | | FCS | | ||
+-----------+-----------+ | +-----------+-----------+ | ||
| + | |||
Fragments must be sent in order starting with a zero offset and | Fragments must be sent in order starting with a zero offset and | ||
ending with the final fragment. These fragments must not be | ending with the final fragment. These fragments must not be | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
interrupted with other packets or information intended for the same | interrupted with other packets or information intended for the same | ||
| Line 825: | Line 632: | ||
fragment is missing, the entire message is dropped. The upper layer | fragment is missing, the entire message is dropped. The upper layer | ||
protocol is responsible for any retransmission in this case. | protocol is responsible for any retransmission in this case. | ||
| + | |||
This fragmentation algorithm is not intended to reliably handle all | This fragmentation algorithm is not intended to reliably handle all | ||
possible failure conditions. As with IP fragmentation, there is a | possible failure conditions. As with IP fragmentation, there is a | ||
| Line 830: | Line 638: | ||
packet. Inclusion of a higher layer checksum greatly reduces this | packet. Inclusion of a higher layer checksum greatly reduces this | ||
risk. | risk. | ||
| + | |||
10. Address Resolution | 10. Address Resolution | ||
| + | |||
There are situations in which a Frame Relay station may wish to | There are situations in which a Frame Relay station may wish to | ||
dynamically resolve a protocol address. Address resolution may be | dynamically resolve a protocol address. Address resolution may be | ||
accomplished using the standard Address Resolution Protocol (ARP) [6] | accomplished using the standard Address Resolution Protocol (ARP) [6] | ||
encapsulated within a SNAP encoded Frame Relay packet as follows: | encapsulated within a SNAP encoded Frame Relay packet as follows: | ||
| + | |||
+-----------------------+-----------------------+ | +-----------------------+-----------------------+ | ||
| Q.922 Address | | | Q.922 Address | | ||
| Line 852: | Line 663: | ||
+-----------------------+-----------------------+ | +-----------------------+-----------------------+ | ||
| + | Where the ARP packet has the following format and values: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Data: | Data: | ||
ar$hrd 16 bits Hardware type | ar$hrd 16 bits Hardware type | ||
| Line 881: | Line 675: | ||
ar$tha noctets target hardware address | ar$tha noctets target hardware address | ||
ar$tpa moctets target protocol address | ar$tpa moctets target protocol address | ||
| + | |||
ar$hrd - assigned to Frame Relay is 15 decimal | ar$hrd - assigned to Frame Relay is 15 decimal | ||
(0x000F) [7]. | (0x000F) [7]. | ||
| + | |||
ar$pro - see assigned numbers for protocol ID number for | ar$pro - see assigned numbers for protocol ID number for | ||
the protocol using ARP. (IP is 0x0800). | the protocol using ARP. (IP is 0x0800). | ||
| + | |||
ar$hln - length in bytes of the address field (2, 3, or 4) | ar$hln - length in bytes of the address field (2, 3, or 4) | ||
| + | |||
ar$pln - protocol address length is dependent on the | ar$pln - protocol address length is dependent on the | ||
protocol (ar$pro) (for IP ar$pln is 4). | protocol (ar$pro) (for IP ar$pln is 4). | ||
| + | |||
ar$op - 1 for request and 2 for reply. | ar$op - 1 for request and 2 for reply. | ||
| + | |||
ar$sha - Q.922 source hardware address, with C/R, FECN, | ar$sha - Q.922 source hardware address, with C/R, FECN, | ||
BECN, and DE set to zero. | BECN, and DE set to zero. | ||
| + | |||
ar$tha - Q.922 target hardware address, with C/R, FECN, | ar$tha - Q.922 target hardware address, with C/R, FECN, | ||
BECN, and DE set to zero. | BECN, and DE set to zero. | ||
| + | |||
Because DLCIs within most Frame Relay networks have only local | Because DLCIs within most Frame Relay networks have only local | ||
significance, an end station will not have a specific DLCI assigned | significance, an end station will not have a specific DLCI assigned | ||
| Line 900: | Line 702: | ||
proposed for the locally addressed Frame Relay network below will | proposed for the locally addressed Frame Relay network below will | ||
work equally well for a network where DLCIs have global significance. | work equally well for a network where DLCIs have global significance. | ||
| + | |||
The DLCI carried within the Frame Relay header is modified as it | The DLCI carried within the Frame Relay header is modified as it | ||
traverses the network. When the packet arrives at its destination, | traverses the network. When the packet arrives at its destination, | ||
| Line 909: | Line 712: | ||
the network and would appear to B as DLCI 70. | the network and would appear to B as DLCI 70. | ||
| − | + | 07:15, 7 May 2021 (UTC)07:15, 7 May 2021 (UTC)07:15, 7 May 2021 (UTC) | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
( ) | ( ) | ||
+-----+ ( ) +-----+ | +-----+ ( ) +-----+ | ||
| Line 924: | Line 721: | ||
( | ) | ( | ) | ||
( | ) <---Frame Relay | ( | ) <---Frame Relay | ||
| − | + | 07:15, 7 May 2021 (UTC)07:15, 7 May 2021 (UTC)07:15, 7 May 2021 (UTC)~ network | |
80 | 80 | ||
| | | | ||
| Line 933: | Line 730: | ||
+-----+ | +-----+ | ||
Figure 1 | Figure 1 | ||
| + | |||
Lines between stations represent data link connections (DLCs). | Lines between stations represent data link connections (DLCs). | ||
The numbers indicate the local DLCI associated with each | The numbers indicate the local DLCI associated with each | ||
connection. | connection. | ||
| + | |||
DLCI to Q.922 Address Table for Figure 1 | DLCI to Q.922 Address Table for Figure 1 | ||
| + | |||
DLCI (decimal) Q.922 address (hex) | DLCI (decimal) Q.922 address (hex) | ||
50 0x0C21 | 50 0x0C21 | ||
| Line 942: | Line 742: | ||
70 0x1061 | 70 0x1061 | ||
80 0x1401 | 80 0x1401 | ||
| + | |||
If you know about frame relay, you should understand the | If you know about frame relay, you should understand the | ||
corrolation between DLCI and Q.922 address. For the uninitiated, | corrolation between DLCI and Q.922 address. For the uninitiated, | ||
| Line 947: | Line 748: | ||
byte address length using the Q.922 encoding format. The format | byte address length using the Q.922 encoding format. The format | ||
is: | is: | ||
| + | |||
8 7 6 5 4 3 2 1 | 8 7 6 5 4 3 2 1 | ||
+------------------------+---+--+ | +------------------------+---+--+ | ||
| Line 953: | Line 755: | ||
| DLCI (lower) |FECN|BECN|DE |EA| | | DLCI (lower) |FECN|BECN|DE |EA| | ||
+--------------+----+----+---+--+ | +--------------+----+----+---+--+ | ||
| + | |||
For ARP and its variants, the FECN, BECN, C/R and DE bits are | For ARP and its variants, the FECN, BECN, C/R and DE bits are | ||
assumed to be 0. | assumed to be 0. | ||
| + | |||
When an ARP message reaches a destination, all hardware addresses | When an ARP message reaches a destination, all hardware addresses | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
will be invalid. The address found in the frame header will, | will be invalid. The address found in the frame header will, | ||
| Line 971: | Line 769: | ||
an implementation may zero fill or ignore the target hardware address | an implementation may zero fill or ignore the target hardware address | ||
field entirely. | field entirely. | ||
| + | |||
As an example of how this address replacement scheme may work, refer | As an example of how this address replacement scheme may work, refer | ||
to figure 1. If station A (protocol address pA) wished to resolve | to figure 1. If station A (protocol address pA) wished to resolve | ||
the address of station B (protocol address pB), it would format an | the address of station B (protocol address pB), it would format an | ||
ARP request with the following values: | ARP request with the following values: | ||
| + | |||
ARP request from A | ARP request from A | ||
ar$op 1 (request) | ar$op 1 (request) | ||
| Line 981: | Line 781: | ||
ar$tha undefined | ar$tha undefined | ||
ar$tpa pB | ar$tpa pB | ||
| + | |||
Because station A will not have a source address associated with it, | Because station A will not have a source address associated with it, | ||
the source hardware address field is not valid. Therefore, when the | the source hardware address field is not valid. Therefore, when the | ||
| Line 986: | Line 787: | ||
Frame Relay header and place it in the source hardware address field. | Frame Relay header and place it in the source hardware address field. | ||
This way, the ARP request from A will become: | This way, the ARP request from A will become: | ||
| + | |||
ARP request from A as modified by B | ARP request from A as modified by B | ||
ar$op 1 (request) | ar$op 1 (request) | ||
| Line 992: | Line 794: | ||
ar$tha undefined | ar$tha undefined | ||
ar$tpa pB | ar$tpa pB | ||
| + | |||
Station B's ARP will then be able to store station A's protocol | Station B's ARP will then be able to store station A's protocol | ||
address and Q.922 address association correctly. Next, station B | address and Q.922 address association correctly. Next, station B | ||
| Line 998: | Line 801: | ||
then fills in the source addresses with its addresses. In this case, | then fills in the source addresses with its addresses. In this case, | ||
the ARP response would be: | the ARP response would be: | ||
| + | |||
ARP response from B | ARP response from B | ||
ar$op 2 (response) | ar$op 2 (response) | ||
| Line 1,004: | Line 808: | ||
ar$tha 0x1061 (DLCI 70) | ar$tha 0x1061 (DLCI 70) | ||
ar$tpa pA | ar$tpa pA | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Again, the source hardware address is unknown and when the request is | Again, the source hardware address is unknown and when the request is | ||
| Line 1,016: | Line 813: | ||
header and place it in the source hardware address field. Therefore, | header and place it in the source hardware address field. Therefore, | ||
the response will become: | the response will become: | ||
| + | |||
ARP response from B as modified by A | ARP response from B as modified by A | ||
ar$op 2 (response) | ar$op 2 (response) | ||
| Line 1,022: | Line 820: | ||
ar$tha 0x1061 (DLCI 70) | ar$tha 0x1061 (DLCI 70) | ||
ar$tpa pA | ar$tpa pA | ||
| + | |||
Station A will now correctly recognize station B having protocol | Station A will now correctly recognize station B having protocol | ||
address pB associated with Q.922 address 0x0C21 (DLCI 50). | address pB associated with Q.922 address 0x0C21 (DLCI 50). | ||
| + | |||
Reverse ARP (RARP) [8] will work in exactly the same way. Still | Reverse ARP (RARP) [8] will work in exactly the same way. Still | ||
using figure 1, if we assume station C is an address server, the | using figure 1, if we assume station C is an address server, the | ||
following RARP exchanges will occur: | following RARP exchanges will occur: | ||
| + | |||
RARP request from A RARP request as modified by C | RARP request from A RARP request as modified by C | ||
ar$op 3 (RARP request) ar$op 3 (RARP request) | ar$op 3 (RARP request) ar$op 3 (RARP request) | ||
| Line 1,033: | Line 834: | ||
ar$tha 0x0CC1 (DLCI 60) ar$tha 0x0CC1 (DLCI 60) | ar$tha 0x0CC1 (DLCI 60) ar$tha 0x0CC1 (DLCI 60) | ||
ar$tpa pC ar$tpa pC | ar$tpa pC ar$tpa pC | ||
| + | |||
Station C will then look up the protocol address corresponding to | Station C will then look up the protocol address corresponding to | ||
Q.922 address 0x1401 (DLCI 80) and send the RARP response. | Q.922 address 0x1401 (DLCI 80) and send the RARP response. | ||
| + | |||
RARP response from C RARP response as modified by A | RARP response from C RARP response as modified by A | ||
ar$op 4 (RARP response) ar$op 4 (RARP response) | ar$op 4 (RARP response) ar$op 4 (RARP response) | ||
| Line 1,041: | Line 844: | ||
ar$tha 0x1401 (DLCI 80) ar$tha 0x1401 (DLCI 80) | ar$tha 0x1401 (DLCI 80) ar$tha 0x1401 (DLCI 80) | ||
ar$tpa pA ar$tpa pA | ar$tpa pA ar$tpa pA | ||
| + | |||
This means that the Frame Relay interface must only intervene in the | This means that the Frame Relay interface must only intervene in the | ||
processing of incoming packets. | processing of incoming packets. | ||
| + | |||
In the absence of suitable multicast, ARP may still be implemented. | In the absence of suitable multicast, ARP may still be implemented. | ||
To do this, the end station simply sends a copy of the ARP request | To do this, the end station simply sends a copy of the ARP request | ||
through each relevant DLC, thereby simulating a broadcast. | through each relevant DLC, thereby simulating a broadcast. | ||
| + | |||
The use of multicast addresses in a Frame Relay environment is | The use of multicast addresses in a Frame Relay environment is | ||
presently under study by Frame Relay providers. At such time that | presently under study by Frame Relay providers. At such time that | ||
| Line 1,051: | Line 857: | ||
addressing may become useful in sending ARP requests and other | addressing may become useful in sending ARP requests and other | ||
"broadcast" messages. | "broadcast" messages. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Because of the inefficiencies of broadcasting in a Frame Relay | Because of the inefficiencies of broadcasting in a Frame Relay | ||
| Line 1,066: | Line 866: | ||
use. That is the source hardware address is inserted at the | use. That is the source hardware address is inserted at the | ||
receiving station. | receiving station. | ||
| + | |||
In our example, station A may use Inverse ARP to discover the | In our example, station A may use Inverse ARP to discover the | ||
protocol address of the station associated with its DLCI 50. The | protocol address of the station associated with its DLCI 50. The | ||
Inverse ARP request would be as follows: | Inverse ARP request would be as follows: | ||
| + | |||
InARP Request from A (DLCI 50) | InARP Request from A (DLCI 50) | ||
ar$op 8 (InARP request) | ar$op 8 (InARP request) | ||
| Line 1,075: | Line 877: | ||
ar$tha 0x0C21 (DLCI 50) | ar$tha 0x0C21 (DLCI 50) | ||
ar$tpa unknown | ar$tpa unknown | ||
| + | |||
When Station B receives this packet, it will modify the source | When Station B receives this packet, it will modify the source | ||
hardware address with the Q.922 address from the Frame Relay header. | hardware address with the Q.922 address from the Frame Relay header. | ||
This way, the InARP request from A will become: | This way, the InARP request from A will become: | ||
| + | |||
ar$op 8 (InARP request) | ar$op 8 (InARP request) | ||
ar$sha 0x1061 | ar$sha 0x1061 | ||
| Line 1,083: | Line 887: | ||
ar$tha 0x0C21 | ar$tha 0x0C21 | ||
ar$tpa unknown. | ar$tpa unknown. | ||
| + | |||
Station B will format an Inverse ARP response and send it to station | Station B will format an Inverse ARP response and send it to station | ||
A as it would for any ARP message. | A as it would for any ARP message. | ||
| + | |||
11. IP over Frame Relay | 11. IP over Frame Relay | ||
| + | |||
Internet Protocol [9] (IP) datagrams sent over a Frame Relay network | Internet Protocol [9] (IP) datagrams sent over a Frame Relay network | ||
conform to the encapsulation described previously. Within this | conform to the encapsulation described previously. Within this | ||
context, IP could be encapsulated in two different ways. | context, IP could be encapsulated in two different ways. | ||
| + | 1. NLPID value indicating IP | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
+-----------------------+-----------------------+ | +-----------------------+-----------------------+ | ||
| Q.922 Address | | | Q.922 Address | | ||
| Line 1,116: | Line 908: | ||
| . | | | . | | ||
+-----------------------+-----------------------+ | +-----------------------+-----------------------+ | ||
| + | |||
2. NLPID value indicating SNAP | 2. NLPID value indicating SNAP | ||
| + | |||
+-----------------------+-----------------------+ | +-----------------------+-----------------------+ | ||
| Q.922 Address | | | Q.922 Address | | ||
| Line 1,133: | Line 927: | ||
| . | | | . | | ||
+-----------------------+-----------------------+ | +-----------------------+-----------------------+ | ||
| + | |||
Although both of these encapsulations are supported under the given | Although both of these encapsulations are supported under the given | ||
definitions, it is advantageous to select only one method as the | definitions, it is advantageous to select only one method as the | ||
| Line 1,140: | Line 935: | ||
transmission (48 fewer bits), and is consistent with the | transmission (48 fewer bits), and is consistent with the | ||
encapsulation of IP in X.25. | encapsulation of IP in X.25. | ||
| + | |||
12. Other Protocols over Frame Relay | 12. Other Protocols over Frame Relay | ||
| + | |||
As with IP encapsulation, there are alternate ways to transmit | As with IP encapsulation, there are alternate ways to transmit | ||
various protocols within the scope of this definition. To eliminate | various protocols within the scope of this definition. To eliminate | ||
the conflicts, the SNAP encapsulation is only used if no NLPID value | the conflicts, the SNAP encapsulation is only used if no NLPID value | ||
is defined for the given protocol. | is defined for the given protocol. | ||
| + | |||
As an example of how this works, ISO CLNP has a NLPID defined (0x81). | As an example of how this works, ISO CLNP has a NLPID defined (0x81). | ||
Therefore, the NLPID field will indicate ISO CLNP and the data packet | Therefore, the NLPID field will indicate ISO CLNP and the data packet | ||
| + | will follow immediately. The frame would be as follows: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
+----------------------+----------------------+ | +----------------------+----------------------+ | ||
| Q.922 Address | | | Q.922 Address | | ||
| Line 1,164: | Line 957: | ||
| . | | | . | | ||
+---------------------------------------------+ | +---------------------------------------------+ | ||
| + | |||
13. Bridging in a Frame Relay network | 13. Bridging in a Frame Relay network | ||
| + | |||
A Frame Relay interface acting as a bridge must be able to flood, | A Frame Relay interface acting as a bridge must be able to flood, | ||
forward, and filter packets. | forward, and filter packets. | ||
| + | |||
Flooding is performed by sending the packet to all possible | Flooding is performed by sending the packet to all possible | ||
destinations. In the Frame Relay environment this means sending the | destinations. In the Frame Relay environment this means sending the | ||
packet through each relevant DLC. | packet through each relevant DLC. | ||
| + | |||
To forward a packet, a bridge must be able to associate a destination | To forward a packet, a bridge must be able to associate a destination | ||
MAC address with a DLC. It is unreasonable and perhaps impossible to | MAC address with a DLC. It is unreasonable and perhaps impossible to | ||
| Line 1,177: | Line 974: | ||
interface to dynamically learn about foreign destinations beyond the | interface to dynamically learn about foreign destinations beyond the | ||
set of Frame Relay stations. | set of Frame Relay stations. | ||
| + | |||
To accomplish dynamic learning, a bridged packet shall conform to the | To accomplish dynamic learning, a bridged packet shall conform to the | ||
encapsulation described within section 7. In this way, the receiving | encapsulation described within section 7. In this way, the receiving | ||
| Line 1,182: | Line 980: | ||
learn the association between foreign destination and Frame Relay | learn the association between foreign destination and Frame Relay | ||
station. | station. | ||
| + | |||
14. For Future Study | 14. For Future Study | ||
| + | |||
It may be desirable for the two ends of a connection to have the | It may be desirable for the two ends of a connection to have the | ||
capability to negotiate end-to-end configuration and service | capability to negotiate end-to-end configuration and service | ||
parameters. The actual protocol and parameters to be negotiated will | parameters. The actual protocol and parameters to be negotiated will | ||
be a topic of future RFCs. | be a topic of future RFCs. | ||
| + | |||
15. Backward Compatibility | 15. Backward Compatibility | ||
| + | |||
This section is included in this RFC for completeness only. It is | This section is included in this RFC for completeness only. It is | ||
not intended to suggest additional requirements. | not intended to suggest additional requirements. | ||
| + | |||
Some existing Frame Relay stations use the NLPID value of 0xCE to | Some existing Frame Relay stations use the NLPID value of 0xCE to | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
indicate an escape to Ethernet Packet Types as defined in the latest | indicate an escape to Ethernet Packet Types as defined in the latest | ||
version of the Assigned Numbers (RFC-1060) [7]. In this case, the | version of the Assigned Numbers (RFC-1060) [7]. In this case, the | ||
frame will have the following format: | frame will have the following format: | ||
| + | |||
+-----------------------------+ | +-----------------------------+ | ||
| Q.922 Address | | | Q.922 Address | | ||
| Line 1,226: | Line 1,024: | ||
| (two octets) | | | (two octets) | | ||
+-----------------------------+ | +-----------------------------+ | ||
| + | |||
The Ethertype field is a 16-bit value used to identify a protocol | The Ethertype field is a 16-bit value used to identify a protocol | ||
type for the following PDU. | type for the following PDU. | ||
| + | |||
In order to be fully interoperable with stations that use this | In order to be fully interoperable with stations that use this | ||
encoding, Frame Relay stations may recognize the NLPID value of 0xCE | encoding, Frame Relay stations may recognize the NLPID value of 0xCE | ||
| Line 1,233: | Line 1,033: | ||
necessary to generate this encapsulation format only to properly | necessary to generate this encapsulation format only to properly | ||
interpret it's meaning. | interpret it's meaning. | ||
| + | |||
For example, IP encapsulated with this NLPID value will have the | For example, IP encapsulated with this NLPID value will have the | ||
following format: | following format: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
+-----------------------+-----------------------+ | +-----------------------+-----------------------+ | ||
| Line 1,260: | Line 1,048: | ||
| . | | | . | | ||
+-----------------------+-----------------------+ | +-----------------------+-----------------------+ | ||
| + | |||
16. Appendix | 16. Appendix | ||
| + | |||
List of Known NLPIDs | List of Known NLPIDs | ||
| + | |||
0x00 Null Network Layer or Inactive Set | 0x00 Null Network Layer or Inactive Set | ||
(not used with Frame Relay) | (not used with Frame Relay) | ||
| Line 1,270: | Line 1,061: | ||
0xCC Internet IP | 0xCC Internet IP | ||
0xCE EtherType - unofficial temporary use | 0xCE EtherType - unofficial temporary use | ||
| + | |||
List of PIDs of OUI 00-80-C2 | List of PIDs of OUI 00-80-C2 | ||
| + | |||
with preserved FCS w/o preserved FCS Media | with preserved FCS w/o preserved FCS Media | ||
------------------ ----------------- -------------- | ------------------ ----------------- -------------- | ||
| Line 1,280: | Line 1,073: | ||
0x00-0D Fragments | 0x00-0D Fragments | ||
0x00-0E BPDUs | 0x00-0E BPDUs | ||
| + | |||
17. References | 17. References | ||
| + | |||
[1] International Telegraph and Telephone Consultative Committee, | [1] International Telegraph and Telephone Consultative Committee, | ||
"ISDN Data Link Layer Specification for Frame Mode Bearer | "ISDN Data Link Layer Specification for Frame Mode Bearer | ||
Services", CCITT Recommendation Q.922, 19 April 1991 . | Services", CCITT Recommendation Q.922, 19 April 1991 . | ||
| + | |||
[2] American National Standard For Telecommunications - Integrated | [2] American National Standard For Telecommunications - Integrated | ||
Services Digital Network - Core Aspects of Frame Protocol for | Services Digital Network - Core Aspects of Frame Protocol for | ||
Use with Frame Relay Bearer Service, ANSI T1.618-1991, 18 June | Use with Frame Relay Bearer Service, ANSI T1.618-1991, 18 June | ||
1991. | 1991. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[3] Information technology - Telecommunications and Information | [3] Information technology - Telecommunications and Information | ||
Exchange between systems - Protocol Identification in the | Exchange between systems - Protocol Identification in the | ||
Network Layer, ISO/IEC TR 9577: 1990 (E) 1990-10-15. | Network Layer, ISO/IEC TR 9577: 1990 (E) 1990-10-15. | ||
| + | |||
[4] Baker, Fred, "Point to Point Protocol Extensions for Bridging", | [4] Baker, Fred, "Point to Point Protocol Extensions for Bridging", | ||
Point to Point Working Group, RFC-1220, April 1991. | Point to Point Working Group, RFC-1220, April 1991. | ||
| + | |||
[5] International Standard, Information Processing Systems - Local | [5] International Standard, Information Processing Systems - Local | ||
Area Networks - Logical Link Control, ISO 8802-2: 1989 (E), IEEE | Area Networks - Logical Link Control, ISO 8802-2: 1989 (E), IEEE | ||
Std 802.2-1989, 1989-12-31. | Std 802.2-1989, 1989-12-31. | ||
| + | |||
[6] Plummer, David C., An Ethernet Address Resolution Protocol", | [6] Plummer, David C., An Ethernet Address Resolution Protocol", | ||
RFC-826, November 1982. | RFC-826, November 1982. | ||
| + | |||
[7] Reynolds, J. and Postel, J., "Assigned Numbers", RFC-1060, ISI, | [7] Reynolds, J. and Postel, J., "Assigned Numbers", RFC-1060, ISI, | ||
March 1990. | March 1990. | ||
| + | |||
[8] Finlayson, Mann, Mogul, Theimer, "A Reverse Address Resolution | [8] Finlayson, Mann, Mogul, Theimer, "A Reverse Address Resolution | ||
Protocol", RFC-903, Stanford University, June 1984. | Protocol", RFC-903, Stanford University, June 1984. | ||
| + | |||
[9] Postel, J. and Reynolds, J., "A Standard for the Transmission of | [9] Postel, J. and Reynolds, J., "A Standard for the Transmission of | ||
IP Datagrams over IEEE 802 Networks", RFC-1042, ISI, February | IP Datagrams over IEEE 802 Networks", RFC-1042, ISI, February | ||
1988. | 1988. | ||
| + | |||
[10] IEEE, "IEEE Standard for Local and Metropolitan Area Networks: | [10] IEEE, "IEEE Standard for Local and Metropolitan Area Networks: | ||
Overview and architecture", IEEE Standards 802-1990. | Overview and architecture", IEEE Standards 802-1990. | ||
| + | |||
[11] Bradley, T., and C. Brown, "Inverse Address Resolution | [11] Bradley, T., and C. Brown, "Inverse Address Resolution | ||
Protocol", RFC-1293, Wellfleet Communications, Inc., January | Protocol", RFC-1293, Wellfleet Communications, Inc., January | ||
1992. | 1992. | ||
| + | |||
18. Security Considerations | 18. Security Considerations | ||
| + | |||
Security issues are not addressed in this memo. | Security issues are not addressed in this memo. | ||
| + | |||
19. Authors' Addresses | 19. Authors' Addresses | ||
| + | |||
Terry Bradley | Terry Bradley | ||
Wellfleet Communications, Inc. | Wellfleet Communications, Inc. | ||
15 Crosby Drive | 15 Crosby Drive | ||
Bedford, MA 01730 | Bedford, MA 01730 | ||
| + | |||
Phone: (617) 275-2400 | Phone: (617) 275-2400 | ||
| + | |||
Email: [email protected] | Email: [email protected] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Caralyn Brown | Caralyn Brown | ||
| Line 1,341: | Line 1,135: | ||
15 Crosby Drive | 15 Crosby Drive | ||
Bedford, MA 01730 | Bedford, MA 01730 | ||
| + | |||
Phone: (617) 275-2400 | Phone: (617) 275-2400 | ||
| + | |||
Email: [email protected] | Email: [email protected] | ||
| Line 1,348: | Line 1,144: | ||
150 CambridgePark Drive | 150 CambridgePark Drive | ||
Cambridge, MA 02140 | Cambridge, MA 02140 | ||
| + | |||
Phone: (617) 873-3419 | Phone: (617) 873-3419 | ||
| + | |||
Email: [email protected] | Email: [email protected] | ||
Latest revision as of 07:15, 7 May 2021
Network Working Group T. Bradley Request for Comments: 1294 C. Brown
Wellfleet Communications, Inc.
A. Malis
BBN Communications
January 1992
Multiprotocol Interconnect over Frame Relay
Contents
Status of this Memo
This RFC specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Abstract
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. Systems with the ability to transfer both this encapsulation method, and others must have a priori knowledge of which virtual circuits will carry which encapsulation method and this encapsulation must only be used over virtual circuits that have been explicitly configured for its use.
Acknowledgements
Comments and contributions from many sources, especially those from Ray Samora of Proteon, Ken Rehbehn of Netrix Corporation, Fred Baker and Charles Carvalho of Advanced Computer Communications and Mostafa Sherif of AT&T have been incorporated into this document. Special thanks to Dory Leifer of University of Michigan for his contributions to the resolution of fragmentation issues. This document could not have been completed without the expertise of the IP over Large Public Data Networks working group of the IETF.
Conventions
The following language conventions are used in the items of specification in this document:
o Must, Shall or Mandatory -- the item is an absolute requirement of the specification.
o Should or Recommended -- the item should generally be followed for all but exceptional circumstances.
o May or Optional -- the item is truly optional and may be followed or ignored according to the needs of the implementor.
Introduction
The following discussion applies to those devices which serve as end stations (DTEs) on a public or private Frame Relay network (for example, provided by a common carrier or PTT). It will not discuss the behavior of those stations that are considered a part of the Frame Relay network (DCEs) other than to explain situations in which the DTE must react.
The Frame Relay network provides a number of virtual circuits that form the basis for connections between stations attached to the same Frame Relay network. The resulting set of interconnected devices forms a private Frame Relay group which may be either fully interconnected with a complete "mesh" of virtual circuits, or only partially interconnected. In either case, each virtual circuit is uniquely identified at each Frame Relay interface by a Data Link Connection Identifier (DLCI). In most circumstances DLCIs have strictly local significance at each Frame Relay interface.
The specifications in this document are intended to apply to both switched and permanent virtual circuits.
Frame Format
All protocols must encapsulate their packets within a Q.922 Annex A frame [1,2]. Additionally, frames shall contain information necessary to identify the protocol carried within the Protocol Data Unit (PDU), thus allowing the receiver to properly process the incoming packet. The format shall be as follows:
+-----------------------------+
| flag (7E hexadecimal) |
+-----------------------------+
| Q.922 Address* |
+-- --+
| |
+-----------------------------+
| Control (UI = 0x03) |
+-----------------------------+
| Optional Pad(s) (0x00) |
+-----------------------------+
| NLPID |
+-----------------------------+
| . |
| . |
| . |
| Data |
| . |
| . |
+-----------------------------+
| Frame Check Sequence |
+-- . --+
| (two octets) |
+-----------------------------+
| flag (7E hexadecimal) |
+-----------------------------+
* Q.922 addresses, as presently defined, are two octets and
contain a 10-bit DLCI. In some networks Q.922 addresses may
optionally be increased to three or four octets.
The control field is the Q.922 control field. The UI (0x03) value is used unless it is negotiated otherwise. The use of XID (0xAF or 0xBF) is permitted and is discussed later.
The pad field is an optional field used to align the remainder of the frame to a convenient boundary for the sender. There may be zero or more pad octets within the pad field and all must have a value of zero.
The Network Level Protocol ID (NLPID) field is administered by ISO and CCITT. It contains values for many different protocols including IP, CLNP and IEEE Subnetwork Access Protocol (SNAP)[10]. This field tells the receiver what encapsulation or what protocol follows. Values for this field are defined in ISO/IEC TR 9577 [3]. A NLPID value of 0x00 is defined within ISO/IEC TR 9577 as the Null Network Layer or Inactive Set. Since it cannot be distinguished from a pad field, and because it has no significance within the context of this
encapsulation scheme, a NLPID value of 0x00 is invalid under the Frame Relay encapsulation. The known NLPID values are listed in the Appendix.
For full interoperability with older Frame Relay encapsulation formats, a station may implement section 15, Backward Compatibility.
There is no commonly implemented maximum frame size for Frame Relay. A network must, however, support at least a 262 octet maximum. Generally, the maximum will be greater than or equal to 1600 octets, but each Frame Relay provider will specify an appropriate value for its network. A Frame Relay DTE, therefore, must allow the maximum acceptable frame size to be configurable.
The minimum frame size allowed for Frame Relay is five octets between the opening and closing flags.
Interconnect Issues
There are two basic types of data packets that travel within the Frame Relay network, routed packets and bridged packets. These packets have distinct formats and therefore, must contain an indication that the destination may use to correctly interpret the contents of the frame. This indication is embedded within the NLPID and SNAP header information.
For those protocols that do not have a NLPID already assigned, it is necessary to provide a mechanism to allow easy protocol identification. There is a NLPID value defined indicating the presence of a SNAP header.
A SNAP header is of the form
+-------------------------------+
| Organizationally Unique |
+-- +---------------+
| Identifier | Protocol |
+---------------+---------------+
| Identifier |
+---------------+
All stations must be able to accept and properly interpret both the NLPID encapsulation and the SNAP header encapsulation for a routed packet.
The three-octet Organizationally Unique Identifier (OUI) identifies an organization which administers the meaning of the Protocol Identifier (PID) which follows. Together they identify a distinct
protocol. Note that OUI 0x00-00-00 specifies that the following PID is an EtherType.
Routed Frames
Some protocols will have an assigned NLPID, but because the NLPID numbering space is so limited many protocols do not have a specific NLPID assigned to them. When packets of such protocols are routed over Frame Relay networks they are sent using the NLPID 0x80 (which indicates a SNAP follows), OUI 0x00-00-00 (which indicates an EtherType follows), and the EtherType of the protocol in use.
Format of Routed Frames
+-------------------------------+
| Q.922 Address |
+-------------------------------+
|Control 0x03 | pad(s) 0x00 |
+-------------------------------+
| NLPID 0x80 | OUI 0x00 |
+---------------+ --+
| OUI 0x00-00 |
+-------------------------------+
| EtherType |
+-------------------------------+
| Protocol Data |
+-------------------------------+
| FCS |
+-------------------------------+
In the few cases when a protocol has an assigned NLPID (see appendix), 48 bits can be saved using the format below:
Format of Routed NLPID Protocol
+-------------------------------+
| Q.922 Address |
+-------------------------------+
|Control 0x03 | NLPID |
+-------------------------------+
| Protocol Data |
+-------------------------------+
| FCS |
+-------------------------------+
In the particular case of an Internet IP datagram, the NLPID is 0xCC.
Format of Routed IP Datagram
+-------------------------------+
| Q.922 Address |
+-------------------------------+
|Control 0x03 | NLPID 0xCC |
+-------------------------------+
| IP Datagram |
+-------------------------------+
| FCS |
+-------------------------------+
Bridged Frames
The second type of Frame Relay traffic is bridged packets. These packets are encapsulated using the NLPID value of 0x80 indicating SNAP and the following SNAP header identifies the format of the bridged packet. The OUI value used for this encapsulation is the 802.1 organization code 0x00-80-C2. The following two octets (PID) specify the form of the MAC header, which immediately follows the SNAP header. Additionally, the PID indicates whether the original FCS is preserved within the bridged frame.
The 802.1 organization has reserved the following values to be used with Frame Relay:
PID Values for OUI 0x00-80-C2
with preserved FCS w/o preserved FCS Media
------------------ ----------------- ----------------
0x00-01 0x00-07 802.3/Ethernet
0x00-02 0x00-08 802.4
0x00-03 0x00-09 802.5
0x00-04 0x00-0A FDDI
0x00-05 0x00-0B 802.6
In addition, the PID value 0x00-0E, when used with OUI 0x00-80-C2, identifies Bridged Protocol Data Units (BPDUs).
A packet bridged over Frame Relay will, therefore, have one of the following formats:
Format of Bridged Ethernet/802.3 Frame
+-------------------------------+
| Q.922 Address |
+-------------------------------+
|Control 0x03 | pad(s) 0x00 |
+-------------------------------+
| NLPID 0x80 | OUI 0x00 |
+---------------+ --+
| OUI 0x80-C2 |
+-------------------------------+
| PID 0x00-01 or 0x00-07 |
+-------------------------------+
| MAC destination address |
+-------------------------------+
| (remainder of MAC frame) |
+-------------------------------+
| LAN FCS (if PID is 0x00-01) |
+-------------------------------+
| FCS |
+-------------------------------+
Format of Bridged 802.4 Frame
+-------------------------------+
| Q.922 Address |
+-------------------------------+
|Control 0x03 | pad(s) 0x00 |
+-------------------------------+
| NLPID 0x80 | OUI 0x00 |
+---------------+ --+
| OUI 0x80-C2 |
+-------------------------------+
| PID 0x00-02 or 0x00-08 |
+-------------------------------+
| pad 0x00 | Frame Control |
+-------------------------------+
| MAC destination address |
+-------------------------------+
| (remainder of MAC frame) |
+-------------------------------+
| LAN FCS (if PID is 0x00-02) |
+-------------------------------+
| FCS |
+-------------------------------+
Format of Bridged 802.5 Frame
+-------------------------------+
| Q.922 Address |
+-------------------------------+
|Control 0x03 | pad(s) 0x00 |
+-------------------------------+
| NLPID 0x80 | OUI 0x00 |
+---------------+ --+
| OUI 0x80-C2 |
+-------------------------------+
| PID 0x00-03 or 0x00-09 |
+-------------------------------+
| Access Control| Frame Control |
+-------------------------------+
| MAC destination address |
| . |
| . |
+-------------------------------+
| (remainder of MAC frame) |
+-------------------------------+
| LAN FCS (if PID is 0x00-03) |
| |
+-------------------------------+
| FCS |
+-------------------------------+
Format of Bridged FDDI Frame
+-------------------------------+
| Q.922 Address |
+-------------------------------+
|Control 0x03 | pad(s) 0x00 |
+-------------------------------+
| NLPID 0x80 | OUI 0x00 |
+---------------+ --+
| OUI 0x80-C2 |
+-------------------------------+
| PID 0x00-04 or 0x00-0A |
+-------------------------------+
| Access Control| Frame Control |
+-------------------------------+
| MAC destination address |
| . |
| . |
+-------------------------------+
| (remainder of MAC frame) |
+-------------------------------+
| LAN FCS (if PID is 0x00-04) |
| |
+-------------------------------+
| FCS |
+-------------------------------+
Format of Bridged 802.6 Frame
+-------------------------------+
| Q.922 Address |
| Control 0x03 | pad(s) 0x00 |
+-------------------------------+
| NLPID 0x80 | OUI 0x00 |
+---------------+ --+
| OUI 0x80-C2 |
+-------------------------------+
| PID 0x00-05 or 0x00-0B |
+-------------------------------+
| Reserved | BEtag | Common
+---------------+---------------+ PDU
| BAsize | Header
+-------------------------------+
| MAC destination address |
+-------------------------------+
| (remainder of MAC frame) |
+-------------------------------+
| |
+- Common PDU Trailer -+
| |
+-------------------------------+
| FCS |
+-------------------------------+
The Common Protocol Data Unit (PDU) Header and Trailer are conveyed to allow pipelining at the egress bridge to an 802.6 subnetwork. Specifically, the Common PDU Header contains the BAsize field, which contains the length of the PDU. If this field is not available to the egress 802.6 bridge, then that bridge cannot begin to transmit the segmented PDU until it has received the entire PDU, calculated the length, and inserted the length into the BAsize field. If the field is available, the egress 802.6 bridge can extract the length from the BAsize field of the Common PDU Header, insert it into the corresponding field of the first segment, and immediately transmit the segment onto the 802.6 subnetwork. Thus, the bridge can begin transmitting the 802.6 PDU before it has received the complete PDU.
One should note that the Common PDU Header and Trailer of the encapsulated frame should not be simply copied to the outgoing 802.6 subnetwork because the encapsulated BEtag value may conflict with the previous BEtag value transmitted by that bridge.
Format of BPDU Frame +-------------------------------+ | Q.922 Address | +-------------------------------+ |Control 0x03 | pad(s) 0x00 | +-------------------------------+ | NLPID 0x80 | OUI 0x00 | +---------------+ --+ | OUI 0x80-C2 | +-------------------------------+ | PID 0x00-0E | +-------------------------------+ ---- | 802.1(d) Protocol Identifier | BPDU, as defined +-------------------------------+ by 802.1(d), | Version = 00 | BPDU Type | section 5.3 +-------------------------------+ | (remainder of BPDU) | +-------------------------------+ ---- | FCS | +-------------------------------+
Data Link Layer Parameter Negotiation
Frame Relay stations may choose to support the Exchange Identification (XID) specified in Appendix III of Q.922 [1]. This XID exchange allows the following parameters to be negotiated at the initialization of a Frame Relay circuit: maximum frame size N201, retransmission timer T200, and the maximum number of outstanding I frames K.
A station may indicate its unwillingness to support acknowledged mode multiple frame operation by specifying a value of zero for the maximum window size, K.
If this exchange is not used, these values must be statically configured by mutual agreement of Data Link Connection (DLC) endpoints, or must be defaulted to the values specified in Section 5.9 of Q.922:
N201: 260 octets
K: 3 for a 16 Kbps link,
7 for a 64 Kbps link,
32 for a 384 Kbps link,
40 for a 1.536 Mbps or above link
T200: 1.5 seconds [see Q.922 for further details]
If a station supporting XID receives an XID frame, it shall respond with an XID response. In processing an XID, if the remote maximum frame size is smaller than the local maximum, the local system shall reduce the maximum size it uses over this DLC to the remotely specified value. Note that this shall be done before generating a response XID.
The following diagram describes the use of XID to specify non-use of acknowledged mode multiple frame operation.
Non-use of Acknowledged Mode Multiple Frame Operation
+---------------+
| Address | (2,3 or 4 octets)
| |
+---------------+
| Control 0xAF |
+---------------+
| format 0x82 |
+---------------+
| Group ID 0x80 |
+---------------+
| Group Length | (2 octets)
| 0x00-0E |
+---------------+
| 0x05 | PI = Frame Size (transmit)
+---------------+
| 0x02 | PL = 2
+---------------+
| Maximum | (2 octets)
| Frame Size |
+---------------+
| 0x06 | PI = Frame Size (receive)
+---------------+
| 0x02 | PL = 2
+---------------+
| Maximum | (2 octets)
| Frame Size |
+---------------+
| 0x07 | PI = Window Size
+---------------+
| 0x01 | PL = 1
+---------------+
| 0x00 |
+---------------+
| 0x09 | PI = Retransmission Timer
+---------------+
| 0x01 | PL = 1
+---------------+
| 0x00 |
+---------------+
| FCS | (2 octets)
| |
+---------------+
Fragmentation Issues
Fragmentation allows the exchange of packets that are greater than the maximum frame size supported by the underlying network. In the case of Frame Relay, the network may support a maximum frame size as small as 262 octets. Because of this small maximum size, it is advantageous to support fragmentation and reassembly.
Unlike IP fragmentation procedures, the scope of Frame Relay fragmentation procedure is limited to the boundary (or DTEs) of the Frame Relay network.
The general format of fragmented packets is the same as any other encapsulated protocol. The most significant difference being that the fragmented packet will contain the encapsulation header. That is, a packet is first encapsulated (with the exception of the address and control fields) as defined above. Large packets are then broken up into frames appropriate for the given Frame Relay network and are encapsulated using the Frame Relay fragmentation format. In this way, a station receiving fragments may reassemble them and then put the reassembled packet through the same processing path as a packet that had not been fragmented.
Within Frame Relay fragments are encapsulated using the SNAP format with an OUI of 0x00-80-C2 and a PID of 0x00-0D. Individual fragments will, therefore, have the following format:
+---------------+---------------+
| Q.922 Address |
+---------------+---------------+
| Control 0x03 | pad 0x00 |
+---------------+---------------+
| NLPID 0x80 | OUI 0x00 |
+---------------+---------------+
| OUI 0x80-C2 |
+---------------+---------------+
| PID 0x00-0D |
+---------------+---------------+
| sequence number |
+---------------+---------------+
|F| RSVD |offset |
+---------------+---------------+
| fragment data |
| . |
| . |
| . |
+---------------+---------------+
| FCS |
+---------------+---------------+
The sequence field is a two octet identifier that is incremented every time a new complete message is fragmented. It allows detection of lost frames and is set to a random value at initialization.
The reserved field is 4 bits long and is not currently defined. It must be set to 0.
The final bit is a one bit field set to 1 on the last fragment and set to 0 for all other fragments.
The offset field is an 11 bit value representing the logical offset of this fragment in bytes divided by 32. The first fragment must have an offset of zero.
The following figure shows how a large IP datagram is fragmented over Frame Relay. In this example, the complete datagram is fragmented into two Frame Relay frames.
Frame Relay Fragmentation Example
+-----------+-----------+
| Q.922 Address |
+-----------+-----------+
| Ctrl 0x03 | pad 0x00 |
+-----------+-----------+
|NLPID 0x80 | OUI 0x00 |
+-----------+-----------+
| OUI 0x80-C2 |
+-----------+-----------+ +-----------+-----------+
| pad 0x00 |NLPID 0xCC | | PID 0x00-0D |
+-----------+-----------+ +-----------+-----------+
| | | sequence number n |
| | +-----------+-----------+
| | |0| RSVD |offset (0) |
| | +-----------+-----------+
| | | pad 0x00 |NLPID 0xCC |
| | +-----------+-----------+
| | | first m bytes of |
| large IP datagram | ... | IP datagram |
| | | |
| | +-----------+-----------+
| | | FCS |
| | +-----------+-----------+
| |
| | +-----------+-----------+
| | | Q.922 Address |
| | +-----------+-----------+
| | | Ctrl 0x03 | pad 0x00 |
+-----------+-----------+ +-----------+-----------+
|NLPID 0x80 | OUI 0x00 |
+-----------+-----------+
| OUI 0x80-C2 |
+-----------+-----------+
| PID 0x00-0D |
+-----------+-----------+
| sequence number n |
+-----------+-----------+
|1| RSVD |offset (m/32) |
+-----------+-----------+
| remainder of IP |
| datagram |
+-----------+-----------+
| FCS |
+-----------+-----------+
Fragments must be sent in order starting with a zero offset and ending with the final fragment. These fragments must not be
interrupted with other packets or information intended for the same DLC. An end station must be able to re-assemble up to 2K octets and is suggested to support up to 8K octet re-assembly. If at any time during this re-assembly process, a fragment is corrupted or a fragment is missing, the entire message is dropped. The upper layer protocol is responsible for any retransmission in this case.
This fragmentation algorithm is not intended to reliably handle all possible failure conditions. As with IP fragmentation, there is a small possibility of reassembly error and delivery of an erroneous packet. Inclusion of a higher layer checksum greatly reduces this risk.
10. Address Resolution
There are situations in which a Frame Relay station may wish to dynamically resolve a protocol address. Address resolution may be accomplished using the standard Address Resolution Protocol (ARP) [6] encapsulated within a SNAP encoded Frame Relay packet as follows:
+-----------------------+-----------------------+
| Q.922 Address |
+-----------------------+-----------------------+
| Control (UI) 0x03 | pad(s) 0x00 |
+-----------------------+-----------------------+
| NLPID = 0x80 | | SNAP Header
+-----------------------+ OUI = 0x00-00-00 + Indicating
| | ARP
+-----------------------+-----------------------+
| PID = 0x0806 |
+-----------------------+-----------------------+
| ARP packet |
| . |
| . |
| . |
+-----------------------+-----------------------+
Where the ARP packet has the following format and values:
Data:
ar$hrd 16 bits Hardware type
ar$pro 16 bits Protocol type
ar$hln 8 bits Octet length of hardware address (n)
ar$pln 8 bits Octet length of protocol address (m)
ar$op 16 bits Operation code (request or reply)
ar$sha noctets source hardware address
ar$spa moctets source protocol address
ar$tha noctets target hardware address
ar$tpa moctets target protocol address
ar$hrd - assigned to Frame Relay is 15 decimal
(0x000F) [7].
ar$pro - see assigned numbers for protocol ID number for
the protocol using ARP. (IP is 0x0800).
ar$hln - length in bytes of the address field (2, 3, or 4)
ar$pln - protocol address length is dependent on the
protocol (ar$pro) (for IP ar$pln is 4).
ar$op - 1 for request and 2 for reply.
ar$sha - Q.922 source hardware address, with C/R, FECN,
BECN, and DE set to zero.
ar$tha - Q.922 target hardware address, with C/R, FECN,
BECN, and DE set to zero.
Because DLCIs within most Frame Relay networks have only local significance, an end station will not have a specific DLCI assigned to itself. Therefore, such a station does not have an address to put into the ARP request or reply. Fortunately, the Frame Relay network does provide a method for obtaining the correct DLCIs. The solution proposed for the locally addressed Frame Relay network below will work equally well for a network where DLCIs have global significance.
The DLCI carried within the Frame Relay header is modified as it traverses the network. When the packet arrives at its destination, the DLCI has been set to the value that, from the standpoint of the receiving station, corresponds to the sending station. For example, in figure 1 below, if station A were to send a message to station B, it would place DLCI 50 in the Frame Relay header. When station B received this message, however, the DLCI would have been modified by the network and would appear to B as DLCI 70.
07:15, 7 May 2021 (UTC)07:15, 7 May 2021 (UTC)07:15, 7 May 2021 (UTC)
( )
+-----+ ( ) +-----+
| |-50------(--------------------)---------70-| |
| A | ( ) | B |
| |-60-----(---------+ ) | |
+-----+ ( | ) +-----+
( | )
( | ) <---Frame Relay
07:15, 7 May 2021 (UTC)07:15, 7 May 2021 (UTC)07:15, 7 May 2021 (UTC)~ network
80
|
+-----+
| |
| C |
| |
+-----+
Figure 1
Lines between stations represent data link connections (DLCs). The numbers indicate the local DLCI associated with each connection.
DLCI to Q.922 Address Table for Figure 1
DLCI (decimal) Q.922 address (hex)
50 0x0C21
60 0x0CC1
70 0x1061
80 0x1401
If you know about frame relay, you should understand the corrolation between DLCI and Q.922 address. For the uninitiated, the translation between DLCI and Q.922 address is based on a two byte address length using the Q.922 encoding format. The format is:
8 7 6 5 4 3 2 1
+------------------------+---+--+
| DLCI (high order) |c/r|ea|
+------------------------+---+--+
| DLCI (lower) |FECN|BECN|DE |EA|
+--------------+----+----+---+--+
For ARP and its variants, the FECN, BECN, C/R and DE bits are assumed to be 0.
When an ARP message reaches a destination, all hardware addresses
will be invalid. The address found in the frame header will, however, be correct. Though it does violate the purity of layering, Frame Relay may use the address in the header as the sender hardware address. It should also be noted that the target hardware address, in both ARP request and reply, will also be invalid. This should not cause problems since ARP does not rely on these fields and in fact, an implementation may zero fill or ignore the target hardware address field entirely.
As an example of how this address replacement scheme may work, refer to figure 1. If station A (protocol address pA) wished to resolve the address of station B (protocol address pB), it would format an ARP request with the following values:
ARP request from A
ar$op 1 (request)
ar$sha unknown
ar$spa pA
ar$tha undefined
ar$tpa pB
Because station A will not have a source address associated with it, the source hardware address field is not valid. Therefore, when the ARP packet is received, it must extract the correct address from the Frame Relay header and place it in the source hardware address field. This way, the ARP request from A will become:
ARP request from A as modified by B
ar$op 1 (request)
ar$sha 0x1061 (DLCI 70) from Frame Relay header
ar$spa pA
ar$tha undefined
ar$tpa pB
Station B's ARP will then be able to store station A's protocol address and Q.922 address association correctly. Next, station B will form a reply message. Many implementations simply place the source addresses from the ARP request into the target addresses and then fills in the source addresses with its addresses. In this case, the ARP response would be:
ARP response from B
ar$op 2 (response)
ar$sha unknown
ar$spa pB
ar$tha 0x1061 (DLCI 70)
ar$tpa pA
Again, the source hardware address is unknown and when the request is received, station A will extract the address from the Frame Relay header and place it in the source hardware address field. Therefore, the response will become:
ARP response from B as modified by A
ar$op 2 (response)
ar$sha 0x0C21 (DLCI 50)
ar$spa pB
ar$tha 0x1061 (DLCI 70)
ar$tpa pA
Station A will now correctly recognize station B having protocol address pB associated with Q.922 address 0x0C21 (DLCI 50).
Reverse ARP (RARP) [8] will work in exactly the same way. Still using figure 1, if we assume station C is an address server, the following RARP exchanges will occur:
RARP request from A RARP request as modified by C
ar$op 3 (RARP request) ar$op 3 (RARP request)
ar$sha unknown ar$sha 0x1401 (DLCI 80)
ar$spa undefined ar$spa undefined
ar$tha 0x0CC1 (DLCI 60) ar$tha 0x0CC1 (DLCI 60)
ar$tpa pC ar$tpa pC
Station C will then look up the protocol address corresponding to Q.922 address 0x1401 (DLCI 80) and send the RARP response.
RARP response from C RARP response as modified by A
ar$op 4 (RARP response) ar$op 4 (RARP response)
ar$sha unknown ar$sha 0x0CC1 (DLCI 60)
ar$spa pC ar$spa pC
ar$tha 0x1401 (DLCI 80) ar$tha 0x1401 (DLCI 80)
ar$tpa pA ar$tpa pA
This means that the Frame Relay interface must only intervene in the processing of incoming packets.
In the absence of suitable multicast, ARP may still be implemented. To do this, the end station simply sends a copy of the ARP request through each relevant DLC, thereby simulating a broadcast.
The use of multicast addresses in a Frame Relay environment is presently under study by Frame Relay providers. At such time that the issues surrounding multicasting are resolved, multicast addressing may become useful in sending ARP requests and other "broadcast" messages.
Because of the inefficiencies of broadcasting in a Frame Relay environment, a new address resolution variation was developed. It is called Inverse ARP [11] and describes a method for resolving a protocol address when the hardware address is already known. In Frame Relay's case, the known hardware address is the DLCI. Using Inverse ARP for Frame Relay follows the same pattern as ARP and RARP use. That is the source hardware address is inserted at the receiving station.
In our example, station A may use Inverse ARP to discover the protocol address of the station associated with its DLCI 50. The Inverse ARP request would be as follows:
InARP Request from A (DLCI 50)
ar$op 8 (InARP request)
ar$sha unknown
ar$spa pA
ar$tha 0x0C21 (DLCI 50)
ar$tpa unknown
When Station B receives this packet, it will modify the source hardware address with the Q.922 address from the Frame Relay header. This way, the InARP request from A will become:
ar$op 8 (InARP request)
ar$sha 0x1061
ar$spa pA
ar$tha 0x0C21
ar$tpa unknown.
Station B will format an Inverse ARP response and send it to station A as it would for any ARP message.
11. IP over Frame Relay
Internet Protocol [9] (IP) datagrams sent over a Frame Relay network conform to the encapsulation described previously. Within this context, IP could be encapsulated in two different ways.
1. NLPID value indicating IP
+-----------------------+-----------------------+
| Q.922 Address |
+-----------------------+-----------------------+
| Control (UI) 0x03 | NLPID = 0xCC |
+-----------------------+-----------------------+
| IP Packet . |
| . |
| . |
+-----------------------+-----------------------+
2. NLPID value indicating SNAP
+-----------------------+-----------------------+
| Q.922 Address |
+-----------------------+-----------------------+
| Control (UI) 0x03 | pad(s) 0x00 |
+-----------------------+-----------------------+
| NLPID = 0x80 | | SNAP Header
+-----------------------+ OUI = 0x00-00-00 + Indicating
| | IP
+-----------------------+-----------------------+
| PID = 0x0800 |
+-----------------------+-----------------------+
| IP packet |
| . |
| . |
| . |
+-----------------------+-----------------------+
Although both of these encapsulations are supported under the given definitions, it is advantageous to select only one method as the appropriate mechanism for encapsulating IP data. Therefore, IP data shall be encapsulated using the NLPID value of 0xCC indicating IP as shown in option 1 above. This (option 1) is more efficient in transmission (48 fewer bits), and is consistent with the encapsulation of IP in X.25.
12. Other Protocols over Frame Relay
As with IP encapsulation, there are alternate ways to transmit various protocols within the scope of this definition. To eliminate the conflicts, the SNAP encapsulation is only used if no NLPID value is defined for the given protocol.
As an example of how this works, ISO CLNP has a NLPID defined (0x81). Therefore, the NLPID field will indicate ISO CLNP and the data packet
will follow immediately. The frame would be as follows:
+----------------------+----------------------+
| Q.922 Address |
+----------------------+----------------------+
| Control (0x03) | NLPID - 0x81 (CLNP) |
+---------------------------------------------+
| CLNP packet |
| . |
| . |
+---------------------------------------------+
13. Bridging in a Frame Relay network
A Frame Relay interface acting as a bridge must be able to flood, forward, and filter packets.
Flooding is performed by sending the packet to all possible destinations. In the Frame Relay environment this means sending the packet through each relevant DLC.
To forward a packet, a bridge must be able to associate a destination MAC address with a DLC. It is unreasonable and perhaps impossible to require bridges to statically configure an association of every possible destination MAC address with a DLC. Therefore, Frame Relay bridges must provide enough information to allow a Frame Relay interface to dynamically learn about foreign destinations beyond the set of Frame Relay stations.
To accomplish dynamic learning, a bridged packet shall conform to the encapsulation described within section 7. In this way, the receiving Frame Relay interface will know to look into the bridged packet and learn the association between foreign destination and Frame Relay station.
14. For Future Study
It may be desirable for the two ends of a connection to have the capability to negotiate end-to-end configuration and service parameters. The actual protocol and parameters to be negotiated will be a topic of future RFCs.
15. Backward Compatibility
This section is included in this RFC for completeness only. It is not intended to suggest additional requirements.
Some existing Frame Relay stations use the NLPID value of 0xCE to
indicate an escape to Ethernet Packet Types as defined in the latest version of the Assigned Numbers (RFC-1060) [7]. In this case, the frame will have the following format:
+-----------------------------+
| Q.922 Address |
+-- --+
| |
+-----------------------------+
| Control (UI = 0x03) |
+-----------------------------+
| Optional Pad(s) (0x00) |
+-----------------------------+
| NLPID (0xCE) |
+-----------------------------+
| Ethertype |
+- -+
| |
+-----------------------------+
| . |
| . |
| Data |
| . |
| . |
+-----------------------------+
| Frame Check Sequence |
+-- . --+
| (two octets) |
+-----------------------------+
The Ethertype field is a 16-bit value used to identify a protocol type for the following PDU.
In order to be fully interoperable with stations that use this encoding, Frame Relay stations may recognize the NLPID value of 0xCE and interpret the following two byte Ethertype. It is never necessary to generate this encapsulation format only to properly interpret it's meaning.
For example, IP encapsulated with this NLPID value will have the following format:
+-----------------------+-----------------------+
|Q.922 Address |
+-----------------------+-----------------------+
|Control (UI) 0x03 | NLPID 0xCE |
+-----------------------+-----------------------+
|Ethertype [7] 0x0800 |
+-----------------------+-----------------------+
| IP Packet |
| . |
| . |
+-----------------------+-----------------------+
16. Appendix
List of Known NLPIDs
0x00 Null Network Layer or Inactive Set
(not used with Frame Relay)
0x80 SNAP
0x81 ISO CLNP
0x82 ISO ESIS
0x83 ISO ISIS
0xCC Internet IP
0xCE EtherType - unofficial temporary use
List of PIDs of OUI 00-80-C2
with preserved FCS w/o preserved FCS Media ------------------ ----------------- -------------- 0x00-01 0x00-07 802.3/Ethernet 0x00-02 0x00-08 802.4 0x00-03 0x00-09 802.5 0x00-04 0x00-0A FDDI 0x00-05 0x00-0B 802.6 0x00-0D Fragments 0x00-0E BPDUs
17. References
[1] International Telegraph and Telephone Consultative Committee,
"ISDN Data Link Layer Specification for Frame Mode Bearer
Services", CCITT Recommendation Q.922, 19 April 1991 .
[2] American National Standard For Telecommunications - Integrated
Services Digital Network - Core Aspects of Frame Protocol for
Use with Frame Relay Bearer Service, ANSI T1.618-1991, 18 June
1991.
[3] Information technology - Telecommunications and Information
Exchange between systems - Protocol Identification in the
Network Layer, ISO/IEC TR 9577: 1990 (E) 1990-10-15.
[4] Baker, Fred, "Point to Point Protocol Extensions for Bridging",
Point to Point Working Group, RFC-1220, April 1991.
[5] International Standard, Information Processing Systems - Local
Area Networks - Logical Link Control, ISO 8802-2: 1989 (E), IEEE
Std 802.2-1989, 1989-12-31.
[6] Plummer, David C., An Ethernet Address Resolution Protocol",
RFC-826, November 1982.
[7] Reynolds, J. and Postel, J., "Assigned Numbers", RFC-1060, ISI,
March 1990.
[8] Finlayson, Mann, Mogul, Theimer, "A Reverse Address Resolution
Protocol", RFC-903, Stanford University, June 1984.
[9] Postel, J. and Reynolds, J., "A Standard for the Transmission of
IP Datagrams over IEEE 802 Networks", RFC-1042, ISI, February
1988.
[10] IEEE, "IEEE Standard for Local and Metropolitan Area Networks:
Overview and architecture", IEEE Standards 802-1990.
[11] Bradley, T., and C. Brown, "Inverse Address Resolution
Protocol", RFC-1293, Wellfleet Communications, Inc., January
1992.
18. Security Considerations
Security issues are not addressed in this memo.
19. Authors' Addresses
Terry Bradley
Wellfleet Communications, Inc.
15 Crosby Drive
Bedford, MA 01730
Phone: (617) 275-2400
Email: [email protected]
Caralyn Brown
Wellfleet Communications, Inc.
15 Crosby Drive
Bedford, MA 01730
Phone: (617) 275-2400
Email: [email protected]
Andrew G. Malis
BBN Communications
150 CambridgePark Drive
Cambridge, MA 02140
Phone: (617) 873-3419
Email: [email protected]
