Support for Notifications in CCN
draft-ravi-ccn-notification-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ravi Ravindran , Asit Chakraborti , Syed Obaid Amin , Marc Mosko , Ignacio Solis | ||
Last updated | 2016-09-22 (Latest revision 2016-03-21) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Ravi Ravindran
Asit Chakraborti
Syed Obaid Amin
Marc Mosko
Ignacio Solis
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)