Re: [Tools-discuss] Reference to NIST document

Carsten Bormann <cabo@tzi.org> Sat, 19 June 2021 19:54 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B3963A1E19 for <tools-discuss@ietfa.amsl.com>; Sat, 19 Jun 2021 12:54:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, 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 jvzXCD1EoWwG for <tools-discuss@ietfa.amsl.com>; Sat, 19 Jun 2021 12:54:45 -0700 (PDT)
Received: from gabriel-2.zfn.uni-bremen.de (gabriel-2.zfn.uni-bremen.de [134.102.50.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 530613A1E17 for <tools-discuss@ietf.org>; Sat, 19 Jun 2021 12:54:45 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4G6mhz2yjcz2xHd; Sat, 19 Jun 2021 21:54:43 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <11896.1624132041@localhost>
Date: Sat, 19 Jun 2021 21:54:43 +0200
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 645825283.061384-32202b849ae162f573f7bf6a329314c6
Content-Transfer-Encoding: quoted-printable
Message-Id: <91F6FBC0-A2CC-4C30-983C-06C7C415D574@tzi.org>
References: <CCFB604C-6084-43A4-AD25-97119E98601B@gmail.com> <11896.1624132041@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/eXQGJni-SkxelE3FiSuyTuqGwD4>
Subject: Re: [Tools-discuss] Reference to NIST document
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jun 2021 19:54:50 -0000

On 2021-06-19, at 21:47, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> Signed PGP part
> 
> Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
>> When I look up the list of bibxml databases in
>> https://xml2rfc.tools.ietf.org/, there’s a “Miscellaneous” section with
>> two links. One is broken, and one (bibxml2) seems to be outdated. In
>> any case it barely contains any NIST documents.
> 
> My understanding is that everything there is dusty, and will get renovated.

This year, we all hope…

> Since we mostly just *add* to these things, with rare updates/fixes, I wonder
> if this isn't something that git{hub} wouldn't be good at?  

It turns out that git is actually good at updates/fixes, too :-)

> I.e. if you find
> yourself needing something else, you should add it to a copy you keep
> locally,  and send a pull request.

Exactly.

The idea is so great Mark Nottingham has started something…
https://www.specref.org

> This solves much of the stability and airplane problem if one has it locally.
> (I've often rsync'ed it)

A git pull is so much easier than getting an rsync right!
(And git also doesn’t resend data that hasn’t changed — some rfc editor info gets new file dates for each RFC every day even without content changes, which can be very time consuming even with rsync.)

Grüße, Carsten