A YANG Data Model for Microwave Radio Link
draft-ietf-ccamp-mw-yang-11
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8561.
|
|
---|---|---|---|
Authors | Jonas Ahlberg , Min Ye , Xi Li , Daniela Spreafico , Marko Vaupotic | ||
Last updated | 2018-11-06 | ||
Replaces | draft-mwdt-ccamp-mw-yang | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
YANGDOCTORS Last Call review
(of
-05)
by Jan Lindblad
Ready w/issues
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Fatai Zhang | ||
Shepherd write-up | Show Last changed 2018-09-12 | ||
IESG | IESG state | Became RFC 8561 (Proposed Standard) | |
Consensus boilerplate | Yes | ||
Telechat date |
(None)
Needs a YES. Needs 10 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Deborah Brungard | ||
Send notices to | Fatai Zhang <zhangfatai@huawei.com> | ||
IANA | IANA review state | Version Changed - Review Needed |
draft-ietf-ccamp-mw-yang-11
gt; 7. Security Considerations The YANG modules specified in this document define schemas for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446]. The NETCONF access control model [RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. There are a number of data nodes defined in these YANG modules that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability: Ahlberg, et al. Expires May 10, 2019 [Page 40] Internet-Draft Microwave YANG Model November 2018 Interfaces of type radio-link-terminal: /if:interfaces/if:interface/mode, /if:interfaces/if:interface/carrier-terminations, /if:interfaces/if:interface/rlp-groups, /if:interfaces/if:interface/xpic-pairs, /if:interfaces/if:interface/mimo-groups, and /if:interfaces/if:interface/tdm-connections: These data nodes represent the configuration of the radio-link- terminal and they need to match the configuration of the radio-link- terminal on the other side of the radio link. Unauthorized access to these data nodes could interrupt the ability to forward traffic. Interfaces of type carrier-termination: /if:interfaces/if:interface/carrier-id, /if:interfaces/if:interface/tx-enabled, /if:interfaces/if:interface/tx-frequency, /if:interfaces/if:interface/rx-frequency, /if:interfaces/if:interface/duplex-distance, /if:interfaces/if:interface/channel-separation, /if:interfaces/if:interface/rtpc/maximum-nominal-power, /if:interfaces/if:interface/atpc/maximum-nominal-power, /if:interfaces/if:interface/atpc/atpc-lower-threshold, /if:interfaces/if:interface/atpc/atpc-upper-threshold, /if:interfaces/if:interface/single/selected-cm, /if:interfaces/if:interface/adaptive/selected-min-acm, /if:interfaces/if:interface/adaptive/selected-max-acm, /if:interfaces/if:interface/if-loop, and /if:interfaces/if:interface/rf-loop: These data nodes represent the configuration of the carrier- termination and they need to match the configuration of the carrier- termination on the other side of the carrier. Unauthorized access to these data nodes could interrupt the ability to forward traffic. Radio link protection: /radio-link-protection-groups/protection-group: Ahlberg, et al. Expires May 10, 2019 [Page 41] Internet-Draft Microwave YANG Model November 2018 This data node represents the configuration of the protection of carrier terminations. Unauthorized access to this data node could interrupt the ability to forward traffic or remove the ability to perform a necessary protection switch. XPIC: /xpic-pairs: This data node represents the XPIC configuration of a pair carriers. Unauthorized access to this data node could interrupt the ability to forward traffic. MIMO: /mimo-groups: This data node represents the MIMO configuration of multiple carriers. Unauthorized access to this data node could interrupt the ability to forward traffic. The security considerations of [RFC8343] also apply to this document. 8. IANA Considerations It is proposed that IANA should assign new URIs from the "IETF XML Registry" [RFC3688] as follows: URI: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link Registrant Contact: The IESG XML: N/A; the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-interface-protection Registrant Contact: The IESG XML: N/A; the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-microwave-types Registrant Contact: The IESG XML: N/A; the requested URI is an XML namespace. It is proposed that IANA should record YANG module names in the "YANG Module Names" registry [RFC6020] as follows: Ahlberg, et al. Expires May 10, 2019 [Page 42] Internet-Draft Microwave YANG Model November 2018 Name: ietf-microwave-radio-link Maintained by IANA?: N Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link Prefix: mrl Reference: RFC XXXX Name: ietf-interface-protection Maintained by IANA?: N Namespace: urn:ietf:params:xml:ns:yang:ietf-interface-protection Prefix: ifprot Reference: RFC XXXX Name: ietf-microwave-types Maintained by IANA?: N Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-types Prefix: mw-types Reference: RFC XXXX 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-editor.org/info/rfc3688>. [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-editor.org/info/rfc6020>. [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, <https://www.rfc-editor.org/info/rfc6241>. [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, <https://www.rfc-editor.org/info/rfc6242>. Ahlberg, et al. Expires May 10, 2019 [Page 43] Internet-Draft Microwave YANG Model November 2018 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, <https://www.rfc-editor.org/info/rfc6991>. [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", RFC 7224, DOI 10.17487/RFC7224, May 2014, <https://www.rfc-editor.org/info/rfc7224>. [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, <https://www.rfc-editor.org/info/rfc8040>. [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>. [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>. [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>. [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 [EN301129] "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] "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. Ahlberg, et al. Expires May 10, 2019 [Page 44] Internet-Draft Microwave YANG Model November 2018 [EN302217-2] "Fixed Radio Systems; Characteristics and requirements for point to-point equipment and antennas; Part 2: Digital systems operating in frequency bands from 1 GHz to 86 GHz; Harmonised Standard covering the essential requirements of article 3.2 of Directive 2014/53/EU", EN 302 217-2 V3.1.1 , May 2017. [G.808.1] "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] "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. [I-D.ahlberg-ccamp-microwave-radio-link] Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M., and M. Vaupotic, "Microwave Radio Link YANG Data Models", draft-ahlberg-ccamp-microwave-radio-link-01 (work in progress), May 2016. [ONF-model] "Microwave Information Model", version 1.0 , December 2016, <https://www.opennetworking.org/images/stories/downloads/ sdn-resources/technical-reports/ TR-532-Microwave-Information-Model-V1.pdf>. [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, <https://www.rfc-editor.org/info/rfc8340>. [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, <https://www.rfc-editor.org/info/rfc8342>. [RFC8432] Ahlberg, J., Ed., Ye, M., Ed., Li, X., Contreras, LM., and CJ. Bernardos, "A Framework for Management and Control of Microwave and Millimeter Wave Interface Parameters", RFC 8432, DOI 10.17487/RFC8432, October 2018, <https://www.rfc-editor.org/info/rfc8432>. Ahlberg, et al. Expires May 10, 2019 [Page 45] Internet-Draft Microwave YANG Model November 2018 [TR102311] "Fixed Radio Systems; Point-to-point equipment; Specific aspects of the spatial frequency reuse method", ETSI TR 102 311 V1.2.1 , November 2015. Appendix A. Example: 1+0 and 2+0 configuration instances 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 a complete module for 1+0 and 2+0 configuration. A.1. 1+0 instance /--------- Radio Link ---------\ Near End Far End +---------------+ +---------------+ | Radio Link | | Radio Link | | Terminal A | | Terminal B | | | | | | | | | | +-----------+ | | +-----------+ | | | | | Carrier A | | | | | | Carrier | |<--------->| | Carrier | | | |Termination| | | |Termination| | | | 1 | | | | 1 | | | +-----------+ | | +-----------+ | | | | | | | | | +---------------+ +---------------+ \--- Microwave Node ---/ \--- Microwave Node ---/ Figure A-1 1+0 example Figure A-1 shows a 1+0 example. The following instance shows the 1+0 configuration of Near End node. "interface": [ { "name": "RLT-A", "description": "Radio Link Terminal A", "type": "mrl:radio-link-terminal", "id": "RLT-A", "mode": "one-plus-zero", "carrier-terminations": [ "RLT-A:CT-1" ], Ahlberg, et al. Expires May 10, 2019 [Page 46] Internet-Draft Microwave YANG Model November 2018 "tdm-connections": [ "tdm-type": "E1", "tdm-connections": "4" ] }, { "name": "RLT-A:CT-1", "description": "Carrier Termination 1", "type": "mrl:carrier-termination", "carrier-id": "A", "tx-enabled": true, "tx-frequency": 10728000, "duplex-distance": 644000, "channel-separation": 28, "polarization": not-specified, "rtpc": { "maximum-nominal-power": 20 }, "single": { "selected-cm": "qam-512" } } ] A.2. 2+0 instance Figure A-2 shows a 2+0 example. /--------- Radio Link ---------\ Near End Far End +---------------+ +---------------+ | Radio Link | | Radio Link | | Terminal A | | Terminal B | | | | | | | | | | +-----------+ | | +-----------+ | | | | | Carrier A | | | | | | Carrier | |<--------->| | Carrier | | | |Termination| | | |Termination| | | | 1 | | | | 1 | | | +-----------+ | | +-----------+ | | | | | | +-----------+ | | +-----------+ | | | | | Carrier B | | | | Ahlberg, et al. Expires May 10, 2019 [Page 47] Internet-Draft Microwave YANG Model November 2018 | | Carrier | |<--------->| | Carrier | | | |Termination| | | |Termination| | | | 2 | | | | 2 | | | +-----------+ | | +-----------+ | | | | | +---------------+ +---------------+ \--- Microwave Node ---/ \--- Microwave Node ---/ Figure A-2 2+0 example The following instance shows the 2+0 configuration of Near End node. "interface": [ { "name": "RLT-A", "description": "Radio Link Terminal A", "type": "mrl:radio-link-terminal", "id": "RLT-A", "mode": "two-plus-zero", "carrier-terminations": [ "RLT-A:CT-1", "RLT-A:CT-2" ], "tdm-connections": [ "tdm-type": "E1", "tdm-connections": "4" ] }, { "name": "RLT-A:CT-1", "description": "Carrier Termination 1", "type": "mrl:carrier-termination", "carrier-id": "A", "tx-enabled": true, "tx-frequency": 10728000, "duplex-distance": 644000, "channel-separation": 28, "polarization": not-specified, "rtpc": { "maximum-nominal-power": 20 }, "single": { "selected-cm": "qam-512" } }, Ahlberg, et al. Expires May 10, 2019 [Page 48] Internet-Draft Microwave YANG Model November 2018 { "name": "RLT-A:CT-2", "description": "Carrier Termination 2", "type": "mrl:carrier-termination", "carrier-id": "B", "tx-enabled": true, "tx-oper-status": on, "tx-frequency": 10618000, "duplex-distance": 644000, "channel-separation": 28, "polarization": not-specified, "rtpc": { "maximum-nominal-power": 20 }, "single": { "selected-cm": "qam-512" } } ] A.3. 2+0 XPIC instance The following instance shows the XPIC configuration of Near End node. "interface": [ { "name": "RLT-A", "description": "Radio Link Terminal A", "type": "mrl:radio-link-terminal", "id": "RLT-A", "mode": "two-plus-zero", "carrier-terminations": [ "RLT-A:CT-1", "RLT-A:CT-2" ], "xpic-pairs": [ "RLT-A:CT-1", "RLT-A:CT-2" ], "tdm-connections": [ "tdm-type": "E1", "tdm-connections": "4" ] }, { Ahlberg, et al. Expires May 10, 2019 [Page 49] Internet-Draft Microwave YANG Model November 2018 "name": "RLT-A:CT-1", "description": "Carrier Termination 1", "type": "mrl:carrier-termination", "carrier-id": "A", "tx-enabled": true, "tx-frequency": 10728000, "duplex-distance": 644000, "channel-separation": 28, "polarization": not-specified, "rtpc": { "maximum-nominal-power": 20 }, "single": { "selected-cm": "qam-512" } }, { "name": "RLT-A:CT-2", "description": "Carrier Termination 2", "type": "mrl:carrier-termination", "carrier-id": "B", "tx-enabled": true, "tx-oper-status": on, "tx-frequency": 10618000, "duplex-distance": 644000, "channel-separation": 28, "polarization": not-specified, "rtpc": { "maximum-nominal-power": 20 }, "single": { "selected-cm": "qam-512" } } ] Appendix B. Contributors Ahlberg, et al. Expires May 10, 2019 [Page 50] Internet-Draft Microwave YANG Model November 2018 Koji Kawada NEC Corporation 1753, Shimonumabe Nakahara-ku Kawasaki, Kanagawa 211-8666 Japan Email: k-kawada@ah.jp.nec.com Carlos J. Bernardos Universidad Carlos III de Madrid Av. Universidad, 30 Leganes, Madrid 28911 Spain Email: cjbc@it.uc3m.es Authors' Addresses Jonas Ahlberg Ericsson AB Lindholmspiren 11 Goteborg 417 56 Sweden Email: jonas.ahlberg@ericsson.com Ye Min Huawei Technologies No.1899, Xiyuan Avenue Chengdu 611731 P.R.China Email: amy.yemin@huawei.com Xi Li NEC Laboratories Europe Kurfursten-Anlage 36 Heidelberg 69115 Germany Email: Xi.Li@neclab.eu Ahlberg, et al. Expires May 10, 2019 [Page 51] Internet-Draft Microwave YANG Model November 2018 Daniela Spreafico Nokia - IT Via Energy Park, 14 Vimercate (MI) 20871 Italy Email: daniela.spreafico@nokia.com Marko Vaupotic Aviat Networks Motnica 9 Trzin-Ljubljana 1236 Slovenia Email: Marko.Vaupotic@Aviatnet.com Ahlberg, et al. Expires May 10, 2019 [Page 52]