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

From: Ravi Ravindran <[email-masked]>
Date: Fri, 8 Jul 2016 14:49:37 +0000

Hi All,

This draft has been renamed and iterates on our earlier draft https://tools.ietf.org/html/draft-ravi-ccn-notification-01

We provide discussions on handling flow and congestion control issue in this version in light of notification traffic.

Regards,
Ravi

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Thursday, July 07, 2016 11:23 PM
To: Syed Obaid Amin; Ignacio Solis; Jiachen Chen; [email-masked]; Ravi Ravindran; Asit Chakraborti; Ravi Ravindran; Marc Mosko
Subject: New Version Notification for draft-ravi-icnrg-ccn-notification-00.txt

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

Name:		draft-ravi-icnrg-ccn-notification
Revision:	00
Title:		Support for Notifications in CCN
Document date:	2016-07-07
Group:		Individual Submission
Pages:		18
URL:            https://www.ietf.org/internet-drafts/draft-ravi-icnrg-ccn-notification-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ravi-icnrg-ccn-notification/
Htmlized:       https://tools.ietf.org/html/draft-ravi-icnrg-ccn-notification-00

Abstract:
   This draft proposes a new packet primitive called Notification for
   CCN.  Notification is a PUSH primitive and can be unicast or
   multicast to multiple listening points.  Notifications do not expect
   a Content Object response hence only requires the use of FIB state in
   the CCN forwarder.  Emulating Notification as a PULL has performance
   and routing implications.  The draft proposes a new fixed header
   primitive called Notification and a CCN message encoding using
   Content Object primitive to transport Notifications.  These
   discussions are presented in the context of CCNx1.0 [1] proposal.
   The draft also provides discussions on various aspects related to
   notification such as flow and congestion control, routing and
   reliability considerations, and use case scenarios.

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