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

Document Type Active Internet-Draft (individual)
Last updated 2017-07-17
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ICN Research Group                                          R. Ravindran
Internet-Draft                                            A. Chakraborti
Intended status: Informational                                  A. Azgin
Expires: January 18, 2018                            Huawei Technologies
                                                           July 17, 2017

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

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, seamless mobility and
   providing mobility as a service, conversational session support,
   handling indirections in manifests, and routing scalability.  We
   enable this through the notion of a 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, a router or a
   host.  FLO can be inserted within the Interest message by the
   applications or by the network.  FLO can be interpreted by the
   network in multiple ways, for instance, to terminate the message or
   to swap it with a new FLO based on the service context.  Furthermore,
   depending on the application and trust context, FLO can be subjected
   to policy based actions by the forwarders, such as invoking security
   verification or enabling other service-centric FLO management
   actions.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 18, 2018.

Ravindran, et al.       Expires January 18, 2018                [Page 1]
Internet-Draft       Forwarding-label support in CCN           July 2017

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  ID-Locator Namespace Split in CCN . . . . . . . . . . . . . .   2
   2.  Forwarding-Label Object Proposal  . . . . . . . . . . . . . .   5
     2.1.  FLO Naming  . . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  FLO Insertion . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  FLO Swapping  . . . . . . . . . . . . . . . . . . . . . .   6
     2.4.  FLO Termination . . . . . . . . . . . . . . . . . . . . .   6
   3.  FLO Message Format  . . . . . . . . . . . . . . . . . . . . .   6
   4.  FLO Processing Rules  . . . . . . . . . . . . . . . . . . . .   7
   5.  Implications on PIT Processing  . . . . . . . . . . . . . . .   8
   6.  Implications on Caching . . . . . . . . . . . . . . . . . . .   8
   7.  Multiple Domain Scenario  . . . . . . . . . . . . . . . . . .   9
   8.  FLO Security  . . . . . . . . . . . . . . . . . . . . . . . .   9
   9.  Use Case Scenarios  . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Handling Producer Mobility  . . . . . . . . . . . . . . .  10
     9.2.  Manifests . . . . . . . . . . . . . . . . . . . . . . . .  11
     9.3.  Support for Conversational Sessions . . . . . . . . . . .  13
     9.4.  Interest Routing Optimization . . . . . . . . . . . . . .  13
     9.5.  Routing Scalability . . . . . . . . . . . . . . . . . . .  13
   10. Informative References  . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  ID-Locator Namespace Split in CCN

   In the context of ICN/CCN, we define Identifier and Locator as
   follows:

   o  Identifier (ID) is a persistent secure or non-secure flat-ID or a
      hierarchical name assigned to a content, device or service.  If
Show full document text