An IPv6 Routing Header for Source Routes with the Routing Protocol for Low-Power and Lossy Networks (RPL)

Abstract

In Low-Power and Lossy Networks (LLNs), memory constraints

Multipath Extension for the Optimized Link State Routing Protocol Version 2 (OLSRv2)

“…In the current specification, only strict source routing is used for IPv6 based on [RFC6554]. In , the use of the loose source routing is also proposed in IPv6.…”

Reactive Discovery of Point-to-Point Routes in Low-Power and Lossy Networks

“…Additionally, this document uses terminology from [RFC6550] and [RFC6554]. Further terminology may be found in [ROLL-TERMS].…”

“…The IPv6 source address in a P2P mode DIO MUST be a link-local address, and the IPv6 destination address MUST be the link-local multicast address all-RPL-nodes [RFC6550]. A P2P mode DIO MUST be transmitted on all interfaces the router has in this RPL routing domain [RFC6554]. The Origin sets this field based on its expectation regarding the time required for the route discovery to complete, which includes the time required for the DIOs to reach the Target(s) and the P2P-DROs to travel back to the Origin.…”

“…The IPv6 source address in a P2P-DRO message MUST be a link-local address, and the IPv6 destination address MUST be the link-local multicast address all-RPL-nodes [RFC6550]. A P2P-DRO message MUST be transmitted on all interfaces the router has in this RPL routing domain [RFC6554]. o Sequence Number (Seq): This 2-bit field indicates the sequence number for the P2P-DRO.…”

“…Packet Forwarding along a Route Discovered Using P2P-RPL An Origin uses the Source Routing Header (SRH) [RFC6554] to send a packet along a Source Route discovered using P2P-RPL.…”