[dispatch] new draft on physical and digital agents communication
yunfei <hishigh@sina.com> Wed, 22 October 2025 02:38 UTC
Return-Path: <hishigh@sina.com>
X-Original-To: dispatch@mail2.ietf.org
Delivered-To: dispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 725107A0C862 for <dispatch@mail2.ietf.org>; Tue, 21 Oct 2025 19:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=sina.com
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 dxxnGsE0L55s for <dispatch@mail2.ietf.org>; Tue, 21 Oct 2025 19:38:07 -0700 (PDT)
Received: from smtp134-31.sina.com.cn (smtp134-31.sina.com.cn [180.149.134.31]) (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 35BB67A0C0A2 for <dispatch@ietf.org>; Tue, 21 Oct 2025 19:31:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sina.com; s=201208; t=1761100291; bh=TMuHsou2WVyJt1YEiJ1zCmN+2697kO8g759LhKW5b50=; h=Date:From:Subject:Message-ID; b=BrVPj7/3MjsrVWP1OUgHWH01RlihksesUb4e4YapbR84HmT8bZl6Z6Ah7HqNUoeoY naggp5fuOIQm/U3dOJ03tJsGguVcrMrdmuK9sBz2+4R+MmPZIf2GXIT0DPG1/ctAv6 RYYpchppG48uxPO44y6JfipFjdEJ5dSwXiS7dGoo=
X-SMAIL-HELO: webmail.sinamail.sina.com.cn
Received: from unknown (HELO webmail.sinamail.sina.com.cn)([10.2.23.146]) by sina.com (10.185.250.21) with SMTP id 68F841EF00007439; Wed, 22 Oct 2025 10:31:12 +0800 (CST)
X-Sender: hishigh@sina.com
Authentication-Results: sina.com; spf=none smtp.mailfrom=hishigh@sina.com; dkim=none header.i=none; dmarc=none action=none header.from=hishigh@sina.com
X-SMAIL-MID: 3803993408724
Received: by webmail.sinamail.sina.com.cn (Postfix, from userid 993) id F19AE26F1; Wed, 22 Oct 2025 10:31:11 +0800 (CST)
Date: Wed, 22 Oct 2025 10:31:11 +0800
Received: from hishigh@sina.com ([36.110.6.178]) by m0.mail.sina.com.cn via HTTP; Wed, 22 Oct 2025 10:31:11 +0800
From: yunfei <hishigh@sina.com>
To: dispatch <dispatch@ietf.org>
X-Priority: 3
Mime-Version: 1.0
Message-ID: <68f841efec9518.34545496.1f0affbc@m0.mail.sina.com.cn>
X-MessageID: 07e90006ea8f930c7e4e3dd9f064e310_202510
X-SMAIL-UIID: 84470F54EA066CE95C1EC0814744E3E7-20251022-103111-2
X-Mailer: Sina WebMail 4.0
Content-Type: multipart/alternative; boundary="=-sinamail_alt_782a2e10524963aeef075e0ed2afcf3e"
Message-ID-Hash: MGEWSQGLRNYKO5NC6ZGMTPETHEE2NVSE
X-Message-ID-Hash: MGEWSQGLRNYKO5NC6ZGMTPETHEE2NVSE
X-MailFrom: hishigh@sina.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: hishigh@sina.com
Subject: [dispatch] new draft on physical and digital agents communication
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/cNRI0oEnwnQ9WE80QmSfUBG8pIQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Owner: <mailto:dispatch-owner@ietf.org>
List-Post: <mailto:dispatch@ietf.org>
List-Subscribe: <mailto:dispatch-join@ietf.org>
List-Unsubscribe: <mailto:dispatch-leave@ietf.org>
Hi all, We have just upload a new draft to standardize Real-Virtual Agent Protocol (RVP) on physical and digital agents communication. Because RVP is more related to application layer interactions based on exisiting IETF protocol stack, we believe DISPATCH may be a good place to discuss it. I am not sure if we can catch this IETF agenda arrangement. Anyway the mailing list comments and suggestions are highly appreciated. Thanks.Name: draft-zhang-rvp-problem-statementRevision: 00Title: Problem Statements and Requirements of Real-Virtual Agent Protocol (RVP): Communication Protocol for Embodied Intelligence in Physical- Digital ContinuumDate: 2025-10-20Group: Individual SubmissionPages: 23URL: https://www.ietf.org/archive/id/draft-zhang-rvp-problem-statement-00.txtStatus: https://datatracker.ietf.org/doc/draft-zhang-rvp-problem-statement/HTMLized: https://datatracker.ietf.org/doc/html/draft-zhang-rvp-problem-statementAbstract: The Real-Virtual Agent Protocol (RVP) enables seamless coordination between physical entities (robots, IoT devices, manufacturing systems and agents) and digital agents (AI systems, software agents, virtual twins) through unified composite identity management, physical/social/production relations graph-based coordination, and physical constraint integration. Unlike existing protocols that assume peer-to-peer digital relationships (A2A for agents, MCP for AI tools, ANP for agent networks), RVP unifies physical and digital agents communication and achieves physical data loop for online learning for embodied agents considering both hierarchical physical/social/production relations and physical world constraints. RVP is designed for immediate deployment in modern manufacturing, smart cities, autonomous mobility systems, and human-AI collaborative environments where non-peer, partially centralized relations and coordination is essential for real-world embodied intelligence networks. BRYunfei