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

Dave Cridland <dave@cridland.net> Wed, 18 June 2008 22:07 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 452FB3A6820; Wed, 18 Jun 2008 15:07:51 -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 A7E463A6837; Wed, 18 Jun 2008 15:07:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.308
X-Spam-Level:
X-Spam-Status: No, score=-1.308 tagged_above=-999 required=5 tests=[AWL=-0.184, 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 RbFHC6-TkaO4; Wed, 18 Jun 2008 15:07:48 -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 AD56A3A6814; Wed, 18 Jun 2008 15:07:47 -0700 (PDT)
Received: from invsysm1 (shiny.isode.com [62.3.217.250]) by turner.dave.cridland.net (submission) via TCP with ESMTPA id <SFjlwAATl8bg@turner.dave.cridland.net>; Wed, 18 Jun 2008 11:38:58 +0100
Subject: RE: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
References: =?US-ASCII?Q?<8832006D4D21836CBE6DB469@klensin-?= =?US-ASCII?Q?sus.vbn.inter-touch.net><485590E2.3080107@gma?= =?US-ASCII?Q?l.com><p06250116c47c330c7dd0@[75.145.176.242]?= <4856DE3A.3090804@gmail.com> <049b01c8d089$6c901ce0$0a00a8c0@CPQ86763045110>
In-Reply-To: <049b01c8d089$6c901ce0$0a00a8c0@CPQ86763045110>
MIME-Version: 1.0
Message-Id: <23618.1213785541.031305@invsysm1>
Date: Wed, 18 Jun 2008 11:39:01 +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 Tue Jun 17 15:50:02 2008, Debbie Garside wrote:
> Not being a expert on this but having briefly read the documents in
> question, I agree with Brian.  This is not editorial.

Well, people have commented that changing the examples will hardly  
break the Internet mail system, so it seems reasonable to assert that  
the counter-argument is also true. In other words, NOT changing the  
examples will also not break Internet mail. However, I couldn't  
really care what the examples say, as long as they're good, clear  
examples, and I think they are.

>  I would also add that
> to go against an IETF BCP

Ah, wait - the document in question is not a missive from the mount  
stating "Thou SHALT use example.net everywhere", it says "The IETF  
said, 'Let there be reserved domain names for examples'; and there  
were."

(I'm translating the documents into language more suitable for the  
religious tracts some people appear to think they are - at this rate,  
I'm fully expecting future editions to include marginalia comencing  
"Once, a student asked the Postel ...")

But the facts are that nobody is "going against" the BCP. The  
examples in the document don't take advantage of the facilities  
provided by the BCP, but that's different.

>  on the grounds of "well we have done so already
> historically" does not make an argument for continuing to do so;

Perhaps your implication that, irrespective of the past behaviour, we  
should create such a rule is sensible...

>  errors
> should be corrected when found, not endorsed.

... but until we do, it is not an error, and - crucially - we should  
not expect nor allow the IESG to decide on a whim what is and is not  
an error.

>   If we are to pick and choose
> which RFC's/BCP's we will take notice of what is the point of
> standardization? 

Well, indeed, bravo, and well spoken - that's what John's appeal is  
about - what's the point of having procedures and policies at all if  
the IESG can say "I must reject your document; it is purple. No  
purple documents on Wednesdays, for lo, I have spoken."

You may think I'm making light of this - and I am, because I think  
it's a remarkably silly stance from the IESG - but if you can explain  
the difference between rejecting all purple documents on Wednesdays  
and rejecting documents that do not use RFC 2606, I'll be most  
grateful.

> On the face of things, and with my little knowledge, I
> would say that the person within the IESG who has invoked the  
> DISCUSS is
> quite correct.
> 
> 
And I reckon they're talking bananas.

It doesn't matter, incidentally, whether you consider the use of  
example.com to be a good idea or not. I do, although I note that the  
XSF's tradition of using a fictional ".lit" TLD with example domains  
taken from Shakespeare's plays is actually considerably more  
readable, but anyway, I'd be perfectly happy if the IESG made a  
statement that as of now, documents which use domains other than  
those present in RFC 2606 will not be acceptable.

But I note that there is no such statement from the IESG, so I'm  
personally not clear about whether there even is such a policy, or  
upon which days of the week it applies - for all I know, given the  
lack of statements made by the IESG on RFC 2606 names, these may be  
mandated only for purple documents submitted on Wednesdays. And those  
aren't allowed, as previously discussed. (And yeah, I know, but  
consider this - if I say that the IESG say that purple documents are  
not allowed on Wednesdays, that gives that equal weight with the  
alledged RFC 2606 rule - the IESG has not made any statement, we've  
only heard about this informally via third parties).

What matters here is whether the IESG is allowed to introduce and  
enforce a rule with the same action. I do not believe they should be  
allowed to.

Even on Wednesdays.

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