rfc.dk

Cited in: RFC 5376

10 RFCs mentioned in the text of RFC 5376 (Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP))

RFCTitleStatusDate
2119Key words for use in RFCs to Indicate Requirement LevelsS. BradnerBest Current PracticeMarch 1997
4107Guidelines for Cryptographic Key ManagementS. Bellovin, R. HousleyBest Current PracticeJune 2005
4206Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)K. Kompella, Y. RekhterProposed StandardOctober 2005
4216MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) RequirementsR. Zhang, Ed., J.-P. Vasseur, Ed.InformationalNovember 2005
4655A Path Computation Element (PCE)-Based ArchitectureA. Farrel, J.-P. Vasseur, J. AshInformationalAugust 2006
4657Path Computation Element (PCE) Communication Protocol Generic RequirementsJ. Ash, Ed., J.L. Le Roux, Ed.InformationalSeptember 2006
4758Cryptographic Token Key Initialization Protocol (CT-KIP) Version 1.0 Revision 1M. NystroemInformationalNovember 2006
5150Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE)A. Ayyangar, K. Kompella, JP. Vasseur, A. FarrelProposed StandardFebruary 2008
5151Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) ExtensionsA. Farrel, Ed., A. Ayyangar, JP. VasseurProposed StandardFebruary 2008
5152A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)JP. Vasseur, Ed., A. Ayyangar, Ed., R. ZhangProposed StandardFebruary 2008