Re: [Int-area] IPv10 draft (was Re: FW: [v6ops] v6ops - New Meeting Session Request for IETF 109 - IPv10)

Khaled Omar <eng.khaled.omar@outlook.com> Thu, 17 September 2020 14:40 UTC

Return-Path: <eng.khaled.omar@outlook.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 AE51B3A0317; Thu, 17 Sep 2020 07:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 e2yvN1JtgJgB; Thu, 17 Sep 2020 07:40:34 -0700 (PDT)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05olkn2058.outbound.protection.outlook.com [40.92.90.58]) (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 C111C3A08AE; Thu, 17 Sep 2020 07:40:33 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lr6I95ey18Dua1qnksz0iZoFNEaoMoiCgVuvIXf/hsqAoqVfn0UFknSa018iKqLfYq8mK1ROaBO/RZPyQNDqswI8IniX0jOCclJlPjNmtgyMdZkdfLPNMQjBjywK/CihbTJALlcVNEbtzxbVvhhRIAba0/toskfUDOVmpVaUETbcVC6fTSH77PpikI+ey6e7dXUMjf+KODhafYQgIQn8DDYc6tEreaAyF9v8jyDGHV2+KTa+e5gLViLQ8mXcBwg0Ah/xGqFPSfMJXgbjTjwAMbfHYy2FlPHY/4wJJBj6gUB5AuxWe6IF8gFKh+f3Q0OrgkEWbOT/ezO+ILSqMNXf5A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4paBivOMF92IWdGHP++4vrPySXf+mjeQBBvN1uxhgYQ=; b=GeoIMbhXveaJKWBq7UWesqt7+z6ucAFoJpb8EPG1B8k7T+yaBMtx4UuU9g0F9ZZliWPx3amqwoObjlZ7o8cNei9QXKFloLSlHly7abkE51WHTvtvS7osbMfYGSPvnPnZkgF58Kt+dOmvmeeGui5OfATrdUVbNhAo4TtotFG1ZLbwwjCyDeKU4fpv/B21Z/TaEPrxqH9A6KgwJPY5uQThm/TvbsHCHpceIwinPykkP7ZfkRWfN2ZcFe0XHy2olER2xmMVxtG3XXGJCc3nUQikpegWit8jO3HzIhZS+XSENVd++yV2oXRvLTTK8YtBVC7dAXEPf6rXUEBOS2SO+4h0kw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4paBivOMF92IWdGHP++4vrPySXf+mjeQBBvN1uxhgYQ=; b=b17hHuBULNezTqBb87mcu7GupYFl7VMCoFJEzFBslMuH+FLIsPg6Pdc6jgOyvOCUQtKk5vLc2qL+BzccGGWWSrbs1S3HWjU/u6gvYlR6FtkI4AkpW9y9TAIoiZ1vVusaZMlmS67bFPCT3zFjTA41HrTVlY9kLnATDTAs2rBI/TOt4kxWzQvFINCtkvJ6G4xqZgjRMDVRPIzzj/UFvqsmz1/o4VXxluY9D80eW3dbhmKyAzzMb2NdLLMscmPk+6OUGFl//abObNNjP/42RWe8SzO72EoaguraLwOTWp+9tlhAv4C0qW2d/4F+Iirb23HXpyUuPZlqDlcQ2UC9JiUutA==
Received: from AM6EUR05FT068.eop-eur05.prod.protection.outlook.com (2a01:111:e400:fc11::41) by AM6EUR05HT034.eop-eur05.prod.protection.outlook.com (2a01:111:e400:fc11::339) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3391.15; Thu, 17 Sep 2020 14:40:31 +0000
Received: from VI1P194MB0285.EURP194.PROD.OUTLOOK.COM (2a01:111:e400:fc11::51) by AM6EUR05FT068.mail.protection.outlook.com (2a01:111:e400:fc11::222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3391.15 via Frontend Transport; Thu, 17 Sep 2020 14:40:31 +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; Thu, 17 Sep 2020 14:40:31 +0000
From: Khaled Omar <eng.khaled.omar@outlook.com>
To: "Bless, Roland (TM)" <roland.bless@kit.edu>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
CC: Ron Bonica <rbonica@juniper.net>, int-area <int-area@ietf.org>, "intarea-chairs@ietf.org" <intarea-chairs@ietf.org>
Thread-Topic: [Int-area] IPv10 draft (was Re: FW: [v6ops] v6ops - New Meeting Session Request for IETF 109 - IPv10)
Thread-Index: AQHWjQB+PygN21kf+kOyQe2OXGJ2Bg==
Date: Thu, 17 Sep 2020 14:40:31 +0000
Message-ID: <VI1P194MB028581B46379B4D1927F352CAE3E0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
References: <BA9AA3A6-AD8E-448C-8435-9861ED6DB844@cisco.com> <VI1P194MB02854BE1477807D40AD44E34AE3E0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <20200917140810.GA29793@nic.fr> <VI1P194MB0285AEE49C63F9DF0E18021FAE3E0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <06e75cc8-dfc2-e6ee-af76-639f2cac1128@kit.edu>
In-Reply-To: <06e75cc8-dfc2-e6ee-af76-639f2cac1128@kit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:9C6FA65FA36A9D21757E21E836881F505835D9A96525F9468481FA26DA4FB688; UpperCasedChecksum:793ECDDCF76DD0368F484AE1B1178E27EFE17C76D4298C666AC41B4394903348; SizeAsReceived:7293; Count:44
x-tmn: [F3arsNwJ+olvvI+KujvKxePpYSPG1OFk]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 5ed3ed1e-84eb-481f-337f-08d85b17a0ad
x-ms-traffictypediagnostic: AM6EUR05HT034:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: WWZl2ZzxNMBN0N/l9+MqpmEfu+ZkF8LUeZLOAdNdThF8v1b2E4xSyBqhB5BtGiuACHwhWH3gouLyHfuxGS+V0RNCjco0zBS+2J3XcnK1hnlQRDP5s6oFmGFi87VE99wNGcMFrb9rchdH8vyXcN8PD+EtZMjpnxdnAN9Hr7Zm4ZLuzStfq6FTnXTUwjpUmzL9Nd6VkccvOhzifqmwBvAEQlNVfP1hwySyuRRp5HB2Ql9nfy+XqPb1KR7zK7fxLw2E
x-ms-exchange-antispam-messagedata: BZS3iHfCGQTDF3CjX67RgP7M+SsWWFZVDCSCL3vJ+JbJ6xRekLOpnSdiYV1jGhKTl8ukSJNQWH+Qg6q5wcRNYDvoYYHwDxSyGAeCSNR+EDOBhxC4oldiFjxRjbtrdBh+31vDkF7e87IQCuV4lIXxpw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: AM6EUR05FT068.eop-eur05.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 5ed3ed1e-84eb-481f-337f-08d85b17a0ad
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Sep 2020 14:40:31.0706 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6EUR05HT034
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/9aAbV1Gey5rGKUzXVkiBtmPXoZU>
Subject: Re: [Int-area] IPv10 draft (was Re: FW: [v6ops] v6ops - New Meeting Session Request for IETF 109 - IPv10)
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: Thu, 17 Sep 2020 14:40:36 -0000

>> - Your IPv10 proposal doesn't solve the IPv6 deployment problems, you
>>   basically get an additional IPv10 deployment problem.
>> - IPv10 doesn't allow an IPv6-only host to communicate to an IPv4-only
>>   host and vice versa as stated in the I-D. Hint: an IPv4-only host
>>   has got no idea what an IPv6 address is, let alone an "IPv10 address".
>> - As others already pointed out: the proposal is technically flawed
>>   and does not work.
>> ...>> Repeating this over and over again does not work. IMHO you only 
>> can move forward with a _technically sound_ proposal, otherwise many 
>> people will regard it as waste of time.

How can IPv10 allow an IPv6-only host to communicate to an IPv4-only host?

This is part of the update, the IPv6 only host will consider the destination (when it is an IP4 only host) as a host not in the same subnet and sent to the default gateway, then the default gateway (router) will use the appropriate routing table (which is the IPv4 routing table in this case) and route the packet until reaching to the destination ......... easy ha.

Best regards,

Khaled Omar

-----Original Message-----
From: Bless, Roland (TM) <roland.bless@kit.edu> 
Sent: Thursday, September 17, 2020 4:35 PM
To: Khaled Omar <eng.khaled.omar@outlook.com>; Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Ron Bonica <rbonica@juniper.net>; int-area <int-area@ietf.org>; intarea-chairs@ietf.org
Subject: Re: [Int-area] IPv10 draft (was Re: FW: [v6ops] v6ops - New Meeting Session Request for IETF 109 - IPv10)

Hi,

Am 17.09.20 um 16:13 schrieb Khaled Omar:
>>> No, most of the feedback you received was to explain why it is a bad idea from the beginning and why your premises, your reasoning and your conclusion are all false.
> 
> Why it is a bad idea ?????!!!!!

Because it is contradictory in itself. Your drafts speaks of
IPv4- and IPv6-only hosts, but your solution requires them to use and implement the IPv10/IPmix format, too.

> IPv6 requires updating and migration.
> IPv10 requires only updating.

Yes, and everything: hosts and routers.
Not simpler than for IPv6.

> IPv6 took so long time.
> IPv10 will take short time.

Nope, that is a wish, since the complexity would be the same.

> IPv6 is a new address structure.
> IPv10 is a solution only.

IPV10 also defines a new address format.

> Other transitioning techniques requires so much translations and involvement of the DNS in the communication process.
> IPv10 doesn't requires neither.

Because everything is IPv10-capable...

> Other transitioning techniques requires training.
> IPv10 requires no training. 

I agree with Stephane and repeat excerpts of my message from 2017 here:
>> - Your IPv10 proposal doesn't solve the IPv6 deployment problems, you
>>   basically get an additional IPv10 deployment problem.
>> - IPv10 doesn't allow an IPv6-only host to communicate to an IPv4-only
>>   host and vice versa as stated in the I-D. Hint: an IPv4-only host
>>   has got no idea what an IPv6 address is, let alone an "IPv10 address".
>> - As others already pointed out: the proposal is technically flawed
>>   and does not work.
>> ...>> Repeating this over and over again does not work. IMHO you only 
>> can move forward with a _technically sound_ proposal, otherwise many 
>> people will regard it as waste of time.

https://mailarchive.ietf.org/arch/msg/int-area/oLszaOAMS5OgSxM0ECKwo-ClYDE/

> -----Original Message-----
> From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
> Sent: Thursday, September 17, 2020 4:08 PM
> To: Khaled Omar <eng.khaled.omar@outlook.com>
> Cc: Eric Vyncke (evyncke) <evyncke@cisco.com>; int-area 
> <int-area@ietf.org>; intarea-chairs@ietf.org; Ron Bonica 
> <rbonica@juniper.net>
> Subject: Re: [Int-area] IPv10 draft (was Re: FW: [v6ops] v6ops - New 
> Meeting Session Request for IETF 109 - IPv10)
> 
> On Thu, Sep 17, 2020 at 01:58:21PM +0000,  Khaled Omar <eng.khaled.omar@outlook.com> wrote  a message of 122 lines which said:
> 
>> Most of the feedbacks I got are related to changing the draft name 
>> from IPv10 to any other name.
> 
> No, most of the feedback you received was to explain why it is a bad idea from the beginning and why your premises, your reasoning and your conclusion are all false.
> 
> No need to spend meeting time on it.

Regards
 Roland