draft-ietf-ccamp-mw-yang-03.txt   draft-ietf-ccamp-mw-yang-04.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: August 30, 2018 Huawei Technologies Expires: September 4, 2018 Huawei Technologies
X. Li X. Li
NEC Laboratories Europe NEC Laboratories Europe GmbH
D. Spreafico D. Spreafico
Nokia - IT Nokia - IT
M. Vaupotic M. Vaupotic
Aviat Networks Aviat Networks
February 26, 2018 March 3, 2018
A YANG Data Model for Microwave Radio Link A YANG Data Model for Microwave Radio Link
draft-ietf-ccamp-mw-yang-03 draft-ietf-ccamp-mw-yang-04
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 August 30, 2018. This Internet-Draft will expire on September 4, 2018.
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 31 skipping to change at page 2, line 31
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 . . . . . . . . . . . . . . 30
6. Security Considerations . . . . . . . . . . . . . . . . . . . 36 6. Security Considerations . . . . . . . . . . . . . . . . . . . 37
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 38 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.1. Normative References . . . . . . . . . . . . . . . . . . 38 8.1. Normative References . . . . . . . . . . . . . . . . . . 39
8.2. Informative References . . . . . . . . . . . . . . . . . 39 8.2. Informative References . . . . . . . . . . . . . . . . . 40
Appendix A. Example: 1+0 and 2+0 configuration instances. . . . . 40 Appendix A. Example: 1+0 and 2+0 configuration instances. . . . . 42
Appendix B. Contributors. . . . . . . . . . . . . . . . . . . . . 43 Appendix B. Contributors. . . . . . . . . . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
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
skipping to change at page 6, line 33 skipping to change at page 6, line 33
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
<CODE BEGINS> file "ietf-microwave-radio-link@2018-02-26.yang" This module imports typedefs and modules from [RFC6991],
[RFC7223bis] and [RFC7224], and it references [TR102311],
[EN302217-1], [EN301129], and [G.826].
<CODE BEGINS> file "ietf-microwave-radio-link@2018-03-03.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";
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference "RFC7223bis"; reference "RFC 7223bis";
// 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";
// RFC Ed.: replace XXXX with actual RFC number and remove
// this note
} }
import iana-if-type { import iana-if-type {
prefix ianaift; prefix ianaift;
reference "RFC 7224";
} }
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 authors: 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);
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.
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.
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."; authors of the code. All rights reserved.";
revision 2018-02-26 { revision 2018-03-03 {
description "Update with respect to the YANG Guideline"; 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 30, line 12 skipping to change at page 30, line 43
<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.
<CODE BEGINS> file "ietf-interface-protection@2018-02-26.yang" This module imports modules from [RFC7223bis], and it references
[G.808.1].
<CODE BEGINS> file "ietf-interface-protection@2018-03-03.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 "RFC7223bis";
// 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 authors: 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);
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 interface protection mechanism. a generic interface protection mechanism.
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 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-02-26 { revision 2018-03-03 {
description "Update with respect to the YANG Guideline"; 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 Rec. G.808.1"; reference "ITU-T G.808.1";
} }
identity one-plus-one-type { identity one-plus-one-type {
base protection-architecture-type; base protection-architecture-type;
description description
"1+1, One interface protects "1+1, One interface protects
another one interface."; another one interface.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
identity one-to-n-type { identity one-to-n-type {
base protection-architecture-type; base protection-architecture-type;
description description
"1:N, One interface protects "1:N, One interface protects
n other interfaces."; n other interfaces.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
/* /*
* Protection states identities * Protection states identities
*/ */
identity protection-states { identity protection-states {
description description
"Identities describing the status of the protection, "Identities describing the status of the protection,
in a group of interfaces configured in in a group of interfaces configured in
skipping to change at page 31, line 54 skipping to change at page 33, line 9
} }
/* /*
* protection-external-commands identities * protection-external-commands identities
*/ */
identity protection-external-commands{ identity protection-external-commands{
description description
"Protection external commands for trouble shooting "Protection external commands for trouble shooting
purpose."; purpose.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
identity manual-switch-working{ identity manual-switch-working{
base protection-external-commands; base protection-external-commands;
description description
"A switch action initiated by an operator command. "A switch action initiated by an operator command.
It switches normal traffic signal to the working It switches normal traffic signal to the working
transport entity."; transport entity.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
identity manual-switch-protection{ identity manual-switch-protection{
base protection-external-commands; base protection-external-commands;
description description
"A switch action initiated by an operator command. "A switch action initiated by an operator command.
It switches normal traffic signal to the protection It switches normal traffic signal to the protection
transport entity."; transport entity.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
identity forced-switch{ identity forced-switch{
base protection-external-commands; base protection-external-commands;
description description
"A switch action initiated by an operator command. "A switch action initiated by an operator command.
It switches normal traffic signal to the protection It switches normal traffic signal to the protection
transport entity and forces it to remain on that transport entity and forces it to remain on that
entity even when criteria for switching back to entity even when criteria for switching back to
the original entity are fulfilled."; the original entity are fulfilled.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
identity lockout-of-protection{ identity lockout-of-protection{
base protection-external-commands; base protection-external-commands;
description description
"A switch action temporarily disables access to the "A switch action temporarily disables access to the
protection transport entity for all signals."; protection transport entity for all signals.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
identity freeze{ identity freeze{
base protection-external-commands; base protection-external-commands;
description description
"A switch action temporarily prevents any switch action "A switch action temporarily prevents any switch action
to be taken and, as such, freezes the current state. to be taken and, as such, freezes the current state.
Until the freeze is cleared, additional near-end external Until the freeze is cleared, additional near-end external
commands are rejected and fault condition changes and commands are rejected and fault condition changes and
received APS messages are ignored.."; received APS messages are ignored..";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
identity exercise{ identity exercise{
base protection-external-commands; base protection-external-commands;
description description
"A switch action to test if the APS communication is "A switch action to test if the APS communication is
operating correctly. It is lower priority than any 'real' operating correctly. It is lower priority than any 'real'
switch request.."; switch request..";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
identity clear{ identity clear{
base protection-external-commands; base protection-external-commands;
description description
"An action clears all switch commands."; "An action clears all switch commands.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
/* /*
* Protection Groups * Protection Groups
*/ */
grouping protection-groups { grouping protection-groups {
description description
"Configuration of protected groups (1+1) of interfaces "Configuration of protected groups (1+1) of interfaces
providing protection for each other. More than one protected providing protection for each other. More than one protected
skipping to change at page 33, line 41 skipping to change at page 35, line 4
key "name"; key "name";
description description
"List of protected groups of interfaces "List of protected groups of interfaces
in a higher-layer-interface."; in a higher-layer-interface.";
leaf name { leaf name {
type string; type string;
description description
"Name used for identification of the protection group"; "Name used for identification of the protection group";
} }
leaf protection-architecture-type { leaf protection-architecture-type {
type identityref{ type identityref{
base protection-architecture-type; base protection-architecture-type;
} }
default "ifprot:one-plus-one-type"; default "ifprot:one-plus-one-type";
description description
"The type of protection architecture used, e.g. one "The type of protection architecture used, e.g. one
interface protecting one or several other interfaces."; interface protecting one or several other interfaces.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
leaf-list members { leaf-list members {
type if:interface-ref; type if:interface-ref;
min-elements 2; min-elements 2;
description description
"Association to a group of interfaces configured for "Association to a group of interfaces configured for
protection and used by a higher-layer-interface."; protection and used by a higher-layer-interface.";
} }
leaf operation-type { leaf operation-type {
type enumeration { type enumeration {
skipping to change at page 34, line 19 skipping to change at page 35, line 30
protection and used by a higher-layer-interface."; protection and used by a higher-layer-interface.";
} }
leaf operation-type { leaf operation-type {
type enumeration { type enumeration {
enum "non-revertive" { enum "non-revertive" {
description description
"In non revertive operation, the traffic does not "In non revertive operation, the traffic does not
return to the working interface if the switch requests return to the working interface if the switch requests
are terminated."; are terminated.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
enum "revertive" { enum "revertive" {
description description
"In revertive operation, the traffic always "In revertive operation, the traffic always
returns to (or remains on) the working interface returns to (or remains on) the working interface
if the switch requests are terminated."; if the switch requests are terminated.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
} }
default "non-revertive"; default "non-revertive";
description description
"The type of protection operation, i.e. revertive "The type of protection operation, i.e. revertive
or non-revertive operation."; or non-revertive operation.";
} }
leaf-list working-entity { leaf-list working-entity {
when "../operation-type = 'revertive'"; when "../operation-type = 'revertive'";
skipping to change at page 34, line 44 skipping to change at page 36, line 4
leaf-list working-entity { leaf-list working-entity {
when "../operation-type = 'revertive'"; when "../operation-type = 'revertive'";
type if:interface-ref; type if:interface-ref;
min-elements 1; min-elements 1;
description description
"The interfaces over which the traffic normally should "The interfaces over which the traffic normally should
be transported over when there is no need to use the be transported over when there is no need to use the
protecting interface."; protecting interface.";
} }
leaf revertive-wait-to-restore { leaf revertive-wait-to-restore {
when "../operation-type = 'revertive'"; when "../operation-type = 'revertive'";
type uint16; type uint16;
units "seconds"; units "seconds";
default "0"; default "0";
description description
"The time to wait before switching back to the working "The time to wait before switching back to the working
interface if operation-type is revertive."; interface if operation-type is revertive.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
leaf hold-off-timer { leaf hold-off-timer {
type uint16; type uint16;
units "milliseconds"; units "milliseconds";
default "0"; default "0";
description description
"Time interval after the detection of a fault and its "Time interval after the detection of a fault and its
confirmation as a condition requiring the protection confirmation as a condition requiring the protection
switching procedure."; switching procedure.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
leaf status { leaf status {
type identityref { type identityref {
base protection-states; base protection-states;
} }
description description
"Status of the protection, in a group of interfaces "Status of the protection, in a group of interfaces
configured in a protection mode."; configured in a protection mode.";
reference "ITU-T Rec. G.808.1"; reference "ITU-T G.808.1";
} }
action external-commands { action external-commands {
input { input {
leaf external-command { leaf external-command {
type identityref { type identityref {
base protection-external-commands; base protection-external-commands;
} }
description description
"Execution of protection external commands for "Execution of protection external commands for
skipping to change at page 37, line 53 skipping to change at page 38, line 53
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
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 8. References
8.1. Normative References 8.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] [RFC7223bis]
Bjorklund, M., "A YANG Data Model for Interface Bjorklund, M., "A YANG Data Model for Interface
Management", draft-bjorklund-netmod-rfc7223bis-00 Management", draft-bjorklund-netmod-rfc7223bis-00
(work in progress), September 2017. (work in progress), September 2017.
[EN301129] ETSI, "Transmission and Multiplexing (TM); Digital Radio
Relay Systems (DRRS); Synchronous Digital Hierarchy (SDH);
System performance monitoring parameters of SDH DRRS",
EN 301 129 V1.1.2, May 1995.
[EN302217-1]
ETSI, "Fixed Radio Systems; Characteristics and
requirements for point-to-point equipment and antennas;
Part 1: Overview, common characteristics and system-
dependent requirements", EN 302 217-1 V3.0.5, June 2016.
[EN302217-2] [EN302217-2]
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 2: Digital systems operating in frequency bands from Part 2: Digital systems operating in frequency bands from
1 GHz to 86 GHz; Harmonised Standard covering the 1 GHz to 86 GHz; Harmonised Standard covering the
essential requirements of article 3.2 of Directive essential requirements of article 3.2 of Directive
2014/53/EU", EN 302 217-2 V3.1.1, May 2017. 2014/53/EU", EN 302 217-2 V3.1.1, May 2017.
[G.808.1] ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL
SYSTEMS AND NETWORKS; Digital networks ; General aspects
Generic protection switching ; Linear trail and subnetwork
protection", ITU-T Rec. G.808.1, May 2014.
[G.826] ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL
SYSTEMS AND NETWORKS; Digital networks ; Quality and
availability targets End-to-end error performance
parameters and objectives for international, constant
bit-rate digital paths and connections", ITU-T Rec. G.826,
December 2002.
[TR102311] ETSI, "Fixed Radio Systems; Point-to-point equipment;
Specific aspects of the spatial frequency reuse method",
ETSI TR 102 311 V1.2.1, November 2015.
[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, <https://www.rfc- DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>. <https://www.rfc-editor.org/info/rfc5246>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
skipping to change at page 39, line 5 skipping to change at page 40, line 34
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 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
March 2012. March 2012.
[RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991,
July 2013.
[RFC7224] Bjorklund, M., "IANA Interface Type YANG Module",
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 8.2. Informative References
[NMDA] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [NMDA] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-10 Architecture", draft-ietf-netmod-revised-datastores-10
(work in progress), January 2018. (work in progress), January 2018.
skipping to change at page 43, line 42 skipping to change at page 45, line 42
Ye Min Ye Min
Huawei Technologies Huawei Technologies
No.1899, Xiyuan Avenue No.1899, Xiyuan Avenue
Chengdu 611731 Chengdu 611731
P.R.China (CHN) P.R.China (CHN)
Email: amy.yemin@huawei.com Email: amy.yemin@huawei.com
Xi Li Xi Li
NEC Laboratories Europe NEC Laboratories Europe GmbH
Kurfursten-Anlage 36 Kurfursten-Anlage 36
Heidelberg 69115 69115 Heidelberg
Germany (DEU) Germany (DEU)
Email: Xi.Li@neclab.eu Email: Xi.Li@neclab.eu
Daniela Spreafico Daniela Spreafico
Nokia - IT Nokia - IT
Via Energy Park, 14 Via Energy Park, 14
Vimercate (MI) 20871 Vimercate (MI) 20871
Italy (ITA) Italy (ITA)
Email: daniela.spreafico@nokia.com Email: daniela.spreafico@nokia.com
 End of changes. 57 change blocks. 
50 lines changed or deleted 129 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/