User-Defined Errors for RSVP
RFC 5284
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'The Resource ReserVation Protocol (RSVP) defines an ERROR_SPEC object for communicating errors. That object has a … Received changes through RFC Editor sync (changed abstract to '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]') |
|
2015-10-14
|
(System) | Notify list changed from tsvwg-chairs@ietf.org, draft-ietf-tsvwg-rsvp-user-error-spec@ietf.org to (None) |
|
2008-08-28
|
Cindy Morgan | State Changes to RFC Published from RFC Ed Queue by Cindy Morgan |
|
2008-08-28
|
Cindy Morgan | [Note]: 'RFC 5284' added by Cindy Morgan |
|
2008-08-27
|
(System) | RFC published |