Re: [apps-discuss] Comments on draft-ietf-appsawg-received-state

SM <sm@resistor.net> Thu, 14 June 2012 15:18 UTC

Return-Path: <sm@resistor.net>
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 78C8E21F86EA for <apps-discuss@ietfa.amsl.com>; Thu, 14 Jun 2012 08:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level:
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 NDhXodEzz7Db for <apps-discuss@ietfa.amsl.com>; Thu, 14 Jun 2012 08:18:19 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 51CF921F86E8 for <apps-discuss@ietf.org>; Thu, 14 Jun 2012 08:18:19 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5EFIE8Q019725 for <apps-discuss@ietf.org>; Thu, 14 Jun 2012 08:18:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1339687098; i=@resistor.net; bh=S1Y8wZ5aJHZQv48h2U1HdTw3ANCGzioAPr0FJ+jDO2k=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=tqwlch/M8NN3LaNqzjjusWv1FJIHsZNltNILlbRNGmCYlLPjp7UQAxsuCCB/Zsvw+ VW5G/igAAg50l+vk7Gh+iO5ubmT6L/RXX85FkSWH/LnnAp67Ey87V0aiSXgKaxRv1O 0I7zCOBM/5wXMuJnXkOb8Xaw6WVWuJXLRSnvqos4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1339687098; i=@resistor.net; bh=S1Y8wZ5aJHZQv48h2U1HdTw3ANCGzioAPr0FJ+jDO2k=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=HCJcH2Eg++azIPLk4gMfgs8/iEfOgXHvKIx4fyh1WttytGkoNL+dsWbvZqCpg9AbH I5BWBMXy8OJfP4qHC6bRX+0K6Ika0+2iY5DoWTCE0X+KQaqrGj5XrlnAMdkXNORVQD WuHapxCsV/qtBdbNz2ofZQhM0wmWRGfOOOoKR6cM=
Message-Id: <6.2.5.6.2.20120614075629.07eb21f0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 14 Jun 2012 08:14:25 -0700
To: apps-discuss@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <4FD75939.6060200@dcrocker.net>
References: <CAL0qLwY1DCP9RY7cykwrPi48A_1h_FJUXo5eRWkn3Rw=rFXpBw@mail.gmail.com> <CAC4RtVBuET9h-QHEtS=genmJnJ6bfKk=KD0bTJQvZJApAsY_ww@mail.gmail.com> <4FD08CA3.6080504@dcrocker.net> <01OGEZDG0T8M000058@mauve.mrochek.com> <4FD29DF5.5010206@dcrocker.net> <CAC4RtVAbC64Bx67b6OD4LApy9p_K2xqAZYGAETHxXZE5gY0-oA@mail.gmail.com> <01OGGS87OI0Q000058@mauve.mrochek.com> <CAC4RtVBReXuj473yvkNt3nOL6AyEPkZpyjqgsd2-fF5SiFs_aQ@mail.gmail.com> <03a901cd487e$908c37c0$4001a8c0@gateway.2wire.net> <4FD75939.6060200@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: Re: [apps-discuss] Comments on draft-ietf-appsawg-received-state
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, 14 Jun 2012 15:18:21 -0000

At 07:59 12-06-2012, Dave Crocker wrote:
>  just started.  I found myself asserting that Expert Review will be 
> used as a quality control for 'goodness' rather than protection 
> against danger.  The latter is actually the claimed purpose of 
> Expert Review, not the former.
>
>This confusion is one of a number of reasons I think Expert Review 
>needs to be limited to situations in which wayward specs can do 
>systemic damage only.

I read Section 6.2 of -01.  Murray mentioned that the choice is 
between Expert Review and First Come, First Served.  The draft 
already populates the sub-registry with entries to cover various use 
cases.  FCFS would provide an easy registration path without having 
to argue about the quality of a specification.

In Section 6.2:

  "Use:  One of "current" (the state keyword is in current use),
       "deprecated" (the state keyword is in use but not recommended for
       new implementations), or "historic" (the state keyword is no
       longer in substantial current use).

The draft does not mention anything about how "deprecated" or 
"historic" are to be handed.  If the WG decides for FCFS, for 
example, how will the "Use" be handled?

As a nit I suggest updating the dates and MTA version numbers in the examples.

Regards,
-sm