IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] Tools Team Report -- 28 December 2018

Bob Hinden <bob.hinden@gmail.com> Fri, 28 December 2018 21:23 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F075213117A; Fri, 28 Dec 2018 13:23:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 5NW8ycpKO-0F; Fri, 28 Dec 2018 13:23:32 -0800 (PST)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (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 BD192131173; Fri, 28 Dec 2018 13:23:31 -0800 (PST)
Received: by mail-wm1-x32d.google.com with SMTP id f188so20580193wmf.5; Fri, 28 Dec 2018 13:23:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=QLfsknlVB/+yyM5GGcVDRJHyq+w1KTuPqNT/gchFgVs=; b=ND3xE7hNNSXpBXaeYHT3tCt84SBn4jOMCZGmNwf/AZdu89ocKmC9Ecz1HEhWwxuRqg bKYLO5zan8sBXhr9lEByk1F2bvjm7B0fo5ZAjbnG2qJxA64D2JeE7Wn0rVuTFyEt1/Au JAL4t+rBSBIVsHhPQ6yaZkjesuLHMu46F/YdZDb3rcrwHvu5SZ5cD4Ct9wyvVNM6ujzd Xtp2n/pSepONS5M5tJUsxpJ4s/842zmcInMrME6R6G3irZP/eCrb5XK4K09U36IRdLFP ZoCpHpgNoEX7cSirHKGt589mKfbNkngicAMr7ec4+FMO9iiam7m9CxTebjj8nNAsbL4W Q6Fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=QLfsknlVB/+yyM5GGcVDRJHyq+w1KTuPqNT/gchFgVs=; b=QLgzvLLMS/PT/S29RU3dJwzNNW26+R6+xk5QcfAYREu+snQ7is1RjI3Sj9Q8UsQ45Z vYaYkMb3VXwjdlE1b8M/vIQG0WvX57BpoISAagfKd1n4D0dDSiy8pSKkTMjBxHDSv7tI uBWn85HbSlZgce47ZJvA64fgbTHLYAcMHiJu3QuprhrKTQRaj8JZjHvAI9Kzc+3hb4/T NS8SBd0GuTu1moDGYt8srZTyr4D39NylconWt9vH6pDRgAIMGbqQqBo9RW3dIlpljtoH fPPNDKktW8htVjCm4OaCWst+jYOd/jM6kDtOquTWwurcrsek8PbDRsnymi3DIaIX03MI LL0A==
X-Gm-Message-State: AJcUukfsYVrK3tW1UXCXvTpJDL43HQs800HpWzWr42UO7RVxA3iEZI+Z Mlc/tUBpr2U2Lb2VBgUCRWY=
X-Google-Smtp-Source: AFSGD/V2O8FgzjY4+8o0PUvRhDr4lbtbJ3WMFRSVkvvjMrmFjOyUD3kCXtfdgxpU66GNcISB7VwWEw==
X-Received: by 2002:a1c:68d7:: with SMTP id d206mr24063186wmc.43.1546032210217; Fri, 28 Dec 2018 13:23:30 -0800 (PST)
Received: from [10.0.0.50] (c-76-21-112-100.hsd1.ca.comcast.net. [76.21.112.100]) by smtp.gmail.com with ESMTPSA id k15sm54250982wru.8.2018.12.28.13.23.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Dec 2018 13:23:28 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <DC0E0F59-3A6B-4527-B917-E1398D6C8803@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2F9461C9-3C1B-4F57-9A59-E42745C6E1E8"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 28 Dec 2018 13:23:25 -0800
In-Reply-To: <DD894BB8-8DCD-4EC0-AAD6-85DC55A72F8D@vigilsec.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF Chair <chair@ietf.org>, IESG <iesg@ietf.org>, IETF Tools Development <tools-development@ietf.org>
To: Russ Housley <housley@vigilsec.com>
References: <DD894BB8-8DCD-4EC0-AAD6-85DC55A72F8D@vigilsec.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/O0lV9400KhM4_i5ak8lUjYwK3Qs>
Subject: Re: [TOOLS-DEVELOPMENT] Tools Team Report -- 28 December 2018
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: Fri, 28 Dec 2018 21:23:34 -0000

Russ,

> On Dec 28, 2018, at 10:06 AM, Russ Housley <housley@vigilsec.com> wrote:
> 
> Tools Team Report -- 28 December 2018

….

>   - More that 1100 old RFCs show no authors in the Datatracker.  This
>     situation is because Datatracker is managing workflow, not trying
>     to provide history from the beginning of time.  For RFCs prior to
>     about RFC 3000, the data is from scraping the RFC files, which are
>     in mant different formats.  Manual clean up would requires a good
>     bit of time, and there are several cases where there is no right
>     answer, such as RFC 2134 and RFC 2319.  This leads to inaccurate
>     statistics being displayed by the Datatracker.  As a result, a
>     disclaimer will be added to the statistics pages, such as
>     https://datatracker.ietf.org/stats/document/authors/?type=rfc.

If you are looking for volunteers to help with this, I am will to help.  Maybe not all 1100, but if someone tell me how to proceed I could start.

Thanks,
Bob

v2.23.0 | Report a Bug | By Email