draft-ietf-manet-dlep-00.txt   draft-ietf-manet-dlep-01.txt 
Mobile Ad hoc Networks Working S. Ratliff Mobile Ad hoc Networks Working S. Ratliff
Group B. Berry Group B. Berry
Internet-Draft G. Harrison Internet-Draft G. Harrison
Intended status: Standards Track S. Jury Intended status: Standards Track S. Jury
Expires: May 22, 2011 D. Satterwhite Expires: November 2, 2011 D. Satterwhite
Cisco Systems Cisco Systems
November 22, 2010 May 2, 2011
Dynamic Link Exchange Protocol (DLEP) Dynamic Link Exchange Protocol (DLEP)
draft-ietf-manet-dlep-00 draft-ietf-manet-dlep-01
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
forwarding decisions. In mobile or other environments where these forwarding 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 46 skipping to change at page 1, line 46
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 22, 2011 . This Internet-Draft will expire on November 2, 2011 .
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 2, line 19 skipping to change at page 2, line 19
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . 5
2. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Normal Session Flow . . . . . . . . . . . . . . . . . . . . . 5 3. Normal Session Flow . . . . . . . . . . . . . . . . . . . . . 5
4. Generic DLEP Packet Definition . . . . . . . . . . . . . . . . 6 4. Generic DLEP Packet Definition . . . . . . . . . . . . . . . . 6
5. Generic DLEP Message Format . . . . . . . . . . . . . . . . . 6 5. Message Header Format . . . . . . . . . . . . . . . . . . . . 7
6. Generic DLEP TLV Block Format . . . . . . . . . . . . . . . . 7 6. Message TLV Block Format . . . . . . . . . . . . . . . . . . . 7
7. DLEP TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. DLEP Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Identification TLV . . . . . . . . . . . . . . . . . . . . 8 7.1. Identification Sub-TLV . . . . . . . . . . . . . . . . . . 9
7.2. DLEP Version TLV . . . . . . . . . . . . . . . . . . . . . 9 7.2. DLEP Version Sub-TLV . . . . . . . . . . . . . . . . . . . 10
7.3. Peer Type TLV . . . . . . . . . . . . . . . . . . . . . . 10 7.3. Peer Type Sub-TLV . . . . . . . . . . . . . . . . . . . . 11
7.4. MAC Address TLV . . . . . . . . . . . . . . . . . . . . . 10 7.4. MAC Address Sub-TLV . . . . . . . . . . . . . . . . . . . 11
7.5. IPv4 Address TLV . . . . . . . . . . . . . . . . . . . . . 11 7.5. IPv4 Address Sub-TLV . . . . . . . . . . . . . . . . . . . 12
7.6. IPv6 Address TLV . . . . . . . . . . . . . . . . . . . . . 12 7.6. IPv6 Address Sub-TLV . . . . . . . . . . . . . . . . . . . 12
7.7. Maximum Data Rate TLV. . . . . . . . . . . . . . . . . . . 13 7.7. Maximum Data Rate Sub-TLV. . . . . . . . . . . . . . . . . 13
7.8. Current Data Rate TLV. . . . . . . . . . . . . . . . . . . 13 7.8. Current Data Rate Sub-TLV. . . . . . . . . . . . . . . . . 14
7.9. Latency TLV. . . . . . . . . . . . . . . . . . . . . . . . 14 7.9. Latency Sub-TLV. . . . . . . . . . . . . . . . . . . . . . 14
7.10. Resources TLV. . . . . . . . . . . . . . . . . . . . . . . 15 7.10. Resources Sub-TLV. . . . . . . . . . . . . . . . . . . . . 15
7.11. Relative Link Quality TLV. . . . . . . . . . . . . . . . . 15 7.11. Relative Link Quality Sub-TLV. . . . . . . . . . . . . . . 16
7.12. Peer Termination TLV . . . . . . . . . . . . . . . . . . . 16 7.12. Peer Termination Sub-TLV . . . . . . . . . . . . . . . . . 16
8. DLEP Messages. . . . . . . . . . . . . . . . . . . . . . . . . 16 7.13 Heartbeat Interval Sub-TLV . . . . . . . . . . . . . . . . 17
8.1. Message TLVs . . . . . . . . . . . . . . . . . . . . . . . 17 7.14 Heartbeat Threshold Sub-TLV. . . . . . . . . . . . . . . . 17
9. Peer Discovery Messages . . . . . . . . . . . . . . . . . . . 17 7.15 Link Characteristics ACK Timer Sub-TLV . . . . . . . . . . 18
9.1. Attached Peer Discovery Message . . . . . . . . . . . . . 17 8. DLEP Protocol Messages . . . . . . . . . . . . . . . . . . . . 19
9.2. Detached Peer Discovery Message . . . . . . . . . . . . . 19 8.1. Message Block TLV Values . . . . . . . . . . . . . . . . . 19
10. Peer Offer Message . . . . . . . . . . . . . . . . . . . . . . 20 9. Peer Discovery Messages . . . . . . . . . . . . . . . . . . . 20
11. Peer Update Message. . . . . . . . . . . . . . . . . . . . . . 21 9.1. Attached Peer Discovery Message . . . . . . . . . . . . . 20
12. Peer Update ACK Message. . . . . . . . . . . . . . . . . . . . 23 9.2. Detached Peer Discovery Message . . . . . . . . . . . . . 22
13. Peer Termination Message . . . . . . . . . . . . . . . . . . . 23 10. Peer Offer Message . . . . . . . . . . . . . . . . . . . . . . 23
14. Peer Termination ACK Message . . . . . . . . . . . . . . . . . 24 11. Peer Update Message. . . . . . . . . . . . . . . . . . . . . . 25
15. Neighbor Up Message . . . . . . . . . . . . . . . . . . . . . 26 12. Peer Update ACK Message. . . . . . . . . . . . . . . . . . . . 27
16. Neighbor Up ACK Message. . . . . . . . . . . . . . . . . . . . 27 13. Peer Termination Message . . . . . . . . . . . . . . . . . . . 27
17. Neighbor Down Message . . . . . . . . . . . . . . . . . . . . 28 14. Peer Termination ACK Message . . . . . . . . . . . . . . . . . 28
18. Neighbor Down ACK Message. . . . . . . . . . . . . . . . . . . 29 15. Neighbor Up Message . . . . . . . . . . . . . . . . . . . . . 29
19. Neighbor Update Message . . . . . . . . . . . . . . . . . . . 30 16. Neighbor Up ACK Message. . . . . . . . . . . . . . . . . . . . 31
20. Neighbor Address Update Message. . . . . . . . . . . . . . . . 31 17. Neighbor Down Message . . . . . . . . . . . . . . . . . . . . 32
21. Neighbor Address Update ACK Message. . . . . . . . . . . . . . 32 18. Neighbor Down ACK Message. . . . . . . . . . . . . . . . . . . 33
22. Heartbeat Message . . . . . . . . . . . . . . . . . . . . . . 33 19. Neighbor Update Message . . . . . . . . . . . . . . . . . . . 35
23. Link Characteristics Message . . . . . . . . . . . . . . . . . 33 20. Neighbor Address Update Message. . . . . . . . . . . . . . . . 36
24. Link Characteristics ACK Message . . . . . . . . . . . . . . . 35 21. Neighbor Address Update ACK Message. . . . . . . . . . . . . . 38
25. Security Considerations. . . . . . . . . . . . . . . . . . . . 36 22. Heartbeat Message . . . . . . . . . . . . . . . . . . . . . . 39
26. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 36 23. Link Characteristics Message . . . . . . . . . . . . . . . . . 39
26.1 TLV Registrations. . . . . . . . . . . . . . . . . . . . . 36 24. Link Characteristics ACK Message . . . . . . . . . . . . . . . 41
26.2 Expert Review: Evaluation Guidelines . . . . . . . . . . . 37 25. Security Considerations. . . . . . . . . . . . . . . . . . . . 42
26.3 Packet TLV Type Registrations. . . . . . . . . . . . . . . 37 26. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 42
26.4 Message TLV Type Registrations . . . . . . . . . . . . . . 37 26.1 TLV Registrations. . . . . . . . . . . . . . . . . . . . . 43
27. Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . 38 26.2 Expert Review: Evaluation Guidelines . . . . . . . . . . . 43
26.3 Message TLV Type Registrations . . . . . . . . . . . . . . 43
26.4 DLEP Order Registrations . . . . . . . . . . . . . . . . . 43
26.5 DLEP Sub-TLV Type Registrations. . . . . . . . . . . . . . 44
27. Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . 45
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 bandwidth and quality. Examples of these types of links variable bandwidth and quality. Examples of these types of links
include line-of-sight (LOS) radios, satellite terminals, and cable/ include line-of-sight (LOS) radios, satellite terminals, and cable/
DSL modems. Fluctuations in speed and quality of these links can DSL modems. Fluctuations in speed and quality of these links can
occur due to configuration (in the case of cable/DSL modems), or on a occur due to configuration (in the case of cable/DSL modems), or on a
moment-to-moment basis, due to physical phenomena like multipath moment-to-moment basis, due to physical phenomena like multipath
interference, obstructions, rain fade, etc. It is also quite possible interference, obstructions, rain fade, etc. It is also quite possible
skipping to change at page 4, line 46 skipping to change at page 4, line 48
+--------+ +-------+ +-------+ +--------+ +--------+ +-------+ +-------+ +--------+
| | | Link | | | | | | Link | | |
|-DLEP--| | Protocol | |-DLEP--| |-DLEP--| | Protocol | |-DLEP--|
| | | (e.g. | | | | | | (e.g. | | |
| | | 802.11) | | | | | | 802.11) | | |
Figure 1: DLEP Network Figure 1: DLEP Network
DLEP exists as a collection of type-length-value (TLV) based messages DLEP exists as a collection of type-length-value (TLV) based messages
formatted using RFC 5444. The protocol can be used for both Ethernet- using [RFC5444] formatting. The protocol can be used for both Ethernet
attached modems (utilizing, for example, a UDP socket for transport attached modems (utilizing, for example, a UDP socket for transport
of the RFC 5444 packets), or in environments where the modem is an of the RFC 5444 packets), or in environments where the modem is an
interface card in a chassis (via a message passing scheme). DLEP interface card in a chassis (via a message passing scheme). DLEP
utilizes a session paradigm between the modem device and its utilizes a session paradigm between the modem device and its
associated router. If multiple modem devices are attached to a associated router. If multiple modem devices are attached to a
router, a separate DLEP session MUST exist for each modem. If a modem router, a separate DLEP session MUST exist for each modem. If a modem
device supports multiple connections to a router (via multiple device supports multiple connections to a router (via multiple
interfaces), or supports connections to multiple routers, a separate interfaces), or supports connections to multiple routers, a separate
DLEP session MUST exist for each connection. DLEP session MUST exist for each connection.
skipping to change at page 5, line 16 skipping to change at page 5, line 18
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. [RFC2119].
2. Assumptions 2. Assumptions
In order to implement discovery in the DLEP protocol (thereby In order to implement discovery in the DLEP protocol (thereby
avoiding some configuration), we have defined a first-speaker and a avoiding some configuration), we have defined a first-speaker and a
passive-listener. Specifically, the router is defined as the passive- passive-listener scheme. Specifically, the router is defined as the
listener, and the modem device defined as the first-speaker (e.g. the passive-listener, and the modem device defined as the first-speaker
initiator for discovery). Borrowing from existing terminology, this (e.g. the initiator for discovery). Borrowing from existing
document refers to the first-speaker as the 'client', even though terminology, this document refers to the first-speaker as the
there is no client/server relationship in the classic sense. 'client', even though there is no client/server relationship in the
classic sense.
DLEP assumes that participating modem devices appear to the router DLEP assumes that participating modem devices appear to the router
as a transparent bridge - specifically, the assumption is that the as a transparent bridge - specifically, the assumption is that the
destination MAC address for data traffic in any frame emitted by destination MAC address for data traffic in any frame emitted by
the router should be the MAC address of the next-hop router or end- the router should be the MAC address of the next-hop router or end-
device, and not the MAC address of any of the intervening modem device, and not the MAC address of any of the intervening modem
devices. devices.
DLEP assumes that security on the session (e.g. authentication of DLEP assumes that security on the session (e.g. authentication of
session partners, encryption of traffic, or both) is dealt with by session partners, encryption of traffic, or both) is dealt with by
the underlying transport mechanism for the RFC 5444 packets (e.g. by the underlying transport mechanism for the RFC 5444 packets (e.g. by
using a transport such as DTLS [DTLS]). using a transport such as DTLS [DTLS]).
The RFC 5444 message header Sequence Number MUST be included in all The optional [RFC5444] message header Sequence Number MUST be
DLEP packets. Sequence Numbers start at 1 and are incremented by one included in all DLEP packets. Sequence Numbers start at 1 and are
for each original and retransmitted message. The unsigned 16-bit incremented by one for each original and retransmitted message. The
Sequence Number rolls over at 65535 to 1. A Sequence Number of 0 is unsigned 16-bit Sequence Number rolls over at 65535 to 1. A
not valid. Peer level Sequence Numbers are unique within the context Sequence Number of 0 is not valid. Peer level Sequence Numbers are
of a DLEP session. Sequence numbers are used in DLEP to correlate unique within the context of a DLEP session. Sequence numbers are
a response to a request. used in DLEP to correlate a response to a request.
3. Normal Session Flow 3. Normal Session Flow
A session between a router and a client is established by exchanging A session between a router and a client is established by exchanging
the "Peer Discovery" and "Peer Offer" messages described below. the "Peer Discovery" and "Peer Offer" messages described below.
Once that exchange has successfully occurred, the client informs the Once that exchange has successfully occurred, the client informs the
router of the presence of a new potential routing partner via the router of the presence of a new potential routing partner via the
"Neighbor Up" message. The loss of a neighbor is communicated via the "Neighbor Up" message. The loss of a neighbor is communicated via the
"Neighbor Down" message, and link quality is communicated via the "Neighbor Down" message, and link quality is communicated via the
skipping to change at page 6, line 17 skipping to change at page 6, line 20
In addition to receiving metrics about the link, DLEP provides for In addition to receiving metrics about the link, DLEP provides for
the ability for the router to request a different amount of the ability for the router to request a different amount of
bandwidth, or latency, for its client via the Link Characteristics bandwidth, or latency, for its client via the Link Characteristics
Message. This allows the router to deal with requisite increases Message. This allows the router to deal with requisite increases
(or decreases) of allocated bandwidth/latency in demand-based (or decreases) of allocated bandwidth/latency in demand-based
schemes in a more deterministic manner. schemes in a more deterministic manner.
4. Generic DLEP Packet Definition 4. Generic DLEP Packet Definition
The Generic DLEP Packet Definition follows the format for packets The Generic DLEP Packet Definition follows the format for packets
defined in RFC 5444. defined in [RFC5444].
The Generic DLEP Packet Definition contains the following fields: The Generic DLEP Packet Definition 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Version| Flags | Packet Sequence Number | Packet TLV | |Version| Flags | Packet Sequence Number | Packet TLV |
| | | | Block... | | | | | Block... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message... | | Message (Contains DLEP message)... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Version - Version of RFC5444 specification on Version - Version of RFC 5444 specification on
which the packet/messages/TLVs are which the packet/messages/TLVs are
constructed. constructed.
Flags - 4 bit field. Only bit 1 (phastlv) is Flags - 4 bit field. All bits MUST be ignored
set/used. All other bits MUST be ignored
by DLEP implementations. by DLEP implementations.
Packet Sequence Number - If present, the packet sequence number Packet Sequence Number - If present, the packet sequence number
is parsed and ignored. DLEP does NOT is parsed and ignored. DLEP does NOT
use or generate packet sequence numbers. use or generate packet sequence numbers.
Packet TLV block - a TLV block which contains packet level Packet TLV block - a TLV block which contains packet level
TLV information. TLV information. DLEP implementations
MUST NOT use this TLV block.
Message - the packet MAY contain zero or more Message - the packet MAY contain zero or more
messages. messages, however, DLEP messages are
encoded within an RFC 5444 Message
5. Generic DLEP Message Format TLV Block.
The Generic DLEP Message Format follows the format for MANET messages 5. Message Header Format
defined in RFC 5444. The <msg-seq-num> field, which is OPTIONAL in
RFC 5444, MUST exist in all DLEP messages.
The Generic DLEP Message Format contains the following fields: DLEP utilizes the following format for the RFC 5444 message header
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type |Msg Flg|AddrLen| Message Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLV Block... | | Message Seq Num | TLV Block... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Type - an 8-bit field which specifies the type Message Type - an 8-bit field which specifies the type
of the message of the message. For DLEP, this field
contains DLEP_MESSAGE (value TBD)
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit is Message Flags - Set to 0x1 (bit 3, mhasseqnum bit is
set). All other bits are unused and MUST set). All other bits are unused and MUST
be set to '0'. be set to '0'.
Message Address Length - a 4-bit unsigned integer field encoding the Message Address Length - a 4-bit unsigned integer field encoding the
length of all addresses included in this length of all addresses included in this
message. DLEP implementations do not use message. DLEP implementations do not use
this field; contents SHOULD be ignored. this field; contents SHOULD be ignored.
skipping to change at page 7, line 40 skipping to change at page 7, line 43
Message Sequence Number - a 16-bit unsigned integer field that Message Sequence Number - a 16-bit unsigned integer field that
contains a sequence number, generated by contains a sequence number, generated by
the originator of the message. Sequence the originator of the message. Sequence
numbers range from 1 to 65535. Sequence numbers range from 1 to 65535. Sequence
numbers roll over at 65535 to 1; 0 is numbers roll over at 65535 to 1; 0 is
invalid. invalid.
TLV Block - TLV Block included in the message. TLV Block - TLV Block included in the message.
6. Generic DLEP TLV Block Format 6. Message TLV Block Format
The Generic DLEP TLV Block Format follows the format for MANET The DLEP protocol is organized as a set of orders, each with a
message TLVs defined in RFC 5444. collection of Sub-TLVs. The Sub-TLVs carry information needed
to process and/or establish context (e.g. the MAC address of a
far-end router), and the 'tlv-type' field in the message TLV
block carries the DLEP order itself. The DLEP orders are
enumerated in section 8.1 of this document, and the messages
created using these orders are documented in sections 9 through
24.
The Generic DLEP TLV Block Format contains the following fields: DLEP uses the following settings for an RFC 5444 Message TLV
block:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLVs Length | TLV Type | TLV Flags | | TLVs Length | TLV Type | TLV Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Value... | | Length | Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLVs Length - a 16-bit unsigned integer field that contains the total TLVs Length - a 16-bit unsigned integer field that contains the total
number of octets in all of the immediately following number of octets in all of the immediately following
TLV elements (tlvs-length not included). TLV elements (tlvs-length not included).
TLV Type - an 8-bit unsigned integer field specifying the type of TLV Type - an 8-bit unsigned integer field specifying the type
the TLV. of the TLV. DLEP uses this field to specify the DLEP
order. Valid DLEP orders are defined in section 8.1 of
this document.
TLV Flags - an 8-bit flags bit field. Only bit 3 (thasvalue) is TLV Flags - an 8-bit flags bit field. Bit 3 (thasvalue) MUST be
set, all other bits are not used and MUST be set to set; all other bits are not used and MUST be set
'0'. to '0'.
Length - Length of the value field of the TLV Length - Length of the 'Value' field of the TLV
Value - A field of length <Length> which contains data specific Value - A field of length <Length> which contains data
to a particular TLV type. specific to a particular TLV type. In the DLEP
case, this field will consist of a collection of
DLEP sub-TLVs appropriate for the DLEP action
specified in the TLV type field.
7. DLEP TLVs 7. DLEP sub-TLVs
DLEP protocol messages are transported in an RFC 5444 message TLV.
All DLEP messages use the RFC 5444 DLEP_MESSAGE value (TBD). The
protocol messages consist of a DLEP order, encoded in the 'tlv-type'
field in the message TLV block, with the 'value' field of the TLV
block containing a collection (1 or more) DLEP sub-TLVs.
The format of DLEP Sub-TLVs is consistent with RFC 5444 in that the
Sub-TLVs contain a flag field in addition to the type, length, and
value fields. Valid DLEP Sub-TLVs are:
TLV TLV TLV TLV
Value Description Value Description
========================================= =========================================
TBD Identification TLV TBD Identification sub-TLV
TBD DLEP Version TLV TBD DLEP Version sub-TLV
TBD Peer Type TLV TBD Peer Type sub-TLV
TBD MAC Address TLV TBD MAC Address sub-TLV
TBD IPv4 Address TLV TBD IPv4 Address sub-TLV
TBD IPv6 Address TLV TBD IPv6 Address sub-TLV
TBD Maximum Data Rate (MDR) TLV TBD Maximum Data Rate (MDR) sub-TLV
TBD Current Data Rate (CDR) TLV TBD Current Data Rate (CDR) sub-TLV
TBD Latency TLV TBD Latency sub-TLV
TBD Resources TLV TBD Resources sub-TLV
TBD Relative Link Quality (RLQ) TLV TBD Relative Link Quality (RLQ) sub-TLV
TBD Status TLV TBD Status sub-TLV
TBD Heartbeat Interval sub-TLV
TBD Heartbeat Threshold sub-TLV
TBD Neighbor down ACK timer sub-TLV
TBD Link Characteristics ACK timer sub-TLV
7.1 Identification TLV DLEP sub-TLVs contain the following fields:
This TLV MUST be in the Packet Header TLV Block for all DLEP 0 1 2 3
messages. It contains client and router identification information 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
used for all messages contained within the packet. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TLV Type |TLV Flags=0x10 | Length | Value... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Identification TLV contains the following fields: TLV Type - an 8-bit unsigned integer field specifying the type
of the sub-TLV.
TLV Flags - an 8-bit flags bit field. Bit 3 (thasvalue) MUST be
set, all other bits are not used and MUST be set to
'0'.
Length - an 8-bit length of the value field of the sub-TLV
Value - A field of length <Length> which contains data
specific to a particular sub-TLV.
7.1 Identification Sub-TLV
This Sub-TLV MUST exist in the TLV Block for all DLEP messages, and
MUST be the first Sub-TLV of the message. Further, there MUST be ONLY
one Identification Sub-TLV in an RFC 5444 message TLV block. The
Identification sub-TLV contains client and router identification
information used to establish the proper context for processing DLEP
protocol messages.
The Identification sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 |Length = 9 | Heartbeat | |TLV Type = TBD |TLV Flags=0x10 |Length = 8 | Router ID |
| | | | Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Client ID | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Client ID |
TLV Type - Value TBD +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Type - Value TBD
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are
unused and MUST be set to '0'. unused and MUST be set to '0'.
Length - 9 Length - 8
Heartbeat - An 8-bit, unsigned value containing the heartbeat
Interval interval, in seconds for this session. A value of
'0' indicates that no heartbeats are used on this
session.
This value is used during the Peer Discovery/Peer
Offer exchange. In other packets, the value MUST be
ignored.
The Heartbeat timer runs at a peer-to-peer level,
that is, it runs between a router and a modem
device. If a peer does NOT receive any messages for
some number of Heartbeat intervals (default 4), it
should initiate DLEP session termination procedures.
Router ID - indicates the router ID of the DLEP session. Router ID - indicates the router ID of the DLEP session.
Client ID - indicates the client ID of the DLEP session. Client ID - indicates the client ID of the DLEP session.
When the client initiates discovery (via the Peer Discovery message), When the client initiates discovery (via the Peer Discovery message),
it MUST set the Client ID to a 32-bit quantity that will be used to it MUST set the Client ID to a 32-bit quantity that will be used to
uniquely identify this session from the client-side. The client MUST uniquely identify this session from the client-side. The client MUST
set the Router ID to '0'. When responding to the Peer Discovery set the Router ID to '0'. When responding to the Peer Discovery
message, the router MUST echo the Client ID, and MUST supply its own message, the router MUST echo the Client ID, and MUST supply its own
unique 32-bit quantity to identify the session from the router's unique 32-bit quantity to identify the session from the router's
perspective. After the Peer Discovery/Peer Offer exchange, both the perspective. After the Peer Discovery/Peer Offer exchange, both the
Client ID and the Router ID MUST be set to the values obtained from Client ID and the Router ID MUST be set to the values obtained from
the Peer DIscovery/Peer Offer sequence. the Peer DIscovery/Peer Offer sequence.
7.2 DLEP Version TLV 7.2 DLEP Version Sub-TLV
The DLEP Version TLV is OPTIONAL, and is used to indicate the client The DLEP Version Sub-TLV is an OPTIONAL TLV in both the Peer
or router version of the protocol. The client and router MAY use this Discovery and Peer Offer messages. The Version Sub-TLV is used to
information to decide if the peer is running at a supported level. indicate the client or router version of the protocol. The client
and router MAY use this information to decide if the peer is running
at a supported level.
The DLEP Version TLV contains the following fields: The DLEP Version Sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length=4 | Major Version | |TLV Type =TBD |TLV Flags=0x10 |Length=4 | Major Version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Major Version | Minor Version | | Major Version | Minor Version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Type - TBD TLV Type - TBD
skipping to change at page 10, line 4 skipping to change at page 10, line 49
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Major Version | Minor Version | | Major Version | Minor Version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Type - TBD TLV Type - TBD
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are
not used and MUST be set to '0'. not used and MUST be set to '0'.
Length - Length is 4 Length - Length is 4
Major Version - Major version of the client or router protocol. Major Version - Major version of the client or router protocol.
Minor Version - Minor version of the client or router protocol. Minor Version - Minor version of the client or router protocol.
Support of this draft is indicated by setting the Major Version Support of this draft is indicated by setting the Major Version
to '1', and the Minor Version to '0' (e.g. Version 1.0). to '1', and the Minor Version to '1' (e.g. Version 1.1).
7.3 Peer Type TLV 7.3 Peer Type Sub-TLV
The Peer Type TLV is used by the router and client to give additional The Peer Type Sub-TLV is used by the router and client to give
information as to its type. It is an OPTIONAL TLV in both the Peer additional information as to its type. It is an OPTIONAL sub-TLV in
Discovery Message and the Peer Offer message. The peer type is a both the Peer Discovery Message and the Peer Offer message. The peer
string and is envisioned to be used for informational purposes (e.g. type is a string and is envisioned to be used for informational
display command). purposes (e.g. display command).
The Peer Type TLV contains the following fields: The Peer Type sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length= peer |Peer Type Str | |TLV Type =TBD |TLV Flags=0x10 |Length= peer |Peer Type Str |
| | |type string len|Max Len = 80 | | | |type string len|Max Len = 80 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Type - TBD TLV Type - TBD
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits
are not used and MUST be set to '0'. are not used and MUST be set to '0'.
Length - length of peer type string (80 bytes maximum) Length - length of peer type string (80 bytes maximum)
Peer Type String - Non-Null terminated peer type string, maximum Peer Type String - Non-Null terminated peer type string, maximum
length of 80 bytes. For example, a satellite length of 80 bytes. For example, a satellite
modem might set this variable to 'Satellite modem might set this variable to 'Satellite
terminal'. terminal'.
7.4 MAC Address TLV 7.4 MAC Address Sub-TLV
The MAC address TLV MUST appear in all neighbor-oriented messages The MAC address Sub-TLV MUST appear in all neighbor-oriented
(e.g. Neighbor Up, Neighbor Up ACK, Neighbor Down, Neighbor Down messages (e.g. Neighbor Up, Neighbor Up ACK, Neighbor Down, Neighbor
ACK, Neighbor Update, Link Characteristics Request, and Link Down ACK, Neighbor Update, Link Characteristics Request, and Link
Characteristics ACK). The MAC Address TLV contains the address of Characteristics ACK). The MAC Address sub-TLV contains the address
the far-end (neighbor) router. of the far-end (neighbor) router.
The MAC Address TLV contains the following fields: The MAC Address sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | | MAC Address |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
TLV Type - TBD TLV Type - TBD
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are not TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are not
used and MUST be set to '0'. used and MUST be set to '0'.
Length - 6 Length - 6
MAC Address - MAC Address of the far-end router. MAC Address - MAC Address of the far-end router.
7.5 IPv4 Address TLV 7.5 IPv4 Address Sub-TLV
The IPv4 Address TLV MAY be used in Neighbor Up, Neighbor Update, The IPv4 Address Sub-TLV MAY be used in Neighbor Up, Neighbor Update,
and Peer Update Messages, if the client is aware of the Layer 3 and Peer Update Messages, if the client is aware of the Layer 3
address. When included in Neighbor messages, the IPv4 Address TLV address. When included in Neighbor messages, the IPv4 Address sub-TLV
contains the IPv4 address of the far-end router (neighbor). In contains the IPv4 address of the far-end router (neighbor). In
the Peer Update message, it contains the IPv4 address of the local the Peer Update message, it contains the IPv4 address of the local
router. In either case, the TLV also contains an indication of router. In either case, the sub-TLV also contains an indication of
whether this is a new or existing address, or is a deletion of whether this is a new or existing address, or is a deletion of
a previously known address. a previously known address.
The IPv4 Address TLV contains the following fields: The IPv4 Address Sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 4 | Add/Drop | |TLV Type =TBD |TLV Flags=0x10 |Length = 5 | Add/Drop |
| | | | Indicator | | | | | Indicator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address | | IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Type - TBD TLV Type - TBD
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are not TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are not
used and MUST be set to '0'. used and MUST be set to '0'.
Length - 5 Length - 5
Add/Drop - Value indicating whether this is a new or
Indicator existing address (0x01), or a withdrawal of Add/Drop - Value indicating whether this is a new or existing
an address (0x02). Indicator address (0x01), or a withdrawal of an address (0x02).
IPv4 Address - IPv4 Address of the far-end router. IPv4 Address - IPv4 Address of the far-end router.
7.6 IPv6 Address TLV 7.6 IPv6 Address Sub-TLV
The IPv6 Address TLV MAY be used in Neighbor Up, Neighbor Update, The IPv6 Address Sub-TLV MAY be used in Neighbor Up, Neighbor Update,
and Peer Update Messages, if the client is aware of the Layer 3 and Peer Update Messages, if the client is aware of the Layer 3
address. When included in Neighbor messages, the IPv6 Address TLV address. When included in Neighbor messages, the IPv6 Address sub-TLV
contains the IPv6 address of the far-end router (neighbor). In contains the IPv6 address of the far-end router (neighbor). In
the Peer Update, it contains the IPv6 address of the local router. the Peer Update, it contains the IPv6 address of the local router.
In either case, the TLV also contains an indication of whether In either case, the sub-TLV also contains an indication of whether
this is a new or existing address, or is a deletion of a this is a new or existing address, or is a deletion of a
previously known address. previously known address.
The IPv6 Address TLV contains the following fields: The IPv6 Address sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 17 | Add/Drop | |TLV Type =TBD |TLV Flags=0x10 |Length = 17 | Add/Drop |
| | | | Indicator | | | | | Indicator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
skipping to change at page 13, line 5 skipping to change at page 13, line 35
used and MUST be set to '0'. used and MUST be set to '0'.
Length - 17 Length - 17
Add/Drop - Value indicating whether this is a new or Add/Drop - Value indicating whether this is a new or
Indicator existing address (0x01), or a withdrawal of Indicator existing address (0x01), or a withdrawal of
an address (0x02). an address (0x02).
IPv6 Address - IPv6 Address of the far-end router. IPv6 Address - IPv6 Address of the far-end router.
7.7 Maximum Data Rate TLV 7.7 Maximum Data Rate Sub-TLV
The Maximum Data Rate (MDR) TLV is used in Neighbor Up, Neighbor The Maximum Data Rate (MDR) Sub-TLV is used in Neighbor Up, Neighbor
Update, and Link Characteristics ACK Messages to indicate the Update, and Link Characteristics ACK Messages to indicate the
maximum theoretical data rate, in bits per second, that can be maximum theoretical data rate, in bits per second, that can be
achieved on the link. When metrics are reported via the messages achieved on the link. When metrics are reported via the messages
listed above, the maximum data rate MUST be reported. listed above, the maximum data rate MUST be reported.
The Maximum Data Rate TLV contains the following fields: The Maximum Data Rate sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 8 | MDR (bps) | |TLV Type =TBD |TLV Flags=0x10 |Length = 8 | MDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MDR (bps) | | MDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MDR (bps) | | MDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 13, line 37 skipping to change at page 14, line 14
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other
bits are not used and MUST be set to '0'. bits are not used and MUST be set to '0'.
Length - 8 Length - 8
Maximum Data Rate - A 64-bit unsigned number, representing the Maximum Data Rate - A 64-bit unsigned number, representing the
maximum theoretical data rate, in bits per maximum theoretical data rate, in bits per
second (bps), that can be achieved on the second (bps), that can be achieved on the
link. link.
7.8 Current Data Rate TLV 7.8 Current Data Rate Sub-TLV
The Current Data Rate (CDR) TLV is used in Neighbor Up, Neighbor The Current Data Rate (CDR) Sub-TLV is used in Neighbor Up, Neighbor
Update, Link Characteristics Request, and Link Characteristics ACK Update, Link Characteristics Request, and Link Characteristics ACK
messages to indicate the rate at which the link is currently messages to indicate the rate at which the link is currently
operating, or in the case of the Link Characteristics Request, operating, or in the case of the Link Characteristics Request,
the desired data rate for the link. the desired data rate for the link.
The Current Data Rate TLV contains the following fields: The Current Data Rate sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 8 |CDR (bps) | |TLV Type =TBD |TLV Flags=0x10 |Length = 8 |CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDR (bps) | | CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDR (bps) | | CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 14, line 20 skipping to change at page 14, line 50
Current Data Rate - A 64-bit unsigned number, representing the Current Data Rate - A 64-bit unsigned number, representing the
current data rate, in bits per second (bps), current data rate, in bits per second (bps),
on the link. When reporting metrics (e.g, on the link. When reporting metrics (e.g,
in Neighbor Up, Neighbor Down, or Link in Neighbor Up, Neighbor Down, or Link
Characteristics ACK), if there is no Characteristics ACK), if there is no
distinction between current and maximum distinction between current and maximum
data rates, current data rate SHOULD be data rates, current data rate SHOULD be
set equal to the maximum data rate. set equal to the maximum data rate.
7.9 Latency TLV 7.9 Latency Sub-TLV
The Latency TLV is used in Neighbor Up, Neighbor Update, Link The Latency Sub-TLV is used in Neighbor Up, Neighbor Update, Link
Characteristics Request, and Link Characteristics ACK messages to Characteristics Request, and Link Characteristics ACK messages to
indicate the amount of latency on the link, or in the case of the indicate the amount of latency on the link, or in the case of the
Link Characteristics Request, to indicate the maximum latency Link Characteristics Request, to indicate the maximum latency
required (e.g. a should-not-exeed value) on the link. required (e.g. a should-not-exeed value) on the link.
The Latency TLV contains the following fields: The Latency Sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 2 |Latency (ms) | |TLV Type =TBD |TLV Flags=0x10 |Length = 2 |Latency (ms) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Latency (ms) | |Latency (ms) |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
TLV Type - TBD TLV Type - TBD
skipping to change at page 14, line 55 skipping to change at page 15, line 32
Latency - the transmission delay that a packet Latency - the transmission delay that a packet
encounters as it is transmitted over the encounters as it is transmitted over the
link. In Neighbor Up, Neighbor Update, link. In Neighbor Up, Neighbor Update,
and Link Characteristics ACK, this value and Link Characteristics ACK, this value
is reported in absolute delay, in is reported in absolute delay, in
milliseconds. The calculation of latency milliseconds. The calculation of latency
is modem-device dependent. For example, is modem-device dependent. For example,
the latency may be a running average the latency may be a running average
calculated from the internal queuing. If calculated from the internal queuing. If
the modem device cannot calculate latency, the modem device cannot calculate latency,
it SHOULD be reported as 0. it SHOULD be reported as 0. In the Link
Characteristics Request Message, this value
In the Link Characteristics Request Message, represents the maximum delay, in milliseconds,
this value represents the maximum delay, expected on the link.
in milliseconds, expected on the link.
7.10 Resources TLV 7.10 Resources Sub-TLV
The Resources TLV is used in Neighbor Up, Neighbor Update, and Link The Resources Sub-TLV is used in Neighbor Up, Neighbor Update, and Link
Characteristics ACK messages to indicate a percentage (0-100) amount Characteristics ACK messages to indicate a percentage (0-100) amount
of resources (e.g. battery power) remaining on the modem device. of resources (e.g. battery power) remaining on the modem device.
The Resources TLV contains the following fields: The Resources TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Resources | |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Resources |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 15, line 28 skipping to change at page 16, line 4
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Resources | |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Resources |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Type - TBD TLV Type - TBD
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other
bits are not used and MUST be set to '0'. bits are not used and MUST be set to '0'.
Length - 1 Length - 1
Resources - a percentage, 0-100, representing the amount Resources - a percentage, 0-100, representing the amount
of remaining resources, such as battery power. of remaining resources, such as battery power.
If resources cannot be calculated, a value of If resources cannot be calculated, a value of
100 SHOULD be reported. 100 SHOULD be reported.
7.11 Relative Link Quality TLV 7.11 Relative Link Quality Sub-TLV
The Relative Link Quality (RLQ) TLV is used in Neighbor Up, Neighbor The Relative Link Quality (RLQ) Sub-TLV is used in Neighbor Up,
Update, and Link Characteristics ACK messages to indicate the Neighbor Update, and Link Characteristics ACK messages to indicate
quality of the link as calculated by the modem device. the quality of the link as calculated by the modem device.
The Relative Link Quality TLV contains the following fields: The Relative Link Quality sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 1 |Relative Link | |TLV Type =TBD |TLV Flags=0x10 |Length = 1 |Relative Link |
| | | |Quality (RLQ) | | | | |Quality (RLQ) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Type - TBD TLV Type - TBD
skipping to change at page 16, line 4 skipping to change at page 16, line 30
|TLV Type =TBD |TLV Flags=0x10 |Length = 1 |Relative Link | |TLV Type =TBD |TLV Flags=0x10 |Length = 1 |Relative Link |
| | | |Quality (RLQ) | | | | |Quality (RLQ) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Type - TBD TLV Type - TBD
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other
bits are not used and MUST be set to '0'. bits are not used and MUST be set to '0'.
Length - 1 Length - 1
Relative Link Quality - a non-dimensional number, 0-100, Relative Link Quality - a non-dimensional number, 0-100,
representing the relative link quality. representing the relative link quality.
A value of 100 represents a link of the A value of 100 represents a link of the
highest quality. If the RLQ cannot be highest quality. If the RLQ cannot be
calculated, a value of 100 should be calculated, a value of 100 SHOULD be
reported. reported.
7.12 Status TLV 7.12 Status Sub-TLV
The Status TLV is sent from either the client or router to The Status Sub-TLV is sent from either the client or router to
indicate the success or failure of a given request indicate the success or failure of a given request
The Status TLV contains the following fields: The Status Sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Code | |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TLV Type - TBD TLV Type - TBD
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are
not used and MUST be set to '0'. not used and MUST be set to '0'.
Length - 1 Length - 1
Termination Code - 0 = Success Termination Code - 0 = Success
Non-zero = Failure. Specific values of a non- Non-zero = Failure. Specific values of a non-
zero termination code depend on the operation zero termination code depend on the operation
requested (e.g. Neighbor Up, Neighbor Down, etc). requested (e.g. Neighbor Up, Neighbor Down, etc).
8. DLEP Messages 7.13 Heartbeat Interval Sub-TLV
The DLEP Packet, being based on [RFC5444], contains the following The Heartbeat Interval Sub-TLV MAY be sent from the client during
fields: Peer Discovery to indicate the desired Heartbeat timeout window.
If included in the Peer Discovery, the router MUST either accept the
timeout interval, or reject the Peer Discovery.
The Heartbeat Interval Sub-TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Version| Flags | TLVs Length | Identification| |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Interval |
| 0x0 | 0x2 | | TLV Type = TBD|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 | Length = 9 | HB Interval | Router ID |
TLV Type - TBD
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are
not used and MUST be set to '0'.
Length - 1
Interval - 0 = Do NOT use heartbeats on this peer-to-peer
session. Non-zero = Interval, in seconds, for
heartbeat messages.
7.14 Heartbeat Threshold Sub-TLV
The Heartbeat Threshold Sub-TLV MAY be sent from the client during
Peer Discovery to indicate the desired number of windows, of time
(Heartbeat Interval) seconds, to wait before either peer declares
the peer-to-peer session lost. In this case, the overall amount of
time before a peer-to-peer session is declared lost is expressed as
(Interval * Threshold), where 'Interval' is the value in the
Heartbeat Interval sub-TLV, documented above. If this sub-TLV is
included by the client in the Peer Discovery, the client MUST also
specify the Heartbeat Interval sub-TLV with a non-zero interval. If
this sub-TLV is received during Peer Discovery, the router MUST
either accept the threshold, or reject the Peer Discovery.
The Heartbeat Threshold Sub-TLV contains the following fields:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID | Client ID | |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Client ID | Message (DLEP |
TLV Type - TBD
TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are
not used and MUST be set to '0'.
Length - 1
Threshold - 0 = Do NOT use heartbeats on this peer-to-peer
session. Non-zero = Number of windows, of
Heartbeat Interval seconds, to wait before
declaring a peer-to-peer session to be lost.
7.15 Link Characteristics ACK Timer Sub-TLV
The Link Characteristic ACK Timer Sub-TLV MAY be sent from the
client during Peer Discovery to indicate the desired number of
seconds the router should wait for a response to a Link
Characteristics Request. If this sub-TLV is received during Peer
Discovery, the router MUST either accept the timeout value, or
reject the Peer Discovery.
The Link Characteristics ACK Timer Sub-TLV contains the
following fields:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| packet can contain zero or more messages) | |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Version - Version of RFC5444 specification on which the packet/
messages/TLVs are constructed.
Flags - 0x2 Only bit 1 (phastlv) is set/used, all other bits are TLV Type - TBD
not used and MUST be set to '0'.
Packet Header TLV Block which contains: TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are
Identification TLV not used and MUST be set to '0'.
Message - the packet may contain zero or more messages. Length - 1
8.1 Message TLVs Interval - 0 = Do NOT use timeouts for Link Characteristics
requests on this peer-to-peer session.
Non-zero = Interval, in seconds, to wait before
considering a Link Characteristics Request has
been lost.
8. DLEP Protocol Messages
DLEP places no additional requirements on the RFC 5444 Packet
formats, or the packet header. DLEP does require that the optional
'msg-seq-num' in the message header exist, and defines a set of
values for the 'tlv-type' field in the RFC 5444 TLV block. Therefore,
a DLEP message, starting from the RFC 5444 Message header, would
appear as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type = |Msg Flg|AddrLen| Message Size |
| DLEP_MESSAGE | 0x1 | 0x0 | |
| (value TBD) | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLV block length (length of |
| | DLEP order + Sub-TLVs) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DLEP Message |TLV Flags=0x10 | Length | Start of DLEP |
| Block value | | | Sub-TLVs... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
8.1 Message Block TLV Values
As mentioned above, all DLEP messages utilize a single RFC 5444
message type, the DLEP_MESSAGE (TBD). DLEP further identifies
protocol messages by using the 'tlv-type' field in the RFC 5444
message TLV block. DLEP defines the following Message-Type-
specific values for the tlv-type field:
TLV TLV TLV TLV
Value Description Value Description
========================================= =========================================
TBD Attached Peer Discovery TBD Attached Peer Discovery
TBD Detached Peer Discovery TBD Detached Peer Discovery
TBD Peer Offer TBD Peer Offer
TBD Peer Update TBD Peer Update
TBD Peer Update ACK TBD Peer Update ACK
TBD Peer Termination TBD Peer Termination
skipping to change at page 17, line 38 skipping to change at page 20, line 5
TBD Neighbor Up ACK TBD Neighbor Up ACK
TBD Neighbor Down TBD Neighbor Down
TBD Neighbor Down ACK TBD Neighbor Down ACK
TBD Neighbor Update TBD Neighbor Update
TBD Neighbor Address Update TBD Neighbor Address Update
TBD Neighbor Address Update ACK TBD Neighbor Address Update ACK
TBD Heartbeat TBD Heartbeat
TBD Link Characteristics Request TBD Link Characteristics Request
TBD Link Characteristics ACK TBD Link Characteristics ACK
In all of the diagrams following, the message layouts begin with the
RFC 5444 message header.
9. Peer Discovery Messages 9. Peer Discovery Messages
There are two different types of Peer Discovery Messages, Attached There are two different types of Peer Discovery Messages, Attached
and Detached. Attached Peer Discovery Messages are sent by the and Detached. Attached Peer Discovery Messages are sent by the
client when it is directly attached to the router (e.g. the client client when it is directly attached to the router (e.g. the client
exists as a card in the chassis, or it is connected via Ethernet with exists as a card in the chassis, or it is connected via Ethernet with
no intervening devices). The Detached Peer Discovery message, on the no intervening devices). The Detached Peer Discovery message, on the
other hand, is sent by a "remote" client -- for example, a client at other hand, is sent by a "remote" client -- for example, a client at
a satellite hub system might use a Detached Discovery Message in a satellite hub system might use a Detached Discovery Message in
order to act as a proxy for remote ground terminals. To explain in order to act as a proxy for remote ground terminals. To explain in
skipping to change at page 18, line 13 skipping to change at page 20, line 35
to a router to begin a new DLEP association. The Peer Offer message to a router to begin a new DLEP association. The Peer Offer message
is required to complete the discovery process. The client MAY is required to complete the discovery process. The client MAY
implement its own retry heuristics in the event it (the client) implement its own retry heuristics in the event it (the client)
determines the Attached Peer Discovery Message has timed out. determines the Attached Peer Discovery Message has timed out.
The Attached Peer Discovery Message contains the following fields: The Attached Peer Discovery Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 |15 + size of opt Peer Type TLV | | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt |
| (value TBD) | | | sub-TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 7 + opt TLVs | | Message Seq Num |TLVs Length =14 + opt sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DLEP Version |TLV Flags=0x10 | Length = 4 | Major Version | | DLEP Attached |TLV Flags=0x10 | Length =11 + | Sub-TLV type= |
| TLV Type = TBD| | | | | Peer Discovery| | opt sub-TLVs | Identification|
| (Value TDB) | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Major Version | Minor Version | Peer Type TLV | |TLV Flags=0x10 |Length = 8 | Router ID |
| | | Type = TBD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 | Length = Len | Peer Type Str | | Router ID | Client ID |
| |of peer string |MaxLen=80 bytes| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP Version | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 4 | Major Version | Minor Version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minor Version |Sub-TLV type= |TLV Flags=0x10 | Length = Len |
| |Peer Type (TBD)| |of peer string |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (Continued on next page) |
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (Continued from previous page) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type Str |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 |
|MaxLen=80 bytes|Heartbeat Int. | | |
| |(TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Heartbeat |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 |
| Interval |HB Thresh. | | |
| (seconds) |(TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Heartbeat |Sub-TLV Type= |TLV FLags=0x10 | Length = 1 |
| Threshold |Link Char. ACK | | |
|(# of windows) |Timer (TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Link Char ACK |
|Timer (sec) |
+-+-+-+-+-+-+-+-+
Attached Peer Discovery Message - TBD Message Type - DLEP_MESSAGE (value TBD)
Message Flags - Set to 0x1 (bit 3, mhasseqnum Message Flags - Set to 0x1 (bit 3, mhasseqnum
bit is set). No other bits are bit is set). No other bits are
used and MUST be set to '0'. used and MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 15 + size of optional Peer Type TLV Message Size - 22 + size of optional sub-TLVs
Message Sequence Number - a 16-bit unsigned integer field Message Sequence Number - a 16-bit unsigned integer field
containing a sequence number containing a sequence number
generated by the message generated by the message
originator. originator.
TLV Block - TLVs Length: 7 + size of OPTIONAL TLV Block - TLVs Length: 14 + size of optional
Peer Type TLV. sub-TLVs.
DLEP Version TLV
Peer Type TLV (OPTIONAL) DLEP Attached Peer Disc. order
Identification TLV (MANDATORY)
Version Sub-TLV (OPTIONAL)
Peer Type Sub-TLV (OPTIONAL)
Heartbeat Int. Sub-TLV (OPTIONAL)
Heartbeat Threshold Sub-TLV (OPT.)
Link Characteristics ACK Timer
Sub-TLV (OPTIONAL)
9.2 Detached Peer Discovery Message 9.2 Detached Peer Discovery Message
The Detached Peer Discovery Message is sent by a detached client The Detached Peer Discovery Message is sent by a detached client
proxy to a router to begin a new DLEP session. The Peer Offer proxy to a router to begin a new DLEP session. The Peer Offer
message is required to complete the discovery process. The client message is required to complete the discovery process. The client
MAY implement its own retry heuristics in the event it (the client) MAY implement its own retry heuristics in the event it (the client)
determines the Detached Peer Discovery Message has timed out. determines the Detached Peer Discovery Message has timed out.
The Detached Peer Discovery Message contains the following fields: The Detached Peer Discovery Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 |15 + size of opt Peer Type TLV | | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt |
| (value TBD) | | | sub-TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 7 + opt TLVs | | Message Seq Num |TLVs Length =14 + opt sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DLEP Version |TLV Flags=0x10 | Length = 4 | Major Version | | DLEP Detached |TLV Flags=0x10 | Length = 11 + | Sub-TLV type= |
| TLV Type = TBD| | | | | Peer Discovery| | opt sub-TLVs | Identification|
| (Value TDB) | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Major Version | Minor Version | Peer Type TLV | |TLV Flags=0x10 |Length = 8 | Router ID |
| | | Type = TBD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 | Length = Len | Peer Type Str | | Router ID | Client ID |
| |of peer string |MaxLen=80 bytes| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP Version | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 4 | Major Version | Minor Version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minor Version |Sub-TLV type= |TLV Flags=0x10 | Length = Len |
| |Peer Type (TBD)| |of peer string |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type Str |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 |
|MaxLen=80 bytes|Heartbeat Int. | | |
| |(TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Heartbeat |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 |
| Interval |HB Thresh. | | |
| (seconds) |(TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Heartbeat |Sub-TLV Type= |TLV FLags=0x10 | Length = 1 |
| Threshold |Link Char. ACK | | |
|(# of windows) |Timer (TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Link Char ACK |
|Timer (sec) |
+-+-+-+-+-+-+-+-+
Detached Peer Discovery Message Type - TBD Message Type - DLEP_MESSAGE (value TBD)
Message Flags - Set to 0x1 (bit 3,
mhasseqnum bit is set).
All other bits are not used
and MUST be set to '0'.
Message Flags - Set to 0x1 (bit 3, Message Address Length - 0x0
mhasseqnum bit is set).
All other bits are not used
and MUST be set to '0'.
Message Address Length - 0x3 Message Size - 22 + size of optional
sub-TLVs
Message Size - 15 + size of optional Peer Message Sequence Number - A 16-bit unsigned integer
Type TLV field containing a sequence
number, generated by the
message originator.
Message Sequence Number - A 16-bit unsigned integer TLV Block - TLVs Length: 14 + size of
field containing a sequence optional sub-TLVs.
number, generated by the
message originator.
TLV Block - TLVs Length: 7 + size of DLEP Detached Peer Discovery order
OPTIONAL Peer Type TLV. Identification sub-TLV (MANDATORY)
DLEP Version TLV Version sub-TLV (OPTIONAL)
Peer Type TLV (optional) Peer Type Sub-TLV (OPTIONAL)
Heartbeat Interval Sub-TLV (OPTIONAL)
Heartbeat Threshold Sub-TLV (OPTIONAL)
Link Char. ACK Timer Sub-TLV(OPTIONAL)
10. Peer Offer Message 10. Peer Offer Message
The Peer Offer Message is sent by a router to a client or client The Peer Offer Message is sent by a router to a client or client
proxy in response to a Peer Discovery Message. The Peer Offer proxy in response to a Peer Discovery Message. The Peer Offer
Message is the response to either of the Peer Discovery messages Message is the response to either of the Peer Discovery messages
(either Attached or Detached), and completes the DLEP session (either Attached or Detached), and completes the DLEP session
establishment. establishment.
The Peer Offer Message contains the following fields: The Peer Offer Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 |15 + size of opt Peer Type TLV | | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt |
| (value TBD) | | | sub-TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 7 + opt TLVs | | Message Seq Num |TLVs Length =14 + opt sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DLEP Version |TLV Flags=0x10 | Length = 4 | Major Version | |DLEP Peer Offer|TLV Flags=0x10 | Length = 11 + | Sub-TLV type= |
| TLV Type = TBD| | | | | (Value TBD) | | opt sub-TLVs | Identification|
| | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Major Version | Minor Version | Peer Type TLV | |TLV Flags=0x10 |Length = 8 | Router ID |
| | | Type = TBD |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 | Length = Len | Peer Type Str |TLV Type = TBD | | (Continued on next page) |
| |of peer string |MaxLen=80 bytes| | 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 5 | Add/Drop Ind. | IPv4 Address | | (Continued from above) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |TLV Type = TBD | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 17 | Add/Drop Ind. | IPv6 Address | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP Version | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 4 | Major Version | Minor Version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minor Version |Peer Type sub- |TLV Flags=0x10 | Length = Len |
| |TLV = TDB | |of peer string |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer Type Str |DLEP IPv4 sub- |TLV Flags=0x10 | Length = 5 |
|MaxLen=80 bytes|TLV (TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Add/Drop Ind. | IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |DLEP IPv6 sub- |TLV Flags=0x10 | Length = 17 |
| |TLV Type = TBD | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Add/Drop Ind. | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address |TLV Type = TBD | |IPv6 Address |Sub-TLV type= |TLV Flags=0x10 | Length = 1 |
| |Heartbeat Int. | | |
| |(TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 | Length = 1 | Code | | Heartbeat |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interval |Heartbeat | | |
| (seconds) |Threshold (TBD)| | |
Peer Offer Message Type - TBD +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Heartbeat |Sub-TLV Type= |TLV FLags=0x10 | Length = 1 |
| Threshold |Link Char. ACK | | |
| (# of windows)|Timer (TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Link Char ACK |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 |
|Timer (sec) |DLEP Status | | |
| |(TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code |
+-+-+-+-+-+-+-+-+
Message Type - DLEP_MESSAGE (Value TBD)
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit Message Flags - Set to 0x1 (bit 3, mhasseqnum bit
is set). All other bits are unused and is set). All other bits are unused and
MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 22 + size of optional sub-TLVs
Message Size - 15 + size of optional Peer Type TLV
Message Sequence Number - A 16-bit unsigned integer field containing Message Sequence Number - A 16-bit unsigned integer field containing
a sequence number, generated by the message a sequence number, generated by the message
originator. originator.
TLV Block - TLV Length: 7 + size of optional Peer Type TLV Block - TLV Length: 14 + size of optional sub-TLVs
TLV. DLEP Peer Offer order
DLEP Version TLV Identification sub-TLV (MANDATORY)
Peer Type TLV (OPTIONAL) DLEP Version sub-TLV (OPTIONAL)
IPv4 Address TLV (OPTIONAL) Peer Type sub-TLV (OPTIONAL)
IPv6 Address TLV (OPTIONAL) IPv4 Address sub-TLV (OPTIONAL)
Status TLV (OPTIONAL) IPv6 Address sub-TLV (OPTIONAL)
Status sub-TLV (OPTIONAL)
Heartbeat Interval Sub-TLV (OPTIONAL)
Heartbeat Threshold Sub-TLV (OPTIONAL)
Link Char. ACK Timer Sub-TLV (OPTIONAL)
11. Peer Update Message 11. Peer Update Message
The Peer Update message is sent by the router to indicate local The Peer Update message is sent by the router to indicate local
Layer 3 address changes. For example, addition of an IPv4 address Layer 3 address changes. For example, addition of an IPv4 address
to the router would prompt a Peer Update message to its attached to the router would prompt a Peer Update message to its attached
DLEP clients. If the modem device is capable of understanding and DLEP clients. If the modem device is capable of understanding and
forwarding this information, the address update would prompt any forwarding this information, the address update would prompt any
remote DLEP clients (DLEP clients that are on the far-end of the remote DLEP clients (DLEP clients that are on the far-end of the
variable link) to issue a "Neighbor Update" message to their local variable link) to issue a "Neighbor Update" message to their local
skipping to change at page 22, line 10 skipping to change at page 26, line 10
heuristics to retransmit Peer Update messages. Sending of Peer heuristics to retransmit Peer Update messages. Sending of Peer
Update Messages SHOULD cease when a router implementation Update Messages SHOULD cease when a router implementation
determines that a partner modem device does NOT support Layer 3 determines that a partner modem device does NOT support Layer 3
address tracking. address tracking.
The Peer Update Message contains the following fields: The Peer Update Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 8 + opt TLVs | | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt |
| (value TBD) | | | sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = length of opt | | Message Seq Num |TLVs Length =14 + opt sub-TLVs |
| | TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 5 | Add/Drop Ind. | | DLEP Peer |TLV Flags=0x10 | Length = 11 + | Sub-TLV type= |
| Update | | opt sub-TLVs | Identification|
| (Value TDB) | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address | |TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 17 | Add/Drop Ind. | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP IPv4 | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 5 | Add/Drop Ind. | IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address | Sub-TLV type= |TLV Flags=0x10 |
| | DLEP IPv6 | |
| | sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 17 | Add/Drop Ind. | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Peer Update Message Type - TBD Message Type - DLEP_MESSAGE (Value TBD)
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit Message Flags - Set to 0x1 (bit 3, mhasseqnum bit
is set). All other bits are unused and is set). All other bits are unused and
MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 8 + optional TLVs Message Size - 22 + optional Sub-TLVs
Message Sequence Number - A 16-bit unsigned integer field containing Message Sequence Number - A 16-bit unsigned integer field containing
a sequence number generated by the message a sequence number generated by the message
originator. originator.
TLV Block - TLV Length: length of optional TLVs. TLV Block - TLV Length: 14 + length of optional
IPv4 Address TLV (OPTIONAL) sub-TLVs.
IPv6 Address TLV (OPTIONAL) DLEP Peer Update order
Identification sub-TLV (MANDATORY)
IPv4 Address Sub-TLV (OPTIONAL)
IPv6 Address Sub-TLV (OPTIONAL)
12. Peer Update ACK Message 12. Peer Update ACK Message
The client sends the Peer Update ACK Message to indicate whether a The client sends the Peer Update ACK Message to indicate whether a
Peer Update Message was successfully processed. Peer Update Message was successfully processed.
The Peer Update ACK message contains the following fields: The Peer Update ACK message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 12 | | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt |
| (value TBD) | | | sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 4 | | Message Seq Num |TLVs Length =14 + opt sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Code | | DLEP Peer |TLV Flags=0x10 | Length = 11 + | Sub-TLV type= |
| Update ACK | | opt sub-TLVs | Identification|
| (Value TDB) | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP Status | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 1 | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Peer Update ACK Message Type - DLEP_MESSAGE (Value TBD)
Message Type - TBD
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit Message Flags - Set to 0x1 (bit 3, mhasseqnum bit
is set). All other bits are unused and is set). All other bits are unused and
MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 12 Message Size - 22 + size of optional sub-TLVs.
Message Sequence Number - A 16-bit unsigned integer field containing Message Sequence Number - A 16-bit unsigned integer field containing
the sequence number from the Neighbor Up the sequence number from the Neighbor Up
Message that is being acknowledged. Message that is being acknowledged.
TLV Block - TLV Length: 4 TLV Block - TLV Length: 14 + optional sub-TLVs
Status TLV DLEP Peer Update ACK order
Identification Sub-TLV (MANDATORY)
Status Sub-TLV (OPTIONAL)
13. Peer Termination Message 13. Peer Termination Message
The Peer Termination Message is sent by either the client or the The Peer Termination Message is sent by either the client or the
router when a session needs to be terminated. Transmission of a router when a session needs to be terminated. Transmission of a
Peer Termination ACK message is required to confirm the Peer Termination ACK message is required to confirm the
termination process. The sender of the Peer Termination message termination process. The sender of the Peer Termination message
is free to define its heuristics in event of a timeout. The is free to define its heuristics in event of a timeout. The
receiver of a Peer Termination Message MUST terminate all receiver of a Peer Termination Message MUST terminate all
neighbor relationships and release associated resources. No neighbor relationships and release associated resources. No
Neighbor Down messages are sent. Neighbor Down messages are sent.
The Peer Termination Message contains the following fields: The Peer Termination Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 12 | | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt |
| (value TBD) | | | sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 4 | | Message Seq Num |TLVs Length =14 + opt sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TDB |TLV Flags=0x10 | Length = 1 | Code | | DLEP Peer |TLV Flags=0x10 | Length = 11 + | Sub-TLV type= |
| Termination | | opt sub-TLVs | Identification|
| (Value TDB) | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP Status | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 1 | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Peer Termination Message Type - TBD Message Type - DLEP_MESSAGE (Value TBD)
Message Flags - Set to 0x1 (bit 3, mhasseqnum Message Flags - Set to 0x1 (bit 3, mhasseqnum
bit is set). All other bits are bit is set). All other bits are
unused and MUST be set to '0'. unused and MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 12 Message Size - 22 + size of optional sub-TLVs.
Message Sequence Number - A 16-bit unsigned integer field Message Sequence Number - A 16-bit unsigned integer field
containing a sequence number containing a sequence number
generated by the message originator. generated by the message originator.
TLV Block - TLV Length = 4. TLV Block - TLV Length = 14 + optional sub-TLVs
Status TLV DLEP Peer Termination order
Identification Sub-TLV (MANDATORY)
Status Sub-TLV (OPTIONAL)
14. Peer Termination ACK Message 14. Peer Termination ACK Message
The Peer Termination Message ACK is sent by either the client or The Peer Termination Message ACK is sent by either the client or
the router when a session needs to be terminated. the router when a session needs to be terminated.
The Peer Termination ACK Message contains the following fields: The Peer Termination ACK Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 12 | | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt |
| (value TBD) | | | sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 4 | | Message Seq Num |TLVs Length =14 + opt sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TDB |TLV Flags=0x10 | Length = 1 | Code | | DLEP Peer Term|TLV Flags=0x10 | Length = 11 + | Sub-TLV type= |
| ACK | | opt sub-TLVs | Identification|
| (Value TBD) | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP Status | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 1 | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Type - DLEP_MESSAGE (Value TBD)
Peer Termination ACK
Message Type - TBD
Message Flags - Set to 0x1 (bit 3, mhasseqnum Message Flags - Set to 0x1 (bit 3, mhasseqnum
bit is set). All other bits are bit is set). All other bits are
unused and MUST be set to '0'. unused and MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 12 Message Size - 22 + optional sub-TLVs.
Message Sequence Number - A 16-bit unsigned integer field Message Sequence Number - A 16-bit unsigned integer field
containing the sequence number in containing the sequence number in
the corresponding Peer Termination the corresponding Peer Termination
Message being acknowledged. Message being acknowledged.
TLV Block - TLV Length = 4. TLV Block - TLV Length = 14 + optional Sub-TLVs
Status TLV DLEP Peer Termination ACK order
Identification Sub-TLV (MANDATORY)
Status Sub-TLV (OPTIONAL)
15. Neighbor Up Message 15. Neighbor Up Message
The client sends the Neighbor Up message to report that a new The client sends the Neighbor Up message to report that a new
potential routing neighbor has been detected. A Neighbor Up potential routing neighbor has been detected. A Neighbor Up
ACK Message is required to confirm a received Neighbor Up. ACK Message is required to confirm a received Neighbor Up.
The sender of the Neighbor Up Message is free to define its The sender of the Neighbor Up Message is free to define its
retry heuristics in event of a timeout. retry heuristics in event of a timeout.
The Neighbor Up Message contains the following fields: The Neighbor Up Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 17 + opt TLVs | | DLEP_MESSAGE | 0x1 | 0x0 | 31 + size of opt |
| (value TBD) | | | sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 9 + opt TLVs | | Message Seq Num |TLVs Length =23 + opt sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | | DLEP Neighbor |TLV Flags=0x10 | Length =20 + | Sub-TLV type= |
| Up (TBD) | | opt sub-TLVs | Identification|
| | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | |TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |TLV Type =TBD |TLV Flags=0x10 |Length = 5 | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Add/Drop Ind. | IPv4 Address | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP MAC | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IPv4 Address |TLV Type =TBD |TLV Flags=0x10 |Length = 17 | |Length = 6 | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Add/Drop Ind. | IPv6 Address | | MAC Address |Sub-TLV type= |
| |DLEP IPv4 (TBD)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 5 | Add/Drop Ind. | IPv4 Address |
| | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |Sub-TLV type= |
| |DLEP IPv6 (TBD)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (Continued on next page) |
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (Continued from above) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 17 | Add/Drop Ind. | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IPv6 Address |TLV Type = TBD |TLV Flags=0x10 |Length = 8 | | IPv6 Address |Sub-TLV type= |
| |DLEP MDR (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MDR (bps) | |TLV Flags=0x10 |Length = 8 | MDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MDR (bps) | | MDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 |Length = 8 | CDR (bps) | | MDR (bps) |sub-TLV Type = |TLV Flags=0x10 |
| |DLEP CDR (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDR (bps) | |Length = 8 | CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDR (bps) |TLV Type = TBD | | CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 2 | Latency (ms) | | CDR (bps) |sub-TLV Type = |TLV Flags=0x10 | Length = 2 |
| |Latency (TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 | Length = 1 | Resources | Latency (ms) |sub-TLV Type = |TLV Flags=0x10 |
| |Resources(TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 | Length = 1 | RLQ | | Length = 1 | Resources |sub-TLV Type = |TLV Flags=0x10 |
| | |DLEP RLQ (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Neighbor Up Message Type - TBD | Length = 1 | RLQ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Type - DLEP_MESSAGE (Value TBD)
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit Message Flags - Set to 0x1 (bit 3, mhasseqnum bit
is set). All other bits are unused and is set). All other bits are unused and
MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 17 + optional TLVs Message Size - 31 + optional Sub-TLVs
Message Sequence Number - A 16-bit unsigned integer field containing Message Sequence Number - A 16-bit unsigned integer field containing
a sequence number generated by the message a sequence number generated by the message
originator. originator.
TLV Block - TLV Length: 9 + optional TLVs. TLV Block - TLV Length: 23 + optional Sub-TLVs.
MAC Address TLV (MANDATORY) DLEP Neighbor Up order
IPv4 Address TLV (OPTIONAL) Identification Sub-TLV (MANDATORY)
IPv6 Address TLV (OPTIONAL) MAC Address Sub-TLV (MANDATORY)
Maximum Data Rate TLV (OPTIONAL) IPv4 Address Sub-TLV (OPTIONAL)
Current Data Rate TLV (OPTIONAL) IPv6 Address Sub-TLV (OPTIONAL)
Latency TLV (OPTIONAL) Maximum Data Rate Sub-TLV (OPTIONAL)
Resources TLV (OPTIONAL) Current Data Rate Sub-TLV (OPTIONAL)
Relative Link Factor TLV (OPTIONAL) Latency Sub-TLV (OPTIONAL)
Resources Sub-TLV (OPTIONAL)
Relative Link Factor Sub-TLV (OPTIONAL)
16. Neighbor Up ACK Message 16. Neighbor Up ACK Message
The router sends the Neighbor Up ACK Message to indicate whether a The router sends the Neighbor Up ACK Message to indicate whether a
Neighbor Up Message was successfully processed. Neighbor Up Message was successfully processed.
The Neighbor Up ACK message contains the following fields: The Neighbor Up ACK message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 21 | | DLEP_MESSAGE | 0x1 | 0x0 | 35 |
| (value TBD) | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 13 | | Message Seq Num |TLVs Length = 27 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | | DLEP Neighbor |TLV Flags=0x10 | Length = 24 | Sub-TLV type= |
| Up ACK (TBD) | | | Identification|
| | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | |TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
+-+-+-+-+-+-+-+-+ | |DLEP MAC | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 6 | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |Sub-TLV type= |
| |DLEP Status
| |(TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 | Length = 1 | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Neighbor Up ACK Message Type - DLEP_MESSAGE (Value TBD)
Message Type - TBD
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit Message Flags - Set to 0x1 (bit 3, mhasseqnum bit
is set). All other bits are unused and is set). All other bits are unused and
MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 21 Message Size - 35
Message Sequence Number - A 16-bit unsigned integer field containing Message Sequence Number - A 16-bit unsigned integer field containing
the sequence number from the Neighbor Down the sequence number from the Neighbor Down
Message that is being acknowledged. Message that is being acknowledged.
TLV Block - TLV Length: 13 TLV Block - TLV Length: 27
MAC Address TLV (MANDATORY)
Status TLV (MANDATORY) DLEP Neighbor Up ACK order
Identification Sub-TLV (MANDATORY)
MAC Address Sub-TLV (MANDATORY)
Status Sub-TLV (MANDATORY)
17. Neighbor Down Message 17. Neighbor Down Message
The client sends the Neighbor Down message to report when a neighbor The client sends the Neighbor Down message to report when a neighbor
is no longer reachable from the client. The Neighbor Down message is no longer reachable from the client. The Neighbor Down message
MUST contain a MAC Address TLV. Any other TLVs present MAY be MUST contain a MAC Address TLV. Any other TLVs present MAY be
ignored. A Neighbor Down ACK Message is required to confirm the ignored. A Neighbor Down ACK Message is required to confirm the
process. The sender of the Neighbor Down message is free to define process. The sender of the Neighbor Down message is free to define
its retry heuristics in event of a timeout. its retry heuristics in event of a timeout.
The Neighbor Down Message contains the following fields: The Neighbor Down Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 17 + optional TLVs | | DLEP_MESSAGE | 0x1 | 0x0 | 31 + optional |
| (value TBD) | | | sub-TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 9 + optional | | Message Seq Num | TLVs Length = 23 + optional |
| | TLVs | | | Sub-TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | | TLV Type = |TLV Flags=0x10 | Length = 20 + | Sub-TLV type= |
| DLEP Neighbor | | optional Sub- | Identification|
| Down (TBD) | | TLV | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | |TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
+-+-+-+-+-+-+-+-+ | |DLEP MAC | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (Continued on next page) |
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (Continued from above) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 6 | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |Sub-TLV type= |
| |DLEP Status
| |(TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 | Length = 1 | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Neighbor Down Message Type - TBD Message Type - DLEP_MESSAGE (Value TBD)
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit Message Flags - Set to 0x1 (bit 3, mhasseqnum bit
is set). All other bits are unused and is set). All other bits are unused and
MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 17 + optional TLVs
Message Size - 31 + optional TLVs
Message Sequence Number - A 16-bit unsigned integer field Message Sequence Number - A 16-bit unsigned integer field
containing a sequence number generated containing a sequence number generated
by the message originator. by the message originator.
TLV Block - TLV Length: 9 + optional TLVs TLV Block - TLV Length: 23 + optional Sub-TLVs
MAC Address TLV (MANDATORY)
Status TLV (OPTIONAL) DLEP Neighbor Down order
Identification Sub-TLV (MANDATORY)
MAC Address Sub-TLV (MANDATORY)
Status Sub-TLV (OPTIONAL)
18. Neighbor Down ACK Message 18. Neighbor Down ACK Message
The router sends the Neighbor Down ACK Message to indicate whether The router sends the Neighbor Down ACK Message to indicate whether
a Neighbor Down Message was successfully processed. a Neighbor Down Message was successfully processed.
The Neighbor Down ACK message contains the following fields: The Neighbor Down ACK message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 21 | | DLEP_MESSAGE | 0x1 | 0x0 | 35 |
| (value TBD) | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 13 | | Message Seq Num |TLVs Length = 27 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | | DLEP Neighbor |TLV Flags=0x10 | Length = 24 | Sub-TLV type= |
| Down ACK (TBD)| | | Identification|
| | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | |TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
+-+-+-+-+-+-+-+-+ | |DLEP MAC | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 6 | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |Sub-TLV type= |
| |DLEP Status
| |(TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 | Length = 1 | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Neighbor Down ACK Message Type - DLEP_MESSAGE (Value TBD)
Message Type - TBD
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit Message Flags - Set to 0x1 (bit 3, mhasseqnum bit
is set). All other bits are unused and is set). All other bits are unused and
MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 21 Message Size - 35
Message Sequence Number - A 16-bit unsigned integer field containing Message Sequence Number - A 16-bit unsigned integer field containing
the sequence number from the Neighbor Down the sequence number from the Neighbor Down
Message that is being acknowledged. Message that is being acknowledged.
TLV Block - TLV Length: 13 TLV Block - TLV Length: 27
MAC Address TLV (MANDATORY)
Status TLV (MANDATORY) DLEP Neighbor Down ACK order
Identification Sub-TLV (MANDATORY)
MAC Address Sub-TLV (MANDATORY)
Status Sub-TLV (MANDATORY)
19. Neighbor Update Message 19. Neighbor Update Message
The client sends the Neighbor Update message when a change in link The client sends the Neighbor Update message when a change in link
metric parameters is detected for a routing neighbor. metric parameters is detected for a routing neighbor.
The Neighbor Update Message contains the following fields: The Neighbor Update Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 17 + opt TLVs | | DLEP_MESSAGE | 0x1 | 0x0 | 31 + optional |
| (value TBD) | | | sub-TLV |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 9 + opt TLVs | | Message Seq Num | TLVs Length = 23 + optional |
| | Sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | |TLV Type = |TLV Flags=0x10 |Length = 20 + |Sub-TLV type = |
|DLEP Neighbor | |optional Sub- |Identification |
|Update (TBD) | |TLVs |Sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | |TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |TLV Type = TBD |TLV Flags=0x10 |Length = 8 | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MDR (bps) | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP MAC | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 6 | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |Sub-TLV type= |
| |DLEP MDR (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 8 | MDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MDR (bps) | | MDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 |Length = 8 | CDR (bps) | | MDR (bps) |Sub-TLV Type = |TLV Flags=0x10 |
| |DLEP CDR (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 8 | CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDR (bps) | | CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDR (bps) |TLV Type = TBD | | CDR (bps) |Sub-TLV Type = |TLV Flags=0x10 | Length = 2 |
| |DLEP Latency | | |
| |(TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 2 | Latency (ms) | | Latency (ms) |Sub-TLV Type= |TLV Flags=0x10 |
| |DLEP Resources | |
| |(TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 | Length = 1 | Resources | | (Continued on next page) |
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 | Length = 1 | RLQ | | (Continued from above) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 1 | Resources |Sub-TLV Type= |TLV FLags=0x10 |
| | |DLEP RLQ (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 1 | RLQ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Neighbor Update Message Type - TBD Message Type - DLEP_MESSAGE (Value TBD)
Message Flags - Set to 0x1 (bit 3, mhasseqnum Message Flags - Set to 0x1 (bit 3, mhasseqnum
bit is set). All other bits are bit is set). All other bits are
unused and MUST be set to '0'. unused and MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 17 + optional TLVs Message Size - 31 + optional TLVs
Message Sequence Number - A 16-bit unsigned integer field Message Sequence Number - A 16-bit unsigned integer field
containing a sequence number, containing a sequence number,
generated by the message originator. generated by the message originator.
TLV Block - TLVs Length - 9 + optional TLVs. TLV Block - TLVs Length - 23 + optional Sub-TLVs.
MAC Address TLV (MANDATORY)
Maximum Data Rate TLV (OPTIONAL) DLEP Neighbor Update order
Current Data Rate TLV (OPTIONAL) Identification Sub-TLV (MANDATORY)
Latency TLV (OPTIONAL) MAC Address Sub-TLV (MANDATORY)
Resources TLV (OPTIONAL) Maximum Data Rate Sub-TLV (OPTIONAL)
Relative Link Quality TLV (OPTIONAL) Current Data Rate Sub-TLV (OPTIONAL)
Latency Sub-TLV (OPTIONAL)
Resources Sub-TLV (OPTIONAL)
Relative Link Quality Sub-TLV
(OPTIONAL)
20. Neighbor Address Update Message 20. Neighbor Address Update Message
The client sends the Neighbor Address Update message when a change The client sends the Neighbor Address Update message when a change
in Layer 3 addressing is detected for a routing neighbor. in Layer 3 addressing is detected for a routing neighbor.
The Neighbor Address Update Message contains the following fields: The Neighbor Address Update Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 17 + opt TLVs | | DLEP_MESSAGE | 0x1 | 0x0 | 31 + size of opt |
| (value TBD) | | | sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 9 + opt TLVs | | Message Seq Num |TLVs Length =23 + opt sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | | (Continued on next page) |
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | | (Continued from above) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |TLV Type =TBD |TLV Flags=0x10 |Length = 5 | | DLEP Neighbor |TLV Flags=0x10 | Length =20 + | Sub-TLV type= |
| Address Update| | opt sub-TLVs | Identification|
|(TBD) | | | Sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Add/Drop Ind. | IPv4 Address | |TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IPv4 Address |TLV Type =TBD |TLV Flags=0x10 |Length = 17 | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Add/Drop Ind. | IPv6 Address | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP MAC | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 6 | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |Sub-TLV type= |
| |DLEP IPv4 (TBD)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 5 | Add/Drop Ind. | IPv4 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address |Sub-TLV type= |
| |DLEP IPv6 (TBD)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 17 | Add/Drop Ind. | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address | | IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Neighbor Address Update Message Type - DLEP_MESSAGE (Value TBD)
Message Type - TBD
Message Flags - Set to 0x1 (bit 3, mhasseqnum Message Flags - Set to 0x1 (bit 3, mhasseqnum bit is
bit is set). All other bits are set). All other bits are unused and
unused and MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 17 + optional TLVs
Message Size - 31 + optional TLVs
Message Sequence Number - A 16-bit unsigned integer field Message Sequence Number - A 16-bit unsigned integer field
containing a sequence number, containing a sequence number,
generated by the message originator. generated by the message originator.
TLV Block - TLVs Length - 9 + optional TLVs. TLV Block - TLVs Length - 23 + optional Sub-TLVs.
MAC Address TLV (MANDATORY) DLEP Neighbor Address Update order
IPv4 Address TLV (OPTIONAL) Identification Sub-TLV (MANDATORY)
IPv6 Address TLV (OPTIONAL) MAC Address Sub-TLV (MANDATORY)
IPv4 Address Sub-TLV (OPTIONAL)
IPv6 Address Sub-TLV (OPTIONAL)
21. Neighbor Address Update ACK Message 21. Neighbor Address Update ACK Message
The router sends the Neighbor Address Update ACK Message to The router sends the Neighbor Address Update ACK Message to
indicate whether a Neighbor Address Update Message was indicate whether a Neighbor Address Update Message was
successfully processed. successfully processed.
The Neighbor Address Update ACK message contains the following The Neighbor Address Update ACK message contains the following
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | 21 | | DLEP_MESSAGE | 0x1 | 0x0 | 35 |
| (value TBD) | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 13 | | Message Seq Num |TLVs Length = 27 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | | DLEP Neighbor |TLV Flags=0x10 | Length = 24 | Sub-TLV type= |
| Address Update| | | Identification|
| ACK (TBD) | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | |TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
+-+-+-+-+-+-+-+-+ | |DLEP MAC | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 6 | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |Sub-TLV type= |
| |DLEP Status
| |(TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 | Length = 1 | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Neighbor Address Update Message Type - DLEP_MESSAGE (Value TBD)
ACK Message Type - TBD
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit Message Flags - Set to 0x1 (bit 3, mhasseqnum bit
is set). All other bits are unused and is set). All other bits are unused and
MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 35
Message Size - 21
Message Sequence Number - A 16-bit unsigned integer field containing Message Sequence Number - A 16-bit unsigned integer field containing
the sequence number from the Neighbor Down the sequence number from the Neighbor Down
Message that is being acknowledged. Message that is being acknowledged.
TLV Block - TLV Length: 13 TLV Block - TLV Length: 27
MAC Address TLV (MANDATORY)
Status TLV (MANDATORY) DLEP Neighbor Address Update ACK order
Identification Sub-TLV (MANDATORY)
MAC Address Sub-TLV (MANDATORY)
Status Sub-TLV (MANDATORY)
22. Heartbeat Message 22. Heartbeat Message
A Heartbeat Message is sent by a peer every N seconds, where N is A Heartbeat Message is sent by a peer every N seconds, where N is
defined in the "Heartbeat Interval" field of the discovery message. defined in the "Heartbeat Interval" field of the discovery message.
The message is used by peers to detect when a DLEP session partner The message is used by peers to detect when a DLEP session partner
is no longer communicating. Peers SHOULD allow some integral number is no longer communicating. Peers SHOULD allow some integral number
of heartbeat intervals (default 4) to expire with no traffic on the of heartbeat intervals (default 4) to expire with no traffic on the
session before initiating DLEP session termination procedures. session before initiating DLEP session termination procedures.
The Heartbeat Message contains the following fields: The Heartbeat Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size = 8 | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | | | DLEP_MESSAGE | 0x1 | 0x0 | 22 |
| (value TBD) | | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 0 | | Message Seq Num |TLVs Length = 14 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DLEP Heartbeat|TLV Flags=0x10 | Length = 11 | Sub-TLV type= |
| (TBD) | | | Identification|
| | | | sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Type - TBD Message Type - DLEP_MESSAGE (Value TBD)
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit is Message Flags - Set to 0x1 (bit 3, mhasseqnum bit is
set). All other bits are unused and SHOULD set). All other bits are unused and SHOULD
be set to '0'. be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 8
Message Size - 22
Message Sequence Number - A 16-bit unsigned integer field containing Message Sequence Number - A 16-bit unsigned integer field containing
a sequence number generated by the message a sequence number generated by the message
originator. originator.
TLV Block - TLV Length = 0
TLV Block - TLV Length = 14
DLEP Heartbeat order
Identification Sub-TLV (MANDATORY)
23. Link Characteristics Request Message 23. Link Characteristics Request Message
The Link Characteristics Request Message is sent by the router to The Link Characteristics Request Message is sent by the router to
the modem device when the router detects that a different set of the modem device when the router detects that a different set of
transmission characteristics is necessary (or desired) for the transmission characteristics is necessary (or desired) for the
type of traffic that is flowing on the link. The request contains type of traffic that is flowing on the link. The request contains
either a Current Data Rate (CDR) TLV to request a different either a Current Data Rate (CDR) TLV to request a different
amount of bandwidth than what is currently allocated, a Latency amount of bandwidth than what is currently allocated, a Latency
TLV to request that traffic delay on the link not exceed the TLV to request that traffic delay on the link not exceed the
skipping to change at page 34, line 12 skipping to change at page 41, line 35
Link Characteristics Request with ONLY the MAC Address TLV is a Link Characteristics Request with ONLY the MAC Address TLV is a
mechanism a peer MAY use to request metrics (via the Link mechanism a peer MAY use to request metrics (via the Link
Characteristics ACK) from its partner. Characteristics ACK) from its partner.
The Link Characteristics Request Message contains the following The Link Characteristics Request Message contains the following
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size = 8 + Length | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | of optional TLVs | | DLEP_MESSAGE | 0x1 | 0x0 | 31 + size of opt |
| (value TBD) | | | sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = | | Message Seq Num |TLVs Length =23 + opt sub-TLVs |
| | 9 + Optional TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | | DLEP Link Char|TLV Flags=0x10 | Length =20 + | Sub-TLV type= |
| Request (TBD) | | opt sub-TLVs | Identification|
| | | | Sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | |TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |TLV Type =TBD |TLV Flags=0x10 |Length = 8 | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDR (bps) | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP MAC | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 6 | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (Continued on next page) |
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (Continued from above) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |Sub-TLV type= |
| |DLEP CDR (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 8 | CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDR (bps) | | CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 |Length = 2 | Latency (ms) | | CDR (bps) |Sub-TLV Type= |TLV Flags=0x10 |
| |Latency (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Latency (ms) | |Length = 2 | Latency (ms) |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Type - TBD Message Type - DLEP_MESSAGE (Value TBD)
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit Message Flags - Set to 0x1 (bit 3, mhasseqnum bit
is set). All other bits are unused and is set). All other bits are unused and
MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 8 + length of optional (Current Data Message Size - 31 + length of optional (Current Data
Rate and/or Latency) TLVs Rate and/or Latency) Sub-TLVs
Message Sequence Number - A 16-bit unsigned integer field containing Message Sequence Number - A 16-bit unsigned integer field containing
a sequence number generated by the message a sequence number generated by the message
originator. originator.
TLV Block - TLVs Length TLV Block - Length: 23 + optional Sub-TLVs
MAC Address TLV (MANDATORY) DLEP Link Characteristics Request order
Identification Sub-TLV (MANDATORY)
MAC Address Sub-TLV (MANDATORY)
Current Data Rate Sub-TLV - if present,
this value represents the requested data
rate in bits per second (bps). (OPTIONAL)
Current Data Rate TLV - if present, this
value represents the requested data rate
in bits per second (bps). (OPTIONAL)
Latency TLV - if present, this value Latency TLV - if present, this value
represents the maximum latency, in represents the maximum latency, in
milliseconds, desired on the link. milliseconds, desired on the link.
(OPTIONAL) (OPTIONAL)
24. Link Characteristics ACK Message 24. Link Characteristics ACK Message
The Link Characteristics ACK Message is sent by the client to the The Link Characteristics ACK Message is sent by the client to the
router letting the router know the success (or failure) of the router letting the router know the success (or failure) of the
requested change in link characteristics. The Link Characteristics requested change in link characteristics. The Link Characteristics
ACK message SHOULD contain a complete set of metric TLVs. It MUST ACK message SHOULD contain a complete set of metric TLVs. It MUST
contain the same TLV types as the request. The values in the contain the same TLV types as the request. The values in the
metric TLVs in the Link Characteristics ACK message MUST reflect metric TLVs in the Link Characteristics ACK message MUST reflect
the link characteristics after the request has been processed. the link characteristics after the request has been processed.
The Link Characteristics ACK Message contains the following fields: The Link Characteristics ACK Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Msg Type |Msg Flg|AddrLen| Message Size = 8 + Length | | Msg Type = |Msg Flg|AddrLen| Message Size |
| = TBD | 0x1 | 0x3 | of additional TLVs | | DLEP_MESSAGE | 0x1 | 0x0 | 31 + size of opt |
| (value TBD) | | | sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Seq Num | TLVs Length = 9 + optional | | Message Seq Num |TLVs Length =23 + opt sub-TLVs |
| | TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | | DLEP Link Char|TLV Flags=0x10 | Length =20 + | Sub-TLV type= |
| ACK (TBD) | | opt sub-TLVs | Identification|
| | | | Sub-TLV (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address | |TLV Flags=0x10 |Length = 8 | Router ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |TLV Type =TBD |TLV Flags=0x10 |Length = 8 | | Router ID | Client ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MDR (bps) | | Client ID |Sub-TLV type= |TLV Flags=0x10 |
| |DLEP MAC | |
| |sub-TLV (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Length = 6 | MAC Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address |Sub-TLV type= |
| |DLEP MDR (TBD) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 8 | MDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MDR (bps) | | MDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 |Length = 8 | CDR (bps) | | MDR (bps) |Sub-TLV Type= |TLV Flags=0x10 |
| |DLEP CDR (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDR (bps) | |Length = 8 | CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CDR (bps) |TLV Type = TBD | | CDR (bps) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Flags=0x10 |Length = 2 | Latency (ms) | | CDR (bps) |Sub-TLV Type = |TLV Flags=0x10 | Length = 2 |
| |Latency (TBD) | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 | Length = 1 | Resources | | Latency (ms) |Sub-TLV Type= |TLV Flags=0x10 |
| |Resources (TBD)| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|TLV Type = TBD |TLV Flags=0x10 | Length = 1 | RLQ | | Length = 1 | Resources |Sub-TLV Type= |TLV Flags=0x10 |
| | |RLQ (TBD) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length = 1 | RLQ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Message Type - DLEP_MESSAGE (Value TBD)
Message Type - TBD
Message Flags - Set to 0x1 (bit 3, mhasseqnum bit Message Flags - Set to 0x1 (bit 3, mhasseqnum bit
is set). All other bits are unused and is set). All other bits are unused and
MUST be set to '0'. MUST be set to '0'.
Message Address Length - 0x3 Message Address Length - 0x0
Message Size - 8 + length of optional (Current Data Message Size - 31 + length of optional (Current Data
Rate and/or Latency) TLVs Rate and/or Latency) TLVs
Message Sequence Number - A 16-bit unsigned integer field containing Message Sequence Number - A 16-bit unsigned integer field containing
the sequence number that appeared on the the sequence number that appeared on the
corresponding Link Characteristics Request corresponding Link Characteristics Request
message. message.
TLV Block - TLVs Length = 9 + Optional TLVs TLV Block - TLVs Length = 23 + Optional TLVs
MAC Address TLV (MANDATORY)
Maximum Data Rate TLV (OPTIONAL) DLEP Link Characteristics ACK order
Identification Sub-TLV (MANDATORY)
MAC Address Sub-TLV (MANDATORY)
Maximum Data Rate Sub-TLV (OPTIONAL)
Current Data Rate TLV - if present, this Current Data Rate Sub-TLV - if present,
value represents the NEW (or unchanged, this value represents the NEW (or
if the request is denied) Current Data unchanged, if the request is denied)
Rate in bits per second (bps). (OPTIONAL) Current Data Rate in bits per second (bps).
(OPTIONAL)
Latency TLV - if present, this value Latency Sub-TLV - if present, this value
represents the NEW maximum latency (or represents the NEW maximum latency (or
unchanged, if the request is denied), unchanged, if the request is denied),
expressed in milliseconds, on the link. expressed in milliseconds, on the link.
(OPTIONAL) (OPTIONAL)
Resources TLV (OPTIONAL) Resources Sub-TLV (OPTIONAL)
Relative Link Quality TLV (OPTIONAL) Relative Link Quality Sub-TLV (OPTIONAL)
25. Security Considerations 25. Security Considerations
The protocol does not contain any mechanisms for security (e.g. The protocol does not contain any mechanisms for security (e.g.
authentication or encryption). The protocol assumes that any authentication or encryption). The protocol assumes that any
security would be implemented in the underlying transport (for security would be implemented in the underlying transport (for
example, by use of DTLS or some other mechanism), and is example, by use of DTLS or some other mechanism), and is
therefore outside the scope of this document. therefore outside the scope of this document.
26. IANA Considerations 26. IANA Considerations
This section specifies requests to IANA. This section specifies requests to IANA.
26.1 TLV Registrations 26.1 TLV Registrations
This specification defines: This specification defines:
o Twelve TLV types which must be allocated from the 0-223 range o One TLV types which must be allocated from the 0-223 range
of the "Assigned Packet TLV Types" repository of [RFC5444]. of the "Assigned Message TLV Types" repository of [RFC5444].
o Seventeen Message types which must be allocated from the 0-127 o A new repository for DLEP orders, with seventeen values currently
range of the "Assigning Message TLV Types" repository of assigned.
[RFC5444].
o A new repository for DLEP Sub-TLV assignments with fifteen values
currently assigned.
26.2 Expert Review: Evaluation Guidelines 26.2 Expert Review: Evaluation Guidelines
For the registries for TLV type extensions where an Expert Review is For the registries for TLV type extensions where an Expert Review is
required, the designated expert SHOULD take the same general required, the designated expert SHOULD take the same general
recommendations into consideration as are specified by [RFC5444]. recommendations into consideration as are specified by [RFC5444].
26.3 Packet TLV Type Registrations 26.3 Message TLV Type Registration
The Packet TLVs specified below must be allocated from the "Packet The Message TLV specified below must be allocated from the "Message
TLV Types" namespace of [RFC5444]. TLV Types" namespace of [RFC5444].
o Identification TLV o DLEP_MESSAGE
o DLEP Version TLV
o Peer Type TLV
o MAC Address TLV
o IPv4 Address TLV
o IPv6 Address TLV
o Maximum Data Rate TLV
o Current Data Rate TLV
o Latency TLV
o Resources TLV
o Relative Link Quality TLV
o Status TLV
26.4 Message TLV Type Registrations 26.4 DLEP Order Registration
The Message TLVs specified below must be allocated from the A new repository must be created with the values of the DLEP orders.
"Message TLV Types" namespace of [RFC5444]. Valid orders are:
o Attached Peer Discovery Message o Attached Peer Discovery Message
o Detached Peer Discovery Message o Detached Peer Discovery Message
o Peer Offer Message o Peer Offer Message
o Peer Update Message o Peer Update Message
o Peer Update ACK Message o Peer Update ACK Message
o Peer Termination Message o Peer Termination Message
o Peer Termination ACK Message o Peer Termination ACK Message
o Neighbor Up Message o Neighbor Up Message
o Neighbor Up ACK Message o Neighbor Up ACK Message
o Neighbor Down Message o Neighbor Down Message
o Neighbor Down ACK Message o Neighbor Down ACK Message
o Neighbor Update Message o Neighbor Update Message
o Neighbor Address Update Message o Neighbor Address Update Message
o Neighbor Address Update ACK Message o Neighbor Address Update ACK Message
o Heartbeat Message o Heartbeat Message
o Link Characteristics Request Message o Link Characteristics Request Message
o Link Characteristics ACK Message o Link Characteristics ACK Message
This registry should be created according to the guidelines for
'Message-Type-Specific TLV' registration as specified in section
6.2.1 of [RFC5444].
26.5 DLEP Sub-TLV Type Registrations
A new repository for DLEP Sub-TLVs must be created. Valid Sub-TLVs are:
o Identification Sub-TLV
o DLEP Version Sub-TLV
o Peer Type Sub-TLV
o MAC Address Sub-TLV
o IPv4 Address Sub-TLV
o IPv6 Address Sub-TLV
o Maximum Data Rate Sub-TLV
o Current Data Rate Sub-TLV
o Latency Sub-TLV
o Resources Sub-TLV
o Relative Link Quality Sub-TLV
o Status Sub-TLV
o Heartbeat Interval Sub-TLV
o Heartbeat Threshold Sub-TLV
o Link Characteristics ACK Timer Sub-TLV
It is also requested that the registry allocation contain space
reserved for experimental sub-TLVs.
27. Appendix A. 27. Appendix A.
Peer Level Message Flows Peer Level Message Flows
*Modem Device (Client) Restarts Discovery *Modem Device (Client) Restarts Discovery
Router Client Message Description Router Client Message Description
==================================================================== ====================================================================
<-------Peer Discovery--------- Modem initiates discovery <-------Peer Discovery--------- Modem initiates discovery
skipping to change at page 45, line 10 skipping to change at page 54, line 10
RFC 5578, February 2010. RFC 5578, February 2010.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
Informative References Informative References
[DTLS] Rescorla, E., Ed,. "Datagram Transport Layer Security", [DTLS] Rescorla, E., Ed,. "Datagram Transport Layer Security",
RFC 4347, April 2006. RFC 4347, April 2006.
An open source (MIT License) DLEP implementation is available at
http://sourceforge.net/projects/dleptools
Author's Addresses Author's Addresses
Stan Ratliff Stan Ratliff
Cisco Cisco
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
EMail: sratliff@cisco.com EMail: sratliff@cisco.com
Bo Berry Bo Berry
 End of changes. 300 change blocks. 
528 lines changed or deleted 1044 lines changed or added

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