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

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Thu, 22 August 2019 10:28 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 8A298120288 for <irtf-discuss@ietfa.amsl.com>; Thu, 22 Aug 2019 03:28:24 -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=unavailable 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 TCY61yPG8Bu3 for <irtf-discuss@ietfa.amsl.com>; Thu, 22 Aug 2019 03:28:22 -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 37D331200B2 for <irtf-discuss@irtf.org>; Thu, 22 Aug 2019 03:28:22 -0700 (PDT)
Received: (qmail 4847 invoked from network); 22 Aug 2019 05:24:48 -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; 22 Aug 2019 05:24:48 -0000
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: Robert Raszuk <robert@raszuk.net>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "6man@ietf.org" <6man@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
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> <ded4f1d5-924b-77f1-90f4-11dc4869a8a7@necom830.hpcl.titech.ac.jp> <C7ABF067-3376-46EF-BB57-7275D6350133@gmail.com>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <7b3301a9-3816-092c-97cb-55c0a8e89e1e@necom830.hpcl.titech.ac.jp>
Date: Thu, 22 Aug 2019 14:36:53 +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: <C7ABF067-3376-46EF-BB57-7275D6350133@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/rQrqrhncFI1HFIk-w35fcpdufws>
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: Thu, 22 Aug 2019 10:28:25 -0000

Fred Baker wrote:

> Actually, I would argue that the essential paragraph is the first
> sentence of the introduction.

Read the paper. The first sentence of the introduction is:

	Choosing the proper boundaries between functions is
	perhaps the primary activity of the computer system
	designer.

not very essential.

> The paragraph you quote is commonly
> quoted,
The paragraph is commonly quoted, because, just after the
paragraph, it is stated:

	We call this line of reasoning against low-level
	function implementation the "end-to-end
	argument."

thus, the paragraph is the principle of the end to end argument.

 > but the introduction is far more applicable and useful.

Read the paper. The paragraph is in the introduction.

> "The principle, called the end-to-end argument, suggests that
> functions placed at low levels of a system may be redundant or of
> little value when compared with the cost of providing them at that
> low level."

That statement is on something suggested by the principle and,
compared to the principle itself, of secondary importance.

 > But even that has issues; in multicast or
 > anycast, the application at most selects the service,

if you want redundant multicast or anycast service, there
should be multiple multicast or anycast addresses offering
the same service, from which, applications choose the working
ones.

PIM with a single rendez-vous point has no redundancy and
anycast is, as is exemplified by multiple addresses of
anycast DNS root servers, for load distribution, not for
redundancy.

						Masataka Ohta