Re: Why do we need to go with 128 bits address space ?

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Tue, 03 September 2019 00:38 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 9334D1200C5 for <ietf@ietfa.amsl.com>; Mon, 2 Sep 2019 17:38:27 -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, SPF_HELO_NONE=0.001, SPF_NONE=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 YGnzTpIIFZls for <ietf@ietfa.amsl.com>; Mon, 2 Sep 2019 17:38:26 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id E2ABE12008F for <ietf@ietf.org>; Mon, 2 Sep 2019 17:38:25 -0700 (PDT)
Received: (qmail 76855 invoked from network); 3 Sep 2019 00:26:01 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 3 Sep 2019 00:26:01 -0000
Subject: Re: Why do we need to go with 128 bits address space ?
To: ietf@ietf.org, shyam bandyopadhyay <shyamb66@gmail.com>
References: <CAPTMOt+cGhBqHmT3yZVChv-PCMqxT-WPDcDdM3RuTc1TMfFeVg@mail.gmail.com> <4278D47A901B3041A737953BAA078ADE148C2FE4@DGGEML532-MBX.china.huawei.com> <10708d7b-a4bc-f9d8-a644-7c5617f5ebf3@gont.com.ar> <CAPTMOtLyiUpi4L+7TpLePvm=JtpEnw-Yv1NCKvO63_HK2jFnCA@mail.gmail.com> <447e5dae-2ae9-b9fe-baa2-111c028d3b68@necom830.hpcl.titech.ac.jp>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <8e4c9f38-4085-bade-c9ed-3598c7c35d59@necom830.hpcl.titech.ac.jp>
Date: Tue, 03 Sep 2019 09:38:24 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <447e5dae-2ae9-b9fe-baa2-111c028d3b68@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9tNDHs2rmpetuJG7eb-8PdCH-cA>
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: Tue, 03 Sep 2019 00:38:28 -0000

To justfy cross posting by Shyam Bandyopadhyay to many lists;

As I wrote:

> shyam bandyopadhyay wrote:
> 
>> draft-shyam-real-ip-framework
> 
> is a reinvention of geography based addressing not acceptable
> by ISPs in the real world.

among many participants of all the lists, I, only on IETF list,
am the only person to pay respect to him by, spending some time,
reading his draft seriously enough to find a known defect.

Though he may be disappointed, it is better if defects, if any,
are found as early as possible.

So, he did the right thing.

						Masataka Ohta

PS

Attacking someone's draft without reading it is a personal attack.

PPS

I found RINA, seemingly, have the same defect. I'll discuss it in
a separate mail.