Re: Globally Unique Link Local Addresses (Re: about violation of standards)

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Tue, 23 April 2019 21:17 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 2373312038A for <ipv6@ietfa.amsl.com>; Tue, 23 Apr 2019 14:17:30 -0700 (PDT)
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] 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 3HEVdVpDEyov for <ipv6@ietfa.amsl.com>; Tue, 23 Apr 2019 14:17:28 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1408C120268 for <ipv6@ietf.org>; Tue, 23 Apr 2019 14:17:27 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1hJ2n5-0000EdC; Tue, 23 Apr 2019 23:17:23 +0200
Message-Id: <m1hJ2n5-0000EdC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: Globally Unique Link Local Addresses (Re: about violation of standards)
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <bb7f7606-2adf-e669-8bcd-e41f17800782@gmail.com> <CAJE_bqd9frqX5-yeVPj8MYXpZ4737HqK1gmfD9cQV3A-Ea5HrQ@mail.gmail.com> <6bd5db47-408a-727e-5c13-f34a3465f986@si6networks.com> <CAJE_bqfTLqRbLp4fLu2ASZuZ+4G5c2G+RXkO92kXfLgPTqBnng@mail.gmail.com> <EEF00EA7-2AAF-403F-99AD-1D53ED18E8B3@cisco.com> <47631828-121F-402D-8165-969684C1101B@employees.org> <CAO42Z2wbq=8f6FfR7DoOOFrY7B5puxS26Dk+SsM71Pk7y03ipQ@mail.gmail.com>
In-reply-to: Your message of "Tue, 23 Apr 2019 19:57:46 +1000 ." <CAO42Z2wbq=8f6FfR7DoOOFrY7B5puxS26Dk+SsM71Pk7y03ipQ@mail.gmail.com>
Date: Tue, 23 Apr 2019 23:17:17 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GSWeqZUs-XcF1jnXsmUaijC2A4k>
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: Tue, 23 Apr 2019 21:17:30 -0000

>I've thought the best idea would be to have a subnet ID that is generated
>using the same/similar algorithm ULAs are generated with, to try to avoid
>subnet ID collision across links attached to interfaces on the same
>multihomed host or router.

I wonder about a use case that is important enough that it is worth adding
quite a bit of protocol to every host.

My first question was, what if there is router on the link? In that case the
router could announce a ULA and there would no need for hosts to do anything.
Even if that would require extra protocol in routers then that would be
better than having all hosts implement an election protocol. I think
homenet already has a coordination protocol.

Okay, no router. In that case you would probably use some sort of
service discovery protocol, like mDNS, DNS-SD, etc., Would it really be hard
to pass a sockaddr_in6 around in an application? 

What else do we have. Debugging. There is a syntax for scope in link local
address literals. Maybe a bit more typing, but you don't want to type IPv6
addresses anyhow. There is a bit of a problem that browsers don't want to
implement that.

So the use case is not clear to me.