idnits 2.17.1 draft-ietf-manet-dlep-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 50 longer pages, the longest (page 5) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 54 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 15 instances of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 2, 2011) is 4743 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC5578' is defined on line 2663, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 5578 -- Obsolete informational reference (is this intentional?): RFC 4347 (ref. 'DTLS') (Obsoleted by RFC 6347) Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Mobile Ad hoc Networks Working S. Ratliff 2 Group B. Berry 3 Internet-Draft G. Harrison 4 Intended status: Standards Track S. Jury 5 Expires: November 2, 2011 D. Satterwhite 6 Cisco Systems 7 May 2, 2011 9 Dynamic Link Exchange Protocol (DLEP) 10 draft-ietf-manet-dlep-01 12 Abstract 14 When routing devices rely on modems to effect communications over 15 wireless links, they need timely and accurate knowledge of the 16 characteristics of the link (speed, state, etc.) in order to make 17 forwarding decisions. In mobile or other environments where these 18 characteristics change frequently, manual configurations or the 19 inference of state through routing or transport protocols does not 20 allow the router to make the best decisions. A bidirectional, event- 21 driven communication channel between the router and the modem is 22 necessary. 24 Status of this Memo 26 This Internet-Draft is submitted to IETF in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF), its areas, and its working groups. Note that 31 other groups may also distribute working documents as Internet- 32 Drafts. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 The list of current Internet-Drafts can be accessed at 40 http://www.ietf.org/ietf/1id-abstracts.txt. 42 The list of Internet-Draft Shadow Directories can be accessed at 43 http://www.ietf.org/shadow.html. 45 This Internet-Draft will expire on November 2, 2011 . 47 Copyright Notice 49 Copyright (c) 2010 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . 5 66 2. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 5 67 3. Normal Session Flow . . . . . . . . . . . . . . . . . . . . . 5 68 4. Generic DLEP Packet Definition . . . . . . . . . . . . . . . . 6 69 5. Message Header Format . . . . . . . . . . . . . . . . . . . . 7 70 6. Message TLV Block Format . . . . . . . . . . . . . . . . . . . 7 71 7. DLEP Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . . 8 72 7.1. Identification Sub-TLV . . . . . . . . . . . . . . . . . . 9 73 7.2. DLEP Version Sub-TLV . . . . . . . . . . . . . . . . . . . 10 74 7.3. Peer Type Sub-TLV . . . . . . . . . . . . . . . . . . . . 11 75 7.4. MAC Address Sub-TLV . . . . . . . . . . . . . . . . . . . 11 76 7.5. IPv4 Address Sub-TLV . . . . . . . . . . . . . . . . . . . 12 77 7.6. IPv6 Address Sub-TLV . . . . . . . . . . . . . . . . . . . 12 78 7.7. Maximum Data Rate Sub-TLV. . . . . . . . . . . . . . . . . 13 79 7.8. Current Data Rate Sub-TLV. . . . . . . . . . . . . . . . . 14 80 7.9. Latency Sub-TLV. . . . . . . . . . . . . . . . . . . . . . 14 81 7.10. Resources Sub-TLV. . . . . . . . . . . . . . . . . . . . . 15 82 7.11. Relative Link Quality Sub-TLV. . . . . . . . . . . . . . . 16 83 7.12. Peer Termination Sub-TLV . . . . . . . . . . . . . . . . . 16 84 7.13 Heartbeat Interval Sub-TLV . . . . . . . . . . . . . . . . 17 85 7.14 Heartbeat Threshold Sub-TLV. . . . . . . . . . . . . . . . 17 86 7.15 Link Characteristics ACK Timer Sub-TLV . . . . . . . . . . 18 87 8. DLEP Protocol Messages . . . . . . . . . . . . . . . . . . . . 19 88 8.1. Message Block TLV Values . . . . . . . . . . . . . . . . . 19 89 9. Peer Discovery Messages . . . . . . . . . . . . . . . . . . . 20 90 9.1. Attached Peer Discovery Message . . . . . . . . . . . . . 20 91 9.2. Detached Peer Discovery Message . . . . . . . . . . . . . 22 92 10. Peer Offer Message . . . . . . . . . . . . . . . . . . . . . . 23 93 11. Peer Update Message. . . . . . . . . . . . . . . . . . . . . . 25 94 12. Peer Update ACK Message. . . . . . . . . . . . . . . . . . . . 27 95 13. Peer Termination Message . . . . . . . . . . . . . . . . . . . 27 96 14. Peer Termination ACK Message . . . . . . . . . . . . . . . . . 28 97 15. Neighbor Up Message . . . . . . . . . . . . . . . . . . . . . 29 98 16. Neighbor Up ACK Message. . . . . . . . . . . . . . . . . . . . 31 99 17. Neighbor Down Message . . . . . . . . . . . . . . . . . . . . 32 100 18. Neighbor Down ACK Message. . . . . . . . . . . . . . . . . . . 33 101 19. Neighbor Update Message . . . . . . . . . . . . . . . . . . . 35 102 20. Neighbor Address Update Message. . . . . . . . . . . . . . . . 36 103 21. Neighbor Address Update ACK Message. . . . . . . . . . . . . . 38 104 22. Heartbeat Message . . . . . . . . . . . . . . . . . . . . . . 39 105 23. Link Characteristics Message . . . . . . . . . . . . . . . . . 39 106 24. Link Characteristics ACK Message . . . . . . . . . . . . . . . 41 107 25. Security Considerations. . . . . . . . . . . . . . . . . . . . 42 108 26. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 42 109 26.1 TLV Registrations. . . . . . . . . . . . . . . . . . . . . 43 110 26.2 Expert Review: Evaluation Guidelines . . . . . . . . . . . 43 111 26.3 Message TLV Type Registrations . . . . . . . . . . . . . . 43 112 26.4 DLEP Order Registrations . . . . . . . . . . . . . . . . . 43 113 26.5 DLEP Sub-TLV Type Registrations. . . . . . . . . . . . . . 44 114 27. Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . 45 116 1. Introduction 118 There exist today a collection of modem devices that control links of 119 variable bandwidth and quality. Examples of these types of links 120 include line-of-sight (LOS) radios, satellite terminals, and cable/ 121 DSL modems. Fluctuations in speed and quality of these links can 122 occur due to configuration (in the case of cable/DSL modems), or on a 123 moment-to-moment basis, due to physical phenomena like multipath 124 interference, obstructions, rain fade, etc. It is also quite possible 125 that link quality and bandwidth varies with respect to individual 126 neighbors on a link, and with the type of traffic being sent. As an 127 example, consider the case of an 802.11g access point, serving 2 128 associated laptop computers. In this environment, the answer to the 129 question "What is the bandwidth on the 802.11g link?" is "It depends 130 on which associated laptop we're talking about, and on what kind of 131 traffic is being sent." While the first laptop, being physically 132 close to the access point, may have a bandwidth of 54Mbps for 133 unicast traffic, the other laptop, being relatively far away, or 134 obstructed by some object, can simultaneously have a bandwidth of 135 only 32Mbps for unicast. However, for multicast traffic sent from the 136 access point, all traffic is sent at the base transmission rate 137 (which is configurable, but depending on the model of the access 138 point, is usually 24Mbps or less). 140 In addition to utilizing variable bandwidth links, mobile networks 141 are challenged by the notion that link connectivity will come and go 142 over time. Effectively utilizing a relatively short-lived connection 143 is problematic in IP routed networks, as routing protocols tend to 144 rely on independent timers at OSI Layer 3 to maintain network 145 convergence (e.g. HELLO messages and/or recognition of DEAD routing 146 adjacencies). These short-lived connections can be better utilized 147 with an event-driven paradigm, where acquisition of a new neighbor 148 (or loss of an existing one) is somehow signaled, as opposed to a 149 timer-driven paradigm. 151 Another complicating factor for mobile networks are the different 152 methods of physically connecting the modem devices to the router. 153 Modems can be deployed as an interface card in a router's 154 chassis, or as a standalone device connected to the router via 155 Ethernet, USB, or even a serial link. In the case of Ethernet or 156 serial attachment, with existing protocols and techniques, routing 157 software cannot be aware of convergence events occurring on the 158 radio link (e.g. acquisition or loss of a potential routing 159 neighbor), nor can the router be aware of the actual capacity of 160 the link. This lack of awareness, along with the variability in 161 bandwidth, leads to a situation where quality of service (QoS) 162 profiles are extremely difficult to establish and properly 163 maintain. This is especially true of demand-based access schemes 164 such as Demand Assigned Multiple Access (DAMA) implementations 165 used on some satellite systems. With a DAMA-based system, 166 additional bandwidth may be available, but will not be used 167 unless the network devices emit traffic at rate higher than the 168 currently established rate. Increasing the traffic rate does not 169 guarantee additional bandwidth will be allocated; rather, it may 170 result in data loss and additional retransmissions on the link. 172 In attempting to address the challenges listed above, the authors 173 have developed the Data Link Exchange Protocol, or DLEP. The DLEP 174 protocol runs between a router and its attached modem devices, 175 allowing the modem to communicate link characteristics as they 176 change, and convergence events (acquisition and loss of potential 177 routing neighbors). The diagram below is used to illustrate the 178 scope of DLEP sessions. When a local client (Modem device) 179 detects the presence of a remote neighbor, it sends an indication 180 to its local router via the DLEP session. Upon receipt of the 181 indication, the local router would take appropriate action (e.g. 182 initiation of discovery or HELLO protocols) to converge the 183 network. After notification of the new neighbor, the modem device 184 utilizes the DLEP session to report the characteristics of the 185 link (bandwidth, latency, etc) to the router on an as-needed 186 basis. Finally, the Modem is able to use the DLEP session to 187 notify the router when the remote neighbor is lost, shortening 188 the time required to re-converge the network. 190 |-----Local Neighbor-----| |-----Remote Neighbor----| 191 | | | (far-end device) | 193 +--------+ +-------+ +-------+ +--------+ 194 | Router |=======| Modem |{~~~~~~~~}| Modem |=======| Router | 195 | | | Device| | Device| | | 196 +--------+ +-------+ +-------+ +--------+ 198 | | | Link | | | 199 |-DLEP--| | Protocol | |-DLEP--| 200 | | | (e.g. | | | 201 | | | 802.11) | | | 203 Figure 1: DLEP Network 205 DLEP exists as a collection of type-length-value (TLV) based messages 206 using [RFC5444] formatting. The protocol can be used for both Ethernet 207 attached modems (utilizing, for example, a UDP socket for transport 208 of the RFC 5444 packets), or in environments where the modem is an 209 interface card in a chassis (via a message passing scheme). DLEP 210 utilizes a session paradigm between the modem device and its 211 associated router. If multiple modem devices are attached to a 212 router, a separate DLEP session MUST exist for each modem. If a modem 213 device supports multiple connections to a router (via multiple 214 interfaces), or supports connections to multiple routers, a separate 215 DLEP session MUST exist for each connection. 217 1.1 Requirements 219 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 220 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 221 document are to be interpreted as described in BCP 14, RFC 2119 222 [RFC2119]. 224 2. Assumptions 226 In order to implement discovery in the DLEP protocol (thereby 227 avoiding some configuration), we have defined a first-speaker and a 228 passive-listener scheme. Specifically, the router is defined as the 229 passive-listener, and the modem device defined as the first-speaker 230 (e.g. the initiator for discovery). Borrowing from existing 231 terminology, this document refers to the first-speaker as the 232 'client', even though there is no client/server relationship in the 233 classic sense. 235 DLEP assumes that participating modem devices appear to the router 236 as a transparent bridge - specifically, the assumption is that the 237 destination MAC address for data traffic in any frame emitted by 238 the router should be the MAC address of the next-hop router or end- 239 device, and not the MAC address of any of the intervening modem 240 devices. 242 DLEP assumes that security on the session (e.g. authentication of 243 session partners, encryption of traffic, or both) is dealt with by 244 the underlying transport mechanism for the RFC 5444 packets (e.g. by 245 using a transport such as DTLS [DTLS]). 247 The optional [RFC5444] message header Sequence Number MUST be 248 included in all DLEP packets. Sequence Numbers start at 1 and are 249 incremented by one for each original and retransmitted message. The 250 unsigned 16-bit Sequence Number rolls over at 65535 to 1. A 251 Sequence Number of 0 is not valid. Peer level Sequence Numbers are 252 unique within the context of a DLEP session. Sequence numbers are 253 used in DLEP to correlate a response to a request. 255 3. Normal Session Flow 257 A session between a router and a client is established by exchanging 258 the "Peer Discovery" and "Peer Offer" messages described below. 260 Once that exchange has successfully occurred, the client informs the 261 router of the presence of a new potential routing partner via the 262 "Neighbor Up" message. The loss of a neighbor is communicated via the 263 "Neighbor Down" message, and link quality is communicated via the 264 "Neighbor Update" message. Note that, due to the issue of metrics 265 varying depending on neighbor (discussed above), DLEP link metrics 266 are expressed within the context of a neighbor relationship, instead 267 of on the link as a whole. 269 Once the DLEP session has started, the session partners exchange 270 heartbeat messages based on a negotiated time interval. The heartbeat 271 messages are used to assure the session partners are in an 272 appropriate state, and that bidirectional connectivity still exists. 274 In addition to receiving metrics about the link, DLEP provides for 275 the ability for the router to request a different amount of 276 bandwidth, or latency, for its client via the Link Characteristics 277 Message. This allows the router to deal with requisite increases 278 (or decreases) of allocated bandwidth/latency in demand-based 279 schemes in a more deterministic manner. 281 4. Generic DLEP Packet Definition 283 The Generic DLEP Packet Definition follows the format for packets 284 defined in [RFC5444]. 286 The Generic DLEP Packet Definition contains the following fields: 288 0 1 2 3 289 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 290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 291 |Version| Flags | Packet Sequence Number | Packet TLV | 292 | | | | Block... | 293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 294 | Message (Contains DLEP message)... | 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 Version - Version of RFC 5444 specification on 298 which the packet/messages/TLVs are 299 constructed. 301 Flags - 4 bit field. All bits MUST be ignored 302 by DLEP implementations. 304 Packet Sequence Number - If present, the packet sequence number 305 is parsed and ignored. DLEP does NOT 306 use or generate packet sequence numbers. 308 Packet TLV block - a TLV block which contains packet level 309 TLV information. DLEP implementations 310 MUST NOT use this TLV block. 312 Message - the packet MAY contain zero or more 313 messages, however, DLEP messages are 314 encoded within an RFC 5444 Message 315 TLV Block. 317 5. Message Header Format 319 DLEP utilizes the following format for the RFC 5444 message header 321 0 1 2 3 322 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 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 | Msg Type |Msg Flg|AddrLen| Message Size | 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 | Message Seq Num | TLV Block... | 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 329 Message Type - an 8-bit field which specifies the type 330 of the message. For DLEP, this field 331 contains DLEP_MESSAGE (value TBD) 333 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit is 334 set). All other bits are unused and MUST 335 be set to '0'. 337 Message Address Length - a 4-bit unsigned integer field encoding the 338 length of all addresses included in this 339 message. DLEP implementations do not use 340 this field; contents SHOULD be ignored. 342 Message Size - a 16-bit unsigned integer field which 343 specifies the number of octets that make up 344 the message including the message header. 346 Message Sequence Number - a 16-bit unsigned integer field that 347 contains a sequence number, generated by 348 the originator of the message. Sequence 349 numbers range from 1 to 65535. Sequence 350 numbers roll over at 65535 to 1; 0 is 351 invalid. 353 TLV Block - TLV Block included in the message. 355 6. Message TLV Block Format 357 The DLEP protocol is organized as a set of orders, each with a 358 collection of Sub-TLVs. The Sub-TLVs carry information needed 359 to process and/or establish context (e.g. the MAC address of a 360 far-end router), and the 'tlv-type' field in the message TLV 361 block carries the DLEP order itself. The DLEP orders are 362 enumerated in section 8.1 of this document, and the messages 363 created using these orders are documented in sections 9 through 364 24. 366 DLEP uses the following settings for an RFC 5444 Message TLV 367 block: 369 0 1 2 3 370 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 371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 | TLVs Length | TLV Type | TLV Flags | 373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 374 | Length | Value... | 375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 377 TLVs Length - a 16-bit unsigned integer field that contains the total 378 number of octets in all of the immediately following 379 TLV elements (tlvs-length not included). 381 TLV Type - an 8-bit unsigned integer field specifying the type 382 of the TLV. DLEP uses this field to specify the DLEP 383 order. Valid DLEP orders are defined in section 8.1 of 384 this document. 386 TLV Flags - an 8-bit flags bit field. Bit 3 (thasvalue) MUST be 387 set; all other bits are not used and MUST be set 388 to '0'. 390 Length - Length of the 'Value' field of the TLV 392 Value - A field of length which contains data 393 specific to a particular TLV type. In the DLEP 394 case, this field will consist of a collection of 395 DLEP sub-TLVs appropriate for the DLEP action 396 specified in the TLV type field. 398 7. DLEP sub-TLVs 400 DLEP protocol messages are transported in an RFC 5444 message TLV. 401 All DLEP messages use the RFC 5444 DLEP_MESSAGE value (TBD). The 402 protocol messages consist of a DLEP order, encoded in the 'tlv-type' 403 field in the message TLV block, with the 'value' field of the TLV 404 block containing a collection (1 or more) DLEP sub-TLVs. 406 The format of DLEP Sub-TLVs is consistent with RFC 5444 in that the 407 Sub-TLVs contain a flag field in addition to the type, length, and 408 value fields. Valid DLEP Sub-TLVs are: 410 TLV TLV 411 Value Description 412 ========================================= 413 TBD Identification sub-TLV 414 TBD DLEP Version sub-TLV 415 TBD Peer Type sub-TLV 416 TBD MAC Address sub-TLV 417 TBD IPv4 Address sub-TLV 418 TBD IPv6 Address sub-TLV 419 TBD Maximum Data Rate (MDR) sub-TLV 420 TBD Current Data Rate (CDR) sub-TLV 421 TBD Latency sub-TLV 422 TBD Resources sub-TLV 423 TBD Relative Link Quality (RLQ) sub-TLV 424 TBD Status sub-TLV 425 TBD Heartbeat Interval sub-TLV 426 TBD Heartbeat Threshold sub-TLV 427 TBD Neighbor down ACK timer sub-TLV 428 TBD Link Characteristics ACK timer sub-TLV 430 DLEP sub-TLVs contain the following fields: 432 0 1 2 3 433 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 434 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 435 | TLV Type |TLV Flags=0x10 | Length | Value... | 436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 438 TLV Type - an 8-bit unsigned integer field specifying the type 439 of the sub-TLV. 441 TLV Flags - an 8-bit flags bit field. Bit 3 (thasvalue) MUST be 442 set, all other bits are not used and MUST be set to 443 '0'. 445 Length - an 8-bit length of the value field of the sub-TLV 447 Value - A field of length which contains data 448 specific to a particular sub-TLV. 450 7.1 Identification Sub-TLV 452 This Sub-TLV MUST exist in the TLV Block for all DLEP messages, and 453 MUST be the first Sub-TLV of the message. Further, there MUST be ONLY 454 one Identification Sub-TLV in an RFC 5444 message TLV block. The 455 Identification sub-TLV contains client and router identification 456 information used to establish the proper context for processing DLEP 457 protocol messages. 459 The Identification sub-TLV contains the following fields: 461 0 1 2 3 462 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 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 464 |TLV Type = TBD |TLV Flags=0x10 |Length = 8 | Router ID | 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 | Router ID | Client ID | 467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 468 | Client ID | 469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 470 TLV Type - Value TBD 472 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are 473 unused and MUST be set to '0'. 475 Length - 8 477 Router ID - indicates the router ID of the DLEP session. 479 Client ID - indicates the client ID of the DLEP session. 481 When the client initiates discovery (via the Peer Discovery message), 482 it MUST set the Client ID to a 32-bit quantity that will be used to 483 uniquely identify this session from the client-side. The client MUST 484 set the Router ID to '0'. When responding to the Peer Discovery 485 message, the router MUST echo the Client ID, and MUST supply its own 486 unique 32-bit quantity to identify the session from the router's 487 perspective. After the Peer Discovery/Peer Offer exchange, both the 488 Client ID and the Router ID MUST be set to the values obtained from 489 the Peer DIscovery/Peer Offer sequence. 491 7.2 DLEP Version Sub-TLV 493 The DLEP Version Sub-TLV is an OPTIONAL TLV in both the Peer 494 Discovery and Peer Offer messages. The Version Sub-TLV is used to 495 indicate the client or router version of the protocol. The client 496 and router MAY use this information to decide if the peer is running 497 at a supported level. 499 The DLEP Version Sub-TLV contains the following fields: 501 0 1 2 3 502 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 503 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 504 |TLV Type =TBD |TLV Flags=0x10 |Length=4 | Major Version | 505 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 506 | Major Version | Minor Version | 507 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 509 TLV Type - TBD 511 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are 512 not used and MUST be set to '0'. 514 Length - Length is 4 516 Major Version - Major version of the client or router protocol. 518 Minor Version - Minor version of the client or router protocol. 520 Support of this draft is indicated by setting the Major Version 521 to '1', and the Minor Version to '1' (e.g. Version 1.1). 523 7.3 Peer Type Sub-TLV 525 The Peer Type Sub-TLV is used by the router and client to give 526 additional information as to its type. It is an OPTIONAL sub-TLV in 527 both the Peer Discovery Message and the Peer Offer message. The peer 528 type is a string and is envisioned to be used for informational 529 purposes (e.g. display command). 531 The Peer Type sub-TLV contains the following fields: 533 0 1 2 3 534 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 535 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 536 |TLV Type =TBD |TLV Flags=0x10 |Length= peer |Peer Type Str | 537 | | |type string len|Max Len = 80 | 538 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 540 TLV Type - TBD 542 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits 543 are not used and MUST be set to '0'. 545 Length - length of peer type string (80 bytes maximum) 546 Peer Type String - Non-Null terminated peer type string, maximum 547 length of 80 bytes. For example, a satellite 548 modem might set this variable to 'Satellite 549 terminal'. 551 7.4 MAC Address Sub-TLV 553 The MAC address Sub-TLV MUST appear in all neighbor-oriented 554 messages (e.g. Neighbor Up, Neighbor Up ACK, Neighbor Down, Neighbor 555 Down ACK, Neighbor Update, Link Characteristics Request, and Link 556 Characteristics ACK). The MAC Address sub-TLV contains the address 557 of the far-end (neighbor) router. 559 The MAC Address sub-TLV contains the following fields: 561 0 1 2 3 562 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 563 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 564 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 565 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 566 | MAC Address | 567 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 568 | MAC Address | 569 +-+-+-+-+-+-+-+-+ 571 TLV Type - TBD 573 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are not 574 used and MUST be set to '0'. 576 Length - 6 578 MAC Address - MAC Address of the far-end router. 580 7.5 IPv4 Address Sub-TLV 582 The IPv4 Address Sub-TLV MAY be used in Neighbor Up, Neighbor Update, 583 and Peer Update Messages, if the client is aware of the Layer 3 584 address. When included in Neighbor messages, the IPv4 Address sub-TLV 585 contains the IPv4 address of the far-end router (neighbor). In 586 the Peer Update message, it contains the IPv4 address of the local 587 router. In either case, the sub-TLV also contains an indication of 588 whether this is a new or existing address, or is a deletion of 589 a previously known address. 591 The IPv4 Address Sub-TLV contains the following fields: 593 0 1 2 3 594 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 595 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 596 |TLV Type =TBD |TLV Flags=0x10 |Length = 5 | Add/Drop | 597 | | | | Indicator | 598 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 599 | IPv4 Address | 600 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 602 TLV Type - TBD 604 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are not 605 used and MUST be set to '0'. 607 Length - 5 609 Add/Drop - Value indicating whether this is a new or existing 610 Indicator address (0x01), or a withdrawal of an address (0x02). 612 IPv4 Address - IPv4 Address of the far-end router. 614 7.6 IPv6 Address Sub-TLV 616 The IPv6 Address Sub-TLV MAY be used in Neighbor Up, Neighbor Update, 617 and Peer Update Messages, if the client is aware of the Layer 3 618 address. When included in Neighbor messages, the IPv6 Address sub-TLV 619 contains the IPv6 address of the far-end router (neighbor). In 620 the Peer Update, it contains the IPv6 address of the local router. 621 In either case, the sub-TLV also contains an indication of whether 622 this is a new or existing address, or is a deletion of a 623 previously known address. 625 The IPv6 Address sub-TLV contains the following fields: 627 0 1 2 3 628 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 629 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 630 |TLV Type =TBD |TLV Flags=0x10 |Length = 17 | Add/Drop | 631 | | | | Indicator | 632 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 633 | IPv6 Address | 634 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 635 | IPv6 Address | 636 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 637 | IPv6 Address | 638 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 639 | IPv6 Address | 640 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 642 TLV Type - TBD 644 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are not 645 used and MUST be set to '0'. 647 Length - 17 649 Add/Drop - Value indicating whether this is a new or 650 Indicator existing address (0x01), or a withdrawal of 651 an address (0x02). 653 IPv6 Address - IPv6 Address of the far-end router. 655 7.7 Maximum Data Rate Sub-TLV 657 The Maximum Data Rate (MDR) Sub-TLV is used in Neighbor Up, Neighbor 658 Update, and Link Characteristics ACK Messages to indicate the 659 maximum theoretical data rate, in bits per second, that can be 660 achieved on the link. When metrics are reported via the messages 661 listed above, the maximum data rate MUST be reported. 663 The Maximum Data Rate sub-TLV contains the following fields: 665 0 1 2 3 666 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 667 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 668 |TLV Type =TBD |TLV Flags=0x10 |Length = 8 | MDR (bps) | 669 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 670 | MDR (bps) | 671 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 672 | MDR (bps) | 673 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 675 TLV Type - TBD 676 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other 677 bits are not used and MUST be set to '0'. 679 Length - 8 681 Maximum Data Rate - A 64-bit unsigned number, representing the 682 maximum theoretical data rate, in bits per 683 second (bps), that can be achieved on the 684 link. 686 7.8 Current Data Rate Sub-TLV 688 The Current Data Rate (CDR) Sub-TLV is used in Neighbor Up, Neighbor 689 Update, Link Characteristics Request, and Link Characteristics ACK 690 messages to indicate the rate at which the link is currently 691 operating, or in the case of the Link Characteristics Request, 692 the desired data rate for the link. 694 The Current Data Rate sub-TLV contains the following fields: 696 0 1 2 3 697 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 698 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 699 |TLV Type =TBD |TLV Flags=0x10 |Length = 8 |CDR (bps) | 700 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 701 | CDR (bps) | 702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 703 | CDR (bps) | 704 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 706 TLV Type - TBD 708 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other 709 bits are not used and MUST be set to '0'. 711 Length - 8 713 Current Data Rate - A 64-bit unsigned number, representing the 714 current data rate, in bits per second (bps), 715 on the link. When reporting metrics (e.g, 716 in Neighbor Up, Neighbor Down, or Link 717 Characteristics ACK), if there is no 718 distinction between current and maximum 719 data rates, current data rate SHOULD be 720 set equal to the maximum data rate. 722 7.9 Latency Sub-TLV 724 The Latency Sub-TLV is used in Neighbor Up, Neighbor Update, Link 725 Characteristics Request, and Link Characteristics ACK messages to 726 indicate the amount of latency on the link, or in the case of the 727 Link Characteristics Request, to indicate the maximum latency 728 required (e.g. a should-not-exeed value) on the link. 730 The Latency Sub-TLV contains the following fields: 732 0 1 2 3 733 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 734 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 735 |TLV Type =TBD |TLV Flags=0x10 |Length = 2 |Latency (ms) | 736 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 737 |Latency (ms) | 738 +-+-+-+-+-+-+-+-+ 740 TLV Type - TBD 742 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other 743 bits are not used and MUST be set to '0'. 745 Length - 2 747 Latency - the transmission delay that a packet 748 encounters as it is transmitted over the 749 link. In Neighbor Up, Neighbor Update, 750 and Link Characteristics ACK, this value 751 is reported in absolute delay, in 752 milliseconds. The calculation of latency 753 is modem-device dependent. For example, 754 the latency may be a running average 755 calculated from the internal queuing. If 756 the modem device cannot calculate latency, 757 it SHOULD be reported as 0. In the Link 758 Characteristics Request Message, this value 759 represents the maximum delay, in milliseconds, 760 expected on the link. 762 7.10 Resources Sub-TLV 764 The Resources Sub-TLV is used in Neighbor Up, Neighbor Update, and Link 765 Characteristics ACK messages to indicate a percentage (0-100) amount 766 of resources (e.g. battery power) remaining on the modem device. 768 The Resources TLV contains the following fields: 769 0 1 2 3 770 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 771 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 772 |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Resources | 773 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 775 TLV Type - TBD 777 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other 778 bits are not used and MUST be set to '0'. 780 Length - 1 781 Resources - a percentage, 0-100, representing the amount 782 of remaining resources, such as battery power. 783 If resources cannot be calculated, a value of 784 100 SHOULD be reported. 786 7.11 Relative Link Quality Sub-TLV 788 The Relative Link Quality (RLQ) Sub-TLV is used in Neighbor Up, 789 Neighbor Update, and Link Characteristics ACK messages to indicate 790 the quality of the link as calculated by the modem device. 792 The Relative Link Quality sub-TLV contains the following fields: 794 0 1 2 3 795 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 796 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 797 |TLV Type =TBD |TLV Flags=0x10 |Length = 1 |Relative Link | 798 | | | |Quality (RLQ) | 799 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 801 TLV Type - TBD 803 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other 804 bits are not used and MUST be set to '0'. 806 Length - 1 808 Relative Link Quality - a non-dimensional number, 0-100, 809 representing the relative link quality. 810 A value of 100 represents a link of the 811 highest quality. If the RLQ cannot be 812 calculated, a value of 100 SHOULD be 813 reported. 815 7.12 Status Sub-TLV 817 The Status Sub-TLV is sent from either the client or router to 818 indicate the success or failure of a given request 820 The Status Sub-TLV contains the following fields: 822 0 1 2 3 823 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 824 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 825 |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Code | 826 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 828 TLV Type - TBD 830 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are 831 not used and MUST be set to '0'. 833 Length - 1 835 Termination Code - 0 = Success 836 Non-zero = Failure. Specific values of a non- 837 zero termination code depend on the operation 838 requested (e.g. Neighbor Up, Neighbor Down, etc). 840 7.13 Heartbeat Interval Sub-TLV 842 The Heartbeat Interval Sub-TLV MAY be sent from the client during 843 Peer Discovery to indicate the desired Heartbeat timeout window. 844 If included in the Peer Discovery, the router MUST either accept the 845 timeout interval, or reject the Peer Discovery. 847 The Heartbeat Interval Sub-TLV contains the following fields: 849 0 1 2 3 850 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 851 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 852 |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Interval | 853 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 855 TLV Type - TBD 857 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are 858 not used and MUST be set to '0'. 860 Length - 1 862 Interval - 0 = Do NOT use heartbeats on this peer-to-peer 863 session. Non-zero = Interval, in seconds, for 864 heartbeat messages. 866 7.14 Heartbeat Threshold Sub-TLV 868 The Heartbeat Threshold Sub-TLV MAY be sent from the client during 869 Peer Discovery to indicate the desired number of windows, of time 870 (Heartbeat Interval) seconds, to wait before either peer declares 871 the peer-to-peer session lost. In this case, the overall amount of 872 time before a peer-to-peer session is declared lost is expressed as 873 (Interval * Threshold), where 'Interval' is the value in the 874 Heartbeat Interval sub-TLV, documented above. If this sub-TLV is 875 included by the client in the Peer Discovery, the client MUST also 876 specify the Heartbeat Interval sub-TLV with a non-zero interval. If 877 this sub-TLV is received during Peer Discovery, the router MUST 878 either accept the threshold, or reject the Peer Discovery. 880 The Heartbeat Threshold Sub-TLV contains the following fields: 882 0 1 2 3 883 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 884 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 885 |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Threshold | 886 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 888 TLV Type - TBD 890 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are 891 not used and MUST be set to '0'. 893 Length - 1 895 Threshold - 0 = Do NOT use heartbeats on this peer-to-peer 896 session. Non-zero = Number of windows, of 897 Heartbeat Interval seconds, to wait before 898 declaring a peer-to-peer session to be lost. 900 7.15 Link Characteristics ACK Timer Sub-TLV 902 The Link Characteristic ACK Timer Sub-TLV MAY be sent from the 903 client during Peer Discovery to indicate the desired number of 904 seconds the router should wait for a response to a Link 905 Characteristics Request. If this sub-TLV is received during Peer 906 Discovery, the router MUST either accept the timeout value, or 907 reject the Peer Discovery. 909 The Link Characteristics ACK Timer Sub-TLV contains the 910 following fields: 912 0 1 2 3 913 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 914 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 915 |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Interval | 916 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 918 TLV Type - TBD 920 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are 921 not used and MUST be set to '0'. 923 Length - 1 925 Interval - 0 = Do NOT use timeouts for Link Characteristics 926 requests on this peer-to-peer session. 927 Non-zero = Interval, in seconds, to wait before 928 considering a Link Characteristics Request has 929 been lost. 931 8. DLEP Protocol Messages 933 DLEP places no additional requirements on the RFC 5444 Packet 934 formats, or the packet header. DLEP does require that the optional 935 'msg-seq-num' in the message header exist, and defines a set of 936 values for the 'tlv-type' field in the RFC 5444 TLV block. Therefore, 937 a DLEP message, starting from the RFC 5444 Message header, would 938 appear as follows: 940 0 1 2 3 941 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 942 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 943 | Msg Type = |Msg Flg|AddrLen| Message Size | 944 | DLEP_MESSAGE | 0x1 | 0x0 | | 945 | (value TBD) | | | | 946 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 947 | Message Seq Num | TLV block length (length of | 948 | | DLEP order + Sub-TLVs) | 949 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 950 | DLEP Message |TLV Flags=0x10 | Length | Start of DLEP | 951 | Block value | | | Sub-TLVs... | 952 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 954 8.1 Message Block TLV Values 956 As mentioned above, all DLEP messages utilize a single RFC 5444 957 message type, the DLEP_MESSAGE (TBD). DLEP further identifies 958 protocol messages by using the 'tlv-type' field in the RFC 5444 959 message TLV block. DLEP defines the following Message-Type- 960 specific values for the tlv-type field: 962 TLV TLV 963 Value Description 964 ========================================= 965 TBD Attached Peer Discovery 966 TBD Detached Peer Discovery 967 TBD Peer Offer 968 TBD Peer Update 969 TBD Peer Update ACK 970 TBD Peer Termination 971 TBD Peer Termination ACK 972 TBD Neighbor Up 973 TBD Neighbor Up ACK 974 TBD Neighbor Down 975 TBD Neighbor Down ACK 976 TBD Neighbor Update 977 TBD Neighbor Address Update 978 TBD Neighbor Address Update ACK 979 TBD Heartbeat 980 TBD Link Characteristics Request 981 TBD Link Characteristics ACK 983 In all of the diagrams following, the message layouts begin with the 984 RFC 5444 message header. 986 9. Peer Discovery Messages 988 There are two different types of Peer Discovery Messages, Attached 989 and Detached. Attached Peer Discovery Messages are sent by the 990 client when it is directly attached to the router (e.g. the client 991 exists as a card in the chassis, or it is connected via Ethernet with 992 no intervening devices). The Detached Peer Discovery message, on the 993 other hand, is sent by a "remote" client -- for example, a client at 994 a satellite hub system might use a Detached Discovery Message in 995 order to act as a proxy for remote ground terminals. To explain in 996 another way, a detached client uses the variable link itself (the 997 radio or satellite link) to establish a DLEP session with a remote 998 router. 1000 9.1 Attached Peer Discovery Message 1002 The Attached Peer Discovery Message is sent by an attached client 1003 to a router to begin a new DLEP association. The Peer Offer message 1004 is required to complete the discovery process. The client MAY 1005 implement its own retry heuristics in the event it (the client) 1006 determines the Attached Peer Discovery Message has timed out. 1008 The Attached Peer Discovery Message contains the following fields: 1010 0 1 2 3 1011 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 1012 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1013 | Msg Type = |Msg Flg|AddrLen| Message Size | 1014 | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt | 1015 | (value TBD) | | | sub-TLV | 1016 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1017 | Message Seq Num |TLVs Length =14 + opt sub-TLVs | 1018 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1019 | DLEP Attached |TLV Flags=0x10 | Length =11 + | Sub-TLV type= | 1020 | Peer Discovery| | opt sub-TLVs | Identification| 1021 | (Value TDB) | | | sub-TLV (TBD) | 1022 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1023 |TLV Flags=0x10 |Length = 8 | Router ID | 1024 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1025 | Router ID | Client ID | 1026 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1027 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1028 | |DLEP Version | | 1029 | |sub-TLV (TBD) | | 1030 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1031 |Length = 4 | Major Version | Minor Version | 1032 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1033 | Minor Version |Sub-TLV type= |TLV Flags=0x10 | Length = Len | 1034 | |Peer Type (TBD)| |of peer string | 1035 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1036 | (Continued on next page) | 1037 0 1 2 3 1038 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 1039 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1040 | (Continued from previous page) | 1041 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1042 | Peer Type Str |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 | 1043 |MaxLen=80 bytes|Heartbeat Int. | | | 1044 | |(TBD) | | | 1045 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1046 | Heartbeat |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 | 1047 | Interval |HB Thresh. | | | 1048 | (seconds) |(TBD) | | | 1049 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1050 | Heartbeat |Sub-TLV Type= |TLV FLags=0x10 | Length = 1 | 1051 | Threshold |Link Char. ACK | | | 1052 |(# of windows) |Timer (TBD) | | | 1053 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1054 |Link Char ACK | 1055 |Timer (sec) | 1056 +-+-+-+-+-+-+-+-+ 1058 Message Type - DLEP_MESSAGE (value TBD) 1060 Message Flags - Set to 0x1 (bit 3, mhasseqnum 1061 bit is set). No other bits are 1062 used and MUST be set to '0'. 1064 Message Address Length - 0x0 1066 Message Size - 22 + size of optional sub-TLVs 1068 Message Sequence Number - a 16-bit unsigned integer field 1069 containing a sequence number 1070 generated by the message 1071 originator. 1073 TLV Block - TLVs Length: 14 + size of optional 1074 sub-TLVs. 1076 DLEP Attached Peer Disc. order 1077 Identification TLV (MANDATORY) 1078 Version Sub-TLV (OPTIONAL) 1079 Peer Type Sub-TLV (OPTIONAL) 1080 Heartbeat Int. Sub-TLV (OPTIONAL) 1081 Heartbeat Threshold Sub-TLV (OPT.) 1082 Link Characteristics ACK Timer 1083 Sub-TLV (OPTIONAL) 1085 9.2 Detached Peer Discovery Message 1087 The Detached Peer Discovery Message is sent by a detached client 1088 proxy to a router to begin a new DLEP session. The Peer Offer 1089 message is required to complete the discovery process. The client 1090 MAY implement its own retry heuristics in the event it (the client) 1091 determines the Detached Peer Discovery Message has timed out. 1093 The Detached Peer Discovery Message contains the following fields: 1095 0 1 2 3 1096 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 1097 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1098 | Msg Type = |Msg Flg|AddrLen| Message Size | 1099 | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt | 1100 | (value TBD) | | | sub-TLV | 1101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1102 | Message Seq Num |TLVs Length =14 + opt sub-TLVs | 1103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1104 | DLEP Detached |TLV Flags=0x10 | Length = 11 + | Sub-TLV type= | 1105 | Peer Discovery| | opt sub-TLVs | Identification| 1106 | (Value TDB) | | | sub-TLV (TBD) | 1107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1108 |TLV Flags=0x10 |Length = 8 | Router ID | 1109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1110 | Router ID | Client ID | 1111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1112 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1113 | |DLEP Version | | 1114 | |sub-TLV (TBD) | | 1115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1116 |Length = 4 | Major Version | Minor Version | 1117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1118 | Minor Version |Sub-TLV type= |TLV Flags=0x10 | Length = Len | 1119 | |Peer Type (TBD)| |of peer string | 1120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1121 | Peer Type Str |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 | 1122 |MaxLen=80 bytes|Heartbeat Int. | | | 1123 | |(TBD) | | | 1124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1125 | Heartbeat |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 | 1126 | Interval |HB Thresh. | | | 1127 | (seconds) |(TBD) | | | 1128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1129 | Heartbeat |Sub-TLV Type= |TLV FLags=0x10 | Length = 1 | 1130 | Threshold |Link Char. ACK | | | 1131 |(# of windows) |Timer (TBD) | | | 1132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1133 |Link Char ACK | 1134 |Timer (sec) | 1135 +-+-+-+-+-+-+-+-+ 1137 Message Type - DLEP_MESSAGE (value TBD) 1138 Message Flags - Set to 0x1 (bit 3, 1139 mhasseqnum bit is set). 1140 All other bits are not used 1141 and MUST be set to '0'. 1143 Message Address Length - 0x0 1145 Message Size - 22 + size of optional 1146 sub-TLVs 1148 Message Sequence Number - A 16-bit unsigned integer 1149 field containing a sequence 1150 number, generated by the 1151 message originator. 1153 TLV Block - TLVs Length: 14 + size of 1154 optional sub-TLVs. 1156 DLEP Detached Peer Discovery order 1157 Identification sub-TLV (MANDATORY) 1158 Version sub-TLV (OPTIONAL) 1159 Peer Type Sub-TLV (OPTIONAL) 1160 Heartbeat Interval Sub-TLV (OPTIONAL) 1161 Heartbeat Threshold Sub-TLV (OPTIONAL) 1162 Link Char. ACK Timer Sub-TLV(OPTIONAL) 1164 10. Peer Offer Message 1166 The Peer Offer Message is sent by a router to a client or client 1167 proxy in response to a Peer Discovery Message. The Peer Offer 1168 Message is the response to either of the Peer Discovery messages 1169 (either Attached or Detached), and completes the DLEP session 1170 establishment. 1172 The Peer Offer Message contains the following fields: 1174 0 1 2 3 1175 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 1176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1177 | Msg Type = |Msg Flg|AddrLen| Message Size | 1178 | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt | 1179 | (value TBD) | | | sub-TLV | 1180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1181 | Message Seq Num |TLVs Length =14 + opt sub-TLVs | 1182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1183 |DLEP Peer Offer|TLV Flags=0x10 | Length = 11 + | Sub-TLV type= | 1184 | (Value TBD) | | opt sub-TLVs | Identification| 1185 | | | | sub-TLV (TBD) | 1186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1187 |TLV Flags=0x10 |Length = 8 | Router ID | 1188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1189 | (Continued on next page) | 1190 0 1 2 3 1191 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 1192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1193 | (Continued from above) | 1194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1195 | Router ID | Client ID | 1196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1197 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1198 | |DLEP Version | | 1199 | |sub-TLV (TBD) | | 1200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1201 | Length = 4 | Major Version | Minor Version | 1202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1203 | Minor Version |Peer Type sub- |TLV Flags=0x10 | Length = Len | 1204 | |TLV = TDB | |of peer string | 1205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1206 | Peer Type Str |DLEP IPv4 sub- |TLV Flags=0x10 | Length = 5 | 1207 |MaxLen=80 bytes|TLV (TBD) | | | 1208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1209 | Add/Drop Ind. | IPv4 Address | 1210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1211 | IPv4 Address |DLEP IPv6 sub- |TLV Flags=0x10 | Length = 17 | 1212 | |TLV Type = TBD | | | 1213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1214 | Add/Drop Ind. | IPv6 Address | 1215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1216 | IPv6 Address | 1217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1218 | IPv6 Address | 1219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1220 | IPv6 Address | 1221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1222 |IPv6 Address |Sub-TLV type= |TLV Flags=0x10 | Length = 1 | 1223 | |Heartbeat Int. | | | 1224 | |(TBD) | | | 1225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1226 | Heartbeat |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 | 1227 | Interval |Heartbeat | | | 1228 | (seconds) |Threshold (TBD)| | | 1229 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1230 | Heartbeat |Sub-TLV Type= |TLV FLags=0x10 | Length = 1 | 1231 | Threshold |Link Char. ACK | | | 1232 | (# of windows)|Timer (TBD) | | | 1233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1234 |Link Char ACK |Sub-TLV Type= |TLV Flags=0x10 | Length = 1 | 1235 |Timer (sec) |DLEP Status | | | 1236 | |(TBD) | | | 1237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1238 | Code | 1239 +-+-+-+-+-+-+-+-+ 1241 Message Type - DLEP_MESSAGE (Value TBD) 1242 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1243 is set). All other bits are unused and 1244 MUST be set to '0'. 1246 Message Address Length - 0x0 1248 Message Size - 22 + size of optional sub-TLVs 1250 Message Sequence Number - A 16-bit unsigned integer field containing 1251 a sequence number, generated by the message 1252 originator. 1254 TLV Block - TLV Length: 14 + size of optional sub-TLVs 1255 DLEP Peer Offer order 1256 Identification sub-TLV (MANDATORY) 1257 DLEP Version sub-TLV (OPTIONAL) 1258 Peer Type sub-TLV (OPTIONAL) 1259 IPv4 Address sub-TLV (OPTIONAL) 1260 IPv6 Address sub-TLV (OPTIONAL) 1261 Status sub-TLV (OPTIONAL) 1262 Heartbeat Interval Sub-TLV (OPTIONAL) 1263 Heartbeat Threshold Sub-TLV (OPTIONAL) 1264 Link Char. ACK Timer Sub-TLV (OPTIONAL) 1266 11. Peer Update Message 1268 The Peer Update message is sent by the router to indicate local 1269 Layer 3 address changes. For example, addition of an IPv4 address 1270 to the router would prompt a Peer Update message to its attached 1271 DLEP clients. If the modem device is capable of understanding and 1272 forwarding this information, the address update would prompt any 1273 remote DLEP clients (DLEP clients that are on the far-end of the 1274 variable link) to issue a "Neighbor Update" message to their local 1275 routers, with the address change information. Clients that do not 1276 track Layer 3 addresses MUST silently ignore the Peer Update 1277 Message. Clients that track Layer 3 addresses MUST acknowledge the 1278 Peer Update with a Peer Update ACK message. Routers MAY employ 1279 heuristics to retransmit Peer Update messages. Sending of Peer 1280 Update Messages SHOULD cease when a router implementation 1281 determines that a partner modem device does NOT support Layer 3 1282 address tracking. 1284 The Peer Update Message contains the following fields: 1286 0 1 2 3 1287 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 1288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1289 | Msg Type = |Msg Flg|AddrLen| Message Size | 1290 | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt | 1291 | (value TBD) | | | sub-TLVs | 1292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1293 | Message Seq Num |TLVs Length =14 + opt sub-TLVs | 1294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1295 | DLEP Peer |TLV Flags=0x10 | Length = 11 + | Sub-TLV type= | 1296 | Update | | opt sub-TLVs | Identification| 1297 | (Value TDB) | | | sub-TLV (TBD) | 1298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1299 |TLV Flags=0x10 |Length = 8 | Router ID | 1300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1301 | Router ID | Client ID | 1302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1303 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1304 | |DLEP IPv4 | | 1305 | |sub-TLV (TBD) | | 1306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1307 |Length = 5 | Add/Drop Ind. | IPv4 Address | 1308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1309 | IPv4 Address | Sub-TLV type= |TLV Flags=0x10 | 1310 | | DLEP IPv6 | | 1311 | | sub-TLV (TBD) | | 1312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1313 |Length = 17 | Add/Drop Ind. | IPv6 Address | 1314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1315 | IPv6 Address | 1316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1317 | IPv6 Address | 1318 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1319 | IPv6 Address | 1320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1321 | IPv6 Address | 1322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1324 Message Type - DLEP_MESSAGE (Value TBD) 1326 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1327 is set). All other bits are unused and 1328 MUST be set to '0'. 1330 Message Address Length - 0x0 1332 Message Size - 22 + optional Sub-TLVs 1334 Message Sequence Number - A 16-bit unsigned integer field containing 1335 a sequence number generated by the message 1336 originator. 1338 TLV Block - TLV Length: 14 + length of optional 1339 sub-TLVs. 1340 DLEP Peer Update order 1341 Identification sub-TLV (MANDATORY) 1342 IPv4 Address Sub-TLV (OPTIONAL) 1343 IPv6 Address Sub-TLV (OPTIONAL) 1345 12. Peer Update ACK Message 1347 The client sends the Peer Update ACK Message to indicate whether a 1348 Peer Update Message was successfully processed. 1350 The Peer Update ACK message contains the following fields: 1352 0 1 2 3 1353 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 1354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1355 | Msg Type = |Msg Flg|AddrLen| Message Size | 1356 | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt | 1357 | (value TBD) | | | sub-TLVs | 1358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1359 | Message Seq Num |TLVs Length =14 + opt sub-TLVs | 1360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1361 | DLEP Peer |TLV Flags=0x10 | Length = 11 + | Sub-TLV type= | 1362 | Update ACK | | opt sub-TLVs | Identification| 1363 | (Value TDB) | | | sub-TLV (TBD) | 1364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1365 |TLV Flags=0x10 |Length = 8 | Router ID | 1366 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1367 | Router ID | Client ID | 1368 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1369 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1370 | |DLEP Status | | 1371 | |sub-TLV (TBD) | | 1372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1373 |Length = 1 | Code | 1374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1376 Message Type - DLEP_MESSAGE (Value TBD) 1378 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1379 is set). All other bits are unused and 1380 MUST be set to '0'. 1382 Message Address Length - 0x0 1384 Message Size - 22 + size of optional sub-TLVs. 1386 Message Sequence Number - A 16-bit unsigned integer field containing 1387 the sequence number from the Neighbor Up 1388 Message that is being acknowledged. 1390 TLV Block - TLV Length: 14 + optional sub-TLVs 1391 DLEP Peer Update ACK order 1392 Identification Sub-TLV (MANDATORY) 1393 Status Sub-TLV (OPTIONAL) 1395 13. Peer Termination Message 1397 The Peer Termination Message is sent by either the client or the 1398 router when a session needs to be terminated. Transmission of a 1399 Peer Termination ACK message is required to confirm the 1400 termination process. The sender of the Peer Termination message 1401 is free to define its heuristics in event of a timeout. The 1402 receiver of a Peer Termination Message MUST terminate all 1403 neighbor relationships and release associated resources. No 1404 Neighbor Down messages are sent. 1406 The Peer Termination Message contains the following fields: 1408 0 1 2 3 1409 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 1410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1411 | Msg Type = |Msg Flg|AddrLen| Message Size | 1412 | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt | 1413 | (value TBD) | | | sub-TLVs | 1414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1415 | Message Seq Num |TLVs Length =14 + opt sub-TLVs | 1416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1417 | DLEP Peer |TLV Flags=0x10 | Length = 11 + | Sub-TLV type= | 1418 | Termination | | opt sub-TLVs | Identification| 1419 | (Value TDB) | | | sub-TLV (TBD) | 1420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1421 |TLV Flags=0x10 |Length = 8 | Router ID | 1422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1423 | Router ID | Client ID | 1424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1425 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1426 | |DLEP Status | | 1427 | |sub-TLV (TBD) | | 1428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1429 | Length = 1 | Code | 1430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1432 Message Type - DLEP_MESSAGE (Value TBD) 1434 Message Flags - Set to 0x1 (bit 3, mhasseqnum 1435 bit is set). All other bits are 1436 unused and MUST be set to '0'. 1438 Message Address Length - 0x0 1440 Message Size - 22 + size of optional sub-TLVs. 1442 Message Sequence Number - A 16-bit unsigned integer field 1443 containing a sequence number 1444 generated by the message originator. 1446 TLV Block - TLV Length = 14 + optional sub-TLVs 1447 DLEP Peer Termination order 1448 Identification Sub-TLV (MANDATORY) 1449 Status Sub-TLV (OPTIONAL) 1451 14. Peer Termination ACK Message 1453 The Peer Termination Message ACK is sent by either the client or 1454 the router when a session needs to be terminated. 1456 The Peer Termination ACK Message contains the following fields: 1458 0 1 2 3 1459 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 1460 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1461 | Msg Type = |Msg Flg|AddrLen| Message Size | 1462 | DLEP_MESSAGE | 0x1 | 0x0 | 22 + size of opt | 1463 | (value TBD) | | | sub-TLVs | 1464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1465 | Message Seq Num |TLVs Length =14 + opt sub-TLVs | 1466 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1467 | DLEP Peer Term|TLV Flags=0x10 | Length = 11 + | Sub-TLV type= | 1468 | ACK | | opt sub-TLVs | Identification| 1469 | (Value TBD) | | | sub-TLV (TBD) | 1470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1471 |TLV Flags=0x10 |Length = 8 | Router ID | 1472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1473 | Router ID | Client ID | 1474 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1475 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1476 | |DLEP Status | | 1477 | |sub-TLV (TBD) | | 1478 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1479 | Length = 1 | Code | 1480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1482 Message Type - DLEP_MESSAGE (Value TBD) 1484 Message Flags - Set to 0x1 (bit 3, mhasseqnum 1485 bit is set). All other bits are 1486 unused and MUST be set to '0'. 1488 Message Address Length - 0x0 1490 Message Size - 22 + optional sub-TLVs. 1492 Message Sequence Number - A 16-bit unsigned integer field 1493 containing the sequence number in 1494 the corresponding Peer Termination 1495 Message being acknowledged. 1497 TLV Block - TLV Length = 14 + optional Sub-TLVs 1498 DLEP Peer Termination ACK order 1499 Identification Sub-TLV (MANDATORY) 1500 Status Sub-TLV (OPTIONAL) 1502 15. Neighbor Up Message 1504 The client sends the Neighbor Up message to report that a new 1505 potential routing neighbor has been detected. A Neighbor Up 1506 ACK Message is required to confirm a received Neighbor Up. 1507 The sender of the Neighbor Up Message is free to define its 1508 retry heuristics in event of a timeout. 1510 The Neighbor Up Message contains the following fields: 1512 0 1 2 3 1513 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 1514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1515 | Msg Type = |Msg Flg|AddrLen| Message Size | 1516 | DLEP_MESSAGE | 0x1 | 0x0 | 31 + size of opt | 1517 | (value TBD) | | | sub-TLVs | 1518 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1519 | Message Seq Num |TLVs Length =23 + opt sub-TLVs | 1520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1521 | DLEP Neighbor |TLV Flags=0x10 | Length =20 + | Sub-TLV type= | 1522 | Up (TBD) | | opt sub-TLVs | Identification| 1523 | | | | sub-TLV (TBD) | 1524 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1525 |TLV Flags=0x10 |Length = 8 | Router ID | 1526 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1527 | Router ID | Client ID | 1528 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1529 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1530 | |DLEP MAC | | 1531 | |sub-TLV (TBD) | | 1532 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1533 |Length = 6 | MAC Address | 1534 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1535 | MAC Address |Sub-TLV type= | 1536 | |DLEP IPv4 (TBD)| 1537 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1538 |TLV Flags=0x10 |Length = 5 | Add/Drop Ind. | IPv4 Address | 1539 | | | | | 1540 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1541 | IPv4 Address |Sub-TLV type= | 1542 | |DLEP IPv6 (TBD)| 1543 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1544 | (Continued on next page) | 1545 0 1 2 3 1546 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 1547 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1548 | (Continued from above) | 1549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1550 |TLV Flags=0x10 |Length = 17 | Add/Drop Ind. | IPv6 Address | 1551 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1552 | IPv6 Address | 1553 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1554 | IPv6 Address | 1555 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1556 | IPv6 Address | 1557 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1558 | IPv6 Address |Sub-TLV type= | 1559 | |DLEP MDR (TBD) | 1560 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1561 |TLV Flags=0x10 |Length = 8 | MDR (bps) | 1562 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1563 | MDR (bps) | 1564 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1565 | MDR (bps) |sub-TLV Type = |TLV Flags=0x10 | 1566 | |DLEP CDR (TBD) | | 1567 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1568 |Length = 8 | CDR (bps) | 1569 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1570 | CDR (bps) | 1571 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1572 | CDR (bps) |sub-TLV Type = |TLV Flags=0x10 | Length = 2 | 1573 | |Latency (TBD) | | | 1574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1575 Latency (ms) |sub-TLV Type = |TLV Flags=0x10 | 1576 | |Resources(TBD) | | 1577 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1578 | Length = 1 | Resources |sub-TLV Type = |TLV Flags=0x10 | 1579 | | |DLEP RLQ (TBD) | | 1580 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1581 | Length = 1 | RLQ | 1582 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1584 Message Type - DLEP_MESSAGE (Value TBD) 1586 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1587 is set). All other bits are unused and 1588 MUST be set to '0'. 1590 Message Address Length - 0x0 1592 Message Size - 31 + optional Sub-TLVs 1594 Message Sequence Number - A 16-bit unsigned integer field containing 1595 a sequence number generated by the message 1596 originator. 1598 TLV Block - TLV Length: 23 + optional Sub-TLVs. 1599 DLEP Neighbor Up order 1600 Identification Sub-TLV (MANDATORY) 1601 MAC Address Sub-TLV (MANDATORY) 1602 IPv4 Address Sub-TLV (OPTIONAL) 1603 IPv6 Address Sub-TLV (OPTIONAL) 1604 Maximum Data Rate Sub-TLV (OPTIONAL) 1605 Current Data Rate Sub-TLV (OPTIONAL) 1606 Latency Sub-TLV (OPTIONAL) 1607 Resources Sub-TLV (OPTIONAL) 1608 Relative Link Factor Sub-TLV (OPTIONAL) 1610 16. Neighbor Up ACK Message 1612 The router sends the Neighbor Up ACK Message to indicate whether a 1613 Neighbor Up Message was successfully processed. 1615 The Neighbor Up ACK message contains the following fields: 1617 0 1 2 3 1618 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 1619 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1620 | Msg Type = |Msg Flg|AddrLen| Message Size | 1621 | DLEP_MESSAGE | 0x1 | 0x0 | 35 | 1622 | (value TBD) | | | | 1623 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1624 | Message Seq Num |TLVs Length = 27 | 1625 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1626 | DLEP Neighbor |TLV Flags=0x10 | Length = 24 | Sub-TLV type= | 1627 | Up ACK (TBD) | | | Identification| 1628 | | | | sub-TLV (TBD) | 1629 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1630 |TLV Flags=0x10 |Length = 8 | Router ID | 1631 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1632 | Router ID | Client ID | 1633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1634 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1635 | |DLEP MAC | | 1636 | |sub-TLV (TBD) | | 1637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1638 |Length = 6 | MAC Address | 1639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1640 | MAC Address |Sub-TLV type= | 1641 | |DLEP Status 1642 | |(TBD) | 1643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1644 |TLV Flags=0x10 | Length = 1 | Code | 1645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1647 Message Type - DLEP_MESSAGE (Value TBD) 1648 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1649 is set). All other bits are unused and 1650 MUST be set to '0'. 1652 Message Address Length - 0x0 1654 Message Size - 35 1656 Message Sequence Number - A 16-bit unsigned integer field containing 1657 the sequence number from the Neighbor Down 1658 Message that is being acknowledged. 1660 TLV Block - TLV Length: 27 1662 DLEP Neighbor Up ACK order 1663 Identification Sub-TLV (MANDATORY) 1664 MAC Address Sub-TLV (MANDATORY) 1665 Status Sub-TLV (MANDATORY) 1667 17. Neighbor Down Message 1669 The client sends the Neighbor Down message to report when a neighbor 1670 is no longer reachable from the client. The Neighbor Down message 1671 MUST contain a MAC Address TLV. Any other TLVs present MAY be 1672 ignored. A Neighbor Down ACK Message is required to confirm the 1673 process. The sender of the Neighbor Down message is free to define 1674 its retry heuristics in event of a timeout. 1676 The Neighbor Down Message contains the following fields: 1678 0 1 2 3 1679 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 1680 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1681 | Msg Type = |Msg Flg|AddrLen| Message Size | 1682 | DLEP_MESSAGE | 0x1 | 0x0 | 31 + optional | 1683 | (value TBD) | | | sub-TLV | 1684 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1685 | Message Seq Num | TLVs Length = 23 + optional | 1686 | | Sub-TLV | 1687 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1688 | TLV Type = |TLV Flags=0x10 | Length = 20 + | Sub-TLV type= | 1689 | DLEP Neighbor | | optional Sub- | Identification| 1690 | Down (TBD) | | TLV | sub-TLV (TBD) | 1691 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1692 |TLV Flags=0x10 |Length = 8 | Router ID | 1693 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1694 | Router ID | Client ID | 1695 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1696 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1697 | |DLEP MAC | | 1698 | |sub-TLV (TBD) | | 1699 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1700 | (Continued on next page) | 1701 0 1 2 3 1702 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 1703 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1704 | (Continued from above) | 1705 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1706 |Length = 6 | MAC Address | 1707 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1708 | MAC Address |Sub-TLV type= | 1709 | |DLEP Status 1710 | |(TBD) | 1711 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1712 |TLV Flags=0x10 | Length = 1 | Code | 1713 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1715 Message Type - DLEP_MESSAGE (Value TBD) 1717 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1718 is set). All other bits are unused and 1719 MUST be set to '0'. 1721 Message Address Length - 0x0 1723 Message Size - 31 + optional TLVs 1725 Message Sequence Number - A 16-bit unsigned integer field 1726 containing a sequence number generated 1727 by the message originator. 1729 TLV Block - TLV Length: 23 + optional Sub-TLVs 1731 DLEP Neighbor Down order 1732 Identification Sub-TLV (MANDATORY) 1733 MAC Address Sub-TLV (MANDATORY) 1734 Status Sub-TLV (OPTIONAL) 1736 18. Neighbor Down ACK Message 1738 The router sends the Neighbor Down ACK Message to indicate whether 1739 a Neighbor Down Message was successfully processed. 1741 The Neighbor Down ACK message contains the following fields: 1743 0 1 2 3 1744 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 1745 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1746 | Msg Type = |Msg Flg|AddrLen| Message Size | 1747 | DLEP_MESSAGE | 0x1 | 0x0 | 35 | 1748 | (value TBD) | | | | 1749 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1750 | Message Seq Num |TLVs Length = 27 | 1751 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1752 | DLEP Neighbor |TLV Flags=0x10 | Length = 24 | Sub-TLV type= | 1753 | Down ACK (TBD)| | | Identification| 1754 | | | | sub-TLV (TBD) | 1755 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1756 |TLV Flags=0x10 |Length = 8 | Router ID | 1757 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1758 | Router ID | Client ID | 1759 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1760 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1761 | |DLEP MAC | | 1762 | |sub-TLV (TBD) | | 1763 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1764 |Length = 6 | MAC Address | 1765 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1766 | MAC Address |Sub-TLV type= | 1767 | |DLEP Status 1768 | |(TBD) | 1769 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1770 |TLV Flags=0x10 | Length = 1 | Code | 1771 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1773 Message Type - DLEP_MESSAGE (Value TBD) 1775 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1776 is set). All other bits are unused and 1777 MUST be set to '0'. 1779 Message Address Length - 0x0 1781 Message Size - 35 1783 Message Sequence Number - A 16-bit unsigned integer field containing 1784 the sequence number from the Neighbor Down 1785 Message that is being acknowledged. 1787 TLV Block - TLV Length: 27 1789 DLEP Neighbor Down ACK order 1790 Identification Sub-TLV (MANDATORY) 1791 MAC Address Sub-TLV (MANDATORY) 1792 Status Sub-TLV (MANDATORY) 1794 19. Neighbor Update Message 1796 The client sends the Neighbor Update message when a change in link 1797 metric parameters is detected for a routing neighbor. 1799 The Neighbor Update Message contains the following fields: 1801 0 1 2 3 1802 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 1803 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1804 | Msg Type = |Msg Flg|AddrLen| Message Size | 1805 | DLEP_MESSAGE | 0x1 | 0x0 | 31 + optional | 1806 | (value TBD) | | | sub-TLV | 1807 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1808 | Message Seq Num | TLVs Length = 23 + optional | 1809 | | Sub-TLVs | 1810 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1811 |TLV Type = |TLV Flags=0x10 |Length = 20 + |Sub-TLV type = | 1812 |DLEP Neighbor | |optional Sub- |Identification | 1813 |Update (TBD) | |TLVs |Sub-TLV (TBD) | 1814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1815 |TLV Flags=0x10 |Length = 8 | Router ID | 1816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1817 | Router ID | Client ID | 1818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1819 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1820 | |DLEP MAC | | 1821 | |sub-TLV (TBD) | | 1822 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1823 |Length = 6 | MAC Address | 1824 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1825 | MAC Address |Sub-TLV type= | 1826 | |DLEP MDR (TBD) | 1827 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1828 |TLV Flags=0x10 |Length = 8 | MDR (bps) | 1829 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1830 | MDR (bps) | 1831 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1832 | MDR (bps) |Sub-TLV Type = |TLV Flags=0x10 | 1833 | |DLEP CDR (TBD) | | 1834 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1835 |Length = 8 | CDR (bps) | 1836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1837 | CDR (bps) | 1838 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1839 | CDR (bps) |Sub-TLV Type = |TLV Flags=0x10 | Length = 2 | 1840 | |DLEP Latency | | | 1841 | |(TBD) | | | 1842 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1843 | Latency (ms) |Sub-TLV Type= |TLV Flags=0x10 | 1844 | |DLEP Resources | | 1845 | |(TBD) | | 1846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1847 | (Continued on next page) | 1848 0 1 2 3 1849 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 1850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1851 | (Continued from above) | 1852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1853 | Length = 1 | Resources |Sub-TLV Type= |TLV FLags=0x10 | 1854 | | |DLEP RLQ (TBD) | | 1855 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1856 | Length = 1 | RLQ | 1857 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1859 Message Type - DLEP_MESSAGE (Value TBD) 1861 Message Flags - Set to 0x1 (bit 3, mhasseqnum 1862 bit is set). All other bits are 1863 unused and MUST be set to '0'. 1865 Message Address Length - 0x0 1867 Message Size - 31 + optional TLVs 1869 Message Sequence Number - A 16-bit unsigned integer field 1870 containing a sequence number, 1871 generated by the message originator. 1873 TLV Block - TLVs Length - 23 + optional Sub-TLVs. 1875 DLEP Neighbor Update order 1876 Identification Sub-TLV (MANDATORY) 1877 MAC Address Sub-TLV (MANDATORY) 1878 Maximum Data Rate Sub-TLV (OPTIONAL) 1879 Current Data Rate Sub-TLV (OPTIONAL) 1880 Latency Sub-TLV (OPTIONAL) 1881 Resources Sub-TLV (OPTIONAL) 1882 Relative Link Quality Sub-TLV 1883 (OPTIONAL) 1885 20. Neighbor Address Update Message 1887 The client sends the Neighbor Address Update message when a change 1888 in Layer 3 addressing is detected for a routing neighbor. 1890 The Neighbor Address Update Message contains the following fields: 1892 0 1 2 3 1893 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 1894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1895 | Msg Type = |Msg Flg|AddrLen| Message Size | 1896 | DLEP_MESSAGE | 0x1 | 0x0 | 31 + size of opt | 1897 | (value TBD) | | | sub-TLVs | 1898 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1899 | Message Seq Num |TLVs Length =23 + opt sub-TLVs | 1900 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1901 | (Continued on next page) | 1902 0 1 2 3 1903 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 1904 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1905 | (Continued from above) | 1906 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1907 | DLEP Neighbor |TLV Flags=0x10 | Length =20 + | Sub-TLV type= | 1908 | Address Update| | opt sub-TLVs | Identification| 1909 |(TBD) | | | Sub-TLV (TBD) | 1910 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1911 |TLV Flags=0x10 |Length = 8 | Router ID | 1912 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1913 | Router ID | Client ID | 1914 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1915 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1916 | |DLEP MAC | | 1917 | |sub-TLV (TBD) | | 1918 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1919 |Length = 6 | MAC Address | 1920 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1921 | MAC Address |Sub-TLV type= | 1922 | |DLEP IPv4 (TBD)| 1923 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1924 |TLV Flags=0x10 |Length = 5 | Add/Drop Ind. | IPv4 Address | 1925 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1926 | IPv4 Address |Sub-TLV type= | 1927 | |DLEP IPv6 (TBD)| 1928 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1929 |TLV Flags=0x10 |Length = 17 | Add/Drop Ind. | IPv6 Address | 1930 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1931 | IPv6 Address | 1932 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1933 | IPv6 Address | 1934 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1935 | IPv6 Address | 1936 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1937 | IPv6 Address | 1938 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1940 Message Type - DLEP_MESSAGE (Value TBD) 1942 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit is 1943 set). All other bits are unused and 1944 MUST be set to '0'. 1946 Message Address Length - 0x0 1948 Message Size - 31 + optional TLVs 1950 Message Sequence Number - A 16-bit unsigned integer field 1951 containing a sequence number, 1952 generated by the message originator. 1954 TLV Block - TLVs Length - 23 + optional Sub-TLVs. 1955 DLEP Neighbor Address Update order 1956 Identification Sub-TLV (MANDATORY) 1957 MAC Address Sub-TLV (MANDATORY) 1958 IPv4 Address Sub-TLV (OPTIONAL) 1959 IPv6 Address Sub-TLV (OPTIONAL) 1961 21. Neighbor Address Update ACK Message 1963 The router sends the Neighbor Address Update ACK Message to 1964 indicate whether a Neighbor Address Update Message was 1965 successfully processed. 1967 The Neighbor Address Update ACK message contains the following 1968 fields: 1970 0 1 2 3 1971 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 1972 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1973 | Msg Type = |Msg Flg|AddrLen| Message Size | 1974 | DLEP_MESSAGE | 0x1 | 0x0 | 35 | 1975 | (value TBD) | | | | 1976 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1977 | Message Seq Num |TLVs Length = 27 | 1978 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1979 | DLEP Neighbor |TLV Flags=0x10 | Length = 24 | Sub-TLV type= | 1980 | Address Update| | | Identification| 1981 | ACK (TBD) | | | sub-TLV (TBD) | 1982 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1983 |TLV Flags=0x10 |Length = 8 | Router ID | 1984 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1985 | Router ID | Client ID | 1986 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1987 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 1988 | |DLEP MAC | | 1989 | |sub-TLV (TBD) | | 1990 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1991 |Length = 6 | MAC Address | 1992 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1993 | MAC Address |Sub-TLV type= | 1994 | |DLEP Status 1995 | |(TBD) | 1996 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1997 |TLV Flags=0x10 | Length = 1 | Code | 1998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2000 Message Type - DLEP_MESSAGE (Value TBD) 2002 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 2003 is set). All other bits are unused and 2004 MUST be set to '0'. 2006 Message Address Length - 0x0 2007 Message Size - 35 2009 Message Sequence Number - A 16-bit unsigned integer field containing 2010 the sequence number from the Neighbor Down 2011 Message that is being acknowledged. 2013 TLV Block - TLV Length: 27 2015 DLEP Neighbor Address Update ACK order 2016 Identification Sub-TLV (MANDATORY) 2017 MAC Address Sub-TLV (MANDATORY) 2018 Status Sub-TLV (MANDATORY) 2020 22. Heartbeat Message 2022 A Heartbeat Message is sent by a peer every N seconds, where N is 2023 defined in the "Heartbeat Interval" field of the discovery message. 2024 The message is used by peers to detect when a DLEP session partner 2025 is no longer communicating. Peers SHOULD allow some integral number 2026 of heartbeat intervals (default 4) to expire with no traffic on the 2027 session before initiating DLEP session termination procedures. 2029 The Heartbeat Message contains the following fields: 2031 0 1 2 3 2032 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 2033 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2034 | Msg Type = |Msg Flg|AddrLen| Message Size | 2035 | DLEP_MESSAGE | 0x1 | 0x0 | 22 | 2036 | (value TBD) | | | | 2037 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2038 | Message Seq Num |TLVs Length = 14 | 2039 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2040 | DLEP Heartbeat|TLV Flags=0x10 | Length = 11 | Sub-TLV type= | 2041 | (TBD) | | | Identification| 2042 | | | | sub-TLV (TBD) | 2043 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2044 |TLV Flags=0x10 |Length = 8 | Router ID | 2045 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2046 | Router ID | Client ID | 2047 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2048 | Client ID | 2049 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2051 Message Type - DLEP_MESSAGE (Value TBD) 2053 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit is 2054 set). All other bits are unused and SHOULD 2055 be set to '0'. 2057 Message Address Length - 0x0 2059 Message Size - 22 2060 Message Sequence Number - A 16-bit unsigned integer field containing 2061 a sequence number generated by the message 2062 originator. 2064 TLV Block - TLV Length = 14 2066 DLEP Heartbeat order 2067 Identification Sub-TLV (MANDATORY) 2069 23. Link Characteristics Request Message 2071 The Link Characteristics Request Message is sent by the router to 2072 the modem device when the router detects that a different set of 2073 transmission characteristics is necessary (or desired) for the 2074 type of traffic that is flowing on the link. The request contains 2075 either a Current Data Rate (CDR) TLV to request a different 2076 amount of bandwidth than what is currently allocated, a Latency 2077 TLV to request that traffic delay on the link not exceed the 2078 specified value, or both. A Link Characteristics ACK Message is 2079 required to complete the request. Implementations are free to 2080 define their retry heuristics in event of a timeout. Issuing a 2081 Link Characteristics Request with ONLY the MAC Address TLV is a 2082 mechanism a peer MAY use to request metrics (via the Link 2083 Characteristics ACK) from its partner. 2085 The Link Characteristics Request Message contains the following 2086 fields: 2088 0 1 2 3 2089 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 2090 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2091 | Msg Type = |Msg Flg|AddrLen| Message Size | 2092 | DLEP_MESSAGE | 0x1 | 0x0 | 31 + size of opt | 2093 | (value TBD) | | | sub-TLVs | 2094 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2095 | Message Seq Num |TLVs Length =23 + opt sub-TLVs | 2096 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2097 | DLEP Link Char|TLV Flags=0x10 | Length =20 + | Sub-TLV type= | 2098 | Request (TBD) | | opt sub-TLVs | Identification| 2099 | | | | Sub-TLV (TBD) | 2100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2101 |TLV Flags=0x10 |Length = 8 | Router ID | 2102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2103 | Router ID | Client ID | 2104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2105 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 2106 | |DLEP MAC | | 2107 | |sub-TLV (TBD) | | 2108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2109 |Length = 6 | MAC Address | 2110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2111 | (Continued on next page) | 2112 0 1 2 3 2113 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 2114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2115 | (Continued from above) | 2116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2117 | MAC Address |Sub-TLV type= | 2118 | |DLEP CDR (TBD) | 2119 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2120 |TLV Flags=0x10 |Length = 8 | CDR (bps) | 2121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2122 | CDR (bps) | 2123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2124 | CDR (bps) |Sub-TLV Type= |TLV Flags=0x10 | 2125 | |Latency (TBD) | | 2126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2127 |Length = 2 | Latency (ms) | 2128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2130 Message Type - DLEP_MESSAGE (Value TBD) 2132 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 2133 is set). All other bits are unused and 2134 MUST be set to '0'. 2136 Message Address Length - 0x0 2138 Message Size - 31 + length of optional (Current Data 2139 Rate and/or Latency) Sub-TLVs 2141 Message Sequence Number - A 16-bit unsigned integer field containing 2142 a sequence number generated by the message 2143 originator. 2145 TLV Block - Length: 23 + optional Sub-TLVs 2147 DLEP Link Characteristics Request order 2148 Identification Sub-TLV (MANDATORY) 2149 MAC Address Sub-TLV (MANDATORY) 2151 Current Data Rate Sub-TLV - if present, 2152 this value represents the requested data 2153 rate in bits per second (bps). (OPTIONAL) 2155 Latency TLV - if present, this value 2156 represents the maximum latency, in 2157 milliseconds, desired on the link. 2158 (OPTIONAL) 2160 24. Link Characteristics ACK Message 2162 The Link Characteristics ACK Message is sent by the client to the 2163 router letting the router know the success (or failure) of the 2164 requested change in link characteristics. The Link Characteristics 2165 ACK message SHOULD contain a complete set of metric TLVs. It MUST 2166 contain the same TLV types as the request. The values in the 2167 metric TLVs in the Link Characteristics ACK message MUST reflect 2168 the link characteristics after the request has been processed. 2170 The Link Characteristics ACK Message contains the following fields: 2172 0 1 2 3 2173 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 2174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2175 | Msg Type = |Msg Flg|AddrLen| Message Size | 2176 | DLEP_MESSAGE | 0x1 | 0x0 | 31 + size of opt | 2177 | (value TBD) | | | sub-TLVs | 2178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2179 | Message Seq Num |TLVs Length =23 + opt sub-TLVs | 2180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2181 | DLEP Link Char|TLV Flags=0x10 | Length =20 + | Sub-TLV type= | 2182 | ACK (TBD) | | opt sub-TLVs | Identification| 2183 | | | | Sub-TLV (TBD) | 2184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2185 |TLV Flags=0x10 |Length = 8 | Router ID | 2186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2187 | Router ID | Client ID | 2188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2189 | Client ID |Sub-TLV type= |TLV Flags=0x10 | 2190 | |DLEP MAC | | 2191 | |sub-TLV (TBD) | | 2192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2193 |Length = 6 | MAC Address | 2194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2195 | MAC Address |Sub-TLV type= | 2196 | |DLEP MDR (TBD) | 2197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2198 |TLV Flags=0x10 |Length = 8 | MDR (bps) | 2199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2200 | MDR (bps) | 2201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2202 | MDR (bps) |Sub-TLV Type= |TLV Flags=0x10 | 2203 | |DLEP CDR (TBD) | | 2204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2205 |Length = 8 | CDR (bps) | 2206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2207 | CDR (bps) | 2208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2209 | CDR (bps) |Sub-TLV Type = |TLV Flags=0x10 | Length = 2 | 2210 | |Latency (TBD) | | | 2211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2212 | Latency (ms) |Sub-TLV Type= |TLV Flags=0x10 | 2213 | |Resources (TBD)| | 2214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2215 | Length = 1 | Resources |Sub-TLV Type= |TLV Flags=0x10 | 2216 | | |RLQ (TBD) | | 2217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2218 | Length = 1 | RLQ | 2219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2220 Message Type - DLEP_MESSAGE (Value TBD) 2222 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 2223 is set). All other bits are unused and 2224 MUST be set to '0'. 2226 Message Address Length - 0x0 2228 Message Size - 31 + length of optional (Current Data 2229 Rate and/or Latency) TLVs 2231 Message Sequence Number - A 16-bit unsigned integer field containing 2232 the sequence number that appeared on the 2233 corresponding Link Characteristics Request 2234 message. 2236 TLV Block - TLVs Length = 23 + Optional TLVs 2238 DLEP Link Characteristics ACK order 2239 Identification Sub-TLV (MANDATORY) 2240 MAC Address Sub-TLV (MANDATORY) 2241 Maximum Data Rate Sub-TLV (OPTIONAL) 2243 Current Data Rate Sub-TLV - if present, 2244 this value represents the NEW (or 2245 unchanged, if the request is denied) 2246 Current Data Rate in bits per second (bps). 2247 (OPTIONAL) 2249 Latency Sub-TLV - if present, this value 2250 represents the NEW maximum latency (or 2251 unchanged, if the request is denied), 2252 expressed in milliseconds, on the link. 2253 (OPTIONAL) 2255 Resources Sub-TLV (OPTIONAL) 2257 Relative Link Quality Sub-TLV (OPTIONAL) 2259 25. Security Considerations 2261 The protocol does not contain any mechanisms for security (e.g. 2262 authentication or encryption). The protocol assumes that any 2263 security would be implemented in the underlying transport (for 2264 example, by use of DTLS or some other mechanism), and is 2265 therefore outside the scope of this document. 2267 26. IANA Considerations 2269 This section specifies requests to IANA. 2271 26.1 TLV Registrations 2273 This specification defines: 2275 o One TLV types which must be allocated from the 0-223 range 2276 of the "Assigned Message TLV Types" repository of [RFC5444]. 2278 o A new repository for DLEP orders, with seventeen values currently 2279 assigned. 2281 o A new repository for DLEP Sub-TLV assignments with fifteen values 2282 currently assigned. 2284 26.2 Expert Review: Evaluation Guidelines 2286 For the registries for TLV type extensions where an Expert Review is 2287 required, the designated expert SHOULD take the same general 2288 recommendations into consideration as are specified by [RFC5444]. 2290 26.3 Message TLV Type Registration 2292 The Message TLV specified below must be allocated from the "Message 2293 TLV Types" namespace of [RFC5444]. 2295 o DLEP_MESSAGE 2297 26.4 DLEP Order Registration 2299 A new repository must be created with the values of the DLEP orders. 2300 Valid orders are: 2302 o Attached Peer Discovery Message 2303 o Detached Peer Discovery Message 2304 o Peer Offer Message 2305 o Peer Update Message 2306 o Peer Update ACK Message 2307 o Peer Termination Message 2308 o Peer Termination ACK Message 2309 o Neighbor Up Message 2310 o Neighbor Up ACK Message 2311 o Neighbor Down Message 2312 o Neighbor Down ACK Message 2313 o Neighbor Update Message 2314 o Neighbor Address Update Message 2315 o Neighbor Address Update ACK Message 2316 o Heartbeat Message 2317 o Link Characteristics Request Message 2318 o Link Characteristics ACK Message 2320 This registry should be created according to the guidelines for 2321 'Message-Type-Specific TLV' registration as specified in section 2322 6.2.1 of [RFC5444]. 2324 26.5 DLEP Sub-TLV Type Registrations 2326 A new repository for DLEP Sub-TLVs must be created. Valid Sub-TLVs are: 2328 o Identification Sub-TLV 2329 o DLEP Version Sub-TLV 2330 o Peer Type Sub-TLV 2331 o MAC Address Sub-TLV 2332 o IPv4 Address Sub-TLV 2333 o IPv6 Address Sub-TLV 2334 o Maximum Data Rate Sub-TLV 2335 o Current Data Rate Sub-TLV 2336 o Latency Sub-TLV 2337 o Resources Sub-TLV 2338 o Relative Link Quality Sub-TLV 2339 o Status Sub-TLV 2340 o Heartbeat Interval Sub-TLV 2341 o Heartbeat Threshold Sub-TLV 2342 o Link Characteristics ACK Timer Sub-TLV 2344 It is also requested that the registry allocation contain space 2345 reserved for experimental sub-TLVs. 2347 27. Appendix A. 2349 Peer Level Message Flows 2351 *Modem Device (Client) Restarts Discovery 2353 Router Client Message Description 2354 ==================================================================== 2356 <-------Peer Discovery--------- Modem initiates discovery 2358 ---------Peer Offer-----------> Router detects a problem, sends 2359 w/ Non-zero Status TLV Peer Offer w/ Status TLV indicating 2360 the error. 2362 Modem accepts failure, restarts 2363 discovery process. 2365 <-------Peer Discovery--------- Modem initiates discovery 2367 ---------Peer Offer-----------> Router accepts, sends Peer Offer 2368 w/ Zero Status TLV w/ Status TLV indicating success. 2370 Discovery completed. 2372 *Modem Device Detects Peer Offer Timeout 2374 Router Client Message Description 2375 ==================================================================== 2377 <-------Peer Discovery--------- Modem initiates discovery, 2378 starts a guard timer. 2380 Modem guard timer expires. 2381 Modem restarts discovery process. 2383 <-------Peer Discovery--------- Modem initiates discovery, 2384 starts a guard timer. 2386 ---------Peer Offer-----------> Router accepts, sends Peer Offer 2387 w/ Zero Status TLV w/ Status TLV indicating success. 2389 Discovery completed. 2391 *Router Peer Offer Lost 2393 Router Client Message Description 2394 ==================================================================== 2396 <-------Peer Discovery--------- Modem initiates discovery, 2397 starts a guard timer. 2399 ---------Peer Offer-------|| Router offers availability 2401 Modem times out on Peer Offer, 2402 restarts discovery process. 2404 <-------Peer Discovery--------- Modem initiates discovery 2406 ---------Peer Offer-----------> Router detects subsequent discovery, 2407 internally terminates the previous, 2408 accepts the new association, sends 2409 Peer Offer w/ Status TLV indicating 2410 success. 2412 Discovery completed. 2414 *Discovery Success 2416 Router Client Message Description 2417 ==================================================================== 2419 <-------Peer Discovery--------- Modem initiates discovery 2421 ---------Peer Offer-----------> Router offers availability 2423 -------Peer Heartbeat---------> 2425 <-------Peer Heartbeat--------- 2427 -------Peer Heartbeat---------> 2429 <==============================> Neighbor Sessions 2431 <-------Peer Heartbeat--------- 2433 -------Peer Heartbeat---------> 2435 --------Peer Term Req---------> Terminate Request 2437 <--------Peer Term Res--------- Terminate Response 2439 *Router Detects a Heartbeat timeout 2441 Router Client Message Description 2442 ==================================================================== 2444 <-------Peer Heartbeat--------- 2446 -------Peer Heartbeat---------> 2448 ||---Peer Heartbeat--------- 2450 ~ ~ ~ ~ ~ ~ ~ 2452 -------Peer Heartbeat---------> 2454 ||---Peer Heartbeat--------- 2455 Router Heartbeat Timer expires, 2456 detects missing heartbeats. Router 2457 takes down all neighbor sessions 2458 and terminates the Peer association. 2460 ------Peer Terminate ---------> Peer Terminate Request 2462 Modem takes down all neighbor 2463 sessions, then acknowledges the 2464 Peer Terminate 2466 <----Peer Terminate ACK--------- Peer Terminate ACK 2468 *Modem Detects a Heartbeat timeout 2470 Router Client Message Description 2471 ==================================================================== 2473 <-------Peer Heartbeat--------- 2475 -------Peer Heartbeat------|| 2477 <-------Peer Heartbeat--------- 2479 ~ ~ ~ ~ ~ ~ ~ 2481 -------Peer Heartbeat------|| 2483 <-------Peer Heartbeat--------- 2484 Modem Heartbeat Timer expires, 2485 detects missing heartbeats. Modem 2486 takes down all neighbor sessions 2487 and terminates the Peer association. 2489 <-------Peer Terminate-------- Peer Terminate Request 2491 Router takes down all neighbor 2492 sessions, then acknowledges the 2493 Peer Terminate 2495 ------Peer Terminate ACK-----> Peer Terminate ACK 2497 *Peer Terminate (from Modem) Lost 2499 Router Client Message Description 2500 ==================================================================== 2502 ||------Peer Terminate-------- Modem Peer Terminate Request 2504 Router Heartbeat times out, 2505 terminates association. 2507 --------Peer Terminate-------> Router Peer Terminate 2509 <-----Peer Terminate ACK------ Modem sends Peer Terminate ACK 2511 *Peer Terminate (from router) Lost 2513 Router Client Message Description 2514 ==================================================================== 2516 -------Peer Terminate--------> Router Peer Terminate Request 2518 Modem HB times out, 2519 terminates association. 2521 <------Peer Terminate-------- Modem Peer Terminate 2523 ------Peer Terminate ACK-----> Peer Terminate ACK 2525 Neighbor Level Message Flows 2527 *Modem Neighbor Up Lost 2529 Router Client Message Description 2530 ==================================================================== 2532 ||-----Neighbor Up ------------ Modem sends Neighbor Up 2534 Modem timesout on ACK 2536 <------Neighbor Up ------------ Modem sends Neighbor Up 2538 ------Neighbor Up ACK---------> Router accepts the neighbor 2539 session 2541 <------Neighbor Update--------- Modem Neighbor Metrics 2542 . . . . . . . . 2543 <------Neighbor Update--------- Modem Neighbor Metrics 2545 *Router Detects Duplicate Neighbor Ups 2547 Router Client Message Description 2548 ==================================================================== 2550 <------Neighbor Up ------------ Modem sends Neighbor Up 2552 ------Neighbor Up ACK-------|| Router accepts the neighbor 2553 session 2555 Modem timesout on ACK 2557 <------Neighbor Up ------------ Modem resends Neighbor Up 2559 Router detects duplicate 2560 Neighbor, takes down the 2561 previous, accepts the new 2562 Neighbor. 2564 ------Neighbor Up ACK---------> Router accepts the neighbor 2565 session 2567 <------Neighbor Update--------- Modem Neighbor Metrics 2568 . . . . . . . . 2569 <------Neighbor Update--------- Modem Neighbor Metrics 2571 *Neighbor Up, No Layer 3 Addresses 2573 Router Client Message Description 2574 ==================================================================== 2576 <------Neighbor Up ------------ Modem sends Neighbor Up 2578 ------Neighbor Up ACK---------> Router accepts the neighbor 2579 session 2581 Router ARPs for IPv4 if defined. 2582 Router drives ND for IPv6 if 2583 defined. 2585 <------Neighbor Update--------- Modem Neighbor Metrics 2586 . . . . . . . . 2587 <------Neighbor Update--------- Modem Neighbor Metrics 2589 *Neighbor Up with IPv4, No IPv6 2591 Router Client Message Description 2592 ==================================================================== 2594 <------Neighbor Up ------------ Modem sends Neighbor Up with 2595 the IPv4 TLV 2597 ------Neighbor Up ACK---------> Router accepts the neighbor 2598 session 2600 Router drives ND for IPv6 if 2601 defined. 2603 <------Neighbor Update--------- Modem Neighbor Metrics 2604 . . . . . . . . 2605 <------Neighbor Update--------- Modem Neighbor Metrics 2607 *Neighbor Up with IPv4 and IPv6 2609 Router Client Message Description 2610 ==================================================================== 2612 <------Neighbor Up ------------ Modem sends Neighbor Up with 2613 the IPv4 and IPv6 TLVs 2615 ------Neighbor Up ACK---------> Router accepts the neighbor 2616 session 2618 <------Neighbor Update--------- Modem Neighbor Metrics 2619 . . . . . . . . 2620 <------Neighbor Update--------- Modem Neighbor Metrics 2622 *Neighbor Session Success 2624 Router Client Message Description 2625 ==================================================================== 2627 ---------Peer Offer-----------> Router offers availability 2629 -------Peer Heartbeat---------> 2631 <------Neighbor Up ----------- Modem 2633 ------Neighbor Up ACK--------> Router 2635 <------Neighbor Update--------- Modem 2636 . . . . . . . . 2637 <------Neighbor Update--------- Modem 2639 Modem initiates the terminate 2641 <------Neighbor Down ---------- Modem 2643 ------Neighbor Down ACK-------> Router 2645 or 2647 Router initiates the terminate 2649 ------Neighbor Down ----------> Router 2651 <------Neighbor Down ACK------- Modem 2653 Acknowledgements 2655 The authors would like to acknowledge the influence and contributions 2656 of Chris Olsen and Teco Boot. 2658 Normative References 2660 [RFC5444] Clausen, T., Ed,. "Generalized Mobile Ad Hoc Network (MANET) 2661 Packet/Message Format", RFC 5444, Februar, 2009. 2663 [RFC5578] Berry, B., Ed., "PPPoE with Credit Flow and Metrics", 2664 RFC 5578, February 2010. 2666 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2667 Requirement Levels", RFC 2119, March 1997. 2669 Informative References 2671 [DTLS] Rescorla, E., Ed,. "Datagram Transport Layer Security", 2672 RFC 4347, April 2006. 2674 Author's Addresses 2676 Stan Ratliff 2677 Cisco 2678 170 West Tasman Drive 2679 San Jose, CA 95134 2680 USA 2681 EMail: sratliff@cisco.com 2683 Bo Berry 2684 Cisco 2685 170 West Tasman Drive 2686 San Jose, CA 95134 2687 USA 2688 EMail: boberry@cisco.com 2690 Greg Harrison 2691 Cisco 2692 170 West Tasman Drive 2693 San Jose, CA 95134 2694 USA 2695 EMail: greharri@cisco.com 2697 Shawn Jury 2698 Cisco 2699 170 West Tasman Drive 2700 San Jose, CA 95134 2701 USA 2702 Email: sjury@cisco.com 2704 Darryl Satterwhite 2705 Cisco 2706 170 West Tasman Drive 2707 San Jose, CA 95134 2708 USA 2709 Email: dsatterw@cisco.com