Re: [v6ops] IPv10 Discussion in v6ops

Khaled Omar <> Mon, 14 September 2020 14:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 13C903A0A3F for <>; Mon, 14 Sep 2020 07:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ll4XP6ngmWAt for <>; Mon, 14 Sep 2020 07:23:48 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2D3F13A0A3D for <>; Mon, 14 Sep 2020 07:23:48 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=VFbPQ8qg3SifvgPmWw6at13JlDzR9pT7Z3DMmwPBmbKt063xQo/gtiWpgIX+xX4ReV80uhoJ0PjbA7y2givHkzo5xjwvr5EULRZ1RYZA9Ri9dr2uiOPg3ksxiIMeowUVSaJ14bwKXCG1QkWfiAYl0I8UBxY+N5dWv4twwYCKzf5eD9J5dEd+RhnVqPsdu0Rqb5lEsXR66lIOKu+2orzGx3YHFXCgCcEbimZKJQpY4DLNeTYryPY9xMmYVTd+7zvKVfmSo5HcneEi/CTV6wfkWnGADX7j79oDV/gb5aA8X8Ufqh3KexoY3/jBky+rMmxa3DW0GbHt0qkURVCym8e0DQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OVClbyl7zhgHiEvYgP03+WoHFDix/HwBIvKA9hjAjmo=; b=H8gxDcwYCuN4PhRXqvVK9kjksksNs4O5TztfdjOivNzKg0Xw49hv+V+7Gf00tB9+glrGhMIguiOTpAuxxJp5Ti8WpnXJbL9VzdRBiLgWrYcu1xd4d+07GtEzFv6ccBkfFtOWTsqAkdxEz5Fs3rEA3kn8OmnFW6bX8tYJx1+hIyhz7m/7WhQwcE5P6RENliyUGZ4Y6Aj9OGvwvSThj25iQTu0SJ0a/SOt7gsP5EpK4m/y5oRjjpfPjP6NZVxOPk3mtpZfULg4C2ysRWobPqsUKEqjMtS42B7rx9bq8Vw5E3LYVs3NXIR98j9KeZPGhDFQhSGn57oNT2uZROKU5dvHHA==
ARC-Authentication-Results: i=1; 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OVClbyl7zhgHiEvYgP03+WoHFDix/HwBIvKA9hjAjmo=; b=MVAhJdK7BLWll8YB4u8erBbH8xTU9Ru2yW1rxse/01a/YQXdso5wgbDi3DUPYV++oUl6oJO2m7T6NzrjtodeF3xn9mN4z+zdFEbB3sYoAOKB7pzIMj9cK6H7zpIXe2QbfNDacAcgSxTCE2USuARQC59jX5AFuYdNn6sDjpcCq6mOk82JCngZnQZY+AObefgtbyil+20VUiFxsOY77NsmI0/fQIQky99txp5oAVBhPFkHQZuow+g/y7jORLbAJg8KquSnRpFoJClzFaeEdi6M+gPERolQOvYK8zKsPvbP6Gqqhd0Q08xXsjLgEc8//zO6pEgugEd+m153i6QV7fbTRw==
Received: from (2a01:111:e400:7e1c::50) by (2a01:111:e400:7e1c::487) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16; Mon, 14 Sep 2020 14:23:45 +0000
Received: from VI1P194MB0285.EURP194.PROD.OUTLOOK.COM (2a01:111:e400:7e1c::47) by (2a01:111:e400:7e1c::490) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16 via Frontend Transport; Mon, 14 Sep 2020 14:23:45 +0000
Received: from VI1P194MB0285.EURP194.PROD.OUTLOOK.COM ([fe80::89f6:7540:e834:ffb8]) by VI1P194MB0285.EURP194.PROD.OUTLOOK.COM ([fe80::89f6:7540:e834:ffb8%5]) with mapi id 15.20.3370.019; Mon, 14 Sep 2020 14:23:45 +0000
From: Khaled Omar <>
To: Ola Thoresen <>, "" <>
Thread-Topic: [v6ops] IPv10 Discussion in v6ops
Thread-Index: AQHWiT43LYhHc7LQV0ie1xfS7y0F1aloGfGQgAAENwCAAAu+gIAAAGeQgAAHggCAAAB2MA==
Date: Mon, 14 Sep 2020 14:23:45 +0000
Message-ID: <VI1P194MB0285090A6E66464C9612EE34AE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
References: <> <VI1P194MB0285E344B7B3E9697E6ED608AE240@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <> <VI1P194MB028561F81F5118ABC14967DFAE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <> <> <VI1P194MB0285FCDBFB6A86DF954D1782AE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-incomingtopheadermarker: OriginalChecksum:2EC770BE7E56DD4A52FC3764EA45AA0A506D1466A3C96CD30C96D3327D106A07; UpperCasedChecksum:5A101220BA24742E67B53A9E27EDAEE5E38497E1309DF840DF90B185E0CAA1B9; SizeAsReceived:3199; Count:42
x-tmn: [JTq1kxvXofJJYjQ4g1l5LMA8w1b/+Wlk]
x-ms-publictraffictype: Email
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 59e14e92-2d26-4324-5619-08d858b9ca12
x-ms-traffictypediagnostic: AM5EUR02HT236:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: exvVOCjby8OTcMyU6S5IUmYj0aEDxwuOI+Eg9z3ySLylRQzkSiYw/t0u8uEmLD/oS4OysqY1XJF8cNhCjpFfPjUjpOTltaRJvVR609XugVxWZ7Bb+qg5KzJARbhqKNbAZEEExfyWa52Z5Wwn9+ePs16fpmwz61x5q+/d1HIo3voYAXDBrqkFOsS6Uf5ENBcLxsWNJvnl7ptoaWclJ8evDkJ7nzpcF8sMrCguc789x6s=
x-ms-exchange-antispam-messagedata: lKURJoxA5TmhTKBz5ZupTQpd6m266FlKDZ/hGStJcS+ldxB+/WjS9V0aoYJ1ClutxnOlw/d9bR8wpQQ7qhmN7Zot6+syBhqDMSEJqUGoprQWl9gAt7ZxORsjNuiiJ4Cv3tsuBIvDMYKBYZkqzj+uLQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 59e14e92-2d26-4324-5619-08d858b9ca12
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Sep 2020 14:23:45.4658 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT236
Archived-At: <>
Subject: Re: [v6ops] IPv10 Discussion in v6ops
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 14 Sep 2020 14:23:50 -0000

>> 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.

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 <> On Behalf Of Ola Thoresen
Sent: Monday, September 14, 2020 4:20 PM
Subject: Re: [v6ops] IPv10 Discussion in v6ops


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.


/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 <> On Behalf Of Lencse Gábor
> Sent: Monday, September 14, 2020 3:52 PM
> To:
> 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 <> wrote:
>>>> Is it possible to reserve a slot for the IPv10 I-D to be presented completely during the v6ops wg meeting session?
>> 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 mailing list
> _______________________________________________
> v6ops mailing list

v6ops mailing list