< draft-jones-dime-3gpp-eps-command-codes-01.txt		draft-jones-dime-3gpp-eps-command-codes-02.txt >
	Diameter Maintenance and M. Jones		Diameter Maintenance and M. Jones
	Extensions (DIME) Bridgewater Systems		Extensions (DIME) Bridgewater Systems
	Internet-Draft L. Morand		Internet-Draft L. Morand
	Intended status: Informational Orange Labs		Intended status: Informational Orange Labs
	Expires: July 3, 2009 December 30, 2008		Expires: September 5, 2009 March 4, 2009
	Diameter Command Code Registration for Third Generation Partnership		Diameter Command Code Registration for Third Generation Partnership
	Project (3GPP) Evolved Packet System (EPS)		Project (3GPP) Evolved Packet System (EPS)
	draft-jones-dime-3gpp-eps-command-codes-01		draft-jones-dime-3gpp-eps-command-codes-02
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on July 3, 2009.		This Internet-Draft will expire on September 5, 2009.
	Copyright Notice		Copyright Notice
	Copyright (c) 2008 IETF Trust and the persons identified as the		Copyright (c) 2009 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents in effect on the date of
	(http://trustee.ietf.org/license-info) in effect on the date of		publication of this document (http://trustee.ietf.org/license-info).
	publication of this document. Please review these documents		Please review these documents carefully, as they describe your rights
	carefully, as they describe your rights and restrictions with respect		and restrictions with respect to this document.
	to this document.
	Abstract		Abstract
	This document registers a set of IANA Diameter Command Codes to be		This document registers a set of IANA Diameter Command Codes to be
	used in new vendor-specific Diameter applications defined for the		used in new vendor-specific Diameter applications defined for the
	Third Generation Partnership Project (3GPP) Evolved Packet System		Third Generation Partnership Project (3GPP) Evolved Packet System
	(EPS). These new Diameter applications are defined for MME and SGSN		(EPS). These new Diameter applications are defined for Mobile
	related interfaces in the Release 8 architecture.		Management Entity (MME) and Serving GPRS Support Node (SGSN) related
			interfaces in the Release 8 architecture.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . . 3		3. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . . 3
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
	5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4		5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4		6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5		7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	7.1. Normative References . . . . . . . . . . . . . . . . . . . 5		7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
	7.2. Informative References . . . . . . . . . . . . . . . . . . 5		7.2. Informative References . . . . . . . . . . . . . . . . . . 5
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
	1. Introduction		1. Introduction
	The Third Generation Partnership Project (3GPP) is defining the		The Third Generation Partnership Project (3GPP) is defining the
	Evolved Packet System (EPS) as part of their Release 8 architecture.		Evolved Packet System (EPS) as part of their Release 8 architecture.
	As part of this architecture, the interfaces based on the Diameter		As part of this architecture, the interfaces based on the Diameter
	protocol [RFC3588] require the definition of two new Diameter		protocol [RFC3588] require the definition of two new Diameter
	applications: the 3GPP S6a application (vendor-specific application
	id: 1677251) and 3GPP S13 application (vendor-specific application
	id: 1677252), both defined under the 3GPP vendor-id "10415". These
	Diameter applications are described in [TS29.272]. This document
	defines the assigned values of the command codes used in these
	applications.		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		2. Terminology
	The base Diameter specification (Section 1.4 of [RFC3588]) defines		The base Diameter specification (Section 1.4 of [RFC3588]) defines
	most of the terminology used in this document. Additionally, the		most of the terminology used in this document. Additionally, the
	terms and acronyms defined in [TS29.272] are used in this document.		terms and acronyms defined in [TS29.272] are used in this document.
	3. Command Codes		3. Command Codes
	The 3GPP S6a application described in [TS29.272] requires the		The 3GPP S6a/S6d application described in section 5 of [TS29.272]
	allocation of command code values for the following command pairs:		requires the allocation of command code values for the following
			command pairs:
	o Update-Location-Request/Answer (ULR/ULA)
	o Cancel-Location-Request/Answer (CLR/CLA)		o 3GPP-Update-Location-Request/Answer (ULR/ULA)
	o Authentication-Information-Request/ Answer (AIR/AIA)		o 3GPP-Cancel-Location-Request/Answer (CLR/CLA)
	o Insert-Subscriber-Data-Request/Answer (IDR/IDA)		o 3GPP-Authentication-Information-Request/ Answer (AIR/AIA)
	o Delete-Subscriber-Data-Request/Answer (DSR/DSA)		o 3GPP-Insert-Subscriber-Data-Request/Answer (IDR/IDA)
			o 3GPP-Delete-Subscriber-Data-Request/Answer (DSR/DSA)
	o Purge-UE-Request/Answer (PUR/PUA)		o 3GPP-Purge-UE-Request/Answer (PUR/PUA)
	o Reset-Request/Answer (RSR/RSA)		o 3GPP-Reset-Request/Answer (RSR/RSA)
	o Notify-Request/Answer (NOR/NOA)		o 3GPP-Notify-Request/Answer (NOR/NOA)
	The 3GPP S13 application described in [TS29.272] requires the		The 3GPP S13/S13 application described in section 6 of [TS29.272]
	allocation of a command code value for the following command pair:		requires the allocation of a command code value for the following
			command pair:
	o ME-Identity-Check-Request/Answer (ECR/ECA)		o 3GPP-ME-Identity-Check-Request/Answer (ECR/ECA)
	4. IANA Considerations		4. IANA Considerations
	This section provides guidance to the Internet Assigned Numbers		This section provides guidance to the Internet Assigned Numbers
	Authority (IANA) regarding registration of values related to the		Authority (IANA) regarding registration of values related to the
	Diameter protocol, in accordance with BCP 26 [RFC5226].		Diameter protocol, in accordance with BCP 26 [RFC5226].
	This document defines values in the namespace that has been defined		This document defines values in the namespace that has been defined
	in the Diameter Base specification [RFC3588]. Section 11 of		in the Diameter Base specification [RFC3588]. Section 11 of
	[RFC3588] (IANA Considerations) details the assignment criteria.		[RFC3588] (IANA Considerations) details the assignment criteria.
	skipping to change at page 4, line 14 ¶		skipping to change at page 4, line 27 ¶
	4. IANA Considerations		4. IANA Considerations
	This section provides guidance to the Internet Assigned Numbers		This section provides guidance to the Internet Assigned Numbers
	Authority (IANA) regarding registration of values related to the		Authority (IANA) regarding registration of values related to the
	Diameter protocol, in accordance with BCP 26 [RFC5226].		Diameter protocol, in accordance with BCP 26 [RFC5226].
	This document defines values in the namespace that has been defined		This document defines values in the namespace that has been defined
	in the Diameter Base specification [RFC3588]. Section 11 of		in the Diameter Base specification [RFC3588]. Section 11 of
	[RFC3588] (IANA Considerations) details the assignment criteria.		[RFC3588] (IANA Considerations) details the assignment criteria.
	IANA is requested to allocate the following command code values:		IANA is requested to allocate the following command code values:
	+---------------------------------------------------------------------+		+----------------------------------------------------------------------+
	| Code Command Name Abbreviation Defined in |		| Code Command Name Abbrev. Defined in |
	+---------------------------------------------------------------------+		+----------------------------------------------------------------------+
	| tbd Update-Location-Request ULR 3GPP TS 29.272 |		| tbd 3GPP-Update-Location-Request ULR 3GPP TS 29.272 |
	| tbd Update-Location-Answer ULA 3GPP TS 29.272 |		| tbd 3GPP-Update-Location-Answer ULA 3GPP TS 29.272 |
	| tbd Cancel-Location-Request CLR 3GPP TS 29.272 |		| tbd 3GPP-Cancel-Location-Request CLR 3GPP TS 29.272 |
	| tbd Cancel-Location-Answer CLA 3GPP TS 29.272 |		| tbd 3GPP-Cancel-Location-Answer CLA 3GPP TS 29.272 |
	| tbd Authentication-Information-Request AIR 3GPP TS 29.272 |		| tbd 3GPP-Authentication-Information-Request AIR 3GPP TS 29.272 |
	| tbd Authentication-Information-Answer AIA 3GPP TS 29.272 |		| tbd 3GPP-Authentication-Information-Answer AIA 3GPP TS 29.272 |
	| tbd Insert-Subscriber-Data-Request IDR 3GPP TS 29.272 |		| tbd 3GPP-Insert-Subscriber-Data-Request IDR 3GPP TS 29.272 |
	| tbd Insert-Subscriber-Data-Answer IDA 3GPP TS 29.272 |		| tbd 3GPP-Insert-Subscriber-Data-Answer IDA 3GPP TS 29.272 |
	| tbd Delete-Subscriber-Data-Request DSR 3GPP TS 29.272 |		| tbd 3GPP-Delete-Subscriber-Data-Request DSR 3GPP TS 29.272 |
	| tbd Delete-Subscriber-Data-Answer DSA 3GPP TS 29.272 |		| tbd 3GPP-Delete-Subscriber-Data-Answer DSA 3GPP TS 29.272 |
	| tbd Purge-UE-Request PUR 3GPP TS 29.272 |		| tbd 3GPP-Purge-UE-Request PUR 3GPP TS 29.272 |
	| tbd Purge-UE-Answer PUA 3GPP TS 29.272 |		| tbd 3GPP-Purge-UE-Answer PUA 3GPP TS 29.272 |
	| tbd Reset-Request RSR 3GPP TS 29.272 |		| tbd 3GPP-Reset-Request RSR 3GPP TS 29.272 |
	| tbd Reset-Answer RSA 3GPP TS 29.272 |		| tbd 3GPP-Reset-Answer RSA 3GPP TS 29.272 |
	| tbd Notify-Request NOR 3GPP TS 29.272 |		| tbd 3GPP-Notify-Request NOR 3GPP TS 29.272 |
	| tbd Notify-Answer NOA 3GPP TS 29.272 |		| tbd 3GPP-Notify-Answer NOA 3GPP TS 29.272 |
	| tbd ME-Identity-Check-Request ECR 3GPP TS 29.272 |		| tbd 3GPP-ME-Identity-Check-Request ECR 3GPP TS 29.272 |
	| tbd ME-Identity-Check-Answer ECA 3GPP TS 29.272 |		| tbd 3GPP-ME-Identity-Check-Answer ECA 3GPP TS 29.272 |
	+---------------------------------------------------------------------+		+----------------------------------------------------------------------+
	5. Security Considerations		5. Security Considerations
	This document describes command codes used in applications which		This document describes command codes used in applications which
	build on top of the Diameter base protocol and the same security		build on top of the Diameter base protocol and the same security
	considerations described in [RFC3588] are applicable to this		considerations described in [RFC3588] are applicable to this
	document. No further extensions are required beyond the security		document. No further extensions are required beyond the security
	mechanisms offered by [RFC3588].		mechanisms offered by [RFC3588].
	6. Acknowledgements		6. Acknowledgements
	skipping to change at page 5, line 16 ¶		skipping to change at page 5, line 27 ¶
	for volunteering to be Document Shepherd.		for volunteering to be Document Shepherd.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.		[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
	Arkko, "Diameter Base Protocol", RFC 3588, September 2003.		Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
	[TS29.272]		[TS29.272]
	3rd Generation Partnership Project, "3GPP TS 29.272		3rd Generation Partnership Project, "3GPP TS 29.272;
	V8.0.0; Technical Specification Group Core Network and		Technical Specification Group Core Network and Terminals;
	Terminals; Evolved Packet System; MME and SGSN Related		Evolved Packet System; Mobility Management Entity (MME)
	Interfaces Based on Diameter Protocol (Release 8)",		and Serving GPRS Support Node (SGSN) Related Interfaces
	http://www.3gpp.org/ftp/Specs/html-info/29272.htm,		Based on Diameter Protocol (Release 8)",
	September 2008.		http://www.3gpp.org/ftp/Specs/html-info/29272.htm.
	7.2. Informative References		7.2. Informative References
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	May 2008.		May 2008.
	Authors' Addresses		Authors' Addresses
	Mark Jones		Mark Jones
End of changes. 22 change blocks.
	62 lines changed or deleted		73 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/