< draft-sun-dime-itu-t-rw-01.txt   draft-sun-dime-itu-t-rw-02.txt >
Diameter Maintenance and D. Sun Diameter Maintenance and D. Sun
Extensions (DIME) Alcatel-Lucent Extensions (DIME) Alcatel-Lucent
Internet-Draft July 14, 2008 Internet-Draft November 10, 2008
Intended status: Informational Intended status: Informational
Expires: January 15, 2009 Expires: May 14, 2009
Diameter ITU-T Rw Policy Enforcement Interface Application Diameter ITU-T Rw Policy Enforcement Interface Application
draft-sun-dime-itu-t-rw-01.txt draft-sun-dime-itu-t-rw-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 15, 2009. This Internet-Draft will expire on May 14, 2009.
Abstract Abstract
This document describes the need for a new pair of IANA Diameter This document describes the need for a new pair of IANA Diameter
Command Codes and a new vendor-specific Application ID to be used in Command Codes to be used in a vendor-specific new application, namely
a vendor-specific new application, namely for the ITU-T Rec. Q.3303.3 for the ITU-T Rec. Q.3303.3 - Rw interface used to send a request/
- Rw interface used to send a request/responses for controlling the responses for authorizing network QoS resources and policy
policy enforcement in a network element, as one of the enforcement in a network element, as one of the recommendations of
recommendations of the International Telecommunication Union - the International Telecommunication Union - Telecommunication
Telecommunication Standardization Sector (ITU-T). Standardization Sector (ITU-T).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Diameter ITU-T Rw Policy Enforcement Interface . . . . . . . . 5 3. Diameter ITU-T Rw Policy Enforcement Interface . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
4.1. Application Identifier . . . . . . . . . . . . . . . . . . 6 4.1. Application Identifier . . . . . . . . . . . . . . . . . . 6
4.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . 6
4.3. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 6 4.3. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 6
skipping to change at page 3, line 8 skipping to change at page 3, line 8
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . . 9 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . . 9 7.2. Informative References . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . . . . 11 Intellectual Property and Copyright Statements . . . . . . . . . . 11
1. Introduction 1. Introduction
This document summarizes the use of Diameter codes in a newly defined This document summarizes the use of Diameter codes in a newly defined
realization of a specification for controlling the policy realization of a specification for authorizing network QoS resources
enforcement. A new pair of Command Codes and a new vendor-specific and policy enforcement. A new pair of Command Codes is requested to
Application ID are requested to be assigned by IANA. The document be assigned by IANA. The document summarizes the uses of newly
summarizes the uses of newly defined Diameter codes (Command Codes, defined Diameter codes (Command Codes, AVP, vendor-specific
AVP, vendor-specific application id). When combined with the application id). When combined with the Diameter Base protocol, this
Diameter Base protocol, this application's specification [Q.3303.3] application's specification [Q.3303.3] satisfies the requirements of
satisfies the requirements of [Y.2111] of the International [Y.2111] of the International Telecommunication Union -
Telecommunication Union - Telecommunication Standardization Sector Telecommunication Standardization Sector (ITU-T) to send a request
(ITU-T) to send a request and receive a response for controlling the and receive a response for controlling the policy enforcement.
policy enforcement.
The Diameter realization of this application assumes the use of The Diameter realization of this application assumes the use of
Diameter Base protocol, as per RFC 3588, and extends it only for a Diameter Base protocol, as per RFC 3588, and extends it only for a
specific application using a vendor-id (ITU-T), a vendor-specific specific application using a vendor-id (ITU-T), a vendor-specific
application ID (TBD), a new Command Code (TBD), and new AVPs defined application ID (166777256), a new Command Code (TBD), and new AVPs
in the vendor-specific namespace. defined in the vendor-specific namespace.
This application is used to authorize network QoS resources and
policy enforcement (including amount of bandwidth, QoS class and
traffic flow processing) as an extension of the Diameter application
[RFC4006]. The request is based on the Diameter extensibility
discussions in the DIME WG that led to the conclusion that it is
better to define new Command Codes whenever the ABNF of a command is
modified by adding, removing or semantically changing required AVP in
order to avoid interoperability problems. The document is utilizing
authorization and accounting functionality and the entire exchange is
related to users utilizing applications that require QoS treatment.
This approach is consistent with the practice and experience gained
since the publication of [RFC3588] (see for example [RFC5224]) which
is now under revision by the DIME Working Group and will provide a
revised set of recommendations and procedures for IANA
considerations[draft-ietf-dime-3588bis].
2. Terminology 2. Terminology
The base Diameter specification [RFC3588] Section 1.4 defines most of The base Diameter specification [RFC3588] Section 1.4 defines most of
the terminology used in this document. Additionally, the terms and the terminology used in this document. Additionally, the terms and
acronyms defined in Section 3 and Section 4 of [Q.3303.3] are used in acronyms defined in Section 3 and Section 4 of [Q.3303.3] are used in
this document. this document.
3. Diameter ITU-T Rw Policy Enforcement Interface 3. Diameter ITU-T Rw Policy Enforcement Interface
The Rw interface is used for information exchange to apply policy The Rw interface is used for information exchange to apply policy
decisions between the Policy Decision Point (PDP) and the Policy decisions between the Policy Decision Point (PDP, i.e. Policy
Enforcement Point (PEP). Decision Functional Entity (PD-FE) in the ITU-T term) and the Policy
Enforcement Point (PEP, i.e. Policy Enforcement Functional Entity
(PE-FE) in the ITU-T term).
It allows the PDP to push the admission decisions to the PEP. It It allows the PDP to push the authorized admission decisions to the
also allows the PEP to request the admission decisions from the PDP PEP. It also allows the PEP to request the authorization of
when path-coupled resource reservation mechanisms are in use. The admission decisions from the PDP when path-coupled resource
main information is conveyed by the Rw interface: reservation mechanisms are in use. The main information is conveyed
by the Rw interface:
o Resources reservation and/or allocation request for media flows; o Resources reservation and/or allocation request for media flows;
o QoS handling request such as packet marking and policing to use; o QoS handling request such as packet marking and policing;
o Gate control (opening/closing) request for a media flow; o Gate control (opening/closing) request for a media flow;
o NAPT and NAT traversal requesting the necessary address mapping o NAPT and NAT traversal request for the necessary address mapping
information; information;
o Resource usage information request and report for media flows o Resource usage information request and report for media flows
The detailed descriptions of the Diameter Policy Enforcement The detailed descriptions of the Diameter Policy Enforcement
interface ITU-T Rw can be found in Section 5 of the [Q.3303.3]. interface ITU-T Rw can be found in Section 5 of the [Q.3303.3].
4. IANA Considerations 4. IANA Considerations
This section provides guidance to the Internet Assigned Numbers This section provides guidance to the Internet Assigned Numbers
Authority (IANA) regarding registration of values related to the Authority (IANA) regarding registration of values related to the
Diameter protocol, in accordance with BCP 26 [RFC5226]. Diameter protocol, in accordance with BCP 26 [RFC5226].
This document defines values in the namespaces that have been created This document defines values in the namespaces that have been created
and defined in the [RFC3588]. The IANA Considerations section of and defined in the [RFC3588]. The IANA Considerations section of
that document details the assignment criteria. Values assigned in that document details the assignment criteria. Values assigned in
this document, or by future IANA action, must be coordinated within this document, or by future IANA action, must be coordinated within
this shared namespace. this shared namespace.
4.1. Application Identifier 4.1. Application Identifier
IANA is requested to allocate a vendor-specific application ID for A vendor-specific application ID - 166777256 for the application
the application [Q.3303.3] from the 16777216-4294967294 range. [Q.3303.3] is assigned by the IANA.
Registry: Registry:
ID values Name Reference ID values Name Reference
---------------------------------------------- ----------------------------------------------------------
to be assigned ITU-T Rw Section 7.2.1 of ITU-T Q.3303.3 166777256 ITU-T Rw 7.2.1 of ITU-T Q.3303.3
4.2. Command Codes 4.2. Command Codes
IANA is requested to allocate command code values for the following IANA is requested to allocate command code values for the following
commands defined in Section 7.4 of [Q.3303.3] from the Command Code commands defined in Section 7.4 of [Q.3303.3] from the Command Code
namespace defined in [RFC3588]. namespace defined in [RFC3588].
Registry: Registry:
Code Value Name Reference Code Value Name Reference
to be assigned Policy-Install-Request (PIR) Section 7.4.1 of ITU-T Q.3303.3 ------------------------------------------------------------------
to be assigned Policy-Install-Answer (PIA) Section 7.4.2 of ITU-T Q.3303.3 to be assigned Policy-Install-Request(PIR) 7.4.1 of ITU-T Q.3303.3
to be assigned Policy-Install-Answer (PIA) 7.4.2 of ITU-T Q.3303.3
4.3. AVP Codes 4.3. AVP Codes
The values 1010~1018 are assigned by ITU-T to the following AVPs The values 1010~1018 are assigned by ITU-T to the following AVPs
within the ITU-T vendor-ID 11502 namespace: PI-Request-Type AVP, PI- within the ITU-T vendor-ID 11502 namespace: PI-Request-Type AVP, PI-
Request-Number AVP, Traffic-Descriptor-UL AVP, Traffic-Descriptor-DL Request-Number AVP, Traffic-Descriptor-UL AVP, Traffic-Descriptor-DL
AVP, Maximum-Burst-Size AVP, Committed-Data-Rate AVP, Committed- AVP, Maximum-Burst-Size AVP, Committed-Data-Rate AVP, Committed-
Burst-Size AVP, Excess-Burst-Size, Removal-Cause AVP. Burst-Size AVP, Excess-Burst-Size, Removal-Cause AVP.
See Table 1/Q.3303.3 in Section 7.3.1 of [Q.3303.3] for the detailed See Table 1/Q.3303.3 in Section 7.3.1 of [Q.3303.3] for the detailed
skipping to change at page 9, line 20 skipping to change at page 9, line 20
ITU-T Recommendation Q.3303.3, "Resource control protocol ITU-T Recommendation Q.3303.3, "Resource control protocol
no. 3 (rcp3): Protocol at the Rw interface between the no. 3 (rcp3): Protocol at the Rw interface between the
Policy Decision Physical Entity (PD-PE) and the Policy Policy Decision Physical Entity (PD-PE) and the Policy
Enforcement Physical Entity (PE-PE): Diameter", 2008. Enforcement Physical Entity (PE-PE): Diameter", 2008.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
7.2. Informative References 7.2. Informative References
[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
Loughney, "Diameter Credit-Control Application",
Auguest 2005.
[RFC5224] Brenner, M., "Diameter Policy Processing Application",
March 2008.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", May 2008. IANA Considerations Section in RFCs", May 2008.
[Y.2111] ITU-T Recommedation Y.2111, "Resource and admission [Y.2111] ITU-T Recommedation Y.2111, "Resource and admission
control functions in Next Generation Networks", control functions in Next Generation Networks",
September 2006. September 2006.
[draft-ietf-dime-3588bis]
Fajardo, V., Arkko, J., Loughney, J., and G. Zorn,
"Diameter Base Protocol", November 2008.
Author's Address Author's Address
Dong Sun Dong Sun
Alcatel-Lucent Alcatel-Lucent
600 Mountain Ave 600 Mountain Ave
Murray Hill, NJ 07974 Murray Hill, NJ 07974
USA USA
Phone: +1 908 582 2617 Phone: +1 908 582 2617
Email: dongsun@alcatel-lucent.com Email: dongsun@alcatel-lucent.com
 End of changes. 16 change blocks. 
39 lines changed or deleted 69 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/