Re: Generic anycast addresses...

Ted Lemon <mellon@fugue.com> Thu, 30 May 2019 00:59 UTC

Return-Path: <mellon@fugue.com>
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 D0BAE12023C for <ipv6@ietfa.amsl.com>; Wed, 29 May 2019 17:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 jpUH-iovjRPy for <ipv6@ietfa.amsl.com>; Wed, 29 May 2019 17:59:32 -0700 (PDT)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1369F120223 for <6man@ietf.org>; Wed, 29 May 2019 17:59:32 -0700 (PDT)
Received: by mail-pf1-x435.google.com with SMTP id d126so2795503pfd.2 for <6man@ietf.org>; Wed, 29 May 2019 17:59:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=CVi7sxMguRQTt2V2THoJsyr1yqqMCX4a2tVrGvhOCKc=; b=G2k27NNmvqe9XZWpWFaAhsLaOmQ2ZwBCgqkcjRRnsMkCjruo5GV1Q/ka8fJgzTZm8k bZIB5YtobdMiwnstA+4rJBdRb9vwlKCcBcviS+gxcPMjX0ZCl4uDy20piQD2FbkaiilH VYvam8N7J5CBV3mMsAa3evi4QhEbBhxlgN6AN4yXawHOkCh1MmOkjQuDZGKLzMD8X/Ek 1hjx5rAjKTDuXkfcRj9v3IHKBa9FoutlNGkVJYpxDdbXDYHUkI8tzHJC3PIUCSkJUAvh OzS6k1cEbDD80UUm5D3Xv1ehmFjFuuJAQcfQUSFOGegejFaaeJprtwtrc3Zgt410YabA XSnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=CVi7sxMguRQTt2V2THoJsyr1yqqMCX4a2tVrGvhOCKc=; b=ixS3GPRPk2RGD1op6cJFRzrQbluKptBopIBdhpwbZAZEoaSB1jQq38s02lJL334iF2 y/p3mELPcpUNa9F0plGLIDKFv6LdEmYsswQZGx/LFOmNaqcrJ3TP2VPlyp1IQPAdDFY8 pf9XKVWWYNyTuZSwGMVFhXgROv7vXxOAyB5R4cGBQ/dJfhwZR5v28GI9K9xCyHCgIARP H7Ejk0tsu8RB9NNPVYeCum/dKc2ngcUcQa7WcnudKJPAVPgmEJQkVDg3yJbpJF2PxcA7 1kkETJu1ZlsxV+W60eXuhm/X+9gNepwtKl+ho1SS/WsZKgtHwcIHeIHpFRz3oxsExamo yN3A==
X-Gm-Message-State: APjAAAXqQQYQvgqlroK+H8vcPTN9KCT4bmbwbn+huXu1SCiY+rEAubDH i868UE2qi2rSkmWrD5OSuFb9LmnISeE=
X-Google-Smtp-Source: APXvYqwyZTi1f/zeVCcJjILGY32e3FhP4F7Rr5RB51KbLnI2cjX8L4RTisXtOeHJmD36I/1JdN51QA==
X-Received: by 2002:a17:90a:5d15:: with SMTP id s21mr842178pji.126.1559177971523; Wed, 29 May 2019 17:59:31 -0700 (PDT)
Received: from [17.230.171.24] ([17.230.171.24]) by smtp.gmail.com with ESMTPSA id b15sm352879pfi.141.2019.05.29.17.59.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 May 2019 17:59:30 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <D6E27B45-437F-45BE-A305-47DD460BCE02@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EC7B6DC6-088D-4BFC-AA0A-C053F3B9B54B"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Generic anycast addresses...
Date: Wed, 29 May 2019 17:59:28 -0700
In-Reply-To: <20190530005734.7d2alod2zoaemmhc@faui48f.informatik.uni-erlangen.de>
Cc: Dave Thaler <dthaler@microsoft.com>, "6man@ietf.org" <6man@ietf.org>
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>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/oQrk1TeB2b5K8RNwyCsL39IAsPE>
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:41 -0000

On May 29, 2019, at 5:57 PM, Toerless Eckert <tte@cs.fau.de> wrote:
> 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.

I think if it makes sense to do this, we should probably allocate a prefix as Bob suggested, and then reserve that for this general purpose.   I don’t think we should invent this scheme in a particular document that’s being worked on in dnssd.  :)