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 21:06 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 9C90F1200B1 for <irtf-discuss@ietfa.amsl.com>; Wed, 21 Aug 2019 14:06:25 -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 HOZqNx6tQ3lp for <irtf-discuss@ietfa.amsl.com>; Wed, 21 Aug 2019 14:06:25 -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 C68F312010D for <irtf-discuss@irtf.org>; Wed, 21 Aug 2019 14:06:24 -0700 (PDT)
Received: (qmail 29082 invoked from network); 21 Aug 2019 20:47:36 -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 20:47:36 -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> <df102b3b-d337-8852-c5dc-f7aa4f479d77@necom830.hpcl.titech.ac.jp> <CAOj+MMHsHQPisxiJCLb4bB_nLy_W1y3YkAtYCXFJT5r00uKbVQ@mail.gmail.com>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <ffa5248f-4fb3-32d2-1ec4-aeb9621c0787@necom830.hpcl.titech.ac.jp>
Date: Thu, 22 Aug 2019 05:59:43 +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+MMHsHQPisxiJCLb4bB_nLy_W1y3YkAtYCXFJT5r00uKbVQ@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/AZX1RYvjVehRAdKEVyhoH_envGs>
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 21:06:25 -0000

Robert Raszuk wrote:

>> IGP metric is used as route preference,
> 
> And that's the issue. Neither IGP metric nor BGP path attributes today
> reflect reality of true network paths.

I'm afraid you are not familiar with BGP policy, where you don't have
to blindly rely on path attributes.

> When I look at my BGP table in NY I get path to Europe via Seattle just
> because such path has 1 AS less in the AS-PATH and neglect the fact that
> there is alternative path just next to it with +1 AS but shorter RTT of 150
> ms.

That you configure your BGP poorly does not mean others can't have
better policy to favor the alternative path.

As is written in the draft:

     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.

proper IGP metric may be given by proper policy based on such knowledge
(not carried by BGP) as "with +1 AS but shorter RTT of 150ms".

						Masataka Ohta