idnits 2.17.1 draft-ietf-roll-aodv-rpl-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 7, 2016) is 2694 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) ** Downref: Normative reference to an Experimental RFC: RFC 3561 ** Downref: Normative reference to an Informational RFC: RFC 5548 ** Downref: Normative reference to an Informational RFC: RFC 5673 ** Downref: Normative reference to an Informational RFC: RFC 5826 ** Downref: Normative reference to an Informational RFC: RFC 5867 ** Downref: Normative reference to an Experimental RFC: RFC 6997 ** Downref: Normative reference to an Experimental RFC: RFC 6998 Summary: 7 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ROLL S. Anamalamudi 3 Internet-Draft M. Zhang 4 Intended status: Standards Track AR. Sangi 5 Expires: June 10, 2017 Huawei Technologies 6 C. Perkins 7 Futurewei 8 S.V.R.Anand 9 Indian Institute of Science 10 December 7, 2016 12 Asymmetric AODV-P2P-RPL in Low-Power and Lossy Networks (LLNs) 13 draft-ietf-roll-aodv-rpl-00 15 Abstract 17 Route discovery for symmetric and asymmetric Point-to-Point (P2P) 18 traffic flows is a desirable feature in Low power and Lossy Networks 19 (LLNs). For that purpose, this document specifies a reactive P2P 20 route discovery mechanism for hop-by-hop routing (storing mode) based 21 on Ad Hoc On-demand Distance Vector Routing (AODV) based RPL 22 protocol. Two separate Instances are used to construct directional 23 paths in case some of the links between source and target node are 24 asymmetric. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on June 10, 2017. 43 Copyright Notice 45 Copyright (c) 2016 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 3. Overview of AODV-RPL . . . . . . . . . . . . . . . . . . . . 5 63 4. AODV-RPL Mode of Operation (MoP) . . . . . . . . . . . . . . 5 64 5. RREQ Message . . . . . . . . . . . . . . . . . . . . . . . . 8 65 6. RREP Message . . . . . . . . . . . . . . . . . . . . . . . . 9 66 7. Gratuitous RREP . . . . . . . . . . . . . . . . . . . . . . . 11 67 8. Operation of Trickle Timer . . . . . . . . . . . . . . . . . 12 68 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 69 9.1. New Mode of Operation: AODV-RPL . . . . . . . . . . . . . 12 70 9.2. AODV-RPL Options: RREQ and RREP . . . . . . . . . . . . . 12 71 10. Security Considerations . . . . . . . . . . . . . . . . . . . 12 72 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 73 11.1. Normative References . . . . . . . . . . . . . . . . . . 13 74 11.2. Informative References . . . . . . . . . . . . . . . . . 14 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 77 1. Introduction 79 RPL[RFC6550], the IPv6 distance vector routing protocol for Low-power 80 and Lossy Networks (LLNs), is designed to support multiple traffic 81 flows through a root-based Destination-Oriented Directed Acyclic 82 Graph (DODAG). For traffic flows between routers within the DODAG 83 (i.e., Point-to-Point (P2P) traffic), this means that data packets 84 either have to traverse the root in non-storing mode (source 85 routing), or traverse a common ancestor in storing mode (hop-by-hop 86 routing). Such P2P traffic is thereby likely to flow along sub- 87 optimal routes and may suffer severe traffic congestion near the DAG 88 root [RFC6997], [RFC6998]. 90 To discover optimal paths for P2P traffic flows in RPL, P2P-RPL 91 [RFC6997] specifies a temporary DODAG where the source acts as 92 temporary root. The source initiates "P2P Route Discovery mode (P2P- 93 RDO)" with an address vector for both non-storing mode (H=0) and 94 storing mode (H=1). Subsequently, each intermediate router adds its 95 IP address and multicasts the P2P-RDO message, until the message 96 reaches the target node (TargNode). TargNode sends the "Discovery 97 Reply" option. P2P-RPL is efficient for source routing, but much 98 less efficient for hop-by-hop routing due to the extra address vector 99 overhead. In fact, when the P2P-RDO message is being multicast from 100 the source hop-by-hop, receiving nodes are able to determine a next 101 hop towards the source in symmetric links. When TargNode 102 subsequently replies to the source along the established forward 103 route, receiving nodes can determine the next hop towards TargNode. 104 In other words, it is efficient to use only routing tables for P2P- 105 RDO message instead of "Address vector" for hop-by-hop routes (H=1) 106 in symmetric links. 108 RPL and P2P-RPL both specify the use of a single DODAG in networks of 109 symmetric links. But, application-specific routing requirements that 110 are defined in IETF ROLL Working Group [RFC5548], [RFC5673], 111 [RFC5826] and [RFC5867] may need routing metrics and constraints 112 enabling use of asymmetric bidirectional links. For this purpose, 113 [I-D.thubert-roll-asymlink] describes bidirectional asymmetric links 114 for RPL [RFC6550] with Paired DODAGs, for which the DAG root 115 (DODAGID) is common for two Instances. This can satisfy application- 116 specific routing requirements for bidirectional asymmetric links in 117 base RPL [RFC6550]. P2P-RPL for Paired DODAGs, on the other hand, 118 requires two DAG roots: one for the source and another for the target 119 node due to temporary DODAG formation. For networks composed of 120 bidirectional asymmetric links (see Section 4), AODV-RPL specifies 121 P2P route discovery, utilizing RPL with a new MoP. AODV-RPL makes 122 use of two multicast messages to discover possibly asymmetric routes. 123 AODV-RPL eliminates the need for address vector control overhead, 124 significantly reducing the control packet size which is important for 125 Constrained LLN networks. Both discovered routes meet the 126 application specific metrics and constraints that are defined in the 127 Objective Function for each Instance [RFC6552]. 129 2. Terminology 131 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 132 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 133 "OPTIONAL" in this document are to be interpreted as described in 134 [RFC2119]. Additionally, this document uses the following terms: 136 AODV 137 Ad Hoc On-demand Distance Vector Routing[RFC3561]. 139 AODV-Instance 140 Either the RREQ-Instance or RREP-Instance 142 Bi-directional Asymmetric Link 143 A link that can be used in both directions but with different link 144 characteristics (see [I-D.thubert-roll-asymlink]). 146 DODAG RREQ-Instance (or simply RREQ-Instance) 147 AODV Instance built using the RREQ option; used for control 148 transmission from OrigNode to TargNode, thus enabling data 149 transmission from TargNode to OrigNode. 151 DODAG RREP-Instance (or simply RREP-Instance) 152 AODV Instance built using the RREP option; used for control 153 transmission from TargNode to OrigNode thus enabling data 154 transmission from OrigNode to TargNode. 156 downstream 157 Routing along the direction from OrigNode to TargNode. 159 hop-by-hop routing 160 Routing when each node stores routing information about the next 161 hop. 163 OrigNode 164 The IPv6 router (Originating Node) initiating the AODV-RPL route 165 discovery to obtain a route to TargNode. 167 Paired DODAGs 168 Two DODAGs for a single application. 170 P2P 171 Point-to-Point -- in other words, not constrained to traverse a 172 common ancestor. 174 RREQ message 175 An AODV-RPL MoP DIO message containing the RREQ option. The 176 InstanceID in DIO object of RREQ option MUST be always an odd 177 number. 179 RREP message 180 An AODV-RPL MoP DIO message containing the RREP option. The 181 InstanceID in DIO object of RREP option MUST be always an even 182 number (InstanceID of RREQ-Instance+1). 184 source routing 185 The mechanism by which the source supplies the complete route 186 towards the target node along with each data packet. [RFC6997]. 188 TargNode 189 The IPv6 router (Target Node) for which OrigNode requires a route 190 and initiates Route Discovery within the LLN network. 192 upstream 193 Routing along the direction from TargNode to OrigNode. 195 3. Overview of AODV-RPL 197 With AODV-RPL, routes from OrigNode to TargNode within the LLN 198 network established are "on-demand". In other words, the route 199 discovery mechanism in AODV-RPL is invoked reactively when OrigNode 200 has data for delivery to the TargNode but existing routes do not 201 satisfy the application's requirements. The routes discovered by 202 AODV-RPL are point-to-point; in other words the routes are not 203 constrained to traverse a common ancestor. Unlike base RPL [RFC6550] 204 and P2P-RPL [RFC6997], AODV-RPL can enable asymmetric communication 205 paths in networks with bidirectional asymmetric links. For this 206 purpose, AODV-RPL enables discovery of two routes: namely, one from 207 OrigNode to TargNode, and another from TargNode to OrigNode. When 208 possible, AODV-RPL also enables symmetric routing along Paired DODAGs 209 (see Section 4). 211 4. AODV-RPL Mode of Operation (MoP) 213 In AODV-RPL, route discovery is initiated by forming a temporary DAG 214 rooted at the OrigNode. Paired DODAGs (Instances) are constructed 215 according to a new AODV-RPL Mode of Operation (MoP) during route 216 formation between the OrigNode and TargNode. The RREQ-Instance is 217 formed by route control messages from OrigNode to TargNode whereas 218 the RREP-Instance is formed by route control messages from TargNode 219 to OrigNode (as shown in Figure 2). Intermediate routers join the 220 Paired DODAGs based on the rank as calculated from the DIO message. 221 Henceforth in this document, the RREQ-Instance message means the 222 AODV-RPL DIO message from OrigNode to TargNode, containing the RREQ 223 option. Similarly, the RREP-Instance means the AODV-RPL DIO message 224 from TargNode to OrigNode, containing the RREP option. Subsequently, 225 the RREQ-Instance is used for data transmission from TargNode to 226 OrigNode and RREP-Instance is used for Data transmission from 227 OrigNode to TargNode. 229 The AODV-RPL Mode of Operation defines a new bit, the Symmetric bit 230 ('S'), which is added to the base DIO message as illustrated in 231 Figure 1. OrigNode sets the the 'S' bit to 1 in the RREQ-Instance 232 message when initiating route discovery. 234 0 1 2 3 235 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 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | RPLInstanceID |Version Number | Rank | 238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 |G|0| MOP | Prf | DTSN |S| Flags | Reserved | 240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 241 | | 242 + + 243 | | 244 + DODAGID + 245 | | 246 + + 247 | | 248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 | Option(s)... 251 Figure 1: DIO modification to support asymmetric route discovery 253 A device originating a AODV-RPL message supplies the following 254 information in the DIO header of the message: 256 'S' bit 258 Symmetric bit in the DIO base object 260 MOP 262 MOP operation in the DIO object MUST be set to "5(TBD1)" for AODV- 263 RPL DIO messages 265 RPLInstanceID 267 RPLInstanceID in the DIO object MUST be the InstanceID of AODV- 268 Instance(RREQ-Instance). The InstanceID for RREQ-Instance MUST be 269 always an odd number. 271 DODAGID 273 For RREQ-Instance : 275 DODAGID in the DIO object MUST be the IPv6 address of the device 276 that initiates the RREQ-Instance. 278 For RREP-Instance 280 DODAGID in the DIO object MUST be the IPv6 address of the device 281 that initiates the RREP-Instance. 283 Rank 285 Rank in the DIO object MUST be the the rank of the AODV-Instance 286 (RREQ-Instance). 288 Metric Container Options 290 AODV-Instance(RREQ-Instance) messages MAY carry one or more Metric 291 Container options to indicate the relevant routing metrics. 293 The 'S' bit is set to mean that the route is symmetric. If the RREQ- 294 Instance arrives over an interface that is known to be symmetric, and 295 the 'S' bit is set to 1, then it remains set at 1, as illustrated in 296 Figure 2. 298 In this figure: 299 S := OrigNode; R := Intermediate nodes; D := TargNode 301 R---------R---------R---------R 302 |<--S=1-->|<--S=1-->|<--S=1-->| 303 | | | | 304 <--S=1--> | | <--S=1--> 305 | | | | 306 | | | | 307 S---------R---------R---------R---------R---------R---------D 308 <--S=1-->| | | |<--S=1-->|<--S=1-->| 309 | | | | | | 310 | | | | | | 311 R---------R---------R---------R---------R---------R 313 >---- RREQ-Instance (Control: S-->D; Data: D-->S) -------> 314 <---- RREP-Instance (Control: D-->S; Data: S-->D) -------< 316 Figure 2: AODV-RPL with Symmetric Paired Instances 318 If the RREQ-Instance arrives over an interface that is not known to 319 be symmetric, or is known to be asymmetric, the 'S' bit is set to be 320 0. Moreover, if the 'S' bit arrives already set to be '0', it is set 321 to be '0' on retransmission (Figure 3). Based on the 'S' bit 322 received in RREQ-Instance, the TargNode decides whether or not the 323 route is symmetric before transmitting the RREP-Instance message 324 upstream towards the OrigNode. The metric used to determine symmetry 325 (i.e., set the "S" bit to be "1" (Symmetric) or "0" (asymmetric)) is 326 not specified in this document. 328 R---------R--------R--------R 329 | --S=1-->|--S=1-->|--S=0-->| 330 | | | | 331 --S=1--> | | --S=0--> 332 | | | | 333 --S=1-->| | | | 334 S--------R---------R--------R--------R--------R---------D 335 <--S=0--| | | |--S=0-->| --S=0-->| 336 | | | | | | 337 <--S=0-- | | | | <--S=0-- 338 | | | | | | 339 | <--S=0--|<--S=0--|<--S=0--|<--S=0--|<--S=0-- | 340 R---------R--------R--------R--------R---------R 342 >---- RREQ-Instance (Control: S-->D; Data: D-->S) -------> 343 <---- RREP-Instance (Control: D-->S; Data: S-->D) -------< 345 Figure 3: AODV-RPL with Asymmetric Paired Instances 347 5. RREQ Message 349 0 1 2 3 350 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 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 | Type | Orig SeqNo | Dest SeqNo | 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 | | 355 | TargNode IPv6 Address | 356 | | 357 | | 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 360 Figure 4: DIO RREQ option format for AODV-RPL MoP 362 OrigNode supplies the following information in the RREQ option of the 363 RREQ-Instance message: 365 Type 367 The type of the RREQ option (see Section 9.2) 369 Orig SeqNo 371 Sequence Number of OrigNode. 373 Dest SeqNo 374 If nonzero, the last known Sequence Number for TargNode for which 375 a route is desired. 377 TargNode IPv6 Address 379 IPv6 address of the TargNode that receives RREQ-Instance message. 380 This address MUST be in the RREQ option (see Figure 4) of AODV- 381 RPL. 383 In order to establish the upstream route from TargNode to OrigNode, 384 OrigNode multicasts the RREQ-Instance message (see Figure 4) to its 385 one-hop neighbours. In order to enable intermediate nodes R_i to 386 associate a future RREP message to an incoming RREQ message, the 387 InstanceID of RREQ-Instance MUST assign an odd number. 389 Each intermediate node R_i computes the rank for RREQ-Instance and 390 creates a routing table entry for the upstream route towards the 391 source if the routing metrics/constraints are satisfied. For this 392 purpose R_i must use the asymmetric link metric measured in the 393 upstream direction, from R_i to its upstream neighbor that 394 multicasted the RREQ-Instance message. 396 When an intermediate node R_i receives a RREQ message in storing 397 mode, it MUST store the OrigNode's InstanceID (RREQ-Instance) along 398 with the other routing information needed to establish the route back 399 to the OrigNode. This will enable R_i to determine that a future 400 RREP message (containing a paired InstanceID for the TargNode) must 401 be transmitted back to the OrigNode's IP address. 403 If the paths to and from TargNode are not known, the intermediate 404 node multicasts the RREQ-Instance message with updated rank to its 405 next-hop neighbors until the message reaches TargNode (Figure 2). 406 Based on the 'S' bit in the received RREQ message, the TargNode will 407 decide whether to unicast or multicast the RREP message back to 408 OrigNode. 410 As described in Section 7, in certain circumstances R_i MAY unicast a 411 Gratuitous RREP towards OrigNode, thereby helping to minimize 412 multicast overhead during the Route Discovery process. 414 6. RREP Message 416 The TargNode supplies the following information in the RREP message: 418 0 1 2 3 419 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 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | Type | Dest SeqNo | Prefix Sz |T|G| Rsvd | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | | 424 | TargNode IPv6 Address (when present) | 425 | | 426 | | 427 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 429 Figure 5: DIO RREP option format for AODV-RPL MoP 431 Type 433 The type of the RREP option (see Section 9.2) 435 Dest SeqNo 437 The Sequence Number for the TargNode for which a route is 438 established. 440 Prefix Sz 442 The size of the prefix which the route to the TargNode is 443 available. This allows routing to other nodes on the same subnet 444 as the TargNode. 446 'T' bit 448 'T' is set to true to indicate that the TargNode IPv6 Address 449 field is present 451 'G' bit 453 (see Section 7) 455 TargNode IPv6 Address (when present) 457 IPv6 address of the TargNode that receives RREP-Instance message. 459 In order to reduce the need for the TargNode IPv6 Address to be 460 included with the RREP message, the InstanceID of the RREP-Instance 461 is paired, whenever possible, with the InstanceID from the RREQ 462 message, which is always an odd number. The pairing is accomplished 463 by adding one to the InstanceID from the RREQ message and using that, 464 whenever possible, as the InstanceID for the RREP message. If this 465 is not possible (for instance because the incremented InstanceID is 466 still a valid InstanceID for another route to the TargNode from an 467 earlier Route Discovery operation), then the 'T' bit is set and an 468 odd number is chosen for the InstanceID of RREP from TargNode. 470 The OrigNode IP address for RREQ-Instance is available as the DODAGID 471 in the DIO base message (see Figure 1). When TargNode receives a 472 RREQ message with the 'S' bit set to 1 (as illustrated in Figure 2), 473 it unicasts the RREP message with the 'S' bit set to 1. In this 474 case, route control messages and application data between OrigNode 475 and TargNode for both RREQ-Instance and RREP-Instance are transmitted 476 along symmetric links. When the InstanceID of RREP-Instance is even 477 number then the TargNode IPv6 Address is elided in RREP option. When 478 the InstanceID of RREP-Instance is an odd number with "T" bit set to 479 "1" then TargNode IPv6 Address is transmitted in RREP option. 481 When (as illustrated in Figure 3) the TargNode receives RREQ message 482 with the 'S' bit set to 0, it also multicasts the RREP message with 483 the 'S' bit set to 0. Intermediate nodes create a routing table 484 entry for the path towards the TargNode while processing the RREP 485 message to OrigNode. Once OrigNode receives the RREP message, it 486 starts transmitting application data to TargNode along the path as 487 discovered through RREP messages. Similarly, application data from 488 TargNode to OrigNode is transmitted through the path that is 489 discovered from RREQ message. 491 7. Gratuitous RREP 493 Under some circumstances, an Intermediate Node that receives a RREQ 494 message MAY transmit a "Gratuitous" RREP message back to OrigNode 495 instead of continuing to multicast the RREQ message towards TargNode. 496 For these circumstances, the 'G' bit of the RREP option is provided 497 to distinguish the Gratuitous RREP sent by the Intermediate node from 498 the RREP sent by TargNode. 500 When an Intermediate node R receives a RREQ message and has recent 501 information about the cost of an upstream route from TargNode to R, 502 then R MAY unicast the Gratuitous RREP (GRREP) message to OrigNode. 503 R determines whether its information is sufficiently recent by 504 comparing the value it has stored for the Sequence Number of TargNode 505 against the DestSeqno in the incoming RREQ message. R also must have 506 information about the metric information of the upstream route from 507 TargNode. The GRREP message MUST have PrefixSz == 0 and the 'G' bit 508 set to 1. R SHOULD also unicast the RREQ message to TargNode, to 509 make sure that TargNode will have a route to OrigNode. 511 8. Operation of Trickle Timer 513 The trickle timer operation to control RREQ-Instance/RREP-Instance 514 multicast is similar to that in P2P-RPL [RFC6997]. 516 9. IANA Considerations 518 9.1. New Mode of Operation: AODV-RPL 520 IANA is required to assign a new Mode of Operation, named "AODV-RPL" 521 for Point-to-Point(P2P) hop-by-hop routing under the RPL registry. 522 The value of TBD1 is assigned from the "Mode of Operation" space 523 [RFC6550]. 525 +-------------+---------------+---------------+ 526 | Value | Description | Reference | 527 +-------------+---------------+---------------+ 528 | TBD1 (5) | AODV-RPL | This document | 529 +-------------+---------------+---------------+ 531 Figure 6: Mode of Operation 533 9.2. AODV-RPL Options: RREQ and RREP 535 Two entries are required for new AODV-RPL options "RREQ-Instance" and 536 "RREQ-Instance", with values of TBD2 (0x0A) and TBD3 (0x0B) from the 537 "RPL Control Message Options" space [RFC6550]. 539 +-------------+---------------------+---------------+ 540 | Value | Meaning | Reference | 541 +-------------+---------------------+---------------+ 542 | TBD2 (0x0A) | RREQ Option | This document | 543 +-------------+---------------------+---------------+ 544 | TBD3 (0x0B) | RREP Option | This document | 545 +-------------+---------------------+---------------+ 547 Figure 7: AODV-RPL Options 549 10. Security Considerations 551 This document does not introduce additional security issues compared 552 to base RPL. For general RPL security considerations, see [RFC6550]. 554 11. References 555 11.1. Normative References 557 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 558 Requirement Levels", BCP 14, RFC 2119, 559 DOI 10.17487/RFC2119, March 1997, 560 . 562 [RFC3561] Perkins, C., Belding-Royer, E., and S. Das, "Ad hoc On- 563 Demand Distance Vector (AODV) Routing", RFC 3561, 564 DOI 10.17487/RFC3561, July 2003, 565 . 567 [RFC5548] Dohler, M., Ed., Watteyne, T., Ed., Winter, T., Ed., and 568 D. Barthel, Ed., "Routing Requirements for Urban Low-Power 569 and Lossy Networks", RFC 5548, DOI 10.17487/RFC5548, May 570 2009, . 572 [RFC5673] Pister, K., Ed., Thubert, P., Ed., Dwars, S., and T. 573 Phinney, "Industrial Routing Requirements in Low-Power and 574 Lossy Networks", RFC 5673, DOI 10.17487/RFC5673, October 575 2009, . 577 [RFC5826] Brandt, A., Buron, J., and G. Porcu, "Home Automation 578 Routing Requirements in Low-Power and Lossy Networks", 579 RFC 5826, DOI 10.17487/RFC5826, April 2010, 580 . 582 [RFC5867] Martocci, J., Ed., De Mil, P., Riou, N., and W. Vermeylen, 583 "Building Automation Routing Requirements in Low-Power and 584 Lossy Networks", RFC 5867, DOI 10.17487/RFC5867, June 585 2010, . 587 [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., 588 Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, 589 JP., and R. Alexander, "RPL: IPv6 Routing Protocol for 590 Low-Power and Lossy Networks", RFC 6550, 591 DOI 10.17487/RFC6550, March 2012, 592 . 594 [RFC6552] Thubert, P., Ed., "Objective Function Zero for the Routing 595 Protocol for Low-Power and Lossy Networks (RPL)", 596 RFC 6552, DOI 10.17487/RFC6552, March 2012, 597 . 599 [RFC6997] Goyal, M., Ed., Baccelli, E., Philipp, M., Brandt, A., and 600 J. Martocci, "Reactive Discovery of Point-to-Point Routes 601 in Low-Power and Lossy Networks", RFC 6997, 602 DOI 10.17487/RFC6997, August 2013, 603 . 605 [RFC6998] Goyal, M., Ed., Baccelli, E., Brandt, A., and J. Martocci, 606 "A Mechanism to Measure the Routing Metrics along a Point- 607 to-Point Route in a Low-Power and Lossy Network", 608 RFC 6998, DOI 10.17487/RFC6998, August 2013, 609 . 611 11.2. Informative References 613 [I-D.thubert-roll-asymlink] 614 Thubert, P., "RPL adaptation for asymmetrical links", 615 draft-thubert-roll-asymlink-02 (work in progress), 616 December 2011. 618 Authors' Addresses 620 Satish Anamalamudi 621 Huawei Technologies 622 No. 156 Beiqing Rd. Haidian District 623 Beijing 100095 624 China 626 Email: satishnaidu80@gmail.com 628 Mingui Zhang 629 Huawei Technologies 630 No. 156 Beiqing Rd. Haidian District 631 Beijing 100095 632 China 634 Email: zhangmingui@huawei.com 636 Abdur Rashid Sangi 637 Huawei Technologies 638 No.156 Beiqing Rd. Haidian District 639 Beijing 100095 640 P.R. China 642 Email: rashid.sangi@huawei.com 643 Charles E. Perkins 644 Futurewei 645 2330 Central Expressway 646 Santa Clara 95050 647 Unites States 649 Email: charliep@computer.org 651 S.V.R Anand 652 Indian Institute of Science 653 Bangalore 560012 654 India 656 Email: anand@ece.iisc.ernet.in