Consent protocol: Internet-Draft -03

XCIM records explicit consent from the person controlling a recipient email address to an identified sender for specified types of communication. An independent third party attests the consent, with immutable evidence anchored in a blockchain.

Revision -03 specifies EVP, OAuth with authenticated provider API verification, and OpenID Connect (OIDC) as alternative methods to establish control of the email address giving consent. An issuer may use any one admitted method after its required checks. Address verification alone does not grant permission: the same recipient must separately and explicitly accept the identified sender and communication types.

Corrected scope and revision status · eXplicit Consent-Identified Mail (XCIM): draft-saez-xcim-03 · Published text.

This is an individual Internet-Draft with intended status Experimental. Publication does not imply IETF endorsement, working-group adoption or an approved RFC. Amoy provisioning and live-node trials remain paused.

XCIM standardization

XCIM records explicit consent from the person controlling a recipient email address to an identified sender for specified types of communication. An independent third party attests the consent, with immutable evidence anchored in a blockchain.

Current scope and correction

The current published revision is draft-saez-xcim-03. The consent-centered scope introduced in -02 supersedes revisions -00 and -01. Read the consent model, address-control alternatives and current revision status.

Core concerns

Recipient address control, identified sender, explicitly accepted communication types, independent third-party attestation, immutable blockchain evidence and current revocable consent. Verification is independent of individual messages. Optional mail-server integrations consume the result under their own policy.

Historical development archive

The following work is preserved for traceability. It does not define current core conformance or establish readiness of the corrected revision.

Evidence and open work

Current wire-format and verification requirements belong to the published Internet-Draft linked above. Historical test counts are not conformance evidence for that revision. Independent review and interoperability remain separate work. Historical implementation evidence.