Re: [Int-area] Fw: Continuing IPv10 I-D discussion.

Tom Herbert <tom@herbertland.com> Fri, 31 March 2017 14:35 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B186129875 for <int-area@ietfa.amsl.com>; Fri, 31 Mar 2017 07:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 1lAvGlvtYSv1 for <int-area@ietfa.amsl.com>; Fri, 31 Mar 2017 07:35:11 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEA9012422F for <int-area@ietf.org>; Fri, 31 Mar 2017 07:35:11 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id i34so66906739qtc.0 for <int-area@ietf.org>; Fri, 31 Mar 2017 07:35:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=p6j9IZvyYxacDGm7mpA5mgTQY8GrMcFp9EEbcg+2hP4=; b=pXNyqqp8ajAHfDDz8ywEmt9OVmSM4BOLEkrrqMfQc7+2ZUvWj8i8GM9i5e6Oja2tcE g2RkmloOxF5pKE2Fy7bAsAMILntu0ngVaHBGBgNswLKqJgN8OIuF4k9NMEia+9pshvnj TYnnPQXZoEjvivSl59d3vX8J5TvtXkEDoSADUpprC8Nok9xjBHEo9t42VpDfRVqqxNtO ju2wZiLNoFzHUjO5MaHpELjGU2joIUEmUV3sFRryk37OTUb1FAHA5e1sRmiaTt9Bfwq5 5wkGbYdlgp29TFa3nAxFnrnx0C59eGzVKp2We/vTzLSbn+I+LdHB1DalRP+g/Hp97Nj3 7Pwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=p6j9IZvyYxacDGm7mpA5mgTQY8GrMcFp9EEbcg+2hP4=; b=dLVhABk4yEAhSzvAdOobcqTblQOdD5hKHzbyBwh/T3esJLcIz4EErVQgaVDBk1gMCR 2BXGrna6IUgvVwTZkekFGh6ttivjl865YF6jO5srIil72+b4Z2CDb09++ifJ+GqGkrue nvnzEZFo21EEJhM5V26+He1uLyOPSFHh4uIIMy1gYICP0x2FN5do17khR0mDBqN9P5MQ 7wm55nWGfL92IbtRsuX/F68PqmdCGI8t6KXj7wEERUi+2ckFiO9WropsHU2jtVEQKCEG 5TlOXAQMXWvp+5RJWnmXhz+au+m0gYa6/561qFs8BsycxOdn/W9NKoJMC4sKBEQAgzAW 1HTw==
X-Gm-Message-State: AFeK/H2i0Zjr5bmIyDDXHvRGjhrdLxjUNjbH/1T1wKmVOk2HjOVQWYY/yY3LgZXWZHqccsAxlDUwyfwW0kTt+g==
X-Received: by 10.237.40.66 with SMTP id r60mr3326708qtd.42.1490970910703; Fri, 31 Mar 2017 07:35:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.94.113 with HTTP; Fri, 31 Mar 2017 07:35:10 -0700 (PDT)
In-Reply-To: <AM4PR0401MB2241D2A7F373B24116E999BCBD370@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <D502B93A.74992%lee@asgard.org> <AM4PR0401MB224189BDD22CD327CF280AA3BD340@AM4PR0401MB2241.eurprd04.prod.outlook.com> <alpine.DEB.2.02.1703310806130.30226@uplift.swm.pp.se> <1d67d033-8a0f-c7eb-ae37-ec99f5a34660@kit.edu> <AM4PR0401MB2241FCE296DCD88D7D065520BD370@AM4PR0401MB2241.eurprd04.prod.outlook.com> <CALx6S35umePtAb-noP_CiXOh9Kf8j00oCVPSevci6EE9fyxTqQ@mail.gmail.com> <AM4PR0401MB2241D2A7F373B24116E999BCBD370@AM4PR0401MB2241.eurprd04.prod.outlook.com>
From: Tom Herbert <tom@herbertland.com>
Date: Fri, 31 Mar 2017 07:35:10 -0700
Message-ID: <CALx6S34h4UbctQOZ6MnByN+7zkr-i-oxwnrXFKGqS1YC8pxL4A@mail.gmail.com>
To: Khaled Omar <eng.khaled.omar@hotmail.com>
Cc: "int-area@ietf.org" <int-area@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/_I3yFWgwZ2I1h28-7T8j-OMaZf0>
Subject: Re: [Int-area] Fw: Continuing IPv10 I-D discussion.
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Mar 2017 14:35:18 -0000

On Fri, Mar 31, 2017 at 7:24 AM, Khaled Omar
<eng.khaled.omar@hotmail.com> wrote:
>> "all OSs will be updated to support IPv10 which is an easy task"...
>>>What makes you think it is ever an easy task to get all OSes to uniformly support anything? Please provide an implementation so we can evaluate the prospects.
>
> For the 2nd time:
>
> "I shouldn't list all devices that need to support IPv10, simply, anything will process a L3 packet, should understand that the IPv10 packet can contain a mixture of IPv4 and IPv6 addresses."
>
I don't know what "anything will process an L3 packet" means. Please
answer directly: does this proposal need changes in every OS or not?

>
> -----Original Message-----
> From: Tom Herbert [mailto:tom@herbertland.com]
> Sent: Friday, March 31, 2017 4:19 PM
> To: Khaled Omar
> Cc: Bless, Roland (TM); int-area@ietf.org
> Subject: Re: [Int-area] Fw: Continuing IPv10 I-D discussion.
>
> On Fri, Mar 31, 2017 at 5:13 AM, Khaled Omar <eng.khaled.omar@hotmail.com> wrote:
>>> As has been stated again and again. Your proposal would have been interesting if it was presented in 1995, or perhaps even in 2000.
>>
>> FYI, IPv10 will allow IPv4 to communicate to IPv6 and vice versa, how can it be interesting if it was presented before IPv6 was even developed !
>>
>>> Most likely, even if Microsoft could be convinced that IPv10 is something they need to support, this would only happen in Windows 10. Then we have the rest of the ecosystem with access routers, load balancers, SAVI-functionality for BCP38 compliance in access devices, core routers etc.
>>
>> Please, let's not be against ourselves, all OSs will be updated to support IPv10 which is an easy task, OSs will not require support for a new IP version like IPv6, they will just be enabled to support the encapsulation of both version on the same L3 packet header.
>
> "all OSs will be updated to support IPv10 which is an easy task"...
> What makes you think it is ever an easy task to get all OSes to uniformly support anything? Please provide an implementation so we can evaluate the prospects.
>
> Tom
>
>>
>> Also, networking devices will be upgraded to understand the new IPv10 packet, I said earlier I don't mind If the process will take some time but we should eventually reach consensus, I shouldn't list all devices that need to support IPv10, simply, anything will process a L3 packet, should understand that the IPv10 packet can contain a mixture of IPv4 and IPv6 addresses.
>>
>>
>> -----Original Message-----
>> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Bless,
>> Roland (TM)
>> Sent: Friday, March 31, 2017 9:51 AM
>> To: Mikael Abrahamsson
>> Cc: int-area
>> Subject: Re: [Int-area] Fw: Continuing IPv10 I-D discussion.
>>
>> Hi Mikael,
>>
>> thanks for clarifying again, everything +1!
>>
>> Regards,
>>  Roland
>>
>> Am 31.03.2017 um 08:17 schrieb Mikael Abrahamsson:
>>> On Thu, 30 Mar 2017, Khaled Omar wrote:
>>>
>>>>  You can read the IPv10 I-D again and all your concerns will be
>>>> obvious, I don't mind if you have already a series of new questions
>>>> that will add a new value to the discussion but the time to deploy
>>>> IPv10 is an important factor.
>>>>
>>>> We need consensus after understanding how IPv10 works and how it
>>>> will be deployed.
>>>
>>> As has been stated again and again. Your proposal would have been
>>> interesting if it was presented in 1995, or perhaps even in 2000.
>>>
>>> Let me give you an IPv6 deployment timeline:
>>>
>>> Standards were worked out in the mid 90-ties, afterwards operating
>>> system vendors started working on it and "real" support started
>>> cropping up in the early to mid 2000:nds, with a large milestone
>>> being Windows Vista in 2006, where as far as I know this was the
>>> first widely used consumer operating system to implement this. It
>>> then took until Windows
>>> 7 timeframe around 2010 before people started moving off of Windows
>>> XP in ernest, and we're still seeing Windows XP in non-trivial numbers.
>>> So now in 2017 we're seeing most operating systems have comprehensive
>>> (albeit perhaps not as well-tested as we would like) support for
>>> IPv6, where the application ecosystem still has a way to go. We're
>>> still working on better APIs to handle the dual-stackedness problem.
>>>
>>> Most likely, even if Microsoft could be convinced that IPv10 is
>>> something they need to support, this would only happen in Windows 10.
>>> Then we have the rest of the ecosystem with access routers, load
>>> balancers, SAVI-functionality for BCP38 compliance in access devices,
>>> core routers etc. Most of these will require a hardware fork-lift in
>>> order to support your proposal, because they do not forward packets
>>> in a CPU, they forward it in purpose-designed hardware that is a lot
>>> less flexible in what they can do.
>>>
>>> So even if we all united now (which won't happen) around your IPv10
>>> proposal, it would take 5-10 years before the first devices out on
>>> the market had support for it. Probably 5-10 years after that before
>>> support is widely available.
>>>
>>> IPv10 would delay and confuse deployment of something that is not IPv4.
>>> While IPv6 is not perfect, there are now hundreds of millions of
>>> devices on the Internet with IPv6 access. It's proven to work, it's
>>> not perfect, but we have a decently good idea what to do to make it better.
>>>
>>> IPv10 is only injecting FUD into where we need to go debate, which is
>>> IPv6 deployment for all.
>>>
>>> Please stop.
>>
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
>>
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area