rfc.dk

Cited in: RFC 7571

13 RFCs mentioned in the text of RFC 7571 (GMPLS RSVP-TE Extensions for Lock Instruct and Loopback)

RFCTitleStatusDate
2119Key words for use in RFCs to Indicate Requirement LevelsS. BradnerBest Current PracticeMarch 1997
3209RSVP-TE: Extensions to RSVP for LSP TunnelsD. Awduche, L. Berger, D. Gan, T. Li, V. Srinivasan, G. SwallowProposed StandardDecember 2001
3471Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional DescriptionL. Berger, Ed.Proposed StandardFebruary 2003
3473Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) ExtensionsL. Berger, Ed.Proposed StandardFebruary 2003
5420Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)A. Farrel, Ed., D. Papadimitriou, JP. Vasseur, A. AyyangarProposed StandardFebruary 2009
5741RFC Streams, Headers, and BoilerplatesL. Daigle, Ed., O. Kolkman, Ed., IAB · obsoleted by RFC 7841InformationalDecember 2009
5860Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport NetworksM. Vigoureux, Ed., D. Ward, Ed., M. Betts, Ed.Proposed StandardMay 2010
5920Security Framework for MPLS and GMPLS NetworksL. Fang, Ed.InformationalJuly 2010
6371Operations, Administration, and Maintenance Framework for MPLS-Based Transport NetworksI. Busi, Ed., D. Allan, Ed.InformationalSeptember 2011
6435MPLS Transport Profile Lock Instruct and Loopback FunctionsS. Boutros, Ed., S. Sivabalan, Ed., R. Aggarwal, Ed., M. Vigoureux, Ed., X. Dai, Ed.Proposed StandardNovember 2011
7260GMPLS RSVP-TE Extensions for Operations, Administration, and Maintenance (OAM) ConfigurationA. Takacs, D. Fedyk, J. HeProposed StandardJune 2014
7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TEE. Bellagamba, A. Takacs, G. Mirsky, L. Andersson, P. Skoldstrom, D. WardProposed StandardMarch 2015
7570Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)C. Margaria, Ed., G. Martinelli, S. Balls, B. WrightProposed StandardJuly 2015