Re: [arch-d] ipv4 and ipv6 Coexistence.
Toerless Eckert <tte@cs.fau.de> Tue, 25 February 2020 20:46 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 106183A157F for <architecture-discuss@ietfa.amsl.com>; Tue, 25 Feb 2020 12:46:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FAR4CFpioQCk for <architecture-discuss@ietfa.amsl.com>; Tue, 25 Feb 2020 12:46:13 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E9983A15AC for <architecture-discuss@ietf.org>; Tue, 25 Feb 2020 12:46:13 -0800 (PST)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 207D4548048; Tue, 25 Feb 2020 21:46:08 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 1A483440040; Tue, 25 Feb 2020 21:46:08 +0100 (CET)
Date: Tue, 25 Feb 2020 21:46:08 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Guntur Wiseno Putra <gsenopu@gmail.com>
Cc: Khaled Omar <eng.khaled.omar@outlook.com>, Mark Andrews <marka@isc.org>, "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>
Message-ID: <20200225204608.GI39574@faui48f.informatik.uni-erlangen.de>
References: <PR3P194MB0843ACAE01F33CEC57266A1AAE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <EDAE6375-EE0B-4864-9834-C1FBC209D581@sobco.com> <PR3P194MB08431E138262F2A43C1D0621AE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <8ADEA0E1-291A-4400-9925-F65A26116372@consulintel.es> <PR3P194MB0843939F3B38426960A66E70AE130@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <D8063303-7DDA-41F8-A63A-C0244E3E9E25@isc.org> <20200224222715.GA49892@faui48f.informatik.uni-erlangen.de> <CAKi_AEuqn0NPiSqzrD4fn_mW1GJCOnh6aeG_DH7t_mmFH=8Dtw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAKi_AEuqn0NPiSqzrD4fn_mW1GJCOnh6aeG_DH7t_mmFH=8Dtw@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/-aqOzU32pygdomaxCrBIwLkgfaA>
Subject: Re: [arch-d] ipv4 and ipv6 Coexistence.
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2020 20:46:22 -0000
Guntur: That URL takes me to an SSO login on internetsociety.org. Is that correct ? Internetsociety hosts walled garden content ? I am puzzled. With the title i found this: https://www.hstoday.us/subject-matter-areas/cybersecurity/adopting-and-enforcing-an-ipv6-only-policy-if-not-now-when/ Is that what you wanted to point to ? Cheers Toerless On Tue, Feb 25, 2020 at 02:47:33PM +0700, Guntur Wiseno Putra wrote: > Dear Toerless and > architecture-discuss, > > To inform that there is a post on IPv6 yesterday at the Open Forum's > Discussion of the Internet Society: > > "Adopting and Enforcing an IPv6-Only Policy: If Not Now, When"? > > by Charles Sun > > > > https://connect.internetsociety.org/communities/community-home/digestviewer/viewthread?MessageKey=f2844839-3d7d-40e2-b7ab-e4b0c1562de8&CommunityKey=3a9fa082-a518-475d-9e7f-ecec4ffe56dd&tab=digestviewer#bmf2844839-3d7d-40e2-b7ab-e4b0c1562de8 > > > > Regard, > Guntur Wiseno Putra > > Pada Selasa, 25 Februari 2020, Toerless Eckert <tte@cs.fau.de> menulis: > > > [Bcc ietf@ietf.org, Cc: architecture-discuss@ietf.org] > > > > Mark: > > > > Funny to see how yours is the first actual answer to at least how i read > > Khaleds question. I would summarize what you said with: > > > > https://en.wikipedia.org/wiki/IPv6_transition_mechanism > > > > (14 standardized plus a lot more. Aka: thank you, but we have enough) > > > > Most everybody else jumps to the growth of the IPv6 Internet, which > > to me is just the visible tip of the iceberg of overall IPv4 and IPv6 > > deployments. I think the picture changes quite a bit if we look at the > > whole iceberg. > > > > In private / controlled networks, the choices are not only IPv4 vs. > > IPv6 or their interop, but also (SR-)MPLS and even more so L2 ethernet > > switching. > > > > For all intent and purpose, Internet IPv6 vs. Internet IPv4 could soon > > be software-only overlay virtual networks whereas the actual > > terrabit accelerated hardware forwarding plane of future networks > > maybe something else. 4G/5G "core" "network" already are such > > overlay networks. > > > > [Rant] > > I am not sure if the question, as constrained as Khaled is asking > > it will really help us to improve what we should do in the future. But > > neither is the defensive reaction of IPv6 evangelists pointing at the > > growth curve of the IPv6 Internet as the only relevant metric to the > > success and benefits of IPv6. > > > > I am primarily concerned that we did manage to recognize we needed > > disruptive innovartion in the 90th, when we came up with IPv6, but > > now the predominant religion seems to be being stuck in small > > incremental enhancements of that 25 year old architecture, especially > > because its bible (RFC8200) did only think of the IPv6 Internet use-case > > requirements, but not those of private/controlled networks. > > [/Rant] > > > > Cheer > > Toerless > > > > On Thu, Feb 20, 2020 at 12:26:28PM +1100, Mark Andrews wrote: > > > Really we do not need to be inventing anything new in this space. > > > We already have too many mechanisms. ISPs just need to DEPLOY the > > > existing mechanism. > > > > > > We have plain dual stack. > > > > > > We have public IPv4 + 6rd for ISPs where the access network doesn???t > > > support IPv6. > > > > > > We have CGN + 6RD + 100.64/10 for ISPs where the access network doesn???t > > > support IPv6 and they have run out of IPv4 space. > > > > > > We have DS-Lite, MAP-E, MAP-T, NAT64 ??? providing IPV4AAS for when the > > ISP > > > has run out of IPv4 and the access network supports IPv6. > > > > > > We have CGN + IPv6. > > > > > > Do we really need something more at the protocol level? > > > > > > We do need Governments to ban the selling of new IPv4-only domestic > > > devices (CPE routers, TV???s, game boxes, etc.). > > > > > > Mark > > > > > > > On 20 Feb 2020, at 11:32, Khaled Omar <eng.khaled.omar@outlook.com> > > wrote: > > > > > > > > Regardless the different %s, lets take the average one, it can not > > make us optimistic and stop thinking about a better solution, we should > > learn from the long time passed without full migration occured, if we will > > wait till that happens, the division will occur which is not good for the > > internet, lets welcome new ideas and give it the space, time, and > > opportunity fairly, if it will be good then welcome, if not, trash is made > > for this. > > > > > > > > Get Outlook for Android > > > > > > > > From: ietf <ietf-bounces@ietf.org> on behalf of JORDI PALET MARTINEZ > > <jordi.palet=40consulintel.es@dmarc.ietf.org> > > > > Sent: Thursday, February 20, 2020 2:00:58 AM > > > > To: IETF Rinse Repeat <ietf@ietf.org> > > > > Subject: Re: ipv4 and ipv6 Coexistence. > > > > > > > > And you're missing several points about how those stats are looked at.. > > > > > > > > The % in the stats shown by google/others is only what they can > > measure, but they can't measure *all*. There are countries (big ones) that > > don't allow measurements, or at least the same level of details, and > > however, are doing massive IPv6 deployments. > > > > > > > > All the CDNs and caches have IPv6. The customers that have those > > caches and enable IPv6 for their subscribers, are getting ranges over 65%, > > sometimes even up to 85-90% of IPv6 traffic when mainly the subscribers are > > householders instead of big enterprises. > > > > > > > > Also, the google (and others) measurements, show average worldwide, > > but if you look to many countries they have even surpassed the 50% or so. > > > > > > > > Regards, > > > > Jordi > > > > @jordipalet > > > > > > > > > > > > > > > > ???El 20/2/20 5:38, "ietf en nombre de Khaled Omar" < > > ietf-bounces@ietf.org en nombre de eng.khaled.omar@outlook.com> escribió: > > > > > > > > Since long time I was observing this, still almost the same, no > > clear progress occurred. > > > > > > > > Thanks, > > > > > > > > Khaled Omar > > > > > > > > -----Original Message----- > > > > From: Scott O. Bradner <sob@sobco.com> > > > > Sent: Wednesday, February 19, 2020 8:11 PM > > > > To: Khaled Omar <eng.khaled.omar@outlook.com> > > > > Cc: IETF Rinse Repeat <ietf@ietf.org> > > > > Subject: Re: ipv4 and ipv6 Coexistence. > > > > > > > > Quite a few folk are already there - see > > https://www.google.com/intl/en/ipv6/statistics.html > > > > > > > > Scott > > > > > > > > > > > > > > > > > > > > > > > > ********************************************** > > > > IPv4 is over > > > > Are you ready for the new Internet ? > > > > http://www.theipv6company.com > > > > The IPv6 Company > > > > > > > > This electronic message contains information which may be privileged > > or confidential. The information is intended to be for the exclusive use of > > the individual(s) named above and further non-explicilty authorized > > disclosure, copying, distribution or use of the contents of this > > information, even if partially, including attached files, is strictly > > prohibited and will be considered a criminal offense. If you are not the > > intended recipient be aware that any disclosure, copying, distribution or > > use of the contents of this information, even if partially, including > > attached files, is strictly prohibited, will be considered a criminal > > offense, so you must reply to the original sender to inform about this > > communication and delete it. > > > > > > > > > > > > > > > > > > -- > > > Mark Andrews, ISC > > > 1 Seymour St., Dundas Valley, NSW 2117, Australia > > > PHONE: +61 2 9871 4742 INTERNET: marka@isc.org > > > > _______________________________________________ > > Architecture-discuss mailing list > > Architecture-discuss@ietf.org > > https://www.ietf.org/mailman/listinfo/architecture-discuss > > > _______________________________________________ > Architecture-discuss mailing list > Architecture-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/architecture-discuss -- --- tte@cs.fau.de
- Re: [arch-d] ipv4 and ipv6 Coexistence. Toerless Eckert
- Re: [arch-d] ipv4 and ipv6 Coexistence. Guntur Wiseno Putra
- Re: [arch-d] ipv4 and ipv6 Coexistence. Fred Baker
- Re: [arch-d] ipv4 and ipv6 Coexistence. Brian E Carpenter
- Re: [arch-d] ipv4 and ipv6 Coexistence. Toerless Eckert
- Re: [arch-d] ipv4 and ipv6 Coexistence. Toerless Eckert
- Re: [arch-d] ipv4 and ipv6 Coexistence. Guntur Wiseno Putra
- Re: [arch-d] ipv4 and ipv6 Coexistence. Guntur Wiseno Putra
- Re: [arch-d] ipv4 and ipv6 Coexistence. heinerhummel
- Re: [arch-d] ipv4 and ipv6 Coexistence. heinerhummel
- Re: [arch-d] ipv4 and ipv6 Coexistence. Stewart Bryant
- Re: [arch-d] ipv4 and ipv6 Coexistence. Stewart Bryant
- Re: [arch-d] ipv4 and ipv6 Coexistence. Stewart Bryant
- Re: [arch-d] ipv4 and ipv6 Coexistence. Stephen Farrell
- Re: [arch-d] ipv4 and ipv6 Coexistence. Vittorio Bertola
- Re: [arch-d] ipv4 and ipv6 Coexistence. FREDERICK BAKER
- Re: [arch-d] ipv4 and ipv6 Coexistence. Toerless Eckert
- Re: [arch-d] ipv4 and ipv6 Coexistence. Toerless Eckert
- Re: [arch-d] ipv4 and ipv6 Coexistence. Guntur Wiseno Putra
- Re: [arch-d] ipv4 and ipv6 Coexistence. Guntur Wiseno Putra