Resource Allocation Protocol (rap) ---------------------------------- Charter Last Modified: 2005-04-19 Current Status: Active Working Group Chair(s): Scott Hahn Mark Stevens Operations and Management Area Director(s): Bert Wijnen David Kessens Operations and Management Area Advisor: Bert Wijnen Mailing Lists: General Discussion:rap@ops.ietf.org To Subscribe: rap-request@ops.ietf.org In Body: subscribe Archive: https://ops.ietf.org/lists/rap Description of Working Group: Recent work in the IETF have led to the development and standardization of enhanced network services such as QoS and traffic engineering. The complexity of these services and the variations in the capabilities of the devices implementing these services provide a challenge to anyone trying to configure services within medium- and large-scale networks. The working group will define general-purpose objects that facilitate the manipulation of policies and provisioned objects available through COPS and COPS-PR. Where appropriate, these will include frameworks clarifying the applicability of COPS objects and the best practices for the definition of additional objects defined in other working groups. In particular, the group will address the following work items: - A standards track framework document describing the usage of COPS in carrying usage reporting and unsolicited state change information between a PDP and a PEP [FEEDBACKFRWK]. - A standards track document describing a feedback PIB to be used to carry usage/feedback information from the PEP to the PDP [FEEDBACKPIB]. - Complete work on the standards track documents for (a) the data definition language for COPS-PR [SPPI] and (b) the set of core data definitions for QoS provisioning [FRWKPIB]. - A standards track document describing a modular architecture for a COPS based Management Framework. The document will address the COPS message processing, security and access control and may specify examples of how the framework may be implemented. [COPSFRWK] - A standards track document describing a framework or PIB to enable the explicit binding of QoS to to authenticated agents, such as corporate entities or individual users. The purpose of this document is to define a set of data structures that represent subscriber identity, subscriber credentials, and provide support for proxing various authentication strategies. This document will describe the client-server interactions necessary to install identities, bind identities to other provisioning components and the credentials necessary to complete authentication. Identities may be represented in the data structures defined by this document and may take one of many forms. Examples include none (open) partial (snooped by the network device), and full (provided by an existing authentication protocol). Examples of existing protocols include 802.1x, PAP, CHAP, EAP, Kerberos, HTTP, TLS, SSL, and SRP. [BINDFRWK]. - An informational document describing the use of COPS over TLS. [COPSTLS] The working group will continue to document changes to COPS objects needed to support any extensions to RSVP and extensions to RVSP directly related to usage control. Specifically the working group will pursue: - A version of draft-ietf-rap-rsvp-newidentity that addresses security shortcomings with the current document [NEWIDENTITY]. - A standards track document defining new ErrorValues for the RSVP Policy Error Object [RSVPERRVAL]. - A standards track document defining the framework and mechanism for authorizing of RSVP sessions [SESSIONAUTH]. - A standards track document defining an RSVP Local Policy Control Criteria PIB [RSVPPIB]. 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. The Working Group will not define semantics of objects for any specific protocol or technology. Such work will be done (if done at all) in protocol or technology specific WGs. For the work on the [FEEDBACKFWRK] and [FEEDBACKPIB], the WG will work with other WGs (like AAA WG) to prevent duplication and overlapping solutions. Goals and Milestones: Done Submit I-D framework document for policy control for RSVP to IESG for publication as a RFC. Done Submit I-D defining any necessary extensions to RSVP to support policy control to IESG for publication as a RFC Done 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. Done Submit Initial draft of document that specifies COPS usage for policy provisioning transactions Done Submit initial ID on object syntax for carrying QoS policy provisioning information (dependent on progress in DiffServ and ISSLL working groups) Done Working Group last call on revised version of COPS Usage document incorporating mailing list discussions Done Submit COPS Usage document to IESG for publication as an RFC Done Submit object syntax transport protocol ID Done Submit object syntax transport protocol to IESG for consideration as a RFC. Done Submit I-D defining framework of COPS-PR PIB for feedback usage Done Submit Update draft FEEDBACKPIB Done Submit COPSTLS as informational draft Done Submit First draft RSVPPIB Done Submit First draft SESSIONAUTH Done Submit First draft RSVPERRVAL Done Submit FRWKPIB to IESG for consideration as a Proposed Standard Done Submit First draft of FEEDBACKFRWK Done Submit First draft NEWIDENTITY Done Submit Update draft SESSIONAUTH Done Submit First draft BINDFRWK Done Milestone Dropped: Submit First draft COPSFRWK Done Milestone Dropped: Submit Update draft RSVPPIB Done Milestone Dropped: Submit Update draft RSVPERRVAL Done Submit Update draft NEWIDENTITY Done Submit Update draft FEEDBACKFRWK Done Submit Update draft COPSFRWK Done FEEDBACKFRWK Draft to to AD/IESG for consideration as Proposed Standard Done FEEDBACKPIB Draft to to AD/IESG for consideration as Proposed Standard Done SESSIONAUTH Draft to to AD/IESG for consideration as Proposed Standard Done RSVPPIB Draft to AD/IESG for consideration as Proposed Standard Done RSVPERRVAL Draft to to AD/IESG for consideration as Proposed Standard Done COPSFRWK Draft to to AD/IESG for consideration as Proposed Standard Done Milestone Dropped: COPSFRWK Draft to to AD/IESG for consideration as Proposed Standard Done Milestone Dropped: BINDFRWK Draft to to AD/IESG for consideration as Proposed Standard Dec 04 Submit COPSTLS draft for consideration as Proposed Standard Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Feb 01 Feb 05 COPS Over TLS Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC2748 PS Feb 00 The COPS (Common Open Policy Service) Protocol RFC2749 PS Feb 00 COPS usage for RSVP RFC2750 PS Feb 00 RSVP Extensions for Policy Control RFC2751 PS Feb 00 Signaled Preemption Priority Policy Element RFC2752 PS Feb 00 Identity Representation for RSVP RFC2753 I Feb 00 A Framework for Policy-based Admission Control RFC2872 PS Jul 00 Application and Sub Application Identity Policy Element for Use with RSVP RFC2940 PS Oct 00 Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol Clients RFC3084 PS Mar 01 COPS Usage for Policy Provisioning RFC3159 PS Aug 01 Structure of Policy Provisioning Information (SPPI) RFC3182 PS Nov 01 Identity Representation for RSVP RFC3181 PS Nov 01 Signaled Preemption Priority Policy Element RFC3318 I Mar 03 Framework Policy Information Base RFC3483 I Mar 03 Framework for Policy Usage Feedback for Common Open Policy Service with Policy Provisioning (COPS-PR) RFC3520 PS Apr 03 Session Authorization Policy Element RFC3521 I Apr 03 Framework for session set-up with Media Authorization RFC3571 I Aug 03 Framework Policy Information Base for Usage Feedback