draft-ietf-tsvwg-rsvp-user-error-spec-01.txt   draft-ietf-tsvwg-rsvp-user-error-spec-02.txt 
Network Working Group George Swallow Network Working Group G. Swallow
Internet Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Category: Standards Track Category: Standards Track
Expiration Date: October 2007 Created: October 6, 2007 A. Farrel
Adrian Farrel Expiration Date: April 6, 2007 Old Dog Consulting
Old Dog Consulting
User-Defined Errors for RSVP User-Defined Errors for RSVP
draft-ietf-tsvwg-rsvp-user-error-spec-01.txt draft-ietf-tsvwg-rsvp-user-error-spec-02.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 3, line 5 skipping to change at page 2, line 21
3.1 Subobjects ................................................ 5 3.1 Subobjects ................................................ 5
4 Procedures for Using the User Error Spec .................. 6 4 Procedures for Using the User Error Spec .................. 6
4.1 Procedures for Sending 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 4.2 Procedures for Receiving the User Error Spec .............. 6
5 IANA Considerations ....................................... 6 5 IANA Considerations ....................................... 6
6 Security Considerations ................................... 7 6 Security Considerations ................................... 7
7 Acknowledgments ........................................... 7 7 Acknowledgments ........................................... 7
8 Normative References ...................................... 7 8 Normative References ...................................... 7
9 Authors' Addresses ........................................ 8 9 Authors' Addresses ........................................ 8
0. Changes Since Last Revision
[This section to be removed before publication as an RFC.]
- Use explicit tags for values to be supplied by IANA.
Sections 2, 3 and 5.
- Definition of Length field mentioned non-existent L field.
Section 3.1.
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.
When developing extensions to RSVP, it is often useful for those When developing extensions to RSVP, it is often useful for those
skipping to change at page 3, line 42 skipping to change at page 3, line 42
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>: 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 subcodes 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> = to be assigned by IANA. Please replace <tba> [RFC Editor's note: <tba-xxx> = to be assigned by IANA as per Section 5.
with the number assigned by IANA and remove this note.] Please replace <tba-xxx> with the number assigned by IANA and remove
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 is defined called the the USER_ERROR_SPEC
Class. The class number is taken from the range 192 - 247. This is Class. The class number is taken from the range 192 - 247. This is
done for backward compatibility. Existing implementations will done for backward compatibility. Existing implementations will
ignore the object and pass it along according to the rules of ignore the object and pass it along according to the rules of
[RFC2205]. [RFC2205].
USER_ERROR_SPEC object: Class = <tba>, C-Type = 1 USER_ERROR_SPEC object: Class = <tba-yyy>, C-Type = 1
[RFC Editor's note: <tba> = to be assigned by IANA. Please replace <tba> [RFC Editor's note: <tba-yyy> = to be assigned by IANA as per Section 5.
with the number assigned by IANA and remove this note.] Please replace <tba-yyy> with the number assigned by IANA and remove
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
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
| Enterprise Number | | Enterprise Number |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
| Sub Org | Err Desc Len | User Error Value | | Sub Org | Err Desc Len | User Error Value |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
| | | |
~ Error Description ~ ~ Error Description ~
skipping to change at page 5, line 46 skipping to change at page 5, line 46
Type Type
An 8-bit number assigned by the the (sub-)organization An 8-bit number assigned by the the (sub-)organization
indicated by the Enterprise Number and Sub Org fields of the indicated by the Enterprise Number and Sub Org fields of the
USER_ERROR_SPEC object. USER_ERROR_SPEC object.
Length Length
The Length contains the total length of the subobject in bytes, The Length contains the total length of the subobject in bytes,
including the L, Type and Length fields. The Length MUST be at including the Type and Length fields. The Length MUST be at
least 4, and MUST be a multiple of 4. least 4, and MUST be a multiple of 4.
4. Procedures for Using the User Error Spec 4. Procedures for Using the User Error Spec
4.1. Procedures for Sending the User Error Spec 4.1. Procedures for Sending the User Error Spec
A USER_ERROR_SPEC object MAY be included in any PathErr, ResvErr, or A USER_ERROR_SPEC object MAY be included in any PathErr, ResvErr, or
Notify message. The Enterprise Number MUST be a valid value assigned Notify message for any defined error code. The Enterprise Number
by IANA. MUST be a valid value assigned by IANA.
As specified in [RFC2205] and [RFC3473], an ERROR_SPEC object with a As specified in [RFC2205] and [RFC3473], an ERROR_SPEC object with a
valid error code MUST be included in all PathErr, ResvErr, and Notify valid error code MUST be included in all PathErr, ResvErr, and Notify
messages. This rule is not changed by these procedures even when a messages. This rule is not changed by these procedures even when a
USER_ERROR_SPEC object is included. If no other error code applies, USER_ERROR_SPEC object is included. If no other error code applies,
the Error Code in the ERROR_SPEC object MUST be set to "User Error the Error Code in the ERROR_SPEC object MUST be set to "User Error
Spec" as defined in Section 2 of this document. Spec" as defined in Section 2 of this document.
4.2. Procedures for Receiving the User Error Spec 4.2. Procedures for Receiving the User Error Spec
skipping to change at page 6, line 50 skipping to change at page 6, line 50
error as a malformed message and process according to [RFC2205]. error as a malformed message and process according to [RFC2205].
5. IANA Considerations 5. IANA Considerations
This document makes the following assignments from the RSVP Error This document makes the following assignments from the RSVP Error
Codes and Globally-Defined Error Value Sub-Codes registry (pending Codes and Globally-Defined Error Value Sub-Codes registry (pending
IANA action): IANA action):
Value Name Value Name
<tba> User Error Spec <tba-xxx> User Error Spec
This document makes the following assignments from the RSVP Class This document makes the following assignments from the RSVP Class
Names, Class Numbers, and Class Types registry (pending IANA action): Names, Class Numbers, and Class Types registry (pending IANA action):
Number Space Value Name Number Space Value Name
Class Numbers <tba>* User Error Spec Class Numbers <tba-yyy>* User Error Spec
Class Type 1 User-Defined Error Class Type 1 User-Defined Error
* Assignment is requested from the range 192 through 247 * Assignment is requested from the range 192 through 247
6. Security Considerations 6. Security Considerations
This document makes no changes to the basic message exchanges of This document makes no changes to the basic message exchanges of
[RFC2205] and [RFC3473]. It will result in a small increase in the [RFC2205] and [RFC3473]. It will result in a small increase in the
number of error messages sent in cases where messages were previously number of error messages sent in cases where messages were previously
silently dropped due to the lack of an appropriate error code. silently dropped due to the lack of an appropriate error code.
The mechanisms defined in this document may be used by The mechanisms defined in this document may be used by
implementations to report additional error conditions and information implementations to report additional error conditions and information
arising from security issues and attacks on the RSVP network. arising from security issues and attacks on the RSVP network.
7. Acknowledgments 7. Acknowledgments
The authors would like to thank Elisheva Halevy for motivating this The authors would like to thank Elisheva Halevy for motivating this
document and Tom Nadeau for his review and comments. document, and Tom Nadeau, and Magnus Westerlund for their review and
comments.
8. Normative References 8. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, September 1997. Functional Specification", RFC 2205, September 1997.
 End of changes. 13 change blocks. 
18 lines changed or deleted 31 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/