RE: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis

Dave Cridland <dave@cridland.net> Wed, 18 June 2008 20:20 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 884773A6A32; Wed, 18 Jun 2008 13:20:59 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2C653A6A32; Wed, 18 Jun 2008 13:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.492
X-Spam-Level:
X-Spam-Status: No, score=-1.492 tagged_above=-999 required=5 tests=[AWL=-0.369, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_NET=0.611, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2FrxhadLlUT; Wed, 18 Jun 2008 13:20:57 -0700 (PDT)
Received: from turner.dave.cridland.net (dsl-217-155-137-60.zen.co.uk [217.155.137.60]) by core3.amsl.com (Postfix) with ESMTP id 871DE3A68F6; Wed, 18 Jun 2008 13:20:56 -0700 (PDT)
Received: from invsysm1 (shiny.isode.com [62.3.217.250]) by turner.dave.cridland.net (submission) via TCP with ESMTPA id <SFjxQgATl7IV@turner.dave.cridland.net>; Wed, 18 Jun 2008 12:28:03 +0100
Subject: RE: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
References: <8832006D4D21836CBE6DB469@klensin-us.vbn.inter-touch.net><485590E2.3080107@gmalcom><p06250116c47c330c7dd0@[75.145.176.242] <4856DE3A.3090804@gmail.com> <049b01c8d089$6c901ce0$0a00a8c0@CPQ86763045110> <23618.1213785541.031305@invsysm1> <059901c8d132$d65df170$0a00a8c0@CPQ86763045110>
In-Reply-To: <059901c8d132$d65df170$0a00a8c0@CPQ86763045110>
MIME-Version: 1.0
Message-Id: <23618.1213788490.265871@invsysm1>
Date: Wed, 18 Jun 2008 12:28:10 +0100
From: Dave Cridland <dave@cridland.net>
To: debbie@ictmarketing.co.uk
Cc: 'John C Klensin' <john-ietf@jck.com>, 'Pete Resnick' <presnick@qualcomm.com>, iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Wed Jun 18 12:02:44 2008, Debbie Garside wrote:
> Dave wrote:
> 
> > Even on Wednesdays.
> 
> Or for purple documents... ;-)
> 
> I see your point.  I do think, assuming it is not already  
> documented and
> further assuming this is the whole point of the appeal, that the  
> IESG could
> create a general policy wrt BCP's.

Well, that is indeed a possibility, but RFC 2606 - the BCP involved  
in this specific case - does not state anywhere that people MUST use  
the domains it reserves in examples.

Therefore, to cover this particular case, such a blanket policy would  
have to be stated such that even vague recommendations in BCPs MUST  
be followed religiously, even if the document's author not only  
doesn't think that was the purpose of the document, but clearly  
states that wasn't the reason it's a BCP anyway.

Maybe the policy could also state a Doctrine Of IESG Infallibility,  
and just bypass the entire issue.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf