RPL Option for Carrying RPL Information in Data-Plane Datagrams
draft-hui-6man-rpl-option-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jonathan Hui , JP Vasseur | ||
| Last updated | 2010-09-22 (Latest revision 2010-06-09) | ||
| Replaced by | draft-ietf-6man-rpl-option | ||
| 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-6man-rpl-option | |
| 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
The RPL protocol requires data-plane datagrams to carry RPL routing information that is processed by RPL routers when forwarding those datagrams. This document describes the RPL option for use within a RPL domain.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)