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

"Tom Worster" <fsb@thefsb.org> Thu, 06 December 2018 16:12 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 49998130E2E for <precis@ietfa.amsl.com>; Thu, 6 Dec 2018 08:12:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 sa9LszXdTSvW for <precis@ietfa.amsl.com>; Thu, 6 Dec 2018 08:12:52 -0800 (PST)
Received: from smtp106.ord1d.emailsrvr.com (smtp106.ord1d.emailsrvr.com [184.106.54.106]) (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 2F573130E08 for <precis@ietf.org>; Thu, 6 Dec 2018 08:12:52 -0800 (PST)
Received: from smtp22.relay.ord1d.emailsrvr.com (localhost [127.0.0.1]) by smtp22.relay.ord1d.emailsrvr.com (SMTP Server) with ESMTP id 2E588E0531; Thu, 6 Dec 2018 11:12:51 -0500 (EST)
X-Auth-ID: fsb@thefsb.org
Received: by smtp22.relay.ord1d.emailsrvr.com (Authenticated sender: fsb-AT-thefsb.org) with ESMTPSA id CC3D6E01FB; Thu, 6 Dec 2018 11:12:50 -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); Thu, 06 Dec 2018 11:12:51 -0500
From: "Tom Worster" <fsb@thefsb.org>
To: "Sam Whited" <sam@samwhited.com>
Cc: precis@ietf.org, "Marc Blanchet" <246aberdeen@gmail.com>
Date: Thu, 06 Dec 2018 11:12:49 -0500
X-Mailer: MailMate (1.12.2r5568)
Message-ID: <6760B800-B1C4-4F77-907B-2F671CA39775@thefsb.org>
In-Reply-To: <1544109351.3157581.1600994568.3C5C4DD0@webmail.messagingengine.com>
References: <1537293673.1189998.1512476568.041D4D88@webmail.messagingengine.com> <2A356330-3E79-40CC-8A62-25790BFE049E@gmail.com> <1544109351.3157581.1600994568.3C5C4DD0@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_F00AE179-C96E-42AB-890B-16534B85336C_="
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/precis/QksT1h4TK9A5t53BiNC1zjZbTkg>
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: Thu, 06 Dec 2018 16:12:57 -0000

Hi Sam,

Two points.

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.

Second, my experience is that formatting of test vectors is kinda all 
over the place in RFCs. I would not look there for guidance. Idk what 
XML format you refer to but I wouldn't want to go down any XML road as 
either producer or consumer. I suggest you devise the simplest 
machine-readable file format that you can imagine and publish it 
yourself, e.g. as a Github gist. Anyone can then easily transform that 
into any other format, for documentation, for a unit test data provider, 
or whatever. I think this serves your and our needs best even in the 
case that IETF would adopt the ID, since you can use the file to 
generate IETF-format docs.

For example, I was recently using this wonderful text file 
https://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-test.txt which is 
both documentation and machine readable. Your ID is machine readable 
(what isn't these days?) but it isn't so simple to either read or write. 
In your position I'd look at UCD files for format ideas.

Tom


-- 
Tom Worster 
skype: spinitron.tom  -  857 210 3243  - tom@spinitron.com


On 6 Dec 2018, at 10:15, Sam Whited wrote:

> On Wed, Dec 5, 2018, at 12:33, Marc Blanchet wrote:
>> haven’t seen any trafic on this, while the doc is (to me) useful.
>> Might consider sending it to the Independent Series Editor. See more
>> information here: https://www.rfc-editor.org/about/independent/
>
> Hi Marc, thanks for the followup.
>
> I've been meaning to go back and double check that there aren't any 
> duplicate vectors covering the same edge cases and prepare an update, 
> but I haven't found a good way to format the test data still so I'd be 
> hesitant to submit it (and there's practically no information about 
> how to format things or write this awful XML format). I've also tried 
> looking into the process, and the various IETF sites are inscrutable 
> and full of contradictory information, so thanks for the link, I'll 
> look into it and see if that would be an easier path, but no promises.
>
> —Sam
>
> _______________________________________________
> precis mailing list
> precis@ietf.org
> https://www.ietf.org/mailman/listinfo/precis