Re: draft-kucherawy-greylisting-bcp

Keith Moore <moore@network-heretics.com> Wed, 26 October 2011 12:12 UTC

Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p9QCCgEt057253 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Oct 2011 05:12:42 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id p9QCCgIb057252; Wed, 26 Oct 2011 05:12:42 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p9QCCew2057246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-smtp@imc.org>; Wed, 26 Oct 2011 05:12:41 -0700 (MST) (envelope-from moore@network-heretics.com)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 7690920B80; Wed, 26 Oct 2011 08:12:39 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Wed, 26 Oct 2011 08:12:39 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=q51SBTDHlkDlMwsBg9O6d9faHqs=; b=uj ywqMRAxbZqUYuZw3mP+eSKOMYC4aQ8VlJrKRLrX1NXjEYoMD57LEdDe4l3UZ9TTe rvfMJNbfrVfjAj9G5LP23gYLe9nK8xOdfbekKz06mhhM3GQsdeOWFBOCBUge0O6L M5/rTH8zhI7mUTsIM+v9HTnrbIwOFTXBAm+F0ysUc=
X-Sasl-enc: 3x2W27rWg+tc4DxparIrRx/PStqGyVrwSJ2ExpD3LLOj 1319631158
Received: from [192.168.1.16] (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 75CBA40CEB6; Wed, 26 Oct 2011 08:12:38 -0400 (EDT)
Subject: Re: draft-kucherawy-greylisting-bcp
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4EA7C3AF.1070402@dcrocker.net>
Date: Wed, 26 Oct 2011 08:12:37 -0400
Cc: Pete Resnick <presnick@qualcomm.com>, "ietf-smtp@imc.org" <ietf-smtp@imc.org>
Message-Id: <2188C106-043B-4A59-A09C-D88E7B17C307@network-heretics.com>
References: <F5833273385BB34F99288B3648C4F06F19C6C14BFC@EXCH-C2.corp.cloudmark.com> <4EA6EE1A.5010804@qualcomm.com> <4EA7C3AF.1070402@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id p9QCCfw1057247
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

IMO, BCPs are a way for IETF to endorse desirable practices for which the 2026 advancement criteria (e.g. interoperability tests) are not applicable.

On Oct 26, 2011, at 4:24 AM, Dave CROCKER wrote:

> 
> Pete,
> 
> I don't understand, either.  While it lists a /set/ of alternative or complementary best practices, it /is/ about best practices.  Please explain.
> 
> d/
> 
> On 10/25/2011 7:12 PM, Pete Resnick wrote:
>> 
>> (a) This shouldn't be labeled as a BCP. It's an A/S Standards Track draft if
>> ever there was one.
>> (b) Given this and the extension, is it worth spinning up a Greylisting WG?
>> 
>> pr
>> 
>> On 10/23/11 3:40 PM, Murray S. Kucherawy wrote:
>>> Maybe a new thread Subject: would help here...
>>> 
>>> Given the interest, I've started putting together a BCP. It's now posted as
>>> draft-kucherawy-greylisting-bcp; comments welcome (and thanks to those of you
>>> that already did). It is only an outline right now, and I'll fill it in as
>>> people make suggestions about topics it should cover and/or start providing
>>> text to include.
>>> 
>>> It doesn't touch the SMTP extension people are discussing. Someone else can
>>> champion that one if so inclined. That shouldn't go in a BCP because it
>>> doesn't even exist yet. This document will only describe current and historic
>>> practices.
>>> 
>>> Maybe we can get it on the docket for Taipei. I'll send out some friendly pings.
>>> 
>>> -MSK
>>> 
>>> 
>> 
> 
> -- 
> 
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
>