RFC 5516

RFC 5516: Diameter Command Code Registration for the 3GPP Evolved Packet System (EPS) 🎀

okay bestie, this one is a Network Working Group doc, and it's Informational 💅 (so it's sharing info, not setting a standard). It was written in April 2009 by M. Jones (Mark Jones, Bridgewater Systems) and L. Morand (Lionel Morand, Orange Labs) 🦋 It's the Diameter command code registration for the 3GPP Evolved Packet System (EPS), and it's giving "paperwork that makes the whole EPS work" ✨

Status of This Memo

this memo just provides information for the Internet community 🌸 it does not specify an Internet standard of any kind, and distribution is unlimited 💖

Copyright Notice

Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. 🎀

this doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication (http://trustee.ietf.org/license-info). pls read those carefully because they explain your rights and restrictions for this doc 🫶

Abstract ✨

so this doc registers a set of IANA Diameter Command Codes 🔥 they're for new vendor-specific Diameter applications defined for the 3GPP Evolved Packet System (EPS). those new apps cover the Mobile Management Entity (MME)- and Serving GPRS (General Packet Radio Service) Support Node (SGSN)-related interfaces in in the architecture for the Evolved 3GPP Packet Switched Domain, which is also known as the Evolved Packet System (EPS) 🧚

Table of Contents 🌈

1. Introduction ....................................................2
2. Terminology .....................................................2
3. Command Codes ...................................................3
4. IANA Considerations .............................................3
5. Security Considerations .........................................4
6. Acknowledgements ................................................4
7. References ......................................................5
   7.1. Normative References .......................................5
   7.2. Informative References .....................................5

1. Introduction 💖

okay so the 3GPP is defining the Evolved 3GPP Packet Switched Domain (aka the Evolved Packet System, EPS) 🍓 as part of this architecture, the interfaces based on the Diameter protocol [RFC3588] need two new Diameter applications. literally two, iykyk 💅

as defined in [TS29.272], the 3GPP S6a/S6d application (vendor-specific application id: 16777251) is the one that moves subscriber-related data between the Mobile Management Entity (MME) and the Home Subscriber Server (HSS) on the S6a interface, and between the Serving GPRS Support Node (SGSN) and the Home Subscriber Server (HSS) on the S6d interface 🦋

also defined in [TS29.272] is the 3GPP S13/S13' application (vendor-specific application id: 16777252). it handles the Mobile Equipment Identity check procedure between the Mobile Management Entity (MME) and the Equipment Identity Register (EIR) on the S13 interface, and between the Serving GPRS Support Node (SGSN) and the Equipment Identity Register (EIR) on the S13' interface 🔥

both Diameter apps live under the 3GPP vendor-id "10415" 👑 this doc defines the assigned values of the command codes used in these apps. ✨

2. Terminology 🧚

the base Diameter spec (Section 1.3 of [RFC3588]) defines most of the terminology in this doc 💅 on top of that, the terms and acronyms defined in [TS29.272] are used here too 🫶

3. Command Codes 🌸

the 3GPP S6a/S6d app described in Section 5 of [TS29.272] needs command code values allocated for these command pairs 💖

• 3GPP-Update-Location-Request/Answer (ULR/ULA)
• 3GPP-Cancel-Location-Request/Answer (CLR/CLA)
• 3GPP-Authentication-Information-Request/ Answer (AIR/AIA)
• 3GPP-Insert-Subscriber-Data-Request/Answer (IDR/IDA)
• 3GPP-Delete-Subscriber-Data-Request/Answer (DSR/DSA)
• 3GPP-Purge-UE-Request/Answer (PUR/PUA)
• 3GPP-Reset-Request/Answer (RSR/RSA)
• 3GPP-Notify-Request/Answer (NOR/NOA)

the 3GPP S13/S13 app described in Section 6 of [TS29.272] needs a command code value for this one command pair 🍓

• 3GPP-ME-Identity-Check-Request/Answer (ECR/ECA)

4. IANA Considerations 🎀

this section gives guidance to the Internet Assigned Numbers Authority (IANA) about registering values related to the Diameter protocol, following BCP 26 [RFC5226] 🦋

this doc defines values in the namespace that the Diameter base spec [RFC3588] already defined. Section 11 of [RFC3588] (that doc's IANA Considerations) has the assignment criteria 🧚 IANA allocated the following command code values 👑

+----------------------------------------------------------------------+
| Code Command Name                            Abbrev.  Defined in     |
+----------------------------------------------------------------------+
| 316  3GPP-Update-Location-Request            ULR      3GPP TS 29.272 |
| 316  3GPP-Update-Location-Answer             ULA      3GPP TS 29.272 |
| 317  3GPP-Cancel-Location-Request            CLR      3GPP TS 29.272 |
| 317  3GPP-Cancel-Location-Answer             CLA      3GPP TS 29.272 |
| 318  3GPP-Authentication-Information-Request AIR      3GPP TS 29.272 |
| 318  3GPP-Authentication-Information-Answer  AIA      3GPP TS 29.272 |
| 319  3GPP-Insert-Subscriber-Data-Request     IDR      3GPP TS 29.272 |
| 319  3GPP-Insert-Subscriber-Data-Answer      IDA      3GPP TS 29.272 |
| 320  3GPP-Delete-Subscriber-Data-Request     DSR      3GPP TS 29.272 |
| 320  3GPP-Delete-Subscriber-Data-Answer      DSA      3GPP TS 29.272 |
| 321  3GPP-Purge-UE-Request                   PUR      3GPP TS 29.272 |
| 321  3GPP-Purge-UE-Answer                    PUA      3GPP TS 29.272 |
| 322  3GPP-Reset-Request                      RSR      3GPP TS 29.272 |
| 322  3GPP-Reset-Answer                       RSA      3GPP TS 29.272 |
| 323  3GPP-Notify-Request                     NOR      3GPP TS 29.272 |
| 323  3GPP-Notify-Answer                      NOA      3GPP TS 29.272 |
| 324  3GPP-ME-Identity-Check-Request          ECR      3GPP TS 29.272 |
| 324  3GPP-ME-Identity-Check-Answer           ECA      3GPP TS 29.272 |
+----------------------------------------------------------------------+

5. Security Considerations 🔥

this doc describes command codes used in apps that build on top of the Diameter base protocol, and the same security considerations described in [RFC3588] apply here too 💀 no further extensions are required beyond the security mechanisms offered by [RFC3588], so [RFC3588] is carrying the security load 🫶

6. Acknowledgements 💜

the authors want to thank the 3GPP CT4 delegates, Victor Fajardo, and Glen Zorn for their review and comments 🌸 they also want to thank Dan Romascanu for volunteering to be AD sponsor, and Hannes Tschofenig for volunteering to be Document Shepherd ✨

7. References 🧚

7.1. Normative References

• [RFC3588]: Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
• [TS29.272]: 3rd Generation Partnership Project, "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", http://www.3gpp.org/ftp/Specs/html-info/29272.htm.

7.2. Informative References

• [RFC5226]: Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.

Authors' Addresses 💖

Mark Jones, Bridgewater Systems EMail: mark.jones@bridgewatersystems.com

Lionel Morand, Orange Labs EMail: lionel.morand@orange-ftgroup.com

---

that's the whole thing, bestie! 🌈🫶💅