UDP-based Transport for Configured Subscriptions
draft-ietf-netconf-udp-notif-00

Document Type Active Internet-Draft (netconf WG)
Authors Guangying Zheng  , Tianran Zhou  , Thomas Graf  , Pierre Francois  , Paolo Lucente 
Last updated 2020-10-02
Replaces draft-unyte-netconf-udp-notif
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Yang Validation 4 errors, 10 warnings.
Additional Resources
- Yang catalog entry for ietf-udp-notif@2020-04-27.yang
- Yang impact analysis for draft-ietf-netconf-udp-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                                                         G. Zheng
Internet-Draft                                                   T. Zhou
Intended status: Standards Track                                  Huawei
Expires: April 6, 2021                                           T. Graf
                                                                Swisscom
                                                             P. Francois
                                                               INSA-Lyon
                                                              P. Lucente
                                                                     NTT
                                                         October 3, 2020

            UDP-based Transport for Configured Subscriptions
                    draft-ietf-netconf-udp-notif-00

Abstract

   This document describes an UDP-based notification mechanism to
   collect data from networking devices.  A shim header is proposed to
   facilitate the streaming of data directly from line cards to a
   collector.  The objective is to rely on a lightweight approach to
   allow for higher frequency and better transit performance compared to
   already established notification mechanisms.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 April 6, 2021.

Zheng, et al.             Expires April 6, 2021                 [Page 1]
Internet-Draft               ietf-udp-notif                 October 2020

Copyright Notice

   Copyright (c) 2020 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Configured Subscription to UDP-Notif  . . . . . . . . . . . .   4
   3.  UDP-Based Transport . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Design Overview . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Format of the UDP-Notif Message Header  . . . . . . . . .   5
     3.3.  Options . . . . . . . . . . . . . . . . . . . . . . . . .   6
       3.3.1.  Fragmentation Option  . . . . . . . . . . . . . . . .   6
     3.4.  Data Encoding . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Congestion Control  . . . . . . . . . . . . . . . . . . . . .   8
   5.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  A YANG Data Model for Management of UDP-Notif . . . . . . . .   8
   7.  YANG Module . . . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     11.2.  Informative References . . . . . . . . . . . . . . . . .  14
     11.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   Sub-Notif [RFC8639] defines a mechanism that lets a collector
   subscribe to the publication of YANG-defined data maintained in a
   YANG [RFC7950] datastore.  The mechanism separates the management and
   control of subscriptions from the transport used to deliver the data.
   Three transport mechanisms, namely NETCONF transport [RFC8640],
   RESTCONF transport [RFC8650], and HTTPS transport
   [I-D.ietf-netconf-https-notif] have been defined so far for such
Show full document text