[Dawn] 回复: A reworked draft charter for DAWN
Lianhua Zhang <zhanglh2@asiainfo.com> Tue, 23 June 2026 02:47 UTC
Return-Path: <zhanglh2@asiainfo.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 92141105805D8; Mon, 22 Jun 2026 19:47:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782182833; bh=lunC1ucl9Y1xCm54wPx1qbMBh76haSEbMOBWgoJ4iDg=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=SHQawslPL0uytucEM1HdCILgZU1iJneyebhIjetE8BFRTdpUJWPsGfUD8yHftfNLD MNA/oiR5IKmOpq8ef4UYBfXV5Qu+x2xPE0JrV0+35qZlibABlTY5AyC91c35U0RhXC BfHVcqsfC6dG1cHqRy4eg8eAEDgk5CPRhQb/jyLY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.105
X-Spam-Level:
X-Spam-Status: No, score=-1.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no 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 HdrPdHSQupsI; Mon, 22 Jun 2026 19:47:10 -0700 (PDT)
Received: from asiainfo.com (unknown [202.60.224.240]) by mail2.ietf.org (Postfix) with ESMTP id 949A0105805CF; Mon, 22 Jun 2026 19:47:00 -0700 (PDT)
Received: from zhanglh2$asiainfo.com ( [10.11.28.226] ) by ajax-webmail-front_06 (Coremail) ; Tue, 23 Jun 2026 10:46:51 +0800 (GMT+08:00)
X-Originating-IP: [10.11.28.226]
Date: Tue, 23 Jun 2026 10:46:51 +0800
X-CM-HeaderCharset: UTF-8
From: Lianhua Zhang <zhanglh2@asiainfo.com>
To: adrian <adrian@olddog.co.uk>, wjhns1 <wjhns1@hardakers.net>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version 2025.2-cmXT6 build 20251107(b4233101) Coremail_cmclient(4.2.1.1373_mac.x64.dmg) Copyright (c) 2002-2026 www.mailtech.cn mispb-d3c9c239-0f2b-4f26-b576-fea94e8ae3d0-asiainfo.com
In-Reply-To: <05d101dd009c$e411c190$ac3544b0$@olddog.co.uk>
References: <05d101dd009c$e411c190$ac3544b0$@olddog.co.uk>
X-CM-CTRLMSGS: arCsAA==
Message-ID: <6a39f39a.a.bJNs0PA7ghjcJNs0@asiainfo.com>
Content-Type: multipart/alternative; boundary="----=_Part_593278_2133628234.1782182811344"
MIME-Version: 1.0
X-Coremail-Locale: zh_CN
X-CM-TRANSID: FgYRCsC2HQ+c8zlqiu4ZAA--.5951W
X-CM-SenderInfo: x2kd0wtoksqtpvldx01irou0bp/1tbiAQEHD2o5QLQP3QACs-
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWDJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Message-ID-Hash: DEXAMITWQ7BIQCYJ3N7RJLRJPHMVGVRW
X-Message-ID-Hash: DEXAMITWQ7BIQCYJ3N7RJLRJPHMVGVRW
X-MailFrom: zhanglh2@asiainfo.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 <dawn@ietf.org>, dawn-chairs <dawn-chairs@ietf.org>, "'Eric Vyncke (evyncke)'" <evyncke@cisco.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Dawn] 回复: 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/8ckuMIL7f1trlbXKlYMH8aoIb7s>
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, A minor editorial comment on the current DAWN draft charter: in the “Coordination with Other Working Groups and Organisations” section, WISME should be changed to WIMSE (Workload Identity in Multi System Environments). Best regards, Lianhua -----原始邮件----- 发件人: "Adrian Farrel" <adrian@olddog.co.uk>(由 "forwardingalgorithm" <forwardingalgorithm@ietf.org> 代发) 发送时间: 2026-06-20 18:09:32 收件人: "dawn" <dawn@ietf.org> 抄送: "dawn-chairs" <dawn-chairs@ietf.org>,"'Eric Vyncke (evyncke)'" <evyncke@cisco.com> 主题: [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