draft-ietf-ccamp-wson-yang-16.txt   draft-ietf-ccamp-wson-yang-17.txt 
CCAMP Working Group Y. Lee (Editor) CCAMP Working Group Y. Lee (Editor)
Internet Draft D. Dhody Internet Draft D. Dhody
Intended status: Standard Track A. Guo Intended status: Standard Track A. Guo
Expires: May 20, 2019 Huawei Expires: May 27, 2019 Huawei
V. Lopez V. Lopez
Telefonica Telefonica
D. King D. King
U. of Lancaster U. of Lancaster
November 19, 2018 November 26, 2018
A YANG Data Model for WSON Optical Networks A YANG Data Model for WSON Optical Networks
draft-ietf-ccamp-wson-yang-16 draft-ietf-ccamp-wson-yang-17
Abstract Abstract
This document provides a YANG data model for the routing and This document provides a YANG data model for the routing and
wavelength assignment (RWA) TE topology in wavelength switched wavelength assignment (RWA) TE topology in wavelength switched
optical networks (WSONs). optical networks (WSONs). The YANG data model defined in this
document conforms to the Network Management Datastore Architecture
defined in RFC 8342.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 46 skipping to change at page 1, line 48
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on May 20, 2019. This Internet-Draft will expire on May 27, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction...................................................2 1. Introduction...................................................2
1.1. Terminology...............................................3 1.1. Requirements Language.....................................3
1.2. Tree diagram..............................................3 1.2. Terminology...............................................3
1.3. Prefixes in Data Node Names...............................3 1.3. Tree diagram..............................................4
1.4. Prefixes in Data Node Names...............................4
2. YANG Model (Tree Structure)....................................4 2. YANG Model (Tree Structure)....................................4
3. IETF-WSON-Topology YANG Model.................................21 3. IETF-WSON-Topology YANG Model.................................22
4. IETF-Layer0-Types YANG Model..................................58 4. IETF-Layer0-Types YANG Model..................................58
5. Security Considerations.......................................70 5. Security Considerations.......................................71
6. IANA Considerations...........................................71 6. IANA Considerations...........................................72
7. Acknowledgments...............................................72 7. Acknowledgments...............................................73
8. References....................................................73 8. References....................................................74
8.1. Normative References.....................................73 8.1. Normative References.....................................74
8.2. Informative References...................................73 8.2. Informative References...................................74
9. Contributors..................................................74 9. Contributors..................................................76
Authors' Addresses...............................................74 Authors' Addresses...............................................76
1. Introduction 1. Introduction
This document provides a YANG data model for the routing and This document provides a YANG data model for the routing and
wavelength assignment (RWA) Traffic Engineering (TE) topology in wavelength assignment (RWA) Traffic Engineering (TE) topology in
wavelength switched optical networks (WSONs). The YANG model wavelength switched optical networks (WSONs). The YANG model
described in this document is a WSON technology-specific YANG model described in this document is a WSON technology-specific YANG model
based on the information model developed in [RFC7446] and the two based on the information model developed in [RFC7446] and the two
encoding documents [RFC7581] and [RFC7579] that developed protocol encoding documents [RFC7581] and [RFC7579] that developed protocol
independent encodings based on [RFC7446]. independent encodings based on [RFC7446].
This document augments the generic TE topology draft [TE-TOPO]. This document augments the generic TE topology draft [TE-TOPO].
What is not in scope of this document is both impairment-aware WSON What is not in scope of this document is both impairment-aware WSON
and flex-grid. and flex-grid.
This document defines two YANG models: ietf-wson-topology (Section This document defines two YANG models: ietf-wson-topology (Section
3) and ietf-layer0-types (Section 4). 3) and ietf-layer0-types (Section 4).
1.1. Terminology There are multiple applications for the yang data model defined in
this document. For example, nodes within the network can use the
data model to capture their understanding of the overall WSON
topology and expose it to a controller. A controller can further
propagate the topology to other controllers. The YANG model is used
by NETCONF [RFC6020], [RFC8341] or a RESTCONF [RFC8040] protocol.
The YANG data model defined in this document conforms to the Network
Management Datastore Architecture [RFC8342].
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
1.2. Terminology
Refer to [RFC7446] and [RFC7581] for the key terms used in this Refer to [RFC7446] and [RFC7581] for the key terms used in this
document. document.
The following terms are defined in [RFC7950] and are not redefined The following terms are defined in [RFC7950] and are not redefined
here: here:
o client o client
o server o server
skipping to change at page 3, line 39 skipping to change at page 4, line 12
The following terms are defined in [RFC6241] and are not redefined The following terms are defined in [RFC6241] and are not redefined
here: here:
o configuration data o configuration data
o state data o state data
The terminology for describing YANG data models is found in The terminology for describing YANG data models is found in
[RFC7950]. [RFC7950].
1.2. Tree diagram 1.3. Tree diagram
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
chapter 2 of this this document. The meaning of the symbols in chapter 2 of this this document. The meaning of the symbols in
these diagrams is defined in [RFC8340]. these diagrams is defined in [RFC8340].
1.3. Prefixes in Data Node Names 1.4. Prefixes in Data Node Names
In this document, names of data nodes and other data model objects In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1. corresponding YANG imported modules, as shown in Table 1.
+-------------+-------------------------+-----------------+ +-------------+-------------------------+-----------------+
| Prefix | YANG module | Reference | | Prefix | YANG module | Reference |
+-------------+-------------------------+-----------------+ +-------------+-------------------------+-----------------+
| layer0-type | ietf-layer0-types | [RFCXXXX] | | layer0-type | ietf-layer0-types | [RFCXXXX] |
| wson | ietf-wson-topology | [RFCXXXX] | | wson | ietf-wson-topology | [RFCXXXX] |
skipping to change at page 21, line 32 skipping to change at page 22, line 7
label/tet:technology: label/tet:technology:
+-:(wson) +-:(wson)
+-rw (grid-type)? +-rw (grid-type)?
+-:(dwdm) +-:(dwdm)
| +-rw channel-freq? frequency-thz | +-rw channel-freq? frequency-thz
+-:(cwdm) +-:(cwdm)
+-rw channel-wavelength? uint32 +-rw channel-wavelength? uint32
3. IETF-WSON-Topology YANG Model 3. IETF-WSON-Topology YANG Model
<CODE BEGINS> file "ietf-wson-topology@2018-11-19.yang" <CODE BEGINS> file "ietf-wson-topology@2018-11-26.yang"
module ietf-wson-topology { module ietf-wson-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-wson-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-wson-topology";
prefix "wson"; prefix "wson";
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "nt"; prefix "nt";
reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-te-topology { import ietf-te-topology {
prefix "tet"; prefix "tet";
reference
"draft-ietf-teas-yang-te-topo-18: YANG Data Model for
Traffic Engineering (TE) Topologies";
} }
import ietf-layer0-types { import ietf-layer0-types {
prefix "layer0-types"; prefix "layer0-types";
reference
"draft-ietf-teas-yang-te-types-01: Traffic Engineering
Common YANG Types";
} }
organization organization
"IETF CCAMP Working Group"; "IETF CCAMP Working Group";
contact contact
"Editor: Young Lee <leeyoung@huawei.com> "Editor: Young Lee <leeyoung@huawei.com>
Editor: Aihua Guo <aihuaguo@huawei.com>"; Editor: Aihua Guo <aihuaguo@huawei.com>";
description description
skipping to change at page 22, line 48 skipping to change at page 23, line 35
Copyright (c) 2018 IETF Trust and the persons identified Copyright (c) 2018 IETF Trust and the persons identified
as authors of the code. All rights reserved. as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Simplified subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."; (http://trustee.ietf.org/license-info).";
revision 2018-11-19 { revision 2018-11-26 {
description description
"Initial Version"; "Initial Version";
reference reference
"RFC XXX: A YANG Data Model for WSON (Wavelenghth Switched "RFC XXX: A YANG Data Model for WSON (Wavelenghth Switched
Optical Networks)"; Optical Networks)";
} }
/* /*
* Groupings * Groupings
skipping to change at page 24, line 50 skipping to change at page 25, line 35
leaf-list supported-termination-types { leaf-list supported-termination-types {
type identityref { type identityref {
base layer0-types:term-type; base layer0-types:term-type;
} }
description description
"List of all supported termination types by this TTP"; "List of all supported termination types by this TTP";
} }
leaf supports-bit-stuffing { leaf supports-bit-stuffing {
type boolean; type boolean;
description description
"Indicates whether bit stuffing is supported by this TTP"; "Indicates whether bit stuffing is supported by this TTP";
} }
leaf is-tunable { leaf is-tunable {
type boolean; type boolean;
description description
"Indicates if the TTP, or transponder, is tunable. Tunable "Indicates if the TTP, or transponder, is tunable. Tunable
transponders are assumed to be fully tunable to any of the transponders are assumed to be fully tunable to any of the
96 channels within DWDM C-band"; 96 channels within DWDM C-band";
} }
leaf max-subcarrier-channel-num { leaf max-subcarrier-channel-num {
type uint8 { type uint8 {
range "1..max"; range "1..max";
} }
default 1; default 1;
description description
"Indicates the maximum number of subcarrier channels for "Indicates the maximum number of subcarrier channels for
super-channel transponders. When the value equals 1 it super-channel transponders. When the value equals 1 it
represents regular single-channel transponder"; represents regular single-channel transponder";
} }
} }
/* /*
* Data nodes * Data nodes
*/ */
augment "/nw:networks/nw:network/nw:network-types" augment "/nw:networks/nw:network/nw:network-types"
skipping to change at page 58, line 43 skipping to change at page 59, line 30
Copyright (c) 2018 IETF Trust and the persons identified Copyright (c) 2018 IETF Trust and the persons identified
as authors of the code. All rights reserved. as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Simplified subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."; (http://trustee.ietf.org/license-info).";
revision "2018-11-19" { revision "2018-11-26" {
description description
"Initial Version"; "Initial Version";
reference "TBD"; reference
"RFC XXX: A YANG Data Model for WSON (Wavelenghth Switched
Optical Networks)";
} }
typedef operational-mode { typedef operational-mode {
type string; type string;
description description
"Vendor-specific mode that guarantees interoperability. "Vendor-specific mode that guarantees interoperability.
It must be an string with the following format: It must be an string with the following format:
B-DScW-ytz(v) where all these attributes are conformant B-DScW-ytz(v) where all these attributes are conformant
to the ITU-T recomendation"; to the ITU-T recomendation";
reference "ITU-T G.698.2 (11/2009) Section 5.3"; reference "ITU-T G.698.2 (11/2009) Section 5.3";
skipping to change at page 65, line 42 skipping to change at page 66, line 31
description description
"Generic label for WSON links"; "Generic label for WSON links";
choice grid-type { choice grid-type {
description description
"Label for DWDM or CWDM grid"; "Label for DWDM or CWDM grid";
case dwdm { case dwdm {
leaf channel-freq { leaf channel-freq {
type frequency-thz; type frequency-thz;
description description
"The DWDM fixed-grid channel frequency in THz, "The DWDM fixed-grid channel frequency in THz,
e.g., 193.12500"; e.g., 193.12500";
reference reference
"RFC6205"; "RFC6205";
} }
} }
case cwdm { case cwdm {
leaf channel-wavelength { leaf channel-wavelength {
type uint32; type uint32;
units nm; units nm;
description description
"The CWDM wavelength in nanometer, e.g., 1511"; "The CWDM wavelength in nanometer, e.g., 1511";
skipping to change at page 66, line 24 skipping to change at page 67, line 11
"Generic label for WSON paths"; "Generic label for WSON paths";
choice grid-type { choice grid-type {
description description
"Label for DWDM or CWDM grid"; "Label for DWDM or CWDM grid";
case dwdm { case dwdm {
choice single-or-super-channel { choice single-or-super-channel {
description "single or super channel"; description "single or super channel";
case single { case single {
leaf channel-freq { leaf channel-freq {
type frequency-thz; type frequency-thz;
description description
"The DWDM fixed-grid channel frequency in THz, "The DWDM fixed-grid channel frequency in THz,
e.g., 193.12500"; e.g., 193.12500";
} }
} }
case super { case super {
leaf-list subcarrier-channels { leaf-list subcarrier-channels {
type frequency-thz; type frequency-thz;
description description
"List of subcarrier channels for super channel"; "List of subcarrier channels for super channel";
} }
} }
} }
} }
case cwdm { case cwdm {
leaf channel-wavelength { leaf channel-wavelength {
type uint32; type uint32;
units nm; units nm;
description description
"The CWDM wavelength in nanometer, e.g., 1511"; "The CWDM wavelength in nanometer, e.g., 1511";
skipping to change at page 69, line 17 skipping to change at page 70, line 4
} }
leaf slot-width { leaf slot-width {
type frequency-ghz; type frequency-ghz;
description description
"Flex-grid The DWDM slot width in GHz, e.g., 50, 100, 150"; "Flex-grid The DWDM slot width in GHz, e.g., 50, 100, 150";
reference reference
"RFC7698"; "RFC7698";
} }
} }
grouping flex-grid-path-label { grouping flex-grid-path-label {
description "Flex-grid path label."; description "Flex-grid path label.";
choice single-or-super-channel { choice single-or-super-channel {
description "single of super channel"; description "single of super channel";
case single { case single {
uses flex-grid-channel; uses flex-grid-channel;
} }
case super { case super {
list subcarrier-channels { list subcarrier-channels {
key central-frequency; key central-frequency;
uses flex-grid-channel; uses flex-grid-channel;
description description
"List of subcarrier channels for flex-grid "List of subcarrier channels for flex-grid
super channel"; super channel";
}
} }
} }
}
} }
grouping flex-grid-label-restriction { grouping flex-grid-label-restriction {
description description
"Flex Grid-specific label restriction"; "Flex Grid-specific label restriction";
uses layer0-label-restriction; uses layer0-label-restriction;
container flex-grid { container flex-grid {
description "flex-grid definition"; description "flex-grid definition";
leaf nominal-central-frequency-granularity { leaf nominal-central-frequency-granularity {
type frequency-ghz; type frequency-ghz;
default 6.25; default 6.25;
description description
"It is the spacing between allowed nominal central "It is the spacing between allowed nominal central
frequencies and it is set to 6.25 GHz"; frequencies and it is set to 6.25 GHz";
reference reference
"RFC7698"; "RFC7698";
} }
leaf slot-width-granularity { leaf slot-width-granularity {
type frequency-ghz; type frequency-ghz;
default 12.5; default 12.5;
description description
"Minimum space between slot widths"; "Minimum space between slot widths";
reference reference
"RFC7698"; "RFC7698";
} }
} }
} }
grouping flex-grid-label-step { grouping flex-grid-label-step {
description "Label step information for flex grid"; description "Label step information for flex grid";
leaf flex { leaf flex {
type identityref { type identityref {
base dwdm-ch-spc-type; base dwdm-ch-spc-type;
} }
skipping to change at page 70, line 33 skipping to change at page 71, line 21
granularity (GHz), e.g., 6.25 GHz"; granularity (GHz), e.g., 6.25 GHz";
reference reference
"RFC7698"; "RFC7698";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
5. Security Considerations 5. Security Considerations
The configuration, state, and action data defined in this document The YANG module specified in this document defines a schema for data
are designed to be accessed via a management protocol with a secure that is designed to be accessed via network management protocols
transport layer, such as NETCONF [RFC6241]. The NETCONF access such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF
control model [RFC6536] provides the means to restrict access for layer is the secure transport layer, and the mandatory-to-implement
particular NETCONF users to a preconfigured subset of all available secure transport is Secure Shell (SSH) [RFC6242]. The lowest
NETCONF protocol operations and content. RESTCONF layer is HTTPS, and the mandatory-to-implement secure
transport is TLS [RFC8446].
The NETCONF access control model [RFC6536] provides the means to
restrict access for particular NETCONF users to a preconfigured
subset of all available NETCONF protocol operations and content. The
NETCONF Protocol over Secure Shell (SSH) [RFC6242] describes a
method for invoking and running NETCONF within a Secure Shell (SSH)
session as an SSH subsystem. The Network Configuration Access
Control Model (NACM) [RFC8341] provides the means to restrict access
for particular NETCONF or RESTCONF users to a preconfigured subset
of all available NETCONF or RESTCONF protocol operations and
content.
A number of configuration data nodes defined in this document are A number of configuration data nodes defined in this document are
writable/deletable (i.e., "config true") These data nodes may be writable/deletable (i.e., "config true"). These data nodes may be
considered sensitive or vulnerable in some network environments. considered sensitive or vulnerable in some network environments.
There are a number of data nodes defined in this YANG module that There are a number of data nodes defined in this YANG module that
are writable/creatable/deletable (i.e., config true, which is the are writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or default). These data nodes may be considered sensitive or
vulnerable in some network environments. Write operations (e.g., vulnerable in some network environments. Write operations (e.g.,
edit-config) to these data nodes without proper protection can have edit-config) to these data nodes without proper protection can have
a negative effect on network operations. These are the subtrees and a negative effect on network operations. These are the subtrees and
data nodes and their sensitivity/vulnerability: data nodes and their sensitivity/vulnerability:
skipping to change at page 73, line 9 skipping to change at page 74, line 9
-------------------------------------------------------------------- --------------------------------------------------------------------
7. Acknowledgments 7. Acknowledgments
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010.
[RFC6241] R. Enns, Ed., M. Bjorklund, Ed., J. Schoenwaelder, Ed.,
"Network Configuration Protocol (NETCONF)", RFC 6241, June
2011.
[RFC6242] M. Wasserman, "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, June 2011.
[RFC6536] A. Bierman, M. Bjorklund, "Network Configuration Protocol
(NETCONF) Access Control Model", RFC 6536, March 2012.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, August 2016.
[RFC8040] A. Bierman, M. Bjorklund, K. Watsen, "RESTCONF Protocol",
RFC 8040, January 2017.
[RFC8341] A. Bierman, M. Bjorklund, "Network Configuration Access
Control Model", RFC 8341, March 2018.
[RFC8446] E. Rescorla, "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC8446, August 2018.
[TE-TOPO] X. Liu, et al., "YANG Data Model for TE Topologies", work [TE-TOPO] X. Liu, et al., "YANG Data Model for TE Topologies", work
in progress: draft-ietf-teas-yang-te-topo. in progress: draft-ietf-teas-yang-te-topo.
8.2. Informative References 8.2. Informative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI
10.17487/RFC2119, March 1997, <https://www.rfc-
editor.org/info/rfc2119>.
[RFC3688] M. Mealling, "The IETF XML Registry", RFC 3688, January [RFC3688] M. Mealling, "The IETF XML Registry", RFC 3688, January
2004. 2004.
[RFC7446] Y. Lee, G. Bernstein, D. Li, W. Imajuku, "Routing and [RFC6163] Y. Lee, Ed. G. Berstein, Ed., W. Imajuku, "Framework for
GMPLS and Path Computation Element (PCE) Control of
Wavelength Switched Optical Networks (WSONs)", RFC 6163,
April 2011.
[RFC6205] T. Otani, Ed., D. Li, Ed., "Generalized Labels for Lambda-
Switch-Capable (LSC) Label Switching Routers", RFC 6205,
March 2011.
[RFC7446] Y. Lee, G. Bernstein, D. Li, W. Imajuku, "Routing and
Wavelength Assignment Information Model for Wavelength Wavelength Assignment Information Model for Wavelength
Switched Optical Networks", RFC 7446, Feburary 2015. Switched Optical Networks", RFC 7446, Feburary 2015.
[RFC7579] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General [RFC7579] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General Network
Network Element Constraint Encoding for GMPLS Controlled Element Constraint Encoding for GMPLS Controlled
Networks", RFC 7579, June 2015. Networks", RFC 7579, June 2015.
[RFC7581] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and [RFC7581] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and
Wavelength Assignment Information Encoding for Wavelength Wavelength Assignment Information Encoding for Wavelength
Switched Optical Networks", RFC 7581, June 2015. Switched Optical Networks", RFC 7581, June 2015.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7698] O. Gonzalez de Dios, Ed., R. Casellas, Ed., "Framework and
RFC 7950, August 2016. Requirements for GMPLS-Based Control of Flexi-Grid Dense
Wavelength Division Multiplexing (DWDM) Networks", RFC
7698, November 2015.
[RFC8340] M. Bjorklund and L. Berger, Ed., "YANG Tree Diagrams", RFC [RFC8340] M. Bjorklund and L. Berger, Ed., "YANG Tree Diagrams", RFC
8340, March 2018. 8340, March 2018.
[RFC8345] A. Clemm, et al, "A YANG Data Model for Network [RFC8342] M. Bjorklund, J. Schoenwaelder, P. Shafer, K. Watsen, R.
Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, March 2018.
[RFC8345] A. Clemm, et al, "A YANG Data Model for Network
Topologies", RFC 8345, March 2018. Topologies", RFC 8345, March 2018.
9. Contributors 9. Contributors
Authors' Addresses Authors' Addresses
Young Lee (ed.) Young Lee (ed.)
Huawei Technologies Huawei Technologies
5340 Legacy Drive, Building 3 5700 Tennyson Parkway, Suite 600
Plano, TX 75023 Plano, TX 75024
USA USA
Phone: (469) 277-5838
Email: leeyoung@huawei.com Email: leeyoung@huawei.com
Dhruv Dhody Dhruv Dhody
Huawei Technologies India Pvt. Ltd, Huawei Technologies
Near EPIP Industrial Area, Kundalahalli Village, Whitefield, Divyashree Techno Park, Whitefield
Bangalore - 560 037 [H1-2A-245] Bangalore, Karnataka 560066
India
Email: dhruv.dhody@huawei.com EMail: dhruv.ietf@gmail.com
Aihua Guo Aihua Guo
Huawei Technologies Huawei Technologies
Email: aihuaguo@huawei.com Email: aihuaguo@huawei.com
Victor Lopez Victor Lopez
Telefonica Telefonica
Email: victor.lopezalvarez@telefonica.com Email: victor.lopezalvarez@telefonica.com
Daniel King Daniel King
skipping to change at line 3453 skipping to change at page 76, line 44
Bin Yeong Yoon Bin Yeong Yoon
ETRI ETRI
218 Gaijeongro, Yuseong-gu 218 Gaijeongro, Yuseong-gu
Daejeon, Korea Daejeon, Korea
Email: byyun@etri.re.kr Email: byyun@etri.re.kr
Ricard Vilalta Ricard Vilalta
CTTC CTTC
Email: ricard.vilalta@cttc.es Email: ricard.vilalta@cttc.es
Italo Busi
Huawei
Email: Italo.Busi@huawei.com
 End of changes. 47 change blocks. 
78 lines changed or deleted 169 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/