draft-ietf-tsvwg-rsvp-user-error-spec-03.txt   draft-ietf-tsvwg-rsvp-user-error-spec-04.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: February 14, 2008 A. Farrel Created: March 28, 2008 A. Farrel
Expiration Date: August 14, 2008 Old Dog Consulting Expiration Date: September 28, 2008 Old Dog Consulting
User-Defined Errors for RSVP User-Defined Errors for RSVP
draft-ietf-tsvwg-rsvp-user-error-spec-03.txt draft-ietf-tsvwg-rsvp-user-error-spec-04.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 5 skipping to change at page 2, line 5
The Resource ReserVation Protocol (RSVP) defines an ERROR_SPEC object The Resource ReserVation Protocol (RSVP) defines an ERROR_SPEC object
for communicating errors. That object has a defined format that for communicating errors. That object has a defined format that
permits the definition of 256 error codes. As RSVP has been permits the definition of 256 error codes. As RSVP has been
developed and extended, the convention has been to be conservative in developed and extended, the convention has been to be conservative in
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.
Contents
1 Introduction .............................................. 3
1.1 Conventions ............................................... 3
2 User-Defined Error ........................................ 3
3 USER_ERROR_SPEC Class ..................................... 4
3.1 Subobjects ................................................ 5
4 Procedures for Using the User Error Spec .................. 6
4.1 Procedures for Sending the User Error Spec ................ 6
4.2 Procedures for Receiving the User Error Spec .............. 6
5 IANA Considerations ....................................... 6
6 Security Considerations ................................... 7
7 Acknowledgments ........................................... 7
8 Normative References ...................................... 7
9 Authors' Addresses ........................................ 8
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.]
- Add reference to RFC 2578. - Minor editorial changes after working group last call review.
- Add text to Abstract. - Add discussion of ResvConf messages.
- Section 4.2, para 1. Resolve "SHOULD" to "should" and replace
"appropriate".
- Section 4.2, para 2. Replace "SHOULD" with "MUST".
- Section 4.2, para 3. Provide reason for ignoring repeated objects.
- Section 4.2, para 4. Replace "SHOULD" with "MUST".
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 3, line 32 skipping to change at page 2, line 39
could also be shared with the community at large to aid in promoting could also be shared with the community at large to aid in promoting
interoperability between diverse implementations. interoperability between diverse implementations.
RSVP PathErr and ResvErr messages require the presence of an RSVP PathErr and ResvErr messages require the presence of an
ERROR_SPEC object ([RFC2205]). [RFC3473] defines the Notify message ERROR_SPEC object ([RFC2205]). [RFC3473] defines the Notify message
that also requires the presence of an ERROR_SPEC object. In order to that also requires the presence of an ERROR_SPEC object. In order to
not change the mandatory contents of these messages, this document not change the mandatory contents of these messages, this document
defines a new error code value that indicates that the new object is defines a new error code value that indicates that the new object is
present and carries a user-defined error code. present and carries a user-defined error code.
Note that the ResvConf message defined in [RFC2205] also carries an
ERROR_SPEC object. But this usage of the object does not carry
meaningful Error Codes or Error Values and so the extensions defined
in this document are not applicable to that message.
1.1. Conventions 1.1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. User-Defined Error 2. User-Defined Error
A new Error Code is defined for use in an ERROR_SPEC object. A new Error Code is defined for use in an ERROR_SPEC object.
Error Code = <tba-xxx>: User Error Spec Error Code = <tba-xxx>: User Error Spec
This error code is used to signal the presence of a This error code is used to signal the presence of a
USER_ERROR_SPEC. No subcodes are defined. USER_ERROR_SPEC. No Error Values are defined.
When sending this error code, a USER_ERROR_SPEC object MUST be When sending this error code, a USER_ERROR_SPEC object MUST be
included in the PathErr, ResvErr, or Notify message. included in the PathErr, ResvErr, or Notify message.
[RFC Editor's note: <tba-xxx> = to be assigned by IANA as per Section 5. [RFC Editor's note: <tba-xxx> = to be assigned by IANA as per Section 5.
Please replace <tba-xxx> with the number assigned by IANA and remove Please replace <tba-xxx> with the number assigned by IANA and remove
this note.] this note.]
3. USER_ERROR_SPEC Class 3. USER_ERROR_SPEC Class
A new RSVP object class is defined called the the USER_ERROR_SPEC A new RSVP object class called USER_ERROR_SPEC is defined. To support
Class. The class number is taken from the range 192 - 247. This is backwards compatibility, its class number is in the range 192-247. As
done for backward compatibility. Existing implementations will defined in [RFC2205], implementations that do not understand such an
ignore the object and pass it along according to the rules of object will forward it unmodified.
[RFC2205].
USER_ERROR_SPEC object: Class = <tba-yyy>, C-Type = 1 USER_ERROR_SPEC object: Class = <tba-yyy>, C-Type = 1
[RFC Editor's note: <tba-yyy> = to be assigned by IANA as per Section 5. [RFC Editor's note: <tba-yyy> = to be assigned by IANA as per Section 5.
Please replace <tba-yyy> with the number assigned by IANA and remove Please replace <tba-yyy> with the number assigned by IANA and remove
this note.] this note.]
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
skipping to change at page 5, line 7 skipping to change at page 4, line 21
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.
User Error Value User Error Value
A 16-bit integer. The format and contents are specified by A 16-bit integer. The meaning is specified by the
the (sub-)organization indicated by the Enterprise Number (sub-)organization indicated by the Enterprise Number and Sub
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. While no format is required, it
is RECOMMENDED that organizations use a published schema for is RECOMMENDED that organizations use a published schema for
this string to promote consistent decoding. this string to promote consistent decoding.
User-Defined Subobjects User-Defined Subobjects
 End of changes. 8 change blocks. 
35 lines changed or deleted 18 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/