From 489254bccd92ee60b95f2b9131378e6fee1d33dd Mon Sep 17 00:00:00 2001 From: Michael Dopheide Date: Thu, 11 Apr 2024 17:58:53 -0500 Subject: [PATCH] just grammatical changes here --- 8. Deployment Status/Deployment by carriers.md | 4 ++-- 8. Deployment Status/Deployment in the enterprise.md | 10 +++++----- 8. Deployment Status/Status.md | 4 ++-- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/8. Deployment Status/Deployment by carriers.md b/8. Deployment Status/Deployment by carriers.md index c16834a..600a77a 100644 --- a/8. Deployment Status/Deployment by carriers.md +++ b/8. Deployment Status/Deployment by carriers.md @@ -9,7 +9,7 @@ the world, as observed in the Internet routing tables. Table shows 18% annual IPv6 growth 2018 to 2022 The percentage of IPv6-capable ASNs is growing over the years, which is -a good sign. On the other hand, the table does not allow to understand +a good sign. On the other hand, the table does not distinguish the degree of adoption across the different industries, that is whether the ASNs are associated to a carrier, a service provider or an entreprise. To zoom in at that level, it is necessary to look at more @@ -26,7 +26,7 @@ Comcast, T-Mobile and Verizon all exceed 70% of IPv6 use in their networks. In Europe, both Belgium and Germany reach 50% of IPv6 traffic. Proximus, Telenet, DT, Telefonica Germany, Versatel and Vodafone Germany range from 50% to 70%. India shows 51% IPv6 adoption. Carriers there -also have high IPv6 rate. Bharti, Reliance Jio and Vodafone India find +also have a high IPv6 rate. Bharti, Reliance Jio and Vodafone India find themselves between 60% and 70%. Whilst it cannot be gneralized, in countries with lower IPv6 adoption diff --git a/8. Deployment Status/Deployment in the enterprise.md b/8. Deployment Status/Deployment in the enterprise.md index 38a4407..24ee44e 100644 --- a/8. Deployment Status/Deployment in the enterprise.md +++ b/8. Deployment Status/Deployment in the enterprise.md @@ -7,14 +7,14 @@ IPv6 readiness from outside the enterprise's network. [NIST](https://fedv6-deployment.antd.nist.gov/cgi-bin/generate-com) provides a method to infer whether US enterprises support IPv6 by checking its external services, such as the availability of Domain Name -System (DNS) AAAA records, of an IPv6-based mail service and of the +System (DNS) AAAA records, an IPv6-based mail service, or the support of IPv6 on their website. The same method can be applied to [Chinese](http://218.2.231.237:5001/cgi-bin/generate) and [Indian](https://cnlabs.in/IPv6_Mon/generate_industry.html) enterprises. DNS has a good support in all cases: more than 50% of the enterprises in the three economies considered have AAAA records, a sign that IPv6 -support is generally available. The same cannot be said or the other +support is generally available. The same cannot be said of the other services that have much lower adoption. \[[RFC9386](https://www.rfc-editor.org/info/rfc9386)\] provides other statistics about more specific industry domains. @@ -41,8 +41,8 @@ resources will be organizational size. The size of a given organization often (but not always) dictates the criticality of networking resources which includes both physical assets (routers, switches, security appliances) as well as human resources, and the level of skill available -either by direct employment or by contacted assistance. Also included in -these resources is the logical elements requires for a presence on the +either by direct employment or by contracted assistance. Also included in +these resources is the logical elements required for a presence on the global internet in the manner of addressing. Larger or more mature organizations may already posses network resources such as Autonomous System Numbers (ASNs), legacy IP resources, and possibly existing @@ -92,7 +92,7 @@ Provider Assigned (PA) address space consists of address space that is assigned to a specific upstream provider and sub-delegated to a customer. -If receiving PA from an upstream provider designs such as multihoming is +If receiving PA from an upstream provider, designs such as multihoming is a more involved process that will involve coordination with the upstream transit provider that owns the IP resources. (See \[[6. Multi-prefix operation](../6.%20Management%20and%20Operations/Multi-prefix%20operation.md)\] diff --git a/8. Deployment Status/Status.md b/8. Deployment Status/Status.md index 36d7132..b79a6d7 100644 --- a/8. Deployment Status/Status.md +++ b/8. Deployment Status/Status.md @@ -48,8 +48,8 @@ There is a caveat, though, we may want to consider. The method used by APNIC cannot be fully employed in China, due to local policy filtering traffic from abroad. An independent [Chinese research](https://www.china-ipv6.cn/#/activeconnect/simpleInfo) -reports 713 millions measured IPv6 customers as of September 2022, -against the 220 reported by APNIC. If we add the difference between the +reports 713 million measured IPv6 customers as of September 2022, +against the 220 million reported by APNIC. If we add the difference between the two statistics to the global count, we end up with a Ratio of 43.68% in September 2022, not that far from the "psychological" threshold of 50%.