RFC 8432: A Framework for Management and Control of Microwave and Millimeter Wave Interface Parameters
In plain English — editorial summary, not part of the RFC
The unification of control and management of microwave radio link interfaces is a precondition for seamless multi-layer networking and automated network provisioning and operation. This document describes the required characteristics and use cases for control and management of radio link interface parameters using a YANG data model. The purpose is to create a framework to identify the necessary information elements and define a YANG data model for control and management of the radio link interfaces in a microwave node. Some parts of the resulting model may be generic and could also be used by other technologies, e.g., Ethernet technology.
Document record
- Document ID
- RFC8432
- Published
- October 2018
- Authors
- J. Ahlberg; M. Ye; X. Li; LM. Contreras; CJ. Bernardos
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8330OSPF Traffic Engineering (OSPF-TE) Link Availability Extension for Links with Variable Discrete BandwidthCurrent
February 2018
- RFC 8625Ethernet Traffic Parameters with Availability InformationCurrent
August 2019
- RFC 9656A YANG Data Model for Microwave TopologyCurrent
September 2024
- RFC 8431A YANG Data Model for the Routing Information Base (RIB)Current
September 2018
- RFC 8430RIB Information ModelCurrent
September 2018
- RFC 8426Recommendations for RSVP-TE and Segment Routing (SR) Label Switched Path (LSP) CoexistenceCurrent
July 2018
- RFC 8424Extensions to RSVP-TE for Label Switched Path (LSP) Ingress Fast Reroute (FRR) ProtectionCurrent
August 2018
- RFC 8444OSPFv2 Extensions for Bit Index Explicit Replication (BIER)Updated
November 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?