< draft-ietf-teas-yang-sr-te-topo-04.txt   draft-ietf-teas-yang-sr-te-topo-05.txt >
Network Working Group X. Liu Network Working Group X. Liu
Internet-Draft Volta Networks Internet-Draft Volta Networks
Intended status: Standards Track I. Bryskin Intended status: Standards Track I. Bryskin
Expires: September 12, 2019 Huawei Technologies Expires: January 9, 2020 Futurewei
V. Beeram V. Beeram
Juniper Networks
T. Saad T. Saad
Cisco Systems Inc Juniper Networks
H. Shah H. Shah
Ciena Ciena
S. Litkowski S. Litkowski
Orange Business Service Orange Business Service
March 11, 2019 July 8, 2019
YANG Data Model for SR and SR TE Topologies YANG Data Model for SR and SR TE Topologies
draft-ietf-teas-yang-sr-te-topo-04 draft-ietf-teas-yang-sr-te-topo-05
Abstract Abstract
This document defines a YANG data model for Segment Routing (SR) This document defines a YANG data model for Segment Routing (SR)
topology and Segment Routing (SR) traffic engineering (TE) topology. topology and Segment Routing (SR) traffic engineering (TE) topology.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 40 skipping to change at page 1, line 39
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 September 12, 2019. This Internet-Draft will expire on January 9, 2020.
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 26 skipping to change at page 2, line 25
2. Modeling Considerations . . . . . . . . . . . . . . . . . . . 3 2. Modeling Considerations . . . . . . . . . . . . . . . . . . . 3
2.1. Segment Routing (SR) Topology . . . . . . . . . . . . . . 3 2.1. Segment Routing (SR) Topology . . . . . . . . . . . . . . 3
2.2. Segment Routing (SR) TE Topology . . . . . . . . . . . . 3 2.2. Segment Routing (SR) TE Topology . . . . . . . . . . . . 3
2.3. Relations to ietf-segment-routing . . . . . . . . . . . . 4 2.3. Relations to ietf-segment-routing . . . . . . . . . . . . 4
2.4. Topology Type Modeling . . . . . . . . . . . . . . . . . 5 2.4. Topology Type Modeling . . . . . . . . . . . . . . . . . 5
2.5. Topology Attributes . . . . . . . . . . . . . . . . . . . 5 2.5. Topology Attributes . . . . . . . . . . . . . . . . . . . 5
2.6. Node Attributes . . . . . . . . . . . . . . . . . . . . . 5 2.6. Node Attributes . . . . . . . . . . . . . . . . . . . . . 5
2.7. Link Attributes . . . . . . . . . . . . . . . . . . . . . 6 2.7. Link Attributes . . . . . . . . . . . . . . . . . . . . . 6
3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 7 3. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 7
4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 9 4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
6. Security Considerations . . . . . . . . . . . . . . . . . . . 17 6. Security Considerations . . . . . . . . . . . . . . . . . . . 17
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.1. Normative References . . . . . . . . . . . . . . . . . . 18 7.1. Normative References . . . . . . . . . . . . . . . . . . 19
7.2. Informative References . . . . . . . . . . . . . . . . . 19 7.2. Informative References . . . . . . . . . . . . . . . . . 20
Appendix A. Companion YANG Model for Non-NMDA Compliant Appendix A. Companion YANG Model for Non-NMDA Compliant
Implementations . . . . . . . . . . . . . . . . . . 21 Implementations . . . . . . . . . . . . . . . . . . 21
A.1. SR Topology State Module . . . . . . . . . . . . . . . . 21 A.1. SR Topology State Module . . . . . . . . . . . . . . . . 21
Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 24 Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 24
Appendix C. Contributors . . . . . . . . . . . . . . . . . . . . 31 Appendix C. Contributors . . . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
This document defines a YANG [RFC7950] data model for describing the This document defines a YANG [RFC7950] data model for describing the
skipping to change at page 9, line 7 skipping to change at page 9, line 7
+--rw is-part-of-set? boolean +--rw is-part-of-set? boolean
+--rw is-persistent? boolean +--rw is-persistent? boolean
+--rw is-on-lan? boolean +--rw is-on-lan? boolean
+--ro information-source? enumeration +--ro information-source? enumeration
+--ro information-source-instance? string +--ro information-source-instance? string
+--ro information-source-state +--ro information-source-state
+--ro credibility-preference? uint16 +--ro credibility-preference? uint16
4. YANG Module 4. YANG Module
<CODE BEGINS> file "ietf-sr-topology@2019-03-09.yang" <CODE BEGINS> file "ietf-sr-topology@2019-06-28.yang"
module ietf-sr-topology { module ietf-sr-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-sr-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-sr-topology";
prefix "srt"; prefix "srt";
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference "RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-network-topology { import ietf-network-topology {
skipping to change at page 10, line 26 skipping to change at page 10, line 26
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2019-03-09 { revision 2019-06-28 {
description "Initial revision"; description "Initial revision";
reference reference
"RFC XXXX: YANG Data Model for SR and SR TE Topologies"; "RFC XXXX: YANG Data Model for SR and SR TE Topologies";
} }
feature msd { feature msd {
description description
"Support of signaling MSD (Maximum SID Depth) in IGP."; "Support of signaling MSD (Maximum SID Depth) in IGP.";
} }
grouping sr-topology-type { grouping sr-topology-type {
description description
"Identifies the SR-MPLS topology type. This type of network "Identifies the SR-MPLS topology type. This type of network
toplogies use Segment Routing (SR) technology over the MPLS topologies use Segment Routing (SR) technology over the MPLS
data plane"; data plane";
container sr-mpls { container sr-mpls {
presence "Indiates SR-MPLS topology"; presence "Indicates SR-MPLS topology";
description description
"Its presence identifies the SR topology type."; "Its presence identifies the SR topology type.";
} }
} }
augment "/nw:networks/nw:network/nw:network-types/" augment "/nw:networks/nw:network/nw:network-types/"
+ "l3t:l3-unicast-topology" { + "l3t:l3-unicast-topology" {
description description
"Defines the SR topology type."; "Defines the SR topology type.";
uses sr-topology-type; uses sr-topology-type;
skipping to change at page 11, line 49 skipping to change at page 11, line 49
} }
description "Augment link configuration"; description "Augment link configuration";
uses sr-link-attributes; uses sr-link-attributes;
} }
grouping sr-topology-attributes { grouping sr-topology-attributes {
description "SR topology scope attributes."; description "SR topology scope attributes.";
container sr { container sr {
description description
"Containing SR attributes."; "Containing SR attributes.";
uses sr-cmn:srgb; uses sr-cmn:srgb {
refine srgb {
must "lower-bound <= upper-bound" {
error-message
"lower-bound must not be greater than upper-bound.";
}
}
}
} // sr } // sr
} // sr-topology-attributes } // sr-topology-attributes
grouping information-source-attributes { grouping information-source-attributes {
description description
"The attributes identifying source that has provided the "The attributes identifying source that has provided the
related information, and the source credibility."; related information, and the source credibility.";
leaf information-source { leaf information-source {
type enumeration { type enumeration {
enum "unknown" { enum "unknown" {
description "The source is unknown."; description "The source is unknown.";
} }
enum "locally-configured" { enum "locally-configured" {
skipping to change at page 13, line 23 skipping to change at page 13, line 31
Higher value is more preferable."; Higher value is more preferable.";
} }
} }
} // information-source-attributes } // information-source-attributes
grouping sr-node-attributes { grouping sr-node-attributes {
description "SR node scope attributes."; description "SR node scope attributes.";
container sr { container sr {
description description
"Containing SR attributes."; "Containing SR attributes.";
uses sr-cmn:srgb; uses sr-cmn:srgb {
uses sr-cmn:srlb; refine srgb {
must "lower-bound <= upper-bound" {
error-message
"lower-bound must not be greater than upper-bound.";
}
}
}
uses sr-cmn:srlb {
refine srlb {
must "lower-bound <= upper-bound" {
error-message
"lower-bound must not be greater than upper-bound.";
}
}
}
uses sr-cmn:node-capabilities; uses sr-cmn:node-capabilities;
leaf msd { leaf msd {
if-feature "msd"; if-feature "msd";
type uint8; type uint8;
description description
"Node MSD is the lowest MSD supported by the node."; "Node MSD is the lowest MSD supported by the node.";
} }
// Operational state data // Operational state data
uses information-source-attributes; uses information-source-attributes;
} // sr } // sr
skipping to change at page 17, line 27 skipping to change at page 17, line 50
-------------------------------------------------------------------- --------------------------------------------------------------------
6. Security Considerations 6. Security Considerations
The YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246]. [RFC8446].
The NETCONF access control model [RFC6536] provides the means to The Network Configuration Access Control Model (NACM) [RFC8341]
restrict access for particular NETCONF or RESTCONF users to a provides the means to restrict access for particular NETCONF or
preconfigured subset of all available NETCONF or RESTCONF protocol RESTCONF users to a preconfigured subset of all available NETCONF or
operations and content. RESTCONF protocol operations and content.
There are a number of data nodes defined in this YANG module that are There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability: and their sensitivity/vulnerability:
nw:network-types/l3t:l3-unicast-topology/sr-mpls nw:network-types/l3t:l3-unicast-topology/sr-mpls
skipping to change at page 18, line 49 skipping to change at page 19, line 24
7. References 7. References
7.1. Normative References 7.1. Normative References
[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>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
(TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/RFC3688, January 2004,
DOI 10.17487/RFC5246, August 2008, <https://www.rfc-editor.org/info/rfc3688>.
<https://www.rfc-editor.org/info/rfc5246>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012,
<https://www.rfc-editor.org/info/rfc6536>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
7.2. Informative References 7.2. Informative References
[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",
RFC 7951, DOI 10.17487/RFC7951, August 2016, RFC 7951, DOI 10.17487/RFC7951, August 2016,
<https://www.rfc-editor.org/info/rfc7951>. <https://www.rfc-editor.org/info/rfc7951>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
skipping to change at page 20, line 13 skipping to change at page 20, line 46
2018, <https://www.rfc-editor.org/info/rfc8345>. 2018, <https://www.rfc-editor.org/info/rfc8345>.
[RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., [RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X.,
Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model
for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346, for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346,
March 2018, <https://www.rfc-editor.org/info/rfc8346>. March 2018, <https://www.rfc-editor.org/info/rfc8346>.
[I-D.ietf-teas-yang-te-topo] [I-D.ietf-teas-yang-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for Traffic Engineering (TE) O. Dios, "YANG Data Model for Traffic Engineering (TE)
Topologies", draft-ietf-teas-yang-te-topo-19 (work in Topologies", draft-ietf-teas-yang-te-topo-22 (work in
progress), February 2019. progress), June 2019.
[I-D.ietf-spring-sr-yang] [I-D.ietf-spring-sr-yang]
Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J. Litkowski, S., Qu, Y., Lindem, A., Sarkar, P., and J.
Tantsura, "YANG Data Model for Segment Routing", draft- Tantsura, "YANG Data Model for Segment Routing", draft-
ietf-spring-sr-yang-12 (work in progress), February 2019. ietf-spring-sr-yang-13 (work in progress), July 2019.
Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations
The YANG module ietf-sr-topology defined in this document is designed The YANG module ietf-sr-topology defined in this document is designed
to be used in conjunction with implementations that support the to be used in conjunction with implementations that support the
Network Management Datastore Architecture (NMDA) defined in Network Management Datastore Architecture (NMDA) defined in
[RFC8342]. In order to allow implementations to use the model even [RFC8342]. In order to allow implementations to use the model even
in cases when NMDA is not supported, the following companion module, in cases when NMDA is not supported, the following companion module,
ietf-sr-topology-state, is defined as state model, which mirrors the ietf-sr-topology-state, is defined as state model, which mirrors the
module ietf-sr-topology defined earlier in this document. However, module ietf-sr-topology defined earlier in this document. However,
skipping to change at page 21, line 27 skipping to change at page 21, line 27
The companion module, ietf-sr-topology-state, is redundant and SHOULD The companion module, ietf-sr-topology-state, is redundant and SHOULD
NOT be supported by implementations that support NMDA. NOT be supported by implementations that support NMDA.
As the structure of the companion module mirrors that of the As the structure of the companion module mirrors that of the
coorespinding NMDA model, the YANG tree of the companion module is coorespinding NMDA model, the YANG tree of the companion module is
not depicted separately. not depicted separately.
A.1. SR Topology State Module A.1. SR Topology State Module
<CODE BEGINS> file "ietf-sr-topology-state@2019-03-09.yang" <CODE BEGINS> file "ietf-sr-topology-state@2019-06-28.yang"
module ietf-sr-topology-state { module ietf-sr-topology-state {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-sr-topology-state"; namespace "urn:ietf:params:xml:ns:yang:ietf-sr-topology-state";
prefix "srt-s"; prefix "srt-s";
import ietf-sr-topology { import ietf-sr-topology {
prefix "srt"; prefix "srt";
} }
import ietf-network-state { import ietf-network-state {
prefix "nw-s"; prefix "nw-s";
skipping to change at page 22, line 50 skipping to change at page 22, line 50
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2019-03-09 { revision 2019-06-28 {
description "Initial revision"; description "Initial revision";
reference reference
"RFC XXXX: YANG Data Model for SR and SR TE Topologies"; "RFC XXXX: YANG Data Model for SR and SR TE Topologies";
} }
augment "/nw-s:networks/nw-s:network/nw-s:network-types/" augment "/nw-s:networks/nw-s:network/nw-s:network-types/"
+ "l3t-s:l3-unicast-topology" { + "l3t-s:l3-unicast-topology" {
description description
"Defines the SR topology type."; "Defines the SR topology type.";
uses srt:sr-topology-type; uses srt:sr-topology-type;
skipping to change at page 31, line 21 skipping to change at page 31, line 21
Email: yingzhen.qu@huawei.com Email: yingzhen.qu@huawei.com
Authors' Addresses Authors' Addresses
Xufeng Liu Xufeng Liu
Volta Networks Volta Networks
EMail: xufeng.liu.ietf@gmail.com EMail: xufeng.liu.ietf@gmail.com
Igor Bryskin Igor Bryskin
Huawei Technologies Futurewei
EMail: Igor.Bryskin@huawei.com EMail: igor.bryskin@futurewei.com
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
Himanshu Shah Himanshu Shah
Ciena Ciena
EMail: hshah@ciena.com EMail: hshah@ciena.com
Stephane Litkowski Stephane Litkowski
Orange Business Service Orange Business Service
EMail: stephane.litkowski@orange.com EMail: stephane.litkowski@orange.com
 End of changes. 29 change blocks. 
40 lines changed or deleted 69 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/