Network Working Group George Swallow Internet Draft Cisco Systems, Inc. Category: Standards Track Expiration Date: April 2007 Adrian Farrel Old Dog Consulting October 2006 User Defined Errors for RSVP draft-swallow-rsvp-user-error-spec-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any 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 aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html 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 communicating errors. Further, no provision for user defined errors exists in RSVP. Swallow & Farrel Standards Track [Page 1] Internet Draft draft-swallow-rsvp-user-error-spec-00.txt October 2006 This document defines a new RSVP object to permit user defined error values to be communicated. Swallow & Farrel Standards Track [Page 2] Internet Draft draft-swallow-rsvp-user-error-spec-00.txt October 2006 Contents 1 Introduction .............................................. 4 1.1 Conventions ............................................... 4 2 User Defined Error ........................................ 4 3 USER_ERROR_SPEC Class ..................................... 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 ........................................ 7 Swallow & Farrel Standards Track [Page 3] Internet Draft draft-swallow-rsvp-user-error-spec-00.txt October 2006 1. Introduction The Resource ReserVation Protocol (RSVP) [RFC2205] 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 communicating errors. Further no provision for user defined errors exists in RSVP. When developing extensions to RSVP it is often useful for those implementing to define error messages to aid both in the initial debugging and in testing against older versions or other implementa- tions. This document defines a new RSVP object to permit user defined errors to be communicated. This will enable diverse organizations to define errors which they can use for internal development. These error val- ues could also be shared with the community at large to aid in pro- moting interoperability between diverse implementations. RSVP PathErr and ResvErr messages require the presence of an ERROR_SPEC object. [RFC3473] defines the Notify message that also requires the presence of an ERROR_SPEC object. In order to not change the mandatory contents of these messages, this document defines a new error code value that indicates that the new object is present and carries a user defined error code. 1.1. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [KEYWORDS]. 2. User Defined Error Error Code = : User Error Spec This error code is used to signal the presence of a USER_ERROR_SPEC. No subcodes are defined. When sending this error code, a USER_ERROR_SPEC object SHOULD be included in the PathErr, ResvErr or Notify message. Swallow & Farrel Standards Track [Page 4] Internet Draft draft-swallow-rsvp-user-error-spec-00.txt October 2006 3. USER_ERROR_SPEC Class 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 done for backward compatibility. Existing implementations will ignore the object and pass it along. USER_DEFINED_ERROR object: Class = , C-Type = 1 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 +---------------+---------------+---------------+---------------+ | Organizationally Unique Identifier | Sub Org | +---------------+---------------+---------------+---------------+ | User Error Value | +---------------+---------------+---------------+---------------+ | | . User Defined Sub-TLVs . . . | | +---------------+---------------+---------------+---------------+ Organizationally Unique Identifier (OUI) A unique identifier of an organization. OUIs are assigned by the IEEE. Sub-organization An organization MAY use this field to create independent Error Value spaces. This is intended to facilitate teams which are doing parallel development. If independent spaces are not required, this field SHOULD be set to zero. User Error Value The format and contents are specified by the (sub-) organization indicated by the OUI and Sub Org fields. User Defined Sub-TLVs The format and contents are specified by the (sub-) organization indicated by the OUI and Sub Org fields. Swallow & Farrel Standards Track [Page 5] Internet Draft draft-swallow-rsvp-user-error-spec-00.txt October 2006 4. Procedures for using the User Error Spec 4.1. Procedures for sending the User Error Spec A USER_DEFINED_ERROR object MAY be included in any PathErr or ResvErr message. The Organizationally Unique Identifier MUST be a valid value assigned by the IEEE. As specified in [RFC2205], an ERROR_SPEC object MUST be included with a valid error code. If no other error code applies, the error code MUST be set to , Unspecified Error. 4.2. Procedures for receiving the User Error Spec It is RECOMMENDED that implementations at a minimum log the OUI, Sub- organization, and User Error Value. If an implementation is capable of interpreting the contents of the User Error Spec it MAY take any appropriate action. 5. IANA Considerations This document makes the following assignments from the RSVP Error Codes and Globally-Defined Error Value Sub-Codes registry (pending IANA action): Value Name User Error Spec This document makes the following assignments from the RSVP Class Names, Class Numbers, and Class Types registry (pending IANA action): Number Space Value Name Class Numbers * User Error Spec Class Type 1 User Defined Error * Assignment is requested from the range 192 through 247 Swallow & Farrel Standards Track [Page 6] Internet Draft draft-swallow-rsvp-user-error-spec-00.txt October 2006 6. Security Considerations This document makes no changes to the basic message exchanges of [RFC2205] and [RFC3473]. It will result in a small increase in the number of error messages sent in cases where messages were silently dropped due to the lack of an appropriate error code. 7. Acknowledgments The authors would like to thank Elisheva Hochberg for motivating this document. 8. Normative References [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification", RFC 2205, September 1997. [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 9. Authors' Addresses George Swallow Cisco Systems, Inc. Email: swallow@cisco.com Adrian Farrel Old Dog Consulting EMail: adrian@olddog.co.uk Swallow & Farrel Standards Track [Page 7] Internet Draft draft-swallow-rsvp-user-error-spec-00.txt October 2006 Copyright Notice Copyright (C) The Internet Society (2006). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Expiration Date April 2007 Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Swallow & Farrel Standards Track [Page 8]