draft-ietf-ccamp-optical-impairment-topology-yang-03.txt   draft-ietf-ccamp-optical-impairment-topology-yang-04.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 V. Lopez Intended status: Standards Track JL. Auge
Expires: September 10, 2020 Telefonica Expires: March 12, 2021 Orange
V. Lopez
Telefonica
G. Galimberti G. Galimberti
Cisco Cisco
D. Beller D. Beller
Nokia Nokia
March 9, 2020 September 8, 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-03 draft-ietf-ccamp-optical-impairment-topology-yang-04
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.
This document provides a YANG data model for the impairment-aware TE This document provides a YANG data model for the impairment-aware TE
topology in optical networks. topology in optical networks.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). 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 September 10, 2020. This Internet-Draft will expire on March 12, 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 . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . . . . . 6
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) . . . . . . . 7
2.3.3. Media Channel (MC) . . . . . . . . . . . . . . . . . 8 2.3.3. Media Channel (MC) . . . . . . . . . . . . . . . . . 8
2.3.4. Media Channel Group (MCG) . . . . . . . . . . . . . . 9 2.3.4. Media Channel Group (MCG) . . . . . . . . . . . . . . 9
2.4. Amplifiers . . . . . . . . . . . . . . . . . . . . . . . 10 2.4. Amplifiers . . . . . . . . . . . . . . . . . . . . . . . 10
2.5. Transponders . . . . . . . . . . . . . . . . . . . . . . 11 2.5. Transponders . . . . . . . . . . . . . . . . . . . . . . 11
2.6. WSS/Filter . . . . . . . . . . . . . . . . . . . . . . . 11 2.6. WSS/Filter . . . . . . . . . . . . . . . . . . . . . . . 11
skipping to change at page 4, line 30 skipping to change at page 4, line 33
Section 2 of this this document. The meaning of the symbols in these Section 2 of this this document. The meaning of the symbols in these
diagrams is defined in [RFC8340]. diagrams is defined in [RFC8340].
1.3. Prefixes in Data Node Names 1.3. Prefixes in Data Node Names
In this document, names of data nodes and other data model objects In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1. corresponding YANG imported modules, as shown in Table 1.
+--------------+--------------------------+-------------------------+ +--------------+--------------------------+-------------------------+
| Prefix | YANG module | Reference | | Prefix | YANG module | Reference |
+--------------+--------------------------+-------------------------+ +--------------+--------------------------+-------------------------+
| optical-imp- | ietf-optical-impairment- | [RFCXXXX] | | optical-imp- | ietf-optical-impairment- | [RFCXXXX] |
| topo | topology | | | topo | topology | |
| layer0-types | ietf-layer0-types | [I-D.ietf-ccamp-layer0- | | layer0-types | ietf-layer0-types | [I-D.ietf-ccamp-layer0- |
| | | types] | | | | types] |
| nw | ietf-network | [RFC8345] | | nw | ietf-network | [RFC8345] |
| nt | ietf-network-topology | [RFC8345] | | nt | ietf-network-topology | [RFC8345] |
| tet | ietf-te-topology | [I-D.ietf-teas-yang-te- | | tet | ietf-te-topology | [I-D.ietf-teas-yang-te- |
| | | topo] | | | | topo] |
+--------------+--------------------------+-------------------------+ +--------------+--------------------------+-------------------------+
skipping to change at page 56, line 8 skipping to change at page 56, line 8
[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., Lopezalvarez, V., and D.
King, "A YANG Data Model for WSON (Wavelength Switched King, "A YANG Data Model for WSON (Wavelength Switched
Optical Networks)", draft-ietf-ccamp-wson-yang-23 (work in Optical Networks)", draft-ietf-ccamp-wson-yang-25 (work in
progress), November 2019. progress), May 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., Lopezalvarez, V., and D.
King, "A YANG Data Model for Layer 0 Types", draft-ietf- King, "A YANG Data Model for Layer 0 Types", draft-ietf-
ccamp-layer0-types-03 (work in progress), November 2019. ccamp-layer0-types-06 (work in progress), May 2020.
[I-D.ietf-ccamp-dwdm-if-param-yang] [I-D.ietf-ccamp-dwdm-if-param-yang]
Galimberti, G., Kunze, R., Hiremagalur, D., and G. Galimberti, G., Kunze, R., Burk, A., Hiremagalur, D., and
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-02 (work in progress), draft-ietf-ccamp-dwdm-if-param-yang-04 (work in progress),
November 2019. 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
process, February 2020. process, February 2020.
[G.709] "Interfaces for the Optical Transport Network (OTN)", [G.709] "Interfaces for the Optical Transport Network (OTN)",
ITU-T Recommendation G.709, June 2016. ITU-T Recommendation G.709, June 2016.
[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.
skipping to change at page 57, line 27 skipping to change at page 57, line 27
Nicola Sambo Nicola Sambo
Scuola Superiore Sant'Anna Scuola Superiore Sant'Anna
Email: nicosambo@gmail.com Email: nicosambo@gmail.com
Giovanni Martinelli Giovanni Martinelli
Cisco Cisco
Email: giomarti@cisco.com Email: giomarti@cisco.com
Jean-Luc Auge
Orange
Email: jeanluc.auge@orange.com
Esther Le Rouzic 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
skipping to change at page 58, line 21 skipping to change at page 58, line 16
Email: ggrammel@juniper.net Email: ggrammel@juniper.net
Authors' Addresses Authors' Addresses
Young Lee Young Lee
SKKU (Sung Kyun Kwan University) SKKU (Sung Kyun Kwan University)
Email: younglee.tx@gmail.com Email: younglee.tx@gmail.com
Jean-Luc Auge
Orange
Email: jeanluc.auge@orange.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
 End of changes. 14 change blocks. 
21 lines changed or deleted 23 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/