RE: IPv10 I-D Destiny.

Khaled Omar <eng.khaled.omar@outlook.com> Wed, 12 August 2020 13:26 UTC

Return-Path: <eng.khaled.omar@outlook.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44C533A128E for <ietf@ietfa.amsl.com>; Wed, 12 Aug 2020 06:26:34 -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 SF3AmXJdQDBa for <ietf@ietfa.amsl.com>; Wed, 12 Aug 2020 06:26:32 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-oln040092069043.outbound.protection.outlook.com [40.92.69.43]) (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 AA66F3A12E2 for <ietf@ietf.org>; Wed, 12 Aug 2020 06:26:03 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IL1yFzOc0uWw9qbU0X+fQgy98fW8M2QkrMCLgzCoDqbqNht7tJYq/SJ+3H19McasSl5C/WPQaiLAbnGlunTZvH5qZoIvf22kS8Vmp5ma0BCJt0H4b+mwinJa1wj089US9yocJ2Od8D3+taaRoG82eP7nxT/QFbGEhM2OmM2+H45/Ar32OA/p+UljbZGL/hlfgjR6r79dsVS01knkzaxLQeasFWQzYyeJebdtQyy//TPida+oYjBOZw0UYuTeo9hAZKZ/AG2kRWxrRTxBHr+u4DJvSQ5Sfxbt8j5bmoB8saramKvryqEduQln/YE7tHJldr0G/VQH0D4zRjWfW25wwg==
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=d96uDrrhY1tT6Axjux/35e3K+sF9qMvQ2ZRFsdowgvU=; b=RQ9UNy2AFQ/bN5YW+kr1DGYBcaqVzs5vPwTr++t4mgNDDlQ+YJcp2XJTtYbCEjDy+heb/s7nIJtTAHX9t8PDBKn1DN4DR3Jyufhv3WdU2s8vtwCTq0C4qAufUQ5t/4cANfmuJmBm/h2GDLhrtI0rU/EfRGgTjEJIyFZDe7Yuz9Sx6e0Hqc2SOZWn/gYZQuZqLYv43vAqut+Ztu6aav1j4cK+j4js6h3aUB6BppVolds8XeeNBOxOCmy8etLARarTbHb3fIhi11M2IJL8PY/TXxIFb9pRb8LI3BUpUb2UHTOzi+Hx+XodCiDQbMDgmNm9pdUeD9q2YgjU9kJcjk7azg==
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=d96uDrrhY1tT6Axjux/35e3K+sF9qMvQ2ZRFsdowgvU=; b=h6q73gzKlv8FYfqHNgkumNDkSul9L31Ef9Fdj6GEokj3dToITD1vLbWgwoMzsNT7PepV5PMVfZLOL6LorTslyDIRqrQ6ZFhdYgmaURjkmHwmvbM+7e8mE1cA4STtByEGEmGf23+bAnHK/QPZgPBbfVNVD6EQ2xQ/OGgdIVdcI2EtvGgC0a+oEQ/tSzbzFrGed7FuRPNjw+jIQ3Q6K8LElUXbPRbQ+DQpgJPmlEBlMrQva/OK2JuDkGxIp6QZzHwyHuNx2QToI1Q2bpUMWlqavQOds0uOSR1vDUIVQsI0EY+avJ4YY3uwRi2ky4opeCEV2WL2d0SUwRE8SWzZQ/JMJQ==
Received: from AM5EUR02FT047.eop-EUR02.prod.protection.outlook.com (2a01:111:e400:7e1c::48) by AM5EUR02HT032.eop-EUR02.prod.protection.outlook.com (2a01:111:e400:7e1c::355) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3283.16; Wed, 12 Aug 2020 13:25:57 +0000
Received: from AM7P194MB0723.EURP194.PROD.OUTLOOK.COM (2a01:111:e400:7e1c::40) by AM5EUR02FT047.mail.protection.outlook.com (2a01:111:e400:7e1c::453) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3283.16 via Frontend Transport; Wed, 12 Aug 2020 13:25:57 +0000
Received: from AM7P194MB0723.EURP194.PROD.OUTLOOK.COM ([fe80::f8b9:eda6:885a:8b70]) by AM7P194MB0723.EURP194.PROD.OUTLOOK.COM ([fe80::f8b9:eda6:885a:8b70%9]) with mapi id 15.20.3283.015; Wed, 12 Aug 2020 13:25:57 +0000
From: Khaled Omar <eng.khaled.omar@outlook.com>
To: Lars Eggert <lars@eggert.org>
CC: IETF Discussion <ietf@ietf.org>
Subject: RE: IPv10 I-D Destiny.
Thread-Topic: IPv10 I-D Destiny.
Thread-Index: AdZwSadmkCW8yAGVQuetrcQGh13YMwAFeBpgAARQ0gAADoleAA==
Date: Wed, 12 Aug 2020 13:25:57 +0000
Message-ID: <AM7P194MB0723333AF98D503C3942E872AE420@AM7P194MB0723.EURP194.PROD.OUTLOOK.COM>
References: <AM7P194MB0723D773FCD8BAE7D9C6C9A8AE420@AM7P194MB0723.EURP194.PROD.OUTLOOK.COM> <AM7P194MB0723BD2C01221F94050AE995AE420@AM7P194MB0723.EURP194.PROD.OUTLOOK.COM> <43E6AD4C-284D-4088-9D6C-2F24062208B1@eggert.org>
In-Reply-To: <43E6AD4C-284D-4088-9D6C-2F24062208B1@eggert.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:CDD0826D13EBF41297732D54610A00BAA2EB3639BDF08D86A2CBE530A2F21791; UpperCasedChecksum:6B6D1B36FE222CA81C262D9CA539C26A26682C5E36C5E5D9A48ED261DA5CC4E8; SizeAsReceived:6916; Count:44
x-tmn: [poSnqccYbKV6Yq4nvfjgiDuClMQEM6Bf]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: ae755331-61fd-41f6-d690-08d83ec33f7d
x-ms-traffictypediagnostic: AM5EUR02HT032:
x-microsoft-antispam: BCL:0;
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:0; SRV:; IPV:NLI; SFV:NSPM; H:AM7P194MB0723.EURP194.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:; DIR:OUT; SFP:1901;
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: AM5EUR02FT047.eop-EUR02.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: ae755331-61fd-41f6-d690-08d83ec33f7d
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Aug 2020 13:25:57.7283 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT032
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tpXhYHAuNq8AbIuowJMOufTFcPI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2020 13:26:34 -0000

Hi Liars,

>> you gave it not even four hours since your earlier email, which you posted in the middle of the night (European/US time). I am sure you will get feedback shortly (incl. mine below).

Last time before this time I got zero response that's why I send another e-mail regardless the different time zones.

>> This is not how the IETF operates. Please review RFC2026.

I don't know which way the IETF would like to work, I tried many ways and all are in vain, there should be a different approach specially for urgent problems that can harm all internet users.

>> Regarding your proposal, briefly:

>>> (1) A networking architecture consist of much more than a header encoding scheme - that is the easy part.

Yes, this is very easy.

>>> (2) Simply pointing to IPsec is not a security analysis.

There is no need to security analysis, just mixing the two versions on one header.

>>> (3) The I-D says "there is no need to think about migration" when there clearly is such a need - the I-D expects all hosts and routers to understand and speak a new packet format.

Again, this is not called migration, this is called updating.

>>> (4) This paragraph IMO demonstrates best how far from deployment realities the proposal is:

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

Where is the problem.

Best Regards,

Khaled Omar


-----Original Message-----
From: Lars Eggert <lars@eggert.org> 
Sent: Wednesday, August 12, 2020 8:21 AM
To: Khaled Omar <eng.khaled.omar@outlook.com>
Cc: IETF Discussion <ietf@ietf.org>
Subject: Re: IPv10 I-D Destiny.

Hi,

On 2020-8-12, at 7:27, Khaled Omar <eng.khaled.omar@outlook.com> wrote:
> It’s really weird to hear the silence for my e-mails at the IETf main list,

you gave it not even four hours since your earlier email, which you posted in the middle of the night (European/US time). I am sure you will get feedback shortly (incl. mine below).

> As I proposed an I-D earlier that offers a solution to this pandemic that started to be distributed in the internet due to IPv4 address space exhaustion and the no migration to IPv6 occurred till now.
> 
> So please take one moment and evaluate the IPv10 I-D and make an accurate decision whether it can be promoted to a Standard or there is another solution that could solve this problem from its roots.

This is not how the IETF operates. Please review RFC2026.

Regarding your proposal, briefly:

(1) A networking architecture consist of much more than a header encoding scheme - that is the easy part.

(2) Simply pointing to IPsec is not a security analysis.

(3) The I-D says "there is no need to think about migration" when there clearly is such a need - the I-D expects all hosts and routers to understand and speak a new packet format.

(4) This paragraph IMO demonstrates best how far from deployment realities the proposal is:

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

Sorry, but this is unpublishable.

Lars