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 23:32 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 7E3BE120100 for <irtf-discuss@ietfa.amsl.com>; Wed, 21 Aug 2019 16:32:26 -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 UR-t2NX94XjQ for <irtf-discuss@ietfa.amsl.com>; Wed, 21 Aug 2019 16:32: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 50370120043 for <irtf-discuss@irtf.org>; Wed, 21 Aug 2019 16:32:25 -0700 (PDT)
Received: (qmail 61844 invoked from network); 21 Aug 2019 23:13:37 -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 23:13:37 -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> <ffa5248f-4fb3-32d2-1ec4-aeb9621c0787@necom830.hpcl.titech.ac.jp> <CAOj+MMHde82V-eZ78iPq8L52WCFOZWbF7-mSM19Q24FxXZz6Kw@mail.gmail.com>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-ID: <2cfb0063-4ed1-096f-f219-df96d24f4c88@necom830.hpcl.titech.ac.jp>
Date: Thu, 22 Aug 2019 08:25:41 +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+MMHde82V-eZ78iPq8L52WCFOZWbF7-mSM19Q24FxXZz6Kw@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/FVn8DsOzxItRkKGQGf0dQdl2PCk>
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 23:32:27 -0000

Robert Raszuk wrote:

> To configure exit path selection such that you take optimal exit to 
> destination X vs destination Y you need mechanism to either
> passively or actively measure it. The entire point I am trying to
> make here is that sweet spot for such measurements is the edge of the
> network and not on each host, VM, container etc ....

As I wrote:

    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.

BGP routers are at the edge.

> Of course even if I would carry selective destinations in IGP with 
> properly mapped metrics how would host learn about it when it has to 
> pick the src address from N available in end to end multi homing 
> principle ? Is the assumption again that hosts, VMs, LXCs
> participate now in the IGP ?

I know poor source address selection is a flaw of current IP (both
v4 and v6).

> And even if it would be a passive IGP listener how do you encode in 
> any IGP today which src address should be selected such that packets
> wil not be dropped due to uRPF check by the upstream provider ?

For the solution, read the draft:

    Any source address may be selected.

    However, to enable source address filtering to discard packets with
    source addresses not belonging to an ISP, it is useful to enable a
    host, not some intelligent intermediate router, select a source
    address compatible with an outgoing ISP.  For that purpose, intra
    domain routing protocols should maintain routing table entries with
    not only preference values of an external routes, but also proper
    prefixes to be selected for source addresses, if the entries are
    chosen by a host.

						Masataka Ohta