Using RPL Headers Without IP-in-IP
draft-hui-6man-rpl-headers-00

Document Type Expired Internet-Draft (individual)
Authors Jonathan Hui  , Pascal Thubert  , Vasseur Jp 
Last updated 2010-07-28
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hui-6man-rpl-headers-00.txt

Abstract

Routing for Low Power and Lossy Networks (RPL) is a routing protocol designed for Low power and Lossy Networks (LLNs). RPL includes routing information in IPv6 data plane datagrams to help maintain the routing topology. When forwarding a datagram into a RPL domain, a RPL router may need to expand the datagram to include routing information in IPv6 Extension headers. A generic solution has been defined that uses IP-in-IP tunneling to include RPL routing information. This document describes an alternative to inserting and removing RPL information in datagrams without the use of IP-in-IP tunneling.

Authors

Jonathan Hui (jhui@archrock.com)
Pascal Thubert (pthubert@cisco.com)
Vasseur Jp (jpv@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)