RFC 9093
A YANG Data Model for Layer 0 Types
RFC 9093: A YANG Data Model for Layer 0 Types π¦
okay bestie, the title block is giving everything π this is RFC 9093 from the IETF (Internet Engineering Task Force), published in August 2021. It's a Standards Track document, so it's an actual Internet standard and not just vibes π The ISSN is 2070-1721 β¨ The authors are ιε₯½ζ£ (H. Zheng) from Huawei Technologies (εδΈΊζζ―ζιε ¬εΈ), Y. Lee from Samsung, A. Guo from Futurewei, V. Lopez from Nokia, and D. King from the University of Lancaster π The title block doesn't list anything this document obsoletes or updates, so no drama there π
Abstract πΈ
this doc defines a bunch of common data types and groupings in the YANG data modeling language π§ The derived types and groupings are meant to be imported by modules that model Layer 0 optical Traffic Engineering (TE) configuration and state capabilities, like Wavelength Switched Optical Networks (WSONs) and flexi-grid Dense Wavelength Division Multiplexing (DWDM) networks. literally the optical networking glow-up π₯
Status of This Memo π
okay so this is an Internet Standards Track document π
this is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community, received public review, and was approved for publication by the Internet Engineering Steering Group (IESG). If you want more info on Internet Standards, check Section 2 of RFC 7841 π
for the current status of this document, any errata, and how to send feedback, go to https://www.rfc-editor.org/info/rfc9093 β¨
Copyright Notice π
Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved.
this document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) as in effect on the date of publication. please read these carefully, because they explain your rights and restrictions for 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 they come without warranty, as described in the Simplified BSD License π«Ά
Table of Contents π
1. Introduction
1.1. Terminology and Notations
1.2. Prefix in Data Node Names
2. Layer 0 Types Module Contents
3. YANG Module for Layer 0 Types
4. Security Considerations
5. IANA Considerations
6. References
6.1. Normative References
6.2. Informative References
Acknowledgements
Contributors
Authors' Addresses
1. Introduction β¨
okay so YANG [RFC7950] is a data modeling language that's used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols, like the Network Configuration Protocol (NETCONF) [RFC6241] π YANG has a small set of built-in data types, and it gives you ways to derive other types from those built-ins π§
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 for modeling Traffic Engineering (TE) features, plus non-TE features (like physical network configuration aspects), for Layer 0 optical networks, in models defined outside of this document. Layer 0 types here apply to Wavelength Switched Optical Networks (WSONs) [RFC6163] [ITU-Tg6982] and flexi-grid Dense Wavelength Division Multiplexing (DWDM) networks [RFC7698] [ITU-Tg6941] πΈ
1.1. Terminology and Notations π
refer to [RFC7446] and [RFC7581] for the key terms used in this document. The terminology for describing YANG data models is in [RFC7950] π
the YANG data model in this document conforms to the Network Management Datastore Architecture defined in [RFC8342] π«Ά
1.2. Prefix in Data Node Names π
in this document, names of data nodes and other data model objects get prefixed with the standard prefix associated with the corresponding YANG imported modules π
+==========+===================+===========+
| Prefix | YANG module | Reference |
+==========+===================+===========+
| l0-types | ietf-layer0-types | RFC 9093 |
+----------+-------------------+-----------+
Table 1: Data Node Names
the YANG module "ietf-layer0-types" (defined in Section 3) references [RFC4203], [RFC6163], [RFC6205], [RFC7698], [RFC7699], [RFC8363], [ITU-Tg6941], and [ITU-Tg6942] β
2. Layer 0 Types Module Contents π
this document defines a YANG module for common Layer 0 types, called ietf-layer0-types π It's used for WSON and flexi-grid DWDM networks. The "ietf-layer0-types" module has these YANG reusable types and groupings:
l0-grid-type: a base YANG identity for the grid type, as defined in [RFC6163] and [RFC7698] π§dwdm-ch-spc-type: a base YANG identity for the DWDM channel-spacing type, as defined in [RFC6205] πΈcwdm-ch-spc-type: a base YANG identity for the Coarse Wavelength Division Multiplexing (CWDM) channel-spacing type, as defined in [RFC6205] π¦wson-label-start-end: the WSON label range was defined in [RFC6205], and the generic topology model defines the label-start/label-end in [RFC8795]. This grouping shows the WSON-specific label-start and label-end information πwson-label-hop: the WSON label range was defined in [RFC6205], and the generic topology model defines the label-hop in [RFC8795]. This grouping shows the WSON-specific label-hop information π«Άl0-label-range-info: a YANG grouping that defines the Layer 0 label range information applicable for WSON, as defined in [RFC6205]. It's used in the flexi-grid DWDM by adding more flexi-grid-specific parameters π₯wson-label-step: a YANG grouping that defines label steps for WSON, as defined in [RFC8776] πflexi-grid-label-start-end: the flexi-grid label range was defined in [RFC7698], and the generic topology model defines the label-start/label-end in [RFC8795]. This grouping shows the flexi-grid-specific label-start and label-end information πflexi-grid-label-hop: the flexi-grid label range was defined in [RFC7698], and the generic topology model defines the label-hop in [RFC8795]. This grouping shows the WSON-specific label-hop information πflexi-grid-label-range-info: a YANG grouping that defines flexi-grid label range information, as defined in [RFC7698] and [RFC8363] βflexi-grid-label-step: a YANG grouping that defines flexi-grid label steps, as defined in [RFC8776] π
3. YANG Module for Layer 0 Types π§
here's the actual YANG module, copied exactly as-is, because we do NOT touch the code π ββοΈ
<CODE BEGINS> file "ietf-layer0-types@2021-08-13.yang"
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: <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.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)) 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";
}
Okay so the tail of that flexi-slot-width-granularity bit is wrapping up, and then we hit the big base identity, l0-grid-type π¦. It's the parent for every grid flavour below it, so it's giving "umbrella" energy πβ¨. Its references point at RFC 6163 and two ITU-T G.694 docs, the DWDM one and the CWDM one.
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";
}
The grid identities are giving "family tree" energy π³π: flexi-grid-dwdm, wson-grid-dwdm and wson-grid-cwdm all hang off l0-grid-type, and the channel-spacing types each get their own little family of values underneath them π§β¨
The groupings are where it gets spicy πΆοΈπ₯. wson-label-start-end and wson-label-hop each split into DWDM and CWDM cases using a choice, and the when statements make sure the right leaf only shows up when the grid type matches π
. l0-label-range-info is the simple one, just a grid type and a priority π. Then wson-label-step picks the right channel-spacing identity based on the grid, and the flexi-grid groupings handle flexi-n and flexi-m for the central frequency and slot width π¦. Literally so much structure, bestie ππ«Ά
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 '. >= ../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";
}
}
}
<CODE ENDS>
4. Security Considerations π
okay bestie, let's talk security, because this part is SERIOUS π The YANG module in this document is basically a schema for data that's meant to be reached through network management protocols like NETCONF [RFC6241] or RESTCONF [RFC8040] π§. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446]. Main character energy for security, no cap β¨.
The Network Configuration Access Control Model (NACM) [RFC8341] is the bouncer π . It gives you a way to restrict particular NETCONF or RESTCONF users to a preconfigured subset of all the available protocol operations and content. The NETCONF protocol over Secure Shell (SSH) specification [RFC6242] also describes how to invoke and run NETCONF inside an SSH session as an SSH subsystem π«Ά.
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's critical to think about how imported definitions get used and accessed through RPC operations, because the resulting schema will have data nodes that can be writable or readable, and that has a big effect on network operations if it's used wrong or maliciously π.
Warning, bestie: all of these considerations belong in the document that defines the modules that import from this YANG module. So it's really important to manage access to the resulting data nodes that are considered sensitive or vulnerable in some network environments. π¨
The security considerations spelled out in the YANG 1.1 specification [RFC7950] apply to this document as well π.
5. IANA Considerations πΈ
IANA has assigned new URIs from the "IETF XML Registry" [RFC3688] as follows:
URI: urn:ietf:params:xml:ns:yang:ietf-layer0-types
Registrant Contact: The IESG
XML: N/A; the requested URI is an XML namespace.
This document registers the following YANG module in the "YANG Module Names" registry [RFC7950]:
Name: ietf-layer0-types
Namespace: urn:ietf:params:xml:ns:yang:ietf-layer0-types
Prefix: l0-types
Reference: RFC 9093
6. References π
6.1. Normative References
[ITU-Tg6982]ITU-T, "Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces", ITU-T Recommendation G.698.2, November 2018.[RFC4203]Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)", RFC 4203, DOI10.17487/RFC4203, October 2005,https://www.rfc-editor.org/info/rfc4203.[RFC6163]Lee, Y., Ed., Bernstein, G., Ed., and W. Imajuku, "Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs)", RFC 6163, DOI10.17487/RFC6163, April 2011,https://www.rfc-editor.org/info/rfc6163.[RFC6205]Otani, T., Ed. and D. Li, Ed., "Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers", RFC 6205, DOI10.17487/RFC6205, March 2011,https://www.rfc-editor.org/info/rfc6205.[RFC6241]Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI10.17487/RFC6241, June 2011,https://www.rfc-editor.org/info/rfc6241.[RFC6242]Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI10.17487/RFC6242, June 2011,https://www.rfc-editor.org/info/rfc6242.[RFC7698]Gonzalez de Dios, O., Ed., Casellas, R., Ed., Zhang, F., Fu, X., Ceccarelli, D., and I. Hussain, "Framework and Requirements for GMPLS-Based Control of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks", RFC 7698, DOI10.17487/RFC7698, November 2015,https://www.rfc-editor.org/info/rfc7698.[RFC7699]Farrel, A., King, D., Li, Y., and F. Zhang, "Generalized Labels for the Flexi-Grid in Lambda Switch Capable (LSC) Label Switching Routers", RFC 7699, DOI10.17487/RFC7699, November 2015,https://www.rfc-editor.org/info/rfc7699.[RFC7950]Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI10.17487/RFC7950, August 2016,https://www.rfc-editor.org/info/rfc7950.[RFC8040]Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI10.17487/RFC8040, January 2017,https://www.rfc-editor.org/info/rfc8040.[RFC8341]Bierman, A. and M. Bjorklund, "Network Configuration Access Control Model", STD 91, RFC 8341, DOI10.17487/RFC8341, March 2018,https://www.rfc-editor.org/info/rfc8341.[RFC8342]Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI10.17487/RFC8342, March 2018,https://www.rfc-editor.org/info/rfc8342.[RFC8363]Zhang, X., Zheng, H., Casellas, R., Gonzalez de Dios, O., and D. Ceccarelli, "GMPLS OSPF-TE Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks", RFC 8363, DOI10.17487/RFC8363, May 2018,https://www.rfc-editor.org/info/rfc8363.[RFC8446]Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI10.17487/RFC8446, August 2018,https://www.rfc-editor.org/info/rfc8446.[RFC8776]Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, "Common YANG Data Types for Traffic Engineering", RFC 8776, DOI10.17487/RFC8776, June 2020,https://www.rfc-editor.org/info/rfc8776.[RFC8795]Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and O. Gonzalez de Dios, "YANG Data Model for Traffic Engineering (TE) Topologies", RFC 8795, DOI10.17487/RFC8795, August 2020,https://www.rfc-editor.org/info/rfc8795.
6.2. Informative References
[ITU-Tg6941]ITU-T, "Spectral grids for WDM applications: DWDM frequency grid", ITU-T Recommendation G.694.1, October 2020.[ITU-Tg6942]ITU-T, "Spectral grids for WDM applications: CWDM wavelength grid", ITU-T Recommendation G.694.2, December 2003.[RFC3688]Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI10.17487/RFC3688, January 2004,https://www.rfc-editor.org/info/rfc3688.[RFC7446]Lee, Y., Ed., Bernstein, G., Ed., Li, D., and W. Imajuku, "Routing and Wavelength Assignment Information Model for Wavelength Switched Optical Networks", RFC 7446, DOI10.17487/RFC7446, February 2015,https://www.rfc-editor.org/info/rfc7446.[RFC7581]Bernstein, G., Ed., Lee, Y., Ed., Li, D., Imajuku, W., and J. Han, "Routing and Wavelength Assignment Information Encoding for Wavelength Switched Optical Networks", RFC 7581, DOI10.17487/RFC7581, June 2015,https://www.rfc-editor.org/info/rfc7581.
Acknowledgements π«Ά
A huge shoutout from the authors and the working group π to Robert Wilton for the YANG doctor review, and to Tom Petch for the comments made during the model and document development. Iconic behaviour, honestly π.
Contributors π
Dhruv Dhody
Huawei
Email: dhruv.ietf@gmail.com
Bin Yeong Yoon
ETRI
Email: byyun@etri.re.kr
Ricard Vilalta
CTTC
Email: ricard.vilalta@cttc.es
Italo Busi
Huawei
Email: Italo.Busi@huawei.com
Authors' Addresses β¨
Okay bestie, time for the squad roll call π«Ά Here are the people who wrote this spec and how to reach them π
Haomian Zheng
Huawei Technologies
H1, Huawei Xiliu Beipo Village, Songshan Lake
Dongguan
Guangdong, 523808
China
Email: zhenghaomian@huawei.com
Additional contact information:
ιε₯½ζ£
δΈε½
523808
εΉΏδΈ δΈθ
ζΎε±±ζΉεδΈΊζΊͺζ΅θε‘ζH1
εδΈΊζζ―ζιε
¬εΈ
Young Lee
Samsung
South Korea
Email: younglee.tx@gmail.com
Aihua Guo
Futurewei
Email: aihuaguo.ietf@gmail.com
Victor Lopez
Nokia
Email: victor.lopez@nokia.com
Daniel King
University of Lancaster
Email: d.king@lancaster.ac.uk
Haomian is at Huawei Technologies in Dongguan, and the address also appears in Chinese for anyone who prefers it π§
Young is at Samsung in South Korea πΈ
Aihua is at Futurewei π¦
Victor is at Nokia π
Daniel is at the University of Lancaster π
Main character energy, all of them π
π¦ where this page comes from
- ietf: rfc9093 2021-08
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms