IETF Logo Mail Archive

Re: [core] Requiring mDNS participation for a node to be discoverable

Christian Amsüss <christian@amsuess.com> Wed, 28 February 2024 16:49 UTC

Return-Path: <christian@amsuess.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BCBC14F6A6 for <core@ietfa.amsl.com>; Wed, 28 Feb 2024 08:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 3h0P_U2_jEKJ for <core@ietfa.amsl.com>; Wed, 28 Feb 2024 08:49:07 -0800 (PST)
Received: from smtp.akis.at (smtp.akis.at [IPv6:2a02:b18:500:a515::f455]) (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 77A26C14F6A1 for <core@ietf.org>; Wed, 28 Feb 2024 08:49:06 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by smtp.akis.at (8.17.1/8.17.1) with ESMTPS id 41SGn2ml017602 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 28 Feb 2024 17:49:02 +0100 (CET) (envelope-from christian@amsuess.com)
X-Authentication-Warning: smtp.akis.at: Host 095129206250.cust.akis.net [95.129.206.250] claimed to be poseidon-mailhub.amsuess.com
Received: from poseidon-mailbox.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 7B95034561; Wed, 28 Feb 2024 17:49:02 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:e80f:997f:17f6:9706]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 33A6E31496; Wed, 28 Feb 2024 17:49:02 +0100 (CET)
Received: (nullmailer pid 1392 invoked by uid 1000); Wed, 28 Feb 2024 16:49:01 -0000
Date: Wed, 28 Feb 2024 17:49:01 +0100
From: Christian Amsüss <christian@amsuess.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: core@ietf.org
Message-ID: <Zd9j_aGhaT-vIKWe@hephaistos.amsuess.com>
References: <3EB788AE-F999-4B11-9F58-D330226C37A4@tzi.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="CDyocheuJAeMmhHV"
Content-Disposition: inline
In-Reply-To: <3EB788AE-F999-4B11-9F58-D330226C37A4@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/hn1R02iY1i1pSYvPzIQ8OtkJK-4>
Subject: Re: [core] Requiring mDNS participation for a node to be discoverable
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Feb 2024 16:49:10 -0000

Hi,

On Wed, Feb 21, 2024 at 09:03:12AM +0100, Carsten Bormann wrote:
> The newest contribution
> <https://www.w3.org/mid/CAPDSy+7h3SSeKyA2CUazyWWsUi6+xhn2i91zNW1uz4NhgOGkug@mail.gmail.com>
> proposes a best current practice (BCP) that essentially requires a
> node to run mDNS so that others are able to find it (IP address and
> which link it is on).

I don't read that as requiring mDNS, just establishing how it is used --
and if wording changes to make the authority of an URI necessarily DNS
based, I trust that (and am willing to push for) the pushback that has
kept the authority apart from DNS will happen again.

The big issue either way will be whether browsers start using this at
all, and how to get HTTPS there.

Using mDNS may or may not be viable for some CoRE devices (I'll trust
Ted's judgement on that), but that won't keep us from implementing
different discovery mechansisms that satisfy the same requirements of
the document.

Best regards
Christian

v2.23.0 | Report a Bug | By Email