Re: Generic anycast addresses...

Toerless Eckert <tte@cs.fau.de> Mon, 03 June 2019 23:31 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 B3D761205EF for <ipv6@ietfa.amsl.com>; Mon, 3 Jun 2019 16:31:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 Y9CZGOp4I_OJ for <ipv6@ietfa.amsl.com>; Mon, 3 Jun 2019 16:31:20 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff: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 5C9581201A2 for <6man@ietf.org>; Mon, 3 Jun 2019 16:31:20 -0700 (PDT)
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 5F503548918; Tue, 4 Jun 2019 01:31:15 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4C1BD440041; Tue, 4 Jun 2019 01:31:15 +0200 (CEST)
Date: Tue, 04 Jun 2019 01:31:15 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Nick Hilliard <nick@foobar.org>
Cc: 6MAN <6man@ietf.org>
Subject: Re: Generic anycast addresses...
Message-ID: <20190603233115.nn2cv5yl47qmhjk5@faui48f.informatik.uni-erlangen.de>
References: <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> <25631.1559317738@localhost> <CAO42Z2x9iTrbvZuCxqSpDX-CQ9MtY8V1yyb-hg+XYtXXYn7LKg@mail.gmail.com> <9021.1559397908@localhost> <CAO42Z2xDUYOZqQ2_gjApifaPO3uG-kzjHpzND3nBD=hzw1TW2A@mail.gmail.com> <20190602130300.ebqbmvhb47r7pdog@faui48f.informatik.uni-erlangen.de> <0b32500d-5b26-60e0-7e73-6fa281ad6c36@foobar.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <0b32500d-5b26-60e0-7e73-6fa281ad6c36@foobar.org>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/y9GF27YF-EDd2terHbYP9LgUB4I>
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: Mon, 03 Jun 2019 23:31:23 -0000

On Sun, Jun 02, 2019 at 02:31:19PM +0100, Nick Hilliard wrote:
> Toerless Eckert wrote on 02/06/2019 14:03:
> > IMHO, it would be lovely to primarily think of standardizing whats
> > IMHO been most missing piece for more proliferation of anycast, and
> > thats an appropriate prototol for anycast members to signal their membership.
> 
> as an observation, this would introduce host-level state into the network,
> which has scalability consequences.

The host-level state also exists today, when you just setup anycast
address routing for a couple of e.g.: anycast DNS servers. Its just more
complicated because its not fully automated: you need to hav an operator
or SDN controller create those anycast route prefixes and then make sure
that the host config is aligned.

Aka: not disagreeing with your startement about state, just with the
statement that host<->network signaling changes it. It just automates
it and removes manual, unaligned config issues, accelerates deployments,
....

Cheers
    Teroelss
> 
> Nick