Re: draft-kucherawy-greylisting-bcp
Dave CROCKER <dhc@dcrocker.net> Fri, 28 October 2011 05:13 UTC
Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p9S5DWCl049415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Oct 2011 22:13:32 -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 p9S5DW4s049414; Thu, 27 Oct 2011 22:13:32 -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 sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p9S5DVNa049408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-smtp@imc.org>; Thu, 27 Oct 2011 22:13:32 -0700 (MST) (envelope-from dhc@dcrocker.net)
Received: from [10.115.193.62] (62-50-227-5.client.stsn.net [62.50.227.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p9S5DMeS011733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Oct 2011 22:13:30 -0700
Message-ID: <4EAA39ED.4080802@dcrocker.net>
Date: Fri, 28 Oct 2011 07:13:17 +0200
From: Dave CROCKER <dhc@dcrocker.net>
Reply-To: dcrocker@bbiw.net
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
CC: "ietf-smtp@imc.org" <ietf-smtp@imc.org>
Subject: Re: draft-kucherawy-greylisting-bcp
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> <F5833273385BB34F99288B3648C4F06F19C6C14CFA@EXCH-C2.corp.cloudmark.com> <4EAA2F74.9040100@qualcomm.com>
In-Reply-To: <4EAA2F74.9040100@qualcomm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 27 Oct 2011 22:13:31 -0700 (PDT)
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>
Pete, On 10/28/2011 6:28 AM, Pete Resnick wrote: > > Herein lies my confusion. What is a Best Current Practices document if not one >> that talks about conventions, particular methods of using the thing a >> specification defines, [improved] interoperability, or relating of operational >> experience? > > I say it just below: A BCP document gives guidelines to operators and > administrators, gives statements of architectural principle, or documents > procedures and operations of the IETF itself. BCPs ought not have conventions > and particular methods of using a technical specification, etc. > If a document is > defines conventions and particular methods of using a technical specification, > then there can be implementations of the document, and therefore incremental > experience with it, and it therefore should be on the standards track. > If a > document defines ways of being interoperable with a technical specification, > then there can be implementations of the document, and therefore incremental > experience with it, and it therefore should be on the standards track. You think BCP 23, 24, 28, 34, ... involve no software and do not change the behavior of protocol engines? By your personal definitions, these seem to have been mis-assigned and ought to be required to be standards track. > All of > these kinds of statements (and the additional ones I cite above) are > applicability statements, and those statements can be implemented, and we can > get incremental experience with those statements, and therefore documents with > those statements belong on the standards track. There is a core problem: you appear to be using your personal terminology and definitions, rather than reflecting community practice. In all likelihood, your terms and definitions are more reasonable, consistent and practical than the community's, but that's irrelevant. What is relevant is established practice. It's fine to seek a change in established practice, but not as a sole voice in a management position, invoking personal and distinct language and requirements. That's not supposed to be the way things work around here. My query about applicability statements was not about documents that effectively serve that role but about documents that are formally assigned that status AND are effective. Established practice, not personal assessment. > The distinction I want to make is: If you're giving implementation > specifications or guidance for the protocol, those belongs as part of a > standards track document, whether they are statements in the protocol document > itself or statements in a standalone document (which I've been calling an AS). Please get the consensus of the community about this. Please then re-label the documents that have been misassigned. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net
- 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