[Dawn] Re: DAWN BoF Proposal
Adrian Farrel <adrian@olddog.co.uk> Wed, 20 May 2026 07:26 UTC
Return-Path: <adrian@olddog.co.uk>
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 B6F57F161116 for <dawn@mail2.ietf.org>; Wed, 20 May 2026 00:26:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779262012; bh=WSvHQsQLFH6VJzGhfj5Myb0Ix4B5rouSUCQGDYS1p88=; h=Reply-To:From:To:Cc:References:In-Reply-To:Subject:Date; b=L1J2A3Z10wc1L5hTvWxd96lMQazJLjvTdSQUP6ZT3QSDe/TgQMEDUXIPMYlibhBze KLRN5hWrH2NScid+mK2x7yvlIeEwKYoQezJK33mHyMasHsIIUw+XTeE5xFObiynFUn xZI8ZoxUkfOHP565o5ZscpMB/lpa1m7YfbWAhf6g=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=olddog.co.uk
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 V0psHOYbuHZ2 for <dawn@mail2.ietf.org>; Wed, 20 May 2026 00:26:51 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A2902F1610BF for <dawn@ietf.org>; Wed, 20 May 2026 00:26:49 -0700 (PDT)
Received: from vs4.iomartmail.com (vs4.iomartmail.com [10.12.10.122]) by mta5.iomartmail.com (8.14.7/8.14.7) with ESMTP id 64K7Pj72018994; Wed, 20 May 2026 08:25:45 +0100
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 130024604D; Wed, 20 May 2026 08:25:44 +0100 (BST)
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0E6A04604A; Wed, 20 May 2026 08:25:44 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs4.iomartmail.com (Postfix) with ESMTPS; Wed, 20 May 2026 08:25:44 +0100 (BST)
Received: from LAPTOPK7AS653V (5.164.125.91.dyn.plus.net [91.125.164.5]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 64K7Pgcq001145 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 May 2026 08:25:42 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: "'Eric Vyncke (evyncke)'" <evyncke@cisco.com>
References: <04e201dce6a3$c0a74e40$41f5eac0$@olddog.co.uk> <PH0PR11MB4966ADAA0275C07F7F68A575A9032@PH0PR11MB4966.namprd11.prod.outlook.com> <04ef01dce6aa$5bab6420$13022c60$@olddog.co.uk> <PH0PR11MB49663B49AC80525A5CCCDCC3A9002@PH0PR11MB4966.namprd11.prod.outlook.com>
In-Reply-To: <PH0PR11MB49663B49AC80525A5CCCDCC3A9002@PH0PR11MB4966.namprd11.prod.outlook.com>
Date: Wed, 20 May 2026 08:25:44 +0100
Organization: Old Dog Consulting
Message-ID: <075701dce829$df12d9d0$9d388d70$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0758_01DCE832.40D9B2D0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIyKy2aeHRrHLEA0MU5zho4RUPWsAL1K4OLActUXm4DUeSvLLUrZlpg
Content-Language: en-gb
X-Originating-IP: 91.125.164.5
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=WSvHQsQLFH6VJzGhfj5My b0Ix4B5rouSUCQGDYS1p88=; b=xKHzeXoyG6gQptdu2Ysf9x1uHabJ5lk0ugWlj nh3AQMc/N6p0BCCpTleHzP25M7PhlCV1zS74LQGYFo09LELDFQlpObRaIc62ZG0Z sYDo1Qsx+yywBvFFBIykiyWfX4K1K4B5pxiXtG5O9LRaXv4F3HXdAAKIBZ9suQKP bYLIUT0f/GZtkhubuAYs5wEc89B5kPhYAW/4UsKpI/L2/WC0ZbdBJWYXGOLKoOWN L492zbsE6EAK1ydrCKQ2tOre2/IHeXZ000k86GSpa7cJ/FKJSv9fhesmwEt7SrCB rT7Zs4ejcnV1SXjX7qb3ASgZ65k1orq+tfUvgQLy53eO2Yuqg==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1006-29464.005
X-TM-AS-Result: No--37.441-10.0-31-10
X-imss-scan-details: No--37.441-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1006-29464.005
X-TMASE-Result: 10--37.441100-10.000000
X-TMASE-MatchedRID: RvgD6ijzkWnuYusHgJkgyhK8RjA2ODb7Gx1IeAFuCyOlmQXE120jTlze JC0sst6tqdCMzUlMACSrofp7IohGw5+stJjZFtGkm/lEl96RipHdEZKQ2x9p3nupyCiVR+dEbqm 1oygU5OZiQBogae1s2NuBUiEfIdx4fUc/goU2yhBceVBIhfwO9Znwlv7Cw6NQ3j63YQvEOy+sRF DzSBAh3hl9cRHrOYb4q/ZGK99IyWBoMLOoNHsM9l/d6ediod7YQ6Cj3EXWBE0xGo3N/81UFQmCE P8/z/mKt5gfc9RTUvWlTHNxJDwdpAw85kvZfX2K82SgwNf6SK4Kz90vj69pJCPFycxHTa2Pibfq ljHnL3iE0szonZHR6EjmXXkLnV9588IuoZswn7+4CCw/t2V6A5F2kRRKjUQ9Y+ItXZ/PvrhgF0Q e5IKU8JQWkZcTz2syH0A/8Vy7hDiVUcz8XpiS9JGAt645FF0SZRL0wm+EOC0hO4eAGt6UvMqg+1 dfQAxyeRyaQf4083glh7MBcP8rvZOJz/rUIvq2YEeiz37wc1gbuYkbK5OH1NdDpwjma+MUVw5Kj ThpZQ4w9U1An+uhRKNLnhzf2ORUBTKD6MIcm3TBlPdI+u7Q6HQ8D+SLaQjs3rE8Oo7Zj65JJOsm oFihLKB8fPmsvZQC1AacdAplL3PmnV13DpXhG13n+beqvEXMCPGhO7SQ1HDd44y51ngd4SOEfEo xqcEMmkn+IZ5EwVA/sDqabNSyQIDcpVWyPxAMxoZTHZ+XCFGWyPi+tKraPCSxSJzWHcFlYI1t3h SgQLVRgM2MVcov0/H/uuICyxMCHPYwOJi6PLlKHhaQPPG6/o5hyiW8kJaQBNVCIloTK1P9dU4/w VV+ooAy6p60ZV62HRcIXG0b6Khr34lUqic7t2sgYR5X7kfKqvYrykp+VIVTptoDfp6JrCBuGJWw gxAra7leoU/OMhPyMXSQdzxi9A==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Message-ID-Hash: GUK4FL6QBD4J2UJY7S6PCP3X3NYASCM5
X-Message-ID-Hash: GUK4FL6QBD4J2UJY7S6PCP3X3NYASCM5
X-MailFrom: adrian@olddog.co.uk
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: dawn@ietf.org, nwilliams@infoblox.com, Roland.Schott@telekom.de, laurent.ciavaglia@nokia.com, arashmid.akhavain@huawei.com, daniel@olddog.co.uk, jmozley@infoblox.com, yaokehan@chinamobile.com, zaheduzzaman.sarker@nokia.com, hesham.moussa@huawei.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: adrian@olddog.co.uk
Subject: [Dawn] Re: DAWN BoF Proposal
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/UrwEJZQB211XF8bWJdKvNrQCY-Q>
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>
Hi again. OK. I put some times and names against the agenda. This is still a very rough draft and I would be happy to hear from you or from the others on this circulation anything like: * No, we need to cover foo * No, we need more time for bar * No, someone else should present on that topic * No, that person should not be a presenter because I want them to chair the BoF For me, there are two big issues for debate: 1. Should DAWN remain generic and open for all similar discovery problems? We could just focus AI agents which is what gave rise to the work effort. But we could note that there are similar efforts arising in other working groups (e.g., CATS). The current DAWN documents and draft charter assume the generic, but it is fair to say that most (all?) of the proponents see AI agents as the pressing problem space. My view is that it would be a shame to miss the opportunity for a general solution by focusing too much on one use case, and that the work effort for the general solution is unlikely to be much larger. 2. Should we move direct to a protocol solution based on a chosen IETF solution (that is, DNS) or should we delegate that decision to the working group? Several comments on the BoF and the draft charter have said Yes, but show us the solution you want to pursue. But there are quite a few drafts proposing a number of alternative protocol approaches. I think that most (all?) of the proponents you see here would like to use DNS, but this is a standard IETF trap (Wheres your proposed solution versus Dont ask us for a rubber stamp), hence the wording in the draft charter and the suggestion to work on some foundational drafts first. Speak later. Adrian From: Eric Vyncke (evyncke) <evyncke@cisco.com> Sent: 19 May 2026 11:16 To: adrian@olddog.co.uk Cc: dawn@ietf.org; nwilliams@infoblox.com; Roland.Schott@telekom.de; laurent.ciavaglia@nokia.com; arashmid.akhavain@huawei.com; daniel@olddog.co.uk; jmozley@infoblox.com; yaokehan@chinamobile.com; zaheduzzaman.sarker@nokia.com; hesham.moussa@huawei.com Subject: Re: [Dawn] Re: DAWN BoF Proposal Adrian, I was indeed thinking of having only the proponents (i.e., doc authors) for now to focus. Obviously, there will be more discussions during the BoF (if accepted). The current BoF proposal is rather detailed, but it would be nice to have the draft agenda more consolidated (e.g., with some duration estimates) and I would like to understand all the intricacies of the BoF request to support it at the first IAB/IESG BoF coordination call on the 26th. I will shortly send a Webex invitation to all the listed BoF proponents (i.e., more people than you suggested), hoping that a short-term notice will be OK. Regards, -éric PS: if you are currently at the RIPE-92 meeting (I know that Jim is), we can also chat here. From: Adrian Farrel <adrian@olddog.co.uk <mailto:adrian@olddog.co.uk> > Date: Monday, 18 May 2026 at 10:41 To: Eric Vyncke (evyncke) <evyncke@cisco.com <mailto:evyncke@cisco.com> > Cc: dawn@ietf.org <mailto:dawn@ietf.org> <dawn@ietf.org <mailto:dawn@ietf.org> > Subject: RE: [Dawn] Re: DAWN BoF Proposal Thanks. A prep/discussion call sounds good. Tempting to open the doors to the whole list (ccd on this thread) but maybe need focus? Shall we limit to a few key document authors? Me Arashmid Akhavain Dan King Kehan Yao Nic Williams Any time or day for me. Best timing for North America and Asia is the usual 3pm Liege-time. A From: Eric Vyncke (evyncke) <evyncke=40cisco.com@dmarc.ietf.org <mailto:evyncke=40cisco.com@dmarc.ietf.org> > Sent: 18 May 2026 10:04 To: adrian@olddog.co.uk <mailto:adrian@olddog.co.uk> Cc: dawn@ietf.org <mailto:dawn@ietf.org> Subject: [Dawn] Re: DAWN BoF Proposal Should we have a call? The two of us or more? So far so good but the stakes are high indeed Envoyé à partir de Outlook pour Android <https://aka.ms/AAb9ysg> _____ From: Adrian Farrel <adrian@olddog.co.uk <mailto:adrian@olddog.co.uk> > Sent: Monday, May 18, 2026 10:53:08 AM To: Eric Vyncke (evyncke) <evyncke@cisco.com <mailto:evyncke@cisco.com> > Cc: dawn@ietf.org <mailto:dawn@ietf.org> <dawn@ietf.org <mailto:dawn@ietf.org> > Subject: DAWN BoF Proposal Hi Éric, As the BoF cut-off date approaches, I wondered whether there is anything we should be doing to the BoF proposal at https://datatracker.ietf.org/doc/bofreq-farrel-discovery-of-agents-workloads -and-named-entities/ Let me know if you think any edits or additions would be helpful. Best, Adrian
- [Dawn] DAWN BoF Proposal Adrian Farrel
- [Dawn] Re: DAWN BoF Proposal Wes Hardaker
- [Dawn] Re: DAWN BoF Proposal Eric Vyncke (evyncke)
- [Dawn] Re: DAWN BoF Proposal Adrian Farrel
- [Dawn] Re: DAWN BoF Proposal Eric Vyncke (evyncke)
- [Dawn] Re: DAWN BoF Proposal Adrian Farrel
- [Dawn] Re: DAWN BoF Proposal Adrian Farrel
- [Dawn] Re: DAWN BoF Proposal Eric Vyncke (evyncke)
- [Dawn] Re: DAWN BoF Proposal Wes Hardaker
- [Dawn] Re: DAWN BoF Proposal Adrian Farrel
- [Dawn] Re: DAWN BoF Proposal Wes Hardaker
- [Dawn] Re: DAWN BoF Proposal Wes Hardaker