Use of the IPv6 Flow Label within an LLN
draft-thubert-roll-flow-label-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Pascal Thubert | ||
Last updated | 2013-05-10 (Latest revision 2012-11-06) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document present how the Flow Label can be used inside a LLN as a replacement to the RPL option and provides rules for the root to set and reset the Flow Label when forwarding between the inside of RPL domain and the larger Internet, in both direction. This new operation aims at saving an IPv6 in IPv6 encapsulation within the RPL domain that is required with the RPL option for all packets that reach outside of the RPL domain.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)