draft-ietf-ccamp-mw-yang-08.txt   draft-ietf-ccamp-mw-yang-09.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: February 9, 2019 Huawei Technologies Expires: March 4, 2019 Huawei Technologies
X. Li X. Li
NEC Laboratories Europe NEC Laboratories Europe
D. Spreafico D. Spreafico
Nokia - IT Nokia - IT
M. Vaupotic M. Vaupotic
Aviat Networks Aviat Networks
August 8, 2018 August 31, 2018
A YANG Data Model for Microwave Radio Link A YANG Data Model for Microwave Radio Link
draft-ietf-ccamp-mw-yang-08 draft-ietf-ccamp-mw-yang-09
Abstract Abstract
This document defines a YANG data model for control and management of This document defines a YANG data model for control and management of
the radio link interfaces, and their connectivity to packet 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 47 skipping to change at page 1, line 47
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 February 9, 2019. This Internet-Draft will expire on March 4, 2019.
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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 36 skipping to change at page 2, line 36
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 . . . . . . . . . 7 3.2. Explanation of the Microwave Data Model . . . . . . . . . 7
4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 7 4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 7
5. Interface Protection YANG Module . . . . . . . . . . . . . . 26 5. Interface Protection YANG Module . . . . . . . . . . . . . . 26
6. Microwave Types YANG Module . . . . . . . . . . . . . . . . . 32 6. Microwave Types YANG Module . . . . . . . . . . . . . . . . . 32
7. Security Considerations . . . . . . . . . . . . . . . . . . . 39 7. Security Considerations . . . . . . . . . . . . . . . . . . . 39
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 42
9.1. Normative References . . . . . . . . . . . . . . . . . . 42 9.1. Normative References . . . . . . . . . . . . . . . . . . 42
9.2. Informative References . . . . . . . . . . . . . . . . . 44 9.2. Informative References . . . . . . . . . . . . . . . . . 43
Appendix A. Example: 1+0 and 2+0 configuration instances . . . . 45 Appendix A. Example: 1+0 and 2+0 configuration instances . . . . 45
A.1. 1+0 instance . . . . . . . . . . . . . . . . . . . . . . 45
A.2. 2+0 instance . . . . . . . . . . . . . . . . . . . . . . 46
A.3. 2+0 XPIC instance . . . . . . . . . . . . . . . . . . . . 48
Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 50 Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 50
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50
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
skipping to change at page 39, line 41 skipping to change at page 39, line 41
<CODE ENDS> <CODE ENDS>
7. Security Considerations 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]. [RFC8446].
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.
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)
skipping to change at page 43, line 5 skipping to change at page 43, line 5
[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,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[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/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<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
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/info/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/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
skipping to change at page 44, line 5 skipping to change at page 43, line 44
[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/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>. <https://www.rfc-editor.org/info/rfc8343>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
9.2. Informative References 9.2. Informative References
[EN301129] [EN301129]
"Transmission and Multiplexing (TM); Digital Radio Relay "Transmission and Multiplexing (TM); Digital Radio Relay
Systems (DRRS); Synchronous Digital Hierarchy (SDH); 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 1995. 301 129 V1.1.2 , May 1995.
[EN302217-1] [EN302217-1]
"Fixed Radio Systems; Characteristics and requirements for "Fixed Radio Systems; Characteristics and requirements for
skipping to change at page 45, line 32 skipping to change at page 45, line 32
"Fixed Radio Systems; Point-to-point equipment; Specific "Fixed Radio Systems; Point-to-point equipment; Specific
aspects of the spatial frequency reuse method", ETSI TR aspects of the spatial frequency reuse method", ETSI TR
102 311 V1.2.1 , November 2015. 102 311 V1.2.1 , November 2015.
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.
/--------- Radio Link ---------\ /--------- Radio Link ---------\
Near End Far End Near End Far End
+---------------+ +---------------+ +---------------+ +---------------+
| Radio Link | | Radio Link | | Radio Link | | Radio Link |
| Terminal - A | | Terminal - B | | Terminal - A | | Terminal - B |
| | | | | | | |
| | | | | | | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | Carrier A | | | | | | | | Carrier A | | | |
| | Carrier | |<--------->| | Carrier | | | | Carrier | |<--------->| | Carrier | |
| |Termination| | | |Termination| | | |Termination| | | |Termination| |
| | -1 | | | | -1 | | | | -1 | | | | -1 | |
skipping to change at page 46, line 5 skipping to change at page 45, line 50
| | | | | | | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | Carrier A | | | | | | | | Carrier A | | | |
| | Carrier | |<--------->| | Carrier | | | | Carrier | |<--------->| | Carrier | |
| |Termination| | | |Termination| | | |Termination| | | |Termination| |
| | -1 | | | | -1 | | | | -1 | | | | -1 | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | | | | |
| | | | | | | |
+---------------+ +---------------+ +---------------+ +---------------+
\--- Microwave Node ---/ \--- Microwave Node ---/ \--- Microwave Node ---/ \--- Microwave Node ---/
Figure A-1 1+0 example Figure A-1 1+0 example
The following instance shows the 1+0 configuration of Figure A-1 shows a 1+0 example. The following instance shows the 1+0
Near End node. configuration of Near End node.
"interface": [ "interface": [
{ {
//RLT-A //RLT-A
"name": "RLT-A", "name": "RLT-A",
"description": "Radio Link Terminal A", "description": "Radio Link Terminal A",
"type": "mrl:radio-link-terminal", "type": "mrl:radio-link-terminal",
"id": "RLT-A", "id": "RLT-A",
"mode": "one-plus-zero", "mode": "one-plus-zero",
"carrier-terminations": [ "carrier-terminations": [
"RLT-A:CT-1", "RLT-A:CT-1",
], ],
skipping to change at page 46, line 49 skipping to change at page 46, line 45
"polarization": not-specified, "polarization": not-specified,
"rtpc": { "rtpc": {
"maximum-nominal-power": 20, "maximum-nominal-power": 20,
} }
"single":{ "single":{
"selected-cm": "qam-512", "selected-cm": "qam-512",
} }
}, },
] ]
A.2 2+0 instance A.2. 2+0 instance
Figure A-2 shows a 2+0 example.
Figure A-2 shows a 2+0 example.
/--------- Radio Link ---------\ /--------- Radio Link ---------\
Near End Far End Near End Far End
+---------------+ +---------------+ +---------------+ +---------------+
| Radio Link | | Radio Link | | Radio Link | | Radio Link |
| Terminal -A | | Terminal -B | | Terminal -A | | Terminal -B |
| | | | | | | |
| | | | | | | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
skipping to change at page 47, line 33 skipping to change at page 47, line 32
| | Carrier | |<--------->| | Carrier | | | | Carrier | |<--------->| | Carrier | |
| |Termination| | | |Termination| | | |Termination| | | |Termination| |
| | -2 | | | | -2 | | | | -2 | | | | -2 | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | | | | |
+---------------+ +---------------+ +---------------+ +---------------+
\--- Microwave Node ---/ \--- Microwave Node ---/ \--- Microwave Node ---/ \--- Microwave Node ---/
Figure A-2 2+0 example Figure A-2 2+0 example
The following instance shows the 2+0 configuration of The following instance shows the 2+0 configuration of Near End node.
Near End node.
"interface": [ "interface": [
{ {
//RLT-A //RLT-A
"name": "RLT-A", "name": "RLT-A",
"description": "Radio Link Terminal A", "description": "Radio Link Terminal A",
"type": "mrl:radio-link-terminal", "type": "mrl:radio-link-terminal",
"id": "RLT-A", "id": "RLT-A",
"mode": "two-plus-zero", "mode": "two-plus-zero",
"carrier-terminations": [ "carrier-terminations": [
skipping to change at page 48, line 48 skipping to change at page 48, line 43
"polarization": not-specified, "polarization": not-specified,
"rtpc": { "rtpc": {
"maximum-nominal-power": 20, "maximum-nominal-power": 20,
} }
"single":{ "single":{
"selected-cm": "qam-512", "selected-cm": "qam-512",
} }
}, },
] ]
A.3 2+0 XPIC instance A.3. 2+0 XPIC instance
The following instance shows the XPIC configuration of The following instance shows the XPIC configuration of Near End node.
Near End node.
"interface": [ "interface": [
{ {
//RLT-A //RLT-A
"name": "RLT-A", "name": "RLT-A",
"description": "Radio Link Terminal A", "description": "Radio Link Terminal A",
"type": "mrl:radio-link-terminal", "type": "mrl:radio-link-terminal",
"id": "RLT-A", "id": "RLT-A",
"mode": "two-plus-zero", "mode": "two-plus-zero",
"carrier-terminations": [ "carrier-terminations": [
 End of changes. 18 change blocks. 
26 lines changed or deleted 23 lines changed or added

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