IETF Logo Mail Archive

[Dawn] Re: Discovery Solution Space

Wes Hardaker <wjhns1@hardakers.net> Sat, 09 May 2026 11:52 UTC

Return-Path: <wjhns1@hardakers.net>
X-Original-To: dawn@mail2.ietf.org
Delivered-To: dawn@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 1EFB8EBB55BA for <dawn@mail2.ietf.org>; Sat, 9 May 2026 04:52:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778327540; bh=Fh7WvpilezWTeyYZSJ4tQScZ0dgTDxvcCit0ngO3few=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=IaR2EqFqPvWbUK8jO+spFH1IfOT+rsKl7Kw6VDzJiRYCtkXOlbrS9anBnFL1ttBQS c4gepUK8QvFE0rnBPp7WzJ4UDFyaj2sIy57Nec0r+fFQN0YF7j9/esfTFL4oURGJHA DMZtW869Zs7Ke+Yue0rgLz23qjNdxvA9BS1ry5rI=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=hardakers.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NonJE05_7MzV for <dawn@mail2.ietf.org>; Sat, 9 May 2026 04:52:16 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [107.220.113.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 01483EBB55B0 for <dawn@ietf.org>; Sat, 9 May 2026 04:52:15 -0700 (PDT)
Received: from localhost (unknown [212.185.66.18]) by mail.hardakers.net (Postfix) with ESMTPA id 121DD218E3; Sat, 09 May 2026 04:52:06 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.hardakers.net 121DD218E3
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardakers.net; s=default; t=1778327529; bh=Icj0E/2aJQXRHohBtc7bSaNUh5UYoitBVEW5kIyhMIg=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=QTPZdwq3e+UucmwebhJGstcXaKqHAD7IMZdOCL5t+SociVp3Ojw1zg1tJbdc4QxvZ 3uZuDfDnDHSafZ7SW+8OHZE0j2bbBRcu036RlS3kDqMEP+erjrG5L99XE8bvmWCMHz 0bt6rmsnH5T0R3oHTaIkhKnz2hHztx1/stVEHhrA=
From: Wes Hardaker <wjhns1@hardakers.net>
To: Adrian Farrel <adrian@olddog.co.uk>
In-Reply-To: <179201dcdd7d$6feb3bd0$4fc1b370$@olddog.co.uk> (Adrian Farrel's message of "Wed, 6 May 2026 18:26:12 +0100")
References: <05ae01dcd342$e3f6d920$abe48b60$@olddog.co.uk> <CO6PR13MB5355182462BED52A6D145100852B2@CO6PR13MB5355.namprd13.prod.outlook.com> <077701dcd43f$8fd19ee0$af74dca0$@olddog.co.uk> <CO6PR13MB5355EFC54413968DF08EF76685342@CO6PR13MB5355.namprd13.prod.outlook.com> <001801dcd779$f0f49e10$d2ddda30$@tsinghua.org.cn> <CO6PR13MB5355363BBA2898A6A7D3F5ED85342@CO6PR13MB5355.namprd13.prod.outlook.com> <0d9201dcd801$19718830$4c549890$@olddog.co.uk> <yblo6j0g15l.fsf@wx.hardakers.net> <CAC8QAccU2HKfbbEhDf7ZS3giLUD3Wt8yrh0-OUPTf9rNpiRPBg@mail.gmail.com> <179201dcdd7d$6feb3bd0$4fc1b370$@olddog.co.uk>
Date: Sat, 09 May 2026 04:52:05 -0700
Message-ID: <ybltssger6i.fsf@wx.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: 6UVMXXGFAUUOFAZUDOXQG6F7YUAAXAXX
X-Message-ID-Hash: 6UVMXXGFAUUOFAZUDOXQG6F7YUAAXAXX
X-MailFrom: wjhns1@hardakers.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: sarikaya@ieee.org, wjhns1@hardakers.net, dawn@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Dawn] Re: Discovery Solution Space
List-Id: "The list is for discussion of the scope, use cases, requirements, and solutions for discovery of entities (e.g., tasks, AI agents, or endpoints) using IETF technologies." <dawn.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dawn/gjaJvReoDMIKqfe9RMRtxR2T5L0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dawn>
List-Help: <mailto:dawn-request@ietf.org?subject=help>
List-Owner: <mailto:dawn-owner@ietf.org>
List-Post: <mailto:dawn@ietf.org>
List-Subscribe: <mailto:dawn-join@ietf.org>
List-Unsubscribe: <mailto:dawn-leave@ietf.org>

"Adrian Farrel" <adrian@olddog.co.uk> writes:

> I don’t think Wes said that there are two protocols. I think he said that there are two
> considerations of “existing protocols” (although he did say that there are two common examples
> of IETF protocol that can be used to find registrations.

What I would state more specifically:  s/two/at least two current, with
many more likely to come/

:-/

-- 
Wes Hardaker
Google

v2.45.0 | Report a Bug | By Email | System Status