Resource Allocation Protocol (rap)

This Working Group did not meet

Last Modified: 2002-11-08

Chair(s):
Scott Hahn <scott.hahn@intel.com>
Mark Stevens <mlstevens@rcn.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: http://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
Sep 99  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
Jul 01  Submit First draft COPSFRWK
Jul 01  Submit Update draft RSVPPIB
Jul 01  Submit Update draft RSVPERRVAL
Done  Submit First draft of FEEDBACKFRWK
Done  Submit First draft NEWIDENTITY
Done  Submit Update draft SESSIONAUTH
Done  Submit First draft BINDFRWK
Done  Submit Update draft NEWIDENTITY
Done  Submit Update draft FEEDBACKFRWK
Done  Submit Update draft COPSFRWK
Jan 02  COPSFRWK Draft to to AD/IESG for consideration as Proposed Standard
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
Jan 03  BINDFRWK Draft to to AD/IESG for consideration as Proposed Standard
Internet-Drafts:
  • - draft-ietf-rap-cops-tls-06.txt
  • - draft-ietf-rap-access-bind-02.txt
    • Request For Comments:
    The COPS (Common Open Policy Service) Protocol (RFC 2748) (90906 bytes)
    COPS usage for RSVP (RFC 2749) (33477 bytes)
    RSVP Extensions for Policy Control (RFC 2750) (26379 bytes)
    Signaled Preemption Priority Policy Element (RFC 2751) (21451 bytes) obsoleted by RFC 3181
    Identity Representation for RSVP (RFC 2752) (33954 bytes) obsoleted by RFC 3182
    A Framework for Policy-based Admission Control (RFC 2753) (49763 bytes)
    Application and Sub Application Identity Policy Element for Use with RSVP (RFC 2872) (10933 bytes)
    Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol Clients (RFC 2940) (52427 bytes)
    COPS Usage for Policy Provisioning (RFC 3084) (79341 bytes)
    Structure of Policy Provisioning Information (SPPI) (RFC 3159) (78621 bytes)
    Identity Representation for RSVP (RFC 3182) (36544 bytes)
    Signaled Preemption Priority Policy Element (RFC 3181) (21990 bytes)
    Framework Policy Information Base (RFC 3318) (144530 bytes)
    Framework for Policy Usage Feedback for Common Open Policy Service with Policy Provisioning (COPS-PR) (RFC 3483) (19869 bytes)
    Session Authorization Policy Element (RFC 3520) (63445 bytes)
    Framework for session set-up with Media Authorization (RFC 3521) (59548 bytes)
    Framework Policy Information Base for Usage Feedback (RFC 3571) (70894 bytes)

    Current Meeting Report

    None received.

    Slides

    None received.