References from draft-ietf-teas-te-service-mapping-yang

These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Reference type help

Document Title Status Type Downref
BCP 14 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
BCP 206 Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
References Referenced by
Best Current Practice normatively references
BCP 215 YANG Tree Diagrams
References Referenced by
Best Current Practice normatively references
draft-ietf-ccamp-l1csm-yang A YANG Data Model for L1 Connectivity Service Model (L1CSM)
References Referenced by
normatively references
draft-ietf-opsawg-l2nm A Layer 2 VPN Network YANG Model
References Referenced by
normatively references
draft-ietf-opsawg-l3sm-l3nm A Layer 3 VPN Network YANG Model
References Referenced by
normatively references
draft-ietf-teas-actn-vn-yang A YANG Data Model for VN Operation
References Referenced by
normatively references
draft-ietf-teas-actn-yang Applicability of YANG models for Abstraction and Control of Traffic Engineered Networks
References Referenced by
informatively references
draft-ietf-teas-yang-te A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths and Interfaces
References Referenced by
normatively references
draft-ietf-teas-yang-te-topo YANG Data Model for Traffic Engineering (TE) Topologies
References Referenced by
Proposed Standard normatively references
draft-raza-spring-sr-policy-yang YANG Data Model for Segment Routing Policy
References Referenced by
normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 3688 The IETF XML Registry
References Referenced by
Best Current Practice normatively references
RFC 6020 YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
References Referenced by
Proposed Standard normatively references
RFC 6241 Network Configuration Protocol (NETCONF)
References Referenced by
Proposed Standard informatively references
RFC 6242 Using the NETCONF Protocol over Secure Shell (SSH)
References Referenced by
Proposed Standard normatively references
RFC 6991 Common YANG Data Types
References Referenced by
Proposed Standard normatively references
RFC 7926 Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
References Referenced by
Best Current Practice normatively references
RFC 7950 The YANG 1.1 Data Modeling Language
References Referenced by
Proposed Standard normatively references
RFC 8040 RESTCONF Protocol
References Referenced by
Proposed Standard normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8199 YANG Module Classification
References Referenced by
Informational informatively references
RFC 8299 YANG Data Model for L3VPN Service Delivery
References Referenced by
Proposed Standard normatively references
RFC 8309 Service Models Explained
References Referenced by
Informational informatively references
RFC 8340 YANG Tree Diagrams
References Referenced by
Best Current Practice normatively references
RFC 8341 Network Configuration Access Control Model
References Referenced by
Internet Standard normatively references
RFC 8342 Network Management Datastore Architecture (NMDA)
References Referenced by
Proposed Standard normatively references
RFC 8345 A YANG Data Model for Network Topologies
References Referenced by
Proposed Standard normatively references
RFC 8349 A YANG Data Model for Routing Management (NMDA Version)
References Referenced by
Proposed Standard normatively references
RFC 8446 The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by
Proposed Standard normatively references
RFC 8453 Framework for Abstraction and Control of TE Networks (ACTN)
References Referenced by
Informational informatively references
RFC 8466 A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery
References Referenced by
Proposed Standard normatively references
RFC 8776 Common YANG Data Types for Traffic Engineering
References Referenced by
Proposed Standard normatively references
STD 91 Network Configuration Access Control Model
References Referenced by
Internet Standard normatively references