Internet Engineering Task Force (IETF) C. Perkins
Request for Comments: 8371 Futurewei
Category: Standards Track V. Devarapalli
ISSN: 2070-1721 Vasona Networks
July 2018
Internet Engineering Task Force (IETF) C. Perkins
Request for Comments: 8371 Futurewei
Category: Standards Track V. Devarapalli
ISSN: 2070-1721 Vasona Networks
July 2018
Mobile Node Identifier Types for MIPv6
MIPv6的移动节点标识符类型
Abstract
摘要
This document defines additional identifier type numbers for use with the mobile node identifier option for Mobile IPv6 (MIPv6) as defined by RFC 4283.
本文档定义了其他标识符类型号，用于RFC 4283定义的移动IPv6（MIPv6）的移动节点标识符选项。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
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). Further information on Internet Standards is available in Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（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/rfc8371.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问https://www.rfc-editor.org/info/rfc8371.
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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. New Mobile Node Identifier Types . . . . . . . . . . . . . . 4
4. Descriptions of MN Identifier Types . . . . . . . . . . . . . 4
4.1. Description of the IPv6 Address Type . . . . . . . . . . 4
4.2. Description of the IMSI MN Identifier Type . . . . . . . 5
4.3. Description of the EUI-48 Address Type . . . . . . . . . 5
4.4. Description of the EUI-64 Address Type . . . . . . . . . 5
4.5. Description of the DUID Type . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. RFID Types . . . . . . . . . . . . . . . . . . . . . 9
A.1. Description of the RFID Types . . . . . . . . . . . . . . 13
A.1.1. Description of the RFID-SGTIN-64 Type . . . . . . . . 14
A.1.2. Description of the RFID-SGTIN-96 Type . . . . . . . . 14
A.1.3. Description of the RFID-SSCC-64 Type . . . . . . . . 14
A.1.4. Description of the RFID-SSCC-96 Type . . . . . . . . 14
A.1.5. Description of the RFID-SGLN-64 Type . . . . . . . . 14
A.1.6. Description of the RFID-SGLN-96 Type . . . . . . . . 14
A.1.7. Description of the RFID-GRAI-64 Type . . . . . . . . 15
A.1.8. Description of the RFID-GRAI-96 Type . . . . . . . . 15
A.1.9. Description of the RFID-GIAI-64 Type . . . . . . . . 15
A.1.10. Description of the RFID-GIAI-96 Type . . . . . . . . 15
A.1.11. Description of the RFID-DoD-64 Type . . . . . . . . . 15
A.1.12. Description of the RFID-DoD-96 Type . . . . . . . . . 15
A.1.13. Description of the RFID URI Types . . . . . . . . . . 15
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. New Mobile Node Identifier Types . . . . . . . . . . . . . . 4
4. Descriptions of MN Identifier Types . . . . . . . . . . . . . 4
4.1. Description of the IPv6 Address Type . . . . . . . . . . 4
4.2. Description of the IMSI MN Identifier Type . . . . . . . 5
4.3. Description of the EUI-48 Address Type . . . . . . . . . 5
4.4. Description of the EUI-64 Address Type . . . . . . . . . 5
4.5. Description of the DUID Type . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. RFID Types . . . . . . . . . . . . . . . . . . . . . 9
A.1. Description of the RFID Types . . . . . . . . . . . . . . 13
A.1.1. Description of the RFID-SGTIN-64 Type . . . . . . . . 14
A.1.2. Description of the RFID-SGTIN-96 Type . . . . . . . . 14
A.1.3. Description of the RFID-SSCC-64 Type . . . . . . . . 14
A.1.4. Description of the RFID-SSCC-96 Type . . . . . . . . 14
A.1.5. Description of the RFID-SGLN-64 Type . . . . . . . . 14
A.1.6. Description of the RFID-SGLN-96 Type . . . . . . . . 14
A.1.7. Description of the RFID-GRAI-64 Type . . . . . . . . 15
A.1.8. Description of the RFID-GRAI-96 Type . . . . . . . . 15
A.1.9. Description of the RFID-GIAI-64 Type . . . . . . . . 15
A.1.10. Description of the RFID-GIAI-96 Type . . . . . . . . 15
A.1.11. Description of the RFID-DoD-64 Type . . . . . . . . . 15
A.1.12. Description of the RFID-DoD-96 Type . . . . . . . . . 15
A.1.13. Description of the RFID URI Types . . . . . . . . . . 15
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
The "Mobile Node Identifier Option for Mobile IPv6 (MIPv6)" [RFC4283] has proved to be a popular design tool for providing identifiers for mobile nodes during authentication procedures with Authentication, Authorization, and Accounting (AAA) protocols such as Diameter [RFC6733]. To date, only a single type of identifier has been specified, namely the Mobile Node (MN) NAI. Other types of identifiers are in common use and are even referenced in RFC 4283. In this document, we propose adding some basic identifier types that are defined in various telecommunications standards, including types for International Mobile Subscriber Identity (IMSI) [ThreeGPP-IDS], Packet - Temporary Mobile Subscriber Identity (P-TMSI) [ThreeGPP-IDS], International Mobile station Equipment Identities (IMEI) [ThreeGPP-IDS], and Globally Unique Temporary UE Identity (GUTI) [ThreeGPP-IDS]. In addition, we specify the IPv6 address itself and IEEE MAC-layer addresses as Mobile Node identifiers. Defining identifiers that are tied to the physical elements of the device (e.g., the MAC address) help in deployment of Mobile IP because, in many cases, such identifiers are the most natural means for uniquely identifying the device and will avoid additional lookup steps that might be needed if other identifiers were used.
“移动IPv6的移动节点标识符选项（MIPv6）”[RFC4283]已被证明是一种流行的设计工具，用于在身份验证、授权和计费（AAA）协议（如Diameter[RFC6733]）的身份验证过程中为移动节点提供标识符。迄今为止，仅指定了一种标识符，即移动节点（MN）NAI。其他类型的标识符是常用的，甚至在RFC 4283中引用。在本文件中，我们建议添加一些在各种电信标准中定义的基本标识符类型，包括国际移动用户标识（IMSI）[3GPP ID]、分组临时移动用户标识（P-TMSI）[3GPP ID]、国际移动站设备标识（IMEI）[3GPP ID]，和全局唯一临时UE标识（GUTI）[3GPP ID]。此外，我们将IPv6地址本身和IEEE MAC层地址指定为移动节点标识符。定义绑定到设备的物理元素（例如，MAC地址）的标识符有助于移动IP的部署，因为在许多情况下，此类标识符是唯一标识设备的最自然的手段，并且将避免使用其他标识符时可能需要的额外查找步骤。
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]所述进行解释。
The following types of identifiers are commonly used to identify mobile nodes. For each type, references are provided with full details on the format of the type of identifier.
以下类型的标识符通常用于标识移动节点。对于每种类型，都会提供参考，并提供有关标识符类型格式的完整详细信息。
+--------------+-----------------------------------+----------------+
| Identifier | Description | Reference |
| Type | | |
+--------------+-----------------------------------+----------------+
| IPv6 Address | | [RFC4291] |
| | | |
| IMSI | International Mobile Subscriber | [ThreeGPP-IDS] |
| | Identity | |
| | | |
| P-TMSI | Packet - Temporary Mobile | [ThreeGPP-IDS] |
| | Subscriber Identity | |
| | | |
| GUTI | Globally Unique Temporary UE | [ThreeGPP-IDS] |
| | Identity | |
| | | |
| EUI-48 | 48-Bit Extended Unique Identifier | [IEEE802] |
| Address | | |
| | | |
| EUI-64 | 64-Bit Extended Unique Identifier | [IEEE802] |
| Address | | |
| | | |
| DUID | DHCPv6 Unique Identifier | [RFC3315] |
+--------------+-----------------------------------+----------------+
+--------------+-----------------------------------+----------------+
| Identifier | Description | Reference |
| Type | | |
+--------------+-----------------------------------+----------------+
| IPv6 Address | | [RFC4291] |
| | | |
| IMSI | International Mobile Subscriber | [ThreeGPP-IDS] |
| | Identity | |
| | | |
| P-TMSI | Packet - Temporary Mobile | [ThreeGPP-IDS] |
| | Subscriber Identity | |
| | | |
| GUTI | Globally Unique Temporary UE | [ThreeGPP-IDS] |
| | Identity | |
| | | |
| EUI-48 | 48-Bit Extended Unique Identifier | [IEEE802] |
| Address | | |
| | | |
| EUI-64 | 64-Bit Extended Unique Identifier | [IEEE802] |
| Address | | |
| | | |
| DUID | DHCPv6 Unique Identifier | [RFC3315] |
+--------------+-----------------------------------+----------------+
Table 1: Mobile Node Identifier Description
表1：移动节点标识符说明
This section provides descriptions for the various MN identifier types.
本节提供各种MN标识符类型的说明。
The IPv6 address [RFC4291] is encoded as a 16-octet string containing a full IPv6 address that has been assigned to the mobile node. The IPv6 address MUST be a unicast routable IPv6 address. Multicast addresses, link-local addresses, and the unspecified IPv6 address MUST NOT be used. IPv6 Unique Local Addresses (ULAs) MAY be used as long as any security operations making use of the ULA also take into account the domain in which the ULA is guaranteed to be unique.
IPv6地址[RFC4291]编码为16个八位字节的字符串，其中包含已分配给移动节点的完整IPv6地址。IPv6地址必须是单播可路由IPv6地址。不得使用多播地址、链路本地地址和未指定的IPv6地址。只要使用ULA的任何安全操作也考虑到保证ULA唯一的域，就可以使用IPv6唯一本地地址（ULA）。
The International Mobile Subscriber Identity (IMSI) [ThreeGPP-IDS] is at most 15 decimal digits (i.e., digits from 0 through 9). The IMSI MUST be encoded as a string of octets in network order (i.e., high to low for all digits), where each digit occupies 4 bits. If needed for full octet size, the last digit MUST be padded with 0xf. For instance, an example IMSI 123456123456789 would be encoded as follows:
国际移动用户标识（IMSI）[3GPP ID]最多为15位十进制数字（即从0到9的数字）。IMSI必须按照网络顺序（即，所有数字从高到低）编码为八位字节字符串，其中每个数字占4位。如果需要完整的八位字节大小，最后一个数字必须用0xf填充。例如，示例IMSI 1234561123456789将被编码如下：
0x12, 0x34, 0x56, 0x12, 0x34, 0x56, 0x78, 0x9f
0x12、0x34、0x56、0x12、0x34、0x56、0x78、0x9f
The IEEE EUI-48 address [IEEE802-GUIDELINES] is encoded as 6 octets containing the IEEE EUI-48 address.
IEEE EUI-48地址[IEEE802-GUIDELINES]编码为包含IEEE EUI-48地址的6个八位字节。
The IEEE EUI-64 address [IEEE802-GUIDELINES] is encoded as 8 octets containing the full IEEE EUI-64 address.
IEEE EUI-64地址[IEEE802-GUIDELINES]编码为8个八位字节，包含完整的IEEE EUI-64地址。
The DUID is the DHCPv6 Unique Identifier [RFC3315]. There are various types of DUIDs, which are distinguished by an initial two-octet type field. Clients and servers MUST treat DUIDs as opaque values and MUST only compare DUIDs for equality.
DUID是DHCPv6唯一标识符[RFC3315]。有各种类型的DUID，它们通过初始的两个八位组类型字段来区分。客户端和服务器必须将DUID视为不透明值，并且必须仅比较DUID是否相等。
This document does not introduce any security mechanisms and does not have any impact on existing security mechanisms.
本文件不引入任何安全机制，也不对现有安全机制产生任何影响。
Mobile node identifiers such as those described in this document are considered to be private information. If used in the MN identifier extension as defined in [RFC4283], the packet including the MN identifier extension MUST be encrypted so that no personal information or trackable identifiers are inadvertently disclosed to passive observers. Operators can potentially apply IPsec Encapsulating Security Payload (ESP) [RFC4303] in transport mode with confidentiality and integrity protection for protecting the identity and location information in MIPv6 signaling messages.
诸如本文档中描述的那些移动节点标识符被认为是私有信息。如果在[RFC4283]中定义的MN标识符扩展中使用，则必须对包括MN标识符扩展的数据包进行加密，以便不会无意中将个人信息或可跟踪标识符透露给被动观察者。运营商可以在传输模式下潜在地应用IPsec封装安全有效负载（ESP）[RFC4303]，并提供机密性和完整性保护，以保护MIPv6信令消息中的身份和位置信息。
Some MN identifiers contain sensitive identifiers that, as used in protocols specified by other Standards Development Organizations (SDOs), are only used for signaling during initial network entry. In such protocols, subsequent exchanges then rely on a temporary
一些MN标识符包含敏感标识符，如其他标准开发组织（SDO）指定的协议中所使用的，这些标识符仅用于初始网络进入期间的信令。在这种协议中，随后的交换依赖于临时协议
identifier allocated during the initial network entry. Managing the association between long-lived and temporary identifiers is outside the scope of this document.
初始网络输入期间分配的标识符。管理长期标识符和临时标识符之间的关联超出了本文档的范围。
The new mobile node identifier types defined in this document have been assigned values from the "Mobile Node Identifier Option Subtypes" registry. The following values have been registered.
本文档中定义的新移动节点标识符类型已从“移动节点标识符选项子类型”注册表中分配了值。已注册以下值。
+-----------------+------------------------+
| Identifier Type | Identifier Type Number |
+-----------------+------------------------+
| IPv6 Address | 2 |
| IMSI | 3 |
| P-TMSI | 4 |
| EUI-48 address | 5 |
| EUI-64 address | 6 |
| GUTI | 7 |
| DUID | 8 |
| Reserved | 9-15 |
| Unassigned | 16-255 |
+-----------------+------------------------+
+-----------------+------------------------+
| Identifier Type | Identifier Type Number |
+-----------------+------------------------+
| IPv6 Address | 2 |
| IMSI | 3 |
| P-TMSI | 4 |
| EUI-48 address | 5 |
| EUI-64 address | 6 |
| GUTI | 7 |
| DUID | 8 |
| Reserved | 9-15 |
| Unassigned | 16-255 |
+-----------------+------------------------+
Table 2: New Mobile Node Identifier Types
表2：新的移动节点标识符类型
See Section 4 for additional information about the identifier types. The registration procedure is Standards Action [RFC8126]. The expert must ascertain that the identifier type allows unique identification of the mobile device; since all MN identifiers require encryption, there is no additional privacy exposure attendant to the use of new types.
有关标识符类型的更多信息，请参见第4节。注册程序为标准行动[RFC8126]。专家必须确定标识符类型允许移动设备的唯一标识；由于所有MN标识符都需要加密，因此使用新类型不会带来额外的隐私暴露。
[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>.
[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 2003, <https://www.rfc-editor.org/info/rfc3315>.
[RFC3315]Droms，R.，Ed.，Bound，J.，Volz，B.，Lemon，T.，Perkins，C.，和M.Carney，“IPv6的动态主机配置协议（DHCPv6）”，RFC 3315，DOI 10.17487/RFC3315，2003年7月<https://www.rfc-editor.org/info/rfc3315>.
[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 (MIPv6)", RFC 4283, DOI 10.17487/RFC4283, November 2005, <https://www.rfc-editor.org/info/rfc4283>.
[RFC4283]Patel，A.，Leung，K.，Khalil，M.，Akhtar，H.，和K.Chowdhury，“移动IPv6的移动节点标识符选项（MIPv6）”，RFC 4283，DOI 10.17487/RFC4283，2005年11月<https://www.rfc-editor.org/info/rfc4283>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, DOI 10.17487/RFC4291, February 2006, <https://www.rfc-editor.org/info/rfc4291>.
[RFC4291]Hinden，R.和S.Deering，“IP版本6寻址体系结构”，RFC 4291，DOI 10.17487/RFC42912006年2月<https://www.rfc-editor.org/info/rfc4291>.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 4303, DOI 10.17487/RFC4303, December 2005, <https://www.rfc-editor.org/info/rfc4303>.
[RFC4303]Kent，S.，“IP封装安全有效载荷（ESP）”，RFC 4303，DOI 10.17487/RFC4303，2005年12月<https://www.rfc-editor.org/info/rfc4303>.
[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>.
[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>.
[EANUCCGS] EAN International and the Uniform Code Council, "General EAN.UCC Specifications", Version 5.0, January 2004.
[EANUCCGS]EAN国际和统一准则委员会，“通用EAN.UCC规范”，版本5.0，2004年1月。
[EPC-Tag-Data] EPCglobal, Inc., "EPC Generation 1 Tag Data Standards Version 1.1 Rev.1.27", May 2005, <https://www.gs1.org/sites/default/files/docs/epc/ tds_1_1_rev_1_27-standard-20050510.pdf>.
[EPC标签数据]EPCglobal，Inc.，“EPC第1代标签数据标准1.1版1.27版”，2005年5月<https://www.gs1.org/sites/default/files/docs/epc/ tds_1_1_rev_1_27-standard-20050510.pdf>。
[IEEE802] IEEE, "IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture", IEEE 802.
[IEEE802]IEEE，“局域网和城域网的IEEE标准：概述和体系结构”，IEEE 802。
[IEEE802-GUIDELINES] IEEE, "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)", August 2018, <http://standards.ieee.org/develop/regauth/tut/eui.pdf>.
[IEEE802-GUIDELINES]IEEE，“扩展唯一标识符（EUI）、组织唯一标识符（OUI）和公司ID（CID）的使用指南”，2018年8月<http://standards.ieee.org/develop/regauth/tut/eui.pdf>.
[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn, Ed., "Diameter Base Protocol", RFC 6733, DOI 10.17487/RFC6733, October 2012, <https://www.rfc-editor.org/info/rfc6733>.
[RFC6733]Fajardo，V.，Ed.，Arkko，J.，Loughney，J.，和G.Zorn，Ed.，“直径基准协议”，RFC 6733，DOI 10.17487/RFC6733，2012年10月<https://www.rfc-editor.org/info/rfc6733>.
[RFID-DoD-spec] Department of Defense, "United States Department of Defense Suppliers' Passive RFID Information Guide", Version 15.0, January 2010.
[RFID国防部规范]国防部，“美国国防部供应商无源RFID信息指南”，版本15.0，2010年1月。
[RFID-framework] Botero, O., "Heterogeneous RFID framework design, analysis and evaluation", Institut National des Telecommunications, July 2012.
[RFID框架]Botero，O.“异构RFID框架设计、分析和评估”，国家des电信研究所，2012年7月。
[ThreeGPP-IDS] 3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification (Release 15)", 3GPP TS 23.003, V15.3.0, March 2018.
[ThreeGPP ID]3GPP，“第三代合作伙伴项目；技术规范组核心网络和终端；编号、寻址和标识（第15版）”，3GPP TS 23.003，V15.3.0，2018年3月。
[TRACK-IoT] Chaouchi, H., "Heterogeneous IoT Network: TRACK-IoT Plateform", Telecom SudParis, Internal Report, March 2012.
[跟踪物联网]Chaouchi，H.，“异构物联网网络：跟踪物联网平台”，电信SudParis，内部报告，2012年3月。
[Using-RFID-IPv6] IPv6.com, "Using RFID & IPv6", September 2006.
[Using-RFID-IPv6]IPv6.com，“使用RFID和IPv6”，2006年9月。
The material in this non-normative appendix was originally composed for inclusion in the main body of the specification but was moved into an appendix because there was insufficient support for allocating Radio Frequency Identification (RFID) types at the time. It was observed that RFID-based mobile devices may create privacy exposures unless confidentiality is assured for signaling. A specification for eliminating unauthorized RFID tracking based on Layer 2 addresses would be helpful.
本非规范性附录中的材料最初是为了包含在规范主体中，但由于当时没有足够的支持来分配射频识别（RFID）类型，因此被移至附录中。据观察，基于RFID的移动设备可能会造成隐私暴露，除非确保信号的机密性。基于第2层地址消除未经授权的RFID跟踪的规范将很有帮助。
Much of the following text is due to contributions from Hakima Chaouchi. For an overview and some initial suggestions about using RFID with IPv6 on mobile devices, see [Using-RFID-IPv6].
以下文字的大部分是由于Hakima Chaouchi的贡献。有关在移动设备上使用带IPv6的RFID的概述和一些初步建议，请参阅[using-RFID-IPv6]。
In the context of Internet of Things (IoT) and Industry 4.0, vertical domain, efficient inventory, and tracking items are of major interest, and RFID technology is the identification technology in the hardware design of many such items.
在物联网（IoT）和工业4.0的背景下，垂直域、高效库存和跟踪项目是主要的兴趣，而RFID技术是许多此类项目硬件设计中的识别技术。
The "TRACK-IoT" project [TRACK-IoT] [RFID-framework] explored Mobile IPv6 as a mobility management protocol for RFID-based mobile devices.
“追踪物联网”项目[追踪物联网][RFID框架]探索了移动IPv6作为基于RFID的移动设备的移动性管理协议。
1. Passive RFID tags (that have no processing resources) need to be handled by the gateway (likely also the RFID reader), which is then the endpoint of the mobility protocol. It is also the point where the Change of Address (CoA) will be created based on some combination such as the RFID tag and the prefix of that gateway. The point here is to offer the possibility to passive RFID items to get an IPv6 address and take advantage of the mobility framework to follow the mobile device (passive tag on the item). One example scenario that has been proposed, which shows the need for mobility management of passive RFID items, would be pieces of art tagged with passive tags that need to be monitored while transported.
1. 无源RFID标签（没有处理资源）需要由网关（也可能是RFID阅读器）处理，网关是移动协议的端点。这也是地址更改（CoA）将基于某些组合（如RFID标签和该网关的前缀）创建的点。这里的要点是为被动RFID项目提供获得IPv6地址的可能性，并利用移动框架跟踪移动设备（项目上的被动标签）。已经提出的一个示例场景显示了被动RFID项目移动性管理的需要，将是带有被动标签的艺术品，需要在运输过程中进行监控。
2. Using active RFID tags (where the processing resource is available on the tag), the endpoint of the mobility protocol can be hosted directly on the RFID active tag, which is also called an identification sensor. A use case for active RFID tags includes traceability of cold food during mobility (transport). Also, mobility of cars equipped with active RFID tags that we already use for toll payment can be added with mobility management.
2. 通过使用有源RFID标签（标签上有处理资源），移动协议的端点可以直接承载在RFID有源标签上，该有源标签也称为识别传感器。有源RFID标签的用例包括在移动（运输）过程中冷食品的可追溯性。此外，配备有源RFID标签（我们已经用于支付通行费）的汽车的移动性可以添加移动性管理。
One major effort to connect IETF efforts to EPCglobal (RFID standardization) led to the Object Name Service (ONS), which is the DNS version applied for RFID logical names and page information
将IETF工作与EPCglobal（RFID标准化）连接的一项主要工作导致了对象名称服务（ONS），这是应用于RFID逻辑名称和页面信息的DNS版本
retrieval. Attempts have been made to connect IPv6 on the address space to RFID identifier format. Other initiatives started working on gateways to map tag identifiers with IPv6 addresses and build signaling protocols for the application level. For instance, tracking of mobile items equipped with a tag can be triggered remotely by a remote correspondent node until a visiting area where a mobile item equipped with an RFID tag is located. An RFID reader will be added with an IPv6-to-RFID tag translation. One option is to build a home IPv6 address of that tagged item by using the prefix of the home agent combined with the tag RFID identifier of the mobile item; as the tag ID is unique, the home IPv6 address of that item will be also unique. Then, the visiting RFID reader will compose the IPv6 care of address of the tagged mobile item by combining the prefix of the RFID reader with the tag ID of the item. MIPv6 can then normally provide the mobility management of that RFID-tagged item. A different, useful example of tagged items involves items of a factory that can be tracked while they are transported, especially for real-time localization and tracking of precious items transported without GPS. An automotive car manufacturer can assign IPv6 addresses corresponding to RFID-tagged cars or mechanical car parts and build a tracking data set of the mobility not only of the cars, but also of the mechanical pieces.
检索已尝试将地址空间上的IPv6连接到RFID标识符格式。其他计划开始在网关上工作，将标签标识符映射到IPv6地址，并为应用程序级构建信令协议。例如，远程通信节点可以远程触发对配备有标签的移动项目的跟踪，直到配备有RFID标签的移动项目所在的访问区域。RFID阅读器将添加IPv6到RFID标签转换。一个选项是通过使用归属代理的前缀与移动项目的标签RFID标识符组合来构建该标记项目的归属IPv6地址；由于标记ID是唯一的，因此该项目的主IPv6地址也将是唯一的。然后，访问的RFID阅读器将通过将RFID阅读器的前缀与项目的标签ID相结合来组成标记移动项目的IPv6转交地址。然后，MIPv6通常可以提供该RFID标签项目的移动性管理。标签物品的另一个有用的例子是，工厂物品在运输过程中可以被跟踪，特别是在没有GPS的情况下对运输的贵重物品进行实时定位和跟踪。汽车制造商可以分配和RFID标记的汽车或机械汽车部件对应的IPv6地址，并建立一个不仅汽车，而且机械部件移动的跟踪数据集。
The Tag Data Standard promoted by Electronic Product Code (EPC) [EPC-Tag-Data] supports several encoding systems or schemes, which are commonly used in RFID applications, including the following:
由电子产品代码（EPC）[EPC标签数据]推动的标签数据标准支持多种编码系统或方案，这些编码系统或方案通常用于RFID应用，包括：
o RFID-GID (Global Identifier),
o RFID-GID（全局标识符），
o RFID-SGTIN (Serialized Global Trade Item Number),
o RFID-SGTIN（序列化全球贸易商品编号），
o RFID-SSCC (Serial Shipping Container Code),
o RFID-SSCC（串行装运集装箱代码），
o RFID-SGLN (Serialized Global Location Number),
o RFID-SGLN（序列化全局位置号），
o RFID-GRAI (Global Returnable Asset Identifier),
o RFID-GRAI（全球可回收资产标识符），
o RFID-DOD (Department of Defense ID), and
o RFID-DOD（国防部ID），以及
o RFID-GIAI (Global Individual Asset Identifier).
o RFID-GIAI（全球个人资产标识符）。
For each RFID scheme except GID, there are three representations:
对于除GID之外的每个RFID方案，有三种表示：
o a 64-bit binary representation (for example, SGLN-64), excluding GID,
o 一种64位二进制表示（例如，SGLN-64），不包括GID，
o a 96-bit binary representation (SGLN-96), and
o 96位二进制表示（SGLN-96），以及
o a representation as a URI.
o 作为URI的表示。
The URI representation for the RFID is actually a URN. The EPC document has the following language:
RFID的URI表示实际上是一个URN。EPC文件采用以下语言：
All categories of URIs are represented as Uniform Reference Names (URNs) as defined by [RFC2141], where the URN Namespace is epc.
所有类别的URI都表示为[RFC2141]定义的统一引用名称（URN），其中URN命名空间为epc。
The following list includes the above RFID types.
以下列表包括上述RFID类型。
+----------------+--------------------------------+-----------------+
| Identifier | Description | Reference |
| Type | | |
+----------------+--------------------------------+-----------------+
| RFID-SGTIN-64 | 64-bit Serialized Global Trade | [EPC-Tag-Data] |
| | Item Number | |
| RFID-SSCC-64 | 64-bit Serial Shipping | [EPC-Tag-Data] |
| | Container Code | |
| RFID-SGLN-64 | 64-bit Serialized Global | [EPC-Tag-Data] |
| | Location Number | |
| RFID-GRAI-64 | 64-bit Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-DOD-64 | 64-bit Department of Defense | [RFID-DoD-spec] |
| | ID | |
| RFID-GIAI-64 | 64-bit Global Individual Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-GID-96 | 96-bit Global Identifier | [EPC-Tag-Data] |
| RFID-SGTIN-96 | 96-bit Serialized Global Trade | [EPC-Tag-Data] |
| | Item Number | |
| RFID-SSCC-96 | 96-bit Serial Shipping | [EPC-Tag-Data] |
| | Container | |
| RFID-SGLN-96 | 96-bit Serialized Global | [EPC-Tag-Data] |
| | Location Number | |
| RFID-GRAI-96 | 96-bit Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-DOD-96 | 96-bit Department of Defense | [RFID-DoD-spec] |
| | ID | |
| RFID-GIAI-96 | 96-bit Global Individual Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-GID-URI | Global Identifier represented | [EPC-Tag-Data] |
| | as a URI | |
| RFID-SGTIN-URI | Serialized Global Trade Item | [EPC-Tag-Data] |
| | Number represented as a URI | |
| RFID-SSCC-URI | Serial Shipping Container Code | [EPC-Tag-Data] |
| | represented as a URI | |
| RFID-SGLN-URI | Global Location Number | [EPC-Tag-Data] |
| | represented as a URI | |
| RFID-GRAI-URI | Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier represented as a | |
| | URI | |
| RFID-DOD-URI | Department of Defense ID | [RFID-DoD-spec] |
| | represented as a URI | |
| RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] |
| | Identifier represented as a | |
| | URI | |
+----------------+--------------------------------+-----------------+
+----------------+--------------------------------+-----------------+
| Identifier | Description | Reference |
| Type | | |
+----------------+--------------------------------+-----------------+
| RFID-SGTIN-64 | 64-bit Serialized Global Trade | [EPC-Tag-Data] |
| | Item Number | |
| RFID-SSCC-64 | 64-bit Serial Shipping | [EPC-Tag-Data] |
| | Container Code | |
| RFID-SGLN-64 | 64-bit Serialized Global | [EPC-Tag-Data] |
| | Location Number | |
| RFID-GRAI-64 | 64-bit Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-DOD-64 | 64-bit Department of Defense | [RFID-DoD-spec] |
| | ID | |
| RFID-GIAI-64 | 64-bit Global Individual Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-GID-96 | 96-bit Global Identifier | [EPC-Tag-Data] |
| RFID-SGTIN-96 | 96-bit Serialized Global Trade | [EPC-Tag-Data] |
| | Item Number | |
| RFID-SSCC-96 | 96-bit Serial Shipping | [EPC-Tag-Data] |
| | Container | |
| RFID-SGLN-96 | 96-bit Serialized Global | [EPC-Tag-Data] |
| | Location Number | |
| RFID-GRAI-96 | 96-bit Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-DOD-96 | 96-bit Department of Defense | [RFID-DoD-spec] |
| | ID | |
| RFID-GIAI-96 | 96-bit Global Individual Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-GID-URI | Global Identifier represented | [EPC-Tag-Data] |
| | as a URI | |
| RFID-SGTIN-URI | Serialized Global Trade Item | [EPC-Tag-Data] |
| | Number represented as a URI | |
| RFID-SSCC-URI | Serial Shipping Container Code | [EPC-Tag-Data] |
| | represented as a URI | |
| RFID-SGLN-URI | Global Location Number | [EPC-Tag-Data] |
| | represented as a URI | |
| RFID-GRAI-URI | Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier represented as a | |
| | URI | |
| RFID-DOD-URI | Department of Defense ID | [RFID-DoD-spec] |
| | represented as a URI | |
| RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] |
| | Identifier represented as a | |
| | URI | |
+----------------+--------------------------------+-----------------+
Table 3: Mobile Node RFID Identifier Description
表3：移动节点RFID标识符说明
The material in this appendix has been either quoted or loosely adapted from [EPC-Tag-Data].
本附录中的材料已被引用或粗略地改编自【EPC标签数据】。
The General Identifier (GID) that is used with RFID is composed of three fields: General Manager Number, Object Class, and Serial Number. The General Manager Number identifies an organizational entity that is responsible for maintaining the numbers in subsequent fields. GID encodings include a fourth field, the header, to guarantee uniqueness in the namespace defined by EPC.
与RFID一起使用的通用标识符（GID）由三个字段组成：总经理编号、对象类和序列号。总经理编号标识负责在后续字段中维护编号的组织实体。GID编码包括第四个字段，即标头，以确保EPC定义的命名空间中的唯一性。
Some of the RFID types depend on the Global Trade Item Number (GTIN) code defined in the EAN.UCC General Specifications [EANUCCGS]. A GTIN identifies a particular class of object, such as a particular kind of product or SKU.
一些RFID类型取决于EAN.UCC通用规范[EANUCCGS]中定义的全球贸易商品编号（GTIN）代码。GTIN标识特定类别的对象，例如特定种类的产品或SKU。
The EPC encoding scheme for SGTIN permits the direct embedding of EAN.UCC System standard GTIN and Serial Number codes on EPC tags. In all cases, the check digit is not encoded. Two encoding schemes are specified, SGTIN-64 (64 bits) and SGTIN-96 (96 bits).
SGTIN的EPC编码方案允许在EPC标签上直接嵌入EAN.UCC系统标准GTIN和序列号代码。在所有情况下，校验位均未编码。指定了两种编码方案，SGTIN-64（64位）和SGTIN-96（96位）。
The Serial Shipping Container Code (SSCC) is defined by the EAN.UCC Specifications. Unlike the GTIN, the SSCC is already intended for assignment to individual objects and therefore does not require additional fields to serve as an EPC pure identity. Two encoding schemes are specified, SSCC-64 (64 bits) and SSCC-96 (96 bits).
串行装运集装箱代码（SSCC）由EAN.UCC规范定义。与GTIN不同，SSCC已经用于分配给单个对象，因此不需要额外的字段作为EPC纯标识。指定了两种编码方案，SSCC-64（64位）和SSCC-96（96位）。
The Global Location Number (GLN) is defined by the EAN.UCC Specifications. A GLN can represent either a discrete, unique physical location such as a warehouse slot, or an aggregate physical location such as an entire warehouse. In addition, a GLN can represent a logical entity that performs a business function such as placing an order. The Serialized Global Location Number (SGLN) includes the Company Prefix, Location Reference, and Serial Number.
全局位置号（GLN）由EAN.UCC规范定义。GLN可以表示离散的、唯一的物理位置（如仓库插槽），也可以表示聚合物理位置（如整个仓库）。此外，GLN可以表示执行业务功能（如下订单）的逻辑实体。序列化全局位置号（SGLN）包括公司前缀、位置参考和序列号。
The Global Returnable Asset Identifier (GRAI) is defined by the General EAN.UCC Specifications. Unlike the GTIN, the GRAI is already intended for assignment to individual objects and therefore does not require any additional fields to serve as an EPC pure identity. The GRAI includes the Company Prefix, Asset Type, and Serial Number.
全局可回收资产标识符（GRAI）由通用EAN.UCC规范定义。与GTIN不同，GRAI已经用于分配给单个对象，因此不需要任何附加字段作为EPC纯标识。GRAI包括公司前缀、资产类型和序列号。
The Global Individual Asset Identifier (GIAI) is defined by the General EAN.UCC Specifications. Unlike the GTIN, the GIAI is already intended for assignment to individual objects and therefore does not require any additional fields to serve as an EPC pure identity. The GRAI includes the Company Prefix and Individual Asset Reference.
全球个人资产标识符（GIAI）由通用EAN.UCC规范定义。与GTIN不同，GIAI已经用于分配给单个对象，因此不需要任何附加字段作为EPC纯标识。GRAI包括公司前缀和个人资产引用。
The DoD Construct identifier is defined by the United States Department of Defense (DoD). This tag data construct may be used to encode tags for shipping goods to the DoD by a supplier who has already been assigned a Commercial and Government Entity (CAGE) code.
国防部构造标识符由美国国防部（DoD）定义。该标签数据结构可用于编码已分配商业和政府实体（CAGE）代码的供应商向国防部运输货物的标签。
The RFID-SGTIN-64 is encoded as specified in [EPC-Tag-Data]. The SGTIN-64 includes five fields: Header, Filter Value (additional data that is used for fast filtering and preselection), Company Prefix Index, Item Reference, and Serial Number. Only a limited number of Company Prefixes can be represented in the 64-bit tag.
RFID-SGTIN-64按照[EPC标签数据]中的规定进行编码。SGTIN-64包括五个字段：标题、筛选值（用于快速筛选和预选的附加数据）、公司前缀索引、项目参考和序列号。64位标记中只能表示有限数量的公司前缀。
The RFID-SGTIN-96 is encoded as specified in [EPC-Tag-Data]. The SGTIN-96 includes six fields: Header, Filter Value, Partition (an indication of where the subsequent Company Prefix and Item Reference numbers are divided), Company Prefix Index, Item Reference, and Serial Number.
RFID-SGTIN-96按照[EPC标签数据]中的规定进行编码。SGTIN-96包括六个字段：标题、筛选值、分区（指示后续公司前缀和项目参考号的划分位置）、公司前缀索引、项目参考和序列号。
The RFID-SSCC-64 is encoded as specified in [EPC-Tag-Data]. The SSCC-64 includes four fields: Header, Filter Value, Company Prefix Index, and Serial Reference. Only a limited number of Company Prefixes can be represented in the 64-bit tag.
RFID-SSCC-64按照[EPC标签数据]中的规定进行编码。SSCC-64包括四个字段：标题、筛选值、公司前缀索引和序列参考。64位标记中只能表示有限数量的公司前缀。
The RFID-SSCC-96 is encoded as specified in [EPC-Tag-Data]. The SSCC-96 includes six fields: Header, Filter Value, Partition, Company Prefix, and Serial Reference, as well as 24 bits that remain unallocated and must be zero.
RFID-SSCC-96按照[EPC标签数据]中的规定进行编码。SSCC-96包括六个字段：标题、筛选值、分区、公司前缀和串行引用，以及24位未分配且必须为零的字段。
The RFID-SGLN-64 type is encoded as specified in [EPC-Tag-Data]. The SGLN-64 includes five fields: Header, Filter Value, Company Prefix Index, Location Reference, and Serial Number.
RFID-SGLN-64类型按照[EPC标签数据]中的规定进行编码。SGLN-64包括五个字段：标题、筛选值、公司前缀索引、位置参考和序列号。
The RFID-SGLN-96 type is encoded as specified in [EPC-Tag-Data]. The SGLN-96 includes six fields: Header, Filter Value, Partition, Company Prefix, Location Reference, and Serial Number.
RFID-SGLN-96类型按照[EPC标签数据]中的规定进行编码。SGLN-96包括六个字段：标题、筛选值、分区、公司前缀、位置参考和序列号。
The RFID-GRAI-64 type is encoded as specified in [EPC-Tag-Data]. The GRAI-64 includes five fields: Header, Filter Value, Company Prefix Index, Asset Type, and Serial Number.
RFID-GRAI-64类型按照[EPC标签数据]中的规定进行编码。GRAI-64包括五个字段：标题、筛选值、公司前缀索引、资产类型和序列号。
The RFID-GRAI-96 type is encoded as specified in [EPC-Tag-Data]. The GRAI-96 includes six fields: Header, Filter Value, Partition, Company Prefix, Asset Type, and Serial Number.
RFID-GRAI-96类型按照[EPC标签数据]中的规定进行编码。GRAI-96包括六个字段：标题、筛选值、分区、公司前缀、资产类型和序列号。
The RFID-GIAI-64 type is encoded as specified in [EPC-Tag-Data]. The GIAI-64 includes four fields: Header, Filter Value, Company Prefix Index, and Individual Asset Reference.
RFID-GIAI-64类型按照[EPC标签数据]中的规定进行编码。GIAI-64包括四个字段：标题、筛选值、公司前缀索引和单个资产引用。
The RFID-GIAI-96 type is encoded as specified in [EPC-Tag-Data]. The GIAI-96 includes five fields: Header, Filter Value, Partition, Company Prefix, and Individual Asset Reference.
RFID-GIAI-96类型按照[EPC标签数据]中的规定进行编码。GIAI-96包括五个字段：标题、筛选值、分区、公司前缀和单个资产引用。
The RFID-DoD-64 type is encoded as specified in [RFID-DoD-spec]. The DoD-64 type includes four fields: Header, Filter Value, Government Managed Identifier, and Serial Number.
RFID-DoD-64类型按照[RFID DoD规范]的规定进行编码。DoD-64类型包括四个字段：标题、筛选值、政府管理的标识符和序列号。
The RFID-DoD-96 type is encoded as specified in [RFID-DoD-spec]. The DoD-96 type includes four fields: Header, Filter Value, Government Managed Identifier, and Serial Number.
RFID-DoD-96类型按照[RFID DoD规范]的规定进行编码。DoD-96类型包括四个字段：标题、筛选值、政府管理的标识符和序列号。
In some cases, it is desirable to encode in URI form a specific encoding of an RFID tag. For example, an application may prefer a URI representation for report preparation. Applications that wish to manipulate any additional data fields on tags may need some representation other than the pure identity forms.
在某些情况下，希望以URI形式编码RFID标签的特定编码。例如，应用程序可能更喜欢报告准备的URI表示。希望操作标记上任何附加数据字段的应用程序可能需要一些表示形式，而不是纯标识形式。
For this purpose, the fields as represented in previous sections are associated with specified fields in the various URI types. For instance, the URI may have fields such as CompanyPrefix,
为此，前面部分中表示的字段与各种URI类型中的指定字段相关联。例如，URI可能有CompanyPrefix等字段，
ItemReference, or SerialNumber. For details and encoding specifics, consult [EPC-Tag-Data].
ItemReference或SerialNumber。有关详细信息和编码细节，请参阅[EPC标签数据]。
Acknowledgements
致谢
The authors wish to acknowledge Hakima Chaouchi, Tatuya Jinmei, Jouni Korhonen, Sri Gundavelli, Suresh Krishnan, Dapeng Liu, Dale Worley, Joseph Salowey, Linda Dunbar, and Mirja Kuehlewind for their helpful comments. The authors also wish to acknowledge the RFC Editor for a number of valuable suggestions and updates during the final stages of producing this document.
作者希望感谢Hakima Chaouchi、Tatuya Jinmei、Jouni Korhonen、Sri Gundavelli、Suresh Krishnan、Dapeng Liu、Dale Worley、Joseph Salowey、Linda Dunbar和Mirja Kuehlewind的有益评论。作者还希望感谢RFC编辑在制作本文件的最后阶段提出的许多有价值的建议和更新。
Authors' Addresses
作者地址
Charles E. Perkins Futurewei Inc. 2330 Central Expressway Santa Clara, CA 95050 United States of America
Charles E.Perkins Futurewei Inc.美国加利福尼亚州圣克拉拉中央高速公路2330号，邮编95050
Phone: +1-408-330-4586
Email: charliep@computer.org
Phone: +1-408-330-4586
Email: charliep@computer.org
Vijay Devarapalli Vasona Networks 2900 Lakeside Drive, Suite 180 Santa Clara, CA 95054 United States of America
Vijay Devarapalli Vasona Networks美国加利福尼亚州圣克拉拉湖边大道2900号180室，邮编95054
Email: dvijay@gmail.com
Email: dvijay@gmail.com