draft-ietf-ccamp-mw-yang-04.txt   draft-ietf-ccamp-mw-yang-05.txt 
CCAMP Working Group J. Ahlberg CCAMP Working Group J. Ahlberg
Internet-Draft Ericsson AB Internet-Draft Ericsson AB
Intended status: Standards Track M. Ye Intended status: Standards Track M. Ye
Expires: September 4, 2018 Huawei Technologies Expires: October 1, 2018 Huawei Technologies
X. Li X. Li
NEC Laboratories Europe GmbH NEC Laboratories Europe GmbH
D. Spreafico D. Spreafico
Nokia - IT Nokia - IT
M. Vaupotic M. Vaupotic
Aviat Networks Aviat Networks
March 3, 2018 March 30, 2018
A YANG Data Model for Microwave Radio Link A YANG Data Model for Microwave Radio Link
draft-ietf-ccamp-mw-yang-04 draft-ietf-ccamp-mw-yang-05
Abstract Abstract
This document defines a YANG data model for control and management This document defines a YANG data model for control and management
of the radio link interfaces, and their connectivity to packet of the radio link interfaces, and their connectivity to packet
(typically Ethernet) interfaces in a microwave/millimeter wave node. (typically Ethernet) interfaces in a microwave/millimeter wave node.
The data nodes for management of the interface protection The data nodes for management of the interface protection
functionality is broken out into a separate and generic YANG data functionality is broken out into a separate and generic YANG data
model in order to make it available also for other interface types. model in order to make it available also for other interface types.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress". material or to cite them other than as "work in progress".
This Internet-Draft will expire on September 4, 2018. This Internet-Draft will expire on October 1, 2018.
// RFC Ed.: replace all XXXX throughout the document with actual
// RFC numbers and remove this note
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 30 skipping to change at page 2, line 30
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3 1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3
1.2. Tree Structure . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Tree Structure . . . . . . . . . . . . . . . . . . . . . . 4
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Microwave Radio Link YANG Data Model. . . . . . . . . . . . . 4 3. Microwave Radio Link YANG Data Model. . . . . . . . . . . . . 4
3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Explanation of the Microwave Data Model . . . . . . . . . 6 3.2. Explanation of the Microwave Data Model . . . . . . . . . 6
4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 6 4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 6
5. Interface Protection YANG Module . . . . . . . . . . . . . . 30 5. Interface Protection YANG Module . . . . . . . . . . . . . . 24
6. Security Considerations . . . . . . . . . . . . . . . . . . . 37 6. Microwave Types YANG Module . . . . . . . . . . . . . . . . . 31
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 7. Security Considerations . . . . . . . . . . . . . . . . . . . 38
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40
8.1. Normative References . . . . . . . . . . . . . . . . . . 39 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 40
8.2. Informative References . . . . . . . . . . . . . . . . . 40 9.1. Normative References . . . . . . . . . . . . . . . . . . 40
Appendix A. Example: 1+0 and 2+0 configuration instances. . . . . 42 9.2. Informative References . . . . . . . . . . . . . . . . . 42
Appendix B. Contributors. . . . . . . . . . . . . . . . . . . . . 45 Appendix A. Example: 1+0 and 2+0 configuration instances. . . . . 43
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45 Appendix B. Contributors. . . . . . . . . . . . . . . . . . . . . 46
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46
1. Introduction 1. Introduction
This document defines a YANG data model for management and control of This document defines a YANG data model for management and control of
the radio link interface(s) and the relationship to packet (typically the radio link interface(s) and the relationship to packet (typically
Ethernet) and/or TDM interfaces in a microwave/millimeter wave node. Ethernet) and/or TDM interfaces in a microwave/millimeter wave node.
ETSI EN 302 217 series defines the characteristics and requirements ETSI EN 302 217 series defines the characteristics and requirements
of microwave/millimeter wave equipment and antennas. Especially ETSI of microwave/millimeter wave equipment and antennas. Especially ETSI
EN 302 217-2 [EN302217-2] specifies the essential parameters for EN 302 217-2 [EN302217-2] specifies the essential parameters for
the systems operating from 1.4GHz to 86GHz. The data model includes the systems operating from 1.4GHz to 86GHz. The data model includes
configuration and state data according to the new Network Management configuration and state data according to the new Network Management
Datastore Architecture [NMDA]. Datastore Architecture [RFC8342].
The design of the data model follows the framework for management and The design of the data model follows the framework for management and
control of microwave and millimeter wave interface parameters defined control of microwave and millimeter wave interface parameters defined
in [I-D.ietf-ccamp-microwave-framework]. This framework identifies in [I-D.ietf-ccamp-microwave-framework]. This framework identifies
the need and the scope of the YANG data model, the use cases and the need and the scope of the YANG data model, the use cases and
requirements that the model needs to support. Moreover, it provides requirements that the model needs to support. Moreover, it provides
a detailed gap analysis to identify the missing parameters and a detailed gap analysis to identify the missing parameters and
functionalities of the existing and established models to support the functionalities of the existing and established models to support the
specified use cases and requirements, and based on that recommends specified use cases and requirements, and based on that recommends
how the gaps should be filled with the development of the new model. how the gaps should be filled with the development of the new model.
According to the conclusion of the gap analysis, the structure of the According to the conclusion of the gap analysis, the structure of the
data model is based on the structure defined in data model is based on the structure defined in
[I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC7223bis] [I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC8343]
to align with the same structure for management of the packet to align with the same structure for management of the packet
interfaces. More specifically, the model will include interface interfaces. More specifically, the model will include interface
layering to manage the capacity provided by a radio link terminal for layering to manage the capacity provided by a radio link terminal for
the associated Ethernet and TDM interfaces, using the principles for the associated Ethernet and TDM interfaces, using the principles for
interface layering described in [RFC7223bis] as a basis. interface layering described in [RFC8343] as a basis.
The data nodes for management of the interface protection The data nodes for management of the interface protection
functionality is broken out into a separate and generic YANG data functionality is broken out into a separate and generic YANG data
module in order to make it available also for other interface types. module in order to make it available also for other interface types.
The designed YANG data model uses established microwave equipment The designed YANG data model uses established microwave equipment
and radio standards, such as ETSI EN 302 217-2, and the IETF: Radio and radio standards, such as ETSI EN 302 217-2, and the IETF: Radio
Link Model[I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: Link Model[I-D.ahlberg-ccamp-microwave-radio-link] and the ONF:
Microwave Modeling[ONF-model] as the basis for the definition of the Microwave Modeling[ONF-model] as the basis for the definition of the
detailed leafs/parameters, and proposes new ones to cover identified detailed leafs/parameters, and proposes new ones to cover identified
skipping to change at page 3, line 53 skipping to change at page 3, line 53
and/or TDM capacity to the associated Ethernet and/or TDM interfaces and/or TDM capacity to the associated Ethernet and/or TDM interfaces
in a node and used for setting up a transport service over a in a node and used for setting up a transport service over a
microwave/millimeter wave link. microwave/millimeter wave link.
The following acronyms are used in this document: The following acronyms are used in this document:
ACM Adaptive Coding Modulation ACM Adaptive Coding Modulation
ATPC Automatic Transmit Power Control ATPC Automatic Transmit Power Control
CM Coding Modulation BPSK Binary Phase-Shift Keying
CM Coding Modulation
CT Carrier Termination CT Carrier Termination
RLT Radio Link Terminal RLT Radio Link Terminal
RTPC Remote Transmit Power Control RTPC Remote Transmit Power Control
XPIC Cross Polarization Interference Cancellation XPIC Cross Polarization Interference Cancellation
MIMO Multiple-Input Multiple-Output MIMO Multiple-Input Multiple-Output
QAM Quadrature Amplitude Modulation
QPSK Quadrature Phase-Shift Keying
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 this document. The meaning of the symbols in chapter 3.1 of this this document. The meaning of the symbols in
these diagrams is defined in [YANG-TREE]. these diagrams is defined in [RFC8340].
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Microwave Radio Link YANG Data Model 3. Microwave Radio Link YANG Data Model
3.1. YANG Tree 3.1. YANG Tree
module: ietf-microwave-radio-link module: ietf-microwave-radio-link
+--rw radio-link-protection-groups +--rw radio-link-protection-groups
| +--rw protection-group* [name] | +--rw protection-group* [name]
| +--rw name string | +--rw name string
| +--rw architecture-type? identityref | +--rw architecture-type? identityref
skipping to change at page 6, line 34 skipping to change at page 6, line 43
The packet related measurements "in-octets", "in-unicast-pkts", "in- The packet related measurements "in-octets", "in-unicast-pkts", "in-
broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors", broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors",
"in-unknown-protos", "out-octets", "out-unicast-pkts", "out- "in-unknown-protos", "out-octets", "out-unicast-pkts", "out-
broadcast-pkts", "out-multicast-pkts", "out-discards", "out-errors" broadcast-pkts", "out-multicast-pkts", "out-discards", "out-errors"
are not within the scope of the microwave radio link domain and are not within the scope of the microwave radio link domain and
therefore not applicable for RLT and CT. therefore not applicable for RLT and CT.
4. Microwave Radio Link YANG Module 4. Microwave Radio Link YANG Module
This module imports typedefs and modules from [RFC6991], This module imports typedefs and modules from [RFC6991],
[RFC7223bis] and [RFC7224], and it references [TR102311], [RFC8343] and [RFC7224], and it references [TR102311],
[EN302217-1], [EN301129], and [G.826]. [EN302217-1], [EN301129], and [G.826].
<CODE BEGINS> file "ietf-microwave-radio-link@2018-03-03.yang" <CODE BEGINS> file "ietf-microwave-radio-link@2018-03-30.yang"
module ietf-microwave-radio-link { module ietf-microwave-radio-link {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link"; namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link";
prefix mrl; prefix mrl;
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
reference "RFC 6991"; reference "RFC 6991";
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference "RFC 7223bis"; reference "RFC 8343";
// RFC Ed.: replace 7223bis with actual RFC number and remove
// this note
} }
import ietf-interface-protection { import ietf-interface-protection {
prefix ifprot; prefix ifprot;
reference "RFC XXXX"; reference "RFC XXXX";
// RFC Ed.: replace XXXX with actual RFC number and remove
// this note
} }
import iana-if-type { import ietf-microwave-types {
prefix ianaift; prefix mw-types;
reference "RFC 7224"; reference "RFC XXXX";
} }
organization organization
"Internet Engineering Task Force (IETF) CCAMP WG"; "Internet Engineering Task Force (IETF) CCAMP WG";
contact contact
"WG List: <mailto:ccamp@ietf.org> "WG List: <mailto:ccamp@ietf.org>
ID-draft editors: ID-draft editors:
// RFC Ed.: replace ID-draft editors with Editors and remove
// this note
Jonas Ahlberg (jonas.ahlberg@ericsson.com); Jonas Ahlberg (jonas.ahlberg@ericsson.com);
Min Ye (amy.yemin@huawei.com); Min Ye (amy.yemin@huawei.com);
Xi Li (Xi.Li@neclab.eu); Xi Li (Xi.Li@neclab.eu);
Daniela Spreafico (daniela.spreafico@nokia.com) Daniela Spreafico (daniela.spreafico@nokia.com)
Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; Marko Vaupotic (Marko.Vaupotic@aviatnet.com)";
description description
"This is a module for the entities in "This is a module for the entities in
a generic microwave system. a generic microwave system.
skipping to change at page 7, line 49 skipping to change at page 8, line 8
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
(http://trustee.ietf.org/license-info). (http://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 XXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved."; authors of the code. All rights reserved.";
revision 2018-03-03 { revision 2018-03-30 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; reference "RFC XXXX: A YANG Data Model for Microwave Radio Link";
// RFC Ed.: replace XXXX with actual RFC number and remove
// this note
} }
/* /*
* Features * Features
*/ */
feature xpic { feature xpic {
description description
"Indicates that the device supports XPIC."; "Indicates that the device supports XPIC.";
reference "ETSI TR 102 311"; reference "ETSI TR 102 311";
} }
skipping to change at page 8, line 26 skipping to change at page 8, line 35
"Indicates that the device supports MIMO."; "Indicates that the device supports MIMO.";
reference "ETSI TR 102 311"; reference "ETSI TR 102 311";
} }
feature tdm { feature tdm {
description description
"Indicates that the device supports TDM."; "Indicates that the device supports TDM.";
} }
/* /*
* Interface identities
*/
identity radio-link-terminal {
base ianaift:iana-interface-type;
description
"Interface identity for a radio link terminal.";
}
identity carrier-termination {
base ianaift:iana-interface-type;
description
"Interface identity for a carrier termination.";
}
/*
* Radio-link-terminal mode identities
*/
identity rlt-mode {
description
"A description of the mode in which the radio link
terminal is configured. The format is X plus Y.
X represent the number of bonded carrier terminations.
Y represent the number of protecting carrier
terminations.";
}
identity one-plus-zero {
base rlt-mode;
description
"1 carrier termination only.";
}
identity one-plus-one {
base rlt-mode;
description
"1 carrier termination
and 1 protecting carrier termination.";
}
identity two-plus-zero {
base rlt-mode;
description
"2 bonded carrier terminations.";
}
/*
* Coding and modulation identities
*/
identity coding-modulation {
description
"The coding and modulation schemes.";
}
identity half-bpsk-strong {
base coding-modulation;
description
"Half BPSK strong coding and modulation scheme.";
}
identity half-bpsk {
base coding-modulation;
description
"Half BPSK coding and modulation scheme.";
}
identity half-bpsk-light {
base coding-modulation;
description
"Half BPSK light coding and modulation scheme.";
}
identity bpsk-strong {
base coding-modulation;
description
"BPSK strong coding and modulation scheme.";
}
identity bpsk {
base coding-modulation;
description
"BPSK coding and modulation scheme.";
}
identity bpsk-light {
base coding-modulation;
description
"BPSK light coding and modulation scheme.";
}
identity qpsk {
base coding-modulation;
description
"QPSK coding and modulation scheme.";
}
identity qam-4-strong {
base coding-modulation;
description
"4 QAM strong coding and modulation scheme.";
}
identity qam-4 {
base coding-modulation;
description
"4 QAM coding and modulation scheme.";
}
identity qam-4-light {
base coding-modulation;
description
"4 QAM light coding and modulation scheme.";
}
identity qam-16-strong {
base coding-modulation;
description
"16 QAM strong coding and modulation scheme.";
}
identity qam-16 {
base coding-modulation;
description
"16 QAM coding and modulation scheme.";
}
identity qam-16-light {
base coding-modulation;
description
"16 QAM light coding and modulation scheme.";
}
identity qam-32-strong {
base coding-modulation;
description
"32 QAM strong coding and modulation scheme.";
}
identity qam-32 {
base coding-modulation;
description
"32 QAM coding and modulation scheme.";
}
identity qam-32-light {
base coding-modulation;
description
"32 QAM light coding and modulation scheme.";
}
identity qam-64-strong {
base coding-modulation;
description
"64 QAM strong coding and modulation scheme.";
}
identity qam-64 {
base coding-modulation;
description
"64 QAM coding and modulation scheme.";
}
identity qam-64-light {
base coding-modulation;
description
"64 QAM light coding and modulation scheme.";
}
identity qam-128-strong {
base coding-modulation;
description
"128 QAM strong coding and modulation scheme.";
}
identity qam-128 {
base coding-modulation;
description
"128 QAM coding and modulation scheme.";
}
identity qam-128-light {
base coding-modulation;
description
"128 QAM light coding and modulation scheme.";
}
identity qam-256-strong {
base coding-modulation;
description
"256 QAM strong coding and modulation scheme.";
}
identity qam-256 {
base coding-modulation;
description
"256 QAM coding and modulation scheme.";
}
identity qam-256-light {
base coding-modulation;
description
"256 QAM light coding and modulation scheme.";
}
identity qam-512-strong {
base coding-modulation;
description
"512 QAM strong coding and modulation scheme.";
}
identity qam-512 {
base coding-modulation;
description
"512 QAM coding and modulation scheme.";
}
identity qam-512-light {
base coding-modulation;
description
"512 QAM light coding and modulation scheme.";
}
identity qam-1024-strong {
base coding-modulation;
description
"1024 QAM strong coding and modulation scheme.";
}
identity qam-1024 {
base coding-modulation;
description
"1024 QAM coding and modulation scheme.";
}
identity qam-1024-light {
base coding-modulation;
description
"1024 QAM light coding and modulation scheme.";
}
identity qam-2048-strong {
base coding-modulation;
description
"2048 QAM strong coding and modulation scheme.";
}
identity qam-2048 {
base coding-modulation;
description
"2048 QAM coding and modulation scheme.";
}
identity qam-2048-light {
base coding-modulation;
description
"2048 QAM light coding and modulation scheme.";
}
identity qam-4096-strong {
base coding-modulation;
description
"4096 QAM strong coding and modulation scheme.";
}
identity qam-4096 {
base coding-modulation;
description
"4096 QAM coding and modulation scheme.";
}
identity qam-4096-light {
base coding-modulation;
description
"4096 QAM light coding and modulation scheme.";
}
/*
* TDM-type identities
*/
identity tdm-type {
description
"A description of the type of TDM connection,
also indicating the supported capacity of the
connection.";
}
identity E1 {
base tdm-type;
description
"E1 connection, 2,048 Mbit/s.";
}
identity STM-1 {
base tdm-type;
description
"STM-1 connection, 155,52 Mbit/s.";
}
/*
* Typedefs * Typedefs
*/ */
typedef power { typedef power {
type decimal64 { type decimal64 {
fraction-digits 1; fraction-digits 1;
} }
description description
"Type used for power values, selected and measured."; "Type used for power values, selected and measured.";
} }
/* /*
* Radio Link Terminal (RLT) * Radio Link Terminal (RLT)
*/ */
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
when "if:type = 'mrl:radio-link-terminal'"; when "if:type = 'mw-types:radio-link-terminal'";
description description
"Addition of data nodes for radio link terminal to "Addition of data nodes for radio link terminal to
the standard Interface data model, for interfaces of the standard Interface data model, for interfaces of
the type 'radio-link-terminal'."; the type 'radio-link-terminal'.";
leaf id { leaf id {
type string; type string;
default ""; default "";
description description
"ID of the radio link terminal. Used by far-end when "ID of the radio link terminal. Used by far-end when
checking that it's connected to the correct RLT."; checking that it's connected to the correct RLT.";
} }
leaf mode { leaf mode {
type identityref { type identityref {
base rlt-mode; base mw-types:rlt-mode;
} }
mandatory true; mandatory true;
description description
"A description of the mode in which the radio link "A description of the mode in which the radio link
terminal is configured. The format is X plus Y. terminal is configured. The format is X plus Y.
X represent the number of bonded carrier terminations. X represent the number of bonded carrier terminations.
Y represent the number of protecting carrier Y represent the number of protecting carrier
terminations."; terminations.";
} }
leaf-list carrier-terminations { leaf-list carrier-terminations {
type if:interface-ref; type if:interface-ref;
must "/if:interfaces/if:interface[if:name = current()]" must "/if:interfaces/if:interface[if:name = current()]"
+ "/if:type = 'mrl:carrier-termination'" { + "/if:type = 'mw-types:carrier-termination'" {
description description
"The type of interface must be "The type of interface must be
'carrier-termination'."; 'carrier-termination'.";
} }
min-elements 1; min-elements 1;
description description
"A list of references to carrier terminations "A list of references to carrier terminations
included in the radio link terminal."; included in the radio link terminal.";
} }
skipping to change at page 16, line 37 skipping to change at page 10, line 32
list tdm-connections { list tdm-connections {
if-feature tdm; if-feature tdm;
key "tdm-type"; key "tdm-type";
description description
"A list stating the number of active TDM connections "A list stating the number of active TDM connections
of a specified tdm-type that is configured to be of a specified tdm-type that is configured to be
supported by the RLT."; supported by the RLT.";
leaf tdm-type { leaf tdm-type {
type identityref { type identityref {
base tdm-type; base mw-types:tdm-type;
} }
description description
"The type of TDM connection, which also indicates "The type of TDM connection, which also indicates
the supported capacity."; the supported capacity.";
} }
leaf tdm-connections { leaf tdm-connections {
type uint16; type uint16;
mandatory true; mandatory true;
description description
"Number of connections of the specified type."; "Number of connections of the specified type.";
} }
} }
} }
/* /*
* Carrier Termination * Carrier Termination
*/ */
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
when "if:type = 'mrl:carrier-termination'"; when "if:type = 'mw-types:carrier-termination'";
description description
"Addition of data nodes for carrier termination to "Addition of data nodes for carrier termination to
the standard Interface data model, for interfaces the standard Interface data model, for interfaces
of the type 'carrier-termination'."; of the type 'carrier-termination'.";
leaf carrier-id { leaf carrier-id {
type string; type string;
default "A"; default "A";
description description
"ID of the carrier. (e.g. A, B, C or D) "ID of the carrier. (e.g. A, B, C or D)
skipping to change at page 21, line 20 skipping to change at page 15, line 4
enum adaptive { enum adaptive {
description "Adaptive coding/modulation."; description "Adaptive coding/modulation.";
reference "ETSI EN 302 217-1"; reference "ETSI EN 302 217-1";
} }
} }
mandatory true; mandatory true;
description description
"A selection of single or "A selection of single or
adaptive coding/modulation mode."; adaptive coding/modulation mode.";
} }
leaf selected-cm { leaf selected-cm {
when "../coding-modulation-mode = 'single'"; when "../coding-modulation-mode = 'single'";
type identityref { type identityref {
base coding-modulation; base mw-types:coding-modulation;
} }
mandatory true; mandatory true;
description description
"Selected the single coding/modulation."; "Selected the single coding/modulation.";
} }
leaf selected-min-acm { leaf selected-min-acm {
when "../coding-modulation-mode = 'adaptive'"; when "../coding-modulation-mode = 'adaptive'";
type identityref { type identityref {
base coding-modulation; base mw-types:coding-modulation;
} }
mandatory true; mandatory true;
description description
"Selected minimum coding/modulation. "Selected minimum coding/modulation.
Adaptive coding/modulation shall not go Adaptive coding/modulation shall not go
below this value."; below this value.";
} }
leaf selected-max-acm { leaf selected-max-acm {
when "../coding-modulation-mode = 'adaptive'"; when "../coding-modulation-mode = 'adaptive'";
type identityref { type identityref {
base coding-modulation; base mw-types:coding-modulation;
} }
mandatory true; mandatory true;
description description
"Selected maximum coding/modulation. "Selected maximum coding/modulation.
Adaptive coding/modulation shall not go Adaptive coding/modulation shall not go
above this value."; above this value.";
} }
leaf actual-tx-cm { leaf actual-tx-cm {
type identityref { type identityref {
base coding-modulation; base mw-types:coding-modulation;
} }
config false; config false;
description description
"Actual coding/modulation in transmitting direction."; "Actual coding/modulation in transmitting direction.";
} }
leaf actual-snir { leaf actual-snir {
type decimal64 { type decimal64 {
fraction-digits 1; fraction-digits 1;
range "0..99"; range "0..99";
skipping to change at page 25, line 51 skipping to change at page 19, line 36
leaf maximum-available-power { leaf maximum-available-power {
type power; type power;
units "dBm"; units "dBm";
description description
"The maximum output power supported."; "The maximum output power supported.";
reference "ETSI EN 302 217-1"; reference "ETSI EN 302 217-1";
} }
leaf available-min-acm { leaf available-min-acm {
type identityref { type identityref {
base coding-modulation; base mw-types:coding-modulation;
} }
description description
"Minimum coding-modulation possible to use."; "Minimum coding-modulation possible to use.";
} }
leaf available-max-acm { leaf available-max-acm {
type identityref { type identityref {
base coding-modulation; base mw-types:coding-modulation;
} }
description description
"Maximum coding-modulation possible to use."; "Maximum coding-modulation possible to use.";
} }
} }
container error-performance-statistics { container error-performance-statistics {
config false; config false;
description description
"ITU-T G.826 error performance statistics relevant for "ITU-T G.826 error performance statistics relevant for
skipping to change at page 28, line 30 skipping to change at page 22, line 9
container radio-link-protection-groups { container radio-link-protection-groups {
description description
"Configuration of radio link protected groups (1+1) of "Configuration of radio link protected groups (1+1) of
carrier terminations in a radio link. More than one carrier terminations in a radio link. More than one
protected group per radio-link-terminal is allowed."; protected group per radio-link-terminal is allowed.";
uses ifprot:protection-groups { uses ifprot:protection-groups {
refine protection-group/members { refine protection-group/members {
must "/if:interfaces/if:interface[if:name = current()]" must "/if:interfaces/if:interface[if:name = current()]"
+ "/if:type = 'mrl:carrier-termination'" { + "/if:type = 'mw-types:carrier-termination'" {
description description
"The type of a protection member must be "The type of a protection member must be
'carrier-termination'."; 'carrier-termination'.";
} }
} }
refine protection-group/working-entity { refine protection-group/working-entity {
must "/if:interfaces/if:interface[if:name = current()]" must "/if:interfaces/if:interface[if:name = current()]"
+ "/if:type = 'mrl:carrier-termination'" { + "/if:type = 'mw-types:carrier-termination'" {
description description
"The type of a working-entity must be "The type of a working-entity must be
'carrier-termination'."; 'carrier-termination'.";
} }
} }
} }
} }
/* /*
* XPIC & MIMO groups - Configuration data nodes * XPIC & MIMO groups - Configuration data nodes
skipping to change at page 29, line 29 skipping to change at page 23, line 4
description description
"Name used for identification of the XPIC pair."; "Name used for identification of the XPIC pair.";
} }
leaf enabled { leaf enabled {
type boolean; type boolean;
default "false"; default "false";
description description
"Enable(true)/disable(false) XPIC"; "Enable(true)/disable(false) XPIC";
} }
leaf-list members { leaf-list members {
type if:interface-ref; type if:interface-ref;
must "/if:interfaces/if:interface[if:name = current()]" must "/if:interfaces/if:interface[if:name = current()]"
+ "/if:type = 'mrl:carrier-termination'" { + "/if:type = 'mw-types:carrier-termination'" {
description description
"The type of a member must be 'carrier-termination'."; "The type of a member must be 'carrier-termination'.";
} }
min-elements 2; min-elements 2;
max-elements 2; max-elements 2;
description description
"Association to XPIC pairs used in the radio link "Association to XPIC pairs used in the radio link
terminal."; terminal.";
} }
} }
skipping to change at page 30, line 21 skipping to change at page 23, line 48
leaf enabled { leaf enabled {
type boolean; type boolean;
default "false"; default "false";
description description
"Enable(true)/disable(false) MIMO"; "Enable(true)/disable(false) MIMO";
} }
leaf-list members { leaf-list members {
type if:interface-ref; type if:interface-ref;
must "/if:interfaces/if:interface[if:name = current()]" must "/if:interfaces/if:interface[if:name = current()]"
+ "/if:type = 'mrl:carrier-termination'" { + "/if:type = 'mw-types:carrier-termination'" {
description description
"The type of a member must be 'carrier-termination'."; "The type of a member must be 'carrier-termination'.";
} }
min-elements 2; min-elements 2;
description description
"Association to a MIMO group if used in the radio "Association to a MIMO group if used in the radio
link terminal."; link terminal.";
} }
} }
} }
skipping to change at page 30, line 43 skipping to change at page 24, line 22
<CODE ENDS> <CODE ENDS>
5. Interface Protection YANG Module 5. Interface Protection YANG Module
The data nodes for management of the interface protection The data nodes for management of the interface protection
functionality is broken out from the Microwave Radio Link Module functionality is broken out from the Microwave Radio Link Module
into a separate and generic YANG data module in order to make it into a separate and generic YANG data module in order to make it
available also for other interface types. available also for other interface types.
This module imports modules from [RFC7223bis], and it references This module imports modules from [RFC8343], and it references
[G.808.1]. [G.808.1].
<CODE BEGINS> file "ietf-interface-protection@2018-03-03.yang" <CODE BEGINS> file "ietf-interface-protection@2018-03-30.yang"
module ietf-interface-protection { module ietf-interface-protection {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection"; namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection";
prefix ifprot; prefix ifprot;
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference "RFC7223bis"; reference "RFC8343";
// RFC Ed.: replace 7223bis with actual RFC number and remove
// this note
} }
organization organization
"Internet Engineering Task Force (IETF) CCAMP WG"; "Internet Engineering Task Force (IETF) CCAMP WG";
contact contact
"WG List: <mailto:ccamp@ietf.org> "WG List: <mailto:ccamp@ietf.org>
ID-draft editors: ID-draft editors:
Jonas Ahlberg (jonas.ahlberg@ericsson.com); Jonas Ahlberg (jonas.ahlberg@ericsson.com);
Min Ye (amy.yemin@huawei.com); Min Ye (amy.yemin@huawei.com);
skipping to change at page 31, line 43 skipping to change at page 25, line 21
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
(http://trustee.ietf.org/license-info). (http://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 XXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved."; authors of the code. All rights reserved.";
revision 2018-03-03 { revision 2018-03-30 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; reference "RFC XXXX: A YANG Data Model for Microwave Radio Link";
// RFC Ed.: replace XXXX with actual RFC number and remove
// this note
} }
/* /*
* Protection architecture type identities * Protection architecture type identities
*/ */
identity protection-architecture-type { identity protection-architecture-type {
description description
"protection architecture type"; "protection architecture type";
reference "ITU-T G.808.1"; reference "ITU-T G.808.1";
skipping to change at page 37, line 5 skipping to change at page 31, line 5
trouble shooting purpose."; trouble shooting purpose.";
} }
} }
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
6. Security Considerations 6. Microwave Types YANG Module
This module defines a collection of common data types using the
YANG data modeling language. These common types are designed
to be imported by other modules defined in the microwave area.
<CODE BEGINS> file "ietf-microwave-types@2018-03-30.yang"
module ietf-microwave-types {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-types";
prefix mw-types;
import iana-if-type {
prefix ianaift;
reference "RFC 7224";
}
organization
"Internet Engineering Task Force (IETF) CCAMP WG";
contact
"WG List: <mailto:ccamp@ietf.org>
ID-draft editors:
Jonas Ahlberg (jonas.ahlberg@ericsson.com);
Min Ye (amy.yemin@huawei.com);
Xi Li (Xi.Li@neclab.eu);
Daniela Spreafico (daniela.spreafico@nokia.com)
Marko Vaupotic (Marko.Vaupotic@aviatnet.com)";
description
"This module contains a collection of YANG data types
considered generally useful for microwave interfaces.
Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.
Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved.";
revision 2018-03-30 {
description "Initial revision.";
reference "RFC XXXX: A YANG Data Model for Microwave Radio Link";
}
/*
* Interface identities
*/
identity radio-link-terminal {
base ianaift:iana-interface-type;
description
"Interface identity for a radio link terminal.";
}
identity carrier-termination {
base ianaift:iana-interface-type;
description
"Interface identity for a carrier termination.";
}
/*
* Radio-link-terminal mode identities
*/
identity rlt-mode {
description
"A description of the mode in which the radio link
terminal is configured. The format is X plus Y.
X represent the number of bonded carrier terminations.
Y represent the number of protecting carrier
terminations.";
}
identity one-plus-zero {
base rlt-mode;
description
"1 carrier termination only.";
}
identity one-plus-one {
base rlt-mode;
description
"1 carrier termination
and 1 protecting carrier termination.";
}
identity two-plus-zero {
base rlt-mode;
description
"2 bonded carrier terminations.";
}
/*
* Coding and modulation identities
*/
identity coding-modulation {
description
"The coding and modulation schemes.";
}
identity half-bpsk-strong {
base coding-modulation;
description
"Half BPSK strong coding and modulation scheme.";
}
identity half-bpsk {
base coding-modulation;
description
"Half BPSK coding and modulation scheme.";
}
identity half-bpsk-light {
base coding-modulation;
description
"Half BPSK light coding and modulation scheme.";
}
identity bpsk-strong {
base coding-modulation;
description
"BPSK strong coding and modulation scheme.";
}
identity bpsk {
base coding-modulation;
description
"BPSK coding and modulation scheme.";
}
identity bpsk-light {
base coding-modulation;
description
"BPSK light coding and modulation scheme.";
}
identity qpsk {
base coding-modulation;
description
"QPSK coding and modulation scheme.";
}
identity qam-4-strong {
base coding-modulation;
description
"4 QAM strong coding and modulation scheme.";
}
identity qam-4 {
base coding-modulation;
description
"4 QAM coding and modulation scheme.";
}
identity qam-4-light {
base coding-modulation;
description
"4 QAM light coding and modulation scheme.";
}
identity qam-16-strong {
base coding-modulation;
description
"16 QAM strong coding and modulation scheme.";
}
identity qam-16 {
base coding-modulation;
description
"16 QAM coding and modulation scheme.";
}
identity qam-16-light {
base coding-modulation;
description
"16 QAM light coding and modulation scheme.";
}
identity qam-32-strong {
base coding-modulation;
description
"32 QAM strong coding and modulation scheme.";
}
identity qam-32 {
base coding-modulation;
description
"32 QAM coding and modulation scheme.";
}
identity qam-32-light {
base coding-modulation;
description
"32 QAM light coding and modulation scheme.";
}
identity qam-64-strong {
base coding-modulation;
description
"64 QAM strong coding and modulation scheme.";
}
identity qam-64 {
base coding-modulation;
description
"64 QAM coding and modulation scheme.";
}
identity qam-64-light {
base coding-modulation;
description
"64 QAM light coding and modulation scheme.";
}
identity qam-128-strong {
base coding-modulation;
description
"128 QAM strong coding and modulation scheme.";
}
identity qam-128 {
base coding-modulation;
description
"128 QAM coding and modulation scheme.";
}
identity qam-128-light {
base coding-modulation;
description
"128 QAM light coding and modulation scheme.";
}
identity qam-256-strong {
base coding-modulation;
description
"256 QAM strong coding and modulation scheme.";
}
identity qam-256 {
base coding-modulation;
description
"256 QAM coding and modulation scheme.";
}
identity qam-256-light {
base coding-modulation;
description
"256 QAM light coding and modulation scheme.";
}
identity qam-512-strong {
base coding-modulation;
description
"512 QAM strong coding and modulation scheme.";
}
identity qam-512 {
base coding-modulation;
description
"512 QAM coding and modulation scheme.";
}
identity qam-512-light {
base coding-modulation;
description
"512 QAM light coding and modulation scheme.";
}
identity qam-1024-strong {
base coding-modulation;
description
"1024 QAM strong coding and modulation scheme.";
}
identity qam-1024 {
base coding-modulation;
description
"1024 QAM coding and modulation scheme.";
}
identity qam-1024-light {
base coding-modulation;
description
"1024 QAM light coding and modulation scheme.";
}
identity qam-2048-strong {
base coding-modulation;
description
"2048 QAM strong coding and modulation scheme.";
}
identity qam-2048 {
base coding-modulation;
description
"2048 QAM coding and modulation scheme.";
}
identity qam-2048-light {
base coding-modulation;
description
"2048 QAM light coding and modulation scheme.";
}
identity qam-4096-strong {
base coding-modulation;
description
"4096 QAM strong coding and modulation scheme.";
}
identity qam-4096 {
base coding-modulation;
description
"4096 QAM coding and modulation scheme.";
}
identity qam-4096-light {
base coding-modulation;
description
"4096 QAM light coding and modulation scheme.";
}
/*
* TDM-type identities
*/
identity tdm-type {
description
"A description of the type of TDM connection,
also indicating the supported capacity of the
connection.";
}
identity E1 {
base tdm-type;
description
"E1 connection, 2.048 Mbit/s.";
}
identity STM-1 {
base tdm-type;
description
"STM-1 connection, 155.52 Mbit/s.";
}
}
<CODE ENDS>
7. Security Considerations
The YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246]. [RFC5246].
The NETCONF access control model [RFC6536] 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.
There are a number of 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 may be considered sensitive or vulnerable default). These data nodes may 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
skipping to change at page 38, line 31 skipping to change at page 39, line 49
This list represents the XPIC configuration of a pair carriers. This list represents the XPIC configuration of a pair carriers.
Unauthorized access to these data nodes could interrupt the ability Unauthorized access to these data nodes could interrupt the ability
to forward traffic. to forward traffic.
MIMO: MIMO:
/mimo-groups: /mimo-groups:
This list represents the MIMO configuration of multiple carriers. This list represents the MIMO configuration of multiple carriers.
Unauthorized access to these data nodes could interrupt the ability Unauthorized access to these data nodes could interrupt the ability
to forward traffic. to forward traffic.
The security considerations of [RFC7223bis] also apply to this The security considerations of [RFC8343] also apply to this
document. document.
7. IANA Considerations 8. IANA Considerations
It is proposed that IANA should assign new URIs from the It is proposed that IANA should assign new URIs from the
"IETF XML Registry" [RFC3688] as follows: "IETF XML Registry" [RFC3688] as follows:
URI: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link URI: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link
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.
URI: urn:ietf:params:xml:ns:yang:ietf-interface-protection URI: urn:ietf:params:xml:ns:yang:ietf-interface-protection
Registrant Contact: The IESG Registrant Contact: The IESG
skipping to change at page 39, line 4 skipping to change at page 40, line 25
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 should record YANG module names in the It is proposed that IANA should record YANG module names in the
"YANG Module Names" registry [RFC6020] as follows: "YANG Module Names" registry [RFC6020] as follows:
Name: ietf-microwave-radio-link Name: ietf-microwave-radio-link
Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link
Prefix: mrl Prefix: mrl
Reference: RFC XXXX Reference: RFC XXXX
Name: ietf-interface-protection Name: ietf-interface-protection
Namespace: urn:ietf:params:xml:ns:yang:ietf-interface-protection Namespace: urn:ietf:params:xml:ns:yang:ietf-interface-protection
Prefix: ifprot Prefix: ifprot
Reference: RFC XXXX Reference: RFC XXXX
8. References 9. References
8.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC7223bis] [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
Bjorklund, M., "A YANG Data Model for Interface 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
Management", draft-bjorklund-netmod-rfc7223bis-00 May 2017, <https://www.rfc-editor.org/info/rfc8174>.
(work in progress), September 2017.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>.
[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", System performance monitoring parameters of SDH DRRS",
EN 301 129 V1.1.2, May 1995. EN 301 129 V1.1.2, May 1995.
[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-
skipping to change at page 40, line 30 skipping to change at page 42, line 5
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
Bierman, "Network Configuration Protocol (NETCONF)", Bierman, "Network Configuration Protocol (NETCONF)",
RFC 6241, June 2011. RFC 6241, June 2011.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, June 2011. Shell (SSH)", RFC 6242, June 2011.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
March 2012.
[RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991,
July 2013. July 2013.
[RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module",
RFC 7224, May 2014. RFC 7224, May 2014.
[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,
<http://www.rfc-editor.org/info/rfc8040>. <http://www.rfc-editor.org/info/rfc8040>.
8.2. Informative References [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, <https://www.rfc-
editor.org/info/rfc8341>.
[NMDA] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 9.2. Informative References
and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-10 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
(work in progress), January 2018. and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
[I-D.ahlberg-ccamp-microwave-radio-link] [I-D.ahlberg-ccamp-microwave-radio-link]
Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M., Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M.,
and M. Vaupotic, "Microwave Radio Link YANG Data Models", and M. Vaupotic, "Microwave Radio Link YANG Data Models",
draft-ahlberg-ccamp-microwave-radio-link-01 (work in draft-ahlberg-ccamp-microwave-radio-link-01 (work in
progress), May 2016. progress), May 2016.
[I-D.ietf-ccamp-microwave-framework] [I-D.ietf-ccamp-microwave-framework]
Ahlberg, J., Contreras, L., Ye, M., Vaupotic, M., Ahlberg, J., Contreras, L., Ye, M., Vaupotic, M.,
Tantsura, J., Kawada, K., Li, X., Akiyoshi, I., C. Tantsura, J., Kawada, K., Li, X., Akiyoshi, I., C.
skipping to change at page 41, line 25 skipping to change at page 42, line 53
[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,
<http://www.rfc-editor.org/info/rfc6241>. <http://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,
<http://www.rfc-editor.org/info/rfc6242>. <http://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
Protocol (NETCONF) Access Control Model", RFC 6536, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
DOI 10.17487/RFC6536, March 2012, <https://www.rfc-editor.org/info/rfc8340>.
<http://www.rfc-editor.org/info/rfc6536>.
[YANG-TREE] Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-06 (work in progress),
February 2018.
Appendix A. Example: 1+0 and 2+0 configuration instances Appendix A. Example: 1+0 and 2+0 configuration instances
This section gives simple examples of 1+0 and 2+0 instance using the This section gives simple examples of 1+0 and 2+0 instance using the
YANG module defined in this draft. The examples are not intended as YANG module defined in this draft. The examples are not intended as
a complete module for 1+0 and 2+0 configuration. a complete module for 1+0 and 2+0 configuration.
A.1 1+0 instance A.1 1+0 instance
Figure A-1 shows a 1+0 example. Figure A-1 shows a 1+0 example.
 End of changes. 63 change blocks. 
382 lines changed or deleted 446 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/