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

Ole Troan <otroan@employees.org> Mon, 04 November 2019 09:24 UTC

Return-Path: <otroan@employees.org>
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 D5751120E30 for <ipv6@ietfa.amsl.com>; Mon, 4 Nov 2019 01:24:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 SHJxrzF569c3 for <ipv6@ietfa.amsl.com>; Mon, 4 Nov 2019 01:24:33 -0800 (PST)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0063120E2E for <6man@ietf.org>; Mon, 4 Nov 2019 01:24:33 -0800 (PST)
Received: from astfgl.hanazo.no (77.16.221.227.tmi.telenormobil.no [77.16.221.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id C893D4E11B05; Mon, 4 Nov 2019 09:24:31 +0000 (UTC)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by astfgl.hanazo.no (Postfix) with ESMTP id 0E5C9217468C; Mon, 4 Nov 2019 10:24:25 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: IPv6 Formal Anycast Addresses and Functional Anycast Addresses (Fwd: New Version Notification for draft-smith-6man-form-func-anycast-addresses-01.txt)
From: Ole Troan <otroan@employees.org>
In-Reply-To: <20191104084301.GN2287@faui48f.informatik.uni-erlangen.de>
Date: Mon, 4 Nov 2019 10:24:24 +0100
Cc: Nick Hilliard <nick@foobar.org>, 6MAN <6man@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3798B338-B5FB-49A1-993B-D0AA66A41AE8@employees.org>
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> <20191103225223.GL2287@faui48f.informatik.uni-erlangen.de> <81f02a3b-fc37-348d-728e-78f33355a729@foobar.org> <20191104084301.GN2287@faui48f.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/kc50Nvza641FMp6hkwZf8_JvSRw>
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 09:24:40 -0000

Toerless,

> You are just arguing about the quantitative relevance of the
> problem. I am talking about the qualitative architectual gap.
> 
> If we're not proactively fixing architectural issues in TCP/IP,
> we will just ensure that IP does not proliferate into networks
> where assumptions like the one you are making based on existing
> practices do not work anymore. Those networks surely would instead
> use some L2(.5) mechanism that can faster be improved. Why do you
> think we have all L2 in most wireless/mobile access ?

From an architectural point of view, changing addresses midflight, like what ayncast (does/could do) is just a mobility event or changing paths in a multi-homed network.

We have tried solving these problems at the network layer with among others Mobile IP and SHIM6, and failed.
We need a session layer or a transport layer with it's own connection identifiers.

As far as I'm concerned we have punted this problem to the transport area.

Best regards,
Ole