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