Re: [v6ops] IPv10 Discussion in v6ops

Wilhelm Boeddinghaus <wilhelm@boeddinghaus.de> Mon, 14 September 2020 16:18 UTC

Return-Path: <wilhelm@boeddinghaus.de>
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 2A4733A0CCF for <v6ops@ietfa.amsl.com>; Mon, 14 Sep 2020 09:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 4qLcS589J0mF for <v6ops@ietfa.amsl.com>; Mon, 14 Sep 2020 09:18:39 -0700 (PDT)
Received: from mail.boeddinghaus.de (mail.boeddinghaus.de [81.169.154.127]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C3883A0CCE for <v6ops@ietf.org>; Mon, 14 Sep 2020 09:18:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.boeddinghaus.de (Postfix) with ESMTP id C03ACD20B0A for <v6ops@ietf.org>; Mon, 14 Sep 2020 18:18:36 +0200 (CEST)
Received: from mail.boeddinghaus.de ([127.0.0.1]) by localhost (h1730.serverkompetenz.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lUYmMtmdNEgY for <v6ops@ietf.org>; Mon, 14 Sep 2020 18:18:34 +0200 (CEST)
Received: from [192.168.33.214] (p4fecda20.dip0.t-ipconnect.de [79.236.218.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: willem) by mail.boeddinghaus.de (Postfix) with ESMTPSA id 3F412D20A6D for <v6ops@ietf.org>; Mon, 14 Sep 2020 18:18:34 +0200 (CEST)
To: 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> <a461b63d-acfc-dd07-61e4-04f38ac85c95@nlogic.no> <VI1P194MB0285F92EB7A41638CCD943BFAE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
From: Wilhelm Boeddinghaus <wilhelm@boeddinghaus.de>
Message-ID: <f149036e-6f14-259d-66a7-6f9c6ff92207@boeddinghaus.de>
Date: Mon, 14 Sep 2020 18:18:33 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.2.2
MIME-Version: 1.0
In-Reply-To: <VI1P194MB0285F92EB7A41638CCD943BFAE230@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: de-DE
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/qj-iKY6u5SsXBTIgZalgEPlSPhg>
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 16:18:41 -0000

Hi Khaled,

have you ever run a network?

It is the operators who have to change all of their security (firewall 
rules, access lists, etc.), not the vendors. They have to modify the 
hardware, invent new asics, write new software.

The problem you try to solve is not "expensive" enough for the world to 
invest in your solution. Its all about money.

Can you show us a running implementation? Windows, Linux, Free Range 
Routing? Do you have a plan to modify the routing protocols used today 
(BGP, OSPF, ISIS, etc.)? Maybe a good showcase can convince the 
engineers and operators on this list. Just repeating your arguments does 
not seem to help. And IPv6 is a good example how long it takes to 
implement a new protocol.

Please go forward, develop your draft, write some code to show how easy 
it is to implement your solution, but stop trying to convince us with 
what you have, you need more.

Best,

Wilhelm

Am 14.09.2020 um 17:11 schrieb Khaled Omar:
> Yes, but WHO will do that modification, those will do it:
>
> Google, Apple, Cisco, Microsoft, Huawei, Juniper, Fortinet, etc.......
>
> Not the USERS.
>
> Khaled Omar
>
> -----Original Message-----
> From: Ola Thoresen <ola@nlogic.no>
> Sent: Monday, September 14, 2020 5:08 PM
> To: Khaled Omar <eng.khaled.omar@outlook.com>om>; v6ops@ietf.org
> Subject: Re: [v6ops] IPv10 Discussion in v6ops
>
> 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)
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops