IETF Logo Mail Archive

Re: Generic anycast addresses...

Ted Lemon <mellon@fugue.com> Thu, 30 May 2019 23:04 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 CB4AF120176 for <ipv6@ietfa.amsl.com>; Thu, 30 May 2019 16:04:23 -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 UpTIR8gTFkVj for <ipv6@ietfa.amsl.com>; Thu, 30 May 2019 16:04:22 -0700 (PDT)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (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 F05A612016F for <6man@ietf.org>; Thu, 30 May 2019 16:04:21 -0700 (PDT)
Received: by mail-pl1-x62f.google.com with SMTP id d21so3170976plr.3 for <6man@ietf.org>; Thu, 30 May 2019 16:04:21 -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=YJaySraJvnsRG01TJSzK57A8pbJEE5cSdc5IT6C/+cs=; b=XhGLS1RacbumbTXKN2VeJ1TA22XFJOg0HWuP0dGbAhXxCc7BKBuRb1anA7DXEuKwEQ kNKUKn7ciupkOhWiE6nrlWtDOnVtWmY/SM8ZueAwRL1ii3x/inUg+7opBlOSEIRujOOB 8LAIuUybGuwRTuFfXYfWZIGyemPUlayl/FizQLlrR++Bk34OFwD9rpjxwbXntDuXITOF 4UryEiqKOxJpQfPrJ3e9ApnZxKpP8MUMks++8qYCUNy1LZgcBLQ6BrZdjFQdIHSQeSky rlD7lI/ZY/9nsbzl7pb/6QGlp36HZOmBZhoGCSjpEeQX3eRVkBIfr/otPzQ3BZw9LL82 3LyA==
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=YJaySraJvnsRG01TJSzK57A8pbJEE5cSdc5IT6C/+cs=; b=a3Vflgi32cCgjO3sduBbeDu+F2aeedu/Uk7W06YCcFE1gYH7eoIQ+VjQFk8E5gH4b3 WOBSFpwDV+leFuJpXvuLRU95zkCutVjbztOCsMFtVGO/pSyu7XoI0uMRzTJg8edRNSAH w0b8sWaFQfxKKRwGBu7PYZSJTECd1K2N/Ppj1uRVCCKNyCWuv2NopCcGLYyFXOSXHYip eWxLUTqUn7jZrvc9t1l01JQQiCH5ktNfUhCEJmv/Ra4RaDIAZ9mTipaZE0AbfxxkNM2W nMftw/i52LgbMsHyjZd15aSiWp1RSJ+XevREEOkVrfAlXx560U6DRE0sFClO0rDVyih2 PyBQ==
X-Gm-Message-State: APjAAAVRazG+AEcZflZER4sE8q6w7l1aauRc3m5giGzZwgWWvxKRYYGf uof8w5f04GcnOGGKiPicEBq+Qg==
X-Google-Smtp-Source: APXvYqw5PrSEPScLHZ6m1EJqmqTYF+wu2aZGEtMFX29Nn/+ZOPzBwss6t5CAutTYvJuT/lvCKyc2cw==
X-Received: by 2002:a17:902:690b:: with SMTP id j11mr5949895plk.149.1559257461282; Thu, 30 May 2019 16:04:21 -0700 (PDT)
Received: from [17.230.172.14] ([17.230.172.14]) by smtp.gmail.com with ESMTPSA id k3sm3563731pgo.81.2019.05.30.16.04.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 May 2019 16:04:20 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <ED6DA426-630A-4056-83F5-DE61FDA21EF5@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EA58D8DA-FAD6-4130-B5B2-1EFDF4C0D01E"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Generic anycast addresses...
Date: Thu, 30 May 2019 16:04:19 -0700
In-Reply-To: <AF1967FC-526D-47FB-98BE-F9B949F26796@steffann.nl>
Cc: Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>
To: Sander Steffann <sander@steffann.nl>
References: <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> <D91629F6-73AC-4A80-80EF-16644F73DA36@fugue.com> <701687d4-842c-6a16-3c97-349125324e3f@gmail.com> <D648647D-60E1-4DCE-B0BE-11002E0AE5A4@fugue.com> <20190530220838.g2hshonsjxmfnd55@faui48f.informatik.uni-erlangen.de> <632BE7EC-26A6-44E9-9CCD-F0AE143D4256@fugue.com> <AF1967FC-526D-47FB-98BE-F9B949F26796@steffann.nl>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/p-iczqsEuGnidqYQNsfkhmVEQSc>
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 23:04:24 -0000

On May 30, 2019, at 3:53 PM, Sander Steffann <sander@steffann.nl> wrote:
> I like the scope aspect of Mark's draft. ULA is always organisation or site scoped, and should be filtered as such. Anycast that have a different scope should have different boundaries. Anycast addresses that have ISP scope can cross from the customer's network to the ISP's network, while there should be a boundary between that customer's ULA addresses and that ISP's ULA addresses (let's assume they both use ULA for this example).

I agree that this makes sense in principle.   But I think it’s a lot fuzzier than you’re at least allowing for.   As I pointed out previously, what “ISP scope means” when you are at a site that’s multi-homed is impossible to specify, because there is more than one scope that could be called “ISP scope,” and the scopes are disjoint.

Therefore I would prefer not to wait for this seemingly intractable problem to be solved before solving the problem that I’m actually trying to solve.

v2.23.0 | Report a Bug | By Email