idnits 2.17.00 (12 Aug 2021) /tmp/idnits26755/draft-ietf-roll-useofrplinfo-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (January 29, 2016) is 2304 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-05) exists of draft-ietf-6lo-routing-dispatch-04 == Outdated reference: draft-ietf-6tisch-architecture has been published as RFC 9030 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ROLL Working Group M. Robles 3 Internet-Draft Ericsson 4 Intended status: Informational M. Richardson 5 Expires: August 1, 2016 SSW 6 P. Thubert 7 Cisco 8 January 29, 2016 10 When to use RFC 6553, 6554 and IPv6-in-IPv6 11 draft-ietf-roll-useofrplinfo-00 13 Abstract 15 This document states different cases where RFC 6553, RFC 6554 and 16 IPv6-in-IPv6 encapsulation is required to set the bases to help 17 defining the compression of RPL routing information in LLN 18 environments. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on August 1, 2016. 37 Copyright Notice 39 Copyright (c) 2016 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Terminology and Requirements Language . . . . . . . . . . . . 3 56 3. Sample/reference topology . . . . . . . . . . . . . . . . . . 3 57 4. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 6 58 5. Storing mode . . . . . . . . . . . . . . . . . . . . . . . . 8 59 5.1. Example of Flow from RPL-aware-leaf to root . . . . . . . 8 60 5.2. Example of Flow from root to RPL-aware-leaf . . . . . . . 9 61 5.3. Example of Flow from root to not-RPL-aware-leaf . . . . . 10 62 5.4. Example of Flow from not-RPL-aware-leaf to root . . . . . 10 63 5.5. Example of Flow from RPL-aware-leaf to Internet . . . . . 11 64 5.6. Example of Flow from Internet to RPL-aware-leaf . . . . . 11 65 5.7. Example of Flow from not-RPL-aware-leaf to Internet . . . 12 66 5.8. Example of Flow from Internet to non-RPL-aware-leaf . . . 13 67 5.9. Example of Flow from RPL-aware-leaf to RPL-aware-leaf . . 14 68 5.10. Example of Flow from RPL-aware-leaf to non-RPL-aware-leaf 15 69 5.11. Example of Flow from not-RPL-aware-leaf to RPL-aware-leaf 16 70 5.12. Example of Flow from not-RPL-aware-leaf to not-RPL-aware- 71 leaf . . . . . . . . . . . . . . . . . . . . . . . . . . 17 72 6. Non Storing mode . . . . . . . . . . . . . . . . . . . . . . 18 73 6.1. Example of Flow from RPL-aware-leaf to root . . . . . . . 18 74 6.2. Example of Flow from root to RPL-aware-leaf . . . . . . . 19 75 6.3. Example of Flow from root to not-RPL-aware-leaf . . . . . 19 76 6.4. Example of Flow from not-RPL-aware-leaf to root . . . . . 20 77 6.5. Example of Flow from RPL-aware-leaf to Internet . . . . . 20 78 6.6. Example of Flow from Internet to RPL-aware-leaf . . . . . 21 79 6.7. Example of Flow from not-RPL-aware-leaf to Internet . . . 22 80 6.8. Example of Flow from Internet to non-RPL-aware-leaf . . . 23 81 6.9. Example of Flow from RPL-aware-leaf to RPL-aware-leaf . . 24 82 6.10. Example of Flow from RPL-aware-leaf to not-RPL-aware-leaf 25 83 6.11. Example of Flow from not-RPL-aware-leaf to RPL-aware-leaf 26 84 6.12. Example of Flow from not-RPL-aware-leaf to not-RPL-aware- 85 leaf . . . . . . . . . . . . . . . . . . . . . . . . . . 26 86 7. Future RPL work . . . . . . . . . . . . . . . . . . . . . . . 27 87 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 88 9. Security Considerations . . . . . . . . . . . . . . . . . . . 27 89 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 28 90 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 91 11.1. Normative References . . . . . . . . . . . . . . . . . . 28 92 11.2. Informative References . . . . . . . . . . . . . . . . . 28 93 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 95 1. Introduction 97 RPL [RFC6550] is a routing protocol for constrained networks. RFC 98 6553 [RFC6553] defines the "RPL option", carried within the IPv6 Hop- 99 by-Hop header to quickly identify inconsistencies in the routing 100 topology. RFC 6554 [RFC6554] defines the "RPL Source Route Header", 101 an IPv6 Extension Header to deliver datagrams within a RPL routing 102 domain. 104 Several discussions in the ROLL/6lo/6TiSCH Mailing Lists took place 105 focusing in the definition of how to compress RPL Information in 106 constrained environment. ROLL Virtual Interim Meeting (02-2015) 107 concluded that there is a need to define how to use [RFC6553], 108 [RFC6554] and IPv6-in-IPv6 encapsulation to be able to set the 109 correct environment for compression A Routing Header Dispatch for 110 6LoWPAN (6LoRH) [I-D.ietf-6lo-routing-dispatch] defines a method to 111 compress RPL Option information and Routing Header type 3 (RFC6554) 112 and an efficient IP-in-IP technique. Uses cases proposed for the 113 [Second6TischPlugtest] involving 6loRH: When the packet travel inside 114 the RPL domain, the IP in IP 6LoRH is not be presented in the packet 115 and when the packet travel outside a RPL domain, Ip in IP 6LoRH is 116 present in the packet. 118 This document is going to be focused in data plane messages and how 119 can be transmitted within the above mentioned RFCs. 121 2. Terminology and Requirements Language 123 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 124 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 125 document are to be interpreted as described in RFC 2119 [RFC2119]. 127 Terminology defined in [RFC7102] 129 3. Sample/reference topology 131 A RPL network is composed of a 6LBR (6LoWPAN Border Router), Backbone 132 Router (6BBR), 6LR (6LoWPAN Router) and 6LN (6LoWPAN Node) as leaf 133 logically organized in a DODAG structure (Destination Oriented 134 Directed Acyclic Graph). 136 RPL defines the RPL Control messages (control plane ), a new ICMPv6 137 message with Type 155. DIS, DIO and DAO messages are all RPL Control 138 messages but with different Code values. 140 RPL supports two modes of Downward traffic: in storing mode, it is 141 fully stateful or an in non-storing, it is fully source routed. A 142 RPL Instance is either fully storing or fully non-storing, i.e. a RPL 143 Instance with a combination of storing and non-storing nodes is not 144 supported with the current specifications. 146 +--------------+ 147 | Upper Layers | 148 | | 149 +--------------+ 150 | RPL | 151 | | 152 +--------------+ 153 | ICMPv6 | 154 | | 155 +--------------+ 156 | IPv6 | 157 | | 158 +--------------+ 159 | 6LoWPAN | 160 | | 161 +--------------+ 162 | PHY-MAC | 163 | | 164 +--------------+ 166 Figure 1: RPL Stack. 168 +---------+ 169 +---+Internet | 170 | +---------+ 171 | 172 +----+--+ 173 |DODAG | 174 +---------+Root +----------+ 175 | |6LBR | | 176 | +----+--+ | 177 | | | 178 | | | 179 ... ... ... 180 | | | 181 +-----+-+ +--+---+ +--+---+ 182 |6LR | | | | | 183 +-----+ | | | | | 184 | | | | | | +------+ 185 | +-----+-+ +-+----+ +-+----+ | 186 | | | | | 187 | | | | | 188 | | | | | 189 +-+---+ +-+---+ +--+--+ +- --+ +---+-+ 190 |Leaf | | | | | | | | | 191 |6LN | | | | | | | | | 192 +-----+ +-----+ +-----+ +----+ +-----+ 194 Figure 2: A reference RPL Topology. 196 This document is in part motivated by the work that is ongoing at the 197 6TiSCH working group. The 6TiSCH architecture 198 [I-D.ietf-6tisch-architecture] draft explains the network 199 architecture of a 6TiSCH network. This architecture is used for the 200 remainder of this document. 202 The scope of the 6TiSCH Architecture is a Backbone Link that 203 federates multiple LLNs (mesh) as a single IPv6 Multi-Link Subnet. 204 Each LLN in the subnet is anchored at a Backbone Router (6BBR). The 205 Backbone Routers interconnect the LLNs over the Backbone Link and 206 emulate that the LLN nodes are present on the Backbone thus creating 207 a so-called: Multi-Link Subnet. An LLN node can move freely from an 208 LLN anchored at a Backbone Router to another LLN anchored at the same 209 or a different Backbone Router inside the Multi-Link Subnet and 210 conserve its addresses. 212 | 213 +-----+ 214 | | Border Router to the RPL domain 215 | | (may be a RPL virtual root) 216 +-----+ 217 | 218 | Backbone 219 +-------------------+-------------------+ 220 | | | 221 +-----+ +-----+ +-----+ 222 | | Backbone | | Backbone | | Backbone 223 | | router | | router | | router 224 +|---|+ +-|||-+ +-[_]-+ 225 | | PCI-exp / | \ USB | Ethernet 226 ( ) ( ) ( )( )( ) (6LBR == RPL DODAG root) 227 o o o o o o o o o o o o 228 o o o o o o o o o o o o o o o o 229 o o o o o o o o o o 6LR == RPL router) o o 230 o o o o o o o z 231 o o o o o o (6LoWPAN Host) 233 <----------------------- RPL Instance ------------------------> 235 Figure 3: RPL domain architecture 237 4. Use cases 239 In data plane context a combination of RFC6553, RFC6554 and IPv6-in- 240 IPv6 encapsulation is going to be analyzed for the following traffic 241 flows: 243 -Flow from RPL-aware-leaf to root 245 -Flow from root to RPL-aware-leaf 247 -Flow from not-RPL-aware-leaf to root 249 -Flow from root to not-RPL-aware-leaf 251 -Flow from RPL-aware-leaf to Internet 253 -Flow from Internet to RPL-aware-leaf 255 -Flow from not-RPL-aware-leaf to Internet 257 -Flow from Internet to not-RPL-aware-leaf 258 -Flow from RPL-aware-leaf to RPL-aware-leaf 260 -Flow from RPL-aware-leaf to not-RPL-aware-leaf 262 -Flow from not-RPL-aware-leaf to RPL-aware-leaf 264 -Flow from not-RPL-aware-leaf to not-RPL-aware-leaf 266 This document assumes a rule that a Header cannot be inserted or 267 removed on the fly inside an IPv6 packet that is being routed. 269 - This means that an intermediate router that needs to add a header 270 must encapsulate the packet in an outer IP header where the new 271 header can be placed. 273 - This also means that a Header can only be removed by an 274 intermediate router if it is placed in an encapsulating IPv6 Header, 275 and in that case, the whole encapsulating header must be removed - a 276 replacement may be added. 278 This document recognizes that some headers such as a Routing Header 279 or a Hop-by-Hop header may be modified by routers on the path of the 280 packet without the need to add to remove an encapsulating header. 282 The RPL RH and the RPL option are mutable but recoverable . 284 RPI should be present in every single RPL data packet. There is an 285 exception in non-storing mode, when a packet is going down from the 286 route: the entire route is written, so there are no loops of 287 confusion about which table to use (purpose of instanceID). 289 The applicability for storing (RPL-SN) and non-Storing (RPL-NSN) 290 modes for the previous cases is showed as follows: 292 +---------------+------+------+---------+--------+--------+---------+ 293 | Use Case | RPL- | RPL- | RPL-SN | RPL- | RPL- | RPL-NSN | 294 | | SN | SN | IP-in- | NSN | NSN | IP-in- | 295 | | RPI | RH3 | IP | RPI | RH3 | IP | 296 | | (RFC | (RFC | | | | | 297 | | 6553 | 6554 | | | | | 298 | | ) | ) | | | | | 299 +---------------+------+------+---------+--------+--------+---------+ 300 | RPL-aware- | Yes | No | No | Yes | No | No | 301 | leaf to root | | | | | | | 302 | root to RPL- | Yes | No | No | Yes | Yes | No | 303 | aware-leaf | | | | | | | 304 | not-RPL- | Yes | No | Yes | Yes | No | Yes | 305 | aware-leaf to | | | | | | | 306 | root | | | | | | | 307 | root to not- | Yes | No | Yes | Yes | Yes | Yes | 308 | RPL-aware- | | | | | | | 309 | leaf | | | | | | | 310 | RPL-aware- | Yes | No | Yes | Yes | No | Yes | 311 | leaf to | | | | | | | 312 | Internet | | | | | | | 313 | Internet to | Yes | No | Yes | Yes | Yes | Yes | 314 | RPL-aware- | | | | | | | 315 | leaf | | | | | | | 316 | not-RPL- | Yes | No | Yes | Yes | No | Yes | 317 | aware-leaf to | | | | | | | 318 | Internet | | | | | | | 319 | Internet to | Yes | No | Yes | Yes | Yes | Yes | 320 | not-RPL- | | | | | | | 321 | aware-leaf | | | | | | | 322 | RPL-aware- | Yes | No | No | Yes | Yes | Yes | 323 | leaf to RPL- | | | | | | | 324 | aware-leaf | | | | | | | 325 | RPL-aware- | Yes | No | Yes | Yes | Yes | Yes | 326 | leaf to not- | | | | | | | 327 | RPL-aware- | | | | | | | 328 | leaf | | | | | | | 329 | not-RPL- | Yes | No | Yes | Yes | Yes | Yes | 330 | aware-leaf to | | | | | | | 331 | RPL-aware- | | | | | | | 332 | leaf | | | | | | | 333 | not-RPL- | Yes | No | Yes | Yes | Yes | Yes | 334 | aware-leaf to | | | | | | | 335 | not-RPL- | | | | | | | 336 | aware-leaf | | | | | | | 337 +---------------+------+------+---------+--------+--------+---------+ 339 Table 1: Posibility to transmit in Storing or Non-Storing mode: RPI, 340 RH3, IP-in-IP encapsulation 342 5. Storing mode 344 5.1. Example of Flow from RPL-aware-leaf to root 346 As states in Section 16.2 of [RFC6550] a RPL-aware-leaf node does 347 not generally issue DIO messages, a leaf node accepts DIO messages 348 (In inconsistency a leaf node generates DIO with infinite rank, to 349 fix it). It may issue DAO and DIS messages though it generally 350 ignores DAO and DIS messages. 352 In storing mode is suitable the use of RFC 6553 to send RPL 353 Information through HBH field checking the routing table to find out 354 where to send the message. 356 In this case the flow comprises: 358 RPL-aware-leaf (6LN) --> 6LR --> 6LR,... --> root (6LBR) Note: In 359 this document 6LRs, 6LBR are always full-fledge RPL routers 361 The 6LN inserts the RPI header, and send the packet to 6LR which 362 decrement the rank in RPI and send the packet up. When the packet 363 arrives to 6LBR, the RPI is removed and the packet is processed. 365 +-------------------+-----+------+------+ 366 | Header | 6LN | 6LR | 6LBR | 367 +-------------------+-----+------+------+ 368 | Inserted headers | RPI | -- | -- | 369 | Removed headers | -- | -- | RPI | 370 | Re-added headers | -- | -- | -- | 371 | Modified headers | -- | RPI | -- | 372 | Untouched headers | -- | -- | -- | 373 +-------------------+-----+------+------+ 375 Storing: Summary of the use of headers from RPL-aware-leaf to root 377 5.2. Example of Flow from root to RPL-aware-leaf 379 In this case the flow comprises: 381 root (6LBR)--> 6LR --> RPL-aware-leaf (6LN) 383 In this case the 6LBR insert RPI header and send the packet down, the 384 6LR is going to increment the rank in RPI (examines instanceID for 385 multiple tables), the packet is processed in 6LN and RPI removed. 387 +-------------------+------+-------+------+ 388 | Header | 6LBR | 6LR | 6LN | 389 +-------------------+------+-------+------+ 390 | Inserted headers | RPI | -- | -- | 391 | Removed headers | -- | -- | RPI | 392 | Re-added headers | -- | -- | -- | 393 | Modified headers | -- | RPI | -- | 394 | Untouched headers | -- | -- | -- | 395 +-------------------+------+-------+------+ 397 Storing: Summary of the use of headers from root to RPL-aware-leaf 399 5.3. Example of Flow from root to not-RPL-aware-leaf 401 In this case the flow comprises: 403 root (6LBR)--> 6LR --> not-RPL-aware-leaf (6LN) 405 It includes IPv6-in-IPv6 encapsulation to transmit information not 406 related with the RPL domain. In the 6LBR the RPI header is inserted 407 into an IPv6-in-IPv6 header addressed to the last 6LR, which removes 408 the header before pass the packet to the IPv6 node. 410 +-------------------+-------------------+-------------------+------+ 411 | Header | 6LBR | 6LR | IPv6 | 412 +-------------------+-------------------+-------------------+------+ 413 | Inserted headers | IPv6-in-IPv6(RPI) | -- | -- | 414 | Removed headers | -- | IPv6-in-IPv6(RPI) | -- | 415 | Re-added headers | -- | -- | -- | 416 | Modified headers | -- | -- | -- | 417 | Untouched headers | -- | -- | -- | 418 +-------------------+-------------------+-------------------+------+ 420 Storing: Summary of the use of headers from root to not-RPL-aware- 421 leaf 423 5.4. Example of Flow from not-RPL-aware-leaf to root 425 In this case the flow comprises: 427 not-RPL-aware-leaf (6LN) --> 6LR --> root (6LBR) 429 When the packet arrives from IPv6 node to 6LR. This router insert 430 the RPI encapsuladed in a IPv6-in-IPv6 header addressed to the root. 431 The root removes the header and process the packet 433 +-------------------+------+--------------------+-------------------+ 434 | Header | IPv6 | 6LR | 6LBR | 435 +-------------------+------+--------------------+-------------------+ 436 | Inserted headers | -- | IPv6-in-IPv6(RPI) | -- | 437 | Removed headers | -- | -- | IPv6-in-IPv6(RPI) | 438 | Re-added headers | -- | -- | -- | 439 | Modified headers | -- | -- | -- | 440 | Untouched headers | -- | -- | -- | 441 +-------------------+------+--------------------+-------------------+ 443 Storing: Summary of the use of headers from not-RPL-aware-leaf to 444 root 446 5.5. Example of Flow from RPL-aware-leaf to Internet 448 RPL information from RFC 6553 should not go out to Internet. The 449 router should take this information out before send the packet to 450 Internet. The HBH Option is going to be analyzed in each node to the 451 root. 453 In this case the flow comprises: 455 RPL-aware-leaf (6LN) --> 6LR --> root (6LBR) --> Internet 457 6LN insert RPI in a IPv6-in-IPv6 in a outer header, and send the 458 packet to 6LR, which modified the rank in the RPI. When the packet 459 arrives to 6LBR, the RPI is removed. 461 +----------+-------------------+-----+-------------------+----------+ 462 | Header | 6LN | 6LR | 6LBR | Internet | 463 +----------+-------------------+-----+-------------------+----------+ 464 | Inserted | IPv6-in-IPv6(RPI) | -- | -- | -- | 465 | headers | | | | | 466 | Removed | -- | -- | IPv6-in-IPv6(RPI) | -- | 467 | headers | | | | | 468 | Re-added | -- | -- | -- | -- | 469 | headers | | | | | 470 | Modified | -- | RPI | -- | -- | 471 | headers | | | | | 472 | Untouche | -- | -- | -- | -- | 473 | d | | | | | 474 | headers | | | | | 475 +----------+-------------------+-----+-------------------+----------+ 477 Storing: Summary of the use of headers from RPL-aware-leaf to 478 Internet 480 5.6. Example of Flow from Internet to RPL-aware-leaf 482 In this case the flow comprises: 484 Internet --> root (6LBR) --> 6LR --> RPL-aware-leaf (6LN) 486 When the packet arrives from Internet to 6LBR the RPI header is added 487 in a outer IPv6-in-IPv6 header and send to 6LR, which modifies the 488 rank in the RPI. When the packet arrives 6LN the RPI header is 489 removed and the packet processed. 491 +----------+----------+-------------------+-----+-------------------+ 492 | Header | Internet | 6LBR | 6LR | 6LN | 493 +----------+----------+-------------------+-----+-------------------+ 494 | Inserted | -- | IPv6-in-IPv6(RPI) | -- | -- | 495 | headers | | | | | 496 | Removed | -- | -- | -- | IPv6-in-IPv6(RPI) | 497 | headers | | | | | 498 | Re-added | -- | -- | -- | -- | 499 | headers | | | | | 500 | Modified | -- | -- | RPI | -- | 501 | headers | | | | | 502 | Untouche | -- | -- | -- | -- | 503 | d | | | | | 504 | headers | | | | | 505 +----------+----------+-------------------+-----+-------------------+ 507 Storing: Summary of the use of headers from Internet to RPL-aware- 508 leaf 510 5.7. Example of Flow from not-RPL-aware-leaf to Internet 512 In this case the flow comprises: 514 not-RPL-aware-leaf (6LN) = IPv6 node --> 6LR --> root (6LBR) --> 515 Internet 517 In the IPv6 node the flow label is assumed to be zero, the packet is 518 transmited to 6LR which encapsule the RPI header in an outer IPv6-in- 519 IPv6 header and send to 6LBR, which removes this header and send the 520 packet to Internet and might set the flow label field. 522 +----------+-----+-------------------+-------------------+----------+ 523 | Header | IPv | 6LR | 6LBR | Internet | 524 | | 6 | | | | 525 +----------+-----+-------------------+-------------------+----------+ 526 | Inserted | -- | IPv6-in-IPv6(RPI) | -- | -- | 527 | headers | | | | | 528 | Removed | -- | -- | IPv6-in-IPv6(RPI) | -- | 529 | headers | | | | | 530 | Re-added | -- | -- | -- | -- | 531 | headers | | | | | 532 | Modified | -- | -- | -- | -- | 533 | headers | | | | | 534 | Untouche | -- | -- | -- | -- | 535 | d | | | | | 536 | headers | | | | | 537 +----------+-----+-------------------+-------------------+----------+ 539 Storing: Summary of the use of headers from not-RPL-aware-leaf to 540 Internet 542 5.8. Example of Flow from Internet to non-RPL-aware-leaf 544 In this case the flow comprises: 546 Internet --> root (6LBR) --> 6LR --> not-RPL-aware-leaf (6LN) 548 6LBR get the packet from Internet and add a RPI header encapsulated 549 in a IPv6-in-IPv6 header addressed to 6LR and send the packet down. 550 The flow label is set to zero on inner IP. The last 6LR removes the 551 RPI header. The IPv6 node might set the flow label since may arrive 552 with zero value. The 6LBR does not know that the is attached to the 553 last 6LR. The non-RPL-aware-leaf drops packet, because RPI has 554 unknown header 0x63, and 0x63 has "01" = discard packet. If RPI had 555 0x23, it would "skip". 557 +----------+---------+-------------------+-------------------+------+ 558 | Header | Interne | 6LBR | 6LR | IPv6 | 559 | | t | | | | 560 +----------+---------+-------------------+-------------------+------+ 561 | Inserted | -- | IPv6-in-IPv6(RPI) | -- | -- | 562 | headers | | | | | 563 | Removed | -- | -- | IPv6-in-IPv6(RPI) | -- | 564 | headers | | | | | 565 | Re-added | -- | -- | -- | -- | 566 | headers | | | | | 567 | Modified | -- | -- | -- | -- | 568 | headers | | | | | 569 | Untouche | -- | -- | -- | -- | 570 | d | | | | | 571 | headers | | | | | 572 +----------+---------+-------------------+-------------------+------+ 574 Storing: Summary of the use of headers from Internet to non-RPL- 575 aware-leaf 577 5.9. Example of Flow from RPL-aware-leaf to RPL-aware-leaf 579 In [RFC6550] RPL allows a simple one-hop P2P optimization for both 580 storing and non-storing networks. A node may send a P2P packet 581 destined to a one-hop neighbor directly to that node. Section 9 in 582 [RFC6550]. 584 In this case the flow comprises: 586 6LN --> 6LR --> common parent (6LR) --> 6LR --> 6LN 588 This case is assumed in the same RPL Domain. In the common parent, 589 the direction of RPI is changed (from increasing to decreasing the 590 rank). 592 +-------------+-------+---------------+---------------+-----+-------+ 593 | Header | 6LN | 6LR | 6LR (common | 6LR | 6LN | 594 | | src | | parent) | | dst | 595 +-------------+-------+---------------+---------------+-----+-------+ 596 | Inserted | RPI | -- | -- | -- | -- | 597 | headers | | | | | | 598 | Removed | -- | -- | -- | -- | RPI | 599 | headers | | | | | | 600 | Re-added | -- | -- | -- | -- | -- | 601 | headers | | | | | | 602 | Modified | -- | RPI | RPI | -- | -- | 603 | headers | | (decreasing | (increasing | | | 604 | | | rank) | rank) | | | 605 | Untouched | -- | -- | -- | -- | -- | 606 | headers | | | | | | 607 +-------------+-------+---------------+---------------+-----+-------+ 609 Storing: Summary of the use of headers for RPL-aware-leaf to RPL- 610 aware-leaf 612 5.10. Example of Flow from RPL-aware-leaf to non-RPL-aware-leaf 614 In this case the flow comprises: 616 6LN --> 6LR --> common parent (6LR) --> 6LR --> not-RPL-aware 6LN 618 Somehow, the sender has to know that the receiver is not RPL aware, 619 and needs to know 6LR, and not even the root knows where the 6LR is 620 (in storing mode). This case FAILS. This needs to be signaled. 621 Attribute of ::/0 route? Or implicit because destination not 622 matching PIO? If in doubt, add IPIP? IPIP dst = 6LBR (00) 623 +-------+------------+------------+-------------+-------------+-----+ 624 | Heade | 6LN | 6LR | 6LR (common | 6LR | IPv | 625 | r | | | parent) | | 6 | 626 +-------+------------+------------+-------------+-------------+-----+ 627 | Inser | IPv6-in- | -- | -- | -- | -- | 628 | ted h | IPv6(RPI) | | | | | 629 | eader | | | | | | 630 | s | | | | | | 631 | Remov | -- | -- | -- | IPv6-in- | -- | 632 | ed he | | | | IPv6(RPI) | | 633 | aders | | | | | | 634 | Re- | -- | -- | -- | -- | -- | 635 | added | | | | | | 636 | heade | | | | | | 637 | rs | | | | | | 638 | Modif | -- | IPv6-in- | IPv6-in- | -- | -- | 639 | ied h | | IPv6(RPI) | IPv6(RPI) | | | 640 | eader | | | | | | 641 | s | | | | | | 642 | Untou | -- | -- | -- | -- | -- | 643 | ched | | | | | | 644 | heade | | | | | | 645 | rs | | | | | | 646 +-------+------------+------------+-------------+-------------+-----+ 648 Storing: Summary of the use of headers from RPL-aware-leaf to not- 649 RPL-aware-leaf 651 5.11. Example of Flow from not-RPL-aware-leaf to RPL-aware-leaf 653 In this case the flow comprises: 655 not-RPL-aware 6LN --> 6LR --> common parent (6LR) --> 6LR --> 6LN 657 The 6LR that get the packet from IPv6 node, insert the RPI header 658 encapsulated in IPv6-in-IPv6 header with destination to 6LN, the 659 common parent change the direction of RPI and finally it is removed 660 by 6LN. 662 +-------+----+------------+-------------+-------------+-------------+ 663 | Heade | IP | 6LR | common | 6LR | 6LN | 664 | r | v6 | | parent | | | 665 | | | | (6LR) | | | 666 +-------+----+------------+-------------+-------------+-------------+ 667 | Inser | -- | IPv6-in- | -- | -- | -- | 668 | ted h | | IPv6(RPI) | | | | 669 | eader | | | | | | 670 | s | | | | | | 671 | Remov | -- | -- | -- | -- | IPv6-in- | 672 | ed he | | | | | IPv6(RPI) | 673 | aders | | | | | | 674 | Re- | -- | -- | -- | -- | -- | 675 | added | | | | | | 676 | heade | | | | | | 677 | rs | | | | | | 678 | Modif | -- | -- | IPv6-in- | IPv6-in- | -- | 679 | ied h | | | IPv6(RPI) | IPv6(RPI) | | 680 | eader | | | | | | 681 | s | | | | | | 682 | Untou | -- | -- | -- | -- | -- | 683 | ched | | | | | | 684 | heade | | | | | | 685 | rs | | | | | | 686 +-------+----+------------+-------------+-------------+-------------+ 688 Storing: Summary of the use of headers from not-RPL-aware-leaf to 689 RPL-aware-leaf 691 5.12. Example of Flow from not-RPL-aware-leaf to not-RPL-aware-leaf 693 In this case the flow comprises: 695 not-RPL-aware 6LN --> 6LR --> root (6LBR) --> 6LR --> not-RPL-aware 696 6LN 698 The problem to solve is how to indicate where to send the packet when 699 get into LLN. Should attributes be added to the border router 700 indicating this? 701 +---------+-----+----------------+---------+-----------------+------+ 702 | Header | IPv | 6LR | 6LR | 6LR | IPv6 | 703 | | 6 | | (common | | dst | 704 | | src | | parent) | | | 705 +---------+-----+----------------+---------+-----------------+------+ 706 | Inserte | -- | IPv6-in- | -- | -- | -- | 707 | d | | IPv6(RPI) | | | | 708 | headers | | | | | | 709 | Removed | -- | -- | -- | IPv6-in- | -- | 710 | headers | | | | IPv6(RPI) | | 711 | Re- | -- | -- | -- | -- | -- | 712 | added | | | | | | 713 | headers | | | | | | 714 | Modifie | -- | -- | -- | -- | -- | 715 | d | | | | | | 716 | headers | | | | | | 717 | Untouch | -- | -- | -- | -- | -- | 718 | ed | | | | | | 719 | headers | | | | | | 720 +---------+-----+----------------+---------+-----------------+------+ 722 Storing: Summary of the use of headers from not-RPL-aware-leaf to 723 not-RPL-aware-leaf 725 6. Non Storing mode 727 6.1. Example of Flow from RPL-aware-leaf to root 729 In non-storing mode the leaf node uses Hop-By-Hop option (RFC 6553) 730 to indicate the routing information to send messages to the DODAG 731 root, this message is going to be analyzed in each node until arrive 732 the DODAG root. 734 In this case not need to use IPv6-in-IPv6 because no header is not 735 going to be removed, neither RH3, the flow comprises: 737 RPL-aware-leaf (6LN) --> 6LR --> root (6LBR) 739 This case is the same case as storing mode. 741 +-------------------+-----+------+------+ 742 | Header | 6LN | 6LR | 6LBR | 743 +-------------------+-----+------+------+ 744 | Inserted headers | RPI | -- | -- | 745 | Removed headers | -- | -- | RPI | 746 | Re-added headers | -- | -- | -- | 747 | Modified headers | -- | RPI | -- | 748 | Untouched headers | -- | -- | -- | 749 +-------------------+-----+------+------+ 751 Non Storing: Summary of the use of headers from RPL-aware-leaf to 752 root 754 6.2. Example of Flow from root to RPL-aware-leaf 756 In this case the flow comprises: 758 root (6LBR)--> 6LR --> RPL-aware-leaf (6LN) 760 6LBR might instert RPI header, and the rute is indicated in RH3. 6LR 761 updated RH3 and 6LN remove these headers. 763 +-------------------+----------------------+------+----------+ 764 | Header | 6LBR | 6LR | 6LN | 765 +-------------------+----------------------+------+----------+ 766 | Inserted headers | (optional: RPI), RH3 | -- | -- | 767 | Removed headers | -- | -- | RH3,RPI | 768 | Re-added headers | -- | -- | -- | 769 | Modified headers | -- | RH3 | -- | 770 | Untouched headers | -- | -- | -- | 771 +-------------------+----------------------+------+----------+ 773 Non Storing: Summary of the use of headers from root to RPL-aware- 774 leaf 776 6.3. Example of Flow from root to not-RPL-aware-leaf 778 In this case the flow comprises: 780 root (6LBR)--> 6LR --> not-RPL-aware-leaf (IPv6 node) 782 In 6LBR the RH3 is added, and modified in 6LR where is fully 783 consumed, but left there. If the RPI is present, the IPv6 node which 784 does not understand it will drop it. To avoid it the RPI should be 785 removed before reach IPv6 node or it is recommended that RPI be 786 omitted. An IPv6-in-IPv6 header should be necessary in this case. 787 The DAO from 6LR about IPv6 could say if that the final IPv6 is not 788 RPL (RPI) capable. 790 +-------------------+------+-----+------+ 791 | Header | 6LBR | 6LR | IPv6 | 792 +-------------------+------+-----+------+ 793 | Inserted headers | RH3 | -- | -- | 794 | Removed headers | -- | -- | -- | 795 | Re-added headers | -- | -- | -- | 796 | Modified headers | -- | RH3 | -- | 797 | Untouched headers | -- | -- | -- | 798 +-------------------+------+-----+------+ 800 Non Storing: Summary of the use of headers from root to not-RPL- 801 aware-leaf 803 6.4. Example of Flow from not-RPL-aware-leaf to root 805 In this case the flow comprises: 807 IPv6-node --> 6LR1 --> 6LR2 --> root (6LBR) 809 In this case the RPI is encapsulated in the first 6LR, and is not 810 modified in the followings 6LRs. 812 +-------------+------+-------------------+------+-------------------+ 813 | Header | IPv6 | 6LR1 | 6LR2 | 6LBR | 814 +-------------+------+-------------------+------+-------------------+ 815 | Inserted | -- | IPv6-in-IPv6(RPI) | -- | -- | 816 | headers | | | | | 817 | Removed | -- | -- | -- | IPv6-in-IPv6(RPI) | 818 | headers | | | | | 819 | Re-added | -- | -- | -- | -- | 820 | headers | | | | | 821 | Modified | -- | -- | -- | -- | 822 | headers | | | | | 823 | Untouched | -- | IPv6-in-IPv6(RPI) | -- | -- | 824 | headers | | | | | 825 +-------------+------+-------------------+------+-------------------+ 827 Non Storing: Summary of the use of headers from not-RPL-aware-leaf to 828 root 830 6.5. Example of Flow from RPL-aware-leaf to Internet 832 In this case the flow comprises: 834 RPL-aware-leaf (6LN) --> 6LR --> root (6LBR) --> Internet 836 This case requires that the network is awareness of what is external 837 to the LLN. Internet node never sees RPI or IPv6-in-IPv6 header. In 838 the 6LBR the flow label is computed if it is zero. RPI remains 839 unmodified. 841 +----------+-------------------+-----+-------------------+----------+ 842 | Header | 6LN | 6LR | 6LBR | Internet | 843 +----------+-------------------+-----+-------------------+----------+ 844 | Inserted | IPV6-in-IPv6(RPI) | -- | -- | -- | 845 | headers | | | | | 846 | Removed | -- | -- | IPV6-in-IPv6(RPI) | -- | 847 | headers | | | | | 848 | Re-added | -- | -- | -- | -- | 849 | headers | | | | | 850 | Modified | -- | -- | -- | -- | 851 | headers | | | | | 852 | Untouche | -- | RPI | -- | -- | 853 | d | | | | | 854 | headers | | | | | 855 +----------+-------------------+-----+-------------------+----------+ 857 Non Storing: Summary of the use of headers from RPL-aware-leaf to 858 Internet 860 6.6. Example of Flow from Internet to RPL-aware-leaf 862 In this case the flow comprises: 864 Internet --> root (6LBR) --> 6LR --> RPL-aware-leaf (6LN) 866 If the last RH3 entry is the 6LR, then the IPv6-in-IPv6 will be 867 removed there, if the last entry is the 6LN, then the RH3 will go all 868 the way to the leaf. In 6LBR the flow label should be set to zero. 870 +---------+--------+-------------------------+----------------+-----+ 871 | Header | Intern | 6LBR | 6LR | 6LN | 872 | | et | | | | 873 +---------+--------+-------------------------+----------------+-----+ 874 | Inserte | -- | IPv6-in- | -- | -- | 875 | d | | IPv6(RH3,optional:RPI) | | | 876 | headers | | | | | 877 | Removed | -- | -- | IPv6-in-IPv6 | -- | 878 | headers | | | can be removed | | 879 | | | | if RH3 | | 880 | | | | consumed | | 881 | Re- | -- | -- | -- | -- | 882 | added | | | | | 883 | headers | | | | | 884 | Modifie | -- | -- | IPv6-in- | -- | 885 | d | | | IPv6(RH3) | | 886 | headers | | | | | 887 | Untouch | -- | -- | -- | -- | 888 | ed | | | | | 889 | headers | | | | | 890 +---------+--------+-------------------------+----------------+-----+ 892 Non Storing: Summary of the use of headers from Internet to RPL- 893 aware-leaf 895 6.7. Example of Flow from not-RPL-aware-leaf to Internet 897 In this case the flow comprises: 899 not-RPL-aware-leaf (6LN) --> 6LR --> root (6LBR) --> Internet 901 In this case the flow label is recommended to be zero in the IPv6 902 node. no RPL headers are added in the IPv6 node, since it is ignorant 903 of RPL. Internet node does not see special headers. In 6LBR the 904 flow label is computed if it is zero. 906 +----------+-----+-------------------+-------------------+----------+ 907 | Header | IPv | 6LR | 6LBR | Internet | 908 | | 6 | | | | 909 +----------+-----+-------------------+-------------------+----------+ 910 | Inserted | -- | IPv6-in-IPv6(RPI) | -- | -- | 911 | headers | | | | | 912 | Removed | -- | -- | IPv6-in-IPv6(RPI) | -- | 913 | headers | | | | | 914 | Re-added | -- | -- | -- | -- | 915 | headers | | | | | 916 | Modified | -- | -- | -- | -- | 917 | headers | | | | | 918 | Untouche | -- | -- | -- | -- | 919 | d | | | | | 920 | headers | | | | | 921 +----------+-----+-------------------+-------------------+----------+ 923 Non Storing: Summary of the use of headers from not-RPL-aware-leaf to 924 Internet 926 6.8. Example of Flow from Internet to non-RPL-aware-leaf 928 In this case the flow comprises: 930 Internet --> root (6LBR) --> 6LR --> not-RPL-aware-leaf (6LN) 932 In this case the flow label in 6LBR should be set zero in 6LBR, where 933 RH3 is inserted and optionally RHI. RH3 must end at 6LR. 935 In Non-Storing mode, root knows that the non-RPL-aware-leaf is 936 attached to the parent 6LR, and builds RH3 with IPv6-in-IPv6 with 937 this 6LR as destination. 939 +---------+--------+-------------------------+---------------+------+ 940 | Header | Intern | 6LBR | 6LR | IPv6 | 941 | | et | | | | 942 +---------+--------+-------------------------+---------------+------+ 943 | Inserte | -- | IPv6-in- | -- | -- | 944 | d | | IPv6(RH3,optional:RPI) | | | 945 | headers | | | | | 946 | Removed | -- | -- | IPv6-in- | -- | 947 | headers | | | IPv6(RH3, | | 948 | | | | RPI) | | 949 | Re- | -- | -- | -- | -- | 950 | added | | | | | 951 | headers | | | | | 952 | Modifie | -- | -- | -- | -- | 953 | d | | | | | 954 | headers | | | | | 955 | Untouch | -- | -- | -- | -- | 956 | ed | | | | | 957 | headers | | | | | 958 +---------+--------+-------------------------+---------------+------+ 960 NonStoring: Summary of the use of headers from Internet to non-RPL- 961 aware-leaf 963 6.9. Example of Flow from RPL-aware-leaf to RPL-aware-leaf 965 In this case the flow comprises: 967 6LN --> 6LR --> root (6LBR) --> 6LR --> 6LN 969 This case comprises in the same RPL Domain. In the 6LN the RPI 970 header is inserted. In the 6LBR the RH3 header is inserted in a 971 IPv6-in-IPv6 header and removed at the 6LN destination. 973 In case of the flow goes from RPL-aware-Leaf to RPL-aware-Leaf, the 974 RPI should be set in a IP-in-IP header, to avoid repetition of RPI 975 header. 977 +---------+---------------+---------------+-----+-------------------+ 978 | Header | 6LN src | 6LBR | 6LR | 6LN dst | 979 +---------+---------------+---------------+-----+-------------------+ 980 | Inserte | IPv6-in- | IPv6-in- | -- | -- | 981 | d | IPv6(RPI) | IPv6(RH3 to | | | 982 | headers | | 6LN,RPI) | | | 983 | | | {IP,payload} | | | 984 | Removed | -- | -- | -- | IPv6-in- | 985 | headers | | | | IPv6(RH3,RPI) | 986 | | | | | {IP,RPI,payload} | 987 | Re- | -- | -- | -- | -- | 988 | added | | | | | 989 | headers | | | | | 990 | Modifie | -- | -- | -- | -- | 991 | d | | | | | 992 | headers | | | | | 993 | Untouch | -- | -- | -- | -- | 994 | ed | | | | | 995 | headers | | | | | 996 +---------+---------------+---------------+-----+-------------------+ 998 Non Storing: Summary of the use of headers for RPL-aware-leaf to RPL- 999 aware-leaf 1001 6.10. Example of Flow from RPL-aware-leaf to not-RPL-aware-leaf 1003 In this case the flow comprises: 1005 6LN --> 6LR --> root (6LBR) --> 6LR --> not-RPL-aware 6LN 1007 The 6LN insert the RPI in a IPv6-in-IPv6 header, which is addressed 1008 to 6LBR. The 6LBR remove this RPI header and insert a RH3 header 1009 with an optional RPI. These headers are removed by 6LR before send 1010 the packet to the IPv6 node. 1012 +------------+-------------------+-------------+-------------+------+ 1013 | Header | 6LN | 6LBR | 6LR | IPv6 | 1014 +------------+-------------------+-------------+-------------+------+ 1015 | Inserted | IPv6-in-IPv6(RPI) | IPIP(RH3, | -- | -- | 1016 | headers | | opt RPI) | | | 1017 | Removed | -- | IPIP(RPI) | IPIP(RH3, | -- | 1018 | headers | | | opt RPI) | | 1019 | Re-added | -- | -- | -- | -- | 1020 | headers | | | | | 1021 | Modified | -- | -- | -- | -- | 1022 | headers | | | | | 1023 | Untouched | -- | -- | -- | -- | 1024 | headers | | | | | 1025 +------------+-------------------+-------------+-------------+------+ 1027 Non Storing: Summary of the use of headers from RPL-aware-leaf to 1028 not-RPL-aware-leaf 1030 6.11. Example of Flow from not-RPL-aware-leaf to RPL-aware-leaf 1032 In this case the flow comprises: 1034 not-RPL-aware 6LN --> 6LR --> root (6LBR) --> 6LR --> 6LN 1036 RPI is added in 6LR until the root and then removed, then RH3 is 1037 added and removed at destination. 1039 +-------------------+------+------------+-----------+------------+ 1040 | Header | IPv6 | 6LR | 6LBR | 6LN | 1041 +-------------------+------+------------+-----------+------------+ 1042 | Inserted headers | -- | IPIP(RPI) | IPIP(RH3) | -- | 1043 | Removed headers | -- | IPIP(RPI) | -- | IPIP(RH3) | 1044 | Re-added headers | -- | -- | -- | -- | 1045 | Modified headers | -- | -- | -- | -- | 1046 | Untouched headers | -- | -- | -- | -- | 1047 +-------------------+------+------------+-----------+------------+ 1049 Non Storing: Summary of the use of headers from not-RPL-aware-leaf to 1050 RPL-aware-leaf 1052 6.12. Example of Flow from not-RPL-aware-leaf to not-RPL-aware-leaf 1054 In this case the flow comprises: 1056 not-RPL-aware 6LN --> 6LR --> root (6LBR) --> 6LR --> not-RPL-aware 1057 6LN 1058 RPI is added in 6LR until the root and then might be removed, then 1059 RH3 is added. These headers are removed at 6LR before go to 1060 destination. 1062 +--------------+------+-----------+-----------+--------------+------+ 1063 | Header | IPv6 | 6LR | 6LBR | 6LR | IPv6 | 1064 +--------------+------+-----------+-----------+--------------+------+ 1065 | Inserted | -- | IPIP(RPI) | IPIP(RH3) | -- | -- | 1066 | headers | | | | | | 1067 | Removed | -- | -- | IPIP(RPI) | IPIP(RH3, | -- | 1068 | headers | | | | opt RPI) | | 1069 | Re-added | -- | -- | -- | -- | -- | 1070 | headers | | | | | | 1071 | Modified | -- | -- | -- | -- | -- | 1072 | headers | | | | | | 1073 | Untouched | -- | -- | -- | -- | -- | 1074 | headers | | | | | | 1075 +--------------+------+-----------+-----------+--------------+------+ 1077 Non Storing: Summary of the use of headers from not-RPL-aware-leaf to 1078 not-RPL-aware-leaf 1080 7. Future RPL work 1082 There are cases from above that are not clear how to send the 1083 information. It requires furhter analysis on how to proceed to send 1084 the information from source to destination. 1086 From the above cases, we have in storing mode: 1088 - Flow from RPL-aware-leaf to non-RPL-aware-leaf: Somehow, the sender 1089 has to know that the receiver is not RPL aware, and needs to know 1090 6LR, and not even the root knows where the 6LR is located. 1092 - Flow from not-RPL-aware-leaf to not-RPL-aware-leaf: The problem to 1093 solve is how to indicate where to send the packet when get into LLN. 1095 8. IANA Considerations 1097 There are no IANA considerations related to this document. 1099 9. Security Considerations 1101 TODO. 1103 10. Acknowledgments 1105 This work is partially funded by the FP7 Marie Curie Initial Training 1106 Network (ITN) METRICS project (grant agreement No. 607728). 1108 The authors would like to acknowledge the review, feedback, and 1109 comments of Thomas Watteyne, Xavier Vilajosana and Robert Cragie. 1111 To be completed with additional Acknowledgments. 1113 11. References 1115 11.1. Normative References 1117 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1118 Requirement Levels", BCP 14, RFC 2119, 1119 DOI 10.17487/RFC2119, March 1997, 1120 . 1122 [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., 1123 Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, 1124 JP., and R. Alexander, "RPL: IPv6 Routing Protocol for 1125 Low-Power and Lossy Networks", RFC 6550, 1126 DOI 10.17487/RFC6550, March 2012, 1127 . 1129 [RFC6553] Hui, J. and JP. Vasseur, "The Routing Protocol for Low- 1130 Power and Lossy Networks (RPL) Option for Carrying RPL 1131 Information in Data-Plane Datagrams", RFC 6553, 1132 DOI 10.17487/RFC6553, March 2012, 1133 . 1135 [RFC6554] Hui, J., Vasseur, JP., Culler, D., and V. Manral, "An IPv6 1136 Routing Header for Source Routes with the Routing Protocol 1137 for Low-Power and Lossy Networks (RPL)", RFC 6554, 1138 DOI 10.17487/RFC6554, March 2012, 1139 . 1141 11.2. Informative References 1143 [I-D.ietf-6lo-routing-dispatch] 1144 Thubert, P., Bormann, C., Toutain, L., and R. Cragie, 1145 "6LoWPAN Routing Header", draft-ietf-6lo-routing- 1146 dispatch-04 (work in progress), January 2016. 1148 [I-D.ietf-6tisch-architecture] 1149 Thubert, P., "An Architecture for IPv6 over the TSCH mode 1150 of IEEE 802.15.4", draft-ietf-6tisch-architecture-09 (work 1151 in progress), November 2015. 1153 [RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and 1154 Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January 1155 2014, . 1157 [Second6TischPlugtest] 1158 "2nd 6Tisch Plugtest", . 1161 Authors' Addresses 1163 Maria Ines Robles 1164 Ericsson 1165 Hirsalantie 11 1166 Jorvas 02420 1167 Finland 1169 Email: maria.ines.robles@ericsson.com 1171 Michael C. Richardson 1172 Sandelman Software Works 1173 470 Dawson Avenue 1174 Ottawa, ON K1Z 5V7 1175 CA 1177 Email: mcr+ietf@sandelman.ca 1178 URI: http://www.sandelman.ca/ 1180 Pascal Thubert 1181 Cisco Systems, Inc 1182 Village d'Entreprises Green Side 400, Avenue de Roumanille 1183 Batiment T3, Biot - Sophia Antipolis 06410 1184 France 1186 Email: pthubert@cisco.com