Re: [apps-discuss] Status of the malformed mail BCP
Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 11 August 2011 14:08 UTC
Return-Path: <ajs@anvilwalrusden.com>
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 A053521F861E for <apps-discuss@ietfa.amsl.com>; Thu, 11 Aug 2011 07:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level:
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599]
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 1yplY2rjAtmH for <apps-discuss@ietfa.amsl.com>; Thu, 11 Aug 2011 07:08:38 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id B6EF221F85FE for <apps-discuss@ietf.org>; Thu, 11 Aug 2011 07:08:38 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 8BCBA1ECB41D for <apps-discuss@ietf.org>; Thu, 11 Aug 2011 14:09:13 +0000 (UTC)
Date: Thu, 11 Aug 2011 10:09:10 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: apps-discuss@ietf.org
Message-ID: <20110811140910.GE95640@shinkuro.com>
References: <F5833273385BB34F99288B3648C4F06F13512DF694@EXCH-C2.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF694@EXCH-C2.corp.cloudmark.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [apps-discuss] Status of the malformed mail BCP
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Thu, 11 Aug 2011 14:08:39 -0000
On Wed, Aug 10, 2011 at 09:10:38AM -0700, Murray S. Kucherawy wrote: > So I think my next step is to convert the existing document into > exactly that. Since the main objection to doing it as an RFC is the > idea that it might need to be changed often, perhaps we should go > with Expert Review instead of one of the rules that says a > specification has to exist. Any comments on that point? I think this is stretching past the point of pragmatism. The proposal, so far, is a sort of extreme case of being liberal in what one accepts (and what one does thereafter, of course). I have to agree with Peter's detection of slight absurdity here, but I also question whether it would be possible to select an appropriate expert. Who is more expert in not conforming to the existing protocol documents than the person who is so nonconforming? And if there is nobody, then the correct expert to appoint in each case would be the implementer of the nonconforming implementation, who would perform the review and approve the registry entry. Therefore, assigning the registry entry on detection of nonconformance would be correct, and no expert is needed. At that point, of course, the problem becomes that you need a stable reference for the way the nonconformance works, and so you need a specification anyway. So "specification required" is correct, I think. (The entire passage above, however, could as easily be construed as a reductio argument against such a registry at all.) A -- Andrew Sullivan ajs@anvilwalrusden.com
- [apps-discuss] Status of the malformed mail BCP Murray S. Kucherawy
- Re: [apps-discuss] Status of the malformed mail B… SM
- Re: [apps-discuss] Status of the malformed mail B… Murray S. Kucherawy
- Re: [apps-discuss] Status of the malformed mail B… Simon Perreault
- Re: [apps-discuss] Status of the malformed mail B… Frank Ellermann
- Re: [apps-discuss] Status of the malformed mail B… Peter Koch
- Re: [apps-discuss] Status of the malformed mail B… Cyrus Daboo
- Re: [apps-discuss] Status of the malformed mail B… Andrew Sullivan
- Re: [apps-discuss] Status of the malformed mail B… Nathaniel Borenstein