Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Wed, 21 August 2019 19:56 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 BB1F41209D1 for <irtf-discuss@ietfa.amsl.com>; Wed, 21 Aug 2019 12:56:21 -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 m1zXfs8c8GO3 for <irtf-discuss@ietfa.amsl.com>; Wed, 21 Aug 2019 12:56:19 -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 B90691209BC for <irtf-discuss@irtf.org>; Wed, 21 Aug 2019 12:56:18 -0700 (PDT)
Received: (qmail 73416 invoked from network); 21 Aug 2019 19:44:10 -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; 21 Aug 2019 19:44:10 -0000
To: Robert Raszuk <robert@raszuk.net>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "6man@ietf.org" <6man@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>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <df102b3b-d337-8852-c5dc-f7aa4f479d77@necom830.hpcl.titech.ac.jp>
Date: Thu, 22 Aug 2019 04:56:15 +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: <CAOj+MMH=wb+v137TvQkZ+KxaBobA8qYmvoHkFzEgi9-PP-Lqxg@mail.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/VGEzuu4ltWhu5dbBjE0AcqUczjg>
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: Wed, 21 Aug 2019 19:56:22 -0000
Robert Raszuk wrote: > *"Instead, APIs and applications must be modified to detect and react > against the loss of connection."* > > Well it is clear that you are making an implicit assumption that quality of > the available paths is equal and all you need to care about is end to end > connectivity/reachability. No, as is written in draft-ohta-e2e-multihoming-03.txt: Once a full routing table is available on all the end systems, it is easy for the end systems try all the destination addresses, from the most and to the least favorable ones, based on the routing metric. Note that end to end multihoming works with the separation between inter domain BGP and intra domain routing protocols, if BGP routers, based on domain policy, assign external routes preference values (metric) of intra domain routing protocols. One may still be allowed, though discouraged, to have local configuration with dumb end systems and an intelligent proxy. But, such configuration should be implemented with a protocol for purely local use without damaging the global protocol. IGP metric is used as route preference, though, some workaround of proxy (last paragraph) or having partial routing table on near ISPs (not mentioned in the draft) may be necessary, until global routing table becomes small enough to be able to be held by ordinary hosts. Note that at the time the draft was written, IPv6 global routing table was small, which means, at that time, IPv6 worth deploying despite all the flaws in it. Masataka Ohta
- [irtf-discuss] Why do we need to go with 128 bits… shyam bandyopadhyay
- Re: [irtf-discuss] Why do we need to go with 128 … Mark Smith
- Re: [irtf-discuss] Why do we need to go with 128 … Roland Bless
- Re: [irtf-discuss] Why do we need to go with 128 … Brian Carpenter
- Re: [irtf-discuss] Why do we need to go with 128 … Roland Bless
- Re: [irtf-discuss] Why do we need to go with 128 … Sam Kerner
- Re: [irtf-discuss] Why do we need to go with 128 … Lixia Zhang
- Re: [irtf-discuss] Why do we need to go with 128 … Mark Allman
- Re: [irtf-discuss] Why do we need to go with 128 … Nico Williams
- Re: [irtf-discuss] Why do we need to go with 128 … Fernando Gont
- Re: [irtf-discuss] Why do we need to go with 128 … Tom Herbert
- Re: [irtf-discuss] Why do we need to go with 128 … Chengli (Cheng Li)
- Re: [irtf-discuss] Why do we need to go with 128 … Carsten Bormann
- Re: [irtf-discuss] Why do we need to go with 128 … Roland Bless
- Re: [irtf-discuss] Why do we need to go with 128 … Fernando Gont
- Re: [irtf-discuss] Why do we need to go with 128 … Mark Smith
- Re: [irtf-discuss] Why do we need to go with 128 … Musa Stephen Honlue
- Re: [irtf-discuss] Why do we need to go with 128 … Behcet Sarikaya
- Re: [irtf-discuss] Why do we need to go with 128 … Phillip Hallam-Baker
- Re: [irtf-discuss] Why do we need to go with 128 … Masataka Ohta
- Re: [irtf-discuss] Why do we need to go with 128 … Mark Smith
- Re: [irtf-discuss] Why do we need to go with 128 … Michael
- Re: [irtf-discuss] Why do we need to go with 128 … Phillip Hallam-Baker
- Re: [irtf-discuss] Why do we need to go with 128 … Pengshuping (Peng Shuping)
- Re: [irtf-discuss] Why do we need to go with 128 … John Levine
- Re: [irtf-discuss] Why do we need to go with 128 … Fernando Gont
- Re: [irtf-discuss] Why do we need to go with 128 … Masataka Ohta
- Re: [irtf-discuss] Why do we need to go with 128 … Robert Raszuk
- Re: [irtf-discuss] Why do we need to go with 128 … shyam bandyopadhyay
- Re: [irtf-discuss] Why do we need to go with 128 … Masataka Ohta
- Re: [irtf-discuss] Why do we need to go with 128 … Robert Raszuk
- Re: [irtf-discuss] Why do we need to go with 128 … Masataka Ohta
- Re: [irtf-discuss] Why do we need to go with 128 … Masataka Ohta
- Re: [irtf-discuss] Why do we need to go with 128 … Robert Raszuk
- Re: [irtf-discuss] Why do we need to go with 128 … Masataka Ohta
- Re: [irtf-discuss] Why do we need to go with 128 … Fred Baker
- Re: [irtf-discuss] Why do we need to go with 128 … John Wroclawski
- Re: [irtf-discuss] Why do we need to go with 128 … Masataka Ohta
- Re: [irtf-discuss] Why do we need to go with 128 … Fred Baker
- Re: [irtf-discuss] Why do we need to go with 128 … Robert Raszuk
- Re: [irtf-discuss] Why do we need to go with 128 … Masataka Ohta
- Re: [irtf-discuss] Why do we need to go with 128 … Masataka Ohta
- Re: [irtf-discuss] Why do we need to go with 128 … Masataka Ohta
- Re: [irtf-discuss] Why do we need to go with 128 … Fernando Gont