Re: IPv6 Formal Anycast Addresses and Functional Anycast Addresses (Fwd: New Version Notification for draft-smith-6man-form-func-anycast-addresses-01.txt)

Toerless Eckert <tte@cs.fau.de> Sun, 03 November 2019 21:27 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 06ED9120123 for <ipv6@ietfa.amsl.com>; Sun, 3 Nov 2019 13:27:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.95
X-Spam-Level:
X-Spam-Status: No, score=-3.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 odOCI1qzdQkK for <ipv6@ietfa.amsl.com>; Sun, 3 Nov 2019 13:27:18 -0800 (PST)
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 C990E120120 for <6man@ietf.org>; Sun, 3 Nov 2019 13:27:17 -0800 (PST)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 875A054802E; Sun, 3 Nov 2019 22:27:12 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 7C0B8440015; Sun, 3 Nov 2019 22:27:12 +0100 (CET)
Date: Sun, 3 Nov 2019 22:27:12 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: Mark Smith <markzzzsmith@gmail.com>, 6MAN <6man@ietf.org>
Subject: Re: IPv6 Formal Anycast Addresses and Functional Anycast Addresses (Fwd: New Version Notification for draft-smith-6man-form-func-anycast-addresses-01.txt)
Message-ID: <20191103212712.GK2287@faui48f.informatik.uni-erlangen.de>
References: <157277906705.13535.345852921709779212.idtracker@ietfa.amsl.com> <CAO42Z2wSU-puDaQq-PzTCTE=S3qyqUNrPhH0pgOEO_d3=StnHA@mail.gmail.com> <b97c15c0-b1fe-0d78-0897-5fc4bb6a9a34@foobar.org> <B42E6EED-5620-49BE-BB3D-B1CF6F04A1CC@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B42E6EED-5620-49BE-BB3D-B1CF6F04A1CC@gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aoBV_1UAeNJNP7Di6WymauoFNL0>
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: Sun, 03 Nov 2019 21:27:21 -0000

It is somewhat architecturally dissatisfying that (AFAIK) we seem to need to
resolve limitations of anycast addresses at the transport layer,
e.g.: redirecting connection requests to an anycast address to a
unicast address of the transport responder. If initiators would know an address is
an anycast address, they could use some TBD network layer (ICMP) extension
to do that resolution independent of individual transport protocols.

And the network layer would only know it needed to do this if there was
a way for the initiator to identify an address as an anycast address
AFAIK (can't think of a simpler way).

Cheers
    toerless

On Sun, Nov 03, 2019 at 01:59:24PM -0500, Fred Baker wrote:
> On Nov 3, 2019, at 9:23 AM, Nick Hilliard <nick@foobar.org>; wrote:
> > If you create an anycast protocol which has characteristics which are sufficiently different to unicast that it requires a separate addressing schema, then by all means it would be appropriate to create an addressing schema to fit in with this.  The determinant here would be that global unicast addresses would not be usable for this protocol. Until then, a separate address block is mostly a matter of aesthetics.
> 
> I would agree. I did some poking around to identify anycast address groups. The IANA has records for three. RFC 4291 has a fourth, which is subnet anycast which is supposed to get a packet to a router I'm not sure I can say how widely deployed any of those are. 
> 
> https://www.iana.org/assignments/ipv6-anycast-addresses/ipv6-anycast-addresses.xml
> RFC 2526             Mobile IPv6 Home-Agents anycast
> ETSI EN 302 636-6-1  IPv6 over GeoNetworking geographic anycast	
> RFC 4291             IPv6 Anycast Subnet-Router Anycast Address
> 
> On the other hand, there are a number of unicast addresses in daily use worldwide as anycast, which are the addresses one uses to access the DNS root. Collected statistics tell us that on the order of 10% of DNS requests to the root use IPv6, and the rest are IPv4. So I would say that the use of unicast addresses as anycast has a strong supporting case.
> 
> https://www.iana.org/domains/root/servers
> https://root-servers.org/
> 
> The one use case that your draft mentions that seemed to be new was that of a network operator that wanted to deploy an anycast service, but only to its customers. It, however, seemed to be hypothetical. Do you know of operators or services that have that requirement?
> 
> In other words, I'm wondering whether there is a problem being solved, or an architectural preference.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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