Re: draft-kucherawy-greylisting-bcp
John C Klensin <john+smtp@jck.com> Wed, 26 October 2011 15:44 UTC
Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p9QFicPW066899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Oct 2011 08:44:39 -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 p9QFic5q066898; Wed, 26 Oct 2011 08:44:38 -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 bs.jck.com (ns.jck.com [209.187.148.211]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p9QFib9f066892 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-smtp@imc.org>; Wed, 26 Oct 2011 08:44:38 -0700 (MST) (envelope-from john+smtp@jck.com)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1RJ5eW-000Bj3-EX; Wed, 26 Oct 2011 11:44:28 -0400
Date: Wed, 26 Oct 2011 11:44:27 -0400
From: John C Klensin <john+smtp@jck.com>
To: Pete Resnick <presnick@qualcomm.com>, Keith Moore <moore@network-heretics.com>
cc: dcrocker@bbiw.net, ietf-smtp@imc.org
Subject: Re: draft-kucherawy-greylisting-bcp
Message-ID: <FE312138ED93DAFF4255D966@PST.JCK.COM>
In-Reply-To: <4EA8226D.80303@qualcomm.com>
References: <F5833273385BB34F99288B3648C4F06F19C6C14BFC@EXCH-C2.corp.cloudmark.com> <4EA6EE1A.5010804@qualcomm.com> <4EA7C3AF.1070402@dcrocker.net> <2188C106-043B-4A59-A09C-D88E7B17C307@network-heretics.com> <4EA8226D.80303@qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>
--On Wednesday, October 26, 2011 10:08 -0500 Pete Resnick <presnick@qualcomm.com> wrote: >... > I think Keith has it pretty spot-on. BCPs are for documents > where it makes no sense to talk about the concepts of (to > quote 2026) "protocol, service, procedure, convention, or > format", "particular methods of using a [technical > specification]", "specify particular values or ranges, of TS > parameters or subfunctions of a TS protocol that must be > implemented", "interoperability", and "implementation and/or > operational experience". If it can be deployed and you get get > incremental implementation experience, it should be on the > Standards Track; it shouldn't be a second class citizen of > being a BCP. My personal take is that BCPs should be reserved > to guidelines for operators and administrators, statements of > architectural principles, and documentation of procedures and > operations of the IETF itself. Agree, with one qualification. I don't see BCPs as "second class citizens" even though some of the things that have been published as BCPs push the whole category in that direction. But, especially since we now have only a two-step standards track, if the effect of a document is to modify or give supplemental instructions about a technical specification or protocol (or any of the other phrases Pete quotes above), then we probably owe it to ourselves and the community to use that two-step mechanism to increase the odds that ideas are exposed to the wider community before we finalize them. Dave wrote: > Greylisting is not a protocol, according to any definition I > know. It isn't. Depending on one's point of view, it is either a clever and unanticipated way to use a particular feature/ characteristic of a protocol specification or it is a horrible abuse of a protocol feature that was intended for another purpose. Either way, it extends the originally-intended use of the protocol. And, not only is interoperability testing (at scale, not just two implementations in the lab) relevant to determine the ways in which the technique interacts with implementations that are not aware of it, its effects on the network are in need of continuing and ongoing evaluation. john
- Re: Per-session SMTP extensions Hector Santos
- Re: Per-session SMTP extensions (was: Re: 4yz Tem… Peter J. Holzer
- Re: 4yz Temporary Rejections is part of the SMTP … Robert A. Rosenberg
- Re: Per-session SMTP extensions (was: Re: 4yz Tem… Robert A. Rosenberg
- Re: 4yz Temporary Rejections is part of the SMTP … John C Klensin
- Re: Per-session SMTP extensions (was: Re: 4yz Tem… John C Klensin
- Re: 4yz Temporary Rejections is part of the SMTP … John C Klensin
- Re: Per-session SMTP extensions (was: Re: 4yz Tem… Peter J. Holzer
- Re: 4yz Temporary Rejections is part of the SMTP … Hector Santos
- Re: 4yz Temporary Rejections is part of the SMTP … Paul Smith
- Re: Per-session SMTP extensions Carl S. Gutekunst
- Per-session SMTP extensions (was: Re: 4yz Tempora… John C Klensin
- Re: 4yz Temporary Rejections is part of the SMTP … Carl S. Gutekunst
- Re: 4yz Temporary Rejections is part of the SMTP … Hector Santos
- Re: 4yz Temporary Rejections is part of the SMTP … John C Klensin
- Proposal: SMTP Ext - Base protocol for structured… Hector Santos
- RE: 4yz Temporary Rejections is part of the SMTP … Murray S. Kucherawy
- RE: 4yz Temporary Rejections is part of the SMTP … SM
- Re: 4yz Temporary Rejections is part of the SMTP … Paul Smith
- Re: 4yz Temporary Rejections is part of the SMTP … Hector Santos
- Re: 4yz Temporary Rejections is part of the SMTP … Peter J. Holzer
- RE: 4yz Temporary Rejections is part of the SMTP … Murray S. Kucherawy
- Re: 4yz Temporary Rejections is part of the SMTP … Carl S. Gutekunst
- RE: 4yz Temporary Rejections is part of the SMTP … Murray S. Kucherawy
- Re: 4yz Temporary Rejections is part of the SMTP … Hector Santos
- Re: 4yz Temporary Rejections is part of the SMTP … John C Klensin
- Re: 4yz Temporary Rejections is part of the SMTP … Hector Santos
- Re: 4yz Temporary Rejections is part of the SMTP … Hector Santos
- Re: 4yz Temporary Rejections is part of the SMTP … Robert A. Rosenberg
- Re: draft-kucherawy-greylisting-bcp Pete Resnick
- Re: draft-kucherawy-greylisting-bcp Dave CROCKER
- Re: draft-kucherawy-greylisting-bcp Pete Resnick
- Re: 4yz Temporary Rejections is part of the SMTP … SM
- Re: 4yz Temporary Rejections is part of the SMTP … Hector Santos
- Re: 4yz Temporary Rejections is part of the SMTP … John C Klensin
- 4yz Temporary Rejections is part of the SMTP Prot… Hector Santos
- Re: draft-kucherawy-greylisting-bcp Dave CROCKER
- Re: draft-kucherawy-greylisting-bcp Dave CROCKER
- RE: draft-kucherawy-greylisting-bcp Murray S. Kucherawy
- RE: draft-kucherawy-greylisting-bcp Murray S. Kucherawy
- Re: draft-kucherawy-greylisting-bcp Hector
- Re: draft-kucherawy-greylisting-bcp Keith Moore
- Re: draft-kucherawy-greylisting-bcp Pete Resnick
- Re: draft-kucherawy-greylisting-bcp John C Klensin
- Re: draft-kucherawy-greylisting-bcp Steve Atkins
- Re: draft-kucherawy-greylisting-bcp Dave CROCKER
- Re: draft-kucherawy-greylisting-bcp Tim Kehres
- Re: draft-kucherawy-greylisting-bcp Pete Resnick
- Re: draft-kucherawy-greylisting-bcp Dave CROCKER
- Re: draft-kucherawy-greylisting-bcp Pete Resnick
- Re: draft-kucherawy-greylisting-bcp Keith Moore
- Re: draft-kucherawy-greylisting-bcp Dave CROCKER
- RE: draft-kucherawy-greylisting-bcp Murray S. Kucherawy
- Re: draft-kucherawy-greylisting-bcp Pete Resnick
- draft-kucherawy-greylisting-bcp Murray S. Kucherawy
- Re: 4yz Temporary Rejections is part of the SMTP … Jeff Macdonald