Diameter ITU-T Rw Policy Enforcement Interface Application
RFC 5431
Document | Type |
RFC - Informational
(March 2009; No errata)
Was draft-sun-dime-itu-t-rw (individual in ops area)
|
|
---|---|---|---|
Author | Dong Sun | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5431 (Informational) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Dan Romascanu | ||
Send notices to | Hannes.Tschofenig@gmx.net |
Network Working Group D. Sun Request for Comments: 5431 Alcatel-Lucent Category: Informational March 2009 Diameter ITU-T Rw Policy Enforcement Interface Application Status of This Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Abstract This document describes the need for a new pair of IANA Diameter Command Codes to be used in a vendor-specific new application, namely for the ITU-T Rec. Q.3303.3 - Rw interface used to send a request/ response for authorizing network Quality of Service (QoS) resources and policy enforcement in a network element, as one of the recommendations of the International Telecommunication Union - Telecommunication Standardization Sector (ITU-T). Table of Contents 1. Introduction ....................................................2 2. Terminology .....................................................2 3. Diameter ITU-T Rw Policy Enforcement Interface ..................3 4. IANA Considerations .............................................3 4.1. Application Identifier .....................................3 4.2. Command Codes ..............................................4 4.3. AVP Codes ..................................................4 5. Security Considerations .........................................4 6. Acknowledgements ................................................4 7. References ......................................................5 7.1. Normative References .......................................5 7.2. Informative References .....................................5 Sun Informational [Page 1] RFC 5431 ITU-T Rw Interface March 2009 1. Introduction This document summarizes the use of Diameter codes in a newly defined realization of a specification for authorizing network QoS resources and policy enforcement [Q.3303.3]. A new pair of Command Codes have been assigned by IANA. This document summarizes the uses of newly defined Diameter codes (Command Codes, AVP, vendor-specific application id). When combined with the Diameter Base protocol, this application's specification [Q.3303.3] satisfies the requirements of [Y.2111] of the International Telecommunication Union - Telecommunication Standardization Sector (ITU-T) to send a request and receive a response for controlling the policy enforcement. The Diameter realization of this application assumes the use of the Diameter Base protocol, as per RFC 3588, and extends it only for a specific application using a vendor-id (ITU-T), a vendor-specific application ID (16777256), a new Command Code (315), and new attribute-value pairs (AVPs), which are defined in the vendor- specific namespace. This application is used to authorize network QoS resources and policy enforcement (including the 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 a 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 who will provide a revised set of recommendations and procedures for IANA considerations [DIME]. 2. Terminology In the base Diameter specification [RFC3588], Section 1.4 defines most of 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 this document. Sun Informational [Page 2] RFC 5431 ITU-T Rw Interface March 2009 3. Diameter ITU-T Rw Policy Enforcement InterfaceShow full document text