RE: New Approach For Discussing IPng

Khaled Omar <eng.khaled.omar@outlook.com> Mon, 19 April 2021 13:52 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 5C8E23A3289 for <ietf@ietfa.amsl.com>; Mon, 19 Apr 2021 06:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 NgGuj5icoGmk for <ietf@ietfa.amsl.com>; Mon, 19 Apr 2021 06:52:54 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-oln040092073046.outbound.protection.outlook.com [40.92.73.46]) (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 15C063A327F for <ietf@ietf.org>; Mon, 19 Apr 2021 06:52:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F0vKD5S++TSkWi6OaYeoAGfvcGB3kRzdNDFjEyeNcSckqF1ShWl/rIFnU5INJl1RAm1KpNXJCn82KGg1pa5rXtSTJ0HxnQVDJB6mv32EA5+qeI9vJ2IFouFOMUbX+qLigUeRr8fE1hyRWza45oZBcxJFlA8l11Drw8+9GWP+U21wYmD4bycuh8JXTybAL0RhaqtBM9waSpqfLzOMQBRvRKoS4K+YM91SdPxkDA0or/LAMAvsd4RStmI3zRJfgN0h+FpU4+c6r7maePjYJkEmZJ7EKa563EuE/fOCOwEoVicieEf8kEhmp/hKalAWNBkYi0PNU+vx0TozBSaMOCnRdA==
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=oUBm6F4vwliNksCl2XTQSRdMn4u+8pjcnyROLm4WIZ0=; b=kpFgZwcL6ea8cO0BQncOto8y1gKUNhqCdtolw7njxEoDVNubI/ImgzG/LGoQY1N/zgl07Xqly7Ie/kLsG51tbmj0ikOaPO3Emhj0MdkztH4FmHzQNbavNnJBzYZQpvYtzmAHATB7/zF2Zk7kyHLO7lfdWuM29TFArBUR0ET/xVPREjSLk8VhaMmuDkZnysNGQqTRiv89K7GlA36fDAMN/Fr/Vsc00JvqsSzctDCluAd3BADaxo4yDKC6HKzQ3BwW8dJqPbfpX+L3xOordXUAIGhZg/JJsY8n/UD2n1onGNrh2xPfK7/aHsJRuVO7Zm2JHkWLKrvi4zb9NNcVBLwScw==
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=oUBm6F4vwliNksCl2XTQSRdMn4u+8pjcnyROLm4WIZ0=; b=LqnmKJwrcDBErJIiPEYGK4a4PmOqbG54a8fZKkVoBq1bKsdwCp4BotP0rtIOWGVdqJbD8is2d+9iZ45cfAjyrNSJdJ0qaOH3uNDLYRwF++O3QJq/zIKma4nfqhl8scVTMGqYcJ3DhsbJRTGY/8EEHyi8ua/XLYPo6AyxPUhqTomCBc7dmQ2o5trkDew9RjCg3Gp52YahNGy59adFjOHJVnfThr3j5qxETprJK8SEyDyZFQtBHk8MYz+XlmCp4Cg4xOKsjSbhgilae1eae6+z9h6HaDHtmhQpChL61Dq1Cze/4dpIu7eEnmuJxkvcISVCfs/AKInxAq5O4xeX1E0wGg==
Received: from DB3EUR04FT014.eop-eur04.prod.protection.outlook.com (2a01:111:e400:7e0c::4b) by DB3EUR04HT026.eop-eur04.prod.protection.outlook.com (2a01:111:e400:7e0c::316) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4042.16; Mon, 19 Apr 2021 13:52:51 +0000
Received: from AM7PR03MB6594.eurprd03.prod.outlook.com (2a01:111:e400:7e0c::40) by DB3EUR04FT014.mail.protection.outlook.com (2a01:111:e400:7e0c::278) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4042.16 via Frontend Transport; Mon, 19 Apr 2021 13:52:51 +0000
Received: from AM7PR03MB6594.eurprd03.prod.outlook.com ([fe80::1dd2:1e11:6d76:6ceb]) by AM7PR03MB6594.eurprd03.prod.outlook.com ([fe80::1dd2:1e11:6d76:6ceb%7]) with mapi id 15.20.4042.020; Mon, 19 Apr 2021 13:52:51 +0000
From: Khaled Omar <eng.khaled.omar@outlook.com>
To: Tom Beecher <beecher@beecher.cc>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, Phillip Hallam-Baker <phill@hallambaker.com>, Joe Touch <touch@strayalpha.com>, Lloyd W <lloyd.wood@yahoo.co.uk>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: RE: New Approach For Discussing IPng
Thread-Topic: New Approach For Discussing IPng
Thread-Index: AQHXNNgFbZYPJH4fe0qegzWbIY3tuaq7s+hggAAm14CAAAGYwA==
Date: Mon, 19 Apr 2021 13:52:51 +0000
Message-ID: <AM7PR03MB65949F4A2FBDE298734450DBAE499@AM7PR03MB6594.eurprd03.prod.outlook.com>
References: <CAMm+LwhV01N_uuFV8TfiyegpqDLmUYwxBcmkUAGG-HfJ7vSB+Q@mail.gmail.com> <989A5048-5EA8-479B-9231-D61B646E46F5@strayalpha.com> <CAMm+Lwhy0c6G7YLx8n7Ya7psG6VxcEckk-ncKg750rscuz-Yaw@mail.gmail.com> <89f2c243-433c-fa32-7dbf-c6392fde3da6@gmail.com> <AM7PR03MB6594B91C2C731546BC059D1CAE499@AM7PR03MB6594.eurprd03.prod.outlook.com> <CAL9Qcx7E8fx4fEsnbxogXpAeut9h_ZzknCfu_hLRrUQWqEXcAQ@mail.gmail.com>
In-Reply-To: <CAL9Qcx7E8fx4fEsnbxogXpAeut9h_ZzknCfu_hLRrUQWqEXcAQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:E71216598BF9509E0097065069B426866C3490F03B3115C31E3621158820EDB2; UpperCasedChecksum:3A7BB3ED9218C085A73E57DE9CD6C8F5002305DCD81DC3B6AEAD0DF916561E92; SizeAsReceived:7368; Count:44
x-tmn: [3f1iako2LlcD6w2WbdyLGHjIPSwZP03i]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: ff63db49-f189-46fe-1742-08d9033a6cd4
x-ms-traffictypediagnostic: DB3EUR04HT026:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: lRriLvuvjCMitVd6dF5jf+cVxFB5bYx0N0RWJrruX9kLhNgi0QNkHJdZL13ktQ4n2N3elPvveINZWcKAASErxBq9GO5/P4NkQ9Jm01QD3tUedJ+rlQqrRo4Jkf/OUCUfAjF/52YstxAQD2pKSGmPZ0kYbh7UgPdOvIeNkllhK4X6fkAaXJkQ8YwcnIieSP08lHFZ4XZHjAzgq5uHBWpg4E4rsSUheLXZS2pK1cK+GKgFgBKUiZ50uUo/p9ZxtIIkGJ1Cj+csAww9nNdzWKtn3iOa/zAFzKkmXVV9NTfCosT1f0ji6OKTbOH9Y//+RKB9q9wnvLGqOSFHl7nAWNb63LsPHbAr/5woRshCxOztS7eRmy6G9SzLDKptnNypxvxAIIm/tgmPDdVlLljx/7LIkg==
x-ms-exchange-antispam-messagedata: 2ucwLCZbTA6aZntM4qF787UJ2fGMFrcTvBpslUNDJ82ukfcB8Ifr4tTOagIdYjf+d5vfWrcuKw/qQkLNcZrX/weyNhAQOKruy66uymaV7HTYZgeb8cim0EYic/I5kAeYRlfCcBCu3kzRk+9yDP+NNQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM7PR03MB65949F4A2FBDE298734450DBAE499AM7PR03MB6594eurp_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: DB3EUR04FT014.eop-eur04.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: ff63db49-f189-46fe-1742-08d9033a6cd4
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Apr 2021 13:52:51.7784 (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: DB3EUR04HT026
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xuy6m5KETnnmKiJAGJAtOPJdiHg>
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: Mon, 19 Apr 2021 13:53:05 -0000

Hi Tom,

>> That would be an accurate description of tunnel mode IPSEC. If that is what you are proposing, numerous v4/v6 tunneling standards are already defined and are well developed.

I’m not asking for an IPSec tunnel, I’m proposing something like that tunnel when it adds another header with different source and destination addresses.

Once that will be accomplished, then peacefully IPv4 and IPv6 can coexist and communicate.

Khaled Omar

From: Tom Beecher [mailto:beecher@beecher.cc]
Sent: Monday, April 19, 2021 3:45 PM
To: Khaled Omar <eng.khaled.omar@outlook.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>; Phillip Hallam-Baker <phill@hallambaker.com>; Joe Touch <touch@strayalpha.com>; Lloyd W <lloyd.wood@yahoo.co.uk>; IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: New Approach For Discussing IPng

How VPN tunnels works in reality?! I think it works by first encrypting the original packet, THEN, "adding a new source and destination addresses to the packet", this is what I'm asking for to allow IPv10 concept works.

That would be an accurate description of tunnel mode IPSEC. If that is what you are proposing, numerous v4/v6 tunneling standards are already defined and are well developed.

On Mon, Apr 19, 2021 at 7:30 AM Khaled Omar <eng.khaled.omar@outlook.com<mailto:eng.khaled.omar@outlook.com>> wrote:
Hi Brian,

>> Back in 1994, it had become clear that deploying new header options in IPv4 across the Internet was in practice impossible, however well they worked in the lab. Extending IPv4 was therefore theoretically possible but impossible in reality. So we started IPv6.

How VPN tunnels works in reality?! I think it works by first encrypting the original packet, THEN, "adding a new source and destination addresses to the packet", this is what I'm asking for to allow IPv10 concept works.

Regards,

Khaled

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org>] On Behalf Of Brian E Carpenter
Sent: Monday, April 19, 2021 6:53 AM
To: Phillip Hallam-Baker <phill@hallambaker.com<mailto:phill@hallambaker.com>>; Joe Touch <touch@strayalpha.com<mailto:touch@strayalpha.com>>
Cc: Lloyd W <lloyd.wood@yahoo.co.uk<mailto:lloyd.wood@yahoo.co.uk>>; IETF Discussion Mailing List <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: New Approach For Discussing IPng

I've been keeping clear of this thread, but I think Phill does remind us of an important point (hence the small change of subject):
On 19-Apr-21 15:42, Phillip Hallam-Baker wrote:
...
> We keep having people coming along making these suggestions for IPv8, IPv10, etc. etc. and the inventors never once seem fit to ask what is so different about their proposal it can't be done in IPv6.

Back in 1994, it had become clear that deploying new header options in IPv4 across the Internet was in practice impossible, however well they worked in the lab. Extending IPv4 was therefore theoretically possible but impossible in reality. So we started IPv6.

27 years later, it has become clear that deploying new extension headers in IPv6 across the Internet is in practice impossible, however well they work in the lab.

There's little prospect that things would be different if we repeat the experiment.

> The whole point of the Internet is the narrow waist is really simple.

As it is written: "The function in question can completely and correctly be implemented only with the knowledge and help of the application standing at the endpoints of the communication system. Therefore, providing that questioned function as a feature of the communication system itself is not possible."

(What about deterministic networking? Indeed, that requires support as a feature of the communication system. Therefore, it will never happen across the Internet as a whole.)

    Brian