Re: [Int-area] [v6ops] Still need to know what has changed.... Re: IPv10 draft

Vasilenko Eduard <vasilenko.eduard@huawei.com> Fri, 25 September 2020 18:22 UTC

Return-Path: <vasilenko.eduard@huawei.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 20D733A1554; Fri, 25 Sep 2020 11:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham 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 nogQo4oEgvcW; Fri, 25 Sep 2020 11:22:08 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E91F3A1543; Fri, 25 Sep 2020 11:21:36 -0700 (PDT)
Received: from lhreml704-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id E7F22D28419B1C1E5B87; Fri, 25 Sep 2020 19:21:33 +0100 (IST)
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by lhreml704-chm.china.huawei.com (10.201.108.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Fri, 25 Sep 2020 19:21:33 +0100
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml703-chm.china.huawei.com (10.219.141.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 25 Sep 2020 21:21:31 +0300
Received: from msceml703-chm.china.huawei.com ([10.219.141.161]) by msceml703-chm.china.huawei.com ([10.219.141.161]) with mapi id 15.01.1913.007; Fri, 25 Sep 2020 21:21:31 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Khaled Omar <eng.khaled.omar@outlook.com>
CC: IPv6 Operations <v6ops@ietf.org>, int-area <int-area@ietf.org>
Thread-Topic: [v6ops] [Int-area] Still need to know what has changed.... Re: IPv10 draft
Thread-Index: AdaTZInZq6fMkJhaSOmmj7LU3urE2g==
Date: Fri, 25 Sep 2020 18:21:31 +0000
Message-ID: <23754dfa24fc4b27b78b5b488af482d9@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.196.218]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/R4t7THlkxn2UpJxaclWL9u3CozE>
X-Mailman-Approved-At: Fri, 25 Sep 2020 11:28:19 -0700
Subject: Re: [Int-area] [v6ops] Still need to know what has changed.... Re: IPv10 draft
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Sep 2020 18:22:17 -0000

Hi all,
I have looked to the draft. This hurricane is a little groundless.

Experts,
What Khaled was trying to invent is not a new IP protocol. It is just a mistake that it was called IPv10.
If you look inside the draft - you would see that it is additional version of IPv6 Stateless translation with IPv4-embedded addresses again.
Hence, billions of man-hours that is needed for development of new IP protocol is not needed. It is good news.

Khaled,
Your solution already exist. It is RFC 6144 - April 2011. Please, read this RFC. It has a bit more details then yours.
Just nobody before you was so brave to propose stateless translation directly from every host in the world. Everybody else was thinking about some gateways to keep the majority of hosts intact.
There is a logical hole in your proposal:
If it possible to upgrade every host from IPv4, then why not to upgrade it to IPv6 directly? That's it - problem solved.
Why anybody would need to upgrade hosts to combination of 2 protocols in the data plane? (second header is IPv10)
It is not logical. Does not make sense.

By the way, it is not possible to upgrade every host in the world out of IPv4 (nobody see money to do the job) - but it is the second problem that you would not face because of previous problem.

And what you propose to do in the next 20 years when part of host would already support IPv10, but other part does not?

Additionally I need to inform you that people are not satisfied with stateless translation, because long transition needs IPv4 per every host, but IPv4 is in shortage.
Hence, other translation technologies: 464XLAT, MAP-T/E, DS-lite, lw4o6.
If you trying to attack translation topic - you need to read all of these carefully.

Eduard