rfc9656.original.xml   rfc9656.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE rfc [ <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;"> <!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;"> <!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;"> <!ENTITY wj "&#8288;">
]> ]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.18 (Ruby 2.7. <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft
6) --> -ietf-ccamp-mw-topo-yang-9656" number="9656" category="std" consensus="true" sub
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft missionType="IETF" updates="" obsoletes="" tocInclude="true" sortRefs="true" sym
-ietf-ccamp-mw-topo-yang-12" category="std" consensus="true" submissionType="IET Refs="true" version="3" xml:lang="en">
F" tocInclude="true" sortRefs="true" symRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 3.18.2 -->
<front> <front>
<title abbrev="Microwave Topology YANG Model">A YANG Data Model for Microwav e Topology</title> <title abbrev="Microwave Topology YANG Model">A YANG Data Model for Microwav e Topology</title>
<seriesInfo name="Internet-Draft" value="draft-ietf-ccamp-mw-topo-yang-12"/> <seriesInfo name="RFC" value="9656"/>
<author fullname="Scott Mansfield" role="editor"> <author fullname="Scott Mansfield" initials="S." surname="Mansfield" role="e
ditor">
<organization>Ericsson Inc</organization> <organization>Ericsson Inc</organization>
<address> <address>
<email>scott.mansfield@ericsson.com</email> <email>scott.mansfield@ericsson.com</email>
</address> </address>
</author> </author>
<author fullname="Jonas Ahlberg"> <author fullname="Jonas Ahlberg" initials="J." surname="Ahlberg">
<organization>Ericsson AB</organization> <organization>Ericsson AB</organization>
<address> <address>
<postal> <postal>
<street>Lindholmspiren 11</street> <street>Lindholmspiren 11</street>
<city>Goteborg</city> <city>Goteborg</city>
<code>417 56</code> <code>417 56</code>
<country>Sweden</country> <country>Sweden</country>
</postal> </postal>
<email>jonas.ahlberg@ericsson.com</email> <email>jonas.ahlberg@ericsson.com</email>
</address> </address>
</author> </author>
<author fullname="Min Ye"> <author fullname="Min Ye" initials="M." surname="Ye">
<organization>Huawei Technologies</organization> <organization>Huawei Technologies</organization>
<address> <address>
<postal> <postal>
<street>No.1899, Xiyuan Avenue</street> <street>No.1899, Xiyuan Avenue</street>
<city>Chengdu</city> <city>Chengdu</city>
<code>611731</code> <code>611731</code>
<country>China</country> <country>China</country>
</postal> </postal>
<email>amy.yemin@huawei.com</email> <email>amy.yemin@huawei.com</email>
</address> </address>
</author> </author>
<author fullname="Xi Li"> <author fullname="Xi Li" initials="X." surname="Li">
<organization>NEC Laboratories Europe</organization> <organization>NEC Laboratories Europe</organization>
<address> <address>
<postal> <postal>
<street>Kurfursten-Anlage 36</street> <street>Kurfursten-Anlage 36</street>
<city>Heidelberg</city> <city>Heidelberg</city>
<code>69115</code> <code>69115</code>
<country>Germany</country> <country>Germany</country>
</postal> </postal>
<email>Xi.Li@neclab.eu</email> <email>Xi.Li@neclab.eu</email>
</address> </address>
</author> </author>
<author fullname="Daniela Spreafico"> <author fullname="Daniela Spreafico" initials="D." surname="Spreafico">
<organization>Nokia - IT</organization> <organization>Nokia - IT</organization>
<address> <address>
<postal> <postal>
<street>Via Energy Park, 14</street> <street>Via Energy Park, 14</street>
<city>Vimercate (MI)</city> <city>Vimercate (MI)</city>
<code>20871</code> <code>20871</code>
<country>Italy</country> <country>Italy</country>
</postal> </postal>
<email>daniela.spreafico@nokia.com</email> <email>daniela.spreafico@nokia.com</email>
</address> </address>
</author> </author>
<date year="2024" month="February" day="28"/> <date year="2024" month="September"/>
<area>Routing</area> <area>RTG</area>
<workgroup>CCAMP Working Group</workgroup> <workgroup>ccamp</workgroup>
<keyword>Internet-Draft</keyword>
<!-- [rfced] Please insert any keywords (beyond those that appear in
the title) for use on https://www.rfc-editor.org/search.
-->
<keyword>microwave</keyword>
<keyword>topology</keyword>
<!--[rfced] Please review these two similar sentences from the Abstract and Intr
oduction. Can these sentences be made uniform?
Abstract:
This document defines a YANG data model to describe microwave/
millimeter radio links in a network topology.
Introduction:
This document defines a YANG data model to describe topologies of
microwave/millimeter wave (hereafter microwave is used to simplify the
text).
-->
<abstract> <abstract>
<t>This document defines a YANG data model to describe microwave/millimete r radio links in a network topology.</t> <t>This document defines a YANG data model to describe microwave and milli meter-wave radio links in a network topology.</t>
</abstract> </abstract>
<note removeInRFC="true">
<name>About This Document</name>
<t>
The latest revision of this draft can be found at <eref target="https://
github.com/ietf-ccamp-wg/draft-ietf-ccamp-mw-topo-yang"/>.
Status information for this document may be found at <eref target="https
://datatracker.ietf.org/doc/draft-ietf-ccamp-mw-topo-yang/"/>.
</t>
<t>
Discussion of this document takes place on the
CCAMP Working Group mailing list (<eref target="mailto:ccamp@ietf.org"/>
),
which is archived at <eref target="https://datatracker.ietf.org/wg/ccamp
/about/"/>.
Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/ccamp/"
/>.
</t>
<t>Source for this draft and an issue tracker can be found at
<eref target="https://github.com/https://github.com/ietf-ccamp-wg/draft-
ietf-ccamp-mw-topo-yang"/>.</t>
</note>
</front> </front>
<middle> <middle>
<section anchor="introduction"> <section anchor="introduction">
<name>Introduction</name> <name>Introduction</name>
<t>This document defines a YANG data model to describe topologies of micro
wave/millimeter wave (hereafter microwave is used to simplify the text). The YA <!--[rfced] Seeing the discussion of Carrier Termination (CT) in RFC
NG data model describes radio links, supporting carrier(s) and the associated te 8561, may we update this text as follows?
rmination points <xref target="RFC8561"/>. A carrier is a description of a link
providing transport capacity over the air by a single carrier. It is typically Original:
defined by its transmitting and receiving frequencies. A radio link is a link p The YANG data model describes radio links, supporting carrier(s) and the associa
roviding the aggregated transport capacity of the supporting carriers in aggrega ted termination points [RFC8561].
ted and/or protected configurations, which can be used to carry traffic on highe
r topology layers such as Ethernet and TDM. The model augments "YANG Data Model Perhaps:
for Traffic Engineering (TE) Topologies" defined in <xref target="RFC8795"/>, w The YANG data model describes radio links, supporting carrier(s), and the associ
hich is based on "A YANG Data Model for Network Topologies" defined in <xref tar ated carrier termination points [RFC8561].
get="RFC8345"/>.</t> -->
<t>The microwave point-to-point radio technology provides connectivity on
Layer 0 / Layer 1 (L0/L1) over a radio link between two termination points, usin <!--[rfced] We had a few questions/comments about this definition of
g one or several supporting carriers in aggregated or protected configurations. "carrier".
That application of microwave technology cannot be used to perform cross-connec
tion or switching of the traffic to create network connectivity across multiple Original:
microwave radio links. Instead, a payload of traffic on higher topology layers, A carrier is a description of a link providing transport capacity over
normally Layer 2 (L2) Ethernet, is carried over the microwave radio link and whe the air by a single carrier.
n the microwave radio link is terminated at the endpoints, cross-connection and
switching can be performed on that higher layer creating connectivity across mul a) Does a carrier = a description?
tiple supporting microwave radio links.</t>
<t>The microwave topology model is expected to be used between a Provision b) Can this definition of "carrier" be updated to not use carrier in
ing Network Controller (PNC) and a Multi Domain Service Coordinator (MDSC) <xref its description?
target="RFC8453"/>. Examples of use cases that can be supported are:</t>
c) Note that we see this somewhat similar text in RFC 8561, where they
are defining a Carrier Termination:
Carrier Termination (CT) is an interface for the capacity provided
over the air by a single carrier.
Perhaps:
A carrier is a single link providing transport capacity over the air.
-->
<!--[rfced] Similar questions about the definition of "radio link":
Original:
A radio link is a link providing the aggregated transport capacity of
the supporting carriers in aggregated and/or protected configurations,
which can be used to carry traffic on higher topology layers such as
Ethernet and TDM.
a) Can we update to remove the use of "link" in the definition of
"radio link" (see below)?
b) We see that "aggregated" is used twice: may this text be updated to
reduce redundancy (see below)?
Perhaps:
A radio link provides the transport capacity of the supporting
carriers in aggregated and/or protected configurations, which can be
used to carry traffic on higher topology layers, such as Ethernet and
Time-Division-Multiplexing (TDM).
If the above does not capture your intent, please let us know if/how
we may rephrase differently.
-->
<t>This document defines a YANG data model to describe microwave and milli
meter-wave radio links in a network topology (hereafter, "microwave" is used to
simplify the text). The YANG data model describes radio links, supporting carri
er(s), and the associated carrier termination points <xref target="RFC8561"/>. A
carrier is a single link providing transport capacity over the air. It is typi
cally defined by its transmitting and receiving frequencies. A radio link provi
des the transport capacity of the supporting carriers in aggregated and/or prote
cted configurations, which can be used to carry traffic on higher topology layer
s such as Ethernet and Time-Division Multiplexing (TDM). The model augments th
e <xref target="RFC8795" format="title"/> defined in <xref target="RFC8795"/>, w
hich is based on <xref target="RFC8345" format="title"/> defined in <xref target
="RFC8345"/>.</t>
<t>The microwave point-to-point radio technology provides connectivity on
Layer 0 or Layer 1 (L0/L1) over a radio link between two termination points usin
g one or several supporting carriers in aggregated or protected configurations.
That application of microwave technology cannot be used to perform cross-connec
tion or switching of the traffic to create network connectivity across multiple
microwave radio links. Instead, a payload of traffic on higher topology layers,
normally Layer 2 (L2) Ethernet, is carried over the microwave radio link. When t
he microwave radio link is terminated at the endpoints, cross-connection and swi
tching can be performed on that higher layer creating connectivity across multip
le supporting microwave radio links.</t>
<t>The microwave topology model is expected to be used between a Provision
ing Network Controller (PNC) and a Multi-Domain Service Coordinator (MDSC) <xref
target="RFC8453"/>. Examples of use cases that can be supported are:</t>
<ol spacing="normal" type="1"><li> <ol spacing="normal" type="1"><li>
<t>Correlation between microwave radio links and the supported links o n higher topology layers (e.g., an L2 Ethernet topology). This information can be used to understand how changes in the performance/status of a microwave radio link affect traffic on higher layers.</t> <t>Correlation between microwave radio links and the supported links o n higher topology layers (e.g., an L2 Ethernet topology). This information can be used to understand how changes in the performance/status of a microwave radio link affect traffic on higher layers.</t>
</li> </li>
<li> <li>
<t>Propagation of relevant characteristics of a microwave radio link, such as bandwidth, to higher topology layers, where it could be used as a criter ion when configuring and optimizing a path for a connection/service through the network end to end.</t> <t>Propagation of relevant characteristics of a microwave radio link, such as bandwidth, to higher topology layers, where it could be used as a criter ion when configuring and optimizing a path for a connection or service through t he network end to end.</t>
</li> </li>
<li> <li>
<t>Optimization of the microwave radio link configurations on a networ k level, with the purpose to minimize overall interference and/or maximize the o verall capacity provided by the links.</t> <t>Optimization of the microwave radio link configurations on a networ k level, with the purpose to minimize overall interference and/or maximize the o verall capacity provided by the links.</t>
</li> </li>
</ol> </ol>
<section anchor="abbreviations"> <section anchor="abbreviations">
<name>Abbreviations</name> <name>Abbreviations</name>
<t>The following abbreviations are used in this document:</t> <t>The following abbreviations are used in this document:</t>
<t>CTP Carrier Termination Point</t> <dl newline="false" spacing="normal">
<t>RLT Radio Link Terminal</t> <dt>CTP:</dt> <dd>Carrier Termination Point</dd>
<t>RLTP Radio Link Termination Point</t> <dt>RLT:</dt> <dd>Radio Link Terminal</dd>
<dt>RLTP:</dt> <dd>Radio Link Termination Point</dd>
</dl>
</section> </section>
<section anchor="tree-structure"> <section anchor="tree-structure">
<name>Tree Structure</name> <name>Tree Structure</name>
<t>A simplified graphical representation of the data model is used in ch
apter 3.1 of this document. The meaning of the symbols in these diagrams is def <t>A simplified graphical representation of the data model is used in <x
ined in <xref target="RFC8340"/>.</t> ref target="microwave-topology-yang-data-model"/> of this document. The meanin
g of the symbols in these diagrams is defined in <xref target="RFC8340"/>.</t>
</section> </section>
<section anchor="prefixes-in-data-node-names"> <section anchor="prefixes-in-data-node-names">
<name>Prefixes in Data Node Names</name> <name>Prefixes in Data Node Names</name>
<!--[rfced] Please review the inclusion of the mwt prefix in Table 1.
As this document defines that prefix, is it "imported"?-->
<t>In this document, names of data nodes and other data model objects ar e prefixed using the standard prefix associated with the corresponding YANG impo rted modules, as shown in <xref target="tab-prefix"/>.</t> <t>In this document, names of data nodes and other data model objects ar e prefixed using the standard prefix associated with the corresponding YANG impo rted modules, as shown in <xref target="tab-prefix"/>.</t>
<table anchor="tab-prefix"> <table anchor="tab-prefix">
<name>Prefixes for imported YANG modules</name> <name>Prefixes for Imported YANG Modules</name>
<thead> <thead>
<tr> <tr>
<th align="left">Prefix</th> <th align="left">Prefix</th>
<th align="left">YANG Module</th> <th align="left">YANG Module</th>
<th align="left">Reference</th> <th align="left">Reference</th>
</tr> </tr>
</thead> </thead>
<tbody> <tbody>
<tr> <tr>
<td align="left">mwt</td>
<td align="left">ietf-microwave-topology</td>
<td align="left">This document</td>
</tr>
<tr>
<td align="left">nw</td> <td align="left">nw</td>
<td align="left">ietf-network</td> <td align="left">ietf-network</td>
<td align="left"> <td align="left">
<xref target="RFC8345"/></td> <xref target="RFC8345"/></td>
</tr> </tr>
<tr> <tr>
<td align="left">nt</td> <td align="left">nt</td>
<td align="left">ietf-network-topology</td> <td align="left">ietf-network-topology</td>
<td align="left"> <td align="left">
<xref target="RFC8345"/></td> <xref target="RFC8345"/></td>
skipping to change at line 171 skipping to change at line 236
</tbody> </tbody>
</table> </table>
</section> </section>
</section> </section>
<section anchor="microwave-topology-yang-data-model"> <section anchor="microwave-topology-yang-data-model">
<name>Microwave Topology YANG Data Model</name> <name>Microwave Topology YANG Data Model</name>
<section anchor="yang-tree"> <section anchor="yang-tree">
<name>YANG Tree</name> <name>YANG Tree</name>
<figure anchor="fig-mw-tree"> <figure anchor="fig-mw-tree">
<name>Microwave Topology Tree</name> <name>Microwave Topology Tree</name>
<artwork><![CDATA[ <sourcecode type="yangtree"><![CDATA[
module: ietf-microwave-topology module: ietf-microwave-topology
augment /nw:networks/nw:network/nw:network-types/tet:te-topology: augment /nw:networks/nw:network/nw:network-types/tet:te-topology:
+--rw mw-topology! +--rw mw-topology!
augment /nw:networks/nw:network/nw:node/tet:te augment /nw:networks/nw:network/nw:node/tet:te
/tet:te-node-attributes: /tet:te-node-attributes:
+--rw mw-node! +--rw mw-node!
augment /nw:networks/nw:network/nw:node/nt:termination-point augment /nw:networks/nw:network/nw:node/nt:termination-point
/tet:te: /tet:te:
+--rw mw-tp! +--rw mw-tp!
+--rw (mw-tp-option)? +--rw (mw-tp-option)?
+--:(microwave-rltp) +--:(microwave-rltp)
| +--rw microwave-rltp! | +--rw microwave-rltp!
+--:(microwave-ctp) +--:(microwave-ctp)
+--rw microwave-ctp! +--rw microwave-ctp!
augment /nw:networks/nw:network/nt:link/tet:te augment /nw:networks/nw:network/nt:link/tet:te
/tet:te-link-attributes: /tet:te-link-attributes:
+--rw mw-link! +--rw mw-link!
+--rw (mw-link-option) +--rw (mw-link-option)
+--:(microwave-radio-link) +--:(microwave-radio-link)
| +--rw microwave-radio-link! | +--rw microwave-radio-link!
| +--rw rlt-mode | +--rw rlt-mode
| +--rw num-bonded-carriers uint32 | +--rw num-bonded-carriers uint32
| +--rw num-protecting-carriers uint32 | +--rw num-protecting-carriers uint32
+--:(microwave-carrier) +--:(microwave-carrier)
+--rw microwave-carrier! +--rw microwave-carrier!
+--rw tx-frequency? uint32 +--rw tx-frequency? uint32
+--rw rx-frequency? uint32 +--ro actual-rx-frequency? uint32
+--rw channel-separation? uint32 +--rw channel-separation? uint32
+--ro actual-tx-cm? identityref +--ro actual-tx-cm? identityref
+--ro actual-snir? decimal64 +--ro actual-snir? decimal64
+--ro actual-transmitted-level? decimal64 +--ro actual-transmitted-level? decimal64
augment /nw:networks/nw:network/nt:link/tet:te augment /nw:networks/nw:network/nt:link/tet:te
/tet:te-link-attributes/tet:max-link-bandwidth /tet:te-link-attributes/tet:max-link-bandwidth
/tet:te-bandwidth: /tet:te-bandwidth:
+--ro mw-bandwidth? uint64 +--ro mw-bandwidth? uint64
]]></artwork> ]]></sourcecode>
</figure> </figure>
</section> </section>
<section anchor="relationship-between-radio-links-and-carriers"> <section anchor="relationship-between-radio-links-and-carriers">
<name>Relationship between radio links and carriers</name> <name>Relationship between Radio Links and Carriers</name>
<t>A microwave radio link is always an aggregate of one or multiple carr <t>A microwave radio link is always an aggregate of one or multiple carr
iers, in various configurations/modes. The supporting carriers are identified b iers in various configurations or modes. The supporting carriers are identified
y their termination points and are listed in the container bundled-links as part by their termination points and are listed in the container-bundled links as pa
of the te-link-config in the YANG Data Model for Traffic Engineering (TE) Topol rt of the te-link-config in the <xref target="RFC8795" format="title"/> <xref ta
ogies <xref target="RFC8795"/> for a radio-link. The exact configuration of the rget="RFC8795"/> for a radio-link. The exact configuration of the included carr
included carriers is further specified in the rlt-mode container (1+0, 2+0, 1+1 iers is further specified in the rlt-mode container (1+0, 2+0, 1+1, etc.) for th
, etc.) for the radio-link. Appendix A includes JSON examples of how such a rel e radio-link. <xref target="examples-mw-only" format="default"/> includes JSON
ationship can be modelled.</t> examples of how such a relationship can be modeled.</t>
</section> </section>
<section anchor="relationship-with-client-topology-model"> <section anchor="relationship-with-client-topology-model">
<name>Relationship with client topology model</name> <name>Relationship with Client Topology Model</name>
<t>A microwave radio link carries a payload of traffic on higher topolog <t>A microwave radio link carries a payload of traffic on higher topolog
y layers, normally L2 Ethernet. The leafs supporting-network, supporting-node, y layers, normally L2 Ethernet. The leafs supporting-network, supporting-node,
supporting-link, and supporting-termination-point in the generic YANG module for supporting-link, and supporting-termination-point in the generic YANG module for
Network Topologies <xref target="RFC8345"/> are expected to be used to model a Network Topologies <xref target="RFC8345"/> are expected to be used to model a
relationship/dependency from higher topology layers to a supporting microwave ra relationship or dependency from higher topology layers to a supporting microwave
dio link topology layer. Appendix A includes JSON examples of an L2 Ethernet li radio link topology layer. <xref target="examples-mw-only" format="default"/>
nk transported over one supporting microwave link.</t> includes JSON examples of an L2 Ethernet link transported over one supporting mi
crowave link.</t>
</section> </section>
<section anchor="applicability-of-the-data-model-for-traffic-engineering-t e-topologies"> <section anchor="applicability-of-the-data-model-for-traffic-engineering-t e-topologies">
<name>Applicability of the Data Model for Traffic Engineering (TE) Topol ogies</name> <name>Applicability of the Data Model for Traffic Engineering (TE) Topol ogies</name>
<t>Since microwave is a point-to-point radio technology, a majority of t
he leafs in the Data Model for Traffic Engineering (TE) Topologies augmented by <!--[rfced] Would you like to add a citation after this mention of the
the microwave topology model are not applicable. An example of which leafs are YANG module from RFC 8795 to match other mentions of YANG
considered applicable can be found in appendices <xref target="examples-mw-only" modules throughout the document?
/> and <xref target="examples-mw-imports"/> in this document.</t>
<t>More specifically in the context of the microwave-specific augmentati Original:
ons of te-topology, admin-status and oper-status leafs (from te-topology) are on Since microwave is a point-to-point radio technology, a majority of
ly applicable to microwave carriers (in the mw-link tree) and not microwave radi the leafs in the Data Model for Traffic Engineering (TE) Topologies
o links. Enable and disable of a radio link is instead done in the constituent c augmented by the microwave topology model are not applicable.
arriers. Furthermore the status leafs related to mw-tp can be used when links ar
e inter-domain and when the status of only one side of the link is known, but si Perhaps:
nce microwave is a point-to-point technology where both ends normally belong to Since microwave is a point-to-point radio technology, a majority of
the same domain it is not expected to be applicable in normal cases.</t> the leafs in the Data Model for Traffic Engineering (TE) Topologies
[RFC8795] augmented by the microwave topology model are not applicable.
-->
<t>Since microwave is a point-to-point radio technology, a majority of the leafs
in the Data Model for Traffic Engineering (TE) Topologies <xref target="RFC8795
"/> augmented by the microwave topology model are not applicable. Examples of w
hich leafs are considered applicable can be found in Appendices <xref target="ex
amples-mw-only" format="counter"/> and <xref target="examples-mw-imports" format
="counter"/> in this document.</t>
<!--[rfced] Does the following rephrasing retain your intended meaning?
Original:
More specifically in the context of the microwave-specific
augmentations of te-topology, admin-status and oper-status leafs
(from te-topology) are only applicable to microwave carriers (in the
mw-link tree) and not microwave radio links.
Perhaps:
In the more specific context of the microwave-specific
augmentations of te-topology, the admin-status and oper-status leafs
(from te-topology) are only applicable to microwave carriers (in the
mw-link tree); they are not applicable to microwave radio links.
-->
<t>In the more specific context of the microwave-specific augmentations
of te-topology, the admin-status, and oper-status leafs (from te-topology) are o
nly applicable to microwave carriers (in the mw-link tree); they are not applica
ble to microwave radio links. Radio links are instead enabled or disabled in the
constituent carriers. Furthermore, the status leafs related to mw-tp can be use
d with inter-domain links and when the status of only one side of the link is kn
own. However, since microwave is a point-to-point technology where both ends nor
mally belong to the same domain, it is not expected to be applicable in normal c
ases.</t>
</section> </section>
<section anchor="microwave-topology-yang-module"> <section anchor="microwave-topology-yang-module">
<name>Microwave Topology YANG Module</name> <name>Microwave Topology YANG Module</name>
<t>This module imports typedefs and modules from <xref target="RFC8345"/ <t>This module imports typedefs and modules from <xref target="RFC8345"/
>, <xref target="RFC8561"/>, and <xref target="RFC8795"/>, and it references <xr >, <xref target="RFC8561"/>, and <xref target="RFC8795"/>. It references <xref t
ef target="EN301129"/> and <xref target="EN302217-1"/>.</t> arget="EN301129"/> and <xref target="EN302217-1"/>.</t>
<sourcecode type="yang" markers="true" name="ietf-microwave-topology@202
4-02-27.yang"><![CDATA[ <!-- [rfced] Italo Busi is listed as a contributor to the document
(not an author) and also as an editor within the YANG module.
Please review this relationship and let us know if/how to update.
-->
<!--[rfced] Please review if a "reference" clause should be added to
the module following descriptions that contain "defined in RFC
8561". Note that more than one such instance exists.-->
<sourcecode type="yang" markers="true" name="ietf-microwave-topology@202
4-09-18.yang"><![CDATA[
module ietf-microwave-topology { module ietf-microwave-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-topology";
prefix mwt; prefix mwt;
import ietf-network { import ietf-network {
prefix nw; prefix nw;
reference reference
"RFC 8345: A YANG Data Model for Network Topologies"; "RFC 8345: A YANG Data Model for Network Topologies";
} }
skipping to change at line 252 skipping to change at line 360
} }
import ietf-te-topology { import ietf-te-topology {
prefix tet; prefix tet;
reference reference
"RFC 8795: YANG Data Model for Traffic Engineering "RFC 8795: YANG Data Model for Traffic Engineering
(TE) Topologies"; (TE) Topologies";
} }
import ietf-microwave-types { import ietf-microwave-types {
prefix mw-types; prefix mw-types;
reference reference
"RFC 8561"; "RFC 8561: A YANG Data Model for Microwave Radio Link";
} }
organization organization
"Internet Engineering Task Force (IETF) CCAMP WG"; "Internet Engineering Task Force (IETF) CCAMP WG";
contact contact
"WG Web: <https://datatracker.ietf.org/wg/ccamp/> "WG Web: <https://datatracker.ietf.org/wg/ccamp/>
WG List: <mailto:ccamp@ietf.org> WG List: <ccamp@ietf.org>
Editor: Jonas Ahlberg Editor: Jonas Ahlberg
<mailto:jonas.ahlberg@ericsson.com> <jonas.ahlberg@ericsson.com>
Editor: Scott Mansfield Editor: Scott Mansfield
<mailto:scott.mansfield@ericsson.com> <scott.mansfield@ericsson.com>
Editor: Min Ye Editor: Min Ye
<mailto:amy.yemin@huawei.com> <amy.yemin@huawei.com>
Editor: Italo Busi Editor: Italo Busi
<mailto:Italo.Busi@huawei.com> <Italo.Busi@huawei.com>
Editor: Xi Li Editor: Xi Li
<mailto:Xi.Li@neclab.eu> <Xi.Li@neclab.eu>
Editor: Daniela Spreafico Editor: Daniela Spreafico
<mailto:daniela.spreafico@nokia.com> <daniela.spreafico@nokia.com>
"; ";
description description
"This is a module for microwave topology. "This is a module for microwave topology.
Copyright (c) 2024 IETF Trust and the persons Copyright (c) 2024 IETF Trust and the persons
identified as authors of the code. All rights reserved. identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Revised BSD License to the license terms contained in, the Revised BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC 9656; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2024-02-27 { revision 2024-09-18 {
description description
"Last call comment resolutions."; "Last call comment resolutions.";
reference reference
""; "";
} }
grouping rlt-mode { grouping rlt-mode {
description description
"This grouping provides a flexible definition of number "This grouping provides a flexible definition of the number
of bonded carriers and protecting carriers of a radio of bonded carriers and protecting carriers of a radio
link."; link.";
leaf num-bonded-carriers { leaf num-bonded-carriers {
type uint32; type uint32;
mandatory true; mandatory true;
description description
"Number of bonded carriers."; "Number of bonded carriers.";
} }
leaf num-protecting-carriers { leaf num-protecting-carriers {
type uint32; type uint32;
skipping to change at line 322 skipping to change at line 430
"Number of protecting carriers."; "Number of protecting carriers.";
} }
} }
grouping microwave-radio-link-attributes { grouping microwave-radio-link-attributes {
description description
"Grouping used for attributes describing a microwave "Grouping used for attributes describing a microwave
radio link."; radio link.";
container rlt-mode { container rlt-mode {
description description
"This grouping provides a flexible definition of number "This grouping provides a flexible definition of the number
of bonded carriers and protecting carriers of a radio of bonded carriers and protecting carriers of a radio
link."; link.";
uses rlt-mode; uses rlt-mode;
} }
} }
grouping microwave-carrier-attributes { grouping microwave-carrier-attributes {
description description
"Grouping used for attributes describing a microwave "Grouping used for attributes describing a microwave
carrier."; carrier.";
leaf tx-frequency { leaf tx-frequency {
type uint32; type uint32;
units "kHz"; units "kHz";
description description
"Selected transmitter frequency. "Selected transmitter frequency.
Related to the data node tx-frequency in RFC 8561."; Related to the data node tx-frequency in RFC 8561.";
reference reference
"RFC 8561: A YANG Data Model for Microwave Radio Link"; "RFC 8561: A YANG Data Model for Microwave Radio Link";
} }
leaf rx-frequency { leaf actual-rx-frequency {
type uint32; type uint32;
units "kHz"; units "kHz";
config false;
description description
"Selected receiver frequency. "Computed receiver frequency.
Related to the data node actual-rx-frequency in RFC 8561."; Related to the data node actual-rx-frequency in RFC 8561.";
reference reference
"RFC 8561: A YANG Data Model for Microwave Radio Link"; "RFC 8561: A YANG Data Model for Microwave Radio Link";
} }
leaf channel-separation { leaf channel-separation {
type uint32; type uint32;
units "kHz"; units "kHz";
description description
"The amount of bandwidth allocated to a carrier. The "The amount of bandwidth allocated to a carrier. The
distance between adjacent channels in a radio distance between adjacent channels in a radio
frequency channels arrangement. frequency channel arrangement.
Related to the data node channel-separation in RFC 8561."; Related to the data node channel-separation in RFC 8561.";
reference reference
"ETSI EN 302 217-1 and "ETSI EN 302 217-1 and
RFC 8561: A YANG Data Model for Microwave Radio Link"; RFC 8561: A YANG Data Model for Microwave Radio Link";
} }
leaf actual-tx-cm { leaf actual-tx-cm {
type identityref { type identityref {
base mw-types:coding-modulation; base mw-types:coding-modulation;
} }
config false; config false;
skipping to change at line 381 skipping to change at line 490
reference reference
"RFC 8561: A YANG Data Model for Microwave Radio Link"; "RFC 8561: A YANG Data Model for Microwave Radio Link";
} }
leaf actual-snir { leaf actual-snir {
type decimal64 { type decimal64 {
fraction-digits 1; fraction-digits 1;
} }
units "dB"; units "dB";
config false; config false;
description description
"Actual signal to noise plus the interference ratio "Actual signal-to-noise plus the interference ratio
(0.1 dB resolution). (0.1 dB resolution).
Related to the data node actual-snir in RFC 8561."; Related to the data node actual-snir in RFC 8561.";
reference reference
"RFC 8561: A YANG Data Model for Microwave Radio Link"; "RFC 8561: A YANG Data Model for Microwave Radio Link";
} }
leaf actual-transmitted-level { leaf actual-transmitted-level {
type decimal64 { type decimal64 {
fraction-digits 1; fraction-digits 1;
} }
units "dBm"; units "dBm";
skipping to change at line 432 skipping to change at line 541
description description
"Microwave topology type"; "Microwave topology type";
} }
} }
augment "/nw:networks/nw:network/nw:node/tet:te" augment "/nw:networks/nw:network/nw:node/tet:te"
+ "/tet:te-node-attributes" { + "/tet:te-node-attributes" {
when '../../../nw:network-types' when '../../../nw:network-types'
+ '/tet:te-topology/mwt:mw-topology' { + '/tet:te-topology/mwt:mw-topology' {
description description
"Augmentation parameters apply only for networks with a "Augmentation parameters apply only to networks with a
microwave network topology type."; microwave network topology type.";
} }
description description
"Augment network node to indicate a microwave node."; "Augment network node to indicate a microwave node.";
container mw-node { container mw-node {
presence "Indicates a microwave node."; presence "Indicates a microwave node.";
description description
"Microwave node"; "Microwave node";
} }
} }
augment "/nw:networks/nw:network/nw:node/nt:termination-point/" augment "/nw:networks/nw:network/nw:node/nt:termination-point/"
+ "tet:te" { + "tet:te" {
when '../../../nw:network-types/tet:te-topology/' when '../../../nw:network-types/tet:te-topology/'
+ 'mwt:mw-topology' { + 'mwt:mw-topology' {
description description
"Augmentation parameters apply only for networks with a "Augmentation parameters apply only for networks with a
microwave network topology type."; microwave network topology type.";
} }
description description
"Augmentation to add microwave technology specific "Augmentation to add microwave-technology-specific
characteristics to a termination point."; characteristics to a termination point.";
container mw-tp { container mw-tp {
presence "Denotes a microwave termination point."; presence "Denotes a microwave termination point.";
description description
"Specification of type of termination point."; "Specification of type of termination point.";
choice mw-tp-option { choice mw-tp-option {
description description
"Selection of type of termination point."; "Selection of type of termination point.";
case microwave-rltp { case microwave-rltp {
container microwave-rltp { container microwave-rltp {
presence presence
"Denotes a microwave radio link termination point. "Denotes a microwave radio link termination point.
It corresponds to a microwave RLT interface as It corresponds to a microwave RLT interface as
defined in RFC 8561."; defined in RFC 8561.";
description description
"Denotes and describes a microwave radio link "Denotes and describes a microwave radio link
termination point."; termination point.";
reference
"RFC 8561: A YANG Data Model for Microwave Radio Link";
} }
} }
case microwave-ctp { case microwave-ctp {
container microwave-ctp { container microwave-ctp {
presence "Denotes a microwave carrier termination point. presence "Denotes a microwave carrier termination point.
It corresponds to a microwave CT interface as It corresponds to a microwave CT interface as
defined in RFC 8561."; defined in RFC 8561.";
description description
"Denotes and describes a microwave carrier "Denotes and describes a microwave carrier
termination point."; termination point.";
reference
"RFC 8561: A YANG Data Model for Microwave Radio Link";
} }
} }
} }
} }
} }
augment "/nw:networks/nw:network/nt:link/tet:te/" augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:te-link-attributes" { + "tet:te-link-attributes" {
when '../../../nw:network-types/tet:te-topology/' when '../../../nw:network-types/tet:te-topology/'
+ 'mwt:mw-topology' { + 'mwt:mw-topology' {
description description
"Augmentation parameters apply only for networks with a "Augmentation parameters apply only for networks with a
microwave network topology type."; microwave network topology type.";
} }
description description
"Augmentation to add microwave technology specific "Augmentation to add microwave-technology-specific
characteristics to a link."; characteristics to a link.";
container mw-link { container mw-link {
presence "This indicates a microwave link"; presence "This indicates a microwave link";
description description
"Specification of type of link."; "Specification of type of link.";
choice mw-link-option { choice mw-link-option {
mandatory true; mandatory true;
description description
"Selection of type of link."; "Selection of type of link.";
case microwave-radio-link { case microwave-radio-link {
container microwave-radio-link { container microwave-radio-link {
presence "Denotes a microwave radio link"; presence "Denotes a microwave radio link";
description description
"Denotes and describes a microwave radio link"; "Denotes and describes a microwave radio link.";
uses microwave-radio-link-attributes; uses microwave-radio-link-attributes;
} }
} }
case microwave-carrier { case microwave-carrier {
container microwave-carrier { container microwave-carrier {
presence "Denotes a microwave carrier"; presence "Denotes a microwave carrier";
description description
"Denotes and describes a microwave carrier"; "Denotes and describes a microwave carrier.";
uses microwave-carrier-attributes; uses microwave-carrier-attributes;
} }
} }
} }
} }
} }
augment "/nw:networks/nw:network/nt:link/tet:te/" augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:te-link-attributes/" + "tet:te-link-attributes/"
+ "tet:max-link-bandwidth/" + "tet:max-link-bandwidth/"
skipping to change at line 561 skipping to change at line 674
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
<xref target="RFC8446"/>.</t> <xref target="RFC8446"/>.</t>
<t>The NETCONF access control model <xref target="RFC8341"/> provides the means to <t>The NETCONF access control model <xref target="RFC8341"/> provides the means to
restrict access for particular NETCONF or RESTCONF users to a restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content.</t> operations and content.</t>
<t>The YANG module specified in this document imports and augments the <t>The YANG module specified in this document imports and augments the
ietf-network and ietf-network-topology models defined in <xref target="RFC834 5"/>. ietf-network and ietf-network-topology models defined in <xref target="RFC834 5"/>.
The security considerations from <xref target="RFC8345"/> are applicable to t he The security considerations from <xref target="RFC8345"/> are applicable to t he
module in this document.</t> module in this document.</t>
<t>There are a several data nodes defined in this YANG module that are <t>There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes can be considered sensitive or vulnerable default). These data nodes can be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability:</t> and their sensitivity/vulnerability:</t>
<ul spacing="normal"> <ul spacing="normal">
<li> <li>
<t>rlt-mode: A malicious client could attempt to modify the mode in <t>rlt-mode: A malicious client could attempt to modify the mode in
which the radio link is configured and thereby change the which the radio link is configured and, thereby, change the
intended behavior of the link.</t> intended behavior of the link.</t>
</li> </li>
<li> <li>
<t>tx-frequency, rx-frequency and channel-separation: A malicious <t>tx-frequency and channel-separation: A malicious
client could attempt to modify the frequency configuration of client could attempt to modify the frequency configuration of
a carrier which could modify the intended behavior or make a carrier, which could modify the intended behavior or make
the configuration invalid and thereby stop the operation of it.</t> the configuration invalid and, thereby, stop the operation of it.</t>
</li> </li>
</ul> </ul>
</section> </section>
<section anchor="iana-considerations"> <section anchor="iana-considerations">
<name>IANA Considerations</name> <name>IANA Considerations</name>
<t>IANA is asked to assign a new URI from the "IETF XML Registry" <xref ta <t>IANA has assigned a new URI from the "IETF XML Registry" <xref target="
rget="RFC3688"/> as follows:</t> RFC3688"/> as follows:</t>
<artwork><![CDATA[ <dl newline="false" spacing="compact">
URI: urn:ietf:params:xml:ns:yang:ietf-microwave-topology <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-microwave-topology</dd>
Registrant Contact: The IESG <dt>Registrant Contact:</dt> <dd>The IESG</dd>
XML: N/A; the requested URI is an XML namespace. <dt>XML:</dt> <dd>N/A; the requested URI is an XML namespace.</dd>
]]></artwork> </dl>
<t>It is proposed that IANA record the YANG module names in the "YANG
<t>IANA has recorded the YANG module names in the "YANG
Module Names" registry <xref target="RFC6020"/> as follows:</t> Module Names" registry <xref target="RFC6020"/> as follows:</t>
<artwork><![CDATA[ <dl newline="false" spacing="compact">
Name: ietf-microwave-topology <dt>Name:</dt> <dd>ietf-microwave-topology</dd>
Maintained by IANA?: N <dt>Maintained by IANA?:</dt> <dd>N</dd>
Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-topology <dt>Namespace:</dt> <dd>urn:ietf:params:xml:ns:yang:ietf-microwave-topolo
Prefix: mwt gy</dd>
Reference: RFC XXXX <dt>Prefix:</dt> <dd>mwt</dd>
]]></artwork> <dt>Reference:</dt> <dd>RFC 9656</dd>
</dl>
</section> </section>
</middle> </middle>
<back> <back>
<displayreference target="I-D.ietf-ccamp-if-ref-topo-yang" to="YANG-IF-REF-T
OPO"/>
<displayreference target="I-D.ietf-ccamp-bwa-topo-yang" to="YANG-BWA-TOPO"/>
<references> <references>
<name>References</name> <name>References</name>
<references> <references>
<name>Normative References</name> <name>Normative References</name>
<reference anchor="RFC8561">
<front> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.85
<title>A YANG Data Model for Microwave Radio Link</title> 61.xml"/>
<author fullname="J. Ahlberg" initials="J." surname="Ahlberg"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.87
<author fullname="M. Ye" initials="M." surname="Ye"/> 95.xml"/>
<author fullname="X. Li" initials="X." surname="Li"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.83
<author fullname="D. Spreafico" initials="D." surname="Spreafico"/> 45.xml"/>
<author fullname="M. Vaupotic" initials="M." surname="Vaupotic"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.62
<date month="June" year="2019"/> 41.xml"/>
<abstract> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.80
<t>This document defines a YANG data model for control and managem 40.xml"/>
ent of radio link interfaces and their connectivity to packet (typically Etherne <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.62
t) interfaces in a microwave/millimeter wave node. The data nodes for management 42.xml"/>
of the interface protection functionality is broken out into a separate and gen <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.84
eric YANG data model in order to make it available for other interface types as 46.xml"/>
well.</t> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.83
</abstract> 41.xml"/>
</front> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.36
<seriesInfo name="RFC" value="8561"/> 88.xml"/>
<seriesInfo name="DOI" value="10.17487/RFC8561"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.60
</reference> 20.xml"/>
<reference anchor="RFC8795">
<front>
<title>YANG Data Model for Traffic Engineering (TE) Topologies</titl
e>
<author fullname="X. Liu" initials="X." surname="Liu"/>
<author fullname="I. Bryskin" initials="I." surname="Bryskin"/>
<author fullname="V. Beeram" initials="V." surname="Beeram"/>
<author fullname="T. Saad" initials="T." surname="Saad"/>
<author fullname="H. Shah" initials="H." surname="Shah"/>
<author fullname="O. Gonzalez de Dios" initials="O." surname="Gonzal
ez de Dios"/>
<date month="August" year="2020"/>
<abstract>
<t>This document defines a YANG data model for representing, retri
eving, 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>
<reference anchor="RFC8345">
<front>
<title>A YANG Data Model for Network Topologies</title>
<author fullname="A. Clemm" initials="A." surname="Clemm"/>
<author fullname="J. Medved" initials="J." surname="Medved"/>
<author fullname="R. Varga" initials="R." surname="Varga"/>
<author fullname="N. Bahadur" initials="N." surname="Bahadur"/>
<author fullname="H. Ananthakrishnan" initials="H." surname="Anantha
krishnan"/>
<author fullname="X. Liu" initials="X." surname="Liu"/>
<date month="March" year="2018"/>
<abstract>
<t>This document defines an abstract (generic, or base) YANG data
model for network/service topologies and inventories. The data model serves as a
base model that is augmented with technology-specific details in other, more sp
ecific topology and inventory data models.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8345"/>
<seriesInfo name="DOI" value="10.17487/RFC8345"/>
</reference>
<reference anchor="RFC6241">
<front>
<title>Network Configuration Protocol (NETCONF)</title>
<author fullname="R. Enns" initials="R." role="editor" surname="Enns
"/>
<author fullname="M. Bjorklund" initials="M." role="editor" surname=
"Bjorklund"/>
<author fullname="J. Schoenwaelder" initials="J." role="editor" surn
ame="Schoenwaelder"/>
<author fullname="A. Bierman" initials="A." role="editor" surname="B
ierman"/>
<date month="June" year="2011"/>
<abstract>
<t>The Network Configuration Protocol (NETCONF) defined in this do
cument provides mechanisms to install, manipulate, and delete the configuration
of network devices. It uses an Extensible Markup Language (XML)-based data encod
ing for the configuration data as well as the protocol messages. The NETCONF pro
tocol operations are realized as remote procedure calls (RPCs). This document ob
soletes RFC 4741. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6241"/>
<seriesInfo name="DOI" value="10.17487/RFC6241"/>
</reference>
<reference anchor="RFC8040">
<front>
<title>RESTCONF Protocol</title>
<author fullname="A. Bierman" initials="A." surname="Bierman"/>
<author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
<author fullname="K. Watsen" initials="K." surname="Watsen"/>
<date month="January" year="2017"/>
<abstract>
<t>This document describes an HTTP-based protocol that provides a
programmatic interface for accessing data defined in YANG, using the datastore c
oncepts 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="RFC6242">
<front>
<title>Using the NETCONF Protocol over Secure Shell (SSH)</title>
<author fullname="M. Wasserman" initials="M." surname="Wasserman"/>
<date month="June" year="2011"/>
<abstract>
<t>This document describes a method for invoking and running the N
etwork Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as a
n 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="RFC8446">
<front>
<title>The Transport Layer Security (TLS) Protocol Version 1.3</titl
e>
<author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
<date month="August" year="2018"/>
<abstract>
<t>This document specifies version 1.3 of the Transport Layer Secu
rity (TLS) protocol. TLS allows client/server applications to communicate over t
he Internet in a way that is designed to prevent eavesdropping, tampering, and m
essage forgery.</t>
<t>This document updates RFCs 5705 and 6066, and obsoletes RFCs 50
77, 5246, and 6961. This document also specifies new requirements for TLS 1.2 im
plementations.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8446"/>
<seriesInfo name="DOI" value="10.17487/RFC8446"/>
</reference>
<reference anchor="RFC8341">
<front>
<title>Network Configuration Access Control Model</title>
<author fullname="A. Bierman" initials="A." surname="Bierman"/>
<author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
<date month="March" year="2018"/>
<abstract>
<t>The standardization of network configuration interfaces for use
with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requ
ires a structured and secure operating environment that promotes human usability
and multi-vendor interoperability. There is a need for standard mechanisms to r
estrict NETCONF or RESTCONF protocol access for particular users to a preconfigu
red subset of all available NETCONF or RESTCONF protocol operations and content.
This document defines such an access control model.</t>
<t>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="RFC3688">
<front>
<title>The IETF XML Registry</title>
<author fullname="M. Mealling" initials="M." surname="Mealling"/>
<date month="January" year="2004"/>
<abstract>
<t>This document describes an IANA maintained registry for IETF st
andards which use Extensible Markup Language (XML) related items such as Namespa
ces, Document Type Declarations (DTDs), Schemas, and Resource Description Framew
ork (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="RFC6020">
<front>
<title>YANG - A Data Modeling Language for the Network Configuration
Protocol (NETCONF)</title>
<author fullname="M. Bjorklund" initials="M." role="editor" surname=
"Bjorklund"/>
<date month="October" year="2010"/>
<abstract>
<t>YANG is a data modeling language used to model configuration an
d state data manipulated by the Network Configuration Protocol (NETCONF), NETCON
F remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6020"/>
<seriesInfo name="DOI" value="10.17487/RFC6020"/>
</reference>
</references> </references>
<references> <references>
<name>Informative References</name> <name>Informative References</name>
<reference anchor="EN301129">
<!-- [rfced] For reference [EN301129], would you like us to add the following UR
L?
Current:
[EN301129] ETSI, "Transmission and Multiplexing (TM); Digital Radio
Relay Systems (DRRS); Synchronous Digital Hierarchy (SDH);
System performance monitoring parameters of SDH DRRS", EN
301 129 V1.1.2, May 1999.
Perhaps:
[EN301129] ETSI, "Transmission and Multiplexing (TM); Digital Radio
Relay Systems (DRRS); Synchronous Digital Hierarchy (SDH);
System performance monitoring parameters of SDH DRRS", EN
301 129 V1.1.2, May 1999, <https://www.etsi.org/deliver/
etsi_en/301100_301199/301129/01.01.02_60/
en_301129v010102p.pdf>
-->
<reference anchor="EN301129" target="https://www.etsi.org/deliver/etsi_e
n/301100_301199/301129/01.01.02_60/en_301129v010102p.pdf">
<front> <front>
<title>Transmission and Multiplexing (TM); Digital Radio Relay Syste <title>Transmission and Multiplexing (TM); Digital Radio Relay
ms (DRRS); Synchronous Digital Hierarchy (SDH); System performance monitoring pa Systems (DRRS); Synchronous Digital Hierarchy (SDH); System
rameters of SDH DRRS</title> performance monitoring parameters of SDH DRRS</title>
<author> <author>
<organization>ETSI</organization> <organization>ETSI</organization>
</author> </author>
<date year="1999" month="May"/> <date year="1999" month="May"/>
</front> </front>
<seriesInfo name="EN 301 129 V1.1.2" value=""/> <refcontent>EN 301 129 V1.1.2</refcontent>
</reference> </reference>
<reference anchor="EN302217-1">
<!-- [rfced] For reference [EN302217-1], we were unable to find a URL that
matches the information provided, but we did find one for ETSI EN 302
217-1 V3.1.1 (not V3.1.0). May we update to V3.1.1 and add the URL?
Original:
[EN302217-1]
ETSI, "Fixed Radio Systems; Characteristics and
requirements for point-to-point equipment and antennas;
Part 1: Overview, common characteristics and system-
dependent requirements", EN 302 217-1 V3.1.0 , May 2017.
Perhaps:
[EN302217-1]
ETSI, "Fixed Radio Systems; Characteristics and
requirements for point-to-point equipment and antennas;
Part 1: Overview, common characteristics and system-
dependent requirements", EN 302 217-1 V3.1.1, May 2017,
<https://www.etsi.org/deliver/etsi_en/302200_302299/
30221701/03.01.01_60/en_30221701v030101p.pdf>.
-->
<reference anchor="EN302217-1" target="https://www.etsi.org/deliver/etsi
_en/302200_302299/30221701/03.01.01_60/en_30221701v030101p.pdf">
<front> <front>
<title>Fixed Radio Systems; Characteristics and requirements for poi <title>Fixed Radio Systems; Characteristics and requirements for
nt-to-point equipment and antennas; Part 1: Overview, common characteristics and point-to-point equipment and antennas; Part 1: Overview, common
system- dependent requirements</title> characteristics and system-dependent requirements</title>
<author> <author>
<organization>ETSI</organization> <organization>ETSI</organization>
</author> </author>
<date year="2017" month="May"/> <date year="2017" month="May"/>
</front> </front>
<seriesInfo name="EN 302 217-1 V3.1.0" value=""/> <refcontent>EN 302 217-1 V3.1.1</refcontent>
</reference>
<reference anchor="RFC8453">
<front>
<title>Framework for Abstraction and Control of TE Networks (ACTN)</
title>
<author fullname="D. Ceccarelli" initials="D." role="editor" surname
="Ceccarelli"/>
<author fullname="Y. Lee" initials="Y." role="editor" surname="Lee"/
>
<date month="August" year="2018"/>
<abstract>
<t>Traffic Engineered (TE) networks have a variety of mechanisms t
o facilitate the separation of the data plane and control plane. They also have
a range of management and provisioning protocols to configure and activate netwo
rk resources. These mechanisms represent key technologies for enabling flexible
and dynamic networking. The term "Traffic Engineered network" refers to a networ
k that uses any connection-oriented technology under the control of a distribute
d or centralized control plane to support dynamic provisioning of end-to- end co
nnectivity.</t>
<t>Abstraction of network resources is a technique that can be app
lied to a single network domain or across multiple domains to create a single vi
rtualized network that is under the control of a network operator or the custome
r of the operator that actually owns the network resources.</t>
<t>This document provides a framework for Abstraction and Control
of TE Networks (ACTN) to support virtual network services and connectivity servi
ces.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8453"/>
<seriesInfo name="DOI" value="10.17487/RFC8453"/>
</reference>
<reference anchor="RFC8340">
<front>
<title>YANG Tree Diagrams</title>
<author fullname="M. Bjorklund" initials="M." surname="Bjorklund"/>
<author fullname="L. Berger" initials="L." role="editor" surname="Be
rger"/>
<date month="March" year="2018"/>
<abstract>
<t>This document captures the current syntax used in YANG module t
ree diagrams. The purpose of this document is to provide a single location for t
his definition. This syntax may be updated from time to time based on the evolut
ion of the YANG language.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="215"/>
<seriesInfo name="RFC" value="8340"/>
<seriesInfo name="DOI" value="10.17487/RFC8340"/>
</reference> </reference>
<reference anchor="I-D.draft-ietf-ccamp-if-ref-topo-yang">
<front>
<title>A YANG Data Model for Interface Reference Topology</title>
<author fullname="Jonas Ahlberg" initials="J." surname="Ahlberg">
<organization>Ericsson AB</organization>
</author>
<author fullname="Scott Mansfield" initials="S." surname="Mansfield"
>
<organization>Ericsson Inc</organization>
</author>
<author fullname="Min Ye" initials="M." surname="Ye">
<organization>Huawei Technologies</organization>
</author>
<author fullname="Italo Busi" initials="I." surname="Busi">
<organization>Huawei Technologies</organization>
</author>
<author fullname="Xi Li" initials="X." surname="Li">
<organization>NEC Laboratories Europe</organization>
</author>
<author fullname="Daniela Spreafico" initials="D." surname="Spreafic
o">
<organization>Nokia - IT</organization>
</author>
<date day="18" month="October" year="2023"/>
<abstract>
<t> This document defines a YANG data model to provide a referen
ce from a
termination point in a topology model to interface management
information.
</t> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.84
</abstract> 53.xml"/>
</front> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.83
<seriesInfo name="Internet-Draft" value="draft-ietf-ccamp-if-ref-topo- 40.xml"/>
yang-01"/>
</reference> <!-- [I-D.ietf-ccamp-if-ref-topo-yang] IESG state: Expired as of 07/01/24 -->
<reference anchor="I-D.draft-ietf-ccamp-bwa-topo-yang"> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-cc
<front> amp-if-ref-topo-yang.xml"/>
<title>A YANG Data Model for Bandwidth Availability Topology</title>
<author fullname="Jonas Ahlberg" initials="J." surname="Ahlberg"> <!-- [I-D.ietf-ccamp-bwa-topo-yang] IESG state: Expired as of 07/01/24 -->
<organization>Ericsson AB</organization> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-cc
</author> amp-bwa-topo-yang.xml"/>
<author fullname="Scott Mansfield" initials="S." surname="Mansfield"
> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.87
<organization>Ericsson Inc</organization> 92.xml"/>
</author> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.89
<author fullname="Min Ye" initials="M." surname="Ye"> 44.xml"/>
<organization>Huawei Technologies</organization>
</author>
<author fullname="Italo Busi" initials="I." surname="Busi">
<organization>Huawei Technologies</organization>
</author>
<author fullname="Xi Li" initials="X." surname="Li">
<organization>NEC Laboratories Europe</organization>
</author>
<author fullname="Daniela Spreafico" initials="D." surname="Spreafic
o">
<organization>Nokia - IT</organization>
</author>
<date day="18" month="October" year="2023"/>
<abstract>
<t> This document defines a YANG data model to describe bandwidt
h
availability for a link in a network topology.
</t>
</abstract>
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-ccamp-bwa-topo-yan
g-01"/>
</reference>
<reference anchor="RFC8792">
<front>
<title>Handling Long Lines in Content of Internet-Drafts and RFCs</t
itle>
<author fullname="K. Watsen" initials="K." surname="Watsen"/>
<author fullname="E. Auerswald" initials="E." surname="Auerswald"/>
<author fullname="A. Farrel" initials="A." surname="Farrel"/>
<author fullname="Q. Wu" initials="Q." surname="Wu"/>
<date month="June" year="2020"/>
<abstract>
<t>This document defines two strategies for handling long lines in
width-bounded text content. One strategy, called the "single backslash" strateg
y, is based on the historical use of a single backslash ('\') character to indic
ate where line-folding has occurred, with the continuation occurring with the fi
rst character that is not a space character (' ') on the next line. The second s
trategy, called the "double backslash" strategy, extends the first strategy by a
dding a second backslash character to identify where the continuation begins and
is thereby able to handle cases not supported by the first strategy. Both strat
egies use a self-describing header enabling automated reconstitution of the orig
inal content.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8792"/>
<seriesInfo name="DOI" value="10.17487/RFC8792"/>
</reference>
<reference anchor="RFC8944">
<front>
<title>A YANG Data Model for Layer 2 Network Topologies</title>
<author fullname="J. Dong" initials="J." surname="Dong"/>
<author fullname="X. Wei" initials="X." surname="Wei"/>
<author fullname="Q. Wu" initials="Q." surname="Wu"/>
<author fullname="M. Boucadair" initials="M." surname="Boucadair"/>
<author fullname="A. Liu" initials="A." surname="Liu"/>
<date month="November" year="2020"/>
<abstract>
<t>This document defines a YANG data model for Layer 2 network top
ologies. In particular, this data model augments the generic network and network
topology data models with topology attributes that are specific to Layer 2.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8944"/>
<seriesInfo name="DOI" value="10.17487/RFC8944"/>
</reference>
</references> </references>
</references> </references>
<section anchor="examples-mw-only"> <section anchor="examples-mw-only">
<name>Microwave Topology Model with base topology models</name> <name>Microwave Topology Model with Base Topology Models</name>
<t>This appendix provides some examples and illustrations of how the Micro
wave Topology Model can be used. The tree illustrates an example of a complete <!--[rfced] In the text before Figure 2, is this redundant? Please
Microwave Topology Model including the relevant data nodes from network-topology review.
and te-topology (base topology models). There are also JSON based instantiatio
ns of the Microwave Topology Model for a couple of small network examples.</t> NOTE: a similar redundancy may exist in Appendix B before Figure 4.
<t>The tree below shows an example of the relevant leafs for a complete Mi
crowave Topology Model including the augmented Network Topology Model defined in Original:
<xref target="RFC8345"/> and the Traffic Engineering (TE) Topologies model defi
ned in <xref target="RFC8795"/>.</t> The tree illustrates an example of a complete Microwave Topology Model
including the relevant data nodes from network-topology and
te-topology (base topology models). There are also JSON based
instantiations of the Microwave Topology Model for a couple of small
network examples.
The tree below shows an example of the relevant leafs for a complete
Microwave Topology Model including the augmented Network Topology
Model defined in [RFC8345] and the Traffic Engineering (TE)
Topologies model defined in [RFC8795].
-->
<t>The tree below shows an example of the relevant leafs for a complete Mi
crowave Topology Model including the augmented Network Topology Model defined in
<xref target="RFC8345"/> and the Traffic Engineering (TE) Topologies model defi
ned in <xref target="RFC8795"/>. There are also JSON-based instantiations of th
e Microwave Topology Model for a couple of small network examples.</t>
<figure anchor="fig-mw-only-tree"> <figure anchor="fig-mw-only-tree">
<name>Microwave Topology with Augmentations Tree</name> <name>Microwave Topology with Augmentations Tree</name>
<artwork><![CDATA[ <sourcecode type="yangtree"><![CDATA[
module: ietf-network module: ietf-network
+--rw networks +--rw networks
+--rw network* [network-id] +--rw network* [network-id]
| +--rw network-id network-id | +--rw network-id network-id
| +--rw network-types | +--rw network-types
| | +--rw tet:te-topology! | | +--rw tet:te-topology!
| | +--rw mwt:mw-topology! | | +--rw mwt:mw-topology!
| +--rw supporting-network* [network-ref] | +--rw supporting-network* [network-ref]
| | +--rw network-ref -> /networks/network/network-id | | +--rw network-ref -> /networks/network/network-id
| +--rw node* [node-id] | +--rw node* [node-id]
skipping to change at line 984 skipping to change at line 920
| | | | +--rw mwt:microwave-radio-link! | | | | +--rw mwt:microwave-radio-link!
| | | | +--rw mwt:rlt-mode | | | | +--rw mwt:rlt-mode
| | | | +--rw mwt:num-bonded-carriers | | | | +--rw mwt:num-bonded-carriers
| | | | | uint32 | | | | | uint32
| | | | +--rw mwt:num-protecting-carriers | | | | +--rw mwt:num-protecting-carriers
| | | | uint32 | | | | uint32
| | | +--:(mwt:microwave-carrier) | | | +--:(mwt:microwave-carrier)
| | | +--rw mwt:microwave-carrier! | | | +--rw mwt:microwave-carrier!
| | | +--rw mwt:tx-frequency? | | | +--rw mwt:tx-frequency?
| | | | uint32 | | | | uint32
| | | +--rw mwt:rx-frequency? | | | +--ro mwt:actual-rx-frequency?
| | | | uint32 | | | | uint32
| | | +--rw mwt:channel-separation? | | | +--rw mwt:channel-separation?
| | | | uint32 | | | | uint32
| | | +--ro mwt:actual-tx-cm? | | | +--ro mwt:actual-tx-cm?
| | | | identityref | | | | identityref
| | | +--ro mwt:actual-snir? | | | +--ro mwt:actual-snir?
| | | | decimal64 | | | | decimal64
| | | +--ro mwt:actual-transmitted-level? | | | +--ro mwt:actual-transmitted-level?
| | | decimal64 | | | decimal64
]]></artwork> ]]></sourcecode>
</figure> </figure>
<t>The Microwave Topology Model augments the TE Topology Model.</t> <t>The Microwave Topology Model augments the TE Topology Model.</t>
<figure anchor="fig-mw-model"> <figure anchor="fig-mw-model">
<name>Example for L2 over microwave</name> <name>Example for L2 over Microwave</name>
<artset> <artset>
<artwork type="svg"> <artwork type="svg">
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 640 480" clas s="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke -linecap="round"> <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 640 480" clas s="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke -linecap="round">
<path d="M 8,32 L 8,384" fill="none" stroke="black"/> <path d="M 8,32 L 8,384" fill="none" stroke="black"/>
<path d="M 24,48 L 24,96" fill="none" stroke="black"/> <path d="M 24,48 L 24,96" fill="none" stroke="black"/>
<path d="M 24,144 L 24,192" fill="none" stroke="black"/> <path d="M 24,144 L 24,192" fill="none" stroke="black"/>
<path d="M 24,240 L 24,288" fill="none" stroke="black"/> <path d="M 24,240 L 24,288" fill="none" stroke="black"/>
<path d="M 24,320 L 24,368" fill="none" stroke="black"/> <path d="M 24,320 L 24,368" fill="none" stroke="black"/>
<path d="M 112,48 L 112,96" fill="none" stroke="black"/> <path d="M 112,48 L 112,96" fill="none" stroke="black"/>
<path d="M 112,144 L 112,192" fill="none" stroke="black"/> <path d="M 112,144 L 112,192" fill="none" stroke="black"/>
skipping to change at line 1173 skipping to change at line 1109
| : | | | | : | | : | | | | : |
| +----------+ | | | | +----------+ | | +----------+ | | | | +----------+ |
| |mw-N1-CTP3*---' '---*mw-N2-CTP4| | | |mw-N1-CTP3*---' '---*mw-N2-CTP4| |
| | o<--------------------->o | | | | o<--------------------->o | |
| +----------+ | mwc-N1-N2-B | +----------+ | | +----------+ | mwc-N1-N2-B | +----------+ |
+--------------+ +--------------+ +--------------+ +--------------+
]]></artwork> ]]></artwork>
</artset> </artset>
</figure> </figure>
<section anchor="instance-data-for-20-mode-for-a-bonded-configuration"> <section anchor="instance-data-for-20-mode-for-a-bonded-configuration">
<name>Instance data for 2+0 mode for a bonded configuration</name> <name>Instance Data for 2+0 Mode for a Bonded Configuration</name>
<t>A L2 network with a supporting microwave network, showing a 2+0 micro
wave configuration. The num-bonded-carriers = 2 and the num-protecting-carriers <!--[rfced] Appendices A.1 and A.2 being with sentence fragments. How
= 0 which means both carriers are active so there is no redundancy but there is may we update to make these full sentences?
more capacity. The JSON encoding of the 2+0 example data follows:</t>
Original:
An L2 network with a supporting microwave network, showing a 2+0
microwave configuration.
and
An L2 network with a supporting microwave network, showing a 1+1
microwave configuration.
-->
<t>An L2 network with a supporting microwave network, showing a 2+0 micr
owave configuration is provided below. The num-bonded-carriers = 2, and the num-
protecting-carriers = 0. This means both carriers are active, so there is no red
undancy and there is more capacity. The JSON encoding of the 2+0 example data f
ollows:</t>
<sourcecode type="json" name="example2plus0-mw-only.json" markers="false "><![CDATA[ <sourcecode type="json" name="example2plus0-mw-only.json" markers="false "><![CDATA[
{ {
"ietf-network:networks": { "ietf-network:networks": {
"network": [ "network": [
{ {
"network-id": "L2-network", "network-id": "L2-network",
"network-types": { "network-types": {
"ietf-te-topology:te-topology": {} "ietf-te-topology:te-topology": {}
}, },
"supporting-network": [ "supporting-network": [
skipping to change at line 1420 skipping to change at line 1372
}, },
"destination": { "destination": {
"dest-node": "mw-N2", "dest-node": "mw-N2",
"dest-tp": "mw-N2-CTP2" "dest-tp": "mw-N2-CTP2"
}, },
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-link-attributes": { "te-link-attributes": {
"ietf-microwave-topology:mw-link": { "ietf-microwave-topology:mw-link": {
"microwave-carrier": { "microwave-carrier": {
"tx-frequency": 10728000, "tx-frequency": 10728000,
"rx-frequency": 10615000,
"channel-separation": 28000 "channel-separation": 28000
} }
} }
} }
} }
}, },
{ {
"link-id": "mwc-N1-N2-B", "link-id": "mwc-N1-N2-B",
"source": { "source": {
"source-node": "mw-N1", "source-node": "mw-N1",
skipping to change at line 1442 skipping to change at line 1393
}, },
"destination": { "destination": {
"dest-node": "mw-N2", "dest-node": "mw-N2",
"dest-tp": "mw-N2-CTP4" "dest-tp": "mw-N2-CTP4"
}, },
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-link-attributes": { "te-link-attributes": {
"ietf-microwave-topology:mw-link": { "ietf-microwave-topology:mw-link": {
"microwave-carrier": { "microwave-carrier": {
"tx-frequency": 10528000, "tx-frequency": 10528000,
"rx-frequency": 10415000,
"channel-separation": 28000 "channel-separation": 28000
} }
} }
} }
} }
} }
] ]
} }
] ]
} }
} }
]]></sourcecode> ]]></sourcecode>
</section> </section>
<section anchor="instance-data-for-11-mode-for-a-protected-configuration"> <section anchor="instance-data-for-11-mode-for-a-protected-configuration">
<name>Instance data for 1+1 mode for a protected configuration</name> <name>Instance Data for 1+1 Mode for a Protected Configuration</name>
<t>A L2 network with a supporting microwave network, showing a 1+1 micro <t>An L2 network with a supporting microwave network, showing a 1+1 micr
wave configuration. The num-bonded-carriers = 1 and the num-protecting-carriers owave configuration is provided below. The num-bonded-carriers = 1, and the num-
= 1 which means there is a standby carrier protecting the active carrier. The JS protecting-carriers = 1. This means there is a standby carrier protecting the ac
ON encoding of the 1+1 example data follows:</t> tive carrier. The JSON encoding of the 1+1 example data follows:</t>
<sourcecode type="json" name="example1plus1-mw-only.json" markers="false "><![CDATA[ <sourcecode type="json" name="example1plus1-mw-only.json" markers="false "><![CDATA[
{ {
"ietf-network:networks": { "ietf-network:networks": {
"network": [ "network": [
{ {
"network-id": "L2-network", "network-id": "L2-network",
"network-types": { "network-types": {
"ietf-te-topology:te-topology": {} "ietf-te-topology:te-topology": {}
}, },
"supporting-network": [ "supporting-network": [
skipping to change at line 1704 skipping to change at line 1654
}, },
"destination": { "destination": {
"dest-node": "mw-N2", "dest-node": "mw-N2",
"dest-tp": "mw-N2-CTP2" "dest-tp": "mw-N2-CTP2"
}, },
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-link-attributes": { "te-link-attributes": {
"ietf-microwave-topology:mw-link": { "ietf-microwave-topology:mw-link": {
"microwave-carrier": { "microwave-carrier": {
"tx-frequency": 10728000, "tx-frequency": 10728000,
"rx-frequency": 10615000,
"channel-separation": 28000 "channel-separation": 28000
} }
} }
} }
} }
}, },
{ {
"link-id": "mwc-N1-N2-B", "link-id": "mwc-N1-N2-B",
"source": { "source": {
"source-node": "mw-N1", "source-node": "mw-N1",
skipping to change at line 1726 skipping to change at line 1675
}, },
"destination": { "destination": {
"dest-node": "mw-N2", "dest-node": "mw-N2",
"dest-tp": "mw-N2-CTP4" "dest-tp": "mw-N2-CTP4"
}, },
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-link-attributes": { "te-link-attributes": {
"ietf-microwave-topology:mw-link": { "ietf-microwave-topology:mw-link": {
"microwave-carrier": { "microwave-carrier": {
"tx-frequency": 10728000, "tx-frequency": 10728000,
"rx-frequency": 10615000,
"channel-separation": 28000 "channel-separation": 28000
} }
} }
} }
} }
} }
] ]
} }
] ]
} }
} }
]]></sourcecode> ]]></sourcecode>
</section> </section>
</section> </section>
<section anchor="examples-mw-imports"> <section anchor="examples-mw-imports">
<name>Microwave Topology Model with example extensions</name> <name>Microwave Topology Model with Example Extensions</name>
<t>This non-normative appendix provides examples of how the Microwave Topo <t>This non-normative appendix provides examples of how the Microwave Topo
logy Model can be used with the interface reference topology (ifref) <xref targe logy Model can be used with the interface reference topology (ifref) <xref targe
t="I-D.draft-ietf-ccamp-if-ref-topo-yang"/> and the bandwidth-availability-topol t="I-D.ietf-ccamp-if-ref-topo-yang"/> and the bandwidth-availability-topology (b
ogy (bwa) <xref target="I-D.draft-ietf-ccamp-bwa-topo-yang"/> models. There is a wa) <xref target="I-D.ietf-ccamp-bwa-topo-yang"/> models. There is also a snippe
lso a snippet of JSON to show geolocation information instance data. When the J t of JSON to show geolocation information instance data. When the JSON files ha
SON files have long lines, <xref target="RFC8792"/> is used to wrap the long lin ve long lines, the long lines are wrapped as described in <xref target="RFC8792"
es.</t> />.</t>
<t>The tree below shows an example of the relevant leafs for a complete Mi <t>The tree below shows an example of the relevant leafs for a complete Mi
crowave Topology Model including interface reference topology (ifref) <xref targ crowave Topology Model including interface reference topology (ifref) <xref targ
et="I-D.draft-ietf-ccamp-if-ref-topo-yang"/> and bandwidth-availability-topology et="I-D.ietf-ccamp-if-ref-topo-yang"/> and bandwidth-availability-topology (bwa)
(bwa) <xref target="I-D.draft-ietf-ccamp-bwa-topo-yang"/> models.</t> <xref target="I-D.ietf-ccamp-bwa-topo-yang"/> models.</t>
<figure anchor="fig-mw-extensions-tree"> <figure anchor="fig-mw-extensions-tree">
<name>Microwave Topology with Extensions Tree</name> <name>Microwave Topology with Extensions Tree</name>
<artwork><![CDATA[ <sourcecode type="yangtree"><![CDATA[
module: ietf-network module: ietf-network
+--rw networks +--rw networks
+--rw network* [network-id] +--rw network* [network-id]
| +--rw network-id network-id | +--rw network-id network-id
| +--rw network-types | +--rw network-types
| | +--rw tet:te-topology! | | +--rw tet:te-topology!
| | +--rw mwt:mw-topology! | | +--rw mwt:mw-topology!
| +--rw supporting-network* [network-ref] | +--rw supporting-network* [network-ref]
| | +--rw network-ref -> /networks/network/network-id | | +--rw network-ref -> /networks/network/network-id
| +--rw node* [node-id] | +--rw node* [node-id]
skipping to change at line 1829 skipping to change at line 1777
| | | | | +--rw mwt:microwave-radio-link! | | | | | +--rw mwt:microwave-radio-link!
| | | | | +--rw mwt:rlt-mode | | | | | +--rw mwt:rlt-mode
| | | | | +--rw mwt:num-bonded-carriers | | | | | +--rw mwt:num-bonded-carriers
| | | | | | uint32 | | | | | | uint32
| | | | | +--rw mwt:num-protecting-carriers | | | | | +--rw mwt:num-protecting-carriers
| | | | | uint32 | | | | | uint32
| | | | +--:(mwt:microwave-carrier) | | | | +--:(mwt:microwave-carrier)
| | | | +--rw mwt:microwave-carrier! | | | | +--rw mwt:microwave-carrier!
| | | | +--rw mwt:tx-frequency? | | | | +--rw mwt:tx-frequency?
| | | | | uint32 | | | | | uint32
| | | | +--rw mwt:rx-frequency? | | | | +--ro mwt:actual-rx-frequency?
| | | | | uint32 | | | | | uint32
| | | | +--rw mwt:channel-separation? | | | | +--rw mwt:channel-separation?
| | | | | uint32 | | | | | uint32
| | | | +--ro mwt:actual-tx-cm? | | | | +--ro mwt:actual-tx-cm?
| | | | | identityref | | | | | identityref
| | | | +--ro mwt:actual-snir? | | | | +--ro mwt:actual-snir?
| | | | | decimal64 | | | | | decimal64
| | | | +--ro mwt:actual-transmitted-level? | | | | +--ro mwt:actual-transmitted-level?
| | | | decimal64 | | | | decimal64
| | | +--rw bwatopo:link-availability* [availability] | | | +--rw bwatopo:link-availability* [availability]
| | | | +--rw bwatopo:availability decimal64 | | | | +--rw bwatopo:availability decimal64
| | | | +--rw bwatopo:link-bandwidth? uint64 | | | | +--rw bwatopo:link-bandwidth? uint64
| | | +--ro bwatopo:actual-bandwidth? | | | +--ro bwatopo:actual-bandwidth?
| | | yang:gauge64 | | | yang:gauge64
]]></artwork> ]]></sourcecode>
</figure> </figure>
<t>Microwave is a transport technology which can be used to transport clie nt services, such as L2 Ethernet links. When an L2 link is transported over a s ingle supporting microwave radio link, the topologies could be as shown below. Note that the figure just shows an example, there might be other possibilities t o demonstrate such a topology. The example of the instantiation encoded in JSON is using only a selected subset of the leafs from the L2 topology model <xref t arget="RFC8944"/>. The example below uses <xref target="fig-mw-model"/> and adds the Interface related information.</t> <t>Microwave is a transport technology that can be used to transport clien t services, such as L2 Ethernet links. When an L2 link is transported over a si ngle supporting microwave radio link, the topologies could be as shown below. N ote that the figure just shows an example: there might be other possibilities to demonstrate such a topology. The example of the instantiation encoded in JSON is using only a selected subset of the leafs from the L2 topology model <xref ta rget="RFC8944"/>. The example below uses <xref target="fig-mw-model"/> and adds the interface-related information.</t>
<figure anchor="fig-mw-extensions"> <figure anchor="fig-mw-extensions">
<name>Interface extension example for L2 over microwave</name> <name>Interface Extension Example for L2 over Microwave</name>
<artset> <artset>
<artwork type="svg"> <artwork type="svg">
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 640 640" clas s="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke -linecap="round"> <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0 0 640 640" clas s="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke -linecap="round">
<path d="M 8,32 L 8,288" fill="none" stroke="black"/> <path d="M 8,32 L 8,288" fill="none" stroke="black"/>
<path d="M 8,368 L 8,624" fill="none" stroke="black"/> <path d="M 8,368 L 8,624" fill="none" stroke="black"/>
<path d="M 24,48 L 24,80" fill="none" stroke="black"/> <path d="M 24,48 L 24,80" fill="none" stroke="black"/>
<path d="M 24,112 L 24,144" fill="none" stroke="black"/> <path d="M 24,112 L 24,144" fill="none" stroke="black"/>
<path d="M 24,176 L 24,208" fill="none" stroke="black"/> <path d="M 24,176 L 24,208" fill="none" stroke="black"/>
<path d="M 24,240 L 24,272" fill="none" stroke="black"/> <path d="M 24,240 L 24,272" fill="none" stroke="black"/>
<path d="M 24,384 L 24,416" fill="none" stroke="black"/> <path d="M 24,384 L 24,416" fill="none" stroke="black"/>
skipping to change at line 2049 skipping to change at line 1997
| +-----------+ | | +------------+ | | +-----------+ | | +------------+ |
| | | | | | | |
| +-----------+ |tp-to-interface-path| +------------+ | | +-----------+ |tp-to-interface-path| +------------+ |
| |mw-N2-CTP4 |<---------------------->| CT-4 | | | |mw-N2-CTP4 |<---------------------->| CT-4 | |
| +-----------+ | | +------------+ | | +-----------+ | | +------------+ |
+---------------+ +----------------+ +---------------+ +----------------+
]]></artwork> ]]></artwork>
</artset> </artset>
</figure> </figure>
<section anchor="instance-data-for-20-mode"> <section anchor="instance-data-for-20-mode">
<name>Instance data for 2+0 mode</name> <name>Instance Data for 2+0 Mode</name>
<t>A L2 network with a supporting microwave network, including microwave <t>An L2 network with a supporting microwave network, including microwav
-topology (MW) and bandwidth-availability-topology (BWA) models as well as the r e-topology (mw) and bandwidth-availability-topology (bwa) models as well as the
eference to the associated interface management information, is encoded in JSON reference to the associated interface management information, is encoded in JSON
as follows:</t> as follows:</t>
<sourcecode type="json" name="example2plus0.json" markers="false"><![CDA TA[ <sourcecode type="json" name="example2plus0.json" markers="false"><![CDA TA[
{ {
"ietf-interfaces:interfaces": { "ietf-interfaces:interfaces": {
"interface": [ "interface": [
{ {
"name": "L2Interface1", "name": "L2Interface1",
"description": "'Ethernet Interface 1'", "description": "'Ethernet Interface 1'",
"type": "iana-if-type:ethernetCsmacd" "type": "iana-if-type:ethernetCsmacd"
}, },
{ {
skipping to change at line 2446 skipping to change at line 2394
"link-bandwidth": "998423" "link-bandwidth": "998423"
}, },
{ {
"availability": "0.95", "availability": "0.95",
"link-bandwidth": "1048576" "link-bandwidth": "1048576"
} }
], ],
"ietf-microwave-topology:mw-link": { "ietf-microwave-topology:mw-link": {
"microwave-carrier": { "microwave-carrier": {
"tx-frequency": 10728000, "tx-frequency": 10728000,
"rx-frequency": 10615000,
"channel-separation": 28000 "channel-separation": 28000
} }
} }
} }
} }
}, },
{ {
"link-id": "mwc-N1-N2-B", "link-id": "mwc-N1-N2-B",
"source": { "source": {
"source-node": "mw-N1", "source-node": "mw-N1",
skipping to change at line 2468 skipping to change at line 2415
}, },
"destination": { "destination": {
"dest-node": "mw-N2", "dest-node": "mw-N2",
"dest-tp": "mw-N2-CTP4" "dest-tp": "mw-N2-CTP4"
}, },
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-link-attributes": { "te-link-attributes": {
"ietf-microwave-topology:mw-link": { "ietf-microwave-topology:mw-link": {
"microwave-carrier": { "microwave-carrier": {
"tx-frequency": 10528000, "tx-frequency": 10528000,
"rx-frequency": 10415000,
"channel-separation": 28000 "channel-separation": 28000
} }
} }
} }
} }
} }
] ]
} }
] ]
} }
} }
]]></sourcecode> ]]></sourcecode>
</section> </section>
<section anchor="instance-data-for-geolocation-information"> <section anchor="instance-data-for-geolocation-information">
<name>Instance data for geolocation information</name> <name>Instance Data for Geolocation Information</name>
<t>This example provides a json snippet that shows geolocation informati <t>This example provides a JSON snippet that shows geolocation informati
on.</t> on.</t>
<artwork type="ascii-art" name="geo-example.json"><![CDATA[
<sourcecode type="json" name="geo-example.json"><![CDATA[
"node": [ "node": [
{ {
"node-id": "mw-N1", "node-id": "mw-N1",
... ...
"ietf-te-topology:te" : { "ietf-te-topology:te" : {
"ietf-te-topology:geolocation": { "ietf-te-topology:geolocation": {
"altitude": "200000", "altitude": "200000",
"latitude": "45", "latitude": "45",
"longitude": "90" "longitude": "90"
} }
}, },
"ietf-network-topology:termination-point": [ "ietf-network-topology:termination-point": [
... ...
]]></sourcecode>
]]></artwork>
</section> </section>
</section> </section>
<section numbered="false" anchor="acknowledgments"> <section numbered="false" anchor="acknowledgments">
<name>Acknowledgments</name> <name>Acknowledgments</name>
<t>This document was prepared using the kramdown RFC tool written and main <t>This document was initially prepared using the kramdown RFC tool writte
tained by Carsten Bormann. Thanks to Martin Thomson for the github integration o n and maintained by <contact fullname="Carsten Bormann"/>. Thanks to <contact fu
f the kramdown RFC tool and for the aasvg tool which is used for the ascii to SV llname="Martin Thomson"/> for the GitHub integration of the kramdown RFC tool an
G conversion.</t> d for the aasvg tool, which is used for the ascii-to-SVG conversion.</t>
<t>The authors would like to thank Tom Petch, Éric Vyncke, and Rob Wilton <t>The authors would like to thank <contact fullname="Tom Petch"/>, <conta
for their reviews.</t> ct fullname="Éric Vyncke"/>, and <contact fullname="Rob Wilton"/> for their revi
ews.</t>
</section> </section>
<section anchor="contributors" numbered="false" toc="include" removeInRFC="f alse"> <section anchor="contributors" numbered="false" toc="include">
<name>Contributors</name> <name>Contributors</name>
<contact fullname="Italo Busi"> <contact fullname="Italo Busi">
<organization>Huawei Technologies</organization> <organization>Huawei Technologies</organization>
<address> <address>
<email>italo.busi@huawei.com</email> <email>italo.busi@huawei.com</email>
</address> </address>
</contact> </contact>
</section> </section>
</back> </back>
<!-- ##markdown-source:
H4sIAAAAAAAAA+19W3vbxq7ou37FRH2I3YqyJTs3dbWpo7hp9rG98sU+Tfe3
Vh8oipJYU6Q2SVnxin3ez+86f+wAmCvJIUXf0qSVvl4scWaAATAABoMBHcdp
efE4iKYDtswmzvNWKwuy0B+w9gH774OTN+y1m7nsOB77IZvECTsOvCReuRc+
O4sXcRhPL9stdzRK/AvoUn7Ix6Du7ZbnZv40Ti4HLM3GrXHsRe4cII0Td5I5
gQ/gPc+dL5z5ysmgv3PpRlMnhE5p1goWyYBlyTLN+ru7L3b7rXQ5mgdpGsRR
drmAUd4env3cAiT2Wm7iuwP2Pl5mMK3WKk7Op0m8XAzYcHhw/I59gB/gAXuD
P7bO/UtoMYb+UeYnkZ85rxGd1oUfLf1BizFmdsbvHFx+FPh57gbhgNEEfsK5
dONkir+7iTcbsFmWLdLBzs4YqJklrnfuJ13Zamc13aF+O+4IkN4hoEE2W450
P/6968XzHYNQ0LGWeDgSp9+dR1oEA/avLPY6LI2TLPEnKfx1Occ/fm+13GU2
ixMgl4MgkxgFyB8HWZzg98kyDDmrT704y9ixG6WTwA/H+BAI4EbBf9wMODlg
h0ngpWkcATs8fOpzsqbYrzuX/X7yRTOchgCqgfxXHLkpO5iFI5+zoALEwSt8
mMJkfKDPURCNZ3E4TxdB4kes18OHXpCBtL6JM38k2AmLBUDs956xJ0/592WU
oUifrvyxHxk4/4FodF2ORj3Gx0HE/tsvo/rL0l35ATvzvVmEyynwUxPlk7jb
e/7iRYf9FlwuXZgQCa3Gezjzo+l4qdF+2us92+vl0B7Ogsg1sHbnl91Lfx5E
P80IuBXf3wIgVxndk8MhOwIZTlxgPODKDpdJvPBNlP/XMpkskzTzI+cgCt2p
z/aeaoR/8QNQFJJtAucXvd6THMpv/AQk4dJA+regexT8FPle6I66/rKE72tA
0g9ddroA1TAJvNiCe3weuMxhb89MdH+F3w4jwOeSvXOT8w7r7Wtsfw3mfoI6
jW0dv93WGPd3nz/LE/lt5oYmvmOOTzeV+PwUIXiiNahj6BSMlpleUHomOFLM
Xi1TC/krpEXADLBndwQ9Tc62ohiImQUXoOtaQTTR36Dn4cnebq/Xf0FfmLAL
P9IXxs4SWI1CAzM3GrPjZZgFi9D/iGpx6+x4+3v2OpgiWPbeHQex6PceJn7J
Ti9BBuYp23r9/v0ptDy9jLxZEkfxMlW9fgn8BLXnJds6ff3L9vdiAN6VLfyE
sI08n83jCHUNAl64CRAKVHnK4gmDfgwhUFelpOhTUApnp2/pAShomCSoqEvW
e/HiBf2W+ijNSB1oeMKAKAyown7tdXvdfktSqt/vPXN6Vlr9HHz0x5wKcubf
w8oDVD3ANEgz0A1IQ9E88f9nCUpo7kdZSkZ3EQdRBsrYoT8YPl7gU6K7C4Yr
AlUj6QOCmrHegP3zwk8uAn/VATmcA4WYVwYIKhyxcUTXsb/wozEObKJwK+L1
d3vP7MTrMyIU+3UPyLfbajmOw9xRilYxa53NgpSBZ7Ck6Y39SRCBHnG5G4HG
E3iNrkgWw8PUg3UC3Jdex848CMOAuM8SInYYROcpA+3qMjDt6AqwTHgmXQ55
HozHod9qfYMOQBKPlx7OqXUrRMTQqPlA9qxokXO0NfNx3eN31YgBuGUKUgID
psF8EQaTS5bNYFD/Y7bdhfUGfxeBS8ipOV2wy8vFAow0LgfPTYD8yVa6TezG
AV0wQ14AnIKvoElB/eOMuYyl7NOnR+9/Hj5/8rR3fd1lB3IARM8V8BbUHmbo
EkC2SOKLAF1I8M9AJyBo6LZwUUuyGKSQgw0SNrqEPiAL09CXA8PM3mY4OrhV
geeG4aUg9hhbB4BRxhVNRvPBSSS+5wcX+G2CYupHHlAcxjkwqMDxLaKHaEyn
iT/ls7dgO6FGZQJyIdJ9AY8dXJgJuAYe/gBaexJMlwkRE3iwmgXeDHpHDARD
MhYHu0S4E1D6DIg4C6YzpI/0lkE1Iqx0CX3BhzkEZNAnpWmfvT4WYsCZ7y6n
XEO0bX76mQByGE2BmH7ClfLhtvTMgWRtRWmYm+D7sxdPrq8l9kDDkYuoA6YV
24ETsarqR93bh1G7uKiM1VrUapx5mbRel4JxINxAW7DtYJaIRRH4GEAltst2
xF89tnW0u3PU2+bS5ppyMAIEffDnAE2LuHeANUiZOPJBp4Gugv5gedbzv4b3
xCQXeLaARey5crHoeRtTBPmI4swUEWHWGDROU0fOHIcA9FZB5s0IXy6nUpJQ
tECjgCcitVyOZC4NxubCQBuoGGqjCwoQbIE77gABF+5lGLtjgrNOWjuMfAhc
uZwdfWBHf1sJbwfliJNxrNWBDQcS89UMuVXVAhWF4CKuwoxags2S7CyRjYyc
optYj4LIXLIzZJaYGs2I05Ka11HREBI7QYvyrujG1y9Mxf+44BIEDJQyIAXW
Ze9Q/tG9QhByoQ3RO4zDENDcency5Grd5c4Xex2DrxexUzT84BYNY9jZIqlA
draOX59C60+fXuKC3H+yh+r98CPs80JurgA4kCeFL0QQQSkxSaR1gi5irwuj
Jgn4cERdiayVAMri6EH479WKb8vvTrsggLDG+1r7yVbcDAa4FoWjil5NXsUu
wX+B/QWCnsUr9HmiqU+rFzExnMYdaJQtU27H7NI4mQB3LAuAI9tt9bvIo4U7
VYscCONfgENW8rUqoXSUsh8BzqtgnM06OI+qtbZC3wHsIm4uwrGauYvmDmwz
QgRUaBFJtSTtZgyGex78h77CCs9mpMFdplfLTiokJwNffDmdEc2kSvEjIjD8
r9va67J/8tHU1CuXbF47Ihm1MwbU8kOYVJBxWItlsohTXCowVoTj+6QyQLsA
C2FyE5g9evzC/s7dj7wRdpYNlTUXBoQ8CWwgl+U337ADClkFHCdapxNYVPGK
iGM+Q7nnJCYRMpxCWA3Ds3dsKBykM8O4vENt1Gq9PzoTTv8REkK0COnBO8sT
sy/geAZ7UHaaJeCSLhO/dSD9QtSj08RdzNBfApGDTWQK+OQ4YTiJ0rEMaAew
QK8TPG/e0JiO9C18NzIsTHo5H8WhXD/AmXHgAmzYuWFX09C/5IZ+lww9YP8u
gacf+dIjp+EEsGEnsDlLW28LpAQTgr8jUEI8itHsk8yiDjBnE4/+AFnlbFlw
EGNhxAlfXPluMhbPTGdXCZmHCgwcv4icQvJqgLBcQQGQJSjEDi6oFBRIxCeX
uSOHj0jTuxKzg+3NlYpwQj9mfq5gqyvEFTrMV5n8mUJsaqk4aolfsdymAzpF
K5brJJdNDorpY2GfzNpHg7H0wUjf5QJIXkaOfjb70M4A+mR+fkKZb4LI40Ze
ZevTgH2jCcn3yD+0lZygMlJ8IKIKZrSvcXtWFVvWDimJHf2GK6f1f+DT4kMM
qmiOm3fhR7OdaDUQxEqNv40/OTV2YOYDY7Z8T/yd4yQrJkKm+POjhkMD5mLE
lslXCQWfO27GI0J+WgCGT28CKMIxla7hjrcNbHFOi0eyFf9ti350YtoKbr80
hoDngy1N6CTMFtvG4ys1aq7Jo+oRvPwArDyAx/uvpUE2QANQR2x8Xk1sfGqh
A3USlKghBGp7aruOHKrho3xDBRQI5qAyLD1WLaLl3BmBfvPHjtq/iM8SOL7X
r+8qdjagHXPdS12LnOJt13GLt3qUb6UaZh8duau/fFloUULA7JjctiO6iJEf
OqmPsUNk48smHWPYEGRLN3QAY29ehBhgFA18EFBu9b3TKEiKncGwegHsqJ7u
r4EsIyPAZ/KkXhb63v+SoJ/B6+K/K5fV2lU91esoxnWkfn8pKAy4krJGAwGu
Ih08oe8jLIRF86OCJ7PwDcWTyVObBQu1HynuQqQYgxNVta10w5V7ia31Nh/9
EREZULs+OVIHHYMLF7ztZVpwcXdwcabCn7KFEtB34QJCvhz3ToPEFo6j3V2C
rmuaSR8UPRhw98D1StgI9jshsp9PNcX4d6bCA4J9HD3Z+ZbRopwtFzsHravE
bP2PIJp5ckhkgsgLl+iM64gK2PxlQg5eCvtgTgyBpNRxxlS3et/tdlgf/9P7
rtdhfuZ1twkR6mCicrDAODb4GAcSbMr+6/SfJ4if2vDi9pDvvVhiypDYUJK7
CaTtlqWMPEkvDHBp5Tf1VfLF55zeIbKit8OC1KHvTlJDvKSj18n9BkjlfuBb
TgqK6B9LLoHkwtSP8NzS9MYqon45j5Ik1hbbwG0dj13mSL4jzx28SzZJ4nlV
dAC6u+vCLoVOTYWhEHHgI8n4sIxboS6wgiex4/tKHvQbBaERTr75YmudBnSu
ZZ4OuOsCphi4m7t/xIkBmkuJYOctFr2wIHoPXRnOQp5jLFOEPUehj7SPJJUR
IR5V5ihhc1jbKejBBOMXqpdcf5MYVBtFXTn/PBIyyTO0EXEUXqKwQbP8A76L
SOFZcc8OTDqOAbLQN/y8wVCq/sesFMtwZGNJDBnImDBjFwDEH8MickRUicdb
/ER+55PeIuk2em0THXAiJgUo+iHJrNTllsBTuJwMTSQP/yHZK2K6hxGNiK3G
QUp/Uygqb/sCHvkFMkW+QY4UDPASlZzEoct+5gp7jkQU+209PVrTYpnj/iAX
m6OQlDBTaP8wmuOMecAyF/fVcTmiCy06kBIl0QLn8wh25x0wgBmeKK1dLEbQ
nYfQRjEocRCsVCvZkR/GGEeIOR7u3GcCwYCOqJDOBbVmcA2a8ZF4GJXrg5qM
KFCm/JRRKFYhtZRfNPYnXIbEFpirRVPHdnL78Y5YBeYZDv4S4EmuCELg8pEn
+mrZ6INrCmygG8Yo30ciVRGr+AQuHaVngV6kDIBet4cH0BTHWbjAjvYyiQbY
fUBH8ung4zwcROkAew0qhm3jECI8MF9l3+P2nJMlH//4RA6laBit+Mm3mqhw
RttAC4bEGrDGZ1c40rUdaH7uGnr2sNAzvwIwONl1kEEIBk1dPem9F88HbfgU
Q0M5nGQcqQ4xkFcxcCufR0Ct2jINL2eVztz0nP0cJyBWW5jnty1T+d7QUOQj
ejyQ0f7whn3wRwP2j2YpdyJFA3odBZgm9w/MlsniQT6R78eWmMMhJbVZcsyM
jxyiOgHsx8JolrQ4y3h1SXDFEXVGmWUgW45XcYB8opFlEGrQfZXPJyqOohLF
LAMUkraKXa05W5ZhanKp+JAkIkbmAv+RnyOhoTD82rJz0xWMH8aLywS80oxt
edusv9vfp4RTWE3LNFMHXWDwUzxPoC7GDg9PZyh/JpVWDDPF0D8KQ0bDovHE
wxfab1D39z4YbL7tlueYeEQHfE3jZcKPQNgI3PbkEnGfp+IYhadcMvoSg3GE
6ZGng6PQUewCvX2MGeBpS7p0aRMj9wQUXecDCDMI5s2P8EgGuqVqO4aeWYee
v/cvArTvr05fA6+pLe+fwiIGxAAlOpLkx7H7XU+SQNPvccqOYMMd6hPPVNIg
5AexgAs1fy38OPF8S65xSgz2fb2+BdYOnhRuS5ISz6XBkucf5t4m0Ptn1FW/
wed7mIeYEM0Wfg6y1A8nJDCYmAfOD+IOzgH6qN02WS08QCIwKCrObt/pPxOq
siiJIItHboo+Fh5dxfM5T79K43DJ0wnaFdpUa1HKUEYyqV1zJSgigWqvMixc
NsHEPXRj6FAnkDv3aDkH7SWXHvzAw4pGLCMaMx0v1L9rL1N2pk2SmAz6i9Yo
5SfRGs2IiL7JvLY5nuyAasAEmqUvfy3PEWZ5Qlhb0JXwr/NY2AKe942JhUgm
NnlG2sLBRhSumr9v5Ajkc1OURvcS6WL8AFiBkMjqLYHES8deCoJVMdm7Cdcd
xSsvYAwJkCq819NZjPzQRJZZb+Y6MEPedWK3jDAdrn3+y3/atTJ36odii6Li
w4lKlQOLpgj2Xu/X1JkxRozyGIH2lo6bpm5RGxneXZXDq7dC+uS7vByThyIG
zxq8KSVEpD358whSPp64D7JgBNGdY346rToZkWdghGJPksI1kjShgyYXeiaU
eK2SlcZ/wJ6P570gtiLntrBANQlVMxgfE3R4bGY9OyzEaMoNTFLOJyDrhGsE
eS/MMo+E8mwyDoTUA0bplWrXNOAXsRxyRmhycjrX4v8ikD9xw7Te7BwQHowP
uKMHpOCOmU87DhLumd1gMfDZfd5VYJyW5emqjrsMqk4w9QqD2WO8SZCyXpGO
YpWMXynEb0rZNJhGLmV/RzG4v2wRLlNxzGFkKZGIasJu7XZ7bPzK8O62b0B2
mvufQvXSOeN9smB+ax4YaLFFvMLEPEJOkHl+SzqXZqu73lzX8Jsi96lpqhwY
rcNv4LfoDa/qnnNNzNPastl5ul8wOyP4707qAyPH6c3ZehJTelx1arC8i1DC
VdFFHni3GyfztBX871i7kNnTriblgQCkbpVQMIwug2BOXC7ZU7SRgFQ4D/uU
XW0jhUhRnGf4YVD1LZ6E4I1OgJAbKJdi3q03/sflMxwc4lbE1OlLOUpWpC9J
ilKw/3G3u8P/KXLlcUuN9LiYbrUzX2UDg0iP6/ckB8aZjXk5DAP3l/yEAReC
nB6Pobh6tZbYaOffdVNB4f51DKqEMzIvKRgVsklEZO697NJgH2WtBGDjWzPe
lk5mW1EN2V5itSkHXyXbOXx0pcdj+w0QebioNoiFxHFyw0uJIXa1sbCIyGs/
iosCUjlc1R5KnpaqfA6hcGoG8mYxJpKbeYKGe2ADozZrzYEwOmor5BIaYHIE
qm6k6ZX7kdmpZ+YalFArDIB323S6seCmHgoTxLnDiCdmblrsbSRYl/2OOkrm
kcfDX3VT0D6VIuRaomsvzvyrwAqvASeKbdYJrnQA1tO9EfmH9dT/TEwQk7oz
B65vqsRzyX9WR6gQdtyo8bupcXtsVeZzlHW3uOtks/Gh3hTcVGnnw6RaTxt5
zMaitMe6b6bB8xDLSluFuNerbnvTdXpD67mH0Z6FUSn0vCaEf1NtKjTfWo1q
addQqz6ATqunSznk/mcruHKbcqqzdRz1tEJF/r0UJaWZHJa36QX+q+f8IPNa
JYHzA248InfmbnIO8/ihjdqnbT7BTKMf2hWJRD/pY9cuJhzxK0Snvrek5Mih
SDwU1/8QOVVeQRwFFzKSbcUgUm/mz11+cQmjSDgM3Z2lq3EYIdRpYp7npxh0
uQj05UdQrS4PfdMRV+zhRTvMSMaBYNyTw7PhP09+FmldT/v7vetrzEV/f3hq
Pni+S5fuRFZwvPLTTHWlHFgcLuDRyRQp4BuVD6hBRyUwKG2PiXN425Cjx7vR
/FRPGPGUj3Y688OQbZ2e/rKtce0XUVJYmzj9cnb27rQh+DzssyMq6iJIsL//
lPLXBCPl9DnZSVEmcSgSVVUWHZJTHVJm4u4jmmocBjQmaAUvk2NQGRY3AWO+
DN1EQTDZAeItkpRbXOfKPHifMiswHwKPLYFW7oUbhJQ0aBtHCgOOgjmk8iJq
NOY5qpTGejORlbmFdJ1A1o3I+JFOLrOOkgatWW9EvMKdT7O4g0AolWvMy62x
cgIjZYHmk14FQjIZo5y7y2FgP/xXlWsw7owa6JWyO2htulyOV4Ajgt2hu/70
F0zPp7/YVtD1ux0ZuETNY1TEEEgCIHcZysosqW8iIdJejfRmsL5pgHWVkNEX
yxCMNkIi8mNCz9y8Zn0RJHFELILBP+CdblMMxBV5rK4mLnbQhStOvjweMgVo
gVW4VMEKeWl+htoetdGUKj7hID6/8Q4NJDYasJqoK1N/lyNMQRZugIJKyouv
5yBREweJ2JHzptz4AXLTYeqEHqPhcxeEgV+o4Zcr+B13sM/+fJGJ2wOyLg6l
IwTSAHH2qIsgKkvYWIICqcQfXYqyAJKXxIXMp8yDkQ90CeLETDfmkufkjsU7
+ZNqWpylw8ncpKTDvX5qxjlp4SaNGEMdzMoyMzSYMYJlOnhZ/lxOVyR4G2MH
0QUgmqdSCouf36yXUoBUCXAlfsPeHpwc2Awp/Y6Jdem5OEVO0RSSpK3Y/37/
lqsCHLZNOV2/HR+x9/4Uk90w4k4qYu/p8+eoIlJxLT8d8NzkFvQfsFtkFrcE
BMx2G/J00QHpq7eHp29agMKAnewcfM8lCKlP160Q24DuhCGSKre5y3Gh2ZIx
wgUW0wUXVDFEAdT+yVhfuBI6iN9zFyn2VLgHRxG3x+lyfBu6cmJIY7rb37XS
Ahl5QlXhqiaNLY5hiyBS9oCliNtLmKvqTBO6HUlxCH57e4DZ2vRdXXkfqAw6
QSwstjVyvfOKu9z8/IvcUjoUL9qdT9+Urn4IexCk8orIR23OSaWqCz5k1cJw
iQKgLm/g/S/kQiUyxu0F4crQrUQ1EA1s3m/BUhr4d1YzKL+CJMsVqHohhtam
5VEyv7QujVzwLRuVhDWSBjJMY37TiVdxwlseACvQJKidviwOshSzS/GShDZT
grbaFSHi4BWKFVVOKBInN11+X0RCuBnN9JWkQgq9bF7hoigvs8m9p3nFSHS3
QlyUyBcX0Kd84iK12GpxjZv77Vv2L8nfYPw7b3BVaANPmOWjn1Z0o42leqYe
F3aaj8wWCr3ClvNRAUT5rqExEdADv5fBGk/xkfMj29E7dblNr5wS8AAh4G7P
pFOugY1O4vdyh8LNyDz6vFtxHrapFJ7LG/QwO7XVL9Nqp3oAYzaCUJW0olO3
qunZjuNgjtmiSL5cj0WFqIkPPa/qXHeJ9NsKMllpjmAspDdh1TLAxoNoNSgw
vIYHOUgCqduDqRzAJLvmNc+2qBIMuXaRES8riJqJ+ziqYc1IjwrPmPkYHZRS
PYLcB/fF8s5QcYyYxpj6MWURqviQ2ezKbOmGeMVwzCHySgD1HTCNjTpY20lq
AAKiQBJskUQNNN8Z+9NE5vJXA4jBKlRDYLeCkFevCwsDVKMt1apQXaXQmsny
G9jcVm6l3P4qh4it/kojGF4NCGYH4RUg5ORaqDMtdKYsF3WdWj+4LwPdRrFZ
u3HgbQrKTfxkbc6Di5Wqjp4SQohqQQNUKWbLCNmCT9Wy5FVT8AMzoUyrRsMm
d8GG+jfBpVA9oGA0iaDVRnON2qZPjTJtajoFr7VGrZyQRQUqod3Ch7yiBt7b
9s55/l9+BSo5HBjNt8stchBzZTqsbVlVc6B3ysMB/u9VPXOdZWv+u1nBZl3H
xHO4WXppp2BlT5CltT1za75w7mKl7x0MUnGMqoI1lfwyj3Tq2BVLpZ6raSOL
2lRgJLoYJZ4KFiZvCcr1pcoGyWYKigWnyr2qDEKxApW1JzM750tSVbXPdbHc
/lrbW/5RJdS1wCyXvNaOID/1AG1GMlcLq9yF2UmfL45l7ZbrmauWVd+pGe2K
AJKHBmCpvnW/YPgSzdXqagagVMKrMRSq6dUMSKHSV/OJlEp/1Q8gPxpeseIW
htTWld2i8NxBrgqKrMR1VhdKMo+c8GQ4/1jWnXBTLwgcNxH3j3m90J59Hsxo
0m8BeczPd5amxSatK/On76z0KjU56qswzxW7gm8nPefsXQ+e8O78l5O+7E5N
+tCkT02co76K2LWuTJDxPxzb58fYROaqGufH1TifKneqZQAcMFbRnT9TXx+D
1PEMwdv0HrCzd+lt0EbygFACNcXc8X/zVRIaBMZfsU3fEV+OP5jswSK7vRJ1
v81RF9v05VjO8QeTPXacd9i/a3DWBBpoCu3Av/9Wffgz+dXsY1B1h/77b4Oq
Rp88SyUOA43mjmj5b43mwJiJZIokMAyNVIFWmh+P6bvzLaLLaYwU+lYX0oOv
Q07fASfwVUF2r7j4DtiQSMxZiGWuuW9bxvwKGexx/joHvEcBc75/S01R5IQu
rt4rTmjjhzJDbX2qhBDmsIc0elzo8xhpxOkDTfb5Gr2fda1p8Upx0cTtNjpP
6nzQsbSf4jk0UvnDr93sY9a+Ns2CeMsJNwmiXjwF7kGXUVE05byIeoxvI3E3
lI40sGX/u11+Wsvj/fKKt3n82God4IDycIFnJ9lrrekydzNRrpsD0Lln5sBd
OpqwVRr4gfXViUBVDYAf2K44YeWpIVQzKlfGEW+5Acw05oemvEoUS/wxSLmL
J7hYn0o9orJZsjy5OFPipegiflVTHpTgjOTZiaCjefTH/kiBZpgQ1jbPHlQW
XHsgssXa4hf44V/i6FdnBrZ15B2et7Vxa3fKbSgio8YVD4sVinKXp6CtkcNn
DFne4Bvo5VHMoQCOGOKJ12FEN6OdBvW7iT3ebqkfnEdJBAFOesbcS8iWBysP
uAbjjqWxCBaLloBCoc117vvvBQSt2Trlc4BmiFPoWNECfRsbxnVRfwscO6wb
E6qCWBUNeThCNXPIGyhSFj/Xpd9+r6e/KXSdxoLV//MFq/+lCBZ5xF+4YNnw
kzMxm5FglSiLnzsJllWb2TlCCei1Ok4EvfW6tkgjxaYL+t14ImXUqiR1q2yR
Vx65ZtcFmEaQ2wZYBbirlpBso4FywaoFWohmP8Cyk5Fo3lLuWNasPTvvW4U5
VNpuK0Z3s90WZVDOATLTBfIGP5fA/xUYf5sx+bsaf9NiftlaurH5H1ZZf1v/
LwHbvYYmxcIf68qWvO296Hd3u/3uno2zlp4WzaybViiERUUn6JY/di6qjOp5
Fn8p8W29PA8rxLmOXL0/mUje56dRU8FQNOp/1TS6q29v8xX/rr696RB/2Xaj
sXc/rHLuP6fduAm2+w9sN/b/ZnZDiMDGbuRBlWnUVDD+8nbDuhe5h627sZe8
7ebd7oTmN++V4bK7bN/tWszcvlcGU4pgm4lIO5dxZRWHXJOb2R+ZYmVf6byJ
SqZa64FKUjgPYXwMVC0Lrg5VmyNYh2pTy7NO27QthUes/KvRAIKlVsVhS3Sq
1hcys6myBdrr8vFSNblFe8txE/TZtXa5DxWVi8zUuLY5haNOYz+Dxinv0D+H
wikvsVvqm88mtLK0RqXEmjlhqKB2n/Wf7+7uVizmpNj6ae9JdetythYKOg7/
Z4voq88jont/ioju/9VF9MmNRHT/yxBR7ei1zF/wm1nNJJ9sIU71+1gweFfm
3XXxPJ/nXdhqn1DpVEvxk9qx7LkYve96Zi6GsEL3m45BMG6ejtFrkI7Ry6Vj
qLwKl7/3Gy/2i3vxxjsD6M4oT9NQ5cwrEy8Q903iRQGFTeJFYXrUfZN4YW24
Sbz4MoOzm8SLqhabxAtWerxJvMjNYZN4sUm8yHXfJF5sEi9Ko20SLzisTeLF
bWi0SbwQTzaJF5vEi03ixSbxYpN4sUm82CRebBIvTIJtEi82iRe6jT3xokIy
WF3iRc/aZZN4QZ02iRebxAtWJaKbxIuNiFLrryPxoofJEr37Sbywj7W2vrnM
L/A/Zvh2BKyilK9uLt7WYRQ4j2C7HsXJnN7UYCl3riqd37CuOUdIv7caX4Sn
3mesq4tvBVjQD9/u8vKt87o7TtxJ5pC0eh4AdoIJOiUksA6WjDeKbavCeI54
6Qm9/cGsY75yqweGh7lReZnzrihyjpkfWOPcZWkUAE3o/SqU1pHFlI/CjEq0
MMMJpyD9bSTG4Fs28HVNmUwKmQRISno/BpaDxaIzftpBJHkJ8D5gArCJgABp
lbj8NQm68eetiv4QvHsQvm3qpm/qpuvnsk7Spm76pm76pm76pm56FXnr6qYr
FjWqm65GbVg3vQCjUd30Shj2uumKNk3qpptUIbOOywFflScdAGfhZrPKgvFc
OQaTgWqf7qg/d1CCKw3gpkh7GZVNkfZNkfZNkfa/ZZH2ktmpL9JebXfqirTX
W5+6Iu0FS7S2SHulKWpUpL3QW/5RL9QVwBoVaS+MID/1AG9UpN2CXZMi7SZK
jYu0m52a0a4IYE2R9rsDaFSk/S5gGhVptwGoLdJeC6WiSLsNSE2R9vqJNCjS
XpLienicJ6OVi8EGbk/N+AzYIfOr3RblxzDbN5muBYOcXq1Tq7GGyimke5Y7
yA+9g3LqLqe+pWq9jqE2ql1/qEOusnA9QNCt6S6Zfs80qKJZJLrzF60aoVN8
465qKd7qmvrJReBhsBDf443lro/67BDvqYF3xItXy2gjjATP5Htq1UgwMJVV
dlkKShDf6my7dadfctuhEGKm31zI3wWL7xxPKeIY8ehjF6vlZ+IlyPSSWXot
LvtjmWalyGRHXK2bB9NZhmPF+J0t4jQNSFIQEMx/7M+BlPQuTDFhFXcU1Y0L
oc7cKyj55Tv+ekWKu1JMlS7j4fvq8f3OIb+cqN+eTWFWHiaVb5E1iuqrN3xT
oPbF/j6+hNxEgwdi6T30nz6ZFa5F1NMdj/lLCt4aIVXYOxOSKnx8+xcWqGHT
Yv1uawHvYgXv0nsLsBK4bQuYbyRrmTPjjQX2wuTOj1dHfYVkr1SbvOJFCcwK
r9jE2q/4w13mZ2TQVM8PgEALp8fBf4XzG9bzD6EMv/L57a2f395d53fb9dey
I7b20zKVRN8GTH6+ACUh3lnSREn0v0IhE/lua5WEfDXI1ze/YT3/EMrwK5/f
/vr57d91frddf5Uv2jD8VevrNoycAOHKak9EPVPuzO3ew3Gb6g76sLmcn8K2
jj9sNzs0fvXhYFu+0R3805Ufhvh/fgquj655zYY0jb1A+F6SBnM3cqc+vkzK
dMg66DoWvUk3rSrewBNtdBDciIeL1Jm2+kXmp8qyDsBIfulVe0kilQgTiLwk
WIjMl/Zj5fdrFvYey8YYPMdWAUwIz+Dx+8AXPYbp3PXGlHvEU46qofdvAL1/
P9DJfaoC+552Jke4rTnjJ5vhulkriaK+2FX2lN0KiVE69jXgGaIiDaiUQMUP
KFaxg4k6zn/8JF4/oojumOeyqU5Sbg/13OmLyEv7vZZalUyyUWsNl+6NWp+L
XH2TXPvryDWska2hKO5ypmE1li3R1+i6fm612XI1/cZLUM4fnXHANTB27e01
6VidQre2a5ItPJ331567H4P5cu5EMYmGs4hXlBfY7u92dzkPrteOySMQxqhy
Q+54c6K0TX7+x507T3oit/e6js97N+Hz3ufk85MNn++Rz5Xaz8bnptrvXvhs
5rNu+HxXPu/fhM/7n5PP+xs+34bPLTLUCK+22lmx1lm+AlpVkbOqIilN66Pw
duCz5trS98SNbMVRrnPkq6uHomCsK4IiEs/ljHJXzvUgVZXO6q6rWyrO1F1j
rqlnItPl1a3I21xCN9CpLVV2g7vmuaI4za5qrynssbb2WPnmQBV1CvJnsFDe
xzbYuOYaSFsOUHH/o1qShVDoq7LyDynRnXpR638WUet/HlErFi/7zKLWrxO1
8gXa+xS1/pcgajlN1+RWtRLKuipolttiawqfral4pq5oVV0Jqy1vVlvX7Nq2
mIp3mG+6mNYULWskM0UJqLtspiNbTroKMm/GU20WIlZXs24qmmuEyI3QrcJ+
6uXXjCy2Wu4VpgtHPnVkHKrZasrLZ9k/rS/Xdj9eSOP6bF+AC5I3m1+5C2Iv
mPZlOSGF+9XmHdLPA33PvpCKRTJuUrhs/c3XG5UJqa8yY1JMAF4YR0Xq4MBA
xnKapOOeTIaw1Q/a6HXWS1uhmETTcjQPR7JyPZUHoNjwTgRbJzu22jRfP8H2
bAS7rRN43/sNO9nusuPIe8lf+Y7DXlLty9pzFGpo3LdlWQ99/34sy/5fzLL0
b6UoSwXP/j6W5Q4EWyc7f03Lsv8XtCy5fcxtAwyWWm0NQgwFP3ptXbYbBhkK
ynRN9bXrxtyoLrVWU2Itv6evqKfWrIpak9pplUapqj5as6poTWqh2YIGHVOU
6+MkNynG06S2WWVFs0bvj2v40rhr2/QbO3NrapDdz0oaPuBCGt5qHTUShTW5
beW7ODXLrtCsvdt98SIv3vl7NdjmxYvn+/29JivLMvqTdaP3dvefP3n2tJk/
d4tVYa9M1aQeVZMqVI1qT93Xenh1/+th7wHXw/4DrYcHFILy2+CavAPuvoSA
+yEtpg/Am73M7T5e4lb/8raKalYtKhEmc4JVTTCX8l1VaSy6+MUvelWMU77W
hEQovs3DZK0lrKyfdrtd45tV6Jj9dSdmKwPXot2kDrISSptyJPBTrp7altVP
sNH+E1sDWb2ENO1uqaBqrUPfMNhQoIxdomC6juCkkgVoBMZ/BPuEsRSj69Y3
7MA7j+IVOHlTTIema9IkCOPYW1KC9MpNQRpwMfhjcbEO86rPE3c+xnuB738e
siyOQ7ZK8I5qRCnccxfwhX+hy+iSDd0kxSevUEYien2fC74mpmgfuxgGgR/i
OYoZyieODmScLUeUsT3li1Be2yvDRXiyn+umF1OBDl21lAXWVAOUSgR8+usb
fKngBawqLrSMXzV0l9ksTlK2oguQYXAuMsldTK6N5+ydn3mzDvt//zcJPPbr
ZeSd+x1C4X08Yh+CMNOzCBKW+BeBv0q7rf8PutalGyIBAQA=
<!-- [rfced] We had the following terminology/abbreviation questions
throughout the document:
a) Please consider updating the slash character with "and", "or", or
"and/or" for the ease of the reader in instances like the following
(just an example):
Original:
This information can be used to understand how changes in the
performance/status of a microwave radio link affect traffic on higher
layers.
b) In the text, we spotted both "radio link" (no hyphen) and
"radio-link" (with hyphen). It appears that the hyphenated version is
referring specifically to the code found in the yang trees, but we
wanted to make sure that this was the pattern. Please verify both
instances within the text and let us know if any updates need to be
made.
c) We have expanded these abbreviation as follows. Please let us know
any objections.
Time-Division Multiplexing (TDM)
-->
<!-- [rfced] Please review the "Inclusive Language" portion of the online
Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
and let us know if any changes are needed.
Note that our script did not flag any words in particular, but this should
still be reviewed as a best practice.
--> -->
</rfc> </rfc>
 End of changes. 91 change blocks. 
854 lines changed or deleted 526 lines changed or added

This html diff was produced by rfcdiff 1.48.