<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" consensus="true" docName="draft-ietf-ccamp-layer0-types-09" indexInclude="true" ipr="trust200902" number="9093" prepTime="2021-08-13T10:14:11" scripts="Common,Han,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocInclude="true" xml:lang="en">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-ccamp-layer0-types-09" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9093" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title>A YANG Data Model for Layer 0 Types</title>
    <seriesInfo name="RFC" value="9093" stream="IETF"/>
    <author fullname="郑好棉" asciiFullname="Haomian Zheng">
      <organization ascii="Huawei Technologies" showOnFrontPage="true">华为技术有限公司</organization>
      <address>
        <postal>
          <street ascii="H1, Huawei Xiliu Beipo Village, Songshan Lake">松山湖华为溪流背坡村H1</street>
          <city ascii="Dongguan">东莞</city>
          <region ascii="Guangdong">广东</region>
          <code>523808</code>
          <country ascii="China">中国</country>
        </postal>
        <email>zhenghaomian@huawei.com</email>
      </address>
    </author>
    <author fullname="Young Lee" initials="Y." surname="Lee">
      <organization showOnFrontPage="true">Samsung</organization>
      <address>
        <postal>
          <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 showOnFrontPage="true">Futurewei</organization>
      <address>
        <email>aihuaguo.ietf@gmail.com</email>
      </address>
    </author>
    <author initials="V." surname="Lopez" fullname="Victor Lopez">
      <organization showOnFrontPage="true">Nokia</organization>
      <address>
        <email>victor.lopez@nokia.com</email>
      </address>
    </author>
    <author initials="D." surname="King" fullname="Daniel King">
      <organization showOnFrontPage="true">University of Lancaster</organization>
      <address>
        <email>d.king@lancaster.ac.uk</email>
      </address>
    </author>
    <date month="08" year="2021"/>
    <area>RTG</area>
    <workgroup>CCAMP</workgroup>
    <keyword>WDM</keyword>
    <keyword>YANG data model</keyword>
    <keyword>Types</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">
   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) and flexi-grid Dense Wavelength Division Multiplexing (DWDM) networks. 
      </t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9093" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2021 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Simplified BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Simplified BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2">
              <li pn="section-toc.1-1.1.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.1.1"><xref derivedContent="1.1" format="counter" sectionFormat="of" target="section-1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-terminology-and-notations">Terminology and Notations</xref></t>
              </li>
              <li pn="section-toc.1-1.1.2.2">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.2.1"><xref derivedContent="1.2" format="counter" sectionFormat="of" target="section-1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-prefix-in-data-node-names">Prefix in Data Node Names</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-layer-0-types-module-conten">Layer 0 Types Module Contents</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-yang-module-for-layer-0-typ">YANG Module for Layer 0 Types</xref></t>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2">
              <li pn="section-toc.1-1.6.2.1">
                <t indent="0" pn="section-toc.1-1.6.2.1.1"><xref derivedContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.2">
                <t indent="0" pn="section-toc.1-1.6.2.2.1"><xref derivedContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-contributors">Contributors</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section toc="include" numbered="true" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">
  YANG <xref target="RFC7950" format="default" sectionFormat="of" derivedContent="RFC7950"/> is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols such as the Network Configuration Protocol (NETCONF) <xref target="RFC6241" format="default" sectionFormat="of" derivedContent="RFC6241"/>.  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 indent="0" pn="section-1-2">
  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 configuration aspects) for Layer 0 optical networks in model(s) defined outside of this document.  The applicability of Layer 0 types specified in this document includes Wavelength Switched Optical Networks (WSONs) <xref target="RFC6163" format="default" sectionFormat="of" derivedContent="RFC6163"/> <xref target="ITU-Tg6982" format="default" sectionFormat="of" derivedContent="ITU-Tg6982"/> and flexi-grid Dense Wavelength Division Multiplexing (DWDM) networks <xref target="RFC7698" format="default" sectionFormat="of" derivedContent="RFC7698"/> <xref target="ITU-Tg6941" format="default" sectionFormat="of" derivedContent="ITU-Tg6941"/>.
      </t>
      <section toc="include" numbered="true" removeInRFC="false" pn="section-1.1">
        <name slugifiedName="name-terminology-and-notations">Terminology and Notations</name>
        <t indent="0" pn="section-1.1-1">
   Refer to <xref target="RFC7446" format="default" sectionFormat="of" derivedContent="RFC7446"/> and <xref target="RFC7581" format="default" sectionFormat="of" derivedContent="RFC7581"/> 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" sectionFormat="of" derivedContent="RFC7950"/>.
        </t>
        <t indent="0" pn="section-1.1-2">   
   The YANG data model in this document conforms to the Network Management Datastore Architecture defined in <xref target="RFC8342" format="default" sectionFormat="of" derivedContent="RFC8342"/>.
        </t>
      </section>
      <section toc="include" numbered="true" removeInRFC="false" pn="section-1.2">
        <name slugifiedName="name-prefix-in-data-node-names">Prefix in Data Node Names</name>
        <t indent="0" pn="section-1.2-1">
   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>
        <table anchor="table_1" align="center" pn="table-1">
          <name slugifiedName="name-data-node-names">Data Node Names</name>
          <thead>
            <tr>
              <th align="left" colspan="1" rowspan="1">Prefix</th>
              <th align="left" colspan="1" rowspan="1">YANG module</th>
              <th align="left" colspan="1" rowspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left" colspan="1" rowspan="1">l0-types</td>
              <td align="left" colspan="1" rowspan="1">ietf-layer0-types</td>
              <td align="left" colspan="1" rowspan="1">RFC 9093</td>
            </tr>
          </tbody>
        </table>
        <t indent="0" pn="section-1.2-3">
  The YANG module "ietf-layer0-types" (defined in <xref target="code" format="default" sectionFormat="of" derivedContent="Section 3"/>) references 
   <xref target="RFC4203" format="default" sectionFormat="of" derivedContent="RFC4203"/>, <xref target="RFC6163" format="default" sectionFormat="of" derivedContent="RFC6163"/>, <xref target="RFC6205" format="default" sectionFormat="of" derivedContent="RFC6205"/>, <xref target="RFC7698" format="default" sectionFormat="of" derivedContent="RFC7698"/>, <xref target="RFC7699" format="default" sectionFormat="of" derivedContent="RFC7699"/>, <xref target="RFC8363" format="default" sectionFormat="of" derivedContent="RFC8363"/>,
   <xref target="ITU-Tg6941" format="default" sectionFormat="of" derivedContent="ITU-Tg6941"/>, and <xref target="ITU-Tg6942" format="default" sectionFormat="of" derivedContent="ITU-Tg6942"/>.   
        </t>
      </section>
    </section>
    <section anchor="DM" toc="include" numbered="true" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-layer-0-types-module-conten">Layer 0 Types Module Contents</name>
      <t indent="0" pn="section-2-1">
   This document defines a YANG module for common Layer 0 types, ietf-layer0-types. This module is used for WSON and flexi-grid DWDM networks.  The "ietf-layer0-types" module contains the following YANG reusable types and groupings:
      </t>
      <dl newline="true" indent="3" spacing="normal" pn="section-2-2">
        <dt pn="section-2-2.1">l0-grid-type:
</dt>
        <dd pn="section-2-2.2">A base YANG identity for the grid type as defined in <xref target="RFC6163" format="default" sectionFormat="of" derivedContent="RFC6163"/> and <xref target="RFC7698" format="default" sectionFormat="of" derivedContent="RFC7698"/>.
</dd>
        <dt pn="section-2-2.3">dwdm-ch-spc-type:
</dt>
        <dd pn="section-2-2.4">A base YANG identity for the DWDM channel-spacing type as defined in <xref target="RFC6205" format="default" sectionFormat="of" derivedContent="RFC6205"/>. 
</dd>
        <dt pn="section-2-2.5">cwdm-ch-spc-type:
</dt>
        <dd pn="section-2-2.6">A base YANG identity for the Coarse Wavelength Division Multiplexing
(CWDM) channel-spacing type as defined in <xref target="RFC6205" format="default" sectionFormat="of" derivedContent="RFC6205"/>.
</dd>
        <dt pn="section-2-2.7">wson-label-start-end:
</dt>
        <dd pn="section-2-2.8">The WSON label range was defined in <xref target="RFC6205" format="default" sectionFormat="of" derivedContent="RFC6205"/>,
and the generic topology model defines the label-start/label-end in <xref target="RFC8795" format="default" sectionFormat="of" derivedContent="RFC8795"/>. This grouping shows the WSON-specific
label-start and label-end information.
</dd>
        <dt pn="section-2-2.9">wson-label-hop:
</dt>
        <dd pn="section-2-2.10">The WSON label range was defined in <xref target="RFC6205" format="default" sectionFormat="of" derivedContent="RFC6205"/>,
and the generic topology model defines the label-hop in <xref target="RFC8795" format="default" sectionFormat="of" derivedContent="RFC8795"/>. This grouping shows the WSON-specific label-hop
information.
</dd>
        <dt pn="section-2-2.11">l0-label-range-info:
</dt>
        <dd pn="section-2-2.12">A YANG grouping that defines the Layer 0 label range information
applicable for WSON as defined in <xref target="RFC6205" format="default" sectionFormat="of" derivedContent="RFC6205"/>. This grouping is used in the flexi-grid
DWDM by adding more flexi-grid-specific parameters.
</dd>
        <dt pn="section-2-2.13">wson-label-step:
</dt>
        <dd pn="section-2-2.14">A YANG grouping that defines label steps for WSON as defined in <xref target="RFC8776" format="default" sectionFormat="of" derivedContent="RFC8776"/>.    
</dd>
        <dt pn="section-2-2.15">flexi-grid-label-start-end:
</dt>
        <dd pn="section-2-2.16">The flexi-grid label range was defined in <xref target="RFC7698" format="default" sectionFormat="of" derivedContent="RFC7698"/>, and the generic topology model defines the
label-start/label-end in <xref target="RFC8795" format="default" sectionFormat="of" derivedContent="RFC8795"/>. This
grouping shows the flexi-grid-specific label-start and label-end information.
</dd>
        <dt pn="section-2-2.17">flexi-grid-label-hop:
</dt>
        <dd pn="section-2-2.18">The flexi-grid label range was defined in <xref target="RFC7698" format="default" sectionFormat="of" derivedContent="RFC7698"/>, and the generic topology model defines the label-hop in
<xref target="RFC8795" format="default" sectionFormat="of" derivedContent="RFC8795"/>. This grouping shows the
WSON-specific label-hop information.
</dd>
        <dt pn="section-2-2.19">flexi-grid-label-range-info:
</dt>
        <dd pn="section-2-2.20">A YANG grouping that defines flexi-grid label range information as
defined in <xref target="RFC7698" format="default" sectionFormat="of" derivedContent="RFC7698"/> and <xref target="RFC8363" format="default" sectionFormat="of" derivedContent="RFC8363"/>.
</dd>
        <dt pn="section-2-2.21">flexi-grid-label-step:
</dt>
        <dd pn="section-2-2.22"> A YANG grouping that defines flexi-grid label steps as defined in <xref target="RFC8776" format="default" sectionFormat="of" derivedContent="RFC8776"/>.
</dd>
      </dl>
    </section>
    <section anchor="code" toc="include" numbered="true" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-yang-module-for-layer-0-typ">YANG Module for Layer 0 Types</name>
      <sourcecode name="ietf-layer0-types@2021-08-13.yang" type="yang" markers="true" pn="section-3-1">
module ietf-layer0-types {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-layer0-types";
  prefix l0-types;

  organization
    "IETF CCAMP Working Group";
  contact
    "WG Web: &lt;https://datatracker.ietf.org/wg/ccamp/&gt;
     WG List: &lt;mailto:ccamp@ietf.org&gt;

     Editor: Haomian Zheng
       &lt;mailto:zhenghaomian@huawei.com&gt;

     Editor: Young Lee
       &lt;mailto:younglee.tx@gmail.com&gt;

     Editor: Aihua Guo
       &lt;mailto:aihuaguo.ietf@gmail.com&gt;

     Editor: Victor Lopez
       &lt;mailto:victor.lopez@nokia.com&gt;

     Editor: Daniel King
       &lt;mailto:d.king@lancaster.ac.uk&gt;";

  description
    "This module defines Optical Layer 0 types.  This module
     provides groupings that can be applicable to Layer 0
     Fixed Optical Networks (e.g., CWDM (Coarse Wavelength
     Division Multiplexing) and DWDM (Dense Wavelength Division
     Multiplexing)) and flexi-grid optical networks.

     Copyright (c) 2021 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
     (https://trustee.ietf.org/license-info).

     This version of this YANG module is part of RFC 9093; see
     the RFC itself for full legal notices.";

  revision 2021-08-13 {
    description
      "Initial version";
    reference
      "RFC 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', is defined by:
         f = 193100.000 GHz + N x channel spacing (measured in GHz),

       where 193100.000 GHz (193.100000 THz) is the ITU-T 'anchor
       frequency' for transmission over the DWDM grid, and where
       '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 (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 x channel spacing (measured in nm)

       where 1471 nm is the conventional 'anchor wavelength' for
       transmission over the CWDM grid, and where 'channel spacing'
       is defined by the cwdm-ch-spc-type.";
    reference
      "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', is defined by:
         f = 193100.000 GHz + N x channel spacing (measured in GHz),

       where 193100.000 GHz (193.100000 THz) is the ITU-T 'anchor
       frequency' for transmission over the DWDM grid, and where
       'channel spacing' is defined by the flexi-ch-spc-type.

       Note that the term 'channel spacing' can be substituted by the
       term 'nominal central frequency granularity' defined in
       clause 8 of ITU-T G.694.1.";
    reference
      "RFC 7698: Framework and Requirements for GMPLS-Based Control
       of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM)
       Networks,
       ITU-T G.694.1 (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
      "RFC 7698: Framework and Requirements for GMPLS-Based Control
       of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM)
       Networks.
       ITU-T G.694.1 (10/2020): Spectral grids for WDM applications:
       DWDM frequency grid";
  }

  identity l0-grid-type {
    description
      "Layer 0 grid type";
    reference
      "RFC 6163: Framework for GMPLS and Path Computation Element
       (PCE) Control of Wavelength Switched Optical Networks (WSONs),
       ITU-T G.694.1 (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
      "RFC 7698: Framework and Requirements for GMPLS-Based Control
       of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM)
       Networks,
       ITU-T G.694.1 (10/2020): Spectral grids for WDM applications:
       DWDM frequency grid";
  }

  identity wson-grid-dwdm {
    base l0-grid-type;
    description
      "DWDM grid";
    reference
      "RFC 6163:Framework for GMPLS and Path Computation Element
       (PCE) Control of Wavelength Switched Optical Networks (WSONs),
       ITU-T G.694.1 (10/2020): Spectral grids for WDM applications:
       DWDM frequency grid";
  }

  identity wson-grid-cwdm {
    base l0-grid-type;
    description
      "CWDM grid";
    reference
      "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
      "DWDM channel-spacing type";
    reference
      "RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC)
       Label Switching Routers,
       ITU-T G.694.1 (10/2020): Spectral grids for WDM applications:
       DWDM frequency grid";
  }

  identity dwdm-100ghz {
    base dwdm-ch-spc-type;
    description
      "100 GHz channel spacing";
  }

  identity dwdm-50ghz {
    base dwdm-ch-spc-type;
    description
      "50 GHz channel spacing";
  }

  identity dwdm-25ghz {
    base dwdm-ch-spc-type;
    description
      "25 GHz channel spacing";
  }

  identity dwdm-12p5ghz {
    base dwdm-ch-spc-type;
    description
      "12.5 GHz channel spacing";
  }

  identity flexi-ch-spc-type {
    description
      "Flexi-grid channel-spacing type";
    reference
      "RFC 7698: Framework and Requirements for GMPLS-Based Control
       of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM)
       Networks,
       ITU-T G.694.1 (10/2020): Spectral grids for WDM applications:
       DWDM frequency grid";
  }

  identity flexi-ch-spc-6p25ghz {
    base flexi-ch-spc-type;
    description
      "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.5 GHz slot width granularity";
  }

  identity cwdm-ch-spc-type {
    description
      "CWDM channel-spacing type";
    reference
      "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\")" {
            description
              "Valid only when grid type is DWDM.";
          }
          type l0-types:dwdm-n;
          description
            "The central frequency of DWDM.";
          reference
            "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\")" {
            description
              "Valid only when grid type is CWDM.";
          }
          type l0-types:cwdm-n;
          description
            "Channel wavelength computing input.";
          reference
            "RFC 6205: Generalized Labels for Lambda-Switch-Capable
             (LSC) Label Switching Routers";
        }
      }
    }
    reference
      "RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC)
       Label Switching Routers";
  }

  grouping wson-label-hop {
    description
      "Generic label-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 subcarrier
                 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
            "RFC 6205: Generalized Labels for Lambda-Switch-Capable
             (LSC) Label Switching Routers";
        }
      }
    }
    reference
      "RFC 6205: Generalized Labels for Lambda-Switch-Capable (LSC)
       Label Switching Routers";
  }

  grouping l0-label-range-info {
    description
      "Information about Layer 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
        "RFC 4203: OSPF Extensions in Support of Generalized
         Multi-Protocol Label Switching (GMPLS)";
    }
    reference
      "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\")" {
            description
              "Valid only when grid type is DWDM.";
          }
          type identityref {
            base dwdm-ch-spc-type;
          }
          description
            "Label-step is the channel spacing (GHz), e.g., 100.000,
             50.000, 25.000, or 12.500 GHz for DWDM.";
          reference
            "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\")" {
            description
              "Valid only when grid type is CWDM.";
          }
          type identityref {
            base cwdm-ch-spc-type;
          }
          description
            "Label-step is the channel spacing (nm), i.e., 20 nm
             for CWDM, which is the only value defined for CWDM.";
          reference
            "RFC 6205: Generalized Labels for Lambda-Switch-Capable
             (LSC) Label Switching Routers";
        }
      }
    }
    reference
      "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
      "The flexi-grid label-start or label-end used to specify
       flexi-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
      "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
      "RFC 7698: Framework and Requirements for GMPLS-Based Control
       of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM)
       Networks";
  }

  grouping flexi-grid-label-hop {
    description
      "Generic label-hop information for 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 {
          key "flexi-n";
          uses flexi-grid-frequency-slot;
          description
            "List of subcarrier channels for flexi-grid super
             channel.";
        }
      }
    }
    reference
      "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;
        }
        default "flexi-swg-12p5ghz";
        description
          "Minimum space between slot widths. Default is 12.500
           GHz.";
        reference
          "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";
        }
        default "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
          "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 '. &gt;= ../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 slot width.  If not specified, maximum
           slot width is equal to minimum slot width.";
        reference
          "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;
      }
      default "flexi-ch-spc-6p25ghz";
      description
        "Label-step is the nominal central frequency granularity
         (GHz), e.g., 6.25 GHz.";
      reference
        "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 in RFC 8363.";
      reference
        "RFC 8363: GMPLS OSPF-TE Extensions in Support of Flexi-Grid
         Dense Wavelength Division Multiplexing (DWDM) Networks";
    }
  }
}
</sourcecode>
    </section>
    <section anchor="Security" toc="include" numbered="true" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-4-1">
   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" sectionFormat="of" derivedContent="RFC6241"/> or RESTCONF <xref target="RFC8040" format="default" sectionFormat="of" derivedContent="RFC8040"/>.  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" sectionFormat="of" derivedContent="RFC6242"/>.  The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS <xref target="RFC8446" format="default" sectionFormat="of" derivedContent="RFC8446"/>.
      </t>
      <t indent="0" pn="section-4-2">
The Network Configuration Access Control Model (NACM) <xref target="RFC8341" format="default" sectionFormat="of" derivedContent="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 NETCONF protocol over Secure Shell (SSH) specification <xref target="RFC6242" format="default" sectionFormat="of" derivedContent="RFC6242"/> describes a method for invoking and running NETCONF within a Secure Shell (SSH) session as an SSH subsystem. 
      </t>
      <t indent="0" pn="section-4-3">
  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 other Layer 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 of these 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 indent="0" pn="section-4-4">
   The security considerations spelled out in the YANG 1.1 specification <xref target="RFC7950" format="default" sectionFormat="of" derivedContent="RFC7950"/> apply for this document as well.
      </t>
    </section>
    <section anchor="IANA" toc="include" numbered="true" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-5-1">
  IANA has assigned new URIs from the "IETF XML Registry" <xref target="RFC3688" format="default" sectionFormat="of" derivedContent="RFC3688"/> as follows:
      </t>
      <dl spacing="compact" indent="3" newline="false" pn="section-5-2">
        <dt pn="section-5-2.1">URI:
</dt>
        <dd pn="section-5-2.2">urn:ietf:params:xml:ns:yang:ietf-layer0-types 
</dd>
        <dt pn="section-5-2.3">Registrant Contact:
</dt>
        <dd pn="section-5-2.4">The IESG  
</dd>
        <dt pn="section-5-2.5">XML:
</dt>
        <dd pn="section-5-2.6">N/A; the requested URI is an XML namespace.
</dd>
      </dl>
      <t indent="0" pn="section-5-3"> 
   This document registers the following YANG module in the "YANG Module Names" registry <xref target="RFC7950" format="default" sectionFormat="of" derivedContent="RFC7950"/>.
      </t>
      <dl spacing="compact" indent="3" newline="false" pn="section-5-4">
        <dt pn="section-5-4.1">Name:
</dt>
        <dd pn="section-5-4.2">ietf-layer0-types   
</dd>
        <dt pn="section-5-4.3">Namespace:
</dt>
        <dd pn="section-5-4.4">urn:ietf:params:xml:ns:yang:ietf-layer0-types
</dd>
        <dt pn="section-5-4.5">Prefix:
</dt>
        <dd pn="section-5-4.6">l0-types 
</dd>
        <dt pn="section-5-4.7">Reference:
</dt>
        <dd pn="section-5-4.8">RFC 9093
</dd>
      </dl>
    </section>
  </middle>
  <back>
    <references pn="section-6">
      <name slugifiedName="name-references">References</name>
      <references pn="section-6.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="ITU-Tg6982" quoteTitle="true" derivedAnchor="ITU-Tg6982">
          <front>
            <title>Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces</title>
            <author>
              <organization showOnFrontPage="true">ITU-T</organization>
            </author>
            <date month="November" year="2018"/>
          </front>
          <refcontent>ITU-T Recommendation G.698.2</refcontent>
        </reference>
        <reference anchor="RFC4203" target="https://www.rfc-editor.org/info/rfc4203" quoteTitle="true" derivedAnchor="RFC4203">
          <front>
            <title>OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)</title>
            <author initials="K." surname="Kompella" fullname="K. Kompella" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="Y." surname="Rekhter" fullname="Y. Rekhter" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2005" month="October"/>
            <abstract>
              <t indent="0">This document specifies encoding of extensions to the OSPF routing protocol in support of Generalized Multi-Protocol Label Switching (GMPLS).  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4203"/>
          <seriesInfo name="DOI" value="10.17487/RFC4203"/>
        </reference>
        <reference anchor="RFC6163" target="https://www.rfc-editor.org/info/rfc6163" quoteTitle="true" derivedAnchor="RFC6163">
          <front>
            <title>Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs)</title>
            <author initials="Y." surname="Lee" fullname="Y. Lee" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="G." surname="Bernstein" fullname="G. Bernstein" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="W." surname="Imajuku" fullname="W. Imajuku">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2011" month="April"/>
            <abstract>
              <t indent="0">This document provides a framework for applying Generalized Multi-Protocol Label Switching (GMPLS) and the Path Computation Element (PCE) architecture to the control of Wavelength Switched Optical Networks (WSONs).  In particular, it examines Routing and Wavelength Assignment (RWA) of optical paths.</t>
              <t indent="0">This document focuses on topological elements and path selection constraints that are common across different WSON environments; as such, it does not address optical impairments in any depth. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6163"/>
          <seriesInfo name="DOI" value="10.17487/RFC6163"/>
        </reference>
        <reference anchor="RFC6205" target="https://www.rfc-editor.org/info/rfc6205" quoteTitle="true" derivedAnchor="RFC6205">
          <front>
            <title>Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers</title>
            <author initials="T." surname="Otani" fullname="T. Otani" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="D." surname="Li" fullname="D. Li" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2011" month="March"/>
            <abstract>
              <t indent="0">Technology in the optical domain is constantly evolving, and, as a consequence, new equipment providing lambda switching capability has been developed and is currently being deployed.</t>
              <t indent="0">Generalized MPLS (GMPLS) is a family of protocols that can be used to operate networks built from a range of technologies including wavelength (or lambda) switching.  For this purpose, GMPLS defined a wavelength label as only having significance between two neighbors.  Global wavelength semantics are not considered.</t>
              <t indent="0">In order to facilitate interoperability in a network composed of next generation lambda-switch-capable equipment, this document defines a standard lambda label format that is compliant with the Dense Wavelength Division Multiplexing (DWDM) and Coarse Wavelength Division Multiplexing (CWDM) grids defined by the International Telecommunication Union Telecommunication Standardization Sector. The label format defined in this document can be used in GMPLS signaling and routing protocols.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6205"/>
          <seriesInfo name="DOI" value="10.17487/RFC6205"/>
        </reference>
        <reference anchor="RFC6241" target="https://www.rfc-editor.org/info/rfc6241" quoteTitle="true" derivedAnchor="RFC6241">
          <front>
            <title>Network Configuration Protocol (NETCONF)</title>
            <author initials="R." surname="Enns" fullname="R. Enns" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Bjorklund" fullname="M. Bjorklund" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Schoenwaelder" fullname="J. Schoenwaelder" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Bierman" fullname="A. Bierman" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2011" month="June"/>
            <abstract>
              <t indent="0">The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices.  It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages.  The NETCONF protocol operations are realized as remote procedure calls (RPCs).  This document obsoletes RFC 4741.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6241"/>
          <seriesInfo name="DOI" value="10.17487/RFC6241"/>
        </reference>
        <reference anchor="RFC6242" target="https://www.rfc-editor.org/info/rfc6242" quoteTitle="true" derivedAnchor="RFC6242">
          <front>
            <title>Using the NETCONF Protocol over Secure Shell (SSH)</title>
            <author initials="M." surname="Wasserman" fullname="M. Wasserman">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2011" month="June"/>
            <abstract>
              <t indent="0">This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem.  This document obsoletes RFC 4742.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6242"/>
          <seriesInfo name="DOI" value="10.17487/RFC6242"/>
        </reference>
        <reference anchor="RFC7698" target="https://www.rfc-editor.org/info/rfc7698" quoteTitle="true" derivedAnchor="RFC7698">
          <front>
            <title>Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks</title>
            <author initials="O." surname="Gonzalez de Dios" fullname="O. Gonzalez de Dios" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Casellas" fullname="R. Casellas" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="F." surname="Zhang" fullname="F. Zhang">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="X." surname="Fu" fullname="X. Fu">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="D." surname="Ceccarelli" fullname="D. Ceccarelli">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="I." surname="Hussain" fullname="I. Hussain">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2015" month="November"/>
            <abstract>
              <t indent="0">To allow efficient allocation of optical spectral bandwidth for systems that have high bit-rates, the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) has extended its Recommendations G.694.1 and G.872 to include a new Dense Wavelength Division Multiplexing (DWDM) grid by defining a set of nominal central frequencies, channel spacings, and the concept of the "frequency slot".  In such an environment, a data-plane connection is switched based on allocated, variable-sized frequency ranges within the optical spectrum, creating what is known as a flexible grid (flexi-grid).</t>
              <t indent="0">Given the specific characteristics of flexi-grid optical networks and their associated technology, this document defines a framework and the associated control-plane requirements for the application of the existing GMPLS architecture and control-plane protocols to the control of flexi-grid DWDM networks.  The actual extensions to the GMPLS protocols will be defined in companion documents.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7698"/>
          <seriesInfo name="DOI" value="10.17487/RFC7698"/>
        </reference>
        <reference anchor="RFC7699" target="https://www.rfc-editor.org/info/rfc7699" quoteTitle="true" derivedAnchor="RFC7699">
          <front>
            <title>Generalized Labels for the Flexi-Grid in Lambda Switch Capable (LSC) Label Switching Routers</title>
            <author initials="A." surname="Farrel" fullname="A. Farrel">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="D." surname="King" fullname="D. King">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="Y." surname="Li" fullname="Y. Li">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="F." surname="Zhang" fullname="F. Zhang">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2015" month="November"/>
            <abstract>
              <t indent="0">GMPLS supports the description of optical switching by identifying entries in fixed lists of switchable wavelengths (called grids) through the encoding of lambda labels.  Work within the ITU-T Study Group 15 has defined a finer-granularity grid, and the facility to flexibly select different widths of spectrum from the grid.  This document defines a new GMPLS lambda label format to support this flexi-grid.</t>
              <t indent="0">This document updates RFCs 3471 and 6205 by introducing a new label format.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7699"/>
          <seriesInfo name="DOI" value="10.17487/RFC7699"/>
        </reference>
        <reference anchor="RFC7950" target="https://www.rfc-editor.org/info/rfc7950" quoteTitle="true" derivedAnchor="RFC7950">
          <front>
            <title>The YANG 1.1 Data Modeling Language</title>
            <author initials="M." surname="Bjorklund" fullname="M. Bjorklund" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2016" month="August"/>
            <abstract>
              <t indent="0">YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols.  This document describes the syntax and semantics of version 1.1 of the YANG language.  YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification.  There are a small number of backward incompatibilities from YANG version 1.  This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7950"/>
          <seriesInfo name="DOI" value="10.17487/RFC7950"/>
        </reference>
        <reference anchor="RFC8040" target="https://www.rfc-editor.org/info/rfc8040" quoteTitle="true" derivedAnchor="RFC8040">
          <front>
            <title>RESTCONF Protocol</title>
            <author initials="A." surname="Bierman" fullname="A. Bierman">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="K." surname="Watsen" fullname="K. Watsen">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2017" month="January"/>
            <abstract>
              <t indent="0">This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8040"/>
          <seriesInfo name="DOI" value="10.17487/RFC8040"/>
        </reference>
        <reference anchor="RFC8341" target="https://www.rfc-editor.org/info/rfc8341" quoteTitle="true" derivedAnchor="RFC8341">
          <front>
            <title>Network Configuration Access Control Model</title>
            <author initials="A." surname="Bierman" fullname="A. Bierman">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2018" month="March"/>
            <abstract>
              <t indent="0">The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability.  There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.  This document defines such an access control model.</t>
              <t indent="0">This document obsoletes RFC 6536.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="91"/>
          <seriesInfo name="RFC" value="8341"/>
          <seriesInfo name="DOI" value="10.17487/RFC8341"/>
        </reference>
        <reference anchor="RFC8342" target="https://www.rfc-editor.org/info/rfc8342" quoteTitle="true" derivedAnchor="RFC8342">
          <front>
            <title>Network Management Datastore Architecture (NMDA)</title>
            <author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Schoenwaelder" fullname="J. Schoenwaelder">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="P." surname="Shafer" fullname="P. Shafer">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="K." surname="Watsen" fullname="K. Watsen">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Wilton" fullname="R. Wilton">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2018" month="March"/>
            <abstract>
              <t indent="0">Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model.  This document updates RFC 7950.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8342"/>
          <seriesInfo name="DOI" value="10.17487/RFC8342"/>
        </reference>
        <reference anchor="RFC8363" target="https://www.rfc-editor.org/info/rfc8363" quoteTitle="true" derivedAnchor="RFC8363">
          <front>
            <title>GMPLS OSPF-TE Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks</title>
            <author initials="X." surname="Zhang" fullname="X. Zhang">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="H." surname="Zheng" fullname="H. Zheng">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Casellas" fullname="R. Casellas">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="O." surname="Gonzalez de Dios" fullname="O. Gonzalez de Dios">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="D." surname="Ceccarelli" fullname="D. Ceccarelli">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2018" month="May"/>
            <abstract>
              <t indent="0">The International Telecommunication Union Telecommunication standardization sector (ITU-T) has extended its Recommendations G.694.1 and G.872 to include a new Dense Wavelength Division Multiplexing (DWDM) grid by defining channel spacings, a set of nominal central frequencies, and the concept of the "frequency slot". Corresponding techniques for data-plane connections are known as "flexi-grid".</t>
              <t indent="0">Based on the characteristics of flexi-grid defined in G.694.1 and in RFCs 7698 and 7699, this document describes the Open Shortest Path First - Traffic Engineering (OSPF-TE) extensions in support of GMPLS control of networks that include devices that use the new flexible optical grid.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8363"/>
          <seriesInfo name="DOI" value="10.17487/RFC8363"/>
        </reference>
        <reference anchor="RFC8446" target="https://www.rfc-editor.org/info/rfc8446" quoteTitle="true" derivedAnchor="RFC8446">
          <front>
            <title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
            <author initials="E." surname="Rescorla" fullname="E. Rescorla">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2018" month="August"/>
            <abstract>
              <t indent="0">This document specifies version 1.3 of the Transport Layer Security (TLS) protocol.  TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery.</t>
              <t indent="0">This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961.  This document also specifies new requirements for TLS 1.2 implementations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8446"/>
          <seriesInfo name="DOI" value="10.17487/RFC8446"/>
        </reference>
        <reference anchor="RFC8776" target="https://www.rfc-editor.org/info/rfc8776" quoteTitle="true" derivedAnchor="RFC8776">
          <front>
            <title>Common YANG Data Types for Traffic Engineering</title>
            <author initials="T." surname="Saad" fullname="T. Saad">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Gandhi" fullname="R. Gandhi">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="X." surname="Liu" fullname="X. Liu">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="V." surname="Beeram" fullname="V. Beeram">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="I." surname="Bryskin" fullname="I. Bryskin">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2020" month="June"/>
            <abstract>
              <t indent="0">This document defines a collection of common data types and groupings in YANG data modeling language. These derived common types and groupings are intended to be imported by modules that model Traffic Engineering (TE) configuration and state capabilities.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8776"/>
          <seriesInfo name="DOI" value="10.17487/RFC8776"/>
        </reference>
        <reference anchor="RFC8795" target="https://www.rfc-editor.org/info/rfc8795" quoteTitle="true" derivedAnchor="RFC8795">
          <front>
            <title>YANG Data Model for Traffic Engineering (TE) Topologies</title>
            <author initials="X." surname="Liu" fullname="X. Liu">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="I." surname="Bryskin" fullname="I. Bryskin">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="V." surname="Beeram" fullname="V. Beeram">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="T." surname="Saad" fullname="T. Saad">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="H." surname="Shah" fullname="H. Shah">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="O." surname="Gonzalez de Dios" fullname="O. Gonzalez de Dios">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2020" month="August"/>
            <abstract>
              <t indent="0">This document defines a YANG data model for representing, retrieving, and manipulating Traffic Engineering (TE) Topologies. The model serves as a base model that other technology-specific TE topology models can augment.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8795"/>
          <seriesInfo name="DOI" value="10.17487/RFC8795"/>
        </reference>
      </references>
      <references pn="section-6.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="ITU-Tg6941" quoteTitle="true" derivedAnchor="ITU-Tg6941">
          <front>
            <title>Spectral grids for WDM applications: DWDM frequency grid</title>
            <author>
              <organization showOnFrontPage="true">ITU-T</organization>
            </author>
            <date month="October" year="2020"/>
          </front>
          <seriesInfo name="ITU-T Recommendation" value="G.694.1"/>
        </reference>
        <reference anchor="ITU-Tg6942" quoteTitle="true" derivedAnchor="ITU-Tg6942">
          <front>
            <title>Spectral grids for WDM applications: CWDM wavelength grid</title>
            <author>
              <organization showOnFrontPage="true">ITU-T</organization>
            </author>
            <date month="December" year="2003"/>
          </front>
          <seriesInfo name="ITU-T Recommendation" value="G.694.2"/>
        </reference>
        <reference anchor="RFC3688" target="https://www.rfc-editor.org/info/rfc3688" quoteTitle="true" derivedAnchor="RFC3688">
          <front>
            <title>The IETF XML Registry</title>
            <author initials="M." surname="Mealling" fullname="M. Mealling">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2004" month="January"/>
            <abstract>
              <t indent="0">This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="81"/>
          <seriesInfo name="RFC" value="3688"/>
          <seriesInfo name="DOI" value="10.17487/RFC3688"/>
        </reference>
        <reference anchor="RFC7446" target="https://www.rfc-editor.org/info/rfc7446" quoteTitle="true" derivedAnchor="RFC7446">
          <front>
            <title>Routing and Wavelength Assignment Information Model for Wavelength Switched Optical Networks</title>
            <author initials="Y." surname="Lee" fullname="Y. Lee" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="G." surname="Bernstein" fullname="G. Bernstein" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="D." surname="Li" fullname="D. Li">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="W." surname="Imajuku" fullname="W. Imajuku">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2015" month="February"/>
            <abstract>
              <t indent="0">This document provides a model of information needed by the Routing and Wavelength Assignment (RWA) process in Wavelength Switched Optical Networks (WSONs).  The purpose of the information described in this model is to facilitate constrained optical path computation in WSONs.  This model takes into account compatibility constraints between WSON signal attributes and network elements but does not include constraints due to optical impairments.  Aspects of this information that may be of use to other technologies utilizing a GMPLS control plane are discussed.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7446"/>
          <seriesInfo name="DOI" value="10.17487/RFC7446"/>
        </reference>
        <reference anchor="RFC7581" target="https://www.rfc-editor.org/info/rfc7581" quoteTitle="true" derivedAnchor="RFC7581">
          <front>
            <title>Routing and Wavelength Assignment Information Encoding for Wavelength Switched Optical Networks</title>
            <author initials="G." surname="Bernstein" fullname="G. Bernstein" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="Y." surname="Lee" fullname="Y. Lee" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="D." surname="Li" fullname="D. Li">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="W." surname="Imajuku" fullname="W. Imajuku">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Han" fullname="J. Han">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2015" month="June"/>
            <abstract>
              <t indent="0">A Wavelength Switched Optical Network (WSON) requires certain key information fields be made available to facilitate path computation and the establishment of Label Switched Paths (LSPs). The information model described in "Routing and Wavelength                           Assignment Information Model for Wavelength Switched Optical Networks" (RFC 7446) shows what information is required at specific points in the WSON. Part of the WSON information model contains aspects that may be of general applicability to other technologies, while other parts are specific to WSONs.</t>
              <t indent="0">This document provides efficient, protocol-agnostic encodings for the WSON-specific information fields.  It is intended that protocol- specific documents will reference this memo to describe how information is carried for specific uses.  Such encodings can be used to extend GMPLS signaling and routing protocols.  In addition, these encodings could be used by other mechanisms to convey this same information to a Path Computation Element (PCE).</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7581"/>
          <seriesInfo name="DOI" value="10.17487/RFC7581"/>
        </reference>
      </references>
    </references>
    <section toc="include" numbered="false" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.a-1">
    The authors and the working group give their sincere thanks to <contact fullname="Robert Wilton"/> for the YANG doctor review and <contact fullname="Tom Petch"/> for his comments during the model and document development.
      </t>
    </section>
    <section anchor="Contributor" toc="include" numbered="false" removeInRFC="false" pn="section-appendix.b">
      <name slugifiedName="name-contributors">Contributors</name>
      <author initials="D" surname="Dhody" fullname="Dhruv Dhody">
        <organization showOnFrontPage="true">Huawei</organization>
        <address>
          <email>dhruv.ietf@gmail.com</email>
        </address>
      </author>
      <author initials="B. Y." surname="Yoon" fullname="Bin Yeong Yoon">
        <organization showOnFrontPage="true">ETRI</organization>
        <address>
          <email>byyun@etri.re.kr</email>
        </address>
      </author>
      <author initials="R" surname="Vilalta" fullname="Ricard Vilalta">
        <organization showOnFrontPage="true">CTTC</organization>
        <address>
          <email>ricard.vilalta@cttc.es</email>
        </address>
      </author>
      <author initials="I" surname="Busi" fullname="Italo Busi">
        <organization showOnFrontPage="true">Huawei</organization>
        <address>
          <email>Italo.Busi@huawei.com</email>
        </address>
      </author>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.c">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author fullname="郑好棉" asciiFullname="Haomian Zheng">
        <organization ascii="Huawei Technologies" showOnFrontPage="true">华为技术有限公司</organization>
        <address>
          <postal>
            <street ascii="H1, Huawei Xiliu Beipo Village, Songshan Lake">松山湖华为溪流背坡村H1</street>
            <city ascii="Dongguan">东莞</city>
            <region ascii="Guangdong">广东</region>
            <code>523808</code>
            <country ascii="China">中国</country>
          </postal>
          <email>zhenghaomian@huawei.com</email>
        </address>
      </author>
      <author fullname="Young Lee" initials="Y." surname="Lee">
        <organization showOnFrontPage="true">Samsung</organization>
        <address>
          <postal>
            <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 showOnFrontPage="true">Futurewei</organization>
        <address>
          <email>aihuaguo.ietf@gmail.com</email>
        </address>
      </author>
      <author initials="V." surname="Lopez" fullname="Victor Lopez">
        <organization showOnFrontPage="true">Nokia</organization>
        <address>
          <email>victor.lopez@nokia.com</email>
        </address>
      </author>
      <author initials="D." surname="King" fullname="Daniel King">
        <organization showOnFrontPage="true">University of Lancaster</organization>
        <address>
          <email>d.king@lancaster.ac.uk</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
