Re: [v6ops] IPv10 Discussion in v6ops

Tom Herbert <tom@herbertland.com> Mon, 14 September 2020 15:06 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C123A0937 for <v6ops@ietfa.amsl.com>; Mon, 14 Sep 2020 08:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 QFKV4jKA6gZa for <v6ops@ietfa.amsl.com>; Mon, 14 Sep 2020 08:06:25 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 DC6443A0989 for <v6ops@ietf.org>; Mon, 14 Sep 2020 08:06:24 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id e22so7432861edq.6 for <v6ops@ietf.org>; Mon, 14 Sep 2020 08:06:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=sCUHos/DwU4KVDUIq2T91DNBsaPhtvIxPzeAPz/fGcQ=; b=YPd8+nOoRCfL2UqW6cNrjl/dzt4eMPGMzzSMN/52auO2u8cdVcFU2d6TPA8ys6Fiwh RTh1dOzuXgXjY/Oj4Zi/EKrsJ8AJRlyjAwre77iiqiLQ9DYpDUQpGyKQbiLdcsx2Y2S7 B1HUl62zwE2U/K9usG1CsoehRDXHbSJEasip76Kd3LXlrc46UfGiokLeGp1Yf1lo4DKm WAGE48DHUNoTILBZ4fxXiSszEj4RtdMvGRLFD3Obi9EFHQ3DGJQpetYk+8h6d201cPoe NvMi1GjrFOCSn6EZUpDi2D3JdaeOwX4ANJpr5d7MofFw7n9GWx4hdk0CB4kcN3DSVqMO Xudg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=sCUHos/DwU4KVDUIq2T91DNBsaPhtvIxPzeAPz/fGcQ=; b=dbAQ3CvFcpHEgaj65Qj/HtkM5qbr4MKDrDeiN2hygg0x6iPnfxLYmNXs0/gSrsELyz 8qUBL3ebFh0/0eeBpz3r5f+meuuhsWXXjEpO3bX9qb+I8IzQZMWhkf3Bc8GQuJXiK0ik HXkamM7ascug01w/6iY2PSe13XXGSbZmTBP/svlvInXC0AGSXBueugSAD6S54mMz13R3 wSSkH85Fi8FWOcF5xflPe14ho4+JZ/wKk9UcJmgQ1sxlT5kLLFpMu5vU0tBluXGUuOCK c0B0r9sVjj54hf0MCIZ7Qw8mJI41w6brthY5hJJpgESKvx1EUB88Pya4SxGiv2Sr7Ot0 Ug0Q==
X-Gm-Message-State: AOAM5321rNGou0ftfKDAFSfc/8tm7h9TtDeC4dHBLKGw4nXVDmPXJ8YE KSrxKl5qKjDNnliEUa+i9Rvhc2YbtCjejuqwH1ndRQ==
X-Google-Smtp-Source: ABdhPJxcNW2ED/Q2Wof4G1Lh2gpeD9neEIZuLGsR+/36KDJ2BspRNd279eyqUsKOhpu96kdeSHC8d5oCqzOqJD8e/kg=
X-Received: by 2002:a05:6402:456:: with SMTP id p22mr17429026edw.177.1600095983174; Mon, 14 Sep 2020 08:06:23 -0700 (PDT)
MIME-Version: 1.0
References: <159985752195.15551.2657932726923781035@ietfa.amsl.com> <VI1P194MB0285E344B7B3E9697E6ED608AE240@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <3FA82C44-0005-45BA-AB09-FAE63C8CD626@gmail.com> <VI1P194MB028561F81F5118ABC14967DFAE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <3B5995B1-CD7A-444C-AD64-37C09E46A763@thehobsons.co.uk> <4fa01d01-bc2e-0f01-77f1-13dd4f6f2430@hit.bme.hu> <VI1P194MB0285FCDBFB6A86DF954D1782AE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <e0e4e5cf-1563-fca1-1388-68c8789384de@nlogic.no> <VI1P194MB0285090A6E66464C9612EE34AE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
In-Reply-To: <VI1P194MB0285090A6E66464C9612EE34AE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
From: Tom Herbert <tom@herbertland.com>
Date: Mon, 14 Sep 2020 09:06:12 -0600
Message-ID: <CALx6S34vq97MQC3jfbtf0b7jJa1g4U2tGS9BYE9djjBa3f97PQ@mail.gmail.com>
To: Khaled Omar <eng.khaled.omar@outlook.com>
Cc: Ola Thoresen <ola@nlogic.no>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Z-c-rZqzJLSX54kez_U4ARLxuFo>
Subject: Re: [v6ops] IPv10 Discussion in v6ops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Sep 2020 15:06:27 -0000

