[TOOLS-DEVELOPMENT] Form of json errata files

Robert Sparks <rjsparks@nostrum.com> Wed, 30 January 2019 18:04 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 58C52131302 for <tools-development@ietfa.amsl.com>; Wed, 30 Jan 2019 10:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ZjadW9QPXePD for <tools-development@ietfa.amsl.com>; Wed, 30 Jan 2019 10:04:09 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66D88131300 for <tools-development@ietf.org>; Wed, 30 Jan 2019 10:04:09 -0800 (PST)
Received: from unescapeable.local ([]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x0UI43UA090219 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 30 Jan 2019 12:04:04 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1548871445; bh=VNIl2wDbbUsImVaWbX7lXQglSHuNFsFZbiMbQdPmvOI=; h=To:From:Subject:Date; b=gsOA5UfGL6aS9pTOw9XFS0z6pq1V8m/JFahl+F6Fca65f8UphzqHmY4E3L8fMZ2oa GxbPmjD0eKrwcPzhJx5qyuFmFd8bb5PAZIaTKwJJK8gBvXrfwnfu+Mn2uky2SW+5uH dxo6PKLIKP2pYPSCZgSar54v0FxxQ8nu0TirJ0Sg=
X-Authentication-Warning: raven.nostrum.com: Host [] claimed to be unescapeable.local
To: IETF Tools Development <tools-development@ietf.org>, Julian Reschke <julian.reschke@gmx.de>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <4d2e9e84-97f1-e525-ddc5-97777c13d4e6@nostrum.com>
Date: Wed, 30 Jan 2019 12:04:03 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------773172BC6352D0259D8B71D6"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/Aim6m6H6v4hyZN_1gaawxcgOgg8>
Subject: [TOOLS-DEVELOPMENT] Form of json errata files
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2019 18:04:10 -0000

Hi Julian -

In a comment on the inline-errata SoW, you said

"This assumes that there's a single JSON file holding errata. I believe 
that's a bad idea, not necessarily for an offline tool, but for other 
use cases. Please provide individual JSON files per RFC."

That's a conversation to have outside the context of this SoW (so I've 
moved it to email and marked the comment in the document as "resolved"). 
The RPC is already producing the single JSON file. You can ask them to 
also produce individual JSON files per RFC, but I don't think we should 
ask that the aggregate file go away.