< draft-montemurro-gsma-imei-urn-17.txt		draft-montemurro-gsma-imei-urn-19.txt >
	Network Working Group M. Montemurro, Ed.		Network Working Group M. Montemurro, Ed.
	Internet-Draft A. Allen		Internet-Draft A. Allen
	Intended status: Informational Blackberry		Intended status: Informational Blackberry
	Expires: April 21, 2014 D. McDonald		Expires: July 16, 2014 D. McDonald
	Eircom		Eircom
	P. Gosden		P. Gosden
	GSM Association		GSM Association
	October 18, 2013		January 12, 2014
	A Uniform Resource Name Namespace for the Global System for Mobile		A Uniform Resource Name Namespace for the Global System for Mobile
	communications Association (GSMA) and the International Mobile station		communications Association (GSMA) and the International Mobile station
	Equipment Identity (IMEI)		Equipment Identity (IMEI)
	draft-montemurro-gsma-imei-urn-17		draft-montemurro-gsma-imei-urn-19
	Abstract		Abstract
	This specification specifies a Uniform Resource Name namespace for		This specification specifies a Uniform Resource Name namespace for
	the GSMA (Global System for Mobile communications Association) and a		the GSMA (Global System for Mobile communications Association) and a
	Namespace Specific String (NSS) for the IMEI (International Mobile		Namespace Specific String (NSS) for the IMEI (International Mobile
	station Equipment Identity), and an associated parameter for the		station Equipment Identity), and an associated parameter for the
	IMEISV (International Mobile station Equipment Identity and Software		IMEISV (International Mobile station Equipment Identity and Software
	Version number). The IMEI is 15 decimal digits long and the IMEISV		Version number). The IMEI is 15 decimal digits long and the IMEISV
	is 16 decimal digits long and both are encoded using Binary Encoded		is 16 decimal digits long and both are encoded using Binary Encoded
	skipping to change at page 1, line 49		skipping to change at page 1, line 49
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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."
	This Internet-Draft will expire on April 21, 2014.		This Internet-Draft will expire on July 16, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2014 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 3, line 13		skipping to change at page 3, line 13
	than English.		than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
	3. Namespace Registration Template . . . . . . . . . . . . . . . 5		3. Namespace Registration Template . . . . . . . . . . . . . . . 5
	4. Specification . . . . . . . . . . . . . . . . . . . . . . . . 8		4. Specification . . . . . . . . . . . . . . . . . . . . . . . . 9
	4.1. IMEI Parameters . . . . . . . . . . . . . . . . . . . . . 8		4.1. IMEI Parameters . . . . . . . . . . . . . . . . . . . . . 9
	4.2. IMEI Format . . . . . . . . . . . . . . . . . . . . . . . 9		4.2. IMEI Format . . . . . . . . . . . . . . . . . . . . . . . 10
	4.2.1. Type Allocation Code (TAC) . . . . . . . . . . . . . . 9		4.2.1. Type Allocation Code (TAC) . . . . . . . . . . . . . . 10
	4.2.2. Serial Number (SNR) . . . . . . . . . . . . . . . . . 9		4.2.2. Serial Number (SNR) . . . . . . . . . . . . . . . . . 10
	4.2.3. Spare . . . . . . . . . . . . . . . . . . . . . . . . 9		4.2.3. Spare . . . . . . . . . . . . . . . . . . . . . . . . 10
	4.2.4. Binary Encoding . . . . . . . . . . . . . . . . . . . 10		4.2.4. Binary Encoding . . . . . . . . . . . . . . . . . . . 10
	4.3. IMEISV Format . . . . . . . . . . . . . . . . . . . . . . 10		4.3. IMEISV Format . . . . . . . . . . . . . . . . . . . . . . 11
	4.3.1. Type Allocation Code (TAC) . . . . . . . . . . . . . . 10		4.3.1. Type Allocation Code (TAC) . . . . . . . . . . . . . . 11
	4.3.2. Serial Number (SNR) . . . . . . . . . . . . . . . . . 10		4.3.2. Serial Number (SNR) . . . . . . . . . . . . . . . . . 11
	4.3.3. Software Version Number (SVN) . . . . . . . . . . . . 10		4.3.3. Software Version Number (SVN) . . . . . . . . . . . . 11
	4.3.4. Binary Encoding . . . . . . . . . . . . . . . . . . . 10		4.3.4. Binary Encoding . . . . . . . . . . . . . . . . . . . 11
	5. Community considerations . . . . . . . . . . . . . . . . . . . 11		5. Community considerations . . . . . . . . . . . . . . . . . . . 12
	6. Namespace considerations . . . . . . . . . . . . . . . . . . . 12		6. Namespace considerations . . . . . . . . . . . . . . . . . . . 12
	7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 12		7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 13
	8. Security considerations . . . . . . . . . . . . . . . . . . . 12		8. Security considerations . . . . . . . . . . . . . . . . . . . 13
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13		10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
	10.1. Normative references . . . . . . . . . . . . . . . . . . . 13		10.1. Normative references . . . . . . . . . . . . . . . . . . . 14
	10.2. Informative references . . . . . . . . . . . . . . . . . . 14		10.2. Informative references . . . . . . . . . . . . . . . . . . 15
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
	1. Introduction		1. Introduction
	This specification specifies a Uniform Resource Name (URN) namespace		This specification specifies a Uniform Resource Name (URN) namespace
	for the GSMA (GSM Association) and a NSS for the IMEI (International		for the GSMA (GSM Association) and a NSS for the IMEI (International
	Mobile station Equipment Identity), and associated parameter for the		Mobile station Equipment Identity), and associated parameter for the
	Software Version number from the IMEISV (International Mobile station		Software Version number from the IMEISV (International Mobile station
	Equipment Identity and Software Version number) as per the namespace		Equipment Identity and Software Version number) as per the namespace
	registration requirement found in RFC 3406 [1]. The NID (Namespace		registration requirement found in RFC 3406 [1]. The NID (Namespace
	Identifier) 'gsma' is for identities used in GSM, UMTS and LTE		Identifier) 'gsma' is for identities used in GSM, UMTS and LTE
	networks. The IMEI and the IMEISV are managed by the GSMA, so this		networks. The IMEI and the IMEISV are managed by the GSMA, so this
	NID is managed by the GSMA. Whilst this specification currently		NID is managed by the GSMA. Whilst this specification currently
	specifies only the IMEI NSS under the 'gsma' NID, additional NSS		specifies only the IMEI NSS under the 'gsma' NID, additional NSS
	under the 'gsma' NID may be specified in the future by the GSMA using		under the 'gsma' NID may be specified in the future by the GSMA using
	the procedure for URN NSS changes and additions (currently through		the procedure for URN NSS changes and additions (currently through
	the publication of future Informational RFCs approved by IETF		the publication of future Informational RFCs approved by IETF
	concensus).		conensus).
	The IMEI is 15 decimal digits long and includes a Type Allocation		The IMEI is 15 decimal digits long and includes a Type Allocation
	Code (TAC) of 8 decimal digits and a Serial Number (SNR) of 6 decimal		Code (TAC) of 8 decimal digits and a Serial Number (SNR) of 6 decimal
	digits plus a Spare decimal digit. The TAC identifies the type of		digits plus a Spare decimal digit. The TAC identifies the type of
	the Mobile Equipment and is chosen from a range of values allocated		the Mobile Equipment and is chosen from a range of values allocated
	to the Mobile Equipment manufacturer in order to uniquely identify		to the Mobile Equipment manufacturer in order to uniquely identify
	the model of the Mobile Equipment. The SNR is an individual serial		the model of the Mobile Equipment. The SNR is an individual serial
	number that uniquely identifies each Mobile Equipment within the TAC.		number that uniquely identifies each Mobile Equipment within the TAC.
	The Spare digit is used as a check digit to validate the IMEI and is		The Spare digit is used as a check digit to validate the IMEI and is
	always set to the value 0 when transmitted by the Mobile Equipment.		always set to the value 0 when transmitted by the Mobile Equipment.
	skipping to change at page 5, line 19		skipping to change at page 5, line 19
	document are to be interpreted as described in RFC 2119 [4].		document are to be interpreted as described in RFC 2119 [4].
	3. Namespace Registration Template		3. Namespace Registration Template
	Namespace ID: 'gsma' requested		Namespace ID: 'gsma' requested
	Registration Information:		Registration Information:
	Registration version number: 1		Registration version number: 1
	Registration date: 2013-10-18		Registration date: 2014-01-12
	Declared registrant of the namespace:		Declared registrant of the namespace:
	Registering organization:		Registering organization:
	Name: GSM Association		Name: GSM Association
	Address: 1st Floor, Mid City Place,		Address: 1st Floor, Mid City Place,
	71 High Holborn, London, England		71 High Holborn, London, England
	Designated contact person:		Designated contact person:
	Name: Paul Gosden		Name: Paul Gosden
	Coordinates: pgosden@gsma.com		Coordinates: pgosden@gsma.com
	Declaration of syntactic structure:		Declaration of syntactic structure:
	The identifier is expressed in American Standard Code for		The identifier is expressed in American Standard Code for
	Information Interchange (ASCII) characters and has a hierarchical		Information Interchange (ASCII) characters and has a hierarchical
	structure expressed using the augmented Backus-Naur Form (ABNF)		structure expressed using the augmented Backus-Naur Form (ABNF)
	defined in RFC 5234 [5] as follows:		defined in RFC 5234 [5] as follows:
	gsma-urn = "urn:" gsma-NID ":" gsma-NSS		gsma-urn = "urn:" gsma-NID ":" gsma-NSS
	gsma-NID = "gsma"		gsma-NID = "gsma"
	gsma-NSS = imei-specifier / future-gsma-specifier		gsma-NSS = imei-specifier / future-gsma-specifier
	imei-specifier = "imei:" imeival [ ";" sw-version-param ]		imei-specifier = "imei:" ( imeival / ext-imei )
			[ ";" sw-version-param ]
	[ ";" imei-version-param ]		[ ";" imei-version-param ]
	sw-version-param = "svn=" software-version-string		ext-imei = gsma-defined-nonempty ;GSMA defined and
			;IETF consensus
			;required
			sw-version-param = "svn=" software-version
	imei-version-param = "vers=" imei-version-val		imei-version-param = "vers=" imei-version-val
	software-version-string = 2DIGIT		software-version = 2DIGIT
	imei-version-val = DIGIT		imei-version-val = DIGIT
	future-gsma-specifier = gsma-defined-nonempty-string ;GSMA defined		future-gsma-specifier = future-specifier
	;and IETF consensus		*( ";" future-param )
			future-specifier = gsma-defined-nonempty ;GSMA defined and
			;IETF consensus
	;required		;required
	gsma-defined-nonempty-string = 1*gsma-urn-char		future-param = gsma-defined-nonempty
	gsma-urn-char = ALPHA / DIGIT / "-" / "." / "_" / "%"/":"/";"/"="		gsma-defined-nonempty = 1*gsma-urn-char
			gsma-urn-char = ALPHA / DIGIT
			/ "-" / "." / "_" / "%" / ":"/ "="
	A NSS for the IMEI is defined under the 'gsma' NID.		A NSS for the IMEI is defined under the 'gsma' NID.
	An IMEI is an identifier under the 'gsma' NID that uniquely		An IMEI is an identifier under the 'gsma' NID that uniquely
	identifies the mobile devices used in the GSM, UMTS and LTE		identifies the mobile devices used in the GSM, UMTS and LTE
	networks.		networks.
	The representation of the IMEI is defined in 3GPP TS 23.003 [2].		The representation of the IMEI is defined in 3GPP TS 23.003 [2].
	To accurately represent an IMEI received in a cellular signaling		To accurately represent an IMEI received in a cellular signaling
	message (see 3GPP TS 24.008 [6]) as a URN, it is necessary to		message (see 3GPP TS 24.008 [6]) as a URN, it is necessary to
	skipping to change at page 6, line 30		skipping to change at page 7, line 10
	of core rules in RFC 5234 [5], and are not repeated here.		of core rules in RFC 5234 [5], and are not repeated here.
	A URN with the 'imei' NSS contains one imeival, and its formal		A URN with the 'imei' NSS contains one imeival, and its formal
	definition is provided by the following ABNF (RFC 5234) [5]:		definition is provided by the following ABNF (RFC 5234) [5]:
	imeival = tac "-" snr "-" spare		imeival = tac "-" snr "-" spare
	tac = 8DIGIT		tac = 8DIGIT
	snr = 6DIGIT		snr = 6DIGIT
	spare = DIGIT		spare = DIGIT
	The <future-gsma-specifier>, and <gsma-defined-nonempty-string>		The <future-gsma-specifier>, and <gsma-defined-nonempty> can
	can comprise any ASCII characters compliant with the above ABNF.		comprise any ASCII characters compliant with the above ABNF.
	The GSMA will take responsibility for the NSS 'imei'.		The GSMA will take responsibility for the NSS 'imei'.
	Additional NSS may be added for future identifiers needed by the		Additional NSS may be added for future identifiers needed by the
	GSMA using the procedure for URN NSS changes and additions		GSMA using the procedure for URN NSS changes and additions
	(currently through the publication of future Informational RFCs		(currently through the publication of future Informational RFCs
	approved by IETF concensus).		approved by IETF consensus).
	Relevant ancillary documentation:		Relevant ancillary documentation:
	See IMEI Allocation and Approval Guidelines [3] and 3GPP TS 23.003		See IMEI Allocation and Approval Guidelines [3] and 3GPP TS 23.003
	[2].		[2].
	Identifier uniqueness considerations:		Identifier uniqueness considerations:
	Identifiers under the 'gsma' NID are defined and assigned by the		Identifiers under the 'gsma' NID are defined and assigned by the
	GSMA after ensuring that the URNs to be assigned are unique.		GSMA after ensuring that the URNs to be assigned are unique.
	Uniqueness is achieved by checking against the IANA registry of		Uniqueness is achieved by checking against the IANA registry of
	previously assigned names.		previously assigned names.
	skipping to change at page 8, line 29		skipping to change at page 9, line 9
	The IMEI can be validated using the mechanism defined in Annex B		The IMEI can be validated using the mechanism defined in Annex B
	of 3GPP TS 23.003 [2]. There is no mechanism defined to validate		of 3GPP TS 23.003 [2]. There is no mechanism defined to validate
	the SVN field of the IMEISV.		the SVN field of the IMEISV.
	Scope: GSMA URN is global in scope.		Scope: GSMA URN is global in scope.
	4. Specification		4. Specification
	4.1. IMEI Parameters		4.1. IMEI Parameters
	The optional 'vers' parameter is included for extensibility of the		The optional 'vers' parameter and the 'ext-imei' field in the ABNF
	IMEI NSS, for example if the IMEI format is extended in the future		are included for extensibility of the IMEI NSS, for example if the
	(such as with additional digits or using hex digits). A value of the		IMEI format is extended in the future (such as with additional digits
			or using hex digits). In this case the 'vers' parameter would
			contain a non zero value and the 'ext-imei' would be further defined
			to represent the syntax of the extended IMEI format. A value of the
	'vers' parameter equal to 0 or the absence of the 'vers' parameter		'vers' parameter equal to 0 or the absence of the 'vers' parameter
	means the URN format is compliant with the format specified here.		means the URN format is compliant with the format specified here.
	Any change to the format specified here requires the use of the		Any change to the format specified here requires the use of the
	procedure for URN NSS changes and additions (currently the		procedure for URN NSS changes and additions (currently the
	publication of a future Informational RFCs approved by IETF		publication of a future Informational RFCs approved by IETF
	concensus). The reason why use of the 'vers' parameter was chosen		consensus). The reason why use of the 'vers' parameter was chosen
	for extensibility instead of defining a new NSS (e.g. 'imei2') is		for extensibility instead of defining a new NSS (e.g. 'imei2') is
	that it is likely that many applications will only need to perform		that it is likely that many applications will only need to perform
	string compares of the 'imeival'. So even if the format or length of		string compares of the 'imeival'. So even if the format or length of
	the 'imeival' changes in the future, such applications should		the 'imeival' changes in the future, such applications should
	continue to work without having to be updated to understand a new		continue to work without having to be updated to understand a new
	NSS.		NSS.
	draft-allen-dispatch-imei-urn-as-instanceid-11 [11] specifies how the		draft-allen-dispatch-imei-urn-as-instanceid-12 [11] specifies how the
	GSMA IMEI URN can be used as an instance ID as specified in RFC 5626		GSMA IMEI URN can be used as an instance ID as specified in RFC 5626
	[12]. Any future value of the 'vers' parameter other than equal to 0		[12]. Any future value of the 'vers' parameter other than equal to 0
	or the definition of additional parameters that are intended to be		or the definition of additional parameters that are intended to be
	used as part of an instance ID will require an update to		used as part of an instance ID will require an update to
	draft-allen-dispatch-imei-urn-as-instanceid-11 [11].		draft-allen-dispatch-imei-urn-as-instanceid-12 [11].
	For example:		For example:
	urn:gsma:imei:90420156-025763-0;vers=0		urn:gsma:imei:90420156-025763-0;vers=0
	The IMEISV is an identifier that uniquely identifies mobile devices		The IMEISV is an identifier that uniquely identifies mobile devices
	and their associated software versions used in the GSM, UMTS and LTE		and their associated software versions used in the GSM, UMTS and LTE
	networks. The representation of the IMEISV is defined in 3GPP TS		networks. The representation of the IMEISV is defined in 3GPP TS
	23.003 [2].		23.003 [2].
	To represent the IMEISV the URN parameter 'svn' is appended to the		To represent the IMEISV the URN parameter 'svn' is appended to the
	skipping to change at page 14, line 33		skipping to change at page 15, line 22
	[9] Moats, R., "URN Syntax", RFC 2141, May 1997.		[9] Moats, R., "URN Syntax", RFC 2141, May 1997.
	10.2. Informative references		10.2. Informative references
	[10] Leach, P., Mealling, M., and R. Salz, "A Universally Unique		[10] Leach, P., Mealling, M., and R. Salz, "A Universally Unique
	IDentifier (UUID) URN Namespace", RFC 4122, July 2005.		IDentifier (UUID) URN Namespace", RFC 4122, July 2005.
	[11] Allen, A., "Using the International Mobile station Equipment		[11] Allen, A., "Using the International Mobile station Equipment
	Identity(IMEI) URN as an Instance ID, work in progress",		Identity(IMEI) URN as an Instance ID, work in progress",
	Internet Draft draft-allen-dispatch-imei-urn-as-instanceid-11,		Internet Draft draft-allen-dispatch-imei-urn-as-instanceid-12,
	October 2013.		November 2013.
	[12] Jennings, C., Mahy, R., and F. Audet, "Managing Client-		[12] Jennings, C., Mahy, R., and F. Audet, "Managing Client-
	Initiated Connections in the Session Initiation Protocol		Initiated Connections in the Session Initiation Protocol
	(SIP)", RFC 5626, October 2009.		(SIP)", RFC 5626, October 2009.
	[13] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,		[13] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
	Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:		Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
	Session Initiation Protocol", RFC 3261, June 2002.		Session Initiation Protocol", RFC 3261, June 2002.
	Authors' Addresses		Authors' Addresses
End of changes. 27 change blocks.
	44 lines changed or deleted		55 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/