Re: [precis] draft-whited-precis-test-vectors-00

"Tom Worster" <fsb@thefsb.org> Tue, 11 December 2018 19:58 UTC

Return-Path: <fsb@thefsb.org>
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 2745B130F55 for <precis@ietfa.amsl.com>; Tue, 11 Dec 2018 11:58:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 Cq2BSno89qu9 for <precis@ietfa.amsl.com>; Tue, 11 Dec 2018 11:58:31 -0800 (PST)
Received: from smtp66.iad3b.emailsrvr.com (smtp66.iad3b.emailsrvr.com [146.20.161.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 420CC130F5B for <precis@ietf.org>; Tue, 11 Dec 2018 11:58:31 -0800 (PST)
Received: from smtp1.relay.iad3b.emailsrvr.com (localhost [127.0.0.1]) by smtp1.relay.iad3b.emailsrvr.com (SMTP Server) with ESMTP id 0C44D6071E; Tue, 11 Dec 2018 14:58:30 -0500 (EST)
X-Auth-ID: fsb@thefsb.org
Received: by smtp1.relay.iad3b.emailsrvr.com (Authenticated sender: fsb-AT-thefsb.org) with ESMTPSA id C24696049A; Tue, 11 Dec 2018 14:58:29 -0500 (EST)
X-Sender-Id: fsb@thefsb.org
Received: from [10.0.1.2] (c-76-119-4-100.hsd1.ma.comcast.net [76.119.4.100]) (using TLSv1.2 with cipher AES256-GCM-SHA384) by 0.0.0.0:465 (trex/5.7.12); Tue, 11 Dec 2018 14:58:30 -0500
From: "Tom Worster" <fsb@thefsb.org>
To: "Martin J. =?utf-8?q?D=C3=BCrst?=" <duerst@it.aoyama.ac.jp>
Cc: "Sam Whited" <sam@samwhited.com>, precis@ietf.org, "Marc Blanchet" <246aberdeen@gmail.com>
Date: Tue, 11 Dec 2018 14:58:18 -0500
X-Mailer: MailMate (1.12.2r5568)
Message-ID: <2336ADE2-10FA-46DF-9ADB-25A0A1878006@thefsb.org>
In-Reply-To: <85bee3a9-091c-b6f8-7a51-45a84dee37b8@it.aoyama.ac.jp>
References: <1537293673.1189998.1512476568.041D4D88@webmail.messagingengine.com> <2A356330-3E79-40CC-8A62-25790BFE049E@gmail.com> <1544109351.3157581.1600994568.3C5C4DD0@webmail.messagingengine.com> <6760B800-B1C4-4F77-907B-2F671CA39775@thefsb.org> <1544113632.3179679.1601079352.0B318044@webmail.messagingengine.com> <85bee3a9-091c-b6f8-7a51-45a84dee37b8@it.aoyama.ac.jp>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_EB53A05A-7151-44C5-8DC8-7C2F6B9D1A87_="
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/precis/QUFOJaP-bCw9XPKSzw8lR-O3w04>
Subject: Re: [precis] draft-whited-precis-test-vectors-00
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Dec 2018 19:58:34 -0000

On 11 Dec 2018, at 3:56, Martin J. Dürst wrote:

> On 2018/12/07 01:27, Sam Whited wrote:
>> On Thu, Dec 6, 2018, at 10:12, Tom Worster wrote:
>>> First, I also think this work is valuable but I don't understand how 
>>> the
>>> ID is supposed to proceed. The point of bringing it to IETF is to 
>>> get
>>> its authority behind the statement that these specific vectors test
>>> conformance to the PRECIS RFCs. How can the IETF give this without
>>> restarting the WG to push the ID forwards as a Standards Track RFC? 
>>> I
>>> don't think the independent submission review process can.
>>
>> I don't really understand the process, but this makes sense to me and 
>> I think you're probably right. I'd be curious to hear if other IETF 
>> people who actually understand how any of this works agree or not 
>> though.
>
> Based on my past own experience, I understand some of this, but not 
> all
> of it. Besides Standards Track RFCs created by a WG, there's also the
> concept of a draft being sponsored by an Area Director for Standards
> Track. But this isn't used very much these days.

That's a possibility. It's not a lot of effort to try. Appears it's a 
matter of asking an Applications and Real-Time Area Director to sponsor 
it and advance it to IETF-wide Last Call. In the worst case the answer 
is that such a draft requires WG review.

Section 6.2 https://datatracker.ietf.org/wg/precis/about/

Tom