Forwarding-Label support in CCN Protocol
draft-ravi-icnrg-ccn-forwarding-label-00

Document Type Expired Internet-Draft (individual)
Last updated 2017-05-20 (latest revision 2016-11-16)
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 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-ravi-icnrg-ccn-forwarding-label-00.txt

Abstract

The objective of this proposal is to enable ID and Locator namespace split in the CCN protocol that has several applications such as towards Interest routing optimization, mobility, handling indirections in manifests, and routing scalability. We enable this through the notion of forwarding-label (FL) object, which is an optional hop-by-hop payload in the Interest message with a locator name which identifies a network domain, router, or a host. Depending on the application and trust context, an FL object can be subjected to policy based actions by the forwarders such as invoking security verification or enabling other service-centric actions such as FL object replacement. FL object can be inserted by the applications or by the network. To enable dynamic name resolution FL objects can also be modified in the network by designated points such as the edge routers.

Authors

Ravi Ravindran (ravi.ravindran@huawei.com)
Asit Chakraborti (asit.chakraborti@huawei.com)
Aytac Azgin (aytac.azgin@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)