draft-ietf-tsvwg-rsvp-user-error-spec-04.txt   draft-ietf-tsvwg-rsvp-user-error-spec-05.txt 
Network Working Group G. Swallow Network Working Group G. Swallow
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Category: Standards Track Category: Standards Track
Created: March 28, 2008 A. Farrel Created: April 1, 2008 A. Farrel
Expiration Date: September 28, 2008 Old Dog Consulting Expiration Date: October 1, 2008 Old Dog Consulting
User-Defined Errors for RSVP User-Defined Errors for RSVP
draft-ietf-tsvwg-rsvp-user-error-spec-04.txt draft-ietf-tsvwg-rsvp-user-error-spec-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 9 skipping to change at page 2, line 9
defining new error codes. Further, no provision for user-defined defining new error codes. Further, no provision for user-defined
errors exists in RSVP. errors exists in RSVP.
This document defines a USER_ERROR_SPEC to be used in addition to the This document defines a USER_ERROR_SPEC to be used in addition to the
ERROR_SPEC to carry additional user information related to errors. ERROR_SPEC to carry additional user information related to errors.
0. Changes Since Last Revision 0. Changes Since Last Revision
[This section to be removed before publication as an RFC.] [This section to be removed before publication as an RFC.]
- Minor editorial changes after working group last call review. - Clarify that Error Description may be empty.
- Add discussion of ResvConf messages.
1. Introduction 1. Introduction
The Resource ReserVation Protocol (RSVP) [RFC2205] defines an The Resource ReserVation Protocol (RSVP) [RFC2205] defines an
ERROR_SPEC object for communicating errors. That object has a ERROR_SPEC object for communicating errors. That object has a
defined format that permits the definition of 256 error codes. As defined format that permits the definition of 256 error codes. As
RSVP has been developed and extended, the convention has been to be RSVP has been developed and extended, the convention has been to be
conservative in communicating errors. Further no provision for user conservative in communicating errors. Further no provision for user
defined errors exists in RSVP. defined errors exists in RSVP.
skipping to change at page 4, line 17 skipping to change at page 4, line 17
A unique identifier of an organization encoded as an 8-bit A unique identifier of an organization encoded as an 8-bit
integer. An organization MAY use this field to create integer. An organization MAY use this field to create
independent Error Value spaces. This is intended to independent Error Value spaces. This is intended to
facilitate teams which are doing parallel development. If facilitate teams which are doing parallel development. If
independent spaces are not required, this field SHOULD be independent spaces are not required, this field SHOULD be
set to zero. set to zero.
Err Desc Len Err Desc Len
The length of the error description in the Error Description The length of the error description in the Error Description
field in bytes excluding any padding. field in bytes excluding any padding. Zero is a valid length if
no error description is supplied.
User Error Value User Error Value
A 16-bit integer. The meaning is specified by the A 16-bit integer. The meaning is specified by the
(sub-)organization indicated by the Enterprise Number and Sub (sub-)organization indicated by the Enterprise Number and Sub
Org fields. Org fields.
Error Description Error Description
A string of characters in US-ASCII padded with nulls (0x00) A string of characters in US-ASCII padded with nulls (0x00)
to a multiple of 4 bytes. While no format is required, it to a multiple of 4 bytes. If the Err Desc Len is zero then
is RECOMMENDED that organizations use a published schema for no bytes are supplied.
this string to promote consistent decoding.
User-Defined Subobjects User-Defined Subobjects
User-defined subobjects MAY be included. The generic format of User-defined subobjects MAY be included. The generic format of
subobjects is specified in Section 3.1. The semantics of a subobjects is specified in Section 3.1. The semantics of a
subobject is indicated by the Type field, but the semantics, subobject is indicated by the Type field, but the semantics,
format and contents of the Value field are specified by the format and contents of the Value field are specified by the
(sub-)organization indicated by the Enterprise Number and (sub-)organization indicated by the Enterprise Number and
Sub Org fields of this object. Sub Org fields of this object.
 End of changes. 5 change blocks. 
9 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/