{"id":3327,"date":"2015-05-18T21:37:07","date_gmt":"2015-05-18T21:37:07","guid":{"rendered":"https:\/\/live-infoblox-blog.pantheonsite.io\/?p=3327"},"modified":"2020-05-06T10:30:12","modified_gmt":"2020-05-06T17:30:12","slug":"dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/","title":{"rendered":"DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)"},"content":{"rendered":"<p>In my last post we looked briefly at a key difference between DHCPv6 and DHCPv4: the use of elements other than just the MAC address to\u00a0identify to which host and interface a particular DHCP lease belongs. Among these\u00a0DHCPv6\u00a0identification\u00a0elements the DHCP Unique Identifier (or DUID) in is the closest thing to how\u00a0a MAC address is used in DHCPv4.<\/p>\n<p>As quoted from\u00a0<a href=\"https:\/\/tools.ietf.org\/html\/rfc3315\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6)<\/a>: &#8220;DHCP servers use DUIDs to identify clients for the selection of configuration parameters and in the association of IAs with clients. DHCP clients use DUIDs to identify a server in messages where a server needs to be identified.&#8221;<\/p>\n<p>The more granular\u00a0host and interface identification\u00a0mechanism\u00a0facilitated by the DUID (and associated elements)\u00a0is arguably better suited to\u00a0a\u00a0IPv6-enabled\u00a0LAN\u00a0environment where interfaces have multiple addresses of different scopes. But enterprise LAN administration practice has long relied on the use of the MAC address to\u00a0reserve address leases\u00a0for particular hosts\u00a0in DHCPv4\u00a0(along with practices not directly related to DHCP such as using the MAC to control access to the network and help track host\u00a0hardware).<\/p>\n<p><a href=\"https:\/\/tools.ietf.org\/html\/rfc6939\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 6939,\u00a0<i>Client Link-Layer Address Option in DHCPv6<\/i><\/a>, offers &#8220;an optional mechanism and the related\u00a0DHCPv6 option to allow first-hop DHCPv6 relay agents (relay agents\u00a0that are connected to the same link as the client) to provide the\u00a0client&#8217;s link-layer address in the DHCPv6 messages being sent towards\u00a0the server.\u201d\u00a0As we discussed in the last post, if the server is on the same link as the client, the MAC address of the originating host\u00a0can always be learned from the layer 2 frame.<\/p>\n<p>From the description, it sounds like RFC 6939 offers a way to preserve the\u00a0lease reservation method used in\u00a0DHCPv4. It would also allow simpler correlation of a host with both IPv4 and IPv6 addresses for management purposes.\u00a0Sounds great, right? But do DHCPv6 servers support this option yet?<\/p>\n<p>Well after I published the first part of this blog, a colleague pointed me to a\u00a0<a href=\"http:\/\/www.insinuator.net\/2015\/02\/is-rfc-6939-support-finally-here-checking-the-implementation-of-the-client-link-layer-address-option-in-dhcpv6\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">recent post from\u00a0Enno Rey\u00a0and Antonios Atlasis<\/a>\u00a0on\u00a0the\u00a0blog\u00a0over at Enno\u2019s excellent Infosec\/IPv6 site,\u00a0<a href=\"http:\/\/www.insinuator.net\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Insinuator<\/a>. As chance would have it, Antonios recently tested exactly the above\u00a0question\u00a0with both ISC DHCP\u00a04.3 and Cisco IOS XE. Seems I was picking up Enno&#8217;s and Antonios\u2019 powerful brainwaves through The Cosmic Ether\u00a0when I chose (er,\u00a0thought I was choosing) the subject to blog about.\u00a0Please do yourself a favor and\u00a0follow the link to read the whole post.<\/p>\n<p>I\u2019ll be back a couple of weeks with a blog discussing (the at least) 3 things that will sink your IPv6 adoption initiative.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In my last post we looked briefly at a key difference between DHCPv6 and DHCPv4: the use of elements other than just the MAC address to\u00a0identify to which host and interface a particular DHCP lease belongs. Among these\u00a0DHCPv6\u00a0identification\u00a0elements the DHCP Unique Identifier (or DUID) in is the closest thing to how\u00a0a MAC address is used [&hellip;]<\/p>\n","protected":false},"author":319,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[17],"tags":[50,51],"class_list":{"0":"post-3327","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-ipv6-coe","7":"tag-dhcp","8":"tag-ipam","9":"entry"},"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.3 (Yoast SEO v27.3) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)<\/title>\n<meta name=\"description\" content=\"In my last post we looked briefly at a key difference between DHCPv6 and DHCPv4: the use of elements other than just the MAC address to identify to which host and interface a particular DHCP lease belongs.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)\" \/>\n<meta property=\"og:description\" content=\"In my last post we looked briefly at a key difference between DHCPv6 and DHCPv4: the use of elements other than just the MAC address to identify to which host and interface a particular DHCP lease belongs.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2015-05-18T21:37:07+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-05-06T17:30:12+00:00\" \/>\n<meta name=\"author\" content=\"Tom Coffeen\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Tom Coffeen\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\\\/\"},\"author\":{\"name\":\"Tom Coffeen\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/b299068ee4a9f542d2ad7d59a5b1d5b1\"},\"headline\":\"DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)\",\"datePublished\":\"2015-05-18T21:37:07+00:00\",\"dateModified\":\"2020-05-06T17:30:12+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\\\/\"},\"wordCount\":453,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"keywords\":[\"DHCP\",\"IPAM\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\\\/\",\"name\":\"DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"datePublished\":\"2015-05-18T21:37:07+00:00\",\"dateModified\":\"2020-05-06T17:30:12+00:00\",\"description\":\"In my last post we looked briefly at a key difference between DHCPv6 and DHCPv4: the use of elements other than just the MAC address to identify to which host and interface a particular DHCP lease belongs.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"IPv6 CoE\",\"item\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/category\\\/ipv6-coe\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\",\"name\":\"infoblox.com\\\/blog\\\/\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\",\"name\":\"Infoblox\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/infoblox-logo-2.svg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/infoblox-logo-2.svg\",\"width\":137,\"height\":30,\"caption\":\"Infoblox\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/b299068ee4a9f542d2ad7d59a5b1d5b1\",\"name\":\"Tom Coffeen\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_319_1574118081-96x96.jpg\",\"url\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_319_1574118081-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_319_1574118081-96x96.jpg\",\"caption\":\"Tom Coffeen\"},\"description\":\"Tom Coffeen is a network engineer, architect, and author with over twenty years of internetwork design, deployment, administration, and management experience. Tom co-founded HexaBuild, an IT consultancy specializing in the advancement of cloud, IoT, and security deployment best practices through IPv6 adoption. Prior to co-founding HexaBuild, Tom was an IPv6 Evangelist and a Distinguished Architect at Infoblox. Before that Tom was the VP of network architecture at the global CDN Limelight Networks where he led their deployment of IPv6. He is also the author of O\u2019Reilly Media\u2019s IPv6 Address Planning.\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/author\\\/tom-coffeen\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)","description":"In my last post we looked briefly at a key difference between DHCPv6 and DHCPv4: the use of elements other than just the MAC address to identify to which host and interface a particular DHCP lease belongs.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/","og_locale":"en_US","og_type":"article","og_title":"DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)","og_description":"In my last post we looked briefly at a key difference between DHCPv6 and DHCPv4: the use of elements other than just the MAC address to identify to which host and interface a particular DHCP lease belongs.","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/","og_site_name":"Infoblox Blog","article_published_time":"2015-05-18T21:37:07+00:00","article_modified_time":"2020-05-06T17:30:12+00:00","author":"Tom Coffeen","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Tom Coffeen","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/"},"author":{"name":"Tom Coffeen","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/b299068ee4a9f542d2ad7d59a5b1d5b1"},"headline":"DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)","datePublished":"2015-05-18T21:37:07+00:00","dateModified":"2020-05-06T17:30:12+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/"},"wordCount":453,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"keywords":["DHCP","IPAM"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/","name":"DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"datePublished":"2015-05-18T21:37:07+00:00","dateModified":"2020-05-06T17:30:12+00:00","description":"In my last post we looked briefly at a key difference between DHCPv6 and DHCPv4: the use of elements other than just the MAC address to identify to which host and interface a particular DHCP lease belongs.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/dhcpv6-and-the-trouble-with-mac-addresses-part-2-of-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.infoblox.com\/blog\/"},{"@type":"ListItem","position":2,"name":"IPv6 CoE","item":"https:\/\/www.infoblox.com\/blog\/category\/ipv6-coe\/"},{"@type":"ListItem","position":3,"name":"DHCPv6 and the Trouble with MAC Addresses (Part 2 of 2)"}]},{"@type":"WebSite","@id":"https:\/\/www.infoblox.com\/blog\/#website","url":"https:\/\/www.infoblox.com\/blog\/","name":"infoblox.com\/blog\/","description":"","publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.infoblox.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.infoblox.com\/blog\/#organization","name":"Infoblox","url":"https:\/\/www.infoblox.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/infoblox-logo-2.svg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/infoblox-logo-2.svg","width":137,"height":30,"caption":"Infoblox"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/b299068ee4a9f542d2ad7d59a5b1d5b1","name":"Tom Coffeen","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_319_1574118081-96x96.jpg","url":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_319_1574118081-96x96.jpg","contentUrl":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_319_1574118081-96x96.jpg","caption":"Tom Coffeen"},"description":"Tom Coffeen is a network engineer, architect, and author with over twenty years of internetwork design, deployment, administration, and management experience. Tom co-founded HexaBuild, an IT consultancy specializing in the advancement of cloud, IoT, and security deployment best practices through IPv6 adoption. Prior to co-founding HexaBuild, Tom was an IPv6 Evangelist and a Distinguished Architect at Infoblox. Before that Tom was the VP of network architecture at the global CDN Limelight Networks where he led their deployment of IPv6. He is also the author of O\u2019Reilly Media\u2019s IPv6 Address Planning.","url":"https:\/\/www.infoblox.com\/blog\/author\/tom-coffeen\/"}]}},"_links":{"self":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/3327","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/users\/319"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/comments?post=3327"}],"version-history":[{"count":1,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/3327\/revisions"}],"predecessor-version":[{"id":3329,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/3327\/revisions\/3329"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=3327"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=3327"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=3327"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}