[Iotops] Use of IPv6 addresses in browsers in IoT ?

Toerless Eckert <tte@cs.fau.de> Sat, 24 February 2024 02:54 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA1BBC14CEFC for <iotops@ietfa.amsl.com>; Fri, 23 Feb 2024 18:54:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.66
X-Spam-Level:
X-Spam-Status: No, score=-6.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 LfdAM3MkZDzf for <iotops@ietfa.amsl.com>; Fri, 23 Feb 2024 18:54:14 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E361CC14CEE4 for <iotops@ietf.org>; Fri, 23 Feb 2024 18:54:13 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4ThWg561hKznkRT for <iotops@ietf.org>; Sat, 24 Feb 2024 03:54:09 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4ThWg551mkzkmw1; Sat, 24 Feb 2024 03:54:09 +0100 (CET)
Date: Sat, 24 Feb 2024 03:54:09 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: iotops@ietf.org
Message-ID: <ZdlaUZ1LNJEgHalg@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/5YCcEJjEpZG2d4WHT8OImJ_pud0>
Subject: [Iotops] Use of IPv6 addresses in browsers in IoT ?
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Feb 2024 02:54:16 -0000

Dear IOTops

I was wondering how common you see the use of IPv6addresses in URLs in the IOT environments,
e.g.: when configuring IOT devices.

I am asking because we have some long-ongoing discuss re the need to support IPv6 link local addresses (LLA)
in URLs/browsers, especially with zone identifiers in the IPv6 LLA - because browsers have not
implemented it, and would love to avoid the work / don't see the business for this.

Of course, whenever mDNS is available its likely easier to use DNS names instead of IPv6 addresses,
but of course that too requires some well-known address schemes so you know the name a particular
device will be on (something like combination of model-name and mac-addrss as a string ...).

Thanks a lot for any insights.

Cheers
    Toerless