RFC 8625: Ethernet Traffic Parameters with Availability Information
In plain English — editorial summary, not part of the RFC
A packet-switching network may contain links with variable bandwidths (e.g., copper and radio). The bandwidth of such links is sensitive to the external environment (e.g., climate). Availability is typically used to describe these links when doing network planning. This document introduces an optional Bandwidth Availability TLV in RSVP-TE signaling. This extension can be used to set up a GMPLS Label Switched Path (LSP) in conjunction with the Ethernet SENDER_TSPEC object.
Document record
- Document ID
- RFC8625
- Published
- August 2019
- Authors
- H. Long; M. Ye; G. Mirsky; A. D'Alessandro; H. Shah
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8779Path Computation Element Communication Protocol (PCEP) Extensions for GMPLSUpdated
July 2020
- RFC 7699Generalized Labels for the Flexi-Grid in Lambda Switch Capable (LSC) Label Switching RoutersCurrent
November 2015
- RFC 7570Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)Current
July 2015
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
- RFC 4558Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification StatementCurrent
June 2006
- RFC 3473Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) ExtensionsUpdated
February 2003
- RFC 6383Advice on When It Is Safe to Start Sending Data on Label Switched Paths Established Using RSVP-TECurrent
September 2011
- RFC 8432A Framework for Management and Control of Microwave and Millimeter Wave Interface ParametersCurrent
October 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?