Re: [Tools-discuss] [rfc-i] Recommendation 9 from Results and analysis of the survey of I-D authors on formats and tools

Carsten Bormann <cabo@tzi.org> Fri, 05 February 2021 17:02 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 B95103A0A93 for <tools-discuss@ietfa.amsl.com>; Fri, 5 Feb 2021 09:02:46 -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, SPF_HELO_NONE=0.001, 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 DLJ5rAN7DC8F for <tools-discuss@ietfa.amsl.com>; Fri, 5 Feb 2021 09:02:43 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E238C3A0A79 for <tools-discuss@ietf.org>; Fri, 5 Feb 2021 09:02:42 -0800 (PST)
Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DXMDJ5183zyZn; Fri, 5 Feb 2021 18:02:40 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <9EB5CCB0-C5E9-4F44-AA41-F237941BAC04@adobe.com>
Date: Fri, 05 Feb 2021 18:02:40 +0100
Cc: RFC Interest <rfc-interest@rfc-editor.org>, tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 634237360.124995-5abc0b7461d2bb81bcf7d246aeda6bfe
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F9EFBB7-346E-4A98-B148-01E681FBE6C2@tzi.org>
References: <161240956258.5082.18097054694330751435@ietfa.amsl.com> <CAA=duU1c3g0qmNmSN9jpfq3o4Lggxg_vT3xLdmwxAzLPm0r-iQ@mail.gmail.com> <15878309-55BA-4BE0-BD26-060308BA1270@tzi.org> <E77A02FF-4DF8-4030-BC77-4355A705E00E@adobe.com> <A2CC3D3F-3920-4E51-AAD7-1FFE83CA5ECB@tzi.org> <9EB5CCB0-C5E9-4F44-AA41-F237941BAC04@adobe.com>
To: Leonard Rosenthol <lrosenth@adobe.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/xqrDffbo3sTF_88z2ueTZu-5iYU>
Subject: Re: [Tools-discuss] [rfc-i] Recommendation 9 from Results and analysis of the survey of I-D authors on formats and tools
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: Fri, 05 Feb 2021 17:02:47 -0000

Hi Leonard,

On 2021-02-05, at 15:35, Leonard Rosenthol <lrosenth@adobe.com> wrote:
> 
> Thanks for the history, Carsten – very helpful.
>  
> So then kramdown-rfc is *both* a piece of software *and* an extension specification for Markdown.  Yes?    

Well, no.  It is a piece of software.  There is no specification, just some documentation.  (Well, that property is only different in magnitude from RFCXMLv3 at this point…)  Note that, as it is based on kramdown, there might be a need to specify that as well in some more detail than it is now.

> If so, does there exist a document that describes those extensions and their behavior?   Because, to me as a standards guy, that is the important thing.   Making sure that there is a formal specification which *anyone* can use to develop their own tooling.

The narrow waist of the RFC authoring process is RFCXMLv3, so I would hope that we build our tooling around that.  That is (supposed to be) more stable than a specific authoring tool.

> NOTE: I read the README at https://github.com/cabo/kramdown-rfc2629 (which I assume is the software we are referring to below) which seems like a great starting point for a language specification.

Indeed, but that would be work that still needs to be completed.  
(See also https://github.com/cabo/kramdown-rfc2629/wiki/Syntax .)
For some reason, there are always other I-Ds that need to be written...

Grüße, Carsten