When to use RFC 6553, 6554 and IPv6-in-IPv6
draft-robles-roll-useofrplinfo-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ines Robles , Michael Richardson , Pascal Thubert | ||
| Last updated | 2015-10-19 | ||
| Replaced by | draft-ietf-roll-useofrplinfo | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-roll-useofrplinfo | |
| 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 states different cases where RFC 6553, RFC 6554 and IPv6-in-IPv6 encapsulation is required to set the bases to help defining the compression of RPL routing information in LLN environments.
Authors
Ines Robles
Michael Richardson
Pascal Thubert
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)