Recommendations for the use of whitelists for email senders transmitting email over IPv6
draft-tzink-ipv6mail-whitelist-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Terry Zink | ||
| Last updated | 2013-01-12 (Latest revision 2012-07-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
This document contains a plan for how providers of email services can manage one aspect of the problem of email abuse over IPv6. Spammers can send mail from a very large range of IPv6 addresses, and this will make current antispam blocklisting technology less effective. This is because email receivers will have to maintain excessively large lists of IP blocklists which either consume too many resources, or will become stale and therefore ineffective as spammers quickly discard one IP address and move onto the next one. This document recommends that during the transition of email from IPv4 to IPv6, email receivers implement a whitelisting option where they only allow email from permitted senders over IPv6 and reject or throttle email from everyone else sending email over IPv6.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)