References from RFC 5376

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 107	References Referenced by		normatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels References Referenced by	Best Current Practice	Possible Reference
RFC 4107	Guidelines for Cryptographic Key Management References Referenced by	Best Current Practice	normatively 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 4216	MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements References Referenced by	Informational	normatively references
RFC 4655	A Path Computation Element (PCE)-Based Architecture References Referenced by	Informational	normatively references
RFC 4657	Path Computation Element (PCE) Communication Protocol Generic Requirements References Referenced by	Informational	normatively references
RFC 4758	Cryptographic Token Key Initialization Protocol (CT-KIP) Version 1.0 Revision 1 References Referenced by	Informational	informatively references
RFC 5150	Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE) References Referenced by	Proposed Standard	informatively references
RFC 5151	Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions References Referenced by	Proposed Standard	informatively references
RFC 5152	A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs) References Referenced by	Proposed Standard	informatively references