User-Defined Errors for RSVP
RFC 5284, “User-Defined Errors for RSVP”, is a Proposed Standard document published in August 2008 by G. Swallow, A. Farrel. The canonical text is published by the RFC Editor.
Abstract
The Resource ReserVation Protocol (RSVP) defines an ERROR_SPEC object for communicating errors. That object has a defined format that permits the definition of 256 error codes. As RSVP has been developed and extended, the convention has been to be conservative in defining new error codes. Further, no provision for user-defined errors exists in RSVP.
This document defines a USER_ERROR_SPEC to be used in addition to the ERROR_SPEC to carry additional user information related to errors. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5284 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5283 LDP Extension for Inter-Area Label Switched Paths
- RFC 5285 A General Mechanism for RTP Header Extensions
- RFC 5282 Using Authenticated Encryption Algorithms with the Encrypted Payload of the Internet Key Exchange version 2 Protocol
- RFC 5286 Basic Specification for IP Fast Reroute: Loop-Free Alternates
- RFC 5281 Extensible Authentication Protocol Tunneled Transport Layer Security Authenticated Protocol Version 0
- RFC 5287 Control Protocol Extensions for the Setup of Time-Division Multiplexing Pseudowires in MPLS Networks
- RFC 5280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List Profile
- RFC 5288 AES Galois Counter Mode Cipher Suites for TLS