IETF Logo Mail Archive

Re: Generic anycast addresses...

Toerless Eckert <tte@cs.fau.de> Thu, 30 May 2019 00:57 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 6CB0E120041 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2019 17:57:40 -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 EGkf8bYs-CPv for <ipv6@ietfa.amsl.com>; Wed, 29 May 2019 17:57:39 -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 35A8D12003F for <6man@ietf.org>; Wed, 29 May 2019 17:57:39 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id DD3AB5488AE; Thu, 30 May 2019 02:57:34 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id CDC0F440041; Thu, 30 May 2019 02:57:34 +0200 (CEST)
Date: Thu, 30 May 2019 02:57:34 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Ted Lemon <mellon@fugue.com>
Cc: Dave Thaler <dthaler@microsoft.com>, "6man@ietf.org" <6man@ietf.org>
Subject: Re: Generic anycast addresses...
Message-ID: <20190530005734.7d2alod2zoaemmhc@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <7A9560FC-0393-45DF-8389-B868455AC6DD@fugue.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/LAjUZSOqQEopXL0kUK_awcQEoD4>
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:57:41 -0000

I cant brainstorm a lot more without more details of what you're
trying to achieve, and  therefore what the constraints are.

Worst case, you float the idea to a single ULA prefix defined
by your RFCs mecanism and see how reviewers like this. At least its
a lot better than trying to define a "well known" rfc1918
anycast address - because your application defined ULA
prefix has a very low probability of colliding with somebodies
actually used ULA prefix. 

On Wed, May 29, 2019 at 05:41:04PM -0700, Ted Lemon 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.

-- 
---
tte@cs.fau.de

v2.23.0 | Report a Bug | By Email