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

Document Type Active Internet-Draft (netconf WG)
Last updated 2017-08-04
Replaces draft-voit-netconf-restconf-notif
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
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. Tripathy
Intended status: Standards Track                       E. Nilsen-Nygaard
Expires: February 5, 2018                                  Cisco Systems
                                                                A. Clemm
                                                                  Huawei
                                                      A. Gonzalez Prieto
                                                                  VMWare
                                                              A. Bierman
                                                               YumaWorks
                                                          August 4, 2017

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

Abstract

   This document defines Restconf, HTTP2, and HTTP1.1 bindings for the
   transport of Subscription requests and corresponding push updates.
   Being subscribed may be either publisher defined event streams or
   nodes/subtrees of 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 February 5, 2018.

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

Voit, et al.            Expires February 5, 2018                [Page 1]
Internet-Draft               Restconf-Notif                  August 2017

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Solution  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Dynamic YANG Subscription with RESTCONF control . . . . .   3
     3.2.  Subscription Multiplexing . . . . . . . . . . . . . . . .   6
   4.  Encoded Subscription and Notification Message Examples  . . .   7
     4.1.  Restconf Subscription and Events over HTTP1.1 . . . . . .   7
     4.2.  Event Notification over HTTP2 . . . . . . . . . . . . . .  12
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  13
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Appendix A.  End-to-End Deployment Guidance . . . . . . . . . . .  14
     A.1.  Call Home . . . . . . . . . . . . . . . . . . . . . . . .  14
     A.2.  TLS Heartbeat . . . . . . . . . . . . . . . . . . . . . .  15
   Appendix B.  RESTCONF over GRPC . . . . . . . . . . . . . . . . .  15
   Appendix C.  Changes between revisions  . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   Mechanisms to support Event subscription and push are defined in
   [sn].  Enhancements to [sn] 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 notifications encapsulating the resulting
   information push can be done with either HTTP1.1 and HTTP2.  When
   using HTTP2 [RFC7540] benefits which can be realized include:

   o  Elimination of head-of-line blocking

   o  Weighting and proportional dequeuing of Events from different
      subscriptions
Show full document text