draft-ietf-manet-dlep-15.txt   draft-ietf-manet-dlep-16.txt 
Mobile Ad hoc Networks Working Group S. Ratliff Mobile Ad hoc Networks Working Group S. Ratliff
Internet-Draft VT iDirect Internet-Draft VT iDirect
Intended status: Standards Track B. Berry Intended status: Standards Track B. Berry
Expires: January 7, 2016 Expires: January 21, 2016
S. Jury S. Jury
Cisco Systems Cisco Systems
D. Satterwhite D. Satterwhite
Broadcom Broadcom
R. Taylor R. Taylor
Airbus Defence & Space Airbus Defence & Space
July 6, 2015 July 20, 2015
Dynamic Link Exchange Protocol (DLEP) Dynamic Link Exchange Protocol (DLEP)
draft-ietf-manet-dlep-15 draft-ietf-manet-dlep-16
Abstract Abstract
When routing devices rely on modems to effect communications over When routing devices rely on modems to effect communications over
wireless links, they need timely and accurate knowledge of the wireless links, they need timely and accurate knowledge of the
characteristics of the link (speed, state, etc.) in order to make characteristics of the link (speed, state, etc.) in order to make
routing decisions. In mobile or other environments where these routing decisions. In mobile or other environments where these
characteristics change frequently, manual configurations or the characteristics change frequently, manual configurations or the
inference of state through routing or transport protocols does not inference of state through routing or transport protocols does not
allow the router to make the best decisions. A bidirectional, event- allow the router to make the best decisions. A bidirectional, event-
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 7, 2016. This Internet-Draft will expire on January 21, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 9 skipping to change at page 4, line 9
12.7. DLEP Well-known Port . . . . . . . . . . . . . . . . . . 57 12.7. DLEP Well-known Port . . . . . . . . . . . . . . . . . . 57
12.8. DLEP Multicast Address . . . . . . . . . . . . . . . . . 57 12.8. DLEP Multicast Address . . . . . . . . . . . . . . . . . 57
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 57 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 57
14.1. Normative References . . . . . . . . . . . . . . . . . . 57 14.1. Normative References . . . . . . . . . . . . . . . . . . 57
14.2. Informative References . . . . . . . . . . . . . . . . . 57 14.2. Informative References . . . . . . . . . . . . . . . . . 57
Appendix A. Discovery Signal Flows . . . . . . . . . . . . . . . 58 Appendix A. Discovery Signal Flows . . . . . . . . . . . . . . . 58
Appendix B. Peer Level Message Flows . . . . . . . . . . . . . . 58 Appendix B. Peer Level Message Flows . . . . . . . . . . . . . . 58
B.1. Session Initialization . . . . . . . . . . . . . . . . . 58 B.1. Session Initialization . . . . . . . . . . . . . . . . . 58
B.2. Session Initialization - Refused . . . . . . . . . . . . 59 B.2. Session Initialization - Refused . . . . . . . . . . . . 59
B.3. Router Changes IP Addresses . . . . . . . . . . . . . . . 59 B.3. Router Changes IP Addresses . . . . . . . . . . . . . . . 60
B.4. Modem Changes Session-wide Metrics . . . . . . . . . . . 59 B.4. Modem Changes Session-wide Metrics . . . . . . . . . . . 60
B.5. Router Terminates Session . . . . . . . . . . . . . . . . 60 B.5. Router Terminates Session . . . . . . . . . . . . . . . . 60
B.6. Modem Terminates Session . . . . . . . . . . . . . . . . 60 B.6. Modem Terminates Session . . . . . . . . . . . . . . . . 61
B.7. Session Heartbeats . . . . . . . . . . . . . . . . . . . 61 B.7. Session Heartbeats . . . . . . . . . . . . . . . . . . . 61
B.8. Router Detects a Heartbeat timeout . . . . . . . . . . . 62 B.8. Router Detects a Heartbeat timeout . . . . . . . . . . . 62
B.9. Modem Detects a Heartbeat timeout . . . . . . . . . . . . 63 B.9. Modem Detects a Heartbeat timeout . . . . . . . . . . . . 63
Appendix C. Destination Specific Signal Flows . . . . . . . . . 63 Appendix C. Destination Specific Signal Flows . . . . . . . . . 63
C.1. Common Destination Signaling . . . . . . . . . . . . . . 63 C.1. Common Destination Signaling . . . . . . . . . . . . . . 63
C.2. Multicast Destination Signaling . . . . . . . . . . . . . 64 C.2. Multicast Destination Signaling . . . . . . . . . . . . . 64
C.3. Link Characteristics Request . . . . . . . . . . . . . . 64 C.3. Link Characteristics Request . . . . . . . . . . . . . . 64
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65
1. Introduction 1. Introduction
There exist today a collection of modem devices that control links of There exist today a collection of modem devices that control links of
variable datarate and quality. Examples of these types of links variable datarate and quality. Examples of these types of links
include line-of-sight (LOS) terrestrial radios, satellite terminals, include line-of-sight (LOS) terrestrial radios, satellite terminals,
and cable/DSL modems. Fluctuations in speed and quality of these and broadband modems. Fluctuations in speed and quality of these
links can occur due to configuration, or on a moment-to-moment basis, links can occur due to configuration, or on a moment-to-moment basis,
due to physical phenomena like multipath interference, obstructions, due to physical phenomena like multipath interference, obstructions,
rain fade, etc. It is also quite possible that link quality and rain fade, etc. It is also quite possible that link quality and
datarate vary with respect to individual destinations on a link, and datarate vary with respect to individual destinations on a link, and
with the type of traffic being sent. As an example, consider the with the type of traffic being sent. As an example, consider the
case of an 802.11 access point, serving 2 associated laptop case of an 802.11 access point, serving two associated laptop
computers. In this environment, the answer to the question "What is computers. In this environment, the answer to the question "What is
the datarate on the 802.11 link?" is "It depends on which associated the datarate on the 802.11 link?" is "It depends on which associated
laptop we're talking about, and on what kind of traffic is being laptop we're talking about, and on what kind of traffic is being
sent." While the first laptop, being physically close to the access sent." While the first laptop, being physically close to the access
point, may have a datarate of 54Mbps for unicast traffic, the other point, may have a datarate of 54Mbps for unicast traffic, the other
laptop, being relatively far away, or obstructed by some object, can laptop, being relatively far away, or obstructed by some object, can
simultaneously have a datarate of only 32Mbps for unicast. However, simultaneously have a datarate of only 32Mbps for unicast. However,
for multicast traffic sent from the access point, all traffic is sent for multicast traffic sent from the access point, all traffic is sent
at the base transmission rate (which is configurable, but depending at the base transmission rate (which is configurable, but depending
on the model of the access point, is usually 24Mbps or less). on the model of the access point, is usually 24Mbps or less).
skipping to change at page 34, line 21 skipping to change at page 34, line 21
The Status data item contains the following fields: The Status data item contains the following fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | Text... : | Code | Text... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 1
Length: 1 + Length of text, in octets Length: 1 + Length of text, in octets
Status Code: One of the codes defined in Table 3 below. Status Code: One of the codes defined in Table 3 below.
Text: UTF-8 encoded string, describing the cause, used for Text: UTF-8 encoded string, describing the cause, used for
implementation defined purposes. Since this field is used for implementation defined purposes. Since this field is used for
description, implementations SHOULD limit characters in this field description, implementations SHOULD limit characters in this field
to printable characters. Implementations receiving this data item to printable characters. Implementations receiving this data item
SHOULD check for printable characters in the field. SHOULD check for printable characters in the field.
skipping to change at page 36, line 12 skipping to change at page 36, line 12
connections. If provided, the receiver MUST use this information to connections. If provided, the receiver MUST use this information to
perform the TCP connect to the DLEP server. perform the TCP connect to the DLEP server.
The IPv4 Connection Point data item contains the following fields: The IPv4 Connection Point data item contains the following fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address | | Use TLS | IPv4 Address... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TCP Port Number (optional) | : ...cont. | TCP Port Number (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 2
Length: 4 (or 6 if TCP Port included) Length: 5 (or 7 if TCP Port included)
Use TLS: Value indicating whether the TCP connection should use TLS
(1), or not (0). Values other than 0 or 1 MUST be considered as
invalid.
IPv4 Address: The IPv4 address listening on the DLEP modem. IPv4 Address: The IPv4 address listening on the DLEP modem.
TCP Port Number: TCP Port number on the DLEP modem. TCP Port Number: TCP Port number on the DLEP modem.
If the Length field is 6, the port number specified MUST be used to If the Length field is 7, the port number specified MUST be used to
establish the TCP session. If the TCP Port Number is omitted, i.e. establish the TCP session. If the TCP Port Number is omitted, i.e.
the Length field is 4, the receiver MUST use the DLEP well-known port the Length field is 5, the receiver MUST use the DLEP well-known port
number (Section 12.7) to establish the TCP connection. number (Section 12.7) to establish the TCP connection.
9.3. IPv6 Connection Point 9.3. IPv6 Connection Point
The IPv6 Connection Point data item MAY appear in the Peer Offer The IPv6 Connection Point data item MAY appear in the Peer Offer
signal (Section 8.2). signal (Section 8.2).
The IPv6 Connection Point data item indicates the IPv6 address and, The IPv6 Connection Point data item indicates the IPv6 address and,
optionally, the TCP port number on the DLEP modem available for optionally, the TCP port number on the DLEP modem available for
connections. If provided, the receiver MUST use this information to connections. If provided, the receiver MUST use this information to
perform the TCP connect to the DLEP server. perform the TCP connect to the DLEP server.
The IPv6 Connection Point data item contains the following fields: The IPv6 Connection Point data item contains the following fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Address : | Use TLS | IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Address : : IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Address : : IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Address : : IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TCP Port Number (optional) | : ...cont. | TCP Port Number (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 3
Length: 16 (or 18 if TCP Port included) Length: 17 (or 19 if TCP Port included)
Use TLS: Value indicating whether the TCP connection should use TLS
(1), or not (0). Values other than 0 or 1 MUST be considered as
invalid.
IPv6 Address: The IPv6 address listening on the DLEP modem. IPv6 Address: The IPv6 address listening on the DLEP modem.
TCP Port Number: TCP Port number on the DLEP modem. TCP Port Number: TCP Port number on the DLEP modem.
If the Length field is 18, the port number specified MUST be used to If the Length field is 19, the port number specified MUST be used to
establish the TCP session. If the TCP Port Number is omitted, i.e. establish the TCP session. If the TCP Port Number is omitted, i.e.
the Length field is 16, the receiver MUST use the DLEP well-known the Length field is 17, the receiver MUST use the DLEP well-known
port number (Section 12.7) to establish the TCP connection. port number (Section 12.7) to establish the TCP connection.
9.4. Peer Type 9.4. Peer Type
The Peer Type data item MAY appear in the Peer Discovery The Peer Type data item MAY appear in the Peer Discovery
(Section 8.1) and Peer Offer (Section 8.2) signals, and the Session (Section 8.1) and Peer Offer (Section 8.2) signals, and the Session
Initialization (Section 8.3) and Session Initialization Response Initialization (Section 8.3) and Session Initialization Response
(Section 8.4) messages. (Section 8.4) messages.
The Peer Type data item is used by the router and modem to give The Peer Type data item is used by the router and modem to give
skipping to change at page 38, line 13 skipping to change at page 38, line 13
The Peer Type data item contains the following fields: The Peer Type data item contains the following fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type... : | Peer Type... :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 4
Length: Length of peer type string, in octets. Length: Length of peer type string, in octets.
Peer Type: UTF-8 encoded string. For example, a satellite modem Peer Type: UTF-8 encoded string. For example, a satellite modem
might set this variable to "Satellite terminal". Since this data might set this variable to "Satellite terminal". Since this data
item is intended to provide additional information for display item is intended to provide additional information for display
commands, sending implementations SHOULD limit the data to commands, sending implementations SHOULD limit the data to
printable characters, and receiving implmentations SHOULD check printable characters, and receiving implmentations SHOULD check
the data for printable characters. the data for printable characters.
skipping to change at page 38, line 50 skipping to change at page 38, line 50
The Heartbeat Interval data item contains the following fields: The Heartbeat Interval data item contains the following fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interval | | Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 5
Length: 2 Length: 2
Interval: 0 = Do not use heartbeats on this DLEP session. Non-zero Interval: 0 = Do not use heartbeats on this DLEP session. Non-zero
= Interval, in seconds, for heartbeat messages. = Interval, in seconds, for heartbeat messages.
9.6. Extensions Supported 9.6. Extensions Supported
The Extensions Supported data item MAY be used in both the Session The Extensions Supported data item MAY be used in both the Session
Initialization (Section 8.3) and Session Initialization Response Initialization (Section 8.3) and Session Initialization Response
(Section 8.4) messages. (Section 8.4) messages.
skipping to change at page 39, line 30 skipping to change at page 39, line 30
The Extensions Supported data item contains the following fields: The Extensions Supported data item contains the following fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extensions List... | Extensions List...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 6
Length: Length of the extensions list in octets. This is twice (2x) Length: Length of the extensions list in octets. This is twice (2x)
the number of extensions. the number of extensions.
Extension List: A list of extensions supported, identified by their Extension List: A list of extensions supported, identified by their
2-octet value as listed in the extensions registry. 2-octet value as listed in the extensions registry.
9.7. MAC Address 9.7. MAC Address
The MAC address data item MUST appear in all destination-oriented The MAC address data item MUST appear in all destination-oriented
skipping to change at page 40, line 17 skipping to change at page 40, line 17
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address : | MAC Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: MAC Address : : MAC Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: MAC Address : (if EUI-64 used) | : MAC Address : (if EUI-64 used) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 7
Length: 6 for EUI-48 format, or 8 for EUI-64 format Length: 6 for EUI-48 format, or 8 for EUI-64 format
MAC Address: MAC Address of the destination. MAC Address: MAC Address of the destination.
9.8. IPv4 Address 9.8. IPv4 Address
The IPv4 Address data item MAY appear in the Session Update The IPv4 Address data item MAY appear in the Session Update
(Section 8.5), Destination Up (Section 8.9) and Destination Update (Section 8.5), Destination Up (Section 8.9) and Destination Update
(Section 8.13) messages. (Section 8.13) messages.
skipping to change at page 40, line 50 skipping to change at page 40, line 50
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Add/Drop | IPv4 Address : | Add/Drop | IPv4 Address :
| Indicator | : | Indicator | :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv4 | : IPv4 |
: Address | : Address |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 8
Length: 5 Length: 5
Add/Drop: Value indicating whether this is a new or existing address Add/Drop: Value indicating whether this is a new or existing address
(1), or a withdrawal of an address (0). Values other than 0 or 1 (1), or a withdrawal of an address (0). Values other than 0 or 1
MUST be considered as invalid. MUST be considered as invalid.
IPv4 Address: The IPv4 address of the destination or peer. IPv4 Address: The IPv4 address of the destination or peer.
9.9. IPv6 Address 9.9. IPv6 Address
skipping to change at page 41, line 40 skipping to change at page 41, line 40
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Address : : IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Address : : IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Address : : IPv6 Address :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Address | : IPv6 Address |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 9
Length: 17 Length: 17
Add/Drop: Value indicating whether this is a new or existing address Add/Drop: Value indicating whether this is a new or existing address
(1), or a withdrawal of an address (0). Values other than 0 or 1 (1), or a withdrawal of an address (0). Values other than 0 or 1
MUST be considered as invalid. MUST be considered as invalid.
IPv6 Address: IPv6 Address of the destination or peer. IPv6 Address: IPv6 Address of the destination or peer.
9.10. IPv4 Attached Subnet 9.10. IPv4 Attached Subnet
skipping to change at page 42, line 29 skipping to change at page 42, line 29
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Attached Subnet | | IPv4 Attached Subnet |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix Len. | | Prefix Len. |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 10
Length: 5 Length: 5
IPv4 Subnet: The IPv4 subnet reachable at the destination. IPv4 Subnet: The IPv4 subnet reachable at the destination.
Prefix Length: Length of the prefix (1-32) for the IPv4 subnet. A Prefix Length: Length of the prefix (1-32) for the IPv4 subnet. A
prefix length outside the speficied range MUST be considered as prefix length outside the speficied range MUST be considered as
invalid. invalid.
9.11. IPv6 Attached Subnet 9.11. IPv6 Attached Subnet
skipping to change at page 43, line 21 skipping to change at page 43, line 21
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Attached Subnet : : IPv6 Attached Subnet :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Attached Subnet : : IPv6 Attached Subnet :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: IPv6 Attached Subnet | : IPv6 Attached Subnet |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix Len. | | Prefix Len. |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 11
Length: 17 Length: 17
IPv4 Subnet: The IPv6 subnet reachable at the destination. IPv4 Subnet: The IPv6 subnet reachable at the destination.
Prefix Length: Length of the prefix (1-128) for the IPv6 subnet. A Prefix Length: Length of the prefix (1-128) for the IPv6 subnet. A
prefix length outside the specified range MUST be considered as prefix length outside the specified range MUST be considered as
invalid. invalid.
9.12. Maximum Data Rate (Receive) 9.12. Maximum Data Rate (Receive)
skipping to change at page 44, line 4 skipping to change at page 44, line 4
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MDRR (bps) : | MDRR (bps) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: MDRR (bps) | : MDRR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 12
Length: 8 Length: 8
Maximum Data Rate (Receive): A 64-bit unsigned integer, representing Maximum Data Rate (Receive): A 64-bit unsigned integer, representing
the maximum theoretical data rate, in bits per second (bps), that the maximum theoretical data rate, in bits per second (bps), that
can be achieved while receiving on the link. can be achieved while receiving on the link.
9.13. Maximum Data Rate (Transmit) 9.13. Maximum Data Rate (Transmit)
The Maximum Data Rate (Transmit) (MDRT) data item MUST appear in the The Maximum Data Rate (Transmit) (MDRT) data item MUST appear in the
skipping to change at page 44, line 35 skipping to change at page 44, line 35
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MDRT (bps) : | MDRT (bps) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: MDRT (bps) | : MDRT (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 13
Length: 8 Length: 8
Maximum Data Rate (Transmit): A 64-bit unsigned integer, Maximum Data Rate (Transmit): A 64-bit unsigned integer,
representing the maximum theoretical data rate, in bits per second representing the maximum theoretical data rate, in bits per second
(bps), that can be achieved while transmitting on the link. (bps), that can be achieved while transmitting on the link.
9.14. Current Data Rate (Receive) 9.14. Current Data Rate (Receive)
The Current Data Rate (Receive) (CDRR) data item MUST appear in the The Current Data Rate (Receive) (CDRR) data item MUST appear in the
skipping to change at page 45, line 22 skipping to change at page 45, line 22
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDRR (bps) : | CDRR (bps) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: CDRR (bps) | : CDRR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 14
Length: 8 Length: 8
Current Data Rate (Receive): A 64-bit unsigned integer, representing Current Data Rate (Receive): A 64-bit unsigned integer, representing
the current data rate, in bits per second, that can currently be the current data rate, in bits per second, that can currently be
achieved while receiving traffic on the link. achieved while receiving traffic on the link.
If there is no distinction between current and maximum receive data If there is no distinction between current and maximum receive data
rates, current data rate receive MUST be set equal to the maximum rates, current data rate receive MUST be set equal to the maximum
data rate receive. data rate receive.
skipping to change at page 46, line 15 skipping to change at page 46, line 15
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDRT (bps) : | CDRT (bps) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: CDRT (bps) | : CDRT (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 15
Length: 8 Length: 8
Current Data Rate (Transmit): A 64-bit unsigned integer, Current Data Rate (Transmit): A 64-bit unsigned integer,
representing the current data rate, in bits per second, that can representing the current data rate, in bits per second, that can
currently be achieved while transmitting traffic on the link. currently be achieved while transmitting traffic on the link.
If there is no distinction between current and maximum transmit data If there is no distinction between current and maximum transmit data
rates, current data rate transmit MUST be set equal to the maximum rates, current data rate transmit MUST be set equal to the maximum
data rate transmit. data rate transmit.
skipping to change at page 47, line 4 skipping to change at page 47, line 4
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Latency : | Latency :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Latency | : Latency |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 16
Length: 8 Length: 8
Latency: A 64-bit unsigned integer, representing the transmission Latency: A 64-bit unsigned integer, representing the transmission
delay, in microseconds, that a packet encounters as it is delay, in microseconds, that a packet encounters as it is
transmitted over the link. transmitted over the link.
9.17. Resources (Receive) 9.17. Resources (Receive)
The Resources (Receive) (RESR) data item MAY appear in the Session The Resources (Receive) (RESR) data item MAY appear in the Session
skipping to change at page 47, line 34 skipping to change at page 47, line 34
The Resources (Receive) data item contains the following fields: The Resources (Receive) data item contains the following fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RESR | | RESR |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 17
Length: 1 Length: 1
Resources (Receive): An 8-bit integer percentage, 0-100, Resources (Receive): An 8-bit integer percentage, 0-100,
representing the amount of resources allocated to receiving data. representing the amount of resources allocated to receiving data.
Any value greater than 100 MUST be considered as invalid. Any value greater than 100 MUST be considered as invalid.
If a device cannot calculate RESR, this data item SHOULD NOT be If a device cannot calculate RESR, this data item SHOULD NOT be
issued. issued.
skipping to change at page 48, line 19 skipping to change at page 48, line 19
The Resources (Transmit) data item contains the following fields: The Resources (Transmit) data item contains the following fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| REST | | REST |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 18
Length: 1 Length: 1
Resources (Transmit): An 8-bit integer percentage, 0-100, Resources (Transmit): An 8-bit integer percentage, 0-100,
representing the amount of resources allocated to transmitting representing the amount of resources allocated to transmitting
data. Any value greater than 100 MUST be considered as invalid. data. Any value greater than 100 MUST be considered as invalid.
If a device cannot calculate REST, this data item SHOULD NOT be If a device cannot calculate REST, this data item SHOULD NOT be
issued. issued.
skipping to change at page 48, line 50 skipping to change at page 48, line 50
fields: fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RLQR | | RLQR |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 19
Length: 1 Length: 1
Relative Link Quality (Receive): A non-dimensional 8-bit integer, Relative Link Quality (Receive): A non-dimensional 8-bit integer,
0-100, representing relative link quality. A value of 100 0-100, representing relative link quality. A value of 100
represents a link of the highest quality. Any value greater than represents a link of the highest quality. Any value greater than
100 MUST be considered as invalid. 100 MUST be considered as invalid.
If a device cannot calculate the RLQR, this data item SHOULD NOT be If a device cannot calculate the RLQR, this data item SHOULD NOT be
issued. issued.
skipping to change at page 49, line 34 skipping to change at page 49, line 34
fields: fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RLQT | | RLQT |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 20
Length: 1 Length: 1
Relative Link Quality (Transmit): A non-dimensional 8-bit integer, Relative Link Quality (Transmit): A non-dimensional 8-bit integer,
0-100, representing relative link quality. A value of 100 0-100, representing relative link quality. A value of 100
represents a link of the highest quality. Any value greater than represents a link of the highest quality. Any value greater than
100 MUST be considered as invalid. 100 MUST be considered as invalid.
If a device cannot calculate the RLQT, this data item SHOULD NOT be If a device cannot calculate the RLQT, this data item SHOULD NOT be
issued. issued.
skipping to change at page 50, line 18 skipping to change at page 50, line 18
following fields: following fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interval | | Interval |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 21
Length: 1 Length: 1
Interval: 0 = Do not use timeouts for this Link Characteristics Interval: 0 = Do not use timeouts for this Link Characteristics
request. Non-zero = Interval, in seconds, to wait before request. Non-zero = Interval, in seconds, to wait before
considering this Link Characteristics Request lost. considering this Link Characteristics Request lost.
10. Credit-Windowing 10. Credit-Windowing
DLEP includes an optional Protocol Extension for a credit-windowing DLEP includes an optional Protocol Extension for a credit-windowing
skipping to change at page 51, line 4 skipping to change at page 51, line 4
router. router.
Credits are managed on a destination-specific basis; that is, Credits are managed on a destination-specific basis; that is,
separate credit counts are maintained for each destination requiring separate credit counts are maintained for each destination requiring
the service. Credits do not apply to the DLEP session that exists the service. Credits do not apply to the DLEP session that exists
between routers and modems; they are applied only to the data plane between routers and modems; they are applied only to the data plane
traffic. traffic.
Credits represent the number of octets, or an increment in the number Credits represent the number of octets, or an increment in the number
of octets, that MAY be sent on the given window. When sending data of octets, that MAY be sent on the given window. When sending data
plane traffic to a credit-enabled peer, the sender MUST decriment the plane traffic to a credit-enabled peer, the sender MUST decrement the
appropriate window by the size of the data being sent. For example, appropriate window by the size of the data being sent. For example,
when sending data plane traffic via the modem, the router MUST when sending data plane traffic via the modem, the router MUST
decriment the 'Modem Receive Window' (MRW) for the corresponding decriment the 'Modem Receive Window' (MRW) for the corresponding
destination. When the number of available credits to the destination destination. When the number of available credits to the destination
reaches 0, a sender MUST stop sending data plane traffic to the reaches 0, a sender MUST stop sending data plane traffic to the
destination, until additional credits are supplied. destination, until additional credits are supplied.
If a peer is able to support the optional credit-windowing extension If a peer is able to support the optional credit-windowing extension
then it MUST include an Extensions Supported data item (Section 9.6) then it MUST include an Extensions Supported data item (Section 9.6)
including the value 1, from Table 4, in the appropriate Session including the value 1, from Table 4, in the appropriate Session
skipping to change at page 52, line 22 skipping to change at page 52, line 22
10.2. Credit-Windowing Data Items 10.2. Credit-Windowing Data Items
The credit-windowing extension introduces 3 additional data items. The credit-windowing extension introduces 3 additional data items.
If a peer has advertised during session initialization that it If a peer has advertised during session initialization that it
supports the credit-windowing extension then it MUST correctly supports the credit-windowing extension then it MUST correctly
process the following data items: process the following data items:
+------------+------------------------------------------------------+ +------------+------------------------------------------------------+
| Type Code | Description | | Type Code | Description |
+------------+------------------------------------------------------+ +------------+------------------------------------------------------+
| 23 | Credit Grant (Section 10.2.1) | | 22 | Credit Grant (Section 10.2.1) |
| 24 | Credit Window Status (Section 10.2.2) | | 23 | Credit Window Status (Section 10.2.2) |
| 25 | Credit Request (Section 10.2.3) | | 24 | Credit Request (Section 10.2.3) |
+------------+------------------------------------------------------+ +------------+------------------------------------------------------+
10.2.1. Credit Grant 10.2.1. Credit Grant
The Credit Grant data item is sent from a DLEP participant to grant The Credit Grant data item is sent from a DLEP participant to grant
an increment to credits on a window. The Credit Grant data item MAY an increment to credits on a window. The Credit Grant data item MAY
appear in the Destination Up (Section 8.9) and Destination Update appear in the Destination Up (Section 8.9) and Destination Update
(Section 8.13) messages. The value in a Credit Grant data item (Section 8.13) messages. The value in a Credit Grant data item
represents an increment to be added to any existing credits available represents an increment to be added to any existing credits available
on the window. Upon successful receipt and processing of a Credit on the window. Upon successful receipt and processing of a Credit
Grant data item, the receiver MUST respond with a message containing Grant data item, the receiver MUST respond with a message containing
a Credit Window Status data item to report the updated aggregate a Credit Window Status data item to report the updated aggregate
values for synchronization purposes, and if initializing a new credit values for synchronization purposes, and if initializing a new credit
window, granting initial credits. window, granting initial credits.
When DLEP peers desire to employ the credit-windowing extension, the When DLEP peers desire to employ the credit-windowing extension, the
peer originating the Destination Up message MUST supply an initial, peer originating the Destination Up message MUST supply an initial,
non-zero value as the credit increment of the receive window it non-zero value as the credit increment of the receive window it
controls (i.e., the Modem Recive Window, or Router Receive Window). controls (i.e., the Modem Receive Window, or Router Receive Window).
When receiving a Credit Grant data item on a Destination Up When receiving a Credit Grant data item on a Destination Up message,
(#msg_dest_up) message, the receiver MUST take one of the following the receiver MUST take one of the following actions:
actions:
1. Reject the use of credits for this destination, via the 1. Reject the use of credits for this destination, via the
Destination Up Response message containing a Status data item Destination Up Response message containing a Status data item
(Section 9.1) with a status code of 'Request Denied'. (See (Section 9.1) with a status code of 'Request Denied'. (See
Table 3), or Table 3), or
2. Initialize the appropriate window value of zero, then apply the 2. Initialize the appropriate window value of zero, then apply the
increment specified in the Credit Grant data item. increment specified in the Credit Grant data item.
If the initialization completes successfully, the receiver MUST If the initialization completes successfully, the receiver MUST
skipping to change at page 53, line 25 skipping to change at page 53, line 25
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Credit Increment : | Credit Increment :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Credit Increment | : Credit Increment |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 22
Length: 8 Length: 8
Reserved: A 64-bit unsigned integer representing the additional Reserved: A 64-bit unsigned integer representing the additional
credits to be assigned to the credit window. credits to be assigned to the credit window.
Since credits can only be granted by the receiver on a window, the Since credits can only be granted by the receiver on a window, the
applicable credit window (either the MRW or the RRW) is derived from applicable credit window (either the MRW or the RRW) is derived from
the sender of the grant. The Credit Increment MUST NOT cause the the sender of the grant. The Credit Increment MUST NOT cause the
window to overflow; if this condition occurs, implementations MUST window to overflow; if this condition occurs, implementations MUST
skipping to change at page 54, line 19 skipping to change at page 54, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Modem Receive Window Value : | Modem Receive Window Value :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Modem Receive Window Value | : Modem Receive Window Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router Receive Window Value : | Router Receive Window Value :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Router Receive Window Value | : Router Receive Window Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 23
Length: 16 Length: 16
Modem Receive Window Value: A 64-bit unsigned integer, indicating Modem Receive Window Value: A 64-bit unsigned integer, indicating
the current number of credits available on the Modem Receive the current number of credits available on the Modem Receive
Window, for the destination referred to by the message. Window, for the destination referred to by the message.
Router Receive Window Value: A 64-bit unsigned integer, indicating Router Receive Window Value: A 64-bit unsigned integer, indicating
the current number of credits available on the Router Receive the current number of credits available on the Router Receive
Window, for the destination referred to by the message. Window, for the destination referred to by the message.
skipping to change at page 54, line 50 skipping to change at page 54, line 50
item MUST be silently dropped by the receiver. item MUST be silently dropped by the receiver.
The Credit Request data item contains the following fields: The Credit Request data item contains the following fields:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length | | Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Data Item Type: TBD Data Item Type: 24
Length: 0 Length: 0
11. Security Considerations 11. Security Considerations
The potential security concerns when using DLEP are: The potential security concerns when using DLEP are:
1. DLEP peers may be 'spoofed' by an attacker, either at DLEP 1. DLEP peers may be 'spoofed' by an attacker, either at DLEP
session initialization, or by injection of messages once a session initialization, or by injection of messages once a
session has been established, and/or session has been established, and/or
2. DLEP data items could be altered by an attacker, causing the 2. DLEP data items could be altered by an attacker, causing the
receiving peer to inappropriately alter its information base receiving peer to inappropriately alter its information base
concerning network status. concerning network status.
The protocol itself does not contain any mechanisms for security If the modem and router are separated by more than a single hop,
(e.g., authentication or encryption), as it assumes that an session messages could be altered in order to subvert the behaviour
appropriate level of authentication and non-repudiation is acheived of either or both DLEP participants. Under these circumstances, the
by use of [TLS] when necessary. This specification does not address use of [TLS] is strongly RECOMMENDED. However, if both devices are
security of the data plane, as it (the data plane) is not affected, directly physically connected, or exist within an externally secured
and standard security procedures can be employed. private network then an implementation MAY choose not to use TLS.
To avoid potential denial of service attack, it is RECOMMENDED that
implementations using the Peer Discovery mechanism maintain an
information base of peers that persistently fail Session
initialization having provided an acceptable Discovery signal, and
ignore discovery signals from such peers.
This specification does not address security of the data plane, as it
(the data plane) is not affected, and standard security procedures
can be employed.
12. IANA Considerations 12. IANA Considerations
This section specifies requests to IANA. This section specifies requests to IANA.
12.1. Registrations 12.1. Registrations
This specification defines: This specification defines:
o A new repository for DLEP signals and messages, with sixteen (16) o A new repository for DLEP signals and messages, with sixteen (16)
skipping to change at page 57, line 43 skipping to change at page 57, line 43
We would also like to acknowledge the influence and contributions of We would also like to acknowledge the influence and contributions of
Greg Harrison, Chris Olsen, Martin Duke, Subir Das, Jaewon Kang, Greg Harrison, Chris Olsen, Martin Duke, Subir Das, Jaewon Kang,
Vikram Kaul, Nelson Powell and Victoria Mercieca. Vikram Kaul, Nelson Powell and Victoria Mercieca.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
14.2. Informative References 14.2. Informative References
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/
RFC5246, August 2008,
<http://www.rfc-editor.org/info/rfc5246>.
[RFC5578] Berry, B., Ratliff, S., Paradise, E., Kaiser, T., and M. [RFC5578] Berry, B., Ed., Ratliff, S., Paradise, E., Kaiser, T., and
Adams, "PPP over Ethernet (PPPoE) Extensions for Credit M. Adams, "PPP over Ethernet (PPPoE) Extensions for Credit
Flow and Link Metrics", RFC 5578, February 2010. Flow and Link Metrics", RFC 5578, DOI 10.17487/RFC5578,
February 2010, <http://www.rfc-editor.org/info/rfc5578>.
Appendix A. Discovery Signal Flows Appendix A. Discovery Signal Flows
Router Modem Signal Description Router Modem Signal Description
======================================================================== ========================================================================
| Router initiates discovery, starts | Router initiates discovery, starts
| a timer, send Peer Discovery | a timer, send Peer Discovery
|-------Peer Discovery---->|| signal. |-------Peer Discovery---->|| signal.
 End of changes. 49 change blocks. 
64 lines changed or deleted 86 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/