idnits 2.17.1 draft-robles-roll-useofrplinfo-02.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 (October 19, 2015) is 3105 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-30) exists of draft-ietf-6tisch-architecture-08 == Outdated reference: A later version (-07) exists of draft-thubert-6lo-routing-dispatch-06 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: April 21, 2016 SSW 6 P. Thubert 7 Cisco 8 October 19, 2015 10 When to use RFC 6553, 6554 and IPv6-in-IPv6 11 draft-robles-roll-useofrplinfo-02 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 April 21, 2016. 37 Copyright Notice 39 Copyright (c) 2015 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 not-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 not-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 . . . . . . . . . . . . . . . . . . . . . . . 27 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.thubert-6lo-routing-dispatch] defines a method 111 to compress RPL Option information and Routing Header type 3 112 (RFC6554) and an efficient IP-in-IP technique. 114 This document is going to be focused in data plane messages and how 115 can be transmitted within the above mentioned RFCs. 117 2. Terminology and Requirements Language 119 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 121 document are to be interpreted as described in RFC 2119 [RFC2119]. 123 Terminology defined in [RFC7102] 125 3. Sample/reference topology 127 A RPL network is composed of a 6LBR (6LoWPAN Border Router), Backbone 128 Router (6BBR), 6LR (6LoWPAN Router) and 6LN (6LoWPAN Node) as leaf 129 logically organized in a DODAG structure (Destination Oriented 130 Directed Acyclic Graph). 132 RPL defines the RPL Control messages (control plane ), a new ICMPv6 133 message with Type 155. DIS, DIO and DAO messages are all RPL Control 134 messages but with different Code values. 136 RPL supports two modes of Downward traffic: in storing mode, it is 137 fully stateful or an in non-storing, it is fully source routed. A 138 RPL Instance is either fully storing or fully non-storing, i.e. a RPL 139 Instance with a combination of storing and non-storing nodes is not 140 supported with the current specifications. 142 +--------------+ 143 | Upper Layers | 144 | | 145 +--------------+ 146 | RPL | 147 | | 148 +--------------+ 149 | ICMPv6 | 150 | | 151 +--------------+ 152 | IPv6 | 153 | | 154 +--------------+ 155 | 6LoWPAN | 156 | | 157 +--------------+ 158 | PHY-MAC | 159 | | 160 +--------------+ 162 Figure 1: RPL Stack. 164 +---------+ 165 +---+Internet | 166 | +---------+ 167 | 168 +----+--+ 169 |DODAG | 170 +---------+Root +----------+ 171 | |6LBR | | 172 | +----+--+ | 173 | | | 174 | | | 175 ... ... ... 176 | | | 177 +-----+-+ +--+---+ +--+---+ 178 |6LR | | | | | 179 +-----+ | | | | | 180 | | | | | | +------+ 181 | +-----+-+ +-+----+ +-+----+ | 182 | | | | | 183 | | | | | 184 | | | | | 185 +-+---+ +-+---+ +--+--+ +- --+ +---+-+ 186 |Leaf | | | | | | | | | 187 |6LN | | | | | | | | | 188 +-----+ +-----+ +-----+ +----+ +-----+ 190 Figure 2: A reference RPL Topology. 192 This document is in part motivated by the work that is ongoing at the 193 6TiSCH working group. The 6TiSCH architecture 194 [I-D.ietf-6tisch-architecture] draft explains the network 195 architecture of a 6TiSCH network. This architecture is used for the 196 remainder of this document. 198 The scope of the 6TiSCH Architecture is a Backbone Link that 199 federates multiple LLNs (mesh) as a single IPv6 Multi-Link Subnet. 200 Each LLN in the subnet is anchored at a Backbone Router (6BBR). The 201 Backbone Routers interconnect the LLNs over the Backbone Link and 202 emulate that the LLN nodes are present on the Backbone thus creating 203 a so-called: Multi-Link Subnet. An LLN node can move freely from an 204 LLN anchored at a Backbone Router to another LLN anchored at the same 205 or a different Backbone Router inside the Multi-Link Subnet and 206 conserve its addresses. 208 | 209 +-----+ 210 | | Border Router to the RPL domain 211 | | (may be a RPL virtual root) 212 +-----+ 213 | 214 | Backbone 215 +-------------------+-------------------+ 216 | | | 217 +-----+ +-----+ +-----+ 218 | | Backbone | | Backbone | | Backbone 219 | | router | | router | | router 220 +|---|+ +-|||-+ +-[_]-+ 221 | | PCI-exp / | \ USB | Ethernet 222 ( ) ( ) ( )( )( ) (6LBR == RPL DODAG root) 223 o o o o o o o o o o o o 224 o o o o o o o o o o o o o o o o 225 o o o o o o o o o o 6LR == RPL router) o o 226 o o o o o o o z 227 o o o o o o (6LoWPAN Host) 229 <----------------------- RPL Instance ------------------------> 231 Figure 3: RPL domain architecture 233 4. Use cases 235 In data plane context a combination of RFC6553, RFC6554 and IPv6-in- 236 IPv6 encapsulation is going to be analyzed for the following traffic 237 flows: 239 -Flow from RPL-aware-leaf to root 241 -Flow from root to RPL-aware-leaf 243 -Flow from not-RPL-aware-leaf to root 245 -Flow from root to not-RPL-aware-leaf 247 -Flow from RPL-aware-leaf to Internet 249 -Flow from Internet to RPL-aware-leaf 251 -Flow from not-RPL-aware-leaf to Internet 253 -Flow from Internet to not-RPL-aware-leaf 254 -Flow from RPL-aware-leaf to RPL-aware-leaf 256 -Flow from RPL-aware-leaf to not-RPL-aware-leaf 258 -Flow from not-RPL-aware-leaf to RPL-aware-leaf 260 -Flow from not-RPL-aware-leaf to not-RPL-aware-leaf 262 This document assumes a rule that a Header cannot be inserted or 263 removed on the fly inside an IPv6 packet that is being routed. 265 - This means that an intermediate router that needs to add a header 266 must encapsulate the packet in an outer IP header where the new 267 header can be placed. 269 - This also means that a Header can only be removed by an 270 intermediate router if it is placed in an encapsulating IPv6 Header, 271 and in that case, the whole encapsulating header must be removed - a 272 replacement may be added. 274 This document recognizes that some headers such as a Routing Header 275 or a Hop-by-Hop header may be modified by routers on the path of the 276 packet without the need to add to remove an encapsulating header. 278 The RPL RH and the RPL option are mutable but recoverable . 280 RPI should be present in every single RPL data packet. There is an 281 exception in non-storing mode, when a packet is going down from the 282 route: the entire route is written, so there are no loops of 283 confusion about which table to use (purpose of instanceID). 285 The applicability for storing (RPL-SN) and non-Storing (RPL-NSN) 286 modes for the previous cases is showed as follows: 288 +---------------+------+------+---------+--------+--------+---------+ 289 | Use Case | RPL- | RPL- | RPL-SN | RPL- | RPL- | RPL-NSN | 290 | | SN | SN | IP-in- | NSN | NSN | IP-in- | 291 | | RPI | RH3 | IP | RPI | RH3 | IP | 292 | | (RFC | (RFC | | | | | 293 | | 6553 | 6554 | | | | | 294 | | ) | ) | | | | | 295 +---------------+------+------+---------+--------+--------+---------+ 296 | RPL-aware- | Yes | No | No | Yes | No | No | 297 | leaf to root | | | | | | | 298 | root to RPL- | Yes | No | No | Yes | Yes | No | 299 | aware-leaf | | | | | | | 300 | not-RPL- | Yes | No | Yes | Yes | No | Yes | 301 | aware-leaf to | | | | | | | 302 | root | | | | | | | 303 | root to not- | Yes | No | Yes | Yes | Yes | Yes | 304 | RPL-aware- | | | | | | | 305 | leaf | | | | | | | 306 | RPL-aware- | Yes | No | Yes | Yes | No | Yes | 307 | leaf to | | | | | | | 308 | Internet | | | | | | | 309 | Internet to | Yes | No | Yes | Yes | Yes | Yes | 310 | RPL-aware- | | | | | | | 311 | leaf | | | | | | | 312 | not-RPL- | Yes | No | Yes | Yes | No | Yes | 313 | aware-leaf to | | | | | | | 314 | Internet | | | | | | | 315 | Internet to | Yes | No | Yes | Yes | Yes | Yes | 316 | not-RPL- | | | | | | | 317 | aware-leaf | | | | | | | 318 | RPL-aware- | Yes | No | No | Yes | Yes | Yes | 319 | leaf to RPL- | | | | | | | 320 | aware-leaf | | | | | | | 321 | RPL-aware- | Yes | No | Yes | Yes | Yes | Yes | 322 | leaf to not- | | | | | | | 323 | RPL-aware- | | | | | | | 324 | leaf | | | | | | | 325 | not-RPL- | Yes | No | Yes | Yes | Yes | Yes | 326 | aware-leaf to | | | | | | | 327 | RPL-aware- | | | | | | | 328 | leaf | | | | | | | 329 | not-RPL- | Yes | No | Yes | Yes | Yes | Yes | 330 | aware-leaf to | | | | | | | 331 | not-RPL- | | | | | | | 332 | aware-leaf | | | | | | | 333 +---------------+------+------+---------+--------+--------+---------+ 335 Table 1: Posibility to transmit in Storing or Non-Storing mode: RPI, 336 RH3, IP-in-IP encapsulation 338 5. Storing mode 340 5.1. Example of Flow from RPL-aware-leaf to root 342 As states in Section 16.2 of [RFC6550] a RPL-aware-leaf node does 343 not generally issue DIO messages, a leaf node accepts DIO messages 344 (In inconsistency a leaf node generates DIO with infinite rank, to 345 fix it). It may issue DAO and DIS messages though it generally 346 ignores DAO and DIS messages. 348 In storing mode is suitable the use of RFC 6553 to send RPL 349 Information through HBH field checking the routing table to find out 350 where to send the message. 352 In this case the flow comprises: 354 RPL-aware-leaf (6LN) --> 6LR --> 6LR,... --> root (6LBR) Note: In 355 this document 6LRs, 6LBR are always full-fledge RPL routers 357 The 6LN inserts the RPI header, and send the packet to 6LR which 358 decrement the rank in RPI and send the packet up. When the packet 359 arrives to 6LBR, the RPI is removed and the packet is processed. 361 +-------------------+-----+------+------+ 362 | Header | 6LN | 6LR | 6LBR | 363 +-------------------+-----+------+------+ 364 | Inserted headers | RPI | -- | -- | 365 | Removed headers | -- | -- | RPI | 366 | Re-added headers | -- | -- | -- | 367 | Modified headers | -- | RPI | -- | 368 | Untouched headers | -- | -- | -- | 369 +-------------------+-----+------+------+ 371 Storing: Summary of the use of headers from RPL-aware-leaf to root 373 5.2. Example of Flow from root to RPL-aware-leaf 375 In this case the flow comprises: 377 root (6LBR)--> 6LR --> RPL-aware-leaf (6LN) 379 In this case the 6LBR insert RPI header and send the packet down, the 380 6LR is going to increment the rank in RPI (examines instanceID for 381 multiple tables), the packet is processed in 6LN and RPI removed. 383 +-------------------+------+-------+------+ 384 | Header | 6LBR | 6LR | 6LN | 385 +-------------------+------+-------+------+ 386 | Inserted headers | RPI | -- | -- | 387 | Removed headers | -- | -- | RPI | 388 | Re-added headers | -- | -- | -- | 389 | Modified headers | -- | RPI | -- | 390 | Untouched headers | -- | -- | -- | 391 +-------------------+------+-------+------+ 393 Storing: Summary of the use of headers from root to RPL-aware-leaf 395 5.3. Example of Flow from root to not-RPL-aware-leaf 397 In this case the flow comprises: 399 root (6LBR)--> 6LR --> not-RPL-aware-leaf (6LN) 401 It includes IPv6-in-IPv6 encapsulation to transmit information not 402 related with the RPL domain. In the 6LBR the RPI header is inserted 403 into an IPv6-in-IPv6 header addressed to the last 6LR, which removes 404 the header before pass the packet to the IPv6 node. 406 +-------------------+-------------------+-------------------+------+ 407 | Header | 6LBR | 6LR | IPv6 | 408 +-------------------+-------------------+-------------------+------+ 409 | Inserted headers | IPv6-in-IPv6(RPI) | -- | -- | 410 | Removed headers | -- | IPv6-in-IPv6(RPI) | -- | 411 | Re-added headers | -- | -- | -- | 412 | Modified headers | -- | -- | -- | 413 | Untouched headers | -- | -- | -- | 414 +-------------------+-------------------+-------------------+------+ 416 Storing: Summary of the use of headers from root to not-RPL-aware- 417 leaf 419 5.4. Example of Flow from not-RPL-aware-leaf to root 421 In this case the flow comprises: 423 not-RPL-aware-leaf (6LN) --> 6LR --> root (6LBR) 425 When the packet arrives from IPv6 node to 6LR. This router insert 426 the RPI encapsuladed in a IPv6-in-IPv6 header addressed to the root. 427 The root removes the header and process the packet 429 +-------------------+------+--------------------+-------------------+ 430 | Header | IPv6 | 6LR | 6LBR | 431 +-------------------+------+--------------------+-------------------+ 432 | Inserted headers | -- | IPv6-in-IPv6(RPI) | -- | 433 | Removed headers | -- | -- | IPv6-in-IPv6(RPI) | 434 | Re-added headers | -- | -- | -- | 435 | Modified headers | -- | -- | -- | 436 | Untouched headers | -- | -- | -- | 437 +-------------------+------+--------------------+-------------------+ 439 Storing: Summary of the use of headers from not-RPL-aware-leaf to 440 root 442 5.5. Example of Flow from RPL-aware-leaf to Internet 444 RPL information from RFC 6553 should not go out to Internet. The 445 router should take this information out before send the packet to 446 Internet. The HBH Option is going to be analyzed in each node to the 447 root. 449 In this case the flow comprises: 451 RPL-aware-leaf (6LN) --> 6LR --> root (6LBR) --> Internet 453 6LN insert RPI in a IPv6-in-IPv6 in a outer header, and send the 454 packet to 6LR, which modified the rank in the RPI. When the packet 455 arrives to 6LBR, the RPI is removed. 457 +----------+-------------------+-----+-------------------+----------+ 458 | Header | 6LN | 6LR | 6LBR | Internet | 459 +----------+-------------------+-----+-------------------+----------+ 460 | Inserted | IPv6-in-IPv6(RPI) | -- | -- | -- | 461 | headers | | | | | 462 | Removed | -- | -- | IPv6-in-IPv6(RPI) | -- | 463 | headers | | | | | 464 | Re-added | -- | -- | -- | -- | 465 | headers | | | | | 466 | Modified | -- | RPI | -- | -- | 467 | headers | | | | | 468 | Untouche | -- | -- | -- | -- | 469 | d | | | | | 470 | headers | | | | | 471 +----------+-------------------+-----+-------------------+----------+ 473 Storing: Summary of the use of headers from RPL-aware-leaf to 474 Internet 476 5.6. Example of Flow from Internet to RPL-aware-leaf 478 In this case the flow comprises: 480 Internet --> root (6LBR) --> 6LR --> RPL-aware-leaf (6LN) 482 When the packet arrives from Internet to 6LBR the RPI header is added 483 in a outer IPv6-in-IPv6 header and send to 6LR, which modifies the 484 rank in the RPI. When the packet arrives 6LN the RPI header is 485 removed and the packet processed. 487 +----------+----------+-------------------+-----+-------------------+ 488 | Header | Internet | 6LBR | 6LR | 6LN | 489 +----------+----------+-------------------+-----+-------------------+ 490 | Inserted | -- | IPv6-in-IPv6(RPI) | -- | -- | 491 | headers | | | | | 492 | Removed | -- | -- | -- | IPv6-in-IPv6(RPI) | 493 | headers | | | | | 494 | Re-added | -- | -- | -- | -- | 495 | headers | | | | | 496 | Modified | -- | -- | RPI | -- | 497 | headers | | | | | 498 | Untouche | -- | -- | -- | -- | 499 | d | | | | | 500 | headers | | | | | 501 +----------+----------+-------------------+-----+-------------------+ 503 Storing: Summary of the use of headers from Internet to RPL-aware- 504 leaf 506 5.7. Example of Flow from not-RPL-aware-leaf to Internet 508 In this case the flow comprises: 510 not-RPL-aware-leaf (6LN) = IPv6 node --> 6LR --> root (6LBR) --> 511 Internet 513 In the IPv6 node the flow label is assumed to be zero, the packet is 514 transmited to 6LR which encapsule the RPI header in an outer IPv6-in- 515 IPv6 header and send to 6LBR, which removes this header and send the 516 packet to Internet and might set the flow label field. 518 +----------+-----+-------------------+-------------------+----------+ 519 | Header | IPv | 6LR | 6LBR | Internet | 520 | | 6 | | | | 521 +----------+-----+-------------------+-------------------+----------+ 522 | Inserted | -- | IPv6-in-IPv6(RPI) | -- | -- | 523 | headers | | | | | 524 | Removed | -- | -- | IPv6-in-IPv6(RPI) | -- | 525 | headers | | | | | 526 | Re-added | -- | -- | -- | -- | 527 | headers | | | | | 528 | Modified | -- | -- | -- | -- | 529 | headers | | | | | 530 | Untouche | -- | -- | -- | -- | 531 | d | | | | | 532 | headers | | | | | 533 +----------+-----+-------------------+-------------------+----------+ 535 Storing: Summary of the use of headers from not-RPL-aware-leaf to 536 Internet 538 5.8. Example of Flow from Internet to not-RPL-aware-leaf 540 In this case the flow comprises: 542 Internet --> root (6LBR) --> 6LR --> not-RPL-aware-leaf (6LN) 544 6LBR get the packet from Internet and add a RPI header encapsulated 545 in a IPv6-in-IPv6 header addressed to 6LR and send the packet down. 546 The flow label is set to zero on inner IP. The last 6LR removes the 547 RPI header. The IPv6 node might set the flow label since may arrive 548 with zero value. 550 +----------+---------+-------------------+-------------------+------+ 551 | Header | Interne | 6LBR | 6LR | IPv6 | 552 | | t | | | | 553 +----------+---------+-------------------+-------------------+------+ 554 | Inserted | -- | IPv6-in-IPv6(RPI) | -- | -- | 555 | headers | | | | | 556 | Removed | -- | -- | IPv6-in-IPv6(RPI) | -- | 557 | headers | | | | | 558 | Re-added | -- | -- | -- | -- | 559 | headers | | | | | 560 | Modified | -- | -- | -- | -- | 561 | headers | | | | | 562 | Untouche | -- | -- | -- | -- | 563 | d | | | | | 564 | headers | | | | | 565 +----------+---------+-------------------+-------------------+------+ 567 Storing: Summary of the use of headers from Internet to not-RPL- 568 aware-leaf 570 5.9. Example of Flow from RPL-aware-leaf to RPL-aware-leaf 572 In [RFC6550] RPL allows a simple one-hop P2P optimization for both 573 storing and non-storing networks. A node may send a P2P packet 574 destined to a one-hop neighbor directly to that node. Section 9 in 575 [RFC6550]. 577 In this case the flow comprises: 579 6LN --> 6LR --> common parent (6LR) --> 6LR --> 6LN 581 This case is assumed in the same RPL Domain. In the common parent, 582 the direction of RPI is changed (from increasing to decreasing the 583 rank). 585 +-------------+-------+---------------+---------------+-----+-------+ 586 | Header | 6LN | 6LR | 6LR (common | 6LR | 6LN | 587 | | src | | parent) | | dst | 588 +-------------+-------+---------------+---------------+-----+-------+ 589 | Inserted | RPI | -- | -- | -- | -- | 590 | headers | | | | | | 591 | Removed | -- | -- | -- | -- | RPI | 592 | headers | | | | | | 593 | Re-added | -- | -- | -- | -- | -- | 594 | headers | | | | | | 595 | Modified | -- | RPI | RPI | -- | -- | 596 | headers | | (decreasing | (increasing | | | 597 | | | rank) | rank) | | | 598 | Untouched | -- | -- | -- | -- | -- | 599 | headers | | | | | | 600 +-------------+-------+---------------+---------------+-----+-------+ 602 Storing: Summary of the use of headers for RPL-aware-leaf to RPL- 603 aware-leaf 605 5.10. Example of Flow from RPL-aware-leaf to non-RPL-aware-leaf 607 In this case the flow comprises: 609 6LN --> 6LR --> common parent (6LR) --> 6LR --> not-RPL-aware 6LN 611 Somehow, the sender has to know that the receiver is not RPL aware, 612 and needs to know 6LR, and not even the root knows where the 6LR is 613 (in storing mode). This case FAILS. 615 +-------+------------+------------+-------------+-------------+-----+ 616 | Heade | 6LN | 6LR | 6LR (common | 6LR | IPv | 617 | r | | | parent) | | 6 | 618 +-------+------------+------------+-------------+-------------+-----+ 619 | Inser | IPv6-in- | -- | -- | -- | -- | 620 | ted h | IPv6(RPI) | | | | | 621 | eader | | | | | | 622 | s | | | | | | 623 | Remov | -- | -- | -- | IPv6-in- | -- | 624 | ed he | | | | IPv6(RPI) | | 625 | aders | | | | | | 626 | Re- | -- | -- | -- | -- | -- | 627 | added | | | | | | 628 | heade | | | | | | 629 | rs | | | | | | 630 | Modif | -- | IPv6-in- | IPv6-in- | -- | -- | 631 | ied h | | IPv6(RPI) | IPv6(RPI) | | | 632 | eader | | | | | | 633 | s | | | | | | 634 | Untou | -- | -- | -- | -- | -- | 635 | ched | | | | | | 636 | heade | | | | | | 637 | rs | | | | | | 638 +-------+------------+------------+-------------+-------------+-----+ 640 Storing: Summary of the use of headers from RPL-aware-leaf to not- 641 RPL-aware-leaf 643 5.11. Example of Flow from not-RPL-aware-leaf to RPL-aware-leaf 645 In this case the flow comprises: 647 not-RPL-aware 6LN --> 6LR --> common parent (6LR) --> 6LR --> 6LN 649 The 6LR that get the packet from IPv6 node, insert the RPI header 650 encapsulated in IPv6-in-IPv6 header with destination to 6LN, the 651 common parent change the direction of RPI and finally it is removed 652 by 6LN. 654 +-------+----+------------+-------------+-------------+-------------+ 655 | Heade | IP | 6LR | common | 6LR | 6LN | 656 | r | v6 | | parent | | | 657 | | | | (6LR) | | | 658 +-------+----+------------+-------------+-------------+-------------+ 659 | Inser | -- | IPv6-in- | -- | -- | -- | 660 | ted h | | IPv6(RPI) | | | | 661 | eader | | | | | | 662 | s | | | | | | 663 | Remov | -- | -- | -- | -- | IPv6-in- | 664 | ed he | | | | | IPv6(RPI) | 665 | aders | | | | | | 666 | Re- | -- | -- | -- | -- | -- | 667 | added | | | | | | 668 | heade | | | | | | 669 | rs | | | | | | 670 | Modif | -- | -- | IPv6-in- | IPv6-in- | -- | 671 | ied h | | | IPv6(RPI) | IPv6(RPI) | | 672 | eader | | | | | | 673 | s | | | | | | 674 | Untou | -- | -- | -- | -- | -- | 675 | ched | | | | | | 676 | heade | | | | | | 677 | rs | | | | | | 678 +-------+----+------------+-------------+-------------+-------------+ 680 Storing: Summary of the use of headers from not-RPL-aware-leaf to 681 RPL-aware-leaf 683 5.12. Example of Flow from not-RPL-aware-leaf to not-RPL-aware-leaf 685 In this case the flow comprises: 687 not-RPL-aware 6LN --> 6LR --> root (6LBR) --> 6LR --> not-RPL-aware 688 6LN 690 The problem to solve is how to indicate where to send the packet when 691 get into LLN. 693 +---------+-----+----------------+---------+-----------------+------+ 694 | Header | IPv | 6LR | 6LR | 6LR | IPv6 | 695 | | 6 | | (common | | dst | 696 | | src | | parent) | | | 697 +---------+-----+----------------+---------+-----------------+------+ 698 | Inserte | -- | IPv6-in- | -- | -- | -- | 699 | d | | IPv6(RPI) | | | | 700 | headers | | | | | | 701 | Removed | -- | -- | -- | IPv6-in- | -- | 702 | headers | | | | IPv6(RPI) | | 703 | Re- | -- | -- | -- | -- | -- | 704 | added | | | | | | 705 | headers | | | | | | 706 | Modifie | -- | -- | -- | -- | -- | 707 | d | | | | | | 708 | headers | | | | | | 709 | Untouch | -- | -- | -- | -- | -- | 710 | ed | | | | | | 711 | headers | | | | | | 712 +---------+-----+----------------+---------+-----------------+------+ 714 Storing: Summary of the use of headers from not-RPL-aware-leaf to 715 not-RPL-aware-leaf 717 6. Non Storing mode 719 6.1. Example of Flow from RPL-aware-leaf to root 721 In non-storing mode the leaf node uses Hop-By-Hop option (RFC 6553) 722 to indicate the routing information to send messages to the DODAG 723 root, this message is going to be analyzed in each node until arrive 724 the DODAG root. 726 In this case not need to use IPv6-in-IPv6 because no header is not 727 going to be removed, neither RH3, the flow comprises: 729 RPL-aware-leaf (6LN) --> 6LR --> root (6LBR) 731 This case is the same case as storing mode. 733 +-------------------+-----+------+------+ 734 | Header | 6LN | 6LR | 6LBR | 735 +-------------------+-----+------+------+ 736 | Inserted headers | RPI | -- | -- | 737 | Removed headers | -- | -- | RPI | 738 | Re-added headers | -- | -- | -- | 739 | Modified headers | -- | RPI | -- | 740 | Untouched headers | -- | -- | -- | 741 +-------------------+-----+------+------+ 743 Non Storing: Summary of the use of headers from RPL-aware-leaf to 744 root 746 6.2. Example of Flow from root to RPL-aware-leaf 748 In this case the flow comprises: 750 root (6LBR)--> 6LR --> RPL-aware-leaf (6LN) 752 6LBR might instert RPI header, and the rute is indicated in RH3. 6LR 753 updated RH3 and 6LN remove these headers. 755 +-------------------+----------------------+------+----------+ 756 | Header | 6LBR | 6LR | 6LN | 757 +-------------------+----------------------+------+----------+ 758 | Inserted headers | (optional: RPI), RH3 | -- | -- | 759 | Removed headers | -- | -- | RH3,RPI | 760 | Re-added headers | -- | -- | -- | 761 | Modified headers | -- | RH3 | -- | 762 | Untouched headers | -- | -- | -- | 763 +-------------------+----------------------+------+----------+ 765 Non Storing: Summary of the use of headers from root to RPL-aware- 766 leaf 768 6.3. Example of Flow from root to not-RPL-aware-leaf 770 In this case the flow comprises: 772 root (6LBR)--> 6LR --> not-RPL-aware-leaf (IPv6 node) 774 In 6LBR the RH3 is added, and modified in 6LR where is fully 775 consumed, but left there. If the RPI is present, the IPv6 node which 776 does not understand it will drop it. To avoid it the RPI should be 777 removed before reach IPv6 node or it is recommended that RPI be 778 omitted. An IPv6-in-IPv6 header should be necessary in this case. 779 The DAO from 6LR about IPv6 could say if that the final IPv6 is not 780 RPL (RPI) capable. 782 +-------------------+------+-----+------+ 783 | Header | 6LBR | 6LR | IPv6 | 784 +-------------------+------+-----+------+ 785 | Inserted headers | RH3 | -- | -- | 786 | Removed headers | -- | -- | -- | 787 | Re-added headers | -- | -- | -- | 788 | Modified headers | -- | RH3 | -- | 789 | Untouched headers | -- | -- | -- | 790 +-------------------+------+-----+------+ 792 Non Storing: Summary of the use of headers from root to not-RPL- 793 aware-leaf 795 6.4. Example of Flow from not-RPL-aware-leaf to root 797 In this case the flow comprises: 799 IPv6-node --> 6LR1 --> 6LR2 --> root (6LBR) 801 In this case the RPI is encapsulated in the first 6LR, and is not 802 modified in the followings 6LRs. 804 +-------------+------+-------------------+------+-------------------+ 805 | Header | IPv6 | 6LR1 | 6LR2 | 6LBR | 806 +-------------+------+-------------------+------+-------------------+ 807 | Inserted | -- | IPv6-in-IPv6(RPI) | -- | -- | 808 | headers | | | | | 809 | Removed | -- | -- | -- | IPv6-in-IPv6(RPI) | 810 | headers | | | | | 811 | Re-added | -- | -- | -- | -- | 812 | headers | | | | | 813 | Modified | -- | -- | -- | -- | 814 | headers | | | | | 815 | Untouched | -- | IPv6-in-IPv6(RPI) | -- | -- | 816 | headers | | | | | 817 +-------------+------+-------------------+------+-------------------+ 819 Non Storing: Summary of the use of headers from not-RPL-aware-leaf to 820 root 822 6.5. Example of Flow from RPL-aware-leaf to Internet 824 In this case the flow comprises: 826 RPL-aware-leaf (6LN) --> 6LR --> root (6LBR) --> Internet 828 This case requires that the network is awareness of what is external 829 to the LLN. Internet node never sees RPI or IPv6-in-IPv6 header. In 830 the 6LBR the flow label is computed if it is zero. RPI remains 831 unmodified. 833 +----------+-------------------+-----+-------------------+----------+ 834 | Header | 6LN | 6LR | 6LBR | Internet | 835 +----------+-------------------+-----+-------------------+----------+ 836 | Inserted | IPV6-in-IPv6(RPI) | -- | -- | -- | 837 | headers | | | | | 838 | Removed | -- | -- | IPV6-in-IPv6(RPI) | -- | 839 | headers | | | | | 840 | Re-added | -- | -- | -- | -- | 841 | headers | | | | | 842 | Modified | -- | -- | -- | -- | 843 | headers | | | | | 844 | Untouche | -- | RPI | -- | -- | 845 | d | | | | | 846 | headers | | | | | 847 +----------+-------------------+-----+-------------------+----------+ 849 Non Storing: Summary of the use of headers from RPL-aware-leaf to 850 Internet 852 6.6. Example of Flow from Internet to RPL-aware-leaf 854 In this case the flow comprises: 856 Internet --> root (6LBR) --> 6LR --> RPL-aware-leaf (6LN) 858 If the last RH3 entry is the 6LR, then the IPv6-in-IPv6 will be 859 removed there, if the last entry is the 6LN, then the RH3 will go all 860 the way to the leaf. In 6LBR the flow label should be set to zero. 862 +---------+--------+-------------------------+----------------+-----+ 863 | Header | Intern | 6LBR | 6LR | 6LN | 864 | | et | | | | 865 +---------+--------+-------------------------+----------------+-----+ 866 | Inserte | -- | IPv6-in- | -- | -- | 867 | d | | IPv6(RH3,optional:RPI) | | | 868 | headers | | | | | 869 | Removed | -- | -- | IPv6-in-IPv6 | -- | 870 | headers | | | can be removed | | 871 | | | | if RH3 | | 872 | | | | consumed | | 873 | Re- | -- | -- | -- | -- | 874 | added | | | | | 875 | headers | | | | | 876 | Modifie | -- | -- | IPv6-in- | -- | 877 | d | | | IPv6(RH3) | | 878 | headers | | | | | 879 | Untouch | -- | -- | -- | -- | 880 | ed | | | | | 881 | headers | | | | | 882 +---------+--------+-------------------------+----------------+-----+ 884 Non Storing: Summary of the use of headers from Internet to RPL- 885 aware-leaf 887 6.7. Example of Flow from not-RPL-aware-leaf to Internet 889 In this case the flow comprises: 891 not-RPL-aware-leaf (6LN) --> 6LR --> root (6LBR) --> Internet 893 In this case the flow label is recommended to be zero in the IPv6 894 node. no RPL headers are added in the IPv6 node, since it is ignorant 895 of RPL. Internet node does not see special headers. In 6LBR the 896 flow label is computed if it is zero. 898 +----------+-----+-------------------+-------------------+----------+ 899 | Header | IPv | 6LR | 6LBR | Internet | 900 | | 6 | | | | 901 +----------+-----+-------------------+-------------------+----------+ 902 | Inserted | -- | IPv6-in-IPv6(RPI) | -- | -- | 903 | headers | | | | | 904 | Removed | -- | -- | IPv6-in-IPv6(RPI) | -- | 905 | headers | | | | | 906 | Re-added | -- | -- | -- | -- | 907 | headers | | | | | 908 | Modified | -- | -- | -- | -- | 909 | headers | | | | | 910 | Untouche | -- | -- | -- | -- | 911 | d | | | | | 912 | headers | | | | | 913 +----------+-----+-------------------+-------------------+----------+ 915 Non Storing: Summary of the use of headers from not-RPL-aware-leaf to 916 Internet 918 6.8. Example of Flow from Internet to not-RPL-aware-leaf 920 In this case the flow comprises: 922 Internet --> root (6LBR) --> 6LR --> not-RPL-aware-leaf (6LN) 924 In this case the flow label in 6LBR should be set zero in 6LBR, where 925 RH3 is inserted and optionally RHI. RH3 must end at 6LR. 927 +---------+--------+-------------------------+---------------+------+ 928 | Header | Intern | 6LBR | 6LR | IPv6 | 929 | | et | | | | 930 +---------+--------+-------------------------+---------------+------+ 931 | Inserte | -- | IPv6-in- | -- | -- | 932 | d | | IPv6(RH3,optional:RPI) | | | 933 | headers | | | | | 934 | Removed | -- | -- | IPv6-in- | -- | 935 | headers | | | IPv6(RH3, | | 936 | | | | RPI) | | 937 | Re- | -- | -- | -- | -- | 938 | added | | | | | 939 | headers | | | | | 940 | Modifie | -- | -- | -- | -- | 941 | d | | | | | 942 | headers | | | | | 943 | Untouch | -- | -- | -- | -- | 944 | ed | | | | | 945 | headers | | | | | 946 +---------+--------+-------------------------+---------------+------+ 948 NonStoring: Summary of the use of headers from Internet to not-RPL- 949 aware-leaf 951 6.9. Example of Flow from RPL-aware-leaf to RPL-aware-leaf 953 In this case the flow comprises: 955 6LN --> 6LR --> root (6LBR) --> 6LR --> 6LN 957 This case comprises in the same RPL Domain. In the 6LN the RPI 958 header is inserted. In the 6LBR the RH3 header is inserted in a 959 IPv6-in-IPv6 header and removed at the 6LN destination. 961 +-----------+------+---------------------+-----+--------------------+ 962 | Header | 6LN | 6LBR | 6LR | 6LN dst | 963 | | src | | | | 964 +-----------+------+---------------------+-----+--------------------+ 965 | Inserted | RPI | IPv6-in-IPv6(RH3 to | -- | -- | 966 | headers | | 6LN) | | | 967 | | | {IP,RPI,payload} | | | 968 | Removed | -- | -- | -- | IPv6-in-IPv6(RH3) | 969 | headers | | | | {IP,RPI,payload} | 970 | Re-added | -- | -- | -- | -- | 971 | headers | | | | | 972 | Modified | -- | -- | -- | -- | 973 | headers | | | | | 974 | Untouched | -- | -- | -- | -- | 975 | headers | | | | | 976 +-----------+------+---------------------+-----+--------------------+ 978 Non Storing: Summary of the use of headers for RPL-aware-leaf to RPL- 979 aware-leaf 981 6.10. Example of Flow from RPL-aware-leaf to not-RPL-aware-leaf 983 In this case the flow comprises: 985 6LN --> 6LR --> root (6LBR) --> 6LR --> not-RPL-aware 6LN 987 The 6LN insert the RPI in a IPv6-in-IPv6 header, which is addressed 988 to 6LBR. The 6LBR remove this RPI header and insert a RH3 header 989 with an optional RPI. These headers are removed by 6LR before send 990 the packet to the IPv6 node. 992 +------------+-------------------+-------------+-------------+------+ 993 | Header | 6LN | 6LBR | 6LR | IPv6 | 994 +------------+-------------------+-------------+-------------+------+ 995 | Inserted | IPv6-in-IPv6(RPI) | IPIP(RH3, | -- | -- | 996 | headers | | opt RPI) | | | 997 | Removed | -- | IPIP(RPI) | IPIP(RH3, | -- | 998 | headers | | | opt RPI) | | 999 | Re-added | -- | -- | -- | -- | 1000 | headers | | | | | 1001 | Modified | -- | -- | -- | -- | 1002 | headers | | | | | 1003 | Untouched | -- | -- | -- | -- | 1004 | headers | | | | | 1005 +------------+-------------------+-------------+-------------+------+ 1007 Non Storing: Summary of the use of headers from RPL-aware-leaf to 1008 not-RPL-aware-leaf 1010 6.11. Example of Flow from not-RPL-aware-leaf to RPL-aware-leaf 1012 In this case the flow comprises: 1014 not-RPL-aware 6LN --> 6LR --> root (6LBR) --> 6LR --> 6LN 1016 RPI is added in 6LR until the root and then removed, then RH3 is 1017 added and removed at destination. 1019 +-------------------+------+------------+-----------+------------+ 1020 | Header | IPv6 | 6LR | 6LBR | 6LN | 1021 +-------------------+------+------------+-----------+------------+ 1022 | Inserted headers | -- | IPIP(RPI) | IPIP(RH3) | -- | 1023 | Removed headers | -- | IPIP(RPI) | -- | IPIP(RH3) | 1024 | Re-added headers | -- | -- | -- | -- | 1025 | Modified headers | -- | -- | -- | -- | 1026 | Untouched headers | -- | -- | -- | -- | 1027 +-------------------+------+------------+-----------+------------+ 1029 Non Storing: Summary of the use of headers from not-RPL-aware-leaf to 1030 RPL-aware-leaf 1032 6.12. Example of Flow from not-RPL-aware-leaf to not-RPL-aware-leaf 1034 In this case the flow comprises: 1036 not-RPL-aware 6LN --> 6LR --> root (6LBR) --> 6LR --> not-RPL-aware 1037 6LN 1039 RPI is added in 6LR until the root and then might be removed, then 1040 RH3 is added. These headers are removed at 6LR before go to 1041 destination. 1043 +--------------+------+-----------+-----------+--------------+------+ 1044 | Header | IPv6 | 6LR | 6LBR | 6LR | IPv6 | 1045 +--------------+------+-----------+-----------+--------------+------+ 1046 | Inserted | -- | IPIP(RPI) | IPIP(RH3) | -- | -- | 1047 | headers | | | | | | 1048 | Removed | -- | -- | IPIP(RPI) | IPIP(RH3, | -- | 1049 | headers | | | | opt RPI) | | 1050 | Re-added | -- | -- | -- | -- | -- | 1051 | headers | | | | | | 1052 | Modified | -- | -- | -- | -- | -- | 1053 | headers | | | | | | 1054 | Untouched | -- | -- | -- | -- | -- | 1055 | headers | | | | | | 1056 +--------------+------+-----------+-----------+--------------+------+ 1058 Non Storing: Summary of the use of headers from not-RPL-aware-leaf to 1059 not-RPL-aware-leaf 1061 7. Future RPL work 1063 There are cases from above that are not clear how to send the 1064 information. It requires furhter analysis on how to proceed to send 1065 the information from source to destination. 1067 From the above cases, we have in storing mode: 1069 - Flow from RPL-aware-leaf to non-RPL-aware-leaf: Somehow, the sender 1070 has to know that the receiver is not RPL aware, and needs to know 1071 6LR, and not even the root knows where the 6LR is located. 1073 - Flow from not-RPL-aware-leaf to not-RPL-aware-leaf: The problem to 1074 solve is how to indicate where to send the packet when get into LLN. 1076 8. IANA Considerations 1078 There are no IANA considerations related to this document. 1080 9. Security Considerations 1082 TODO. 1084 10. Acknowledgments 1086 This work is partially funded by the FP7 Marie Curie Initial Training 1087 Network (ITN) METRICS project (grant agreement No. 607728). 1089 The authors would like to acknowledge the review, feedback, and 1090 comments of Thomas Watteyne, Xavier Vilajosana and Robert Cragie. 1092 To be completed with additional Acknowledgments. 1094 11. References 1096 11.1. Normative References 1098 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1099 Requirement Levels", BCP 14, RFC 2119, 1100 DOI 10.17487/RFC2119, March 1997, 1101 . 1103 [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., 1104 Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, 1105 JP., and R. Alexander, "RPL: IPv6 Routing Protocol for 1106 Low-Power and Lossy Networks", RFC 6550, 1107 DOI 10.17487/RFC6550, March 2012, 1108 . 1110 [RFC6553] Hui, J. and JP. Vasseur, "The Routing Protocol for Low- 1111 Power and Lossy Networks (RPL) Option for Carrying RPL 1112 Information in Data-Plane Datagrams", RFC 6553, 1113 DOI 10.17487/RFC6553, March 2012, 1114 . 1116 [RFC6554] Hui, J., Vasseur, JP., Culler, D., and V. Manral, "An IPv6 1117 Routing Header for Source Routes with the Routing Protocol 1118 for Low-Power and Lossy Networks (RPL)", RFC 6554, 1119 DOI 10.17487/RFC6554, March 2012, 1120 . 1122 11.2. Informative References 1124 [I-D.ietf-6tisch-architecture] 1125 Thubert, P., "An Architecture for IPv6 over the TSCH mode 1126 of IEEE 802.15.4", draft-ietf-6tisch-architecture-08 (work 1127 in progress), May 2015. 1129 [I-D.thubert-6lo-routing-dispatch] 1130 Thubert, P., Bormann, C., Toutain, L., and R. Cragie, "A 1131 Routing Header Dispatch for 6LoWPAN", draft-thubert-6lo- 1132 routing-dispatch-06 (work in progress), August 2015. 1134 [RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and 1135 Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January 1136 2014, . 1138 Authors' Addresses 1140 Maria Ines Robles 1141 Ericsson 1142 Hirsalantie 11 1143 Jorvas 02420 1144 Finland 1146 Email: maria.ines.robles@ericsson.com 1148 Michael C. Richardson 1149 Sandelman Software Works 1150 470 Dawson Avenue 1151 Ottawa, ON K1Z 5V7 1152 CA 1154 Email: mcr+ietf@sandelman.ca 1155 URI: http://www.sandelman.ca/ 1157 Pascal Thubert 1158 Cisco Systems, Inc 1159 Village d'Entreprises Green Side 400, Avenue de Roumanille 1160 Batiment T3, Biot - Sophia Antipolis 06410 1161 France 1163 Email: pthubert@cisco.com