Re: Generic anycast addresses...

Mikael Abrahamsson <swmike@swm.pp.se> Mon, 03 June 2019 15:08 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 854611202F1 for <ipv6@ietfa.amsl.com>; Mon, 3 Jun 2019 08:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.279
X-Spam-Level:
X-Spam-Status: No, score=-4.279 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 mX9yK4jPz3qE for <ipv6@ietfa.amsl.com>; Mon, 3 Jun 2019 08:08:37 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D94AD1202F0 for <6man@ietf.org>; Mon, 3 Jun 2019 08:08:36 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id E7059AF; Mon, 3 Jun 2019 17:08:33 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1559574513; bh=mkdEN4BJFw9HSByRvQP3WSwIxClVfXT7TnqC7WT71fk=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=pxe6uEJ/vrW8joZS8tHUSuw6mjYh1BLm/cPuP2nn5GOQe0Ie1n3zV4n8yZOcFLdag vtdxBMYWEANv77XU/NmJdnRhCCBD4AJvnUbGMlvyHfSK8QbVK0cez5D0mj8LT9OIll Zyqj+VGZgb/eb+dQhi9/8KbWXrwq+ynP7VIJ0aI8=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id E4D039F; Mon, 3 Jun 2019 17:08:33 +0200 (CEST)
Date: Mon, 03 Jun 2019 17:08:33 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Michael Richardson <mcr+ietf@sandelman.ca>
cc: 6MAN <6man@ietf.org>
Subject: Re: Generic anycast addresses...
In-Reply-To: <20612.1559573730@localhost>
Message-ID: <alpine.DEB.2.20.1906031703430.19892@uplift.swm.pp.se>
References: <D22E680C-3EE3-4AD7-90C0-9339DA2E5A29@fugue.com> <4EF97F31-1F39-4150-B044-955C46E96FB4@fugue.com> <20190530002833.wfvjfbj2lv2ig664@faui48f.informatik.uni-erlangen.de> <7A9560FC-0393-45DF-8389-B868455AC6DD@fugue.com> <20190530005734.7d2alod2zoaemmhc@faui48f.informatik.uni-erlangen.de> <D6E27B45-437F-45BE-A305-47DD460BCE02@fugue.com> <26144.1559226966@localhost> <1DD451A7-D898-4105-974C-53776A3DA9F2@fugue.com> <20190530152902.l2nmyhadr4e4kt7x@faui48f.informatik.uni-erlangen.de> <0FF19D6D-1A45-41EF-BE34-CC35B5E51E1E@steffann.nl> <D91629F6-73AC-4A80-80EF-16644F73DA36@fugue.com> <701687d4-842c-6a16-3c97-349125324e3f@gmail.com> <D648647D-60E1-4DCE-B0BE-11002E0AE5A4@fugue.com> <25631.1559317738@localhost> <CAO42Z2x9iTrbvZuCxqSpDX-CQ9MtY8V1yyb-hg+XYtXXYn7LKg@mail.gmail.com> <9021.1559397908@localhost> <7cec7521-7e14-0eae-c166-2c727324dc5e@gmail.com> <CAO42Z2wwC5rjP91qG6nxsaj=0HBKPFzbOXdgGPiTT=pcDjW-+ w@mail.gmail.com> <20612.1559573730@localhost>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0BcoNb6ghnWw3JvcRBxeweb7aO8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jun 2019 15:08:39 -0000

On Mon, 3 Jun 2019, Michael Richardson wrote:

> My ISP does DHCPv6-PD correctly now, but alas, isn't providing the 
> correct prefix.  In debugging, I noticed that it is now using 
> Source-Address specific routing:

Yes, openWrt has done that for a while. I am surprised cerowrt didn't.

> root@budwrt18:/etc/config# ip -6 route
> default from 2607:f0b0:7:1d0::/64 via fe80::fe5b:39ff:fe89:7b00 dev pppoe-wan  metric 512
> default from 2607:f0b0:7:8350::/64 via fe80::fe5b:39ff:fe89:7b00 dev pppoe-wan  metric 512
>
> (why two prefixes, I'm unclear)

Is your ISP only handing you /64 and no /56? This is what I have (I have 
another router in my home that gets /62 from my openwrt router):

default from 2001:9b0:XXXX:XX00::/56 via fe80::e681:84ff:fe41:740f dev eth1.2 proto static metric 512 pref medium

2001:9b0:21a:3100::/64 dev br-lan proto static metric 1024 pref medium

2001:9b0:XXXX:XX08::/62 via fe80::6666:b3ff:fede:fffd dev br-lan proto static metric 1024 pref medium

unreachable 2001:9b0:XXXX:XX00::/56 dev lo proto static metric 2147483647 error -113 pref medium

If I would have had multiple uplinks and had two different ISPs both 
handing me /56:es, this would have properly made source based routing to 
work to avoid BCP38 filtering on the upstream.

> The upshot is that all other prefixes will fall flat at the border, 
> which is rather what we want.

My biggest beef with the scoping is that we're going to have to agree on 
topology, what a "site" is, etc. This has been historically hard.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se