Re: IPv10.

"Bless, Roland (TM)" <roland.bless@kit.edu> Fri, 11 November 2016 14:33 UTC

Return-Path: <roland.bless@kit.edu>
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 36F531294A6; Fri, 11 Nov 2016 06:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 PqJR6YwirbG1; Fri, 11 Nov 2016 06:33:37 -0800 (PST)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) (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 F024812940D; Fri, 11 Nov 2016 06:33:36 -0800 (PST)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=i72vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25 iface 141.3.10.81 id 1c5Ctb-0007oP-8m; Fri, 11 Nov 2016 15:33:35 +0100
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by i72vorta.tm.kit.edu (Postfix) with ESMTPS id EDB2BB00618; Fri, 11 Nov 2016 15:33:36 +0100 (CET)
Subject: Re: IPv10.
To: Khaled Omar <eng.khaled.omar@hotmail.com>, "ietf@ietf.org" <ietf@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
References: <HE1PR04MB1449514D421EAC698335EE99BDBB0@HE1PR04MB1449.eurprd04.prod.outlook.com>
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
Message-ID: <37c3bc17-daa1-cac0-3848-5eb97350b87c@kit.edu>
Date: Fri, 11 Nov 2016 15:33:36 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <HE1PR04MB1449514D421EAC698335EE99BDBB0@HE1PR04MB1449.eurprd04.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1478874815.
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aJvk9fR96Mj0gFBS3fj63KQQpM8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 11 Nov 2016 14:33:39 -0000

Hi Khaled,

> I wish I’m not bothering you by my e-mails, but all what I’m asking you
> is to find a free time on your calendars so we can discuss, suggest, and
> participate in making the final version of the IPv10 draft and start
> experimenting its work, and once it will work efficiently and we find
> that it will bring a great value to the Internet, it can be standardized
> by the IETF.

Most of the time :-) the IETF works problem oriented.
Right now it seems that you have got a solution proposal
for a problem, that is IMHO not very clearly described.
I have not understood the point of your solution either,
it looks like having IPv4-Compatible IPv6 Addresses in
an IPv6 header. Such solutions were considered as
not being useful long time ago.

Suggestion:
- Check the material for newcomers to the IETF
  https://www.ietf.org/newcomers.html
- Describe the problem that you want to solve
  in an individual Internet-Draft (I-D) https://www.ietf.org/id-info/
  along with a statement why existing technologies
  do not solve it sufficiently, probably also give a
  sketch of your solution. The I-D is accessible by
  everyone from a central repository.
- You can then solicit discussion of the I-D on certain
  mailing lists that are related to the topic.

Coming back to your proposal, the statement
"IPv10 allows hosts from two IP versions to be able to communicate, and
this can be accomplished by having an IPv10 packet containing a mixture
of IPv4 and IPv6 addresses in the same IP packet header."
is contradictory in itself since neither IPv4-_only_ nor IPv6-only_
hosts will understand your "new" IPv10 format by definition.

Best regards,
 Roland