idnits 2.17.1 draft-sratliff-manet-dlep-00.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 44 longer pages, the longest (page 2) being 59 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 45 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 9 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 (October 6, 2010) is 4950 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 2142, 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: April 6, 2011 D. Satterwhite 6 Cisco Systems 7 October 6, 2010 9 Dynamic Link Exchange Protocol (DLEP) 10 draft-sratliff-manet-dlep-00 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 April 6, 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. Generic DLEP Message Format . . . . . . . . . . . . . . . . . 6 70 6. Generic DLEP TLV Block Format . . . . . . . . . . . . . . . . 7 71 7. DLEP TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . 8 72 7.1. Identification TLV . . . . . . . . . . . . . . . . . . . . 8 73 7.2. DLEP Version TLV . . . . . . . . . . . . . . . . . . . . . 9 74 7.3. Peer Type TLV . . . . . . . . . . . . . . . . . . . . . . 10 75 7.4. MAC Address TLV . . . . . . . . . . . . . . . . . . . . . 10 76 7.5. IPv4 Address TLV . . . . . . . . . . . . . . . . . . . . . 11 77 7.6. IPv6 Address TLV . . . . . . . . . . . . . . . . . . . . . 12 78 7.7. Maximum Data Rate TLV. . . . . . . . . . . . . . . . . . . 13 79 7.8. Current Data Rate TLV. . . . . . . . . . . . . . . . . . . 13 80 7.9. Latency TLV. . . . . . . . . . . . . . . . . . . . . . . . 14 81 7.10. Resources TLV. . . . . . . . . . . . . . . . . . . . . . . 15 82 7.11. Relative Link Quality TLV. . . . . . . . . . . . . . . . . 15 83 7.12. Peer Termination TLV . . . . . . . . . . . . . . . . . . . 16 84 8. DLEP Messages. . . . . . . . . . . . . . . . . . . . . . . . . 16 85 8.1. Message TLVs . . . . . . . . . . . . . . . . . . . . . . . 17 86 9. Peer Discovery Messages . . . . . . . . . . . . . . . . . . . 17 87 9.1. Attached Peer Discovery Message . . . . . . . . . . . . . 17 88 9.2. Detached Peer Discovery Message . . . . . . . . . . . . . 19 89 10. Peer Offer Message . . . . . . . . . . . . . . . . . . . . . . 20 90 11. Peer Update Message. . . . . . . . . . . . . . . . . . . . . . 21 91 12. Peer Update ACK Message. . . . . . . . . . . . . . . . . . . . 23 92 13. Peer Termination Message . . . . . . . . . . . . . . . . . . . 23 93 14. Peer Termination ACK Message . . . . . . . . . . . . . . . . . 24 94 15. Neighbor Up Message . . . . . . . . . . . . . . . . . . . . . 26 95 16. Neighbor Up ACK Message. . . . . . . . . . . . . . . . . . . . 27 96 17. Neighbor Down Message . . . . . . . . . . . . . . . . . . . . 28 97 18. Neighbor Down ACK Message. . . . . . . . . . . . . . . . . . . 29 98 19. Neighbor Update Message . . . . . . . . . . . . . . . . . . . 30 99 20. Neighbor Address Update Message. . . . . . . . . . . . . . . . 31 100 21. Neighbor Address Update ACK Message. . . . . . . . . . . . . . 32 101 22. Heartbeat Message . . . . . . . . . . . . . . . . . . . . . . 33 102 23. Link Characteristics Message . . . . . . . . . . . . . . . . . 33 103 24. Link Characteristics ACK Message . . . . . . . . . . . . . . . 35 104 25. Security Considerations. . . . . . . . . . . . . . . . . . . . 36 105 26. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 36 106 26.1 TLV Registrations. . . . . . . . . . . . . . . . . . . . . 36 107 26.2 Expert Review: Evaluation Guidelines . . . . . . . . . . . 37 108 26.3 Packet TLV Type Registrations. . . . . . . . . . . . . . . 37 109 26.4 Message TLV Type Registrations . . . . . . . . . . . . . . 37 110 27. Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . 38 112 1. Introduction 114 There exist today a collection of modem devices that control links of 115 variable bandwidth and quality. Examples of these types of links 116 include line-of-sight (LOS) radios, satellite terminals, and cable/ 117 DSL modems. Fluctuations in speed and quality of these links can 118 occur due to configuration (in the case of cable/DSL modems), or on a 119 moment-to-moment basis, due to physical phenomena like multipath 120 interference, obstructions, rain fade, etc. It is also quite possible 121 that link quality and bandwidth varies with respect to individual 122 neighbors on a link, and with the type of traffic being sent. As an 123 example, consider the case of an 802.11g access point, serving 2 124 associated laptop computers. In this environment, the answer to the 125 question "What is the bandwidth on the 802.11g link?" is "It depends 126 on which associated laptop we're talking about, and on what kind of 127 traffic is being sent." While the first laptop, being physically 128 close to the access point, may have a bandwidth of 54Mbps for 129 unicast traffic, the other laptop, being relatively far away, or 130 obstructed by some object, can simultaneously have a bandwidth of 131 only 32Mbps for unicast. However, for multicast traffic sent from the 132 access point, all traffic is sent at the base transmission rate 133 (which is configurable, but depending on the model of the access 134 point, is usually 24Mbps or less). 136 In addition to utilizing variable bandwidth links, mobile networks 137 are challenged by the notion that link connectivity will come and go 138 over time. Effectively utilizing a relatively short-lived connection 139 is problematic in IP routed networks, as routing protocols tend to 140 rely on independent timers at OSI Layer 3 to maintain network 141 convergence (e.g. HELLO messages and/or recognition of DEAD routing 142 adjacencies). These short-lived connections can be better utilized 143 with an event-driven paradigm, where acquisition of a new neighbor 144 (or loss of an existing one) is somehow signaled, as opposed to a 145 timer-driven paradigm. 147 Another complicating factor for mobile networks are the different 148 methods of physically connecting the modem devices to the router. 149 Modems can be deployed as an interface card in a router's 150 chassis, or as a standalone device connected to the router via 151 Ethernet, USB, or even a serial link. In the case of Ethernet or 152 serial attachment, with existing protocols and techniques, routing 153 software cannot be aware of convergence events occurring on the 154 radio link (e.g. acquisition or loss of a potential routing 155 neighbor), nor can the router be aware of the actual capacity of 156 the link. This lack of awareness, along with the variability in 157 bandwidth, leads to a situation where quality of service (QoS) 158 profiles are extremely difficult to establish and properly 159 maintain. This is especially true of demand-based access schemes 160 such as Demand Assigned Multiple Access (DAMA) implementations 161 used on some satellite systems. With a DAMA-based system, 162 additional bandwidth may be available, but will not be used 163 unless the network devices emit traffic at rate higher than the 164 currently established rate. Increasing the traffic rate does not 165 guarantee additional bandwidth will be allocated; rather, it may 166 result in data loss and additional retransmissions on the link. 168 In attempting to address the challenges listed above, the authors 169 have developed the Data Link Exchange Protocol, or DLEP. The DLEP 170 protocol runs between a router and its attached modem devices, 171 allowing the modem to communicate link characteristics as they 172 change, and convergence events (acquisition and loss of potential 173 routing neighbors). The diagram below is used to illustrate the 174 scope of DLEP sessions. When a local client (Modem device) 175 detects the presence of a remote neighbor, it sends an indication 176 to its local router via the DLEP session. Upon receipt of the 177 indication, the local router would take appropriate action (e.g. 178 initiation of discovery or HELLO protocols) to converge the 179 network. After notification of the new neighbor, the modem device 180 utilizes the DLEP session to report the characteristics of the 181 link (bandwidth, latency, etc) to the router on an as-needed 182 basis. Finally, the Modem is able to use the DLEP session to 183 notify the router when the remote neighbor is lost, shortening 184 the time required to re-converge the network. 186 |-----Local Neighbor-----| |-----Remote Neighbor----| 187 | | | (far-end device) | 189 +--------+ +-------+ +-------+ +--------+ 190 | Router |=======| Modem |{~~~~~~~~}| Modem |=======| Router | 191 | | | Device| | Device| | | 192 +--------+ +-------+ +-------+ +--------+ 194 | | | Link | | | 195 |-DLEP--| | Protocol | |-DLEP--| 196 | | | (e.g. | | | 197 | | | 802.11) | | | 199 Figure 1: DLEP Network 201 DLEP exists as a collection of type-length-value (TLV) based messages 202 formatted using RFC 5444. The protocol can be used for both Ethernet- 203 attached modems (utilizing, for example, a UDP socket for transport 204 of the RFC 5444 packets), or in environments where the modem is an 205 interface card in a chassis (via a message passing scheme). DLEP 206 utilizes a session paradigm between the modem device and its 207 associated router. If multiple modem devices are attached to a 208 router, a separate DLEP session MUST exist for each modem. If a modem 209 device supports multiple connections to a router (via multiple 210 interfaces), or supports connections to multiple routers, a separate 211 DLEP session MUST exist for each connection. 213 1.1 Requirements 215 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 216 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 217 document are to be interpreted as described in BCP 14, RFC 2119 218 [RFC2119]. 220 2. Assumptions 222 In order to implement discovery in the DLEP protocol (thereby 223 avoiding some configuration), we have defined a first-speaker and a 224 passive-listener. Specifically, the router is defined as the passive- 225 listener, and the modem device defined as the first-speaker (e.g. the 226 initiator for discovery). Borrowing from existing terminology, this 227 document refers to the first-speaker as the 'client', even though 228 there is no client/server relationship in the classic sense. 230 DLEP assumes that participating modem devices appear to the router 231 as a transparent bridge - specifically, the assumption is that the 232 destination MAC address for data traffic in any frame emitted by 233 the router should be the MAC address of the next-hop router or end- 234 device, and not the MAC address of any of the intervening modem 235 devices. 237 DLEP assumes that security on the session (e.g. authentication of 238 session partners, encryption of traffic, or both) is dealt with by 239 the underlying transport mechanism for the RFC 5444 packets (e.g. by 240 using a transport such as DTLS [DTLS]). 242 The RFC 5444 message header Sequence Number MUST be included in all 243 DLEP packets. Sequence Numbers start at 1 and are incremented by one 244 for each original and retransmitted message. The unsigned 16-bit 245 Sequence Number rolls over at 65535 to 1. A Sequence Number of 0 is 246 not valid. Peer level Sequence Numbers are unique within the context 247 of a DLEP session. Sequence numbers are used in DLEP to correlate 248 a response to a request. 250 3. Normal Session Flow 252 A session between a router and a client is established by exchanging 253 the "Peer Discovery" and "Peer Offer" messages described below. 255 Once that exchange has successfully occurred, the client informs the 256 router of the presence of a new potential routing partner via the 257 "Neighbor Up" message. The loss of a neighbor is communicated via the 258 "Neighbor Down" message, and link quality is communicated via the 259 "Neighbor Update" message. Note that, due to the issue of metrics 260 varying depending on neighbor (discussed above), DLEP link metrics 261 are expressed within the context of a neighbor relationship, instead 262 of on the link as a whole. 264 Once the DLEP session has started, the session partners exchange 265 heartbeat messages based on a negotiated time interval. The heartbeat 266 messages are used to assure the session partners are in an 267 appropriate state, and that bidirectional connectivity still exists. 269 In addition to receiving metrics about the link, DLEP provides for 270 the ability for the router to request a different amount of 271 bandwidth, or latency, for its client via the Link Characteristics 272 Message. This allows the router to deal with requisite increases 273 (or decreases) of allocated bandwidth/latency in demand-based 274 schemes in a more deterministic manner. 276 4. Generic DLEP Packet Definition 278 The Generic DLEP Packet Definition follows the format for packets 279 defined in RFC 5444. 281 The Generic DLEP Packet Definition contains the following fields: 283 0 1 2 3 284 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 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 |Version| Flags | Packet Sequence Number | Packet TLV | 287 | | | | Block... | 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 | Message... | 290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 292 Version - Version of RFC5444 specification on 293 which the packet/messages/TLVs are 294 constructed. 296 Flags - 4 bit field. Only bit 1 (phastlv) is 297 set/used. All other bits MUST be ignored 298 by DLEP implementations. 300 Packet Sequence Number - If present, the packet sequence number 301 is parsed and ignored. DLEP does NOT 302 use or generate packet sequence numbers. 304 Packet TLV block - a TLV block which contains packet level 305 TLV information. 307 Message - the packet MAY contain zero or more 308 messages. 310 5. Generic DLEP Message Format 312 The Generic DLEP Message Format follows the format for MANET messages 313 defined in RFC 5444. The field, which is OPTIONAL in 314 RFC 5444, MUST exist in all DLEP messages. 316 The Generic DLEP Message Format contains the following fields: 318 0 1 2 3 319 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 320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 | Msg Type |Msg Flg|AddrLen| Message Size | 322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 323 | Message Seq Num | TLV Block... | 324 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 Message Type - an 8-bit field which specifies the type 327 of the message 329 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit is 330 set). All other bits are unused and MUST 331 be set to '0'. 333 Message Address Length - a 4-bit unsigned integer field encoding the 334 length of all addresses included in this 335 message. DLEP implementations do not use 336 this field; contents SHOULD be ignored. 338 Message Size - a 16-bit unsigned integer field which 339 specifies the number of octets that make up 340 the message including the message header. 342 Message Sequence Number - a 16-bit unsigned integer field that 343 contains a sequence number, generated by 344 the originator of the message. Sequence 345 numbers range from 1 to 65535. Sequence 346 numbers roll over at 65535 to 1; 0 is 347 invalid. 349 TLV Block - TLV Block included in the message. 351 6. Generic DLEP TLV Block Format 353 The Generic DLEP TLV Block Format follows the format for MANET 354 message TLVs defined in RFC 5444. 356 The Generic DLEP TLV Block Format contains the following fields: 358 0 1 2 3 359 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 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 | TLVs Length | TLV Type | TLV Flags | 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 | Length | Value... | 364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 366 TLVs Length - a 16-bit unsigned integer field that contains the total 367 number of octets in all of the immediately following 368 TLV elements (tlvs-length not included). 370 TLV Type - an 8-bit unsigned integer field specifying the type of 371 the TLV. 373 TLV Flags - an 8-bit flags bit field. Only bit 3 (thasvalue) is 374 set, all other bits are not used and MUST be set to 375 '0'. 377 Length - Length of the value field of the TLV 379 Value - A field of length which contains data specific 380 to a particular TLV type. 382 7. DLEP TLVs 384 TLV TLV 385 Value Description 386 ========================================= 387 TBD Identification TLV 388 TBD DLEP Version TLV 389 TBD Peer Type TLV 390 TBD MAC Address TLV 391 TBD IPv4 Address TLV 392 TBD IPv6 Address TLV 393 TBD Maximum Data Rate (MDR) TLV 394 TBD Current Data Rate (CDR) TLV 395 TBD Latency TLV 396 TBD Resources TLV 397 TBD Relative Link Quality (RLQ) TLV 398 TBD Status TLV 400 7.1 Identification TLV 402 This TLV MUST be in the Packet Header TLV Block for all DLEP 403 messages. It contains client and router identification information 404 used for all messages contained within the packet. 406 The Identification TLV contains the following fields: 408 0 1 2 3 409 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 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 |TLV Type = TBD |TLV Flags=0x10 |Length = 9 | Dead Interval | 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | Router ID | 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 | Client ID | 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 418 TLV Type - Value TBD 420 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are 421 unused and MUST be set to '0'. 423 Length - 9 425 Dead Interval - An 8-bit, unsigned value containing the maximum 426 number of seconds during which no messages can be 427 received before determining that the session is dead. 428 A value of '0' indicates that the field is ignored. 429 This value is used during the Peer Discovery/Peer 430 Offer exchange. In other packets, the value MUST be 431 ignored. 432 The Dead timer runs at a peer-to-peer level, that is, 433 it runs between a router and a modem device. If a 434 peer does NOT receive any messages for a complete 435 dead interval, it should initiate DLEP session 436 termination procedures. 438 Router ID - indicates the router ID of the DLEP session. 440 Client ID - indicates the client ID of the DLEP session. 442 When the client initiates discovery (via the Peer Discovery message), 443 it MUST set the Client ID to a 32-bit quantity that will be used to 444 uniquely identify this session from the client-side. The client MUST 446 set the Router ID to '0'. When responding to the Peer Discovery 447 message, the router MUST echo the Client ID, and MUST supply its own 448 unique 32-bit quantity to identify the session from the router's 449 perspective. After the Peer Discovery/Peer Offer exchange, both the 450 Client ID and the Router ID MUST be set to the values obtained from 451 the Peer DIscovery/Peer Offer sequence. 453 7.2 DLEP Version TLV 455 The DLEP Version TLV is OPTIONAL, and is used to indicate the client 456 or router version of the protocol. The client and router MAY use this 457 information to decide if the peer is running at a supported level. 459 The DLEP Version 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=4 | Major Version | 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 | Major Version | Minor Version | 467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 469 TLV Type - TBD 471 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are 472 not used and MUST be set to '0'. 474 Length - Length is 4 475 Major Version - Major version of the client or router protocol. 477 Minor Version - Minor version of the client or router protocol. 479 Support of this draft is indicated by setting the Major Version 480 to '1', and the Minor Version to '0' (e.g. Version 1.0). 482 7.3 Peer Type TLV 484 The Peer Type TLV is used by the router and client to give additional 485 information as to its type. It is an OPTIONAL TLV in both the Peer 486 Discovery Message and the Peer Offer message. The peer type is a 487 string and is envisioned to be used for informational purposes (e.g. 488 display command). 490 The Peer Type TLV contains the following fields: 492 0 1 2 3 493 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 494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 495 |TLV Type =TBD |TLV Flags=0x10 |Length= peer |Peer Type Str | 496 | | |type string len|Max Len = 80 | 497 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 499 TLV Type - TBD 501 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits 502 are not used and MUST be set to '0'. 504 Length - length of peer type string (80 bytes maximum) 505 Peer Type String - Non-Null terminated peer type string, maximum 506 length of 80 bytes. For example, a satellite 507 modem might set this variable to 'Satellite 508 terminal'. 510 7.4 MAC Address TLV 512 The MAC address TLV MUST appear in all neighbor-oriented messages 513 (e.g. Neighbor Up, Neighbor Up ACK, Neighbor Down, Neighbor Down 514 ACK, Neighbor Update, Link Characteristics Request, and Link 515 Characteristics ACK). The MAC Address TLV contains the address of 516 the far-end (neighbor) router. 518 The MAC Address TLV contains the following fields: 520 0 1 2 3 521 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 522 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 523 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 524 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 525 | MAC Address | 526 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 527 | MAC Address | 528 +-+-+-+-+-+-+-+-+ 530 TLV Type - TBD 532 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are not 533 used and MUST be set to '0'. 535 Length - 6 537 MAC Address - MAC Address of the far-end router. 539 7.5 IPv4 Address TLV 541 The IPv4 Address TLV MAY be used in Neighbor Up, Neighbor Update, 542 and Peer Update Messages, if the client is aware of the Layer 3 543 address. When included in Neighbor messages, the IPv4 Address TLV 544 contains the IPv4 address of the far-end router (neighbor). In 545 the Peer Update message, it contains the IPv4 address of the local 546 router. In either case, the TLV also contains an indication of 547 whether this is a new or existing address, or is a deletion of 548 a previously known address. 550 The IPv4 Address TLV contains the following fields: 552 0 1 2 3 553 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 554 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 555 |TLV Type =TBD |TLV Flags=0x10 |Length = 4 | Add/Drop | 556 | | | | Indicator | 557 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 558 | IPv4 Address | 559 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 561 TLV Type - TBD 563 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are not 564 used and MUST be set to '0'. 566 Length - 5 567 Add/Drop - Value indicating whether this is a new or 568 Indicator existing address (0x01), or a withdrawal of 569 an address (0x02). 571 IPv4 Address - IPv4 Address of the far-end router. 573 7.6 IPv6 Address TLV 575 The IPv6 Address TLV MAY be used in Neighbor Up, Neighbor Update, 576 and Peer Update Messages, if the client is aware of the Layer 3 577 address. When included in Neighbor messages, the IPv6 Address TLV 578 contains the IPv6 address of the far-end router (neighbor). In 579 the Peer Update, it contains the IPv6 address of the local router. 580 In either case, the TLV also contains an indication of whether 581 this is a new or existing address, or is a deletion of a 582 previously known address. 584 The IPv6 Address TLV contains the following fields: 586 0 1 2 3 587 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 588 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 589 |TLV Type =TBD |TLV Flags=0x10 |Length = 17 | Add/Drop | 590 | | | | Indicator | 591 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 592 | IPv6 Address | 593 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 594 | IPv6 Address | 595 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 596 | IPv6 Address | 597 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 598 | IPv6 Address | 599 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 601 TLV Type - TBD 603 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are not 604 used and MUST be set to '0'. 606 Length - 17 608 Add/Drop - Value indicating whether this is a new or 609 Indicator existing address (0x01), or a withdrawal of 610 an address (0x02). 612 IPv6 Address - IPv6 Address of the far-end router. 614 7.7 Maximum Data Rate TLV 616 The Maximum Data Rate (MDR) TLV is used in Neighbor Up, Neighbor 617 Update, and Link Characteristics ACK Messages to indicate the 618 maximum theoretical data rate, in bits per second, that can be 619 achieved on the link. When metrics are reported via the messages 620 listed above, the maximum data rate MUST be reported. 622 The Maximum Data Rate TLV contains the following fields: 624 0 1 2 3 625 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 626 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 627 |TLV Type =TBD |TLV Flags=0x10 |Length = 8 | MDR (bps) | 628 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 629 | MDR (bps) | 630 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 631 | MDR (bps) | 632 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 634 TLV Type - TBD 636 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other 637 bits are not used and MUST be set to '0'. 639 Length - 8 641 Maximum Data Rate - A 64-bit unsigned number, representing the 642 maximum theoretical data rate, in bits per 643 second (bps), that can be achieved on the 644 link. 646 7.8 Current Data Rate TLV 648 The Current Data Rate (CDR) TLV is used in Neighbor Up, Neighbor 649 Update, Link Characteristics Request, and Link Characteristics ACK 650 messages to indicate the rate at which the link is currently 651 operating, or in the case of the Link Characteristics Request, 652 the desired data rate for the link. 654 The Current Data Rate TLV contains the following fields: 656 0 1 2 3 657 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 658 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 659 |TLV Type =TBD |TLV Flags=0x10 |Length = 8 |CDR (bps) | 660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 661 | CDR (bps) | 662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 663 | CDR (bps) | 664 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 665 TLV Type - TBD 667 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other 668 bits are not used and MUST be set to '0'. 670 Length - 8 672 Current Data Rate - A 64-bit unsigned number, representing the 673 current data rate, in bits per second (bps), 674 on the link. When reporting metrics (e.g, 675 in Neighbor Up, Neighbor Down, or Link 676 Characteristics ACK), if there is no 677 distinction between current and maximum 678 data rates, current data rate SHOULD be 679 set equal to the maximum data rate. 681 7.9 Latency TLV 683 The Latency TLV is used in Neighbor Up, Neighbor Update, Link 684 Characteristics Request, and Link Characteristics ACK messages to 685 indicate the amount of latency on the link, or in the case of the 686 Link Characteristics Request, to indicate the maximum latency 687 required (e.g. a should-not-exeed value) on the link. 689 The Latency TLV contains the following fields: 691 0 1 2 3 692 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 693 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 694 |TLV Type =TBD |TLV Flags=0x10 |Length = 2 |Latency (ms) | 695 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 696 |Latency (ms) | 697 +-+-+-+-+-+-+-+-+ 699 TLV Type - TBD 701 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other 702 bits are not used and MUST be set to '0'. 704 Length - 2 706 Latency - the transmission delay that a packet 707 encounters as it is transmitted over the 708 link. In Neighbor Up, Neighbor Update, 709 and Link Characteristics ACK, this value 710 is reported in absolute delay, in 711 milliseconds. The calculation of latency 712 is modem-device dependent. For example, 713 the latency may be a running average 714 calculated from the internal queuing. If 715 the modem device cannot calculate latency, 716 it SHOULD be reported as 0. 718 In the Link Characteristics Request Message, 719 this value represents the maximum delay, 720 in milliseconds, expected on the link. 722 7.10 Resources TLV 724 The Resources TLV is used in Neighbor Up, Neighbor Update, and Link 725 Characteristics ACK messages to indicate a percentage (0-100) amount 726 of resources (e.g. battery power) remaining on the modem device. 728 The Resources TLV contains the following fields: 729 0 1 2 3 730 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 731 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 732 |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Resources | 733 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 735 TLV Type - TBD 737 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other 738 bits are not used and MUST be set to '0'. 740 Length - 1 742 Resources - a percentage, 0-100, representing the amount 743 of remaining resources, such as battery power. 744 If resources cannot be calculated, a value of 745 100 SHOULD be reported. 747 7.11 Relative Link Quality TLV 749 The Relative Link Quality (RLQ) TLV is used in Neighbor Up, Neighbor 750 Update, and Link Characteristics ACK messages to indicate the 751 quality of the link as calculated by the modem device. 753 The Relative Link Quality TLV contains the following fields: 755 0 1 2 3 756 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 757 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 758 |TLV Type =TBD |TLV Flags=0x10 |Length = 1 |Relative Link | 759 | | | |Quality (RLQ) | 760 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 762 TLV Type - TBD 764 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other 765 bits are not used and MUST be set to '0'. 767 Length - 1 768 Relative Link Quality - a non-dimensional number, 0-100, 769 representing the relative link quality. 770 A value of 100 represents a link of the 771 highest quality. If the RLQ cannot be 772 calculated, a value of 100 should be 773 reported. 775 7.12 Status TLV 777 The Status TLV is sent from either the client or router to 778 indicate the success or failure of a given request 780 The Status TLV contains the following fields: 782 0 1 2 3 783 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 784 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 785 |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Code | 786 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 788 TLV Type - TBD 790 TLV Flags - 0x10, Bit 3 (thasvalue) is set, all other bits are 791 not used and MUST be set to '0'. 793 Length - 1 795 Termination Code - 0 = Success 796 Non-zero = Failure. Specific values of a non- 797 zero termination code depend on the operation 798 requested (e.g. Neighbor Up, Neighbor Down, etc). 800 8. DLEP Messages 802 The DLEP Packet, being based on [RFC5444], contains the following 803 fields: 805 0 1 2 3 806 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 807 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 808 |Version| Flags | TLVs Length | Identification| 809 | 0x0 | 0x2 | | TLV Type = TBD| 810 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 811 |TLV Flags=0x10 | Length = 9 | Dead Interval | Router ID | 812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 813 | Router ID | Client ID | 814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 815 | Client ID | Message (DLEP | 816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 817 | packet can contain zero or more messages) | 818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 819 Version - Version of RFC5444 specification on which the packet/ 820 messages/TLVs are constructed. 822 Flags - 0x2 Only bit 1 (phastlv) is set/used, all other bits are 823 not used and MUST be set to '0'. 825 Packet Header TLV Block which contains: 826 Identification TLV 828 Message - the packet may contain zero or more messages. 830 8.1 Message TLVs 832 TLV TLV 833 Value Description 834 ========================================= 835 TBD Attached Peer Discovery 836 TBD Detached Peer Discovery 837 TBD Peer Offer 838 TBD Peer Update 839 TBD Peer Update ACK 840 TBD Peer Termination 841 TBD Peer Termination ACK 842 TBD Neighbor Up 843 TBD Neighbor Up ACK 844 TBD Neighbor Down 845 TBD Neighbor Down ACK 846 TBD Neighbor Update 847 TBD Neighbor Address Update 848 TBD Neighbor Address Update ACK 849 TBD Heartbeat 850 TBD Link Characteristics Request 851 TBD Link Characteristics ACK 853 9. Peer Discovery Messages 855 There are two different types of Peer Discovery Messages, Attached 856 and Detached. Attached Peer Discovery Messages are sent by the 857 client when it is directly attached to the router (e.g. the client 858 exists as a card in the chassis, or it is connected via Ethernet with 859 no intervening devices). The Detached Peer Discovery message, on the 860 other hand, is sent by a "remote" client -- for example, a client at 861 a satellite hub system might use a Detached Discovery Message in 862 order to act as a proxy for remote ground terminals. To explain in 863 another way, a detached client uses the variable link itself (the 864 radio or satellite link) to establish a DLEP session with a remote 865 router. 867 9.1 Attached Peer Discovery Message 869 The Attached Peer Discovery Message is sent by an attached client 870 to a router to begin a new DLEP association. The Peer Offer message 871 is required to complete the discovery process. The client MAY 872 implement its own retry heuristics in the event it (the client) 873 determines the Attached Peer Discovery Message has timed out. 875 The Attached Peer Discovery Message contains the following fields: 877 0 1 2 3 878 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 879 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 880 | Msg Type |Msg Flg|AddrLen| Message Size | 881 | = TBD | 0x1 | 0x3 |15 + size of opt Peer Type TLV | 882 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 883 | Message Seq Num | TLVs Length = 7 + opt TLVs | 884 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 885 | DLEP Version |TLV Flags=0x10 | Length = 4 | Major Version | 886 | TLV Type = TBD| | | | 887 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 888 | Major Version | Minor Version | Peer Type TLV | 889 | | | Type = TBD | 890 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 891 |TLV Flags=0x10 | Length = Len | Peer Type Str | 892 | |of peer string |MaxLen=80 bytes| 893 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 895 Attached Peer Discovery Message - TBD 897 Message Flags - Set to 0x1 (bit 3, mhasseqnum 898 bit is set). No other bits are 899 used and MUST be set to '0'. 901 Message Address Length - 0x3 903 Message Size - 15 + size of optional Peer Type TLV 905 Message Sequence Number - a 16-bit unsigned integer field 906 containing a sequence number 907 generated by the message 908 originator. 910 TLV Block - TLVs Length: 7 + size of OPTIONAL 911 Peer Type TLV. 912 DLEP Version TLV 913 Peer Type TLV (OPTIONAL) 915 9.2 Detached Peer Discovery Message 917 The Detached Peer Discovery Message is sent by a detached client 918 proxy to a router to begin a new DLEP session. The Peer Offer 919 message is required to complete the discovery process. The client 920 MAY implement its own retry heuristics in the event it (the client) 921 determines the Detached Peer Discovery Message has timed out. 923 The Detached Peer Discovery Message contains the following fields: 925 0 1 2 3 926 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 927 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 928 | Msg Type |Msg Flg|AddrLen| Message Size | 929 | = TBD | 0x1 | 0x3 |15 + size of opt Peer Type TLV | 930 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 931 | Message Seq Num | TLVs Length = 7 + opt TLVs | 932 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 933 | DLEP Version |TLV Flags=0x10 | Length = 4 | Major Version | 934 | TLV Type = TBD| | | | 935 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 936 | Major Version | Minor Version | Peer Type TLV | 937 | | | Type = TBD | 938 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 939 |TLV Flags=0x10 | Length = Len | Peer Type Str | 940 | |of peer string |MaxLen=80 bytes| 941 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 943 Detached Peer Discovery Message Type - TBD 945 Message Flags - Set to 0x1 (bit 3, 946 mhasseqnum bit is set). 947 All other bits are not used 948 and MUST be set to '0'. 950 Message Address Length - 0x3 952 Message Size - 15 + size of optional Peer 953 Type TLV 955 Message Sequence Number - A 16-bit unsigned integer 956 field containing a sequence 957 number, generated by the 958 message originator. 960 TLV Block - TLVs Length: 7 + size of 961 OPTIONAL Peer Type TLV. 962 DLEP Version TLV 963 Peer Type TLV (optional) 965 10. Peer Offer Message 967 The Peer Offer Message is sent by a router to a client or client 968 proxy in response to a Peer Discovery Message. The Peer Offer 969 Message is the response to either of the Peer Discovery messages 970 (either Attached or Detached), and completes the DLEP session 971 establishment. 973 The Peer Offer Message contains the following fields: 975 0 1 2 3 976 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 977 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 978 | Msg Type |Msg Flg|AddrLen| Message Size | 979 | = TBD | 0x1 | 0x3 |15 + size of opt Peer Type TLV | 980 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 981 | Message Seq Num | TLVs Length = 7 + opt TLVs | 982 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 983 | DLEP Version |TLV Flags=0x10 | Length = 4 | Major Version | 984 | TLV Type = TBD| | | | 985 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 986 | Major Version | Minor Version | Peer Type TLV | 987 | | | Type = TBD | 988 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 989 |TLV Flags=0x10 | Length = Len | Peer Type Str |TLV Type = TBD | 990 | |of peer string |MaxLen=80 bytes| | 991 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 992 |TLV Flags=0x10 |Length = 5 | Add/Drop Ind. | IPv4 Address | 993 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 994 | IPv4 Address |TLV Type = TBD | 995 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 996 |TLV Flags=0x10 |Length = 17 | Add/Drop Ind. | IPv6 Address | 997 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 998 | IPv6 Address | 999 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1000 | IPv6 Address | 1001 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1002 | IPv6 Address | 1003 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1004 | IPv6 Address |TLV Type = TBD | 1005 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1006 |TLV Flags=0x10 | Length = 1 | Code | 1007 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1009 Peer Offer Message Type - TBD 1011 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1012 is set). All other bits are unused and 1013 MUST be set to '0'. 1015 Message Address Length - 0x3 1017 Message Size - 15 + size of optional Peer Type TLV 1018 Message Sequence Number - A 16-bit unsigned integer field containing 1019 a sequence number, generated by the message 1020 originator. 1022 TLV Block - TLV Length: 7 + size of optional Peer Type 1023 TLV. 1024 DLEP Version TLV 1025 Peer Type TLV (OPTIONAL) 1026 IPv4 Address TLV (OPTIONAL) 1027 IPv6 Address TLV (OPTIONAL) 1028 Status TLV (OPTIONAL) 1030 11. Peer Update Message 1032 The Peer Update message is sent by the router to indicate local 1033 Layer 3 address changes. For example, addition of an IPv4 address 1034 to the router would prompt a Peer Update message to its attached 1035 DLEP clients. If the modem device is capable of understanding and 1036 forwarding this information, the address update would prompt any 1037 remote DLEP clients (DLEP clients that are on the far-end of the 1038 variable link) to issue a "Neighbor Update" message to their local 1039 routers, with the address change information. Clients that do not 1040 track Layer 3 addresses MUST silently ignore the Peer Update 1041 Message. Clients that track Layer 3 addresses MUST acknowledge the 1042 Peer Update with a Peer Update ACK message. Routers MAY employ 1043 heuristics to retransmit Peer Update messages. Sending of Peer 1044 Update Messages SHOULD cease when a router implementation 1045 determines that a partner modem device does NOT support Layer 3 1046 address tracking. 1048 The Peer Update Message contains the following fields: 1050 0 1 2 3 1051 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 1052 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1053 | Msg Type |Msg Flg|AddrLen| Message Size | 1054 | = TBD | 0x1 | 0x3 | 8 + opt TLVs | 1055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1056 | Message Seq Num | TLVs Length = length of opt | 1057 | | TLVs | 1058 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1059 |TLV Type =TBD |TLV Flags=0x10 |Length = 5 | Add/Drop Ind. | 1060 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1061 | IPv4 Address | 1062 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1063 |TLV Type =TBD |TLV Flags=0x10 |Length = 17 | Add/Drop Ind. | 1064 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1065 | IPv6 Address | 1066 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1067 | IPv6 Address | 1068 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1069 | IPv6 Address | 1070 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1071 | IPv6 Address | 1072 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1074 Peer Update Message Type - TBD 1076 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1077 is set). All other bits are unused and 1078 MUST be set to '0'. 1080 Message Address Length - 0x3 1082 Message Size - 8 + optional TLVs 1084 Message Sequence Number - A 16-bit unsigned integer field containing 1085 a sequence number generated by the message 1086 originator. 1088 TLV Block - TLV Length: length of optional TLVs. 1089 IPv4 Address TLV (OPTIONAL) 1090 IPv6 Address TLV (OPTIONAL) 1092 12. Peer Update ACK Message 1094 The client sends the Peer Update ACK Message to indicate whether a 1095 Peer Update Message was successfully processed. 1097 The Peer Update ACK message contains the following fields: 1099 0 1 2 3 1100 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 1101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1102 | Msg Type |Msg Flg|AddrLen| Message Size | 1103 | = TBD | 0x1 | 0x3 | 12 | 1104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1105 | Message Seq Num | TLVs Length = 4 | 1106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1107 |TLV Type =TBD |TLV Flags=0x10 |Length = 1 | Code | 1108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1110 Peer Update ACK 1111 Message Type - TBD 1113 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1114 is set). All other bits are unused and 1115 MUST be set to '0'. 1117 Message Address Length - 0x3 1119 Message Size - 12 1121 Message Sequence Number - A 16-bit unsigned integer field containing 1122 the sequence number from the Neighbor Up 1123 Message that is being acknowledged. 1125 TLV Block - TLV Length: 4 1126 Status TLV 1128 13. Peer Termination Message 1130 The Peer Termination Message is sent by either the client or the 1131 router when a session needs to be terminated. Transmission of a 1132 Peer Termination ACK message is required to confirm the 1133 termination process. The sender of the Peer Termination message 1134 is free to define its heuristics in event of a timeout. The 1135 receiver of a Peer Termination Message MUST terminate all 1136 neighbor relationships and release associated resources. No 1137 Neighbor Down messages are sent. 1139 The Peer Termination Message contains the following fields: 1141 0 1 2 3 1142 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 1143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1144 | Msg Type |Msg Flg|AddrLen| Message Size | 1145 | = TBD | 0x1 | 0x3 | 12 | 1146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1147 | Message Seq Num | TLVs Length = 4 | 1148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1149 |TLV Type = TDB |TLV Flags=0x10 | Length = 1 | Code | 1150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1152 Peer Termination Message Type - TBD 1154 Message Flags - Set to 0x1 (bit 3, mhasseqnum 1155 bit is set). All other bits are 1156 unused and MUST be set to '0'. 1158 Message Address Length - 0x3 1160 Message Size - 12 1162 Message Sequence Number - A 16-bit unsigned integer field 1163 containing a sequence number 1164 generated by the message originator. 1166 TLV Block - TLV Length = 4. 1167 Status TLV 1169 14. Peer Termination ACK Message 1171 The Peer Termination Message ACK is sent by either the client or 1172 the router when a session needs to be terminated. 1174 The Peer Termination ACK Message contains the following fields: 1176 0 1 2 3 1177 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 1178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1179 | Msg Type |Msg Flg|AddrLen| Message Size | 1180 | = TBD | 0x1 | 0x3 | 12 | 1181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1182 | Message Seq Num | TLVs Length = 4 | 1183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1184 |TLV Type = TDB |TLV Flags=0x10 | Length = 1 | Code | 1185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1187 Peer Termination ACK 1188 Message Type - TBD 1189 Message Flags - Set to 0x1 (bit 3, mhasseqnum 1190 bit is set). All other bits are 1191 unused and MUST be set to '0'. 1193 Message Address Length - 0x3 1195 Message Size - 12 1197 Message Sequence Number - A 16-bit unsigned integer field 1198 containing the sequence number in 1199 the corresponding Peer Termination 1200 Message being acknowledged. 1202 TLV Block - TLV Length = 4. 1203 Status TLV 1205 15. Neighbor Up Message 1207 The client sends the Neighbor Up message to report that a new 1208 potential routing neighbor has been detected. A Neighbor Up 1209 ACK Message is required to confirm a received Neighbor Up. 1210 The sender of the Neighbor Up Message is free to define its 1211 retry heuristics in event of a timeout. 1213 The Neighbor Up Message contains the following fields: 1215 0 1 2 3 1216 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 1217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1218 | Msg Type |Msg Flg|AddrLen| Message Size | 1219 | = TBD | 0x1 | 0x3 | 17 + opt TLVs | 1220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1221 | Message Seq Num | TLVs Length = 9 + opt TLVs | 1222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1223 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 1224 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1225 | MAC Address | 1226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1227 | MAC Address |TLV Type =TBD |TLV Flags=0x10 |Length = 5 | 1228 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1229 | Add/Drop Ind. | IPv4 Address | 1230 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1231 |IPv4 Address |TLV Type =TBD |TLV Flags=0x10 |Length = 17 | 1232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1233 | Add/Drop Ind. | IPv6 Address | 1234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1235 | IPv6 Address | 1236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1237 | IPv6 Address | 1238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1239 | IPv6 Address | 1240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1241 |IPv6 Address |TLV Type = TBD |TLV Flags=0x10 |Length = 8 | 1242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1243 | MDR (bps) | 1244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1245 | MDR (bps) | 1246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1247 |TLV Type = TBD |TLV Flags=0x10 |Length = 8 | CDR (bps) | 1248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1249 | CDR (bps) | 1250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1251 | CDR (bps) |TLV Type = TBD | 1252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1253 |TLV Flags=0x10 |Length = 2 | Latency (ms) | 1254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1255 |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | Resources | 1256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1257 |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | RLQ | 1258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1259 Neighbor Up Message Type - TBD 1261 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1262 is set). All other bits are unused and 1263 MUST be set to '0'. 1265 Message Address Length - 0x3 1267 Message Size - 17 + optional TLVs 1269 Message Sequence Number - A 16-bit unsigned integer field containing 1270 a sequence number generated by the message 1271 originator. 1273 TLV Block - TLV Length: 9 + optional TLVs. 1274 MAC Address TLV (MANDATORY) 1275 IPv4 Address TLV (OPTIONAL) 1276 IPv6 Address TLV (OPTIONAL) 1277 Maximum Data Rate TLV (OPTIONAL) 1278 Current Data Rate TLV (OPTIONAL) 1279 Latency TLV (OPTIONAL) 1280 Resources TLV (OPTIONAL) 1281 Relative Link Factor TLV (OPTIONAL) 1283 16. Neighbor Up ACK Message 1285 The router sends the Neighbor Up ACK Message to indicate whether a 1286 Neighbor Up Message was successfully processed. 1288 The Neighbor Up ACK message contains the following fields: 1290 0 1 2 3 1291 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 1292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1293 | Msg Type |Msg Flg|AddrLen| Message Size | 1294 | = TBD | 0x1 | 0x3 | 21 | 1295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1296 | Message Seq Num | TLVs Length = 13 | 1297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1298 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 1299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1300 | MAC Address | 1301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1302 | MAC Address |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | 1303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1304 | Code | 1305 +-+-+-+-+-+-+-+-+ 1307 Neighbor Up ACK 1308 Message Type - TBD 1309 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1310 is set). All other bits are unused and 1311 MUST be set to '0'. 1313 Message Address Length - 0x3 1315 Message Size - 21 1317 Message Sequence Number - A 16-bit unsigned integer field containing 1318 the sequence number from the Neighbor Down 1319 Message that is being acknowledged. 1321 TLV Block - TLV Length: 13 1322 MAC Address TLV (MANDATORY) 1323 Status TLV (MANDATORY) 1325 17. Neighbor Down Message 1327 The client sends the Neighbor Down message to report when a neighbor 1328 is no longer reachable from the client. The Neighbor Down message 1329 MUST contain a MAC Address TLV. Any other TLVs present MAY be 1330 ignored. A Neighbor Down ACK Message is required to confirm the 1331 process. The sender of the Neighbor Down message is free to define 1332 its retry heuristics in event of a timeout. 1334 The Neighbor Down Message contains the following fields: 1336 0 1 2 3 1337 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 1338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1339 | Msg Type |Msg Flg|AddrLen| Message Size | 1340 | = TBD | 0x1 | 0x3 | 17 + optional TLVs | 1341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1342 | Message Seq Num | TLVs Length = 9 + optional | 1343 | | TLVs | 1344 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1345 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 1346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1347 | MAC Address | 1348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1349 | MAC Address |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | 1350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1351 | Code | 1352 +-+-+-+-+-+-+-+-+ 1354 Neighbor Down Message Type - TBD 1356 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1357 is set). All other bits are unused and 1358 MUST be set to '0'. 1360 Message Address Length - 0x3 1361 Message Size - 17 + optional TLVs 1363 Message Sequence Number - A 16-bit unsigned integer field 1364 containing a sequence number generated 1365 by the message originator. 1367 TLV Block - TLV Length: 9 + optional TLVs 1368 MAC Address TLV (MANDATORY) 1369 Status TLV (OPTIONAL) 1371 18. Neighbor Down ACK Message 1373 The router sends the Neighbor Down ACK Message to indicate whether 1374 a Neighbor Down Message was successfully processed. 1376 The Neighbor Down ACK message contains the following fields: 1378 0 1 2 3 1379 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 1380 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1381 | Msg Type |Msg Flg|AddrLen| Message Size | 1382 | = TBD | 0x1 | 0x3 | 21 | 1383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1384 | Message Seq Num | TLVs Length = 13 | 1385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1386 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 1387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1388 | MAC Address | 1389 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1390 | MAC Address |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | 1391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1392 | Code | 1393 +-+-+-+-+-+-+-+-+ 1395 Neighbor Down ACK 1396 Message Type - TBD 1398 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1399 is set). All other bits are unused and 1400 MUST be set to '0'. 1402 Message Address Length - 0x3 1404 Message Size - 21 1406 Message Sequence Number - A 16-bit unsigned integer field containing 1407 the sequence number from the Neighbor Down 1408 Message that is being acknowledged. 1410 TLV Block - TLV Length: 13 1411 MAC Address TLV (MANDATORY) 1412 Status TLV (MANDATORY) 1414 19. Neighbor Update Message 1416 The client sends the Neighbor Update message when a change in link 1417 metric parameters is detected for a routing neighbor. 1419 The Neighbor Update Message contains the following fields: 1421 0 1 2 3 1422 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 1423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1424 | Msg Type |Msg Flg|AddrLen| Message Size | 1425 | = TBD | 0x1 | 0x3 | 17 + opt TLVs | 1426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1427 | Message Seq Num | TLVs Length = 9 + opt TLVs | 1428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1429 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 1430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1431 | MAC Address | 1432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1433 | MAC Address |TLV Type = TBD |TLV Flags=0x10 |Length = 8 | 1434 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1435 | MDR (bps) | 1436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1437 | MDR (bps) | 1438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1439 |TLV Type = TBD |TLV Flags=0x10 |Length = 8 | CDR (bps) | 1440 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1441 | CDR (bps) | 1442 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1443 | CDR (bps) |TLV Type = TBD | 1444 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1445 |TLV Flags=0x10 |Length = 2 | Latency (ms) | 1446 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1447 |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | Resources | 1448 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1449 |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | RLQ | 1450 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1452 Neighbor Update Message Type - TBD 1454 Message Flags - Set to 0x1 (bit 3, mhasseqnum 1455 bit is set). All other bits are 1456 unused and MUST be set to '0'. 1458 Message Address Length - 0x3 1460 Message Size - 17 + optional TLVs 1462 Message Sequence Number - A 16-bit unsigned integer field 1463 containing a sequence number, 1464 generated by the message originator. 1466 TLV Block - TLVs Length - 9 + optional TLVs. 1467 MAC Address TLV (MANDATORY) 1468 Maximum Data Rate TLV (OPTIONAL) 1469 Current Data Rate TLV (OPTIONAL) 1470 Latency TLV (OPTIONAL) 1471 Resources TLV (OPTIONAL) 1472 Relative Link Quality TLV (OPTIONAL) 1474 20. Neighbor Address Update Message 1476 The client sends the Neighbor Address Update message when a change 1477 in Layer 3 addressing is detected for a routing neighbor. 1479 The Neighbor Address Update Message contains the following fields: 1481 0 1 2 3 1482 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 1483 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1484 | Msg Type |Msg Flg|AddrLen| Message Size | 1485 | = TBD | 0x1 | 0x3 | 17 + opt TLVs | 1486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1487 | Message Seq Num | TLVs Length = 9 + opt TLVs | 1488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1489 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 1490 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1491 | MAC Address | 1492 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1493 | MAC Address |TLV Type =TBD |TLV Flags=0x10 |Length = 5 | 1494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1495 | Add/Drop Ind. | IPv4 Address | 1496 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1497 |IPv4 Address |TLV Type =TBD |TLV Flags=0x10 |Length = 17 | 1498 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1499 | Add/Drop Ind. | IPv6 Address | 1500 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1501 | IPv6 Address | 1502 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1503 | IPv6 Address | 1504 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1505 | IPv6 Address | 1506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1508 Neighbor Address Update 1509 Message Type - TBD 1511 Message Flags - Set to 0x1 (bit 3, mhasseqnum 1512 bit is set). All other bits are 1513 unused and MUST be set to '0'. 1515 Message Address Length - 0x3 1516 Message Size - 17 + optional TLVs 1518 Message Sequence Number - A 16-bit unsigned integer field 1519 containing a sequence number, 1520 generated by the message originator. 1522 TLV Block - TLVs Length - 9 + optional TLVs. 1523 MAC Address TLV (MANDATORY) 1524 IPv4 Address TLV (OPTIONAL) 1525 IPv6 Address TLV (OPTIONAL) 1527 21. Neighbor Address Update ACK Message 1529 The router sends the Neighbor Address Update ACK Message to 1530 indicate whether a Neighbor Address Update Message was 1531 successfully processed. 1533 The Neighbor Address Update ACK message contains the following 1534 fields: 1536 0 1 2 3 1537 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 1538 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1539 | Msg Type |Msg Flg|AddrLen| Message Size | 1540 | = TBD | 0x1 | 0x3 | 21 | 1541 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1542 | Message Seq Num | TLVs Length = 13 | 1543 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1544 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 1545 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1546 | MAC Address | 1547 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1548 | MAC Address |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | 1549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1550 | Code | 1551 +-+-+-+-+-+-+-+-+ 1553 Neighbor Address Update 1554 ACK Message Type - TBD 1556 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1557 is set). All other bits are unused and 1558 MUST be set to '0'. 1560 Message Address Length - 0x3 1562 Message Size - 21 1564 Message Sequence Number - A 16-bit unsigned integer field containing 1565 the sequence number from the Neighbor Down 1566 Message that is being acknowledged. 1568 TLV Block - TLV Length: 13 1569 MAC Address TLV (MANDATORY) 1570 Status TLV (MANDATORY) 1572 22. Heartbeat Message 1574 A Heartbeat Message is sent by a peer every N seconds where no 1575 messages have been received on the DLEP session. The message is 1576 used by peers to detect when a DLEP session partner is no longer 1577 communicating. When the (N * 2) timeout expires, the peer should 1578 initiate DLEP session termination procedures. 1580 The Heartbeat Message contains the following fields: 1582 0 1 2 3 1583 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 1584 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1585 | Msg Type |Msg Flg|AddrLen| Message Size = 8 | 1586 | = TBD | 0x1 | 0x3 | | 1587 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1588 | Message Seq Num | TLVs Length = 0 | 1589 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1591 Message Type - TBD 1593 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit is 1594 set). All other bits are unused and SHOULD 1595 be set to '0'. 1597 Message Address Length - 0x3 1599 Message Size - 8 1601 Message Sequence Number - A 16-bit unsigned integer field containing 1602 a sequence number generated by the message 1603 originator. 1604 TLV Block - TLV Length = 0 1606 23. Link Characteristics Request Message 1608 The Link Characteristics Request Message is sent by the router to 1609 the modem device when the router detects that a different set of 1610 transmission characteristics is necessary (or desired) for the 1611 type of traffic that is flowing on the link. The request contains 1612 either a Current Data Rate (CDR) TLV to request a different 1613 amount of bandwidth than what is currently allocated, a Latency 1614 TLV to request that traffic delay on the link not exceed the 1615 specified value, or both. A Link Characteristics ACK Message is 1616 required to complete the request. Implementations are free to 1617 define their retry heuristics in event of a timeout. Issuing a 1618 Link Characteristics Request with ONLY the MAC Address TLV is a 1619 mechanism a peer MAY use to request metrics (via the Link 1620 Characteristics ACK) from its partner. 1622 The Link Characteristics Request Message contains the following 1623 fields: 1625 0 1 2 3 1626 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 1627 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1628 | Msg Type |Msg Flg|AddrLen| Message Size = 8 + Length | 1629 | = TBD | 0x1 | 0x3 | of optional TLVs | 1630 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1631 | Message Seq Num | TLVs Length = | 1632 | | 9 + Optional TLVs | 1633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1634 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 1635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1636 | MAC Address | 1637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1638 | MAC Address |TLV Type =TBD |TLV Flags=0x10 |Length = 8 | 1639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1640 | CDR (bps) | 1641 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1642 | CDR (bps) | 1643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1644 |TLV Type = TBD |TLV Flags=0x10 |Length = 2 | Latency (ms) | 1645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1646 | Latency (ms) | 1647 +-+-+-+-+-+-+-+-+ 1649 Message Type - TBD 1651 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1652 is set). All other bits are unused and 1653 MUST be set to '0'. 1655 Message Address Length - 0x3 1657 Message Size - 8 + length of optional (Current Data 1658 Rate and/or Latency) TLVs 1660 Message Sequence Number - A 16-bit unsigned integer field containing 1661 a sequence number generated by the message 1662 originator. 1664 TLV Block - TLVs Length 1666 MAC Address TLV (MANDATORY) 1668 Current Data Rate TLV - if present, this 1669 value represents the requested data rate 1670 in bits per second (bps). (OPTIONAL) 1671 Latency TLV - if present, this value 1672 represents the maximum latency, in 1673 milliseconds, desired on the link. 1674 (OPTIONAL) 1676 24. Link Characteristics ACK Message 1678 The Link Characteristics ACK Message is sent by the client to the 1679 router letting the router know the success (or failure) of the 1680 requested change in link characteristics. The Link Characteristics 1681 ACK message SHOULD contain a complete set of metric TLVs. It MUST 1682 contain the same TLV types as the request. The values in the 1683 metric TLVs in the Link Characteristics ACK message MUST reflect 1684 the link characteristics after the request has been processed. 1686 The Link Characteristics ACK Message contains the following fields: 1688 0 1 2 3 1689 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 1690 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1691 | Msg Type |Msg Flg|AddrLen| Message Size = 8 + Length | 1692 | = TBD | 0x1 | 0x3 | of additional TLVs | 1693 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1694 | Message Seq Num | TLVs Length = 9 + optional | 1695 | | TLVs | 1696 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1697 |TLV Type =TBD |TLV Flags=0x10 |Length = 6 |MAC Address | 1698 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1699 | MAC Address | 1700 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1701 | MAC Address |TLV Type =TBD |TLV Flags=0x10 |Length = 8 | 1702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1703 | MDR (bps) | 1704 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1705 | MDR (bps) | 1706 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1707 |TLV Type = TBD |TLV Flags=0x10 |Length = 8 | CDR (bps) | 1708 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1709 | CDR (bps) | 1710 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1711 | CDR (bps) |TLV Type = TBD | 1712 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1713 |TLV Flags=0x10 |Length = 2 | Latency (ms) | 1714 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1715 |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | Resources | 1716 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1717 |TLV Type = TBD |TLV Flags=0x10 | Length = 1 | RLQ | 1718 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1720 Message Type - TBD 1721 Message Flags - Set to 0x1 (bit 3, mhasseqnum bit 1722 is set). All other bits are unused and 1723 MUST be set to '0'. 1725 Message Address Length - 0x3 1727 Message Size - 8 + length of optional (Current Data 1728 Rate and/or Latency) TLVs 1730 Message Sequence Number - A 16-bit unsigned integer field containing 1731 the sequence number that appeared on the 1732 corresponding Link Characteristics Request 1733 message. 1735 TLV Block - TLVs Length = 9 + Optional TLVs 1737 MAC Address TLV (MANDATORY) 1739 Maximum Data Rate TLV (OPTIONAL) 1741 Current Data Rate TLV - if present, this 1742 value represents the NEW (or unchanged, 1743 if the request is denied) Current Data 1744 Rate in bits per second (bps). (OPTIONAL) 1746 Latency TLV - if present, this value 1747 represents the NEW maximum latency (or 1748 unchanged, if the request is denied), 1749 expressed in milliseconds, on the link. 1750 (OPTIONAL) 1752 Resources TLV (OPTIONAL) 1754 Relative Link Quality TLV (OPTIONAL) 1756 25. Security Considerations 1758 The protocol does not contain any mechanisms for security (e.g. 1759 authentication or encryption). The protocol assumes that any 1760 security would be implemented in the underlying transport (for 1761 example, by use of DTLS or some other mechanism), and is 1762 therefore outside the scope of this document. 1764 26. IANA Considerations 1766 This section specifies requests to IANA. 1768 26.1 TLV Registrations 1770 This specification defines: 1772 o Twelve TLV types which must be allocated from the 0-223 range 1773 of the "Assigned Packet TLV Types" repository of [RFC5444]. 1775 o Seventeen Message types which must be allocated from the 0-127 1776 range of the "Assigning Message TLV Types" repository of 1777 [RFC5444]. 1779 26.2 Expert Review: Evaluation Guidelines 1781 For the registries for TLV type extensions where an Expert Review is 1782 required, the designated expert SHOULD take the same general 1783 recommendations into consideration as are specified by [RFC5444]. 1785 26.3 Packet TLV Type Registrations 1787 The Packet TLVs specified below must be allocated from the "Packet 1788 TLV Types" namespace of [RFC5444]. 1790 o Identification TLV 1791 o DLEP Version TLV 1792 o Peer Type TLV 1793 o MAC Address TLV 1794 o IPv4 Address TLV 1795 o IPv6 Address TLV 1796 o Maximum Data Rate TLV 1797 o Current Data Rate TLV 1798 o Latency TLV 1799 o Resources TLV 1800 o Relative Link Quality TLV 1801 o Status TLV 1803 26.4 Message TLV Type Registrations 1805 The Message TLVs specified below must be allocated from the 1806 "Message TLV Types" namespace of [RFC5444]. 1808 o Attached Peer Discovery Message 1809 o Detached Peer Discovery Message 1810 o Peer Offer Message 1811 o Peer Update Message 1812 o Peer Update ACK Message 1813 o Peer Termination Message 1814 o Peer Termination ACK Message 1815 o Neighbor Up Message 1816 o Neighbor Up ACK Message 1817 o Neighbor Down Message 1818 o Neighbor Down ACK Message 1819 o Neighbor Update Message 1820 o Neighbor Address Update Message 1821 o Neighbor Address Update ACK Message 1822 o Heartbeat Message 1823 o Link Characteristics Request Message 1824 o Link Characteristics ACK Message 1826 27. Appendix A. 1828 Peer Level Message Flows 1830 *Modem Device (Client) Restarts Discovery 1832 Router Client Message Description 1833 ==================================================================== 1835 <-------Peer Discovery--------- Modem initiates discovery 1837 ---------Peer Offer-----------> Router detects a problem, sends 1838 w/ Non-zero Status TLV Peer Offer w/ Status TLV indicating 1839 the error. 1841 Modem accepts failure, restarts 1842 discovery process. 1844 <-------Peer Discovery--------- Modem initiates discovery 1846 ---------Peer Offer-----------> Router accepts, sends Peer Offer 1847 w/ Zero Status TLV w/ Status TLV indicating success. 1849 Discovery completed. 1851 *Modem Device Detects Peer Offer Timeout 1853 Router Client Message Description 1854 ==================================================================== 1856 <-------Peer Discovery--------- Modem initiates discovery, 1857 starts a guard timer. 1859 Modem guard timer expires. 1860 Modem restarts discovery process. 1862 <-------Peer Discovery--------- Modem initiates discovery, 1863 starts a guard timer. 1865 ---------Peer Offer-----------> Router accepts, sends Peer Offer 1866 w/ Zero Status TLV w/ Status TLV indicating success. 1868 Discovery completed. 1870 *Router Peer Offer Lost 1872 Router Client Message Description 1873 ==================================================================== 1875 <-------Peer Discovery--------- Modem initiates discovery, 1876 starts a guard timer. 1878 ---------Peer Offer-------|| Router offers availability 1880 Modem times out on Peer Offer, 1881 restarts discovery process. 1883 <-------Peer Discovery--------- Modem initiates discovery 1885 ---------Peer Offer-----------> Router detects subsequent discovery, 1886 internally terminates the previous, 1887 accepts the new association, sends 1888 Peer Offer w/ Status TLV indicating 1889 success. 1891 Discovery completed. 1893 *Discovery Success 1895 Router Client Message Description 1896 ==================================================================== 1898 <-------Peer Discovery--------- Modem initiates discovery 1900 ---------Peer Offer-----------> Router offers availability 1902 -------Peer Heartbeat---------> 1904 <-------Peer Heartbeat--------- 1906 -------Peer Heartbeat---------> 1908 <==============================> Neighbor Sessions 1910 <-------Peer Heartbeat--------- 1912 -------Peer Heartbeat---------> 1914 --------Peer Term Req---------> Terminate Request 1916 <--------Peer Term Res--------- Terminate Response 1918 *Router Detects a Heartbeat timeout 1920 Router Client Message Description 1921 ==================================================================== 1923 <-------Peer Heartbeat--------- 1925 -------Peer Heartbeat---------> 1927 ||---Peer Heartbeat--------- 1929 ~ ~ ~ ~ ~ ~ ~ 1931 -------Peer Heartbeat---------> 1933 ||---Peer Heartbeat--------- 1934 Router Heartbeat Timer expires, 1935 detects missing heartbeats. Router 1936 takes down all neighbor sessions 1937 and terminates the Peer association. 1939 ------Peer Terminate ---------> Peer Terminate Request 1941 Modem takes down all neighbor 1942 sessions, then acknowledges the 1943 Peer Terminate 1945 <----Peer Terminate ACK--------- Peer Terminate ACK 1947 *Modem Detects a Heartbeat timeout 1949 Router Client Message Description 1950 ==================================================================== 1952 <-------Peer Heartbeat--------- 1954 -------Peer Heartbeat------|| 1956 <-------Peer Heartbeat--------- 1958 ~ ~ ~ ~ ~ ~ ~ 1960 -------Peer Heartbeat------|| 1962 <-------Peer Heartbeat--------- 1963 Modem Heartbeat Timer expires, 1964 detects missing heartbeats. Modem 1965 takes down all neighbor sessions 1966 and terminates the Peer association. 1968 <-------Peer Terminate-------- Peer Terminate Request 1970 Router takes down all neighbor 1971 sessions, then acknowledges the 1972 Peer Terminate 1974 ------Peer Terminate ACK-----> Peer Terminate ACK 1976 *Peer Terminate (from Modem) Lost 1978 Router Client Message Description 1979 ==================================================================== 1981 ||------Peer Terminate-------- Modem Peer Terminate Request 1983 Router Heartbeat times out, 1984 terminates association. 1986 --------Peer Terminate-------> Router Peer Terminate 1988 <-----Peer Terminate ACK------ Modem sends Peer Terminate ACK 1990 *Peer Terminate (from router) Lost 1992 Router Client Message Description 1993 ==================================================================== 1995 -------Peer Terminate--------> Router Peer Terminate Request 1997 Modem HB times out, 1998 terminates association. 2000 <------Peer Terminate-------- Modem Peer Terminate 2002 ------Peer Terminate ACK-----> Peer Terminate ACK 2004 Neighbor Level Message Flows 2006 *Modem Neighbor Up Lost 2008 Router Client Message Description 2009 ==================================================================== 2011 ||-----Neighbor Up ------------ Modem sends Neighbor Up 2013 Modem timesout on ACK 2015 <------Neighbor Up ------------ Modem sends Neighbor Up 2017 ------Neighbor Up ACK---------> Router accepts the neighbor 2018 session 2020 <------Neighbor Update--------- Modem Neighbor Metrics 2021 . . . . . . . . 2022 <------Neighbor Update--------- Modem Neighbor Metrics 2024 *Router Detects Duplicate Neighbor Ups 2026 Router Client Message Description 2027 ==================================================================== 2029 <------Neighbor Up ------------ Modem sends Neighbor Up 2031 ------Neighbor Up ACK-------|| Router accepts the neighbor 2032 session 2034 Modem timesout on ACK 2036 <------Neighbor Up ------------ Modem resends Neighbor Up 2038 Router detects duplicate 2039 Neighbor, takes down the 2040 previous, accepts the new 2041 Neighbor. 2043 ------Neighbor Up ACK---------> Router accepts the neighbor 2044 session 2046 <------Neighbor Update--------- Modem Neighbor Metrics 2047 . . . . . . . . 2048 <------Neighbor Update--------- Modem Neighbor Metrics 2050 *Neighbor Up, No Layer 3 Addresses 2052 Router Client Message Description 2053 ==================================================================== 2055 <------Neighbor Up ------------ Modem sends Neighbor Up 2057 ------Neighbor Up ACK---------> Router accepts the neighbor 2058 session 2060 Router ARPs for IPv4 if defined. 2061 Router drives ND for IPv6 if 2062 defined. 2064 <------Neighbor Update--------- Modem Neighbor Metrics 2065 . . . . . . . . 2066 <------Neighbor Update--------- Modem Neighbor Metrics 2068 *Neighbor Up with IPv4, No IPv6 2070 Router Client Message Description 2071 ==================================================================== 2073 <------Neighbor Up ------------ Modem sends Neighbor Up with 2074 the IPv4 TLV 2076 ------Neighbor Up ACK---------> Router accepts the neighbor 2077 session 2079 Router drives ND for IPv6 if 2080 defined. 2082 <------Neighbor Update--------- Modem Neighbor Metrics 2083 . . . . . . . . 2084 <------Neighbor Update--------- Modem Neighbor Metrics 2086 *Neighbor Up with IPv4 and IPv6 2088 Router Client Message Description 2089 ==================================================================== 2091 <------Neighbor Up ------------ Modem sends Neighbor Up with 2092 the IPv4 and IPv6 TLVs 2094 ------Neighbor Up ACK---------> Router accepts the neighbor 2095 session 2097 <------Neighbor Update--------- Modem Neighbor Metrics 2098 . . . . . . . . 2099 <------Neighbor Update--------- Modem Neighbor Metrics 2101 *Neighbor Session Success 2103 Router Client Message Description 2104 ==================================================================== 2106 ---------Peer Offer-----------> Router offers availability 2108 -------Peer Heartbeat---------> 2110 <------Neighbor Up ----------- Modem 2112 ------Neighbor Up ACK--------> Router 2114 <------Neighbor Update--------- Modem 2115 . . . . . . . . 2116 <------Neighbor Update--------- Modem 2118 Modem initiates the terminate 2120 <------Neighbor Down ---------- Modem 2122 ------Neighbor Down ACK-------> Router 2124 or 2126 Router initiates the terminate 2128 ------Neighbor Down ----------> Router 2130 <------Neighbor Down ACK------- Modem 2132 Acknowledgements 2134 The authors would like to acknowledge the influence and contributions 2135 of Chris Olsen and Teco Boot. 2137 Normative References 2139 [RFC5444] Clausen, T., Ed,. "Generalized Mobile Ad Hoc Network (MANET) 2140 Packet/Message Format", RFC 5444, Februar, 2009. 2142 [RFC5578] Berry, B., Ed., "PPPoE with Credit Flow and Metrics", 2143 RFC 5578, February 2010. 2145 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2146 Requirement Levels", RFC 2119, March 1997. 2148 Informative References 2150 [DTLS] Rescorla, E., Ed,. "Datagram Transport Layer Security", 2151 RFC 4347, April 2006. 2153 Author's Addresses 2155 Stan Ratliff 2156 Cisco 2157 170 West Tasman Drive 2158 San Jose, CA 95134 2159 USA 2160 EMail: sratliff@cisco.com 2162 Bo Berry 2163 Cisco 2164 170 West Tasman Drive 2165 San Jose, CA 95134 2166 USA 2167 EMail: boberry@cisco.com 2169 Greg Harrison 2170 Cisco 2171 170 West Tasman Drive 2172 San Jose, CA 95134 2173 USA 2174 EMail: greharri@cisco.com 2176 Shawn Jury 2177 Cisco 2178 170 West Tasman Drive 2179 San Jose, CA 95134 2180 USA 2181 Email: sjury@cisco.com 2183 Darryl Satterwhite 2184 Cisco 2185 170 West Tasman Drive 2186 San Jose, CA 95134 2187 USA 2188 Email: dsatterw@cisco.com