References from draft-ietf-teas-yang-rsvp-te

This is an experimental product. 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
Refs Ref'd by
Best Current Practice normatively references
BCP 215 YANG Tree Diagrams
Refs Ref'd by
Best Current Practice normatively references
draft-ietf-teas-yang-rsvp A YANG Data Model for Resource Reservation Protocol (RSVP)
Refs Ref'd by
normatively references
draft-ietf-teas-yang-te A YANG Data Model for Traffic Engineering Tunnels and Interfaces
Refs Ref'd by
normatively references
draft-ietf-teas-yang-te-types Traffic Engineering Common YANG Types
Refs Ref'd by
Proposed Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 2205 Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
Refs Ref'd by
Proposed Standard normatively references
RFC 2210 The Use of RSVP with IETF Integrated Services
Refs Ref'd by
Proposed Standard informatively references
RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels
Refs Ref'd by
Proposed Standard informatively references
RFC 3688 The IETF XML Registry
Refs Ref'd by
Best Current Practice normatively references
RFC 4859 Codepoint Registry for the Flags Field in the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Session Attribute Object
Refs Ref'd by
Informational informatively references
RFC 4920 Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE
Refs Ref'd by
Proposed Standard informatively references
RFC 5420 Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)
Refs Ref'd by
Proposed Standard informatively references
RFC 6020 YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
Refs Ref'd by
Proposed Standard normatively references
RFC 6241 Network Configuration Protocol (NETCONF)
Refs Ref'd by
Proposed Standard normatively references
RFC 6242 Using the NETCONF Protocol over Secure Shell (SSH)
Refs Ref'd by
Proposed Standard normatively references
RFC 6991 Common YANG Data Types
Refs Ref'd by
Proposed Standard normatively references
RFC 7570 Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)
Refs Ref'd by
Proposed Standard informatively references
RFC 7950 The YANG 1.1 Data Modeling Language
Refs Ref'd by
Proposed Standard normatively references
RFC 8040 RESTCONF Protocol
Refs Ref'd by
Proposed Standard normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Refs Ref'd by
Best Current Practice normatively references
RFC 8294 Common YANG Data Types for the Routing Area
Refs Ref'd by
Proposed Standard normatively references
RFC 8340 YANG Tree Diagrams
Refs Ref'd by
Best Current Practice normatively references
RFC 8341 Network Configuration Access Control Model
Refs Ref'd by
Internet Standard normatively references
RFC 8349 A YANG Data Model for Routing Management (NMDA Version)
Refs Ref'd by
Proposed Standard normatively references
STD 91 Network Configuration Access Control Model
Refs Ref'd by
Internet Standard normatively references