Internet Engineering Task Force (IETF) R. Atarius
Request for Comments: 8464 September 2018
Category: Informational
ISSN: 2070-1721
Internet Engineering Task Force (IETF) R. Atarius
Request for Comments: 8464 September 2018
Category: Informational
ISSN: 2070-1721
A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)
设备标识和移动设备标识（MEID）的URN命名空间
Abstract
摘要
This document defines a Uniform Resource Name (URN) namespace for the Third Generation Partnership Project 2 (3GPP2) and a Namespace Specific String (NSS) for the Mobile Equipment Identity (MEID). The structure of an MEID is 15 hexadecimal digits long and is defined in the 3GPP2 to uniquely identify each individual mobile equipment (e.g., a handset or mobile phone). The 3GPP2 has a requirement to be able to use an MEID as a URN. This document fulfills that requirement.
本文档定义了第三代合作伙伴关系项目2（3GPP2）的统一资源名称（URN）命名空间和移动设备标识（MEID）的命名空间特定字符串（NSS）。MEID的结构是15个十六进制数字长，并且在3GPP2中定义为唯一地标识每个单独的移动设备（例如，手机或移动电话）。3GPP2要求能够将MEID用作URN。本文件满足这一要求。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are candidates for any level of Internet Standard; see Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8464.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问https://www.rfc-editor.org/info/rfc8464.
Copyright Notice
版权公告
Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2018 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(https://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Namespace Registration Template . . . . . . . . . . . . . . . 4
4. Specification . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. MEID Parameters . . . . . . . . . . . . . . . . . . . . . 6
4.2. MEID Format . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.1. Overview . . . . . . . . . . . . . . . . . . . . . . 6
4.2.2. Manufacturer Code . . . . . . . . . . . . . . . . . . 6
4.2.3. Serial Number . . . . . . . . . . . . . . . . . . . . 7
4.2.4. Check Digit . . . . . . . . . . . . . . . . . . . . . 7
4.2.5. Hexadecimal Encoding . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Security and Privacy Considerations . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . 10
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Namespace Registration Template . . . . . . . . . . . . . . . 4
4. Specification . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. MEID Parameters . . . . . . . . . . . . . . . . . . . . . 6
4.2. MEID Format . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.1. Overview . . . . . . . . . . . . . . . . . . . . . . 6
4.2.2. Manufacturer Code . . . . . . . . . . . . . . . . . . 6
4.2.3. Serial Number . . . . . . . . . . . . . . . . . . . . 7
4.2.4. Check Digit . . . . . . . . . . . . . . . . . . . . . 7
4.2.5. Hexadecimal Encoding . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Security and Privacy Considerations . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . 10
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
Mobile equipment that is either a) single-mode 3GPP using only 3GPP technology to transmit and receive voice or data or b) dual-mode 3GPP/3GPP2 using either 3GPP or 3GPP2 technology to transmit and receive voice or data has an International Mobile station Equipment Identity (IMEI) to identify it. A URN namespace and an NSS for the IMEI are defined in [RFC7254]. For cases where the mobile equipment uses IMEI as an identity for dual-mode 3GPP/3GPP2 access, the IMEI URN as defined in [RFC7254] can be used to identify the mobile equipment.
a）仅使用3GPP技术来发送和接收语音或数据的单模3GPP或b）使用3GPP或3GPP2技术来发送和接收语音或数据的双模3GPP/3GPP2的移动设备具有国际移动站设备标识（IMEI）来识别它。IMEI的URN命名空间和NSS在[RFC7254]中定义。对于移动设备使用IMEI作为双模3GPP/3GPP2接入的标识的情况，可以使用[RFC7254]中定义的IMEI URN来识别移动设备。
However, single-mode 3GPP2 mobile equipment that supports only 3GPP2 access technology to transmit and receive voice or data has a hexadecimal MEID. Since there are fundamental differences between MEID and IMEI (i.e., in encoding, format, and the ownership), [RFC7254] cannot be employed to represent the hexadecimal MEID.
然而，仅支持3GPP2接入技术以发送和接收语音或数据的单模3GPP2移动设备具有十六进制MEID。由于MEID和IMEI（即编码、格式和所有权）之间存在根本性差异，[RFC7254]不能用于表示十六进制MEID。
This document specifies a URN namespace for 3GPP2 and an NSS for the MEID as per the namespace registration requirement in [RFC8141]. The structure of an MEID is 15 hexadecimal digits long and is defined by 3GPP2 (see [S.R0048-A]) to uniquely identify each individual piece of mobile equipment (e.g., a handset or mobile phone). The 3GPP2 has a requirement to be able to use an MEID as a URN. This document fulfills that requirement. The Namespace Identifier (NID) '3gpp2' is for identities used in 3GPP2 networks. The MEID is managed by the 3GPP2, so this NID is managed by the 3GPP2. This specification defines only NSSs constructed from MEIDs under the '3gpp2' NID. These NSSs start with "meid:" in order to identify them as such. In the future, the 3GPP2 may specify other types of NSSs under the '3gpp2' NID.
本文档根据[RFC8141]中的名称空间注册要求，为3GPP2指定了URN名称空间，为MEID指定了NSS。MEID的结构是15位十六进制数字，由3GPP2（参见[S.R0048-A]）定义，以唯一地标识每个单独的移动设备（例如，手机或移动电话）。3GPP2要求能够将MEID用作URN。本文件满足这一要求。命名空间标识符（NID）“3gpp2”用于3gpp2网络中使用的标识。MEID由3GPP2管理，因此该NID由3GPP2管理。本规范仅定义了在“3gpp2”NID下由MEIDs构建的NSS。这些NSS以“meid:”开头，以便识别它们。将来，3GPP2可以在“3GPP2”NID下指定其他类型的nss。
The MEID is 15 hexadecimal digits long, includes a manufacturer code of 8 hexadecimal digits, and includes the serial number of 6 hexadecimal digits plus a hexadecimal digit as a check digit.
MEID长度为15个十六进制数字，包括8个十六进制数字的制造商代码，以及6个十六进制数字加上一个十六进制数字作为校验数字的序列号。
The manufacturer code identifies the mobile equipment manufacturer. A manufacturer can be assigned more than one manufacturer code. The serial number uniquely identifies each piece of mobile equipment within the manufacturer code. The check digit is used as assurance of integrity in error-prone operations, e.g., when used with certain types of readers during inventory-management operations. The check digit is not transmitted. Therefore, the first 14 of the 15 hexadecimal digits are used for defining the MEID as a URN.
制造商代码标识移动设备制造商。可以为制造商分配多个制造商代码。序列号唯一标识制造商代码内的每件移动设备。校验位用于确保易出错操作的完整性，例如在库存管理操作期间与某些类型的读卡器一起使用时。校验位不被传输。因此，15位十六进制数字中的前14位用于将MEID定义为URN。
The information here is meant to be a concise guide for those wishing to use the hexadecimal MEID as a URN. Nothing in this document should be construed to override [S.R0048-A], which defines the MEID.
这里的信息旨在为那些希望使用十六进制MEID作为URN的人提供简明指南。本文件中的任何内容均不得解释为覆盖定义MEID的[S.R0048-A]。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”在所有大写字母出现时（如图所示）应按照BCP 14[RFC2119][RFC8174]所述进行解释。
A completed namespace registration follows.
随后是完整的命名空间注册。
Namespace Identifier: '3gpp2'
命名空间标识符：“3gpp2”
Version: 1
版本:1
Date: 2018-06-10
日期：2018-06-10
Registrant: Standards Organization: Third Generation Partnership Project 2 (3GPP2)
注册人：标准组织：第三代合作伙伴项目2（3GPP2）
Contact:
联系人：
John Derr, MEID Global Hexadecimal Administrator, JDerr@tiaonline.org
John Derr，MEID全局十六进制管理员，JDerr@tiaonline.org
Gary Pellegrino, TIA TR-45 EUMAG Chair, gary@commflowresources.com c/o Telecommunications Industry Association 1320 N. Courthouse Rd., Suite 200 Arlington, Virginia 22201, United States of America
Gary Pellegrino，TIA TR-45 EUMAG主席，gary@commflowresources.com转交美国弗吉尼亚州阿灵顿法院北路1320号电信业协会，邮编：22201
Purpose: The '3gpp2' namespace is used to identify mobile equipment that uses technologies defined by the Third Generation Partnership Project 2 ((3GPP2); initially, such equipment is identified by a URN that embeds a Mobile Equipment Identity (MEID) that is 15 hexadecimal digits long and unique to each individual piece of mobile equipment (e.g., a handset or mobile phone).
用途：“3gpp2”名称空间用于标识使用第三代合作伙伴关系项目2（3gpp2）定义的技术的移动设备；最初，此类设备由嵌入移动设备标识（MEID）的URN标识，该标识长度为15个十六进制数字，且每个移动设备都是唯一的（例如，手机或移动电话）。
Syntax: The identifier is expressed in American Standard Code for Information Interchange (ASCII) characters and has a hierarchical expression using the Augmented Backus-Naur Form (ABNF) defined in [RFC5234], as follows:
语法：标识符以美国信息交换标准代码（ASCII）字符表示，并使用[RFC5234]中定义的增广巴科斯-诺尔形式（ABNF）具有分层表达式，如下所示：
pp2-urn = "urn:" pp2-NID ":" pp2-NSS
pp2-NID = "3gpp2"
pp2-NSS = meid-specifier / future-pp2-specifier
meid-specifier = "meid:" meidval
future-pp2-specifier = future-specifier *[ ":" 1*( pchar / "/" )]
future-specifier = 1*pp2-char
pp2-char = ALPHA / DIGIT / "-" / "." / "_" /
pct-encoded
pp2-urn = "urn:" pp2-NID ":" pp2-NSS
pp2-NID = "3gpp2"
pp2-NSS = meid-specifier / future-pp2-specifier
meid-specifier = "meid:" meidval
future-pp2-specifier = future-specifier *[ ":" 1*( pchar / "/" )]
future-specifier = 1*pp2-char
pp2-char = ALPHA / DIGIT / "-" / "." / "_" /
pct-encoded
where 'pchar' and 'pct-encoded' are defined in [RFC3986]. An NSS for the MEID is defined under the '3gpp2' NID. The representation of the MEID is a specific number of hexadecimal digits, as
其中，[RFC3986]中定义了“pchar”和“pct编码”。MEID的NSS在“3gpp2”NID下定义。MEID的表示形式是特定数量的十六进制数字，如下所示：
described in [S.R0048-A]. The formal definition of a URN with 'meid' NSS contains one meidval with the formal definition according to the following ABNF [RFC5234]:
如[S.R0048-A]所述。带有“meid”NSS的URN的正式定义包含一个meidval，其正式定义符合以下ABNF[RFC5234]：
meidval = Manufacturer-Code "-" Serial-Number
Manufacturer-Code = 8HEX
Serial-Number = 6HEX
HEX = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
meidval = Manufacturer-Code "-" Serial-Number
Manufacturer-Code = 8HEX
Serial-Number = 6HEX
HEX = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
Assignment: The manufacturer code and serial number portions of the MEID are permanently stored in the mobile equipment, so they remain persistent as long as the mobile equipment exists. The process for manufacturer code and serial number assignment is documented in [SC.R4002-0] and the manufacturer code and serial number values once assigned are not reassigned to other pieces of mobile equipment.
分配：MEID的制造商代码和序列号部分永久存储在移动设备中，因此只要移动设备存在，它们就会保持不变。制造商代码和序列号分配过程记录在[SC.R4002-0]中，且一旦分配制造商代码和序列号值，则不会重新分配给其他移动设备。
Identifiers in the '3gpp2' namespace are defined and assigned by the 3GPP2 or an agency appointed by 3GPP2 after ensuring that the URNs to be assigned are unique. Procedures are in place to ensure that each MEID is uniquely assigned by the mobile equipment manufacturer so that it is guaranteed to uniquely identify that particular piece of mobile equipment.
在确保要分配的URN是唯一的之后，“3gpp2”命名空间中的标识符由3gpp2或3gpp2指定的机构定义和分配。制定程序以确保每个MEID由移动设备制造商唯一分配，从而确保其唯一识别特定移动设备。
Security and Privacy: See Section 6 of RFC 8464.
安全和隐私：见RFC 8464第6节。
Interoperability: Although both the 3GPP2 Mobile Equipment Identity (MEID) and the 3GPP International Mobile station Equipment Identity (IMEI) are used to identify mobile equipment, they are separate identifiers and are not to be confused. Internet implementations will not generally possess MEID identifiers. The identifiers generated by such implementations will typically be URNs within namespaces other than '3gpp2', and may, depending on context, even be non-URN URIs. Implementations are advised to be ready to process URIs other than '3gpp2' namespace URNs, so as to aid in interoperability.
互操作性：尽管3GPP2移动设备标识（MEID）和3GPP国际移动站设备标识（IMEI）都用于识别移动设备，但它们是单独的标识符，不能混淆。Internet实现通常不具有MEID标识符。由此类实现生成的标识符通常是除“3gpp2”之外的名称空间中的URN，并且根据上下文，甚至可以是非URN uri。建议实现准备好处理除“3gpp2”命名空间URN以外的URI，以帮助实现互操作性。
Resolution: No resolution is envisioned.
解决方案：未设想任何解决方案。
Documentation: Documentation can be found in the following specifications:
文档：文档可在以下规范中找到：
* "A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)" [RFC8464].
* “用于设备标识和移动设备标识（MEID）的URN命名空间”[RFC8464]。
* "3G Mobile Equipment Identifier (MEID) - Stage 1" [S.R0048-A].
* “3G移动设备标识符（MEID）-第1阶段”[S.R0048-A]。
* "GHA (Global Hexadecimal Administrator) Assignment Guidelines and Procedures for Mobile Equipment Identifier (MEID) and Short Form Expanded UIM Identifier (SF_EUIMID)" [SC.R4002-0].
* “GHA（全球十六进制管理员）移动设备标识符（MEID）和缩写扩展UIM标识符（SF_EUIMID）的分配指南和程序”[SC.R4002-0]。
Additional Information: Because the syntax of a 3GPP2 Mobile Equipment Identity (MEID) differs from that of a 3GPP International Mobile station Equipment Identity (IMEI), reuse of the URN specified in RFC 7254 is not possible.
附加信息：由于3GPP2移动设备标识（MEID）的语法不同于3GPP国际移动站设备标识（IMEI），因此不可能重用RFC 7254中指定的URN。
Revision Information: N/A
修订资料：不适用
Any future change to the format of the 'meid' NSS requires the use of the procedure for URN NSS changes (currently through the publication of a future Informational RFC approved by IETF consensus).
“meid”NSS格式的任何未来变更都需要使用URN NSS变更程序（目前通过发布IETF共识批准的未来信息RFC）。
[RFC8465] specifies how the MEID URN can be used as an Instance ID as specified in [RFC5626]. Any change to the Instance ID will require an update to [RFC8465]. An example of 3GPP2 MEID URN is:
[RFC8465]指定如何将MEID URN用作[RFC5626]中指定的实例ID。对实例ID的任何更改都需要更新到[RFC8465]。3GPP2 MEID URN的一个示例是：
urn:3gpp2:meid:A04B0D56-02A7E3
urn:3gpp2:meid:A04B0D56-02A7E3
The MEID format is 15 hexadecimal digits encoded in 8 octets as defined in [S.R0048-A]. The first 8 hexadecimal digits constitute the manufacturer code; the next 6 hexadecimal digits the serial number within the manufacturer code. The last hexadecimal digit is a check digit. For more details on the hexadecimal encoding, see Section 4.2.5.
MEID格式为[S.R0048-A]中定义的以8个八位字节编码的15个十六进制数字。前8位十六进制数字构成制造商代码；接下来的6位十六进制数字表示制造商代码内的序列号。最后一个十六进制数字是校验位。有关十六进制编码的更多详细信息，请参见第4.2.5节。
The manufacturer code is a value of 8 hexadecimal digits. The manufacturer code identifies the mobile equipment manufacturer. The manufacturer code is chosen from a range of values allocated to the mobile equipment manufacturer in order to uniquely identify the mobile equipment.
制造商代码是8位十六进制数字的值。制造商代码标识移动设备制造商。从分配给移动设备制造商的一系列值中选择制造商代码，以便唯一地识别移动设备。
The serial number is a value of 6 hexadecimal digits. The serial number identifies equipment within the manufacturer code.
序列号是6个十六进制数字的值。序列号标识制造商代码内的设备。
This is a single hexadecimal digit (bits 1-4 of octet 8), and it is used as assurance of integrity in error-prone operations, e.g., when used with certain types of readers during inventory management operations. The check digit is not transmitted by the mobile equipment and is not used in the MEID URN.
这是一个十六进制数字（八位字节8的第1-4位），在容易出错的操作中用作完整性保证，例如在库存管理操作期间与某些类型的读卡器一起使用时。移动设备不会传输校验位，也不会在MEID URN中使用校验位。
The MEID format is 15 hexadecimal digits encoded in 8 octets as defined in [S.R0048-A]. The following figure is an abstract representation of a hexadecimal-encoded MEID stored in memory (the actual storage format in memory is implementation specific). In this figure, the most significant digit of the manufacturer code is encoded in bits 1-4 of octet 1. Bits 5-8 of octet 8 are zero-padded, since bits 1-4 are only needed to encode the check digit. The most significant digit of the serial number is encoded in the bits 1-4 of octet 5. When MEID is included in a cellular signaling message, the check digit is omitted and the first 7 Octets in the following figure are only transmitted, [X.S0008-A].
MEID格式为[S.R0048-A]中定义的以8个八位字节编码的15个十六进制数字。下图是存储在内存中的十六进制编码MEID的抽象表示（内存中的实际存储格式是特定于实现的）。在该图中，制造商代码的最高有效位编码为八位位组1的第1-4位。八位字节8的位5-8是零填充的，因为位1-4只需要编码校验位。序列号的最高有效位编码在八位组5的位1-4中。当MEID包含在蜂窝信令消息中时，校验位被省略，下图中的前7个八位字节仅被传输[X.S0008-a]。
14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Hexadecimal
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ Digits
| | | |
| | | |
| Manufacturer Code | Serial Number |CD|
| | | |
| | | |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
1 2 3 4 5 6 7 8 Octets
14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Hexadecimal
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ Digits
| | | |
| | | |
| Manufacturer Code | Serial Number |CD|
| | | |
| | | |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
1 2 3 4 5 6 7 8 Octets
In accordance with BCP 66 [RFC8141], IANA has registered the Formal URN namespace '3gpp2' in the "Uniform Resource Name (URN) Namespaces" registry, using the registration template presented in Section 3.
根据BCP 66[RFC8141]，IANA已使用第3节中介绍的注册模板在“统一资源名称（URN）命名空间”注册表中注册了正式的URN命名空间“3gpp2”。
An MEID is usually printed outside of the box in which a mobile device ships. The MEID may also be printed under the battery on a mobile device; however, very few devices have removable batteries today. One can retrieve the MEID via either settings or by dialing *#06#. Anyone with brief physical access to the mobile device or its box can easily obtain the MEID. Therefore, MEIDs MUST NOT be used as security capabilities (identifiers whose mere possession grants access). Unfortunately, there are currently examples of some applications that are using the MEID for authorization. Also, some service providers' customer service departments have been known to use knowledge of the MEID as "proof" that the caller is the legitimate owner of the mobile device. Both of these are inappropriate uses of the MEID.
MEID通常打印在移动设备装运的盒子外面。MEID也可以打印在移动设备上的电池下方；然而，现在很少有设备有可拆卸电池。您可以通过设置或拨打*#06#来检索MEID。任何人只要对移动设备或其机箱进行短暂的物理访问，就可以轻松获得MEID。因此，不能将MEID用作安全功能（仅拥有就可以访问的标识符）。不幸的是，目前有一些应用程序使用MEID进行授权。此外，一些服务提供商的客户服务部门已经知道使用MEID的知识作为“证据”，证明呼叫者是移动设备的合法所有者。这两个都是MEID的不当使用。
Since the MEID is permanently assigned to the mobile equipment and is not modified when the ownership of the mobile equipment changes (even upon a complete software reload of the mobile equipment), the MEID URN MUST NOT be used as a user identifier or user address by an application. Using the MEID to identify a user or as a user address could result in communications destined for a previous owner of a device being received by the new device owner or could allow the new device owner to access information or services owned by the previous device owner.
由于MEID是永久分配给移动设备的，并且在移动设备的所有权发生变化时（即使在移动设备的完整软件重新加载时）不会进行修改，因此应用程序不得将MEID URN用作用户标识符或用户地址。使用MEID识别用户或将其作为用户地址可能导致发送给设备的前一所有者的通信被新设备所有者接收，或者可能允许新设备所有者访问前一设备所有者拥有的信息或服务。
Additionally, since the MEID identifies the mobile equipment, it potentially could be used to identify and track users for the purposes of surveillance and call data mining if sent in the clear.
此外，由于MEID识别移动设备，因此如果以明文形式发送，它可能用于识别和跟踪用户，以便进行监视和呼叫数据挖掘。
Since the MEID is personally identifiable information, uses of the MEID URN with IETF protocols require a specification and IETF expert review [RFC8126] in order to ensure that the privacy concerns are appropriately addressed. Protocols carrying the MEID URN SHOULD, at a minimum, use strongly hop-by-hop encrypted channels, and it is RECOMMENDED that end-to-end encryption be used.
由于MEID是个人可识别信息，MEID URN与IETF协议的使用需要规范和IETF专家评审[RFC8126]，以确保隐私问题得到适当解决。承载MEID URN的协议至少应使用强逐跳加密通道，建议使用端到端加密。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<https://www.rfc-editor.org/info/rfc2119>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, <https://www.rfc-editor.org/info/rfc3986>.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，DOI 10.17487/RFC3986，2005年1月<https://www.rfc-editor.org/info/rfc3986>.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace", RFC 4122, DOI 10.17487/RFC4122, July 2005, <https://www.rfc-editor.org/info/rfc4122>.
[RFC4122]Leach，P.，Mealling，M.和R.Salz，“通用唯一标识符（UUID）URN名称空间”，RFC 4122，DOI 10.17487/RFC4122，2005年7月<https://www.rfc-editor.org/info/rfc4122>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008, <https://www.rfc-editor.org/info/rfc5234>.
[RFC5234]Crocker，D.，Ed.和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，DOI 10.17487/RFC5234，2008年1月<https://www.rfc-editor.org/info/rfc5234>.
[RFC5626] Jennings, C., Ed., Mahy, R., Ed., and F. Audet, Ed., "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)", RFC 5626, DOI 10.17487/RFC5626, October 2009, <https://www.rfc-editor.org/info/rfc5626>.
[RFC5626]Jennings，C.，Ed.，Mahy，R.，Ed.，和F.Audet，Ed.，“在会话启动协议（SIP）中管理客户端启动的连接”，RFC 5626，DOI 10.17487/RFC5626，2009年10月<https://www.rfc-editor.org/info/rfc5626>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, <https://www.rfc-editor.org/info/rfc8126>.
[RFC8126]Cotton，M.，Leiba，B.，和T.Narten，“在RFC中编写IANA考虑事项部分的指南”，BCP 26，RFC 8126，DOI 10.17487/RFC8126，2017年6月<https://www.rfc-editor.org/info/rfc8126>.
[RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, <https://www.rfc-editor.org/info/rfc8141>.
[RFC8141]Saint Andre，P.和J.Klensin，“统一资源名称（URN）”，RFC 8141，DOI 10.17487/RFC81412017年4月<https://www.rfc-editor.org/info/rfc8141>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8174]Leiba，B.，“RFC 2119关键词中大写与小写的歧义”，BCP 14，RFC 8174，DOI 10.17487/RFC8174，2017年5月<https://www.rfc-editor.org/info/rfc8174>.
[S.R0048-A] 3GPP2, "3G Mobile Equipment Identifier (MEID) - Stage 1, Version 4.0", Stage 1, Version 4.0, 3GPP2 S.R0048-A, June 2005, <http://www.3gpp2.org/Public_html/specs/ S.R0048-A_v4.0_050630.pdf>.
[S.R0048-A]3GPP2，“3G移动设备标识符（MEID）-第1阶段，版本4.0”，第1阶段，版本4.0，3GPP2 S.R0048-A，2005年6月<http://www.3gpp2.org/Public_html/specs/ S.R0048-A_v4.0_050630.pdf>。
[SC.R4002-0] 3GPP2, "GHA (Global Hexadecimal Administrator) Assignment Guidelines and Procedures for Mobile Equipment Identifier (MEID) and Short Form Expanded UIM Identifier (SF_EUIMID)", 3GPP2 TS SC.R4002-0, Version 12.0, December 2016, <http://www.3gpp2.org/Public_html/Specs/SC.R4002-0_v 12.0_GHA_%20Guidelines_for_MEID_December_2016.pdf>.
[SC.R4002-0]3GPP2，“GHA（全球十六进制管理员）移动设备标识符（MEID）和缩写扩展UIM标识符（SF_EUIMID）的分配指南和程序”，3GPP2 TS SC.R4002-0，版本12.0，2016年12月<http://www.3gpp2.org/Public_html/Specs/SC.R4002-0_v 12.0_GHA_%20 2016年12月的指南。pdf>。
[X.S0008-A] 3GPP2, "MAP Support for the Mobile Equipment Identity (MEID)", 3GPP2 TS X.S0008-A, Version 2.0, March 2014, <http://www.3gpp2.org/Public_html/Specs/ X.S0008-A_v2.0_20140321.PDF>.
[X.S0008-A]3GPP2，“移动设备标识（MEID）的地图支持”，3GPP2 TS X.S0008-A，版本2.0，2014年3月<http://www.3gpp2.org/Public_html/Specs/ X.S0008-A_v2.0_20140321.PDF>。
[RFC7254] Montemurro, M., Ed., Allen, A., McDonald, D., and P. Gosden, "A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)", RFC 7254, DOI 10.17487/RFC7254, May 2014, <https://www.rfc-editor.org/info/rfc7254>.
[RFC7254]Montemurro，M.，Ed.，Allen，A.，McDonald，D.，和P.Gosden，“全球移动通信系统协会（GSMA）和国际移动站设备标识（IMEI）的统一资源名称空间”，RFC 7254，DOI 10.17487/RFC7254，2014年5月<https://www.rfc-editor.org/info/rfc7254>.
[RFC8465] Atarius, R., Ed., "Using the Mobile Equipment Identity (MEID) URN as an Instance ID", RFC 8465, DOI 10.17487/RFC8465, September 2018, <https://www.rfc-editor.org/info/rfc8465>.
[RFC8465]Atarius，R.，Ed.“使用移动设备标识（MEID）URN作为实例ID”，RFC 8465，DOI 10.17487/RFC8465，2018年9月<https://www.rfc-editor.org/info/rfc8465>.
Acknowledgements
致谢
This document draws heavily on the 3GPP2 work on Numbering, Addressing, and Identification in [S.R0048-A] and also on the style and structure used in [RFC7254] and [RFC4122].
本文件大量借鉴了[S.R0048-A]中关于编号、寻址和标识的3GPP2工作，以及[RFC7254]和[RFC4122]中使用的样式和结构。
The author thanks Ramachandran Subramanian, Alex Gogic, Randall Gellens, and Peter Saint-Andre for detailed comments.
作者感谢Ramachandran Subramanian、Alex Gogic、Randall Gellens和Peter Saint Andre的详细评论。
Author's Address
作者地址
Roozbeh Atarius
罗兹贝·阿塔里斯
Email: ratarius@motorola.com
Email: ratarius@motorola.com