{"id":4546,"date":"2012-07-12T10:27:57","date_gmt":"2012-07-12T17:27:57","guid":{"rendered":"https:\/\/blogs.infoblox.com\/?p=4546"},"modified":"2020-05-06T10:31:42","modified_gmt":"2020-05-06T17:31:42","slug":"creating-an-ipv6-addressing-plan-part-2","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/","title":{"rendered":"Creating an IPv6 Addressing Plan (part 2)"},"content":{"rendered":"<p>Here&#8217;s the second part of a four-part blog on creating an IPv6 addressing plan. Today, we&#8217;ll discuss assigning subnets and addresses within a site and getting IPv6 addresses.<\/p>\n<p><strong>Assigning Subnets and Addresses within a Site<\/strong><\/p>\n<p>The standard single site allocation is a \/48 (the maximum number of bits allowed for a prefix that ISPs will accept and re-advertise). The subnet ID portion of the prefix allows for subnet assignments within a given site.<\/p>\n<p>Any subnets derived from this primary site assignment should not be any smaller (i.e., more bits) than the standard interface assignment in IPv6 of a \/64.<\/p>\n<p>The more granular subnet assignments derived from the \/48 assigned to a site have two primary characteristics. First, as mentioned above, they are typically larger than the standard \/64 interface assignment and are appropriately sized to define groups of these interface subnets. Second, these groups will be sized and assigned based on the network function or location they provide addressing for.<\/p>\n<p><em>Table 2<\/em>\u00a0shows the number of subnet groups per \/48 with the resulting number of \/64 subnets.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-4547\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/number-of-bits-per-allocation-2.jpg\" alt=\"number of bits per allocation 2\" width=\"908\" height=\"299\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/number-of-bits-per-allocation-2.jpg 908w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/number-of-bits-per-allocation-2-300x99.jpg 300w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/number-of-bits-per-allocation-2-768x253.jpg 768w\" sizes=\"auto, (max-width: 908px) 100vw, 908px\" \/><\/p>\n<p>These values should help guide how many groups of subnets, as well as \/64s per group, are required for a given site. In general, the more \/64s required for a particular function or location within the site, the fewer the number of larger subnets available for other locations or functions at that same site. Fortunately, most organizations are unlikely to use more than 4,096 \/64 subnets for a single site function or location (a limit which would still allow for 15 additional \/52s\u2014each with 4,096 \/64 subnets).<\/p>\n<p>The determination of how many groups of subnets (and \/64s per group) are needed should include current production requirements as well as expected growth. The 4-bit boundary preferred for prefix legibility leaves room in between for unexpected growth (though at the potential future cost of concision and legibility as we\u2019ll explore later).<\/p>\n<p>As mentioned, all network interfaces should be assigned a \/64 by default. The only exceptions to this rule are for point-to-point links and loopback addresses.<\/p>\n<p>In recent years, there has been much debate in the Internet engineering community and among network operators as to what size subnet should be used for point-to-point links. Initial IPv6 deployments often used \/64s for consistency\u2019s sake but security issues (i.e., neighbor cache exhaustion and forwarding loops) emerged that made this method controversial. As a result, both \/126s and \/127s were proposed and deployed as preferable alternatives. More recently, RFC 6164 recommends the use of \/127s on point-to-point links.<\/p>\n<p><em>Figure 2<\/em>\u00a0shows each of the standard IPv6 subnet assignments.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-4549\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/standard-IPv6-assignments.jpg\" alt=\"standard IPv6 assignments\" width=\"925\" height=\"548\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/standard-IPv6-assignments.jpg 925w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/standard-IPv6-assignments-300x178.jpg 300w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/standard-IPv6-assignments-768x455.jpg 768w\" sizes=\"auto, (max-width: 925px) 100vw, 925px\" \/><\/p>\n<p>To preserve address plan consistency, every point-to-point link can be allocated a \/64 but configured with a single \/127 from that allocation. Alternatively, a \/64 can be allocated per routing domain from which all of the \/127s for that domain will be assigned.<\/p>\n<p>\/128s can be assigned from one \/64 allocated per routing domain exclusively for loopback addresses.<\/p>\n<p><strong>Getting IPv6 Addresses<\/strong><\/p>\n<p>Now that you have some information to determine how many IPv6 addresses you might need, the next step is to obtain an IPv6 address allocation. This is typically done in one of two ways: an organization will either request IPv6 space from their ISP or from one of the Regional Internet Registries (or RIRs). The decision to request an IPv6 allocation from an ISP or a RIR is based on whether an organization needs a Provider Aggregatable (PA) allocation or a Provider Independent (PI) allocation.<\/p>\n<p>IPv6 allocations from ISPs or IP transit providers are typically PA allocations. These allocations are usually good for the duration of the contract for IPv6 connectivity from the ISP or transit provider. As a result, renumbering the network will be required if a new provider is chosen. If your organization\u2019s network connectivity and addressing requirements are based on a single site and you\u2019re planning on requesting IPv6 addresses from your ISP, now would be an excellent time to inquire as to whether your ISP supports IPv6 and what the requirements are for requesting IPv6 addresses.<\/p>\n<p>Alternatively, IPv6 allocations from the RIRs are typically PI allocations and are considered permanent once allocated. Such allocations are \u201cportable\u201d meaning that the PI allocation will generally be accepted and re-announced by any ISP or IP transit provider. Both PI and PA allocations are globally registered and globally routable. In general, multi-site networks connected to multiple ISPs or transit providers require PI allocations.<\/p>\n<p>PI allocations obtained through a RIR will require justification for the address space by filling out and submitting documentation detailing current and anticipated IPv6 address requirements. If an organization has obtained IPv4 space from a RIR in the past, the process is similar for IPv6. Most organizations should have no difficulty obtaining IPv6 addresses.<\/p>\n<p>Next time: a sample IPv6 addressing plan.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Here&#8217;s the second part of a four-part blog on creating an IPv6 addressing plan. Today, we&#8217;ll discuss assigning subnets and addresses within a site and getting IPv6 addresses. Assigning Subnets and Addresses within a Site The standard single site allocation is a \/48 (the maximum number of bits allowed for a prefix that ISPs will [&hellip;]<\/p>\n","protected":false},"author":319,"featured_media":3187,"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":[16,56,38,15],"class_list":{"0":"post-4546","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-infoblox","9":"tag-ipv4","10":"tag-ipv6","11":"tag-security","12":"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>Creating an IPv6 Addressing Plan (part 2)<\/title>\n<meta name=\"description\" content=\"Here&#039;s the second part of a four-part blog on creating an IPv6 addressing plan. Today, we&#039;ll discuss assigning subnets and addresses within a site and getting IPv6 addresses.\" \/>\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\/creating-an-ipv6-addressing-plan-part-2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Creating an IPv6 Addressing Plan (part 2)\" \/>\n<meta property=\"og:description\" content=\"Here&#039;s the second part of a four-part blog on creating an IPv6 addressing plan. Today, we&#039;ll discuss assigning subnets and addresses within a site and getting IPv6 addresses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2012-07-12T17:27:57+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-05-06T17:31:42+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"660\" \/>\n\t<meta property=\"og:image:height\" content=\"454\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\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=\"4 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\\\/creating-an-ipv6-addressing-plan-part-2\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-2\\\/\"},\"author\":{\"name\":\"Tom Coffeen\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/b299068ee4a9f542d2ad7d59a5b1d5b1\"},\"headline\":\"Creating an IPv6 Addressing Plan (part 2)\",\"datePublished\":\"2012-07-12T17:27:57+00:00\",\"dateModified\":\"2020-05-06T17:31:42+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-2\\\/\"},\"wordCount\":791,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"keywords\":[\"Infoblox\",\"IPv4\",\"IPv6\",\"Security\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-2\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-2\\\/\",\"name\":\"Creating an IPv6 Addressing Plan (part 2)\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-2\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"datePublished\":\"2012-07-12T17:27:57+00:00\",\"dateModified\":\"2020-05-06T17:31:42+00:00\",\"description\":\"Here's the second part of a four-part blog on creating an IPv6 addressing plan. Today, we'll discuss assigning subnets and addresses within a site and getting IPv6 addresses.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-2\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-2\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-2\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"width\":660,\"height\":454,\"caption\":\"The IPv6 Tipping Point Effect\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/creating-an-ipv6-addressing-plan-part-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\":\"Creating an IPv6 Addressing Plan (part 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":"Creating an IPv6 Addressing Plan (part 2)","description":"Here's the second part of a four-part blog on creating an IPv6 addressing plan. Today, we'll discuss assigning subnets and addresses within a site and getting IPv6 addresses.","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\/creating-an-ipv6-addressing-plan-part-2\/","og_locale":"en_US","og_type":"article","og_title":"Creating an IPv6 Addressing Plan (part 2)","og_description":"Here's the second part of a four-part blog on creating an IPv6 addressing plan. Today, we'll discuss assigning subnets and addresses within a site and getting IPv6 addresses.","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/","og_site_name":"Infoblox Blog","article_published_time":"2012-07-12T17:27:57+00:00","article_modified_time":"2020-05-06T17:31:42+00:00","og_image":[{"width":660,"height":454,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","type":"image\/jpeg"}],"author":"Tom Coffeen","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Tom Coffeen","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/"},"author":{"name":"Tom Coffeen","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/b299068ee4a9f542d2ad7d59a5b1d5b1"},"headline":"Creating an IPv6 Addressing Plan (part 2)","datePublished":"2012-07-12T17:27:57+00:00","dateModified":"2020-05-06T17:31:42+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/"},"wordCount":791,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","keywords":["Infoblox","IPv4","IPv6","Security"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/","name":"Creating an IPv6 Addressing Plan (part 2)","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","datePublished":"2012-07-12T17:27:57+00:00","dateModified":"2020-05-06T17:31:42+00:00","description":"Here's the second part of a four-part blog on creating an IPv6 addressing plan. Today, we'll discuss assigning subnets and addresses within a site and getting IPv6 addresses.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-2\/#primaryimage","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","width":660,"height":454,"caption":"The IPv6 Tipping Point Effect"},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/creating-an-ipv6-addressing-plan-part-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":"Creating an IPv6 Addressing Plan (part 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\/4546","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=4546"}],"version-history":[{"count":1,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/4546\/revisions"}],"predecessor-version":[{"id":4550,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/4546\/revisions\/4550"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media\/3187"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=4546"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=4546"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=4546"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}