IETF Logo Mail Archive

Re: Generic anycast addresses...

Ted Lemon <mellon@fugue.com> Mon, 03 June 2019 18:48 UTC

Return-Path: <mellon@fugue.com>
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 7532A120155 for <ipv6@ietfa.amsl.com>; Mon, 3 Jun 2019 11:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 tGUNJbMGCYaR for <ipv6@ietfa.amsl.com>; Mon, 3 Jun 2019 11:48:13 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17997120043 for <6man@ietf.org>; Mon, 3 Jun 2019 11:48:13 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id s22so1106800qkj.12 for <6man@ietf.org>; Mon, 03 Jun 2019 11:48:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=i18OYuoL6Qp9/57xgv3VugwhufaDb5soL+dGR5KLFTY=; b=iEVF6qpSGePzqNuqPFQnytDoIs/7LfD4Kes8Jd7xXARTSWzxB0ZBKnLiK3oEOOlxaw vfm8gGUO1fM/PVRZvQRC3FKU53RLW0IFL4ZdyoTn3ZtfwI9Sp/3dshjBDS3u1GZgqRPN NlS9A40Qs7bpzEnyqX4ZDbQahlXzMmQ6kPS+hOpkLRyOhmUtJUo4iEoCIPteyWIO6QqJ oSBw7orihUQRSfwRRyoTDgzyxlbB2PaE2uKXyBRuheLLpl81B4tSR1EN/kElf/TOMfCa x8AXqEsncKxC0r3uGEoz8FgaugsphzPwfbtHyJ0jwrm7k99/QIOVbEeobP3uOT6ZGo4X FJBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=i18OYuoL6Qp9/57xgv3VugwhufaDb5soL+dGR5KLFTY=; b=S6YPYObI4LoF3z5cCZsSNO98IE82x7bbgS+av7Mwkl8FLuHyinz5s9VmMTzSJav3Lo ssNgFP4d+NAjRrxcpOs2K6JxYBMxZwXmqVIo9pM+QwtTEYyqhCdSwZTaGWaT4Q3oRW1j HQilt2ugpgm/9U32S4gu7iuuLX9MWNvPrcZieR08SC599CiHxvx4nhbZ6LJS1P7LvdIt uoWB32oS6OcvnJHqW/qBauvIbS5nhJ92I5QbMDdiJUPL+jVDh/D/DWjIfELtddHqMKEN XiYWvoWuWA64xYCxNk61IpcBHCE+pUcYTa50RvZTIqq6VqM4rqkVnrbrTLtZsh47UB+L Qm7Q==
X-Gm-Message-State: APjAAAULFPGGHIZBkiiMbBxtoqthnhInlj1PLPTjiDtGp9LN+5I6nevU YjYQE/R3X9hGoZixckEPCuIDr8OZxONZXg==
X-Google-Smtp-Source: APXvYqxv37oKZgbqDkLAt/m0ldb1oiURBoDpen4lsYjN/aUQMYnHHCVQTqq3W5v44oD5pKjvb98EdQ==
X-Received: by 2002:a37:e10e:: with SMTP id c14mr4543610qkm.54.1559587692099; Mon, 03 Jun 2019 11:48:12 -0700 (PDT)
Received: from [10.0.30.11] (c-73-186-137-119.hsd1.nh.comcast.net. [73.186.137.119]) by smtp.gmail.com with ESMTPSA id d38sm3104393qtb.95.2019.06.03.11.48.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 03 Jun 2019 11:48:11 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
Subject: Re: Generic anycast addresses...
From: Ted Lemon <mellon@fugue.com>
X-Mailer: iPhone Mail (16G41)
In-Reply-To: <18416.1559587590@localhost>
Date: Mon, 03 Jun 2019 14:48:10 -0400
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, 6MAN <6man@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <01CFF2B0-7024-498A-B7F4-D316870B7354@fugue.com>
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> <alpine.DEB.2.20.1906031703430.19 892@uplift.swm.pp.se> <18416.1559587590@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/MmZpxxPtYoFYdPdb5dvCZXpfw6Y>
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 18:48:15 -0000

What size prefix are you requesting?

Sent from my iPhone

> On Jun 3, 2019, at 2:46 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Mikael Abrahamsson <swmike@swm.pp.se> 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):
> 
> I'm not sure.
> I have a /56 statically routed to me, but that was done before they could
> support PD.   I don't know why I have two different /64s delegated, and I've
> already asked about this.
> 
>>> 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.
> 
> I know, but I think that it's okay if we get it right automatically for 80%
> of the cases, as they probably cover 99% of the usage.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email