IETF Logo Mail Archive

Re: [v6ops] IPv10 Discussion in v6ops

Ola Thoresen <ola@nlogic.no> Mon, 14 September 2020 15:08 UTC

Return-Path: <ola@nlogic.no>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E233A0B1F for <v6ops@ietfa.amsl.com>; Mon, 14 Sep 2020 08:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.723
X-Spam-Level:
X-Spam-Status: No, score=-0.723 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.398, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no 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 dNzxc_4jpjg9 for <v6ops@ietfa.amsl.com>; Mon, 14 Sep 2020 08:08:01 -0700 (PDT)
Received: from mail.nytt.no (poseidon.nytt.no [178.62.243.165]) (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 B66693A09DF for <v6ops@ietf.org>; Mon, 14 Sep 2020 08:08:00 -0700 (PDT)
Received: from olen-jobb.nlogic.no (host-77-234-50-66.lynet.no [77.234.50.66]) (authenticated bits=0) by mail.nytt.no (8.15.2/8.15.2) with ESMTPSA id 08EF7uiP009497 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 14 Sep 2020 17:07:56 +0200
To: Khaled Omar <eng.khaled.omar@outlook.com>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <159985752195.15551.2657932726923781035@ietfa.amsl.com> <VI1P194MB0285E344B7B3E9697E6ED608AE240@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <3FA82C44-0005-45BA-AB09-FAE63C8CD626@gmail.com> <VI1P194MB028561F81F5118ABC14967DFAE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <3B5995B1-CD7A-444C-AD64-37C09E46A763@thehobsons.co.uk> <4fa01d01-bc2e-0f01-77f1-13dd4f6f2430@hit.bme.hu> <VI1P194MB0285FCDBFB6A86DF954D1782AE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <e0e4e5cf-1563-fca1-1388-68c8789384de@nlogic.no> <VI1P194MB0285090A6E66464C9612EE34AE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
From: Ola Thoresen <ola@nlogic.no>
Message-ID: <a461b63d-acfc-dd07-61e4-04f38ac85c95@nlogic.no>
Date: Mon, 14 Sep 2020 17:07:56 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <VI1P194MB0285090A6E66464C9612EE34AE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/thW__GfougZHQrzNbNlv7cqd0lM>
Subject: Re: [v6ops] IPv10 Discussion in v6ops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Sep 2020 15:08:03 -0000

On 14.09.2020 16:23, Khaled Omar wrote:

>>> You say this is not a new protocol, but you still specify a header format in section 4 of your draft.
> The discussion will keep repeating if the ietf will not show a different solution to the community that suffers now from the depletion of IPv4.


No. The discussion keeps repeating because you do not realize that you 
are trying to suggest that ALL hosts on the internet needs to be updated 
to support _another_ protocol than IPv4 and IPv6.  A "protocol" you have 
invented.  Nobody else is bringing this suggestion up again and again.



> Regarding the new packet header, users will not have a problem with it, its migration from v4 packet to v10 packet, that’s all.


USERS don't have a problem with IPv6 headers either.  But their hardware 
might have issues.  And their OS will definitely have issues with this 
new protocol.  And all their firewalls, access lists, applications, 
security policies etc needs to be reconfigured in the exact same way if 
they decide to start using "IPv10" as they would if they started using 
IPv6.


Rgds.

/Ola (T)

v2.23.0 | Report a Bug | By Email