draft-ietf-ccamp-wson-yang-20.txt   draft-ietf-ccamp-wson-yang-21.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: September 25, 2019 Huawei Expires: November 8, 2019 Huawei
V. Lopez V. Lopez
Telefonica Telefonica
D. King D. King
U. of Lancaster U. of Lancaster
March 24, 2019 May 8, 2019
A YANG Data Model for WSON (Wavelength Switched Optical Networks) A YANG Data Model for WSON (Wavelength Switched Optical Networks)
draft-ietf-ccamp-wson-yang-20 draft-ietf-ccamp-wson-yang-21
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). The YANG data model defined in this optical networks (WSONs). The YANG data model defined in this
document conforms to the Network Management Datastore Architecture document conforms to the Network Management Datastore Architecture
defined in RFC 8342. defined in RFC 8342.
Status of this Memo Status of this Memo
skipping to change at page 1, line 48 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 September 25, 2019. This Internet-Draft will expire on November 8, 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
(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
skipping to change at page 2, line 24 skipping to change at page 2, line 24
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. Requirements Language.....................................3 1.1. Requirements Language.....................................3
1.2. Terminology...............................................3 1.2. Terminology...............................................3
1.3. Tree diagram..............................................4 1.3. Tree diagram..............................................4
1.4. Prefixes in Data Node Names...............................4 1.4. Prefixes in Data Node Names...............................4
2. YANG Model (Tree Structure)....................................5 2. YANG Model (Tree Structure)....................................4
3. IETF-WSON-Topology YANG Model.................................28 3. IETF-WSON-Topology YANG Model.................................28
4. IETF-Layer0-Types YANG Model..................................67 4. Security Considerations.......................................67
5. Security Considerations.......................................83 5. IANA Considerations...........................................68
6. IANA Considerations...........................................84 6. Acknowledgments...............................................69
7. Acknowledgments...............................................85 7. References....................................................70
8. References....................................................86 7.1. Normative References.....................................70
8.1. Normative References.....................................86 7.2. Informative References...................................70
8.2. Informative References...................................86 8. Contributors..................................................72
9. Contributors..................................................88 Authors' Addresses...............................................72
Authors' Addresses...............................................88
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].
skipping to change at page 3, line 15 skipping to change at page 3, line 15
[G.698.2] defines amplified multichannel dense wavelength division [G.698.2] defines amplified multichannel dense wavelength division
multiplexing applications with single channel optical interfaces. multiplexing applications with single channel optical interfaces.
The YANG data model defined in this document refers to the standard The YANG data model defined in this document refers to the standard
application mode defined in [G.698.2]. application mode defined in [G.698.2].
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 one YANG models: ietf-wson-topology (Section
3) and ietf-layer0-types (Section 4). 3).
There are multiple applications for the yang data model defined in There are multiple applications for the yang data model defined in
this document. For example, nodes within the network can use the this document. For example, nodes within the network can use the
data model to capture their understanding of the overall WSON data model to capture their understanding of the overall WSON
topology and expose it to a controller. A controller can further topology and expose it to a controller. A controller can further
propagate the topology to other controllers. The YANG model is used propagate the topology to other controllers. The YANG model is used
by NETCONF [RFC6020], [RFC8341] or a RESTCONF [RFC8040] protocol. by NETCONF [RFC6020], [RFC8341] or a RESTCONF [RFC8040] protocol.
The YANG data model defined in this document conforms to the Network The YANG data model defined in this document conforms to the Network
Management Datastore Architecture [RFC8342]. Management Datastore Architecture [RFC8342].
skipping to change at page 4, line 31 skipping to change at page 4, line 31
1.4. 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 | [Layer0-Types] |
| wson | ietf-wson-topology | [RFCXXXX] | | wson | ietf-wson-topology | [RFCXXXX] |
| nw | ietf-network | [RFC8345] | | nw | ietf-network | [RFC8345] |
| nt | ietf-network-topology | [RFC8345] | | nt | ietf-network-topology | [RFC8345] |
| tet | ietf-te-topology | [TE-TOPO] | | tet | ietf-te-topology | [TE-TOPO] |
+-------------+-------------------------+-----------------+ +-------------+-------------------------+-----------------+
Table 1: Prefixes and corresponding YANG modules Table 1: Prefixes and corresponding YANG modules
Note: The RFC Editor will replace XXXX with the number assigned to Note: The RFC Editor will replace XXXX with the number assigned to
the RFC once this draft becomes an RFC. the RFC once this draft becomes an RFC.
YANG module "ietf-layer0-types" (defined in Section 4) references
[RFC6163], [RFC7205], and [RFC7698].
2. YANG Model (Tree Structure) 2. YANG Model (Tree Structure)
module: ietf-wson-topology module: ietf-wson-topology
augment /nw:networks/nw:network/nw:network-types/tet:te-topology: augment /nw:networks/nw:network/nw:network-types/tet:te-topology:
+--rw wson-topology! +--rw wson-topology!
augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link- augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link-
attributes: attributes:
augment /nw:networks/nw:network/nw:node/nt:termination-point/tet:te: augment /nw:networks/nw:network/nw:node/nt:termination-point/tet:te:
+--rw supported-payload-types* [index] +--rw supported-payload-types* [index]
| +--rw index uint16 | +--rw index uint16
skipping to change at page 67, line 44 skipping to change at page 67, line 39
description description
"Augment WSON label restrictions step of TE link template"; "Augment WSON label restrictions step of TE link template";
case wson { case wson {
uses layer0-types:wson-label-step; uses layer0-types:wson-label-step;
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4. IETF-Layer0-Types YANG Model 4. Security Considerations
<CODE BEGINS> file ietf-layer0-types@2019-02-07.yang
module ietf-layer0-types {
namespace "urn:ietf:params:xml:ns:yang:ietf-layer0-types";
prefix "layer0-types";
organization
"IETF CCAMP Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/ccamp/>
WG List: <mailto:ccamp@ietf.org>
Editor: Aihua Guo
<mailto:aihuaguo@huawei.com>
Editor: Young Lee
<mailto:leeyoung@huawei.com>
Editor: Italo Busi
<mailto:Italo.Busi@huawei.com>";
description
"This module defines Optical Layer 0 types. This module
provides groupings that can be applicable to Layer 0
Fixed Optical Networks (e.g., CWDM (Coarse Wavelength
Division Multiplexing) and DWDM (Dense Wavelength Division
Multiplexing)) and Flexi-grid Optical Networks.
Copyright (c) 2018 IETF Trust and the persons identified
as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).";
revision "2018-02-07" {
description
"Initial Version";
reference
"RFC XXXX: A YANG Data Model for WSON (Wavelength Switched
Optical Networks)";
}
typedef operational-mode {
type string;
description
"Vendor-specific mode that guarantees interoperability.";
}
typedef standard-mode {
type string;
description
"ITU-T G.698.2 standard mode that guarantees interoperability.
It must be an string with the following format:
B-DScW-ytz(v) where all these attributes are conformant
to the ITU-T recomendation";
reference "ITU-T G.698.2 (11/2018)";
}
typedef vendor-identifier {
type string;
description
"vendor identifier that uses vendor-specific mode";
reference "RFC7581";
}
typedef frequency-thz {
type decimal64 {
fraction-digits 5;
}
units THz;
description
"The DWDM frequency in THz, e.g., 193.12500";
reference
"RFC6205";
}
typedef frequency-ghz {
type decimal64 {
fraction-digits 5;
}
units GHz;
description
"The DWDM frequency in GHz, e.g., 193125.00";
reference
"RFC6205";
}
identity layer0-node-type {
description
"layer0 node type.";
reference
"RFC6163";
}
identity flex-grid-node {
base layer0-node-type;
description
"Flex Grid node";
}
identity wson-node-foadm {
base layer0-node-type;
description
"Fixed OADM (Optical Add-Drop Multiplexer) node";
}
identity wson-node-roadm {
base layer0-node-type;
description
"ROADM (Reconfigurable Optical Add-Drop Multiplexer)
or OXC (Optical Cross Connect) node";
}
identity wson-node-ila {
base layer0-node-type;
description
"ILA (In-Line Amplifier) node";
}
identity wavelength-assignment {
description
"Wavelength selection base";
}
identity unspecified-wavelength-assignment {
base wavelength-assignment;
description
"No method specified";
}
identity first-fit-wavelength-asignment {
base wavelength-assignment;
description
"All the available wavelengths are numbered,
and this WA (Wavelength Assignment) method chooses
the available wavelength with the lowest index";
}
identity random-wavelength-asignment {
base wavelength-assignment;
description
"This WA method chooses an available
wavelength randomly";
}
identity least-loaded-wavelength-asignment {
base wavelength-assignment;
description
"This WA method selects the wavelength that
has the largest residual capacity on the most loaded
link along the route (in multi-fiber networks)";
}
identity layer0-grid-type {
description
"Layer0 grid type.";
}
identity flex-grid-dwdm {
base layer0-grid-type;
description
"Flex grid";
}
identity wson-grid-dwdm {
base layer0-grid-type;
description
"DWDM grid";
}
identity wson-grid-cwdm {
base layer0-grid-type;
description
"CWDM grid";
}
identity term-type {
description
"Termination type.";
}
identity term-phys {
base term-type;
description
"Physical Layer Termination";
}
identity term-otu {
base term-type;
description
"OTU (Optical Transport Unit) Termination";
}
identity term-odu {
base term-type;
description
"ODU (Optical Data Unit) Termination";
}
identity term-opu {
base term-type;
description
"OPU (Optical Payload Unit) Termination";
}
identity term-section {
base term-type;
description
"Section Layer Termination";
}
identity layer0-bandwidth-type {
description
"Bandwidth type carried by a single wavelength channel";
}
identity bw-otu1 {
base layer0-bandwidth-type;
description
"OTU1 (2.66G)";
}
identity bw-otu1e {
base layer0-bandwidth-type;
description
"OTU1e (11.04G)";
}
identity bw-otu1f {
base layer0-bandwidth-type;
description
"OTU1f (11.27G)";
}
identity bw-otu2 {
base layer0-bandwidth-type;
description
"OTU2 (10.70G)";
}
identity bw-otu2e {
base layer0-bandwidth-type;
description
"OTU2e (11.09G)";
}
identity bw-otu2f {
base layer0-bandwidth-type;
description
"OTU2f (11.31G)";
}
identity bw-otu3 {
base layer0-bandwidth-type;
description
"OTU3 (43.01G)";
}
identity bw-otu3e1 {
base layer0-bandwidth-type;
description
"OTU3e1 (44.57G)";
}
identity bw-otu3e2 {
base layer0-bandwidth-type;
description
"OTU3e2 (44.58G)";
}
identity bw-otu4 {
base layer0-bandwidth-type;
description
"OTU4 (111.80G)";
}
identity bw-otucn {
base layer0-bandwidth-type;
description
"OTUCn (beyond 100G)";
}
identity dwdm-ch-spc-type {
description
"DWDM channel spacing type";
}
identity dwdm-100ghz {
base dwdm-ch-spc-type;
description
"100GHz channel spacing";
}
identity dwdm-50ghz {
base dwdm-ch-spc-type;
description
"50GHz channel spacing";
}
identity dwdm-25ghz {
base dwdm-ch-spc-type;
description
"25GHz channel spacing";
}
identity dwdm-12p5ghz {
base dwdm-ch-spc-type;
description
"12.5GHz channel spacing";
}
identity flex-ch-spc-type {
description
"Flex-grid channel spacing type";
}
identity flex-ch-spc-6p25ghz {
base flex-ch-spc-type;
description
"6.25GHz channel spacing";
}
identity flex-slot-width-granularity {
description
"Flex-grid slot width granularity";
}
identity flex-swg-12p5ghz {
base flex-slot-width-granularity;
description
"12.5GHz slot width granularity";
}
identity cwdm-ch-spc-type {
description
"CWDM channel spacing type";
}
identity cwdm-20nm {
base cwdm-ch-spc-type;
description
"20nm channel spacing";
}
identity fec-type {
description
"FEC (Forward Error Correction) type";
}
identity g-fec {
base fec-type;
description
"G-FEC (Generic-FEC)";
}
identity e-fec {
base fec-type;
description
"E-FEC (Enhanced-FEC)";
}
identity no-fec {
base fec-type;
description
"No FEC";
}
/* Groupings. */
grouping wson-path-bandwidth {
description "WSON (Wavelength Switched Optical Network)
path bandwidth attributes";
leaf bandwidth-type {
type identityref {
base layer0-bandwidth-type;
}
description "WSON bandwidth type";
}
}
grouping wson-link-bandwidth {
description "WSON link bandwidth attributes";
leaf-list supported-bandwidth-list {
type identityref {
base layer0-bandwidth-type;
}
description "WSON bandwidth type";
}
}
grouping wson-link-label {
description
"Generic label for WSON links";
choice grid-type {
description
"Label for DWDM or CWDM grid";
case dwdm {
leaf dwdm-n {
type int16;
description
"N is used to determine the Nominal Central Frequency.
The set of nominal central frequencies can be
built using the following expression
f = 193.1 THz + N x 0.00625 THz,
where 193.1 THz is ITU-T 'anchor frequency'
for transmission over the C band, N is a positive or
negative integer including 0.";
reference
"RFC6205";
}
}
case cwdm {
leaf cwdm-n {
type int16;
description
"N is a two's-complement integer to take either a
positive, negative, or zero value. This value is
used to compute the channel wavelength as such
in G.694.2:
Wavelength (nm) = 1471 nm + N * 20 nm";
reference
"RFC6205";
}
}
}
}
grouping wson-path-label {
description
"Generic label for WSON paths";
choice grid-type {
description
"Label for DWDM or CWDM grid";
case dwdm {
choice single-or-super-channel {
description "single or super channel";
case single {
leaf dwdm-n {
type int16;
description
"N is used to determine the Nominal Central Frequency.
The set of nominal central frequencies can be
built using the following expression
f = 193.1 THz + N x 0.00625 THz,
where 193.1 THz is ITU-T 'anchor frequency'
for transmission over the C band, N is a positive or
negative integer including 0.";
}
}
case super {
leaf-list subcarrier-dwdm-n {
type int16;
description
"List of subcarrier channels for super channel.
Each of the channels is represented by an
integer, n, a two's-complement integer to take
either a positive, negative, or zero value.
This value is used to compute the frequency as
such in G.694.1:
Frequency (THz) =
193.1 THz + n * channel spacing (THz)";
}
}
}
}
case cwdm {
leaf cwdm-n {
type int16;
description
"Represented by an integer, n, a two's-complement
integer to take either a positive, negative, or
zero value. This value is used to compute the
channel wavelength as such in G.694.2:
Wavelength (nm) = 1471 nm + n * 20 nm";
reference
"RFC6205";
}
}
}
}
grouping layer0-label-restriction {
description
"layer0 label restriction.";
leaf grid-type {
type identityref {
base layer0-grid-type;
}
description "Grid type";
}
leaf priority {
type uint8;
description "priority";
}
}
grouping wson-label-step {
description "Label step information for WSON";
choice layer0-grid-type {
description
"Grid type: DWDM, CWDM, etc.";
case dwdm {
leaf wson-dwdm {
type identityref {
base dwdm-ch-spc-type;
}
description
"Label-step is the channel-spacing (GHz), e.g.,
100, 50, 25, or 12.5 GHz for DWDM";
reference
"RFC6205";
}
}
case cwdm {
leaf wson-cwdm {
type identityref {
base cwdm-ch-spc-type;
}
description
"label-step is the channel-spacing (nm), i.e., 20 nm
for CWDM, which is the only value defined for CWDM";
reference
"RFC6205";
}
}
}
}
grouping flex-grid-node-attributes {
description "Flex-grid node attributes";
container flex-grid-node {
description "Flex-grid node attrtibutes";
leaf node-type {
type identityref {
base layer0-node-type;
}
description "Flex-grid node type";
}
}
}
grouping flex-grid-path-bandwidth {
description "Flex-grid path bandwidth attributes";
leaf bandwidth-type {
type identityref {
base layer0-bandwidth-type;
}
description "Flex-grid bandwidth type";
}
}
grouping flex-grid-link-bandwidth {
description "flex-grid link bandwidth attributes";
leaf-list supported-bandwidth-list {
type identityref {
base layer0-bandwidth-type;
}
description "Flex-grid bandwidth type";
}
}
grouping flex-grid-link-label {
description "Flex-grid link label.";
leaf flex-n {
type uint16;
description
"N is used to determine the Nominal Central Frequency.
The set of nominal central frequencies can be
built using the following expression
f = 193.1 THz + N x 0.00625 THz,
where 193.1 THz is ITU-T 'anchor frequency'
for transmission over the C band, N is a positive or
negative integer including 0.";
reference
"RFC7698";
}
}
grouping flex-grid-channel {
description "Flex-grid channel grouping.";
uses flex-grid-link-label;
leaf flex-m {
type uint16 {
range "1..max";
}
description
"M is used to determine the slot width. A slot width is
constrained to be M x SWG (that is, M x 12.5 GHz),
where M is an integer greater than or equal to 1.";
reference
"RFC7698";
}
}
grouping flex-grid-path-label {
description "Flex-grid path label.";
choice single-or-super-channel {
description "single of super channel";
case single {
uses flex-grid-channel;
}
case super {
list subcarrier-flex-n {
key flex-n;
uses flex-grid-channel;
description
"List of subcarrier channels for flex-grid
super channel.";
}
}
}
}
grouping flex-grid-label-restriction {
description
"Flex Grid-specific label restriction";
uses layer0-label-restriction;
container flex-grid {
description "flex-grid definition";
leaf nominal-central-frequency-granularity {
type identityref {
base flex-ch-spc-type;
}
default flex-ch-spc-6p25ghz;
description
"It is the spacing between allowed nominal central
frequencies. Default is 6.25 GHz";
reference
"RFC7698";
}
leaf slot-width-granularity {
type identityref {
base flex-slot-width-granularity;
}
default flex-swg-12p5ghz;
description
"Minimum space between slot widths. Default is
12.5 GHz";
reference
"RFC7698";
}
leaf min-slot-width-factor {
type uint16 {
range "1..max";
}
default 1;
description
"Minimum slot width is calculated by:
Minimum slot width (GHz) =
min-slot-width-factor * slot-width-granularity";
reference
"RFC8363";
}
leaf max-slot-width-factor {
type uint16 {
range "1..max";
}
description
"Maximum slot width is calculated by:
Maximum slot width (GHz) =
max-slot-width-factor * slot-width-granularity";
reference
"RFC8363";
}
}
}
grouping flex-grid-label-step {
description "Label step information for flex grid";
leaf flex {
type identityref {
base flex-ch-spc-type;
}
default flex-ch-spc-6p25ghz;
description
"Label-step is the nominal central frequency
granularity (GHz), e.g., 6.25 GHz";
reference
"RFC7698";
}
}
}
<CODE ENDS>
5. 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 that is designed to be accessed via network management protocols
such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF
layer is the secure transport layer, and the mandatory-to-implement layer is the secure transport layer, and the mandatory-to-implement
secure transport is Secure Shell (SSH) [RFC6242]. The lowest secure transport is Secure Shell (SSH) [RFC6242]. The lowest
RESTCONF layer is HTTPS, and the mandatory-to-implement secure RESTCONF layer is HTTPS, and the mandatory-to-implement secure
transport is TLS [RFC8446]. transport is TLS [RFC8446].
The NETCONF access control model [RFC6536] provides the means to The NETCONF access control model [RFC6536] provides the means to
skipping to change at page 84, line 21 skipping to change at page 68, line 42
/nw:networks/nw:network/nw:node/nt:termination-point/tet:te /nw:networks/nw:network/nw:node/nt:termination-point/tet:te
/nw:networks/nw:network/nw:node/tet:te/tet:te-node-attributes /nw:networks/nw:network/nw:node/tet:te/tet:te-node-attributes
/te-connectivity-matrices/te-connectivity-matrix/tet:path- /te-connectivity-matrices/te-connectivity-matrix/tet:path-
constraints/tet:te-bandwidth/tet:technology constraints/tet:te-bandwidth/tet:technology
/nw:networks/nw:network/nw:node/tet:te /nw:networks/nw:network/nw:node/tet:te
/tet:tunnel-termination-point/tet:local-link-connectivities /tet:tunnel-termination-point/tet:local-link-connectivities
/tet:label-restrictions/tet:label-restriction /tet:label-restrictions/tet:label-restriction
6. IANA Considerations 5. IANA Considerations
This document registers the following namespace URIs in the IETF XML This document registers the following namespace URIs in the IETF XML
registry [RFC3688]: registry [RFC3688]:
-------------------------------------------------------------------- --------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang: ietf-wson-topology URI: urn:ietf:params:xml:ns:yang: ietf-wson-topology
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
-------------------------------------------------------------------- --------------------------------------------------------------------
URI: urn:ietf:params:xml:ns:yang: ietf-layer0-types
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
--------------------------------------------------------------------
This document registers the following YANG modules in the YANG This document registers the following YANG modules in the YANG
Module Names registry [RFC7950] & [RFC6020]: Module Names registry [RFC7950] & [RFC6020]:
-------------------------------------------------------------------- --------------------------------------------------------------------
name: ietf-wson-topology name: ietf-wson-topology
namespace: urn:ietf:params:xml:ns:yang:ietf-wson-topology namespace: urn:ietf:params:xml:ns:yang:ietf-wson-topology
reference: RFC XXXX (TDB) reference: RFC XXXX (TDB)
-------------------------------------------------------------------- --------------------------------------------------------------------
name: ietf-layer0-types
namespace: urn:ietf:params:xml:ns:yang: ietf-layer0-types
reference: RFC XXXX (TDB)
--------------------------------------------------------------------
7. Acknowledgments 6. 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 7. References
8.1. Normative References 7.1. Normative References
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
[RFC6241] R. Enns, Ed., M. Bjorklund, Ed., J. Schoenwaelder, Ed., [RFC6241] R. Enns, Ed., M. Bjorklund, Ed., J. Schoenwaelder, Ed.,
"Network Configuration Protocol (NETCONF)", RFC 6241, June "Network Configuration Protocol (NETCONF)", RFC 6241, June
2011. 2011.
[RFC6242] M. Wasserman, "Using the NETCONF Protocol over Secure [RFC6242] M. Wasserman, "Using the NETCONF Protocol over Secure
skipping to change at page 86, line 38 skipping to change at page 70, line 38
[RFC8341] A. Bierman, M. Bjorklund, "Network Configuration Access [RFC8341] A. Bierman, M. Bjorklund, "Network Configuration Access
Control Model", RFC 8341, March 2018. Control Model", RFC 8341, March 2018.
[RFC8446] E. Rescorla, "The Transport Layer Security (TLS) Protocol [RFC8446] E. Rescorla, "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC8446, August 2018. 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 [Layer0-Types] Y. Lee, et al., "YANG Data Model for Layer0 Types",
work in progress: draft-ietf-ccamp-layer0-types.
7.2. Informative 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, DOI Requirement Levels", BCP 14, RFC 2119, DOI
10.17487/RFC2119, March 1997, <https://www.rfc- 10.17487/RFC2119, March 1997, <https://www.rfc-
editor.org/info/rfc2119>. 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.
[RFC6163] Y. Lee, Ed. G. Berstein, Ed., W. Imajuku, "Framework for [RFC6163] Y. Lee, Ed. G. Berstein, Ed., W. Imajuku, "Framework for
skipping to change at page 88, line 5 skipping to change at page 72, line 5
Wilton, "Network Management Datastore Architecture Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, March 2018. (NMDA)", RFC 8342, March 2018.
[RFC8345] A. Clemm, et al, "A YANG Data Model for Network [RFC8345] A. Clemm, et al, "A YANG Data Model for Network
Topologies", RFC 8345, March 2018. Topologies", RFC 8345, March 2018.
[G.698.2] "Amplified multichannel dense wavelength division [G.698.2] "Amplified multichannel dense wavelength division
multiplexing applications with single channel optical multiplexing applications with single channel optical
interfaces", ITU-T G.698.2 (11/2018). interfaces", ITU-T G.698.2 (11/2018).
9. Contributors 8. Contributors
Authors' Addresses Authors' Addresses
Young Lee (ed.) Young Lee (ed.)
Huawei Technologies Huawei Technologies
5700 Tennyson Parkway, Suite 600 5700 Tennyson Parkway, Suite 600
Plano, TX 75024 Plano, TX 75024
USA USA
Email: leeyoung@huawei.com Email: leeyoung@huawei.com
 End of changes. 18 change blocks. 
729 lines changed or deleted 26 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/