2.4.14 Resource Allocation Protocol (rap)

NOTE: This charter is a snapshot of the 50th IETF Meeting in Minneapolis, Minnesota. It may now be out-of-date. Last Modified: 14-Mar-01


Scott Hahn <sdhahn@ibeam.intel.com>
Mark Stevens <mstevens@ellacoya.com>

Operations and Management Area Director(s):

Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>

Operations and Management Area Advisor:

Bert Wijnen <bwijnen@lucent.com>

Mailing Lists:

General Discussion:rap@ops.ietf.org
To Subscribe: rap-request@ops.ietf.org
In Body: subscribe
Archive: ftp://ops.ietf.org/pub/lists/rap.*

Description of Working Group:

Recent work in the IETF has led to the development of standards for a QoS-enabled Internet. Through the efforts of the Integrated Services working group, data flows can describe their desired or required service to the network. RSVP carries the service requests into the network, where the acceptance of these QoS requests results in better network service to some flows, possibly at the expense of service to traditional best-effort flows.

In an open and public Internet (as well as large intranets), maintaining such service differentiation inherently depends on mechanisms capable of enforcing (or reporting) operational policy constraints. Towards this end, RSVP message formats contain a place-holder for policy data elements, which may contain information relevant to the network's decision to grant a reservation request.
Certain network elements may require assistance in the processing of these policy-data elements and, therefore, may communicate with one or more policy servers, entities which specialize in the making of policy decisions.
The purpose of the RAP working group is to establish a scalable policy control model for RSVP. The working group will specify a protocol for use among RSVP-capable network nodes and policy servers. This work will also require documentation of any extensions to RSVP which may be necessary in support of this policy control.
In addition, the working group will define usage directives for use of the COPS base protocol to support policy information exchange transactions within the framework being standardized in the Policy Framework Working Group. In particular, the group will address the following work items:
1. COPS usage for policy provisioning transactions ("COPS Usage"): The working group will produce a standards-track RFC that specifies usage of COPS for the support of policy information exchange transactions between a PDP and its PEPs.
2. Object syntax for carrying policy provisioning information ("Object Syntax"): The working group will produce a standards track RFC that specifies the syntax of objects and their contents for carrying policy information. The working group will specifically focus on the syntax of objects needed for carrying information related to QoS policy provisioning.
This work explicitly excludes definition of semantics of policy provisioning objects. Instead, it will rely on the definitions from the relevant working groups such as DiffServ and ISSLL.
Documents produced by the working group must fully address all the security aspects of this type of protocol. In particular, theft and denial of service threats must be minimized.
In pursuit of these goals, the working group must expressly avoid specifying policy behavior. The judgment of specific policies is similarly beyond the scope of the working group. The working group will, however, specify mechanisms that allow for a wide variety of possible policies to be carried out.

Goals and Milestones:



Submit I-D framework document for policy control for RSVP to IESG for publication as a RFC.



Submit I-D defining any necessary extensions to RSVP to support policy control to IESG for publication as a RFC



Submit I-D defining a standard protocol for the exchange of policy information between RSVP-capable network nodes and policy servers to IESG for publication as a RFC.



Submit Initial draft of document that specifies COPS usage for policy provisioning transactions

Sep 99


Submit initial ID on object syntax for carrying QoS policy provisioning information (dependent on progress in DiffServ and ISSLL working groups)



Working Group last call on revised version of COPS Usage document incorporating mailing list discussions



Submit COPS Usage document to IESG for publication as an RFC



Submit object syntax transport protocol ID



Submit object syntax transport protocol to IESG for consideration as a RFC.

Request For Comments:






Signaled Preemption Priority Policy Element



Identity Representation for RSVP



A Framework for Policy-based Admission Control



The COPS (Common Open Policy Service) Protocol



COPS usage for RSVP



RSVP Extensions for Policy Control



Application and Sub Application Identity Policy Element for Use with RSVP



Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol Clients

Current Meeting Report

Resource Allocation Protocol WG Meeting Minutes
50th IETF

TUESDAY, March 20, 2001 1300-1400 Afternoon Session I Salon E/F
WEDNESDAY, March 21, 2001 1300-1500 Afternoon Sessions I & II Salon C

