[Dawn] Re: A reworked draft charter for DAWN
Hesham Moussa <hesham.moussa@huawei.com> Mon, 22 June 2026 14:17 UTC
Return-Path: <hesham.moussa@huawei.com>
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 ACEA51051EC69; Mon, 22 Jun 2026 07:17:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782137824; bh=8UwV5BIqEkfRZwLb2xPig78OF1CspOIzjfzR5iLa3sw=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=IHiNVhGns+Egj7AD5ncQV9AhZ2seUn2MR6pvsAxCevy5HZHDohO32kM8KOt5ENUgK VSy499kZAGSmmOf3d+W1h3Ir5DfaaWCYXBNcOkaewZ4ZPs3/Or8bnzfwVGGRzhmY7+ VHm8z5uMtaDUjhXxIsIUNS9H6Dc8seqdQpWSKQL4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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
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 v6e5Cvd0mr7v; Mon, 22 Jun 2026 07:17:02 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (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 A29931051EC64; Mon, 22 Jun 2026 07:17:02 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.224.107]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4gkVcY5mJ1zHnH69; Mon, 22 Jun 2026 22:16:29 +0800 (CST)
Received: from lhrpeml500010.china.huawei.com (unknown [7.191.174.240]) by mail.maildlp.com (Postfix) with ESMTPS id 3BF704058D; Mon, 22 Jun 2026 22:16:58 +0800 (CST)
Received: from ytopeml100001.china.huawei.com (7.184.17.227) by lhrpeml500010.china.huawei.com (7.191.174.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.39; Mon, 22 Jun 2026 15:16:57 +0100
Received: from ytopeml500001.china.huawei.com (7.184.16.223) by ytopeml100001.china.huawei.com (7.184.17.227) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Mon, 22 Jun 2026 10:16:56 -0400
Received: from ytopeml500001.china.huawei.com ([7.184.16.223]) by ytopeml500001.china.huawei.com ([7.184.16.223]) with mapi id 15.02.1544.011; Mon, 22 Jun 2026 10:16:56 -0400
From: Hesham Moussa <hesham.moussa@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dawn@ietf.org" <dawn@ietf.org>
Thread-Topic: [Dawn] A reworked draft charter for DAWN
Thread-Index: Ad0AmrIyrwLktx5QReOe4l3akJpT5gBtWWNQ
Date: Mon, 22 Jun 2026 14:16:56 +0000
Message-ID: <51caa2a441bf4946946e8381284629dc@huawei.com>
References: <05d101dd009c$e411c190$ac3544b0$@olddog.co.uk>
In-Reply-To: <05d101dd009c$e411c190$ac3544b0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.193.51.162]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: R7OVEHYQCK5MXF6MVLVXNZ7ZBIK4MTS7
X-Message-ID-Hash: R7OVEHYQCK5MXF6MVLVXNZ7ZBIK4MTS7
X-MailFrom: hesham.moussa@huawei.com
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-chairs@ietf.org" <dawn-chairs@ietf.org>, "'Eric Vyncke (evyncke)'" <evyncke@cisco.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Dawn] Re: A reworked draft charter for DAWN
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/vJcvtXgZe1LSwuVMCwW2LBXja2w>
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 Adrian and Wes, Thank you for updating the charter and for the work you’ve put into this effort. I would like to suggest clarifying that the starting point includes the discovery of AI agents, agentic tools, and agentic skills. The discovery of these entities currently represents the most prominent and active set of discovery targets, as demonstrated by ongoing work in both the IETF and the open‑source community, including efforts such as A2A and MCP. With that in mind, we might consider adjusting the current sentence: “Although initially focused on discovery of AI agents, the WG is expected to produce results that are general and reusable within other discovery contexts whenever possible.” to something along the lines of: “Although initially focused on discovery of AI agents, agentic tools, and agentic skills, the WG is expected to produce results that are general and reusable within other discovery contexts whenever possible.” Regarding the DNS sentence , “The WG will consider the DNS as a likely initial protocol upon which to build a discovery protocol.”, I wonder whether it would be better if we say that one of the WG’s first tasks it to identify which initial protocols are suitable to build upon, rather than highlighting a specific protocol from the outset. This may help ensure that the group evaluates all options with an open and neutral starting point. Thoughts?? Regards, Hesham -----Original Message----- From: Adrian Farrel <adrian@olddog.co.uk> Sent: Saturday, June 20, 2026 6:10 AM To: dawn@ietf.org Cc: dawn-chairs@ietf.org; 'Eric Vyncke (evyncke)' <evyncke@cisco.com> Subject: [Dawn] A reworked draft charter for DAWN Hi, Now that the BoF is approved and we have some I-Ds to fill in the background, Wes and I have been working on the draft charter text for a potential DAWN working group. You can find the working copy at https://github.com/danielkinguk/discovery/blob/main/charter/dawn-charter-02. md First step was to halve the number of words (sorry, the initial verbosity was mainly my fault). Then we also worked to focus in on the distinctions between the WG's initial focus and what might come later. This was addressing two key questions: 1. Should the WG work only on AI agent discovery, or should it be open to more general "entity" discovery? Here, we noted that most of the drafts that have been posted are dealing with AI agent discovery, and the need for work in that area could be described as "pressing". On the other hand, it seems highly likely that in solving AI agent discovery we could also solve discovery for a range of similar entities. That leads us to suggest the WG should initially be focused on discovery of AI agents, but that the WG is expected to produce results that are general and reusable within other discovery contexts whenever possible. 2. Should the WG select between a number of possible solution technologies, or should it build immediately on DNS? A number of factors influenced us here: - There is often a preference to use pre-existing IETF technology where possible. - A quick start will re-use or modify existing code, but can then be developed along different lines. - There are probably two stages to "discovery", the first being relatively simple discovery, the second being the exchange and negotiation of capabilities and other information. - We are not certain at this stage that DNS will do the job. This lead us to suggest that, "Where possible, any solutions work will be built in a modular way using existing IETF protocols that provide support for any needed communication, authentication and privacy. The WG will consider the DNS as a likely initial protocol upon which to build a discovery protocol." We would very much like to hear discussion (or just words of approval/opprobrium) on the charter text and these two questions. Thanks, Adrian (per pro Wes) _______________________________________________ Dawn mailing list -- dawn@ietf.org To unsubscribe send an email to dawn-leave@ietf.org
- [Dawn] A reworked draft charter for DAWN Adrian Farrel
- [Dawn] Re: A reworked draft charter for DAWN Nic Williams
- [Dawn] Re: A reworked draft charter for DAWN Hesham Moussa
- [Dawn] Re: A reworked draft charter for DAWN Wes Hardaker
- [Dawn] Re: A reworked draft charter for DAWN Hesham Moussa
- [Dawn] Re: A reworked draft charter for DAWN Wes Hardaker
- [Dawn] Re: A reworked draft charter for DAWN Arashmid Akhavain
- [Dawn] Re: A reworked draft charter for DAWN Wes Hardaker
- [Dawn] Re: A reworked draft charter for DAWN Linda Dunbar
- [Dawn] 回复: A reworked draft charter for DAWN Lianhua Zhang
- [Dawn] Re: A reworked draft charter for DAWN Arashmid Akhavain
- [Dawn] Re: A reworked draft charter for DAWN Arashmid Akhavain
- [Dawn] Re: A reworked draft charter for DAWN Adrian Farrel
- [Dawn] Re: A reworked draft charter for DAWN Kehan Yao
- [Dawn] Re: A reworked draft charter for DAWN Hesham Moussa
- [Dawn] Re: A reworked draft charter for DAWN Hesham Moussa
- [Dawn] Re: A reworked draft charter for DAWN Linda Dunbar
- [Dawn] Re: A reworked draft charter for DAWN Arashmid Akhavain
- [Dawn] Re: A reworked draft charter for DAWN Wes Hardaker
- [Dawn] Re: A reworked draft charter for DAWN Kehan Yao
- [Dawn] Re: A reworked draft charter for DAWN Diego R. Lopez
- [Dawn] Re: A reworked draft charter for DAWN Wes Hardaker