HTTP Header for Future Correspondence Addresses
draft-shacham-http-corr-uris-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ron Shacham , Henning Schulzrinne | ||
| Last updated | 2007-05-11 | ||
| 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
A large amount of email is non-personal, automated communication, such as newsletters, confirmations and legitimate advertisements. These are often tagged as spam by content filters. This type of correspondence is usually initiated by a transaction over the web, such as a purchase or signing up for a service. Therefore, we propose a new HTTP header to carry the addresses that may be used by the provider to correspond with the user. These may be email addresses, or those used in other protocols, such as SIP. This will facilitate the automatic inclusion of these addresses in whitelists used for spam prevention.
Authors
Ron Shacham
Henning Schulzrinne
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)