draft-ietf-ccamp-otn-topo-yang-01.txt   draft-ietf-ccamp-otn-topo-yang-02.txt 
CCAMP Working Group H. Zheng CCAMP Working Group H. Zheng
Internet-Draft Z. Fan Internet-Draft Z. Fan
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: March 18, 2018 A. Sharma Expires: May 3, 2018 A. Sharma
Google Google
X. Liu X. Liu
Jabil Jabil
S. Belotti S. Belotti
Nokia Nokia
Y. Xu Y. Xu
CAICT CAICT
L. Wang L. Wang
China Mobile China Mobile
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica Telefonica
September 14, 2017 October 30, 2017
A YANG Data Model for Optical Transport Network Topology A YANG Data Model for Optical Transport Network Topology
draft-ietf-ccamp-otn-topo-yang-01 draft-ietf-ccamp-otn-topo-yang-02
Abstract Abstract
A transport network is a server-layer network designed to provide A transport network is a server-layer network designed to provide
connectivity services for a client-layer network to carry the client connectivity services for a client-layer network to carry the client
traffic transparently across the server-layer network resources. A traffic transparently across the server-layer network resources. A
transport network can be constructed from equipments utilizing any of transport network can be constructed from equipments utilizing any of
a number of different transport technologies such as the evolving a number of different transport technologies such as the evolving
Optical Transport Networks (OTN) or packet transport as provided by Optical Transport Networks (OTN) or packet transport as provided by
the MPLS-Transport Profile (MPLS-TP). the MPLS-Transport Profile (MPLS-TP).
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 March 18, 2018. This Internet-Draft will expire on May 3, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 33 skipping to change at page 2, line 33
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3
3. YANG Data Model for OTN Topology . . . . . . . . . . . . . . 4 3. YANG Data Model for OTN Topology . . . . . . . . . . . . . . 4
3.1. the YANG Tree . . . . . . . . . . . . . . . . . . . . . . 4 3.1. the YANG Tree . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Explanation of the OTN Topology Data Model . . . . . . . 5 3.2. Explanation of the OTN Topology Data Model . . . . . . . 4
3.3. The YANG Code . . . . . . . . . . . . . . . . . . . . . . 6 3.3. The YANG Code . . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5. Manageability Considerations . . . . . . . . . . . . . . . . 11 5. Manageability Considerations . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 12 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 13 9.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
A transport network is a server-layer network designed to provide A transport network is a server-layer network designed to provide
connectivity services for a client-layer network to carry the client connectivity services for a client-layer network to carry the client
traffic transparently across the server-layer network resources. A traffic transparently across the server-layer network resources. A
transport network can be constructed of equipments utilizing any of a transport network can be constructed of equipments utilizing any of a
number of different transport technologies such as the Optical number of different transport technologies such as the Optical
Transport Networks (OTN) or packet transport as provided by the MPLS- Transport Networks (OTN) or packet transport as provided by the MPLS-
Transport Profile (MPLS-TP). Transport Profile (MPLS-TP).
skipping to change at page 3, line 28 skipping to change at page 3, line 28
o To enforce the establishment and update of a network topology with o To enforce the establishment and update of a network topology with
the characteristic specified in the data model, e.g., by a client the characteristic specified in the data model, e.g., by a client
controller; controller;
The YANG model defined in this document is independent of control The YANG model defined in this document is independent of control
plane protocols and captures topology related information pertaining plane protocols and captures topology related information pertaining
to an Optical Transport Networks (OTN)-electrical layer, as the scope to an Optical Transport Networks (OTN)-electrical layer, as the scope
specified by [RFC7062] and [RFC7138]. Furthermore, it is not a specified by [RFC7062] and [RFC7138]. Furthermore, it is not a
stand-alone model, but augmenting from the TE topology YANG model stand-alone model, but augmenting from the TE topology YANG model
defined in [I-D.ietf-teas-yang-te-topo]. defined in [I-D.ietf-teas-yang-te-topo]. Following TE topology YANG
model, the YANG model defined in this document is interface
independent. The applicability of models to interfaces is described
in [I-D.zhang-teas-actn-yang].
Optical network technologies, including fixed Dense Wavelength Optical network technologies, including fixed Dense Wavelength
Switched Optical Network (WSON) and flexible optical networks Switched Optical Network (WSON) and flexible optical networks
(a.k.a., flexi-grid networks), are covered in (a.k.a., flexi-grid networks), are covered in
[I-D.ietf-ccamp-wson-yang] and [I-D.vergara-ccamp-flexigrid-yang], [I-D.ietf-ccamp-wson-yang] and [I-D.vergara-ccamp-flexigrid-yang],
respectively. respectively.
2. Terminology and Notations 2. Terminology and Notations
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
skipping to change at page 5, line 4 skipping to change at page 4, line 17
o Parentheses enclose choice and case nodes, and case nodes are also o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":"). marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
3. YANG Data Model for OTN Topology 3. YANG Data Model for OTN Topology
3.1. the YANG Tree 3.1. the YANG Tree
module: ietf-otn-topology module: ietf-otn-topology
augment /nd:networks/nd:network/nd:network-types/tet:te-topology: augment /nw:networks/nw:network/nw:network-types/tet:te-topology:
+--rw otn-topology! +--rw otn-topology!
augment /nd:networks/nd:network: augment /nw:networks/nw:network/nt:link/tet:te
+--rw name? string /tet:te-link-attributes:
augment /nd:networks/nd:network/nd:node:
+--rw name? string
augment /nd:networks/nd:network/lnk:link/tet:te/tet:config:
+--rw available-odu-info* [priority] +--rw available-odu-info* [priority]
| +--rw priority uint8 | +--rw priority uint8
| +--rw odulist* [odu-type] | +--rw odulist* [odu-type]
| | +--rw odu-type identityref | | +--rw odu-type identityref
| | +--rw number? uint16 | | +--rw number? uint16
| | +--rw tpn-range? string | | +--rw tpn-range? string
| +--rw ts-range? string | +--rw ts-range? string
+--rw tsg? identityref +--rw tsg? identityref
+--rw distance? uint32 +--rw distance? uint32
augment /nd:networks/nd:network/lnk:link/tet:te/tet:state: augment /nw:networks/nw:network/nw:node/nt:termination-point
+--ro available-odu-info* [priority] /tet:te:
| +--ro priority uint8
| +--ro odulist* [odu-type]
| | +--ro odu-type identityref
| | +--ro number? uint16
| | +--ro tpn-range? string
| +--ro ts-range? string
+--ro tsg? identityref
+--ro distance? uint32
augment /nd:networks/nd:network/nd:node/lnk:termination-point
/tet:te/tet:config:
+--rw supported-payload-types* [index] +--rw supported-payload-types* [index]
+--rw index uint16 +--rw index uint16
+--rw payload-type? string +--rw payload-type? string
augment /nd:networks/nd:network/nd:node/lnk:termination-point
/tet:te/tet:state:
+--ro supported-payload-types* [index]
+--ro index uint16
+--ro payload-type? string
3.2. Explanation of the OTN Topology Data Model 3.2. Explanation of the OTN Topology Data Model
As can be seen, from the data tree shown in Section 3.1, the YANG As can be seen, from the data tree shown in Section 3.1, the YANG
module presented in this document augments from a more generic module presented in this document augments from a more generic
Traffic Engineered (TE) network topology data model, i.e., the ietf- Traffic Engineered (TE) network topology data model, i.e., the ietf-
te-topology.yang as specified in [I-D.ietf-teas-yang-te-topo]. The te-topology.yang as specified in [I-D.ietf-teas-yang-te-topo]. The
entities and their attributes, such as node, termination points and entities and their attributes, such as node, termination points and
links, are still applicable for describing an OTN topology and the links, are still applicable for describing an OTN topology and the
model presented in this document only specifies with technology- model presented in this document only specifies with technology-
skipping to change at page 6, line 27 skipping to change at page 5, line 23
per priority level. For example, for a ODU3 link, it may advertise per priority level. For example, for a ODU3 link, it may advertise
32*ODU0, 16*ODU1, 4*ODU2 available, assuming only a single priority 32*ODU0, 16*ODU1, 4*ODU2 available, assuming only a single priority
level is supported. If one of ODU2 resource is taken to establish a level is supported. If one of ODU2 resource is taken to establish a
ODU path, then the availability of this ODU link is updated as ODU path, then the availability of this ODU link is updated as
24*ODU0, 12*ODU1, 3*ODU2 available. If there are equipment hardware 24*ODU0, 12*ODU1, 3*ODU2 available. If there are equipment hardware
limitations, then a subset of potential ODU type SHALL be advertised. limitations, then a subset of potential ODU type SHALL be advertised.
For instance, an ODU3 link may only support 4*ODU2. For instance, an ODU3 link may only support 4*ODU2.
3.3. The YANG Code 3.3. The YANG Code
<CODE BEGINS> file "ietf-otn-topology@2017-09-14.yang" <CODE BEGINS> file "ietf-otn-topology@2017-10-30.yang"
module ietf-otn-topology { module ietf-otn-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-otn-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-otn-topology";
prefix "otntopo"; prefix "otntopo";
import ietf-network { import ietf-network {
prefix "nd"; prefix "nw";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "lnk"; prefix "nt";
} }
import ietf-te-topology { import ietf-te-topology {
prefix "tet"; prefix "tet";
revision-date 2017-06-10;
} }
import ietf-transport-types { import ietf-otn-types {
prefix "tran-types"; prefix "otn-types";
} }
organization organization
"IETF CCAMP Working Group"; "IETF CCAMP Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/ccamp/> "WG Web: <http://tools.ietf.org/wg/ccamp/>
WG List: <mailto:ccamp@ietf.org> WG List: <mailto:ccamp@ietf.org>
Editor: Haomian Zheng Editor: Haomian Zheng
<mailto:zhenghaomian@huawei.com> <mailto:zhenghaomian@huawei.com>
Editor: Zheyu Fan Editor: Zheyu Fan
skipping to change at page 7, line 35 skipping to change at page 6, line 31
Editor: Yunbin Xu Editor: Yunbin Xu
<mailto:xuyunbin@ritt.cn> <mailto:xuyunbin@ritt.cn>
Editor: Lei Wang Editor: Lei Wang
<mailto:wangleiyj@chinamobile.com> <mailto:wangleiyj@chinamobile.com>
Editor: Oscar Gonzalez de Dios Editor: Oscar Gonzalez de Dios
<mailto:oscar.gonzalezdedios@telefonica.com>"; <mailto:oscar.gonzalezdedios@telefonica.com>";
description description
"This module defines a protocol independent Layer 1/ODU "This module defines a protocol independent Layer 1/ODU topology
topology data model."; data model.";
revision 2017-09-14 { revision 2017-10-30 {
description description
"Revision 0.4"; "Revision 0.5";
reference reference
"draft-ietf-ccamp-otn-topo-yang-01.txt"; "draft-ietf-ccamp-otn-topo-yang-02.txt";
}
/*
* Groupings
*/
grouping otn-topology-type {
container otn-topology {
presence "indicates a topology type of Optical Transport
Network (OTN)-electrical layer.";
description "otn topology type";
}
description "otn-topology-type";
}
grouping otn-topology-attributes {
leaf name {
type string;
description "the topology name";
}
description "name attribute for otn topology";
}
grouping otn-node-attributes {
description "otn-node-attributes";
leaf name {
type string;
description "a name for this node.";
}
} }
/*
* Groupings
*/
grouping otn-link-attributes { grouping otn-link-attributes {
description "link attributes for OTN"; description "link attributes for OTN";
list available-odu-info { list available-odu-info {
key "priority"; key "priority";
max-elements "8"; max-elements "8";
description "List of ODU type and number on this link"; description "List of ODU type and number on this link";
leaf priority { leaf priority {
type uint8 { type uint8 {
range "0..7"; range "0..7";
} }
description "priority"; description "priority";
} }
list odulist { list odulist {
key "odu-type"; key "odu-type";
description description
"the list of available ODUs per priority level"; "the list of available ODUs per priority level";
leaf odu-type { leaf odu-type {
type identityref { type identityref {
base tran-types:tributary-protocol-type; base otn-types:tributary-protocol-type;
} }
description "the type of ODU"; description "the type of ODU";
} }
leaf number { leaf number {
type uint16; type uint16;
description "the number of odu type supported"; description "the number of odu type supported";
} }
leaf tpn-range { leaf tpn-range {
type string { type string {
pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?"
+ "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)";
} }
description description
"A list of available tributary port number range "A list of available tributary port number range
between 1 and 9999. between 1 and 9999.
For example 1-20,25,50-1000"; For example 1-20,25,50-1000";
reference reference "RFC 7139: GMPLS Signaling Extensions for Control
"RFC 7139: GMPLS Signaling Extensions for Control of of Evolving G.709 Optical Transport Networks";
Evolving G.709 Optical Transport Networks";
} }
} }
leaf ts-range { leaf ts-range {
type string { type string {
pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?" pattern "([1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?"
+ "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)"; + "(,[1-9][0-9]{0,3}(-[1-9][0-9]{0,3})?)*)";
} }
description description
"A list of available tributary slot range "A list of available tributary slot range
between 1 and 9999. between 1 and 9999.
For example 1-20,25,50-1000"; For example 1-20,25,50-1000";
reference reference "RFC 7139: GMPLS Signaling Extensions for Control
"RFC 7139: GMPLS Signaling Extensions for Control of of Evolving G.709 Optical Transport Networks";
Evolving G.709 Optical Transport Networks";
} }
} }
leaf tsg { leaf tsg {
type identityref { type identityref {
base tran-types:tributary-slot-granularity; base otn-types:tributary-slot-granularity;
} }
description "Tributary slot granularity"; description "Tributary slot granularity.";
reference reference
"RFC 7138: Traffic Engineering Extensions to OSPF for GMPLS "G.709/Y.1331, February 2016: Interfaces for the
Control of Evolving G.709 Optical Transport Networks"; Optical Transport Network (OTN)";
} }
leaf distance { leaf distance {
type uint32; type uint32;
description "distance in the unit of kilometers"; description "distance in the unit of kilometers";
} }
} }
grouping otn-tp-attributes { grouping otn-tp-attributes {
description "tp attributes for OTN"; description "tp attributes for OTN";
list supported-payload-types { list supported-payload-types {
skipping to change at page 10, line 20 skipping to change at page 8, line 38
leaf payload-type { leaf payload-type {
type string; type string;
description "the payload type supported by this client tp"; description "the payload type supported by this client tp";
reference reference
"http://www.iana.org/assignments/gmpls-sig-parameters "http://www.iana.org/assignments/gmpls-sig-parameters
/gmpls-sig-parameters.xhtml"; /gmpls-sig-parameters.xhtml";
} }
} }
} }
/* /*
* Data nodes * Data nodes
*/ */
augment "/nd:networks/nd:network/nd:network-types/" augment "/nw:networks/nw:network/nw:network-types/"
+ "tet:te-topology" { + "tet:te-topology" {
uses otn-topology-type; container otn-topology {
description "augment network types to include otn newtork"; presence "indicates a topology type of Optical Transport
} Network (OTN)-electrical layer.";
description "otn topology type";
augment "/nd:networks/nd:network" {
when "nd:network-types/tet:te-topology/otntopo:otn-topology" {
description "Augment only for otn network";
} }
uses otn-topology-attributes; description "augment network types to include otn newtork";
description "Augment network configuration";
} }
augment "/nd:networks/nd:network/nd:node" { augment "/nw:networks/nw:network/nt:link/tet:te/"
when "../nd:network-types/tet:te-topology/otntopo:otn-topology" { + "tet:te-link-attributes" {
description "Augment only for otn network";
}
description "Augment node configuration";
uses otn-node-attributes;
}
augment "/nd:networks/nd:network/lnk:link/tet:te/tet:config" { when "../../../nw:network-types/tet:te-topology/"
when "../../../nd:network-types/tet:te-topology/"
+ "otntopo:otn-topology" { + "otntopo:otn-topology" {
description "Augment only for otn network."; description "Augment only for otn network.";
} }
description "Augment link configuration"; description "Augment link configuration";
uses otn-link-attributes; uses otn-link-attributes;
}
augment "/nd:networks/nd:network/lnk:link/tet:te/tet:state" {
when "../../../nd:network-types/tet:te-topology/"
+ "otntopo:otn-topology" {
description "Augment only for otn network.";
}
description "Augment link state";
uses otn-link-attributes;
} }
augment "/nd:networks/nd:network/nd:node/" augment "/nw:networks/nw:network/nw:node/nt:termination-point/"
+ "lnk:termination-point/tet:te/tet:config" { + "tet:te" {
when "../../../../nd:network-types/tet:te-topology/" when "../../../nw:network-types/tet:te-topology/"
+ "otntopo:otn-topology" { + "otntopo:otn-topology" {
description "Augment only for otn network"; description "Augment only for otn network";
} }
description "OTN TP attributes config in ODU topology."; description "OTN TP attributes config in ODU topology.";
uses otn-tp-attributes; uses otn-tp-attributes;
} }
augment "/nd:networks/nd:network/nd:node/"
+ "lnk:termination-point/tet:te/tet:state" {
when "../../../../nd:network-types/tet:te-topology/"
+ "otntopo:otn-topology" {
description "Augment only for otn network";
}
description "OTN TP attributes state in ODU topology.";
uses otn-tp-attributes;
}
} }
<CODE ENDS> <CODE ENDS>
4. IANA Considerations 4. IANA Considerations
TBD. TBD.
5. Manageability Considerations 5. Manageability Considerations
skipping to change at page 13, line 20 skipping to change at page 11, line 7
9.1. Normative References 9.1. Normative References
[I-D.ietf-ccamp-otn-tunnel-model] [I-D.ietf-ccamp-otn-tunnel-model]
zhenghaomian@huawei.com, z., Fan, Z., Sharma, A., Rao, R., zhenghaomian@huawei.com, z., Fan, Z., Sharma, A., Rao, R.,
Belotti, S., Lopezalvarez, V., and Y. Li, "OTN Tunnel YANG Belotti, S., Lopezalvarez, V., and Y. Li, "OTN Tunnel YANG
Model", draft-ietf-ccamp-otn-tunnel-model-00 (work in Model", draft-ietf-ccamp-otn-tunnel-model-00 (work in
progress), July 2017. progress), July 2017.
[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 TE Topologies", draft-ietf- O. Dios, "YANG Data Model for Traffic Engineering (TE)
teas-yang-te-topo-12 (work in progress), July 2017. Topologies", draft-ietf-teas-yang-te-topo-13 (work in
progress), October 2017.
[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>.
[RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and [RFC7138] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and
J. Drake, "Traffic Engineering Extensions to OSPF for J. Drake, "Traffic Engineering Extensions to OSPF for
GMPLS Control of Evolving G.709 Optical Transport GMPLS Control of Evolving G.709 Optical Transport
Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014, Networks", RFC 7138, DOI 10.17487/RFC7138, March 2014,
skipping to change at page 13, line 47 skipping to change at page 11, line 35
[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>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-ccamp-wson-yang] [I-D.ietf-ccamp-wson-yang]
Lee, Y., Dhody, D., Zhang, X., Guo, A., Lopezalvarez, V., Lee, Y., Dhody, D., Zhang, X., Guo, A., Lopezalvarez, V.,
King, D., Yoon, B., and R. Vilata, "A Yang Data Model for King, D., Yoon, B., and R. Vilata, "A Yang Data Model for
WSON Optical Networks", draft-ietf-ccamp-wson-yang-07 WSON Optical Networks", draft-ietf-ccamp-wson-yang-08
(work in progress), July 2017. (work in progress), October 2017.
[I-D.ietf-netmod-yang-tree-diagrams] [I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-01 (work in progress), June ietf-netmod-yang-tree-diagrams-02 (work in progress),
2017. October 2017.
[I-D.vergara-ccamp-flexigrid-yang] [I-D.vergara-ccamp-flexigrid-yang]
Madrid, U., Perdices, D., Lopezalvarez, V., Dios, O., Madrid, U., Perdices, D., Lopezalvarez, V., Dios, O.,
King, D., Lee, Y., and G. Galimberti, "YANG data model for King, D., Lee, Y., and G. Galimberti, "YANG data model for
Flexi-Grid Optical Networks", draft-vergara-ccamp- Flexi-Grid Optical Networks", draft-vergara-ccamp-
flexigrid-yang-05 (work in progress), July 2017. flexigrid-yang-05 (work in progress), July 2017.
[I-D.zhang-teas-actn-yang]
Lee, Y., zhenghaomian@huawei.com, z., Yoon, B., Dios, O.,
Shin, J., and S. Belotti, "Applicability of YANG models
for Abstraction and Control of Traffic Engineered
Networks", draft-zhang-teas-actn-yang-05 (work in
progress), June 2017.
[RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. [RFC7062] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D.
Ceccarelli, "Framework for GMPLS and PCE Control of G.709 Ceccarelli, "Framework for GMPLS and PCE Control of G.709
Optical Transport Networks", RFC 7062, Optical Transport Networks", RFC 7062,
DOI 10.17487/RFC7062, November 2013, DOI 10.17487/RFC7062, November 2013,
<https://www.rfc-editor.org/info/rfc7062>. <https://www.rfc-editor.org/info/rfc7062>.
Authors' Addresses Authors' Addresses
Haomian Zheng Haomian Zheng
Huawei Technologies Huawei Technologies
 End of changes. 40 change blocks. 
141 lines changed or deleted 78 lines changed or added

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