Reverse Routing Header
draft-thubert-6man-reverse-routing-header-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2010-12-10 | ||
| 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-thubert-6man-reverse-routing-header-01.txt
https://www.ietf.org/archive/id/draft-thubert-6man-reverse-routing-header-01.txt
Abstract
For new classes of devices such as highly constrained nodes, forward and return Record Route capabilities are required to enable basic forwarding operations. This memo defines a such a technique for IPv6.
Authors
Pascal Thubert (pthubert@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)