Support for Notifications in CCN
draft-ravi-icnrg-ccn-notification-01

Document Type Active Internet-Draft (individual)
Last updated 2017-07-16
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                   S. Amin
Expires: January 17, 2018                            Huawei Technologies
                                                                 J. Chen
                                              Winlab, Rutgers University
                                                           July 16, 2017

                    Support for Notifications in CCN
                  draft-ravi-icnrg-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 routing implications.  The draft first discusses the design
   choices associated with using current Interest/Data abstraction for
   achieving push and challenges associated with them.  We follow this
   by proposing a new fixed header primitive called Notification and a
   CCN message encoding using Content Object primitive to transport
   Notifications.  This discussion 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.

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 17, 2018.

Ravindran, et al.       Expires January 17, 2018                [Page 1]
Internet-Draft            Interest Notification                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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notification Requirements in CCN  . . . . . . . . . . . . . .   3
   3.  Using Interest/Data Abstraction for PUSH  . . . . . . . . . .   4
   4.  Proposed Notification Primitive in CCN  . . . . . . . . . . .   9
   5.  Notification Message Encoding . . . . . . . . . . . . . . . .  10
   6.  Notification Processing . . . . . . . . . . . . . . . . . . .  12
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   8.  Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     8.1.  Flow and Congestion Control . . . . . . . . . . . . . . .  13
       8.1.1.  Issues with Basic Notifications . . . . . . . . . . .  13
       8.1.2.  Flow and Congestion Control Mechanims . . . . . . . .  14
         8.1.2.1.  End-to-End Approaches . . . . . . . . . . . . . .  14
         8.1.2.2.  Hybrid Approaches . . . . . . . . . . . . . . . .  15
       8.1.3.  Receiver Reliability  . . . . . . . . . . . . . . . .  17
     8.2.  Routing Notifications . . . . . . . . . . . . . . . . . .  18
     8.3.  Notification reliability  . . . . . . . . . . . . . . . .  18
     8.4.  Use Case Scenarios  . . . . . . . . . . . . . . . . . . .  19
       8.4.1.  Realizing PUB/SUB System  . . . . . . . . . . . . . .  19
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  20
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   Notification is a PUSH primitive used in the Internet today by many
   IoT and social applications.  The nature of notifications varies with
Show full document text