Re: [precis] Milestones changed for precis WG

Peter Saint-Andre <stpeter@stpeter.im> Tue, 05 April 2016 15:50 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3B0912D6D9 for <precis@ietfa.amsl.com>; Tue, 5 Apr 2016 08:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id corYh5OvXNz4 for <precis@ietfa.amsl.com>; Tue, 5 Apr 2016 08:50:45 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB8312D6D3 for <precis@ietf.org>; Tue, 5 Apr 2016 08:50:45 -0700 (PDT)
Received: from aither.local (unknown [73.34.202.214]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 2E928E8206; Tue, 5 Apr 2016 09:58:22 -0600 (MDT)
To: Barry Leiba <barryleiba@computer.org>
References: <20160301221928.17792.35793.idtracker@ietfa.amsl.com> <1C1668EA-1734-4D90-82E6-3894ECB6407C@viagenie.ca> <56D61E27.40000@stpeter.im> <56F96A20.7030509@stpeter.im> <E5D59850-BE7B-4AB9-863F-E883DA9C4E13@viagenie.ca> <B85A8CBE12087A2E41BC3D35@JcK-HP8200.jck.com> <56766496-6ABC-43C1-8A8E-BFF381E47333@viagenie.ca> <56F99A92.9090901@stpeter.im> <CAC4RtVB270GE4e_6MarL7s6Sahj=qYuDX1x09h70Gfn_qLzSCQ@mail.gmail.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <5703DED3.4080005@stpeter.im>
Date: Tue, 5 Apr 2016 09:50:43 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAC4RtVB270GE4e_6MarL7s6Sahj=qYuDX1x09h70Gfn_qLzSCQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/ql024tekLIOQ4n_EgWNxwWUs-4M>
Cc: precis@ietf.org
Subject: Re: [precis] Milestones changed for precis WG
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 15:50:47 -0000

On 4/3/16 10:00 AM, Barry Leiba wrote:
>>>>>      I'm sure that the wg is likely to be ok with wg drafts, but
>>>>>      let's do the normal process. Please submit first as
>>>>>      individual draft and we will call later for wg adoption.
>>>>
>>>>    For whatever my opinion as a participant is worth, that would be
>>>>    meaningless, time-wasting, ritual for its own sake.
>>>
>>> disagree. the step from individual to wg is the normal process and has
>>> no impact on technical work: the technical work can continue whatever
>>> the filename is. Let’s spend time on technical discussions on the
>>> content of the to-be-published draft.
>>
>> I have no preference, but to be clear the -00 versions will be exactly what
>> is in the published RFCs so that we can more easily track changes.
>
> As AD for now, still, I'll say that I do have a preference, and a
> rather strong one: these are updates to documents the working group
> has already published.  The working group has already decided to
> update them.  Please just submit them as working group documents from
> the start.  Even going through motions here makes a statement that the
> working group is not working on what it agreed to work on.

-00 versions submitted.

These are as close as I could make the documents to the published RFCs. 
By the end of the week I will publish -01 versions incorporating the 
fixes previously outlined.

Peter