draft-ietf-ccamp-optical-impairment-topology-yang-01.txt   draft-ietf-ccamp-optical-impairment-topology-yang-02.txt 
CCAMP Working Group Y. Lee CCAMP Working Group Y. Lee
Internet Draft Futurewei Internet Draft SKKU (Sung Kyun Kwan University)
Intended Status: Standard Track Intended Status: Standard Track
Expires: November 27, 2019 V. Lopez Expires: May 7, 2020 V. Lopez
Telefonica Telefonica
G. Galimberti G. Galimberti
Cisco Cisco
Jean Luc Auge Jean Luc Auge
Orange Orange
D. Beller D. Beller
Nokia Nokia
May 27, 2019 November 4, 2019
A Yang Data Model for Optical Impairment-aware Topology A Yang Data Model for Optical Impairment-aware Topology
draft-ietf-ccamp-optical-impairment-topology-yang-01 draft-ietf-ccamp-optical-impairment-topology-yang-02
Abstract Abstract
In order to provision an optical connection through optical In order to provision an optical connection through optical
networks, a combination of path continuity, resource availability, networks, a combination of path continuity, resource availability,
and impairment constraints must be met to determine viable and and impairment constraints must be met to determine viable and
optimal paths through the network. The determination of appropriate optimal paths through the network. The determination of appropriate
paths is known as Impairment-Aware Routing and Wavelength Assignment paths is known as Impairment-Aware Routing and Wavelength Assignment
(IA-RWA) for WSON, while it is known as Impairment-Aware Routing and (IA-RWA) for WSON, while it is known as Impairment-Aware Routing and
Spectrum Assigment (IA-RSA) for SSON. Spectrum Assigment (IA-RSA) for SSON.
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
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 November 27, 2019. This Internet-Draft will expire on May 7, 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
(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...................................................3 1. Introduction ................................................ 3
1.1. Terminology...............................................4 1.1. Terminology ............................................ 4
1.2. Tree diagram..............................................4 1.2. Tree diagram ........................................... 4
1.3. Prefixes in Data Node Names...............................4 1.3. Prefixes in Data Node Names............................. 4
2. Reference Architecture.........................................5 2. Reference Architecture....................................... 5
2.1. Control Plane Architecture................................5 2.1. Control Plane Architecture.............................. 5
2.2. Transport Data Plane......................................6 2.2. Transport Data Plane.................................... 6
2.3. OMS Media Links...........................................7 2.3. OMS Media Links......................................... 7
2.3.1. Optical Tributary Signal (OTSi)......................7 2.3.1. Optical Tributary Signal (OTSi) ................... 7
2.3.2. Optical Tributary Signal Group (OTSiG)...............7 2.3.2. Optical Tributary Signal Group (OTSiG) ............ 8
2.3.3. Media Channel Group (MCG)............................9 2.3.3. Media Channel Group (MCG) ........................ 10
2.4. Amplifiers...............................................11 2.4. Amplifiers ............................................ 11
2.5. Transponders.............................................11 2.5. Transponders .......................................... 11
2.6. WSS/Filter...............................................12 2.6. WSS/Filter ............................................ 12
2.7. Optical Fiber............................................12 2.7. Optical Fiber ......................................... 12
3. YANG Model (Tree Structure)...................................12 3. YANG Model (Tree Structure)................................. 17
4. Optical Impairment Topology YANG Model........................14 4. Optical Impairment Topology YANG Model ..................... 19
5. Security Considerations.......................................34 5. Security Considerations..................................... 38
6. IANA Considerations...........................................34 6. IANA Considerations ........................................ 38
7. Acknowledgments...............................................35 7. Acknowledgments ............................................ 39
8. References....................................................36 8. References ................................................. 40
8.1. Normative References.....................................36 8.1. Normative References................................... 40
8.2. Informative References...................................36 8.2. Informative References................................. 40
9. Contributors..................................................38 9. Contributors ............................................... 42
Authors' Addresses...............................................38 Authors' Addresses ............................................ 42
1. Introduction 1. Introduction
In order to provision an optical connection (an optical path) In order to provision an optical connection (an optical path)
through a wavelength switched optical networks (WSONs) or spectrum through a wavelength switched optical networks (WSONs) or spectrum
switched optical networks (SSONs), a combination of path continuity, switched optical networks (SSONs), a combination of path continuity,
resource availability, and impairment constraints must be met to resource availability, and impairment constraints must be met to
determine viable and optimal paths through the network. The determine viable and optimal paths through the network. The
determination of appropriate paths is known as Impairment-Aware determination of appropriate paths is known as Impairment-Aware
Routing and Wavelength Assignment (IA-RWA) [RFC6566] for WSON, while Routing and Wavelength Assignment (IA-RWA) [RFC6566] for WSON, while
skipping to change at page 5, line 44 skipping to change at page 5, line 44
| +--------+ | +---/ \---+ | +--------+ | | +--------+ | +---/ \---+ | +--------+ |
| |Vend. B |--|--+ / \ +--|--| Vend. B| | | |Vend. B |--|--+ / \ +--|--| Vend. B| |
| +--------+ | +---( OLS Segment )---+ | +--------+ | | +--------+ | +---( OLS Segment )---+ | +--------+ |
| +--------+ | +---( )---+ | +--------+ | | +--------+ | +---( )---+ | +--------+ |
| |Vend. C |--|--+ \ / +--|--| Vend. C| | | |Vend. C |--|--+ \ / +--|--| Vend. C| |
| +--------+ | +---\ /---+ | +--------+ | | +--------+ | +---\ /---+ | +--------+ |
| +--------+ | | ~-( )-~ | | +--------+ | | +--------+ | | ~-( )-~ | | +--------+ |
| |Vend. D |--|----+ (__ __) +----|--| Vend. D| | | |Vend. D |--|----+ (__ __) +----|--| Vend. D| |
| +--------+ | -- | +--------+ | | +--------+ | -- | +--------+ |
\_____________/ \_____________/ \_____________/ \_____________/
^ ^ ^ ^
| | | |
| | | |
Scope of draft-ietf-ccamp-dwdm-if-param-yang Scope of draft-ietf-ccamp-dwdm-if-param-yang
Figure 1. Control Plane Architecture Figure 1. Control Plane Architecture
The models developed in this document is an abstracted Yang model The models developed in this document is an abstracted Yang model
that may be used in the interfaces between the MDSC and the Optical that may be used in the interfaces between the MDSC and the Optical
Domain Controller (aka MPI) and between the Optical Domain Domain Controller (aka MPI) and between the Optical Domain
Controller and the Optical Device (aka SBI) in Figure 1. It is not Controller and the Optical Device (aka SBI) in Figure 1. It is not
intended to support detailed low-level DWDM interface model. DWDM intended to support a detailed low-level DWDM interface model. DWDM
interface model is supported by the models presented in [draft-ietf- interface model is supported by the models presented in [draft-ietf-
ccamp-dwdm-if-parameter-yang]. ccamp-dwdm-if-parameter-yang].
2.2. Transport Data Plane 2.2. Transport Data Plane
This section provides the description of the reference optical This section provides the description of the reference optical
network architecture and its relevant components to support optical network architecture and its relevant components to support optical
impairment-aware path computation. impairment-aware path computation.
Figure 2 shows the reference architecture. Figure 2 shows the reference architecture.
+-------------------+ +-------------------+ +-------------------+ +-------------------+
| ROADM Node | | ROADM Node | | ROADM Node | | ROADM Node |
| | | | | | | |
| PA +-------+ BA | ILA | PA +-------+ BA | | PA +-------+ BA | ILA | PA +-------+ BA |
| +-+ | WSS/ | +-+ | _____ +--+ _____ | +-+ | WSS/ | +-+ | | +-+ | WSS/ | +-+ | _____ +--+ _____ | +-+ | WSS/ | +-+ |
--|-| |-|Filter |-| |-|-()____)--| |-()____)-|-| |-|Filter |-| |-|-- ---|-| |-|Filter |-| |-|-()____)--| |-()____)-|-| |-|Filter |-| |-|---
| +-+ | | +-+ | +--+ | +-+ | | +-+ | | +-+ | | +-+ | +--+ | +-+ | | +-+ |
| +-------+ | optical | +-------+ | | +-------+ | optical | +-------+ |
| | | | | fiber | | | | | | | | | | fiber | | | | |
| | | | | | | | | | | | | | | | | | | |
| o-o-o | | o-o-o | | o-o-o | | o-o-o |
| transponders | | transponders | | transponders | | transponders |
+-------------------+ +-------------------+ +-------------------+ +-------------------+
OTS Link OTS Link OTS Link OTS Link
-----------> ----------> --------> -------->
OMS Link OMS Link
---------------------------------> ---------------------------------->
PA: Pre-Amplifier PA: Pre-Amplifier
BA: Booster Amplifier BA: Booster Amplifier
ILA: In-Line Amplifier ILA: In-Line Amplifier
Figure 2. Reference Architecture for Optical Transport Network Figure 2. Reference Architecture for Optical Transport Network
BA (on the left side ROADM) is the ingress Amplifier and PA (on the BA (on the left side ROADM) is the ingress Amplifier and PA (on the
right side ROADM is the egress amplifier for the OMS link shown in right side ROADM is the egress amplifier for the OMS link shown in
the Figure. the Figure.
2.3. OMS Media Links 2.3. OMS Media Links
According to [G.872], OMS Media Link represents a media link between According to [G.872], OMS Media Link represents a media link between
two ROADM. Specifically, it originates at the ROADM's Filter in the two ROADMs. Specifically, it originates at the ROADM's Filter in the
source ROADM and terminates at the ROADM's Filter in the destination source ROADM and terminates at the ROADM's Filter in the destination
ROADM. ROADM.
OTS Media Link represents a media link: OTS Media Link represents a media link:
(i) between ROADM's BA and ILA; (i) between ROADM's BA and ILA;
(ii) between a pair of ILAs; (ii) between a pair of ILAs;
(iii) between ILA and ROADM's PA. (iii) between ILA and ROADM's PA.
OMS Media link can be decomposed in a sequence of OTS links type OMS Media link can be decomposed in a sequence of OTS links type
(i), (ii), and (iii) as discussed above. OMS Media link would give (i), (ii), and (iii) as discussed above. OMS Media link would give
an abstracted view of impairment data (e.g., power, OSNR, etc.) to an abstracted view of impairment data (e.g., power, OSNR, etc.) to
the network controller. the network controller.
For the sake of optical impairment evaluation OMS Media link can be For the sake of optical impairment evaluation OMS Media link can be
also decomposed in a sequence of elements such as BA, fiber section, also decomposed in a sequence of elements such as BA, fiber section,
ILA, concentrated loss and PA. ILA, concentrated loss and PA.
skipping to change at page 8, line 21 skipping to change at page 8, line 27
YANG model perspective, the OTSiG is a logical construct that YANG model perspective, the OTSiG is a logical construct that
associates the OTSi's, which belong to the same OTSiG. The typical associates the OTSi's, which belong to the same OTSiG. The typical
application of an OTSiG consisting of more than one OTSi is inverse application of an OTSiG consisting of more than one OTSi is inverse
multiplexing. Constraints exist for the OTSi's belonging to the same multiplexing. Constraints exist for the OTSi's belonging to the same
OTSiG such as: (i) all OTSi's must be co-routed over the same OTSiG such as: (i) all OTSi's must be co-routed over the same
optical fibers and nodes and (ii) the differential delay between the optical fibers and nodes and (ii) the differential delay between the
different OTSi's may not exceed a certain limit. Example: a 400Gbps different OTSi's may not exceed a certain limit. Example: a 400Gbps
client signal may be carried by 4 OTSi's where each OTSi carries client signal may be carried by 4 OTSi's where each OTSi carries
100Gbps of client traffic. 100Gbps of client traffic.
OTSiG OTSiG
__________________________/\__________________________ _________________________/\__________________________
/ \ / \
m=7 m=7
- - - +---------------------------X---------------------------+ - - - - - +---------------------------X---------------------------+ - - -
/ / / | | / / / / / | | / / /
/ / /| OTSi OTSi OTSi OTSi |/ / / / / /| OTSi OTSi OTSi OTSi |/ / /
/ / / | ^ ^ ^ ^ | / / / / / | ^ ^ ^ ^ | / / /
/ / /| | | | | |/ / / / / /| | | | | |/ / /
/ / / | | | | | | / / / / / | | | | | | / / /
/ / /| | | | | |/ / / / / /| | | | | |/ / /
-4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12
--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+--- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---
n = ? n = ?
K1 K2 K3 K4 K1 K2 K3 K4
2.3.3 Media Channel (MC) 2.3.3 Media Channel (MC)
The definition of the MC is currently being moved from ITU-T The definition of the MC is currently being moved from ITU-T
Recommendation G.872 [G.872] to the new draft Recommendation G.807 Recommendation G.872 [G.872] to the new draft Recommendation G.807
(still work in progress) [G.807]. Section 3.2.2 defines the term MC (still work in progress) [G.807]. Section 3.2.2 defines the term MC
and section 7.1.2 provides a more detailed description with some and section 7.1.2 provides a more detailed description with some
examples. The definition of the MC is very generic (see ITU-T draft examples. The definition of the MC is very generic (see ITU-T draft
Recommendation G.807, Figure 7-1). In the YANG model below, the MC Recommendation G.807, Figure 7-1). In the YANG model below, the MC
is used with the following semantics: is used with the following semantics:
The MC is an end-to-end topological network construct and can be The MC is an end-to-end topological network construct and can be
considered as an "optical pipe" with a well-defined frequency slot considered as an "optical pipe" with a well-defined frequency slot
skipping to change at page 9, line 16 skipping to change at page 9, line 20
is used with the following semantics: is used with the following semantics:
The MC is an end-to-end topological network construct and can be The MC is an end-to-end topological network construct and can be
considered as an "optical pipe" with a well-defined frequency slot considered as an "optical pipe" with a well-defined frequency slot
between one or more optical transmitters each generating an OTSi and between one or more optical transmitters each generating an OTSi and
the corresponding optical receivers terminating the OTSi's. If the the corresponding optical receivers terminating the OTSi's. If the
MC carries more than one OTSi, it is assumed that these OTSi's MC carries more than one OTSi, it is assumed that these OTSi's
belong to the same OTSiG. belong to the same OTSiG.
m=8 m=8
+-------------------------------X------------------------------+ +-------------------------------X-------------------------------+
| | | | | |
| +----------X----------+ | +----------X----------+ | | +----------X----------+ | +----------X----------+ |
| | OTSi | | OTSi | | | | OTSi | | OTSi | |
| | o | | | o | | | | ^ | | | ^ | |
| | | | | | | | | | | | | | | |
-4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12
--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-
| n=4 | | n=4 |
K1 K2 K1 K2
<------------------------ Media Channel -----------------------> <------------------------ Media Channel ----------------------->
The frequency slot of the MC is defined by the n value defining the The frequency slot of the MC is defined by the n value defining the
central frequency of the MC and the m value that defines the width central frequency of the MC and the m value that defines the width
of the MC following the flexible grid definition in ITU-T of the MC following the flexible grid definition in ITU-T
Recommendation G.694.1 [G.694.1]. In this model, the effective Recommendation G.694.1 [G.694.1]. In this model, the effective
frequency slot as defined in ITU-T draft Recommendation G.807 is frequency slot as defined in ITU-T draft Recommendation G.807 is
equal to the frequency slot of this end-to-end MC. It is also equal to the frequency slot of this end-to-end MC. It is also
assumed that ROADM devices can switch MCs. For various reasons (e.g. assumed that ROADM devices can switch MCs. For various reasons (e.g.
skipping to change at page 10, line 18 skipping to change at page 10, line 23
to to carry all OTSi's belonging to the same OTSiG. to to carry all OTSi's belonging to the same OTSiG.
The MCG can be considered as an association of MCs without defining The MCG can be considered as an association of MCs without defining
a hierarchy where each MC is defined by its (n,m) value pair. An MCG a hierarchy where each MC is defined by its (n,m) value pair. An MCG
consists of more than one MC when no single MC can be found from consists of more than one MC when no single MC can be found from
source to destination that is wide enough to accommodate all OTSi's source to destination that is wide enough to accommodate all OTSi's
(modulated carriers) that belong to the same OTSiG. In such a case (modulated carriers) that belong to the same OTSiG. In such a case
the set of OTSi's belonging to a single OTSiG have to be split the set of OTSi's belonging to a single OTSiG have to be split
across 2 or more MCs. across 2 or more MCs.
MCG1 = {M1.1, M1.2} MCG1 = {M1.1, M1.2}
_______________________/\_____________________________ __________________________/\__________________________
/ \ / \
M1.1 M2 M1.2 M1.1 M2 M1.2
________/\____________ _____/\______ ____/\_____ ____________/\____________ ______/\______ ____/\____
/ \ / \/ \ / \/ \/ \
- - +-------------------------------------------------------+ - - - - - +-------------------------------------------------------+ - - -
/ / | | / / / / / / /| | / / / / / | | / / / / / / /| | / / /
/ /| OTSi OTSi OTSi |/ / / / / / / | OTSi |/ / / / /| OTSi OTSi OTSi |/ / / / / / / | OTSi |/ / /
/ / | ^ ^ ^ | / / / / / / /| ^ | / / / / / | ^ ^ ^ | / / / / / / /| ^ | / / /
/ /| | | | |/ / / / / / / | | |/ / / / /| | | | |/ / / / / / / | | |/ / /
/ / | | | | | / / / / / / /| | | / / / / / | | | | | / / / / / / /| | | / / /
/ /| | | | |/ / / / / / / | | |/ / / / /| | | | |/ / / / / / / | | |/ / /
-7 -1 0 1 2 3 4 5 6 7 8 9 10 . . . . . 17 . . 21 -7 -1 0 1 2 3 4 5 6 7 8 9 10 . . . . . 17 . . 21
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--
n=0 n=11 n=17 n=0 n=11 n=17
K1 K2 K3 K4 K1 K2 K3 K4
The MCG is relevant for path computation because all end-to-end MCs The MCG is relevant for path computation because all end-to-end MCs
belonging to the same MCG have to be co-routed, i.e., have to follow belonging to the same MCG have to be co-routed, i.e., have to follow
the same path. Additional constraints may exist (e.g. differential the same path. Additional constraints may exist (e.g. differential
delay). delay).
2.4. Amplifiers 2.4. Amplifiers
Optical amplifiers are in charge of amplifying the optical signal in Optical amplifiers are in charge of amplifying the optical signal in
the optical itself without any electrical conversion. There are the optical itself without any electrical conversion. There are
skipping to change at page 12, line 30 skipping to change at page 12, line 36
There are various optical fiber types defined by ITU-T. There are There are various optical fiber types defined by ITU-T. There are
several fiber-level parameters that need to be factored in, such as, several fiber-level parameters that need to be factored in, such as,
fiber-type, length, loss coefficient, pmd, connectors (in/out). fiber-type, length, loss coefficient, pmd, connectors (in/out).
ITU-T G.652 defines Standard Singlemode Fiber; G.654 Cutoff Shifted ITU-T G.652 defines Standard Singlemode Fiber; G.654 Cutoff Shifted
Fiber; G.655 Non-Zero Dispersion Shifted Fiber; G.656 Non-Zero Fiber; G.655 Non-Zero Dispersion Shifted Fiber; G.656 Non-Zero
Dispersion for Wideband Optical Transport; G.657 Bend-Insensitive Dispersion for Wideband Optical Transport; G.657 Bend-Insensitive
Fiber. There may be other fiber-types that need to be considered. Fiber. There may be other fiber-types that need to be considered.
2.8. ROADM Node Architectures
The ROADM node architectures in today's dense wavelength division
multiplexing (DWDM) networks can be categorized as follows:
o Integrated ROADM architecture with integrated optical transponders
o Integrated ROADM architecture with integrated optical transponders
and single channel add/drop ports for remote optical transponders
o Disaggregated ROADM architecture where the ROADM is subdivided
into degree, add/drop, and optical transponder subsystems handled
as separate network elements
The TE topology YANG model augmentations including optical
impairments for DWDM networks defined below intend to cover all the
3 categories of ROADM architectures listed above. In the case of a
disaggregated ROADM architecture, it is assumed that optical domain
controller already performs some form of abstraction and presents
the TE-node representing the disaggregated ROADM in the same way as
an integrated ROADM with integrated optical transponders if the
optical transponder subsystems and the add/drop subsystems are
collocated (short fiber links not imposing significant optical
impairments).
The different ROADM architectures are briefly described and
illustrated in the following subsections.
[Editor's Note: The modeling of remote optical transponders located
for example in the client device with a single channel link between
the OT and the add/drop port of the ROADM requires further
investigations and will be addressed in a future revision of this
document.]
2.8.1. Integrated ROADM architecture with integrated transponders
Figure 2 and Figure <A1> below show the typical architecture of an
integrated ROADM node, which contains the optical transponders as an
integral part of the ROADM node. Such an integrated ROADM node
provides DWDM interfaces as external interfaces for interconnecting
the device with its neighboring ROADMs (see OTS link above). The
number of these interfaces denote also the degree of the ROADM. A
degree 3 ROADM for example has 3 DWDM links that interconnect the
ROADM node with 3 neighboring ROADMs. Additionally, the ROADM
provides client interfaces for interconnecting the ROADM with client
devices such as IP routers or Ethernet switches. These client
interfaces are the client interfaces of the integrated optical
transponders.
. . . . . . . . . . . . . . . . . .
+-----.-------------------------------- .-----+
| . ROADM . |
| . /| +-----------------+ |\ . |
Line | . / |--| |--| \ . | Line
WEST | /| . | |--| |--| | . |\ | EAST
------+-/ |-.-| |--| OCX |--| |-.-| \-+-----
------+-\ |-.-| |--| |--| |-.-| /-+-----
| \| . | |--| |--| | . |/ |
| . \ |--| |--| / . |
| . \| +-----------------+ |/ . |
| . . |
| . +---+ +---+ +---+ +---+ . |
| . | O | | O | | O | | O | . |
| . | T | | T | | T | | T | . |
| . +---+ +---+ +---+ +---+ . |
| . | | | | | | | | . |
+-----.------+-+---+-+---+-+---+-+------.-----+
. . . .|.| . |.| . |.| . |.|. . . .
| | | | | | | | TE Node
Client Interfaces
Figure <A1>: ROADM architectiure with integrated transponders
2.8.2. Integrated ROADMs with integrated optical transponders and
single channel add/drop interfaces for remote optical transponders
Figure <A2> below shows the extreme case where all optical
transponders are not integral parts of the ROADM but are separate
devices that are interconnected with add/drop ports of the ROADM. If
the optical transponders and the ROADM are collocated and if short
single channel fiber links are used to interconnect the optical
transponders with an add/drop port of the ROADM, the optical domain
controller may present these optical transponders in the same way as
integrated optical transponders. If, however, the optical
impairments of the single channel fiber link between the optical
transponder and the add/drop port of the ROADM cannot be neglected,
it is necessary to represent the fiber link with its optical
impairments in the topology model This also implies that the optical
transponders belong to a separate TE node [Editor's Note: this
requires further study].
. . . . . . . . . . . . . . . . . .
. Abstracted ROADM .
+-----.-------------------------------- .-----+
| . ROADM . |
| . /| +-----------------+ |\ . |
Line | . / |--| |--| \ . | Line
WEST | /| . | |--| |--| | . |\ | EAST
------+-/ |-.-| |--| OCX |--| |-.-| \-+-----
------+-\ |-.-| |--| |--| |-.-| /-+-----
| \| . | |--| |--| | . |/ |
| . \ |--| |--| / . |
| . \| +-----------------+ |/ . |
+-----.---------|----|---|----|---------.-----|
Colored OT . +-+ ++ ++ +-+ .
line I/F . | | | | .
. +---+ +---+ +---+ +---+ .
. | O | | O | | O | | O | .
. | T | | T | | T | | T | .
. +---+ +---+ +---+ +---+ .
. . . .|.| . |.| . |.| . |.|. . . .
| | | | | | | | TE Node
Client Interfaces
Figure <A2>: ROADM architectiure with remote transponders
2.8.3. Disaggregated ROADMs that are subdivided into degree, add/drop,
and optical transponder subsystems
Recently, some DWDM network operators started demanding ROADM
subsystems from their vendors. An example is the OpenROADM project
where multiple operators and vendors are developing related YANG
models. The subsystems of a disaggregated ROADM are: single degree
subsystems, add/drop subsystems and optical transponder subsystems.
These subsystems separate network elements and each network element
provides a separate management and control interface. The subsystems
are typically interconnected using short fiber patch cables and form
together a disaggregated ROADM node. This disaggregated ROADM
architecture is depicted in Figure <A3> below.
As this document defines TE topology YANG model augmentations [TE-
TOPO] for the TE topology YANG model provided at the north-bound
interface of the optical domain controller, it is a valid assumption
that the optical domain controller abstracts the subsystems of a
disaggregated ROADM and presents the disaggregated ROADM in the same
way as an integrated ROADM hiding all the interconnects that are not
relevant from an external TE topology view.
. . . . . . . . . . . . . . . . . .
. Abstracted ROADM .
+-----.----------+ +----------.-----+
| Degree 1 | | Degree 2 |
Line | . +-----+ | + +-----+ . | Line
1 | /| . | W |-|------------|-| W | . |\ | 2
-----+-/ |-.--| S ******** ******** S |--.-| \-+-----
-----+-\ |-.--| S | | * * | | S |--.-| /-+-----
| \| . | |-|-+ * * +-|-| | . |/ |
| . +-+-+-+ | | * * | | +-+-+-+ . |
+-----.----|-----+ | * * | +-----|----.-----+
. | | * * | | .
+-----.----|-----+ | * * | +-----|----.-----+
| Degree 4 | | | * * | | | Degree 3 |
Line | . +-----+ | | * * | | +-----+ . | Line
4 | /| . | W |-|-|--*--*--+ | | W | . |\ | 3
-----+-/ |-.--| S | | +--*--*----|-| S |--.-| \-+-----
-----+-\ |-.--| S |-|----*--*----|-| S |--.-| /-+-----
| \| . | | | * * | | | . |/ |
| . +--*--+ | * * | +--*--+ . |
+-----.-----*----+ * * +----*-----.-----+
. * * * * .
. +--*---------*--*---------*--+ .
. | ADD | .
. | DROP | .
. +----------------------------+ .
Colored OT . | | | | .
line I/F . +---+ +---+ +---+ +---+ .
. | O | | O | | O | | O | .
. | T | | T | | T | | T | .
. +---+ +---+ +---+ +---+ .
. . .|.| . |.| . |.| . |.|. . .
| | | | | | | | TE Node
Client Interfaces
Figure <A3>: ROADM architectiure with remote transponders
3. YANG Model (Tree Structure) 3. YANG Model (Tree Structure)
module: ietf-optical-impairment-topology module: ietf-optical-impairment-topology
augment /nw:networks/nw:network/nw:network-types/tet:te-topology: augment /nw:networks/nw:network/nw:network-types/tet:te-topology:
+--rw optical-impairment-topology! +--rw optical-impairment-topology!
augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes: augment /nw:networks/nw:network/nt:link/tet:te/tet:te-link-attributes:
+--ro OMS-attributes +--ro OMS-attributes
+--ro generalized-snr? decimal64 +--ro generalized-snr? decimal64
+--ro equalization-mode identityref +--ro equalization-mode identityref
+--ro (power-param)? +--ro (power-param)?
skipping to change at page 29, line 11 skipping to change at page 33, line 27
} }
grouping OTSiG { grouping OTSiG {
description "OTSiG definition , representing client digital information stream description "OTSiG definition , representing client digital information stream
supported by 1 or more OTSi"; supported by 1 or more OTSi";
container OTSiG-container { container OTSiG-container {
config false; config false;
description description
"the container contains the related list of OTSi. "the container contains the related list of OTSi.
The list could also be of only 1 element"; The list could also be of only 1 element";
list OTSi { list OTSi {
key "OTSi-carrier-id"; key "OTSi-carrier-id";
description description
"list of OTSi's under OTSi-G"; "list of OTSi's under OTSi-G";
leaf OTSi-carrier-id { leaf OTSi-carrier-id {
type int16; type int16;
description "OTSi carrier-id"; description "OTSi carrier-id";
} }
leaf OTSi-carrier-frequency { leaf OTSi-carrier-frequency {
type decimal64 { type decimal64 {
skipping to change at page 29, line 46 skipping to change at page 34, line 12
"OTSi signal width"; "OTSi signal width";
} }
leaf channel-delta-power { leaf channel-delta-power {
type decimal64 { type decimal64 {
fraction-digits 2; fraction-digits 2;
} }
units dB; units dB;
config false; config false;
description description
"optional ; delta power to ref channel input-power applied "optional ; delta power to ref channel input-power applied
to this media channel"; to this media channel";
} }
} }
} // OTSiG container } // OTSiG container
} // OTSiG grouping } // OTSiG grouping
grouping media-channel-groups { grouping media-channel-groups {
description "media channel groups"; description "media channel groups";
list media-channel-group { list media-channel-group {
key "i"; key "i";
description description
"list of media channel groups"; "list of media channel groups";
leaf i { leaf i {
type int16; type int16;
description "index of media channel group member"; description "index of media channel group member";
} }
skipping to change at page 36, line 24 skipping to change at page 40, line 24
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", RFC 8341, March 2018. Access Control Model", RFC 8341, March 2018.
8.2. Informative References 8.2. Informative References
[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, June 2011. (NETCONF)", RFC 6241, June 2011.
[RFC6566] Y. Lee, G. Bernstein, D. Li, G. Martinelli, "A Framework [RFC6566] Y. Lee, G. Bernstein, D. Li, G. Martinelli, "A Framework
for the Control of Wavelength Switched Optical Networks for the Control of Wavelength Switched Optical Networks
(WSONs) with Impairments", RFC 6566, March 2012. (WSONs) with Impairments", RFC 6566, March 2012.
[RFC7446] Y. Lee, G. Bernstein, D. Li, W. Imajuku, "Routing and [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 Network [RFC7579] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General Network
Element Constraint Encoding for GMPLS Controlled Element Constraint Encoding for GMPLS Controlled
Networks", RFC 7579, June 2015. Networks", RFC 7579, June 2015.
skipping to change at page 37, line 8 skipping to change at page 41, line 8
Switched Optical Networks", RFC 7581, June 2015. Switched Optical Networks", RFC 7581, June 2015.
[RFC7698] O. Gonzalez de Dios, Ed. and R. Casellas, Ed., "Framework [RFC7698] O. Gonzalez de Dios, Ed. and R. Casellas, Ed., "Framework
and Requirements for GMPLS-Based Control of Flexi-Grid and Requirements for GMPLS-Based Control of Flexi-Grid
Dense Wavelength Division Multiplexing (DWDM) Networks", Dense Wavelength Division Multiplexing (DWDM) Networks",
RFC 7698, November 2015. RFC 7698, November 2015.
[RFC8340] M. Bjorklund, L. Berger, Ed., "YANG Tree Diagrams", RFC [RFC8340] M. Bjorklund, L. Berger, Ed., "YANG Tree Diagrams", RFC
8340, March 2018. 8340, March 2018.
[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, 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.
[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.
[RFC8453] Ceccarelli, D. and Y. Lee, "Framework for Abstraction and [RFC8453] Ceccarelli, D. and Y. Lee, "Framework for Abstraction and
Control of Traffic Engineered Networks", RFC 8453, August Control of Traffic Engineered Networks", RFC 8453, August
2018. 2018.
[WSON-Topo] Y. Lee, Ed., "A Yang Data Model for WSON Optical [WSON-Topo] Y. Lee, Ed., "A Yang Data Model for WSON Optical
Networks", draft-ietf-ccamp-wson-yang-13, work in Networks", draft-ietf-ccamp-wson-yang-13, work in
progress. progress.
skipping to change at page 38, line 20 skipping to change at page 42, line 20
Email: jonas.martensson@ri.se Email: jonas.martensson@ri.se
Aihua Guo Aihua Guo
Huawei Technologies Huawei Technologies
Email: aguo@futurewei.com Email: aguo@futurewei.com
Authors' Addresses Authors' Addresses
Young Lee Young Lee
Futurewei Technologies SKKU (Sung Kyun Kwan University)
Email: younglee.tx@gmail.com Email: younglee.tx@gmail.com
Haomian Zheng Haomian Zheng
Huawei Technologies Huawei Technologies
Email: zhenghaomian@huawei.com Email: zhenghaomian@huawei.com
Italo Busi Italo Busi
Huawei Technologies Huawei Technologies
skipping to change at page 38, line 43 skipping to change at page 43, line 4
Nicola Sambo Nicola Sambo
Scuola Superiore Sant'Anna Scuola Superiore Sant'Anna
Email: nicosambo@gmail.com Email: nicosambo@gmail.com
Victor Lopez Victor Lopez
Telefonica Telefonica
Email: victor.lopezalvarez@telefonica.com Email: victor.lopezalvarez@telefonica.com
G. Galimberti G. Galimberti
Cisco Cisco
Email: ggalimbe@cisco.com Email: ggalimbe@cisco.com
Giovanni Martinelli Giovanni Martinelli
Cisco Cisco
Email: giomarti@cisco.com Email: giomarti@cisco.com
AUGE Jean Luc Jean Luc Auge
Orange Orange
Email: jeanluc.auge@orange.com Email: jeanluc.auge@orange.com
LE ROUZIC Esther Esther Le Rouzic
Orange Orange
Email: esther.lerouzic@orange.com Email: esther.lerouzic@orange.com
Julien Meuric Julien Meuric
Orange Orange
Email: julien.meuric@orange.com Email: julien.meuric@orange.com
Dieter Beller Dieter Beller
 End of changes. 36 change blocks. 
116 lines changed or deleted 289 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/