Debian Codegraph @

rfc5431.html

raw
1 <pre>Network Working Group D. Sun
2 Request for Comments: 5431 Alcatel-Lucent
3 Category: Informational March 2009
4
5
6 <span class="h1">Diameter ITU-T Rw Policy Enforcement Interface Application</span>
7
8 Status of This Memo
9
10 This memo provides information for the Internet community. It does
11 not specify an Internet standard of any kind. Distribution of this
12 memo is unlimited.
13
14 Copyright Notice
15
16 Copyright (c) 2009 IETF Trust and the persons identified as the
17 document authors. All rights reserved.
18
19 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
20 Provisions Relating to IETF Documents in effect on the date of
21 publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
22 Please review these documents carefully, as they describe your rights
23 and restrictions with respect to this document.
24
25 Abstract
26
27 This document describes the need for a new pair of IANA Diameter
28 Command Codes to be used in a vendor-specific new application, namely
29 for the ITU-T Rec. Q.3303.3 - Rw interface used to send a request/
30 response for authorizing network Quality of Service (QoS) resources
31 and policy enforcement in a network element, as one of the
32 recommendations of the International Telecommunication Union -
33 Telecommunication Standardization Sector (ITU-T).
34
35 Table of Contents
36
37 <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
38 <a href="#section-2">2</a>. Terminology .....................................................<a href="#page-2">2</a>
39 <a href="#section-3">3</a>. Diameter ITU-T Rw Policy Enforcement Interface ..................<a href="#page-3">3</a>
40 <a href="#section-4">4</a>. IANA Considerations .............................................<a href="#page-3">3</a>
41 <a href="#section-4.1">4.1</a>. Application Identifier .....................................<a href="#page-3">3</a>
42 <a href="#section-4.2">4.2</a>. Command Codes ..............................................<a href="#page-4">4</a>
43 <a href="#section-4.3">4.3</a>. AVP Codes ..................................................<a href="#page-4">4</a>
44 <a href="#section-5">5</a>. Security Considerations .........................................<a href="#page-4">4</a>
45 <a href="#section-6">6</a>. Acknowledgements ................................................<a href="#page-4">4</a>
46 <a href="#section-7">7</a>. References ......................................................<a href="#page-5">5</a>
47 <a href="#section-7.1">7.1</a>. Normative References .......................................<a href="#page-5">5</a>
48 <a href="#section-7.2">7.2</a>. Informative References .....................................<a href="#page-5">5</a>
49
50
51
52 <span class="grey">Sun Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc5431">RFC 5431</a> ITU-T Rw Interface March 2009</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
58
59 This document summarizes the use of Diameter codes in a newly defined
60 realization of a specification for authorizing network QoS resources
61 and policy enforcement [<a href="#ref-Q.3303.3" title="&quot;Resource control protocol no. 3 (rcp3): Protocol at the Rw interface between the Policy Decision Physical Entity (PD-PE) and the Policy Enforcement Physical Entity (PE-PE): Diameter&quot;">Q.3303.3</a>]. A new pair of Command Codes have
62 been assigned by IANA. This document summarizes the uses of newly
63 defined Diameter codes (Command Codes, AVP, vendor-specific
64 application id). When combined with the Diameter Base protocol, this
65 application's specification [<a href="#ref-Q.3303.3" title="&quot;Resource control protocol no. 3 (rcp3): Protocol at the Rw interface between the Policy Decision Physical Entity (PD-PE) and the Policy Enforcement Physical Entity (PE-PE): Diameter&quot;">Q.3303.3</a>] satisfies the requirements of
66 [<a href="#ref-Y.2111" title="&quot;Resource and admission control functions in Next Generation Networks&quot;">Y.2111</a>] of the International Telecommunication Union -
67 Telecommunication Standardization Sector (ITU-T) to send a request
68 and receive a response for controlling the policy enforcement.
69
70 The Diameter realization of this application assumes the use of the
71 Diameter Base protocol, as per <a href="./rfc3588">RFC 3588</a>, and extends it only for a
72 specific application using a vendor-id (ITU-T), a vendor-specific
73 application ID (16777256), a new Command Code (315), and new
74 attribute-value pairs (AVPs), which are defined in the vendor-
75 specific namespace.
76
77 This application is used to authorize network QoS resources and
78 policy enforcement (including the amount of bandwidth, QoS class, and
79 traffic flow processing) as an extension of the Diameter application
80 [<a href="./rfc4006" title="&quot;Diameter Credit-Control Application&quot;">RFC4006</a>]. The request is based on the Diameter extensibility
81 discussions in the DIME WG that led to the conclusion that it is
82 better to define new Command Codes whenever the ABNF of a command is
83 modified by adding, removing, or semantically changing a required AVP
84 in order to avoid interoperability problems. The document is
85 utilizing authorization and accounting functionality, and the entire
86 exchange is related to users utilizing applications that require QoS
87 treatment. This approach is consistent with the practice and
88 experience gained since the publication of [<a href="./rfc3588" title="&quot;Diameter Base Protocol&quot;">RFC3588</a>] (see for example
89 [<a href="./rfc5224" title="&quot;Diameter Policy Processing Application&quot;">RFC5224</a>]), which is now under revision by the DIME Working Group who
90 will provide a revised set of recommendations and procedures for IANA
91 considerations [<a href="#ref-DIME" title="&quot;Diameter Base Protocol&quot;">DIME</a>].
92
93 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
94
95 In the base Diameter specification <a href="./rfc3588#section-1.4">[RFC3588], Section&nbsp;1.4</a> defines
96 most of the terminology used in this document. Additionally, the
97 terms and acronyms defined in <a href="#section-3">Section 3</a> and Section 4 of [<a href="#ref-Q.3303.3" title="&quot;Resource control protocol no. 3 (rcp3): Protocol at the Rw interface between the Policy Decision Physical Entity (PD-PE) and the Policy Enforcement Physical Entity (PE-PE): Diameter&quot;">Q.3303.3</a>]
98 are used in this document.
99
100
101
102
103
104
105
106
107
108 <span class="grey">Sun Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc5431">RFC 5431</a> ITU-T Rw Interface March 2009</span>
111
112
113 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Diameter ITU-T Rw Policy Enforcement Interface</span>
114
115 The Rw interface is used for information exchange to apply policy
116 decisions between the Policy Decision Point (PDP, i.e., in the ITU-T
117 term, Policy Decision Functional Entity (PD-FE)) and the Policy
118 Enforcement Point (PEP, i.e., in the ITU-T term, Policy Enforcement
119 Functional Entity (PE-FE)).
120
121 The interface allows the PDP to push the authorized admission
122 decisions to the PEP. It also allows the PEP to request the
123 authorization of admission decisions from the PDP when path-coupled
124 resource reservation mechanisms are in use. The main information
125 conveyed by the Rw interface is:
126
127 o Resources reservation and/or allocation requests for media flows;
128
129 o QoS handling requests such as packet marking and policing;
130
131 o Gate control (opening/closing) requests for a media flow;
132
133 o NAPT and NAT traversal requests for the necessary address mapping
134 information;
135
136 o Resource usage information requests and reports for media flows.
137
138 The detailed descriptions of the Diameter Policy Enforcement
139 interface ITU-T Rw can be found in Section 5 of [<a href="#ref-Q.3303.3" title="&quot;Resource control protocol no. 3 (rcp3): Protocol at the Rw interface between the Policy Decision Physical Entity (PD-PE) and the Policy Enforcement Physical Entity (PE-PE): Diameter&quot;">Q.3303.3</a>].
140
141 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
142
143 This section provides guidance to the Internet Assigned Numbers
144 Authority (IANA) regarding registration of values related to the
145 Diameter protocol, in accordance with <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a> [<a href="./rfc5226" title="">RFC5226</a>].
146
147 This document defines values in the namespaces that have been created
148 and defined in [<a href="./rfc3588" title="&quot;Diameter Base Protocol&quot;">RFC3588</a>]. The IANA Considerations section of that
149 document details the assignment criteria. Values assigned in this
150 document, or by future IANA action, must be coordinated within this
151 shared namespace.
152
153 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Application Identifier</span>
154
155 A vendor-specific application ID (16777256) for the application of
156 [<a href="#ref-Q.3303.3" title="&quot;Resource control protocol no. 3 (rcp3): Protocol at the Rw interface between the Policy Decision Physical Entity (PD-PE) and the Policy Enforcement Physical Entity (PE-PE): Diameter&quot;">Q.3303.3</a>] has been assigned by the IANA.
157
158
159
160
161
162
163
164 <span class="grey">Sun Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc5431">RFC 5431</a> ITU-T Rw Interface March 2009</span>
167
168
169 Registry:
170 ID values Name Reference
171 ----------------------------------------------------------
172 16777256 ITU-T Rw 7.2.1 of ITU-T Q.3303.3
173
174
175 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Command Codes</span>
176
177 IANA has allocated Command Code values for the following commands
178 defined in Section 7.4 of [<a href="#ref-Q.3303.3" title="&quot;Resource control protocol no. 3 (rcp3): Protocol at the Rw interface between the Policy Decision Physical Entity (PD-PE) and the Policy Enforcement Physical Entity (PE-PE): Diameter&quot;">Q.3303.3</a>] from the Command Code namespace
179 defined in [<a href="./rfc3588" title="&quot;Diameter Base Protocol&quot;">RFC3588</a>].
180
181 Registry:
182 Code Value Name Reference
183 ------------------------------------------------------------------
184 315 Policy-Install-Request(PIR) 7.4.1 of ITU-T Q.3303.3
185 315 Policy-Install-Answer (PIA) 7.4.2 of ITU-T Q.3303.3
186
187 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. AVP Codes</span>
188
189 The values 1010~1018 are assigned by the ITU-T to the following AVPs
190 within the ITU-T vendor-ID 11502 namespace: PI-Request-Type AVP, PI-
191 Request-Number AVP, Traffic-Descriptor-UL AVP, Traffic-Descriptor-DL
192 AVP, Maximum-Burst-Size AVP, Committed-Data-Rate AVP, Committed-
193 Burst-Size AVP, Excess-Burst-Size, Removal-Cause AVP.
194
195 See Table 1/Q.3303.3 in Section 7.3.1 of [<a href="#ref-Q.3303.3" title="&quot;Resource control protocol no. 3 (rcp3): Protocol at the Rw interface between the Policy Decision Physical Entity (PD-PE) and the Policy Enforcement Physical Entity (PE-PE): Diameter&quot;">Q.3303.3</a>] for detailed
196 information on AVP codes, value types, and flag rules.
197
198 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
199
200 This document describes the Diameter Policy Enforcement Application.
201 It builds on top of the Diameter Base protocol and the same security
202 considerations described in [<a href="./rfc3588" title="&quot;Diameter Base Protocol&quot;">RFC3588</a>] are applicable to this
203 document. No further extensions are required beyond the security
204 mechanisms offered by [<a href="./rfc3588" title="&quot;Diameter Base Protocol&quot;">RFC3588</a>].
205
206 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
207
208 The author would like to thank Dan Romascanu, Hannes Tschofenig, and
209 Tina Tsou for their help and support. Finally, the author would like
210 to thank Alcatel-Lucent, as most of the effort put into this document
211 was done while he was in their employ.
212
213
214
215
216
217
218
219
220 <span class="grey">Sun Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc5431">RFC 5431</a> ITU-T Rw Interface March 2009</span>
223
224
225 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
226
227 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
228
229 [<a id="ref-Q.3303.3">Q.3303.3</a>] ITU-T Recommendation Q.3303.3, "Resource control protocol
230 no. 3 (rcp3): Protocol at the Rw interface between the
231 Policy Decision Physical Entity (PD-PE) and the Policy
232 Enforcement Physical Entity (PE-PE): Diameter", 2008.
233
234 [<a id="ref-RFC3588">RFC3588</a>] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
235 Arkko, "Diameter Base Protocol", <a href="./rfc3588">RFC 3588</a>,
236 September 2003.
237
238 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
239
240 [<a id="ref-DIME">DIME</a>] Fajardo, V., Arkko, J., Loughney, J., and G. Zorn,
241 "Diameter Base Protocol", Work in Progress,
242 November 2008.
243
244 [<a id="ref-RFC4006">RFC4006</a>] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and
245 J. Loughney, "Diameter Credit-Control Application",
246 <a href="./rfc4006">RFC 4006</a>, August 2005.
247
248 [<a id="ref-RFC5224">RFC5224</a>] Brenner, M., "Diameter Policy Processing Application",
249 <a href="./rfc5224">RFC 5224</a>, March 2008.
250
251 [<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
252 IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
253 May 2008.
254
255 [<a id="ref-Y.2111">Y.2111</a>] ITU-T Recommedation Y.2111, "Resource and admission
256 control functions in Next Generation Networks",
257 September 2006.
258
259 Author's Address
260
261 Dong Sun
262 Alcatel-Lucent
263 600 Mountain Ave
264 Murray Hill, NJ 07974
265 USA
266
267 Phone: +1 908 582 2617
268 EMail: [email protected]
269
270
271
272
273
274
275
276 Sun Informational [Page 5]
277 </pre>