Skip to main content

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

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
References Referenced by
normatively references
BCP 215
References Referenced by
normatively references
draft-ietf-teas-yang-rsvp A YANG Data Model for Resource Reservation Protocol (RSVP)
References Referenced by
normatively 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-types Common YANG Data Types for Traffic Engineering
References Referenced by
Proposed Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2205 Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
References Referenced by
Proposed Standard normatively references
RFC 2210 The Use of RSVP with IETF Integrated Services
References Referenced by
Proposed Standard informatively references
RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels
References Referenced by
Proposed Standard informatively references
RFC 3688 The IETF XML Registry
References Referenced 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
References Referenced by
Informational informatively references
RFC 4920 Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE
References Referenced by
Proposed Standard informatively references
RFC 5420 Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)
References Referenced by
Proposed Standard informatively 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 normatively 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 7570 Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)
References Referenced by
Proposed Standard informatively 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 8294 Common YANG Data Types for the Routing Area
References Referenced by
Proposed Standard normatively 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 8349 A YANG Data Model for Routing Management (NMDA Version)
References Referenced by
Proposed Standard normatively references
STD 91
References Referenced by
normatively references