RFCs about resource reservation protocol
32 documents indexed under this keyword
- RFC 2380RSVP over ATM Implementation RequirementsCurrentAugust 1998proposed standard
- RFC 2745RSVP Diagnostic MessagesCurrentJanuary 2000proposed standard
- RFC 2746RSVP Operation Over IP TunnelsCurrentJanuary 2000proposed standard
- RFC 2747RSVP Cryptographic AuthenticationUpdatedJanuary 2000proposed standard
- RFC 2749COPS usage for RSVPCurrentJanuary 2000proposed standard
- RFC 2750RSVP Extensions for Policy ControlCurrentJanuary 2000proposed standard
- RFC 2814SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networksCurrentMay 2000proposed standard
- RFC 2872Application and Sub Application Identity Policy Element for Use with RSVPCurrentJune 2000proposed standard
- RFC 2961RSVP Refresh Overhead Reduction ExtensionsUpdatedApril 2001proposed standard
- RFC 2996Format of the RSVP DCLASS ObjectCurrentNovember 2000proposed standard
- RFC 2997Specification of the Null Service TypeCurrentNovember 2000proposed standard
- RFC 3097RSVP Cryptographic Authentication -- Updated Message Type ValueCurrentApril 2001proposed standard
- RFC 3175Aggregation of RSVP for IPv4 and IPv6 ReservationsUpdatedSeptember 2001proposed standard
- RFC 3181Signaled Preemption Priority Policy ElementCurrentOctober 2001proposed standard
- RFC 3182Identity Representation for RSVPCurrentOctober 2001proposed standard
- RFC 3209RSVP-TE: Extensions to RSVP for LSP TunnelsUpdatedDecember 2001proposed standard
- RFC 3473Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) ExtensionsUpdatedFebruary 2003proposed standard
- RFC 3477Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)UpdatedFebruary 2003proposed standard
- RFC 3496Protocol Extension for Support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic EngineeringCurrentMarch 2003informational
- RFC 3726Requirements for Signaling ProtocolsCurrentApril 2004informational
- RFC 3936Procedures for Modifying the Resource reSerVation Protocol (RSVP)CurrentOctober 2004best current practice
- RFC 4090Fast Reroute Extensions to RSVP-TE for LSP TunnelsUpdatedMay 2005proposed standard
- RFC 4124Protocol Extensions for Support of Diffserv-aware MPLS Traffic EngineeringCurrentJune 2005proposed standard
- RFC 4230RSVP Security PropertiesCurrentDecember 2005informational
- RFC 4872RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) RecoveryUpdatedMay 2007proposed standard
- RFC 4873GMPLS Segment RecoveryUpdatedMay 2007proposed standard
- RFC 5284User-Defined Errors for RSVPCurrentAugust 2008proposed standard
- RFC 5710PathErr Message Triggered MPLS and GMPLS LSP ReroutesCurrentJanuary 2010proposed standard
- RFC 5852RSVP-TE Signaling Extension for LSP Handover from the Management Plane to the Control Plane in a GMPLS-Enabled Transport NetworkCurrentApril 2010proposed standard
- RFC 6387GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)CurrentSeptember 2011proposed standard
- RFC 6411Applicability of Keying Methods for RSVP SecurityCurrentOctober 2011informational
- RFC 6689Usage of the RSVP ASSOCIATION ObjectCurrentJuly 2012informational