Re: Generic anycast addresses...

Toerless Eckert <tte@cs.fau.de> Thu, 30 May 2019 20:29 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 7E7B6120137 for <ipv6@ietfa.amsl.com>; Thu, 30 May 2019 13:29:10 -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 qAv7dEHK7_Dk for <ipv6@ietfa.amsl.com>; Thu, 30 May 2019 13:29:08 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.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 C4A8812001A for <6man@ietf.org>; Thu, 30 May 2019 13:29:07 -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 CD63954807D; Thu, 30 May 2019 22:29:02 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id B7081440041; Thu, 30 May 2019 22:29:02 +0200 (CEST)
Date: Thu, 30 May 2019 22:29:02 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Sander Steffann <sander@steffann.nl>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: Generic anycast addresses...
Message-ID: <20190530202902.ocpxn6kp7qs7ws5n@faui48f.informatik.uni-erlangen.de>
References: <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> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <0FF19D6D-1A45-41EF-BE34-CC35B5E51E1E@steffann.nl>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/uCtk6VL19Pt6fwaJwbpYgZcUHi4>
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 20:29:11 -0000

On Thu, May 30, 2019 at 05:48:15PM +0200, Sander Steffann wrote:
> Addresses in ULA space are expected to be used in a certain way, and scoped (well-known) anycast addresses in another. Let's keep things simple and use ULA space for ULA and a different (and more easily recognisable) prefix for anycast.

No, thats not a real justification. I could equally say that unicast
addresses are expected to be used in a certain way an anycast addresses
in another.

I also don't see how scoping changes anything wrt. whether or not
ULA could be used.

> > Of course, you want to make sure that your scheme still
> > works when multiple instances of that application/side do interconnect,
> > but th way i understand what you want to do, that would be the case.
> > 
> > I am not saying this is the best way, i am just saying that i hven't
> > seen enough evidence to try to create more RIR work.
> 
> IMHO there should be well-known anycast addresses managed by IETF/IANA/etc. I agree that this is something that doesn't belong with the RIRs.

Well. i made my points why i think this is not a good solution.

Cheers
    Toerless

> Cheers,
> Sander
> 



> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


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