Restconf and HTTP Transport for Event Notifications
draft-ietf-netconf-restconf-notif-01

The information below is for an old version of the document
Document Type Active Internet-Draft (netconf WG)
Last updated 2016-09-29
Replaces draft-voit-netconf-restconf-notif
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
NETCONF                                                          E. Voit
Internet-Draft                                                  A. Clemm
Intended status: Standards Track                      A. Gonzalez Prieto
Expires: April 2, 2017                                       A. Tripathy
                                                       E. Nilsen-Nygaard
                                                           Cisco Systems
                                                              A. Bierman
                                                               YumaWorks
                                                      September 29, 2016

          Restconf and HTTP Transport for Event Notifications
                  draft-ietf-netconf-restconf-notif-01

Abstract

   This document defines Restconf, HTTP2, and HTTP1.1 bindings for the
   transport Subscription requests and corresponding push updates.
   Being subscribed may be both Event Notifications and YANG Datastores.

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 April 2, 2017.

Copyright Notice

   Copyright (c) 2016 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

Voit, et al.              Expires April 2, 2017                 [Page 1]
Internet-Draft               Restconf-Notif               September 2016

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Solution  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Mechanisms for Subscription Establishment and Maintenance   4
     3.2.  Dynamic YANG Subscription with RESTCONF control . . . . .   5
     3.3.  Subscription Multiplexing . . . . . . . . . . . . . . . .   8
     3.4.  Encoded Subscription and Event Notification Examples  . .   9
     3.5.  Stream Discovery  . . . . . . . . . . . . . . . . . . . .  14
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Appendix A.  Proxy YANG Subscription when the Subscriber and
                Receiver are different . . . . . . . . . . . . . . .  17
   Appendix B.  End-to-End Deployment Guidance . . . . . . . . . . .  17
     B.1.  Call Home . . . . . . . . . . . . . . . . . . . . . . . .  17
     B.2.  TLS Heartbeat . . . . . . . . . . . . . . . . . . . . . .  18
   Appendix C.  Issues being worked and resolved . . . . . . . . . .  18
     C.1.  Unresolved Issues . . . . . . . . . . . . . . . . . . . .  18
     C.2.  Agreement in principal  . . . . . . . . . . . . . . . . .  18
     C.3.  Resolved Issues . . . . . . . . . . . . . . . . . . . . .  18
   Appendix D.  Changes between revisions  . . . . . . . . . . . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction

   Mechanisms to support Event subscription and push are defined in
   [rfc5277bis].  Enhancements to [rfc5277bis] which enable YANG
   Datastore subscription and push are defined in [yang-push].  This
   document provides a transport specification for these protocols over
   Restconf and HTTP.  Driving these requirements is [RFC7923].

   The streaming of Subscription Event Notifications has synergies with
   HTTP2 streams.  Benefits which can be realized when transporting
   events directly HTTP2 [RFC7540] include:

   o  Elimination of head-of-line blocking
Show full document text