Re: Generic anycast addresses...

Ted Lemon <mellon@fugue.com> Fri, 12 July 2019 14:23 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 62CB91201B7 for <ipv6@ietfa.amsl.com>; Fri, 12 Jul 2019 07:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.603
X-Spam-Level:
X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 PfcgLyE7ocRk for <ipv6@ietfa.amsl.com>; Fri, 12 Jul 2019 07:23:57 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 1C327120196 for <6man@ietf.org>; Fri, 12 Jul 2019 07:23:52 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id r6so4054523qtt.0 for <6man@ietf.org>; Fri, 12 Jul 2019 07:23:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=1FLF6IUa9X+OsapwKviiU2sx2fxsVnUun/K7E8s9Dfs=; b=Rv/aAwwiIjleWGlRJl3Uoc/iT5gYM/FYyMXKEiDCuMA3taV4eeA18N/16CxyL9CA04 hVKvwkiaaysO5scipxogyMIF61OtxQ4hFPQjlOiiv5AF5JM81rn/6CBvm0LHRI+24pCk VQnEa9DUlwdWd4CHCRG5U8GLDwabrIvf4eryFyrSK2C9JxjGMvBYxdGrQpygWRlN4Olz 2JErGFMnnNEP2IdGY+F+hvE5tjqQ8dH7OpMfleqbUc1l/33ODJ1+y4R0I2K3GylyaT1Y w+SeA1HHJ0z8jljc/6Nl2IGQpfZrwaPiE1P41sUY7EaSS3n348MjvRjzGtGPMjpDb2V2 lEfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=1FLF6IUa9X+OsapwKviiU2sx2fxsVnUun/K7E8s9Dfs=; b=BDdQDRXULg7m9Y+Tx7g9vd+iw1fJ9F9kEyTg32b5NCOO+JGeqConXc1YFUDcvqGqeT 5TMPTLHI48hS0MXvdL2DPTZBSJw+7JtaKIZ59A/YQM9jih85NuUsrgBsdTwUytA0dz3M rAgt2gMWSZYbd//USQKEi83enORfQmTkoaEbWwFbVmI3B0rzeEQa0HEP2TvzjuWPep+H KaDAJgB7itwsgynYoWfpXwISZbMuNGuP/fU69U2FnQIpD/C7M1/PdpvG0cD0MaK73vM2 Mlxwl/ko4VIIwnj8rnJi/OZvHlWqyzj5hKf7jnwPI/rtGcQRZqEmr33vhF/4u1pziPWl F9aQ==
X-Gm-Message-State: APjAAAU0ZXEGYD9nlaDxxcpe29bZlCn5EWmtIMAk7EldHCpDDl5bncXx n/OcIOU/dbjzbThhKW78uwrGk3zL3c8=
X-Google-Smtp-Source: APXvYqwdPCYKGwtlx8zIK3tZ5ZDqrRgSVrMIt9N9aB3W+bKF9NXeezCz1/2D3+6H/9xlErwWTjiydA==
X-Received: by 2002:ac8:1a9d:: with SMTP id x29mr6716254qtj.128.1562941430991; Fri, 12 Jul 2019 07:23:50 -0700 (PDT)
Received: from ?IPv6:2001:470:c1a2:1:358d:7499:872b:5444? ([2001:470:c1a2:1:358d:7499:872b:5444]) by smtp.gmail.com with ESMTPSA id p23sm3374580qkm.55.2019.07.12.07.23.50 for <6man@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Jul 2019 07:23:50 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EDA83A33-411B-4109-A18A-18C2825D06A6"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Generic anycast addresses...
Date: Fri, 12 Jul 2019 10:23:42 -0400
References: <D22E680C-3EE3-4AD7-90C0-9339DA2E5A29@fugue.com> <F8BDFED1-744A-4476-9913-43D34AE15D67@fugue.com> <A053CAD6-F20A-4811-84FD-225ADDB1CD4D@fugue.com> <FDE52B38-D00F-4AB4-B3D3-B46ABA34CBEA@fugue.com>
To: 6MAN <6man@ietf.org>
In-Reply-To: <FDE52B38-D00F-4AB4-B3D3-B46ABA34CBEA@fugue.com>
Message-Id: <D7F1E070-2152-42E1-AE6E-C9277A574735@fugue.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/mrLewUWWKDwfxT621KGICJqRsX4>
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: Fri, 12 Jul 2019 14:23:59 -0000

On Jul 12, 2019, at 9:57 AM, Ted Lemon <mellon@fugue.com> wrote:
> Apparently I just can’t type IPv6 addresses.   Let’s try this one more time: 2001:1::/64.   But actually it looks like it’s 2001:1::/32.   This isn’t specifically stated anywhere, so we don’t really know, but the next non-/128 allocation is the next /32.

There’s no way to answer definitively.   Certainly the remainder of the /32 is unallocated.   However, the next thing that’s allocated is explicitly a /48, and the thing that follows that is a /32.   So 2001:2::/48 is allocated, but the rest of 2001:2::/32 is not.   If a /64 were needed, the IANA could decide to allocate 2001:1:0:1::/64 and this would not create a conflict.   But since this isn’t stated explicitly, we don’t know, and it’s entirely possible that IANA would not allocate that /64, since they probably don’t know either.

For reference, here’s the part of the table I’m talking about:

2001::/23	IETF Protocol Assignments	[RFC2928 <http://www.iana.org/go/rfc2928>]	2000-09	N/A	False [1 <https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml#note1>]	False [1 <https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml#note1>]	False [1 <https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml#note1>]	False [1 <https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml#note1>]	False
2001::/32	TEREDO	[RFC4380 <http://www.iana.org/go/rfc4380>] [RFC8190 <http://www.iana.org/go/rfc8190>]	2006-01	N/A	True	True	True	N/A [2 <https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml#note2>]	False
2001:1::1/128	Port Control Protocol Anycast	[RFC7723 <http://www.iana.org/go/rfc7723>]	2015-10	N/A	True	True	True	True	False
2001:1::2/128	Traversal Using Relays around NAT Anycast	[RFC8155 <http://www.iana.org/go/rfc8155>]	2017-02	N/A	True	True	True	True	False
2001:2::/48	Benchmarking	[RFC5180 <http://www.iana.org/go/rfc5180>][RFC Errata 1752 <http://www.rfc-editor.org/errata_search.php?eid=1752>]	2008-04	N/A	True	True	True	False	False
2001:3::/32	AMT	[RFC7450 <http://www.iana.org/go/rfc7450>]	2014-12	N/A	True	True	True	True	False
If your MUA rendered this incomprehensibly, here’s the actual URL for convenience: https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml <https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml>