A YANG Data Model for RSVP-TE
draft-ietf-teas-yang-rsvp-te-03
|
| Document |
Type |
|
Active Internet-Draft (teas WG)
|
|
Last updated |
|
2018-02-19
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Yang Validation |
|
☯
0 errors, 0 warnings.
draft-ietf-teas-yang-rsvp-te-03.txt:
xym 0.4:
Extracting 'ietf-rsvp-te@2018-02-19.yang'
Removed 2 empty lines
Extracting 'ietf-rsvp-te-mpls@2018-02-19.yang'
Removed 0 empty lines
ietf-rsvp-te@2018-02-19.yang:
pyang 1.7.4: pyang --verbose --ietf -p {libs} {model}:
No validation errors
yanglint 0.14.78: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
ietf-rsvp-te-mpls@2018-02-19.yang:
pyang 1.7.4: pyang --verbose --ietf -p {libs} {model}:
No validation errors
yanglint 0.14.78: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
|
|
Additional URLs |
|
|
| 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: August 23, 2018 R. Gandhi
Cisco Systems, Inc.
X. Liu
Jabil
I. Bryskin
Huawei Technologies
H. Shah
Ciena
February 19, 2018
A YANG Data Model for RSVP-TE
draft-ietf-teas-yang-rsvp-te-03
Abstract
This document defines a YANG data model for the configuration and
management of RSVP (Resource Reservation Protocol) to establish
Traffic-Engineered (TE) Label-Switched Paths (LSPs) for MPLS (Multi-
Protocol Label Switching) and other technologies.
The model defines a generic RSVP-TE module for signaling LSPs that is
technology agnostic. The generic RSVP-TE module is to be augmented
by technology specific RSVP-TE modules that define technology
specific data. This document defines the augmentation for RSVP-TE
MPLS LSPs model.
This model covers data for the configuration, operational state,
remote procedural calls, and event notifications.
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."
Beeram, et al. Expires August 23, 2018 [Page 1]
Internet-Draft RSVP YANG Data Model February 2018
This Internet-Draft will expire on August 23, 2018.
Copyright Notice
Copyright (c) 2018 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
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4
2. Design Considerations . . . . . . . . . . . . . . . . . . . . 5
2.1. Module Hierarchy . . . . . . . . . . . . . . . . . . . . 5
2.2. RSVP-TE Generic Model . . . . . . . . . . . . . . . . . . 6
2.2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . 6
2.2.2. YANG Module . . . . . . . . . . . . . . . . . . . . . 14
2.3. RSVP-TE MPLS Model . . . . . . . . . . . . . . . . . . . 26
2.3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . 26
2.3.2. YANG Module . . . . . . . . . . . . . . . . . . . . . 28
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41
4. Security Considerations . . . . . . . . . . . . . . . . . . . 41
5. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 42
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 42
7. Normative References . . . . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43
1. Introduction
YANG [RFC6020] is a data definition language that was introduced to
define the contents of a conceptual data store that allows networked
devices to be managed using NETCONF [RFC6241]. YANG is proving
relevant beyond its initial confines, as bindings to other interfaces
(e.g. ReST) and encoding other than XML (e.g. JSON) are being
defined. Furthermore, YANG data models can be used as the basis of
Show full document text