Re: [irtf-discuss] Why do we need to go with 128 bits address space ?

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

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF7F1200D8 for <irtf-discuss@ietfa.amsl.com>; Mon, 2 Sep 2019 18:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 bxwLvriFUZZX for <irtf-discuss@ietfa.amsl.com>; Mon, 2 Sep 2019 18:12:32 -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 4FF641200CD for <irtf-discuss@irtf.org>; Mon, 2 Sep 2019 18:12:32 -0700 (PDT)
Received: (qmail 5263 invoked from network); 3 Sep 2019 01:00:07 -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 01:00:07 -0000
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "ietf@ietf.org" <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> <CAOj+MMH=wb+v137TvQkZ+KxaBobA8qYmvoHkFzEgi9-PP-Lqxg@mail.gmail.com> <df102b3b-d337-8852-c5dc-f7aa4f479d77@necom830.hpcl.titech.ac.jp> <CAF46EB5-03AE-495C-A85D-73B3A9B7EB02@gmail.com>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <c7b4bafa-5aab-1a11-d871-4ee4c242a2f4@necom830.hpcl.titech.ac.jp>
Date: Tue, 03 Sep 2019 10:12:30 +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: <CAF46EB5-03AE-495C-A85D-73B3A9B7EB02@gmail.com>
Content-Type: text/plain; charset="iso-2022-jp"; format="flowed"; delsp="yes"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/1F1McHp8X8Epx7ORSOGF2PnMO_A>
Subject: Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2019 01:12:34 -0000

Fred Baker wrote:

> I'm familiar with the paper "End to end arguments in system design"
> as well. I'm also familiar with John Day, although I suspect I have
> learned more from him than he has learned from me.

As for RINA by John Day, following description in wikipedia (if any
of you have better reference, hopefully open access one, let me know)
disturbed me:

	https://en.wikipedia.org/wiki/Recursive_Internetwork_Architecture

	CLNP was an OSI-based protocol that addressed nodes instead
	of interfaces, solving the old multi-homing problem
	introduced by the ARPANET, and allowing for better routing
	information aggregation.

As CLNP addresses basically are telephone numbers, they are
aggregated by country code, which requires reliable telephone
exchangers exist connecting all the international and intra-national
long distance carriers in each country.

Similarly, aggregation by area code needs similar telephone
exchangers in each area.

That is, John, seemingly, think geography based addressing
is good, which is against our understanding that requiring
IXes in all the geographic regions is not practical.

Or, according to the E2E argument:

	The function in question can completely and correctly be
	implemented only with the knowledge and help of the
	application standing at the end points of the
	communication system. Therefore, providing that
	questioned function as a feature of the communication
	system itself is not possible.

providing multihoming function by telephone exchangers or
IXes, that is, "as a feature of the communication system
itself", completely and correctly is not possible.

Thus, if telephone exchangers or IXes fail and intra-national
network is partitioned, the result will be disastrous.

						Masataka Ohta

PS

Distribution of this mail is unlimited.