draft-ietf-dmm-4283mnids-05.txt   draft-ietf-dmm-4283mnids-06.txt 
Distributed Mobility Management [dmm] C. Perkins Distributed Mobility Management [dmm] C. Perkins
Internet-Draft Futurewei Internet-Draft Futurewei
Intended status: Standards Track V. Devarapalli Intended status: Standards Track V. Devarapalli
Expires: January 21, 2018 Vasona Networks Expires: May 17, 2018 Vasona Networks
July 20, 2017 November 13, 2017
MN Identifier Types for RFC 4283 Mobile Node Identifier Option MN Identifier Types for RFC 4283 Mobile Node Identifier Option
draft-ietf-dmm-4283mnids-05.txt draft-ietf-dmm-4283mnids-06.txt
Abstract Abstract
Additional Identifier Type Numbers are defined for use with the Additional Identifier Type Numbers are defined for use with the
Mobile Node Identifier Option for MIPv6 (RFC 4283). Mobile Node Identifier Option for MIPv6 (RFC 4283).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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). 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 https://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 January 21, 2018. This Internet-Draft will expire on May 17, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 (https://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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
skipping to change at page 9, line 24 skipping to change at page 9, line 24
This document does not introduce any security mechanisms, and does This document does not introduce any security mechanisms, and does
not have any impact on existing security mechanisms. not have any impact on existing security mechanisms.
Mobile Node Identifiers such as those described in this document are Mobile Node Identifiers such as those described in this document are
considered to be private information. If used in the MNID extension considered to be private information. If used in the MNID extension
as defined in [RFC4283], the packet including the MNID extension MUST as defined in [RFC4283], the packet including the MNID extension MUST
be encrypted so that no personal information or trackable identifiers be encrypted so that no personal information or trackable identifiers
is inadvertently disclosed to passive observers. Operators can is inadvertently disclosed to passive observers. Operators can
potentially apply IPsec Encapsulating Security Payload (ESP) potentially apply IPsec Encapsulating Security Payload (ESP)
[RFC4303], with confidentiality and integrity protection for [RFC4303], in transport mode, with confidentiality and integrity
protecting the identity and location information. protection for protecting the identity and location information in
Mobile IPv6 signaling messages.
Some MNIDs contain sensitive identifiers which, as used in protocols Some MNIDs contain sensitive identifiers which, as used in protocols
specified by other SDOs, are only used for signaling during initial specified by other SDOs, are only used for signaling during initial
network entry. In such protocols, subsequent exchanges then rely on network entry. In such protocols, subsequent exchanges then rely on
a temporary identifier allocated during the initial network entry. a temporary identifier allocated during the initial network entry.
Managing the association between long-lived and temporary identifiers Managing the association between long-lived and temporary identifiers
is outside the scope of this document. is outside the scope of this document.
6. IANA Considerations 6. IANA Considerations
skipping to change at page 11, line 21 skipping to change at page 11, line 21
Joseph Salowey, Linda Dunbar, and Mirja Kuehlewind for their helpful Joseph Salowey, Linda Dunbar, and Mirja Kuehlewind for their helpful
comments. comments.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
C., and M. Carney, "Dynamic Host Configuration Protocol C., and M. Carney, "Dynamic Host Configuration Protocol
for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
2003, <http://www.rfc-editor.org/info/rfc3315>. 2003, <https://www.rfc-editor.org/info/rfc3315>.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, Unique IDentifier (UUID) URN Namespace", RFC 4122,
DOI 10.17487/RFC4122, July 2005, DOI 10.17487/RFC4122, July 2005,
<http://www.rfc-editor.org/info/rfc4122>. <https://www.rfc-editor.org/info/rfc4122>.
[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 Chowdhury, "Mobile Node Identifier Option for Mobile IPv6
(MIPv6)", RFC 4283, DOI 10.17487/RFC4283, November 2005, (MIPv6)", RFC 4283, DOI 10.17487/RFC4283, November 2005,
<http://www.rfc-editor.org/info/rfc4283>. <https://www.rfc-editor.org/info/rfc4283>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <http://www.rfc-editor.org/info/rfc4291>. 2006, <https://www.rfc-editor.org/info/rfc4291>.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, DOI 10.17487/RFC4303, December 2005, RFC 4303, DOI 10.17487/RFC4303, December 2005,
<http://www.rfc-editor.org/info/rfc4303>. <https://www.rfc-editor.org/info/rfc4303>.
[RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based [RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based
DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355, DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355,
DOI 10.17487/RFC6355, August 2011, DOI 10.17487/RFC6355, August 2011,
<http://www.rfc-editor.org/info/rfc6355>. <https://www.rfc-editor.org/info/rfc6355>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<http://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
8.2. Informative References 8.2. Informative References
[EANUCCGS] [EANUCCGS]
EAN International and the Uniform Code Council, "General EAN International and the Uniform Code Council, "General
EAN.UCC Specifications Version 5.0", Jan 2004. EAN.UCC Specifications Version 5.0", Jan 2004.
[EPC-Tag-Data] [EPC-Tag-Data]
EPCglobal Inc., "EPC(TM) Generation 1 Tag Data Standards EPCglobal Inc., "EPC(TM) Generation 1 Tag Data Standards
Version 1.1 Rev.1.27 Version 1.1 Rev.1.27
skipping to change at page 12, line 38 skipping to change at page 12, line 38
2001. 2001.
[IEEE802-eui64] [IEEE802-eui64]
IEEE, "Guidelines for 64-Bit Global Identifier (EUI-64) IEEE, "Guidelines for 64-Bit Global Identifier (EUI-64)
https://standards.ieee.org/develop/regauth/tut/eui.pdf64", https://standards.ieee.org/develop/regauth/tut/eui.pdf64",
2001. 2001.
[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, Arkko, "Diameter Base Protocol", RFC 3588,
DOI 10.17487/RFC3588, September 2003, DOI 10.17487/RFC3588, September 2003,
<http://www.rfc-editor.org/info/rfc3588>. <https://www.rfc-editor.org/info/rfc3588>.
[RFID-DoD-spec] [RFID-DoD-spec]
Department of Defense, "United States Department of Department of Defense, "United States Department of
Defense Suppliers Passive RFID Information Guide (Version Defense Suppliers Passive RFID Information Guide (Version
15.0)", January 2010. 15.0)", January 2010.
[ThreeGPP-IDS] [ThreeGPP-IDS]
3rd Generation Partnership Project, "3GPP Technical 3rd Generation Partnership Project, "3GPP Technical
Specification 23.003 V8.4.0: Technical Specification Group Specification 23.003 V8.4.0: Technical Specification Group
Core Network and Terminals; Numbering, addressing and Core Network and Terminals; Numbering, addressing and
skipping to change at line 570 skipping to change at page 13, line 21
USA USA
Phone: +1-408-330-4586 Phone: +1-408-330-4586
Email: charliep@computer.org Email: charliep@computer.org
Vijay Devarapalli Vijay Devarapalli
Vasona Networks Vasona Networks
2900 Lakeside Drive, Suite 180 2900 Lakeside Drive, Suite 180
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
Email: dvijay@gmail.com
 End of changes. 16 change blocks. 
17 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/