Re: [Asrg] How will we manage IPv6 spam?
Daniel Feenberg <feenberg@nber.org> Fri, 17 August 2012 21:16 UTC
Return-Path: <feenberg@nber.org>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id EF83411E80EF for <asrg@ietfa.amsl.com>;
Fri, 17 Aug 2012 14:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hv6UUvI9IJrQ for
<asrg@ietfa.amsl.com>; Fri, 17 Aug 2012 14:16:23 -0700 (PDT)
Received: from mail2.nber.org (mail2.nber.org [66.251.72.79]) by
ietfa.amsl.com (Postfix) with ESMTP id 2F67C11E80F0 for <asrg@irtf.org>;
Fri, 17 Aug 2012 14:16:21 -0700 (PDT)
Received: from nber6 (nber6.nber.org [66.251.72.76]) by mail2.nber.org
(8.14.4/8.14.4) with ESMTP id q7HLGHbU094936;
Fri, 17 Aug 2012 17:16:17 -0400 (EDT) (envelope-from feenberg@nber.org)
Date: Fri, 17 Aug 2012 17:08:02 -0400 (EDT)
From: Daniel Feenberg <feenberg@nber.org>
X-X-Sender: feenberg@nber6
To: Michael Thomas <mike@mtcc.com>
In-Reply-To: <502EB1E1.6050807@mtcc.com>
Message-ID: <Pine.GSO.4.64.1208171702000.8836@nber6>
References: <alpine.BSF.2.00.1208171554300.31068@joyce.lan>
<Pine.GSO.4.64.1208171642250.8836@nber6> <502EB1E1.6050807@mtcc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.39/RELEASE,
bases: 20120817 #7899949, check: 20120817 clean
Cc: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Subject: Re: [Asrg] How will we manage IPv6 spam?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>,
<mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>,
<mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 21:16:24 -0000
On Fri, 17 Aug 2012, Michael Thomas wrote: > On 08/17/2012 01:51 PM, Daniel Feenberg wrote: >> >> >> On Fri, 17 Aug 2012, John R. Levine wrote: >> >>> Hi. Remember the ASRG? I was hoping it might do a little research. >>> >>> In talking to people about IPv6 mail, I'm still coming to the conclusion >>> that anyone who thinks they know how they're going to handle it, beyond >>> the current toy scale, doesn't understand the problem. Things we might >>> address include: >>> >> >> I would not expect to accept any IPv6 mail until users come forward to show >> me that they wish to correspond with MTAs that have no IPv4 connection >> ability. While this may happen in the fullness of time, I don't expect it >> soon. Now and for the foreseeable future such a system would have very >> little connectivity, far less than a blacklisted spam source. > > Host operating systems -- all of them to my knowledge -- prefer v6 over > v4 if you have a public v6 address. So the mere existence of a AAAA > associated with the MX will cause the sender to pick the v6 destination. > I have a v6 mail system and got bitten because I had forgot to put up > the v6 reverse map. It will happen just as a natural consequence of > people enabling v6 on their infrastructure. This sounds inconvenient. If I want to accept mail from one IPv6 host, then all the IPv6 hosts will want to use IPv6, and unless I accept mail from unknown IPv6 hosts, mail from hosts that would have been accepted over IPv4 will be rejected? That is a problem, but I can't imagine IPv6 acceptance being so universal that there would be more desirable mail from IPv6 only hosts than from IPv4 only hosts, at least not for some decades. This is especially true since more important hosts are more likely to have access to IPv4 addresses. I actually wonder if the transition could ever occur as long as IPv4 is supported at all by ISPs. daniel feenberg NBER > > Mike >
- [Asrg] How will we manage IPv6 spam? John R. Levine
- Re: [Asrg] How will we manage IPv6 spam? Daniel Feenberg
- Re: [Asrg] How will we manage IPv6 spam? Michael Thomas
- Re: [Asrg] How will we manage IPv6 spam? Daniel Feenberg
- Re: [Asrg] How will we manage IPv6 spam? Paul Smith
- Re: [Asrg] How will we manage IPv6 spam? Michael Thomas
- Re: [Asrg] How will we manage IPv6 spam? John Levine
- Re: [Asrg] How will we manage IPv6 spam? Daniel Feenberg
- Re: [Asrg] How will we manage IPv6 spam? Daniel Feenberg
- Re: [Asrg] How will we manage IPv6 spam? Paul Smith
- Re: [Asrg] How will we manage IPv6 spam? Emanuele Balla (aka Skull)
- Re: [Asrg] How will we manage IPv6 spam? SM
- Re: [Asrg] rDNS and cache issues, was How will we… John Levine
- Re: [Asrg] rDNS and cache issues, was How will we… Emanuele Balla (aka Skull)
- Re: [Asrg] rDNS and cache issues, was How will we… Matthias Leisi
- Re: [Asrg] rDNS and cache issues, was How will we… John Levine