Forwarding-Label support in CCN Protocol
draft-ravi-ccn-forwarding-label-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Ravi Ravindran , Asit Chakraborti | ||
| Last updated | 2015-09-10 (Latest revision 2015-03-09) | ||
| RFC stream | (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 motivates the need for a forwarding-label which is another name that can be used in forwarding, in addition to the mandatory name in a CCNx Interest message. Forwarding-label once inserted by a edge router can be modified en-route towards the producer. Forwarding-label can be used for several purposes such as to support routing scalability, producer mobility, multi-protocol support, or for fast forwarding. We describe its encoding format, and rules followed by a forwarder while processing it. We also illustrate its use by applying it towards producer mobility. This draft scopes the use of forwarding-label within a closed trusted domain, while the use of it by applications is not ruled out.
Authors
Ravi Ravindran
Asit Chakraborti
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)