CINXE.COM

<!DOCTYPE html> <html class="client-nojs vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-sticky-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-feature-night-mode-enabled skin-theme-clientpref-day vector-toc-available" lang="en" dir="ltr"> <head> <meta charset="UTF-8"> <title>IPv6 - Wikipedia</title> <script>(function(){var className="client-js vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-sticky-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-feature-night-mode-enabled skin-theme-clientpref-day vector-toc-available";var cookie=document.cookie.match(/(?:^|; )enwikimwclientpreferences=([^;]+)/);if(cookie){cookie[1].split('%2C').forEach(function(pref){className=className.replace(new RegExp('(^| )'+pref.replace(/-clientpref-\w+$|[^\w-]+/g,'')+'-clientpref-\\w+( |$)'),'$1'+pref+'$2');});}document.documentElement.className=className;}());RLCONF={"wgBreakFrames":false,"wgSeparatorTransformTable":["",""],"wgDigitTransformTable":["",""],"wgDefaultDateFormat":"dmy", "wgMonthNames":["","January","February","March","April","May","June","July","August","September","October","November","December"],"wgRequestId":"1f35b92d-f394-46ba-9ddd-6fd9acfd9b68","wgCanonicalNamespace":"","wgCanonicalSpecialPageName":false,"wgNamespaceNumber":0,"wgPageName":"IPv6","wgTitle":"IPv6","wgCurRevisionId":1247827527,"wgRevisionId":1247827527,"wgArticleId":15318,"wgIsArticle":true,"wgIsRedirect":false,"wgAction":"view","wgUserName":null,"wgUserGroups":["*"],"wgCategories":["Articles with short description","Short description matches Wikidata","Wikipedia articles in need of updating from July 2017","All Wikipedia articles in need of updating","Use dmy dates from September 2020","Pages with timeline metadata","All articles with unsourced statements","Articles with unsourced statements from January 2022","IPv6","Internet properties established in 1996","Internet layer protocols","Network layer protocols"],"wgPageViewLanguage":"en","wgPageContentLanguage":"en", "wgPageContentModel":"wikitext","wgRelevantPageName":"IPv6","wgRelevantArticleId":15318,"wgIsProbablyEditable":true,"wgRelevantPageIsProbablyEditable":true,"wgRestrictionEdit":[],"wgRestrictionMove":[],"wgRedirectedFrom":"Internet_Protocol_Version_6","wgNoticeProject":"wikipedia","wgCiteReferencePreviewsActive":false,"wgFlaggedRevsParams":{"tags":{"status":{"levels":1}}},"wgMediaViewerOnClick":true,"wgMediaViewerEnabledByDefault":true,"wgPopupsFlags":0,"wgVisualEditor":{"pageLanguageCode":"en","pageLanguageDir":"ltr","pageVariantFallbacks":"en"},"wgMFDisplayWikibaseDescriptions":{"search":true,"watchlist":true,"tagline":false,"nearby":true},"wgWMESchemaEditAttemptStepOversample":false,"wgWMEPageLength":60000,"wgInternalRedirectTargetUrl":"/wiki/IPv6","wgRelatedArticlesCompat":[],"wgCentralAuthMobileDomain":false,"wgEditSubmitButtonLabelPublish":true,"wgULSPosition":"interlanguage","wgULSisCompactLinksEnabled":false,"wgVector2022LanguageInHeader":true,"wgULSisLanguageSelectorEmpty": false,"wgWikibaseItemId":"Q2551624","wgCheckUserClientHintsHeadersJsApi":["brands","architecture","bitness","fullVersionList","mobile","model","platform","platformVersion"],"GEHomepageSuggestedEditsEnableTopics":true,"wgGETopicsMatchModeEnabled":false,"wgGEStructuredTaskRejectionReasonTextInputEnabled":false,"wgGELevelingUpEnabledForUser":false};RLSTATE={"ext.globalCssJs.user.styles":"ready","site.styles":"ready","user.styles":"ready","ext.globalCssJs.user":"ready","user":"ready","user.options":"loading","ext.cite.styles":"ready","skins.vector.search.codex.styles":"ready","skins.vector.styles":"ready","skins.vector.icons":"ready","jquery.makeCollapsible.styles":"ready","ext.wikimediamessages.styles":"ready","ext.visualEditor.desktopArticleTarget.noscript":"ready","ext.uls.interlanguage":"ready","wikibase.client.init":"ready","ext.wikimediaBadges":"ready"};RLPAGEMODULES=["mediawiki.action.view.redirect","ext.cite.ux-enhancements","mediawiki.page.media","site","mediawiki.page.ready", "jquery.makeCollapsible","mediawiki.toc","skins.vector.js","ext.centralNotice.geoIP","ext.centralNotice.startUp","ext.gadget.ReferenceTooltips","ext.gadget.switcher","ext.urlShortener.toolbar","ext.centralauth.centralautologin","mmv.bootstrap","ext.popups","ext.visualEditor.desktopArticleTarget.init","ext.visualEditor.targetLoader","ext.echo.centralauth","ext.eventLogging","ext.wikimediaEvents","ext.navigationTiming","ext.uls.interface","ext.cx.eventlogging.campaigns","ext.cx.uls.quick.actions","wikibase.client.vector-2022","ext.checkUser.clientHints","ext.quicksurveys.init","ext.growthExperiments.SuggestedEditSession","wikibase.sidebar.tracking"];</script> <script>(RLQ=window.RLQ||[]).push(function(){mw.loader.impl(function(){return["user.options@12s5i",function($,jQuery,require,module){mw.user.tokens.set({"patrolToken":"+\\","watchToken":"+\\","csrfToken":"+\\"}); }];});});</script> <link rel="stylesheet" href="/w/load.php?lang=en&modules=ext.cite.styles%7Cext.uls.interlanguage%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediaBadges%7Cext.wikimediamessages.styles%7Cjquery.makeCollapsible.styles%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles%7Cwikibase.client.init&only=styles&skin=vector-2022"> <script async="" src="/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector-2022"></script> <meta name="ResourceLoaderDynamicStyles" content=""> <link rel="stylesheet" href="/w/load.php?lang=en&modules=site.styles&only=styles&skin=vector-2022"> <meta name="generator" content="MediaWiki 1.44.0-wmf.4"> <meta name="referrer" content="origin"> <meta name="referrer" content="origin-when-cross-origin"> <meta name="robots" content="max-image-preview:standard"> <meta name="format-detection" content="telephone=no"> <meta property="og:image" content="https://upload.wikimedia.org/wikipedia/commons/thumb/4/4c/IPv6_header-en.svg/1200px-IPv6_header-en.svg.png"> <meta property="og:image:width" content="1200"> <meta property="og:image:height" content="553"> <meta property="og:image" content="https://upload.wikimedia.org/wikipedia/commons/thumb/4/4c/IPv6_header-en.svg/800px-IPv6_header-en.svg.png"> <meta property="og:image:width" content="800"> <meta property="og:image:height" content="368"> <meta property="og:image" content="https://upload.wikimedia.org/wikipedia/commons/thumb/4/4c/IPv6_header-en.svg/640px-IPv6_header-en.svg.png"> <meta property="og:image:width" content="640"> <meta property="og:image:height" content="295"> <meta name="viewport" content="width=1120"> <meta property="og:title" content="IPv6 - Wikipedia"> <meta property="og:type" content="website"> <link rel="preconnect" href="//upload.wikimedia.org"> <link rel="alternate" media="only screen and (max-width: 640px)" href="//en.m.wikipedia.org/wiki/IPv6"> <link rel="alternate" type="application/x-wiki" title="Edit this page" href="/w/index.php?title=IPv6&action=edit"> <link rel="apple-touch-icon" href="/static/apple-touch/wikipedia.png"> <link rel="icon" href="/static/favicon/wikipedia.ico"> <link rel="search" type="application/opensearchdescription+xml" href="/w/rest.php/v1/search" title="Wikipedia (en)"> <link rel="EditURI" type="application/rsd+xml" href="//en.wikipedia.org/w/api.php?action=rsd"> <link rel="canonical" href="https://en.wikipedia.org/wiki/IPv6"> <link rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en"> <link rel="alternate" type="application/atom+xml" title="Wikipedia Atom feed" href="/w/index.php?title=Special:RecentChanges&feed=atom"> <link rel="dns-prefetch" href="//meta.wikimedia.org" /> <link rel="dns-prefetch" href="//login.wikimedia.org"> </head> <body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject mw-editable page-IPv6 rootpage-IPv6 skin-vector-2022 action-view"><a class="mw-jump-link" href="#bodyContent">Jump to content</a> <div class="vector-header-container"> <header class="vector-header mw-header"> <div class="vector-header-start"> <nav class="vector-main-menu-landmark" aria-label="Site"> <div id="vector-main-menu-dropdown" class="vector-dropdown vector-main-menu-dropdown vector-button-flush-left vector-button-flush-right" > <input type="checkbox" id="vector-main-menu-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-main-menu-dropdown" class="vector-dropdown-checkbox " aria-label="Main menu" > <label id="vector-main-menu-dropdown-label" for="vector-main-menu-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" > Main menu </label> <div class="vector-dropdown-content"> <div id="vector-main-menu-unpinned-container" class="vector-unpinned-container"> <div id="vector-main-menu" class="vector-main-menu vector-pinnable-element"> <div class="vector-pinnable-header vector-main-menu-pinnable-header vector-pinnable-header-unpinned" data-feature-name="main-menu-pinned" data-pinnable-element-id="vector-main-menu" data-pinned-container-id="vector-main-menu-pinned-container" data-unpinned-container-id="vector-main-menu-unpinned-container" > <div class="vector-pinnable-header-label">Main menu</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-main-menu.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-main-menu.unpin">hide</button> </div> <div id="p-navigation" class="vector-menu mw-portlet mw-portlet-navigation" > <div class="vector-menu-heading"> Navigation </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="n-mainpage-description" class="mw-list-item"><a href="/wiki/Main_Page" title="Visit the main page [z]" accesskey="z">Main page</a></li><li id="n-contents" class="mw-list-item"><a href="/wiki/Wikipedia:Contents" title="Guides to browsing Wikipedia">Contents</a></li><li id="n-currentevents" class="mw-list-item"><a href="/wiki/Portal:Current_events" title="Articles related to current events">Current events</a></li><li id="n-randompage" class="mw-list-item"><a href="/wiki/Special:Random" title="Visit a randomly selected article [x]" accesskey="x">Random article</a></li><li id="n-aboutsite" class="mw-list-item"><a href="/wiki/Wikipedia:About" title="Learn about Wikipedia and how it works">About Wikipedia</a></li><li id="n-contactpage" class="mw-list-item"><a href="//en.wikipedia.org/wiki/Wikipedia:Contact_us" title="How to contact Wikipedia">Contact us</a></li> </ul> </div> </div> <div id="p-interaction" class="vector-menu mw-portlet mw-portlet-interaction" > <div class="vector-menu-heading"> Contribute </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="n-help" class="mw-list-item"><a href="/wiki/Help:Contents" title="Guidance on how to use and edit Wikipedia">Help</a></li><li id="n-introduction" class="mw-list-item"><a href="/wiki/Help:Introduction" title="Learn how to edit Wikipedia">Learn to edit</a></li><li id="n-portal" class="mw-list-item"><a href="/wiki/Wikipedia:Community_portal" title="The hub for editors">Community portal</a></li><li id="n-recentchanges" class="mw-list-item"><a href="/wiki/Special:RecentChanges" title="A list of recent changes to Wikipedia [r]" accesskey="r">Recent changes</a></li><li id="n-upload" class="mw-list-item"><a href="/wiki/Wikipedia:File_upload_wizard" title="Add images or other media for use on Wikipedia">Upload file</a></li> </ul> </div> </div> </div> </div> </div> </div> </nav> <a href="/wiki/Main_Page" class="mw-logo"> <img class="mw-logo-icon" src="/static/images/icons/wikipedia.png" alt="" aria-hidden="true" height="50" width="50"> <img class="mw-logo-wordmark" alt="Wikipedia" src="/static/images/mobile/copyright/wikipedia-wordmark-en.svg" style="width: 7.5em; height: 1.125em;"> <img class="mw-logo-tagline" alt="The Free Encyclopedia" src="/static/images/mobile/copyright/wikipedia-tagline-en.svg" width="117" height="13" style="width: 7.3125em; height: 0.8125em;"> </a> </div> <div class="vector-header-end"> <div id="p-search" role="search" class="vector-search-box-vue vector-search-box-collapses vector-search-box-show-thumbnail vector-search-box-auto-expand-width vector-search-box"> <a href="/wiki/Special:Search" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only search-toggle" title="Search Wikipedia [f]" accesskey="f"> Search </a> <div class="vector-typeahead-search-container"> <div class="cdx-typeahead-search cdx-typeahead-search--show-thumbnail cdx-typeahead-search--auto-expand-width"> <form action="/w/index.php" id="searchform" class="cdx-search-input cdx-search-input--has-end-button"> <div id="simpleSearch" class="cdx-search-input__input-wrapper" data-search-loc="header-moved"> <div class="cdx-text-input cdx-text-input--has-start-icon"> <input class="cdx-text-input__input" type="search" name="search" placeholder="Search Wikipedia" aria-label="Search Wikipedia" autocapitalize="sentences" title="Search Wikipedia [f]" accesskey="f" id="searchInput" > </div> <input type="hidden" name="title" value="Special:Search"> </div> <button class="cdx-button cdx-search-input__end-button">Search</button> </form> </div> </div> </div> <nav class="vector-user-links vector-user-links-wide" aria-label="Personal tools"> <div class="vector-user-links-main"> <div id="p-vector-user-menu-preferences" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <div id="p-vector-user-menu-userpage" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <nav class="vector-appearance-landmark" aria-label="Appearance"> <div id="vector-appearance-dropdown" class="vector-dropdown " title="Change the appearance of the page's font size, width, and color" > <input type="checkbox" id="vector-appearance-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-appearance-dropdown" class="vector-dropdown-checkbox " aria-label="Appearance" > <label id="vector-appearance-dropdown-label" for="vector-appearance-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" > Appearance </label> <div class="vector-dropdown-content"> <div id="vector-appearance-unpinned-container" class="vector-unpinned-container"> </div> </div> </div> </nav> <div id="p-vector-user-menu-notifications" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <div id="p-vector-user-menu-overflow" class="vector-menu mw-portlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-sitesupport-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="https://donate.wikimedia.org/wiki/Special:FundraiserRedirector?utm_source=donate&utm_medium=sidebar&utm_campaign=C13_en.wikipedia.org&uselang=en" class="">Donate</a> </li> <li id="pt-createaccount-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="/w/index.php?title=Special:CreateAccount&returnto=IPv6" title="You are encouraged to create an account and log in; however, it is not mandatory" class="">Create account</a> </li> <li id="pt-login-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="/w/index.php?title=Special:UserLogin&returnto=IPv6" title="You're encouraged to log in; however, it's not mandatory. [o]" accesskey="o" class="">Log in</a> </li> </ul> </div> </div> </div> <div id="vector-user-links-dropdown" class="vector-dropdown vector-user-menu vector-button-flush-right vector-user-menu-logged-out" title="Log in and more options" > <input type="checkbox" id="vector-user-links-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-user-links-dropdown" class="vector-dropdown-checkbox " aria-label="Personal tools" > <label id="vector-user-links-dropdown-label" for="vector-user-links-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" > Personal tools </label> <div class="vector-dropdown-content"> <div id="p-personal" class="vector-menu mw-portlet mw-portlet-personal user-links-collapsible-item" title="User menu" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-sitesupport" class="user-links-collapsible-item mw-list-item"><a href="https://donate.wikimedia.org/wiki/Special:FundraiserRedirector?utm_source=donate&utm_medium=sidebar&utm_campaign=C13_en.wikipedia.org&uselang=en">Donate</a></li><li id="pt-createaccount" class="user-links-collapsible-item mw-list-item"><a href="/w/index.php?title=Special:CreateAccount&returnto=IPv6" title="You are encouraged to create an account and log in; however, it is not mandatory"> Create account</a></li><li id="pt-login" class="user-links-collapsible-item mw-list-item"><a href="/w/index.php?title=Special:UserLogin&returnto=IPv6" title="You're encouraged to log in; however, it's not mandatory. [o]" accesskey="o"> Log in</a></li> </ul> </div> </div> <div id="p-user-menu-anon-editor" class="vector-menu mw-portlet mw-portlet-user-menu-anon-editor" > <div class="vector-menu-heading"> Pages for logged out editors <a href="/wiki/Help:Introduction" aria-label="Learn more about editing">learn more</a> </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-anoncontribs" class="mw-list-item"><a href="/wiki/Special:MyContributions" title="A list of edits made from this IP address [y]" accesskey="y">Contributions</a></li><li id="pt-anontalk" class="mw-list-item"><a href="/wiki/Special:MyTalk" title="Discussion about edits from this IP address [n]" accesskey="n">Talk</a></li> </ul> </div> </div> </div> </div> </nav> </div> </header> </div> <div class="mw-page-container"> <div class="mw-page-container-inner"> <div class="vector-sitenotice-container"> <div id="siteNotice"></div> </div> <div class="vector-column-start"> <div class="vector-main-menu-container"> <div id="mw-navigation"> <nav id="mw-panel" class="vector-main-menu-landmark" aria-label="Site"> <div id="vector-main-menu-pinned-container" class="vector-pinned-container"> </div> </nav> </div> </div> <div class="vector-sticky-pinned-container"> <nav id="mw-panel-toc" aria-label="Contents" data-event-name="ui.sidebar-toc" class="mw-table-of-contents-container vector-toc-landmark"> <div id="vector-toc-pinned-container" class="vector-pinned-container"> <div id="vector-toc" class="vector-toc vector-pinnable-element"> <div class="vector-pinnable-header vector-toc-pinnable-header vector-pinnable-header-pinned" data-feature-name="toc-pinned" data-pinnable-element-id="vector-toc" > <h2 class="vector-pinnable-header-label">Contents</h2> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-toc.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-toc.unpin">hide</button> </div> <ul class="vector-toc-contents" id="mw-panel-toc-list"> <li id="toc-mw-content-text" class="vector-toc-list-item vector-toc-level-1"> <a href="#" class="vector-toc-link"> <div class="vector-toc-text">(Top)</div> </a> </li> <li id="toc-Main_features" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Main_features"> <div class="vector-toc-text"> 1 Main features </div> </a> <ul id="toc-Main_features-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Motivation_and_origin" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Motivation_and_origin"> <div class="vector-toc-text"> 2 Motivation and origin </div> </a> <button aria-controls="toc-Motivation_and_origin-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> Toggle Motivation and origin subsection </button> <ul id="toc-Motivation_and_origin-sublist" class="vector-toc-list"> <li id="toc-IPv4_address_exhaustion" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#IPv4_address_exhaustion"> <div class="vector-toc-text"> 2.1 IPv4 address exhaustion </div> </a> <ul id="toc-IPv4_address_exhaustion-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Comparison_with_IPv4" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Comparison_with_IPv4"> <div class="vector-toc-text"> 3 Comparison with IPv4 </div> </a> <button aria-controls="toc-Comparison_with_IPv4-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> Toggle Comparison with IPv4 subsection </button> <ul id="toc-Comparison_with_IPv4-sublist" class="vector-toc-list"> <li id="toc-Larger_address_space" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Larger_address_space"> <div class="vector-toc-text"> 3.1 Larger address space </div> </a> <ul id="toc-Larger_address_space-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Multicasting" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Multicasting"> <div class="vector-toc-text"> 3.2 Multicasting </div> </a> <ul id="toc-Multicasting-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Stateless_address_autoconfiguration_(SLAAC)" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Stateless_address_autoconfiguration_(SLAAC)"> <div class="vector-toc-text"> 3.3 Stateless address autoconfiguration (SLAAC) </div> </a> <ul id="toc-Stateless_address_autoconfiguration_(SLAAC)-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-IPsec" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#IPsec"> <div class="vector-toc-text"> 3.4 IPsec </div> </a> <ul id="toc-IPsec-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Simplified_processing_by_routers" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Simplified_processing_by_routers"> <div class="vector-toc-text"> 3.5 Simplified processing by routers </div> </a> <ul id="toc-Simplified_processing_by_routers-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Mobility" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Mobility"> <div class="vector-toc-text"> 3.6 Mobility </div> </a> <ul id="toc-Mobility-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Extension_headers" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Extension_headers"> <div class="vector-toc-text"> 3.7 Extension headers </div> </a> <ul id="toc-Extension_headers-sublist" class="vector-toc-list"> <li id="toc-Jumbograms" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Jumbograms"> <div class="vector-toc-text"> 3.7.1 Jumbograms </div> </a> <ul id="toc-Jumbograms-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> </ul> </li> <li id="toc-IPv6_packets" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#IPv6_packets"> <div class="vector-toc-text"> 4 IPv6 packets </div> </a> <ul id="toc-IPv6_packets-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Addressing" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Addressing"> <div class="vector-toc-text"> 5 Addressing </div> </a> <button aria-controls="toc-Addressing-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> Toggle Addressing subsection </button> <ul id="toc-Addressing-sublist" class="vector-toc-list"> <li id="toc-Address_representation" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Address_representation"> <div class="vector-toc-text"> 5.1 Address representation </div> </a> <ul id="toc-Address_representation-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Link-local_address" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Link-local_address"> <div class="vector-toc-text"> 5.2 Link-local address </div> </a> <ul id="toc-Link-local_address-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Address_uniqueness_and_router_solicitation" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Address_uniqueness_and_router_solicitation"> <div class="vector-toc-text"> 5.3 Address uniqueness and router solicitation </div> </a> <ul id="toc-Address_uniqueness_and_router_solicitation-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Global_addressing" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Global_addressing"> <div class="vector-toc-text"> 5.4 Global addressing </div> </a> <ul id="toc-Global_addressing-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-IPv6_in_the_Domain_Name_System" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#IPv6_in_the_Domain_Name_System"> <div class="vector-toc-text"> 6 IPv6 in the Domain Name System </div> </a> <ul id="toc-IPv6_in_the_Domain_Name_System-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Transition_mechanisms" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Transition_mechanisms"> <div class="vector-toc-text"> 7 Transition mechanisms </div> </a> <button aria-controls="toc-Transition_mechanisms-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> Toggle Transition mechanisms subsection </button> <ul id="toc-Transition_mechanisms-sublist" class="vector-toc-list"> <li id="toc-Dual-stack_IP_implementation" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Dual-stack_IP_implementation"> <div class="vector-toc-text"> 7.1 Dual-stack IP implementation </div> </a> <ul id="toc-Dual-stack_IP_implementation-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-ISP_customers_with_public-facing_IPv6" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#ISP_customers_with_public-facing_IPv6"> <div class="vector-toc-text"> 7.2 ISP customers with public-facing IPv6 </div> </a> <ul id="toc-ISP_customers_with_public-facing_IPv6-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Tunneling" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Tunneling"> <div class="vector-toc-text"> 7.3 Tunneling </div> </a> <ul id="toc-Tunneling-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-IPv4-mapped_IPv6_addresses" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#IPv4-mapped_IPv6_addresses"> <div class="vector-toc-text"> 7.4 IPv4-mapped IPv6 addresses </div> </a> <ul id="toc-IPv4-mapped_IPv6_addresses-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Security" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Security"> <div class="vector-toc-text"> 8 Security </div> </a> <button aria-controls="toc-Security-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> Toggle Security subsection </button> <ul id="toc-Security-sublist" class="vector-toc-list"> <li id="toc-Shadow_networks" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Shadow_networks"> <div class="vector-toc-text"> 8.1 Shadow networks </div> </a> <ul id="toc-Shadow_networks-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-IPv6_packet_fragmentation" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#IPv6_packet_fragmentation"> <div class="vector-toc-text"> 8.2 IPv6 packet fragmentation </div> </a> <ul id="toc-IPv6_packet_fragmentation-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Standardization_through_RFCs" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Standardization_through_RFCs"> <div class="vector-toc-text"> 9 Standardization through RFCs </div> </a> <button aria-controls="toc-Standardization_through_RFCs-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> Toggle Standardization through RFCs subsection </button> <ul id="toc-Standardization_through_RFCs-sublist" class="vector-toc-list"> <li id="toc-Working-group_proposals" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Working-group_proposals"> <div class="vector-toc-text"> 9.1 Working-group proposals </div> </a> <ul id="toc-Working-group_proposals-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-RFC_standardization" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#RFC_standardization"> <div class="vector-toc-text"> 9.2 RFC standardization </div> </a> <ul id="toc-RFC_standardization-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Deployment" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Deployment"> <div class="vector-toc-text"> 10 Deployment </div> </a> <ul id="toc-Deployment-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Peering_issues" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#Peering_issues"> <div class="vector-toc-text"> 11 Peering issues </div> </a> <ul id="toc-Peering_issues-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-See_also" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#See_also"> <div class="vector-toc-text"> 12 See also </div> </a> <ul id="toc-See_also-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-References" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#References"> <div class="vector-toc-text"> 13 References </div> </a> <ul id="toc-References-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-External_links" class="vector-toc-list-item vector-toc-level-1"> <a class="vector-toc-link" href="#External_links"> <div class="vector-toc-text"> 14 External links </div> </a> <ul id="toc-External_links-sublist" class="vector-toc-list"> </ul> </li> </ul> </div> </div> </nav> </div> </div> <div class="mw-content-container"> <main id="content" class="mw-body"> <header class="mw-body-header vector-page-titlebar"> <nav aria-label="Contents" class="vector-toc-landmark"> <div id="vector-page-titlebar-toc" class="vector-dropdown vector-page-titlebar-toc vector-button-flush-left" > <input type="checkbox" id="vector-page-titlebar-toc-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-page-titlebar-toc" class="vector-dropdown-checkbox " aria-label="Toggle the table of contents" > <label id="vector-page-titlebar-toc-label" for="vector-page-titlebar-toc-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" > Toggle the table of contents </label> <div class="vector-dropdown-content"> <div id="vector-page-titlebar-toc-unpinned-container" class="vector-unpinned-container"> </div> </div> </div> </nav> <h1 id="firstHeading" class="firstHeading mw-first-heading">IPv6</h1> <div id="p-lang-btn" class="vector-dropdown mw-portlet mw-portlet-lang" > <input type="checkbox" id="p-lang-btn-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-p-lang-btn" class="vector-dropdown-checkbox mw-interlanguage-selector" aria-label="Go to an article in another language. Available in 60 languages" > <label id="p-lang-btn-label" for="p-lang-btn-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--action-progressive mw-portlet-lang-heading-60" aria-hidden="true" > 60 languages </label> <div class="vector-dropdown-content"> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li class="interlanguage-link interwiki-ar badge-Q17437796 badge-featuredarticle mw-list-item" title="featured article badge"><a href="https://ar.wikipedia.org/wiki/%D8%A8%D8%B1%D9%88%D8%AA%D9%88%D9%83%D9%88%D9%84_%D8%A7%D9%84%D8%A5%D9%86%D8%AA%D8%B1%D9%86%D8%AA_(%D8%A7%D9%84%D8%A5%D8%B5%D8%AF%D8%A7%D8%B1_%D8%A7%D9%84%D8%B3%D8%A7%D8%AF%D8%B3)" title="بروتوكول الإنترنت (الإصدار السادس) – Arabic" lang="ar" hreflang="ar" data-title="بروتوكول الإنترنت (الإصدار السادس)" data-language-autonym="العربية" data-language-local-name="Arabic" class="interlanguage-link-target">العربية</a></li><li class="interlanguage-link interwiki-az mw-list-item"><a href="https://az.wikipedia.org/wiki/IPv6" title="IPv6 – Azerbaijani" lang="az" hreflang="az" data-title="IPv6" data-language-autonym="Azərbaycanca" data-language-local-name="Azerbaijani" class="interlanguage-link-target">Azərbaycanca</a></li><li class="interlanguage-link interwiki-bn mw-list-item"><a href="https://bn.wikipedia.org/wiki/%E0%A6%86%E0%A6%87%E0%A6%AA%E0%A6%BF%E0%A6%AD%E0%A6%BF%E0%A7%AC" title="আইপিভি৬ – Bangla" lang="bn" hreflang="bn" data-title="আইপিভি৬" data-language-autonym="বাংলা" data-language-local-name="Bangla" class="interlanguage-link-target">বাংলা</a></li><li class="interlanguage-link interwiki-be mw-list-item"><a href="https://be.wikipedia.org/wiki/IPv6" title="IPv6 – Belarusian" lang="be" hreflang="be" data-title="IPv6" data-language-autonym="Беларуская" data-language-local-name="Belarusian" class="interlanguage-link-target">Беларуская</a></li><li class="interlanguage-link interwiki-bg mw-list-item"><a href="https://bg.wikipedia.org/wiki/IPv6" title="IPv6 – Bulgarian" lang="bg" hreflang="bg" data-title="IPv6" data-language-autonym="Български" data-language-local-name="Bulgarian" class="interlanguage-link-target">Български</a></li><li class="interlanguage-link interwiki-bs mw-list-item"><a href="https://bs.wikipedia.org/wiki/IPv6" title="IPv6 – Bosnian" lang="bs" hreflang="bs" data-title="IPv6" data-language-autonym="Bosanski" data-language-local-name="Bosnian" class="interlanguage-link-target">Bosanski</a></li><li class="interlanguage-link interwiki-ca mw-list-item"><a href="https://ca.wikipedia.org/wiki/IPv6" title="IPv6 – Catalan" lang="ca" hreflang="ca" data-title="IPv6" data-language-autonym="Català" data-language-local-name="Catalan" class="interlanguage-link-target">Català</a></li><li class="interlanguage-link interwiki-cs mw-list-item"><a href="https://cs.wikipedia.org/wiki/IPv6" title="IPv6 – Czech" lang="cs" hreflang="cs" data-title="IPv6" data-language-autonym="Čeština" data-language-local-name="Czech" class="interlanguage-link-target">Čeština</a></li><li class="interlanguage-link interwiki-da mw-list-item"><a href="https://da.wikipedia.org/wiki/IPv6" title="IPv6 – Danish" lang="da" hreflang="da" data-title="IPv6" data-language-autonym="Dansk" data-language-local-name="Danish" class="interlanguage-link-target">Dansk</a></li><li class="interlanguage-link interwiki-de mw-list-item"><a href="https://de.wikipedia.org/wiki/IPv6" title="IPv6 – German" lang="de" hreflang="de" data-title="IPv6" data-language-autonym="Deutsch" data-language-local-name="German" class="interlanguage-link-target">Deutsch</a></li><li class="interlanguage-link interwiki-et mw-list-item"><a href="https://et.wikipedia.org/wiki/IPv6" title="IPv6 – Estonian" lang="et" hreflang="et" data-title="IPv6" data-language-autonym="Eesti" data-language-local-name="Estonian" class="interlanguage-link-target">Eesti</a></li><li class="interlanguage-link interwiki-el mw-list-item"><a href="https://el.wikipedia.org/wiki/IPv6" title="IPv6 – Greek" lang="el" hreflang="el" data-title="IPv6" data-language-autonym="Ελληνικά" data-language-local-name="Greek" class="interlanguage-link-target">Ελληνικά</a></li><li class="interlanguage-link interwiki-es mw-list-item"><a href="https://es.wikipedia.org/wiki/IPv6" title="IPv6 – Spanish" lang="es" hreflang="es" data-title="IPv6" data-language-autonym="Español" data-language-local-name="Spanish" class="interlanguage-link-target">Español</a></li><li class="interlanguage-link interwiki-eu mw-list-item"><a href="https://eu.wikipedia.org/wiki/IPv6" title="IPv6 – Basque" lang="eu" hreflang="eu" data-title="IPv6" data-language-autonym="Euskara" data-language-local-name="Basque" class="interlanguage-link-target">Euskara</a></li><li class="interlanguage-link interwiki-fa mw-list-item"><a href="https://fa.wikipedia.org/wiki/%D9%BE%D8%B1%D9%88%D8%AA%DA%A9%D9%84_%D8%A7%DB%8C%D9%86%D8%AA%D8%B1%D9%86%D8%AA_%D9%86%D8%B3%D8%AE%D9%87_%DB%B6" title="پروتکل اینترنت نسخه ۶ – Persian" lang="fa" hreflang="fa" data-title="پروتکل اینترنت نسخه ۶" data-language-autonym="فارسی" data-language-local-name="Persian" class="interlanguage-link-target">فارسی</a></li><li class="interlanguage-link interwiki-fr mw-list-item"><a href="https://fr.wikipedia.org/wiki/IPv6" title="IPv6 – French" lang="fr" hreflang="fr" data-title="IPv6" data-language-autonym="Français" data-language-local-name="French" class="interlanguage-link-target">Français</a></li><li class="interlanguage-link interwiki-gl mw-list-item"><a href="https://gl.wikipedia.org/wiki/Protocolo_IPv6" title="Protocolo IPv6 – Galician" lang="gl" hreflang="gl" data-title="Protocolo IPv6" data-language-autonym="Galego" data-language-local-name="Galician" class="interlanguage-link-target">Galego</a></li><li class="interlanguage-link interwiki-ko mw-list-item"><a href="https://ko.wikipedia.org/wiki/IPv6" title="IPv6 – Korean" lang="ko" hreflang="ko" data-title="IPv6" data-language-autonym="한국어" data-language-local-name="Korean" class="interlanguage-link-target">한국어</a></li><li class="interlanguage-link interwiki-hy mw-list-item"><a href="https://hy.wikipedia.org/wiki/IPv6_%D5%B0%D5%A1%D5%B4%D5%A1%D6%81%D5%A1%D5%B6%D6%81%D5%A1%D5%B5%D5%AB%D5%B6_%D5%B0%D5%A1%D5%B2%D5%B8%D6%80%D5%A4%D5%A1%D5%AF%D5%A1%D6%80%D5%A3" title="IPv6 համացանցային հաղորդակարգ – Armenian" lang="hy" hreflang="hy" data-title="IPv6 համացանցային հաղորդակարգ" data-language-autonym="Հայերեն" data-language-local-name="Armenian" class="interlanguage-link-target">Հայերեն</a></li><li class="interlanguage-link interwiki-hi mw-list-item"><a href="https://hi.wikipedia.org/wiki/%E0%A4%87%E0%A4%82%E0%A4%9F%E0%A4%B0%E0%A4%A8%E0%A5%87%E0%A4%9F_%E0%A4%AA%E0%A5%8D%E0%A4%B0%E0%A5%8B%E0%A4%9F%E0%A5%8B%E0%A4%95%E0%A5%89%E0%A4%B2_%E0%A4%B8%E0%A4%82%E0%A4%B8%E0%A5%8D%E0%A4%95%E0%A4%B0%E0%A4%A3_%E0%A5%AC" title="इंटरनेट प्रोटोकॉल संस्करण ६ – Hindi" lang="hi" hreflang="hi" data-title="इंटरनेट प्रोटोकॉल संस्करण ६" data-language-autonym="हिन्दी" data-language-local-name="Hindi" class="interlanguage-link-target">हिन्दी</a></li><li class="interlanguage-link interwiki-hr mw-list-item"><a href="https://hr.wikipedia.org/wiki/IPv6" title="IPv6 – Croatian" lang="hr" hreflang="hr" data-title="IPv6" data-language-autonym="Hrvatski" data-language-local-name="Croatian" class="interlanguage-link-target">Hrvatski</a></li><li class="interlanguage-link interwiki-id mw-list-item"><a href="https://id.wikipedia.org/wiki/IPv6" title="IPv6 – Indonesian" lang="id" hreflang="id" data-title="IPv6" data-language-autonym="Bahasa Indonesia" data-language-local-name="Indonesian" class="interlanguage-link-target">Bahasa Indonesia</a></li><li class="interlanguage-link interwiki-is mw-list-item"><a href="https://is.wikipedia.org/wiki/IPv6" title="IPv6 – Icelandic" lang="is" hreflang="is" data-title="IPv6" data-language-autonym="Íslenska" data-language-local-name="Icelandic" class="interlanguage-link-target">Íslenska</a></li><li class="interlanguage-link interwiki-it mw-list-item"><a href="https://it.wikipedia.org/wiki/IPv6" title="IPv6 – Italian" lang="it" hreflang="it" data-title="IPv6" data-language-autonym="Italiano" data-language-local-name="Italian" class="interlanguage-link-target">Italiano</a></li><li class="interlanguage-link interwiki-he mw-list-item"><a href="https://he.wikipedia.org/wiki/IPv6" title="IPv6 – Hebrew" lang="he" hreflang="he" data-title="IPv6" data-language-autonym="עברית" data-language-local-name="Hebrew" class="interlanguage-link-target">עברית</a></li><li class="interlanguage-link interwiki-la mw-list-item"><a href="https://la.wikipedia.org/wiki/IPv6" title="IPv6 – Latin" lang="la" hreflang="la" data-title="IPv6" data-language-autonym="Latina" data-language-local-name="Latin" class="interlanguage-link-target">Latina</a></li><li class="interlanguage-link interwiki-lv mw-list-item"><a href="https://lv.wikipedia.org/wiki/IPv6" title="IPv6 – Latvian" lang="lv" hreflang="lv" data-title="IPv6" data-language-autonym="Latviešu" data-language-local-name="Latvian" class="interlanguage-link-target">Latviešu</a></li><li class="interlanguage-link interwiki-lt mw-list-item"><a href="https://lt.wikipedia.org/wiki/IPv6" title="IPv6 – Lithuanian" lang="lt" hreflang="lt" data-title="IPv6" data-language-autonym="Lietuvių" data-language-local-name="Lithuanian" class="interlanguage-link-target">Lietuvių</a></li><li class="interlanguage-link interwiki-ln mw-list-item"><a href="https://ln.wikipedia.org/wiki/IPv6" title="IPv6 – Lingala" lang="ln" hreflang="ln" data-title="IPv6" data-language-autonym="Lingála" data-language-local-name="Lingala" class="interlanguage-link-target">Lingála</a></li><li class="interlanguage-link interwiki-hu mw-list-item"><a href="https://hu.wikipedia.org/wiki/IPv6" title="IPv6 – Hungarian" lang="hu" hreflang="hu" data-title="IPv6" data-language-autonym="Magyar" data-language-local-name="Hungarian" class="interlanguage-link-target">Magyar</a></li><li class="interlanguage-link interwiki-mk mw-list-item"><a href="https://mk.wikipedia.org/wiki/IPv6" title="IPv6 – Macedonian" lang="mk" hreflang="mk" data-title="IPv6" data-language-autonym="Македонски" data-language-local-name="Macedonian" class="interlanguage-link-target">Македонски</a></li><li class="interlanguage-link interwiki-ml mw-list-item"><a href="https://ml.wikipedia.org/wiki/%E0%B4%90.%E0%B4%AA%E0%B4%BF._%E0%B4%B5%E0%B4%BF%E0%B4%B2%E0%B4%BE%E0%B4%B8%E0%B4%82_%E0%B4%B5%E0%B4%BF6" title="ഐ.പി. വിലാസം വി6 – Malayalam" lang="ml" hreflang="ml" data-title="ഐ.പി. വിലാസം വി6" data-language-autonym="മലയാളം" data-language-local-name="Malayalam" class="interlanguage-link-target">മലയാളം</a></li><li class="interlanguage-link interwiki-mr mw-list-item"><a href="https://mr.wikipedia.org/wiki/%E0%A4%87%E0%A4%82%E0%A4%9F%E0%A4%B0%E0%A4%A8%E0%A5%87%E0%A4%9F_%E0%A4%AA%E0%A5%8D%E0%A4%B0%E0%A5%8B%E0%A4%9F%E0%A5%8B%E0%A4%95%E0%A5%89%E0%A4%B2_%E0%A4%B8%E0%A4%82%E0%A4%B8%E0%A5%8D%E0%A4%95%E0%A4%B0%E0%A4%A3_%E0%A5%AC" title="इंटरनेट प्रोटोकॉल संस्करण ६ – Marathi" lang="mr" hreflang="mr" data-title="इंटरनेट प्रोटोकॉल संस्करण ६" data-language-autonym="मराठी" data-language-local-name="Marathi" class="interlanguage-link-target">मराठी</a></li><li class="interlanguage-link interwiki-ms mw-list-item"><a href="https://ms.wikipedia.org/wiki/IPv6" title="IPv6 – Malay" lang="ms" hreflang="ms" data-title="IPv6" data-language-autonym="Bahasa Melayu" data-language-local-name="Malay" class="interlanguage-link-target">Bahasa Melayu</a></li><li class="interlanguage-link interwiki-mn mw-list-item"><a href="https://mn.wikipedia.org/wiki/IPv6" title="IPv6 – Mongolian" lang="mn" hreflang="mn" data-title="IPv6" data-language-autonym="Монгол" data-language-local-name="Mongolian" class="interlanguage-link-target">Монгол</a></li><li class="interlanguage-link interwiki-nl mw-list-item"><a href="https://nl.wikipedia.org/wiki/Internet_Protocol_versie_6" title="Internet Protocol versie 6 – Dutch" lang="nl" hreflang="nl" data-title="Internet Protocol versie 6" data-language-autonym="Nederlands" data-language-local-name="Dutch" class="interlanguage-link-target">Nederlands</a></li><li class="interlanguage-link interwiki-ja mw-list-item"><a href="https://ja.wikipedia.org/wiki/IPv6" title="IPv6 – Japanese" lang="ja" hreflang="ja" data-title="IPv6" data-language-autonym="日本語" data-language-local-name="Japanese" class="interlanguage-link-target">日本語</a></li><li class="interlanguage-link interwiki-no mw-list-item"><a href="https://no.wikipedia.org/wiki/IPv6" title="IPv6 – Norwegian Bokmål" lang="nb" hreflang="nb" data-title="IPv6" data-language-autonym="Norsk bokmål" data-language-local-name="Norwegian Bokmål" class="interlanguage-link-target">Norsk bokmål</a></li><li class="interlanguage-link interwiki-nn mw-list-item"><a href="https://nn.wikipedia.org/wiki/IPv6" title="IPv6 – Norwegian Nynorsk" lang="nn" hreflang="nn" data-title="IPv6" data-language-autonym="Norsk nynorsk" data-language-local-name="Norwegian Nynorsk" class="interlanguage-link-target">Norsk nynorsk</a></li><li class="interlanguage-link interwiki-pl mw-list-item"><a href="https://pl.wikipedia.org/wiki/IPv6" title="IPv6 – Polish" lang="pl" hreflang="pl" data-title="IPv6" data-language-autonym="Polski" data-language-local-name="Polish" class="interlanguage-link-target">Polski</a></li><li class="interlanguage-link interwiki-pt mw-list-item"><a href="https://pt.wikipedia.org/wiki/IPv6" title="IPv6 – Portuguese" lang="pt" hreflang="pt" data-title="IPv6" data-language-autonym="Português" data-language-local-name="Portuguese" class="interlanguage-link-target">Português</a></li><li class="interlanguage-link interwiki-ro mw-list-item"><a href="https://ro.wikipedia.org/wiki/IPv6" title="IPv6 – Romanian" lang="ro" hreflang="ro" data-title="IPv6" data-language-autonym="Română" data-language-local-name="Romanian" class="interlanguage-link-target">Română</a></li><li class="interlanguage-link interwiki-ru mw-list-item"><a href="https://ru.wikipedia.org/wiki/IPv6" title="IPv6 – Russian" lang="ru" hreflang="ru" data-title="IPv6" data-language-autonym="Русский" data-language-local-name="Russian" class="interlanguage-link-target">Русский</a></li><li class="interlanguage-link interwiki-sq mw-list-item"><a href="https://sq.wikipedia.org/wiki/IPv6" title="IPv6 – Albanian" lang="sq" hreflang="sq" data-title="IPv6" data-language-autonym="Shqip" data-language-local-name="Albanian" class="interlanguage-link-target">Shqip</a></li><li class="interlanguage-link interwiki-sk mw-list-item"><a href="https://sk.wikipedia.org/wiki/IPv6" title="IPv6 – Slovak" lang="sk" hreflang="sk" data-title="IPv6" data-language-autonym="Slovenčina" data-language-local-name="Slovak" class="interlanguage-link-target">Slovenčina</a></li><li class="interlanguage-link interwiki-sl mw-list-item"><a href="https://sl.wikipedia.org/wiki/IPv6" title="IPv6 – Slovenian" lang="sl" hreflang="sl" data-title="IPv6" data-language-autonym="Slovenščina" data-language-local-name="Slovenian" class="interlanguage-link-target">Slovenščina</a></li><li class="interlanguage-link interwiki-sr mw-list-item"><a href="https://sr.wikipedia.org/wiki/IPv6" title="IPv6 – Serbian" lang="sr" hreflang="sr" data-title="IPv6" data-language-autonym="Српски / srpski" data-language-local-name="Serbian" class="interlanguage-link-target">Српски / srpski</a></li><li class="interlanguage-link interwiki-sh mw-list-item"><a href="https://sh.wikipedia.org/wiki/IPv6" title="IPv6 – Serbo-Croatian" lang="sh" hreflang="sh" data-title="IPv6" data-language-autonym="Srpskohrvatski / српскохрватски" data-language-local-name="Serbo-Croatian" class="interlanguage-link-target">Srpskohrvatski / српскохрватски</a></li><li class="interlanguage-link interwiki-fi mw-list-item"><a href="https://fi.wikipedia.org/wiki/IPv6" title="IPv6 – Finnish" lang="fi" hreflang="fi" data-title="IPv6" data-language-autonym="Suomi" data-language-local-name="Finnish" class="interlanguage-link-target">Suomi</a></li><li class="interlanguage-link interwiki-sv mw-list-item"><a href="https://sv.wikipedia.org/wiki/IPv6" title="IPv6 – Swedish" lang="sv" hreflang="sv" data-title="IPv6" data-language-autonym="Svenska" data-language-local-name="Swedish" class="interlanguage-link-target">Svenska</a></li><li class="interlanguage-link interwiki-tl mw-list-item"><a href="https://tl.wikipedia.org/wiki/IPv6" title="IPv6 – Tagalog" lang="tl" hreflang="tl" data-title="IPv6" data-language-autonym="Tagalog" data-language-local-name="Tagalog" class="interlanguage-link-target">Tagalog</a></li><li class="interlanguage-link interwiki-ta mw-list-item"><a href="https://ta.wikipedia.org/wiki/%E0%AE%87%E0%AE%A3%E0%AF%88%E0%AE%AF_%E0%AE%A8%E0%AF%86%E0%AE%B1%E0%AE%BF%E0%AE%AE%E0%AF%81%E0%AE%B1%E0%AF%88%E0%AE%AA%E0%AF%8D_%E0%AE%AA%E0%AE%A4%E0%AE%BF%E0%AE%AA%E0%AF%8D%E0%AE%AA%E0%AF%81_6" title="இணைய நெறிமுறைப் பதிப்பு 6 – Tamil" lang="ta" hreflang="ta" data-title="இணைய நெறிமுறைப் பதிப்பு 6" data-language-autonym="தமிழ்" data-language-local-name="Tamil" class="interlanguage-link-target">தமிழ்</a></li><li class="interlanguage-link interwiki-tg mw-list-item"><a href="https://tg.wikipedia.org/wiki/IPv6" title="IPv6 – Tajik" lang="tg" hreflang="tg" data-title="IPv6" data-language-autonym="Тоҷикӣ" data-language-local-name="Tajik" class="interlanguage-link-target">Тоҷикӣ</a></li><li class="interlanguage-link interwiki-tr mw-list-item"><a href="https://tr.wikipedia.org/wiki/IPv6" title="IPv6 – Turkish" lang="tr" hreflang="tr" data-title="IPv6" data-language-autonym="Türkçe" data-language-local-name="Turkish" class="interlanguage-link-target">Türkçe</a></li><li class="interlanguage-link interwiki-uk mw-list-item"><a href="https://uk.wikipedia.org/wiki/IPv6" title="IPv6 – Ukrainian" lang="uk" hreflang="uk" data-title="IPv6" data-language-autonym="Українська" data-language-local-name="Ukrainian" class="interlanguage-link-target">Українська</a></li><li class="interlanguage-link interwiki-vi mw-list-item"><a href="https://vi.wikipedia.org/wiki/IPv6" title="IPv6 – Vietnamese" lang="vi" hreflang="vi" data-title="IPv6" data-language-autonym="Tiếng Việt" data-language-local-name="Vietnamese" class="interlanguage-link-target">Tiếng Việt</a></li><li class="interlanguage-link interwiki-wuu mw-list-item"><a href="https://wuu.wikipedia.org/wiki/IPv6" title="IPv6 – Wu" lang="wuu" hreflang="wuu" data-title="IPv6" data-language-autonym="吴语" data-language-local-name="Wu" class="interlanguage-link-target">吴语</a></li><li class="interlanguage-link interwiki-yi mw-list-item"><a href="https://yi.wikipedia.org/wiki/IPv6" title="IPv6 – Yiddish" lang="yi" hreflang="yi" data-title="IPv6" data-language-autonym="ייִדיש" data-language-local-name="Yiddish" class="interlanguage-link-target">ייִדיש</a></li><li class="interlanguage-link interwiki-yo mw-list-item"><a href="https://yo.wikipedia.org/wiki/IPv6" title="IPv6 – Yoruba" lang="yo" hreflang="yo" data-title="IPv6" data-language-autonym="Yorùbá" data-language-local-name="Yoruba" class="interlanguage-link-target">Yorùbá</a></li><li class="interlanguage-link interwiki-zh mw-list-item"><a href="https://zh.wikipedia.org/wiki/IPv6" title="IPv6 – Chinese" lang="zh" hreflang="zh" data-title="IPv6" data-language-autonym="中文" data-language-local-name="Chinese" class="interlanguage-link-target">中文</a></li> </ul> <div class="after-portlet after-portlet-lang"><a href="https://www.wikidata.org/wiki/Special:EntityPage/Q2551624#sitelinks-wikipedia" title="Edit interlanguage links" class="wbc-editpage">Edit links</a></div> </div> </div> </div> </header> <div class="vector-page-toolbar"> <div class="vector-page-toolbar-container"> <div id="left-navigation"> <nav aria-label="Namespaces"> <div id="p-associated-pages" class="vector-menu vector-menu-tabs mw-portlet mw-portlet-associated-pages" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-nstab-main" class="selected vector-tab-noicon mw-list-item"><a href="/wiki/IPv6" title="View the content page [c]" accesskey="c">Article</a></li><li id="ca-talk" class="vector-tab-noicon mw-list-item"><a href="/wiki/Talk:IPv6" rel="discussion" title="Discuss improvements to the content page [t]" accesskey="t">Talk</a></li> </ul> </div> </div> <div id="vector-variants-dropdown" class="vector-dropdown emptyPortlet" > <input type="checkbox" id="vector-variants-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-variants-dropdown" class="vector-dropdown-checkbox " aria-label="Change language variant" > <label id="vector-variants-dropdown-label" for="vector-variants-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet" aria-hidden="true" >English </label> <div class="vector-dropdown-content"> <div id="p-variants" class="vector-menu mw-portlet mw-portlet-variants emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> </div> </div> </nav> </div> <div id="right-navigation" class="vector-collapsible"> <nav aria-label="Views"> <div id="p-views" class="vector-menu vector-menu-tabs mw-portlet mw-portlet-views" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-view" class="selected vector-tab-noicon mw-list-item"><a href="/wiki/IPv6">Read</a></li><li id="ca-edit" class="vector-tab-noicon mw-list-item"><a href="/w/index.php?title=IPv6&action=edit" title="Edit this page [e]" accesskey="e">Edit</a></li><li id="ca-history" class="vector-tab-noicon mw-list-item"><a href="/w/index.php?title=IPv6&action=history" title="Past revisions of this page [h]" accesskey="h">View history</a></li> </ul> </div> </div> </nav> <nav class="vector-page-tools-landmark" aria-label="Page tools"> <div id="vector-page-tools-dropdown" class="vector-dropdown vector-page-tools-dropdown" > <input type="checkbox" id="vector-page-tools-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-page-tools-dropdown" class="vector-dropdown-checkbox " aria-label="Tools" > <label id="vector-page-tools-dropdown-label" for="vector-page-tools-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet" aria-hidden="true" >Tools </label> <div class="vector-dropdown-content"> <div id="vector-page-tools-unpinned-container" class="vector-unpinned-container"> <div id="vector-page-tools" class="vector-page-tools vector-pinnable-element"> <div class="vector-pinnable-header vector-page-tools-pinnable-header vector-pinnable-header-unpinned" data-feature-name="page-tools-pinned" data-pinnable-element-id="vector-page-tools" data-pinned-container-id="vector-page-tools-pinned-container" data-unpinned-container-id="vector-page-tools-unpinned-container" > <div class="vector-pinnable-header-label">Tools</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-page-tools.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-page-tools.unpin">hide</button> </div> <div id="p-cactions" class="vector-menu mw-portlet mw-portlet-cactions emptyPortlet vector-has-collapsible-items" title="More options" > <div class="vector-menu-heading"> Actions </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-more-view" class="selected vector-more-collapsible-item mw-list-item"><a href="/wiki/IPv6">Read</a></li><li id="ca-more-edit" class="vector-more-collapsible-item mw-list-item"><a href="/w/index.php?title=IPv6&action=edit" title="Edit this page [e]" accesskey="e">Edit</a></li><li id="ca-more-history" class="vector-more-collapsible-item mw-list-item"><a href="/w/index.php?title=IPv6&action=history">View history</a></li> </ul> </div> </div> <div id="p-tb" class="vector-menu mw-portlet mw-portlet-tb" > <div class="vector-menu-heading"> General </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="t-whatlinkshere" class="mw-list-item"><a href="/wiki/Special:WhatLinksHere/IPv6" title="List of all English Wikipedia pages containing links to this page [j]" accesskey="j">What links here</a></li><li id="t-recentchangeslinked" class="mw-list-item"><a href="/wiki/Special:RecentChangesLinked/IPv6" rel="nofollow" title="Recent changes in pages linked from this page [k]" accesskey="k">Related changes</a></li><li id="t-upload" class="mw-list-item"><a href="/wiki/Wikipedia:File_Upload_Wizard" title="Upload files [u]" accesskey="u">Upload file</a></li><li id="t-specialpages" class="mw-list-item"><a href="/wiki/Special:SpecialPages" title="A list of all special pages [q]" accesskey="q">Special pages</a></li><li id="t-permalink" class="mw-list-item"><a href="/w/index.php?title=IPv6&oldid=1247827527" title="Permanent link to this revision of this page">Permanent link</a></li><li id="t-info" class="mw-list-item"><a href="/w/index.php?title=IPv6&action=info" title="More information about this page">Page information</a></li><li id="t-cite" class="mw-list-item"><a href="/w/index.php?title=Special:CiteThisPage&page=IPv6&id=1247827527&wpFormIdentifier=titleform" title="Information on how to cite this page">Cite this page</a></li><li id="t-urlshortener" class="mw-list-item"><a href="/w/index.php?title=Special:UrlShortener&url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FIPv6">Get shortened URL</a></li><li id="t-urlshortener-qrcode" class="mw-list-item"><a href="/w/index.php?title=Special:QrCode&url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FIPv6">Download QR code</a></li> </ul> </div> </div> <div id="p-coll-print_export" class="vector-menu mw-portlet mw-portlet-coll-print_export" > <div class="vector-menu-heading"> Print/export </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="coll-download-as-rl" class="mw-list-item"><a href="/w/index.php?title=Special:DownloadAsPdf&page=IPv6&action=show-download-screen" title="Download this page as a PDF file">Download as PDF</a></li><li id="t-print" class="mw-list-item"><a href="/w/index.php?title=IPv6&printable=yes" title="Printable version of this page [p]" accesskey="p">Printable version</a></li> </ul> </div> </div> <div id="p-wikibase-otherprojects" class="vector-menu mw-portlet mw-portlet-wikibase-otherprojects" > <div class="vector-menu-heading"> In other projects </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li class="wb-otherproject-link wb-otherproject-commons mw-list-item"><a href="https://commons.wikimedia.org/wiki/Category:IPv6" hreflang="en">Wikimedia Commons</a></li><li class="wb-otherproject-link wb-otherproject-mediawiki mw-list-item"><a href="https://www.mediawiki.org/wiki/IPv6_support" hreflang="en">MediaWiki</a></li><li class="wb-otherproject-link wb-otherproject-wikiversity mw-list-item"><a href="https://en.wikiversity.org/wiki/IPv6" hreflang="en">Wikiversity</a></li><li id="t-wikibase" class="wb-otherproject-link wb-otherproject-wikibase-dataitem mw-list-item"><a href="https://www.wikidata.org/wiki/Special:EntityPage/Q2551624" title="Structured data on this page hosted by Wikidata [g]" accesskey="g">Wikidata item</a></li> </ul> </div> </div> </div> </div> </div> </div> </nav> </div> </div> </div> <div class="vector-column-end"> <div class="vector-sticky-pinned-container"> <nav class="vector-page-tools-landmark" aria-label="Page tools"> <div id="vector-page-tools-pinned-container" class="vector-pinned-container"> </div> </nav> <nav class="vector-appearance-landmark" aria-label="Appearance"> <div id="vector-appearance-pinned-container" class="vector-pinned-container"> <div id="vector-appearance" class="vector-appearance vector-pinnable-element"> <div class="vector-pinnable-header vector-appearance-pinnable-header vector-pinnable-header-pinned" data-feature-name="appearance-pinned" data-pinnable-element-id="vector-appearance" data-pinned-container-id="vector-appearance-pinned-container" data-unpinned-container-id="vector-appearance-unpinned-container" > <div class="vector-pinnable-header-label">Appearance</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-appearance.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-appearance.unpin">hide</button> </div> </div> </div> </nav> </div> </div> <div id="bodyContent" class="vector-body" aria-labelledby="firstHeading" data-mw-ve-target-container> <div class="vector-body-before-content"> <div class="mw-indicators"> </div> <div id="siteSub" class="noprint">From Wikipedia, the free encyclopedia</div> </div> <div id="contentSub"><div id="mw-content-subtitle">(Redirected from <a href="/w/index.php?title=Internet_Protocol_Version_6&redirect=no" class="mw-redirect" title="Internet Protocol Version 6">Internet Protocol Version 6</a>)</div></div> <div id="mw-content-text" class="mw-body-content"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><div class="shortdescription nomobile noexcerpt noprint searchaux" style="display:none">Version 6 of the Internet Protocol</div> <style data-mw-deduplicate="TemplateStyles:r1251242444">.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}</style><table class="box-Update plainlinks metadata ambox ambox-content ambox-Update" role="presentation"><tbody><tr><td class="mbox-image"><div class="mbox-image-div"><img alt="" src="//upload.wikimedia.org/wikipedia/commons/thumb/b/bd/Ambox_current_red_Asia_Australia.svg/42px-Ambox_current_red_Asia_Australia.svg.png" decoding="async" width="42" height="34" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/b/bd/Ambox_current_red_Asia_Australia.svg/63px-Ambox_current_red_Asia_Australia.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/b/bd/Ambox_current_red_Asia_Australia.svg/84px-Ambox_current_red_Asia_Australia.svg.png 2x" data-file-width="360" data-file-height="290" /></div></td><td class="mbox-text"><div class="mbox-text-span">Parts of this article (those related to RFC 8200 and RFC 8201) need to be updated. Please help update this article to reflect recent events or newly available information. (July 2017)</div></td></tr></tbody></table> <style data-mw-deduplicate="TemplateStyles:r1257001546">.mw-parser-output .infobox-subbox{padding:0;border:none;margin:-3px;width:auto;min-width:100%;font-size:100%;clear:none;float:none;background-color:transparent}.mw-parser-output .infobox-3cols-child{margin:auto}.mw-parser-output .infobox .navbar{font-size:100%}@media screen{html.skin-theme-clientpref-night .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .infobox-full-data:not(.notheme) div:not(.notheme){background:#1f1f23!important;color:#f8f9fa}}@media(min-width:640px){body.skin--responsive .mw-parser-output .infobox-table{display:table!important}body.skin--responsive .mw-parser-output .infobox-table>caption{display:table-caption!important}body.skin--responsive .mw-parser-output .infobox-table>tbody{display:table-row-group}body.skin--responsive .mw-parser-output .infobox-table tr{display:table-row!important}body.skin--responsive .mw-parser-output .infobox-table th,body.skin--responsive .mw-parser-output .infobox-table td{padding-left:inherit;padding-right:inherit}}</style><table class="infobox vevent" style="width:26em;"><caption class="infobox-title summary">Internet Protocol version 6</caption><tbody><tr><td colspan="2" class="infobox-subheader"><a href="/wiki/Protocol_stack" title="Protocol stack">Protocol stack</a></td></tr><tr><td colspan="2" class="infobox-image"><a href="/wiki/File:IPv6_header-en.svg" class="mw-file-description"><img alt="Diagram of an IPV6 header" src="//upload.wikimedia.org/wikipedia/commons/thumb/4/4c/IPv6_header-en.svg/300px-IPv6_header-en.svg.png" decoding="async" width="300" height="138" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/4/4c/IPv6_header-en.svg/450px-IPv6_header-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/4/4c/IPv6_header-en.svg/600px-IPv6_header-en.svg.png 2x" data-file-width="506" data-file-height="233" /></a><div class="infobox-caption">IPv6 header</div></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Abbreviation</th><td class="infobox-data">IPv6</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Purpose</th><td class="infobox-data"><a href="/wiki/Internetworking" title="Internetworking">Internetworking</a> protocol</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Developer(s)</th><td class="infobox-data"><a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Introduction</th><td class="infobox-data">December 1995; 28 years ago (1995-12)</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Based on</th><td class="infobox-data"><a href="/wiki/IPv4" title="IPv4">IPv4</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;"><a href="/wiki/OSI_model" title="OSI model">OSI layer</a></th><td class="infobox-data"><a href="/wiki/Network_layer" title="Network layer">Network layer</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;"><a href="/wiki/Request_for_Comments" title="Request for Comments">RFC(s)</a></th><td class="infobox-data"><style data-mw-deduplicate="TemplateStyles:r1238218222">.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("//upload.wikimedia.org/wikipedia/commons/6/65/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("//upload.wikimedia.org/wikipedia/commons/d/d6/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("//upload.wikimedia.org/wikipedia/commons/a/aa/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("//upload.wikimedia.org/wikipedia/commons/4/4c/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}</style><a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2460">2460</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8200">8200</a></td></tr></tbody></table> <style data-mw-deduplicate="TemplateStyles:r1129693374">.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}</style><style data-mw-deduplicate="TemplateStyles:r1246091330">.mw-parser-output .sidebar{width:22em;float:right;clear:right;margin:0.5em 0 1em 1em;background:var(--background-color-neutral-subtle,#f8f9fa);border:1px solid var(--border-color-base,#a2a9b1);padding:0.2em;text-align:center;line-height:1.4em;font-size:88%;border-collapse:collapse;display:table}body.skin-minerva .mw-parser-output .sidebar{display:table!important;float:right!important;margin:0.5em 0 1em 1em!important}.mw-parser-output .sidebar-subgroup{width:100%;margin:0;border-spacing:0}.mw-parser-output .sidebar-left{float:left;clear:left;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-none{float:none;clear:both;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-outer-title{padding:0 0.4em 0.2em;font-size:125%;line-height:1.2em;font-weight:bold}.mw-parser-output .sidebar-top-image{padding:0.4em}.mw-parser-output .sidebar-top-caption,.mw-parser-output .sidebar-pretitle-with-top-image,.mw-parser-output .sidebar-caption{padding:0.2em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-pretitle{padding:0.4em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-title,.mw-parser-output .sidebar-title-with-pretitle{padding:0.2em 0.8em;font-size:145%;line-height:1.2em}.mw-parser-output .sidebar-title-with-pretitle{padding:0.1em 0.4em}.mw-parser-output .sidebar-image{padding:0.2em 0.4em 0.4em}.mw-parser-output .sidebar-heading{padding:0.1em 0.4em}.mw-parser-output .sidebar-content{padding:0 0.5em 0.4em}.mw-parser-output .sidebar-content-with-subgroup{padding:0.1em 0.4em 0.2em}.mw-parser-output .sidebar-above,.mw-parser-output .sidebar-below{padding:0.3em 0.8em;font-weight:bold}.mw-parser-output .sidebar-collapse .sidebar-above,.mw-parser-output .sidebar-collapse .sidebar-below{border-top:1px solid #aaa;border-bottom:1px solid #aaa}.mw-parser-output .sidebar-navbar{text-align:right;font-size:115%;padding:0 0.4em 0.4em}.mw-parser-output .sidebar-list-title{padding:0 0.4em;text-align:left;font-weight:bold;line-height:1.6em;font-size:105%}.mw-parser-output .sidebar-list-title-c{padding:0 0.4em;text-align:center;margin:0 3.3em}@media(max-width:640px){body.mediawiki .mw-parser-output .sidebar{width:100%!important;clear:both;float:none!important;margin-left:0!important;margin-right:0!important}}body.skin--responsive .mw-parser-output .sidebar a>img{max-width:none!important}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media print{body.ns-0 .mw-parser-output .sidebar{display:none!important}}</style><table class="sidebar nomobile nowraplinks hlist"><tbody><tr><th class="sidebar-title"><a href="/wiki/Internet_protocol_suite" title="Internet protocol suite">Internet protocol suite</a></th></tr><tr><th class="sidebar-heading"> <a href="/wiki/Application_layer" title="Application layer">Application layer</a></th></tr><tr><td class="sidebar-content"> <ul><li><a href="/wiki/Border_Gateway_Protocol" title="Border Gateway Protocol">BGP</a></li> <li><a href="/wiki/Dynamic_Host_Configuration_Protocol" title="Dynamic Host Configuration Protocol">DHCP</a> (<a href="/wiki/DHCPv6" title="DHCPv6">v6</a>)</li> <li><a href="/wiki/Domain_Name_System" title="Domain Name System">DNS</a></li> <li><a href="/wiki/File_Transfer_Protocol" title="File Transfer Protocol">FTP</a></li> <li><a href="/wiki/HTTP" title="HTTP">HTTP</a> (<a href="/wiki/HTTP/3" title="HTTP/3">HTTP/3</a>)</li> <li><a href="/wiki/HTTPS" title="HTTPS">HTTPS</a></li> <li><a href="/wiki/Internet_Message_Access_Protocol" title="Internet Message Access Protocol">IMAP</a></li> <li><a href="/wiki/IRC" title="IRC">IRC</a></li> <li><a href="/wiki/Lightweight_Directory_Access_Protocol" title="Lightweight Directory Access Protocol">LDAP</a></li> <li><a href="/wiki/Media_Gateway_Control_Protocol" title="Media Gateway Control Protocol">MGCP</a></li> <li><a href="/wiki/MQTT" title="MQTT">MQTT</a></li> <li><a href="/wiki/Network_News_Transfer_Protocol" title="Network News Transfer Protocol">NNTP</a></li> <li><a href="/wiki/Network_Time_Protocol" title="Network Time Protocol">NTP</a></li> <li><a href="/wiki/Open_Shortest_Path_First" title="Open Shortest Path First">OSPF</a></li> <li><a href="/wiki/Post_Office_Protocol" title="Post Office Protocol">POP</a></li> <li><a href="/wiki/Precision_Time_Protocol" title="Precision Time Protocol">PTP</a></li> <li><a href="/wiki/Open_Network_Computing_Remote_Procedure_Call" class="mw-redirect" title="Open Network Computing Remote Procedure Call">ONC/RPC</a></li> <li><a href="/wiki/Real-time_Transport_Protocol" title="Real-time Transport Protocol">RTP</a></li> <li><a href="/wiki/Real_Time_Streaming_Protocol" class="mw-redirect" title="Real Time Streaming Protocol">RTSP</a></li> <li><a href="/wiki/Routing_Information_Protocol" title="Routing Information Protocol">RIP</a></li> <li><a href="/wiki/Session_Initiation_Protocol" title="Session Initiation Protocol">SIP</a></li> <li><a href="/wiki/Simple_Mail_Transfer_Protocol" title="Simple Mail Transfer Protocol">SMTP</a></li> <li><a href="/wiki/Simple_Network_Management_Protocol" title="Simple Network Management Protocol">SNMP</a></li> <li><a href="/wiki/Secure_Shell" title="Secure Shell">SSH</a></li> <li><a href="/wiki/Telnet" title="Telnet">Telnet</a></li> <li><a href="/wiki/Transport_Layer_Security" title="Transport Layer Security">TLS/SSL</a></li> <li><a href="/wiki/XMPP" title="XMPP">XMPP</a></li> <li><a href="/wiki/Category:Application_layer_protocols" title="Category:Application layer protocols">more...</a></li></ul></td> </tr><tr><th class="sidebar-heading"> <a href="/wiki/Transport_layer" title="Transport layer">Transport layer</a></th></tr><tr><td class="sidebar-content"> <ul><li><a href="/wiki/Transmission_Control_Protocol" title="Transmission Control Protocol">TCP</a></li> <li><a href="/wiki/User_Datagram_Protocol" title="User Datagram Protocol">UDP</a></li> <li><a href="/wiki/Datagram_Congestion_Control_Protocol" title="Datagram Congestion Control Protocol">DCCP</a></li> <li><a href="/wiki/Stream_Control_Transmission_Protocol" title="Stream Control Transmission Protocol">SCTP</a></li> <li><a href="/wiki/Resource_Reservation_Protocol" title="Resource Reservation Protocol">RSVP</a></li> <li><a href="/wiki/QUIC" title="QUIC">QUIC</a></li> <li><a href="/wiki/Category:Transport_layer_protocols" title="Category:Transport layer protocols">more...</a></li></ul></td> </tr><tr><th class="sidebar-heading"> <a href="/wiki/Internet_layer" title="Internet layer">Internet layer</a></th></tr><tr><td class="sidebar-content"> <ul><li><a href="/wiki/Internet_Protocol" title="Internet Protocol">IP</a> <ul><li><a href="/wiki/IPv4" title="IPv4">v4</a></li> <li><a class="mw-selflink selflink">v6</a></li></ul></li> <li><a href="/wiki/Internet_Control_Message_Protocol" title="Internet Control Message Protocol">ICMP</a> (<a href="/wiki/ICMPv6" title="ICMPv6">v6</a>)</li> <li><a href="/wiki/Neighbor_Discovery_Protocol" title="Neighbor Discovery Protocol">NDP</a></li> <li><a href="/wiki/Explicit_Congestion_Notification" title="Explicit Congestion Notification">ECN</a></li> <li><a href="/wiki/Internet_Group_Management_Protocol" title="Internet Group Management Protocol">IGMP</a></li> <li><a href="/wiki/IPsec" title="IPsec">IPsec</a></li> <li><a href="/wiki/Category:Internet_layer_protocols" title="Category:Internet layer protocols">more...</a></li></ul></td> </tr><tr><th class="sidebar-heading"> <a href="/wiki/Link_layer" title="Link layer">Link layer</a></th></tr><tr><td class="sidebar-content"> <ul><li><a href="/wiki/Address_Resolution_Protocol" title="Address Resolution Protocol">ARP</a></li> <li><a href="/wiki/Tunneling_protocol" title="Tunneling protocol">Tunnels</a></li> <li><a href="/wiki/Point-to-Point_Protocol" title="Point-to-Point Protocol">PPP</a></li> <li><a href="/wiki/Medium_access_control" title="Medium access control">MAC</a></li> <li><a href="/wiki/Category:Link_protocols" title="Category:Link protocols">more...</a></li></ul></td> </tr><tr><td class="sidebar-navbar"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><style data-mw-deduplicate="TemplateStyles:r1239400231">.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}</style><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:Internet_protocol_suite" title="Template:Internet protocol suite"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/wiki/Template_talk:Internet_protocol_suite" title="Template talk:Internet protocol suite"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:Internet_protocol_suite" title="Special:EditPage/Template:Internet protocol suite"><abbr title="Edit this template">e</abbr></a></li></ul></div></td></tr></tbody></table> <table cellpadding="1" class="mw-collapsible mw-collapsed" style="width: 220px; float: right; clear: right; border: 1px solid #8888aa; padding: 5px; margin: 0 0 15px 15px; text-align: left;"> <tbody><tr> <td style="background: #ccf; text-align: center;">Internet history timeline </td></tr> <tr> <td> Early research and development: <ul><li>1960–4 (1960–4): <a href="/wiki/RAND" class="mw-redirect" title="RAND">RAND</a> networking concepts developed</li> <li>1962–4 (1962–4): <a href="/wiki/DARPA" title="DARPA">ARPA</a> networking ideas</li> <li>1965 (1965): <a href="/wiki/NPL_network" title="NPL network">NPL network</a> concepts conceived</li> <li>1966 (1966): <a href="/wiki/Merit_Network" title="Merit Network">Merit Network</a> founded</li> <li>1967 (1967): <a href="/wiki/ARPANET" title="ARPANET">ARPANET</a> planning begins</li> <li>1967 (1967): <a href="/wiki/Symposium_on_Operating_Systems_Principles" title="Symposium on Operating Systems Principles">Symposium on Operating Systems Principles</a></li> <li>1969 (1969): NPL followed by the ARPANET carry their first packets</li> <li>1970 (1970): <a href="/wiki/InterNIC#History" title="InterNIC">Network Information Center</a> (NIC)</li> <li>1971 (1971): <a href="/wiki/Tymnet" title="Tymnet">Tymnet</a> switched-circuit network</li> <li>1972 (1972): Merit Network's packet-switched network operational</li> <li>1972 (1972): <a href="/wiki/Internet_Assigned_Numbers_Authority" title="Internet Assigned Numbers Authority">Internet Assigned Numbers Authority</a> (IANA) established</li> <li>1973 (1973): <a href="/wiki/CYCLADES" title="CYCLADES">CYCLADES</a> network demonstrated</li> <li>1973 (1973): <a href="/wiki/PARC_Universal_Packet" title="PARC Universal Packet">PARC Universal Packet</a> development begins</li> <li>1974 (1974): <a href="/wiki/Transmission_Control_Program" class="mw-redirect" title="Transmission Control Program">Transmission Control Program</a> specification published</li> <li>1975 (1975): <a href="/wiki/Telenet" title="Telenet">Telenet</a> commercial packet-switched network</li> <li>1976 (1976): <a href="/wiki/X.25" title="X.25">X.25</a> protocol approved and deployed on <a href="/wiki/Public_data_network" title="Public data network">public data networks</a></li> <li>1978 (1978): <a href="/wiki/Minitel" title="Minitel">Minitel</a> introduced</li> <li>1979 (1979): <a href="/wiki/Internet_Architecture_Board" title="Internet Architecture Board">Internet Activities Board</a> (IAB)</li> <li>1980 (1980): <a href="/wiki/Usenet" title="Usenet">USENET</a> news using <a href="/wiki/UUCP" title="UUCP">UUCP</a></li> <li>1980 (1980): <a href="/wiki/Ethernet" title="Ethernet">Ethernet</a> standard introduced</li> <li>1981 (1981): <a href="/wiki/BITNET" title="BITNET">BITNET</a> established</li></ul> Merging the networks and creating the Internet: <ul><li>1981 (1981): <a href="/wiki/CSNET" title="CSNET">Computer Science Network</a> (CSNET)</li> <li>1982 (1982): <a href="/wiki/Internet_protocol_suite" title="Internet protocol suite">TCP/IP</a> protocol suite formalized</li> <li>1982 (1982): <a href="/wiki/Simple_Mail_Transfer_Protocol" title="Simple Mail Transfer Protocol">Simple Mail Transfer Protocol</a> (SMTP)</li> <li>1983 (1983): <a href="/wiki/Domain_Name_System" title="Domain Name System">Domain Name System</a> (DNS)</li> <li>1983 (1983): <a href="/wiki/MILNET" title="MILNET">MILNET</a> split off from ARPANET</li> <li>1984 (1984): <a href="/wiki/OSI_model" title="OSI model">OSI Reference Model</a> released</li> <li>1985 (1985): <a href="/wiki/Domain_names#Domain_name_registration" class="mw-redirect" title="Domain names">First .COM domain name registered</a></li> <li>1986 (1986): <a href="/wiki/National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> with 56 kbit/s links</li> <li>1986 (1986): <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF)</li> <li>1987 (1987): <a href="/wiki/UUNET" title="UUNET">UUNET</a> founded</li> <li>1988 (1988): <a href="/wiki/National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> upgraded to 1.5 Mbit/s (T1)</li> <li>1988 (1988): <a href="/wiki/Morris_worm" title="Morris worm">Morris worm</a></li> <li>1988 (1988): Complete <a href="/wiki/Internet_protocol_suite" title="Internet protocol suite">Internet protocol suite</a></li> <li>1989 (1989): <a href="/wiki/Border_Gateway_Protocol" title="Border Gateway Protocol">Border Gateway Protocol</a> (BGP)</li> <li>1989 (1989): <a href="/wiki/PSINet" title="PSINet">PSINet</a> founded, allows commercial traffic</li> <li>1989 (1989): <a href="/wiki/Federal_Internet_Exchange" title="Federal Internet Exchange">Federal Internet Exchanges (FIX East|FIXes)</a></li> <li>1990 (1990): <a href="/wiki/Government_Open_Systems_Interconnection_Profile" title="Government Open Systems Interconnection Profile">GOSIP</a> (without <a href="/wiki/Internet_protocol_suite" title="Internet protocol suite">TCP/IP</a>)</li> <li>1990 (1990): ARPANET decommissioned</li> <li>1990 (1990): <a href="/wiki/Advanced_Network_and_Services" title="Advanced Network and Services">Advanced Network and Services</a> (ANS)</li> <li>1990 (1990): <a href="/wiki/UUNET#Early_existence" title="UUNET">UUNET/Alternet</a> allows commercial traffic</li> <li>1990 (1990): <a href="/wiki/Archie_(search_engine)" title="Archie (search engine)">Archie search engine</a></li> <li>1991 (1991): <a href="/wiki/Wide_area_information_server" title="Wide area information server">Wide area information server</a> (WAIS)</li> <li>1991 (1991): <a href="/wiki/Gopher_(protocol)" title="Gopher (protocol)">Gopher</a></li> <li>1991 (1991): <a href="/wiki/Commercial_Internet_eXchange" title="Commercial Internet eXchange">Commercial Internet eXchange</a> (CIX)</li> <li>1991 (1991): <a href="/wiki/Advanced_Network_and_Services" title="Advanced Network and Services">ANS CO+RE</a> allows commercial traffic</li> <li>1991 (1991): <a href="/wiki/World_Wide_Web" title="World Wide Web">World Wide Web</a> (WWW)</li> <li>1992 (1992): <a href="/wiki/National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> upgraded to 45 Mbit/s (T3)</li> <li>1992 (1992): <a href="/wiki/Internet_Society" title="Internet Society">Internet Society</a> (ISOC) established</li> <li>1993 (1993): <a href="/wiki/Classless_Inter-Domain_Routing" title="Classless Inter-Domain Routing">Classless Inter-Domain Routing</a> (CIDR)</li> <li>1993 (1993): <a href="/wiki/InterNIC" title="InterNIC">InterNIC</a> established</li> <li>1993 (1993): <a href="/wiki/AOL" title="AOL">AOL</a> added <a href="/wiki/Usenet" title="Usenet">USENET</a> access</li> <li>1993 (1993): <a href="/wiki/NCSA_Mosaic" title="NCSA Mosaic">Mosaic web browser</a> released</li> <li>1994 (1994): <a href="/wiki/Search_engine" title="Search engine">Full text web search engines</a></li> <li>1994 (1994): <a href="/wiki/North_American_Network_Operators%27_Group" title="North American Network Operators' Group">North American Network Operators' Group</a> (NANOG) established</li></ul> Commercialization, privatization, broader access leads to the modern Internet: <ul><li>1995 (1995): New Internet architecture with commercial <a href="/wiki/Internet_service_provider" title="Internet service provider">ISPs</a> connected at <a href="/wiki/Network_Access_Point" class="mw-redirect" title="Network Access Point">NAPs</a></li> <li>1995 (1995): <a href="/wiki/National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> decommissioned</li> <li>1995 (1995): <a href="/wiki/GOSIP" class="mw-redirect" title="GOSIP">GOSIP</a> updated to allow <a href="/wiki/Internet_protocol_suite" title="Internet protocol suite">TCP/IP</a></li> <li>1995 (1995): <a href="/wiki/Very_high-speed_Backbone_Network_Service" title="Very high-speed Backbone Network Service">very high-speed Backbone Network Service (vBNS)</a></li> <li>1995 (1995): <a class="mw-selflink selflink">IPv6</a> proposed</li> <li>1996 (1996): <a href="/wiki/AOL" title="AOL">AOL</a> changes pricing model from hourly to monthly</li> <li>1998 (1998): <a href="/wiki/ICANN" title="ICANN">Internet Corporation for Assigned Names and Numbers (ICANN)</a></li> <li>1999 (1999): <a href="/wiki/IEEE_802.11" title="IEEE 802.11">IEEE 802.11b</a> wireless networking</li> <li>1999 (1999): <a href="/wiki/Internet2" title="Internet2">Internet2</a>/<a href="/wiki/Abilene_Network" title="Abilene Network">Abilene Network</a></li> <li>1999 (1999): <a href="/wiki/VBNS" class="mw-redirect" title="VBNS">vBNS+</a> allows broader access</li> <li>2000 (2000): <a href="/wiki/Dot-com_bubble" title="Dot-com bubble">Dot-com bubble</a> bursts</li> <li>2001 (2001): <a href="/wiki/Top-level_domain#Proposed_domains" title="Top-level domain">New top-level domain names activated</a></li> <li>2001 (2001): <a href="/wiki/Code_Red_(computer_worm)" title="Code Red (computer worm)">Code Red I</a>, <a href="/wiki/Code_Red_II" title="Code Red II">Code Red II</a>, and <a href="/wiki/Nimda" title="Nimda">Nimda</a> worms</li> <li>2003 (2003): <a href="/wiki/World_Summit_on_the_Information_Society" title="World Summit on the Information Society">UN World Summit on the Information Society (WSIS) phase I</a></li></ul> <ul><li>2003 (2003): <a href="/wiki/National_LambdaRail" title="National LambdaRail">National LambdaRail</a> founded</li> <li>2004 (2004): <a href="/wiki/Working_Group_on_Internet_Governance" title="Working Group on Internet Governance">UN Working Group on Internet Governance (WGIG)</a></li> <li>2005 (2005): <a href="/wiki/World_Summit_on_the_Information_Society" title="World Summit on the Information Society">UN WSIS phase II</a></li> <li>2006 (2006): <a href="/wiki/Internet_Governance_Forum" title="Internet Governance Forum">First meeting of the Internet Governance Forum</a></li> <li>2010 (2010): <a href="/wiki/Top-level_domain#Internationalized_country_code_TLDs" title="Top-level domain">First internationalized country code top-level domains</a> registered</li> <li>2012 (2012): <a href="/wiki/Generic_top-level_domain#New_top-level_domains" title="Generic top-level domain">ICANN begins accepting applications for new generic top-level domain names</a></li> <li>2013 (2013): <a href="/wiki/Montevideo_Statement_on_the_Future_of_Internet_Cooperation" title="Montevideo Statement on the Future of Internet Cooperation">Montevideo Statement on the Future of Internet Cooperation</a></li> <li>2014 (2014): <a href="/wiki/NetMundial_Initiative" title="NetMundial Initiative">NetMundial international Internet governance proposal</a></li> <li>2016 (2016): <a href="/wiki/ICANN" title="ICANN">ICANN</a> contract with U.S. Dept. of Commerce ends, <a href="/wiki/Internet_Assigned_Numbers_Authority" title="Internet Assigned Numbers Authority">IANA</a> oversight passes to the global Internet community on October 1st</li></ul> Examples of Internet services: <ul><li>1989 (1989): <a href="/wiki/AOL" title="AOL">AOL</a> dial-up service provider, email, instant messaging, and web browser</li> <li>1990 (1990): <a href="/wiki/IMDb" title="IMDb">IMDb</a> Internet movie database</li> <li>1994 (1994): <a href="/wiki/Yahoo" title="Yahoo">Yahoo!</a> web directory</li> <li>1995 (1995): <a href="/wiki/Amazon_(company)" title="Amazon (company)">Amazon</a> online retailer</li> <li>1995 (1995): <a href="/wiki/EBay" title="EBay">eBay</a> online auction and shopping</li> <li>1995 (1995): <a href="/wiki/Craigslist" title="Craigslist">Craigslist</a> classified advertisements</li> <li>1995 (1995): <a href="/wiki/AltaVista" title="AltaVista">AltaVista</a> search engine</li> <li>1996 (1996): <a href="/wiki/Outlook.com" title="Outlook.com">Outlook (formerly Hotmail)</a> free web-based e-mail</li> <li>1996 (1996): <a href="/wiki/Baidu" title="Baidu">RankDex</a> search engine</li> <li>1997 (1997): <a href="/wiki/Google_Search" title="Google Search">Google Search</a></li> <li>1997 (1997): <a href="/wiki/Babel_Fish_(website)" title="Babel Fish (website)">Babel Fish</a> automatic translation</li> <li>1998 (1998): <a href="/wiki/Yahoo_Groups" title="Yahoo Groups">Yahoo Groups (formerly Yahoo! Clubs)</a></li> <li>1998 (1998): <a href="/wiki/PayPal" title="PayPal">PayPal</a> Internet payment system</li> <li>1998 (1998): <a href="/wiki/Rotten_Tomatoes" title="Rotten Tomatoes">Rotten Tomatoes</a> review aggregator</li> <li>1999 (1999): <a href="/wiki/2channel" title="2channel">2ch</a> Anonymous textboard</li> <li>1999 (1999): <a href="/wiki/I-mode" title="I-mode">i-mode</a> mobile internet service</li> <li>1999 (1999): <a href="/wiki/Napster" title="Napster">Napster</a> peer-to-peer file sharing</li> <li>2000 (2000): <a href="/wiki/Baidu" title="Baidu">Baidu</a> search engine</li> <li>2001 (2001): <a href="/wiki/Futaba_Channel" title="Futaba Channel">2chan</a> Anonymous imageboard</li> <li>2001 (2001): <a href="/wiki/BitTorrent_(software)" title="BitTorrent (software)">BitTorrent</a> peer-to-peer file sharing</li> <li>2001 (2001): <a href="/wiki/Wikipedia" title="Wikipedia">Wikipedia</a>, the free encyclopedia</li> <li>2003 (2003): <a href="/wiki/LinkedIn" title="LinkedIn">LinkedIn</a> business networking</li> <li>2003 (2003): <a href="/wiki/Myspace" title="Myspace">Myspace</a> social networking site</li> <li>2003 (2003): <a href="/wiki/Skype" title="Skype">Skype</a> Internet voice calls</li> <li>2003 (2003): <a href="/wiki/ITunes_Store" title="ITunes Store">iTunes Store</a></li> <li>2003 (2003): <a href="/wiki/4chan" title="4chan">4chan</a> Anonymous imageboard</li> <li>2003 (2003): <a href="/wiki/The_Pirate_Bay" title="The Pirate Bay">The Pirate Bay</a>, <a href="/wiki/Torrent_file" title="Torrent file">torrent file</a> host</li> <li>2004 (2004): <a href="/wiki/Facebook" title="Facebook">Facebook</a> social networking site</li> <li>2004 (2004): <a href="/wiki/Podcast" title="Podcast">Podcast</a> media file series</li> <li>2004 (2004): <a href="/wiki/Flickr" title="Flickr">Flickr</a> image hosting</li> <li>2005 (2005): <a href="/wiki/YouTube" title="YouTube">YouTube</a> video sharing</li> <li>2005 (2005): <a href="/wiki/Reddit" title="Reddit">Reddit</a> link voting</li> <li>2005 (2005): <a href="/wiki/Google_Earth" title="Google Earth">Google Earth</a> virtual globe</li> <li>2006 (2006): <a href="/wiki/Twitter" title="Twitter">Twitter</a> microblogging</li> <li>2007 (2007): <a href="/wiki/WikiLeaks" title="WikiLeaks">WikiLeaks</a> anonymous news and information leaks</li> <li>2007 (2007): <a href="/wiki/Google_Street_View" title="Google Street View">Google Street View</a></li> <li>2007 (2007): <a href="/wiki/Amazon_Kindle" title="Amazon Kindle">Kindle</a>, <a href="/wiki/E-reader" title="E-reader">e-reader</a> and virtual bookshop</li> <li>2008 (2008): <a href="/wiki/Amazon_Elastic_Compute_Cloud" title="Amazon Elastic Compute Cloud">Amazon Elastic Compute Cloud</a> (EC2)</li> <li>2008 (2008): <a href="/wiki/Dropbox" title="Dropbox">Dropbox</a> cloud-based file hosting</li> <li>2008 (2008): <a href="/wiki/Encyclopedia_of_Life" title="Encyclopedia of Life">Encyclopedia of Life</a>, a collaborative encyclopedia intended to document all living species</li> <li>2008 (2008): <a href="/wiki/Spotify" title="Spotify">Spotify</a>, a <a href="/wiki/Digital_rights_management" title="Digital rights management">DRM-based</a> music streaming service</li> <li>2009 (2009): <a href="/wiki/Microsoft_Bing" title="Microsoft Bing">Bing</a> search engine</li> <li>2009 (2009): <a href="/wiki/Google_Docs" title="Google Docs">Google Docs</a>, Web-based word processor, spreadsheet, presentation, form, and data storage service</li> <li>2009 (2009): <a href="/wiki/Kickstarter" title="Kickstarter">Kickstarter</a>, a <a href="/wiki/Threshold_pledge_system" title="Threshold pledge system">threshold pledge system</a></li> <li>2009 (2009): <a href="/wiki/Bitcoin" title="Bitcoin">Bitcoin</a>, a <a href="/wiki/Digital_currency" title="Digital currency">digital currency</a></li> <li>2010 (2010): <a href="/wiki/Instagram" title="Instagram">Instagram</a>, <a href="/wiki/Photo_sharing" class="mw-redirect" title="Photo sharing">photo sharing</a> and <a href="/wiki/Social_networking" class="mw-redirect" title="Social networking">social networking</a></li> <li>2011 (2011): <a href="/wiki/Google%2B" title="Google+">Google+</a>, <a href="/wiki/Social_networking" class="mw-redirect" title="Social networking">social networking</a></li> <li>2011 (2011): <a href="/wiki/Snapchat" title="Snapchat">Snapchat</a>, <a href="/wiki/Photo_sharing" class="mw-redirect" title="Photo sharing">photo sharing</a></li> <li>2012 (2012): <a href="/wiki/Coursera" title="Coursera">Coursera</a>, massive open online courses</li> <li>2016 (2016): <a href="/wiki/TikTok" title="TikTok">TikTok</a>, <a href="/wiki/Video_sharing" class="mw-redirect" title="Video sharing">video sharing</a> and <a href="/wiki/Social_networking" class="mw-redirect" title="Social networking">social networking</a></li></ul> </td></tr></tbody></table> Internet Protocol version 6 (IPv6) is the most recent version of the <a href="/wiki/Internet_Protocol" title="Internet Protocol">Internet Protocol</a> (IP), the <a href="/wiki/Communication_protocol" title="Communication protocol">communications protocol</a> that provides an identification and location system for computers on networks and routes traffic across the <a href="/wiki/Internet" title="Internet">Internet</a>. IPv6 was developed by the <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF) to deal with the long-anticipated problem of <a href="/wiki/IPv4_address_exhaustion" title="IPv4 address exhaustion">IPv4 address exhaustion</a>, and was intended to replace <a href="/wiki/IPv4" title="IPv4">IPv4</a>.<a href="#cite_note-ipv6nz-1">[1]</a> In December 1998, IPv6 became a Draft Standard for the IETF,<a href="#cite_note-rfc2460-2">[2]</a> which subsequently ratified it as an <a href="/wiki/Internet_Standard" title="Internet Standard">Internet Standard</a> on 14 July 2017.<a href="#cite_note-rfc8200-3">[3]</a><a href="#cite_note-4">[4]</a> Devices on the Internet are assigned a unique <a href="/wiki/IP_address" title="IP address">IP address</a> for identification and location definition. With the rapid growth of the Internet after commercialization in the 1990s, it became evident that far more addresses would be needed to connect devices than the IPv4 address space had available. By 1998, the IETF had formalized the successor protocol. IPv6 uses 128-<a href="/wiki/Bit" title="Bit">bit</a> addresses, theoretically allowing 2128, or approximately 3.4×1038 total addresses. The actual number is slightly smaller, as multiple ranges are reserved for special usage or completely excluded from general use. The two protocols are not designed to be <a href="/wiki/Interoperable" class="mw-redirect" title="Interoperable">interoperable</a>, and thus direct communication between them is impossible, complicating the move to IPv6. However, several <a href="/wiki/IPv6_transition_mechanism" title="IPv6 transition mechanism">transition mechanisms</a> have been devised to rectify this. IPv6 provides other technical benefits in addition to a larger addressing space. In particular, it permits hierarchical address allocation methods that facilitate <a href="/wiki/Route_aggregation" class="mw-redirect" title="Route aggregation">route aggregation</a> across the Internet, and thus limit the expansion of <a href="/wiki/Routing_table" title="Routing table">routing tables</a>. The use of multicast addressing is expanded and simplified, and provides additional optimization for the delivery of services. Device mobility, security, and configuration aspects have been considered in the design of the protocol. IPv6 addresses are represented as eight groups of four <a href="/wiki/Hexadecimal" title="Hexadecimal">hexadecimal</a> digits each, separated by colons. The full representation may be shortened; for example, 2001:0db8:0000:0000:0000:8a2e:0370:7334 becomes 2001:db8::8a2e:370:7334. <style data-mw-deduplicate="TemplateStyles:r886046785">.mw-parser-output .toclimit-2 .toclevel-1 ul,.mw-parser-output .toclimit-3 .toclevel-2 ul,.mw-parser-output .toclimit-4 .toclevel-3 ul,.mw-parser-output .toclimit-5 .toclevel-4 ul,.mw-parser-output .toclimit-6 .toclevel-5 ul,.mw-parser-output .toclimit-7 .toclevel-6 ul{display:none}</style><div class="toclimit-3"><meta property="mw:PageProp/toc" /></div> <div class="mw-heading mw-heading2"><h2 id="Main_features">Main features</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=1" title="Edit section: Main features">edit</a>]</div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv6_address_terminology-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/5/5e/IPv6_address_terminology-en.svg/260px-IPv6_address_terminology-en.svg.png" decoding="async" width="260" height="94" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/5/5e/IPv6_address_terminology-en.svg/390px-IPv6_address_terminology-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/5/5e/IPv6_address_terminology-en.svg/520px-IPv6_address_terminology-en.svg.png 2x" data-file-width="720" data-file-height="259" /></a><figcaption>Glossary of terms used for IPv6 addresses</figcaption></figure> IPv6 is an <a href="/wiki/Internet_Layer" class="mw-redirect" title="Internet Layer">Internet Layer</a> protocol for <a href="/wiki/Packet_switching" title="Packet switching">packet-switched</a> <a href="/wiki/Internetworking" title="Internetworking">internetworking</a> and provides end-to-end <a href="/wiki/Datagram" title="Datagram">datagram</a> transmission across multiple IP networks, closely adhering to the design principles developed in the previous version of the protocol, <a href="/wiki/IPv4" title="IPv4">Internet Protocol Version 4</a> (IPv4). In addition to offering more addresses, IPv6 also implements features not present in IPv4. It simplifies aspects of address configuration, network renumbering, and router announcements when changing network connectivity providers. It simplifies packet processing in routers by placing the responsibility for packet fragmentation in the end points. The IPv6 <a href="/wiki/Subnetwork" class="mw-redirect" title="Subnetwork">subnet</a> size is standardized by fixing the size of the host identifier portion of an address to 64 bits. The addressing architecture of IPv6 is defined in <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4291">4291</a> and allows three different types of transmission: <a href="/wiki/Unicast" title="Unicast">unicast</a>, <a href="/wiki/Anycast" title="Anycast">anycast</a> and <a href="/wiki/Multicast" title="Multicast">multicast</a>.<a href="#cite_note-Rosen_kernel_networking-5">[5]</a>: 210  <div class="mw-heading mw-heading2"><h2 id="Motivation_and_origin">Motivation and origin</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=2" title="Edit section: Motivation and origin">edit</a>]</div> <div class="mw-heading mw-heading3"><h3 id="IPv4_address_exhaustion">IPv4 address exhaustion</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=3" title="Edit section: IPv4 address exhaustion">edit</a>]</div> <style data-mw-deduplicate="TemplateStyles:r1236090951">.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}</style><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="/wiki/IPv4_address_exhaustion" title="IPv4 address exhaustion">IPv4 address exhaustion</a></div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv4_address_structure_and_writing_systems-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/6/66/IPv4_address_structure_and_writing_systems-en.svg/260px-IPv4_address_structure_and_writing_systems-en.svg.png" decoding="async" width="260" height="88" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/6/66/IPv4_address_structure_and_writing_systems-en.svg/390px-IPv4_address_structure_and_writing_systems-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/6/66/IPv4_address_structure_and_writing_systems-en.svg/520px-IPv4_address_structure_and_writing_systems-en.svg.png 2x" data-file-width="1138" data-file-height="386" /></a><figcaption>Decomposition of the dot-decimal <a href="/wiki/IPv4_address" class="mw-redirect" title="IPv4 address">IPv4 address</a> representation to its binary notation</figcaption></figure> <a href="/wiki/IPv4" title="IPv4">Internet Protocol Version 4</a> (IPv4) was the first publicly used version of the <a href="/wiki/Internet_Protocol" title="Internet Protocol">Internet Protocol</a>. IPv4 was developed as a research project by the <a href="/wiki/DARPA" title="DARPA">Defense Advanced Research Projects Agency</a> (DARPA), a <a href="/wiki/United_States_Department_of_Defense" title="United States Department of Defense">United States Department of Defense</a> <a href="/wiki/Government_agency" title="Government agency">agency</a>, before becoming the foundation for the <a href="/wiki/Internet" title="Internet">Internet</a> and the <a href="/wiki/World_Wide_Web" title="World Wide Web">World Wide Web</a>. IPv4 includes an addressing system that uses numerical identifiers consisting of 32 bits. These addresses are typically displayed in <a href="/wiki/Dot-decimal_notation" title="Dot-decimal notation">dot-decimal notation</a> as decimal values of four octets, each in the range 0 to 255, or 8 bits per number. Thus, IPv4 provides an addressing capability of 232 or approximately 4.3 billion addresses. Address exhaustion was not initially a concern in IPv4 as this version was originally presumed to be a test of DARPA's networking concepts.<a href="#cite_note-6">[6]</a> During the first decade of operation of the Internet, it became apparent that methods had to be developed to conserve address space. In the early 1990s, even after the redesign of the addressing system using a <a href="/wiki/Classless_Inter-Domain_Routing" title="Classless Inter-Domain Routing">classless network</a> model, it became clear that this would not suffice to prevent <a href="/wiki/IPv4_address_exhaustion" title="IPv4 address exhaustion">IPv4 address exhaustion</a>, and that further changes to the Internet infrastructure were needed.<a href="#cite_note-rfc1752-7">[7]</a> The last unassigned top-level address blocks of 16 million IPv4 addresses were allocated in February 2011 by the <a href="/wiki/Internet_Assigned_Numbers_Authority" title="Internet Assigned Numbers Authority">Internet Assigned Numbers Authority</a> (IANA) to the five <a href="/wiki/Regional_Internet_registry" title="Regional Internet registry">regional Internet registries</a> (RIRs).<a href="#cite_note-8">[8]</a> However, each RIR still has available address pools and is expected to continue with standard address allocation policies until one /8 <a href="/wiki/Classless_Inter-Domain_Routing" title="Classless Inter-Domain Routing">Classless Inter-Domain Routing</a> (CIDR) block remains. After that, only blocks of 1,024 addresses (/22) will be provided from the RIRs to a <a href="/wiki/Local_Internet_registry" class="mw-redirect" title="Local Internet registry">local Internet registry</a> (LIR). As of September 2015, all of <a href="/wiki/Asia-Pacific_Network_Information_Centre" class="mw-redirect" title="Asia-Pacific Network Information Centre">Asia-Pacific Network Information Centre</a> (APNIC), the <a href="/wiki/RIPE_NCC" title="RIPE NCC">Réseaux IP Européens Network Coordination Centre</a> (RIPE NCC), <a href="/wiki/Latin_America_and_Caribbean_Network_Information_Centre" class="mw-redirect" title="Latin America and Caribbean Network Information Centre">Latin America and Caribbean Network Information Centre</a> (LACNIC), and <a href="/wiki/American_Registry_for_Internet_Numbers" title="American Registry for Internet Numbers">American Registry for Internet Numbers</a> (ARIN) have reached this stage.<a href="#cite_note-9">[9]</a><a href="#cite_note-10">[10]</a><a href="#cite_note-11">[11]</a> This leaves <a href="/wiki/AFRINIC" title="AFRINIC">African Network Information Center</a> (AFRINIC) as the sole regional internet registry that is still using the normal protocol for distributing IPv4 addresses. As of November 2018, AFRINIC's minimum allocation is /22 or 1024 IPv4 addresses. A <a href="/wiki/Local_Internet_registry" class="mw-redirect" title="Local Internet registry">LIR</a> may receive additional allocation when about 80% of all the address space has been utilized.<a href="#cite_note-12">[12]</a> RIPE NCC announced that it had fully run out of IPv4 addresses on 25 November 2019,<a href="#cite_note-13">[13]</a> and called for greater progress on the adoption of IPv6. <div class="mw-heading mw-heading2"><h2 id="Comparison_with_IPv4">Comparison with IPv4</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=4" title="Edit section: Comparison with IPv4">edit</a>]</div> On the Internet, data is transmitted in the form of <a href="/wiki/Network_packet" title="Network packet">network packets</a>. IPv6 specifies a new <a href="/wiki/IPv6_packet" title="IPv6 packet">packet format</a>, designed to minimize packet header processing by routers.<a href="#cite_note-rfc2460-2">[2]</a><a href="#cite_note-rfc1726-14">[14]</a> Because the headers of IPv4 packets and IPv6 packets are significantly different, the two protocols are not interoperable. However, most transport and application-layer protocols need little or no change to operate over IPv6; exceptions are application protocols that embed Internet-layer addresses, such as <a href="/wiki/File_Transfer_Protocol" title="File Transfer Protocol">File Transfer Protocol</a> (FTP) and <a href="/wiki/Network_Time_Protocol" title="Network Time Protocol">Network Time Protocol</a> (NTP), where the new address format may cause conflicts with existing protocol syntax. <div class="mw-heading mw-heading3"><h3 id="Larger_address_space">Larger address space</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=5" title="Edit section: Larger address space">edit</a>]</div> The main advantage of IPv6 over IPv4 is its larger address space. The size of an IPv6 address is 128 bits, compared to 32 bits in IPv4.<a href="#cite_note-rfc2460-2">[2]</a> The address space therefore has 2128=340,282,366,920,938,463,463,374,607,431,768,211,456 addresses (340 <a href="/wiki/Undecillion" class="mw-redirect" title="Undecillion">undecillion</a>, approximately 3.4×1038). Some blocks of this space and some specific addresses are <a href="/wiki/Reserved_IP_addresses" title="Reserved IP addresses">reserved for special uses</a>. While this address space is very large, it was not the intent of the designers of IPv6 to assure geographical saturation with usable addresses. Rather, the longer addresses simplify allocation of addresses, enable efficient <a href="/wiki/Route_aggregation" class="mw-redirect" title="Route aggregation">route aggregation</a>, and allow implementation of special addressing features. In IPv4, complex <a href="/wiki/Classless_Inter-Domain_Routing" title="Classless Inter-Domain Routing">Classless Inter-Domain Routing</a> (CIDR) methods were developed to make the best use of the small address space. The standard size of a subnet in IPv6 is 264 addresses, about four billion times the size of the entire IPv4 address space. Thus, actual address space utilization will be small in IPv6, but network management and routing efficiency are improved by the large subnet space and hierarchical route aggregation. <div class="mw-heading mw-heading3"><h3 id="Multicasting">Multicasting</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=6" title="Edit section: Multicasting">edit</a>]</div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv6_multicast_address_stracture-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/2/2f/IPv6_multicast_address_stracture-en.svg/220px-IPv6_multicast_address_stracture-en.svg.png" decoding="async" width="220" height="41" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/2/2f/IPv6_multicast_address_stracture-en.svg/330px-IPv6_multicast_address_stracture-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/2/2f/IPv6_multicast_address_stracture-en.svg/440px-IPv6_multicast_address_stracture-en.svg.png 2x" data-file-width="716" data-file-height="132" /></a><figcaption>Multicast structure in IPv6</figcaption></figure> <a href="/wiki/Multicast" title="Multicast">Multicasting</a>, the transmission of a packet to multiple destinations in a single send operation, is part of the base specification in IPv6. In IPv4 this is an optional (although commonly implemented) feature.<a href="#cite_note-rfc1112-15">[15]</a> IPv6 multicast addressing has features and protocols in common with IPv4 multicast, but also provides changes and improvements by eliminating the need for certain protocols. IPv6 does not implement traditional <a href="/wiki/Broadcast_IP_address" class="mw-redirect" title="Broadcast IP address">IP broadcast</a>, i.e. the transmission of a packet to all hosts on the attached link using a special broadcast address, and therefore does not define broadcast addresses. In IPv6, the same result is achieved by sending a packet to the link-local all nodes multicast group at address ff02::1, which is analogous to IPv4 multicasting to address 224.0.0.1. IPv6 also provides for new multicast implementations, including embedding rendezvous point addresses in an IPv6 multicast group address, which simplifies the deployment of inter-domain solutions.<a href="#cite_note-rfc3956-16">[16]</a> In IPv4 it is very difficult for an organization to get even one globally routable multicast group assignment, and the implementation of inter-domain solutions is arcane.<a href="#cite_note-17">[17]</a> Unicast address assignments by a <a href="/wiki/Local_Internet_registry" class="mw-redirect" title="Local Internet registry">local Internet registry</a> for IPv6 have at least a 64-bit routing prefix, yielding the smallest subnet size available in IPv6 (also 64 bits). With such an assignment it is possible to embed the unicast address prefix into the IPv6 multicast address format, while still providing a 32-bit block, the least significant bits of the address, or approximately 4.2 billion multicast group identifiers. Thus each user of an IPv6 subnet automatically has available a set of globally routable source-specific multicast groups for multicast applications.<a href="#cite_note-18">[18]</a> <div class="mw-heading mw-heading3"><h3 id="Stateless_address_autoconfiguration_(SLAAC)">Stateless address autoconfiguration (SLAAC)</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=7" title="Edit section: Stateless address autoconfiguration (SLAAC)">edit</a>]</div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">See also: <a href="/wiki/IPv6_address#Stateless_address_autoconfiguration_(SLAAC)" title="IPv6 address">IPv6 address § Stateless address autoconfiguration</a></div> IPv6 hosts configure themselves automatically. Every interface has a self-generated link-local address and, when connected to a network, conflict resolution is performed and routers provide network prefixes via router advertisements.<a href="#cite_note-rfc4862-19">[19]</a> Stateless configuration of routers can be achieved with a special router renumbering protocol.<a href="#cite_note-rfc2894-20">[20]</a> When necessary, hosts may configure additional stateful addresses via <a href="/wiki/DHCPv6" title="DHCPv6">Dynamic Host Configuration Protocol version 6</a> (DHCPv6) or static addresses manually. Like IPv4, IPv6 supports globally unique <a href="/wiki/IP_address" title="IP address">IP addresses</a>. The design of IPv6 intended to re-emphasize the end-to-end principle of network design that was originally conceived during the establishment of the early Internet by rendering <a href="/wiki/Network_address_translation" title="Network address translation">network address translation</a> obsolete. Therefore, every device on the network is globally addressable directly from any other device. A stable, unique, globally addressable IP address would facilitate tracking a device across networks. Therefore, such addresses are a particular privacy concern for mobile devices, such as laptops and cell phones.<a href="#cite_note-21">[21]</a> To address these privacy concerns, the SLAAC protocol includes what are typically called "privacy addresses" or, more correctly, "temporary addresses".<a href="#cite_note-rfc8981-22">[22]</a> Temporary addresses are random and unstable. A typical consumer device generates a new temporary address daily and will ignore traffic addressed to an old address after one week. Temporary addresses are used by default by Windows since XP SP1,<a href="#cite_note-23">[23]</a> macOS since (Mac OS X) 10.7, Android since 4.0, and iOS since version 4.3. Use of temporary addresses by Linux distributions varies.<a href="#cite_note-24">[24]</a> Renumbering an existing network for a new connectivity provider with different routing prefixes is a major effort with IPv4.<a href="#cite_note-rfc2071-25">[25]</a><a href="#cite_note-26">[26]</a><a href="#cite_note-27">[27]</a> With IPv6, however, changing the prefix announced by a few routers can in principle renumber an entire network, since the host identifiers (the least-significant 64 bits of an address) can be independently self-configured by a host.<a href="#cite_note-rfc4862-19">[19]</a> The SLAAC address generation method is implementation-dependent. IETF recommends that addresses be deterministic but semantically opaque.<a href="#cite_note-28">[28]</a> <div class="mw-heading mw-heading3"><h3 id="IPsec">IPsec</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=8" title="Edit section: IPsec">edit</a>]</div> <a href="/wiki/Internet_Protocol_Security" class="mw-redirect" title="Internet Protocol Security">Internet Protocol Security</a> (IPsec) was originally developed for IPv6, but found widespread deployment first in IPv4, for which it was re-engineered. IPsec was a mandatory part of all IPv6 protocol implementations,<a href="#cite_note-rfc2460-2">[2]</a> and <a href="/wiki/Internet_Key_Exchange" title="Internet Key Exchange">Internet Key Exchange</a> (IKE) was recommended, but with RFC 6434 the inclusion of IPsec in IPv6 implementations was downgraded to a recommendation because it was considered impractical to require full IPsec implementation for all types of devices that may use IPv6. However, as of RFC 4301 IPv6 protocol implementations that do implement IPsec need to implement IKEv2 and need to support a minimum set of <a href="/wiki/Cryptography" title="Cryptography">cryptographic algorithms</a>. This requirement will help to make IPsec implementations more interoperable between devices from different vendors. The IPsec Authentication Header (AH) and the Encapsulating Security Payload header (ESP) are implemented as IPv6 extension headers.<a href="#cite_note-29">[29]</a> <div class="mw-heading mw-heading3"><h3 id="Simplified_processing_by_routers">Simplified processing by routers</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=9" title="Edit section: Simplified processing by routers">edit</a>]</div> The packet header in IPv6 is simpler than the IPv4 header. Many rarely used fields have been moved to optional header extensions. The IPv6 packet header has simplified the process of packet forwarding by <a href="/wiki/Router_(computing)" title="Router (computing)">routers</a>. Although IPv6 packet headers are at least twice the size of IPv4 packet headers, processing of packets that only contain the base IPv6 header by routers may, in some cases, be more efficient, because less processing is required in routers due to the headers being aligned to match common <a href="/wiki/Word_(computer_architecture)" title="Word (computer architecture)">word sizes</a>.<a href="#cite_note-rfc2460-2">[2]</a><a href="#cite_note-rfc1726-14">[14]</a> However, many devices implement IPv6 support in software (as opposed to hardware), thus resulting in very bad packet processing performance.<a href="#cite_note-30">[30]</a> Additionally, for many implementations, the use of Extension Headers causes packets to be processed by a router's CPU, leading to poor performance or even security issues.<a href="#cite_note-draft-gont-v6ops-ipv6-ehs-packet-drops-03-31">[31]</a> Moreover, an IPv6 header does not include a checksum. The <a href="/wiki/IPv4_header_checksum" class="mw-redirect" title="IPv4 header checksum">IPv4 header checksum</a> is calculated for the IPv4 header, and has to be recalculated by routers every time the <a href="/wiki/Time_to_live" title="Time to live">time to live</a> (called <a href="/wiki/Hop_limit" class="mw-redirect" title="Hop limit">hop limit</a> in the IPv6 protocol) is reduced by one. The absence of a checksum in the IPv6 header furthers the <a href="/wiki/End-to-end_principle" title="End-to-end principle">end-to-end principle</a> of Internet design, which envisioned that most processing in the network occurs in the leaf nodes. Integrity protection for the data that is encapsulated in the IPv6 packet is assumed to be assured by both the <a href="/wiki/Link_layer" title="Link layer">link layer</a> or error detection in higher-layer protocols, namely the <a href="/wiki/Transmission_Control_Protocol" title="Transmission Control Protocol">Transmission Control Protocol</a> (TCP) and the <a href="/wiki/User_Datagram_Protocol" title="User Datagram Protocol">User Datagram Protocol</a> (UDP) on the <a href="/wiki/Transport_layer" title="Transport layer">transport layer</a>. Thus, while IPv4 allowed UDP datagram headers to have no checksum (indicated by 0 in the header field), IPv6 requires a checksum in UDP headers. IPv6 routers do not perform <a href="/wiki/IP_fragmentation" title="IP fragmentation">IP fragmentation</a>. IPv6 hosts are required to do one of the following: perform <a href="/wiki/Path_MTU_Discovery" title="Path MTU Discovery">Path MTU Discovery</a>, perform end-to-end fragmentation, or send packets no larger than the default <a href="/wiki/Maximum_transmission_unit" title="Maximum transmission unit">maximum transmission unit</a> (MTU), which is 1280 <a href="/wiki/Octet_(computing)" title="Octet (computing)">octets</a>. <div class="mw-heading mw-heading3"><h3 id="Mobility">Mobility</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=10" title="Edit section: Mobility">edit</a>]</div> Unlike mobile IPv4, <a href="/wiki/Mobile_IPv6" class="mw-redirect" title="Mobile IPv6">mobile IPv6</a> avoids <a href="/wiki/Triangular_routing" title="Triangular routing">triangular routing</a> and is therefore as efficient as native IPv6. IPv6 routers may also allow entire subnets to move to a new router connection point without renumbering.<a href="#cite_note-rfc3963-32">[32]</a> <div class="mw-heading mw-heading3"><h3 id="Extension_headers">Extension headers</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=11" title="Edit section: Extension headers">edit</a>]</div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv6_headers_sequence-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/9/9a/IPv6_headers_sequence-en.svg/220px-IPv6_headers_sequence-en.svg.png" decoding="async" width="220" height="94" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/9/9a/IPv6_headers_sequence-en.svg/330px-IPv6_headers_sequence-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/9/9a/IPv6_headers_sequence-en.svg/440px-IPv6_headers_sequence-en.svg.png 2x" data-file-width="725" data-file-height="311" /></a><figcaption>Several examples of IPv6 extension headers</figcaption></figure> The IPv6 packet header has a minimum size of 40 octets (320 bits). Options are implemented as extensions. This provides the opportunity to extend the protocol in the future without affecting the core packet structure.<a href="#cite_note-rfc2460-2">[2]</a> However, RFC 7872 notes that some network operators drop IPv6 packets with extension headers when they traverse transit <a href="/wiki/Autonomous_system_(Internet)" title="Autonomous system (Internet)">autonomous systems</a>. <div class="mw-heading mw-heading4"><h4 id="Jumbograms">Jumbograms</h4>[<a href="/w/index.php?title=IPv6&action=edit&section=12" title="Edit section: Jumbograms">edit</a>]</div> IPv4 limits packets to 65,535 (216−1) octets of payload. An IPv6 node can optionally handle packets over this limit, referred to as <a href="/wiki/Jumbogram" title="Jumbogram">jumbograms</a>, which can be as large as 4,294,967,295 (232−1) octets. The use of jumbograms may improve performance over high-<a href="/wiki/Maximum_transmission_unit" title="Maximum transmission unit">MTU</a> links. The use of jumbograms is indicated by the Jumbo Payload Option extension header.<a href="#cite_note-rfc2675-33">[33]</a> <div class="mw-heading mw-heading2"><h2 id="IPv6_packets">IPv6 packets</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=13" title="Edit section: IPv6 packets">edit</a>]</div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="/wiki/IPv6_packet" title="IPv6 packet">IPv6 packet</a></div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:Ipv6_header.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/a/ab/Ipv6_header.svg/220px-Ipv6_header.svg.png" decoding="async" width="220" height="172" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/a/ab/Ipv6_header.svg/330px-Ipv6_header.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/a/ab/Ipv6_header.svg/440px-Ipv6_header.svg.png 2x" data-file-width="803" data-file-height="628" /></a><figcaption>IPv6 packet header</figcaption></figure> An IPv6 packet has two parts: a <a href="/wiki/Header_(computing)" title="Header (computing)">header</a> and <a href="/wiki/Payload_(computing)" title="Payload (computing)">payload</a>. The header consists of a fixed portion with minimal functionality required for all packets and may be followed by optional extensions to implement special features. The fixed header occupies the first 40 <a href="/wiki/Octet_(computing)" title="Octet (computing)">octets</a> (320 bits) of the IPv6 packet. It contains the source and destination addresses, traffic class, hop count, and the type of the optional extension or payload which follows the header. This Next Header field tells the receiver how to interpret the data which follows the header. If the packet contains options, this field contains the option type of the next option. The "Next Header" field of the last option points to the upper-layer protocol that is carried in the packet's <a href="/wiki/Payload_(computing)" title="Payload (computing)">payload</a>. The current use of the IPv6 Traffic Class field divides this between a 6 bit <a href="/wiki/Differentiated_Services_Code_Point" class="mw-redirect" title="Differentiated Services Code Point">Differentiated Services Code Point</a><a href="#cite_note-rfc2474-34">[34]</a> and a 2-bit <a href="/wiki/Explicit_Congestion_Notification" title="Explicit Congestion Notification">Explicit Congestion Notification</a> field.<a href="#cite_note-rfc3168-35">[35]</a> Extension headers carry options that are used for special treatment of a packet in the network, e.g., for routing, fragmentation, and for security using the <a href="/wiki/IPsec" title="IPsec">IPsec</a> framework. Without special options, a payload must be less than 64kB. With a Jumbo Payload option (in a Hop-By-Hop Options extension header), the payload must be less than 4 GB. Unlike with IPv4, routers never fragment a packet. Hosts are expected to use <a href="/wiki/Path_MTU_Discovery" title="Path MTU Discovery">Path MTU Discovery</a> to make their packets small enough to reach the destination without needing to be fragmented. See <a href="/wiki/IPv6_packet#Fragmentation" title="IPv6 packet">IPv6 packet fragmentation</a>. <div class="mw-heading mw-heading2"><h2 id="Addressing">Addressing</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=14" title="Edit section: Addressing">edit</a>]</div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="/wiki/IPv6_address" title="IPv6 address">IPv6 address</a></div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv6_address_stracture-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/6/6d/IPv6_address_stracture-en.svg/220px-IPv6_address_stracture-en.svg.png" decoding="async" width="220" height="43" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/6/6d/IPv6_address_stracture-en.svg/330px-IPv6_address_stracture-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/6/6d/IPv6_address_stracture-en.svg/440px-IPv6_address_stracture-en.svg.png 2x" data-file-width="646" data-file-height="126" /></a><figcaption>A general structure for an IPv6 unicast address</figcaption></figure> <a href="/wiki/IPv6_address" title="IPv6 address">IPv6 addresses</a> have 128 bits. The design of the IPv6 address space implements a different design philosophy than in IPv4, in which subnetting was used to improve the efficiency of utilization of the small address space. In IPv6, the address space is deemed large enough for the foreseeable future, and a local area subnet always uses 64 bits for the host portion of the address, designated as the interface identifier, while the most-significant 64 bits are used as the routing prefix.<a href="#cite_note-rfc4291-36">[36]</a>: 9  While the myth has existed regarding IPv6 subnets being impossible to scan, RFC 7707 notes that patterns resulting from some IPv6 address configuration techniques and algorithms allow address scanning in many real-world scenarios. <div class="mw-heading mw-heading3"><h3 id="Address_representation">Address representation</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=15" title="Edit section: Address representation">edit</a>]</div> The 128 bits of an IPv6 address are represented in 8 groups of 16 bits each. Each group is written as four hexadecimal digits (sometimes called <a href="/wiki/Hextet" title="Hextet">hextets</a><a href="#cite_note-Graziani2012-37">[37]</a><a href="#cite_note-Coffeen2014-38">[38]</a> or more formally <a href="/wiki/Hexadectet" class="mw-redirect" title="Hexadectet">hexadectets</a><a href="#cite_note-Horley2013-39">[39]</a> and informally a quibble or quad-nibble<a href="#cite_note-Horley2013-39">[39]</a>) and the groups are separated by colons (:). An example of this representation is 2001:0db8:0000:0000:0000:ff00:0042:8329. For convenience and clarity, the representation of an IPv6 address may be shortened with the following rules: <ul><li>One or more <a href="/wiki/Leading_zero" title="Leading zero">leading zeros</a> from any group of hexadecimal digits are removed, which is usually done to all of the leading zeros. For example, the group 0042 is converted to 42. The group 0000 is converted to 0.</li> <li>Consecutive sections of zeros are replaced with two colons (::). This may only be used once in an address, as multiple use would render the address indeterminate. A double colon should not be used to denote an omitted single section of zeros.<a href="#cite_note-rfc5952-40">[40]</a>: §4.2.2 </li></ul> An example of application of these rules: <dl><dd>Initial address: 2001:0db8:0000:0000:0000:ff00:0042:8329.</dd> <dd>After removing all leading zeros in each group: 2001:db8:0:0:0:ff00:42:8329.</dd> <dd>After omitting consecutive sections of zeros: 2001:db8::ff00:42:8329.</dd></dl> The loopback address is defined as 0000:0000:0000:0000:0000:0000:0000:0001<a href="#cite_note-rfc5156-41">[41]</a> and is abbreviated to ::1 by using both rules. As an IPv6 address may have more than one representation, the IETF has issued a <a href="/wiki/IPv6_address#Representation" title="IPv6 address">proposed standard for representing them in text</a>.<a href="#cite_note-rfc5952-40">[40]</a> Because IPv6 addresses contain colons, and URLs use colons to separate the host from the port number, an IPv6 address used as the host-part of a URL should be enclosed in square brackets,<a href="#cite_note-rfc3986-42">[42]</a> e.g. http://[2001:db8:4006:812::200e] or http://[2001:db8:4006:812::200e]:8080/path/page.html. <div class="mw-heading mw-heading3"><h3 id="Link-local_address">Link-local address</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=16" title="Edit section: Link-local address">edit</a>]</div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv6_link_local_unicast_address_structure-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/f/f4/IPv6_link_local_unicast_address_structure-en.svg/220px-IPv6_link_local_unicast_address_structure-en.svg.png" decoding="async" width="220" height="25" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/f/f4/IPv6_link_local_unicast_address_structure-en.svg/330px-IPv6_link_local_unicast_address_structure-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/f/f4/IPv6_link_local_unicast_address_structure-en.svg/440px-IPv6_link_local_unicast_address_structure-en.svg.png 2x" data-file-width="683" data-file-height="79" /></a><figcaption>The Link-Local Unicast Address structure in IPv6</figcaption></figure> All interfaces of IPv6 hosts require a <a href="/wiki/Link-local_address" title="Link-local address">link-local address</a>, which have the prefix fe80::/10. This prefix is followed by 54 bits that can be used for subnetting, although they are typically set to zeros, and a 64-bit interface identifier. The host can compute and assign the Interface identifier by itself without the presence or cooperation of an external network component like a DHCP server, in a process called link-local address autoconfiguration.[<a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a>] The lower 64 bits of the link-local address (the suffix) were originally derived from the MAC address of the underlying network interface card. As this method of assigning addresses would cause undesirable address changes when faulty network cards were replaced, and as it also suffered from a number of security and privacy issues, <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8064">8064</a> has replaced the original MAC-based method with the hash-based method specified in <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc7217">7217</a>.[<a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a>] <div class="mw-heading mw-heading3"><h3 id="Address_uniqueness_and_router_solicitation">Address uniqueness and router solicitation</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=17" title="Edit section: Address uniqueness and router solicitation">edit</a>]</div> IPv6 uses a new mechanism for mapping IP addresses to link-layer addresses (e.g. <a href="/wiki/MAC_address" title="MAC address">MAC addresses</a>), because it does not support the <a href="/wiki/Broadcasting_(networking)" title="Broadcasting (networking)">broadcast</a> addressing method, on which the functionality of the <a href="/wiki/Address_Resolution_Protocol" title="Address Resolution Protocol">Address Resolution Protocol</a> (ARP) in IPv4 is based. IPv6 implements the <a href="/wiki/Neighbor_Discovery_Protocol" title="Neighbor Discovery Protocol">Neighbor Discovery Protocol</a> (NDP, ND) in the <a href="/wiki/Link_layer" title="Link layer">link layer</a>, which relies on <a href="/wiki/ICMPv6" title="ICMPv6">ICMPv6</a> and <a href="/wiki/Multicast" title="Multicast">multicast</a> transmission.<a href="#cite_note-Rosen_kernel_networking-5">[5]</a>: 210  IPv6 hosts verify the uniqueness of their IPv6 addresses in a <a href="/wiki/Local_area_network" title="Local area network">local area network</a> (LAN) by sending a neighbor solicitation message asking for the link-layer address of the IP address. If any other host in the LAN is using that address, it responds.<a href="#cite_note-T._Narten_pp._54-43">[43]</a> A host bringing up a new IPv6 interface first generates a unique link-local address using one of several mechanisms designed to generate a unique address. Should a non-unique address be detected, the host can try again with a newly generated address. Once a unique link-local address is established, the IPv6 host determines whether the LAN is connected on this link to any <a href="/wiki/Router_(computing)" title="Router (computing)">router</a> interface that supports IPv6. It does so by sending out an ICMPv6 router solicitation message to the all-routers<a href="#cite_note-rfc4861sec637-44">[44]</a> multicast group with its link-local address as source. If there is no answer after a predetermined number of attempts, the host concludes that no routers are connected. If it does get a response, known as a router advertisement, from a router, the response includes the network configuration information to allow establishment of a globally unique address with an appropriate unicast network prefix.<a href="#cite_note-rfc4862sec551-45">[45]</a> There are also two flag bits that tell the host whether it should use DHCP to get further information and addresses: <ul><li>The Manage bit, which indicates whether or not the host should use DHCP to obtain additional addresses rather than rely on an auto-configured address from the router advertisement.</li> <li>The Other bit, which indicates whether or not the host should obtain other information through DHCP. The other information consists of one or more prefix information options for the subnets that the host is attached to, a lifetime for the prefix, and two flags:<a href="#cite_note-T._Narten_pp._54-43">[43]</a> <ul><li>On-link: If this flag is set, the host will treat all addresses on the specific subnet as being on-link and send packets directly to them instead of sending them to a router for the duration of the given lifetime.</li> <li>Address: This flag tells the host to actually create a global address.</li></ul></li></ul> <div class="mw-heading mw-heading3"><h3 id="Global_addressing">Global addressing</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=18" title="Edit section: Global addressing">edit</a>]</div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv6_global_unicast_address_stracture-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/2/27/IPv6_global_unicast_address_stracture-en.svg/220px-IPv6_global_unicast_address_stracture-en.svg.png" decoding="async" width="220" height="26" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/2/27/IPv6_global_unicast_address_stracture-en.svg/330px-IPv6_global_unicast_address_stracture-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/2/27/IPv6_global_unicast_address_stracture-en.svg/440px-IPv6_global_unicast_address_stracture-en.svg.png 2x" data-file-width="643" data-file-height="76" /></a><figcaption>The global unicast address structure in IPv6</figcaption></figure> The assignment procedure for global addresses is similar to local-address construction. The prefix is supplied from router advertisements on the network. Multiple prefix announcements cause multiple addresses to be configured.<a href="#cite_note-T._Narten_pp._54-43">[43]</a> Stateless address autoconfiguration (SLAAC) requires a /64 address block.<a href="#cite_note-rfc4291-36">[36]</a> <a href="/wiki/Local_Internet_registry" class="mw-redirect" title="Local Internet registry">Local Internet registries</a> are assigned at least /32 blocks, which they divide among subordinate networks.<a href="#cite_note-46">[46]</a> The initial recommendation of September 2001 stated assignment of a /48 subnet to end-consumer sites.<a href="#cite_note-rfc3177-47">[47]</a> In March 2011 this recommendation was refined:<a href="#cite_note-rfc6177-48">[48]</a> The <a href="/wiki/IETF" class="mw-redirect" title="IETF">IETF</a> "recommends giving home sites significantly more than a single /64, but does not recommend that every home site be given a /48 either". Blocks of /56s are specifically considered. It remains to be seen whether ISPs will honor this recommendation. For example, during initial trials, <a href="/wiki/Comcast" title="Comcast">Comcast</a> customers were given a single /64 network.<a href="#cite_note-49">[49]</a> <div class="mw-heading mw-heading2"><h2 id="IPv6_in_the_Domain_Name_System">IPv6 in the Domain Name System</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=19" title="Edit section: IPv6 in the Domain Name System">edit</a>]</div> In the <a href="/wiki/Domain_Name_System" title="Domain Name System">Domain Name System</a> (DNS), <a href="/wiki/Hostname" title="Hostname">hostnames</a> are mapped to IPv6 addresses by <a href="/wiki/AAAA_record" class="mw-redirect" title="AAAA record">AAAA</a> ("quad-A") resource records. For <a href="/wiki/Reverse_DNS_lookup" title="Reverse DNS lookup">reverse resolution</a>, the IETF reserved the domain <a href="/wiki/.arpa" title=".arpa">ip6.arpa</a>, where the name space is hierarchically divided by the 1-digit <a href="/wiki/Hexadecimal" title="Hexadecimal">hexadecimal</a> representation of <a href="/wiki/Nibble" title="Nibble">nibble</a> units (4 bits) of the IPv6 address. This scheme is defined in <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3596">3596</a>. When a dual-stack host queries a DNS server to resolve a <a href="/wiki/Fully_qualified_domain_name" title="Fully qualified domain name">fully qualified domain name</a> (FQDN), the DNS client of the host sends two DNS requests, one querying A records and the other querying AAAA records. The host operating system may be configured with a preference for address selection rules <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6724">6724</a>.<a href="#cite_note-50">[50]</a> An alternative record type was used in early DNS implementations for IPv6, designed to facilitate network renumbering, the A6 records for the forward lookup and a number of other innovations such as bit-string labels and <a href="/wiki/CNAME_record#DNAME_record" title="CNAME record">DNAME</a> records. It is defined in <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2874">2874</a> and its references (with further discussion of the pros and cons of both schemes in <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3364">3364</a>), but has been deprecated to experimental status (<link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3363">3363</a>). <div class="mw-heading mw-heading2"><h2 id="Transition_mechanisms">Transition mechanisms</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=20" title="Edit section: Transition mechanisms">edit</a>]</div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="/wiki/IPv6_transition_mechanism" title="IPv6 transition mechanism">IPv6 transition mechanism</a></div> IPv6 is not foreseen to supplant IPv4 instantaneously. Both protocols will continue to operate simultaneously for some time. Therefore, <a href="/wiki/IPv6_transition_mechanism" title="IPv6 transition mechanism">IPv6 transition mechanisms</a> are needed to enable IPv6 hosts to reach IPv4 services and to allow isolated IPv6 hosts and networks to reach each other over IPv4 infrastructure.<a href="#cite_note-sixxs-51">[51]</a> According to <a href="/wiki/Silvia_Hagen" title="Silvia Hagen">Silvia Hagen</a>, a dual-stack implementation of the IPv4 and IPv6 on devices is the easiest way to migrate to IPv6.<a href="#cite_note-52">[52]</a> Many other transition mechanisms use tunneling to encapsulate IPv6 traffic within IPv4 networks and vice versa. This is an imperfect solution, which reduces the <a href="/wiki/Maximum_transmission_unit" title="Maximum transmission unit">maximum transmission unit</a> (MTU) of a link and therefore complicates <a href="/wiki/Path_MTU_Discovery" title="Path MTU Discovery">Path MTU Discovery</a>, and may increase <a href="/wiki/Network_latency" class="mw-redirect" title="Network latency">latency</a>.<a href="#cite_note-53">[53]</a><a href="#cite_note-54">[54]</a> <div class="mw-heading mw-heading3"><h3 id="Dual-stack_IP_implementation">Dual-stack IP implementation</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=21" title="Edit section: Dual-stack IP implementation">edit</a>]</div> Dual-stack IP implementations provide complete IPv4 and IPv6 protocol stacks in the operating system of a <a href="/wiki/Computer" title="Computer">computer</a> or <a href="/wiki/Network_device" class="mw-redirect" title="Network device">network device</a> on top of the common <a href="/wiki/Physical_layer" title="Physical layer">physical layer</a> implementation, such as <a href="/wiki/Ethernet" title="Ethernet">Ethernet</a>. This permits dual-stack hosts to participate in IPv6 and IPv4 networks simultaneously.<a href="#cite_note-rfc4213-55">[55]</a> A device with dual-stack implementation in the operating system has an IPv4 and IPv6 address, and can communicate with other nodes in the LAN or the Internet using either IPv4 or IPv6. The DNS protocol is used by both IP protocols to resolve fully qualified domain names and IP addresses, but dual stack requires that the resolving DNS server can resolve both types of addresses. Such a dual-stack DNS server holds IPv4 addresses in the A records and IPv6 addresses in the AAAA records. Depending on the destination that is to be resolved, a DNS name server may return an IPv4 or IPv6 IP address, or both. A default address selection mechanism, or preferred protocol, needs to be configured either on hosts or the DNS server. The <a href="/wiki/IETF" class="mw-redirect" title="IETF">IETF</a> has published <a href="/wiki/Happy_Eyeballs" title="Happy Eyeballs">Happy Eyeballs</a> to assist dual-stack applications, so that they can connect using both IPv4 and IPv6, but prefer an IPv6 connection if it is available. However, dual-stack also needs to be implemented on all routers between the host and the service for which the DNS server has returned an IPv6 address. Dual-stack clients should be configured to prefer IPv6 only if the network is able to forward IPv6 packets using the IPv6 versions of <a href="/wiki/Routing_protocols" class="mw-redirect" title="Routing protocols">routing protocols</a>. When dual-stack network protocols are in place the <a href="/wiki/Application_layer" title="Application layer">application layer</a> can be migrated to IPv6.<a href="#cite_note-56">[56]</a> While dual-stack is supported by major <a href="/wiki/Operating_system" title="Operating system">operating system</a> and network device vendors, legacy networking hardware and servers do not support IPv6. <div class="mw-heading mw-heading3"><h3 id="ISP_customers_with_public-facing_IPv6">ISP customers with public-facing IPv6</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=22" title="Edit section: ISP customers with public-facing IPv6">edit</a>]</div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv6_Prefix_Assignment_Example-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/2/27/IPv6_Prefix_Assignment_Example-en.svg/260px-IPv6_Prefix_Assignment_Example-en.svg.png" decoding="async" width="260" height="91" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/2/27/IPv6_Prefix_Assignment_Example-en.svg/390px-IPv6_Prefix_Assignment_Example-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/2/27/IPv6_Prefix_Assignment_Example-en.svg/520px-IPv6_Prefix_Assignment_Example-en.svg.png 2x" data-file-width="695" data-file-height="242" /></a><figcaption>IPv6 Prefix Assignment mechanism with IANA, RIRs, and ISPs</figcaption></figure> <a href="/wiki/Internet_service_providers" class="mw-redirect" title="Internet service providers">Internet service providers</a> (ISPs) are increasingly providing their business and private customers with public-facing IPv6 global unicast addresses. If IPv4 is still used in the local area network (LAN), however, and the ISP can only provide one public-facing IPv6 address, the IPv4 LAN addresses are translated into the public facing IPv6 address using <a href="/wiki/NAT64" title="NAT64">NAT64</a>, a <a href="/wiki/Network_address_translation" title="Network address translation">network address translation</a> (NAT) mechanism. Some ISPs cannot provide their customers with public-facing IPv4 and IPv6 addresses, thus supporting dual-stack networking, because some ISPs have exhausted their globally routable IPv4 address pool. Meanwhile, ISP customers are still trying to reach IPv4 <a href="/wiki/Web_servers" class="mw-redirect" title="Web servers">web servers</a> and other destinations.<a href="#cite_note-57">[57]</a> A significant percentage of ISPs in all <a href="/wiki/Regional_Internet_registry" title="Regional Internet registry">regional Internet registry</a> (RIR) zones have obtained IPv6 address space. This includes many of the world's major ISPs and <a href="/wiki/Mobile_network" class="mw-redirect" title="Mobile network">mobile network</a> operators, such as <a href="/wiki/Verizon_Wireless" class="mw-redirect" title="Verizon Wireless">Verizon Wireless</a>, <a href="/wiki/StarHub_TV" title="StarHub TV">StarHub Cable</a>, <a href="/wiki/Chubu_Electric_Power" title="Chubu Electric Power">Chubu Telecommunications</a>, <a href="/wiki/Kabel_Deutschland" class="mw-redirect" title="Kabel Deutschland">Kabel Deutschland</a>, <a href="/wiki/Swisscom" title="Swisscom">Swisscom</a>, <a href="/wiki/T-Mobile_International_AG" class="mw-redirect" title="T-Mobile International AG">T-Mobile</a>, <a href="/wiki/Internode_(ISP)" title="Internode (ISP)">Internode</a> and <a href="/wiki/Telef%C3%B3nica" title="Telefónica">Telefónica</a>.<a href="#cite_note-58">[58]</a> While some ISPs still allocate customers only IPv4 addresses, many ISPs allocate their customers only an IPv6 or dual-stack IPv4 and IPv6. ISPs report the share of IPv6 traffic from customers over their network to be anything between 20% and 40%, but by mid-2017 IPv6 traffic still only accounted for a fraction of total traffic at several large <a href="/wiki/Internet_exchange_point" title="Internet exchange point">Internet exchange points</a> (IXPs). <a href="/wiki/AMS-IX" class="mw-redirect" title="AMS-IX">AMS-IX</a> reported it to be 2% and <a href="/wiki/SeattleIX" class="mw-redirect" title="SeattleIX">SeattleIX</a> reported 7%. A 2017 survey found that many DSL customers that were served by a dual stack ISP did not request DNS servers to resolve fully qualified domain names into IPv6 addresses. The survey also found that the majority of traffic from IPv6-ready web-server resources were still requested and served over IPv4, mostly due to ISP customers that did not use the dual stack facility provided by their ISP and to a lesser extent due to customers of IPv4-only ISPs.<a href="#cite_note-59">[59]</a> <div class="mw-heading mw-heading3"><h3 id="Tunneling">Tunneling</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=23" title="Edit section: Tunneling">edit</a>]</div> The technical basis for tunneling, or encapsulating IPv6 packets in IPv4 packets, is outlined in RFC 4213. When the Internet backbone was IPv4-only, one of the frequently used tunneling protocols was <a href="/wiki/6to4" title="6to4">6to4</a>.<a href="#cite_note-Steven_J._Vaughan-Nichols-60">[60]</a> <a href="/wiki/Teredo_tunneling" title="Teredo tunneling">Teredo tunneling</a> was also frequently used for integrating IPv6 LANs with the IPv4 Internet backbone. Teredo is outlined in RFC 4380 and allows IPv6 <a href="/wiki/Local_area_networks" class="mw-redirect" title="Local area networks">local area networks</a> to tunnel over IPv4 networks, by encapsulating IPv6 packets within UDP. The Teredo relay is an IPv6 router that mediates between a Teredo server and the native IPv6 network. It was expected that 6to4 and Teredo would be widely deployed until ISP networks would switch to native IPv6, but by 2014 Google Statistics showed that the use of both mechanisms had dropped to almost 0.<a href="#cite_note-61">[61]</a> <div class="mw-heading mw-heading3"><h3 id="IPv4-mapped_IPv6_addresses">IPv4-mapped IPv6 addresses</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=24" title="Edit section: IPv4-mapped IPv6 addresses">edit</a>]</div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv6_IPv4-Compatible_address_structure-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/2/2b/IPv6_IPv4-Compatible_address_structure-en.svg/220px-IPv6_IPv4-Compatible_address_structure-en.svg.png" decoding="async" width="220" height="25" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/2/2b/IPv6_IPv4-Compatible_address_structure-en.svg/330px-IPv6_IPv4-Compatible_address_structure-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/2/2b/IPv6_IPv4-Compatible_address_structure-en.svg/440px-IPv6_IPv4-Compatible_address_structure-en.svg.png 2x" data-file-width="644" data-file-height="74" /></a><figcaption>IPv4-compatible IPv6 unicast address</figcaption></figure> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv6_IPv4-Mapped_address_structure-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/5/55/IPv6_IPv4-Mapped_address_structure-en.svg/220px-IPv6_IPv4-Mapped_address_structure-en.svg.png" decoding="async" width="220" height="25" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/5/55/IPv6_IPv4-Mapped_address_structure-en.svg/330px-IPv6_IPv4-Mapped_address_structure-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/5/55/IPv6_IPv4-Mapped_address_structure-en.svg/440px-IPv6_IPv4-Mapped_address_structure-en.svg.png 2x" data-file-width="644" data-file-height="74" /></a><figcaption>IPv4-mapped IPv6 unicast address</figcaption></figure> Hybrid dual-stack IPv6/IPv4 implementations recognize a special class of addresses, the IPv4-mapped IPv6 addresses.<a href="#cite_note-rfc6890-62">[62]</a>: §2.2.3 <a href="#cite_note-rfc4291-36">[36]</a> These addresses are typically written with a 96-bit prefix in the standard IPv6 format, and the remaining 32 bits are written in the customary <a href="/wiki/Dot-decimal_notation" title="Dot-decimal notation">dot-decimal notation</a> of IPv4. Addresses in this group consist of an 80-bit prefix of zeros, the next 16 bits are ones, and the remaining, least-significant 32 bits contain the IPv4 address. For example, ::ffff:192.0.2.128 represents the IPv4 address 192.0.2.128. A previous format, called "IPv4-compatible IPv6 address", was ::192.0.2.128; however, this method is deprecated.<a href="#cite_note-rfc4291-36">[36]</a> Because of the significant internal differences between IPv4 and IPv6 protocol stacks, some of the lower-level functionality available to programmers in the IPv6 stack does not work the same when used with IPv4-mapped addresses. Some common IPv6 stacks do not implement the IPv4-mapped address feature, either because the IPv6 and IPv4 stacks are separate implementations (e.g., <a href="/wiki/Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a> 2000, XP, and Server 2003), or because of security concerns (<a href="/wiki/OpenBSD" title="OpenBSD">OpenBSD</a>).<a href="#cite_note-openbsd-mapped-addr-63">[63]</a> On these operating systems, a program must open a separate socket for each IP protocol it uses. On some systems, e.g., the <a href="/wiki/Linux_kernel" title="Linux kernel">Linux kernel</a>, <a href="/wiki/NetBSD" title="NetBSD">NetBSD</a>, and <a href="/wiki/FreeBSD" title="FreeBSD">FreeBSD</a>, this feature is controlled by the socket option IPV6_V6ONLY.<a href="#cite_note-rfc3493-64">[64]</a>: 22  The address prefix 64:ff9b::/96 is a class of IPv4-embedded IPv6 addresses for use in <a href="/wiki/NAT64" title="NAT64">NAT64</a> transition methods.<a href="#cite_note-rfc6052-65">[65]</a> For example, 64:ff9b::192.0.2.128 represents the IPv4 address 192.0.2.128. <div class="mw-heading mw-heading2"><h2 id="Security">Security</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=25" title="Edit section: Security">edit</a>]</div> A number of security implications may arise from the use of IPv6. Some of them may be related with the IPv6 protocols themselves, while others may be related with implementation flaws.<a href="#cite_note-66">[66]</a><a href="#cite_note-67">[67]</a> <div class="mw-heading mw-heading3"><h3 id="Shadow_networks">Shadow networks</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=26" title="Edit section: Shadow networks">edit</a>]</div> The addition of nodes having IPv6 enabled by default by the software manufacturer may result in the inadvertent creation of shadow networks, causing IPv6 traffic flowing into networks having only IPv4 security management in place. This may also occur with operating system upgrades, when the newer operating system enables IPv6 by default, while the older one did not. Failing to update the security infrastructure to accommodate IPv6 can lead to IPv6 traffic bypassing it.<a href="#cite_note-68">[68]</a> Shadow networks have occurred on business networks in which enterprises are replacing <a href="/wiki/Windows_XP" title="Windows XP">Windows XP</a> systems that do not have an IPv6 stack enabled by default, with <a href="/wiki/Windows_7" title="Windows 7">Windows 7</a> systems, that do.<a href="#cite_note-69">[69]</a> Some IPv6 stack implementors have therefore recommended disabling IPv4 mapped addresses and instead using a dual-stack network where supporting both IPv4 and IPv6 is necessary.<a href="#cite_note-70">[70]</a> <div class="mw-heading mw-heading3"><h3 id="IPv6_packet_fragmentation">IPv6 packet fragmentation</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=27" title="Edit section: IPv6 packet fragmentation">edit</a>]</div> Research has shown that the use of fragmentation can be leveraged to evade network security controls, similar to IPv4. As a result, <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc7112">7112</a> requires that the first fragment of an IPv6 packet contains the entire IPv6 header chain, such that some very pathological fragmentation cases are forbidden. Additionally, as a result of research on the evasion of RA-Guard in <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc7113">7113</a>, <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6980">6980</a> has deprecated the use of fragmentation with Neighbor Discovery, and discouraged the use of fragmentation with Secure Neighbor Discovery (SEND). <div class="mw-heading mw-heading2"><h2 id="Standardization_through_RFCs">Standardization through RFCs</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=28" title="Edit section: Standardization through RFCs">edit</a>]</div> <div class="mw-heading mw-heading3"><h3 id="Working-group_proposals">Working-group proposals</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=29" title="Edit section: Working-group proposals">edit</a>]</div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:IPv6_timeline-en.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/7/76/IPv6_timeline-en.svg/220px-IPv6_timeline-en.svg.png" decoding="async" width="220" height="82" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/7/76/IPv6_timeline-en.svg/330px-IPv6_timeline-en.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/7/76/IPv6_timeline-en.svg/440px-IPv6_timeline-en.svg.png 2x" data-file-width="861" data-file-height="322" /></a><figcaption>A timeline for the standards governing IPv6</figcaption></figure> Due to the anticipated global growth of the <a href="/wiki/Internet" title="Internet">Internet</a>, the <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF) in the early 1990s started an effort to develop a next generation IP protocol.<a href="#cite_note-Rosen_kernel_networking-5">[5]</a>: 209  By the beginning of 1992, several proposals appeared for an expanded Internet addressing system and by the end of 1992 the IETF announced a call for white papers.<a href="#cite_note-71">[71]</a> In September 1993, the IETF created a temporary, ad hoc IP Next Generation (IPng) area to deal specifically with such issues. The new area was led by <a href="/wiki/Allison_Mankin" title="Allison Mankin">Allison Mankin</a> and <a href="/wiki/Scott_Bradner" title="Scott Bradner">Scott Bradner</a>, and had a directorate with 15 engineers from diverse backgrounds for direction-setting and preliminary document review:<a href="#cite_note-rfc1752-7">[7]</a><a href="#cite_note-72">[72]</a> The working-group members were <a href="/wiki/J._Allard" class="mw-redirect" title="J. Allard">J. Allard</a> (Microsoft), <a href="/wiki/Steven_M._Bellovin" title="Steven M. Bellovin">Steve Bellovin</a> (AT&T), Jim Bound (Digital Equipment Corporation), Ross Callon (Wellfleet), <a href="/wiki/Brian_Carpenter_(Internet_engineer)" class="mw-redirect" title="Brian Carpenter (Internet engineer)">Brian Carpenter</a> (CERN), <a href="/wiki/David_D._Clark" title="David D. Clark">Dave Clark</a> (MIT), <a href="/wiki/John_Curran_(businessman)" title="John Curran (businessman)">John Curran</a> (NEARNET), <a href="/wiki/Steve_Deering" title="Steve Deering">Steve Deering</a> (Xerox), Dino Farinacci (Cisco), Paul Francis (NTT), Eric Fleischmann (Boeing), Mark Knopper (Ameritech), Greg Minshall (Novell), Rob Ullmann (Lotus), and <a href="/wiki/Lixia_Zhang" title="Lixia Zhang">Lixia Zhang</a> (Xerox).<a href="#cite_note-73">[73]</a> The Internet Engineering Task Force adopted the IPng model on 25 July 1994, with the formation of several IPng working groups.<a href="#cite_note-rfc1752-7">[7]</a> By 1996, a series of <a href="/wiki/Request_for_Comments" title="Request for Comments">RFCs</a> was released defining Internet Protocol version 6 (IPv6), starting with <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1883">1883</a>. (Version 5 was used by the experimental <a href="/wiki/Internet_Stream_Protocol" title="Internet Stream Protocol">Internet Stream Protocol</a>.) <div class="mw-heading mw-heading3"><h3 id="RFC_standardization">RFC standardization</h3>[<a href="/w/index.php?title=IPv6&action=edit&section=30" title="Edit section: RFC standardization">edit</a>]</div> The first RFC to standardize IPv6 was the <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1883">1883</a> in 1995,<a href="#cite_note-74">[74]</a> which became obsoleted by <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2460">2460</a> in 1998.<a href="#cite_note-Rosen_kernel_networking-5">[5]</a>: 209  In July 2017 this RFC was superseded by <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8200">8200</a>, which elevated IPv6 to "Internet Standard" (the highest maturity level for IETF protocols).<a href="#cite_note-rfc8200-3">[3]</a> <div class="mw-heading mw-heading2"><h2 id="Deployment">Deployment</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=31" title="Edit section: Deployment">edit</a>]</div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="/wiki/IPv6_deployment" title="IPv6 deployment">IPv6 deployment</a></div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:Rir-ipv6-allocation-rate.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Rir-ipv6-allocation-rate.svg/220px-Rir-ipv6-allocation-rate.svg.png" decoding="async" width="220" height="176" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Rir-ipv6-allocation-rate.svg/330px-Rir-ipv6-allocation-rate.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Rir-ipv6-allocation-rate.svg/440px-Rir-ipv6-allocation-rate.svg.png 2x" data-file-width="600" data-file-height="480" /></a><figcaption>Monthly IPv6 allocations per <a href="/wiki/Regional_Internet_registry" title="Regional Internet registry">regional Internet registry</a> (RIR)</figcaption></figure> The 1993 introduction of <a href="/wiki/Classless_Inter-Domain_Routing" title="Classless Inter-Domain Routing">Classless Inter-Domain Routing</a> (CIDR) in the routing and IP address allocation for the Internet, and the extensive use of <a href="/wiki/Network_address_translation" title="Network address translation">network address translation</a> (NAT), delayed <a href="/wiki/IPv4_address_exhaustion" title="IPv4 address exhaustion">IPv4 address exhaustion</a> to allow for IPv6 deployment, which began in the mid-2000s. Universities were among the early adopters of IPv6. <a href="/wiki/Virginia_Tech" title="Virginia Tech">Virginia Tech</a> deployed IPv6 at a trial location in 2004 and later expanded IPv6 deployment across the <a href="/wiki/Campus_network" title="Campus network">campus network</a>. By 2016, 82% of the traffic on their network used IPv6. <a href="/wiki/Imperial_College_London" title="Imperial College London">Imperial College London</a> began experimental IPv6 deployment in 2003 and by 2016 the IPv6 traffic on their networks averaged between 20% and 40%. A significant portion of this IPv6 traffic was generated through their <a href="/wiki/High_energy_physics" class="mw-redirect" title="High energy physics">high energy physics</a> collaboration with <a href="/wiki/CERN" title="CERN">CERN</a>, which relies entirely on IPv6.<a href="#cite_note-75">[75]</a> The <a href="/wiki/Domain_Name_System" title="Domain Name System">Domain Name System</a> (DNS) has supported IPv6 since 2008. In the same year, IPv6 was first used in a major world event during the Beijing <a href="/wiki/2008_Summer_Olympics" title="2008 Summer Olympics">2008 Summer Olympics</a>.<a href="#cite_note-beijing2008-pressrelease-76">[76]</a><a href="#cite_note-77">[77]</a> By 2011, all major operating systems in use on personal computers and server systems had production-quality IPv6 implementations. Cellular telephone systems presented a large deployment field for Internet Protocol devices as mobile telephone service made the transition from <a href="/wiki/3G" title="3G">3G</a> to <a href="/wiki/4G" title="4G">4G</a> technologies, in which voice is provisioned as a <a href="/wiki/Voice_over_IP" title="Voice over IP">voice over IP</a> (VoIP) service that would leverage IPv6 enhancements. In 2009, the US cellular operator <a href="/wiki/Verizon_Communications" class="mw-redirect" title="Verizon Communications">Verizon</a> released technical specifications for devices to operate on its "next-generation" networks.<a href="#cite_note-verizon-78">[78]</a> The specification mandated IPv6 operation according to the 3GPP Release 8 Specifications (March 2009), and deprecated IPv4 as an optional capability.<a href="#cite_note-verizon-78">[78]</a> The deployment of IPv6 in the <a href="/wiki/Internet_backbone" title="Internet backbone">Internet backbone</a> continued. In 2018 only 25.3% of the about 54,000 autonomous systems advertised both IPv4 and IPv6 prefixes in the global <a href="/wiki/Border_Gateway_Protocol" title="Border Gateway Protocol">Border Gateway Protocol</a> (BGP) routing database. A further 243 networks advertised only an IPv6 prefix. Internet backbone transit networks offering IPv6 support existed in every country globally, except in parts of <a href="/wiki/Africa" title="Africa">Africa</a>, the <a href="/wiki/Middle_East" title="Middle East">Middle East</a> and China.<a href="#cite_note-IS_2018-79">[79]</a>: 6  By mid-2018 some major European <a href="/wiki/Broadband" title="Broadband">broadband</a> ISPs had deployed IPv6 for the majority of their customers. <a href="/wiki/Sky_UK" title="Sky UK">Sky UK</a> provided over 86% of its customers with IPv6, <a href="/wiki/Deutsche_Telekom" title="Deutsche Telekom">Deutsche Telekom</a> had 56% deployment of IPv6, <a href="/wiki/XS4ALL" title="XS4ALL">XS4ALL</a> in the Netherlands had 73% deployment and in Belgium the broadband ISPs <a href="/wiki/VOO" title="VOO">VOO</a> and <a href="/wiki/Telenet" title="Telenet">Telenet</a> had 73% and 63% IPv6 deployment respectively.<a href="#cite_note-IS_2018-79">[79]</a>: 7  In the United States the broadband ISP <a href="/wiki/Xfinity" title="Xfinity">Xfinity</a> had an IPv6 deployment of about 66%. In 2018 Xfinity reported an estimated 36.1 million IPv6 users, while <a href="/wiki/AT%26T" title="AT&T">AT&T</a> reported 22.3 million IPv6 users.<a href="#cite_note-IS_2018-79">[79]</a>: 7–8  <div class="mw-heading mw-heading2"><h2 id="Peering_issues">Peering issues</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=32" title="Edit section: Peering issues">edit</a>]</div> There is a peering dispute going on between <a href="/wiki/Hurricane_Electric" title="Hurricane Electric">Hurricane Electric</a> and <a href="/wiki/Cogent_Communications" title="Cogent Communications">Cogent Communications</a> on IPv6, with the two network providers refusing to peer.<a href="#cite_note-80">[80]</a> <div class="mw-heading mw-heading2"><h2 id="See_also">See also</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=33" title="Edit section: See also">edit</a>]</div> <style data-mw-deduplicate="TemplateStyles:r1259569809">.mw-parser-output .portalbox{padding:0;margin:0.5em 0;display:table;box-sizing:border-box;max-width:175px;list-style:none}.mw-parser-output .portalborder{border:1px solid var(--border-color-base,#a2a9b1);padding:0.1em;background:var(--background-color-neutral-subtle,#f8f9fa)}.mw-parser-output .portalbox-entry{display:table-row;font-size:85%;line-height:110%;height:1.9em;font-style:italic;font-weight:bold}.mw-parser-output .portalbox-image{display:table-cell;padding:0.2em;vertical-align:middle;text-align:center}.mw-parser-output .portalbox-link{display:table-cell;padding:0.2em 0.2em 0.2em 0.3em;vertical-align:middle}@media(min-width:720px){.mw-parser-output .portalleft{clear:left;float:left;margin:0.5em 1em 0.5em 0}.mw-parser-output .portalright{clear:right;float:right;margin:0.5em 0 0.5em 1em}}</style><ul role="navigation" aria-label="Portals" class="noprint portalbox portalborder portalright"> <li class="portalbox-entry"><a href="/wiki/File:Crystal_Clear_app_linneighborhood.svg" class="mw-file-description"><img alt="icon" src="//upload.wikimedia.org/wikipedia/commons/thumb/f/f9/Crystal_Clear_app_linneighborhood.svg/28px-Crystal_Clear_app_linneighborhood.svg.png" decoding="async" width="28" height="28" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/f/f9/Crystal_Clear_app_linneighborhood.svg/42px-Crystal_Clear_app_linneighborhood.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/f/f9/Crystal_Clear_app_linneighborhood.svg/56px-Crystal_Clear_app_linneighborhood.svg.png 2x" data-file-width="407" data-file-height="407" /></a><a href="/wiki/Portal:Internet" title="Portal:Internet">Internet portal</a></li></ul> <ul><li><a href="/wiki/China_Next_Generation_Internet" title="China Next Generation Internet">China Next Generation Internet</a></li> <li><a href="/wiki/Comparison_of_IPv6_support_in_operating_systems" title="Comparison of IPv6 support in operating systems">Comparison of IPv6 support in operating systems</a></li> <li><a href="/wiki/Comparison_of_IPv6_support_in_common_applications" title="Comparison of IPv6 support in common applications">Comparison of IPv6 support in common applications</a></li> <li><a href="/wiki/DoD_IPv6_product_certification" title="DoD IPv6 product certification">DoD IPv6 product certification</a></li> <li><a href="/wiki/OCCAID" title="OCCAID">OCCAID</a></li> <li><a href="/wiki/University_of_New_Hampshire_InterOperability_Laboratory" title="University of New Hampshire InterOperability Laboratory">University of New Hampshire InterOperability Laboratory</a></li></ul> <div class="mw-heading mw-heading2"><h2 id="References">References</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=34" title="Edit section: References">edit</a>]</div> <style data-mw-deduplicate="TemplateStyles:r1239543626">.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}</style><div class="reflist"> <div class="mw-references-wrap mw-references-columns"><ol class="references"> <li id="cite_note-ipv6nz-1"><a href="#cite_ref-ipv6nz_1-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20190129005124/http://www.ipv6.org.nz/ipv6-faqs/">"FAQs"</a>. New Zealand IPv6 Task Force. Archived from <a rel="nofollow" class="external text" href="https://www.ipv6.org.nz/ipv6-faqs/">the original</a> on 29 January 2019. Retrieved 26 October 2015.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=FAQs&rft.pub=New+Zealand+IPv6+Task+Force&rft_id=https%3A%2F%2Fwww.ipv6.org.nz%2Fipv6-faqs%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc2460-2">^ <a href="#cite_ref-rfc2460_2-0">a</a> <a href="#cite_ref-rfc2460_2-1">b</a> <a href="#cite_ref-rfc2460_2-2">c</a> <a href="#cite_ref-rfc2460_2-3">d</a> <a href="#cite_ref-rfc2460_2-4">e</a> <a href="#cite_ref-rfc2460_2-5">f</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFS._DeeringR._Hinden1998" class="citation cs2"><a href="/wiki/Steve_Deering" title="Steve Deering">S. Deering</a>; <a href="/w/index.php?title=Bob_Hinden&action=edit&redlink=1" class="new" title="Bob Hinden (page does not exist)">R. Hinden</a> (December 1998), Internet Protocol, Version 6 (IPv6) Specification, <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF), <a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc2460">2460</a></cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Internet+Protocol%2C+Version+6+%28IPv6%29+Specification&rft.pub=Internet+Engineering+Task+Force+%28IETF%29&rft.date=1998-12&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc2460%23id-name%3DRFC&rft.au=S.+Deering&rft.au=R.+Hinden&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Obsoletes RFC 1883. </li> <li id="cite_note-rfc8200-3">^ <a href="#cite_ref-rfc8200_3-0">a</a> <a href="#cite_ref-rfc8200_3-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFS._DeeringR._Hinden2017" class="citation cs2"><a href="/wiki/Steve_Deering" title="Steve Deering">S. Deering</a>; <a href="/w/index.php?title=Bob_Hinden&action=edit&redlink=1" class="new" title="Bob Hinden (page does not exist)">R. Hinden</a> (July 2017), "Internet Protocol, Version 6 (IPv6) Specification", IETF Request for Comments (RFC) Pages – Test, <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF), <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2070-1721">2070-1721</a>, <a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc8200">8200</a></cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=IETF+Request+for+Comments+%28RFC%29+Pages+%E2%80%93+Test&rft.atitle=Internet+Protocol%2C+Version+6+%28IPv6%29+Specification&rft.date=2017-07&rft.issn=2070-1721&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc8200%23id-name%3DRFC&rft.au=S.+Deering&rft.au=R.+Hinden&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Obsoletes RFC 2460. </li> <li id="cite_note-4"><a href="#cite_ref-4">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSiddiqui2017" class="citation web cs1">Siddiqui, Aftab (17 July 2017). <a rel="nofollow" class="external text" href="https://www.internetsociety.org/blog/2017/07/rfc-8200-ipv6-has-been-standardized/">"RFC 8200 – IPv6 Has Been Standardized"</a>. <a href="/wiki/Internet_Society" title="Internet Society">Internet Society</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20231023162212/https://www.internetsociety.org/blog/2017/07/rfc-8200-ipv6-has-been-standardized/">Archived</a> from the original on 23 October 2023. Retrieved 25 February 2018.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=RFC+8200+%E2%80%93+IPv6+Has+Been+Standardized&rft.pub=Internet+Society&rft.date=2017-07-17&rft.aulast=Siddiqui&rft.aufirst=Aftab&rft_id=https%3A%2F%2Fwww.internetsociety.org%2Fblog%2F2017%2F07%2Frfc-8200-ipv6-has-been-standardized%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-Rosen_kernel_networking-5">^ <a href="#cite_ref-Rosen_kernel_networking_5-0">a</a> <a href="#cite_ref-Rosen_kernel_networking_5-1">b</a> <a href="#cite_ref-Rosen_kernel_networking_5-2">c</a> <a href="#cite_ref-Rosen_kernel_networking_5-3">d</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFRosen2014" class="citation book cs1">Rosen, Rami (2014). Linux Kernel Networking: Implementation and Theory. New York: Apress. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/9781430261971" title="Special:BookSources/9781430261971"><bdi>9781430261971</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/869747983">869747983</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Linux+Kernel+Networking%3A+Implementation+and+Theory&rft.place=New+York&rft.pub=Apress&rft.date=2014&rft_id=info%3Aoclcnum%2F869747983&rft.isbn=9781430261971&rft.aulast=Rosen&rft.aufirst=Rami&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-6"><a href="#cite_ref-6">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation audio-visual cs1"><a rel="nofollow" class="external text" href="https://www.youtube.com/watch?v=mZo69JQoLb8">Google IPv6 Conference 2008: What will the IPv6 Internet look like?</a>. Event occurs at 13:35. <a rel="nofollow" class="external text" href="https://ghostarchive.org/varchive/youtube/20211211/mZo69JQoLb8">Archived</a> from the original on 11 December 2021.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Google+IPv6+Conference+2008%3A+What+will+the+IPv6+Internet+look+like%3F&rft_id=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DmZo69JQoLb8&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc1752-7">^ <a href="#cite_ref-rfc1752_7-0">a</a> <a href="#cite_ref-rfc1752_7-1">b</a> <a href="#cite_ref-rfc1752_7-2">c</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBradnerMankin1995" class="citation cs1">Bradner, S.; Mankin, A. (January 1995). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1752">The Recommendation for the IP Next Generation Protocol</a>. <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">IETF</a>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1752">10.17487/RFC1752</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1752">1752</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=The+Recommendation+for+the+IP+Next+Generation+Protocol&rft.pub=IETF&rft.date=1995-01&rft_id=info%3Adoi%2F10.17487%2FRFC1752&rft.aulast=Bradner&rft.aufirst=S.&rft.au=Mankin%2C+A.&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc1752&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-8"><a href="#cite_ref-8">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.nro.net/ipv4-free-pool-depleted">"Free Pool of IPv4 Address Space Depleted"</a>. NRO.net. <a href="/wiki/Montevideo" title="Montevideo">Montevideo</a>: The Number Resource Organization. 3 February 2011. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20240118044214/https://www.nro.net/ipv4-free-pool-depleted">Archived</a> from the original on 18 January 2024. Retrieved 19 January 2022.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=NRO.net&rft.atitle=Free+Pool+of+IPv4+Address+Space+Depleted&rft.date=2011-02-03&rft_id=https%3A%2F%2Fwww.nro.net%2Fipv4-free-pool-depleted&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-9"><a href="#cite_ref-9">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFRashid2011" class="citation web cs1">Rashid, Fahmida (1 February 2011). <a rel="nofollow" class="external text" href="https://www.eweek.com/networking/ipv4-address-exhaustion-not-instant-cause-for-concern-with-ipv6-in-wings/">"IPv4 Address Exhaustion Not Instant Cause for Concern with IPv6 in Wings"</a>. eWeek. <a rel="nofollow" class="external text" href="https://archive.today/20240120181901/https://www.eweek.com/networking/ipv4-address-exhaustion-not-instant-cause-for-concern-with-ipv6-in-wings/">Archived</a> from the original on 20 January 2024. Retrieved 23 June 2012.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=IPv4+Address+Exhaustion+Not+Instant+Cause+for+Concern+with+IPv6+in+Wings&rft.pub=eWeek&rft.date=2011-02-01&rft.aulast=Rashid&rft.aufirst=Fahmida&rft_id=https%3A%2F%2Fwww.eweek.com%2Fnetworking%2Fipv4-address-exhaustion-not-instant-cause-for-concern-with-ipv6-in-wings%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-10"><a href="#cite_ref-10">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFWard2012" class="citation news cs1">Ward, Mark (14 September 2012). <a rel="nofollow" class="external text" href="https://www.bbc.co.uk/news/technology-19600718">"Europe hits old internet address limits"</a>. <a href="/wiki/BBC_News" title="BBC News">BBC News</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20231105171900/https://www.bbc.com/news/technology-19600718">Archived</a> from the original on 5 November 2023. Retrieved 15 September 2012.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=BBC+News&rft.atitle=Europe+hits+old+internet+address+limits&rft.date=2012-09-14&rft.aulast=Ward&rft.aufirst=Mark&rft_id=https%3A%2F%2Fwww.bbc.co.uk%2Fnews%2Ftechnology-19600718&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-11"><a href="#cite_ref-11">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFHuston" class="citation web cs1">Huston, Geoff. <a rel="nofollow" class="external text" href="https://www.potaroo.net/tools/ipv4/">"IPV4 Address Report"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20240110052921/https://www.potaroo.net/tools/ipv4/">Archived</a> from the original on 10 January 2024.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=IPV4+Address+Report&rft.aulast=Huston&rft.aufirst=Geoff&rft_id=https%3A%2F%2Fwww.potaroo.net%2Ftools%2Fipv4%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-12"><a href="#cite_ref-12">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://my.afrinic.net/help/policies/afpol-v4200407-000.htm">"FAQ"</a>. my.afrinic.net. <a href="/wiki/AFRINIC" title="AFRINIC">AFRINIC</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20231023065714/https://my.afrinic.net/help/policies/afpol-v4200407-000.htm">Archived</a> from the original on 23 October 2023. Retrieved 28 November 2018.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=my.afrinic.net&rft.atitle=FAQ&rft_id=https%3A%2F%2Fmy.afrinic.net%2Fhelp%2Fpolicies%2Fafpol-v4200407-000.htm&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-13"><a href="#cite_ref-13">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation pressrelease cs1"><a rel="nofollow" class="external text" href="https://www.ripe.net/publications/news/about-ripe-ncc-and-ripe/the-ripe-ncc-has-run-out-of-ipv4-addresses">"The RIPE NCC has run out of IPv4 Addresses"</a> (Press release). <a href="/wiki/RIPE_NCC" title="RIPE NCC">RIPE NCC</a>. 25 November 2019. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20240119220002/https://www.ripe.net/publications/news/the-ripe-ncc-has-run-out-of-ipv4-addresses/">Archived</a> from the original on 19 January 2024. Retrieved 26 November 2019.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=The+RIPE+NCC+has+run+out+of+IPv4+Addresses&rft.pub=RIPE+NCC&rft.date=2019-11-25&rft_id=https%3A%2F%2Fwww.ripe.net%2Fpublications%2Fnews%2Fabout-ripe-ncc-and-ripe%2Fthe-ripe-ncc-has-run-out-of-ipv4-addresses&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc1726-14">^ <a href="#cite_ref-rfc1726_14-0">a</a> <a href="#cite_ref-rfc1726_14-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFPartridgeKastenholz1994" class="citation web cs1">Partridge, C.; Kastenholz, F. (December 1994). <a rel="nofollow" class="external text" href="https://www.ietf.org/rfc/rfc1726.txt">"Technical Criteria for Choosing IP The Next Generation (IPng)"</a>. <a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc1726">1726</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Technical+Criteria+for+Choosing+IP+The+Next+Generation+%28IPng%29&rft.date=1994-12&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc1726%23id-name%3DRFC&rft.aulast=Partridge&rft.aufirst=C.&rft.au=Kastenholz%2C+F.&rft_id=https%3A%2F%2Fwww.ietf.org%2Frfc%2Frfc1726.txt&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc1112-15"><a href="#cite_ref-rfc1112_15-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1112">1112</a>, Host extensions for IP multicasting, S. Deering (August 1989) </li> <li id="cite_note-rfc3956-16"><a href="#cite_ref-rfc3956_16-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3956">3956</a>, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address, P. Savola, B. Haberman (November 2004) </li> <li id="cite_note-17"><a href="#cite_ref-17">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2908">2908</a>, The Internet Multicast Address Allocation Architecture, D. Thaler, M. Handley, D. Estrin (September 2000) </li> <li id="cite_note-18"><a href="#cite_ref-18">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3306">3306</a>, Unicast-Prefix-based IPv6 Multicast Addresses, B. Haberman, D. Thaler (August 2002) </li> <li id="cite_note-rfc4862-19">^ <a href="#cite_ref-rfc4862_19-0">a</a> <a href="#cite_ref-rfc4862_19-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFS._ThomsonT._NartenT._Jinmei2007" class="citation cs1">S. Thomson; T. Narten; T. Jinmei (September 2007). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4862">IPv6 Stateless Address Autoconfiguration</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC4862">10.17487/RFC4862</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4862">4862</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Stateless+Address+Autoconfiguration&rft.pub=Network+Working+Group&rft.date=2007-09&rft_id=info%3Adoi%2F10.17487%2FRFC4862&rft.au=S.+Thomson&rft.au=T.+Narten&rft.au=T.+Jinmei&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc4862&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Draft Standard. Obsoletes <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2462">2462</a>. Updated by <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc7527">7527</a>. </li> <li id="cite_note-rfc2894-20"><a href="#cite_ref-rfc2894_20-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFM._Crawford2000" class="citation cs1">M. Crawford (August 2000). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2894">Router Renumbering for IPv6</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC2894">10.17487/RFC2894</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2894">2894</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Router+Renumbering+for+IPv6&rft.pub=Network+Working+Group&rft.date=2000-08&rft_id=info%3Adoi%2F10.17487%2FRFC2894&rft.au=M.+Crawford&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc2894&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Proposed Standard. </li> <li id="cite_note-21"><a href="#cite_ref-21">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFT._NartenR._DravesS._Krishnan2007" class="citation web cs1">T. Narten; R. Draves; S. Krishnan (September 2007). <a rel="nofollow" class="external text" href="https://www.internetsociety.org/resources/deploy360/2014/privacy-extensions-for-ipv6-slaac/">"Privacy Extensions for Stateless Address Autoconfiguration in IPv6"</a>. www.ietf.org. Retrieved 13 March 2017.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=www.ietf.org&rft.atitle=Privacy+Extensions+for+Stateless+Address+Autoconfiguration+in+IPv6&rft.date=2007-09&rft.au=T.+Narten&rft.au=R.+Draves&rft.au=S.+Krishnan&rft_id=https%3A%2F%2Fwww.internetsociety.org%2Fresources%2Fdeploy360%2F2014%2Fprivacy-extensions-for-ipv6-slaac%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc8981-22"><a href="#cite_ref-rfc8981_22-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFF._GontS._KrishnanT._NartenR._Draves2021" class="citation cs1">F. Gont; S. Krishnan; T. Narten; R. Draves (February 2021). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8981">Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6</a>. <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC8981">10.17487/RFC8981</a>. <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2070-1721">2070-1721</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8981">8981</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Temporary+Address+Extensions+for+Stateless+Address+Autoconfiguration+in+IPv6&rft.pub=Internet+Engineering+Task+Force&rft.date=2021-02&rft_id=info%3Adoi%2F10.17487%2FRFC8981&rft.issn=2070-1721&rft.au=F.+Gont&rft.au=S.+Krishnan&rft.au=T.+Narten&rft.au=R.+Draves&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc8981&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Proposed Standard. Obsoletes <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4941">4941</a>. </li> <li id="cite_note-23"><a href="#cite_ref-23">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20170907013704/https://support.microsoft.com/en-us/help/817778/overview-of-the-advanced-networking-pack-for-windows-xp">"Overview of the Advanced Networking Pack for Windows XP"</a>. <a href="/wiki/Microsoft" title="Microsoft">Microsoft</a>. Archived from <a rel="nofollow" class="external text" href="http://support.microsoft.com/kb/817778">the original</a> on 7 September 2017. Retrieved 15 April 2019.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Overview+of+the+Advanced+Networking+Pack+for+Windows+XP&rft.pub=Microsoft&rft_id=http%3A%2F%2Fsupport.microsoft.com%2Fkb%2F817778&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-24"><a href="#cite_ref-24">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.internetsociety.org/resources/deploy360/2014/privacy-extensions-for-ipv6-slaac">"Privacy Extensions for IPv6 SLAAC"</a>. <a href="/wiki/Internet_Society" title="Internet Society">Internet Society</a>. 8 August 2014. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20231023063407/https://www.internetsociety.org/resources/deploy360/2014/privacy-extensions-for-ipv6-slaac/">Archived</a> from the original on 23 October 2023. Retrieved 17 January 2020.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Privacy+Extensions+for+IPv6+SLAAC&rft.pub=Internet+Society&rft.date=2014-08-08&rft_id=https%3A%2F%2Fwww.internetsociety.org%2Fresources%2Fdeploy360%2F2014%2Fprivacy-extensions-for-ipv6-slaac&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc2071-25"><a href="#cite_ref-rfc2071_25-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFP._FergusonH._Berkowitz1997" class="citation cs1">P. Ferguson; H. Berkowitz (January 1997). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2071">Network Renumbering Overview: Why would I want it and what is it anyway?</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC2071">10.17487/RFC2071</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2071">2071</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Network+Renumbering+Overview%3A+Why+would+I+want+it+and+what+is+it+anyway%3F&rft.pub=Network+Working+Group&rft.date=1997-01&rft_id=info%3Adoi%2F10.17487%2FRFC2071&rft.au=P.+Ferguson&rft.au=H.+Berkowitz&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc2071&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Informational. </li> <li id="cite_note-26"><a href="#cite_ref-26">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFFergusonBerkowitz1997" class="citation web cs1">Ferguson, P.; Berkowitz, H. (January 1997). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2071">"Network Renumbering Overview: Why would I want it and what is it anyway?"</a>. <a href="/wiki/IETF" class="mw-redirect" title="IETF">IETF</a>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC2071">10.17487/RFC2071</a>. <a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc2071">2071</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20240107145323/https://datatracker.ietf.org/doc/html/rfc2071">Archived</a> from the original on 7 January 2024.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Network+Renumbering+Overview%3A+Why+would+I+want+it+and+what+is+it+anyway%3F&rft.pub=IETF&rft.date=1997-01&rft_id=info%3Adoi%2F10.17487%2FRFC2071&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc2071%23id-name%3DRFC&rft.aulast=Ferguson&rft.aufirst=P.&rft.au=Berkowitz%2C+H.&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc2071&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-27"><a href="#cite_ref-27">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBerkowitz1997" class="citation web cs1">Berkowitz, H. (January 1997). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2072">"Router Renumbering Guide"</a>. <a href="/wiki/IETF" class="mw-redirect" title="IETF">IETF</a>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC2072">10.17487/RFC2072</a>. <a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc2072">2072</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20230608094931/https://datatracker.ietf.org/doc/html/rfc2072">Archived</a> from the original on 8 June 2023.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Router+Renumbering+Guide&rft.pub=IETF&rft.date=1997-01&rft_id=info%3Adoi%2F10.17487%2FRFC2072&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc2072%23id-name%3DRFC&rft.aulast=Berkowitz&rft.aufirst=H.&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc2072&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-28"><a href="#cite_ref-28">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFCooperGontThaler" class="citation cs1">Cooper, Alissa; Gont, Fernando; Thaler, Dave. <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8064">Recommendation on Stable IPv6 Interface Identifiers</a>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC8064">10.17487/RFC8064</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8064">8064</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Recommendation+on+Stable+IPv6+Interface+Identifiers&rft_id=info%3Adoi%2F10.17487%2FRFC8064&rft.aulast=Cooper&rft.aufirst=Alissa&rft.au=Gont%2C+Fernando&rft.au=Thaler%2C+Dave&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc8064&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-29"><a href="#cite_ref-29">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSilvia_Hagen2014" class="citation book cs1">Silvia Hagen (2014). IPv6 Essentials: Integrating IPv6 into Your IPv4 Network (3rd ed.). Sebastopol, CA: O'Reilly Media. p. 196. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/978-1-4493-3526-7" title="Special:BookSources/978-1-4493-3526-7"><bdi>978-1-4493-3526-7</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/881832733">881832733</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Essentials%3A+Integrating+IPv6+into+Your+IPv4+Network&rft.place=Sebastopol%2C+CA&rft.pages=196&rft.edition=3rd&rft.pub=O%27Reilly+Media&rft.date=2014&rft_id=info%3Aoclcnum%2F881832733&rft.isbn=978-1-4493-3526-7&rft.au=Silvia+Hagen&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-30"><a href="#cite_ref-30">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFZack2013" class="citation web cs1">Zack, E. (July 2013). <a rel="nofollow" class="external text" href="http://www.ipv6hackers.org/meetings/ipv6-hackers-1">"IPv6 Security Assessment and Benchmarking"</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=IPv6+Security+Assessment+and+Benchmarking&rft.date=2013-07&rft.aulast=Zack&rft.aufirst=E.&rft_id=http%3A%2F%2Fwww.ipv6hackers.org%2Fmeetings%2Fipv6-hackers-1&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-draft-gont-v6ops-ipv6-ehs-packet-drops-03-31"><a href="#cite_ref-draft-gont-v6ops-ipv6-ehs-packet-drops-03_31-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFGont2016" class="citation web cs1">Gont, F. (March 2016). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/draft-gont-v6ops-ipv6-ehs-packet-drops-03">"Operational Implications of IPv6 Packets with Extension Headers"</a>. <a href="/wiki/IETF" class="mw-redirect" title="IETF">IETF</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20231027170015/https://datatracker.ietf.org/doc/html/draft-gont-v6ops-ipv6-ehs-packet-drops-03">Archived</a> from the original on 27 October 2023.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Operational+Implications+of+IPv6+Packets+with+Extension+Headers&rft.pub=IETF&rft.date=2016-03&rft.aulast=Gont&rft.aufirst=F.&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-gont-v6ops-ipv6-ehs-packet-drops-03&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc3963-32"><a href="#cite_ref-rfc3963_32-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFV._DevarapalliR._WakikawaA._PetrescuP._Thubert2005" class="citation cs1">V. Devarapalli; R. Wakikawa; A. Petrescu; P. Thubert (January 2005). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3963">Network Mobility (NEMO) Basic Support Protocol</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC3963">10.17487/RFC3963</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3963">3963</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Network+Mobility+%28NEMO%29+Basic+Support+Protocol&rft.pub=Network+Working+Group&rft.date=2005-01&rft_id=info%3Adoi%2F10.17487%2FRFC3963&rft.au=V.+Devarapalli&rft.au=R.+Wakikawa&rft.au=A.+Petrescu&rft.au=P.+Thubert&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc3963&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Proposed Standard. </li> <li id="cite_note-rfc2675-33"><a href="#cite_ref-rfc2675_33-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFD._BormanS._DeeringR._Hinden1999" class="citation cs1">D. Borman; <a href="/wiki/Steve_Deering" title="Steve Deering">S. Deering</a>; R. Hinden (August 1999). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2675">IPv6 Jumbograms</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC2675">10.17487/RFC2675</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2675">2675</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Jumbograms&rft.pub=Network+Working+Group&rft.date=1999-08&rft_id=info%3Adoi%2F10.17487%2FRFC2675&rft.au=D.+Borman&rft.au=S.+Deering&rft.au=R.+Hinden&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc2675&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Proposed Standard. Obsoletes <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2147">2147</a>. </li> <li id="cite_note-rfc2474-34"><a href="#cite_ref-rfc2474_34-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFK._NicholsS._BlakeF._BakerD._Black1998" class="citation cs1">K. Nichols; S. Blake; <a href="/wiki/Fred_Baker_(IETF_chair)" class="mw-redirect" title="Fred Baker (IETF chair)">F. Baker</a>; D. Black (December 1998). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2474">Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC2474">10.17487/RFC2474</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2474">2474</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Definition+of+the+Differentiated+Services+Field+%28DS+Field%29+in+the+IPv4+and+IPv6+Headers&rft.pub=Network+Working+Group&rft.date=1998-12&rft_id=info%3Adoi%2F10.17487%2FRFC2474&rft.au=K.+Nichols&rft.au=S.+Blake&rft.au=F.+Baker&rft.au=D.+Black&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc2474&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Proposed Standard. Obsoletes <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1455">1455</a> and <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1349">1349</a>. Updated by <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3168">3168</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3260">3260</a> and <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8436">8436</a>. </li> <li id="cite_note-rfc3168-35"><a href="#cite_ref-rfc3168_35-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFK._RamakrishnanS._FloydD._Black2001" class="citation cs1">K. Ramakrishnan; S. Floyd; D. Black (September 2001). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3168">The Addition of Explicit Congestion Notification (ECN) to IP</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC3168">10.17487/RFC3168</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3168">3168</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=The+Addition+of+Explicit+Congestion+Notification+%28ECN%29+to+IP&rft.pub=Network+Working+Group&rft.date=2001-09&rft_id=info%3Adoi%2F10.17487%2FRFC3168&rft.au=K.+Ramakrishnan&rft.au=S.+Floyd&rft.au=D.+Black&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc3168&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Proposed Standard. Obsoletes <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2481">2481</a>. Updates <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2474">2474</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2401">2401</a> and <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc793">793</a>. Updated by <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4301">4301</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6040">6040</a> and <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8311">8311</a>. </li> <li id="cite_note-rfc4291-36">^ <a href="#cite_ref-rfc4291_36-0">a</a> <a href="#cite_ref-rfc4291_36-1">b</a> <a href="#cite_ref-rfc4291_36-2">c</a> <a href="#cite_ref-rfc4291_36-3">d</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFR._HindenS._Deering2006" class="citation cs1">R. Hinden; <a href="/wiki/Steve_Deering" title="Steve Deering">S. Deering</a> (February 2006). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4291">IP Version 6 Addressing Architecture</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC4291">10.17487/RFC4291</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4291">4291</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IP+Version+6+Addressing+Architecture&rft.pub=Network+Working+Group&rft.date=2006-02&rft_id=info%3Adoi%2F10.17487%2FRFC4291&rft.au=R.+Hinden&rft.au=S.+Deering&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc4291&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Draft Standard. Obsoletes <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3513">3513</a>. Updated by <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5952">5952</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6052">6052</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc7136">7136</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc7346">7346</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc7371">7371</a> and <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8064">8064</a>. </li> <li id="cite_note-Graziani2012-37"><a href="#cite_ref-Graziani2012_37-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFGraziani2012" class="citation book cs1">Graziani, Rick (2012). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=FbYjJjZNA5gC&pg=PA55">IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6</a>. <a href="/wiki/Cisco_Press" title="Cisco Press">Cisco Press</a>. p. 55. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/978-0-13-303347-2" title="Special:BookSources/978-0-13-303347-2"><bdi>978-0-13-303347-2</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Fundamentals%3A+A+Straightforward+Approach+to+Understanding+IPv6&rft.pages=55&rft.pub=Cisco+Press&rft.date=2012&rft.isbn=978-0-13-303347-2&rft.aulast=Graziani&rft.aufirst=Rick&rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3DFbYjJjZNA5gC%26pg%3DPA55&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-Coffeen2014-38"><a href="#cite_ref-Coffeen2014_38-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFCoffeen2014" class="citation book cs1">Coffeen, Tom (2014). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=dZU8BQAAQBAJ&pg=PT170">IPv6 Address Planning: Designing an Address Plan for the Future</a>. <a href="/wiki/O%27Reilly_Media" title="O'Reilly Media">O'Reilly Media</a>. p. 170. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/978-1-4919-0326-1" title="Special:BookSources/978-1-4919-0326-1"><bdi>978-1-4919-0326-1</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Address+Planning%3A+Designing+an+Address+Plan+for+the+Future&rft.pages=170&rft.pub=O%27Reilly+Media&rft.date=2014&rft.isbn=978-1-4919-0326-1&rft.aulast=Coffeen&rft.aufirst=Tom&rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3DdZU8BQAAQBAJ%26pg%3DPT170&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-Horley2013-39">^ <a href="#cite_ref-Horley2013_39-0">a</a> <a href="#cite_ref-Horley2013_39-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFHorley2013" class="citation book cs1">Horley, Edward (2013). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=u50QAwAAQBAJ&q=17&pg=PA17">Practical IPv6 for Windows Administrators</a>. <a href="/wiki/Apress" class="mw-redirect" title="Apress">Apress</a>. p. 17. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/978-1-4302-6371-5" title="Special:BookSources/978-1-4302-6371-5"><bdi>978-1-4302-6371-5</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Practical+IPv6+for+Windows+Administrators&rft.pages=17&rft.pub=Apress&rft.date=2013&rft.isbn=978-1-4302-6371-5&rft.aulast=Horley&rft.aufirst=Edward&rft_id=https%3A%2F%2Fbooks.google.com%2Fbooks%3Fid%3Du50QAwAAQBAJ%26q%3D17%26pg%3DPA17&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc5952-40">^ <a href="#cite_ref-rfc5952_40-0">a</a> <a href="#cite_ref-rfc5952_40-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFS._KawamuraM._Kawashima2010" class="citation cs1">S. Kawamura; M. Kawashima (August 2010). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5952">A Recommendation for IPv6 Address Text Representation</a>. <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC5952">10.17487/RFC5952</a>. <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2070-1721">2070-1721</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5952">5952</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=A+Recommendation+for+IPv6+Address+Text+Representation&rft.pub=Internet+Engineering+Task+Force&rft.date=2010-08&rft_id=info%3Adoi%2F10.17487%2FRFC5952&rft.issn=2070-1721&rft.au=S.+Kawamura&rft.au=M.+Kawashima&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc5952&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Proposed Standard. Updates <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4291">4291</a>. </li> <li id="cite_note-rfc5156-41"><a href="#cite_ref-rfc5156_41-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFM._Blanchet2008" class="citation cs1">M. Blanchet (April 2008). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5156">Special-Use IPv6 Addresses</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC5156">10.17487/RFC5156</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5156">5156</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Special-Use+IPv6+Addresses&rft.pub=Network+Working+Group&rft.date=2008-04&rft_id=info%3Adoi%2F10.17487%2FRFC5156&rft.au=M.+Blanchet&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc5156&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Proposed Standard. Obsoleted by <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6890">6890</a>. </li> <li id="cite_note-rfc3986-42"><a href="#cite_ref-rfc3986_42-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFT._Berners-LeeR._FieldingL._Masinter2005" class="citation cs1"><a href="/wiki/Tim_Berners-Lee" title="Tim Berners-Lee">T. Berners-Lee</a>; <a href="/wiki/Roy_Fielding" title="Roy Fielding">R. Fielding</a>; <a href="/wiki/Larry_Masinter" title="Larry Masinter">L. Masinter</a> (January 2005). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC3986">10.17487/RFC3986</a>. STD 66. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3986">3986</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Uniform+Resource+Identifier+%28URI%29%3A+Generic+Syntax&rft.pub=Network+Working+Group&rft.date=2005-01&rft_id=info%3Adoi%2F10.17487%2FRFC3986&rft.au=T.+Berners-Lee&rft.au=R.+Fielding&rft.au=L.+Masinter&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc3986&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Internet Standard 66. Obsoletes <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2732">2732</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2396">2396</a> and <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1808">1808</a>. Updated by <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6874">6874</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc7320">7320</a> and <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8820">8820</a>. Updates <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1738">1738</a>. </li> <li id="cite_note-T._Narten_pp._54-43">^ <a href="#cite_ref-T._Narten_pp._54_43-0">a</a> <a href="#cite_ref-T._Narten_pp._54_43-1">b</a> <a href="#cite_ref-T._Narten_pp._54_43-2">c</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFNarten1999" class="citation journal cs1">Narten, T. (August 1999). "Neighbor discovery and stateless autoconfiguration in IPv6". IEEE Internet Computing. 3 (4): 54–62. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2F4236.780961">10.1109/4236.780961</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=IEEE+Internet+Computing&rft.atitle=Neighbor+discovery+and+stateless+autoconfiguration+in+IPv6&rft.volume=3&rft.issue=4&rft.pages=54-62&rft.date=1999-08&rft_id=info%3Adoi%2F10.1109%2F4236.780961&rft.aulast=Narten&rft.aufirst=T.&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc4861sec637-44"><a href="#cite_ref-rfc4861sec637_44-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFNarten2007" class="citation web cs1">Narten, T. (September 2007). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4861#section-6.3.7">"Neighbor Discovery for IP version 6 (IPv6)"</a>. <a href="/wiki/IETF" class="mw-redirect" title="IETF">IETF</a>. section 6.3.7. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC4861">10.17487/RFC4861</a>. <a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc4861">4861</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20240117035643/https://datatracker.ietf.org/doc/html/rfc4861#section-6.3.7">Archived</a> from the original on 17 January 2024.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Neighbor+Discovery+for+IP+version+6+%28IPv6%29&rft.pages=section+6.3.7&rft.pub=IETF&rft.date=2007-09&rft_id=info%3Adoi%2F10.17487%2FRFC4861&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc4861%23id-name%3DRFC&rft.aulast=Narten&rft.aufirst=T.&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc4861%23section-6.3.7&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc4862sec551-45"><a href="#cite_ref-rfc4862sec551_45-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFThomson2007" class="citation web cs1">Thomson, S. (September 2007). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4862#section-5.5.1">"IPv6 Stateless Address Autoconfiguration - Section 5.5.1"</a>. <a href="/wiki/IETF" class="mw-redirect" title="IETF">IETF</a>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC4862">10.17487/RFC4862</a>. <a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc4862">4862</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20240111084216/https://datatracker.ietf.org/doc/html/rfc4862#section-5.5.1">Archived</a> from the original on 11 January 2024.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=IPv6+Stateless+Address+Autoconfiguration+-+Section+5.5.1&rft.pub=IETF&rft.date=2007-09&rft_id=info%3Adoi%2F10.17487%2FRFC4862&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc4862%23id-name%3DRFC&rft.aulast=Thomson&rft.aufirst=S.&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc4862%23section-5.5.1&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-46"><a href="#cite_ref-46">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.ripe.net/publications/docs/ripe-512/">"IPv6 Address Allocation and Assignment Policy"</a>. <a href="/wiki/RIPE_NCC" title="RIPE NCC">RIPE NCC</a>. 8 February 2011. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20230603052402/https://www.ripe.net/publications/docs/ripe-512">Archived</a> from the original on 3 June 2023. Retrieved 27 March 2011.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=IPv6+Address+Allocation+and+Assignment+Policy&rft.pub=RIPE+NCC&rft.date=2011-02-08&rft_id=https%3A%2F%2Fwww.ripe.net%2Fpublications%2Fdocs%2Fripe-512%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc3177-47"><a href="#cite_ref-rfc3177_47-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFIABIESG2001" class="citation cs1"><a href="/wiki/Internet_Architecture_Board" title="Internet Architecture Board">IAB</a>; <a href="/wiki/Internet_Engineering_Steering_Group" class="mw-redirect" title="Internet Engineering Steering Group">IESG</a> (September 2001). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3177">IAB/IESG Recommendations on IPv6 Address Allocations to Sites</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC3177">10.17487/RFC3177</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3177">3177</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IAB%2FIESG+Recommendations+on+IPv6+Address+Allocations+to+Sites&rft.pub=Network+Working+Group&rft.date=2001-09&rft_id=info%3Adoi%2F10.17487%2FRFC3177&rft.au=IAB&rft.au=IESG&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc3177&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Obsolete. Obsoleted by <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6177">6177</a>. </li> <li id="cite_note-rfc6177-48"><a href="#cite_ref-rfc6177_48-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFT._NartenG._HustonL._Roberts2011" class="citation cs1">T. Narten; G. Huston; L. Roberts (March 2011). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6177">IPv6 Address Assignment to End Sites</a>. <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF). <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC6177">10.17487/RFC6177</a>. <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2070-1721">2070-1721</a>. BCP 157. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6177">6177</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Address+Assignment+to+End+Sites&rft.pub=Internet+Engineering+Task+Force+%28IETF%29&rft.date=2011-03&rft_id=info%3Adoi%2F10.17487%2FRFC6177&rft.issn=2070-1721&rft.au=T.+Narten&rft.au=G.+Huston&rft.au=L.+Roberts&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc6177&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Best Common Practice. Obsoletes <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3177">3177</a>. </li> <li id="cite_note-49"><a href="#cite_ref-49">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBrzozowski2011" class="citation pressrelease cs1">Brzozowski, John (31 January 2011). <a rel="nofollow" class="external text" href="https://corporate.comcast.com/comcast-voices/comcast-activates-first-users-with-ipv6-native-dual-stack-over-docsis">"Comcast Activates First Users With IPv6 Native Dual Stack Over DOCSIS"</a> (Press release). <a href="/wiki/Comcast" title="Comcast">Comcast</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20231023064638/https://corporate.comcast.com/comcast-voices/comcast-activates-first-users-with-ipv6-native-dual-stack-over-docsis">Archived</a> from the original on 23 October 2023. Retrieved 15 April 2019.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Comcast+Activates+First+Users+With+IPv6+Native+Dual+Stack+Over+DOCSIS&rft.pub=Comcast&rft.date=2011-01-31&rft.aulast=Brzozowski&rft.aufirst=John&rft_id=https%3A%2F%2Fcorporate.comcast.com%2Fcomcast-voices%2Fcomcast-activates-first-users-with-ipv6-native-dual-stack-over-docsis&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-50"><a href="#cite_ref-50">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSilvia_Hagen2014" class="citation book cs1">Silvia Hagen (2014). IPv6 Essentials: Integrating IPv6 into Your IPv4 Network. O'Reilly Media, Inc. p. 176. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/9781449335267" title="Special:BookSources/9781449335267"><bdi>9781449335267</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Essentials%3A+Integrating+IPv6+into+Your+IPv4+Network&rft.pages=176&rft.pub=O%27Reilly+Media%2C+Inc.&rft.date=2014&rft.isbn=9781449335267&rft.au=Silvia+Hagen&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-sixxs-51"><a href="#cite_ref-sixxs_51-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.sixxs.net/faq/connectivity/?faq=comparison">"IPv6 Transition Mechanism/Tunneling Comparison"</a>. Sixxs.net. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20231023064851/https://www.sixxs.net/faq/connectivity/?faq=comparison">Archived</a> from the original on 23 October 2023. Retrieved 20 January 2012.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=IPv6+Transition+Mechanism%2FTunneling+Comparison&rft.pub=Sixxs.net&rft_id=https%3A%2F%2Fwww.sixxs.net%2Ffaq%2Fconnectivity%2F%3Ffaq%3Dcomparison&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-52"><a href="#cite_ref-52">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSilvia_Hagen2014" class="citation book cs1">Silvia Hagen (2014). IPv6 Essentials: Integrating IPv6 into Your IPv4 Network. O'Reilly Media, Inc. pp. 222–223. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/9781449335267" title="Special:BookSources/9781449335267"><bdi>9781449335267</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Essentials%3A+Integrating+IPv6+into+Your+IPv4+Network&rft.pages=222-223&rft.pub=O%27Reilly+Media%2C+Inc.&rft.date=2014&rft.isbn=9781449335267&rft.au=Silvia+Hagen&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-53"><a href="#cite_ref-53">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFCarpenter2011" class="citation web cs1">Carpenter, B. (August 2011). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6343">"Advisory Guidelines for 6to4 Deployment"</a>. <a href="/wiki/IETF" class="mw-redirect" title="IETF">IETF</a>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC6343">10.17487/RFC6343</a>. <a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc6343">6343</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20230128112750/https://datatracker.ietf.org/doc/html/rfc6343">Archived</a> from the original on 28 January 2023. Retrieved 20 August 2012.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Advisory+Guidelines+for+6to4+Deployment&rft.pub=IETF&rft.date=2011-08&rft_id=info%3Adoi%2F10.17487%2FRFC6343&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc6343%23id-name%3DRFC&rft.aulast=Carpenter&rft.aufirst=B.&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc6343&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-54"><a href="#cite_ref-54">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.networkworld.com/article/813230/ipv6-dual-stack-where-you-can-tunnel-where-you-must.html">"IPv6: Dual stack where you can; tunnel where you must"</a>. networkworld.com. 5 September 2007. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20240120184843/https://www.networkworld.com/article/813230/ipv6-dual-stack-where-you-can-tunnel-where-you-must.html">Archived</a> from the original on 20 January 2024. Retrieved 27 November 2012.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=IPv6%3A+Dual+stack+where+you+can%3B+tunnel+where+you+must&rft.pub=networkworld.com&rft.date=2007-09-05&rft_id=https%3A%2F%2Fwww.networkworld.com%2Farticle%2F813230%2Fipv6-dual-stack-where-you-can-tunnel-where-you-must.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc4213-55"><a href="#cite_ref-rfc4213_55-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFE._NordmarkR._Gilligan2005" class="citation cs1">E. Nordmark; R. Gilligan (October 2005). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4213">Basic Transition Mechanisms for IPv6 Hosts and Routers</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC4213">10.17487/RFC4213</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4213">4213</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Basic+Transition+Mechanisms+for+IPv6+Hosts+and+Routers&rft.pub=Network+Working+Group&rft.date=2005-10&rft_id=info%3Adoi%2F10.17487%2FRFC4213&rft.au=E.+Nordmark&rft.au=R.+Gilligan&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc4213&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Proposed Standard. Obsoletes <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2893">2893</a>. </li> <li id="cite_note-56"><a href="#cite_ref-56">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSilvia_Hagen2014" class="citation book cs1">Silvia Hagen (2014). IPv6 Essentials: Integrating IPv6 into Your IPv4 Network. O'Reilly Media, Inc. p. 222. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/9781449335267" title="Special:BookSources/9781449335267"><bdi>9781449335267</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Essentials%3A+Integrating+IPv6+into+Your+IPv4+Network&rft.pages=222&rft.pub=O%27Reilly+Media%2C+Inc.&rft.date=2014&rft.isbn=9781449335267&rft.au=Silvia+Hagen&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-57"><a href="#cite_ref-57">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.juniper.net/documentation/en_US/junos/topics/concept/ipv6-dual-stack-understanding.html">"Understanding Dual Stacking of IPv4 and IPv6 Unicast Addresses"</a>. Juniper.net. Juniper Networks. 31 August 2017. Retrieved 19 January 2022.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=Juniper.net&rft.atitle=Understanding+Dual+Stacking+of+IPv4+and+IPv6+Unicast+Addresses&rft.date=2017-08-31&rft_id=https%3A%2F%2Fwww.juniper.net%2Fdocumentation%2Fen_US%2Fjunos%2Ftopics%2Fconcept%2Fipv6-dual-stack-understanding.html&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-58"><a href="#cite_ref-58">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20170112052541/https://www.nro.net/ipv6">"IPv6"</a>. NRO.net. Archived from <a rel="nofollow" class="external text" href="https://www.nro.net/ipv6/">the original</a> on 12 January 2017. Retrieved 13 March 2017.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=NRO.net&rft.atitle=IPv6&rft_id=https%3A%2F%2Fwww.nro.net%2Fipv6%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-59"><a href="#cite_ref-59">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFPujol2017" class="citation web cs1">Pujol, Enric (12 June 2017). <a rel="nofollow" class="external text" href="https://blog.apnic.net/2017/06/13/stops-ipv6-traffic-dual-stack-isp/">"What Stops IPv6 Traffic in a Dual-Stack ISP?"</a>. APNIC.net. <a href="/wiki/APNIC" title="APNIC">APNIC</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20230327133355/https://blog.apnic.net/2017/06/13/stops-ipv6-traffic-dual-stack-isp/">Archived</a> from the original on 27 March 2023. Retrieved 13 June 2017.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=APNIC.net&rft.atitle=What+Stops+IPv6+Traffic+in+a+Dual-Stack+ISP%3F&rft.date=2017-06-12&rft.aulast=Pujol&rft.aufirst=Enric&rft_id=https%3A%2F%2Fblog.apnic.net%2F2017%2F06%2F13%2Fstops-ipv6-traffic-dual-stack-isp%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-Steven_J._Vaughan-Nichols-60"><a href="#cite_ref-Steven_J._Vaughan-Nichols_60-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFVaughan-Nichols2010" class="citation news cs1">Vaughan-Nichols, Steven J. (14 October 2010). <a rel="nofollow" class="external text" href="https://www.zdnet.com/home-and-office/networking/five-ways-for-ipv6-and-ipv4-to-peacefully-co-exist/">"Five ways for IPv6 and IPv4 to peacefully co-exist"</a>. <a href="/wiki/ZDNET" title="ZDNET">ZDNET</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20231205094000/https://www.zdnet.com/home-and-office/networking/five-ways-for-ipv6-and-ipv4-to-peacefully-co-exist/">Archived</a> from the original on 5 December 2023. Retrieved 13 March 2017.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=ZDNET&rft.atitle=Five+ways+for+IPv6+and+IPv4+to+peacefully+co-exist&rft.date=2010-10-14&rft.aulast=Vaughan-Nichols&rft.aufirst=Steven+J.&rft_id=https%3A%2F%2Fwww.zdnet.com%2Fhome-and-office%2Fnetworking%2Ffive-ways-for-ipv6-and-ipv4-to-peacefully-co-exist%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-61"><a href="#cite_ref-61">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFSilvia_Hagen2014" class="citation book cs1">Silvia Hagen (2014). IPv6 Essentials: Integrating IPv6 into Your IPv4 Network. O'Reilly Media, Inc. p. 33. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <a href="/wiki/Special:BookSources/9781449335267" title="Special:BookSources/9781449335267"><bdi>9781449335267</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Essentials%3A+Integrating+IPv6+into+Your+IPv4+Network&rft.pages=33&rft.pub=O%27Reilly+Media%2C+Inc.&rft.date=2014&rft.isbn=9781449335267&rft.au=Silvia+Hagen&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc6890-62"><a href="#cite_ref-rfc6890_62-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFM._CottonL._VegodaB._Haberman2013" class="citation cs1">M. Cotton; L. Vegoda; B. Haberman (April 2013). R. Bonica (ed.). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6890">Special-Purpose IP Address Registries</a>. <a href="/wiki/IETF" class="mw-redirect" title="IETF">IETF</a>. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC6890">10.17487/RFC6890</a>. <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2070-1721">2070-1721</a>. BCP 153. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6890">6890</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Special-Purpose+IP+Address+Registries&rft.pub=IETF&rft.date=2013-04&rft_id=info%3Adoi%2F10.17487%2FRFC6890&rft.issn=2070-1721&rft.au=M.+Cotton&rft.au=L.+Vegoda&rft.au=B.+Haberman&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc6890&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Best Current Practice 153. Obsoletes <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4773">4773</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5156">5156</a>, <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5735">5735</a> and <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5736">5736</a>. Updated by <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8190">8190</a>. </li> <li id="cite_note-openbsd-mapped-addr-63"><a href="#cite_ref-openbsd-mapped-addr_63-0">^</a> <code><a rel="nofollow" class="external text" href="https://man.openbsd.org/inet6.4">inet6(4)</a></code> – <a href="/wiki/OpenBSD" title="OpenBSD">OpenBSD</a> Kernel Interfaces <a href="/wiki/Man_page" title="Man page">Manual</a> </li> <li id="cite_note-rfc3493-64"><a href="#cite_ref-rfc3493_64-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFR._GilliganS._ThomsonJ._BoundJ._McCann2003" class="citation cs1">R. Gilligan; S. Thomson; J. Bound; J. McCann; W. Stevens (February 2003). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3493">Basic Socket Interface Extensions for IPv6</a>. Network Working Group. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC3493">10.17487/RFC3493</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3493">3493</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Basic+Socket+Interface+Extensions+for+IPv6&rft.pub=Network+Working+Group&rft.date=2003-02&rft_id=info%3Adoi%2F10.17487%2FRFC3493&rft.au=R.+Gilligan&rft.au=S.+Thomson&rft.au=J.+Bound&rft.au=J.+McCann&rft.au=W.+Stevens&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc3493&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-rfc6052-65"><a href="#cite_ref-rfc6052_65-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFC._BaoC._HuitemaM._BagnuloM._Boucadair2010" class="citation cs1">C. Bao; <a href="/wiki/Christian_Huitema" title="Christian Huitema">C. Huitema</a>; M. Bagnulo; M. Boucadair; X. Li (October 2010). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6052">IPv6 Addressing of IPv4/IPv6 Translators</a>. <a href="/wiki/Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF). <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC6052">10.17487/RFC6052</a>. <a href="/wiki/ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/2070-1721">2070-1721</a>. <a href="/wiki/Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6052">6052</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Addressing+of+IPv4%2FIPv6+Translators&rft.pub=Internet+Engineering+Task+Force+%28IETF%29&rft.date=2010-10&rft_id=info%3Adoi%2F10.17487%2FRFC6052&rft.issn=2070-1721&rft.au=C.+Bao&rft.au=C.+Huitema&rft.au=M.+Bagnulo&rft.au=M.+Boucadair&rft.au=X.+Li&rft_id=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc6052&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> Proposed Standard. Updates <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222">RFC <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4291">4291</a>. </li> <li id="cite_note-66"><a href="#cite_ref-66">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFGont2019" class="citation cs2">Gont, Fernando (10 March 2019), <a rel="nofollow" class="external text" href="https://www.internetsociety.org/wp-content/uploads/2019/03/deploy360-ipv6-security-v1.0.pdf">IPv6 Security for IPv4 Engineers</a> (PDF), retrieved 30 August 2019</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Security+for+IPv4+Engineers&rft.date=2019-03-10&rft.aulast=Gont&rft.aufirst=Fernando&rft_id=https%3A%2F%2Fwww.internetsociety.org%2Fwp-content%2Fuploads%2F2019%2F03%2Fdeploy360-ipv6-security-v1.0.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-67"><a href="#cite_ref-67">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFGont2019" class="citation cs2">Gont, Fernando (10 January 2019), <a rel="nofollow" class="external text" href="https://www.internetsociety.org/wp-content/uploads/2019/02/Deploy360-IPv6-Security-FAQ.pdf">IPv6 Security Frequently Asked Questions (FAQ)</a> (PDF), retrieved 30 August 2019</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+Security+Frequently+Asked+Questions+%28FAQ%29&rft.date=2019-01-10&rft.aulast=Gont&rft.aufirst=Fernando&rft_id=https%3A%2F%2Fwww.internetsociety.org%2Fwp-content%2Fuploads%2F2019%2F02%2FDeploy360-IPv6-Security-FAQ.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-68"><a href="#cite_ref-68">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFMullins2012" class="citation cs2">Mullins, Robert (5 April 2012), <a rel="nofollow" class="external text" href="https://web.archive.org/web/20130411113334/http://www.networkcomputing.com/ipv6-tech-center/shadow-networks-an-unintended-ipv6-side/232800326">Shadow Networks: an Unintended IPv6 Side Effect</a>, archived from <a rel="nofollow" class="external text" href="http://www.networkcomputing.com/ipv6-tech-center/shadow-networks-an-unintended-ipv6-side/232800326">the original</a> on 11 April 2013, retrieved 2 March 2013</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=Shadow+Networks%3A+an+Unintended+IPv6+Side+Effect&rft.date=2012-04-05&rft.aulast=Mullins&rft.aufirst=Robert&rft_id=http%3A%2F%2Fwww.networkcomputing.com%2Fipv6-tech-center%2Fshadow-networks-an-unintended-ipv6-side%2F232800326&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-69"><a href="#cite_ref-69">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFCicileoGaglianoO’FlahertyRocha2009" class="citation book cs1">Cicileo, Guillermo; Gagliano, Roque; O’Flaherty, Christian; et al. (October 2009). <a rel="nofollow" class="external text" href="https://www.ipv6forum.com/dl/books/ipv6forall.pdf">IPv6 For All: A Guide for IPv6 Usage and Application in Different Environments</a> (PDF). p. 5. Retrieved 2 March 2013.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=IPv6+For+All%3A+A+Guide+for+IPv6+Usage+and+Application+in+Different+Environments&rft.pages=5&rft.date=2009-10&rft.aulast=Cicileo&rft.aufirst=Guillermo&rft.au=Gagliano%2C+Roque&rft.au=O%E2%80%99Flaherty%2C+Christian&rft.au=Rocha%2C+Mariela&rft.au=Morales%2C+C%C3%A9sar+Olvera&rft.au=Mart%C3%ADnez%2C+Jordi+Palet&rft.au=Mart%C3%ADnez%2C+%C3%81lvaro+Vives&rft_id=https%3A%2F%2Fwww.ipv6forum.com%2Fdl%2Fbooks%2Fipv6forall.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-70"><a href="#cite_ref-70">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFJun-ichiro_itojun_Hagino2003" class="citation web cs1">Jun-ichiro itojun Hagino (October 2003). <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/draft-itojun-v6ops-v4mapped-harmful-02">"IPv4-Mapped Addresses on the Wire Considered Harmful"</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=IPv4-Mapped+Addresses+on+the+Wire+Considered+Harmful&rft.date=2003-10&rft.au=Jun-ichiro+itojun+Hagino&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-itojun-v6ops-v4mapped-harmful-02&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-71"><a href="#cite_ref-71">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBradnerMankin1993" class="citation web cs1">Bradner, S.; Mankin, A. (December 1993). <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc1550">"IP: Next Generation (IPng) White Paper Solicitation"</a>. <a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc1550">1550</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=IP%3A+Next+Generation+%28IPng%29+White+Paper+Solicitation&rft.date=1993-12&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc1550%23id-name%3DRFC&rft.aulast=Bradner&rft.aufirst=S.&rft.au=Mankin%2C+A.&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc1550&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-72"><a href="#cite_ref-72">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20140523072903/http://grnlight.net/index.php/programming-articles/103-history-of-the-ipng-effort">"History of the IPng Effort"</a>. The Sun. Archived from <a rel="nofollow" class="external text" href="http://grnlight.net/index.php/programming-articles/103-history-of-the-ipng-effort">the original</a> on 23 May 2014.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=The+Sun&rft.atitle=History+of+the+IPng+Effort&rft_id=http%3A%2F%2Fgrnlight.net%2Findex.php%2Fprogramming-articles%2F103-history-of-the-ipng-effort&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-73"><a href="#cite_ref-73">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBradnerMankin1995" class="citation web cs1">Bradner, Scott O.; Mankin, Allison J. (January 1995). <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc1752#appendix-B">"The Recommendation for the IP Next Generation Protocol – Appendix B"</a>. <a href="/wiki/RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://tools.ietf.org/html/rfc1752">1752</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=The+Recommendation+for+the+IP+Next+Generation+Protocol+%E2%80%93+Appendix+B&rft.date=1995-01&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc1752%23id-name%3DRFC&rft.aulast=Bradner&rft.aufirst=Scott+O.&rft.au=Mankin%2C+Allison+J.&rft_id=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc1752%23appendix-B&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-74"><a href="#cite_ref-74">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFWangGao2019" class="citation journal cs1">Wang, Tao; Gao, Jiaqiong (1 January 2019). <a rel="nofollow" class="external text" href="https://doi.org/10.21307%2Fijanmc-2019-029">"The Shortcomings of Ipv6 and Upgrade of Ipv4"</a>. International Journal of Advanced Network, Monitoring and Controls. 4 (1): 1–9. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.21307%2Fijanmc-2019-029">10.21307/ijanmc-2019-029</a>.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.jtitle=International+Journal+of+Advanced+Network%2C+Monitoring+and+Controls&rft.atitle=The+Shortcomings+of+Ipv6+and+Upgrade+of+Ipv4&rft.volume=4&rft.issue=1&rft.pages=1-9&rft.date=2019-01-01&rft_id=info%3Adoi%2F10.21307%2Fijanmc-2019-029&rft.aulast=Wang&rft.aufirst=Tao&rft.au=Gao%2C+Jiaqiong&rft_id=https%3A%2F%2Fdoi.org%2F10.21307%252Fijanmc-2019-029&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-75"><a href="#cite_ref-75">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation cs2"><a rel="nofollow" class="external text" href="https://www.internetsociety.org/resources/2018/state-of-ipv6-deployment-2018/">State of IPv6 Deployment 2018</a>, <a href="/wiki/Internet_Society" title="Internet Society">Internet Society</a>, 2018, p. 3</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=book&rft.btitle=State+of+IPv6+Deployment+2018&rft.pages=3&rft.pub=Internet+Society&rft.date=2018&rft_id=https%3A%2F%2Fwww.internetsociety.org%2Fresources%2F2018%2Fstate-of-ipv6-deployment-2018%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-beijing2008-pressrelease-76"><a href="#cite_ref-beijing2008-pressrelease_76-0">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation pressrelease cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20090204051327/http://en.beijing2008.cn/news/official/preparation/n214384681.shtml">"Beijing2008.cn leaps to next-generation Net"</a> (Press release). The Beijing Organizing Committee for the Games of the XXIX Olympiad. 30 May 2008. Archived from <a rel="nofollow" class="external text" href="http://en.beijing2008.cn/news/official/preparation/n214384681.shtml">the original</a> on 4 February 2009.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Beijing2008.cn+leaps+to+next-generation+Net&rft.pub=The+Beijing+Organizing+Committee+for+the+Games+of+the+XXIX+Olympiad&rft.date=2008-05-30&rft_id=http%3A%2F%2Fen.beijing2008.cn%2Fnews%2Fofficial%2Fpreparation%2Fn214384681.shtml&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-77"><a href="#cite_ref-77">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFDas2008" class="citation web cs1">Das, Kaushik (2008). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20080801051918/http://www.ipv6.com/articles/general/IPv6-Olympics-2008.htm">"IPv6 and the 2008 Beijing Olympics"</a>. IPv6.com. Archived from <a rel="nofollow" class="external text" href="http://ipv6.com/articles/general/IPv6-Olympics-2008.htm">the original</a> on 1 August 2008. Retrieved 15 August 2008.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=IPv6.com&rft.atitle=IPv6+and+the+2008+Beijing+Olympics&rft.date=2008&rft.aulast=Das&rft.aufirst=Kaushik&rft_id=http%3A%2F%2Fipv6.com%2Farticles%2Fgeneral%2FIPv6-Olympics-2008.htm&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-verizon-78">^ <a href="#cite_ref-verizon_78-0">a</a> <a href="#cite_ref-verizon_78-1">b</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFMorr2009" class="citation web cs1">Morr, Derek (9 June 2009). <a rel="nofollow" class="external text" href="http://www.circleid.com/posts/20090609_verizon_mandates_ipv6_support_for_next_gen_cell_phones/">"Verizon Mandates IPv6 Support for Next-Gen Cell Phones"</a>. CircleID.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&rft.genre=unknown&rft.btitle=Verizon+Mandates+IPv6+Support+for+Next-Gen+Cell+Phones&rft.pub=CircleID&rft.date=2009-06-09&rft.aulast=Morr&rft.aufirst=Derek&rft_id=http%3A%2F%2Fwww.circleid.com%2Fposts%2F20090609_verizon_mandates_ipv6_support_for_next_gen_cell_phones%2F&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-IS_2018-79">^ <a href="#cite_ref-IS_2018_79-0">a</a> <a href="#cite_ref-IS_2018_79-1">b</a> <a href="#cite_ref-IS_2018_79-2">c</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.internetsociety.org/wp-content/uploads/2018/06/2018-ISOC-Report-IPv6-Deployment.pdf">"State of IPv6 Deployment 2018"</a> (PDF). InternetSociety.org. <a href="/wiki/Internet_Society" title="Internet Society">Internet Society</a>. Retrieved 19 January 2022.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=InternetSociety.org&rft.atitle=State+of+IPv6+Deployment+2018&rft_id=https%3A%2F%2Fwww.internetsociety.org%2Fwp-content%2Fuploads%2F2018%2F06%2F2018-ISOC-Report-IPv6-Deployment.pdf&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> <li id="cite_note-80"><a href="#cite_ref-80">^</a> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://bgp.tools/kb/partitions">"The case of Hurricane Electric And Cogent"</a>. BGP.tools. BGP.tools. Retrieved 10 September 2024.</cite><span title="ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=unknown&rft.jtitle=BGP.tools&rft.atitle=The+case+of+Hurricane+Electric+And+Cogent&rft_id=https%3A%2F%2Fbgp.tools%2Fkb%2Fpartitions&rfr_id=info%3Asid%2Fen.wikipedia.org%3AIPv6" class="Z3988"> </li> </ol></div></div> <div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2>[<a href="/w/index.php?title=IPv6&action=edit&section=35" title="Edit section: External links">edit</a>]</div> <style data-mw-deduplicate="TemplateStyles:r1235681985">.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}</style><style data-mw-deduplicate="TemplateStyles:r1237033735">@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}</style><div class="side-box side-box-right plainlinks sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}</style> <div class="side-box-flex"> <div class="side-box-image"><img alt="" src="//upload.wikimedia.org/wikipedia/commons/thumb/f/ff/Wikidata-logo.svg/40px-Wikidata-logo.svg.png" decoding="async" width="40" height="22" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/f/ff/Wikidata-logo.svg/60px-Wikidata-logo.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/f/ff/Wikidata-logo.svg/80px-Wikidata-logo.svg.png 2x" data-file-width="1050" data-file-height="590" /></div> <div class="side-box-text plainlist"><a href="/wiki/Wikidata" title="Wikidata">Wikidata</a> has the property: <ul><li><img alt="" src="//upload.wikimedia.org/wikipedia/commons/thumb/a/a8/Disc_Plain_blue_dark.svg/4px-Disc_Plain_blue_dark.svg.png" decoding="async" width="4" height="4" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/a/a8/Disc_Plain_blue_dark.svg/6px-Disc_Plain_blue_dark.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/a/a8/Disc_Plain_blue_dark.svg/8px-Disc_Plain_blue_dark.svg.png 2x" data-file-width="460" data-file-height="460" /> <a href="https://www.wikidata.org/wiki/Property_talk:P3793" class="extiw" title="d:Property talk:P3793">IPv6 routing prefix (P3793)</a> (see <a class="external text" href="https://query.wikidata.org/embed.html#SELECT%20%3FWikidata_item_%20%3FWikidata_item_Label%20%3Fvalue%20%3FvalueLabel%20%3FEnglish_Wikipedia_article%20%23Show%20data%20in%20this%20order%0A%7B%0A%09%3FWikidata_item_%20wdt%3AP3793%20%3Fvalue%20.%20%23Collecting%20all%20items%20which%20have%20P3793%20data%2C%20from%20whole%20Wikidata%20item%20pages%0A%09OPTIONAL%20%7B%3FEnglish_Wikipedia_article%20schema%3Aabout%20%3FWikidata_item_%3B%20schema%3AisPartOf%20%3Chttps%3A%2F%2Fen.wikipedia.org%2F%3E%20.%7D%20%23If%20collected%20item%20has%20link%20to%20English%20Wikipedia%2C%20show%20that%0A%09SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22en%22%20%20%7D%20%23Show%20label%20in%20this%20language.%20%22en%22%20is%20English.%20%20%20%0A%7D%0ALIMIT%201000">uses</a>)</li></ul></div></div> </div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1235681985"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1237033735"><div class="side-box side-box-right plainlinks sistersitebox"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1126788409"> <div class="side-box-flex"> <div class="side-box-image"><img alt="" src="//upload.wikimedia.org/wikipedia/commons/thumb/0/0b/Wikiversity_logo_2017.svg/40px-Wikiversity_logo_2017.svg.png" decoding="async" width="40" height="33" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/0/0b/Wikiversity_logo_2017.svg/60px-Wikiversity_logo_2017.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/0/0b/Wikiversity_logo_2017.svg/80px-Wikiversity_logo_2017.svg.png 2x" data-file-width="626" data-file-height="512" /></div> <div class="side-box-text plainlist">Wikiversity has learning resources about <a href="https://en.wikiversity.org/wiki/IPv6" class="extiw" title="v:IPv6">IPv6</a></div></div> </div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1235681985"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1237033735"><div class="side-box side-box-right plainlinks sistersitebox"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1126788409"> <div class="side-box-flex"> <div class="side-box-image"><img alt="" src="//upload.wikimedia.org/wikipedia/commons/thumb/9/99/Wiktionary-logo-en-v2.svg/40px-Wiktionary-logo-en-v2.svg.png" decoding="async" width="40" height="40" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/9/99/Wiktionary-logo-en-v2.svg/60px-Wiktionary-logo-en-v2.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/9/99/Wiktionary-logo-en-v2.svg/80px-Wiktionary-logo-en-v2.svg.png 2x" data-file-width="512" data-file-height="512" /></div> <div class="side-box-text plainlist">Look up <a href="https://en.wiktionary.org/wiki/IPv6" class="extiw" title="wiktionary:IPv6">IPv6</a> in Wiktionary, the free dictionary.</div></div> </div> <ul><li><a rel="nofollow" class="external text" href="https://www.haifux.org/lectures/187">IPv6 in the Linux Kernel</a> by Rami Rosen</li> <li><a rel="nofollow" class="external text" href="https://www.google.com/intl/en/ipv6/">An Introduction and Statistics about IPv6</a> by Google</li> <li><a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8200">The standard document ratifying IPv6</a> – RFC 8200 document ratifying IPv6 as an Internet Standard</li></ul> <div class="navbox-styles"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><style data-mw-deduplicate="TemplateStyles:r1236075235">.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}</style></div><div role="navigation" class="navbox" aria-labelledby="Internet_Protocol_version_6" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1239400231"><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:IPv6" title="Template:IPv6"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/wiki/Template_talk:IPv6" title="Template talk:IPv6"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:IPv6" title="Special:EditPage/Template:IPv6"><abbr title="Edit this template">e</abbr></a></li></ul></div><div id="Internet_Protocol_version_6" style="font-size:114%;margin:0 4em"><a href="/wiki/Internet_Protocol" title="Internet Protocol">Internet Protocol</a> <a class="mw-selflink selflink">version 6</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">General</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a class="mw-selflink selflink">IPv6</a></li> <li><a href="/wiki/IPv6_address" title="IPv6 address">IPv6 address</a></li> <li><a href="/wiki/IPv6_packet" title="IPv6 packet">IPv6 packet</a></li> <li><a href="/wiki/Mobile_IP#Changes_in_IPv6_for_Mobile_IPv6" title="Mobile IP">Mobile IPv6</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Deployment</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/IPv6_deployment" title="IPv6 deployment">IPv6 deployment</a> <ul><li><a href="/wiki/6rd" class="mw-redirect" title="6rd">6rd</a></li></ul></li> <li><a href="/wiki/World_IPv6_Day_and_World_IPv6_Launch_Day" title="World IPv6 Day and World IPv6 Launch Day">World IPv6 Day and World IPv6 Launch Day</a></li> <li><a href="/wiki/Comparison_of_IPv6_support_in_operating_systems" title="Comparison of IPv6 support in operating systems">Comparison of IPv6 support in operating systems</a></li> <li><a href="/wiki/Comparison_of_IPv6_support_in_common_applications" title="Comparison of IPv6 support in common applications">Comparison of IPv6 support in common applications</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">IPv4 to IPv6 topics</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/IPv4_address_exhaustion" title="IPv4 address exhaustion">IPv4 address exhaustion</a></li> <li><a href="/wiki/IPv6_transition_mechanism" title="IPv6 transition mechanism">IPv6 transition mechanism</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related protocols</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/DHCPv6" title="DHCPv6">DHCPv6</a></li> <li><a href="/wiki/Internet_Control_Message_Protocol_for_IPv6" class="mw-redirect" title="Internet Control Message Protocol for IPv6">ICMPv6</a> <ul><li><a href="/wiki/Neighbor_Discovery_Protocol" title="Neighbor Discovery Protocol">Neighbor Discovery Protocol</a></li> <li><a href="/wiki/Multicast_Listener_Discovery" title="Multicast Listener Discovery">Multicast Listener Discovery</a></li> <li><a href="/wiki/Secure_Neighbor_Discovery" title="Secure Neighbor Discovery">Secure Neighbor Discovery</a></li> <li><a href="/wiki/Multicast_router_discovery" title="Multicast router discovery">Multicast router discovery</a></li></ul></li> <li><a href="/wiki/Site_Multihoming_by_IPv6_Intermediation" title="Site Multihoming by IPv6 Intermediation">Site Multihoming by IPv6 Intermediation</a></li></ul> </div></td></tr></tbody></table></div> <div class="navbox-styles"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236075235"><style data-mw-deduplicate="TemplateStyles:r1038841319">.mw-parser-output .tooltip-dotted{border-bottom:1px dotted;cursor:help}</style></div><div role="navigation" class="navbox authority-control" aria-label="Navbox" style="padding:3px"><table class="nowraplinks hlist navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Help:Authority_control" title="Help:Authority control">Authority control databases</a>: National <a href="https://www.wikidata.org/wiki/Q2551624#identifiers" title="Edit this at Wikidata"><img alt="Edit this at Wikidata" src="//upload.wikimedia.org/wikipedia/en/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/10px-OOjs_UI_icon_edit-ltr-progressive.svg.png" decoding="async" width="10" height="10" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/en/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/15px-OOjs_UI_icon_edit-ltr-progressive.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/20px-OOjs_UI_icon_edit-ltr-progressive.svg.png 2x" data-file-width="20" data-file-height="20" /></a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://d-nb.info/gnd/4462513-3">Germany</a></li><li><a rel="nofollow" class="external text" href="https://aleph.nkp.cz/F/?func=find-c&local_base=aut&ccl_term=ica=ph165186&CON_LNG=ENG">Czech Republic</a></li></ul></div></td></tr></tbody></table></div>    </div><noscript><img src="https://login.wikimedia.org/wiki/Special:CentralAutoLogin/start?type=1x1" alt="" width="1" height="1" style="border: none; position: absolute;"></noscript> <div class="printfooter" data-nosnippet="">Retrieved from "<a dir="ltr" href="https://en.wikipedia.org/w/index.php?title=IPv6&oldid=1247827527">https://en.wikipedia.org/w/index.php?title=IPv6&oldid=1247827527</a>"</div></div> <div id="catlinks" class="catlinks" data-mw="interface"><div id="mw-normal-catlinks" class="mw-normal-catlinks"><a href="/wiki/Help:Category" title="Help:Category">Categories</a>: <ul><li><a href="/wiki/Category:IPv6" title="Category:IPv6">IPv6</a></li><li><a href="/wiki/Category:Internet_properties_established_in_1996" title="Category:Internet properties established in 1996">Internet properties established in 1996</a></li><li><a href="/wiki/Category:Internet_layer_protocols" title="Category:Internet layer protocols">Internet layer protocols</a></li><li><a href="/wiki/Category:Network_layer_protocols" title="Category:Network layer protocols">Network layer protocols</a></li></ul></div><div id="mw-hidden-catlinks" class="mw-hidden-catlinks mw-hidden-cats-hidden">Hidden categories: <ul><li><a href="/wiki/Category:Articles_with_short_description" title="Category:Articles with short description">Articles with short description</a></li><li><a href="/wiki/Category:Short_description_matches_Wikidata" title="Category:Short description matches Wikidata">Short description matches Wikidata</a></li><li><a href="/wiki/Category:Wikipedia_articles_in_need_of_updating_from_July_2017" title="Category:Wikipedia articles in need of updating from July 2017">Wikipedia articles in need of updating from July 2017</a></li><li><a href="/wiki/Category:All_Wikipedia_articles_in_need_of_updating" title="Category:All Wikipedia articles in need of updating">All Wikipedia articles in need of updating</a></li><li><a href="/wiki/Category:Use_dmy_dates_from_September_2020" title="Category:Use dmy dates from September 2020">Use dmy dates from September 2020</a></li><li><a href="/wiki/Category:Pages_with_timeline_metadata" title="Category:Pages with timeline metadata">Pages with timeline metadata</a></li><li><a href="/wiki/Category:All_articles_with_unsourced_statements" title="Category:All articles with unsourced statements">All articles with unsourced statements</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_January_2022" title="Category:Articles with unsourced statements from January 2022">Articles with unsourced statements from January 2022</a></li></ul></div></div> </div> </main> </div> <div class="mw-footer-container"> <footer id="footer" class="mw-footer" > <ul id="footer-info"> <li id="footer-info-lastmod"> This page was last edited on 26 September 2024, at 06:50 (UTC).</li> <li id="footer-info-copyright">Text is available under the <a href="/wiki/Wikipedia:Text_of_the_Creative_Commons_Attribution-ShareAlike_4.0_International_License" title="Wikipedia:Text of the Creative Commons Attribution-ShareAlike 4.0 International License">Creative Commons Attribution-ShareAlike 4.0 License</a>; additional terms may apply. By using this site, you agree to the <a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use" class="extiw" title="foundation:Special:MyLanguage/Policy:Terms of Use">Terms of Use</a> and <a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Privacy_policy" class="extiw" title="foundation:Special:MyLanguage/Policy:Privacy policy">Privacy Policy</a>. Wikipedia® is a registered trademark of the <a rel="nofollow" class="external text" href="https://wikimediafoundation.org/">Wikimedia Foundation, Inc.</a>, a non-profit organization.</li> </ul> <ul id="footer-places"> <li id="footer-places-privacy"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Privacy_policy">Privacy policy</a></li> <li id="footer-places-about"><a href="/wiki/Wikipedia:About">About Wikipedia</a></li> <li id="footer-places-disclaimers"><a href="/wiki/Wikipedia:General_disclaimer">Disclaimers</a></li> <li id="footer-places-contact"><a href="//en.wikipedia.org/wiki/Wikipedia:Contact_us">Contact Wikipedia</a></li> <li id="footer-places-wm-codeofconduct"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Universal_Code_of_Conduct">Code of Conduct</a></li> <li id="footer-places-developers"><a href="https://developer.wikimedia.org">Developers</a></li> <li id="footer-places-statslink"><a href="https://stats.wikimedia.org/#/en.wikipedia.org">Statistics</a></li> <li id="footer-places-cookiestatement"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Cookie_statement">Cookie statement</a></li> <li id="footer-places-mobileview"><a href="//en.m.wikipedia.org/w/index.php?title=IPv6&mobileaction=toggle_view_mobile" class="noprint stopMobileRedirectToggle">Mobile view</a></li> </ul> <ul id="footer-icons" class="noprint"> <li id="footer-copyrightico"><a href="https://wikimediafoundation.org/" class="cdx-button cdx-button--fake-button cdx-button--size-large cdx-button--fake-button--enabled"><img src="/static/images/footer/wikimedia-button.svg" width="84" height="29" alt="Wikimedia Foundation" loading="lazy"></a></li> <li id="footer-poweredbyico"><a href="https://www.mediawiki.org/" class="cdx-button cdx-button--fake-button cdx-button--size-large cdx-button--fake-button--enabled"><img src="/w/resources/assets/poweredby_mediawiki.svg" alt="Powered by MediaWiki" width="88" height="31" loading="lazy"></a></li> </ul> </footer> </div> </div> </div> <div class="vector-settings" id="p-dock-bottom"> <ul></ul> </div><script>(RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgHostname":"mw-web.codfw.main-669b4ddb54-j9hfq","wgBackendResponseTime":175,"wgPageParseReport":{"limitreport":{"cputime":"2.155","walltime":"2.387","ppvisitednodes":{"value":45269,"limit":1000000},"postexpandincludesize":{"value":613901,"limit":2097152},"templateargumentsize":{"value":48003,"limit":2097152},"expansiondepth":{"value":26,"limit":100},"expensivefunctioncount":{"value":24,"limit":500},"unstrip-depth":{"value":1,"limit":20},"unstrip-size":{"value":457155,"limit":5000000},"entityaccesscount":{"value":1,"limit":400},"timingprofile":["100.00% 2114.625 1 -total"," 36.37% 769.107 21 Template:Ref_RFC"," 26.25% 555.048 45 Template:Cite_IETF"," 20.81% 439.950 1 Template:Reflist"," 16.73% 353.717 21 Template:Ref_RFC/getref"," 8.22% 173.719 49 Template:IETF_RFC"," 7.84% 165.712 31 Template:Cite_web"," 7.78% 164.426 49 Template:Catalog_lookup_link"," 5.98% 126.448 1 Template:Infobox_networking_protocol"," 5.88% 124.251 1 Template:Infobox"]},"scribunto":{"limitreport-timeusage":{"value":"1.139","limit":"10.000"},"limitreport-memusage":{"value":11380548,"limit":52428800},"limitreport-profile":[["MediaWiki\\Extension\\Scribunto\\Engines\\LuaSandbox\\LuaSandboxCallback::callParserFunction","280","18.9"],["?","240","16.2"],["MediaWiki\\Extension\\Scribunto\\Engines\\LuaSandbox\\LuaSandboxCallback::getExpandedArgument","200","13.5"],["MediaWiki\\Extension\\Scribunto\\Engines\\LuaSandbox\\LuaSandboxCallback::getAllExpandedArguments","140","9.5"],["dataWrapper \u003Cmw.lua:672\u003E","120","8.1"],["MediaWiki\\Extension\\Scribunto\\Engines\\LuaSandbox\\LuaSandboxCallback::match","60","4.1"],["MediaWiki\\Extension\\Scribunto\\Engines\\LuaSandbox\\LuaSandboxCallback::gsub","60","4.1"],["\u003CmwInit.lua:45\u003E","40","2.7"],["gsub","40","2.7"],["MediaWiki\\Extension\\Scribunto\\Engines\\LuaSandbox\\LuaSandboxCallback::find","40","2.7"],["[others]","260","17.6"]]},"cachereport":{"origin":"mw-api-int.codfw.main-5f67bcf949-fgq7d","timestamp":"20241127004140","ttl":343111,"transientcontent":true}}});});</script> <script type="application/ld+json">{"@context":"https:\/\/schema.org","@type":"Article","name":"IPv6","url":"https:\/\/en.wikipedia.org\/wiki\/IPv6","sameAs":"http:\/\/www.wikidata.org\/entity\/Q2551624","mainEntity":"http:\/\/www.wikidata.org\/entity\/Q2551624","author":{"@type":"Organization","name":"Contributors to Wikimedia projects"},"publisher":{"@type":"Organization","name":"Wikimedia Foundation, Inc.","logo":{"@type":"ImageObject","url":"https:\/\/www.wikimedia.org\/static\/images\/wmf-hor-googpub.png"}},"datePublished":"2001-12-04T16:18:48Z","dateModified":"2024-09-26T06:50:14Z","image":"https:\/\/upload.wikimedia.org\/wikipedia\/commons\/4\/4c\/IPv6_header-en.svg","headline":"version 6 of the Internet Protocol"}</script> </body> </html>