I-D Action: draft-das-execution-finality-ai-interoperability-01.txt

[email protected]
Newsgroups gmane.ietf.announce
Message-ID <178798073862.124362.5526807135106294023@dt-datatracker-6669c7b496-s9mrn>
Internet-Draft draft-das-execution-finality-ai-interoperability-01.txt is now
available.

   Title:   Breaking the Apple-Siri EU DMA Deadlock Without Sacrificing Privacy or Security
   Author:  Sangam Das
   Name:    draft-das-execution-finality-ai-interoperability-01.txt
   Pages:   140
   Dates:   2026-08-28

Abstract:

   The Apple-Siri interoperability debate under the EU Digital Markets
   Act exposes a difficult technical question: how can third-party AI
   assistants gain meaningful access to device functions without forcing
   the platform to surrender privacy, security, or control over
   consequential actions?

   The DMA can require AI interoperability, but interoperability alone
   does not determine when a third-party AI is authorized to cause a
   real-world effect.  The architecture described in this document
   addresses that missing execution-finality boundary.

   This document proposes an execution-finality architecture in which an
   AI assistant may request an action, but the request itself has no
   power to make that action effective.  Each consequential operation
   remains in a Non-Effective State until protected infrastructure
   validates the requester, resource, destination, user intent where
   required, freshness, revocation state, and policy conditions.

   Only then is narrowly scoped, non-bearer execution authority created.
   At the Finality Sink—the first boundary where the action can become
   externally effective—the system independently verifies that the real
   operation still matches what was authorized.  Any mismatch, replay,
   substitution, expiry, or revocation causes fail-closed denial.

   The key principle is simple: interoperability should grant
   participation, not uncontrolled execution authority.

   This offers a possible technical approach to the interoperability-
   security problem: third-party assistants could participate
   meaningfully without requiring broad reusable permissions, while
   platforms retain privacy, security, revocation, anti-replay, and
   final-effect controls.

   Execution-Finality Governance therefore reframes the problem from
   closed versus open to open participation with bounded, verifiable
   authority.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-das-execution-finality-ai-interoperability/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-das-execution-finality-ai-interoperability-01.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-das-execution-finality-ai-interoperability-01

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
I-D-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.