IETF Logo Mail Archive

Proposal: Integrating DAAP Functionality into QUIC

Edward Aylward <aylward.edward@gmail.com> Fri, 11 July 2025 20:43 UTC

Return-Path: <aylward.edward@gmail.com>
X-Original-To: quic@mail2.ietf.org
Delivered-To: quic@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2B6FA431AA31; Fri, 11 Jul 2025 13:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level:
X-Spam-Status: No, score=-1.098 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 AC6NcEYVFatj; Fri, 11 Jul 2025 13:43:51 -0700 (PDT)
Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id C0D29431AA2C; Fri, 11 Jul 2025 13:43:51 -0700 (PDT)
Received: by mail-ej1-x62b.google.com with SMTP id a640c23a62f3a-ae6f8d3bcd4so315471766b.1; Fri, 11 Jul 2025 13:43:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1752266630; x=1752871430; darn=ietf.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=A3hDqx27ENy0F4QYK3GMe7IiX7B4ydo2GG2IvQ8g/Jg=; b=j4S1AzU7Q685drU9+Iswdh8DvT4bLr2cWnTd6H9mO82pc98XlzQ88Bt0A/VOKzl7On cZtpZXKjmFUS3vUxRTc0+303AvmQQ2rRrRG+us+SW1f2k9aEafdQDG1g3WxY+QNhR3+S Nti2WCXrdasnqfLbPhtuAXFfkPs+//wOpn5qCzSAFZm7U2N/T0O7GHIio3yjdk9stdik P3T1kn+Lrx+N9Q6d/gFb/0DDkFwmcvT4K2JoGcEkLmJngi6uf3LoVy+tx8h2f1Bcn7BA vgIYUYmacquBC1ptsyDLpBWzSj2hPqwvztCjLKROnAl1aGvTtloR/xBbptUW+VqalpCU fXog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752266630; x=1752871430; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=A3hDqx27ENy0F4QYK3GMe7IiX7B4ydo2GG2IvQ8g/Jg=; b=TWuo2354DWowQ4xr2ed27gsqRvaFbN3vEa3GXtS70dUoitRBCrIjgxu8Vmxya4E+OV qwQOUElqTWeTwew43RtqsjLtbVsFBaDvtqE+kmNgo3jmQsS+WlTa3Ub7+KqiQue1ilW3 wNymq4aibl6uiDnxFdxUfmEgu5DPb7siSQZSCbWAL2TVD7PX6+ifYwst+LgzAaZAB05I D15uVHArxnDIKG1/mb4qE8tgTGihVM4kAu1pOprLwdHyaA6EYmNQF2m71wz7DBEQSjXk 7n9rOn3g+fAgnV5OkIHNoiRX1wLE+rf7jHi7Ivka7Vb8y+sl6FzmQrwEJp+n85bq94Vd p7JA==
X-Gm-Message-State: AOJu0Yyjpj2ZHtwSVHyi0cOvvMBonGk5NQC/RZ2UhB28jY68LJng+EJ0 QUCEs0QLPQK868V7QpDIp2bsQbWGxLWkc3srJheUJ+0nNY+dedpwIO0A4HhoVKrJ/zTc765Nt/8 g3lL2xMyfKR2BMUS+ohTw3CWXfIiXQkTcydOECHQ=
X-Gm-Gg: ASbGnctHmaSG7Hwt2HTuHJqsoW3Oml4Le3Kb34+pZJ6FvG0dVuvK2Qg0cNmdLN7YjgQ hVSC2GCEV+q1X3jIiohqDXliGhUhNhAE3oeSqVCTAdL1sdrVufgudMWijl3hA4wdo5AwMb9otF7 SQYsxCWsEzh5g8OzFdnQGPMYbAq6PG1Eiz5w7MTBBgSDDjYkjGPi3Xg5SEI7uy9iZSRJR+ezy6l XB9TOjECOgtmtL4I4LyekbRBPPJVWwoM3a/CqkJ
X-Google-Smtp-Source: AGHT+IEoqx/wKIPSi0JK0rdOuDkEtXAldtXx2kM+LIihyLEWcUjwEMUILEhGM1iFCoaT5CPgJF93PXf/c4/q0FOTrwM=
X-Received: by 2002:a17:906:fd86:b0:acb:abff:a5b6 with SMTP id a640c23a62f3a-ae7010feb8dmr313494666b.13.1752266630122; Fri, 11 Jul 2025 13:43:50 -0700 (PDT)
MIME-Version: 1.0
From: Edward Aylward <aylward.edward@gmail.com>
Date: Fri, 11 Jul 2025 13:43:13 -0700
X-Gm-Features: Ac12FXxUmHjlFytFuLc3YSshaDLgbpXOXm2nBurjXEC2w_8W0jtV_4QSIfTWhwA
Message-ID: <CAL6-Gb-dC9OesKtXSYkB4C0U0Zb9A6gm_1gFXdG6uHOfx7RZCw@mail.gmail.com>
Subject: Proposal: Integrating DAAP Functionality into QUIC
To: quic-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000a554a0639ad5eb7"
Message-ID-Hash: Q2O5KYSEZG3ZNXFYGVTJN4HT6I4RBCXC
X-Message-ID-Hash: Q2O5KYSEZG3ZNXFYGVTJN4HT6I4RBCXC
X-MailFrom: aylward.edward@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-quic.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: quic@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eTq6T93PYljEr2NRbLfpFE8itSw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Owner: <mailto:quic-owner@ietf.org>
List-Post: <mailto:quic@ietf.org>
List-Subscribe: <mailto:quic-join@ietf.org>
List-Unsubscribe: <mailto:quic-leave@ietf.org>

*Subject:* Proposal: Integrating DAAP Functionality into QUIC

*To:* quic-chairs@ietf.org
*Cc:* quic@ietf.org
*From:* Ed Aylward aylward.edward@gmail.com
*Date:* July 11, 2025
------------------------------

Dear Lucas and Matt,

I hope you’re both doing well.

My name is Ed Aylward, and I’m the author of *draft-aylward-daap-v2*, which
outlines the Distributed AI Accountability Protocol (DAAP). It’s a
framework designed to help maintain human oversight over autonomous AI systems
by requiring regular, verifiable communication with a designated authority.

I’m reaching out to propose a new QUIC extension that would allow DAAP to
run natively over QUIC. The goal is to move beyond HTTP-over-TCP, embedding
DAAP’s core functions directly into the transport layer by defining:

   -

   New QUIC frame types for behavioral check-ins, policy updates, and
   emergency signaling
   -

   A TLS extension (daap_identity) to establish agent identity at the start
   of the QUIC handshake
   -

   Multiplexed streams to handle real-time control, telemetry, and
   enforcement in parallel

This integration would provide tighter security guarantees, better
performance, and more responsive control, especially valuable for
environments where speed, reliability, and accountability are critical.

If the working group is open to reviewing this idea, either as a
contribution to QUIC or as an individual draft submission, I’d be happy to
share:

   -

   A working draft in the IETF format
   -

   Notes on how the implementation maps to current QUIC capabilities
   -

   Example use cases in sectors like robotics, edge AI, and smart
   infrastructure

Thanks for considering this. I appreciate your time and would welcome any
suggestions or guidance on next steps.

Best regards,
*Edward Richard Aylward, Jr.*
Email: aylward.edward@gmail.com
DAAP GitHub: https://github.com/ELF-GUARD/DAAP/
ORCID: 0000-0003-0313-6993

v2.32.0 | Report a Bug | By Email | System Status