Re: [apps-discuss] A greylisting question

Dave CROCKER <dhc@dcrocker.net> Fri, 17 February 2012 13:50 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB24621F86D5 for <apps-discuss@ietfa.amsl.com>; Fri, 17 Feb 2012 05:50:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8F+jkcN0dGFw for <apps-discuss@ietfa.amsl.com>; Fri, 17 Feb 2012 05:50:29 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C76A421F86D1 for <apps-discuss@ietf.org>; Fri, 17 Feb 2012 05:50:28 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1HDoNgQ012807 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <apps-discuss@ietf.org>; Fri, 17 Feb 2012 05:50:28 -0800
Message-ID: <4F3E5B1B.7090200@dcrocker.net>
Date: Fri, 17 Feb 2012 05:50:19 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <F5833273385BB34F99288B3648C4F06F19C9A7DDDF@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C9A7DDDF@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 17 Feb 2012 05:50:28 -0800 (PST)
Subject: Re: [apps-discuss] A greylisting question
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2012 13:50:30 -0000

On 2/16/2012 11:35 PM, Murray S. Kucherawy wrote:
> I suspect the IESG will ask this if we don’t cover it, so let’s put something in
> about this now…
>
> The current draft only talks about IPv4, because that’s what we have experience
> with so far in terms of greylisting. How does our advice translate to IPv6? Is
> it the same?


There will, at least, be some differences and possibly many.  But since we have 
no experience with this stuff in that space, we can't be sure.  There is no 
practice that we can declare 'best'.  At most, we can add a comment 
acknowledging the topic and commenting on some basic issues.

Something along the lines of:

      At the time of this writing, there is no widespread experience with 
greylisting as applied to sources using IPv6 addresses.  The greater size of an 
IPv6 address seems likely to permit differences in behaviors by bad actors, and 
this could well mean needing to alter the details for applying greylisting; it 
might even negate any benefits in using greylisting at all.  At a minimum, it is 
likely to call for different specific choices for any greylisting algorithm 
variables.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net