References from rfc6016

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
References Referenced by
Best Current Practice normatively references
RFC 1633 Integrated Services in the Internet Architecture: an Overview
References Referenced by
Informational informatively references
RFC 2113 IP Router Alert Option
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 2209 Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules
References Referenced by
Informational informatively references
RFC 2210 The Use of RSVP with IETF Integrated Services
References Referenced by
Proposed Standard informatively references
RFC 2711 IPv6 Router Alert Option
References Referenced by
Proposed Standard normatively references
RFC 2747 RSVP Cryptographic Authentication
References Referenced by
Proposed Standard informatively references
RFC 2748 The COPS (Common Open Policy Service) Protocol
References Referenced by
Proposed Standard informatively references
RFC 2749 COPS usage for RSVP
References Referenced by
Proposed Standard informatively references
RFC 2961 RSVP Refresh Overhead Reduction Extensions
References Referenced by
Proposed Standard informatively references
RFC 3097 RSVP Cryptographic Authentication -- Updated Message Type Value
References Referenced by
Proposed Standard informatively references
RFC 3175 Aggregation of RSVP for IPv4 and IPv6 Reservations
References Referenced by
Proposed Standard normatively references
RFC 3473 Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions
References Referenced by
Proposed Standard informatively references
RFC 4206 Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)
References Referenced by
Proposed Standard informatively references
RFC 4208 Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model
References Referenced by
Proposed Standard informatively references
RFC 4364 BGP/MPLS IP Virtual Private Networks (VPNs)
References Referenced by
Proposed Standard normatively references
RFC 4659 BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN
References Referenced by
Proposed Standard normatively references
RFC 4804 Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE Tunnels
References Referenced by
Proposed Standard normatively references
RFC 4860 Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations
References Referenced by
Proposed Standard informatively references
RFC 4923 Quality of Service (QoS) Signaling in a Nested Virtual Private Network
References Referenced by
Informational informatively references
RFC 5741 RFC Streams, Headers, and Boilerplates
References Referenced by
Informational Possible Reference Possible Downref
RFC 5824 Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN
References Referenced by
Informational informatively references
RFC 5971 GIST: General Internet Signalling Transport
References Referenced by
Experimental informatively references
RFC 5974 NSIS Signaling Layer Protocol (NSLP) for Quality-of-Service Signaling
References Referenced by
Experimental informatively references