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

Mark Smith <markzzzsmith@gmail.com> Mon, 04 November 2019 01:16 UTC

Return-Path: <markzzzsmith@gmail.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 EF525120858 for <ipv6@ietfa.amsl.com>; Sun, 3 Nov 2019 17:16:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.497
X-Spam-Level:
X-Spam-Status: No, score=-0.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, 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=gmail.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 pAPfeLN4arzP for <ipv6@ietfa.amsl.com>; Sun, 3 Nov 2019 17:16:44 -0800 (PST)
Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (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 89274120857 for <6man@ietf.org>; Sun, 3 Nov 2019 17:16:44 -0800 (PST)
Received: by mail-ot1-x331.google.com with SMTP id b16so13014430otk.9 for <6man@ietf.org>; Sun, 03 Nov 2019 17:16:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kEnFW9y87WFKb/d4y8q4kGWRyWL0jU8WQxaugE5SG6Y=; b=TTQBpBwwYXCgZU84QUgnV5sEL8WwUMR2FUNLksHoUdp/76wMTD+Fw7Pe1+CZb/iY2h c88a5op0BOhS1tzc8U+QNrpTGAkUWz/DLOKrSUf+OBMeUpUcFziMlN+D7jYBQ4G/7QfB 0UW2ZipMt0mmHXUohkQe6GyXwWmd0ZS62k8EZr1fW/RUhe966ohtcyLu/V2h4wLYGKDy s27TVVGlIZXo1/OBweh6S2y30vW5cKf2ffMPZDpeLJTEovbnkMvAgX/tqKMrwyqI5jcW FDEY/e/aSfsW9JMjJR3F7z7G4FZqJMC0IzyhTVCnrDzx9LtoIJO1G3VkDSm/SDwo32Wu WK7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kEnFW9y87WFKb/d4y8q4kGWRyWL0jU8WQxaugE5SG6Y=; b=GLq6KmfhlmvdSxgOwdYgzvKOH9YhSTkdRM7to/0WhgMT90LJO2wnLiPlvL2YBgStjV B2GTBK0YQI05D5t5YdwU+o48+wjhFkg9h5GGiUasMnzuuj/IV9B7jr/hnApmaVoQprlf rLJZ8we7FtvhLDjpbe0S6YUgSwtAgOFNuNVQP/m876xz3pmQvcn/0oZaEBhIZYICiWXc DdesWsdJFesPKpduzEDnl2HsvJ/cUYbraNo5fpI/tALx+009zdRYD9mmfVIznF3xcZxC DUDI8JVjy9NcPgWlW0EZrHEopYpEyh2EpoWlHyS365P4YO1KJQr0axuIaNYlbrkKW9Us 6h0A==
X-Gm-Message-State: APjAAAW8DIOBuTv4TYe2wqD5EPYQQggl8riqemG9fTlDLApt9ayAMGvA WDmlJIAwaOUgXelixlXB5KD16E5LnV1fdMr7CtY=
X-Google-Smtp-Source: APXvYqxycKdN2kByLADh4zANozqvqJB/xny8GPFto7BN4BQUW+xd7jb61nomjVS7WvrmD2jUc6MkOOLl11NRqeVO0YA=
X-Received: by 2002:a05:6830:4c8:: with SMTP id s8mr13415889otd.257.1572830203907; Sun, 03 Nov 2019 17:16:43 -0800 (PST)
MIME-Version: 1.0
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> <20191103212712.GK2287@faui48f.informatik.uni-erlangen.de> <B2A9EAB8-BF52-4302-BB77-70EE252F45E5@gmail.com> <24313.1572827211@localhost>
In-Reply-To: <24313.1572827211@localhost>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Mon, 4 Nov 2019 12:16:17 +1100
Message-ID: <CAO42Z2y_qpaxMz86Oj6E5OHJr_whJit_2P7zwqNK3CbrKSZhyg@mail.gmail.com>
Subject: Re: IPv6 Formal Anycast Addresses and Functional Anycast Addresses (Fwd: New Version Notification for draft-smith-6man-form-func-anycast-addresses-01.txt)
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: 6MAN <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/7UrH6vZUotk3K5Y9Rz1zKlsKJ1M>
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, 04 Nov 2019 01:16:46 -0000

On Mon, 4 Nov 2019 at 11:27, Michael Richardson <mcr+ietf@sandelman.ca>; wrote:
>
>
> Fred Baker <fredbaker.ietf@gmail.com>; wrote:
>     > Funny. It doesn't work that way in DNS. Every root server simply thinks
>     > that one of its addresses is the anycast address and so accepts the
>     > packet as "directed to it". It also responds from that address, so that
>     > the requester recognizes the response.
>
> Yes, as long as it's UDP, or very short-lived TCP connections, it works.
> If someone wants to use anycast for a longer-lived connection (in DNS, that
> could include DoT...) then we run into problems.
>
> {shim6 could have dealt with this, but we decided we couldn't do it. I'm
> still sad}
>

Host Identity Protocol could have also achieve this.

I've started to wondered if solving the identifier/locator problem
within the transport layer, using temporary transport layer connection
identifiers - a  32 bit 'token' in MPTCP, rather than persistent host
identifiers, might be the better solution. It's certainly has been
much more successful at being deployed - Apple put MPTCP in iOS 7 and
it was being used for Siri (don't know if it still is).



>     >> On Nov 3, 2019, at 4:27 PM, Toerless Eckert <tte@cs.fau.de>; wrote:
>     >>
>     >> 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
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>;, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------