| 1 |
<pre>Network Working Group M. Jones |
| 2 |
Request for Comments: 5516 Bridgewater Systems |
| 3 |
Category: Informational L. Morand |
| 4 |
Orange Labs |
| 5 |
April 2009 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">Diameter Command Code Registration for the</span> |
| 9 |
Third Generation Partnership Project (3GPP) Evolved Packet System (EPS) |
| 10 |
|
| 11 |
Status of This Memo |
| 12 |
|
| 13 |
This memo provides information for the Internet community. It does |
| 14 |
not specify an Internet standard of any kind. Distribution of this |
| 15 |
memo is unlimited. |
| 16 |
|
| 17 |
Copyright Notice |
| 18 |
|
| 19 |
Copyright (c) 2009 IETF Trust and the persons identified as the |
| 20 |
document authors. All rights reserved. |
| 21 |
|
| 22 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 23 |
Provisions Relating to IETF Documents in effect on the date of |
| 24 |
publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). |
| 25 |
Please review these documents carefully, as they describe your rights |
| 26 |
and restrictions with respect to this document. |
| 27 |
|
| 28 |
Abstract |
| 29 |
|
| 30 |
This document registers a set of IANA Diameter Command Codes to be |
| 31 |
used in new vendor-specific Diameter applications defined for the |
| 32 |
Third Generation Partnership Project (3GPP) Evolved Packet System |
| 33 |
(EPS). These new Diameter applications are defined for Mobile |
| 34 |
Management Entity (MME)- and Serving GPRS (General Packet Radio |
| 35 |
Service) Support Node (SGSN)-related interfaces in in the |
| 36 |
architecture for the Evolved 3GPP Packet Switched Domain, which is |
| 37 |
also known as the Evolved Packet System (EPS). |
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Jones & Morand Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc5516">RFC 5516</a> 3GPP EPS Command Codes April 2009</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-2">2</a> |
| 61 |
<a href="#section-3">3</a>. Command Codes ...................................................<a href="#page-3">3</a> |
| 62 |
<a href="#section-4">4</a>. IANA Considerations .............................................<a href="#page-3">3</a> |
| 63 |
<a href="#section-5">5</a>. Security Considerations .........................................<a href="#page-4">4</a> |
| 64 |
<a href="#section-6">6</a>. Acknowledgements ................................................<a href="#page-4">4</a> |
| 65 |
<a href="#section-7">7</a>. References ......................................................<a href="#page-5">5</a> |
| 66 |
<a href="#section-7.1">7.1</a>. Normative References .......................................<a href="#page-5">5</a> |
| 67 |
<a href="#section-7.2">7.2</a>. Informative References .....................................<a href="#page-5">5</a> |
| 68 |
|
| 69 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 70 |
|
| 71 |
The Third Generation Partnership Project (3GPP) is defining the |
| 72 |
Evolved 3GPP Packet Switched Domain - also known as the Evolved |
| 73 |
Packet System (EPS). As part of this architecture, the interfaces |
| 74 |
based on the Diameter protocol [<a href="./rfc3588" title=""Diameter Base Protocol"">RFC3588</a>] require the definition of |
| 75 |
two new Diameter applications. |
| 76 |
|
| 77 |
As defined in [<a href="#ref-TS29.272" title=""3GPP TS 29.272; Technical Specification Group Core Network and Terminals; Evolved Packet System; Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) Related Interfaces Based on Diameter Protocol"">TS29.272</a>], the 3GPP S6a/S6d application (vendor- |
| 78 |
specific application id: 16777251) enables the transfer of |
| 79 |
subscriber-related data between the Mobile Management Entity (MME) |
| 80 |
and the Home Subscriber Server (HSS) on the S6a interface and between |
| 81 |
the Serving GPRS Support Node (SGSN) and the Home Subscriber Server |
| 82 |
(HSS) on the S6d interface. |
| 83 |
|
| 84 |
Also defined in [<a href="#ref-TS29.272" title=""3GPP TS 29.272; Technical Specification Group Core Network and Terminals; Evolved Packet System; Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) Related Interfaces Based on Diameter Protocol"">TS29.272</a>], the 3GPP S13/S13' application (vendor- |
| 85 |
specific application id: 16777252) enables the Mobile Equipment |
| 86 |
Identity check procedure between the Mobile Management Entity (MME) |
| 87 |
and the Equipment Identity Register (EIR) on the S13 interface and |
| 88 |
between the Serving GPRS Support Node (SGSN) and the Equipment |
| 89 |
Identity Register (EIR) on the S13' interface. |
| 90 |
|
| 91 |
Both Diameter applications are defined under the 3GPP vendor-id |
| 92 |
"10415". This document defines the assigned values of the command |
| 93 |
codes used in these applications. |
| 94 |
|
| 95 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 96 |
|
| 97 |
The base Diameter specification (<a href="./rfc3588#section-1.3">Section 1.3 of [RFC3588]</a>) defines |
| 98 |
most of the terminology used in this document. Additionally, the |
| 99 |
terms and acronyms defined in [<a href="#ref-TS29.272" title=""3GPP TS 29.272; Technical Specification Group Core Network and Terminals; Evolved Packet System; Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) Related Interfaces Based on Diameter Protocol"">TS29.272</a>] are used in this document. |
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Jones & Morand Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc5516">RFC 5516</a> 3GPP EPS Command Codes April 2009</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Command Codes</span> |
| 114 |
|
| 115 |
The 3GPP S6a/S6d application described in Section 5 of [<a href="#ref-TS29.272" title=""3GPP TS 29.272; Technical Specification Group Core Network and Terminals; Evolved Packet System; Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) Related Interfaces Based on Diameter Protocol"">TS29.272</a>] |
| 116 |
requires the allocation of command code values for the following |
| 117 |
command pairs: |
| 118 |
|
| 119 |
o 3GPP-Update-Location-Request/Answer (ULR/ULA) |
| 120 |
|
| 121 |
o 3GPP-Cancel-Location-Request/Answer (CLR/CLA) |
| 122 |
|
| 123 |
o 3GPP-Authentication-Information-Request/ Answer (AIR/AIA) |
| 124 |
|
| 125 |
o 3GPP-Insert-Subscriber-Data-Request/Answer (IDR/IDA) |
| 126 |
|
| 127 |
o 3GPP-Delete-Subscriber-Data-Request/Answer (DSR/DSA) |
| 128 |
|
| 129 |
o 3GPP-Purge-UE-Request/Answer (PUR/PUA) |
| 130 |
|
| 131 |
o 3GPP-Reset-Request/Answer (RSR/RSA) |
| 132 |
|
| 133 |
o 3GPP-Notify-Request/Answer (NOR/NOA) |
| 134 |
|
| 135 |
The 3GPP S13/S13 application described in Section 6 of [<a href="#ref-TS29.272" title=""3GPP TS 29.272; Technical Specification Group Core Network and Terminals; Evolved Packet System; Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) Related Interfaces Based on Diameter Protocol"">TS29.272</a>] |
| 136 |
requires the allocation of a command code value for the following |
| 137 |
command pair: |
| 138 |
|
| 139 |
o 3GPP-ME-Identity-Check-Request/Answer (ECR/ECA) |
| 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 namespace that has been defined |
| 148 |
in the Diameter base specification [<a href="./rfc3588" title=""Diameter Base Protocol"">RFC3588</a>]. <a href="./rfc3588#section-11">Section 11 of |
| 149 |
[RFC3588]</a> (that document's IANA Considerations) details the |
| 150 |
assignment criteria. IANA allocated the following command code |
| 151 |
values: |
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Jones & Morand Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc5516">RFC 5516</a> 3GPP EPS Command Codes April 2009</span> |
| 167 |
|
| 168 |
|
| 169 |
+----------------------------------------------------------------------+ |
| 170 |
| Code Command Name Abbrev. Defined in | |
| 171 |
+----------------------------------------------------------------------+ |
| 172 |
| 316 3GPP-Update-Location-Request ULR 3GPP TS 29.272 | |
| 173 |
| 316 3GPP-Update-Location-Answer ULA 3GPP TS 29.272 | |
| 174 |
| 317 3GPP-Cancel-Location-Request CLR 3GPP TS 29.272 | |
| 175 |
| 317 3GPP-Cancel-Location-Answer CLA 3GPP TS 29.272 | |
| 176 |
| 318 3GPP-Authentication-Information-Request AIR 3GPP TS 29.272 | |
| 177 |
| 318 3GPP-Authentication-Information-Answer AIA 3GPP TS 29.272 | |
| 178 |
| 319 3GPP-Insert-Subscriber-Data-Request IDR 3GPP TS 29.272 | |
| 179 |
| 319 3GPP-Insert-Subscriber-Data-Answer IDA 3GPP TS 29.272 | |
| 180 |
| 320 3GPP-Delete-Subscriber-Data-Request DSR 3GPP TS 29.272 | |
| 181 |
| 320 3GPP-Delete-Subscriber-Data-Answer DSA 3GPP TS 29.272 | |
| 182 |
| 321 3GPP-Purge-UE-Request PUR 3GPP TS 29.272 | |
| 183 |
| 321 3GPP-Purge-UE-Answer PUA 3GPP TS 29.272 | |
| 184 |
| 322 3GPP-Reset-Request RSR 3GPP TS 29.272 | |
| 185 |
| 322 3GPP-Reset-Answer RSA 3GPP TS 29.272 | |
| 186 |
| 323 3GPP-Notify-Request NOR 3GPP TS 29.272 | |
| 187 |
| 323 3GPP-Notify-Answer NOA 3GPP TS 29.272 | |
| 188 |
| 324 3GPP-ME-Identity-Check-Request ECR 3GPP TS 29.272 | |
| 189 |
| 324 3GPP-ME-Identity-Check-Answer ECA 3GPP TS 29.272 | |
| 190 |
+----------------------------------------------------------------------+ |
| 191 |
|
| 192 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 193 |
|
| 194 |
This document describes command codes used in applications that build |
| 195 |
on top of the Diameter base protocol and the same security |
| 196 |
considerations described in [<a href="./rfc3588" title=""Diameter Base Protocol"">RFC3588</a>] are applicable to this |
| 197 |
document. No further extensions are required beyond the security |
| 198 |
mechanisms offered by [<a href="./rfc3588" title=""Diameter Base Protocol"">RFC3588</a>]. |
| 199 |
|
| 200 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span> |
| 201 |
|
| 202 |
We would like to thank the 3GPP CT4 delegates, Victor Fajardo, and |
| 203 |
Glen Zorn for their review and comments. We would also like to thank |
| 204 |
Dan Romascanu for volunteering to be AD sponsor and Hannes Tschofenig |
| 205 |
for volunteering to be Document Shepherd. |
| 206 |
|
| 207 |
|
| 208 |
|
| 209 |
|
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Jones & Morand Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc5516">RFC 5516</a> 3GPP EPS Command Codes April 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-RFC3588">RFC3588</a>] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. |
| 230 |
Arkko, "Diameter Base Protocol", <a href="./rfc3588">RFC 3588</a>, |
| 231 |
September 2003. |
| 232 |
|
| 233 |
[<a id="ref-TS29.272">TS29.272</a>] 3rd Generation Partnership Project, "3GPP TS 29.272; |
| 234 |
Technical Specification Group Core Network and Terminals; |
| 235 |
Evolved Packet System; Mobility Management Entity (MME) |
| 236 |
and Serving GPRS Support Node (SGSN) Related Interfaces |
| 237 |
Based on Diameter Protocol", |
| 238 |
<a href="http://www.3gpp.org/ftp/Specs/html-info/29272.htm">http://www.3gpp.org/ftp/Specs/html-info/29272.htm</a>. |
| 239 |
|
| 240 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span> |
| 241 |
|
| 242 |
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an |
| 243 |
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, |
| 244 |
May 2008. |
| 245 |
|
| 246 |
Authors' Addresses |
| 247 |
|
| 248 |
Mark Jones |
| 249 |
Bridgewater Systems |
| 250 |
|
| 251 |
EMail: [email protected] |
| 252 |
|
| 253 |
|
| 254 |
Lionel Morand |
| 255 |
Orange Labs |
| 256 |
|
| 257 |
EMail: [email protected] |
| 258 |
|
| 259 |
|
| 260 |
|
| 261 |
|
| 262 |
|
| 263 |
|
| 264 |
|
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
Jones & Morand Informational [Page 5] |
| 277 |
</pre> |