RFC 8776: Common YANG Data Types for Traffic Engineering
In plain English — editorial summary, not part of the RFC
This document defines a collection of common data types and groupings in YANG data modeling language. These derived common types and groupings are intended to be imported by modules that model Traffic Engineering (TE) configuration and state capabilities.
Document record
- Document ID
- RFC8776
- Published
- June 2020
- Authors
- T. Saad; R. Gandhi; X. Liu; V. Beeram; I. Bryskin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 84
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8795YANG Data Model for Traffic Engineering (TE) TopologiesCurrent
August 2020
- RFC 8775PIM Designated Router Load BalancingCurrent
April 2020
- RFC 8779Path Computation Element Communication Protocol (PCEP) Extensions for GMPLSUpdated
July 2020
- RFC 8780The Path Computation Element Communication Protocol (PCEP) Extension for Wavelength Switched Optical Network (WSON) Routing and Wavelength Assignment (RWA)Updated
July 2020
- RFC 8770Host Router Support for OSPFv2Current
April 2020
- RFC 8786Updated Rules for Processing Stateful PCE Request Parameters FlagsCurrent
May 2020
- RFC 8757Dynamic Link Exchange Protocol (DLEP) Latency Range ExtensionCurrent
March 2020
- RFC 8796RSVP-TE Summary Fast Reroute Extensions for Label Switched Path (LSP) TunnelsCurrent
July 2020
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?