draft-ietf-ccamp-optical-impairment-topology-yang-04.txt   draft-ietf-ccamp-optical-impairment-topology-yang-05.txt 
CCAMP Working Group Y. Lee CCAMP Working Group Y. Lee
Internet-Draft SKKU (Sung Kyun Kwan University) Internet-Draft SKKU (Sung Kyun Kwan University)
Intended status: Standards Track JL. Auge Intended status: Standards Track JL. Auge
Expires: March 12, 2021 Orange Expires: May 6, 2021 Orange
V. Lopez V. Lopez
Telefonica Telefonica
G. Galimberti G. Galimberti
Cisco Cisco
D. Beller D. Beller
Nokia Nokia
September 8, 2020 November 2, 2020
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-04 draft-ietf-ccamp-optical-impairment-topology-yang-05
Abstract Abstract
In order to provision an optical connection through optical networks, In order to provision an optical connection through optical networks,
a combination of path continuity, resource availability, and a combination of path continuity, resource availability, and
impairment constraints must be met to determine viable and optimal impairment constraints must be met to determine viable and optimal
paths through the network. The determination of appropriate paths is paths through the network. The determination of appropriate paths is
known as Impairment-Aware Routing and Wavelength Assignment (IA-RWA) known as Impairment-Aware Routing and Wavelength Assignment (IA-RWA)
for WSON, while it is known as Impairment-Aware Routing and Spectrum for WSON, while it is known as Impairment-Aware Routing and Spectrum
Assigment (IA-RSA) for SSON. Assigment (IA-RSA) for SSON.
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 12, 2021. This Internet-Draft will expire on May 6, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 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 . . . . . . . . . . . . . . . . . . . . . 6 2.3. OMS Media Links . . . . . . . . . . . . . . . . . . . . . 7
2.3.1. Optical Tributary Signal (OTSi) . . . . . . . . . . . 7 2.3.1. Optical Tributary Signal (OTSi) . . . . . . . . . . . 8
2.3.2. Optical Tributary Signal Group (OTSiG) . . . . . . . 7 2.3.2. Optical Tributary Signal Group (OTSiG) . . . . . . . 8
2.3.3. Media Channel (MC) . . . . . . . . . . . . . . . . . 8 2.3.3. Media Channel (MC) . . . . . . . . . . . . . . . . . 9
2.3.4. Media Channel Group (MCG) . . . . . . . . . . . . . . 9 2.3.4. Media Channel Group (MCG) . . . . . . . . . . . . . . 10
2.4. Amplifiers . . . . . . . . . . . . . . . . . . . . . . . 10 2.4. Amplifiers . . . . . . . . . . . . . . . . . . . . . . . 11
2.5. Transponders . . . . . . . . . . . . . . . . . . . . . . 11 2.5. Transponders . . . . . . . . . . . . . . . . . . . . . . 12
2.6. WSS/Filter . . . . . . . . . . . . . . . . . . . . . . . 11 2.5.1. Application Codes . . . . . . . . . . . . . . . . . . 12
2.7. Optical Fiber . . . . . . . . . . . . . . . . . . . . . . 11 2.5.2. Organizational Modes . . . . . . . . . . . . . . . . 13
2.8. ROADM Node Architectures . . . . . . . . . . . . . . . . 12 2.5.3. Explicit Modes . . . . . . . . . . . . . . . . . . . 14
2.5.4. Transponder Capabilities and Current Configuration . 14
2.6. WSS/Filter . . . . . . . . . . . . . . . . . . . . . . . 15
2.7. Optical Fiber . . . . . . . . . . . . . . . . . . . . . . 15
2.8. ROADM Node Architectures . . . . . . . . . . . . . . . . 16
2.8.1. Integrated ROADM Architecture with Integrated Optical 2.8.1. Integrated ROADM Architecture with Integrated Optical
Transponders . . . . . . . . . . . . . . . . . . . . 12 Transponders . . . . . . . . . . . . . . . . . . . . 16
2.8.2. Integrated ROADMs with Integrated Optical 2.8.2. Integrated ROADMs with Integrated Optical
Transponders and Single Channel Add/Drop Interfaces Transponders and Single Channel Add/Drop Interfaces
for Remote Optical Transponders . . . . . . . . . . . 13 for Remote Optical Transponders . . . . . . . . . . . 17
2.8.3. Disaggregated ROADMs Subdivided into Degree, 2.8.3. Disaggregated ROADMs Subdivided into Degree,
Add/Drop, and Optical Transponder Subsystems . . . . 14 Add/Drop, and Optical Transponder Subsystems . . . . 18
2.8.4. Optical Impairments Imposed by ROADM Nodes . . . . . 15 2.8.4. Optical Impairments Imposed by ROADM Nodes . . . . . 19
3. YANG Model (Tree Structure) . . . . . . . . . . . . . . . . . 17 3. YANG Model (Tree Structure) . . . . . . . . . . . . . . . . . 21
4. Optical Impairment Topology YANG Model . . . . . . . . . . . 20 4. Optical Impairment Topology YANG Model . . . . . . . . . . . 25
5. Security Considerations . . . . . . . . . . . . . . . . . . . 53 5. Security Considerations . . . . . . . . . . . . . . . . . . . 56
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 54 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 57
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 54 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.1. Normative References . . . . . . . . . . . . . . . . . . 54 8.1. Normative References . . . . . . . . . . . . . . . . . . 57
8.2. Informative References . . . . . . . . . . . . . . . . . 54 8.2. Informative References . . . . . . . . . . . . . . . . . 57
Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 56 Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 60
Appendix B. Additional Authors . . . . . . . . . . . . . . . . . 57 Appendix B. Additional Authors . . . . . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 61
1. Introduction 1. Introduction
In order to provision an optical connection (an optical path) through In order to provision an optical connection (an optical path) through
a wavelength switched optical networks (WSONs) or spectrum switched a wavelength switched optical networks (WSONs) or spectrum switched
optical networks (SSONs), a combination of path continuity, resource optical networks (SSONs), a combination of path continuity, resource
availability, and impairment constraints must be met to determine availability, and impairment constraints must be met to determine
viable and optimal paths through the network. The determination of viable and optimal paths through the network. The determination of
appropriate paths is known as Impairment-Aware Routing and Wavelength appropriate paths is known as Impairment-Aware Routing and Wavelength
Assignment (IA-RWA) [RFC6566] for WSON, while it is known as IA- Assignment (IA-RWA) [RFC6566] for WSON, while it is known as IA-
skipping to change at page 11, line 13 skipping to change at page 12, line 13
abstract as much as possible. abstract as much as possible.
One modeling consideration of the ROADM internal is to model power One modeling consideration of the ROADM internal is to model power
parameter through the ROADM, factoring the output power from the Pre- parameter through the ROADM, factoring the output power from the Pre-
Amplifier minus the ROADM power loss would give the input power to Amplifier minus the ROADM power loss would give the input power to
the Booster Amplifier. In other words, Power_in (@ ROADM Booster) = the Booster Amplifier. In other words, Power_in (@ ROADM Booster) =
Power_out (@ ROADM Pre-Amplifier) - Power_loss (@ ROADM WSS/Filter). Power_out (@ ROADM Pre-Amplifier) - Power_loss (@ ROADM WSS/Filter).
2.5. Transponders 2.5. Transponders
[Editor's note: The relationship between the transponder and the OTSi
in the YANG model described in Section 3 needs further clarification
and refinement.]
A Transponder is the element that sends and receives the optical A Transponder is the element that sends and receives the optical
signal from a fiber. A transponder is typically characterized by its signal from a DWDM network. A transponder can comprise one or more
data rate and the maximum distance the signal can travel. Channel transceivers. A transceiver can be seen as a pair of transmitter and
frequency, per channel input power, FEC and Modulation are also receiver, as defined in ITU-T Recommendation G.698.2 [G.698.2].
associated with a transponder. From a path computation point of
view, the selection of the compatible source and destination
transponders is an important factor for optical signal to traverse
through the fiber. There are three main approaches to determine
optical signal compatibility. Application Code based on G.698.2 is
one approach that only checks the code at both ends of the link.
Another approach is organization codes that are specific to an
organization or a vendor. The third approach is specify all the
relevant parameters explicitly, e.g., FEC type, Modulation type, etc.
[Editor's note: The current YANG model described in Section 3 with A transponder is typically characterized by its data/symbol rate and
respect to the relationship between the transponder attributes and the maximum distance the signal can travel. Other transponder
the OTSi will need to be investigated in the future revision] properties are: carrier frequency for the optical channels, output
power per channel, measured input power, modulation scheme, FEC, etc.
From a path computation perspective, the selection of the compatible
configuration of the source and the destination transceivers is an
important factor for optical signals to traverse through the DWDM
network.
The YANG model defines three different approaches to describe the
transceiver capabilities (called "modes") that are needed to
determine optical signal compatibility:
o Application Codes as defined in ITU-T Recommendation G.698.2
[G.698.2]
o Organizational Modes
o Explicit Modes
2.5.1. Application Codes
An application code represents a standard ITU-T G.698.2 optical
interface specification towards the realization of transversely
compatible DWDM systems. Two transceivers supporting the same
application code and a line system matching the constraints, defined
in ITU-T G.698.2, for that application code will interoperate.
2.5.2. Organizational Modes
Organizations like operator groups, industry fora, or equipment
vendors can define organizational modes, which will allow these
organizations to make use of advanced transceiver capabilities going
beyond existing standardized application codes. Such an
organizational mode is identified by the organization-identifier
attribute defining the scope and an operational-mode that is
meaningful within the scope of the organization. Hence, the two
attributes must always be considered together. Two transceivers are
inter-operable, if they have at least one (organization-identifier,
operational-mode) pair in common and if the supported carrier
frequency and power attributes have a matching range. This is a
necessary condition for path computation in the context of
organizational modes. An operational mode is a transceiver preset (a
configuration with well-defined parameter values) subsuming several
transceiver properties including:
o FEC type
o Modulation scheme
o Encoding (mapping of bit patterns to symbols in the constellation
diagram)
o Baud rate (symbol rate)
o Carrier bandwidth (typically measured in GHz)
The major reason for these transceiver presets is the fact that the
attribute values typically cannot be configured independently and are
therefore advertised as supported operational mode capabilities. It
is the responsibility of the organization to assign operational modes
and to ensure that operational modes are unique and not ambiguous
within the scope of the organization.
In addition to the transceiver properties subsumed by the operational
mode, optical power and carrier frequency related properties are
modeled separately, i.e., outside of the operational mode. This
modeling approach allows transponders using different transceiver
variants (e.g. optical modules) with slightly different power and/or
frequency range properties to interoperate without defining separate
operational modes. Different optical modules (pluggables) from
different suppliers typically have slightly different input and
output power ranges or may have slightly different carrier frequency
tuning ranges.
The received channel power and the received total power are two
parameters that can be measured by the receiver and can be provided
by the transceiver in order to allow a controller to determine the
expected performance of the end-to-end service taking into account
the optical impairments along the path.
2.5.3. Explicit Modes
The explicit mode allows to encode, explicitly, any subset of
parameters e.g., FEC type, Modulation type, etc, to enable a
controller entity to check for interoperability by means outside of
this draft. It shall be noted that using the explicit encoding does
not guarantee interoperability between two transceivers even in case
of identical parameter definitions. The explicit mode shall
therefore be used with care, but it could be useful when no common
Application Codes or Organizational Modes exist or the constraints of
common Application Codes or Organizational Modes cannot be met by the
line system.
2.5.4. Transponder Capabilities and Current Configuration
The YANG model described in Section 3 defines the optical transceiver
properties. They are divided between:
a. Optical transceiver capabilities, describing how it can be
configured
b. Current transceiver setting, indicating how it is currently
configured
The transceiver capabilities are described by the set of modes the
transceiver is supporting. Each mode MUST follow only one of the
three mode options defined above (choice in the YANG model). The
YANG model allows to describe the transceiver capabilities by mixing
different modes. A transceiver may support some ITU-T application
codes and in addition some organizational or explicit modes.
A transceiver mode description comprises the following properties:
o Supported transmitter tuning range with min/max nominal carrier
frequency [f_tx_min, f_tx_max]
o Supported transmitter tunability grid, the distance between two
adjacent carrier frequencies (in GHz)
o Supported transmitter power range [p_tx-min, p_tx_max]
o Supported receiver channel power range [p_rx-min, p_rx_max]
o Supported maximum total power, rx power for all channels fed into
the receiver
These optical transceiver properties are explicitly defined in the
model for explicit and organizational modes, while they are
implicitly defined for the application codes (see ITU-T G698.2
[G.698.2]).
The set of optical impairment limits, e.g., min OSNR, max PMD, max
CD, max PDL, Q-factor limit, are explicitly defined for the explicit
modes while they are defined implicitly for the application codes and
organizational modes.
It is possible that the set of parameter values defined for an
explicit mode may also be represented in form of an organizational
mode or one or more application codes. The "supported-mode"
container may provide two different lists with pointers to
application codes and organizational modes, respectively.
The current transponder configuration describes the properties of the
OTSi transmitted or received by the transceiver attached to a
specific transponder port.
Each OTSi has the following three pointer attributes modeled as
leafrefs:
o Pointer to the transponder instance containing the transceiver
terminating the OTSi
o Pointer to the transceiver instance terminating the OTSi
o Pointer to the currently configured transceiver mode
Additionally, the OTSi is described by the following frequency and
optical power related attributes:
o current carrier-frequency
o currently transmitted channel power
o currently received channel power
o currently received total power
2.6. WSS/Filter 2.6. WSS/Filter
WSS separates the incoming light input spectrally as well as WSS separates the incoming light input spectrally as well as
spatially, then chooses the wavelength that is of interest by spatially, then chooses the wavelength that is of interest by
deflecting it from the original optical path and then couple it to deflecting it from the original optical path and then couple it to
another optical fibre port. WSS/Filter is internal to ROADM. So another optical fibre port. WSS/Filter is internal to ROADM. So
this document does not model the inside of ROADM. this document does not model the inside of ROADM.
2.7. Optical Fiber 2.7. Optical Fiber
skipping to change at page 17, line 15 skipping to change at page 21, line 15
describes the connectivity for the Add and Drop paths of the ROADM. describes the connectivity for the Add and Drop paths of the ROADM.
These matrices are augmented with a new roadm-path-impairment matrix These matrices are augmented with a new roadm-path-impairment matrix
element, an add-path-impairment, and drop-path-impairment matrix element, an add-path-impairment, and drop-path-impairment matrix
element, respectively, which are defined as a pointer to the element, respectively, which are defined as a pointer to the
corresponding entry in the roadm-path-impairments list (leaf-ref). corresponding entry in the roadm-path-impairments list (leaf-ref).
[Editor's note: this section is still work in progress] [Editor's note: this section is still work in progress]
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/ augment /nw:networks/nw:network/nt:link/tet:te
tet:te-link-attributes: /tet:te-link-attributes:
+--ro OMS-attributes +--ro OMS-attributes
+--ro generalized-snr? decimal64 +--ro generalized-snr? l0-types-ext:snr
+--ro equalization-mode identityref +--ro equalization-mode identityref
+--ro (power-param)? +--ro (power-param)?
| +--:(channel-power) | +--:(channel-power)
| | +--ro nominal-channel-power? decimal64 | | +--ro nominal-channel-power? decimal64
| +--:(power-spectral-density) | +--:(power-spectral-density)
| +--ro nominal-power-spectral-density? decimal64 | +--ro nominal-power-spectral-density? decimal64
+--ro media-channel-group* [i] +--ro media-channel-group* [i]
| +--ro i int16 | +--ro i int16
| +--ro media-channels* [flexi-n] | +--ro media-channels* [flexi-n]
| +--ro flexi-n uint16 | +--ro flexi-n l0-types:flexi-n
| +--ro flexi-m? uint16 | +--ro flexi-m? l0-types:flexi-m
| +--ro OTSiG-ref? -> /nw:networks/network/node/tet:te/ | +--ro OTSiG-ref? leafref
tunnel-termination-point/OTSiG-element/OTSiG-identifier | +--ro OTSi-ref? leafref
| +--ro OTSi-ref? -> /nw:networks/network/node/tet:te/ +--ro OMS-elements* [elt-index]
tunnel-termination-point/ +--ro elt-index uint16
OTSiG-element[OTSiG-identifier=current()/../OTSiG-ref]/ +--ro uid? string
OTSiG-container/OTSi/OTSi-carrier-id +--ro type identityref
+--ro OMS-elements* [elt-index] +--ro element
+--ro elt-index uint16 +--ro (element)?
+--ro uid? string +--:(amplifier)
+--ro type identityref | +--ro amplifier
+--ro element | +--ro type-variety string
+--ro (element)? | +--ro operational
+--:(amplifier) | +--ro actual-gain
| +--ro amplifier | | decimal64
| +--ro type-variety string | +--ro tilt-target
| +--ro operational | | decimal64
| +--ro actual-gain decimal64 | +--ro out-voa
| +--ro tilt-target decimal64 | | decimal64
| +--ro out-voa decimal64 | +--ro in-voa
| +--ro in-voa decimal64 | | decimal64
| +--ro (power-param)? | +--ro (power-param)?
| +--:(channel-power) | +--:(channel-power)
| | +--ro nominal-channel-power? | | +--ro nominal-channel-power?
decimal64 | | decimal64
| +--:(power-spectral-density) | +--:(power-spectral-density)
| +--ro nominal-power-spectral-density? | +--ro nominal-power-spectral-density?
decimal64 | decimal64
+--:(fiber) +--:(fiber)
| +--ro fiber | +--ro fiber
| +--ro type-variety string | +--ro type-variety string
| +--ro length decimal64 | +--ro length decimal64
| +--ro loss-coef decimal64 | +--ro loss-coef decimal64
| +--ro total-loss decimal64 | +--ro total-loss decimal64
| +--ro pmd? decimal64 | +--ro pmd? decimal64
| +--ro conn-in? decimal64 | +--ro conn-in? decimal64
| +--ro conn-out? decimal64 | +--ro conn-out? decimal64
+--:(concentratedloss) +--:(concentratedloss)
+--ro concentratedloss +--ro concentratedloss
+--ro loss? decimal64 +--ro loss? decimal64
augment /nw:networks/nw:network/nw:node/tet:te/ augment /nw:networks/nw:network/nw:node/tet:te
tet:tunnel-termination-point: /tet:tunnel-termination-point:
+--ro OTSiG-element* [OTSiG-identifier] +--ro otsi-group* [otsi-group-id]
| +--ro OTSiG-identifier int16 | +--ro otsi-group-id int16
| +--ro OTSiG-container | +--ro otsi* [otsi-carrier-id]
| +--ro OTSi* [OTSi-carrier-id] | +--ro otsi-carrier-id int16
| +--ro OTSi-carrier-id int16 | +--ro transponder-ref? leafref
| +--ro OTSi-carrier-frequency? decimal64 | +--ro transceiver-ref? leafref
| +--ro OTSi-signal-width? decimal64 | +--ro configured-mode? leafref
| +--ro channel-delta-power? decimal64 | +--ro OTSi-carrier-frequency? frequency-thz
+--ro transponders-list* [transponder-id] | +--ro tx-channel-power? dbm-t
+--ro transponder-id uint32 | +--ro rx-channel-power? dbm-t
+--ro (mode)? | +--ro rx-total-power? dbm-t
| +--:(G.692.2) +--ro transponder* [transponder-id]
| | +--ro standard-mode? standard-mode +--ro transponder-id uint32
| +--:(organizational-mode) +--ro transceiver* [transceiver-id]
| | +--ro operational-mode? operational-mode +--ro transceiver-id uint32
| | +--ro organization-identifier? vendor-identifier +--ro supported-modes
| +--:(explicit-mode) +--ro supported-mode* [mode-id]
| +--ro available-modulation-types* identityref +--ro mode-id string
| +--ro configured-modulation-type? identityref +--ro (mode)
| +--ro available-baud-rates* uint32 +--:(G.698.2)
| +--ro configured-baud-rate? uint32 | +--ro standard-mode? standard-mode
| +--ro available-FEC-types* identityref +--:(organizational-mode)
| +--ro configured-FEC-type? identityref | +--ro organizational-mode
| +--ro FEC-code-rate? decimal64 | +--ro operational-mode?
| +--ro FEC-threshold? decimal64 | | operational-mode
+--ro power? int32 | +--ro organization-identifier?
+--ro power-min? int32 | | organization-identifier
+--ro power-max? int32 | +--ro min-central-frequency?
augment /nw:networks/nw:network/nw:node/tet:te/ | | frequency-thz
tet:tunnel-termination-point: | +--ro max-central-frequency?
+--ro transponder-list* [carrier-id] | | frequency-thz
+--ro carrier-id uint32 | +--ro minimum-channel-spacing?
augment /nw:networks/nw:network/nw:node/tet:te/ | | frequency-ghz
tet:te-node-attributes: | +--ro tx-channel-power-min? dbm-t
+--ro roadm-path-impairments* [roadm-path-impairments-id] | +--ro tx-channel-power-max? dbm-t
+--ro roadm-path-impairments-id uint32 | +--ro rx-channel-power-min? dbm-t
+--ro (impairment-type)? | +--ro rx-channel-power-max? dbm-t
+--:(roadm-express-path) | +--ro rx-total-power-max? dbm-t
| +--ro roadm-express-path +--:(explicit-mode)
| +--ro roadm-pmd? decimal64 +--ro explicit-mode
| +--ro roadm-cd? decimal64 +--ro supported-modes
| +--ro roadm-pdl? decimal64 | +--ro supported-application-codes*
| +--ro roadm-inband-crosstalk? decimal64 | | -> ../../mode-id
| +--ro roadm-maxloss? decimal64 | +--ro supported-organizational-modes*
+--:(roadm-add-path) | -> ../../mode-id
| +--ro roadm-add-path +--ro line-coding-bitrate?
| +--ro roadm-pmd? decimal64 | identityref
| +--ro roadm-cd? decimal64 +--ro max-polarization-mode-dispersion?
| +--ro roadm-pdl? decimal64 | decimal64
| +--ro roadm-inband-crosstalk? decimal64 +--ro max-chromatic-dispersion?
| +--ro roadm-maxloss? decimal64 | decimal64
| +--ro roadm-pmax? decimal64 +--ro chromatic-and-polarization-dispersion-penalty* []
| +--ro roadm-osnr? decimal64 | +--ro chromatic-dispersion
| +--ro roadm-noise-figure? decimal64 | | decimal64
+--:(roadm-drop-path) | +--ro polarization-mode-dispersion
+--ro roadm-drop-path | | decimal64
+--ro roadm-pmd? decimal64 | +--ro penalty
+--ro roadm-cd? decimal64 | decimal64
+--ro roadm-pdl? decimal64 +--ro max-diff-group-delay?
+--ro roadm-inband-crosstalk? decimal64 | int32
+--ro roadm-maxloss? decimal64 +--ro max-polarization-dependent-loss?
+--ro roadm-minloss? decimal64 | decimal64
+--ro roadm-typloss? decimal64 +--ro available-modulation-type?
+--ro roadm-pmin? decimal64 | identityref
+--ro roadm-pmax? decimal64 +--ro OTSi-carrier-bandwidth?
+--ro roadm-ptyp? decimal64 | frequency-ghz
+--ro roadm-osnr? decimal64 +--ro min-OSNR?
+--ro roadm-noise-figure? decimal64 | snr
augment /nw:networks/nw:network/nw:node/tet:te/ +--ro min-Q-factor?
tet:information-source-entry/tet:connectivity-matrices: | int32
+--ro roadm-path-impairments? -> ../../../ +--ro available-baud-rate?
tet:te-node-attributes/roadm-path-impairments/ | uint32
roadm-path-impairments-id +--ro available-FEC-type?
augment /nw:networks/nw:network/nw:node/tet:te/ | identityref
tet:information-source-entry/tet:connectivity-matrices/ +--ro FEC-code-rate?
tet:connectivity-matrix: | decimal64
+--ro roadm-path-impairments? -> ../../../../ +--ro FEC-threshold?
tet:te-node-attributes/roadm-path-impairments/ | decimal64
roadm-path-impairments-id +--ro min-central-frequency?
augment /nw:networks/nw:network/nw:node/tet:te/ | frequency-thz
tet:te-node-attributes/tet:connectivity-matrices: +--ro max-central-frequency?
+--ro roadm-path-impairments? -> ../../roadm-path-impairments/ | frequency-thz
roadm-path-impairments-id +--ro minimum-channel-spacing?
augment /nw:networks/nw:network/nw:node/tet:te/ | frequency-ghz
tet:te-node-attributes/tet:connectivity-matrices/ +--ro tx-channel-power-min?
tet:connectivity-matrix: | dbm-t
+--ro roadm-path-impairments? -> ../../../ +--ro tx-channel-power-max?
roadm-path-impairments/roadm-path-impairments-id | dbm-t
augment /nw:networks/nw:network/nw:node/tet:te/ +--ro rx-channel-power-min?
tet:tunnel-termination-point/tet:local-link-connectivities: | dbm-t
+--ro add-path-impairments? -> ../../../ +--ro rx-channel-power-max?
tet:te-node-attributes/roadm-path-impairments/ | dbm-t
roadm-path-impairments-id +--ro rx-total-power-max?
+--ro drop-path-impairments? -> ../../../ dbm-t
tet:te-node-attributes/roadm-path-impairments/ augment /nw:networks/nw:network/nw:node/tet:te
roadm-path-impairments-id /tet:tunnel-termination-point:
augment /nw:networks/nw:network/nw:node/tet:te/ +--ro sliceable-transponder-list* [carrier-id]
tet:tunnel-termination-point/tet:local-link-connectivities/ +--ro carrier-id uint32
tet:local-link-connectivity: augment /nw:networks/nw:network/nw:node/tet:te
+--ro add-path-impairments? -> ../../../../ /tet:te-node-attributes:
tet:te-node-attributes/roadm-path-impairments/ +--ro roadm-path-impairments* [roadm-path-impairments-id]
roadm-path-impairments-id +--ro roadm-path-impairments-id uint32
+--ro drop-path-impairments? -> ../../../../ +--ro (impairment-type)?
tet:te-node-attributes/roadm-path-impairments/ +--:(roadm-express-path)
roadm-path-impairments-id | +--ro roadm-express-path
| +--ro roadm-pmd? decimal64
| +--ro roadm-cd? decimal64
| +--ro roadm-pdl? decimal64
| +--ro roadm-inband-crosstalk? decimal64
| +--ro roadm-maxloss? decimal64
+--:(roadm-add-path)
| +--ro roadm-add-path
| +--ro roadm-pmd? decimal64
| +--ro roadm-cd? decimal64
| +--ro roadm-pdl? decimal64
| +--ro roadm-inband-crosstalk? decimal64
| +--ro roadm-maxloss? decimal64
| +--ro roadm-pmax? decimal64
| +--ro roadm-osnr? l0-types-ext:snr
| +--ro roadm-noise-figure? decimal64
+--:(roadm-drop-path)
+--ro roadm-drop-path
+--ro roadm-pmd? decimal64
+--ro roadm-cd? decimal64
+--ro roadm-pdl? decimal64
+--ro roadm-inband-crosstalk? decimal64
+--ro roadm-maxloss? decimal64
+--ro roadm-minloss? decimal64
+--ro roadm-typloss? decimal64
+--ro roadm-pmin? decimal64
+--ro roadm-pmax? decimal64
+--ro roadm-ptyp? decimal64
+--ro roadm-osnr? l0-types-ext:snr
+--ro roadm-noise-figure? decimal64
augment /nw:networks/nw:network/nw:node/tet:te
/tet:information-source-entry/tet:connectivity-matrices:
+--ro roadm-path-impairments? leafref
augment /nw:networks/nw:network/nw:node/tet:te
/tet:information-source-entry/tet:connectivity-matrices
/tet:connectivity-matrix:
+--ro roadm-path-impairments? leafref
augment /nw:networks/nw:network/nw:node/tet:te
/tet:te-node-attributes/tet:connectivity-matrices:
+--ro roadm-path-impairments?
-> ../../roadm-path-impairments/roadm-path-impairments-id
augment /nw:networks/nw:network/nw:node/tet:te
/tet:te-node-attributes/tet:connectivity-matrices
/tet:connectivity-matrix:
+--ro roadm-path-impairments? leafref
augment /nw:networks/nw:network/nw:node/tet:te
/tet:tunnel-termination-point
/tet:local-link-connectivities:
+--ro add-path-impairments? leafref
+--ro drop-path-impairments? leafref
augment /nw:networks/nw:network/nw:node/tet:te
/tet:tunnel-termination-point
/tet:local-link-connectivities
/tet:local-link-connectivity:
+--ro add-path-impairments? leafref
+--ro drop-path-impairments? leafref
4. Optical Impairment Topology YANG Model 4. Optical Impairment Topology YANG Model
[Editor's note: YANG code below may have to be updated before [Editor's note: YANG code below may have to be updated before
submission!] submission!]
<CODE BEGINS> <CODE BEGINS>
module ietf-optical-impairment-topology { module ietf-optical-impairment-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml" namespace "urn:ietf:params:xml"
+":ns:yang:ietf-optical-impairment-topology"; +":ns:yang:ietf-optical-impairment-topology";
prefix "optical-imp-topo"; prefix "optical-imp-topo";
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "nt"; prefix "nt";
} }
import ietf-te-topology { import ietf-te-topology {
prefix "tet"; prefix "tet";
} }
skipping to change at page 21, line 16 skipping to change at page 26, line 22
import ietf-network-topology { import ietf-network-topology {
prefix "nt"; prefix "nt";
} }
import ietf-te-topology { import ietf-te-topology {
prefix "tet"; prefix "tet";
} }
import ietf-layer0-types { import ietf-layer0-types {
prefix "layer0-types"; prefix "l0-types";
}
import ietf-layer0-types-ext {
prefix "l0-types-ext";
} }
organization organization
"IETF CCAMP Working Group"; "IETF CCAMP Working Group";
contact contact
"Editor: Young Lee <younglee.tx@gmail.com> "Editor: Young Lee <younglee.tx@gmail.com>
Editor: Haomian Zheng <zhenghaomian@huawei.com> Editor: Haomian Zheng <zhenghaomian@huawei.com>
Editor: Nicola Sambo <nicosambo@gmail.com> Editor: Nicola Sambo <nicosambo@gmail.com>
Editor: Victor Lopez <victor.lopezalvarez@telefonica.com> Editor: Victor Lopez <victor.lopezalvarez@telefonica.com>
skipping to change at page 21, line 50 skipping to change at page 27, line 13
impairment-aware optical networks. impairment-aware optical networks.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2019 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."; (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision 2020-03-09 { // RFC Ed.: replace XXXX with actual RFC number and remove
// this note
// replace the revision date with the module publication date
// the format is (year-month-day)
revision 2020-10-13 {
description description
"Initial Version"; "Initial Version";
reference reference
"RFC XXXX: A Yang Data Model for Impairment-aware "RFC XXXX: A Yang Data Model for Impairment-aware
Optical Networks"; Optical Networks";
} }
// identity // identity
identity modulation { identity modulation {
skipping to change at page 24, line 4 skipping to change at page 29, line 23
} }
enum G.653 { enum G.653 {
description "G.653 Dispersion Shifted Fiber"; description "G.653 Dispersion Shifted Fiber";
} }
enum G.655 { enum G.655 {
description "G.655 Non-Zero Dispersion Shifted Fiber"; description "G.655 Non-Zero Dispersion Shifted Fiber";
} }
enum G.656 { enum G.656 {
description "G.656 Non-Zero Dispersion for Wideband description "G.656 Non-Zero Dispersion for Wideband
Optical Transport"; Optical Transport";
} }
enum G.657 { enum G.657 {
description "G.657 Bend-Insensitive Fiber"; description "G.657 Bend-Insensitive Fiber";
} }
} }
description description
"ITU-T based fiber-types"; "ITU-T based fiber-types";
} }
/*temporary defined here for disalignment with*/
/* ietf-layer0-types module*/
typedef operational-mode {
type string;
description
"Vendor-specific mode that guarantees
interoperability.";
reference "ITU-T G.698.2 (11/2018)";
}
// temporary defined here for disalignment with
//ietf-layer0-types module
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)";
}
// temporary defined here for disalignment
//with ietf-layer0-types module
typedef vendor-identifier {
type string;
description
"vendor identifier that uses vendor-specific mode";
reference
"RFC7581: Routing and Wavelength Assignment Information
Encoding for Wavelength Switched Optical Networks";
}
// grouping // grouping
grouping transponder-attributes { grouping transponder-attributes {
description "Configuration of an optical transponder"; description "Configuration of an optical transponder";
leaf-list available-modulation-types { leaf-list available-modulation-types {
type identityref { type identityref {
base modulation; base modulation;
} }
config false; config false;
skipping to change at page 26, line 42 skipping to change at page 31, line 25
description description
"Threshold on the BER, for which FEC "Threshold on the BER, for which FEC
is able to correct errors"; is able to correct errors";
} }
} }
grouping sliceable-transponder-attributes { grouping sliceable-transponder-attributes {
description description
"Configuration of a sliceable transponder."; "Configuration of a sliceable transponder.";
list transponder-list { list sliceable-transponder-list {
key "carrier-id"; key "carrier-id";
config false; config false;
description "List of carriers"; description "List of carriers";
leaf carrier-id { leaf carrier-id {
type uint32; type uint32;
config false; config false;
description "Identifier of the carrier"; description "Identifier of the carrier";
} }
} }
} }
grouping optical-fiber-data { grouping optical-fiber-data {
description description
"optical link (fiber) attributes with impairment data"; "optical link (fiber) attributes with impairment data";
leaf fiber-type { leaf fiber-type {
type fiber-type; type fiber-type;
config false; config false;
description "fiber-type"; description "fiber-type";
} }
skipping to change at page 28, line 18 skipping to change at page 32, line 49
type decimal64 { type decimal64 {
fraction-digits 5; fraction-digits 5;
} }
units "ps/nm/km"; units "ps/nm/km";
config false; config false;
description description
"Cromatic Dispersion"; "Cromatic Dispersion";
} }
leaf osnr { leaf osnr {
type decimal64 { type l0-types-ext:snr;
fraction-digits 5;
}
units "dB";
config false; config false;
description description
"Optical Signal-to-Noise Ratio (OSNR) estimated "Optical Signal-to-Noise Ratio (OSNR) estimated
at the receiver"; at the receiver";
} }
leaf sigma { leaf sigma {
type decimal64 { type decimal64 {
fraction-digits 5; fraction-digits 5;
} }
skipping to change at page 29, line 47 skipping to change at page 34, line 29
type decimal64 { type decimal64 {
fraction-digits 5; fraction-digits 5;
} }
units "ps/nm/km"; units "ps/nm/km";
config false; config false;
description description
"per channel Cromatic Dispersion"; "per channel Cromatic Dispersion";
} }
leaf ch-osnr { leaf ch-osnr {
type decimal64 { type l0-types-ext:snr;
fraction-digits 5;
}
units "dB";
config false; config false;
description description
"per channel Optical Signal-to-Noise Ratio "per channel Optical Signal-to-Noise Ratio
(OSNR) estimated at the receiver"; (OSNR) estimated at the receiver";
} }
leaf q-factor { leaf q-factor {
type decimal64 { type decimal64 {
fraction-digits 5; fraction-digits 5;
} }
units "dB"; units "dB";
config false; config false;
description description
"q-factor estimated at the receiver"; "q-factor estimated at the receiver";
} }
} }
grouping standard-mode { /*
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";
leaf standard-mode {
type standard-mode;
config false;
description
"G.698.2 standard mode";
}
}
grouping organizational-mode {
description
"Transponder operational mode supported by organizations or
vendor";
leaf operational-mode {
type operational-mode;
config false;
description
"configured organization- or vendor-specific
application identifiers (AI) supported by the transponder";
}
leaf organization-identifier {
type vendor-identifier;
config false;
description
"organization identifier that uses organizational
mode";
}
}
/*
* Identities * Identities
*/ */
identity type-element { identity type-element {
description description
"Base identity for element type"; "Base identity for element type";
} }
identity Fiber { identity Fiber {
base type-element; base type-element;
description description
"Fiber element"; "Fiber element";
} }
identity Roadm { identity Roadm {
base type-element; base type-element;
skipping to change at page 37, line 22 skipping to change at page 41, line 8
"This is the maximum (per carrier) power level "This is the maximum (per carrier) power level
permitted at the add block input ports, permitted at the add block input ports,
that can be handled by the ROADM node. that can be handled by the ROADM node.
This may reflect either add amplifier power This may reflect either add amplifier power
contraints or WSS adjustment limits. contraints or WSS adjustment limits.
Higher power transponders would need to have Higher power transponders would need to have
their launch power reduced their launch power reduced
to this value or lower"; to this value or lower";
} }
leaf roadm-osnr { leaf roadm-osnr {
type decimal64 { type l0-types-ext:snr;
fraction-digits 5;
}
units "dB";
description description
"Optical Signal-to-Noise Ratio (OSNR). "Optical Signal-to-Noise Ratio (OSNR).
If the add path contains the ability to adjust the If the add path contains the ability to adjust the
carrier power levels into an add path amplifier carrier power levels into an add path amplifier
(if present) to a target value, (if present) to a target value,
this reflects the OSNR contribution of the this reflects the OSNR contribution of the
add amplifier assuming this target value is obtained. add amplifier assuming this target value is obtained.
The worst case OSNR based on the input power and The worst case OSNR based on the input power and
NF calculation method, and this value, should be used NF calculation method, and this value, should be used
(if both are defined)."; (if both are defined).";
skipping to change at page 41, line 14 skipping to change at page 44, line 48
for example, to hit target power levels into a for example, to hit target power levels into a
drop path amplifier,or simply,to reduce the drop path amplifier,or simply,to reduce the
power of a "strong" carrier(due to ripple,for example), power of a "strong" carrier(due to ripple,for example),
then the use of the ROADM input power levels and then the use of the ROADM input power levels and
the above drop losses is not appropriate. the above drop losses is not appropriate.
This parameter corresponds to the typical case This parameter corresponds to the typical case
per carrier power levels expected per carrier power levels expected
at the output of the drop block."; at the output of the drop block.";
} }
leaf roadm-osnr { leaf roadm-osnr {
type decimal64 { type l0-types-ext:snr;
fraction-digits 5;
}
units "dB";
description description
"Optical Signal-to-Noise Ratio (OSNR). "Optical Signal-to-Noise Ratio (OSNR).
Expected OSNR contribution of the drop path Expected OSNR contribution of the drop path
amplifier(if present) amplifier(if present)
for the case of additional drop path loss for the case of additional drop path loss
(before this amplifier) (before this amplifier)
in order to hit a target power level (per carrier). in order to hit a target power level (per carrier).
If both, the OSNR based on the ROADM If both, the OSNR based on the ROADM
input power level input power level
(Pcarrier = (Pcarrier =
skipping to change at page 43, line 4 skipping to change at page 46, line 34
leaf nominal-power-spectral-density{ leaf nominal-power-spectral-density{
type decimal64 { type decimal64 {
fraction-digits 16; fraction-digits 16;
} }
units W/Hz ; units W/Hz ;
description description
" Reference power spectral density after " Reference power spectral density after
the ROADM or after the out-voa. the ROADM or after the out-voa.
Typical value : 3.9 E-14, resolution 0.1nW/MHz"; Typical value : 3.9 E-14, resolution 0.1nW/MHz";
} }
} }
} }
} }
grouping oms-general-optical-params { grouping oms-general-optical-params {
description "OMS link optical parameters"; description "OMS link optical parameters";
leaf generalized-snr { leaf generalized-snr {
type decimal64 { type l0-types-ext:snr;
fraction-digits 5;
}
units "dB@0.1nm";
description "generalized snr"; description "generalized snr";
} }
leaf equalization-mode{ leaf equalization-mode{
type identityref { type identityref {
base type-power-mode; base type-power-mode;
} }
mandatory true; mandatory true;
description "equalization mode"; description "equalization mode";
} }
uses power-param; uses power-param;
skipping to change at page 43, line 26 skipping to change at page 47, line 4
description "generalized snr"; description "generalized snr";
} }
leaf equalization-mode{ leaf equalization-mode{
type identityref { type identityref {
base type-power-mode; base type-power-mode;
} }
mandatory true; mandatory true;
description "equalization mode"; description "equalization mode";
} }
uses power-param; uses power-param;
} }
grouping OTSiG { grouping OTSiG {
description "OTSiG definition , representing client description "OTSiG definition , representing client
digital information stream supported by 1 or more OTSi"; digital information stream supported by 1 or more OTSi";
container OTSiG-container { list otsi {
config false; key "otsi-carrier-id";
description config false;
"the container contains the related list of OTSi.
The list could also be of only 1 element";
list OTSi {
key "OTSi-carrier-id";
description description
"list of OTSi's under OTSi-G"; "list of OTSi contained in 1 OTSiG.
leaf OTSi-carrier-id { The list could also be of only 1 element";
leaf otsi-carrier-id {
type int16; type int16;
description "OTSi carrier-id"; description "OTSi carrier-id";
} }
leaf OTSi-carrier-frequency {
type decimal64 {
fraction-digits 3;
}
units GHz;
config false;
description
"OTSi carrier frequency";
/*any OTSi as signal generated by transceiver and*/
/* attached to a transponder.*/
leaf transponder-ref {
type leafref {
path "/nw:networks/nw:network/nw:node/tet:te" +
"/tet:tunnel-termination-point" +
"/transponder/transponder-id";
}
description
"Reference to the configured transponder";
} }
leaf OTSi-signal-width { leaf transceiver-ref {
type decimal64 { type leafref {
fraction-digits 3; path "/nw:networks/nw:network/nw:node/tet:te" +
} "/tet:tunnel-termination-point/"
units GHz; +"transponder[transponder-id=current()"
config false; +"/../transponder-ref]/"
description + "transceiver/transceiver-id" ;
"OTSi signal width"; }
description
"Reference to the configured transceiver " ;
} }
leaf channel-delta-power { leaf configured-mode {
type decimal64 { type leafref {
fraction-digits 2; path "/nw:networks/nw:network/nw:node/tet:te" +
"/tet:tunnel-termination-point/"
+"transponder[transponder-id=current()"
+"/../transponder-ref]/"+
"transceiver[transceiver-id=current()/"+
"../transceiver-ref]/supported-modes/"+
"supported-mode/mode-id";
} }
units dB; description
config false; "Reference to the configured mode for transceiver
description compatibility approach";
"optional ; delta power to ref channel
input-power applied
to this media channel";
} }
uses l0-types-ext:common-transceiver-configured-param;
} } // OTSi list
} // 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";
} }
list media-channels { list media-channels {
key "flexi-n"; key "flexi-n";
description description
"list of media channels represented as (n,m)"; "list of media channels represented as (n,m)";
uses layer0-types:flexi-grid-channel;
// this grouping add both n.m values
uses l0-types:flexi-grid-frequency-slot;
leaf OTSiG-ref { leaf OTSiG-ref {
type leafref { type leafref {
path "/nw:networks/nw:network/nw:node/tet:te" + path "/nw:networks/nw:network/nw:node/tet:te" +
"/tet:tunnel-termination-point" + "/tet:tunnel-termination-point" +
"/OTSiG-element/OTSiG-identifier" ; "/otsi-group/otsi-group-id" ;
} }
description description
"Reference to the OTSiG list to get OTSiG "Reference to the otsi-group list to get otsi-group
identifier of the identifier of the
OSiG carried by this media channel OTSiG carried by this media channel
that reports the transient stat"; that reports the transient stat";
} }
leaf OTSi-ref { leaf OTSi-ref {
type leafref { type leafref {
path "/nw:networks/nw:network/nw:node/tet:te" + path "/nw:networks/nw:network/nw:node/tet:te" +
"/tet:tunnel-termination-point/" "/tet:tunnel-termination-point/"
+"OTSiG-element[OTSiG-identifier=current()" +"otsi-group[otsi-group-id=current()"
+"/../OTSiG-ref]/" +"/../OTSiG-ref]/"
+ "OTSiG-container/OTSi/OTSi-carrier-id" ; + "otsi/otsi-carrier-id" ;
} }
description description
"Reference to the OTSi list supporting the "Reference to the otsi list supporting
related OTSiG" ; the related OTSiG to get otsi identifier";
} }
} // media channels list } // media channels list
} // media-channel-groups list } // media-channel-groups list
} // media media-channel-groups grouping } // media media-channel-groups grouping
grouping oms-element { grouping oms-element {
description "OMS description"; description "OMS description";
list OMS-elements { list OMS-elements {
key "elt-index"; key "elt-index";
skipping to change at page 47, line 23 skipping to change at page 51, line 11
when "/nw:networks/nw:network/nw:network-types" when "/nw:networks/nw:network/nw:network-types"
+"/tet:te-topology/optical-imp-topo:optical-impairment-topology"{ +"/tet:te-topology/optical-imp-topo:optical-impairment-topology"{
description description
"This augment is only valid for Impairment with non-sliceable "This augment is only valid for Impairment with non-sliceable
transponder model"; transponder model";
} }
description description
"Tunnel termination point augmentation for non-sliceable "Tunnel termination point augmentation for non-sliceable
transponder model."; transponder model.";
list OTSiG-element { list otsi-group {
key "OTSiG-identifier"; key "otsi-group-id";
config false; config false;
description description
"the list of possible OTSiG representing client digital "the list of possible OTSiG representing client digital
stream"; stream";
leaf OTSiG-identifier { leaf otsi-group-id {
type int16; type int16;
description "index of OTSiG element"; description "index of otsi-group element";
} }
uses OTSiG; uses OTSiG;
} } // list of OTSiG
list transponders-list {
key "transponder-id";
config false;
description "list of transponders";
leaf transponder-id {
type uint32;
description "transponder identifier";
}
choice mode {
description "standard mode, organizational mode or
explicit mode";
case G.692.2 {
uses standard-mode;
}
case organizational-mode { list transponder {
uses organizational-mode; key "transponder-id";
} config false;
description "list of transponder";
leaf transponder-id {
type uint32;
description "transponder identifier";
}
case explicit-mode { list transceiver {
uses transponder-attributes; key "transceiver-id";
} config false;
description "list of transceiver related to a transponder";
leaf transceiver-id {
type uint32;
description "transceiver identifier";
} }
uses l0-types-ext:transceiver-capabilities;
} // end of list of transceiver
leaf power { } // end list of transponder
type int32;
units "dBm";
config false;
description "per channel power";
}
leaf power-min { } // end of augment
type int32;
units "dBm";
config false;
description "minimum power of the transponder";
}
leaf power-max {
type int32;
units "dBm";
config false;
description "maximum power of the transponder";
}
}
}
augment "/nw:networks/nw:network/nw:node/tet:te" augment "/nw:networks/nw:network/nw:node/tet:te"
+ "/tet:tunnel-termination-point" { + "/tet:tunnel-termination-point" {
when "/nw:networks/nw:network/nw:network-types" when "/nw:networks/nw:network/nw:network-types"
+"/tet:te-topology/" +"/tet:te-topology/"
+ "optical-imp-topo:optical-impairment-topology" { + "optical-imp-topo:optical-impairment-topology" {
description description
"This augment is only valid for optical impairment "This augment is only valid for optical impairment
with sliceable transponder model"; with sliceable transponder model";
} }
skipping to change at page 56, line 6 skipping to change at page 59, line 17
DOI 10.17487/RFC8453, August 2018, DOI 10.17487/RFC8453, August 2018,
<https://www.rfc-editor.org/info/rfc8453>. <https://www.rfc-editor.org/info/rfc8453>.
[I-D.ietf-teas-yang-te-topo] [I-D.ietf-teas-yang-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for Traffic Engineering (TE) O. Dios, "YANG Data Model for Traffic Engineering (TE)
Topologies", draft-ietf-teas-yang-te-topo-22 (work in Topologies", draft-ietf-teas-yang-te-topo-22 (work in
progress), June 2019. progress), June 2019.
[I-D.ietf-ccamp-wson-yang] [I-D.ietf-ccamp-wson-yang]
Zheng, H., Lee, Y., Guo, A., Lopezalvarez, V., and D. Zheng, H., Lee, Y., Guo, A., Lopez, V., and D. King, "A
King, "A YANG Data Model for WSON (Wavelength Switched YANG Data Model for WSON (Wavelength Switched Optical
Optical Networks)", draft-ietf-ccamp-wson-yang-25 (work in Networks)", draft-ietf-ccamp-wson-yang-27 (work in
progress), May 2020. progress), October 2020.
[I-D.ietf-ccamp-layer0-types] [I-D.ietf-ccamp-layer0-types]
Zheng, H., Lee, Y., Guo, A., Lopezalvarez, V., and D. Zheng, H., Lee, Y., Guo, A., Lopez, V., and D. King, "A
King, "A YANG Data Model for Layer 0 Types", draft-ietf- YANG Data Model for Layer 0 Types", draft-ietf-ccamp-
ccamp-layer0-types-06 (work in progress), May 2020. layer0-types-08 (work in progress), October 2020.
[I-D.ietf-ccamp-dwdm-if-param-yang] [I-D.ietf-ccamp-dwdm-if-param-yang]
Galimberti, G., Kunze, R., Burk, A., Hiremagalur, D., and Galimberti, G., Kunze, R., Burk, A., Hiremagalur, D., and
G. Grammel, "A YANG model to manage the optical interface G. Grammel, "A YANG model to manage the optical interface
parameters for an external transponder in a WDM network", parameters for an external transponder in a WDM network",
draft-ietf-ccamp-dwdm-if-param-yang-04 (work in progress), draft-ietf-ccamp-dwdm-if-param-yang-04 (work in progress),
May 2020. May 2020.
[G.807] "Generic functional architecture of the optical media [G.807] "Generic functional architecture of the optical media
network", ITU-T Recommendation G.807 - in publication network", ITU-T Recommendation G.807 - in publication
skipping to change at page 56, line 39 skipping to change at page 59, line 50
[G.694.1] "Spectral grids for WDM applications: DWDM frequency [G.694.1] "Spectral grids for WDM applications: DWDM frequency
grid", ITU-T Recommendation G.694.1, February 2012. grid", ITU-T Recommendation G.694.1, February 2012.
[G.959.1] "Optical transport network physical layer interfaces", [G.959.1] "Optical transport network physical layer interfaces",
ITU-T Recommendation G.959.1, February 2012. ITU-T Recommendation G.959.1, February 2012.
[G.872] "Architecture of optical transport networks", [G.872] "Architecture of optical transport networks",
ITU-T Recommendation G.872, January 2017. ITU-T Recommendation G.872, January 2017.
[G.698.2] "Amplified multichannel dense wavelength division
multiplexing applications with single channel optical
interfaces", ITU-T Recommendation G.698.2, November 2018.
Appendix A. Contributors Appendix A. Contributors
Aihua Guo Aihua Guo
Huawei Technologies Huawei Technologies
Email: aguo@futurewei.com Email: aguo@futurewei.com
Jonas Martensson Jonas Martensson
RISE RISE
 End of changes. 58 change blocks. 
415 lines changed or deleted 524 lines changed or added

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