RFC 8795: YANG Data Model for Traffic Engineering (TE) Topologies

This document defines a YANG data model for representing, retrieving, and manipulating Traffic Engineering (TE) Topologies. The model serves as a base model…

Read RFC 8795 on the RFC Editor

Outgoing relationships (41 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3
Normative reference — RFC 3688: The IETF XML Registry
Normative reference — RFC 6241: Network Configuration Protocol (NETCONF)
Normative reference — RFC 6020: YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
Normative reference — RFC 7950: The YANG 1.1 Data Modeling Language
Normative reference — RFC 8040: RESTCONF Protocol
Normative reference — RFC 8341: Network Configuration Access Control Model
Normative reference — RFC 6991: Common YANG Data Types
Normative reference — RFC 6242: Using the NETCONF Protocol over Secure Shell (SSH)
Normative reference — RFC 8342: Network Management Datastore Architecture (NMDA)
Normative reference — RFC 3945: Generalized Multi-Protocol Label Switching (GMPLS) Architecture
Normative reference — RFC 8345: A YANG Data Model for Network Topologies
Normative reference — RFC 7926: Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
Normative reference — RFC 8776: Common YANG Data Types for Traffic Engineering
Informative reference — RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
Informative reference — RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description
Informative reference — RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2
Informative reference — RFC 8340: YANG Tree Diagrams
Informative reference — RFC 1195: Use of OSI IS-IS for routing in TCP/IP and dual environments
Informative reference — RFC 5305: IS-IS Extensions for Traffic Engineering
Informative reference — RFC 4203: OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Informative reference — RFC 4202: Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Informative reference — RFC 4206: Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)
Informative reference — RFC 2702: Requirements for Traffic Engineering Over MPLS
Informative reference — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Informative reference — RFC 4872: RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery
Informative reference — RFC 4201: Link Bundling in MPLS Traffic Engineering (TE)
Informative reference — RFC 5152: A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)
Informative reference — RFC 7471: OSPF Traffic Engineering (TE) Metric Extensions
Informative reference — RFC 5212: Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)
Informative reference — RFC 5316: ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Informative reference — RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)
Informative reference — RFC 8641: Subscription to YANG Notifications for Datastore Updates
Informative reference — RFC 3272: Overview and Principles of Internet Traffic Engineering
Informative reference — RFC 7308: Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)
Informative reference — RFC 5392: OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Informative reference — RFC 8639: Subscription to YANG Notifications
Informative reference — RFC 7579: General Network Element Constraint Encoding for GMPLS-Controlled Networks
Informative reference — RFC 3785: Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric

Incoming relationships (5 related RFCs)

Normatively referenced by — RFC 9093: A YANG Data Model for Layer 0 Types
Normatively referenced by — RFC 9094: A YANG Data Model for Wavelength Switched Optical Networks (WSONs)
Normatively referenced by — RFC 9656: A YANG Data Model for Microwave Topology
Informatively referenced by — RFC 8969: A Framework for Automating Service and Network Management with YANG
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering