listwatch: watch the dmsc list - #336
Merged
Merged
Conversation
SAMP discussion is moving from agent2agent to dmsc, the ART-area BoF "Dynamic Multi-agent Secured Collaboration" registered on 2026-06-29. The list parses with the existing IETF entry regex; no new source or trigger term is needed. Dry run over the branch: dmsc 2026-08 19 messages, 2026-09 18, all new. No KNOWN_SENDERS entry, so the NEW SENDER trigger stays off for it until a roster is established.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SAMP discussion is moving from
agent2agenttodmsc, the ART-area BoF "Dynamic Multi-agent Secured Collaboration" (registered 2026-06-29,dmsc@ietf.org).Adds one entry to
LISTS. No new source, no new trigger term — the list parses with the existing IETF entry regex.Read-only verification before the edit
Dry run on this branch
Triggers fire as expected on the parsed bodies (
STRUCTURE: charter,MOLTRUST: emilia). State was not written.Note on seeding
--seedseeds every list at once and suppresses the report. At the time of the dry runagent2agent 2026-09held 5 unreported messages, which a seed would mark as seen and silently drop. So no seed here: the first cron run after merge reports the 37-message dmsc backlog once, then settles.No
KNOWN_SENDERSentry for dmsc, so the NEW SENDER trigger stays off until a roster is established — same handling the file already documents for lists whose roster is unknown.