{"id":28804,"date":"2025-02-06T15:52:53","date_gmt":"2025-02-06T15:52:53","guid":{"rendered":"https:\/\/blog.lacnic.net\/?p=28804"},"modified":"2025-02-11T15:27:47","modified_gmt":"2025-02-11T15:27:47","slug":"applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20","status":"publish","type":"post","link":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/","title":{"rendered":"Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)"},"content":{"rendered":"\n<p>By <a href=\"https:\/\/blog.lacnic.net\/autor\/alejandro-acosta\/\">Alejandro Acosta<\/a>, R&amp;D Coordinator, and <a href=\"https:\/\/blog.lacnic.net\/en\/author\/julio-buiza\/\">Julio Buiza<\/a>, Registration Services Specialist, at LACNIC<\/p>\n\n\n\n<h1 class=\"wp-block-heading\"><a><\/a><strong><u>Introduction<\/u><\/strong><strong><\/strong><\/h1>\n\n\n\n<p>On 23 July 2024, the IANA reserved <strong>3FFF::\/20<\/strong> as a new dedicated IPv6 address prefix for documentation purposes, thus adding a new block to the existing documentation block <strong>(2001:db8::\/32). <\/strong>This request was included in IETF draft <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-ietf-v6ops-rfc3849-update\/05\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/datatracker.ietf.org\/doc\/draft-ietf-v6ops-rfc3849-update\/05\/<\/a> as follows:<\/p>\n\n\n\n<p><em>\u201cThe document describes the reservation of an additional IPv6 address prefix for use in documentation. This update to RFC 3849 expands on the existing 2001:db8::\/32 address block with the reservation of an additional, larger prefix. The addition of a \/20 allows documented examples to more closely reflect a broader range of realistic, current deployment scenarios and more closely aligns with contemporary allocation models for large networks.\u201d<\/em><\/p>\n\n\n\n<p>Following this expansion, in this article we will discuss an IPv6 address plan as an example, using address block<strong>3FFF::\/20.<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><a><\/a><strong>Importance of an IP Address Plan<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a><strong>What is an IP (v4\/v6) address plan?<\/strong><\/h3>\n\n\n\n<p>An IP address plan is defined as the form, actions, and systematic model used for assigning IP addresses on a network [1].<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a><strong>Why you should develop an IP address plan<\/strong><strong><\/strong><\/h3>\n\n\n\n<p>An IP address plan:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Helps to keep the network documentation in order,<\/li>\n\n\n\n<li>Simplifies the implementation of assignment policies,<\/li>\n\n\n\n<li>Supports the orderly growth of the network (future assignments\/scaling),<\/li>\n\n\n\n<li>Improves network performance efficiency (smaller routing tables),<\/li>\n\n\n\n<li>Facilitates troubleshooting, and<\/li>\n\n\n\n<li>Simplifies network management.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><a><\/a><strong>What should an IP address plan look like? What aspects should it consider?<\/strong><strong><\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An IP address plan must be <em>scalable<\/em> (anticipate the potential growth of the network over the next 2, 5, 10, and 15 years).<\/li>\n\n\n\n<li>It must be <em>flexible<\/em>. For example, in the future, new services may be added or coverage may be extended to other cities.<\/li>\n\n\n\n<li>It must be <em>simple<\/em> and comprehensible, in other words, it must not introduce unnecessary complexity.<\/li>\n\n\n\n<li>It must follow <em>best practices<\/em>.<\/li>\n\n\n\n<li>It must separate <em>the infrastructure<\/em> from <em>customers<\/em> (important).<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><a><\/a><strong>Recommendations to begin your IPv6 address plan<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a><strong>1)&nbsp;&nbsp;&nbsp; <\/strong>The most important piece of advice, and one of the most fundamental, is to manipulate the blocks by nibbles, in other words, considering each character of the IPv6 address.<\/h3>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a><strong>What would the new 3FFF::\/20 prefix look like?<\/strong><strong><\/strong><\/h3>\n\n\n\n<p>As shown in the image below, because the prefix is \u200b\u200ba \/20, the first five nibbles are fixed and every \u201cX\u201d character can be modified:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"366\" src=\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig1-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-1024x366.png\" alt=\"\" class=\"wp-image-28784\" srcset=\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig1-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-1024x366.png 1024w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig1-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-300x107.png 300w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig1-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-680x243.png 680w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig1-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-768x274.png 768w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig1-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-1536x549.png 1536w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig1-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20.png 1606w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Where:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>C1, C2, C3, C4, C5, C6, C7, C8 -&gt; Represent groups of 16 bits<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><a><\/a><strong>2)&nbsp;&nbsp;&nbsp; <\/strong><strong>Mapping the nibbles to a function<\/strong><\/h3>\n\n\n\n<p>A common practice is to map a nibble or a group of nibbles to \u201csomething\u201d, where this \u201csomething\u201d might be a function, a country, a service, a type of customer, or something else.<\/p>\n\n\n\n<p>This is illustrated in the following image:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>For ISPs:<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"467\" src=\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig2-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-1024x467.png\" alt=\"\" class=\"wp-image-28787\" srcset=\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig2-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-1024x467.png 1024w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig2-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-300x137.png 300w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig2-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-680x310.png 680w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig2-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-768x351.png 768w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig2-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-1536x701.png 1536w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig2-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20.png 1582w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Where:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PPP -&gt; Represents a country<\/li>\n\n\n\n<li>CCC -&gt; Represents a city<\/li>\n\n\n\n<li>SS -&gt; Represents a service<\/li>\n\n\n\n<li>T -&gt; Represents a type of customer<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>For End Users (EU):<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"434\" src=\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig3-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-1024x434.png\" alt=\"\" class=\"wp-image-28790\" srcset=\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig3-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-1024x434.png 1024w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig3-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-300x127.png 300w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig3-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-680x288.png 680w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig3-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20-768x326.png 768w, https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/fig3-aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff20.png 1500w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Where:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>UUU -&gt; Represents a campus\/location<\/li>\n\n\n\n<li>EEE -&gt; Represents a building withing the campus\/location<\/li>\n\n\n\n<li>SS -&gt; Represents a service<\/li>\n\n\n\n<li>F -&gt; Represents a faculty<\/li>\n<\/ul>\n\n\n\n<p><strong>Important:<\/strong> Keep in mind that the final 64 bits (C5, C6, C7, and C8) are typically assigned by the autoconfiguration process and\/or manually by the administrator.<\/p>\n\n\n<section class=\"acf-view acf-view--id--21788 acf-view--object-id--28804\"><div class=\"acf-view__texto_fijo acf-view__row\"><div class=\"acf-view__texto_fijo-field acf-view__field\"><div class=\"acf-view__texto_fijo-choice acf-view__choice\">Additional reading:<\/div><\/div><\/div><div class=\"acf-view__enlace acf-view__row\"><div class=\"acf-view__enlace-field acf-view__field\"><a target=\"_self\" class=\"acf-view__enlace-link acf-view__link\" href=\"https:\/\/blog.lacnic.net\/en\/expanding-the-ipv6-documentation-space\/\">Expanding the IPv6 Documentation Space<\/a><\/div><\/div><\/section>\n\n\n<h2 class=\"wp-block-heading\"><a><\/a><strong><u>Practical Example of an IPv6 Address Plan<\/u><\/strong><strong>:<\/strong><\/h2>\n\n\n\n<p>Below we have included a couple of examples of an address plan using the new 3FFF::\/20 prefix.<\/p>\n\n\n\n<p><strong>Note: <\/strong>These examples are offered as recommendations and show one of many possible approaches to developing an IPv6 address plan within a network.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>IPv6 Address Plan for an ISP<\/strong><\/li>\n<\/ol>\n\n\n\n<p>In this scenario, an ISP operating in three countries, each with three cities, has been considered. Using the nomenclature in the previous example, specific values \u200b\u200bhave been assigned and characters have been replaced based on the category they each represent, as shown in the following table:<\/p>\n\n\n\n<figure class=\"wp-block-table tabla\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Characters to be modified<\/strong><\/td><td><strong>Category<\/strong><\/td><td><strong>Values<\/strong><\/td><td><strong>Description<\/strong><\/td><\/tr><tr><td rowspan=\"3\">PPP<\/td><td rowspan=\"3\">Country<\/td><td>058<\/td><td>Venezuela<\/td><\/tr><tr><td>057<\/td><td>Colombia<\/td><\/tr><tr><td>051<\/td><td>Peru<\/td><\/tr><tr><td rowspan=\"9\">CCC<\/td><td rowspan=\"9\">Ciudad<\/td><td>212<\/td><td>Caracas<\/td><\/tr><tr><td>261<\/td><td>Maracaibo<\/td><\/tr><tr><td>241<\/td><td>Valencia<\/td><\/tr><tr><td>601<\/td><td>Bogota<\/td><\/tr><tr><td>604<\/td><td>Medellin<\/td><\/tr><tr><td>605<\/td><td>Cartagena<\/td><\/tr><tr><td>031<\/td><td>Lima<\/td><\/tr><tr><td>032<\/td><td>Arequipa<\/td><\/tr><tr><td>033<\/td><td>Cusco<\/td><\/tr><tr><td rowspan=\"3\">SS<\/td><td rowspan=\"3\">Service<\/td><td>10<\/td><td>HFC Internet<\/td><\/tr><tr><td>20<\/td><td>GPON Internet<\/td><\/tr><tr><td>30<\/td><td>Satellite Internet<\/td><\/tr><tr><td rowspan=\"4\">T<\/td><td rowspan=\"4\">Type of customer<\/td><td>1<\/td><td>Company<\/td><\/tr><tr><td>2<\/td><td>Government entity<\/td><\/tr><tr><td>3<\/td><td>Residential<\/td><\/tr><tr><td>4<\/td><td>NGO<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>This is an example of what an IPv6 address plan for an ISP would look like:<\/p>\n\n\n\n<figure class=\"wp-block-table tabla\" style=\"font-size:11px\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>IPv6 prefix<\/strong><\/td><td><strong>Country<\/strong><\/td><td><strong>Prefix assigned to the country [NET_ID]<\/strong><\/td><td><strong>City<\/strong><\/td><td><strong>Subnet assigned to the city<\/strong><strong><\/strong> <strong>[Subnet]<\/strong><\/td><td><strong>Service<\/strong><\/td><td><strong>Type of customer<\/strong><\/td><td><strong>Subnet assigned to the service and type of customer<\/strong><strong><\/strong> <strong>[Division]<\/strong><\/td><\/tr><tr><td rowspan=\"41\"><strong>3FFF::\/20<\/strong><\/td><td rowspan=\"14\">Venezuela<\/td><td rowspan=\"14\"><strong>3FFF:0058::\/32<\/strong><\/td><td rowspan=\"6\">Caracas<\/td><td rowspan=\"6\"><strong>3FFF:0058:0212::\/48<\/strong><\/td><td rowspan=\"4\">HFC Internet<\/td><td>Company<\/td><td><strong>3FFF:0058:0212:0101::\/64<\/strong><\/td><\/tr><tr><td>Government entity<\/td><td><strong>3FFF:0058:0212:0102::\/64<\/strong><\/td><\/tr><tr><td>Residential<\/td><td><strong>3FFF:0058:0212:0103::\/64<\/strong><\/td><\/tr><tr><td>NGO<\/td><td><strong>3FFF:0058:0212:0104::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"2\">GPON Internet<\/td><td>Company<\/td><td><strong>3FFF:0058:0212:0201::\/64<\/strong><\/td><\/tr><tr><td>Residential<\/td><td><strong>3FFF:0058:0212:0203::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"4\">Maracaibo<\/td><td rowspan=\"4\"><strong>3FFF:0058:0261::\/48<\/strong><\/td><td rowspan=\"4\">GPON Internet<\/td><td>Company<\/td><td><strong>3FFF:0058:0261:0201::\/64<\/strong><\/td><\/tr><tr><td>Government entity<\/td><td><strong>3FFF:0058:0261:0202::\/64<\/strong><\/td><\/tr><tr><td>Residential<\/td><td><strong>3FFF:0058:0261:0203::\/64<\/strong><\/td><\/tr><tr><td>NGO<\/td><td><strong>3FFF:0058:0261:0204::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"4\">Valencia<\/td><td rowspan=\"4\"><strong>3FFF:0058:0241::\/48<\/strong><\/td><td rowspan=\"2\">GPON Internet<\/td><td>Company<\/td><td><strong>3FFF:0058:0241:0201::\/64<\/strong><\/td><\/tr><tr><td>Government entity<\/td><td><strong>3FFF:0058:0241:0202::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"2\">Satellite Internet<\/td><td>Residential<\/td><td><strong>3FFF:0058:0241:0303::\/64<\/strong><\/td><\/tr><tr><td>NGO<\/td><td><strong>3FFF:0058:0241:0304::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"12\">Colombia<\/td><td rowspan=\"12\"><strong>3FFF:0057::\/32<\/strong><\/td><td rowspan=\"4\">Bogota<\/td><td rowspan=\"4\"><strong>3FFF:0057:0601::\/48<\/strong><\/td><td rowspan=\"4\">HFC Internet<\/td><td>Company<\/td><td><strong>3FFF:0057:0601:0101::\/64<\/strong><\/td><\/tr><tr><td>Government entity<\/td><td><strong>3FFF:0057:0601:0102::\/64<\/strong><\/td><\/tr><tr><td>Residential<\/td><td><strong>3FFF:0057:0601:0103::\/64<\/strong><\/td><\/tr><tr><td>NGO<\/td><td><strong>3FFF:0057:0601:0104::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"4\">Medellin<\/td><td rowspan=\"4\"><strong>3FFF:0057:0604::\/48<\/strong><\/td><td rowspan=\"4\">GPON Internet<\/td><td>Company<\/td><td><strong>3FFF:0057:0604:0201::\/64<\/strong><\/td><\/tr><tr><td>Government entity<\/td><td><strong>3FFF:0057:0604:0202::\/64<\/strong><\/td><\/tr><tr><td>Residential<\/td><td><strong>3FFF:0057:0604:0203::\/64<\/strong><\/td><\/tr><tr><td>NGO<\/td><td><strong>3FFF:0057:0604:0204::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"4\">Cartagena<\/td><td rowspan=\"4\"><strong>3FFF:0057:0605::\/48<\/strong><\/td><td rowspan=\"2\">GPON Internet<\/td><td>Company<\/td><td><strong>3FFF:0057:0605:0201::\/64<\/strong><\/td><\/tr><tr><td>Government entity<\/td><td><strong>3FFF:0057:0605:0202::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"2\">Satellite Internet<\/td><td>Residential<\/td><td><strong>3FFF:0057:0605:0303::\/64<\/strong><\/td><\/tr><tr><td>NGO<\/td><td><strong>3FFF:0057:0605:0304::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"14\">Peru<\/td><td rowspan=\"14\"><strong>3FFF:0051::\/32<\/strong><\/td><td rowspan=\"3\">Lima<\/td><td rowspan=\"3\"><strong>3FFF:0051:0031::\/48<\/strong><\/td><td rowspan=\"2\">GPON Internet<\/td><td>Company<\/td><td><strong>3FFF:0051:0031:0201::\/64<\/strong><\/td><\/tr><tr><td>Residential<\/td><td><strong>3FFF:0051:0031:0203::\/64<\/strong><\/td><\/tr><tr><td>Satellite Internet<\/td><td>Residential<\/td><td><strong>3FFF:0051:0031:0303::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"8\">Arequipa<\/td><td rowspan=\"8\"><strong>3FFF:0051:0032::\/48<\/strong><\/td><td rowspan=\"4\">HFC Internet<\/td><td>Company<\/td><td><strong>3FFF:0051:0032:0101::\/64<\/strong><\/td><\/tr><tr><td>Government entity<\/td><td><strong>3FFF:0051:0032:0102::\/64<\/strong><\/td><\/tr><tr><td>Residential<\/td><td><strong>3FFF:0051:0032:0103::\/64<\/strong><\/td><\/tr><tr><td>NGO<\/td><td><strong>3FFF:0051:0032:0104::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"4\">GPON Internet<\/td><td>Company<\/td><td><strong>3FFF:0051:0032:0201::\/64<\/strong><\/td><\/tr><tr><td>Government entity<\/td><td><strong>3FFF:0051:0032:0202::\/64<\/strong><\/td><\/tr><tr><td>Residential<\/td><td><strong>3FFF:0051:0032:0203::\/64<\/strong><\/td><\/tr><tr><td>NGO<\/td><td><strong>3FFF:0051:0032:0204::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"3\">Cusco<\/td><td rowspan=\"3\"><strong>3FFF:0051:0033::\/48<\/strong><\/td><td rowspan=\"2\">GPON Internet<\/td><td>Company<\/td><td><strong>3FFF:0051:0033:0201::\/64<\/strong><\/td><\/tr><tr><td>Residential<\/td><td><strong>3FFF:0051:0033:0203::\/64<\/strong><\/td><\/tr><tr><td>Satellite Internet<\/td><td>NGO<\/td><td><strong>3FFF:0051:0033:0304::\/64<\/strong><\/td><\/tr><tr><td>Reserve blocks<\/td><td><strong>3FFF:0004::\/32 &#8211; 3FFF::0FFF::\/32<\/strong><\/td><td>Reserve IPv6 blocks<\/td><td>\/32<\/td><td>&#8211;<\/td><td>&#8211;<\/td><td>&#8211;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>IPv6 Address Plan for an End User (EU)<\/strong><\/li>\n<\/ul>\n\n\n\n<p>For an End User (EU) scenario, an example will be provided considering a university with three campuses. Values have been assigned and characters have been replaced based on the category they each represent, as shown in the following table.<\/p>\n\n\n\n<figure class=\"wp-block-table tabla\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Characters to be modified<\/strong><\/td><td><strong>Category<\/strong><\/td><td><strong>Values<\/strong><\/td><td><strong>Description<\/strong><\/td><\/tr><tr><td rowspan=\"3\">UUU<\/td><td rowspan=\"3\">Campus\/Location<\/td><td>001<\/td><td>Main campus<\/td><\/tr><tr><td>002<\/td><td>Secondary campus 1<\/td><\/tr><tr><td>003<\/td><td>Secondary campus 2<\/td><\/tr><tr><td rowspan=\"3\">EEE<\/td><td rowspan=\"3\">Building<\/td><td>111<\/td><td>Building 1<\/td><\/tr><tr><td>222<\/td><td>Building 2<\/td><\/tr><tr><td>333<\/td><td>Building 3<\/td><\/tr><tr><td rowspan=\"2\">SS<\/td><td rowspan=\"2\">Service<\/td><td>10<\/td><td>HFC Internet<\/td><\/tr><tr><td>20<\/td><td>GPON Internet<\/td><\/tr><tr><td rowspan=\"4\">F<\/td><td rowspan=\"4\">Faculty<\/td><td>1<\/td><td>Law<\/td><\/tr><tr><td>2<\/td><td>Medicine<\/td><\/tr><tr><td>3<\/td><td>Administration<\/td><\/tr><tr><td>4<\/td><td>Engineering<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>This is an example of what an IPv6 address plan for an End User would look like:<\/p>\n\n\n\n<figure class=\"wp-block-table tabla\" style=\"font-size:11px\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>IPv6 prefix<\/strong><\/td><td><strong>Campus\/Location<\/strong><\/td><td><strong>Prefix assigned to the campus [NET_ID]<\/strong><\/td><td><strong>Building<\/strong><\/td><td><strong>Subnet assigned to the building<\/strong><strong><\/strong> <strong>[Subnet]<\/strong><\/td><td><strong>Service<\/strong><\/td><td><strong>Faculty<\/strong><\/td><td><strong>Subnet assigned to the service and the faculty<\/strong><strong><\/strong> <strong>[Division]<\/strong><\/td><\/tr><tr><td rowspan=\"23\"><strong>3FFF::\/20<\/strong><\/td><td rowspan=\"12\">Main campus<\/td><td rowspan=\"12\"><strong>3FFF:0001::\/32<\/strong><\/td><td rowspan=\"6\">Building 1<\/td><td rowspan=\"6\"><strong>3FFF:0001:0111::\/48<\/strong><\/td><td rowspan=\"4\">HFC Internet<\/td><td>Law<\/td><td><strong>3FFF:0001:0111:0101::\/64<\/strong><\/td><\/tr><tr><td>Medicine<\/td><td><strong>3FFF:0001:0111:0102::\/64<\/strong><\/td><\/tr><tr><td>Administration<\/td><td><strong>3FFF:0001:0111:0103::\/64<\/strong><\/td><\/tr><tr><td>Engineering<\/td><td><strong>3FFF:0001:0111:0104::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"2\">GPON Internet<\/td><td>Law<\/td><td><strong>3FFF:0001:0111:0201::\/64<\/strong><\/td><\/tr><tr><td>Administration<\/td><td><strong>3FFF:0001:0111:0203::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"4\">Building 2<\/td><td rowspan=\"4\"><strong>3FFF:0001:0222::\/48<\/strong><\/td><td rowspan=\"4\">GPON Internet<\/td><td>Law<\/td><td><strong>3FFF:0001:0222:0201::\/64<\/strong><\/td><\/tr><tr><td>Medicine<\/td><td><strong>3FFF:0001:0222:0202::\/64<\/strong><\/td><\/tr><tr><td>Administration<\/td><td><strong>3FFF:0001:0222:0203::\/64<\/strong><\/td><\/tr><tr><td>Engineering<\/td><td><strong>3FFF:0001:0222:0204::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"2\">Building 3<\/td><td rowspan=\"2\"><strong>3FFF:0001:0333::\/48<\/strong><\/td><td rowspan=\"2\">GPON Internet<\/td><td>Law<\/td><td><strong>3FFF:0001:0333:0201::\/64<\/strong><\/td><\/tr><tr><td>Medicine<\/td><td><strong>3FFF:0001:0333:0202::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"6\">Secondary campus 1<\/td><td rowspan=\"6\"><strong>3FFF:0002::\/32<\/strong><\/td><td rowspan=\"4\">Building 1<\/td><td rowspan=\"4\"><strong>3FFF:0002:0111::\/48<\/strong><\/td><td rowspan=\"4\">HFC Internet<\/td><td>Law<\/td><td><strong>3FFF:0002:0111:0101::\/64<\/strong><\/td><\/tr><tr><td>Medicine<\/td><td><strong>3FFF:0002:0111:0102::\/64<\/strong><\/td><\/tr><tr><td>Administration<\/td><td><strong>3FFF:0002:0111:0103::\/64<\/strong><\/td><\/tr><tr><td>Engineering<\/td><td><strong>3FFF:0002:0111:0104::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"2\">Building 2<\/td><td rowspan=\"2\"><strong>3FFF:0002:0222::\/48<\/strong><\/td><td rowspan=\"2\">GPON Internet<\/td><td>Law<\/td><td><strong>3FFF:0002:0222:0201::\/64<\/strong><\/td><\/tr><tr><td>Medicine<\/td><td><strong>3FFF:0002:0222:0202::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"4\">Secondary campus 2<\/td><td rowspan=\"4\"><strong>3FFF:0003::\/32<\/strong><\/td><td rowspan=\"2\">Building 1<\/td><td rowspan=\"2\"><strong>3FFF:0003:0111::\/48<\/strong><\/td><td rowspan=\"2\">GPON Internet<\/td><td>Law<\/td><td><strong>3FFF:0003:0111:0201::\/64<\/strong><\/td><\/tr><tr><td>Administration<\/td><td><strong>3FFF:0003:0111:0203::\/64<\/strong><\/td><\/tr><tr><td rowspan=\"2\">Building 2<\/td><td rowspan=\"2\"><strong>3FFF:0003:0222::\/48<\/strong><\/td><td rowspan=\"2\">GPON Internet<\/td><td>Law<\/td><td><strong>3FFF:0003:0222:0201::\/64<\/strong><\/td><\/tr><tr><td>Administration<\/td><td><strong>3FFF:0003:0222:0203::\/64<\/strong><\/td><\/tr><tr><td>Reserve blocks<\/td><td><strong>3FFF:0004::\/32 &#8211; 3FFF::0FFF::\/32<\/strong><\/td><td>Reserve IPv6 blocks<\/td><td>\/32<\/td><td>&#8211;<\/td><td>&#8211;<\/td><td>&#8211;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusions<\/strong><\/h2>\n\n\n\n<p>An IPv6 address plan should be scalable, easy to understand, and facilitate network management. While there is no single way to create an IPv6 address plan, it is recommended to consider separating addresses by nibbles and assigning a function\/task to each nibble character. This will help keep everything in order during the assignment process throughout the operation of the network.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>References<\/strong><\/h2>\n\n\n\n<p>[1] <a href=\"https:\/\/blog.acostasite.com\/2018\/06\/concepto-que-es-un-plan-de.html?m=1\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/blog.acostasite.com\/2018\/06\/concepto-que-es-un-plan-de.html?m=1<\/a><\/p>\n\n\n\n<p><a href=\"https:\/\/datatracker.ietf.org\/doc\/rfc9637\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/datatracker.ietf.org\/doc\/rfc9637<\/a><\/p>\n\n\n\n<p>[2] LACNIC Podcast: <a href=\"https:\/\/www.youtube.com\/watch?v=lCFGwEjEoNk\" target=\"_blank\" rel=\"noreferrer noopener\">Ampliaci\u00f3n del espacio documentaci\u00f3n IPv6<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>By Alejandro Acosta, R&amp;D Coordinator, and Julio Buiza, Registration Services Specialist, at LACNIC Introduction On 23 July 2024, the IANA reserved 3FFF::\/20 as a new dedicated IPv6 address prefix for documentation purposes, thus adding a new block to the existing documentation block (2001:db8::\/32). This request was included in IETF draft https:\/\/datatracker.ietf.org\/doc\/draft-ietf-v6ops-rfc3849-update\/05\/ as follows: \u201cThe document [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":28794,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[531],"tags":[1304],"archivo":[1345,1451],"taxonomy-authors":[1248,1546],"tipo_autor":[],"class_list":["post-28804","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ipv6","tag-ipv6","archivo-editions","archivo-highlights-2023","taxonomy-authors-alejandro-acosta-en","taxonomy-authors-julio-buiza-en"],"acf":{"author":"","related_notes":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>LACNIC Blog | Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"LACNIC Blog | Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)\" \/>\n<meta property=\"og:description\" content=\"By Alejandro Acosta, R&amp;D Coordinator, and Julio Buiza, Registration Services Specialist, at LACNIC Introduction On 23 July 2024, the IANA reserved 3FFF::\/20 as a new dedicated IPv6 address prefix for documentation purposes, thus adding a new block to the existing documentation block (2001:db8::\/32). This request was included in IETF draft https:\/\/datatracker.ietf.org\/doc\/draft-ietf-v6ops-rfc3849-update\/05\/ as follows: \u201cThe document [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/\" \/>\n<meta property=\"og:site_name\" content=\"LACNIC Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/facebook.com\/lacnic\" \/>\n<meta property=\"article:published_time\" content=\"2025-02-06T15:52:53+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-02-11T15:27:47+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png\" \/>\n\t<meta property=\"og:image:width\" content=\"680\" \/>\n\t<meta property=\"og:image:height\" content=\"330\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Gianni\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@lacnic\" \/>\n<meta name=\"twitter:site\" content=\"@lacnic\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/\"},\"author\":{\"name\":\"Gianni\",\"@id\":\"https:\/\/blog.lacnic.net\/#\/schema\/person\/1338d9cfdb0137e8bc5581f3771f39ab\"},\"headline\":\"Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)\",\"datePublished\":\"2025-02-06T15:52:53+00:00\",\"dateModified\":\"2025-02-11T15:27:47+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/\"},\"wordCount\":1197,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/blog.lacnic.net\/#organization\"},\"image\":{\"@id\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png\",\"keywords\":[\"IPv6\"],\"articleSection\":[\"IPv6\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/\",\"url\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/\",\"name\":\"LACNIC Blog | Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)\",\"isPartOf\":{\"@id\":\"https:\/\/blog.lacnic.net\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png\",\"datePublished\":\"2025-02-06T15:52:53+00:00\",\"dateModified\":\"2025-02-11T15:27:47+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#primaryimage\",\"url\":\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png\",\"contentUrl\":\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png\",\"width\":680,\"height\":330},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Portada\",\"item\":\"https:\/\/blog.lacnic.net\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.lacnic.net\/#website\",\"url\":\"https:\/\/blog.lacnic.net\/\",\"name\":\"LACNIC Blog\",\"description\":\"En el Blog de LACNIC encontrar\u00e1s art\u00edculos t\u00e9cnicos vinculados al desarrollo de Internet en la regi\u00f3n de Am\u00e9rica Latina y el Caribe.\",\"publisher\":{\"@id\":\"https:\/\/blog.lacnic.net\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.lacnic.net\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.lacnic.net\/#organization\",\"name\":\"LACNIC Blog\",\"url\":\"https:\/\/blog.lacnic.net\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.lacnic.net\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2023\/03\/lacnic-blog.svg\",\"contentUrl\":\"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2023\/03\/lacnic-blog.svg\",\"caption\":\"LACNIC Blog\"},\"image\":{\"@id\":\"https:\/\/blog.lacnic.net\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/facebook.com\/lacnic\",\"https:\/\/x.com\/lacnic\",\"https:\/\/www.instagram.com\/lacnic\/?hl=es-la\",\"https:\/\/uy.linkedin.com\/company\/lacnic\",\"https:\/\/www.youtube.com\/user\/lacnicstaff\",\"https:\/\/www.lacnic.net\/podcast\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.lacnic.net\/#\/schema\/person\/1338d9cfdb0137e8bc5581f3771f39ab\",\"name\":\"Gianni\",\"url\":\"https:\/\/blog.lacnic.net\/en\/author\/gianni\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"LACNIC Blog | Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/","og_locale":"en_US","og_type":"article","og_title":"LACNIC Blog | Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)","og_description":"By Alejandro Acosta, R&amp;D Coordinator, and Julio Buiza, Registration Services Specialist, at LACNIC Introduction On 23 July 2024, the IANA reserved 3FFF::\/20 as a new dedicated IPv6 address prefix for documentation purposes, thus adding a new block to the existing documentation block (2001:db8::\/32). This request was included in IETF draft https:\/\/datatracker.ietf.org\/doc\/draft-ietf-v6ops-rfc3849-update\/05\/ as follows: \u201cThe document [&hellip;]","og_url":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/","og_site_name":"LACNIC Blog","article_publisher":"https:\/\/facebook.com\/lacnic","article_published_time":"2025-02-06T15:52:53+00:00","article_modified_time":"2025-02-11T15:27:47+00:00","og_image":[{"width":680,"height":330,"url":"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png","type":"image\/png"}],"author":"Gianni","twitter_card":"summary_large_image","twitter_creator":"@lacnic","twitter_site":"@lacnic","schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#article","isPartOf":{"@id":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/"},"author":{"name":"Gianni","@id":"https:\/\/blog.lacnic.net\/#\/schema\/person\/1338d9cfdb0137e8bc5581f3771f39ab"},"headline":"Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)","datePublished":"2025-02-06T15:52:53+00:00","dateModified":"2025-02-11T15:27:47+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/"},"wordCount":1197,"commentCount":0,"publisher":{"@id":"https:\/\/blog.lacnic.net\/#organization"},"image":{"@id":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png","keywords":["IPv6"],"articleSection":["IPv6"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/","url":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/","name":"LACNIC Blog | Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)","isPartOf":{"@id":"https:\/\/blog.lacnic.net\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#primaryimage"},"image":{"@id":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png","datePublished":"2025-02-06T15:52:53+00:00","dateModified":"2025-02-11T15:27:47+00:00","breadcrumb":{"@id":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#primaryimage","url":"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png","contentUrl":"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png","width":680,"height":330},{"@type":"BreadcrumbList","@id":"https:\/\/blog.lacnic.net\/en\/applying-the-new-ipv6-documentation-space-a-practical-approach-3fff-20\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Portada","item":"https:\/\/blog.lacnic.net\/en\/"},{"@type":"ListItem","position":2,"name":"Applying the New IPv6 Documentation Space: A Practical Approach (3FFF::\/20)"}]},{"@type":"WebSite","@id":"https:\/\/blog.lacnic.net\/#website","url":"https:\/\/blog.lacnic.net\/","name":"LACNIC Blog","description":"En el Blog de LACNIC encontrar\u00e1s art\u00edculos t\u00e9cnicos vinculados al desarrollo de Internet en la regi\u00f3n de Am\u00e9rica Latina y el Caribe.","publisher":{"@id":"https:\/\/blog.lacnic.net\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.lacnic.net\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/blog.lacnic.net\/#organization","name":"LACNIC Blog","url":"https:\/\/blog.lacnic.net\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.lacnic.net\/#\/schema\/logo\/image\/","url":"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2023\/03\/lacnic-blog.svg","contentUrl":"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2023\/03\/lacnic-blog.svg","caption":"LACNIC Blog"},"image":{"@id":"https:\/\/blog.lacnic.net\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/facebook.com\/lacnic","https:\/\/x.com\/lacnic","https:\/\/www.instagram.com\/lacnic\/?hl=es-la","https:\/\/uy.linkedin.com\/company\/lacnic","https:\/\/www.youtube.com\/user\/lacnicstaff","https:\/\/www.lacnic.net\/podcast"]},{"@type":"Person","@id":"https:\/\/blog.lacnic.net\/#\/schema\/person\/1338d9cfdb0137e8bc5581f3771f39ab","name":"Gianni","url":"https:\/\/blog.lacnic.net\/en\/author\/gianni\/"}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/blog.lacnic.net\/wp-content\/uploads\/2025\/02\/plan-direccionamiento-ipv4-ipv6-redes.png","jetpack_sharing_enabled":true,"wpml_current_locale":"en_US","wpml_translations":[{"locale":"es_ES","id":28781,"post_title":"Aplicando el nuevo espacio de documentaci\u00f3n IPv6: un enfoque pr\u00e1ctico (3FFF::\/20)","slug":"aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff-20","href":"https:\/\/blog.lacnic.net\/aplicando-el-nuevo-espacio-de-documentacion-ipv6-un-enfoque-practico-3fff-20\/"},{"locale":"pt_BR","id":28811,"post_title":"Aplicando o novo espa\u00e7o de Documenta\u00e7\u00e3o IPv6: Uma Abordagem Pr\u00e1tica (3FFF::\/20)","slug":"aplicando-o-novo-espaco-de-documentacao-ipv6-uma-abordagem-pratica-3fff-20","href":"https:\/\/blog.lacnic.net\/pt-br\/aplicando-o-novo-espaco-de-documentacao-ipv6-uma-abordagem-pratica-3fff-20\/"}],"_links":{"self":[{"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/posts\/28804","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/comments?post=28804"}],"version-history":[{"count":6,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/posts\/28804\/revisions"}],"predecessor-version":[{"id":28850,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/posts\/28804\/revisions\/28850"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/media\/28794"}],"wp:attachment":[{"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/media?parent=28804"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/categories?post=28804"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/tags?post=28804"},{"taxonomy":"archivo","embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/archivo?post=28804"},{"taxonomy":"taxonomy-authors","embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/taxonomy-authors?post=28804"},{"taxonomy":"tipo_autor","embeddable":true,"href":"https:\/\/blog.lacnic.net\/en\/wp-json\/wp\/v2\/tipo_autor?post=28804"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}