Current Meeting Report
Slides
2.3.16 Resource Allocation Protocol (rap)
NOTE: This charter is a snapshot of the 52nd IETF Meeting in Salt Lake City, Utah USA. It
may now be out-of-date. Last Modified:
04-Dec-01
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: ftp://ops.ietf.org/pub/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. |
| Jul 01 | | Submit FRWKPIB to IESG for consideration as a Proposed Standard |
| Done | | Submit COPSTLS as informational draft |
| Done | | Submit First draft RSVPPIB |
| Done | | Submit Update draft FEEDBACKPIB |
| Done | | Submit First draft SESSIONAUTH |
| Done | | Submit First draft RSVPERRVAL |
| Done | | Submit I-D defining framework of COPS-PR PIB for feedback usage |
| Jul 01 | | Submit First draft COPSFRWK |
| Jul 01 | | Submit Update draft RSVPPIB |
| Jul 01 | | Submit Update draft RSVPERRVAL |
| Done | | Submit Update draft SESSIONAUTH |
| Done | | Submit First draft BINDFRWK |
| Done | | Submit First draft of FEEDBACKFRWK |
| Done | | Submit First draft NEWIDENTITY |
| Sep 01 | | Submit Update draft NEWIDENTITY |
| Oct 01 | | Submit Update draft FEEDBACKFRWK |
| Oct 01 | | Submit Update draft COPSFRWK |
| Jan 02 | | FEEDBACKFRWK Draft to to AD/IESG for consideration as Proposed Standard |
| Jan 02 | | FEEDBACKPIB Draft to to AD/IESG for consideration as Proposed Standard |
| Jan 02 | | RSVPPIB Draft to AD/IESG for consideration as Proposed Standard |
| Jan 02 | | NEWIDENTITY Draft to to AD/IESG for consideration as Proposed Standard |
| Jan 02 | | RSVPERRVAL Draft to to AD/IESG for consideration as Proposed Standard |
| Jan 02 | | SESSIONAUTH Draft to to AD/IESG for consideration as Proposed Standard |
| Jan 02 | | COPSFRWK Draft to to AD/IESG for consideration as Proposed Standard |
| Jan 02 | | COPSFRWK Draft to to AD/IESG for consideration as Proposed Standard |
Internet-Drafts:
Request For Comments:
| RFC | Status | Title |
|
| RFC2748 | PS | The COPS (Common Open Policy Service) Protocol |
| RFC2749 | PS | COPS usage for RSVP |
| RFC2750 | PS | RSVP Extensions for Policy Control |
| RFC2753 | | A Framework for Policy-based Admission Control |
| RFC2872 | PS | Application and Sub Application Identity Policy Element
for Use with RSVP |
| RFC2940 | PS | Definitions of Managed Objects for Common Open Policy
Service (COPS) Protocol Clients |
| RFC3084 | PS | COPS Usage for Policy Provisioning |
| RFC3159 | PS | Structure of Policy Provisioning Information (SPPI) |
| RFC3182 | PS | Identity Representation for RSVP |
| RFC3181 | PS | Signaled Preemption Priority Policy Element |
Current Meeting Report
RAP WG Meeting Minutes from the 52nd IETF
Co-Chairs:
Scott Hahn
Mark Stevens not present - Kwok Ho Chan (acting)
Note Taker: David Durham.
Agenda:
WG status
Framework of COPS-PR policy usage feedback
Framework of COPS-PR policy information base for policy feedback
RSVP policy control criteria PIB
Framework for Binding Access Control to COPS provisioning
-------------------------------------
Framework PIB 06: Ravi Sahita:
Passed WG last call, a few minor edits, doesn't require new last call.
Issues addressed before WG last call from 05 draft:
Sending the entry request state on every request is not optimal.
RoleCombinations are reported by the PEP. Setting of these in the first place was not well defined. And Dynamic control over this required from the PDP.
The rolecombination association table must be reused to allow de-aggregating policies to different targets (one example is Ifindex).
Resolutions:
Described a method for sending incremental requests.
Described a usage section for PEP, PDP interaction regarding RoleCombination updates. Initial Rolecombinations reported to PDP may be device defined defaults.
A frawkRoleCombo base PRC is defined that the frwkifrolecombo PRC extends. This could be extended as required (not defined in draft 06) to support other interface identifiers other than ifIndex.
Added text to described outsourced and configuration contexts using COPS-PR/PIBS.
Other changes:
Added an internal flow label filter. Allows for optimization of classification of PEP internal flows.
Added marker branch and defined 802 and Internal Flow label marker PRCs. These can be referenced from a data path of any policy.
Defined the frwkreference table to allow cross context referencing for shared PRIs.
Defined the frwkErrorTable that the PDP uses to send errors to the PEP in response to a problem with the Request message.
Updated frwkIPfilter to reuse TCs in rfc2851.
Added abstract.
Next steps: Cleared WG last call. Submit07 IETF drafts to IESG.
Questions?
Scott: clarify rolecombo modification. Ravi: allows PDP to control Role Combination assignments to interfaces.
Question: Are Multiple outsourced contexts on different or the same connection. Ravi: On the same connection. Open a different handle/client type w/ different namespace.
--------------------------------------------
Kwok Chan: UMTS Go PIB:
Bert: Is this WG charter work? Scott, No, in 3GPP, but Kwok is here as a liaison.
Purpose: Informational Purpose. Indication of related on going work in 3GPP. 3GPP has decided to adopt COPS for UMTS. Using COPS for access control, QoS and accounting in 3G wireless network.
Collaboration between 3GPP and IETF. Allow 3GPP build upon IETF technology. RAP WG FEEDBACK AND RATIFICATION of usage of RAP WG technology.
Prevents divergence of COPS-PR usage between IETF and 3GPP.
Go interface requirements:
Service based policy control of :
Diffserv inter-working with external networks
UMTS bearer authorization
Gating function
QOS charging related functions
Requested QoS & admission control based on:
UMTS specific layer 2 signaling.
What's new:
Combined COPS-PR usage for provisioning and outsourcing. Using COPSPR to provision the event handler. Using COPSPR to handle the outsourced event.
Creating a new UMTS Go PIB with objects: to describe event handling. To describe the outsource event. To describe the decision of the outsourced event. To describe the termini nation of the outsourced event. To describe the resource used for the outsourced event. ALLOW RESOURCE ALLOCATION to be done correctly.
Reuse of existing PIBs. Will import Framework and Diffserv PIB. Intention to import parts of Feedback Framework PIB.
3GPP standardized COPS-PR as the protocol for the 3GIO interface!!!
Interaction with IETF Documents: The overall framework is based on the Session authorization draft currently under review by the RAP WG.
Issues: Usage of Feedback Framework PIB to be worked out. Coordination with Access Bind PIB.
Next Steps: Gain advice from RAP WG on usage of COPS-PR and PIB.
3GPP will publish a final version of the UMTS Go PIB in March 2002.
3GPP will then ask the RAP WG to ratify it as an informational RFC.
Questions:
Where to get URL for the documentation? Kwok: Pointers are in the UMTS draft.
Information or RFC? Which one is it? Kwok: UMTS PIB.
Scott: Does Informational mean it needs to be a WG document. Bert: Refers to MIB doctors. Not a WG item. May need a PIB doctor. But that's independent of this WG. Bert has No problem with informational drafts being individual contributions. Need to have a separate PIB mailing list. WG mailing list should have discussions over what's on WG charter. Need to create a PIB mailing list.
-----------------------------------------
Diana Rawlins:
COPS Policy Feedback Framework and PIB update:
1. Regarding what to report: Expanded what drives the feedback notifications (REPORT Type accounting)
2. Regarding what to monitor: Permit option to specify arbitrary conditions.
See Diana's slides for details.
Questions:
Kwok. What is the time frame to complete WG last call on this? Diana: Trying to keep with the WG schedule.
RSVP Policy PIB:
Expanded to include Intserv over DiffServ networks policy control. 4 additional PRCs: Intsrv to DiffServ inter-working function table. Admission control Virtual Table. Virtual Pool Usage Table. Edge Point Identification Table.
Next Steps: Optimize the association of filter policies with authorization policies. Session Stats Table - usage.
No time was provided for questions.
--------------------------------------
Walter Weiss: Update on the Access Bind PIB.
Based on extending the DiffServ model and Framework to allow for access control within a PEP's data path elements. New flows can be outsourced for access control purposes, and then QOS and other data path characteristics can be assigned to that flow by the PDP based on access request. Hierarchical classifiers enable classifiers for a specific user to a set of classifiers for specific services for that user. Outstanding issues, using multiple handles allows for the deserialization of messaging between PEP & PDP. COPS(RSVP) normalization: RSVP specific filter specification & separating session scope and session trigger criterion.... Working on harmonizing COPS-RSVP with COPS-PR. Also doing a Use case for Wireless applications.
--------------------------------------
Shai Herzog: COPS Unified Model:
The unification is/was always part of the RAP standards. Work goal is to not change the COPS standards, but to provide a unified usage model. LDP never found its way into subsequent drafts, LDP is the unifying layer that ties together outsourcing & PEP's "smarts". Don't need any protocol changes, just clarification of usage. In summary, Shai agrees with Walter's approach in the Access BIND PIB... But not just a bind draft, but should be a general usage model... Walter's says this usage model is already in the Framework.
Slides
Framework PIB 06
Update: COPS Policy Feedback Framework and PIB
Framework for Binding Access Control to COPS Provisioning
RSVP Policy Control Criteria PIB
UMTS Go PIB