Re: Last Call: draft-harkins-emu-eap-pwd (EAP Authentication UsingOnly A Password) to Informational RFC

John Leslie <john@jlc.net> Wed, 22 July 2009 18:03 UTC

Return-Path: <john@jlc.net>
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 252803A68D7 for <ietf@core3.amsl.com>; Wed, 22 Jul 2009 11:03:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.732
X-Spam-Level:
X-Spam-Status: No, score=-5.732 tagged_above=-999 required=5 tests=[AWL=0.868, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 j8-XTJXUGpnU for <ietf@core3.amsl.com>; Wed, 22 Jul 2009 11:03:08 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.9]) by core3.amsl.com (Postfix) with ESMTP id 471023A6820 for <ietf@ietf.org>; Wed, 22 Jul 2009 11:03:08 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 83F7633C25; Wed, 22 Jul 2009 13:27:42 -0400 (EDT)
Date: Wed, 22 Jul 2009 13:27:42 -0400
From: John Leslie <john@jlc.net>
To: Glen Zorn <gwz@net-zen.net>
Subject: Re: Last Call: draft-harkins-emu-eap-pwd (EAP Authentication UsingOnly A Password) to Informational RFC
Message-ID: <20090722172742.GH99140@verdi>
References: <012501ca0a0b$b435e770$1ca1b650$@net> <AC1CFD94F59A264488DC2BEC3E890DE50867B247@xmb-sjc-225.amer.cisco.com> <00a201ca0aa1$cf2c9ba0$6d85d2e0$@net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <00a201ca0aa1$cf2c9ba0$6d85d2e0$@net>
User-Agent: Mutt/1.4.1i
Cc: 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/mail-archive/web/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>
X-List-Received-Date: Wed, 22 Jul 2009 18:03:09 -0000

Glen Zorn <gwz@net-zen.net> wrote:
> Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com] writes:
>  
>> I object to this document being published as a Proposed Standard.  When
>> this document was discussed in the EMU meeting at IETF-71 there was
>> much concern raised with respect to existing IPR...
> 
> IMHO, this question is orthogonal (& largely immaterial) to the one at hand.

   Agreed.

> It's one thing for the IETF to reach consensus that the draft be
> Informational; it is a completely different thing for the publication path
> to be changed without either notification of (other than the Last Call
> announcement itself) or consultation with the authors.

   Lack of consultation with the authors would be unfortunate.

> If this was _not_ a simple error, then the action was arbitrary &
> capricious, not to mentioned underhanded & must certainly be considered
> as grounds for dismissal of the (as yet unnamed) person or persons
> responsible,

   I do not agree. At most, an apology might be required.

> unless the IETF has recently converted to an authoritarian regime.

   There is nothing "recent" about this. To be considered by the IESG,
there must be a sponsoring Area Director for any Individual Submission.
That Area Director has always had full authority to decide whether to
LastCall as Informational or Proposed Standard.

> As an aside, it seems that draft-green-secsh-ecc has suffered the same
> fate, suggesting that this is neither an error nor an isolated occurrence.

   Exactly!

   (You technically have the right to appeal the decision to LastCall as
Informational; but the Area Director will always have the right to
decline to sponsor publication as Proposed Standard.)

   The difference may not be as great as you seem to think. Appeal if
you must, but it's really not unusual to change "proposed status" as
a result of LastCall comments. It might be more helpful to simply post
(polite) LastCall comments of your own about why "Proposed Standard"
would be more appropriate than "Informational".

--
John Leslie <john@jlc.net>