Re: [Int-area] Continuing IPv10 I-D discussion.

Khaled Omar <eng.khaled.omar@hotmail.com> Thu, 30 March 2017 15:39 UTC

Return-Path: <eng.khaled.omar@hotmail.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 4CB76128BE1 for <int-area@ietfa.amsl.com>; Thu, 30 Mar 2017 08:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.147
X-Spam-Level:
X-Spam-Status: No, score=-1.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 2JGpBptGtO9t for <int-area@ietfa.amsl.com>; Thu, 30 Mar 2017 08:39:25 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-oln040092066081.outbound.protection.outlook.com [40.92.66.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22603129512 for <int-area@ietf.org>; Thu, 30 Mar 2017 08:39:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=55l4/v8rvnGGZrqyWWnE+ELZxE4uz1tYs8UJO/sITEs=; b=BMohyhni56t/Znfdnvsj2yeFcU1suqIVox4HWjBo2wxhiZm1g6hsI4x1ZhBbbHxJB3THPcyObv/ocL0lfoCUoSaIARJunyzwGRk5AxUWpjwAh3l1AiSdRrFL8WlCTAd8XunQofIjuhrUB+QweCY0Esknj/z5sB4OhAunj4KRVuuFKYh33QiIw+jQoAAD+KOCxnKvImjq8INVZ1RPGgurxtxnSeyrwbvkBH+YOlnOyhdZwksg5Nh3/SabB/7iYL9pQWR9FwP5LAzC9lRpy9z5cOogHwJ+2dBHByjWlg8lNdNe3ECOWSiGSTLTIc45SjO2uDjdsqAimRteOfwl0G1yNw==
Received: from DB5EUR01FT038.eop-EUR01.prod.protection.outlook.com (10.152.4.58) by DB5EUR01HT161.eop-EUR01.prod.protection.outlook.com (10.152.5.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.977.7; Thu, 30 Mar 2017 15:39:23 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.4.57) by DB5EUR01FT038.mail.protection.outlook.com (10.152.4.191) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1005.5 via Frontend Transport; Thu, 30 Mar 2017 15:39:22 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([10.165.44.150]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([10.165.44.150]) with mapi id 15.01.0991.022; Thu, 30 Mar 2017 15:39:22 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "Bless, Roland (TM)" <roland.bless@kit.edu>
CC: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] Continuing IPv10 I-D discussion.
Thread-Index: AdKpViCv4ucVibQQSyGDqyi2P9NswAAEJZeAAAAdAFAAARi1IA==
Date: Thu, 30 Mar 2017 15:39:22 +0000
Message-ID: <AM4PR0401MB22411EB78EC5193AF5D30D2ABD340@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <AM4PR0401MB2241D42F2FDC359193FD6B80BD340@AM4PR0401MB2241.eurprd04.prod.outlook.com> <9c0d9f36-7a07-f9a0-c8b9-75ea5bcb7cf2@kit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: kit.edu; dkim=none (message not signed) header.d=none;kit.edu; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:B5E7E52105FE660CEEDCF25B6570518EE76AAC230FA28176C35CB69706A465C1; UpperCasedChecksum:D1EA7220629EC82806561FBA344C343A4E6DDE169092C68E9C59C0E158C2F969; SizeAsReceived:8131; Count:41
x-tmn: [TVJyxLnqC1qrNpSUAi6jLQt5zpBlstfh]
x-microsoft-exchange-diagnostics: 1; DB5EUR01HT161; 5:U8AZgl7My//lA2wiBXKif4djp+vHCB3AX/mJLgWcXm7QiGobj0s2eJr+cFUbq3BVXAkRn6aKgl0PqnyhGmhOiByPjv6uvgoEXlW2jcCyBdLvHRpVXLaGzxjOGILOFdUok4cLlkzVu5+IVFpjT6Ca1g==; 24:fMqWNiibn4wtT4Icoj5cx3M2puFnKhW9j9aYxnjtEgkuNmuY2ZJEZZBuxSvWdfSEDbWSfBesi9pmd0NVDQdGMk7/jOGFJn0ez3fFio4c6rE=; 7:NxEDuZkooECUlkt6aemIWnB8XvupdjXi2FQXR5WMPQA3a5VEgfg3SX6NsEYvMuIZpIdTsxOsO+RrTplwQEAGbRJlKQe6r5iGM3+j/cNJ2mtPaWvjstR1QLVo4xZkPIWRtzh6L0SexI5KMRIA5YbjhpSWUFB7PcqU9FlDHl3NMP/suMeRvlKGcW2B064J9F5el+leIWGfqYKq/0ktlTOlxdC77TtTEqlhE3SMNiUEY22SZgmwa4/2qX96xzqObb77Zg39WjbExqXbUNXp+ivPC4lm4MjvM8k2YXmmNfqaLsuUxFKR0LPYr9gmlx6yoCYE
x-incomingheadercount: 41
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:DB5EUR01HT161; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en;
x-ms-office365-filtering-correlation-id: 6c4abc16-fb6a-410e-bdec-08d47782f045
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:DB5EUR01HT161;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:DB5EUR01HT161; BCL:0; PCL:0; RULEID:; SRVR:DB5EUR01HT161;
x-forefront-prvs: 02622CEF0A
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2017 15:39:22.3906 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5EUR01HT161
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/Oiri0UH7YlXyj7DTyt9idtZCkrc>
Subject: Re: [Int-area] Continuing IPv10 I-D discussion.
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
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, 30 Mar 2017 15:39:27 -0000

I forgot to tell you that I was waiting for a replacement solution for 3 years but after a short time I found IPv10 is the best.

Best Regards,


-----Original Message-----
From: Khaled Omar 
Sent: Thursday, March 30, 2017 5:26 PM
To: 'Bless, Roland (TM)'
Subject: RE: [Int-area] Continuing IPv10 I-D discussion.

Hi Roland,

This way too is not working, keeping repeating same answers to the same questions is ridiculous.

 > Your IPv10 proposal doesn't solve the IPv6 deployment problems, you
  basically get an additional IPv10 deployment problem.

IPv10 does not depends on clients (ISPs or Enterprises) like IPv6 migration process, it depends on software modification on all hosts' OSs and routers' OSs to be able to encapsulate both IP version on the same IP header.

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

Think about a host treats a different version destination as a host in a different subnet, it will send the packet to the gateway, the gateway (router) will check the destination packet, and based on its version (whether it is an IPv4 packet or and IPv6 packet) it will checks its IP routing table (whether the IPv4 routing or the IPv6 routing table respectively) to make a routing decision, and each router on the road to the destination will do the same till reaching the destination. 

> As others already pointed out: the proposal is technically flawed
  and does not work.

Please speak with your own tongue, others who stated that had no full information about how IPv10 works, later they believed it is the best solution for IPv4 and IPv6 coexistence until reaching a full migration to IPv6.

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

Simply, if IPv10 is not of your interest, peacefully don't participate in the discussion, as I stated on my proposal, the internet will be divided into two divisions, and that will not be good for all of us when some new users will be assigned (or already assigned) IPv6 only addresses and has no access to all internet resources or a limited access(Google and Facebook).

> There are various WGs in the IETF that try to work towards better solutions. You may not like them, but they are at least rough community consensus.

Science doesn't understand consensus, science understands ideas, better ideas and the best idea, that can technically deployed easily and in a short time, I can make a solution like IPv6 and think about forcing people to migrate, but this will not work practically in a short time, and this is what we are experiencing, also, thinking about a solution that requires giving training everywhere to let people deploy it is not a good solution, because still depends on clients (users), but to make a solution that depends on a few number of companies developing networking OSs and can be deployed in a short time with no interventions of a helping technology (like protocol translation or asking DNS for more efforts).

Eventually, IMHO, you will never reach a full consensus by all IETF members, so it is the time for the responsible ADs and Chairs with some help from interested participants to make a good impact for all.

Best regards,

Khaled Omar 


 

-----Original Message-----
From: Bless, Roland (TM) [mailto:roland.bless@kit.edu]
Sent: Thursday, March 30, 2017 5:03 PM
To: Khaled Omar; int-area@ietf.org
Subject: Re: [Int-area] Continuing IPv10 I-D discussion.

Dear Omar,

Am 30.03.2017 um 15:16 schrieb Khaled Omar:
> I think all of you now know about IPv10 and what is the problem and 
> how
> IPv10 can solve it and how it can be deployed in a short time.

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

> You can ask any question and I'll do my best to give you answers to 
> make it clear for everyone so the IPv10 I-D can go forward through the 
> IETF standardization process and be published.

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.

> If there is a better solution for this problem I can participate 
> freely on its discussion.

There are various WGs in the IETF that try to work towards better solutions. You may not like them, but they are at least rough community consensus.

Best,
 Roland