On Mon, Sep 14, 2020 at 8:24 AM Khaled Omar <eng.khaled.omar@outlook.com> wrote:
>
> >> You say this is not a new protocol, but you still specify a header format in section 4 of your draft.
>
> The discussion will keep repeating if the ietf will not show a different solution to the community that suffers now from the depletion of IPv4.
>
Khaled,

The draft was already thoroughly discussed in int-area back in 2017
(there were at least three threads). There was a pretty clear
consensus that IETF should not work on it. For instance, my opinion
from Oct. 4, 2017 was:

"The draft and the concept have been thoroughly discussed on int-area
list (twice). I don't see that the problem is worth solving, the
proposed solution is remotely feasible, or that the author is willing
to apply feedback from the discussion."

What has changed since 2017 that would make it productive to revisit
this proposal again?

Tom


> Regarding the new packet header, users will not have a problem with it, its migration from v4 packet to v10 packet, that’s all.
>
> Khaled Omar
>
> -----Original Message-----
> From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Ola Thoresen
> Sent: Monday, September 14, 2020 4:20 PM
> To: v6ops@ietf.org
> Subject: Re: [v6ops] IPv10 Discussion in v6ops
>
> Khaled:
>
> You have promoted this discussion again and again over many years, yet you do not listen to any of the objections that people have.
>
> You say this is not a new protocol, but you still specify a header format in section 4 of your draft.
>
> You then state in section 5.2 that:
>
> 5. Advantages of IPv10.
>
>      2) Allows IPv4 only hosts to exist and communicate with IPv6 only
>         hosts even after the depletion of the IPv4 address space.
>
> But this is an obvious lie.
>
> What this "IPv10" allows, is for "IPv10" hosts to talk to other "IPv10"
> hosts if ALL of the routers on the internet between those two hosts also are "IPv10" enabled.
>
> That is NOT the same as allowing IPv4 _only_ hosts to talk to IPv6 _only_ hosts.  They both need to actively talk and understand this "IPv10" protocol and header format. You clearly do not grasp this, but this is the big issue with your draft.  You ARE suggesting that every single host on the internet should add another protocol to its stack, and you even believe that this can happen very fast:
>
>
>      5) IPv10 support on "all" Internet connected hosts can be deployed
>         in a very short time by technology companies developing OSs
>         (for hosts and networking devices, and there will be no
>         dependence on enterprise users and it is just a software
>         development process in the NIC cards of all hosts to allow
>         encapsulating both IPv4 and IPv6 in the same IP packet header.
>
>
> While we are still struggling to get lots of devices to support IPv6, which has been in development and widely supported in operating systems and hardware for more than a decade.
> So please. Until you understand what you are really trying to achieve here, do not expect any progress in getting this accepted by the community - and especially not the IPv6 community.
>
>
> Rgds.
>
> /Ola (T)
>
>
> On 14.09.2020 15:55, Khaled Omar wrote:
> > Hi,
> >
> > Don't copy the opinion that was mentioned there, use your own mind and give a clear opinion to make the discussion beneficial.
> >
> > Maybe they have their own reasoning.
> >
> > Best regards,
> >
> > Khaled Omar
> >
> > -----Original Message-----
> > From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Lencse Gábor
> > Sent: Monday, September 14, 2020 3:52 PM
> > To: v6ops@ietf.org
> > Subject: Re: [v6ops] IPv10 Discussion in v6ops
> >
> > Simon, you are completely right: this thing has already been discussed
> > on int-area mailing list in 2017. It was pointed out that the name was
> > misleading, as well as that this solution was not at all viable as an
> > IPv6 transition mechanism.
> >
> > I do not see any reason to reiterate the topic on this mailing list.
> >
> > Best regards,
> >
> > Gábor
> >
> > 14/09/2020 15:09 keltezéssel, Simon Hobson írta:
> >> Khaled Omar <eng.khaled.omar@outlook.com> wrote:
> >>
> >>>> Is it possible to reserve a slot for the IPv10 I-D to be presented completely during the v6ops wg meeting session?
> >>>>
> >>>> https://tools.ietf.org/html/draft-omar-ipv10-06
> >> I only had a quick look, but doesn't this just re-hash discussions/documentation that's already been done elsewhere ?
> >> Also, I think calling it IPv10 is just asking to cause confusion - it
> >> should be rejected just for that ;-)
> >>
> >> Simon
> >>
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops