IETF Logo Mail Archive

Re: Generic anycast addresses...

Sander Steffann <sander@steffann.nl> Thu, 30 May 2019 15:48 UTC

Return-Path: <sander@steffann.nl>
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 16CC012015A for <ipv6@ietfa.amsl.com>; Thu, 30 May 2019 08:48:24 -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=steffann.nl
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 sOhHecLPlv8y for <ipv6@ietfa.amsl.com>; Thu, 30 May 2019 08:48:22 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [83.247.10.6]) (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 0789F12013B for <6man@ietf.org>; Thu, 30 May 2019 08:48:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 301FA71; Thu, 30 May 2019 17:48:19 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:in-reply-to:date:date:subject:subject :mime-version:content-type:content-type:message-id:from:from :received:received; s=mail; t=1559231297; bh=0RjdZNjk1Z47hjMLf13 +4TSJ3bZtutfsUpFpc98bc6Q=; b=kHPVx9hPOizphK/O5zF0s+EzjzpMMciIzz7 leFBME6Wrw4BmTgYVsAJOhCyI3cQh2onj+xnzLSrnpHm4SiX/Y++ZEbUDW4D858V JnHHubA1fMJbevgu2siLhe4nkr9cmTukECMs/e+yrNUTrpOgFpuKRO8/xjde309c L1Pb3W/s=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id CtO83-fNi1kH; Thu, 30 May 2019 17:48:17 +0200 (CEST)
Received: from [IPv6:2a02:a213:a300:ce80:3cac:a6d:c809:5674] (unknown [IPv6:2a02:a213:a300:ce80:3cac:a6d:c809:5674]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id 634AE6F; Thu, 30 May 2019 17:48:16 +0200 (CEST)
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
Message-Id: <0FF19D6D-1A45-41EF-BE34-CC35B5E51E1E@steffann.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_8D550238-98B1-4641-A9BF-B0DCBCAB0D3B"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Generic anycast addresses...
Date: Thu, 30 May 2019 17:48:15 +0200
In-Reply-To: <20190530152902.l2nmyhadr4e4kt7x@faui48f.informatik.uni-erlangen.de>
Cc: Ted Lemon <mellon@fugue.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>
To: Toerless Eckert <tte@cs.fau.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> <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>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FT5et9D0ClddHhNcPnekWpTew5s>
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 15:48:24 -0000

Hi,

> I still haven't seen an argument why this anycast scoped app could not
> simply use an existing ULA prefix. AFAIK, there is nothing prohibiting
> the author of an app using ULA to pick the randomn ULA prefix and write
> it into an RFC.

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.

> 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.

Cheers,
Sander

v2.23.0 | Report a Bug | By Email