datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Resource Allocation Protocol (rap)
(concluded WG)

Note: The data for concluded WGs is occasionally incorrect.
Group
Name: Resource Allocation Protocol
Acronym:rap
Area:Operations and Management Area (ops)
State: Concluded
Charter: charter-ietf-rap-01 (Approved)
Personnel
Chairs: Mark Stevens <mlstevens@rcn.com>
Scott Hahn <scott.hahn@intel.com>
Area Director: ?
Mailing List
Address:rap@ops.ietf.org
To Subscribe:rap-request@ops.ietf.org
Archive:https://ops.ietf.org/lists/rap

Charter for 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.

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 FRWKPIB to IESG for consideration as a Proposed Standard
Done
Submit COPSTLS as informational draft
Done
Submit First draft RSVPPIB
Done
Submit First draft SESSIONAUTH
Done
Submit First draft RSVPERRVAL
Done
Milestone Dropped: Submit First draft COPSFRWK
Done
Submit First draft of FEEDBACKFRWK
Done
Submit First draft NEWIDENTITY
Done
Milestone Dropped: Submit Update draft RSVPPIB
Done
Milestone Dropped: Submit Update draft RSVPERRVAL
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
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
RSVPPIB Draft to AD/IESG for consideration as Proposed Standard
Done
RSVPERRVAL Draft to to AD/IESG for consideration as Proposed Standard
Done
SESSIONAUTH 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 2004
Submit COPSTLS draft for consideration as Proposed Standard