feat: add 2026-04-08 weekly meeting notes (#32)
This commit is contained in:
parent
bf117ddccd
commit
10b122934c
1 changed files with 79 additions and 0 deletions
79
meetings/2026-04-08_weekly.md
Normal file
79
meetings/2026-04-08_weekly.md
Normal file
|
|
@ -0,0 +1,79 @@
|
|||
# 2026-04-08 Transports WG (Weekly)
|
||||
|
||||
## TL;DR
|
||||
The group discussed the outcomes of the recent Dev Summit, most notably the core
|
||||
maintainers' decision to officially remove sessions from the protocol and
|
||||
establish the new Multi-Roundtrip Request (MRTR) pattern as the default. Peter
|
||||
Alexander will draft the Specification Enhancement Proposal (SEP) for session
|
||||
removal, which will drastically simplify SEP 1442. The group also refined the
|
||||
scope of MRTR, deciding that elicitation will be restricted to specific requests
|
||||
(`read resources`, `get prompt`, `call tool`, and `get task payload request`)
|
||||
and explicitly disallowed on `list` requests to preserve caching functionality.
|
||||
Finally, the group agreed that Time-To-Live (TTL) functionality must be included
|
||||
in the June release to support caching without Server-Sent Events (SSE), and
|
||||
established ownership for several upcoming SEPs to meet the looming deadlines.
|
||||
|
||||
## Detailed Summary
|
||||
|
||||
### Dev Summit Outcomes and Process
|
||||
* **Session Removal:** Core maintainers voted to eliminate sessions from the
|
||||
protocol. This decision significantly reduces the scope of SEP 1442 (which
|
||||
Kurtis Van Gent will now rewrite). Peter Alexander is tasked with drafting a
|
||||
standalone SEP explicitly documenting the removal of sessions.
|
||||
* **MRTR Code Pattern:** The async code pattern has been officially deprecated,
|
||||
making the new MRTR pattern the default. Stephen Halter provided a link to a
|
||||
reference implementation comparing the old and new methods.
|
||||
* **Tracking and Backlog:** Kurtis Van Gent is creating a tracking spreadsheet
|
||||
and a prioritized backlog to monitor the progress of all SEPs (MRTR, Pluggable
|
||||
Transports, 1442, etc.) toward reference implementation and finalization for
|
||||
the June release.
|
||||
* **Draft Versioning:** Stephen Halter raised the need for a standardized
|
||||
protocol version string for the draft SDKs to facilitate compatibility
|
||||
testing. Suggestions included `2026-draft` or prefixing with a date. Stephen
|
||||
will follow up with SDK maintainers to align on a standard string.
|
||||
|
||||
### Technical Decisions: MRTR Scope and Capabilities
|
||||
* **Restricting Elicitation:** Caitie McCaffrey proposed scoping down the client
|
||||
requests that support server requests for additional information
|
||||
(elicitation).
|
||||
* **Allowed Requests:** The group agreed to restrict elicitation to `read
|
||||
resources`, `get prompt`, `call tool`, and `get task payload request`.
|
||||
* **Disallowed Requests:** Elicitation will *not* be permitted on `ping`,
|
||||
`initialize`, `list` requests (e.g., `list tools`), or task-related endpoints.
|
||||
This restriction ensures that tools lists remain cacheable and do not mutate
|
||||
based on individual request contexts.
|
||||
* **Capabilities on Tool Lists:** Because the protocol is stateless and
|
||||
elicitation is no longer allowed on `list tools`, a client might call a tool
|
||||
requiring elicitation without actually supporting it. Gabriel Zimmerman
|
||||
proposed an SEP to allow the server to return the required capabilities for
|
||||
specific tools alongside the tool list.
|
||||
|
||||
### Technical Decisions: Caching, TTLs, and Deprecations
|
||||
* **Feature Deprecations:** Peter Alexander noted that `sampling roots` and `log
|
||||
level` (or logging altogether) are candidates for deprecation in the upcoming
|
||||
release. Prompts will remain as they are actively used. Andreas Schlapbach
|
||||
highlighted the need for a formal deprecation policy (sunsetting before
|
||||
removal).
|
||||
* **Time-To-Live (TTL):** Kurtis Van Gent stressed that TTL functionality is
|
||||
critical for the current release to support caching, especially since the
|
||||
protocol is moving away from reliance on SSE streams.
|
||||
* **TTL Scope:** Mark Roth clarified that the TTL mechanism acts similarly to a
|
||||
DNS TTL (a maximum cache time for previous results) and must work for both
|
||||
HTTP and standard IO transports. Caitie McCaffrey volunteered to draft this
|
||||
SEP to expedite the process.
|
||||
|
||||
## Action Items
|
||||
- [ ] **Peter Alexander** to write the SEP officially removing sessions from the
|
||||
protocol.
|
||||
- [ ] **Kurtis Van Gent** to rewrite SEP 1442 reflecting the removal of sessions
|
||||
and initialization.
|
||||
- [ ] **Kurtis Van Gent** to finalize the tracking spreadsheet and prioritized
|
||||
backlog of all SEPs targeted for the June release by the end of the week.
|
||||
- [ ] **Caitie McCaffrey** to compile a list of Tasks-related SEPs and send them
|
||||
to Kurtis for the tracking spreadsheet.
|
||||
- [ ] **Stephen Halter** to coordinate with SDK maintainers to align on a
|
||||
standardized protocol version string for the draft.
|
||||
- [ ] **Caitie McCaffrey** to draft the SEP defining Time-To-Live (TTL) fields
|
||||
for relevant primitives.
|
||||
- [ ] **Gabriel Zimmerman** to write an SEP specifying how servers can declare
|
||||
required capabilities for specific tools within the tool list.
|
||||
Loading…
Reference in a new issue