draft-ietf-dhc-mac-assign-02.txt   draft-ietf-dhc-mac-assign-03.txt 
Dynamic Host Configuration (DHC) B. Volz Dynamic Host Configuration (DHC) B. Volz
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track T. Mrugalski Intended status: Standards Track T. Mrugalski
Expires: July 10, 2020 ISC Expires: July 16, 2020 ISC
CJ. Bernardos CJ. Bernardos
UC3M UC3M
January 7, 2020 January 13, 2020
Link-Layer Addresses Assignment Mechanism for DHCPv6 Link-Layer Addresses Assignment Mechanism for DHCPv6
draft-ietf-dhc-mac-assign-02 draft-ietf-dhc-mac-assign-03
Abstract Abstract
In certain environments, e.g. large scale virtualization deployments, In certain environments, e.g. large scale virtualization deployments,
new devices are created in an automated manner. Such devices new devices are created in an automated manner. Such devices
typically have their link-layer (MAC) addresses randomized. With typically have their link-layer (MAC) addresses randomized. With
sufficient scale, the likelihood of collision is not acceptable. sufficient scale, the likelihood of collision is not acceptable.
Therefore an allocation mechanism is required. This draft proposes Therefore an allocation mechanism is required. This draft proposes
an extension to DHCPv6 that allows a scalable approach to link-layer an extension to DHCPv6 that allows a scalable approach to link-layer
address assignments. address assignments.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 https://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 July 10, 2020. This Internet-Draft will expire on July 16, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://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
skipping to change at page 2, line 31 skipping to change at page 2, line 31
7. Requesting Addresses . . . . . . . . . . . . . . . . . . . . 8 7. Requesting Addresses . . . . . . . . . . . . . . . . . . . . 8
8. Renewing Addresses . . . . . . . . . . . . . . . . . . . . . 9 8. Renewing Addresses . . . . . . . . . . . . . . . . . . . . . 9
9. Releasing Addresses . . . . . . . . . . . . . . . . . . . . . 10 9. Releasing Addresses . . . . . . . . . . . . . . . . . . . . . 10
10. Option Definitions . . . . . . . . . . . . . . . . . . . . . 10 10. Option Definitions . . . . . . . . . . . . . . . . . . . . . 10
10.1. Identity Association for Link-Layer Addresses Option . . 10 10.1. Identity Association for Link-Layer Addresses Option . . 10
10.2. Link-Layer Addresses Option . . . . . . . . . . . . . . 12 10.2. Link-Layer Addresses Option . . . . . . . . . . . . . . 12
11. Selecting Link Layer Addresses for Assignment to an IA_LL . . 14 11. Selecting Link Layer Addresses for Assignment to an IA_LL . . 14
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
13. Security Considerations . . . . . . . . . . . . . . . . . . . 15 13. Security Considerations . . . . . . . . . . . . . . . . . . . 15
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 15 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 15
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
15.1. Normative References . . . . . . . . . . . . . . . . . . 15 15.1. Normative References . . . . . . . . . . . . . . . . . . 16
15.2. Informative References . . . . . . . . . . . . . . . . . 16 15.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. IEEE 802c Summary . . . . . . . . . . . . . . . . . 17 Appendix A. IEEE 802c Summary . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
There are several new deployment types that deal with a large number There are several new deployment types that deal with a large number
of devices that need to be initialized. One of them is a scenario of devices that need to be initialized. One of them is a scenario
where virtual machines (VMs) are created on a massive scale. where virtual machines (VMs) are created on a massive scale.
Typically the new VM instances are assigned a random link-layer (MAC) Typically the new VM instances are assigned a random link-layer (MAC)
skipping to change at page 15, line 7 skipping to change at page 15, line 7
client's link. client's link.
For Ethernet / IEEE 802 MAC addresses, a server MAY use additional For Ethernet / IEEE 802 MAC addresses, a server MAY use additional
options supplied by a relay agent or client to select the quadrant options supplied by a relay agent or client to select the quadrant
(see Appendix A) from which addresses are to be assigned. This MAY (see Appendix A) from which addresses are to be assigned. This MAY
include new options, such as those specified in include new options, such as those specified in
[I-D.ietf-dhc-slap-quadrant]. [I-D.ietf-dhc-slap-quadrant].
12. IANA Considerations 12. IANA Considerations
IANA is kindly requested to assign new value for options OPTION_LL IANA is requested to assign the OPTION_IA_LL (tbd1) option code from
(tbd1) and OPTION_LLADDR (tbd2) and add those values to the DHCPv6 the DHCPv6 "Option Codes" registry maintained at
Option Codes registry maintained at http://www.iana.org/assignments/ http://www.iana.org/assignments/dhcpv6-parameters and use the
dhcpv6-parameters. following data when adding the option to the registry:
Value: tbd1
Description: OPTION_IA_LL
Client ORO: No
Singleton Option: No
Reference: this document
IANA is requested to assign the OPTION_LLADDR (tbd2) option code from
the DHCPv6 "Option Codes" registry maintained at
http://www.iana.org/assignments/dhcpv6-parameters and use the
following data when adding the option to the registry:
Value: tbd2
Description: OPTION_LLADDR
Client ORO: No
Singleton Option: No
Reference: this document
13. Security Considerations 13. Security Considerations
See [RFC8415] for the DHCPv6 security considerations. See [RFC8200] See [RFC8415] for the DHCPv6 security considerations. See [RFC8200]
for the IPv6 security considerations. for the IPv6 security considerations.
There is a possibility of the same link-layer address being used by There is a possibility of the same link-layer address being used by
more than one device if not all parties on a link use this mechanism more than one device if not all parties on a link use this mechanism
to obtain a link-layer address from the space assigned to the DHCP to obtain a link-layer address from the space assigned to the DHCP
server. It is also possible that a bad actor purposely uses a server. It is also possible that a bad actor purposely uses a
skipping to change at page 16, line 15 skipping to change at page 16, line 30
[RFC8415] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A., [RFC8415] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A.,
Richardson, M., Jiang, S., Lemon, T., and T. Winters, Richardson, M., Jiang, S., Lemon, T., and T. Winters,
"Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
RFC 8415, DOI 10.17487/RFC8415, November 2018, RFC 8415, DOI 10.17487/RFC8415, November 2018,
<https://www.rfc-editor.org/info/rfc8415>. <https://www.rfc-editor.org/info/rfc8415>.
15.2. Informative References 15.2. Informative References
[I-D.ietf-dhc-slap-quadrant] [I-D.ietf-dhc-slap-quadrant]
Bernardos, C. and A. Mourad, "SLAP quadrant selection Bernardos, C. and A. Mourad, "SLAP quadrant selection
options for DHCPv6", draft-ietf-dhc-slap-quadrant-01 (work options for DHCPv6", draft-ietf-dhc-slap-quadrant-02 (work
in progress), July 2019. in progress), January 2020.
[IEEE-802-Tutorial] [IEEE-802-Tutorial]
Thaler, P., "Emerging IEEE 802 Work on MAC Addressing", Thaler, P., "Emerging IEEE 802 Work on MAC Addressing",
<https://datatracker.ietf.org/meeting/96/materials/slides- <https://datatracker.ietf.org/meeting/96/materials/slides-
96-edu-ieee802work-0/>. 96-edu-ieee802work-0/>.
[IEEE-802.11-02-109r0] [IEEE-802.11-02-109r0]
Edney, J., Haverinen, H., Honkanen, J-P., and P. Orava, Edney, J., Haverinen, H., Honkanen, J-P., and P. Orava,
"Temporary MAC address for anonymity", "Temporary MAC address for anonymity",
<https://mentor.ieee.org/802.11/dcn/02/11-02-0109-00-000i- <https://mentor.ieee.org/802.11/dcn/02/11-02-0109-00-000i-
 End of changes. 7 change blocks. 
12 lines changed or deleted 29 lines changed or added

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