draft-ietf-teas-yang-rsvp-te-05.txt   draft-ietf-teas-yang-rsvp-te-06.txt 
TEAS Working Group V. Beeram TEAS Working Group V. Beeram
Internet-Draft Juniper Networks Internet-Draft T. Saad
Intended status: Standards Track T. Saad Intended status: Standards Track Juniper Networks
Expires: August 22, 2019 R. Gandhi Expires: October 11, 2019 R. Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
X. Liu X. Liu
Volta Networks Volta Networks
I. Bryskin I. Bryskin
Huawei Technologies Huawei Technologies
H. Shah H. Shah
Ciena Ciena
February 18, 2019 April 09, 2019
A YANG Data Model for RSVP-TE Protocol A YANG Data Model for RSVP-TE Protocol
draft-ietf-teas-yang-rsvp-te-05 draft-ietf-teas-yang-rsvp-te-06
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 RSVP (Resource Reservation Protocol) to establish management of RSVP (Resource Reservation Protocol) to establish
Traffic-Engineered (TE) Label-Switched Paths (LSPs) for MPLS (Multi- Traffic-Engineered (TE) Label-Switched Paths (LSPs) for MPLS (Multi-
Protocol Label Switching) and other technologies. Protocol Label Switching) and other technologies.
The model defines a generic RSVP-TE module for signaling LSPs that is The model defines a generic RSVP-TE module for signaling LSPs that is
technology agnostic. The generic RSVP-TE module is to be augmented technology agnostic. The generic RSVP-TE module is to be augmented
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 August 22, 2019. This Internet-Draft will expire on October 11, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
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
2. Model Overview . . . . . . . . . . . . . . . . . . . . . . . 4 2. Model Overview . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Module Relationship . . . . . . . . . . . . . . . . . . . 4 2.1. Module Relationship . . . . . . . . . . . . . . . . . . . 4
2.2. Model Tree Diagrams . . . . . . . . . . . . . . . . . . . 5 2.2. Model Tree Diagrams . . . . . . . . . . . . . . . . . . . 5
2.2.1. RSVP-TE Model Tree Diagram . . . . . . . . . . . . . 5 2.2.1. RSVP-TE Model Tree Diagram . . . . . . . . . . . . . 5
2.2.2. RSVP-TE MPLS Model Tree Diagram . . . . . . . . . . . 13 2.2.2. RSVP-TE MPLS Model Tree Diagram . . . . . . . . . . . 14
2.3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . 15 2.3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . 16
2.3.1. RSVP-TE YANG Module . . . . . . . . . . . . . . . . . 15 2.3.1. RSVP-TE YANG Module . . . . . . . . . . . . . . . . . 16
2.3.2. RSVP-TE MPLS YANG Module . . . . . . . . . . . . . . 26 2.3.2. RSVP-TE MPLS YANG Module . . . . . . . . . . . . . . 29
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41
4. Security Considerations . . . . . . . . . . . . . . . . . . . 38 4. Security Considerations . . . . . . . . . . . . . . . . . . . 41
5. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 39 5. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 42
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 39 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 42
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.1. Normative References . . . . . . . . . . . . . . . . . . 40 7.1. Normative References . . . . . . . . . . . . . . . . . . 43
7.2. Informative References . . . . . . . . . . . . . . . . . 42 7.2. Informative References . . . . . . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
1. Introduction 1. Introduction
YANG [RFC7950] is a data modeling language that was introduced to YANG [RFC7950] is a data modeling language that was introduced 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 11, line 18 skipping to change at page 11, line 18
| +--ro node-id? te-node-id | +--ro node-id? te-node-id
| +--ro flags* path-attribute-flags | +--ro flags* path-attribute-flags
+--:(label) +--:(label)
+--ro label-hop +--ro label-hop
+--ro te-label +--ro te-label
| +--ro (technology)? | +--ro (technology)?
| | +--:(generic) | | +--:(generic)
| | +--ro generic? rt-types:generalized-label | | +--ro generic? rt-types:generalized-label
| +--ro direction? te-label-direction | +--ro direction? te-label-direction
+--ro flags* path-attribute-flags +--ro flags* path-attribute-flags
augment /te:te/te:tunnels/te:tunnel/te:p2p-primary-paths
/te:p2p-primary-path/te:lsp-provisioning-error-infos
/te:lsp-provisioning-error-info:
+--ro rsvp-message-type? identityref
+--ro rsvp-error-code? uint8
+--ro rsvp-error-subcode? uint16
augment /te:te/te:tunnels/te:tunnel/te:p2p-primary-paths
/te:p2p-primary-path/te:lsps/te:lsp
/te:lsp-provisioning-error-infos
/te:lsp-provisioning-error-info:
+--ro rsvp-message-type? identityref
+--ro rsvp-error-code? uint8
+--ro rsvp-error-subcode? uint16
augment /te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths augment /te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths
/te:p2p-secondary-path/te:lsps/te:lsp: /te:p2p-secondary-path/te:lsps/te:lsp:
+--ro associated-rsvp-session? leafref +--ro associated-rsvp-session? leafref
+--ro lsp-signaled-name? string +--ro lsp-signaled-name? string
+--ro session-attribute* identityref +--ro session-attribute* identityref
+--ro lsp-attribute* identityref +--ro lsp-attribute* identityref
+--ro explicit-route-objects +--ro explicit-route-objects
| +--ro incoming-explicit-route-hop* [index] | +--ro incoming-explicit-route-hop* [index]
| | +--ro index uint32 | | +--ro index uint32
| | +--ro (type)? | | +--ro (type)?
skipping to change at page 13, line 37 skipping to change at page 13, line 50
| +--ro node-id? te-node-id | +--ro node-id? te-node-id
| +--ro flags* path-attribute-flags | +--ro flags* path-attribute-flags
+--:(label) +--:(label)
+--ro label-hop +--ro label-hop
+--ro te-label +--ro te-label
| +--ro (technology)? | +--ro (technology)?
| | +--:(generic) | | +--:(generic)
| | +--ro generic? rt-types:generalized-label | | +--ro generic? rt-types:generalized-label
| +--ro direction? te-label-direction | +--ro direction? te-label-direction
+--ro flags* path-attribute-flags +--ro flags* path-attribute-flags
augment /te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths
/te:p2p-secondary-path/te:lsp-provisioning-error-infos
/te:lsp-provisioning-error-info:
+--ro rsvp-message-type? identityref
+--ro rsvp-error-code? uint8
+--ro rsvp-error-subcode? uint16
augment /te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths
/te:p2p-secondary-path/te:lsps/te:lsp
/te:lsp-provisioning-error-infos
/te:lsp-provisioning-error-info:
+--ro rsvp-message-type? identityref
+--ro rsvp-error-code? uint8
+--ro rsvp-error-subcode? uint16
augment /te:te/te-dev:interfaces/te-dev:interface: augment /te:te/te-dev:interfaces/te-dev:interface:
Figure 2: RSVP-TE model Tree diagram Figure 2: RSVP-TE model Tree diagram
2.2.2. RSVP-TE MPLS Model Tree Diagram 2.2.2. RSVP-TE MPLS Model Tree Diagram
Figure 5 shows the YANG tree diagram of the RSVP-TE MPLS YANG model Figure 5 shows the YANG tree diagram of the RSVP-TE MPLS YANG model
defined in module ietf-rsvp-te-mpls.yang and that augments RSVP-TE defined in module ietf-rsvp-te-mpls.yang and that augments RSVP-TE
module as well as RSVP and TE YANG modules. module as well as RSVP and TE YANG modules.
skipping to change at page 15, line 49 skipping to change at page 16, line 26
o ietf-te-types defined in [I-D.ietf-teas-yang-te-types] o ietf-te-types defined in [I-D.ietf-teas-yang-te-types]
o ietf-te and ietf-te-dev defined in [I-D.ietf-teas-yang-te] o ietf-te and ietf-te-dev defined in [I-D.ietf-teas-yang-te]
This module references the following documents: This module references the following documents:
[I-D.ietf-teas-yang-rsvp], [RFC8349], [I-D.ietf-teas-yang-te], [I-D.ietf-teas-yang-rsvp], [RFC8349], [I-D.ietf-teas-yang-te],
[I-D.ietf-teas-yang-te-types], [RFC2210], [RFC4920], [RFC5420], [I-D.ietf-teas-yang-te-types], [RFC2210], [RFC4920], [RFC5420],
[RFC7570], [RFC4859]. [RFC7570], [RFC4859].
<CODE BEGINS> file "ietf-rsvp-te@2019-02-18.yang" <CODE BEGINS> file "ietf-rsvp-te@2019-04-09.yang"
module ietf-rsvp-te { module ietf-rsvp-te {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te"; namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te";
prefix "rsvp-te"; prefix "rsvp-te";
import ietf-rsvp { import ietf-rsvp {
prefix rsvp; prefix rsvp;
reference "draft-ietf-teas-yang-rsvp: A YANG Data Model for reference "draft-ietf-teas-yang-rsvp: A YANG Data Model for
Resource Reservation Protocol (RSVP)"; Resource Reservation Protocol (RSVP)";
} }
skipping to change at page 17, line 50 skipping to change at page 18, line 28
(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-02-18" { revision "2019-04-09" {
description "A YANG Data Model for RSVP-TE"; description "A YANG Data Model for RSVP-TE";
reference reference
"RFCXXXX: A YANG Data Model for RSVP-TE Protocol"; "RFCXXXX: A YANG Data Model for RSVP-TE Protocol";
} }
identity rsvp-message-type {
description "RSVP message types";
}
identity rsvp-message-path {
base rsvp-message-type;
description "RSVP Path message";
reference "RFC2205";
}
identity rsvp-message-resv {
base rsvp-message-type;
description "RSVP Resv message";
reference "RFC2205";
}
identity rsvp-message-path-err {
base rsvp-message-type;
description "RSVP Path-Err message";
reference "RFC2205";
}
identity rsvp-message-resv-err {
base rsvp-message-type;
description "RSVP Resv-Err message";
reference "RFC2205";
}
identity rsvp-message-path-tear {
base rsvp-message-type;
description "RSVP Path Tear message";
reference "RFC2205";
}
identity rsvp-message-resv-conf {
base rsvp-message-type;
description "RSVP Resv Confirm message";
reference "RFC2205";
}
identity rsvp-message-srefresh {
base rsvp-message-type;
description "RSVP SRefresh message";
reference "RFC2961";
}
identity rsvp-message-hello {
base rsvp-message-type;
description "RSVP Hello message";
reference "RFC3209";
}
identity rsvp-message-bundle {
base rsvp-message-type;
description "RSVP Bundle message";
reference "RFC2961";
}
identity rsvp-message-notify {
base rsvp-message-type;
description "RSVP Notify message";
reference "RFC3473";
}
/** /**
* RSVP-TE LSPs groupings. * RSVP-TE LSPs groupings.
*/ */
grouping lsp-record-route-information-state { grouping lsp-record-route-information-state {
description "recorded route information grouping"; description "recorded route information grouping";
container incoming-record-route-subobjects { container incoming-record-route-subobjects {
description "RSVP recorded route object incoming information"; description "RSVP recorded route object incoming information";
list incoming-record-route-subobject { list incoming-record-route-subobject {
when "../../te:origin-type != 'ingress'" { when "../../te:origin-type != 'ingress'" {
description "Applicable on non-ingress LSPs only"; description "Applicable on non-ingress LSPs only";
} }
key "index"; key "index";
ordered-by user; ordered-by user;
description description
"List of RSVP Path record-route objects"; "List of RSVP Path record-route objects";
uses te-types:record-route_state; uses te-types:record-route-state;
} }
} }
container outgoing-record-route-subobjects { container outgoing-record-route-subobjects {
description "RSVP recorded route object outgoing information"; description "RSVP recorded route object outgoing information";
list outgoing-record-route-subobject { list outgoing-record-route-subobject {
when "../../te:origin-type != 'egress'" { when "../../te:origin-type != 'egress'" {
description "Applicable on non-egress LSPs only"; description "Applicable on non-egress LSPs only";
} }
key "index"; key "index";
ordered-by user; ordered-by user;
description description
"List of RSVP Resv record-route objects"; "List of RSVP Resv record-route objects";
uses te-types:record-route_state; uses te-types:record-route-state;
} }
} }
} }
grouping lsp-explicit-route-information-state { grouping lsp-explicit-route-information-state {
description "RSVP-TE LSP explicit-route information"; description "RSVP-TE LSP explicit-route information";
container explicit-route-objects { container explicit-route-objects {
description "Explicit route object information"; description "Explicit route object information";
list incoming-explicit-route-hop { list incoming-explicit-route-hop {
when "../../te:origin-type != 'ingress'" { when "../../te:origin-type != 'ingress'" {
skipping to change at page 24, line 30 skipping to change at page 26, line 14
description description
"When the path signaling protocol is RSVP-TE "; "When the path signaling protocol is RSVP-TE ";
} }
description description
"RSVP-TE generic data augmentation pertaining to TE tunnels"; "RSVP-TE generic data augmentation pertaining to TE tunnels";
uses lsp-properties-config; uses lsp-properties-config;
uses tunnel-properties-config; uses tunnel-properties-config;
} }
/* TE LSP augmentation */ /* TE LSP augmentation */
grouping rsvp-te-lsp-error-info {
description
"Grouping for RSVP-TE error reporting information";
leaf rsvp-message-type {
type identityref {
base rsvp-message-type;
}
description
"The RSVP message type that delivered the error";
}
leaf rsvp-error-code {
type uint8;
description "RSVP error code";
reference "RFC2205";
}
leaf rsvp-error-subcode {
type uint16;
description "RSVP Error sub-codes";
reference "RFC2205";
}
}
grouping rsvp-te-lsp-properties { grouping rsvp-te-lsp-properties {
description "RSVP-TE LSP properties grouping"; description "RSVP-TE LSP properties grouping";
leaf associated-rsvp-session { leaf associated-rsvp-session {
type leafref { type leafref {
path "/rt:routing/rt:control-plane-protocols/" path "/rt:routing/rt:control-plane-protocols/"
+ "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/" + "rt:control-plane-protocol/rsvp:rsvp/rsvp:globals/"
+ "rsvp:sessions/rsvp:session/rsvp:local-index"; + "rsvp:sessions/rsvp:session/rsvp:local-index";
} }
config false; config false;
description description
skipping to change at page 25, line 28 skipping to change at page 27, line 34
"/te:p2p-primary-path/te:lsps/te:lsp" + "/te:p2p-primary-path/te:lsps/te:lsp" +
"/te:path-setup-protocol = 'te-types:path-setup-rsvp'" { "/te:path-setup-protocol = 'te-types:path-setup-rsvp'" {
description description
"When the signaling protocol is RSVP-TE "; "When the signaling protocol is RSVP-TE ";
} }
description description
"RSVP-TE generic data augmentation pertaining to specific TE "RSVP-TE generic data augmentation pertaining to specific TE
LSP"; LSP";
uses rsvp-te-lsp-properties; uses rsvp-te-lsp-properties;
} }
augment "/te:te/te:tunnels/te:tunnel/te:p2p-primary-paths" +
"/te:p2p-primary-path" +
"/te:lsp-provisioning-error-infos" +
"/te:lsp-provisioning-error-info" {
description
"Augmentation for RSVP-TE per LSP error reason";
uses rsvp-te-lsp-error-info;
}
augment "/te:te/te:tunnels/te:tunnel/te:p2p-primary-paths" +
"/te:p2p-primary-path/te:lsps/te:lsp" +
"/te:lsp-provisioning-error-infos" +
"/te:lsp-provisioning-error-info" {
when "/te:te/te:tunnels/te:tunnel/te:p2p-primary-paths" +
"/te:p2p-primary-path/te:lsps/te:lsp" +
"/te:path-setup-protocol = 'te-types:path-setup-rsvp'" {
description
"When the signaling protocol is RSVP-TE ";
}
description
"Augmentation for RSVP-TE per path error reason";
uses rsvp-te-lsp-error-info;
}
augment "/te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths" + augment "/te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths" +
"/te:p2p-secondary-path/te:lsps/te:lsp" { "/te:p2p-secondary-path/te:lsps/te:lsp" {
when "/te:te/te:tunnels/te:tunnel/te:p2p-primary-paths" + when "/te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths" +
"/te:p2p-primary-path/te:lsps/te:lsp" + "/te:p2p-secondary-path/te:lsps/te:lsp" +
"/te:path-setup-protocol = 'te-types:path-setup-rsvp'" { "/te:path-setup-protocol = 'te-types:path-setup-rsvp'" {
description description
"When the signaling protocol is RSVP-TE "; "When the signaling protocol is RSVP-TE ";
} }
description description
"RSVP-TE generic data augmentation pertaining to specific TE "RSVP-TE generic data augmentation pertaining to specific TE
LSP"; LSP";
uses rsvp-te-lsp-properties; uses rsvp-te-lsp-properties;
} }
augment "/te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths" +
"/te:p2p-secondary-path" +
"/te:lsp-provisioning-error-infos" +
"/te:lsp-provisioning-error-info" {
description
"Augmentation for RSVP-TE per path error reason";
uses rsvp-te-lsp-error-info;
}
augment "/te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths" +
"/te:p2p-secondary-path/te:lsps/te:lsp" +
"/te:lsp-provisioning-error-infos" +
"/te:lsp-provisioning-error-info" {
when "/te:te/te:tunnels/te:tunnel/te:p2p-secondary-paths" +
"/te:p2p-secondary-path/te:lsps/te:lsp" +
"/te:path-setup-protocol = 'te-types:path-setup-rsvp'" {
description
"When the signaling protocol is RSVP-TE ";
}
description
"Augmentation for RSVP-TE per LSP error reason";
uses rsvp-te-lsp-error-info;
}
/* TE interface augmentation */ /* TE interface augmentation */
augment "/te:te/te-dev:interfaces/te-dev:interface" { augment "/te:te/te-dev:interfaces/te-dev:interface" {
description description
"RSVP-TE generic data augmentation pertaining to specific TE "RSVP-TE generic data augmentation pertaining to specific TE
interface"; interface";
} }
} }
<CODE ENDS> <CODE ENDS>
Figure 4: RSVP TE generic YANG module Figure 4: RSVP TE generic YANG module
2.3.2. RSVP-TE MPLS YANG Module 2.3.2. RSVP-TE MPLS YANG Module
The RSVP-TE MPLS YANG module "ietf-rsvp-te-mpls" imports the The RSVP-TE MPLS YANG module "ietf-rsvp-te-mpls" imports the
following module(s): following module(s):
o ietf-rsvp defined in [I-D.ietf-teas-yang-rsvp] o ietf-rsvp defined in [I-D.ietf-teas-yang-rsvp]
o ietf-routing-types defined in [RFC8294] o ietf-routing-types defined in [RFC8294]
skipping to change at page 26, line 23 skipping to change at page 29, line 25
o ietf-routing-types defined in [RFC8294] o ietf-routing-types defined in [RFC8294]
o ietf-te-mpls-types defined in [I-D.ietf-teas-yang-te-types] o ietf-te-mpls-types defined in [I-D.ietf-teas-yang-te-types]
o ietf-te and ietf-te-dev defined in [I-D.ietf-teas-yang-te] o ietf-te and ietf-te-dev defined in [I-D.ietf-teas-yang-te]
This module references the following documents: This module references the following documents:
[I-D.ietf-teas-yang-rsvp], [RFC8349], [I-D.ietf-teas-yang-te-types], [I-D.ietf-teas-yang-rsvp], [RFC8349], [I-D.ietf-teas-yang-te-types],
[I-D.ietf-teas-yang-te], [RFC3209]. [I-D.ietf-teas-yang-te], [RFC3209].
<CODE BEGINS> file "ietf-rsvp-te-mpls@2019-02-18.yang" <CODE BEGINS> file "ietf-rsvp-te-mpls@2019-04-09.yang"
module ietf-rsvp-te-mpls { module ietf-rsvp-te-mpls {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te-mpls"; namespace "urn:ietf:params:xml:ns:yang:ietf-rsvp-te-mpls";
prefix "rsvp-te-mpls"; prefix "rsvp-te-mpls";
import ietf-rsvp { import ietf-rsvp {
prefix "rsvp"; prefix "rsvp";
reference "draft-ietf-teas-yang-rsvp: A YANG Data Model for reference "draft-ietf-teas-yang-rsvp: A YANG Data Model for
skipping to change at page 28, line 26 skipping to change at page 31, line 28
(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-02-18" { revision "2019-04-09" {
description "Update to MPLS RSVP-TE YANG initial revision."; description "Update to MPLS RSVP-TE YANG initial revision.";
reference reference
"RFCXXXX: A YANG Data Model for RSVP-TE Protocol"; "RFCXXXX: A YANG Data Model for RSVP-TE Protocol";
} }
/* RSVP-TE MPLS LSPs groupings */ /* RSVP-TE MPLS LSPs groupings */
grouping lsp-attributes-flags-mpls-config { grouping lsp-attributes-flags-mpls-config {
description description
"Configuration parameters relating to RSVP-TE MPLS LSP "Configuration parameters relating to RSVP-TE MPLS LSP
attribute flags"; attribute flags";
skipping to change at page 40, line 32 skipping to change at page 43, line 32
[I-D.ietf-teas-yang-rsvp] [I-D.ietf-teas-yang-rsvp]
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 Resource Reservation and H. Shah, "A YANG Data Model for Resource Reservation
Protocol (RSVP)", draft-ietf-teas-yang-rsvp-10 (work in Protocol (RSVP)", draft-ietf-teas-yang-rsvp-10 (work in
progress), February 2019. progress), February 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-19 (work in Interfaces", draft-ietf-teas-yang-te-21 (work in
progress), February 2019. progress), April 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-06 (work in progress), February 2019. yang-te-types-08 (work in progress), April 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>.
[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. [RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, DOI 10.17487/RFC2205, Functional Specification", RFC 2205, DOI 10.17487/RFC2205,
September 1997, <https://www.rfc-editor.org/info/rfc2205>. September 1997, <https://www.rfc-editor.org/info/rfc2205>.
skipping to change at page 43, line 5 skipping to change at page 46, line 5
DOI 10.17487/RFC7570, July 2015, DOI 10.17487/RFC7570, July 2015,
<https://www.rfc-editor.org/info/rfc7570>. <https://www.rfc-editor.org/info/rfc7570>.
Authors' Addresses Authors' Addresses
Vishnu Pavan Beeram Vishnu Pavan Beeram
Juniper Networks Juniper Networks
Email: vbeeram@juniper.net Email: vbeeram@juniper.net
Tarek Saad Tarek Saad
Cisco Systems, Inc. Juniper Networks
Email: tsaad@cisco.com Email: tsaad@juniper.net
Rakesh Gandhi Rakesh Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
Email: rgandhi@cisco.com Email: rgandhi@cisco.com
Xufeng Liu Xufeng Liu
Volta Networks Volta Networks
Email: xufeng.liu.ietf@gmail.com Email: xufeng.liu.ietf@gmail.com
 End of changes. 24 change blocks. 
31 lines changed or deleted 180 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/