A YANG Data Model for Resource Reservation Protocol (RSVP)
draft-ietf-teas-yang-rsvp-06

Document Type Active Internet-Draft (teas WG)
Last updated 2016-10-30
Stream IETF
Intended RFC status (None)
Formats plain text 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)
TEAS Working Group                                             V. Beeram
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                            T. Saad, Ed.
Expires: May 3, 2017                                           R. Gandhi
                                                       Cisco Systems Inc
                                                                  X. Liu
                                                                Ericsson
                                                                 H. Shah
                                                                   Ciena
                                                                 X. Chen
                                                     Huawei Technologies
                                                                R. Jones
                                                                 Brocade
                                                                  B. Wen
                                                                 Comcast
                                                        October 30, 2016

       A YANG Data Model for Resource Reservation Protocol (RSVP)
                      draft-ietf-teas-yang-rsvp-06

Abstract

   This document defines a YANG data model for the configuration and
   management of RSVP Protocol.  The model defines generic RSVP protocol
   building blocks that can be augmented and used by other RSVP
   extension models such as RVSP extensions to Traffic-Engineering
   (RSVP-TE).  The model covers the RSVP protocol configuration,
   operational state, remote procedural calls, and event notifications
   data.

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 May 3, 2017.

Beeram, et al.             Expires May 3, 2017                  [Page 1]
Internet-Draft            RSVP YANG Data Model              October 2016

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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Prefixes in Data Node Names . . . . . . . . . . . . . . .   4
     1.4.  Open Issues and Next Steps  . . . . . . . . . . . . . . .   5
       1.4.1.  Module Hierarchy  . . . . . . . . . . . . . . . . . .   5
       1.4.2.  Model Data Organization . . . . . . . . . . . . . . .   5
       1.4.3.  State Data  . . . . . . . . . . . . . . . . . . . . .   5
   2.  Design Considerations . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Base Model(s) . . . . . . . . . . . . . . . . . . . . . .   6
     2.2.  Extended Model(s) . . . . . . . . . . . . . . . . . . . .   7
     2.3.  Configuration Inheritance . . . . . . . . . . . . . . . .   7
     2.4.  Routing Instance Support  . . . . . . . . . . . . . . . .   8
   3.  Model Organization  . . . . . . . . . . . . . . . . . . . . .   8
     3.1.  RSVP Base YANG Model  . . . . . . . . . . . . . . . . . .   8
       3.1.1.  Configuration and State Data  . . . . . . . . . . . .  10
       3.1.2.  RPC and Notification Data . . . . . . . . . . . . . .  15
       3.1.3.  YANG Module . . . . . . . . . . . . . . . . . . . . .  15
     3.2.  RSVP Extended YANG Model  . . . . . . . . . . . . . . . .  32
       3.2.1.  Configuration and State Data  . . . . . . . . . . . .  32
       3.2.2.  YANG Module . . . . . . . . . . . . . . . . . . . . .  35
     3.3.  RSVP-TE Generic YANG Model  . . . . . . . . . . . . . . .  46
Show full document text