What
IRCv3 SASL capability negotiation, letting a client authenticate during
connection registration using the account module.
Why it's deferred, not forgotten
specs/001-ircv3-server/spec.md's capability-scope clarification: "Minimal
core set only — message-tags... server-time... echo-message... Broader
capabilities (SASL beyond the minimum needed for Story 3, account-notify,
away-notify, batch, chathistory, etc.) are deferred to a later iteration."
Current state
Confirmed unimplemented — only message-tags, server-time, and
echo-message capabilities exist in jircd-capabilities/.
Depends on
- The account/authentication module (see the accounts issue) — SASL is the
transport for authenticating against it; there's little reason to build
this before that module exists.
What
IRCv3
SASLcapability negotiation, letting a client authenticate duringconnection registration using the account module.
Why it's deferred, not forgotten
specs/001-ircv3-server/spec.md's capability-scope clarification: "Minimalcore set only —
message-tags...server-time...echo-message... Broadercapabilities (SASL beyond the minimum needed for Story 3, account-notify,
away-notify, batch, chathistory, etc.) are deferred to a later iteration."
Current state
Confirmed unimplemented — only
message-tags,server-time, andecho-messagecapabilities exist injircd-capabilities/.Depends on
transport for authenticating against it; there's little reason to build
this before that module exists.