{"id":2139,"date":"2017-07-19T18:30:49","date_gmt":"2017-07-19T18:30:49","guid":{"rendered":"https:\/\/live-infoblox-blog.pantheonsite.io\/?p=2139"},"modified":"2022-10-19T16:05:25","modified_gmt":"2022-10-19T23:05:25","slug":"the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/","title":{"rendered":"The Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 of 2)"},"content":{"rendered":"

Part 1: Top IPv6 RFCs 1-5 (Part 2 will be published later and contain Top IPv6 RFCs 6-10)<\/strong><\/p>\n

Introduction<\/strong><\/p>\n

In the middle of the last century, the existentialist philosopher and author Albert Camus famously wrote: \u201cI sometimes think of what future historians will say of us. A single sentence will suffice for modern man: he … read the papers.\u201d [Ed. Note: those ellipses, as is sometimes said in the literature biz, are “doing significant work\u201d but I\u2019ll leave the rest of the quote to be discovered by our more intrepid readers.]<\/p>\n

As for us here in 2017, the dead tree papers are rapidly going the way of the dodo. So, we\u2019ll have to modify the object of we modern’s attention generally to blogs and online articles, and in particular to everyone\u2019s either favorite or hated subgenre: the listicle!<\/p>\n

Depending on your taste, we\u2019ve been either merciful or neglectful not including more listicles on our IPv6 CoE blog. \u00a0So, either rejoice or bear with me as we explore the top 10 IPv6 RFCs (and why you should read them).<\/p>\n

Before we start in on our list though, I want to make sure we\u2019re all on the same page about what RFCs are (as well as where to find them). If that\u2019s old hat to you feel free to skip ahead.<\/p>\n

What the Heck is an RFC?<\/strong><\/p>\n

If you\u2019ve been wrangling data networks for any significant amount of time, you\u2019re likely already quite familiar with what RFCs are and the role that they play in said networking.<\/p>\n

But for those that don\u2019t know (or need reminding), an RFC (short for “Request for Comment\u201d) is a document dealing with some relatively specific aspect of computer networking. (Early RFCs were more like detailed notes shared between the early Internet protocol pioneers, which over time became more formalized documents.) The specific aspect might be a protocol as in the original RFC for the Internet Protocol (version 4), RFC 791 \u201cInternet Protocol\u201d from way back in 1981. Or the RFCs for the Domain Name System (1034 “Domain names – concepts and facilities” and 1035 “Domain names – implementation and specification\u201d), from 1987.\u00a0Can you remember where you were in 1981 and 1987?<\/p>\n

An example of a more recent RFC covering a networking protocol (and one perhaps near and dear to our hearts in the IPv6 community), RFC 8156 “DHCPv6 Failover Protocol\u201d from June of this year.<\/p>\n

Another aspect of networking an RFC might cover is network operations. For example, DNS operations are included in multiple RFCs but RFC 1033 (“Domain Administrators Operations Guide\u201d) is an early one.<\/p>\n

A careful reader may have noticed that the DNS operations RFC is earlier in sequence number than the protocol definition RFCs 1034 and 1035, though they were all released contemporaneously.<\/p>\n

Network architecture is also a subject sometimes detailed in RFCs. For example, deployers of MPLS might be familiar with RFC 7625 “Architecture of an IP\/MPLS Network with Hardened Pipes.”<\/p>\n

Arguably, among the different types, protocol definition RFCs are the most read, reviewed, and referred to. Vendors, for instance, rely heavily on the definitions they provide in order to design their software and hardware and deploy those protocols in their products.\u00a0 Therefore, lack of precision in the protocol specifications can lead to bugs and lack of vendor interoperability.<\/p>\n

It\u2019s not hyperbole to say that all computer networks up to and including the Internet can trace their characteristics back to the technological DNA provided by the RFCs.<\/p>\n

So where do they come from?\u00a0<\/strong><\/p>\n

RFCs are created collaboratively by participants in the Internet Engineering Task Force and IETF participation is open to anyone, anywhere who has something to contribute. Computer scientists, researchers, software engineers, network operators and architects (both service provider and enterprise), vendor product managers,\u00a0graduate students and many other roles \u2014 men and women from all over the world \u2014\u00a0are represented in the IETF RFC process. Indeed, the IETF enshrines this kind of techno-democratic ideal in its document\u00a0The Tao of IETF: A Novice’s Guide to the Internet Engineering Task Force<\/a>: “We reject kings, presidents and voting. We believe in rough consensus and running code.\u201d\u00a0I personally find it very stirring that something as massive and revolutionary as the Internet is largely a product of such open and free collaboration.<\/p>\n

There\u2019s plenty more info about RFCs \u2014 and related IETF documents, such as BPCs (i.e., “Best Current Practices”) and IDs (i.e., Internet Drafts, often precursors to RFCs) \u2014 at the link above. And if you\u2019re not already participating (or at least following along) in one or more of the Working Groups, you might want to consider it. There is rarely a dull moment for those striving for \u201crough consensus and running code.\u201d<\/p>\n

But now, on with our top IPv6 RFCs and why you should read them. (This entry will cover the first five.)<\/p>\n

In the spirit of the late (for television), great David Letterman, I would have liked to attempt to count down from the (arguably) less important IPv6 RFCs to the more important ones. But at least 8 out of 10 of the RFCs listed are what should be considered \u201cfoundational\u201d; i.e., critical to a thorough understanding of how IPv6 is designed and how it is supposed to behave in most deployments. So, we\u2019ll just go (mostly) in the order in which the original RFCs appeared.<\/p>\n

You\u2019ll probably notice when you follow the links that some of the RFCs contain a field indicating \u201cObsoletes\u201d or \u201cUpdated by.\u201d As you might imagine, once the vendor and open source code employing the guidance in the RFCs makes contact with real world deployments, technical issues arise. Some of these issues are merely operational or due to software bugs. Others may reveal something problematic with the underlying RFC. For example, sometimes network technology advancements that couldn\u2019t have been foreseen by the authors or reviewers lead to the need for RFC updates (i.e., additional RFCs that serve to expand the standard into a new tech domain). Sometimes components of the RFC go entirely unused in code and subsequent deployment and are omitted in a new RFC that obsoletes the original one.<\/p>\n

The Top IPv6 RFCs<\/strong><\/p>\n

#1:<\/p>\n

RFC 2460: Internet Protocol, Version 6 (IPv6) Specification<\/a><\/p>\n

Love IPv6 or hate it (and if you hate it, why are you torturing yourself reading this blog?), this is the RFC that started the IPv6\u00a0revoluci\u00f3n<\/em>. Well, technically, that was RFC 1883, which was obsoleted (see above) by this one. RFC 2460 is the first document to lay out the basic design of the IPv6 protocol and resulting packet: the 128-bit address; the IPv6 packet, the fixed (40-byte) header,\u00a0the various extension headers\u00a0and formats for each (including the original effort to make IPv6 more secure with authentication and security extensions);\u00a0flow labels for Layer 3 QoS; the restriction of fragmentation to end nodes; etc.<\/p>\n

The long list of “updated by\u201d RFCs are mostly related to operational challenges in implementing extension headers (as well as handling fragments in real-world deployments). The flexibility and functionality promised by these headers as originally conceived in this RFC has largely not materialized for more than one reason, but the primary impediment has been the secure processing of these headers by routers, switches, security appliances and middle boxes. As a result, for example, RFC 5095 deprecates the Type 0 Routing Header to avoid it being exploited for traffic amplification in denial-of-service attacks.<\/p>\n

[Author\u2019s note: And just literally hours after I finished the first draft of this blog, the IETF published\u00a0RFC 8200: Internet Protocol, Version 6 (IPv6) Specification<\/a>\u00a0moving IPv6 from a\u00a0Draft Standard<\/em>\u00a0to an\u00a0Internet Standard<\/em>, indicating the highest level of technical maturity a protocol can achieve. For more information on the distinctions between standards, refer to\u00a0RFC 2026<\/a>.]<\/p>\n

#2<\/p>\n

RFC 4443: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Spec…<\/a><\/p>\n

A big part of the IPv6 standard is a from-the-ground-up redesign of IPv4. In other words, while adding 96 more address bits to overcome IPv4\u2019s limited supply was and is the most significant aspect of IPv6, the early IETF IPv6 effort went beyond it to focus on additional ways in which IPv4 could be enhanced or improved. \u00a0\u00a0If you say to yourself, \u201cI already know ICMP, I don\u2019t need to read this RFC\u201d, then think again. \u00a0ICMPv6 is much different than ICMP for IPv4.\u00a0 You won\u2019t get far into IPv6 without understanding the differences.<\/p>\n

One of the most impactful parts of this redesign is Neighbor Discovery (or ND \u2014 something that shows up in its own RFC, which we\u2019ll cover below). ND is a total redesign of IPv4 ARP (Address Resolution Protocol) and it relies on ICMPv6 to function properly. While the ICMPv6 messages used in ND are not discussed in\u00a0RFC 4443, it is still worth being familiar with for the specifications it includes: e.g., general message format and message\u00a0types.<\/p>\n

In particular, the new Packet Too Big message type is uniquely important to IPv6, given that packet fragmentation is not permitted or done by intermediate network nodes.<\/p>\n

#3<\/p>\n

RFC 4861: Neighbor Discovery for IP Version 6 (IPv6)<\/a><\/p>\n

As mentioned above,\u00a0Neighbor Discovery is a total redesign of IPv4 ARP. The early IETF IPv6 effort focused on ways it might be possible to make the process for establishing and\u00a0maintaining Layer 2 to Layer 3 mappings more efficient. Neighbor Discovery in IPv6 is the result of those efforts. As summarized in the RFC abstract, IPv6 “nodes (hosts and routers) use Neighbor Discovery to determine the link-layer addresses for neighbors known to reside on attached links and to quickly purge cached values that become invalid. Hosts also use Neighbor Discovery to find neighboring routers that are willing to forward packets on their behalf. Finally, nodes use the protocol to actively keep track of which neighbors are reachable and which are not, and to detect changed link-layer addresses.\u00a0\u00a0When a router or the path to a router fails, a host actively searches for functioning alternates.\u201d<\/p>\n

This RFC (as with many of the others) is really an essential reference document, in this case for how ND is supposed to operate and the messages it exchanges to provide the functions described above. It\u2019s worth reviewing the RFC more closely to gain a better understanding of each of the ND functions (e.g., Address Resolution; Router, Prefix, and Parameter Discovery; Neighbor Unreachability and Duplicate Address Detection; etc.) are defined and supposed to behave.<\/p>\n

#4<\/p>\n

RFC 4862: IPv6 Stateless Address Autoconfiguration<\/a><\/p>\n

Another aspect of the redesign of IPv4 that greatly interested the designers of IPv6 was the potential ability for a node to configure its own addresses (whether locally or globally scoped). The invention of DHCP was a response to the lack of this feature in IPv4 driven by network operators who wanted a way to get nodes online without direct manual configuration of each node. It was successfully argued early on that IPv6 should include this functionality at the protocol level. IPv6 Stateless Address Autoconfiguration is the result.<\/p>\n

The RFC covers the interaction of routers and hosts using Router Solicitations and Router Advertisements as defined in Neighbor Discovery and the mechanism combining an interface identifier with a prefix that results in a globally scoped address. Other areas of significance in the RFC include how address lifetimes (e.g., Valid and Preferred) are intended to be handled in IPv6 and allow for rapid renumbering of nodes.<\/p>\n

#5<\/p>\n

RFC 3596: DNS Extensions to Support IP Version 6<\/a><\/p>\n

As proved time and again \u2014 most recently with increased attacks on elements of the global DNS infrastructure, the Internet and all computer networks are rendered largely useless when DNS isn\u2019t working properly. The existing structure of IPv4 DNS wasn\u2019t sufficient to support a 128-bit address so extensions to the DNS had to be made. Among the shortest of all the IPv6 RFCs, this one defines AAAA (or \u201cQuad A\u201d) records for the forward mapping of domain names to IPv6 addresses.\u00a0It also defines the ip6.arpa domain to handle reverse mapping of IPv6 addresses to domain names.<\/p>\n

That\u2019s it for this installment! Be sure to check back for the\u00a0second part of the article<\/a>, which will include the remaining 5 essential IPv6 RFCs.<\/p>\n","protected":false},"excerpt":{"rendered":"

Part 1: Top IPv6 RFCs 1-5 (Part 2 will be published later and contain Top IPv6 RFCs 6-10) Introduction In the middle of the last century, the existentialist philosopher and author Albert Camus famously wrote: \u201cI sometimes think of what future historians will say of us. A single sentence will suffice for modern man: he […]<\/p>\n","protected":false},"author":319,"featured_media":2135,"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,38],"class_list":{"0":"post-2139","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-infoblox","9":"tag-ipv6","10":"entry"},"acf":[],"yoast_head":"\nThe Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 of 2)<\/title>\n<meta name=\"description\" content=\"IPv6 RFCs and their origin are a concept that is unfamiliar to many. Learn more about the top 10 IPv6 RFCs Infoblox advises your company's network to utilize.\" \/>\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\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 of 2)\" \/>\n<meta property=\"og:description\" content=\"IPv6 RFCs and their origin are a concept that is unfamiliar to many. Learn more about the top 10 IPv6 RFCs Infoblox advises your company's network to utilize.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2017-07-19T18:30:49+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-10-19T23:05:25+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/DNS-Server-Like-Teenager.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"725\" \/>\n\t<meta property=\"og:image:height\" content=\"483\" \/>\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=\"10 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\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/\"},\"author\":{\"name\":\"Tom Coffeen\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/b299068ee4a9f542d2ad7d59a5b1d5b1\"},\"headline\":\"The Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 of 2)\",\"datePublished\":\"2017-07-19T18:30:49+00:00\",\"dateModified\":\"2022-10-19T23:05:25+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/\"},\"wordCount\":2020,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/DNS-Server-Like-Teenager.jpg\",\"keywords\":[\"Infoblox\",\"IPv6\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/\",\"name\":\"The Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 of 2)\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/DNS-Server-Like-Teenager.jpg\",\"datePublished\":\"2017-07-19T18:30:49+00:00\",\"dateModified\":\"2022-10-19T23:05:25+00:00\",\"description\":\"IPv6 RFCs and their origin are a concept that is unfamiliar to many. Learn more about the top 10 IPv6 RFCs Infoblox advises your company's network to utilize.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/DNS-Server-Like-Teenager.jpg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/DNS-Server-Like-Teenager.jpg\",\"width\":725,\"height\":483},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-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\":\"The Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 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":"The Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 of 2)","description":"IPv6 RFCs and their origin are a concept that is unfamiliar to many. Learn more about the top 10 IPv6 RFCs Infoblox advises your company's network to utilize.","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\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/","og_locale":"en_US","og_type":"article","og_title":"The Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 of 2)","og_description":"IPv6 RFCs and their origin are a concept that is unfamiliar to many. Learn more about the top 10 IPv6 RFCs Infoblox advises your company's network to utilize.","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/","og_site_name":"Infoblox Blog","article_published_time":"2017-07-19T18:30:49+00:00","article_modified_time":"2022-10-19T23:05:25+00:00","og_image":[{"width":725,"height":483,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/DNS-Server-Like-Teenager.jpg","type":"image\/jpeg"}],"author":"Tom Coffeen","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Tom Coffeen","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/"},"author":{"name":"Tom Coffeen","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/b299068ee4a9f542d2ad7d59a5b1d5b1"},"headline":"The Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 of 2)","datePublished":"2017-07-19T18:30:49+00:00","dateModified":"2022-10-19T23:05:25+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/"},"wordCount":2020,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/DNS-Server-Like-Teenager.jpg","keywords":["Infoblox","IPv6"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/","name":"The Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 of 2)","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/DNS-Server-Like-Teenager.jpg","datePublished":"2017-07-19T18:30:49+00:00","dateModified":"2022-10-19T23:05:25+00:00","description":"IPv6 RFCs and their origin are a concept that is unfamiliar to many. Learn more about the top 10 IPv6 RFCs Infoblox advises your company's network to utilize.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-of-2\/#primaryimage","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/DNS-Server-Like-Teenager.jpg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/DNS-Server-Like-Teenager.jpg","width":725,"height":483},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/the-top-10-ipv6-rfcs-you-should-read-and-why-part-1-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":"The Top 10 IPv6 RFCs You Should Read (And Why) (Part 1 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\/2139","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=2139"}],"version-history":[{"count":3,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/2139\/revisions"}],"predecessor-version":[{"id":8096,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/2139\/revisions\/8096"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media\/2135"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=2139"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=2139"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=2139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}