Re: Generic anycast addresses...

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 31 May 2019 09:11 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 443511200B2 for <ipv6@ietfa.amsl.com>; Fri, 31 May 2019 02:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 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, SPF_HELO_NONE=0.001, SPF_PASS=-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 kAIE5XLFMx6x for <ipv6@ietfa.amsl.com>; Fri, 31 May 2019 02:11:29 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 EFE7D12008B for <6man@ietf.org>; Fri, 31 May 2019 02:11:28 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id F133FAF; Fri, 31 May 2019 11:11:24 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1559293884; bh=9/m1jazwMlBdutrUtj4vRFUeSOSD+Zvp6zReVKPztzg=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=MkXvIPu4YrPq6WSWu/kk3ycvk2Zt38mKELe72U9ZcFYAV8qGkvWC9n7Ylc01pka3U 5S5dQXB1RIwuvrBxpvcsrVZ8YPK55bA2BoHRNWTJ61EtTHkiKDlr3+DAPguEPa3wIL Lx+6uddwhcZ0yl/qREkDdg4qD6oejvDpP3iyo4KE=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id EF0D99F; Fri, 31 May 2019 11:11:24 +0200 (CEST)
Date: Fri, 31 May 2019 11:11:24 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
cc: "6man@ietf.org" <6man@ietf.org>
Subject: Re: Generic anycast addresses...
In-Reply-To: <F1401F04-550E-41EA-880E-F66D464B3554@fugue.com>
Message-ID: <alpine.DEB.2.20.1905311101160.2454@uplift.swm.pp.se>
References: <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> <20190530220838.g2hshonsjxmfnd55@faui48f.informatik.uni-erlangen.de> <632BE7EC-26A6-44E9-9CCD-F0AE143D4256@fugue.com> <AF1967FC-526D-47FB-98BE-F9B949F26796@steffann.nl> <CAO42Z2yY=z-wKCUaCYZqJLHfT+LdyDOWz9bLG8QTh9C8sJCx3g@mail.gmail.com> <F3E48F41-DED1-4D5D-AEC1-A01356D4110B@fugue.com> <CAO42Z2xXbwUd6G2EZcUvPStP8acyM=Dt8n-R=Cdpra+wMwWf3Q@mail.gmail.com> <F1401F04-550E-41EA-880E-F66D464B3554@fugue.com>
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/hQ0Ev6miraVRRTPtCwmAkjXsFnU>
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: Fri, 31 May 2019 09:11:32 -0000

On Thu, 30 May 2019, Ted Lemon wrote:

I tried to read up on this thread, and I don't think I understand the 
use-case still.

However, since I didn't see anyone mention it in the discussion yet we do 
have a WKP from another somewhat similar deployment case (unless I didn't 
understand correctly):

https://tools.ietf.org/html/rfc6052#section-2.1 , the 64:ff9b::/96 prefix 
for NAT64, out of global scope. However, you typically need the traffic to 
only hit one of these (because of state), so I guess they will not be BGP 
anycasted.

For AFTRs for LW4o6 and MAP-E (which are stateless and thus works nicely 
with BGP anycast), people will deploy these using BGP anycast in their 
networks, numbered out of their own LIR allocated GUA global scope address 
space.

So... again, I'm not sure I didn't miss just everything in the discussion, 
so if I'm completely off above, could someone please sum up the discussion 
again with what you've agreed on?

Numerous times in the discussion the term "scoped address" was used, but I 
never understood what scope was intended in the statement.

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