Subject: [icnrg] FW: New Version Notification for draft-ravi-ccn-forwarding-label-00.txt

From: Ravi Ravindran <[email-masked]>
Date: Mon, 9 Mar 2015 23:51:25 +0000

Hi All,

This draft elaborates on one of the topics raised as part of the CCN/NDN requirements in the last Boston meeting, requiring a need for forwarding-label as an optional field. We will discuss this during our assigned timeslot on Sunday. Comments are welcome in the meantime.

Regards,
Ravi

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Monday, March 09, 2015 4:42 PM
To: Ravi Ravindran; Asit Chakraborti; Ravi Ravindran; Asit Chakraborti
Subject: New Version Notification for draft-ravi-ccn-forwarding-label-00.txt

A new version of I-D, draft-ravi-ccn-forwarding-label-00.txt
has been successfully submitted by Ravishankar Ravindran and posted to the IETF repository.

Name:		draft-ravi-ccn-forwarding-label
Revision:	00
Title:		Forwarding-Label support in CCN Protocol
Document date:	2015-03-09
Group:		Individual Submission
Pages:		10
URL:            http://www.ietf.org/internet-drafts/draft-ravi-ccn-forwarding-label-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ravi-ccn-forwarding-label/
Htmlized:       http://tools.ietf.org/html/draft-ravi-ccn-forwarding-label-00

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.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat