Internet Engineering Task Force G. Galimberti, Ed.
Internet-Draft C
Intended status: Standards Track D. Hiremagalur, Ed.
Expires: 14 August 2025 G. Grammel, Ed.
Juniper
R. Manzotti, Ed.
Cisco
D. Breuer, Ed.
DEUTSCHE TELEKOM AG
10 February 2025
A YANG data model to manage configurable DWDM optical interfaces
draft-ietf-ccamp-dwdm-if-param-yang-12
Abstract
This memo defines a Yang model related to the Optical Transceiver
parameters characterising coherent 100G and above interfaces. 100G
and above Transceivers support coherent modulation, multiple
modulation formats, multiple FEC codes including some not yet
specified (or in phase of specification by) [ITU-T_G.698.2] or any
other ITU-T recommendation. Use cases are described in [RFC7698].
The Yang model defined in this memo can be used for Optical
Parameters monitoring and/or configuration of DWDM interfaces. The
use of this model does not guarantee interworking of DWDM
transceivers. Optical path feasibility and interoperability has to
be determined by tools and algorithms outside the scope of this
document. The purpose of this model is to program interface
parameters to consistently configure the mode of operation of
transceivers.
Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Galimberti, et al. Expires 14 August 2025 [Page 1]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 14 August 2025.
Copyright Notice
Copyright (c) 2025 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) 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 Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Module Description . . . . . . . . . . . . . . . . . . . . . 4
3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. YANG Module Classification . . . . . . . . . . . . . . . 5
3.3. Optical Parameters Description . . . . . . . . . . . . . 5
3.3.1. Parameters at Ss . . . . . . . . . . . . . . . . . . 6
3.3.2. Interface at point Rs . . . . . . . . . . . . . . . . 6
3.4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 6
4. WDM Interface YANG Module . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 19
Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 20
Appendix C. YANG Tree . . . . . . . . . . . . . . . . . . . . . 20
Appendix D. Applicability examples . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
Galimberti, et al. Expires 14 August 2025 [Page 2]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
1. Introduction
This memo defines a Yang model for managing single channel optical
interface parameters of coherent interfaces supporting DWDM
applications, using the approach specified in G.698.2. This model
supports parameters to characterize coherent transceivers found in
current implementations to specify the mode of operation. As
application identifiers like those specified in [ITU-T_G.874] and
[ITU-T_G.698.2] may not always be available, mode templates are used.
A mode template describes transceiver characteristics in detail and
can be identified by a mode-id.
This draft refers to [RFC7698] use cases and is aligned to the
definition of [RFC9093] and its extension RFC9093-bis. Finally, the
models described in this draft are compliant with the models
described in draft-ietf-ccamp-optical-impairment-topology-yang and
draft-ietf-ccamp-wdm-tunnel-yang.
The key concept introduced by this YANG model in accordance with
draft-ietf-ccamp-optical-impairment-topology-yang and RFC9093-bis is
the notion of a mode. A mode is a combination of parameters and
parameter ranges that is supported by a transceiver. As an example,
operating a device in QPSK modulation may use a different FEC and
requires less OSNR than the same transceiver operating in QAM16
modulation. Given the number of parameters and their possible
combinations it is important for vendors to be able to qualify a set
of combinations which is the basis to define a mode. As described in
draft-ccamp-optical-impairment-topology-yang and modeled in
RFC9093-bis, the list of transceiver modes (properly classified in
standard, organizational and explicit modes) provide information
about the transmission capabilities of an optical DWDM interface.
The same approach is used in this RFC to allow the device netconf
agent to export such capabilities to the client controllers.
To advertise the capability supported by an interface, a list of
transceiver modes is provided by the device for each dwdm coherent
module (supported-modes).
Galimberti, et al. Expires 14 August 2025 [Page 3]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
The YANG model provides a configuration attribute named "configured-
mode" as a mean to provision the working mode of the interface from
the supported-modes listed as capabilities. Once provisioned,
current-wdm-if-parameters provide the means to configure specific
parameters at run time and retrieve configuration, performance and
operational state information from the module. For example, the
frequency is a parameter that can be set within min/max boundaries
defined in the current mode. Laser Temperature, RX/TX optical power,
RX OSNR, etc. however are read-only parameters available at run-time
that can be checked against the mode boundaries and may trigger
events.
2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14 [RFC2119]
[RFC8174] when, and only when, they appear in all capitals, as shown
here.
3. Module Description
3.1. Overview
Figure 1 shows a set of reference points, for single-channel
connection between transmitters (Tx) and receivers (Rx). Here the
DWDM network elements include an OM (Optical Multiplexer) and an OD
(Optical Demultiplexer) which are used as a pair with the opposing
element, one or more optical amplifiers and may also include one or
more ROADMs. Is to be noted that the TX L1 and RX L1 may be located
outside the DWDM network and fitted in the packet layer network
elements as pluggable modules.
Galimberti, et al. Expires 14 August 2025 [Page 4]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
Ss +-------------------------------------------------+ Rs
| | DWDM Network Elements | |
+---+ | | | \ / | | | +---+
Tx L1---|->| \ +------+ +------+ / |--|-->Rx L1
+---+ | | | | | +------+ | | | | | +---+
+---+ | | | | | | | | | | | | +---+
Tx L2---|->| OM |-->|------|->|ROADM |--|------|->| OD |--|-->Rx L2
+---+ | | | | | | | | | | | | +---+
+---+ | | | | | +------+ | | | | | +---+
Tx L3---|->| / | DWDM | | ^ | DWDM | \ |--|-->Rx L4
+---+ | | / | Link +----|--|----+ Link | \ | | +---+
+-----------+ | | +----------+
+----+ +----+
| |
Rs v | Ss
+-----+ +-----+
|RxL3 | |TxL4 |
+-----+ +-----+
Ss = reference point at the DWDM network element tributary output
Rs = reference point at the DWDM network element tributary input
Lx = Lambda x
OM = Optical Mux
OD = Optical Demux
ROADM = Reconfigurable Optical Add Drop Multiplexer
Figure 1: External transponder in WDM netwoks
from Fig. 5.1/G.698.2
3.2. YANG Module Classification
The model defined in this RFC is meant to be used as Device Model as
per definition in [RFC8199] and [RFC8309]
3.3. Optical Parameters Description
[Editor Note: This section need some update to describe all the
relevant parameters added in the model]
The link between the external transponders through a WDM network
media channels are managed at the edges, i.e. at the transmitters
(Tx) and receivers (Rx) attached to the S and R reference points
respectively.
Definitions of the optical parameters are provided below to increase
the readability of the document.
Galimberti, et al. Expires 14 August 2025 [Page 5]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
3.3.1. Parameters at Ss
output-power:
The mean launched power at Ss is the average power (in dBm) of a
pseudo-random data sequence coupled into the DWDM link.
central frequency:
This parameter indicates the Central frequency value that Ss and
Rs will be set to work (in THz)
3.3.2. Interface at point Rs
input-power:
The average received power (in dBm) at point Rs.
Curr-OSNR:
Current Optical Signal to Noise Ratio (OSNR) estimated at Rx
Transceiver port.
Curr-q-factor:
"Q" factor estimated at Rx Transceiver port.
3.4. Use Cases
The use cases are described in draft-ietf-ccamp-optical-impairment-
topology-yang, draft-ietf-teas-actn-poi-applicability and draft-
poidt-ccamp-actn-poi-pluggable-usecases-gaps.
4. WDM Interface YANG Module
The ietf-wdm-interface is an augment to the ietf-interface. It
allows the user to set the operating mode of transceivers as well as
other operational parameters. The module provides also threshold
settings and notifications to supervise measured parameters and
notify the client.
ietf-wdm-interface is a top level model for the support of this
feature. It is defined as an extension to ietf interfaces.
<CODE BEGINS> file "ietf-wdm-interface.yang"
module ietf-wdm-interface {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-wdm-interface";
prefix wdm-if;
import ietf-interfaces {
prefix if;
}
Galimberti, et al. Expires 14 August 2025 [Page 6]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
import 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: Dharini Hiremagalur <mailto:dharinih@juniper.net>
Editor: Gabriele Galimberti <mailto:ggalimbe56@gmail.com>
Editor: Gert Grammel <mailto:ggrammel@juniper.net>
Editor: Roberto Manzotti <mailto:rmanzott@cisco.com>";
description
"This module contains a collection of YANG definitions for
configuring DWDM Optical interfaces.
Copyright (c) 2024 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 Revised 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 XXXX; see
the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove
// this note
// replace the revision date with the module publication date
// the format is (year-month-day)
revision "2025-02-10" {
description
"v1.0 Initial Version";
reference
"RFC XXXX: YANG model to manage the optical interface
parameters for an external transponder in a WDM network";
// RFC Ed.: replace XXXX with actual RFC number, update date
// information and remove this note
Galimberti, et al. Expires 14 August 2025 [Page 7]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
}
typedef wdm-if-tca-types {
type enumeration {
enum laser-linewdt-tca {
description "The laser linewidth TCA";
}
enum tx-power-tca {
description "The tx power TCA";
}
enum rx-power-tca {
description "The tx power TCA";
}
enum pol-power-diff-tca {
description
"The power difference between polarization TCA";
}
enum pol-skew-diff-tca {
description
"The skew between the two polarization TCA";
}
enum cd-tca {
description "The chromatic dispersion TCA";
}
enum frequency-offset-tca {
description "Frequency offset TCA";
}
enum osnr-tca {
description "OSNR TCA";
}
enum laser-temperature-tca {
description "Laser temperature TCA";
}
enum pre-fec-ber-tca {
description "Pre Fec BER TCA";
}
enum uncorrected-words-tca {
description "Uncorrected words TCA";
}
enum q-factor-tca{
description "Q Factor TCA";
}
}
description
"The different types of TCA's for DWDM Interfaces";
}
Galimberti, et al. Expires 14 August 2025 [Page 8]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
grouping wdm-if-tca-thresholds {
description "Thresholds for TCA's";
leaf tca-type {
type wdm-if-tca-types;
description "type of the TCA eg TX Power";
}
leaf min-threshold {
type int32;
description
"A TCA is generated if the variable is less than
this value";
}
leaf max-threshold {
type int32;
description
"A TCA is generated if the variable is more than
this value";
}
leaf threshold-hysteresis {
type int32;
description
"The TCA raise/clear hysteresisis around the
threshold value to avoi alert flikering";
}
}
grouping wdm-if-tca-list {
description "List of TCA's";
leaf number-of-tcas-supported {
type uint32;
config false;
description "Number of TCAs supported by this interface";
}
list tca-list {
key "tca-type";
description "List of the TCAs";
uses wdm-if-tca-thresholds;
}
}
grouping wdm-if-mode-params {
description "OCh mode parameters";
leaf min-osnr-margin {
type l0-types:snr-or-null;
units "dB";
config false;
description "OSNR margin to FEC threshold";
Galimberti, et al. Expires 14 August 2025 [Page 9]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
}
leaf q-margin {
type int32;
units "dB";
config false;
description "Q-Factor margin to FEC threshold";
}
leaf central-frequency {
type l0-types:frequency-thz;
description
"This parameter indicates the nterface Central Frequency";
}
// uses wdm-if-fec-tca-thresholds;
uses wdm-if-tca-list;
}
grouping wdm-if-statistics {
description "OCh statistics";
leaf cur-osnr {
type l0-types:snr;
units "dB";
config false;
description "OSNR margin to FEC threshold";
}
leaf cur-q-factor {
type int32;
units "dB";
config false;
description "Q-Factor of the interface";
}
leaf uncorrected-words {
type uint64;
config false;
description "Post-FEC errored words";
}
leaf pre-fec-ber {
type decimal64 {
fraction-digits 18;
}
config false;
description "Pre-FEC errored words";
}
}
notification wdm-if-min-tca {
description "A min output TCA notification";
leaf "if-name" {
Galimberti, et al. Expires 14 August 2025 [Page 10]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
type leafref { path "/if:interfaces/if:interface/if:name"; }
mandatory true;
description "Interface name";
}
leaf tca-type {
type wdm-if-tca-types;
mandatory true;
description "Type of TCA for eg min tx power TCA";
}
}
augment "/if:interfaces" {
description
"Template definition for Optical Interface explicit-modes";
container "wdm-if-templates" {
config false;
description "Optical Interface explicit-mode templates";
container explicit-transceiver-modes {
description
"The top level container for the list of the
transceivers' explicit modes.";
list explicit-transceiver-mode {
key explicit-transceiver-mode-id;
description
"The list of the transceivers' explicit modes.";
leaf explicit-transceiver-mode-id {
type string;
description
"The identifier of the transceivers' explicit mode.";
}
uses l0-types:explicit-mode;
} // list explicit-transceiver-mode
} // container explicit-transceiver-modes
} // container dwdm-if-templates
} // augment interfaces
augment "/if:interfaces/if:interface" {
description "Parameters for an optical interface";
container wdm-interface {
description
"Container for capabilities, configuration,
current operational data for a DWDM interface";
uses l0-types:transceiver-capabilities {
augment "supported-modes/supported-mode/mode/"
+ "explicit-mode/explicit-mode" {
description
Galimberti, et al. Expires 14 August 2025 [Page 11]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
"Augment the explicit-mode container with the
proper leafref.";
leaf explicit-transceiver-mode-ref {
type leafref {
path "../../../../../../wdm-if:wdm-if-templates"
+ "/wdm-if:explicit-transceiver-modes"
+ "/wdm-if:explicit-transceiver-mode"
+ "/wdm-if:explicit-transceiver-mode-id";
}
description
"The refernce to the explicit transceiver
mode template.";
}
}
}
container current-wdm-if-parameters {
leaf configured-mode {
type union {
type empty;
type leafref {
path "../../supported-modes/supported-mode/mode-id";
}
}
description
"Reference to the configured mode for transceiver
compatibility approach.
The empty value is used to report that no mode has
been configured and there is no default mode.
When not present, the configured-mode is not reported
by the server.";
}
uses l0-types:common-transceiver-param;
description "Current parameters of this interface";
uses wdm-if-mode-params;
uses wdm-if-statistics;
}
}
}
}
<CODE ENDS>
5. Security Considerations
This section is modeled after the template described in Section 3.7
of [RFC8407bis].
Galimberti, et al. Expires 14 August 2025 [Page 12]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
The "ietf-wdm-interface" YANG module defines a data model that is
designed to be accessed via YANG-based management protocols, such as
NETCONF [RFC6241] and RESTCONF [RFC8040]. These protocols have to
use a secure transport layer (e.g., SSH [RFC4252], TLS [RFC8446], and
QUIC [RFC9000]) and have to use mutual authentication.
The Network Configuration Access Control Model (NACM) [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.
There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., "config true", which is the
default). All writable data nodes are likely to be reasonably
sensitive or vulnerable in some network environments. Write
operations (e.g., edit-config) and delete operations to these data
nodes without proper protection or authentication can have a negative
effect on network operations. The following subtrees and data nodes
have particular sensitivities/vulnerabilities:
augment /if:interfaces/if:interface:
+--rw wdm-interface
.
.
.
+--rw current-wdm-if-parameters
+--rw configured-mode? union
+--rw line-coding-bitrate? identityref
+--rw tx-channel-power? power-dbm-or-null
+--rw central-frequency? l0-types:frequency-thz
There are no particularly sensitive readable data nodes.
6. IANA Considerations
// TEMPLATE TODO In order to comply with IESG policy as set forth in
// http://www.ietf.org/ID-Checklist.html, every Internet-Draft that
// is submitted to the IESG for publication MUST contain an IANA
// Considerations section. The requirements for this section vary
// depending what actions are required of the IANA. See "Guidelines
// for Writing an IANA Considerations Section in RFCs" [RFC8126]. and
// see [RFC4181] section 3.5 for more information on writing an IANA
// clause for a MIB module internet draft.
Galimberti, et al. Expires 14 August 2025 [Page 13]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
This document registers a URI in the IETF XML registry [RFC3688].
Following the format in [RFC3688], the following registration is
requested to be made:
URI: urn:ietf:params:xml:ns:yang:ietf-interfaces:ietf-wdm-interface
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
This document registers a YANG module in the YANG Module Names
registry [RFC6020].
This document registers a YANG module in the YANG Module Names
registry [RFC6020].
prefix: ietf-wdm-interface reference: RFC XXXX
7. Acknowledgements
Italo Busi
Huawei Technologies
Email: Italo.Busi@huawei.com
8. Contributors
Ruediger Kunze
Deutsche Telekom
Winterfeldtstr. 21-27
10781 Berlin
Germany
+491702275321
RKunze@telekom.de
Dean Bogdanovic
Westford
U.S.A.
email ivandean@gmail.com
Bernd Zeuner
Deutsche Telekom
Darmstadt
Germany
email B.Zeuner@telekom.de
Massimiliano Salsi
Juniper Networks
1133 Innovation Way
Galimberti, et al. Expires 14 August 2025 [Page 14]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
Sunnyvale, CA, 94089
U.S.A.
+1 408936847
email msalsi@google.com
Arnold Mattheus
Deutsche Telekom
Darmstadt
Germany
email a.mattheus@telekom.de
Manuel Paul
Deutsche Telekom
Berlin
Germany
email Manuel.Paul@telekom.de
Walid Wakim
Infinera
ILLINOIS
UNITED STATES
email wakims@mac.com
Hing-Kam Lam
Fhusa
USA
kam.lam@fhusainc.com
Sergio Belotti
Nokia
Via Energy Park
20871 Vimercate (MB)
Italy
Sergio.belotti@nokia.com
Andreas Burk
Architekt Network Automation CTO Board
1und1
Versatel Deutschland GmbH Solmsstr. 73
D-60486 Frankfurt am Main
+49 69 21789246
Andreas.Burk@1und1.net
9. References
9.1. Normative References
Galimberti, et al. Expires 14 August 2025 [Page 15]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
<https://www.rfc-editor.org/info/rfc2863>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578,
DOI 10.17487/RFC2578, April 1999,
<https://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
<https://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Conformance Statements for SMIv2",
STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,
<https://www.rfc-editor.org/info/rfc2580>.
[RFC3591] Lam, H., Stewart, M., and A. Huynh, "Definitions of
Managed Objects for the Optical Interface Type", RFC 3591,
DOI 10.17487/RFC3591, September 2003,
<https://www.rfc-editor.org/info/rfc3591>.
[RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for
Lambda-Switch-Capable (LSC) Label Switching Routers",
RFC 6205, DOI 10.17487/RFC6205, March 2011,
<https://www.rfc-editor.org/info/rfc6205>.
[RFC8199] Bogdanovic, D., Claise, B., and C. Moberg, "YANG Module
Classification", RFC 8199, DOI 10.17487/RFC8199, July
2017, <https://www.rfc-editor.org/info/rfc8199>.
[RFC8309] Wu, Q., Liu, W., and A. Farrel, "Service Models
Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018,
<https://www.rfc-editor.org/info/rfc8309>.
Galimberti, et al. Expires 14 August 2025 [Page 16]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
[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, DOI 10.17487/RFC7698, November 2015,
<https://www.rfc-editor.org/info/rfc7698>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC9093] Zheng, H., Lee, Y., Guo, A., Lopez, V., and D. King, "A
YANG Data Model for Layer 0 Types", RFC 9093,
DOI 10.17487/RFC9093, August 2021,
<https://www.rfc-editor.org/info/rfc9093>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
[RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
Multiplexed and Secure Transport", RFC 9000,
DOI 10.17487/RFC9000, May 2021,
<https://www.rfc-editor.org/info/rfc9000>.
[RFC4252] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH)
Authentication Protocol", RFC 4252, DOI 10.17487/RFC4252,
January 2006, <https://www.rfc-editor.org/info/rfc4252>.
Galimberti, et al. Expires 14 August 2025 [Page 17]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
[ITU-T_G.698.2]
International Telecommunications Union, "Amplified
multichannel dense wavelength division multiplexing
applications with single channel optical interfaces",
ITU-T Recommendation G.698.2, November 2009.
[ITU-T_G.709]
International Telecommunications Union, "Interface for the
Optical Transport Network (OTN)", ITU-T Recommendation
G.709, June 2016.
[ITU-T_G.872]
International Telecommunications Union, "Architecture of
optical transport networks", ITU-T Recommendation G.872,
January 2017.
[ITU-T_G.798]
International Telecommunications Union, "Characteristics
of optical transport network hierarchy equipment
functional blocks", ITU-T Recommendation G.798, December
2017.
[ITU-T_G.874]
International Telecommunications Union, "Management
aspects of optical transport network elements",
ITU-T Recommendation G.874, October 2020.
[ITU-T_G.874.1]
International Telecommunications Union, "Optical transport
network (OTN): Protocol-neutral management information
model for the network element view", ITU-T Recommendation
G.874.1, November 2016.
[ITU-T_G.959.1]
International Telecommunications Union, "Optical transport
network physical layer interfaces", ITU-T Recommendation
G.959.1, November 2009.
[ITU-T_G.826]
International Telecommunications Union, "End-to-end error
performance parameters and objectives for international,
constant bit-rate digital paths and connections",
ITU-T Recommendation G.826, December 2002.
Galimberti, et al. Expires 14 August 2025 [Page 18]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
[ITU-T_G.8201]
International Telecommunications Union, "Error performance
parameters and objectives for multi-operator international
paths within the Optical Transport Network (OTN)",
ITU-T Recommendation G.8201, April 2011.
[ITU-T_G.694.1]
International Telecommunications Union, "Spectral grids
for WDM applications: DWDM frequency grid",
ITU-T Recommendation G.694.1, February 2012.
[ITU-T_G.7710]
International Telecommunications Union, "Common equipment
management function requirements", ITU-T Recommendation
G.7710, August 2017.
9.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410,
DOI 10.17487/RFC3410, December 2002,
<https://www.rfc-editor.org/info/rfc3410>.
[RFC7991] Hoffman, P., "The "xml2rfc" Version 3 Vocabulary",
RFC 7991, DOI 10.17487/RFC7991, December 2016,
<https://www.rfc-editor.org/info/rfc7991>.
[RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of
MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181,
September 2005, <https://www.rfc-editor.org/info/rfc4181>.
[RFC4054] Strand, J., Ed. and A. Chiu, Ed., "Impairments and Other
Constraints on Optical Layer Routing", RFC 4054,
DOI 10.17487/RFC4054, May 2005,
<https://www.rfc-editor.org/info/rfc4054>.
Appendix A. Change Log
This optional section should be removed before the internet draft is
submitted to the IESG for publication as an RFC.
Note to RFC Editor: please remove this appendix before publication as
an RFC.
Galimberti, et al. Expires 14 August 2025 [Page 19]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
Appendix B. Open Issues
// TEMPLATE TODO This list of issues listed in this optional section
// should be cleared and removed, and this optional section should be
// removed before the internet draft is submitted to the IESG for
// publication as an RFC.
Note to RFC Editor: please remove this appendix before publication as
an RFC.
Appendix C. YANG Tree
module: ietf-wdm-interface
augment /if:interfaces:
+--ro wdm-if-templates
+--ro explicit-transceiver-modes
+--ro explicit-transceiver-mode*
[explicit-transceiver-mode-id]
+--ro explicit-transceiver-mode-id string
+--ro line-coding-bitrate? identityref
+--ro bitrate? uint16
+--ro max-diff-group-delay? decimal-2
+--ro max-chromatic-dispersion? decimal-2
+--ro cd-penalty* [cd-value]
| +--ro cd-value decimal-2
| +--ro penalty-value union
+--ro max-polarization-mode-dispersion? decimal-2
+--ro pmd-penalty* [pmd-value]
| +--ro pmd-value decimal-2
| +--ro penalty-value union
+--ro max-polarization-dependent-loss
| power-loss-or-null
+--ro pdl-penalty* [pdl-value]
| +--ro pdl-value power-loss
| +--ro penalty-value union
+--ro available-modulation-type? identityref
+--ro min-OSNR? snr
+--ro rx-ref-channel-power? power-dbm
+--ro rx-channel-power-penalty* [rx-channel-power-value]
| +--ro rx-channel-power-value power-dbm
| +--ro penalty-value union
+--ro min-Q-factor? decimal-2
+--ro available-baud-rate? decimal64
+--ro roll-off? decimal64
+--ro min-carrier-spacing? frequency-ghz
+--ro available-fec-type? identityref
Galimberti, et al. Expires 14 August 2025 [Page 20]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
+--ro fec-code-rate? decimal64
+--ro fec-threshold? decimal64
+--ro in-band-osnr? snr
+--ro out-of-band-osnr? snr
+--ro tx-polarization-power-difference? power-ratio
+--ro polarization-skew? decimal-2
augment /if:interfaces/if:interface:
+--rw wdm-interface
+--ro supported-modes!
| +--ro supported-mode* [mode-id]
| +--ro mode-id string
| +--ro (mode)
| +--:(G.698.2)
| | +--ro standard-mode? standard-mode
| | +--ro line-coding-bitrate* identityref
| | +--ro transmitter-tuning-range
| | | +--ro min-central-frequency? frequency-thz
| | | +--ro max-central-frequency? frequency-thz
| | | +--ro transceiver-tunability? frequency-ghz
| | +--ro tx-channel-power-min? power-dbm
| | +--ro tx-channel-power-max? power-dbm
| | +--ro rx-channel-power-min? power-dbm
| | +--ro rx-channel-power-max? power-dbm
| | +--ro rx-total-power-max? power-dbm
| +--:(organizational-mode)
| | +--ro organizational-mode
| | +--ro operational-mode?
| | | operational-mode
| | +--ro organization-identifier?
| | | organization-identifier
| | +--ro line-coding-bitrate* identityref
| | +--ro transmitter-tuning-range
| | | +--ro min-central-frequency?
| | | | frequency-thz
| | | +--ro max-central-frequency?
| | | | frequency-thz
| | | +--ro transceiver-tunability?
| | | frequency-ghz
| | +--ro tx-channel-power-min? power-dbm
| | +--ro tx-channel-power-max? power-dbm
| | +--ro rx-channel-power-min? power-dbm
| | +--ro rx-channel-power-max? power-dbm
| | +--ro rx-total-power-max? power-dbm
| +--:(explicit-mode)
| +--ro explicit-mode
| +--ro transmitter-tuning-range
| | +--ro min-central-frequency?
| | | frequency-thz
Galimberti, et al. Expires 14 August 2025 [Page 21]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
| | +--ro max-central-frequency?
| | | frequency-thz
| | +--ro transceiver-tunability?
| | frequency-ghz
| +--ro tx-channel-power-min?
| | power-dbm
| +--ro tx-channel-power-max?
| | power-dbm
| +--ro rx-channel-power-min?
| | power-dbm
| +--ro rx-channel-power-max?
| | power-dbm
| +--ro rx-total-power-max?
| | power-dbm
| +--ro compatible-modes
| | +--ro supported-application-codes*
| | | -> ../../../../supported-mode/mode-id
| | +--ro supported-organizational-modes*
| | -> ../../../../supported-mode/mode-id
| +--ro explicit-transceiver-mode-ref? leafref
+--rw current-wdm-if-parameters
+--rw configured-mode? union
+--rw line-coding-bitrate? identityref
+--rw tx-channel-power? power-dbm-or-null
+--ro rx-channel-power? power-dbm-or-null
+--ro rx-total-power? power-dbm-or-null
+--ro min-osnr-margin? l0-types:snr-or-null
+--ro q-margin? int32
+--rw central-frequency? l0-types:frequency-thz
+--ro number-of-tcas-supported? uint32
+--rw tca-list* [tca-type]
| +--rw tca-type wdm-if-tca-types
| +--rw min-threshold? int32
| +--rw max-threshold? int32
| +--rw threshold-hysteresis? int32
+--ro cur-osnr? l0-types:snr
+--ro cur-q-factor? int32
+--ro uncorrected-words? uint64
+--ro pre-fec-ber? decimal64
notifications:
+---n wdm-if-min-tca
+--ro if-name -> /if:interfaces/interface/name
+--ro tca-type wdm-if-tca-types
Galimberti, et al. Expires 14 August 2025 [Page 22]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
Appendix D. Applicability examples
As an examample here below is the way and OpenROADM compliant
equipment could be managed using the Yang models described in thei
draft.
[Editor Note: We may need to refrase the following sentece, OpenROADM
has now many DWDM interface mode supported]
In OpenROADM MSA there is a limited number of DWDM interfaces
supported. Basically only the 100G Staircase FEC and 400G oFEC are
supported and these two kind of interfaces can be easily summarized
with the "mode-id" and the "application-identifier" strings.
the models below are enough to identify the interface and few working
parameters:
module: ietf-wdm-interface
augment /if:interfaces/if:interface:
+--rw wdm-interface
+--rw current-wdm-if-parameters
+--rw configured-mode? union
+--rw central-frequency? l0-types:frequency-thz
+--rw tx-channel-power? power-dbm-or-null
+--ro rx-channel-power? power-dbm-or-null
.
.
.
+--ro cur-osnr? layer0-types:snr
+--ro cur-q-factor? int32
+--ro uncorrected-words? uint64
+--ro pre-fec-ber? decimal64
Authors' Addresses
Gabriele Galimberti (editor)
C
Via Melgacciata 13 c
20813 - Bovisio Masciago
Italy
Phone: +393357481947
Email: ggalimbe56@gmail.com
Galimberti, et al. Expires 14 August 2025 [Page 23]
Internet-Draft draft-ietf-ccamp-dwdm-if-param-yang-12 February 2025
Dharini Hiremagalur (editor)
Juniper
1133 Innovation Way
Sunnyvale - 94089 California,
United States of America
Email: dharinih@juniper.net
Gert Grammel (editor)
Juniper
Oskar-Schlemmer Str. 15
80807 Muenchen
Germany
Phone: +49 1725186386
Email: ggrammel@juniper.net
Roberto Manzotti (editor)
Cisco
Santa Maria Molgora 48 C
20871 Vimercate
Italy
Phone: +390392091280
Email: rmanzott@cisco.com
Dirk Breuer (editor)
DEUTSCHE TELEKOM AG
Winterfeldtstr 21
10781 Berlin
Germany
Phone: +4930835358828
Email: d.breuer@telekom.de
Galimberti, et al. Expires 14 August 2025 [Page 24]