Proof of Consent Mechanism
draft-hallambaker-consent-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Phillip Hallam-Baker | ||
| Last updated | 2004-07-16 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
We propose a mechanism Proof of Consent that allows an email recipient to provide verifiable proof of ‘opt-in’ consent to receive email. Proof of Consent may be used to automatically whitelist email from mailing lists and email forwarded from another email server. Proof of Consent is designed to require minimal state maintenance by both the email sender and the recipient and to be deployable with minimal impact on existing email infrastructure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)