[dispatch] Request for Scheduling Individual Submission: draft-shenzhihong-dacp-00
"xjzhu@cnic.cn" <xjzhu@cnic.cn> Sun, 28 September 2025 08:40 UTC
Return-Path: <xjzhu@cnic.cn>
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 4195A6A12BBE for <dispatch@mail2.ietf.org>; Sun, 28 Sep 2025 01:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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=cnic.cn
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 t5IpdWveiHUG for <dispatch@mail2.ietf.org>; Sun, 28 Sep 2025 01:40:36 -0700 (PDT)
Received: from cstnet.cn (smtp84.cstnet.cn [159.226.251.84]) (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 092BD6A12BA2 for <dispatch@ietf.org>; Sun, 28 Sep 2025 01:40:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cnic.cn; s=dkim; h=Received:Date:From:To:Cc:Subject:Mime-Version: Message-ID:Content-Type; bh=YncW8nfGg3V0T8PbwqLkIotmiaz3QncdFSaL UDRLYr4=; b=GKqya1DZg+W0XGnVrhPZE2zOwNYccg+MOV/tyyRprwjE2XU+/mqV JMU73mSA9ngXJbHrmwsVtmUoOJcQ68RubVUJ7ony1M6LxnDbEhcZXO9Rv9pqnXE4 ijqbRVXZ7dtJGN/YJg2OL6l7vGgkb7oHdjb6vVLtfLW2l/0/vmN2sX0=
Received: from TABLET-I7HFUM74 (unknown [223.193.3.32]) by APP-05 (Coremail) with SMTP id zQCowAAXuhN29NhoJJD5Bw--.58179S2; Sun, 28 Sep 2025 16:40:23 +0800 (CST)
Date: Sun, 28 Sep 2025 16:40:21 +0800
From: "xjzhu@cnic.cn" <xjzhu@cnic.cn>
To: dispatch <dispatch@ietf.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.433[cn]
Mime-Version: 1.0
Message-ID: <202509281640201732482@cnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart376422215316_=----"
X-CM-TRANSID: zQCowAAXuhN29NhoJJD5Bw--.58179S2
X-Coremail-Antispam: 1UD129KBjvJXoWxAryfZF45uryrAw18XFy7ZFb_yoW5ZFWDpF W8Ww45Ka1fJFyfCF18Zw48uFWSgw1kG3y7JFW7KryfJwsxt3WjyF1Yva1Sk348Zr1DZ348 Za1qvw1DZan2yF7anT9S1TB71UUUUUDqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUHSb7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Ar0_tr1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Cr0_Gr1UM28EF7xvwVC2z280aVAFwI0_GcCE3s1l84ACjcxK6I 8E87Iv6xkF7I0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAYj202 j2C_Gr0_Xr1l5I8CrVAqjxCE14ACF2xKxwAqx4xG64kEw2xG04xIwI0_Gr0_Xr1l5I8CrV CF0I0E4I0vr24l5I8CrVC2j2CEjI02ccxYII8I62kEc4x0xVAYj21lYx0E2Ix0cI8IcVAF wI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0x vY0x0EwIxGrwACY4xI67k04243AVAKzVAKj4xxM4xvF2IEb7IF0Fy26I8I3I1l42xK82IY c2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67AKxVWUGVWUWwC20s 026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1Y6r17MIIYrxkI7VAKI48JMIIF 0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0x vE42xK8VAvwI8IcIk0rVWUJVWUCwCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv 6xkF7I0E14v26r1j6r4UMVCEFcxC0VAYjxAxZFUvcSsGvfC2KfnxnUUI43ZEXa7IU5k3kt UUUUU==
X-Originating-IP: [223.193.3.32]
X-CM-SenderInfo: x0m2x346fqxugofq/
Message-ID-Hash: 4BSX2ZM2K6SJVTUVG43T6HG3QRKXA6PU
X-Message-ID-Hash: 4BSX2ZM2K6SJVTUVG43T6HG3QRKXA6PU
X-MailFrom: xjzhu@cnic.cn
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
CC: zjcheng <zjcheng@cniccn>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dispatch] Request for Scheduling Individual Submission: draft-shenzhihong-dacp-00
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/YIJrYqO069f7yjN4vKjPEmnQe2U>
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>
Dear Dispatch Working Group, I am submitting this request for the scheduling of a new Internet-Draft as an Individual Submission. The draft defines a proposed protocol named DACP: Data Access and Collaboration Protocol. The details of the submission are as follows: - Draft Name: draft-shenzhihong-dacp-00 - Title: DACP: Data Access and Collaboration Protocol - Authors: Zhihong Shen ,"><bluejoe@cnic.cn>, Xiaojie Zhu<xjzhu@cnic.cn> - Intended Working Group: Individual Submission - Abstract: This document describes the Data Access and Collaboration Protocol (DACP), a communication protocol designed to support cross-node, cross-process data access in scientific and distributed computing environments. DACP provides standardized streaming-based data interactions over the Arrow Flight protocol and defines a unified Streaming DataFrame (SDF) model, which acts as a high-performance abstraction for accessing and processing both structured and unstructured data. - IPR Status: No IPR disclosures relevant to this draft have been submitted. - Expiration: 6 months from submission Additional Notes: - The draft is ready for initial publication and review. - The authors request guidance from the Dispatch Working Group regarding any additional steps necessary for scheduling or potential WG assignment, if appropriate. Charter / Scope Summary: - Problem Statement: Scientific and enterprise data workflows often require unified, low-latency, structured data access across distributed systems. Current solutions either incur high serialization overhead or lack native support for data stream transport, as well as multi-hop auditing of data access. - Scope: Define a Streaming DataFrame (SDF) model and a protocol (DACP) for structured, streaming, cross-node, and cross-process data access leveraging Arrow Flight. Includes data model, operations, framing strategy, and basic security considerations. - Goals: 1. Standardize a low-latency protocol for accessing both structured and unstructured data. 2. Support semantic data collaboration across heterogeneous systems. - Non-Goals: 1. Not redefining or replacing application-layer features already covered by Arrow Flight. DACP builds on Arrow Flight transport. 2. Not defining a complete storage layer, database, or query language standard. DACP is not a database protocol. 3. Not handling authorization beyond relying on existing transport security mechanisms (e.g., TLS). 4. Not intended to replace general-purpose transfer protocols (e.g., FTP, HTTP, NFS, gRPC). DACP targets structured, streaming, cross-node data collaboration. - Deliverables: 1. DACP protocol specification (Internet-Draft / RFC). 2. Reference implementation or pseudo-code for SDF streaming. 3. Example data models and use cases. The full Internet-Draft can be found here: https://datatracker.ietf.org/doc/draft-shenzhihong-dacp/ Please let me know if any additional information or clarification is required for the scheduling process. Thank you very much for your attention and assistance. Best regards, Xiaojie Zhu (on behalf of the authors) xjzhu@cnic.cn
- [dispatch] Request for Scheduling Individual Subm… xjzhu@cnic.cn