Re: Generic anycast addresses...

Toerless Eckert <tte@cs.fau.de> Thu, 30 May 2019 00:59 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 3AFF2120041 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2019 17:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 yvy9Au7ChKZ4 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2019 17:59:25 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6ED7D12003F for <6man@ietf.org>; Wed, 29 May 2019 17:59:25 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id EDD3F54807D; Thu, 30 May 2019 02:59:20 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id DD405440041; Thu, 30 May 2019 02:59:20 +0200 (CEST)
Date: Thu, 30 May 2019 02:59:20 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Bob Hinden <bob.hinden@gmail.com>
Cc: Ted Lemon <mellon@fugue.com>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: Generic anycast addresses...
Message-ID: <20190530005920.envuazcwnguppjse@faui48f.informatik.uni-erlangen.de>
References: <D22E680C-3EE3-4AD7-90C0-9339DA2E5A29@fugue.com> <BN6PR21MB04978DB375C05CB3CE4C914EA31F0@BN6PR21MB0497.namprd21.prod.outlook.com> <4EF97F31-1F39-4150-B044-955C46E96FB4@fugue.com> <20190530002833.wfvjfbj2lv2ig664@faui48f.informatik.uni-erlangen.de> <7A9560FC-0393-45DF-8389-B868455AC6DD@fugue.com> <83ABDD66-9B41-4845-A958-5B721FE78C1B@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <83ABDD66-9B41-4845-A958-5B721FE78C1B@gmail.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ijD3HKoJYzdsve7u5N5sAEnPR98>
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: Thu, 30 May 2019 00:59:28 -0000

Yepp. we brainstormed reviving the definition for that bit when doing ACP
in ANIMA, but felt it would be too much work.

I would have loved if some of the informal sites on the internet where
you could list your ULA prefix use would still be there, but they all
seemed to have died ;-(

On Wed, May 29, 2019 at 05:48:19PM -0700, Bob Hinden wrote:
> Ted,
> 
> > On May 29, 2019, at 5:41 PM, Ted Lemon <mellon@fugue.com> wrote:
> > 
> > Indeed, the propagation pattern of a ULA would work nicely for this, but there???s no way to do this automatically.   I might have (and indeed unfortunately it???s common to have) more than one ULA on a constrained network.   How do I pick?   :)
> > 
> > So what I really want is indeed something that is treated like a ULA, but that can be a constant, and not something that has to be derived.
> 
> We when ULAs were being developed, there was a notion of centrally assigned ULAs.  It???s not currently defined, but that???s was the original intent for having the ???L??? bit in the prefix.  See RFC4193.
> 
> Bob
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------