7. Correlating Application Requests
Dialog content is carried by the application protocol over its own HTTP transport, such as A2A JSON-RPC over HTTP or MCP Streamable HTTP. Those messages carry the dialog reference in their own extension points (Section 8.1 of [PACE]), which HTTP intermediaries do not parse. This binding adds an HTTP header field so that intermediaries and servers can correlate a request to a dialog without parsing its content.¶
7.1. The PACE-Dialog Header Field
PACE-Dialog is a Dictionary Structured Field [RFC9651] with
these members:¶
- id:
-
Required. A String carrying the canonical textual form of the dialog-id.¶
- gen:
-
Optional. An Integer carrying the latest generation the sender knows.¶
- uri:
-
Optional. A String carrying the dialog URI.¶
Receivers ignore members they do not recognize. For example, agent-a
sends an A2A request to agent-b in the dialog, at generation 3, and
names the dialog both in PACE-Dialog and in the A2A message
metadata:¶
A client SHOULD send PACE-Dialog on every application HTTP request
that belongs to a dialog, in addition to the dialog reference in the
application message. When both are present, they MUST name the same
dialog-id; a receiver MUST reject a request in which they differ, with
400 (Bad Request). A server MAY send PACE-Dialog on responses.¶
Like every dialog reference, PACE-Dialog is a correlation value. It
MUST NOT be treated as a credential, and a server MUST authorize the
request independently of it (Section 3.2 of [PACE]). A server that
receives a request naming a dialog in which the client is not an
active participant SHOULD reject it with 403 (Forbidden).¶
The field gives HTTP intermediaries one place to apply dialog-level
policy, such as routing all requests of a dialog to the same backend,
rate limiting per dialog, or rejecting requests for a terminated
dialog, and to record the dialog-id for audit. An HTTP intermediary
MUST NOT add, change, or remove PACE-Dialog.¶
7.2. Application Protocols over HTTP
This binding does not change the HTTP transport, message format, or semantics of any application protocol. An MCP client and server keep Streamable HTTP, JSON-RPC, and MCP session handling; an A2A client and server keep their JSON-RPC or HTTP+JSON binding. PACE support is added beside them:¶
-
Application requests carry the dialog reference in the protocol's existing extension point, such as MCP
_metaor A2A messagemetadata(Section 8.1 of [PACE]), and SHOULD carry thePACE-Dialogheader field. Implementations that do not support PACE ignore both.¶ -
PACE control messages go to the dialog URI, not to the application endpoint (Section 4). A PACE component next to the application client or server sends and receives them; the application protocol does not see them.¶
-
A PACE CANCEL is applied through the protocol's own cancellation, so the application sees its native cancel (Section 4.10).¶
| Protocol | HTTP transport | Dialog reference | Cancellation |
|---|---|---|---|
| MCP | Streamable HTTP |
_meta, and PACE-Dialog
|
PACE CANCEL applied as notifications/cancelled
|
| A2A | JSON-RPC or HTTP+JSON | Message metadata, and PACE-Dialog
|
PACE CANCEL applied as CancelTask
|
| Other | Protocol's own | Protocol's extension point, and PACE-Dialog
|
Protocol's own |
PACE dialog-ids are distinct from application session and context
identifiers, such as the MCP session identifier (Mcp-Session-Id) or
the A2A contextId. A dialog-id MUST NOT be used as one of them
(Section 8.1 of [PACE]). A dialog can contain one MCP session or A2A
context, or span several, for example when an application reconnects.¶
An application server need not be the dialog host or implement PACE. A server that does not implement PACE works unchanged but does not enforce dialog membership. One that does, even when another origin hosts the dialog, tracks the control log or snapshot to know the participant set and state.¶