RFC 8330: OSPF Traffic Engineering (OSPF-TE) Link Availability Extension for Links with Variable Discrete Bandwidth
In plain English — editorial summary, not part of the RFC
A network may contain links with variable discrete bandwidth, e.g., microwave and copper. The bandwidth of such links may change discretely in response to a changing external environment. The word "availability" is typically used to describe such links during network planning. This document defines a new type of Generalized Switching Capability-Specific Information (SCSI) TLV to extend the Generalized Multiprotocol Label Switching (GMPLS) Open Shortest Path First (OSPF) routing protocol. The extension can be used for route computation in a network that contains links with variable discrete bandwidth. Note that this document only covers the mechanisms by which the availability information is distributed. The mechanisms by which availability information of a link is determined and the use of the distributed information for route computation are outside the scope of this document. It is intended that technology-specific documents will reference this document to describe specific uses.
Document record
- Document ID
- RFC8330
- Published
- February 2018
- Authors
- H. Long; M. Ye; G. Mirsky; A. D'Alessandro; H. Shah
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8432A Framework for Management and Control of Microwave and Millimeter Wave Interface ParametersCurrent
October 2018
- RFC 8625Ethernet Traffic Parameters with Availability InformationCurrent
August 2019
- RFC 9656A YANG Data Model for Microwave TopologyCurrent
September 2024
- RFC 8333Micro-loop Prevention by Introducing a Local Convergence DelayCurrent
March 2018
- RFC 8338Signaling Root-Initiated Point-to-Multipoint Pseudowire Using LDPCurrent
March 2018
- RFC 8339Definition of P2MP PW TLV for Label Switched Path (LSP) Ping MechanismsCurrent
March 2018
- RFC 8320LDP Extensions to Support Maximally Redundant TreesCurrent
February 2018
- RFC 8317Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)Current
January 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?