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

Document Type Expired Internet-Draft (individual)
Last updated 2018-09-06 (latest revision 2018-03-05)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf 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-ravi-icnrg-ccn-forwarding-label-02.txt

Abstract

The objective of this proposal is to enable application identifier (AI) and network identifier (NI) split in the CCN protocol that has several applications such as towards Interest routing optimization, mobility, conversational session support, handling indirections in manifests, and routing scalability. We enable this through the notion of forwarding label object (FLO), which is an optional hop-by- hop payload in the Interest message with a topological name which identifies a network domain, router or a host. FLO can be inserted by the end user applications or by the network. FLO is processed by the network resulting in either terminating it or swapping it with a new FLO based on the network service context. Furthermore, depending on the application and trust context, a FLO can be subjected to policy based actions by the forwarders such as invoking security verification or enabling other FLO management actions.

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.)