rfc9656.original   rfc9656.txt 
CCAMP Working Group S. Mansfield, Ed. Internet Engineering Task Force (IETF) S. Mansfield, Ed.
Internet-Draft Ericsson Inc Request for Comments: 9656 Ericsson Inc
Intended status: Standards Track J. Ahlberg Category: Standards Track J. Ahlberg
Expires: 31 August 2024 Ericsson AB ISSN: 2070-1721 Ericsson AB
M. Ye M. Ye
Huawei Technologies Huawei Technologies
X. Li X. Li
NEC Laboratories Europe NEC Laboratories Europe
D. Spreafico D. Spreafico
Nokia - IT Nokia - IT
28 February 2024 September 2024
A YANG Data Model for Microwave Topology A YANG Data Model for Microwave Topology
draft-ietf-ccamp-mw-topo-yang-12
Abstract Abstract
This document defines a YANG data model to describe microwave/ This document defines a YANG data model to describe microwave/
millimeter radio links in a network topology. millimeter radio links in a network topology.
About This Document
This note is to be removed before publishing as an RFC.
The latest revision of this draft can be found at https://github.com/
ietf-ccamp-wg/draft-ietf-ccamp-mw-topo-yang. Status information for
this document may be found at https://datatracker.ietf.org/doc/draft-
ietf-ccamp-mw-topo-yang/.
Discussion of this document takes place on the CCAMP Working Group
mailing list (mailto:ccamp@ietf.org), which is archived at
https://datatracker.ietf.org/wg/ccamp/about/. Subscribe at
https://www.ietf.org/mailman/listinfo/ccamp/.
Source for this draft and an issue tracker can be found at
https://github.com/https://github.com/ietf-ccamp-wg/draft-ietf-ccamp-
mw-topo-yang.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on 31 August 2024. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9656.
Copyright Notice Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Revised BSD License text as described in Section 4.e of the
provided without warranty as described in the Revised BSD License. Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction
1.1. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Abbreviations
1.2. Tree Structure . . . . . . . . . . . . . . . . . . . . . 4 1.2. Tree Structure
1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4 1.3. Prefixes in Data Node Names
2. Microwave Topology YANG Data Model . . . . . . . . . . . . . 4 2. Microwave Topology YANG Data Model
2.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. YANG Tree
2.2. Relationship between radio links and carriers . . . . . . 5 2.2. Relationship between Radio Links and Carriers
2.3. Relationship with client topology model . . . . . . . . . 6 2.3. Relationship with Client Topology Model
2.4. Applicability of the Data Model for Traffic Engineering 2.4. Applicability of the Data Model for Traffic Engineering
(TE) Topologies . . . . . . . . . . . . . . . . . . . . . 6 (TE) Topologies
2.5. Microwave Topology YANG Module . . . . . . . . . . . . . 6 2.5. Microwave Topology YANG Module
3. Security Considerations . . . . . . . . . . . . . . . . . . . 13 3. Security Considerations
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 4. IANA Considerations
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 5. References
5.1. Normative References . . . . . . . . . . . . . . . . . . 14 5.1. Normative References
5.2. Informative References . . . . . . . . . . . . . . . . . 15 5.2. Informative References
Appendix A. Microwave Topology Model with base topology Appendix A. Microwave Topology Model with Base Topology Models
models . . . . . . . . . . . . . . . . . . . . . . . . . 16 A.1. Instance Data for 2+0 Mode for a Bonded Configuration
A.1. Instance data for 2+0 mode for a bonded configuration . . 19 A.2. Instance Data for 1+1 Mode for a Protected Configuration
A.2. Instance data for 1+1 mode for a protected Appendix B. Microwave Topology Model with Example Extensions
configuration . . . . . . . . . . . . . . . . . . . . . . 25 B.1. Instance Data for 2+0 Mode
Appendix B. Microwave Topology Model with example extensions . . 31 B.2. Instance Data for Geolocation Information
B.1. Instance data for 2+0 mode . . . . . . . . . . . . . . . 35 Acknowledgments
B.2. Instance data for geolocation information . . . . . . . . 44 Contributors
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 44 Authors' Addresses
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
1. Introduction 1. Introduction
This document defines a YANG data model to describe topologies of This document defines a YANG data model to describe topologies of
microwave/millimeter wave (hereafter microwave is used to simplify microwave/millimeter wave (hereafter, "microwave" is used to simplify
the text). The YANG data model describes radio links, supporting the text). The YANG data model describes radio links, supporting
carrier(s) and the associated termination points [RFC8561]. A carrier(s) and the associated termination points [RFC8561]. A
carrier is a description of a link providing transport capacity over carrier is a description of a link providing transport capacity over
the air by a single carrier. It is typically defined by its the air by a single carrier. It is typically defined by its
transmitting and receiving frequencies. A radio link is a link transmitting and receiving frequencies. A radio link is a link
providing the aggregated transport capacity of the supporting providing the aggregated transport capacity of the supporting
carriers in aggregated and/or protected configurations, which can be carriers in aggregated and/or protected configurations, which can be
used to carry traffic on higher topology layers such as Ethernet and used to carry traffic on higher topology layers such as Ethernet and
TDM. The model augments "YANG Data Model for Traffic Engineering Time-Division Multiplexing (TDM). The model augments the YANG Data
(TE) Topologies" defined in [RFC8795], which is based on "A YANG Data Model for Traffic Engineering (TE) Topologies defined in [RFC8795],
Model for Network Topologies" defined in [RFC8345]. which is based on A YANG Data Model for Network Topologies defined in
[RFC8345].
The microwave point-to-point radio technology provides connectivity The microwave point-to-point radio technology provides connectivity
on Layer 0 / Layer 1 (L0/L1) over a radio link between two on Layer 0 / Layer 1 (L0/L1) over a radio link between two
termination points, using one or several supporting carriers in termination points using one or several supporting carriers in
aggregated or protected configurations. That application of aggregated or protected configurations. That application of
microwave technology cannot be used to perform cross-connection or microwave technology cannot be used to perform cross-connection or
switching of the traffic to create network connectivity across switching of the traffic to create network connectivity across
multiple microwave radio links. Instead, a payload of traffic on multiple microwave radio links. Instead, a payload of traffic on
higher topology layers, normally Layer 2 (L2) Ethernet, is carried higher topology layers, normally Layer 2 (L2) Ethernet, is carried
over the microwave radio link and when the microwave radio link is over the microwave radio link. When the microwave radio link is
terminated at the endpoints, cross-connection and switching can be terminated at the endpoints, cross-connection and switching can be
performed on that higher layer creating connectivity across multiple performed on that higher layer creating connectivity across multiple
supporting microwave radio links. supporting microwave radio links.
The microwave topology model is expected to be used between a The microwave topology model is expected to be used between a
Provisioning Network Controller (PNC) and a Multi Domain Service Provisioning Network Controller (PNC) and a Multi-Domain Service
Coordinator (MDSC) [RFC8453]. Examples of use cases that can be Coordinator (MDSC) [RFC8453]. Examples of use cases that can be
supported are: supported are:
1. Correlation between microwave radio links and the supported links 1. Correlation between microwave radio links and the supported links
on higher topology layers (e.g., an L2 Ethernet topology). This on higher topology layers (e.g., an L2 Ethernet topology). This
information can be used to understand how changes in the information can be used to understand how changes in the
performance/status of a microwave radio link affect traffic on performance/status of a microwave radio link affect traffic on
higher layers. higher layers.
2. Propagation of relevant characteristics of a microwave radio 2. Propagation of relevant characteristics of a microwave radio
skipping to change at page 4, line 13 skipping to change at line 132
path for a connection/service through the network end to end. path for a connection/service through the network end to end.
3. Optimization of the microwave radio link configurations on a 3. Optimization of the microwave radio link configurations on a
network level, with the purpose to minimize overall interference network level, with the purpose to minimize overall interference
and/or maximize the overall capacity provided by the links. and/or maximize the overall capacity provided by the links.
1.1. Abbreviations 1.1. Abbreviations
The following abbreviations are used in this document: The following abbreviations are used in this document:
CTP Carrier Termination Point CTP: Carrier Termination Point
RLT Radio Link Terminal RLT: Radio Link Terminal
RLTP Radio Link Termination Point RLTP: Radio Link Termination Point
1.2. Tree Structure 1.2. Tree Structure
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
chapter 3.1 of this document. The meaning of the symbols in these Section 2 of this document. The meaning of the symbols in these
diagrams is defined in [RFC8340]. diagrams is defined in [RFC8340].
1.3. Prefixes in Data Node Names 1.3. Prefixes in Data Node Names
In this document, names of data nodes and other data model objects In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1. corresponding YANG imported modules, as shown in Table 1.
+==========+=========================+===============+ +==========+=========================+===========+
| Prefix | YANG Module | Reference | | Prefix | YANG Module | Reference |
+==========+=========================+===============+ +==========+=========================+===========+
| mwt | ietf-microwave-topology | This document | | mwt | ietf-microwave-topology | RFC 9656 |
+----------+-------------------------+---------------+ +----------+-------------------------+-----------+
| nw | ietf-network | [RFC8345] | | nw | ietf-network | [RFC8345] |
+----------+-------------------------+---------------+ +----------+-------------------------+-----------+
| nt | ietf-network-topology | [RFC8345] | | nt | ietf-network-topology | [RFC8345] |
+----------+-------------------------+---------------+ +----------+-------------------------+-----------+
| mw-types | ietf-microwave-types | [RFC8561] | | mw-types | ietf-microwave-types | [RFC8561] |
+----------+-------------------------+---------------+ +----------+-------------------------+-----------+
| tet | ietf-te-topology | [RFC8795] | | tet | ietf-te-topology | [RFC8795] |
+----------+-------------------------+---------------+ +----------+-------------------------+-----------+
Table 1: Prefixes for imported YANG modules Table 1: Prefixes for Imported YANG Modules
2. Microwave Topology YANG Data Model 2. Microwave Topology YANG Data Model
2.1. YANG Tree 2.1. YANG Tree
module: ietf-microwave-topology
augment /nw:networks/nw:network/nw:network-types/tet:te-topology: module: ietf-microwave-topology
+--rw mw-topology!
augment /nw:networks/nw:network/nw:node/tet:te augment /nw:networks/nw:network/nw:network-types/tet:te-topology:
/tet:te-node-attributes: +--rw mw-topology!
+--rw mw-node! augment /nw:networks/nw:network/nw:node/tet:te
augment /nw:networks/nw:network/nw:node/nt:termination-point /tet:te-node-attributes:
/tet:te: +--rw mw-node!
+--rw mw-tp! augment /nw:networks/nw:network/nw:node/nt:termination-point
+--rw (mw-tp-option)? /tet:te:
+--:(microwave-rltp) +--rw mw-tp!
| +--rw microwave-rltp! +--rw (mw-tp-option)?
+--:(microwave-ctp) +--:(microwave-rltp)
+--rw microwave-ctp! | +--rw microwave-rltp!
augment /nw:networks/nw:network/nt:link/tet:te +--:(microwave-ctp)
/tet:te-link-attributes: +--rw microwave-ctp!
+--rw mw-link! augment /nw:networks/nw:network/nt:link/tet:te
+--rw (mw-link-option) /tet:te-link-attributes:
+--:(microwave-radio-link) +--rw mw-link!
| +--rw microwave-radio-link! +--rw (mw-link-option)
| +--rw rlt-mode +--:(microwave-radio-link)
| +--rw num-bonded-carriers uint32 | +--rw microwave-radio-link!
| +--rw num-protecting-carriers uint32 | +--rw rlt-mode
+--:(microwave-carrier) | +--rw num-bonded-carriers uint32
+--rw microwave-carrier! | +--rw num-protecting-carriers uint32
+--rw tx-frequency? uint32 +--:(microwave-carrier)
+--rw rx-frequency? uint32 +--rw microwave-carrier!
+--rw channel-separation? uint32 +--rw tx-frequency? uint32
+--ro actual-tx-cm? identityref +--rw rx-frequency? uint32
+--ro actual-snir? decimal64 +--rw channel-separation? uint32
+--ro actual-transmitted-level? decimal64 +--ro actual-tx-cm? identityref
augment /nw:networks/nw:network/nt:link/tet:te +--ro actual-snir? decimal64
/tet:te-link-attributes/tet:max-link-bandwidth +--ro actual-transmitted-level? decimal64
/tet:te-bandwidth: augment /nw:networks/nw:network/nt:link/tet:te
+--ro mw-bandwidth? uint64 /tet:te-link-attributes/tet:max-link-bandwidth
/tet:te-bandwidth:
+--ro mw-bandwidth? uint64
Figure 1: Microwave Topology Tree Figure 1: Microwave Topology Tree
2.2. Relationship between radio links and carriers 2.2. Relationship between Radio Links and Carriers
A microwave radio link is always an aggregate of one or multiple A microwave radio link is always an aggregate of one or multiple
carriers, in various configurations/modes. The supporting carriers carriers in various configurations/modes. The supporting carriers
are identified by their termination points and are listed in the are identified by their termination points and are listed in the
container bundled-links as part of the te-link-config in the YANG container-bundled links as part of the te-link-config in the YANG
Data Model for Traffic Engineering (TE) Topologies [RFC8795] for a Data Model for Traffic Engineering (TE) Topologies [RFC8795] for a
radio-link. The exact configuration of the included carriers is radio-link. The exact configuration of the included carriers is
further specified in the rlt-mode container (1+0, 2+0, 1+1, etc.) for further specified in the rlt-mode container (1+0, 2+0, 1+1, etc.) for
the radio-link. Appendix A includes JSON examples of how such a the radio-link. Appendix A includes JSON examples of how such a
relationship can be modelled. relationship can be modeled.
2.3. Relationship with client topology model 2.3. Relationship with Client Topology Model
A microwave radio link carries a payload of traffic on higher A microwave radio link carries a payload of traffic on higher
topology layers, normally L2 Ethernet. The leafs supporting-network, topology layers, normally L2 Ethernet. The leafs supporting-network,
supporting-node, supporting-link, and supporting-termination-point in supporting-node, supporting-link, and supporting-termination-point in
the generic YANG module for Network Topologies [RFC8345] are expected the generic YANG module for Network Topologies [RFC8345] are expected
to be used to model a relationship/dependency from higher topology to be used to model a relationship/dependency from higher topology
layers to a supporting microwave radio link topology layer. layers to a supporting microwave radio link topology layer.
Appendix A includes JSON examples of an L2 Ethernet link transported Appendix A includes JSON examples of an L2 Ethernet link transported
over one supporting microwave link. over one supporting microwave link.
2.4. Applicability of the Data Model for Traffic Engineering (TE) 2.4. Applicability of the Data Model for Traffic Engineering (TE)
Topologies Topologies
Since microwave is a point-to-point radio technology, a majority of Since microwave is a point-to-point radio technology, a majority of
the leafs in the Data Model for Traffic Engineering (TE) Topologies the leafs in the Data Model for Traffic Engineering (TE) Topologies
augmented by the microwave topology model are not applicable. An augmented by the microwave topology model are not applicable.
example of which leafs are considered applicable can be found in Examples of which leafs are considered applicable can be found in
appendices Appendix A and Appendix B in this document. Appendices A and B in this document.
More specifically in the context of the microwave-specific More specifically in the context of the microwave-specific
augmentations of te-topology, admin-status and oper-status leafs augmentations of te-topology, admin-status, and oper-status leafs
(from te-topology) are only applicable to microwave carriers (in the (from te-topology) are only applicable to microwave carriers (in the
mw-link tree) and not microwave radio links. Enable and disable of a mw-link tree) and not microwave radio links. Radio links are instead
radio link is instead done in the constituent carriers. Furthermore enabled or disabled in the constituent carriers. Furthermore, the
the status leafs related to mw-tp can be used when links are inter- status leafs related to mw-tp can be used with inter-domain links and
domain and when the status of only one side of the link is known, but when the status of only one side of the link is known. However,
since microwave is a point-to-point technology where both ends since microwave is a point-to-point technology where both ends
normally belong to the same domain it is not expected to be normally belong to the same domain, it is not expected to be
applicable in normal cases. applicable in normal cases.
2.5. Microwave Topology YANG Module 2.5. Microwave Topology YANG Module
This module imports typedefs and modules from [RFC8345], [RFC8561], This module imports typedefs and modules from [RFC8345], [RFC8561],
and [RFC8795], and it references [EN301129] and [EN302217-1]. and [RFC8795]. It references [EN301129] and [EN302217-1].
<CODE BEGINS> file "ietf-microwave-topology@2024-02-27.yang" <CODE BEGINS> file "ietf-microwave-topology@2024-09-18.yang"
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 page 7, line 20 skipping to change at line 282
} }
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 page 8, line 42 skipping to change at line 352
"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.";
skipping to change at page 9, line 29 skipping to change at line 387
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 page 10, line 5 skipping to change at line 411
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 page 11, line 8 skipping to change at line 462
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 {
skipping to change at page 12, line 4 skipping to change at line 506
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.";
} }
} }
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.";
} }
} }
} }
} }
} }
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/"
+ "tet:te-bandwidth" { + "tet:te-bandwidth" {
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
skipping to change at page 13, line 44 skipping to change at line 593
The NETCONF access control model [RFC8341] provides the means to The NETCONF access control model [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. operations and content.
The YANG module specified in this document imports and augments the The YANG module specified in this document imports and augments the
ietf-network and ietf-network-topology models defined in [RFC8345]. ietf-network and ietf-network-topology models defined in [RFC8345].
The security considerations from [RFC8345] are applicable to the The security considerations from [RFC8345] are applicable to the
module in this document. module in this document.
There are a several data nodes defined in this YANG module that are 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: and their sensitivity/vulnerability:
* rlt-mode: A malicious client could attempt to modify the mode in * rlt-mode: A malicious client could attempt to modify the mode in
which the radio link is configured and thereby change the intended which the radio link is configured and, thereby, change the
behavior of the link. intended behavior of the link.
* tx-frequency, rx-frequency and channel-separation: A malicious * tx-frequency, rx-frequency, and channel-separation: A malicious
client could attempt to modify the frequency configuration of a client could attempt to modify the frequency configuration of a
carrier which could modify the intended behavior or make the carrier, which could modify the intended behavior or make the
configuration invalid and thereby stop the operation of it. configuration invalid and, thereby, stop the operation of it.
4. IANA Considerations 4. IANA Considerations
IANA is asked to assign a new URI from the "IETF XML Registry" IANA has assigned a new URI from the "IETF XML Registry" [RFC3688] as
[RFC3688] as follows: follows:
URI: urn:ietf:params:xml:ns:yang:ietf-microwave-topology URI: urn:ietf:params:xml:ns:yang:ietf-microwave-topology
Registrant Contact: The IESG Registrant Contact: The IESG
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
It is proposed that IANA record the YANG module names in the "YANG IANA has recorded the YANG module names in the "YANG Module Names"
Module Names" registry [RFC6020] as follows: registry [RFC6020] as follows:
Name: ietf-microwave-topology Name: ietf-microwave-topology
Maintained by IANA?: N Maintained by IANA?: N
Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-topology Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-topology
Prefix: mwt Prefix: mwt
Reference: RFC XXXX Reference: RFC 9656
5. References 5. References
5.1. Normative References 5.1. Normative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/rfc/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/rfc/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/rfc/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/rfc/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/rfc/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/rfc/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,
Ananthakrishnan, H., and X. Liu, "A YANG Data Model for Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
2018, <https://www.rfc-editor.org/rfc/rfc8345>. 2018, <https://www.rfc-editor.org/info/rfc8345>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/rfc/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
[RFC8561] Ahlberg, J., Ye, M., Li, X., Spreafico, D., and M. [RFC8561] Ahlberg, J., Ye, M., Li, X., Spreafico, D., and M.
Vaupotic, "A YANG Data Model for Microwave Radio Link", Vaupotic, "A YANG Data Model for Microwave Radio Link",
RFC 8561, DOI 10.17487/RFC8561, June 2019, RFC 8561, DOI 10.17487/RFC8561, June 2019,
<https://www.rfc-editor.org/rfc/rfc8561>. <https://www.rfc-editor.org/info/rfc8561>.
[RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Gonzalez de Dios, "YANG Data Model for Traffic O. Gonzalez de Dios, "YANG Data Model for Traffic
Engineering (TE) Topologies", RFC 8795, Engineering (TE) Topologies", RFC 8795,
DOI 10.17487/RFC8795, August 2020, DOI 10.17487/RFC8795, August 2020,
<https://www.rfc-editor.org/rfc/rfc8795>. <https://www.rfc-editor.org/info/rfc8795>.
5.2. Informative References 5.2. Informative References
[EN301129] ETSI, "Transmission and Multiplexing (TM); Digital Radio [EN301129] ETSI, "Transmission and Multiplexing (TM); Digital Radio
Relay Systems (DRRS); Synchronous Digital Hierarchy (SDH); Relay Systems (DRRS); Synchronous Digital Hierarchy (SDH);
System performance monitoring parameters of SDH DRRS", EN System performance monitoring parameters of SDH DRRS", EN
301 129 V1.1.2 , May 1999. 301 129 V1.1.2, May 1999.
[EN302217-1] [EN302217-1]
ETSI, "Fixed Radio Systems; Characteristics and ETSI, "Fixed Radio Systems; Characteristics and
requirements for point-to-point equipment and antennas; requirements for point-to-point equipment and antennas;
Part 1: Overview, common characteristics and system- Part 1: Overview, common characteristics and system-
dependent requirements", EN 302 217-1 V3.1.0 , May 2017. dependent requirements", EN 302 217-1 V3.1.0, May 2017.
[I-D.draft-ietf-ccamp-bwa-topo-yang]
Ahlberg, J., Mansfield, S., Ye, M., Busi, I., Li, X., and
D. Spreafico, "A YANG Data Model for Bandwidth
Availability Topology", Work in Progress, Internet-Draft,
draft-ietf-ccamp-bwa-topo-yang-01, 18 October 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-
bwa-topo-yang-01>.
[I-D.draft-ietf-ccamp-if-ref-topo-yang]
Ahlberg, J., Mansfield, S., Ye, M., Busi, I., Li, X., and
D. Spreafico, "A YANG Data Model for Interface Reference
Topology", Work in Progress, Internet-Draft, draft-ietf-
ccamp-if-ref-topo-yang-01, 18 October 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-
if-ref-topo-yang-01>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/rfc/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for [RFC8453] Ceccarelli, D., Ed. and Y. Lee, Ed., "Framework for
Abstraction and Control of TE Networks (ACTN)", RFC 8453, Abstraction and Control of TE Networks (ACTN)", RFC 8453,
DOI 10.17487/RFC8453, August 2018, DOI 10.17487/RFC8453, August 2018,
<https://www.rfc-editor.org/rfc/rfc8453>. <https://www.rfc-editor.org/info/rfc8453>.
[RFC8792] Watsen, K., Auerswald, E., Farrel, A., and Q. Wu, [RFC8792] Watsen, K., Auerswald, E., Farrel, A., and Q. Wu,
"Handling Long Lines in Content of Internet-Drafts and "Handling Long Lines in Content of Internet-Drafts and
RFCs", RFC 8792, DOI 10.17487/RFC8792, June 2020, RFCs", RFC 8792, DOI 10.17487/RFC8792, June 2020,
<https://www.rfc-editor.org/rfc/rfc8792>. <https://www.rfc-editor.org/info/rfc8792>.
[RFC8944] Dong, J., Wei, X., Wu, Q., Boucadair, M., and A. Liu, "A [RFC8944] Dong, J., Wei, X., Wu, Q., Boucadair, M., and A. Liu, "A
YANG Data Model for Layer 2 Network Topologies", RFC 8944, YANG Data Model for Layer 2 Network Topologies", RFC 8944,
DOI 10.17487/RFC8944, November 2020, DOI 10.17487/RFC8944, November 2020,
<https://www.rfc-editor.org/rfc/rfc8944>. <https://www.rfc-editor.org/info/rfc8944>.
Appendix A. Microwave Topology Model with base topology models [YANG-BWA-TOPO]
Ahlberg, J., Mansfield, S., Ye, M., Busi, I., Li, X., and
D. Spreafico, "A YANG Data Model for Bandwidth
Availability Topology", Work in Progress, Internet-Draft,
draft-ietf-ccamp-bwa-topo-yang-01, 18 October 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-
bwa-topo-yang-01>.
[YANG-IF-REF-TOPO]
Ahlberg, J., Mansfield, S., Ye, M., Busi, I., Li, X., and
D. Spreafico, "A YANG Data Model for Interface Reference
Topology", Work in Progress, Internet-Draft, draft-ietf-
ccamp-if-ref-topo-yang-01, 18 October 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-
if-ref-topo-yang-01>.
Appendix A. Microwave Topology Model with Base Topology Models
This appendix provides some examples and illustrations of how the This appendix provides some examples and illustrations of how the
Microwave Topology Model can be used. The tree illustrates an Microwave Topology Model can be used. The tree illustrates an
example of a complete Microwave Topology Model including the relevant example of a complete Microwave Topology Model including the relevant
data nodes from network-topology and te-topology (base topology data nodes from network-topology and te-topology (base topology
models). There are also JSON based instantiations of the Microwave models). There are also JSON-based instantiations of the Microwave
Topology Model for a couple of small network examples. Topology Model for a couple of small network examples.
The tree below shows an example of the relevant leafs for a complete The tree below shows an example of the relevant leafs for a complete
Microwave Topology Model including the augmented Network Topology Microwave Topology Model including the augmented Network Topology
Model defined in [RFC8345] and the Traffic Engineering (TE) Model defined in [RFC8345] and the Traffic Engineering (TE)
Topologies model defined in [RFC8795]. Topologies model defined in [RFC8795].
module: ietf-network module: ietf-network
+--rw networks +--rw networks
+--rw network* [network-id] +--rw network* [network-id]
skipping to change at page 19, line 30 skipping to change at line 860
| |mw-N1- : *---+--' '--+---* : mw-N2-| | * carriers | |mw-N1- : *---+--' '--+---* : mw-N2-| | * carriers
| |CTP1 : o<--|---------------|-->o : CTP2 | | as bundled | |CTP1 : o<--|---------------|-->o : CTP2 | | as bundled
| +-------:--+ | | mwc-N1-N2-A | | +--:-------+ | links | +-------:--+ | | mwc-N1-N2-A | | +--:-------+ | links
| : | | | | : | | : | | | | : |
| +----------+ | | | | +----------+ | | +----------+ | | | | +----------+ |
| |mw-N1-CTP3*---' '---*mw-N2-CTP4| | | |mw-N1-CTP3*---' '---*mw-N2-CTP4| |
| | o<--------------------->o | | | | o<--------------------->o | |
| +----------+ | mwc-N1-N2-B | +----------+ | | +----------+ | mwc-N1-N2-B | +----------+ |
+--------------+ +--------------+ +--------------+ +--------------+
Figure 3: Example for L2 over microwave Figure 3: Example for L2 over Microwave
A.1. Instance data for 2+0 mode for a bonded configuration A.1. Instance Data for 2+0 Mode for a Bonded Configuration
A L2 network with a supporting microwave network, showing a 2+0 An L2 network with a supporting microwave network, showing a 2+0
microwave configuration. The num-bonded-carriers = 2 and the num- microwave configuration. The num-bonded-carriers = 2, and the num-
protecting-carriers = 0 which means both carriers are active so there protecting-carriers = 0. This means both carriers are active, so
is no redundancy but there is more capacity. The JSON encoding of there is no redundancy and there is more capacity. The JSON encoding
the 2+0 example data follows: of the 2+0 example data follows:
{ {
"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 page 25, line 30 skipping to change at line 1149
} }
} }
} }
} }
] ]
} }
] ]
} }
} }
A.2. Instance data for 1+1 mode for a protected configuration A.2. Instance Data for 1+1 Mode for a Protected Configuration
A L2 network with a supporting microwave network, showing a 1+1 An L2 network with a supporting microwave network, showing a 1+1
microwave configuration. The num-bonded-carriers = 1 and the num- microwave configuration. The num-bonded-carriers = 1, and the num-
protecting-carriers = 1 which means there is a standby carrier protecting-carriers = 1. This means there is a standby carrier
protecting the active carrier. The JSON encoding of the 1+1 example protecting the active carrier. The JSON encoding of the 1+1 example
data follows: data follows:
{ {
"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": {}
skipping to change at page 31, line 29 skipping to change at line 1436
} }
} }
} }
} }
] ]
} }
] ]
} }
} }
Appendix B. Microwave Topology Model with example extensions Appendix B. Microwave Topology Model with Example Extensions
This non-normative appendix provides examples of how the Microwave This non-normative appendix provides examples of how the Microwave
Topology Model can be used with the interface reference topology Topology Model can be used with the interface reference topology
(ifref) [I-D.draft-ietf-ccamp-if-ref-topo-yang] and the bandwidth- (ifref) [YANG-IF-REF-TOPO] and the bandwidth-availability-topology
availability-topology (bwa) [I-D.draft-ietf-ccamp-bwa-topo-yang] (bwa) [YANG-BWA-TOPO] models. There is also a snippet of JSON to
models. There is also a snippet of JSON to show geolocation show geolocation information instance data. When the JSON files have
information instance data. When the JSON files have long lines, long lines, the long lines are wrapped as described in [RFC8792].
[RFC8792] is used to wrap the long lines.
The tree below shows an example of the relevant leafs for a complete The tree below shows an example of the relevant leafs for a complete
Microwave Topology Model including interface reference topology Microwave Topology Model including interface reference topology
(ifref) [I-D.draft-ietf-ccamp-if-ref-topo-yang] and bandwidth- (ifref) [YANG-IF-REF-TOPO] and bandwidth-availability-topology (bwa)
availability-topology (bwa) [I-D.draft-ietf-ccamp-bwa-topo-yang] [YANG-BWA-TOPO] models.
models.
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
skipping to change at page 33, line 48 skipping to change at line 1549
| | | | +--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
Figure 4: Microwave Topology with Extensions Tree Figure 4: Microwave Topology with Extensions Tree
Microwave is a transport technology which can be used to transport Microwave is a transport technology that can be used to transport
client services, such as L2 Ethernet links. When an L2 link is client services, such as L2 Ethernet links. When an L2 link is
transported over a single supporting microwave radio link, the transported over a single supporting microwave radio link, the
topologies could be as shown below. Note that the figure just shows topologies could be as shown below. Note that the figure just shows
an example, there might be other possibilities to demonstrate such a an example: there might be other possibilities to demonstrate such a
topology. The example of the instantiation encoded in JSON is using topology. The example of the instantiation encoded in JSON is using
only a selected subset of the leafs from the L2 topology model only a selected subset of the leafs from the L2 topology model
[RFC8944]. The example below uses Figure 3 and adds the Interface [RFC8944]. The example below uses Figure 3 and adds the interface-
related information. related information.
Node N1 Interfaces Node N1 Interfaces
+---------------+ +----------------+ +---------------+ +----------------+
| +-----------+ |tp-to-interface-path| +------------+ | | +-----------+ |tp-to-interface-path| +------------+ |
| | L2-N1-TP1 |<---------------------->|L2Interface1| | | | L2-N1-TP1 |<---------------------->|L2Interface1| |
| +-----------+ | | +------------+ | | +-----------+ | | +------------+ |
| | | | | | | |
| +-----------+ |tp-to-interface-path| +------------+ | | +-----------+ |tp-to-interface-path| +------------+ |
| |mw-N1-RLTP1|<---------------------->| RLT-1 | | | |mw-N1-RLTP1|<---------------------->| RLT-1 | |
skipping to change at page 34, line 50 skipping to change at line 1599
| | | | | | | |
| +-----------+ |tp-to-interface-path| +------------+ | | +-----------+ |tp-to-interface-path| +------------+ |
| |mw-N2-CTP2 |<---------------------->| CT-2 | | | |mw-N2-CTP2 |<---------------------->| CT-2 | |
| +-----------+ | | +------------+ | | +-----------+ | | +------------+ |
| | | | | | | |
| +-----------+ |tp-to-interface-path| +------------+ | | +-----------+ |tp-to-interface-path| +------------+ |
| |mw-N2-CTP4 |<---------------------->| CT-4 | | | |mw-N2-CTP4 |<---------------------->| CT-4 | |
| +-----------+ | | +------------+ | | +-----------+ | | +------------+ |
+---------------+ +----------------+ +---------------+ +----------------+
Figure 5: Interface extension example for L2 over microwave Figure 5: Interface Extension Example for L2 over Microwave
B.1. Instance data for 2+0 mode B.1. Instance Data for 2+0 Mode
A L2 network with a supporting microwave network, including An L2 network with a supporting microwave network, including
microwave-topology (MW) and bandwidth-availability-topology (BWA) microwave-topology (mw) and bandwidth-availability-topology (bwa)
models as well as the reference to the associated interface models as well as the reference to the associated interface
management information, is encoded in JSON as follows: management information, is encoded in JSON as follows:
{ {
"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 page 44, line 4 skipping to change at line 2033
"tx-frequency": 10528000, "tx-frequency": 10528000,
"rx-frequency": 10415000, "rx-frequency": 10415000,
"channel-separation": 28000 "channel-separation": 28000
} }
} }
} }
} }
} }
] ]
} }
] ]
} }
} }
B.2. Instance data for geolocation information B.2. Instance Data for Geolocation Information
This example provides a json snippet that shows geolocation This example provides a JSON snippet that shows geolocation
information. information.
"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": {
skipping to change at page 44, line 33 skipping to change at line 2061
"latitude": "45", "latitude": "45",
"longitude": "90" "longitude": "90"
} }
}, },
"ietf-network-topology:termination-point": [ "ietf-network-topology:termination-point": [
... ...
Acknowledgments Acknowledgments
This document was prepared using the kramdown RFC tool written and This document was initially prepared using the kramdown RFC tool
maintained by Carsten Bormann. Thanks to Martin Thomson for the written and maintained by Carsten Bormann. Thanks to Martin Thomson
github integration of the kramdown RFC tool and for the aasvg tool for the GitHub integration of the kramdown RFC tool and for the aasvg
which is used for the ascii to SVG conversion. tool, which is used for the ascii-to-SVG conversion.
The authors would like to thank Tom Petch, Éric Vyncke, and Rob The authors would like to thank Tom Petch, Éric Vyncke, and Rob
Wilton for their reviews. Wilton for their reviews.
Contributors Contributors
Italo Busi Italo Busi
Huawei Technologies Huawei Technologies
Email: italo.busi@huawei.com Email: italo.busi@huawei.com
 End of changes. 99 change blocks. 
252 lines changed or deleted 226 lines changed or added

This html diff was produced by rfcdiff 1.48.