draft-ietf-teas-yang-te-mpls-02.txt   draft-ietf-teas-yang-te-mpls-03.txt 
TEAS Working Group T. Saad TEAS Working Group T. Saad
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track R. Gandhi Intended status: Standards Track R. Gandhi
Expires: May 5, 2020 Cisco Systems Inc Expires: September 10, 2020 Cisco Systems Inc
X. Liu X. Liu
Volta Networks Volta Networks
V. Beeram V. Beeram
Juniper Networks Juniper Networks
I. Bryskin I. Bryskin
Individual Individual
November 02, 2019 March 09, 2020
A YANG Data Model for MPLS Traffic Engineering Tunnels A YANG Data Model for MPLS Traffic Engineering Tunnels
draft-ietf-teas-yang-te-mpls-02 draft-ietf-teas-yang-te-mpls-03
Abstract Abstract
This document defines a YANG data model for the configuration and This document defines a YANG data model for the configuration and
management of Multiprotocol Label Switching (MPLS) Traffic management of Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) tunnels, Label Switched Paths (LSPs) and interfaces. Engineering (TE) tunnels, Label Switched Paths (LSPs) and interfaces.
The model augments the TE generic YANG model for MPLS packet The model augments the TE generic YANG model for MPLS packet
dataplane technology. dataplane technology.
This model covers data for configuration, operational state, remote This model covers data for configuration, operational state, remote
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 5, 2020. This Internet-Draft will expire on September 10, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 30 skipping to change at page 2, line 30
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3 1.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3
1.3. Acronyms and Abbreviations . . . . . . . . . . . . . . . 3 1.3. Acronyms and Abbreviations . . . . . . . . . . . . . . . 3
2. MPLS TE YANG Model . . . . . . . . . . . . . . . . . . . . . 3 2. MPLS TE YANG Model . . . . . . . . . . . . . . . . . . . . . 3
2.1. Module(s) Relationship . . . . . . . . . . . . . . . . . 4 2.1. Module(s) Relationship . . . . . . . . . . . . . . . . . 4
2.2. Model Tree Diagram . . . . . . . . . . . . . . . . . . . 4 2.2. Model Tree Diagram . . . . . . . . . . . . . . . . . . . 4
2.3. MPLS TE YANG Module . . . . . . . . . . . . . . . . . . . 8 2.3. MPLS TE YANG Module . . . . . . . . . . . . . . . . . . . 8
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
4. Security Considerations . . . . . . . . . . . . . . . . . . . 18 4. Security Considerations . . . . . . . . . . . . . . . . . . . 18
5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19
6. Normative References . . . . . . . . . . . . . . . . . . . . 18 6. Normative References . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
YANG [RFC6020] and [RFC7950] is a data modeling language used to YANG [RFC6020] and [RFC7950] is a data modeling language used to
define the contents of a conceptual data store that allows networked define the contents of a conceptual data store that allows networked
devices to be managed using NETCONF [RFC6241]. YANG has proved devices to be managed using NETCONF [RFC6241]. YANG has proved
relevant beyond its initial confines, as bindings to other interfaces relevant beyond its initial confines, as bindings to other interfaces
(e.g. RESTCONF [RFC8040]) and encoding other than XML (e.g. JSON) (e.g. RESTCONF [RFC8040]) and encoding other than XML (e.g. JSON)
are being defined. Furthermore, YANG data models can be used as the are being defined. Furthermore, YANG data models can be used as the
basis of implementation for other interfaces, such as CLI and basis of implementation for other interfaces, such as CLI and
skipping to change at page 4, line 40 skipping to change at page 4, line 40
YANG modules YANG modules
The MPLS TE YANG module "ietf-te-mpls" augments the "ietf-te" TE The MPLS TE YANG module "ietf-te-mpls" augments the "ietf-te" TE
generic YANG module as shown in Figure 1. generic YANG module as shown in Figure 1.
2.2. Model Tree Diagram 2.2. Model Tree Diagram
Figure 2 shows the tree diagram of the MPLS TE YANG model that is Figure 2 shows the tree diagram of the MPLS TE YANG model that is
defined in ietf-te-mpls.yang. defined in ietf-te-mpls.yang.
module: ietf-te-mpls module: ietf-te-mpls
augment /te:te/te-dev:performance-thresholds: augment /te:te/te-dev:performance-thresholds:
+--rw throttle +--rw throttle
+--rw one-way-delay-offset? uint32 +--rw one-way-delay-offset? uint32
+--rw measure-interval? uint32 +--rw measure-interval? uint32
+--rw advertisement-interval? uint32 +--rw advertisement-interval? uint32
+--rw suppression-interval? uint32 +--rw suppression-interval? uint32
+--rw threshold-out +--rw threshold-out
| +--rw one-way-delay? uint32 | +--rw one-way-delay? uint32
| +--rw one-way-residual-bandwidth? | +--rw one-way-residual-bandwidth?
| | rt-types:bandwidth-ieee-float32 | | rt-types:bandwidth-ieee-float32
| +--rw one-way-available-bandwidth? | +--rw one-way-available-bandwidth?
| | rt-types:bandwidth-ieee-float32 | | rt-types:bandwidth-ieee-float32
| +--rw one-way-utilized-bandwidth? | +--rw one-way-utilized-bandwidth?
| | rt-types:bandwidth-ieee-float32 | | rt-types:bandwidth-ieee-float32
| +--rw two-way-delay? uint32 | +--rw two-way-delay? uint32
| +--rw one-way-min-delay? uint32 | +--rw one-way-min-delay? uint32
| +--rw one-way-max-delay? uint32 | +--rw one-way-max-delay? uint32
| +--rw one-way-delay-variation? uint32 | +--rw one-way-delay-variation? uint32
| +--rw one-way-packet-loss? decimal64 | +--rw one-way-packet-loss? decimal64
| +--rw two-way-min-delay? uint32 | +--rw two-way-min-delay? uint32
| +--rw two-way-max-delay? uint32 | +--rw two-way-max-delay? uint32
| +--rw two-way-delay-variation? uint32 | +--rw two-way-delay-variation? uint32
| +--rw two-way-packet-loss? decimal64 | +--rw two-way-packet-loss? decimal64
+--rw threshold-in +--rw threshold-in
| +--rw one-way-delay? uint32 | +--rw one-way-delay? uint32
| +--rw one-way-residual-bandwidth? | +--rw one-way-residual-bandwidth?
| | rt-types:bandwidth-ieee-float32 | | rt-types:bandwidth-ieee-float32
| +--rw one-way-available-bandwidth? | +--rw one-way-available-bandwidth?
| | rt-types:bandwidth-ieee-float32 | | rt-types:bandwidth-ieee-float32
| +--rw one-way-utilized-bandwidth? | +--rw one-way-utilized-bandwidth?
| | rt-types:bandwidth-ieee-float32 | | rt-types:bandwidth-ieee-float32
| +--rw two-way-delay? uint32 | +--rw two-way-delay? uint32
| +--rw one-way-min-delay? uint32 | +--rw one-way-min-delay? uint32
| +--rw one-way-max-delay? uint32 | +--rw one-way-max-delay? uint32
| +--rw one-way-delay-variation? uint32 | +--rw one-way-delay-variation? uint32
| +--rw one-way-packet-loss? decimal64 | +--rw one-way-packet-loss? decimal64
| +--rw two-way-min-delay? uint32 | +--rw two-way-min-delay? uint32
| +--rw two-way-max-delay? uint32 | +--rw two-way-max-delay? uint32
| +--rw two-way-delay-variation? uint32 | +--rw two-way-delay-variation? uint32
| +--rw two-way-packet-loss? decimal64 | +--rw two-way-packet-loss? decimal64
+--rw threshold-accelerated-advertisement +--rw threshold-accelerated-advertisement
+--rw one-way-delay? uint32 +--rw one-way-delay? uint32
+--rw one-way-residual-bandwidth? +--rw one-way-residual-bandwidth?
| rt-types:bandwidth-ieee-float32 | rt-types:bandwidth-ieee-float32
+--rw one-way-available-bandwidth? +--rw one-way-available-bandwidth?
| rt-types:bandwidth-ieee-float32 | rt-types:bandwidth-ieee-float32
+--rw one-way-utilized-bandwidth? +--rw one-way-utilized-bandwidth?
| rt-types:bandwidth-ieee-float32 | rt-types:bandwidth-ieee-float32
+--rw two-way-delay? uint32 +--rw two-way-delay? uint32
+--rw one-way-min-delay? uint32 +--rw one-way-min-delay? uint32
+--rw one-way-max-delay? uint32 +--rw one-way-max-delay? uint32
+--rw one-way-delay-variation? uint32 +--rw one-way-delay-variation? uint32
+--rw one-way-packet-loss? decimal64 +--rw one-way-packet-loss? decimal64
+--rw two-way-min-delay? uint32 +--rw two-way-min-delay? uint32
+--rw two-way-max-delay? uint32 +--rw two-way-max-delay? uint32
+--rw two-way-delay-variation? uint32 +--rw two-way-delay-variation? uint32
+--rw two-way-packet-loss? decimal64 +--rw two-way-packet-loss? decimal64
augment /te:te/te:tunnels/te:tunnel: augment /te:te/te:tunnels/te:tunnel:
+--rw tunnel-igp-shortcut +--rw tunnel-igp-shortcut
| +--rw shortcut-eligible? boolean | +--rw shortcut-eligible? boolean
| +--rw metric-type? identityref | +--rw metric-type? identityref
| +--rw metric? int32 | +--rw metric? int32
| +--rw routing-afs* inet:ip-version | +--rw routing-afs* inet:ip-version
+--rw forwarding +--rw forwarding
| +--rw binding-label? rt-types:mpls-label | +--rw binding-label? rt-types:mpls-label
| +--rw load-share? uint32 | +--rw load-share? uint32
| +--rw policy-class? uint8 | +--rw policy-class? uint8
+--rw bandwidth-mpls +--rw bandwidth-mpls
+--rw specification-type? +--rw specification-type?
| te-packet-types:te-bandwidth-requested-type | te-packet-types:te-bandwidth-requested-type
+--rw set-bandwidth? te-packet-types:bandwidth-kbps +--rw set-bandwidth? te-packet-types:bandwidth-kbps
+--rw class-type? te-types:te-ds-class +--rw class-type? te-types:te-ds-class
+--ro state +--ro state
| +--ro signaled-bandwidth? te-packet-types:bandwidth-kbps | +--ro signaled-bandwidth? te-packet-types:bandwidth-kbps
+--rw auto-bandwidth +--rw auto-bandwidth
+--rw enabled? boolean +--rw enabled? boolean
+--rw min-bw? te-packet-types:bandwidth-kbps +--rw min-bw? te-packet-types:bandwidth-kbps
+--rw max-bw? te-packet-types:bandwidth-kbps +--rw max-bw? te-packet-types:bandwidth-kbps
+--rw adjust-interval? uint32 +--rw adjust-interval? uint32
+--rw adjust-threshold? rt-types:percentage +--rw adjust-threshold? rt-types:percentage
+--rw overflow +--rw overflow
| +--rw enabled? boolean | +--rw enabled? boolean
| +--rw overflow-threshold? rt-types:percentage | +--rw overflow-threshold? rt-types:percentage
| +--rw trigger-event-count? uint16 | +--rw trigger-event-count? uint16
+--rw underflow +--rw underflow
+--rw enabled? boolean +--rw enabled? boolean
+--rw underflow-threshold? rt-types:percentage +--rw underflow-threshold? rt-types:percentage
+--rw trigger-event-count? uint16 +--rw trigger-event-count? uint16
augment /te:te/te:tunnels/te:tunnel/te:p2p-primary-paths augment /te:te/te:tunnels/te:tunnel/te:primary-paths/te:primary-path:
/te:p2p-primary-path: +--rw static-lsp-name? mpls-static:static-lsp-ref
+--rw static-lsp-name? mpls-static:static-lsp-ref augment /te:te/te:tunnels/te:tunnel/te:secondary-paths
augment /te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths /te:secondary-path:
/te:p2p-secondary-path: +--rw static-lsp-name? mpls-static:static-lsp-ref
+--rw static-lsp-name? mpls-static:static-lsp-ref augment /te:te/te:globals/te:named-path-constraints
augment /te:te/te:globals/te:named-path-constraints /te:named-path-constraint:
/te:named-path-constraint: +--rw bandwidth
+--rw bandwidth +--rw specification-type?
+--rw specification-type? | te-packet-types:te-bandwidth-requested-type
| te-packet-types:te-bandwidth-requested-type +--rw set-bandwidth? te-packet-types:bandwidth-kbps
+--rw set-bandwidth? te-packet-types:bandwidth-kbps +--rw class-type? te-types:te-ds-class
+--rw class-type? te-types:te-ds-class +--ro state
+--ro state +--ro signaled-bandwidth? te-packet-types:bandwidth-kbps
+--ro signaled-bandwidth? te-packet-types:bandwidth-kbps augment /te:te/te:tunnels/te:tunnel/te:primary-paths/te:primary-path
augment /te:te/te:tunnels/te:tunnel/te:p2p-primary-paths /te:lsps/te:lsp:
/te:p2p-primary-path/te:lsps/te:lsp: +--ro performance-metrics-one-way
+--ro performance-metrics-one-way | +--ro one-way-delay? uint32
| +--ro one-way-delay? uint32 | +--ro one-way-delay-normality?
| +--ro one-way-delay-normality? | | te-types:performance-metrics-normality
| | te-types:performance-metrics-normality | +--ro one-way-residual-bandwidth?
| +--ro one-way-residual-bandwidth? | | rt-types:bandwidth-ieee-float32
| | rt-types:bandwidth-ieee-float32 | +--ro one-way-residual-bandwidth-normality?
| +--ro one-way-residual-bandwidth-normality? | | te-types:performance-metrics-normality
| | te-types:performance-metrics-normality | +--ro one-way-available-bandwidth?
| +--ro one-way-available-bandwidth? | | rt-types:bandwidth-ieee-float32
| | rt-types:bandwidth-ieee-float32 | +--ro one-way-available-bandwidth-normality?
| +--ro one-way-available-bandwidth-normality? | | te-types:performance-metrics-normality
| | te-types:performance-metrics-normality | +--ro one-way-utilized-bandwidth?
| +--ro one-way-utilized-bandwidth? | | rt-types:bandwidth-ieee-float32
| | rt-types:bandwidth-ieee-float32 | +--ro one-way-utilized-bandwidth-normality?
| +--ro one-way-utilized-bandwidth-normality? | | te-types:performance-metrics-normality
| | te-types:performance-metrics-normality | +--ro one-way-min-delay? uint32
| +--ro one-way-min-delay? uint32 | +--ro one-way-min-delay-normality?
| +--ro one-way-min-delay-normality? | | te-types:performance-metrics-normality
| | te-types:performance-metrics-normality | +--ro one-way-max-delay? uint32
| +--ro one-way-max-delay? uint32 | +--ro one-way-max-delay-normality?
| +--ro one-way-max-delay-normality? | | te-types:performance-metrics-normality
| | te-types:performance-metrics-normality | +--ro one-way-delay-variation? uint32
| +--ro one-way-delay-variation? uint32 | +--ro one-way-delay-variation-normality?
| +--ro one-way-delay-variation-normality? | | te-types:performance-metrics-normality
| | te-types:performance-metrics-normality | +--ro one-way-packet-loss? decimal64
| +--ro one-way-packet-loss? decimal64 | +--ro one-way-packet-loss-normality?
| +--ro one-way-packet-loss-normality? | te-types:performance-metrics-normality
| te-types:performance-metrics-normality +--ro performance-metrics-two-way
+--ro performance-metrics-two-way +--ro two-way-delay? uint32
+--ro two-way-delay? uint32 +--ro two-way-delay-normality?
+--ro two-way-delay-normality? | te-types:performance-metrics-normality
| te-types:performance-metrics-normality +--ro two-way-min-delay? uint32
+--ro two-way-min-delay? uint32 +--ro two-way-min-delay-normality?
+--ro two-way-min-delay-normality? | te-types:performance-metrics-normality
| te-types:performance-metrics-normality +--ro two-way-max-delay? uint32
+--ro two-way-max-delay? uint32 +--ro two-way-max-delay-normality?
+--ro two-way-max-delay-normality? | te-types:performance-metrics-normality
| te-types:performance-metrics-normality +--ro two-way-delay-variation? uint32
+--ro two-way-delay-variation? uint32 +--ro two-way-delay-variation-normality?
+--ro two-way-delay-variation-normality? | te-types:performance-metrics-normality
| te-types:performance-metrics-normality +--ro two-way-packet-loss? decimal64
+--ro two-way-packet-loss? decimal64 +--ro two-way-packet-loss-normality?
+--ro two-way-packet-loss-normality? te-types:performance-metrics-normality
te-types:performance-metrics-normality
Figure 2: MPLS TE model configuration and state tree Figure 2: MPLS TE model configuration and state tree
2.3. MPLS TE YANG Module 2.3. MPLS TE YANG Module
<CODE BEGINS> file "ietf-te-mpls@2019-11-02.yang" <CODE BEGINS> file "ietf-te-mpls@2020-03-09.yang"
module ietf-te-mpls { module ietf-te-mpls {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-te-mpls"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-mpls";
/* Replace with IANA when assigned */ /* Replace with IANA when assigned */
prefix "te-mpls"; prefix "te-mpls";
/* Import TE base model */ /* Import TE base model */
import ietf-te { import ietf-te {
prefix te; prefix te;
skipping to change at page 10, line 8 skipping to change at page 10, line 8
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision "2019-11-02" { revision "2020-03-09" {
description "Latest update to MPLS TE YANG module."; description "Latest update to MPLS TE YANG module.";
reference reference
"RFCXXXX: A YANG Data Model for MPLS-TE Tunnels and LSP(s)"; "RFCXXXX: A YANG Data Model for MPLS-TE Tunnels and LSP(s)";
} }
/* MPLS TE tunnel properties*/ /* MPLS TE Identities */
identity tunnel-action-resetup {
base te:tunnel-actions-type;
description "Resetup tunnel action type";
}
/* MPLS TE tunnel properties*/
grouping tunnel-igp-shortcut-config { grouping tunnel-igp-shortcut-config {
description "TE tunnel IGP shortcut configs"; description "TE tunnel IGP shortcut configs";
leaf shortcut-eligible { leaf shortcut-eligible {
type boolean; type boolean;
default "true"; default "true";
description description
"Whether this LSP is considered to be eligible for us as a "Whether this LSP is considered to be eligible for us as a
shortcut in the IGP. In the case that this leaf is set to shortcut in the IGP. In the case that this leaf is set to
true, the IGP SPF calculation uses the metric specified to true, the IGP SPF calculation uses the metric specified to
determine whether traffic should be carried over this LSP"; determine whether traffic should be carried over this LSP";
skipping to change at page 16, line 42 skipping to change at page 16, line 48
/* MPLS TE tunnel augmentations */ /* MPLS TE tunnel augmentations */
augment "/te:te/te:tunnels/te:tunnel" { augment "/te:te/te:tunnels/te:tunnel" {
description "MPLS TE tunnel config augmentations"; description "MPLS TE tunnel config augmentations";
uses tunnel-igp-shortcuts; uses tunnel-igp-shortcuts;
uses tunnel-forwarding-adjacency; uses tunnel-forwarding-adjacency;
uses tunnel-bandwidth_top; uses tunnel-bandwidth_top;
} }
/* MPLS TE LSPs augmentations */ /* MPLS TE LSPs augmentations */
augment "/te:te/te:tunnels/te:tunnel/" + augment "/te:te/te:tunnels/te:tunnel/" +
"te:p2p-primary-paths/te:p2p-primary-path" { "te:primary-paths/te:primary-path" {
when "/te:te/te:tunnels/te:tunnel" + when "/te:te/te:tunnels/te:tunnel" +
"/te:p2p-primary-paths/te:p2p-primary-path" + "/te:primary-paths/te:primary-path" +
"/te:path-setup-protocol = 'te-types:path-setup-static'" { "/te:signaling-type = 'te-types:path-setup-static'" {
description description
"When the path is statically provisioned"; "When the path is statically provisioned";
} }
description "MPLS TE LSP augmentation"; description "MPLS TE LSP augmentation";
leaf static-lsp-name { leaf static-lsp-name {
type mpls-static:static-lsp-ref; type mpls-static:static-lsp-ref;
description "Static LSP name"; description "Static LSP name";
} }
} }
augment "/te:te/te:tunnels/te:tunnel/" + augment "/te:te/te:tunnels/te:tunnel/" +
"te:p2p-secondary-paths/te:p2p-secondary-path" { "te:secondary-paths/te:secondary-path" {
when "/te:te/te:tunnels/te:tunnel" + when "/te:te/te:tunnels/te:tunnel" +
"/te:p2p-secondary-paths/te:p2p-secondary-path/" + "/te:secondary-paths/te:secondary-path/" +
"te:path-setup-protocol = 'te-types:path-setup-static'" { "te:signaling-type = 'te-types:path-setup-static'" {
description description
"When the path is statically provisioned"; "When the path is statically provisioned";
} }
description "MPLS TE LSP augmentation"; description "MPLS TE LSP augmentation";
leaf static-lsp-name { leaf static-lsp-name {
type mpls-static:static-lsp-ref; type mpls-static:static-lsp-ref;
description "Static LSP name"; description "Static LSP name";
} }
} }
augment "/te:te/te:globals/te:named-path-constraints/" + augment "/te:te/te:globals/te:named-path-constraints/" +
"te:named-path-constraint" { "te:named-path-constraint" {
description "foo"; description "foo";
uses te-path-bandwidth_top; uses te-path-bandwidth_top;
} }
augment "/te:te/te:tunnels/te:tunnel/te:p2p-primary-paths" + augment "/te:te/te:tunnels/te:tunnel/te:primary-paths" +
"/te:p2p-primary-path/te:lsps/te:lsp" { "/te:primary-path/te:lsps/te:lsp" {
description description
"MPLS TE generic data augmentation pertaining to specific TE "MPLS TE generic data augmentation pertaining to specific TE
LSP"; LSP";
uses te-packet-types:performance-metrics-attributes-packet; uses te-packet-types:performance-metrics-attributes-packet;
} }
} }
<CODE ENDS> <CODE ENDS>
Figure 3: TE generic YANG module Figure 3: TE generic YANG module
skipping to change at page 19, line 8 skipping to change at page 19, line 21
6. Normative References 6. Normative References
[I-D.ietf-mpls-static-yang] [I-D.ietf-mpls-static-yang]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"A YANG Data Model for MPLS Static LSPs", draft-ietf-mpls- "A YANG Data Model for MPLS Static LSPs", draft-ietf-mpls-
static-yang-10 (work in progress), September 2019. static-yang-10 (work in progress), September 2019.
[I-D.ietf-teas-yang-rsvp] [I-D.ietf-teas-yang-rsvp]
Beeram, V., Saad, T., Gandhi, R., Liu, X., and I. Bryskin, Beeram, V., Saad, T., Gandhi, R., Liu, X., and I. Bryskin,
"A YANG Data Model for Resource Reservation Protocol "A YANG Data Model for Resource Reservation Protocol
(RSVP)", draft-ietf-teas-yang-rsvp-11 (work in progress), (RSVP)", draft-ietf-teas-yang-rsvp-12 (work in progress),
July 2019. January 2020.
[I-D.ietf-teas-yang-rsvp-te] [I-D.ietf-teas-yang-rsvp-te]
Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I., Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I.,
and H. Shah, "A YANG Data Model for RSVP-TE Protocol", and H. Shah, "A YANG Data Model for RSVP-TE Protocol",
draft-ietf-teas-yang-rsvp-te-07 (work in progress), July draft-ietf-teas-yang-rsvp-te-07 (work in progress), July
2019. 2019.
[I-D.ietf-teas-yang-te] [I-D.ietf-teas-yang-te]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"A YANG Data Model for Traffic Engineering Tunnels and "A YANG Data Model for Traffic Engineering Tunnels and
Interfaces", draft-ietf-teas-yang-te-21 (work in Interfaces", draft-ietf-teas-yang-te-22 (work in
progress), April 2019. progress), November 2019.
[I-D.ietf-teas-yang-te-types] [I-D.ietf-teas-yang-te-types]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"Traffic Engineering Common YANG Types", draft-ietf-teas- "Traffic Engineering Common YANG Types", draft-ietf-teas-
yang-te-types-11 (work in progress), October 2019. yang-te-types-13 (work in progress), November 2019.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
<https://www.rfc-editor.org/info/rfc3209>. <https://www.rfc-editor.org/info/rfc3209>.
 End of changes. 20 change blocks. 
175 lines changed or deleted 179 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/