draft-ietf-issll-rsvp-cap-02.txt Internet Draft Syed, Hamid draft-ietf-issll-rsvp-cap-02.txt Nortel Networks February, 2001 Capability Negotiation: The RSVP CAP Object Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. 1. Abstract The resource reservation protocol [RSVP] is an end-to-end signaling protocol and it can be a useful mechanism to carry the upstream node or network capabilities/willingness to the downstream network/nodes. This draft proposes a capability negotiation object, CAP object, in the RSVP PATH message that can be used to convey end host/upstream node capabilities to the downstream network/nodes. 2. Introduction In today's heterogenous networking environment, it is important for each network to have a knowledge of its upstream nodes/network capabilities before it can perform any actions to support the QoS requirements of the Hamid Expires August, 2001 [Page 1] draft-ietf-issll-rsvp-cap-02.txt February, 2001 flows from upstream networks. Such an advance information would help the network operator to configure the network according to the expected nature of traffic that the network devices have to process and route. The current standards does not provide any way to the end host or network devices to specify their capabilities to the downstream nodes. The resource reservation protocol [RSVP] is an end-to-end signaling protocol and has already been proposed in different scenarios to support end-to-end QoS [INTDIFF]. It can be a useful signaling mechanism to carry the upstream node/network capabilities or willingness to the downstream network or nodes. This draft proposes a capability negotiation object, The RSVP CAP object, in the RSVP PATH message that can be used to convey end host/upstream node capabilities/willingness to the downstream network. This is a generic object that can be used to carry any meaningful capability information in the RSVP PATH message. 3. Conventions used in this document 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]. 4. Format of CAP Object The CAP object has the following format: 0 | 1 | 2 | 3 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | C-Num (TBD) | C-Type=1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | CAP field | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The CAP field is defined with full 32 bits in the object. Each bit in the field can be used for one specific capability representation. 5. Message Processing Rules 5.1 Message Generation (RSVP Host) An RSVP PATH message is created as specified in [RSVP] with following modifications 1. A capability (CAP) object is created and the CAP field is set to indicate the various capabilities of the end host. Only those bits are set that represent a specific capability of the end host. The bits that are unused MUST be left reset Hamid Expires August, 2001 [Page 2] draft-ietf-issll-rsvp-cap-02.txt February, 2001 An example; CAP field: 0x0X: A_Cap The host/node capability/willingness identifier. If A_Cap bit is reset, the sender host/upstream node does not have the capability If A_Cap bit is set, the sender host/upstream node does have the capability Note: A_Cap represents a single capability/willingness of the end host/upstream network node 2. The CAP Object is inserted in the RSVP message in the appropriate place. 5.2 Message Reception (Downstream Router) RSVP PATH message is processed at the downstream router as specified in [RSVP] with following modifications. 1. The router records the CAP object as the micro-flow PATH state 2. The router modifies the CAP object by setting the CAP field to reflect its own capabilities 5.3 Message Reception (Upstream Router) RSVP RESV message is processed at the upstream router as specified in [RSVP] with following modifications. 1. The router checks the recorded PATH state for the micro-flow and installs any rules required to handle the traffic 2. If the router is not aware of the rules, it SHOULD seek the policy rules from the domain policy server 6. IANA Considerations The format of CAP object requires a class number (C-Num) in RSVP message. Moreover, the capabilities defined through the CAP object will be defined in other RFCs and their values will be assigned through IANA. 7. References [INTDIFF], Bernet, Y., Yavatkar, R., Ford, P., Baker, F., Zhang, L., Speer, M., Braden, R., Davie, B., Wroclawski, J., "Integrated Services Operation over Diffserv Networks", RFC 2998, November 2000 Hamid Expires August, 2001 [Page 3] draft-ietf-issll-rsvp-cap-02.txt February, 2001 [RSVP] Braden, R. ed., "Resource ReSerVation Protocol (RSVP) - Functional Specification.", IETF RFC 2205, Sep. 1997. [RFC-2119] S. Bradner, "keywords for use in RFCs to Indicate Requirement Levels", RFC 2119 (BCP), IETF, March 1997. 8. Acknowledgments Thanks to Yoram Bernet and other ISSLL WG members for providing useful comments to make this one happen. Special thanks to Bill Gage for reviewing this draft 9. Author's Address Syed, Hamid Nortel Networks 100 - Constellation Crescent, Nepean, ON K2G 6J8 Phone: (613) 763-6553 Email: hmsyed@nortelnetworks.com 10. Full Copyright Statement "Copyright (C) The Internet Society (date). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organisations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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. Hamid Expires August, 2001 [Page 4] draft-ietf-issll-rsvp-cap-02.txt February, 2001