Internet-Draft Cross-Owner Agent Requirements November 2026
Curtis Expires 23 May 2027 [Page]
Workgroup:
Agent Communication Protocols
Internet-Draft:
draft-curtis-agentproto-cross-owner-usecases-00
Published:
Intended Status:
Informational
Expires:
Author:
J. Curtis
Independent

Cross-Owner Agent Use Cases and Requirements: Spending, Delegation Depth, Ownership, Disclosure and Retention

Abstract

This document describes use cases where an AI agent acting for one Owner asks an agent acting for a different Owner to provide/receive information, process or store data or otherwise work on an agent's behalf. This communication can be unidirectional or bidirectional. It lists the requirements that those cases place on an agent dialog protocol, mainly in five areas: a spending limit that stays with the work as it is passed on, a limit on how many times the work may be passed on, a way to check which Owner an agent acts for, the sender's control over which information about its Owner is disclosed, and how long that information may be kept. It does not propose a protocol. It is offered as input to the working group's use cases and requirements document.

About This Document

This note is to be removed before publishing as an RFC.

Status information for this document may be found at https://datatracker.ietf.org/doc/draft-curtis-agentproto-cross-owner-usecases/.

Discussion of this document takes place on the Agent Communication Protocols Working Group mailing list (mailto:agentproto@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/agentproto/. Subscribe at https://www.ietf.org/mailman/listinfo/agentproto/.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 23 May 2027.

▲

Table of Contents

1. Introduction

People are starting to use agents to act on their behalf in ways that have real world impact on their lives, relationships, finances, and careers. Businesses are deploying them in production workloads to deal with intra and inter company processes.

Three big things can go wrong when two agents meet. Without shared rules the Owner has no framework to agree upon how much may be spent on any given task. This spending can be either a computational token cost or real world money moving between the requesting agent and the receiving agent. There are also no limits on whether a request can be passed to other agents down the chain, so an agent can sit in the middle and forward to a third agent that the sender was not aware of. Finally, nothing lets the requesting agent share only what it needs to complete the task as approved. Agents tend to default to sharing whatever they know, which is not usually the intent.

This document lists use cases and requirements only. It does not define a protocol, a message format, or a security mechanism, and it does not assume any particular right answer to solve the problems.

The working group's use cases document [I-D.agentic-ai-usecases-requirements] covers delegation between agents and approval checkpoints for sensitive actions. This document adds the case where the two agents have different Owners, money is being spent, and information about an Owner is involved.

2. Terms

3. Use Cases

3.1. A personal agent buys from a business agent

James asks his agent to find flights and a hotel room to Austin, TX from Ontario in Canada. His agent contacts a travel company's agent and asks for a quote. James's agent knows a good deal about James, which airport he usually prefers, where he likes to sit, his frequent flyer status on certain airlines, his passport number, and that the trip is for a technology conference. The quote needs the first two, and he might get a better price if it is able to share the third. It has no need for the last two, and James would be upset to learn that they had been sent and an agent now has that information about him. He is willing to pay a few cents for the quote itself, but no more. If he goes to book, the company may need his passport number for that booking, but the company's agent has no reason to hold it after the booking is over.

This case needs allowances XO-1 and XO-2 because the travel company should know the ceiling before it starts. It needs disclosure control (XO-7 to XO-9), because what James's agent knows is more than the task requires. It needs a statement about keeping (XO-10), because what is shared for one booking does not need to be retained by the travel company's agent afterward. What is retained by the travel agency and airline systems themselves is out of scope since we are focusing on agent-to-agent communication.

3.2. A business agent passes part of the work to a supplier's agent

In order to produce a quote, the travel company asks a fare wholesaler's agent for a price. James did not choose the wholesaler and does not know it exists. However, part of what he has agreed to spend is now being spent there. The wholesaler could in turn ask someone else. Then the wholesaler's answer is lost on the way back. The travel company cannot tell whether the wholesaler did the work and charged for it, or just didn't receive the request.

This case needs the allowance to cover the whole chain (XO-3), a limit on the length of the chain (XO-5), an honest account of what was spent when something fails (XO-4), and a way to ask again without paying twice (XO-12).

3.3. Several agents of one Owner

James also has an agent in his car and one that runs his home automation as well as an agent that deals with his finances, another agent that is handling his legal work, and yet another agent that manages his calendar. They all share his calendar and location with each other freely. None of them should share those things with the travel company on the same terms. What can and cannot be shared depends on who owns the agent on the other end. An outside agent claiming to be one of James's would be handed everything which is not acceptable.

This case needs a claim of ownership to be something that can be checked (XO-6), because everything else depends on knowing whose agent is asking. It needs the sending agent to decide what goes to which peer (XO-7), and it shows why an agent cannot raise its own standing by what it says about itself (XO-9).

4. Requirements

Each requirement below is something an agent dialog protocol has to allow. None of them says how it should be done. They are numbered XO-1 to XO-12 so they can be pointed to in discussion.

4.1. Spending

XO-1: A request needs to be able to carry an allowance (i.e. the most that may be spent in total) including anything the receiving agent pays to others to do. The allowance needs to say what it is measured in, for example an amount of money or a computational token cost. Without an allowance the requesting Owner has no say in the cost until after the money is spent.

XO-2: A receiving agent needs to be able to refuse a request before doing any work when the cost would exceed the allowance. The requester needs to be able to tell that apart from work that was started and failed. A decline costs nothing. A failure (partial or in full) might not.

XO-3: When an agent passes work on to another agent, the allowance given to the next agent comes out of the original allowance. The next agent is told only its own allowance, not what the first agent was given or has already used. The total across the whole chain cannot exceed what the Owner allowed.

XO-4: Every final answer says how much was spent. When work failed part-way, it needs to say what was spent anyway and what is still unknown.

4.2. Delegation depth

XO-5: A request needs to carry a limit on how many more times it may be handed on, and each hand-over reduces the total allowed handover count. At zero the agent may do the work itself and may not pass it further down the chain.

4.3. Ownership

XO-6: A claim that an agent is acting on behalf of an Owner needs to be something the other agent can check. It cannot be something accepted on the agent's word alone. Any agent may decline to say who its Owner is. It needs to be unable to name an Owner falsely. In the third use case, James's agents share freely with each other, so an agent that could falsely claim to be his would receive everything they hold. An agent who is forced to identify their Owner could inadvertently leak information about their Owner.

4.4. Disclosure

XO-7: The sending agent decides which context items go to which peer. A dialog needs to work without any context item being passed on. If the protocol required context to travel with the dialog, the Owner's choice would be overridden at the first hop.

XO-8: A context item that is sent needs to be able to carry a label saying how far it may travel. An agent that relays the item needs to keep a label at least as strict as the one it received. It can increase strictness, but never decrease. A context item with no label is treated as not to be shared. This is the safe default.

XO-9: An agent cannot raise its own standing with another agent by what it says about itself. How much one Owner trusts another's agent is decided by that Owner.

4.5. Retention

XO-10: A message need to be able to identify context items and how long the receiving agent may keep it. That can be a period of time, or only until the task is done. If no length is defined, the receiving agent does not keep the item after the task. A receiving agent that cannot work within those terms needs a way to turn the item down. In the first use case the passport number is given for one booking, and there is no reason to hold it after that.

4.6. Peer-supplied text

XO-11: A dialog needs to be able to distinguish what a peer is asking for from material the peer is merely passing along, so that the receiver can treat the second as information only, not as a request.

4.7. Repeated requests

XO-12: A request needs an identifier that stays the same when the request is sent again, so that the receiver can recognise a repeat and avoid doing the work twice.

5. Relationship to the Working Group's Scope

The working group's charter limits dialog context to identifiers and lifecycle state. It leaves out content such as memory and prompts. Nothing in this document asks the protocol to carry memory or to understand it. XO-7 only asks that a dialog still works when no context is passed. XO-8 asks for room to attach a label to whatever an application decides to send. XO-10 asks for room to say how long an item may be kept. That takes effect when the dialog ends, and the charter names termination and revocation as lifecycle the protocol manages.

The allowance and the hop limit are two small values. They go with the dialog and they change at each hand-over. This document counts them as lifecycle state.

The charter rules out the behavioural security of agents. XO-11 is the requirement closest to that line. It asks that a dialog can tell a request apart from material that is passed along. It does not say what an agent should do with either. If the working group decides XO-11 is out of scope, it can be removed and the rest still stands.

The charter says agents need verifiable identities separate from their users'. XO-6 is about one link only: that an agent acts for the Owner it names. It is not about proving who that Owner is in the real world. It asks for no new mechanism and depends on the identity work the group is already doing.

6. Relationship to Other Documents

The table sets this document beside the working group's use cases document [I-D.agentic-ai-usecases-requirements].

Table 1
Topic In the use cases document Added by this document
Who owns the agents Agents run by different providers One person's agent dealing with a company's agent
Spending Checkpoints that approve sensitive actions One allowance for the whole chain (XO-1 to XO-4)
Delegation chains Scope narrows at each hop and loops are rejected A limit on how long a chain can get (XO-5)
Ownership Agent identity and authorization across boundaries A way to check a claim to act for an Owner (XO-6)
Disclosure Dialog context is passed along the chain The sender decides, and labels travel with items (XO-7 to XO-9)
Retention Not covered How long a shared item may be kept (XO-10)
Repeated requests Advice to check the outcome before sending again An identifier that stays the same (XO-12)

7. Security Considerations

Nothing in this document stops a dishonest agent. An allowance and a hop limit only hold if the agents in the chain respect them, so they are no replacement for controls on the payment itself. Once a context item has been sent, its label and its retention statement are terms the receiving agent was told. They are not locks. A retention statement does not prove an item was deleted. A checked ownership claim shows the Owner approved that agent. It says nothing about who the Owner is in the real world. What the requirements do is set out what an honest chain of agents will do, and make it clear when an agent has gone outside the terms it was given. This document assumes the dialog is already authenticated and protected by whatever the working group adopts. It asks for nothing new there.

8. Privacy Considerations

The disclosure and retention requirements are here to keep an Owner's information from travelling further, or staying longer, than the task needs. They also create one new leak. An allowance or a hop limit that agents along the path can read says something about the requester, for example how much James is willing to spend. A protocol meeting these requirements needs to think about which agents have to see those values. Checking ownership has a privacy cost too. An agent should not have to reveal its Owner to every agent it talks to. It may stay silent about its Owner. It may not name one falsely.

9. IANA Considerations

This document has no IANA actions.

10. Informative References

[I-D.agentic-ai-usecases-requirements]
Reddy.K, T., Sarker, Z., and K. Yao, "Agentic AI Use Cases and Requirements", Work in Progress, Internet-Draft, draft-agentic-ai-usecases-requirements-07, , <https://datatracker.ietf.org/doc/html/draft-agentic-ai-usecases-requirements-07>.

Author's Address

James Curtis
Independent
Rocklin, CA
United States