<?xmlversion="1.0" encoding="US-ASCII"?>version='1.0' encoding='utf-8'?> <!DOCTYPE rfc SYSTEM"rfc2629.dtd"> <!-- vi: set et smarttab sw=2 tabstop=4:--> <?rfc toc="yes"?> <?rfc tocompact="yes"?> <?rfc tocdepth="3"?> <?rfc tocindent="yes"?> <?rfc symrefs="yes"?> <?rfc sortrefs="yes"?> <?rfc comments="yes"?> <?rfc inline="yes"?> <?rfc compact="yes"?> <?rfc subcompact="no"?>"rfc2629-xhtml.ent"> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" docName="draft-ietf-ccamp-layer0-types-09" number="9093" consensus="true" ipr="trust200902" obsoletes="" updates="" submissionType="IETF"xml:lang="en">xml:lang="en" tocInclude="true" tocDepth="3" symRefs="true" sortRefs="true" version="3"> <!-- xml2rfc v2v3 conversion 3.7.0 --> <front><title abbrev=" A<title>A YANG Data Model for Layer 0Types"> A YANG Data Model for Layer 0 Types </title>Types</title> <seriesInfo name="RFC" value="9093"/> <authorinitials="H." surname="Zheng" fullname="Haomianfullname="郑好棉" asciiFullname="Haomian Zheng"><organization>Huawei Technologies</organization><organization ascii="Huawei Technologies">华为技术有限公司</organization> <address> <postal><street>H1,<street ascii="H1, Huawei Xiliu Beipo Village, SongshanLake</street> <city>Dongguan</city> <region>Guangdong</region>Lake">松山湖华为溪流背坡村H1</street> <city ascii="Dongguan">东莞</city> <region ascii="Guangdong">广东</region> <code>523808</code><country>China</country><country ascii="China">中国</country> </postal> <email>zhenghaomian@huawei.com</email> </address> </author> <author fullname="Young Lee" initials="Y." surname="Lee"> <organization>Samsung</organization> <address> <postal><street></street> <city></city> <region></region> <code></code><street/> <city/> <region/> <code/> <country>South Korea</country> </postal> <email>younglee.tx@gmail.com</email> </address> </author> <author initials="A." surname="Guo" fullname="Aihua Guo"> <organization>Futurewei</organization> <address><postal> <street></street> <city></city> <region></region> <code></code> <country></country> </postal><email>aihuaguo.ietf@gmail.com</email> </address> </author> <author initials="V." surname="Lopez" fullname="Victor Lopez"><organization>Telefonica</organization><organization>Nokia</organization> <address><postal> <street></street> <city></city> <region></region> <code></code> <country></country> </postal> <email>victor.lopezalvarez@telefonica.com</email><email>victor.lopez@nokia.com</email> </address> </author> <author initials="D." surname="King" fullname="Daniel King"> <organization>University of Lancaster</organization> <address><postal> <street></street> <city></city> <region></region> <code></code> <country></country> </postal><email>d.king@lancaster.ac.uk</email> </address> </author> <datemonth="December" day="29" year="2020"></date> <workgroup>CCAMP Working Group</workgroup>month="July" year="2021"/> <area>RTG</area> <workgroup>CCAMP</workgroup> <keyword>WDM</keyword> <keyword>YANG data model</keyword> <keyword>Types</keyword> <abstract> <t> This document defines a collection of common data types and groupings in the YANG data modeling language. These derived common types and groupings are intended to be imported by modules that model Layer 0 optical Traffic Engineering (TE) configuration and state capabilities such as Wavelength Switched Optical Networks (WSONs) andFlexi-gridflexi-grid Dense Wavelength Division Multiplexing (DWDM)Networks.networks. </t> </abstract><!-- <note title="Requirements Language"> <t> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <xref target="RFC2119" />. </t> </note> --></front> <middle> <sectiontitle="Introduction" toc="default">toc="default" numbered="true"> <name>Introduction</name> <t> YANG <xref target="RFC7950"/>format="default"/> is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols such asNETCONFthe Network Configuration Protocol (NETCONF) <xref target="RFC6241"/>.format="default"/>. The YANG language supports a small set of built-in data types and provides mechanisms to derive other types from the built-in types. </t> <t> This document introduces a collection of common data types derived from the built-in YANG data types. The derived types and groupings are designed to be the common types applicable for modeling Traffic Engineering (TE) features as well as non-TE features (e.g., physical network configurationaspect)aspects) for Layer 0 optical networks in model(s) defined outside of this document. The applicability of Layer 0 types specified in this documentincludeincludes Wavelength Switched Optical Networks (WSONs) <xref target="RFC6163"/> andformat="default"/> <xref target="ITU-Tg6982"/>,format="default"/> andFlexi-gridflexi-grid Dense Wavelength Division Multiplexing (DWDM)Networksnetworks <xref target="RFC7698"/> andformat="default"/> <xref target="ITU-Tg6941"/> .format="default"/>. </t> <sectiontitle="Terminologytoc="default" numbered="true"> <name>Terminology andNotations" toc="default">Notations</name> <t> Refer to <xref target="RFC7446"/>format="default"/> and <xref target="RFC7581"/>format="default"/> for the key terms used in this document, and the terminology for describing YANG data models can be found in <xref target="RFC7950"/>.format="default"/>. </t> <t> The YANG data model in this document conforms to the Network Management Datastore Architecture defined in <xref target="RFC8342"/>.format="default"/>. </t> </section><!-- Terminology and Notation END --><sectiontitle="Prefixtoc="default" numbered="true"> <name>Prefix in Data NodeNames" toc="default">Names</name> <t> In this document, names of data nodes and other data model objects are prefixed using the standard prefix associated with the corresponding YANG imported modules. </t><figure> <artwork> <![CDATA[ +-------------+---------------------------+----------------------+ | Prefix | YANG module | Reference | +-------------+---------------------------+----------------------+ | l0-types | ietf-layer0-types | [RFCXXXX] | +-------------+---------------------------+----------------------+ ]]> </artwork> </figure> <t> Note: The RFC Editor will replace XXXX with the number assigned to the RFC once this document becomes<table anchor="table_1"> <!-- Assign anRFC. </t>anchor --> <name>Data Node Names</name> <!-- Give the table a title --> <thead> <tr> <th>Prefix</th> <!-- <th>: headings --> <th>YANG module</th> <th>Reference</th> </tr> </thead> <tbody> <!-- The rows --> <tr> <td>l0-types</td> <td>ietf-layer0-types</td> <td>RFC 9093</td> </tr> </tbody> </table> <t> The YANG moduleietf-layer0-types"ietf-layer0-types" (defined inSection 3)<xref target="code"/>) references <xreftarget="RFC6163" />,target="RFC4203"/>, <xreftarget="RFC6205" />,target="RFC6163"/>, <xref target="RFC6205"/>, <xref target="RFC7698"/>, <xref target="RFC7699"/>, <xref target="RFC8363"/>, <xref target="ITU-Tg6941"/>, and <xreftarget="RFC7698" />.target="ITU-Tg6942"/>. </t> </section><!-- Prefix END --></section><!-- Introduction END --><section anchor="DM"title="Layertoc="default" numbered="true"> <name>Layer 0 Types ModuleContents" toc="default">Contents</name> <t> This document defines a YANG module for common Layer 0 types, ietf-layer0-types. This module is used for WSON andFlexi-gridflexi-grid DWDM networks. Theietf-layer0-types"ietf-layer0-types" module contains the following YANG reusable types and groupings: </t><t> l0-grid-type: </t> <t> A<dl newline="true"> <dt>l0-grid-type: </dt> <dd>A base YANG identity for the grid type as defined in <xref target="RFC6163"/>format="default"/> and <xref target="RFC7698"/>. </t> <t> dwdm-ch-spc-type: </t> <t> Aformat="default"/>. </dd> <dt>dwdm-ch-spc-type: </dt> <dd>A base YANG identity for the DWDMchannel spacingchannel-spacing type as defined in <xref target="RFC6205"/>. </t> <t> cwdm-ch-spc-type: </t> <t> Aformat="default"/>. </dd> <dt>cwdm-ch-spc-type: </dt> <dd>A base YANG identity for theCWDM channel spacingCoarse Wavelength Division Multiplexing (CWDM) channel-spacing type as defined in <xref target="RFC6205"/>. </t> <t> wson-label-start-end: </t> <t>format="default"/>. </dd> <dt>wson-label-start-end: </dt> <dd>The WSON label range was defined in <xref target="RFC6205"/>,format="default"/>, and the generic topology model defines the label-start/label-end in <xref target="RFC8795"/>.format="default"/>. This grouping shows the WSON-specific label-start and label-end information.</t> <t> wson-label-hop: </t> <t></dd> <dt>wson-label-hop: </dt> <dd>The WSON label range was defined in <xref target="RFC6205"/>,format="default"/>, and the generic topology model defines the label-hop in <xref target="RFC8795"/>.format="default"/>. This grouping shows the WSON-specific label-hop information.</t> <t> l0-label-range-info: </t> <t> A</dd> <dt>l0-label-range-info: </dt> <dd>A YANG grouping that defines thelayerLayer 0 label range information applicable forbothWSONper priority levelas defined in <xref target="RFC6205"/>.format="default"/>. This grouping is used in the flexi-grid DWDM by adding more flexi-grid-specific parameters.</t> <t> wson-label-step: </t> <t> A</dd> <dt>wson-label-step: </dt> <dd>A YANG grouping that defines label steps for WSON as defined in <xref target="RFC8776"/>. </t> <t> flexi-grid-label-start-end: </t> <t> Flexi-gridformat="default"/>. </dd> <dt>flexi-grid-label-start-end: </dt> <dd>The flexi-grid label range was defined in <xref target="RFC7698"/>,format="default"/>, and the generic topology model defines the label-start/label-end in <xref target="RFC8795"/>.format="default"/>. This grouping shows the flexi-grid-specific label-start and label-end information.</t> <t> flexi-grid-label-hop: </t> <t> Flexi-grid</dd> <dt>flexi-grid-label-hop: </dt> <dd>The flexi-grid label range was defined in <xref target="RFC7698"/>,format="default"/>, and the generic topology model defines the label-hop in <xref target="RFC8795"/>.format="default"/>. This grouping shows the WSON-specific label-hop information.</t> <t> flexi-grid-label-range-info: </t> <t> A</dd> <dt>flexi-grid-label-range-info: </dt> <dd>A YANG grouping that defines flexi-grid label range informationand per priority levelas defined in <xref target="RFC7698"/>format="default"/> and <xref target="RFC8363"/>. </t> <t> flexi-grid-label-step: </t> <t>format="default"/>. </dd> <dt>flexi-grid-label-step: </dt> <dd> A YANG grouping that defines flexi-grid label steps as defined in <xref target="RFC8776"/>. </t>format="default"/>. </dd> </dl> </section><!-- Layer-0-Types Overview END --><section anchor="code"title="YANG Codetoc="default" numbered="true"> <name>YANG Module for Layer 0Types" toc="default"> <figure anchor="TheYANGCode" title="" suppress-title="true" align="left" alt="" width="" height=""> <artwork xml:space="preserve" name="" type="" align="left" alt="" width="" height=""> <![CDATA[ <CODE BEGINS>file "ietf-layer0-types@2020-12-29.yang"Types</name> <sourcecode name="ietf-layer0-types@2021-07-20.yang" type="yang" markers="true"><![CDATA[ module ietf-layer0-types { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-layer0-types"; prefix"l0-types";l0-types; organization "IETF CCAMP Working Group"; contact "WG Web:<http://tools.ietf.org/wg/ccamp/><https://datatracker.ietf.org/wg/ccamp/> WG List: <mailto:ccamp@ietf.org> Editor: Haomian Zheng <mailto:zhenghaomian@huawei.com> Editor: Young Lee <mailto:younglee.tx@gmail.com> Editor: Aihua Guo <mailto:aihuaguo.ietf@gmail.com> Editor: Victor Lopez<mailto:victor.lopezalvarez@telefonica.com><mailto:victor.lopez@nokia.com> Editor: Daniel King <mailto:d.king@lancaster.ac.uk>"; description "This module defines Optical Layer 0 types. This module provides groupings that can be applicable to Layer 0 Fixed Optical Networks (e.g., CWDM (Coarse Wavelength Division Multiplexing) and DWDM (Dense Wavelength Division Multiplexing)) andFlexi-grid Optical Networks.flexi-grid optical networks. Copyright (c)20202021 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents(http://trustee.ietf.org/license-info).(https://trustee.ietf.org/license-info). This version of this YANG module is part of RFCXXXX;9093; see the RFC itself for full legal notices."; revision"2020-12-29"2021-07-20 { description "InitialVersion";version"; reference "RFCXXXX:9093: A YANG Data Model for Layer 0 Types"; } typedef dwdm-n { type int16; description "The given value 'N' is used to determine the nominal central frequency. The nominal central frequency,'f''f', is defined by: f = 193100.000 GHz + N xchannel-spacingchannel spacing (measured in GHz), where 193100.000 GHz (193.100000 THz) is the ITU-T 'anchor frequency' for transmission over theC band;DWDM grid, and where'channel-spacing''channel spacing' is defined by the dwdm-ch-spc-type."; reference "RFC6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers, ITU-T G.694.1(02/2012):(10/2020): Spectral grids for WDM applications: DWDM frequency grid"; } typedef cwdm-n { type int16; description "The given value 'N' is used to determine the nominal central wavelength. The nominal central wavelength is defined by: Wavelength = 1471 nm + N xchannel-spacingchannel spacing (measured in nm) where 1471 nm is theITU-Tconventional 'anchor wavelength' for transmission over theC band;CWDM grid, and where'channel-spacing''channel spacing' is defined by the cwdm-ch-spc-type."; reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers, ITU-T G.694.2 (12/2003): Spectral grids for WDM applications: CWDM wavelength grid"; } typedef flexi-n { type int16; description "The given value 'N' is used to determine the nominal central frequency. The nominal central frequency,'f''f', is definedby,by: f = 193100.000 GHz + N xchannel-spacingchannel spacing (measured in GHz), where 193100.000 GHz (193.100000 THz) is the ITU-T 'anchor frequency' for transmission over theC band;DWDM grid, and where'channel-spacing''channel spacing' is defined by the flexi-ch-spc-type. Note that the term'channel-spacing''channel spacing' can bealternatedsubstituted by the term 'nominal central frequency granularity' defined in clause78 of ITU-T G.694.1."; reference"RFC7698:"RFC 7698: Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM)Networks.Networks, ITU-T G.694.1(02/2012):(10/2020): Spectral grids for WDM applications: DWDM frequency grid"; } typedef flexi-m { type uint16; description "The given value 'M' is used to determine the slot width. A slot width is defined by: slot width = M x SWG (measured in GHz), where SWG is defined by the flexi-slot-width-granularity."; reference"RFC7698:"RFC 7698: Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks. ITU-T G.694.1(02/2012):(10/2020): Spectral grids for WDM applications: DWDM frequency grid"; } identity l0-grid-type { description "Layer 0 grid type"; reference"RFC6163:Framework"RFC 6163: Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs), ITU-T G.694.1(02/2012):(10/2020): Spectral grids for WDM applications: DWDM frequency grid, ITU-T G.694.2 (12/2003): Spectral grids for WDM applications: CWDM wavelength grid"; } identity flexi-grid-dwdm { base l0-grid-type; description "Flexi-grid"; reference"RFC7698:"RFC 7698: Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks, ITU-T G.694.1(02/2012):(10/2020): Spectral grids for WDM applications: DWDM frequency grid"; } identity wson-grid-dwdm { base l0-grid-type; description "DWDM grid"; reference"RFC6163:Framework"RFC 6163:Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs), ITU-T G.694.1(02/2012):(10/2020): Spectral grids for WDM applications: DWDM frequency grid"; } identity wson-grid-cwdm { base l0-grid-type; description "CWDM grid"; reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers, ITU-T G.694.2 (12/2003): Spectral grids for WDM applications: CWDM wavelength grid"; } identity dwdm-ch-spc-type { description "DWDMchannel spacingchannel-spacing type"; reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers, ITU-T G.694.1(02/2012):(10/2020): Spectral grids for WDM applications: DWDM frequency grid"; } identity dwdm-100ghz { base dwdm-ch-spc-type; description"100GHz"100 GHz channel spacing"; } identity dwdm-50ghz { base dwdm-ch-spc-type; description"50GHz"50 GHz channel spacing"; } identity dwdm-25ghz { base dwdm-ch-spc-type; description"25GHz"25 GHz channel spacing"; } identity dwdm-12p5ghz { base dwdm-ch-spc-type; description"12.5GHz"12.5 GHz channel spacing"; } identity flexi-ch-spc-type { description "Flexi-gridchannel spacingchannel-spacing type"; reference"RFC7698:"RFC 7698: Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM)NetworksNetworks, ITU-T G.694.1(02/2012):(10/2020): Spectral grids for WDM applications: DWDM frequency grid"; } identity flexi-ch-spc-6p25ghz { base flexi-ch-spc-type; description"6.25GHz"6.25 GHz channel spacing"; } identity flexi-slot-width-granularity { description "Flexi-grid slot width granularity"; } identity flexi-swg-12p5ghz { base flexi-slot-width-granularity; description"12.5GHz"12.5 GHz slot width granularity"; } identity cwdm-ch-spc-type { description "CWDMchannel spacingchannel-spacing type"; reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers, ITU-T G.694.2 (12/2003): Spectral grids for WDM applications: CWDM wavelength grid"; } identity cwdm-20nm { base cwdm-ch-spc-type; description "20nm channel spacing"; } /* Groupings. */ grouping wson-label-start-end { description "The WSON label-start or label-end used to specify WSON label range."; choice grid-type { description "Label for DWDM or CWDM grid"; case dwdm { leaf dwdm-n { when'derived-from-or-self(../../../grid-type, "wson-grid-dwdm")'"derived-from-or-self(../../../grid-type, \"wson-grid-dwdm\")" { description "Valid only when grid type is DWDM."; } type l0-types:dwdm-n; description "The central frequency of DWDM."; reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers"; } } case cwdm { leaf cwdm-n { when'derived-from-or-self(../../../grid-type, "wson-grid-cwdm")'"derived-from-or-self(../../../grid-type, \"wson-grid-cwdm\")" { description "Valid only when grid type is CWDM."; } type l0-types:cwdm-n; description "Channel wavelength computing input."; reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers"; } } } reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers"; } grouping wson-label-hop { description "Genericlabel hoplabel-hop information for WSON"; choice grid-type { description "Label for DWDM or CWDM grid"; case dwdm { choice single-or-super-channel { description "single or super channel"; case single { leaf dwdm-n { type l0-types:dwdm-n; description "The given value 'N' is used to determine the nominal central frequency."; } } case super { leaf-list subcarrier-dwdm-n { type l0-types:dwdm-n; description "The given values 'N' are used to determine the nominal central frequency for each subcarrierchannels.";channel."; reference "ITU-T Recommendation G.694.1: Spectral grids for WDM applications: DWDM frequency grid"; } } } } case cwdm { leaf cwdm-n { type l0-types:cwdm-n; description "The given value 'N' is used to determine the nominal central wavelength."; reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers"; } } } reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers"; } grouping l0-label-range-info { description "Information aboutlayerLayer 0 label range."; leaf grid-type { type identityref { base l0-grid-type; } description "Grid type"; } leaf priority { type uint8; description "Priority in Interface Switching Capability Descriptor (ISCD)."; reference"RFC4203:"RFC 4203: OSPF Extensions in Support of Generalized Multi-Protocol Label Switching(GMPLS).";(GMPLS)"; } reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers"; } grouping wson-label-step { description "Label step information for WSON"; choice l0-grid-type { description "Grid type: DWDM, CWDM, etc."; case dwdm { leaf wson-dwdm-channel-spacing { when'derived-from-or-self(../../grid-type, "wson-grid-dwdm")'"derived-from-or-self(../../grid-type, \"wson-grid-dwdm\")" { description "Valid only when grid type is DWDM."; } type identityref { base dwdm-ch-spc-type; } description "Label-step is thechannel-spacingchannel spacing (GHz), e.g., 100.000, 50.000, 25.000, or 12.500 GHz forDWDM";DWDM."; reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers"; } } case cwdm { leaf wson-cwdm-channel-spacing { when'derived-from-or-self(../../grid-type, "wson-grid-cwdm")'"derived-from-or-self(../../grid-type, \"wson-grid-cwdm\")" { description "Valid only when grid type is CWDM."; } type identityref { base cwdm-ch-spc-type; } description "Label-step is thechannel-spacingchannel spacing (nm), i.e., 20 nm for CWDM, which is the only value defined forCWDM";CWDM."; reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers"; } } } reference"RFC6205:"RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers, ITU-T G.694.2 (12/2003): Spectral grids for WDM applications: CWDM wavelength grid"; } grouping flexi-grid-label-start-end { description "TheFlexi-gridflexi-grid label-start or label-end used to specifyFlexi-gridflexi-grid label range."; leaf flexi-n { type l0-types:flexi-n; description "The given value 'N' is used to determine the nominal central frequency."; } reference"RFC7698:"RFC 7698: Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks"; } grouping flexi-grid-frequency-slot { description "Flexi-grid frequency slot grouping."; uses flexi-grid-label-start-end; leaf flexi-m { type l0-types:flexi-m; description "The given value 'M' is used to determine the slot width."; } reference"RFC7698:"RFC 7698: Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks"; } grouping flexi-grid-label-hop { description "Genericlabel hoplabel-hop information forFlexi-grid";flexi-grid"; choice single-or-super-channel { description "single or super channel"; case single { uses flexi-grid-frequency-slot; } case super { list subcarrier-flexi-n { keyflexi-n;"flexi-n"; uses flexi-grid-frequency-slot; description "List of subcarrier channels for flexi-grid super channel."; } } } reference"RFC7698:"RFC 7698: Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks"; } grouping flexi-grid-label-range-info { description "Flexi-grid-specific label range related information"; uses l0-label-range-info; container flexi-grid { description "flexi-grid definition"; leaf slot-width-granularity { type identityref { base flexi-slot-width-granularity; } defaultflexi-swg-12p5ghz;"flexi-swg-12p5ghz"; description "Minimum space between slot widths. Default is 12.500GHz";GHz."; reference"RFC7698:"RFC 7698: Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks"; } leaf min-slot-width-factor { type uint16 { range "1..max"; } default1;"1"; description "A multiplier of the slot width granularity, indicating the minimum slot width supported by an optical port. Minimum slot width is calculated by: Minimum slot width (GHz) = min-slot-width-factor * slot-width-granularity."; reference"RFC8363:"RFC 8363: GMPLS OSPF-TE Extensions in Support of Flexi- Grid Dense Wavelength Division Multiplexing (DWDM) Networks"; } leaf max-slot-width-factor { type uint16 { range "1..max"; } must '. >=min-slot-width-factor'../min-slot-width-factor' { error-message "Maximum slot width must be greater than or equal to minimum slot width."; } description "A multiplier of the slot width granularity, indicating the maximum slot width supported by an optical port. Maximum slot width is calculated by: Maximum slot width (GHz) = max-slot-width-factor * slot-width-granularity If specified, maximum slot width must be greater than or equal to minimum slotwidth.Ifwidth. If not specified, maximum slot width is equal to minimum slot width."; reference"RFC8363:"RFC 8363: GMPLS OSPF-TE Extensions in Support of Flexi- Grid Dense Wavelength Division Multiplexing (DWDM) Networks"; } } } grouping flexi-grid-label-step { description "Label step information for flexi-grid"; leaf flexi-grid-channel-spacing { type identityref { base flexi-ch-spc-type; } defaultflexi-ch-spc-6p25ghz;"flexi-ch-spc-6p25ghz"; description "Label-step is the nominal central frequency granularity (GHz), e.g., 6.25GHz";GHz."; reference"RFC7699:"RFC 7699: Generalized Labels for the Flexi-Grid in Lambda Switch Capable (LSC) Label Switching Routers"; } leaf flexi-n-step { type uint8; description "This attribute defines the multiplier for the supported values of 'N'. For example, given a grid with a nominal central frequency granularity of 6.25 GHz, the granularity of the supported values of the nominal central frequency could be 12.5 GHz. In this case, the values of flexi-n should be even and this constraint is reported by setting the flexi-n-step to 2. This attribute is also known as central frequency granularity inRFC8363.";RFC 8363."; reference"RFC8363:"RFC 8363: GMPLS OSPF-TE Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks"; } } }<CODE ENDS> ]]> </artwork> </figure>]]></sourcecode> </section> <!-- YANG CODE END --> <!-- DM END --> <section anchor="Security"title="Security Considerations" toc="default">toc="default" numbered="true"> <name>Security Considerations</name> <t> The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF <xref target="RFC6241"/>format="default"/> or RESTCONF <xref target="RFC8040"/>.format="default"/>. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) <xref target="RFC6242"/>.format="default"/>. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS <xref target="RFC8446"/>.format="default"/>. </t> <t> TheNETCONF access control modelNetwork Configuration Access Control Model (NACM) <xreftarget="RFC8341" />target="RFC8341"/> provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. The NETCONFProtocolprotocol over Secure Shell (SSH) specification <xref target="RFC6242"/>format="default"/> describes a method for invoking and running NETCONF within a Secure Shell (SSH) session as an SSH subsystem.The NETCONF access control model <xref target="RFC8341" /> provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.</t> <t> The objects in this YANG module are common data types and groupings. No object in this module can be read or written to. These definitions can be imported and used by otherlayerLayer 0 specific modules. It is critical to consider how imported definitions will be utilized and accessible via RPC operations, as the resultant schema will have data nodes that can be writable, or readable, and will have a significant effect on the network operations if used incorrectly or maliciously. All ofthis consideration belongsthese considerations belong in the document that defines the modules that import from this YANG module. Therefore, it is important to manage access to resultant data nodes that are considered sensitive or vulnerable in some network environments. </t> <t> The security considerations spelled out in the YANG 1.1 specification <xref target="RFC7950"/>format="default"/> apply for this document as well. </t> </section> <!-- Security END --> <section anchor="IANA"title="IANA Considerations" toc="default">toc="default" numbered="true"> <name>IANA Considerations</name> <t>It is proposed toIANAto assignhas assigned new URIs from the "IETF XML Registry" <xref target="RFC3688"/>format="default"/> as follows: </t><figure> <artwork> <![CDATA[ URI: urn:ietf:params:xml:ns:yang:ietf-layer0-types Registrant<dl spacing="compact"> <dt>URI: </dt> <dd>urn:ietf:params:xml:ns:yang:ietf-layer0-types </dd> <dt>Registrant Contact:The</dt> <dd>The IESGXML: N/A;</dd> <dt>XML: </dt> <dd>N/A; the requested URI is an XML namespace.]]> </artwork> </figure></dd> </dl> <t> This document registers the following YANGmodulesmodule in theYANG"YANG ModuleNamesNames" registry <xref target="RFC7950"/>.format="default"/>. </t><figure> <artwork> <![CDATA[ name: ietf-layer0-types namespace: urn:ietf:params:xml:ns:yang:ietf-layer0-types prefix: l0-types reference: RFC XXXX(TBD) ]]> </artwork> </figure><dl spacing="compact"> <dt>Name: </dt> <dd>ietf-layer0-types </dd> <dt>Namespace: </dt> <dd>urn:ietf:params:xml:ns:yang:ietf-layer0-types </dd> <dt>Prefix: </dt> <dd>l0-types </dd> <dt>Reference: </dt> <dd>RFC 9093 </dd> </dl> </section> <!-- IANA END --><section title="Acknowledgements" toc="default"> <t> The authors and the working group give their sincere thanks for Robert Wilton for the YANG doctor review, and Tom Petch for his comments during the model and document development. </t> </section> <section anchor="Contributor" title="Contributors" toc="default"> <t> Dhruv Dhody <vspace blankLines="0" /> Huawei <vspace blankLines="0" /> Email: dhruv.ietf@gmail.com <vspace blankLines="0" /> </t> <t> Bin Yeong Yoon <vspace blankLines="0" /> ETRI <vspace blankLines="0" /> Email: byyun@etri.re.kr <vspace blankLines="0" /> </t> <t> Ricard Vilalta <vspace blankLines="0" /> CTTC <vspace blankLines="0" /> Email: ricard.vilalta@cttc.es <vspace blankLines="0" /> </t> <t> Italo Busi <vspace blankLines="0" /> Huawei <vspace blankLines="0" /> Email: Italo.Busi@huawei.com <!-- zhengyanlei@chinaunicom.cn --> <vspace blankLines="0" /> </t> </section><!-- Contributor END --> </middle> <back><references title="Normative References"><references> <name>References</name> <references> <name>Normative References</name> <!--<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?> --><?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.4203.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.7699.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8446.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.6163.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.6205.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.6241.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.6242.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8363.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8341.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.7698.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.7950.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8040.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8342.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8776.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8795.xml"?><xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4203.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7699.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6163.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6205.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6242.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8363.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7698.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8776.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8795.xml"/> <reference anchor="ITU-Tg6982"> <front> <title> Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces </title> <author><organization>International Telecommunication Union</organization><organization>ITU-T</organization> </author> <date month="November" year="2018"/> </front><seriesInfo name="ITU-T" value="G.698.2"/><refcontent>ITU-T Recommendation G.698.2</refcontent> </reference> </references><!-- Normative END --> <references title="Informative References"> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.7446.xml"?> <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.7581.xml"?><references> <name>Informative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7446.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7581.xml"/> <reference anchor="ITU-Tg6941"> <front> <title> Spectral grids for WDM applications: DWDM frequency grid </title> <author><organization>International Telecommunication Union</organization><organization>ITU-T</organization> </author> <datemonth="February" year="2012"/>month="October" year="2020"/> </front> <seriesInfoname="ITU-T"name="ITU-T Recommendation" value="G.694.1"/> </reference> <reference anchor="ITU-Tg6942"> <front> <title> Spectral grids for WDM applications: CWDM wavelength grid </title> <author><organization>International Telecommunication Union</organization><organization>ITU-T</organization> </author> <date month="December" year="2003"/> </front> <seriesInfoname="ITU-T"name="ITU-T Recommendation" value="G.694.2"/> </reference><reference anchor="ITU-Tg709"> <front> <title> Interfaces</references> </references> <section toc="default" numbered="false"> <name>Acknowledgements</name> <t> The authors and the working group give their sincere thanks to <contact fullname="Robert Wilton"/> for theoptical transport network </title> <author> <organization>International Telecommunication Union</organization>YANG doctor review and <contact fullname="Tom Petch"/> for his comments during the model and document development. </t> </section> <section anchor="Contributor" toc="default" numbered="false"> <name>Contributors</name> <author initials="D" surname="Dhody" fullname="Dhruv Dhody"> <organization>Huawei</organization> <address> <email>dhruv.ietf@gmail.com</email> </address> </author><date month="June" year="2016"/> </front> <seriesInfo name="ITU-T" value="G.709"/> </reference> </references> <!-- Informative END --><author initials="B. Y." surname="Yoon" fullname="Bin Yeong Yoon"> <organization>ETRI</organization> <address> <email>byyun@etri.re.kr</email> </address> </author> <author initials="R" surname="Vilalta" fullname="Ricard Vilalta"> <organization>CTTC</organization> <address> <email>ricard.vilalta@cttc.es</email> </address> </author> <author initials="I" surname="Busi" fullname="Italo Busi"> <organization>Huawei</organization> <address> <email>Italo.Busi@huawei.com</email> </address> </author> </section> </back> </rfc>