On Tuesday, the RAP working group session focused on draft updates and presentations on new drafts. On Wednesday, the working group discussed the revised working group charter and working group items.



Amol Kulkarni reviewed the updates to the Framework PIB for Accounting Usage. The updates were primarily related to the reporting interval mechanisms and invocation of a solicited accounting report. It was identified that there is a need for defining global selections and usage reporting, and the need for partial solicited accounting report invocation.


Diana Rawlins reviewed the updates to the RSVP Policy Control Criteria PIB. The updates expanded the policy mode capability negotiation between the PEP and PDP and there was the addition of usage reporting on the allocated traffic specifications and session duration.


Louis-Nicolas Hamer presented a framework for media authorization to network resources using three models. These models are the coupled model, the associated model and the non-associated model. The coupled model assumes that a pre-established trust relationship exists among all the affected network elements including the session management and resource policy management servers. The associated model involves a single logical session management and policy server that is controlling the decisions for elements that are not known in advance of the transaction, and where the edge device client selects a session management server from a pool of servers. The non-associated model assumes that there is no trust relationship and coordination among the session management and resource policy servers.


Christian Jacquenet presented a draft defining a new COPS-PR client type for the enforcement of Traffic Engineering policies. These provisioned policies would specify criteria used to control the dynamic routing selection process for OSPF, BGP-4 and IS-IS protocols.


A revised charter was proposed, discussed and adopted with the following new items being included in the revised RAP charter.

A version of draft-ietf-rap-rsvp-newidentity that addresses security shortcomings with the current document. Rodney Hess is the editor of this document.


A standards track document defining new RSVP error codes values for the Policy object that modifies sender behavior. Ralph Santitoro is the editor of this document.


A standards track document for defining the framework and mechanism for the authorization of RSVP sessions. Louis Hamer is the editor of this document.


A standards track document defining an RSVP Local Policy Control Criteria PIB. Diana Rawlins is the editor of this document.


A standards track document defining the COPS usage for the RSVP proxy with Dinesh Dutt being the editor. There was confusion as to whether this draft had already been added to the working group charter in the past. Amol Kulkarni and Alan Crouch will also work on the draft.

A standards track document describing the COPS provisioning framework. This document is to address security and extensibility considerations that would provide guidance to future draft submissions regarding COPS extensions. Kwok Ho Chan is the editor of this document.

The existing working group items included in the revised charter are:

A standards track document defining the accounting framework and accounting PIB with Amol Kulkarni as the editor.


A standards track document defining the Structure of Provisioning Policy Interface (SSPI) with Scott Hahn as the editor.


There was discussion on the working group doing additional PIBs within the RAP working group until there was more operational experience with PIBs. Bert Wijnen, Operations and Management Area Director, stated that PIBs should be done in their respective working group. He also stated that while MIBs are required for the various standards track protocols, PIBs are not, and that working groups are only to do PIBs if they have the available resources to do so.

It was asked whether informational track drafts, such as Policy Management for RSVP and DiffServ Interworking, needed to be chartered as working group items. Bert explained that personal submission can be made to the IESG for the informational track drafts but otherwise, the draft needed to be chartered by the working group for informational draft consideration.

David Durham took the action item to get an IANA port for COPS over TLS. Bert Wijnen did not believe that a related standards track document was required for the port registration with IANA.

Comments were made questioning the need for both COPS and SNMP for device management and accounting. The observation was made several times that there needs to be a consolidated operations architectural vision. Bert Wijnen explained that today there are two management mechanisms in use, SNMP and command line interface, and that while an overall architectural vision was needed it was beyond the scope of the RAP working group. He further explained that the original MIBs were not suited to policy management and today there did not exist good policy management mechanisms.

A show of hands was requested to indicate persons willing to work on the newly chartered items. More than 10 hands were raised.

Meeting participants argued the need for support for authentication.
Support for work in this area was expressed by a sufficient number of people to warrant addition to the charter.

Minutes submitted by Kwok Ho Chan and Diana Rawlins 3/29/2001


RSVP Policy Control Criteria PIB
Framework for session set-up with media authorization & Session Authorization for RSVP
A COPS client-type for IP Traffic Engineering Policy Enforcement