Current Meeting Report
Slides
2.4.16 Resource Allocation Protocol (rap)
NOTE: This charter is a snapshot of the 54th IETF Meeting in Yokohama, Japan. It may now be out-of-date.
Last Modifield: 06/13/2002
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. |
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 First draft RSVPERRVAL |
Done | | Submit First draft SESSIONAUTH |
Done | | Submit I-D defining framework of COPS-PR PIB for feedback
usage |
Done | | Submit Update draft FEEDBACKPIB |
JUL 01 | | Submit First draft COPSFRWK |
JUL 01 | | Submit Update draft RSVPERRVAL |
JUL 01 | | Submit Update draft RSVPPIB |
Done | | Submit First draft NEWIDENTITY |
Done | | Submit First draft of FEEDBACKFRWK |
Done | | Submit Update draft SESSIONAUTH |
Done | | Submit First draft BINDFRWK |
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 | | COPSFRWK Draft to to AD/IESG for consideration as Proposed
Standard |
JAN 02 | | NEWIDENTITY Draft to to AD/IESG for consideration as
Proposed Standard |
JAN 02 | | RSVPPIB Draft 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 |
Internet-Drafts:
- draft-ietf-rap-frameworkpib-09.txt
- draft-ietf-rap-cops-tls-04.txt
- draft-ietf-rap-rsvp-authsession-03.txt
- draft-ietf-rap-session-auth-04.txt
- draft-ietf-rap-feedback-fr-pib-03.txt
- draft-ietf-rap-feedback-frwk-02.txt
- draft-ietf-rap-access-bind-01.txt
- draft-ietf-rap-cops-frwk-01.txt
- draft-ietf-rap-rsvppcc-pib-01.txt
Request For Comments:
RFC | Status | Title |
RFC2749 | PS | COPS usage for RSVP |
RFC2748 | PS | The COPS (Common Open Policy Service) Protocol |
RFC2750 | PS | RSVP Extensions for Policy Control |
RFC2753 | I | A Framework for Policy-based Admission Control |
RFC2751 | PS | Signaled Preemption Priority Policy Element |
RFC2752 | PS | Identity Representation for RSVP |
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
54th IETF - Resource Allocation Protocol WG
RAP Minutes
Tuesday July 16th 2002 1pm
Co-chairs: Scott Hahn, Mark Stevens (absent)
Notes submitted by Diana Rawlins and Ravi Sahita
Agenda (Agenda was posted on mailing list)
------
1) Agenda bashing.
2) Chair reviewed current drafts-
3) Diana Rawlins - RSVP PCC PIB, acct feedback drafts
4) Kwok Chan - cops framework
5) Yacine El Mghazli - COPS usage for SLS- complements RSVP auth session that has passed last call
6) Christian Jacquenet - Enforcing an IP TE policy: early implementation results
Current Status
-Framework PIB - RFC editor queue RFC 3318 v09
-IESG discussion since first PIBs coming out - hence made informational
-mgmt proposals are being reviewed, IAB meeting was held same time DiffServ PIB has gone thru the IESG, is in editors queue with RFC # 3317 - also informational.
-framework for session setup has gone thru the IESG - Louis Hamer has made changes and the draft is back with the IESG and will through pretty shortly
-Diana will talk about two drafts that are in the closing end the acct feedback framework and the associated PIB.
-COPS TLS asked for a particular port - IESG doesn't want to give out specific ports for TLS - new draft uses the redirect command to transfer a clear connection to a secure connection. Bert to get some feedback from security experts.
-Access Bind PIB is work in progress. COPS Framework - Kwok will talk about that shortly.
Diana Rawlins presented the update on the Feedback Framework and Feedback PIB. There were no changes since IETF 53 on the framework and she briefly went over the editorial and table changes in the revised Feedback PIB draft. She recommended, on behalf of the other co-authors, that the Feedback Framework and Feedback PIB be submitted for working group last call.
Kwok Ho Chan came to microphone to clarify that the DPE policies that were removed from the Feedback PIB were not needed because of later revisions to the Policy Framework PIB.
Diana Rawlins presented the update on the RSVP Policy Control Criteria PIB. No changes were made since IETF 53. The draft is ready for working group last call. But the draft includes feedback usage tables and is dependent on Feedback Framework and Feedback PIB. The RSVP Policy Control Criteria PIB draft is waiting on the feedback framework drafts go through working group last call before being submitted for working group last call.
Kwok Ho Chan gave an update on the working group item Architecture for COPS Based Policy Control Management Framework He went over the common COPS models, COPS-PR usage, inter-working RSVP outsourcing with provisioning and next steps.
Bert Wijnen questioned that the Management Framework appeared to be introducing new COPS models and non-chartered work. Kwok Chan and Scott Hahn clarified that the scope of the Management Framework is to describe existing COPS mechanisms only. It does not contain any new COPS functionality. Bert raised a question that the Management Framework was not addressing the fundamental usage of COPS-PR and PIB definitions that were needed in an architecture management framework document.
David Durham pointed out the while the COPS Management Framework was bounded to describing existing mechanisms such as inter-working between RSVP outsourcing and provisioning, it may stimulate examination of the RSVP Policy Control Criteria PIB and propose changes it.
Yacine El Mghazli presented a non-working group item titled " COPS-PR Usage for SLS" This provides Service Level Specification policies using a combination of the outsourcing and provisioning policy model.
Scott Hahn asked about the SLSTable being defined with a pib-access of INSTALL/ NOTIFY. The NOTIFY access mechanism in the SLSTable was to provide PDP with IP flow information from the PEP. Bert Wijnen also questioned the using the pib-access NOTIFY to gain flow information. Thi Mai Trang Nguyen, a co-author of the draft, explained that SLS needed to obtain IP flow information from the device. Diana Rawlins suggested that the authors consider using the feedback mechanism to obtain flow information rather than using the pib-access NOTIFY mechanism.
Christian Jacquenet presented performance test results of an implementation of an IP Traffic Engineering Policy Information Base. A base measurement of the time required to use command language interface to configure 12 Linux routers platforms was compared to the provisioning time required when using the IP Traffic Engineering Policy Base. The cli mechanism took approximately 1 hour and the TE PIB approach required approximately 5 minutes. This test did not have a full PEP implementation of the COPS-PR protocol and TE PIB. David Durham offered the opinion that it would have very likely taken less time if a full COPS PR implementation in the PEP had been tested. David Perkins asked if another protocol such as SNMP had been used to benchmark against the COPS. Glen Waters also asked this. Christian responded that he had not included SNMP in his testing since he didn't think SNMP would provide the configuration solution that he desired.
Slides
Agenda
Enforcing an IP TE policy: early implementation results
- Mohamed Boucadair
- Christian Jacquenet
IETF 54 Update COPS Policy Feedback Framework and PIB
- Martin Bokaemper
- Dinesh Duit
- Amol Kulkarni
- Diana Rawlins
IETF 54 Update RSVP Policy Control Criteria PIB
- Amol Kulkarni
- Richard McClain
- Diana Rawlins
- Lei Yao
COPS-PR usage for SLS negotiation
- Thi Mai Trang Nguyen
- Yacine El Mghazli
- Nadia Boukhatem
- Louis-Nicolas Hamer
- Nathalie Charton
- Guy Pujolle
COPS Framework for 54th IETF
- Kwok Ho Chan
- Louis-Nicolas Hamer