An HTTPS-based Transport for Configured Subscriptions
draft-ietf-netconf-https-notif-01

Document Type Active Internet-Draft (netconf WG)
Last updated 2019-10-30
Replaces draft-mahesh-netconf-https-notif
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Yang Validation 7 errors, 2 warnings.
Additional URLs
- Yang catalog entry for ietf-https-notif@2019-10-30.yang
- Yang impact analysis for draft-ietf-netconf-https-notif
- Mailing list discussion
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                                                  M. Jethanandani
Internet-Draft                                                    VMware
Intended status: Standards Track                               K. Watsen
Expires: May 2, 2020                                     Watsen Networks
                                                        October 30, 2019

         An HTTPS-based Transport for Configured Subscriptions
                   draft-ietf-netconf-https-notif-01

Abstract

   This document defines a YANG data module for configuring HTTPS based
   configured subscription, as defined in Subscribed Notifications
   (RFC8639).  The use of HTTPS maximizes transport-level
   interoperability, while allowing for encoding selection from text,
   e.g.  XML or JSON, to binary.

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 https://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 May 2, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Jethanandani & Watsen      Expires May 2, 2020                  [Page 1]
Internet-Draft        HTTP Configured Subscription          October 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Note to RFC Editor  . . . . . . . . . . . . . . . . . . .   3
     1.2.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
       1.3.1.  Subscribed Notifications  . . . . . . . . . . . . . .   3
     1.4.  Receiver and Publisher Interaction  . . . . . . . . . . .   3
       1.4.1.  Pipelining of messages  . . . . . . . . . . . . . . .   4
   2.  YANG module . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.2.  YANG module . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  URI Registration  . . . . . . . . . . . . . . . . . . . .  11
     4.2.  YANG Module Name Registration . . . . . . . . . . . . . .  12
   5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     5.1.  HTTPS Configured Subscription . . . . . . . . . . . . . .  12
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   8.  Normative references  . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   Subscribed Notifications [RFC8639] defines a YANG data module for
   configuring subscribed notifications.  It even defines a
   subscriptions container that contains a list of receivers.  But it
   defers the configuration and management of those receivers to other
   documents.  This document defines a YANG [RFC7950] data module for
   configuring and managing HTTPS based receivers for the notifications.
   Such a configured receiver can be a third party collector, collecting
   events on behalf of receivers that want to correlate events from
   different publishers.  Configured subscriptions enable a server,
   acting as a publisher of notifications, to proactively push
   notifications to external receivers without the receivers needing to
   first connect to the server, as is the case with dynamic
   subscriptions.

   This document describes how to enable the transmission of YANG
   modeled notifications, in the configured encoding (i.e., XML, JSON)
   over HTTPS.  It comes in the form of a HTTPS POST.  The use of HTTPS
   maximizes transport-level interoperability, while the encoding
   selection pivots between implementation simplicity (XML, JSON) and
Show full document text