Internet Draft A. Smith Expires August 1999 Extreme Networks draft-smith-sbm-config-00.txt February 1999 Definitions of Managed Parameters for RSVP and SBM network nodes 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. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress." To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). Copyright (C) The Internet Society (1999). All Rights Reserved. Abstract This memo includes a list of manageable parameters for RSVP and SBM implementations. These are in addition to those already described in RFC 2206 and RFC 2213. Specifically, it describes parameters for control of the base signaling protocols themselves, as well as a basic set of parameters for control of policy decisions by a Local Policy Module. These are not intended to be exhaustive lists but they have been identified as useful for practical implementations. Smith Expires August 1999 [Page 1] Internet Draft SBM Parameters February 1999 1. Introduction SBM components of the ISSLL/IS802 architecture require some configuration parameters for operational use. These fall into 2 main areas: configuration of RSVP protocol operation and configuration of SBM-specifics. For the former, RFC 2206 and RFC 2213 cover some configuration operations as SNMP MIBS and some more are listed here. There are currently no proposals for the latter and some are offered here for discussion. In addition, admission policy decisions need to be managed. The RSVP architecture accomodates both policy decisions made locally at the RSVP node ("Local Policy Module" or LPM) and also the outsourcing of policy decisions to another Policy Server node ("Policy Decision Point" or PDP) using the COPS protocol. The work of the IETF's RAP WG covers the latter scenario in detail. The former is not covered by any current proposals and so some suggestions for a simple set of manageable objects, focussed on LPM decisions made in an RSVP/SBM context, are proposed here. 2. Editorial information 2.1. Issues requiring further consideration (1) The "LPM" parts of this are probably just for use when policy is not to be outsourced via COPS although I can conceive of scenarios where you might have a mix of LPM and PDP making decisions e.g. you might care a lot more about accuracy on Guaranteed admissions than you do about Controlled Load ones. The LPM parts can, therefore, be considered seperable from the whole. (2) Not sure about the bandwidth % vs. absolute bps parameters. It is painful to write absolute-b/w rules in auto-sensing environments when you don't know the available link bandwidth until run-time. Might need to duplicate some of these. (3) Granularity on many of objects needs to be determined - per-port, per-subnet or per-system: suggestions are offered. (4) This is a bit confused about delay/slack terms - probably need to match up pragmatic needs vs. what the GS specs and MIBs say about this. Smith Expires August 1999 [Page 2] Internet Draft SBM Parameters February 1999 3. Parameters Indexing ======== N = per-node only S = per-subnet and per-node P = per-port, per-subnet and per-node All parameters are assumed to apply in both transmit and receive directions unless otherwise stated. RSVP parameters =============== Parameter Units Index Default Description ---------------------------------------------------------------------------- ---- rsvpEnabled* Boolean S false Enable processing of RSVP messages. rsvpCopsEnabled Boolean S false Enable outsourcing of RSVP policy via COPS. rsvpSenderPolicyEnabled Boolean S false Enable processing of RSVP policy objects in PATH messages. rsvpReceiverPolicyEnabled Boolean S false Enable processing of RSVP policy objects in RESV messages. rsvpGsDelay usec P - Maximum GS queueing delay to account for in admission control. rsvpGsSlack usec P - Slack-term that may be used to adjust GS reservations (is this the rate-proportional term?). RSVP Local Policy Module parameters =================================== Parameter Units Index Default Description ---------------------------------------------------------------------------- ---- rsvpLpmClServiceEnabled Boolean S true Enable admission of Controlled-Load session Smith Expires August 1999 [Page 3] Internet Draft SBM Parameters February 1999 requests. rsvpLpmGsServiceEnabled Boolean S true Enable admission of Guaranteed Service session requests. rsvpLpmMaxBwPercent** % P 100 Maximum limit on bandwidth use of outbound link for all RSVP flows. rsvpLpmMaxBuffer % P 100 Maximum limit on buffer use for all committed RSVP flows. rsvpLpmClMaxBwPercent % P 100 Maximum limit on bandwidth use of outbound link for CL flows. rsvpLpmClOversubscribeRatio % P 100 Allowed ratio of outbound bandwidth oversubscription for CL flows. rsvpLpmClMaxBuffer % P 100 Maximum limit on buffer use for all committed CL flows. rsvpLpmClMaxFlows ea P infinite Maximum number of CL flows outbound on this link. rsvpLpmClMaxPeakRate bps P line Maximum outbound peak rate limit for any one admitted CL flow rsvpLpmClMaxTokenRate bps P line Maximum outbound average token rate for any one admitted CL flow. rsvpLpmClMaxDuration sec P infinite Outbound CL flows will be torn down after this maximum time limit. rsvpLpmClDefaultBumpPriority 0..255 P 128 Default priority of CL reservations w.r.t. other admitted outbound flows. rsvpLpmClMulticastAllowed Boolean P true Are outbound CL multicast flows allowed? rsvpLpmGsMaxBwPercent % P 100 Maximum limit on bandwidth use of outbound link for GS flows. rsvpLpmGsOversubscribeRatio % P 100 Allowed ratio of outbound oversubscription for GS flows. rsvpLpmGsMaxBuffer % P 100 Maximum limit on buffer use for all committed Smith Expires August 1999 [Page 4] Internet Draft SBM Parameters February 1999 GS flows. rsvpLpmGsMaxFlows ea P infinite Maximum number of GS flows outbound on this link. rsvpLpmGsMaxPeakRate bps P line Maximum outbound peak rate limit for any one admitted GS flow. rsvpLpmGsMaxTokenRate bps P line Maximum outbound average token rate for any one admitted GS flow. rsvpLpmGsMaxDuration sec P infinite Outbound GS flows will be torn down after this maximum time limit. rsvpLpmGsDefaultBumpPriority 0..255 P 128 Default priority of GS reservations w.r.t. other admitted flows. rsvpLpmGsMulticastAllowed Boolean P true Are outbound GS multicast flows allowed? * rsvpEnabled partially overlaps functionality with RFC2206 rsvpIfEnabled although it is not clear that ifIndex is the appropriate unit of control ** rsvpLpmMaxBwPercent partially overlaps functionality with RFC2213 intSrvIfAttribMaxAllocatedBits. SBM parameters ============== Parameter Units Index Default Description ---------------------------------------------------------------------------- ---- sbmEnable Boolean S true Enable SBM processing of messages (implies rsvpEnable). sbmClTrafficClass 0..7 S 4 Traffic Class (802.1p user_priority) to be applied to CL flows. sbmGsLooseBound usec S infinite Target delay bound on GS flows admitted to loose delay bound class. sbmGsLooseServiceEnable Boolean S true Enable admission of GS flows that require medium delay bounds Smith Expires August 1999 [Page 5] Internet Draft SBM Parameters February 1999 (implies rsvpGsServiceEnable). sbmGsLooseTrafficClass 0..7 S 4 Traffic Class (802.1p user_priority) to be applied to GS flows requiring loose delay bounds. sbmGsMedBound usec S 100000 Target delay bound on GS flows admitted to medium delay bound class. sbmGsMedServiceEnable Boolean S true Enable admission of GS flows that require medium delay bounds (implies rsvpGsServiceEnable). sbmGsMedTrafficClass 0..7 S 5 Traffic Class (802.1p user_priority) to be applied to Guaranteed Service flows requiring medium delay bounds. sbmGsTightBound usec S 10000 Target delay bound on GS flows admitted to tight delay bound class. sbmGsTightServiceEnable Boolean S true Enable admission of GS flows that require tight delay bounds (implies rsvpGsServiceEnable). sbmGsTightTrafficClass 0..7 S 6 Traffic Class (802.1p user_priority) to be applied to GS flows that require tight delay bounds. sbmDsbmRefreshInterval sec N 5 DSBM refresh interval. sbmDsbmDeadInterval sec N 15 DSBM Election dead time. sbmDsbmElectionPriority 0..?? S 4 Election bid for this SBM to become DSBM. SBM Local Policy Module parameters ================================== Smith Expires August 1999 [Page 6] Internet Draft SBM Parameters February 1999 Parameter Units Index Default Description ---------------------------------------------------------------------------- ---- sbmLpmGsLooseMaxBwPercent % P 100 Maximum limit on bandwidth use of outbound link for GS flows. sbmLpmGsLooseOversubscribeRatio % P 100 Allowed ratio of outbound oversubscription for GS flows. sbmLpmGsLooseMaxFlows ea P infinite Maximum number of GS flows outbound on this link. sbmLpmGsLooseMaxPeakRate bps P line Maximum outbound peak rate limit for any one admitted GS flow. sbmLpmGsLooseMaxTokenRate bps P line Maximum outbound average token rate for any one admitted GS flow. sbmLpmGsLooseMaxDuration sec P infinite Outbound GS flow will be torn down after this maximum time limit. sbmLpmGsLooseDefaultBumpPriority 0..255 P 128 Default priority of GS reservations w.r.t. other admitted outbound flows (overrides rsvpLpmGsDefaultBumpPriority). sbmLpmGsMedMaxBwPercent % P 100 Maximum limit on bandwidth use of outbound link for GS flows. sbmLpmGsMedOversubscribeRatio % P 100 Allowed ratio of outbound oversubscription for GS flows. sbmLpmGsMedMaxFlows ea P infinite Maximum number of GS flows outbound on this link. sbmLpmGsMedMaxPeakRate bps P line Maximum outbound peak rate limit for any one admitted GS flow. sbmLpmGsMedMaxTokenRate bps P line Maximum outbound average token rate for any one Smith Expires August 1999 [Page 7] Internet Draft SBM Parameters February 1999 admitted GS flow. sbmLpmGsMedMaxDuration sec P infinite Outbound GS flow will be torn down after this maximum time limit. sbmLpmGsMedDefaultBumpPriority 0..255 P 128 Default priority of GS reservations w.r.t. other admitted outbound flows (overrides rsvpLpmGsDefaultBumpPriority). sbmLpmGsTightMaxBwPercent % P 100 Maximum limit on bandwidth use of outbound link for GS flows. sbmLpmGsTightOversubscribeRatio % P 100 Allowed ratio of outbound oversubscription for GS flows. sbmLpmGsTightMaxFlows ea P infinite Maximum number of GS flows outbound on this link. sbmLpmGsTightMaxPeakRate bps P line Maximum outbound peak rate limit for any one admitted GS flow. sbmLpmGsTightMaxTokenRate bps P line Maximum outbound average token rate for any one admitted GS flow sbmLpmGsTightMaxDuration sec P infinite Outbound GS flow will be torn down after this maximum time limit. sbmLpmGsTightDefaultBumpPriority 0..255 P 128 Default priority of GS reservations w.r.t. other admitted flows (overrides rsvpLpmGsDefaultBumpPriority). Smith Expires August 1999 [Page 8] Internet Draft SBM Parameters February 1999 4. Acknowledgements Thanks to Ramesh Pabbati for useful prior discussions on SBM config requirements: much of this is based on his ideas. 5. References [RSVP] Braden, R., L. Zhang, S. Berson, S. Herzog, S. Jamin, "Resource Reservation Protocol (RSVP) - Version 1 Functional Specification", RFC 2205, September 1997 [IS802] Ghanwani, A., Pace, W., Srinivasan, V., Smith, A., Seaman, M., "A Framework for Providing Integrated Services Over Shared and Switched LAN Technologies", Internet Draft, May 1998 [SBM] Yavatkar, R., Hoffman, D., Bernet, Y., Baker, F., Speer, M., "SBM (Subnet Bandwidth Manager): A Protocol for Admission Control over IEEE 802-style Networks", Internet Draft, December 1998 [RSVPMIB] Baker, F., Krawczyk, J., Sastry, A., "RSVP Management Information Base using SMIv2", RFC 2206, Cisco Systems, Arrowpoint Communications, Cisco Systems, Sepember 1997 [INTSERVMIB] Baker, F., Krawczyk, J., Sastry, A., "Integrated Services Management Information Base using SMIv2", RFC 2213, Cisco Systems, Arrowpoint Communications, Cisco Systems, Sepember 1997 [PROCESS] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, Harvard University, October 1996. Smith Expires August 1999 [Page 9] Internet Draft SBM Parameters February 1999 6. Security Considerations There are a number of management objects defined in this memo that are writeable. Such objects may be considered sensitive or vulnerable in some network environments. The support for modify operations in a non- secure environment without proper protection can have a negative effect on network operations. 7. Authors' Addresses Andrew Smith Extreme Networks 10460 Bandley Drive Cupertino CA 95014 USA +1 (408) 342 0999 andrew@extremenetworks.com Smith Expires August 1999 [Page 10] Internet Draft SBM Parameters February 1999 Copyright (C) The Internet Society (1999). 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 implmentation 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 organizations, 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. Smith Expires August 1999 [Page 11]