Re: [Madinas] Comments on draft-ietf-madinas-use-cases-05.txt

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 16 March 2023 08:37 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: madinas@ietfa.amsl.com
Delivered-To: madinas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D686C170B47 for <madinas@ietfa.amsl.com>; Thu, 16 Mar 2023 01:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id apMDvvhFZvTp for <madinas@ietfa.amsl.com>; Thu, 16 Mar 2023 01:37:47 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85DB9C15154E for <madinas@ietf.org>; Thu, 16 Mar 2023 01:37:47 -0700 (PDT)
Received: from dyas.sandelman.ca (ip-185-104-136-48.ptr.icomera.net [185.104.136.48]) by relay.sandelman.ca (Postfix) with ESMTPS id 20C7C1F47D; Thu, 16 Mar 2023 08:37:45 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 9039BA1A01; Thu, 16 Mar 2023 04:37:44 -0400 (EDT)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 8E013A1071; Thu, 16 Mar 2023 08:37:44 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Bob Hinden <bob.hinden@gmail.com>, madinas@ietf.org
In-reply-to: <0C9FB60F-8302-472D-A0DD-B47CF820D6A8@gmail.com>
References: <0C9FB60F-8302-472D-A0DD-B47CF820D6A8@gmail.com>
Comments: In-reply-to Bob Hinden <bob.hinden@gmail.com> message dated "Tue, 14 Mar 2023 09:47:06 -0700."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 16 Mar 2023 08:37:44 +0000
Message-ID: <2632362.1678955864@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/madinas/GW0PscY0gUVJEFDx_wgccuFU9AY>
Subject: Re: [Madinas] Comments on draft-ietf-madinas-use-cases-05.txt
X-BeenThere: madinas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: MAC Address Device Identification for Network and Application Services <madinas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/madinas>, <mailto:madinas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/madinas/>
List-Post: <mailto:madinas@ietf.org>
List-Help: <mailto:madinas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/madinas>, <mailto:madinas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Mar 2023 08:37:48 -0000

Bob Hinden <bob.hinden@gmail.com> wrote:
    >    MAC randomization in IETF Protocol Standards

    > The text in this section starts with:

    > Several IP address assignment mechanisms such as the IPv6 stateless
...
    > This section needs a serious rewrite.

On 802.11 networks with encryption, the IPv6 IIDs are nicely encrypted and
are not visible.

Pretty much no hotel captive portal or home network makes use of the IPv6, or
IID for access control decisions. (Sadly, that's likely because of a lack of
IPv6...)

What I'm saying is that this part is largely irrelevant.
We could fix it by just deleting the section.

Saw this this week at my hotel:
    https://github.com/mcr/madinas-bcp/blob/main/img/hotel-london-portal.png

They let me maintain a MAC address accept list, long-term, across stays.
That's completely going in the wrong direction, even if it is very
convenient.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*