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

Thanks, Ravi.

A tip for naming drafts like this in the future: It's easier for people to locate ICNRG-related drafts if those include 'icnrg' in their name, e.g.:

draft-ravi-icnrg-ccn-notification-01

--
Best regards,
Dirk

> Am 22.03.2016 um 01:32 schrieb Ravi Ravindran <ravi.ravindran@huawei.com>:
> 
> Here is the updated CCN Notification draft for discussion in Buenos Aires. Section 2&3 discussing the requirements and current approaches are the key changes.
> 
> Regards,
> Ravi
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
> Sent: Monday, March 21, 2016 4:21 PM
> To: Syed Obaid Amin; Ignacio Solis; marc.mosko@parc.com; Ravi Ravindran; Asit Chakraborti; 
> 
> Subject: New Version Notification for draft-ravi-ccn-notification-01.txt
> 
> 
> A new version of I-D, draft-ravi-ccn-notification-01.txt
> has been successfully submitted by Ravishankar Ravindran and posted to the
> IETF repository.
> 
> Name:        draft-ravi-ccn-notification
> Revision:    01
> Title:        Support for Notifications in CCN
> Document date:    2016-03-21
> Group:        Individual Submission
> Pages:        12
> URL:            https://www.ietf.org/internet-drafts/draft-ravi-ccn-notification-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-ravi-ccn-notification/
> Htmlized:       https://tools.ietf.org/html/draft-ravi-ccn-notification-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ravi-ccn-notification-01
> 
> 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 forwarding 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.
> 
> 
> 
> 
> 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
> 
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg