idnits 2.17.1 draft-sun-dime-itu-t-rw-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 246. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 257. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 264. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 270. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 10, 2008) is 5646 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3588 (Obsoleted by RFC 6733) -- Obsolete informational reference (is this intentional?): RFC 4006 (Obsoleted by RFC 8506) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Diameter Maintenance and D. Sun 3 Extensions (DIME) Alcatel-Lucent 4 Internet-Draft November 10, 2008 5 Intended status: Informational 6 Expires: May 14, 2009 8 Diameter ITU-T Rw Policy Enforcement Interface Application 9 draft-sun-dime-itu-t-rw-02.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on May 14, 2009. 36 Abstract 38 This document describes the need for a new pair of IANA Diameter 39 Command Codes to be used in a vendor-specific new application, namely 40 for the ITU-T Rec. Q.3303.3 - Rw interface used to send a request/ 41 responses for authorizing network QoS resources and policy 42 enforcement in a network element, as one of the recommendations of 43 the International Telecommunication Union - Telecommunication 44 Standardization Sector (ITU-T). 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 50 3. Diameter ITU-T Rw Policy Enforcement Interface . . . . . . . . 5 51 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 52 4.1. Application Identifier . . . . . . . . . . . . . . . . . . 6 53 4.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . 6 54 4.3. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 6 55 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 56 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 57 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 58 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9 59 7.2. Informative References . . . . . . . . . . . . . . . . . . 9 60 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 61 Intellectual Property and Copyright Statements . . . . . . . . . . 11 63 1. Introduction 65 This document summarizes the use of Diameter codes in a newly defined 66 realization of a specification for authorizing network QoS resources 67 and policy enforcement. A new pair of Command Codes is requested to 68 be assigned by IANA. The document summarizes the uses of newly 69 defined Diameter codes (Command Codes, AVP, vendor-specific 70 application id). When combined with the Diameter Base protocol, this 71 application's specification [Q.3303.3] satisfies the requirements of 72 [Y.2111] of the International Telecommunication Union - 73 Telecommunication Standardization Sector (ITU-T) to send a request 74 and receive a response for controlling the policy enforcement. 76 The Diameter realization of this application assumes the use of 77 Diameter Base protocol, as per RFC 3588, and extends it only for a 78 specific application using a vendor-id (ITU-T), a vendor-specific 79 application ID (166777256), a new Command Code (TBD), and new AVPs 80 defined in the vendor-specific namespace. 82 This application is used to authorize network QoS resources and 83 policy enforcement (including amount of bandwidth, QoS class and 84 traffic flow processing) as an extension of the Diameter application 85 [RFC4006]. The request is based on the Diameter extensibility 86 discussions in the DIME WG that led to the conclusion that it is 87 better to define new Command Codes whenever the ABNF of a command is 88 modified by adding, removing or semantically changing required AVP in 89 order to avoid interoperability problems. The document is utilizing 90 authorization and accounting functionality and the entire exchange is 91 related to users utilizing applications that require QoS treatment. 92 This approach is consistent with the practice and experience gained 93 since the publication of [RFC3588] (see for example [RFC5224]) which 94 is now under revision by the DIME Working Group and will provide a 95 revised set of recommendations and procedures for IANA 96 considerations[draft-ietf-dime-3588bis]. 98 2. Terminology 100 The base Diameter specification [RFC3588] Section 1.4 defines most of 101 the terminology used in this document. Additionally, the terms and 102 acronyms defined in Section 3 and Section 4 of [Q.3303.3] are used in 103 this document. 105 3. Diameter ITU-T Rw Policy Enforcement Interface 107 The Rw interface is used for information exchange to apply policy 108 decisions between the Policy Decision Point (PDP, i.e. Policy 109 Decision Functional Entity (PD-FE) in the ITU-T term) and the Policy 110 Enforcement Point (PEP, i.e. Policy Enforcement Functional Entity 111 (PE-FE) in the ITU-T term). 113 It allows the PDP to push the authorized admission decisions to the 114 PEP. It also allows the PEP to request the authorization of 115 admission decisions from the PDP when path-coupled resource 116 reservation mechanisms are in use. The main information is conveyed 117 by the Rw interface: 119 o Resources reservation and/or allocation request for media flows; 120 o QoS handling request such as packet marking and policing; 121 o Gate control (opening/closing) request for a media flow; 122 o NAPT and NAT traversal request for the necessary address mapping 123 information; 124 o Resource usage information request and report for media flows 125 The detailed descriptions of the Diameter Policy Enforcement 126 interface ITU-T Rw can be found in Section 5 of the [Q.3303.3]. 128 4. IANA Considerations 130 This section provides guidance to the Internet Assigned Numbers 131 Authority (IANA) regarding registration of values related to the 132 Diameter protocol, in accordance with BCP 26 [RFC5226]. 134 This document defines values in the namespaces that have been created 135 and defined in the [RFC3588]. The IANA Considerations section of 136 that document details the assignment criteria. Values assigned in 137 this document, or by future IANA action, must be coordinated within 138 this shared namespace. 140 4.1. Application Identifier 142 A vendor-specific application ID - 166777256 for the application 143 [Q.3303.3] is assigned by the IANA. 145 Registry: 146 ID values Name Reference 147 ---------------------------------------------------------- 148 166777256 ITU-T Rw 7.2.1 of ITU-T Q.3303.3 150 4.2. Command Codes 152 IANA is requested to allocate command code values for the following 153 commands defined in Section 7.4 of [Q.3303.3] from the Command Code 154 namespace defined in [RFC3588]. 156 Registry: 157 Code Value Name Reference 158 ------------------------------------------------------------------ 159 to be assigned Policy-Install-Request(PIR) 7.4.1 of ITU-T Q.3303.3 160 to be assigned Policy-Install-Answer (PIA) 7.4.2 of ITU-T Q.3303.3 162 4.3. AVP Codes 164 The values 1010~1018 are assigned by ITU-T to the following AVPs 165 within the ITU-T vendor-ID 11502 namespace: PI-Request-Type AVP, PI- 166 Request-Number AVP, Traffic-Descriptor-UL AVP, Traffic-Descriptor-DL 167 AVP, Maximum-Burst-Size AVP, Committed-Data-Rate AVP, Committed- 168 Burst-Size AVP, Excess-Burst-Size, Removal-Cause AVP. 170 See Table 1/Q.3303.3 in Section 7.3.1 of [Q.3303.3] for the detailed 171 information of AVP codes, value type and flag rules. 173 5. Security Considerations 175 This document describes the Diameter Policy Enforcement Application. 176 It builds on top of the Diameter Base protocol and the same security 177 considerations described in [RFC3588] are applicable to this 178 document. No further extensions are required beyond the security 179 mechanisms offered by [RFC3588]. 181 6. Acknowledgements 183 The author would like to thank Dan Romascanu, Hannes Tschofenig and 184 Tina Tsou for their help and support. Finally, the author would like 185 to thank Alcatel-Lucent, as most of the effort put into this document 186 was done while he was in their employ. 188 7. References 190 7.1. Normative References 192 [Q.3303.3] 193 ITU-T Recommendation Q.3303.3, "Resource control protocol 194 no. 3 (rcp3): Protocol at the Rw interface between the 195 Policy Decision Physical Entity (PD-PE) and the Policy 196 Enforcement Physical Entity (PE-PE): Diameter", 2008. 198 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 199 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 201 7.2. Informative References 203 [RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. 204 Loughney, "Diameter Credit-Control Application", 205 Auguest 2005. 207 [RFC5224] Brenner, M., "Diameter Policy Processing Application", 208 March 2008. 210 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 211 IANA Considerations Section in RFCs", May 2008. 213 [Y.2111] ITU-T Recommedation Y.2111, "Resource and admission 214 control functions in Next Generation Networks", 215 September 2006. 217 [draft-ietf-dime-3588bis] 218 Fajardo, V., Arkko, J., Loughney, J., and G. Zorn, 219 "Diameter Base Protocol", November 2008. 221 Author's Address 223 Dong Sun 224 Alcatel-Lucent 225 600 Mountain Ave 226 Murray Hill, NJ 07974 227 USA 229 Phone: +1 908 582 2617 230 Email: dongsun@alcatel-lucent.com 232 Full Copyright Statement 234 Copyright (C) The IETF Trust (2008). 236 This document is subject to the rights, licenses and restrictions 237 contained in BCP 78, and except as set forth therein, the authors 238 retain all their rights. 240 This document and the information contained herein are provided on an 241 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 242 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 243 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 244 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 245 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 246 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 248 Intellectual Property 250 The IETF takes no position regarding the validity or scope of any 251 Intellectual Property Rights or other rights that might be claimed to 252 pertain to the implementation or use of the technology described in 253 this document or the extent to which any license under such rights 254 might or might not be available; nor does it represent that it has 255 made any independent effort to identify any such rights. Information 256 on the procedures with respect to rights in RFC documents can be 257 found in BCP 78 and BCP 79. 259 Copies of IPR disclosures made to the IETF Secretariat and any 260 assurances of licenses to be made available, or the result of an 261 attempt made to obtain a general license or permission for the use of 262 such proprietary rights by implementers or users of this 263 specification can be obtained from the IETF on-line IPR repository at 264 http://www.ietf.org/ipr. 266 The IETF invites any interested party to bring to its attention any 267 copyrights, patents or patent applications, or other proprietary 268 rights that may cover technology that may be required to implement 269 this standard. Please address the information to the IETF at 270 ietf-ipr@ietf.org.