Diameter Command Code Registration for the Third Generation Partnership Project (3GPP) Evolved Packet System (EPS)
draft-jones-dime-3gpp-eps-command-codes-02
The information below is for an old version of the document that is already published as an RFC.
| Document | Type | RFC Internet-Draft (individual in ops area) | |
|---|---|---|---|
| Authors | Lionel Morand , Mark Jones | ||
| Last updated | 2015-10-14 (Latest revision 2009-03-06) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats | plain text html xml htmlized pdfized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | RFC 5516 (Informational) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Dan Romascanu | ||
| Send notices to | (None) |
draft-jones-dime-3gpp-eps-command-codes-02
Diameter Maintenance and M. Jones
Extensions (DIME) Bridgewater Systems
Internet-Draft L. Morand
Intended status: Informational Orange Labs
Expires: September 5, 2009 March 4, 2009
Diameter Command Code Registration for Third Generation Partnership
Project (3GPP) Evolved Packet System (EPS)
draft-jones-dime-3gpp-eps-command-codes-02
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 5, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
This document registers a set of IANA Diameter Command Codes to be
Jones & Morand Expires September 5, 2009 [Page 1]
Internet-Draft 3gpp-eps-command-codes March 2009
used in new vendor-specific Diameter applications defined for the
Third Generation Partnership Project (3GPP) Evolved Packet System
(EPS). These new Diameter applications are defined for Mobile
Management Entity (MME) and Serving GPRS Support Node (SGSN) related
interfaces in the Release 8 architecture.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
Jones & Morand Expires September 5, 2009 [Page 2]
Internet-Draft 3gpp-eps-command-codes March 2009
1. Introduction
The Third Generation Partnership Project (3GPP) is defining the
Evolved Packet System (EPS) as part of their Release 8 architecture.
As part of this architecture, the interfaces based on the Diameter
protocol [RFC3588] require the definition of two new Diameter
applications.
The 3GPP S6a/S6d application (vendor-specific application id:
1677251) enables the transfer of subscriber related data between the
Mobile Management Entity (MME) and Home Subscriber Server (HSS) on
the S6a interface and between the Serving GPRS Support Node (SGSN)
and Home Subscriber Server (HSS) on the S6d interface.
The 3GPP S13/S13' application (vendor-specific application id:
1677252) enables the Mobile Equipment Identity check procedure
between the Mobile Management Entity (MME) and Equipment Identity
Register (EIR) on the S13 interface and between the Serving GPRS
Support Node (SGSN) and Equipment Identity Register (EIR) on the S13'
interface.
Both Diameter applications are defined under the 3GPP vendor-id
"10415" and are defined in [TS29.272]. This document defines the
assigned values of the command codes used in these applications.
2. Terminology
The base Diameter specification (Section 1.4 of [RFC3588]) defines
most of the terminology used in this document. Additionally, the
terms and acronyms defined in [TS29.272] are used in this document.
3. Command Codes
The 3GPP S6a/S6d application described in section 5 of [TS29.272]
requires the allocation of command code values for the following
command pairs:
o 3GPP-Update-Location-Request/Answer (ULR/ULA)
o 3GPP-Cancel-Location-Request/Answer (CLR/CLA)
o 3GPP-Authentication-Information-Request/ Answer (AIR/AIA)
o 3GPP-Insert-Subscriber-Data-Request/Answer (IDR/IDA)
Jones & Morand Expires September 5, 2009 [Page 3]
Internet-Draft 3gpp-eps-command-codes March 2009
o 3GPP-Delete-Subscriber-Data-Request/Answer (DSR/DSA)
o 3GPP-Purge-UE-Request/Answer (PUR/PUA)
o 3GPP-Reset-Request/Answer (RSR/RSA)
o 3GPP-Notify-Request/Answer (NOR/NOA)
The 3GPP S13/S13 application described in section 6 of [TS29.272]
requires the allocation of a command code value for the following
command pair:
o 3GPP-ME-Identity-Check-Request/Answer (ECR/ECA)
4. IANA Considerations
This section provides guidance to the Internet Assigned Numbers
Authority (IANA) regarding registration of values related to the
Diameter protocol, in accordance with BCP 26 [RFC5226].
This document defines values in the namespace that has been defined
in the Diameter Base specification [RFC3588]. Section 11 of
[RFC3588] (IANA Considerations) details the assignment criteria.
IANA is requested to allocate the following command code values:
+----------------------------------------------------------------------+
| Code Command Name Abbrev. Defined in |
+----------------------------------------------------------------------+
| tbd 3GPP-Update-Location-Request ULR 3GPP TS 29.272 |
| tbd 3GPP-Update-Location-Answer ULA 3GPP TS 29.272 |
| tbd 3GPP-Cancel-Location-Request CLR 3GPP TS 29.272 |
| tbd 3GPP-Cancel-Location-Answer CLA 3GPP TS 29.272 |
| tbd 3GPP-Authentication-Information-Request AIR 3GPP TS 29.272 |
| tbd 3GPP-Authentication-Information-Answer AIA 3GPP TS 29.272 |
| tbd 3GPP-Insert-Subscriber-Data-Request IDR 3GPP TS 29.272 |
| tbd 3GPP-Insert-Subscriber-Data-Answer IDA 3GPP TS 29.272 |
| tbd 3GPP-Delete-Subscriber-Data-Request DSR 3GPP TS 29.272 |
| tbd 3GPP-Delete-Subscriber-Data-Answer DSA 3GPP TS 29.272 |
| tbd 3GPP-Purge-UE-Request PUR 3GPP TS 29.272 |
| tbd 3GPP-Purge-UE-Answer PUA 3GPP TS 29.272 |
| tbd 3GPP-Reset-Request RSR 3GPP TS 29.272 |
| tbd 3GPP-Reset-Answer RSA 3GPP TS 29.272 |
| tbd 3GPP-Notify-Request NOR 3GPP TS 29.272 |
| tbd 3GPP-Notify-Answer NOA 3GPP TS 29.272 |
| tbd 3GPP-ME-Identity-Check-Request ECR 3GPP TS 29.272 |
| tbd 3GPP-ME-Identity-Check-Answer ECA 3GPP TS 29.272 |
+----------------------------------------------------------------------+
Jones & Morand Expires September 5, 2009 [Page 4]
Internet-Draft 3gpp-eps-command-codes March 2009
5. Security Considerations
This document describes command codes used in applications which
build on top of the Diameter base protocol and the same security
considerations described in [RFC3588] are applicable to this
document. No further extensions are required beyond the security
mechanisms offered by [RFC3588].
6. Acknowledgements
We would like to thank the 3GPP CT4 delegates, Victor Fajardo and
Glen Zorn for their review and comments. We would also like 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 (Release 8)",
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
Jones & Morand Expires September 5, 2009 [Page 5]
Internet-Draft 3gpp-eps-command-codes March 2009
Lionel Morand
Orange Labs
Email: lionel.morand@orange-ftgroup.com
Jones & Morand Expires September 5, 2009 [Page 6]