When to use RFC 6553, 6554 and IPv6-in-IPv6
draft-robles-roll-useofrplinfo-02
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2015-10-19 | ||
| Replaced by | draft-ietf-roll-useofrplinfo | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-roll-useofrplinfo | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-robles-roll-useofrplinfo-02.txt
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
(maria.ines.robles@ericsson.com)
Michael Richardson
(mcr+ietf@sandelman.ca)
Pascal Thubert
(pthubert@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)