
From nobody Thu Feb  4 08:26:18 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 313853A168D; Thu,  4 Feb 2021 08:26:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 OMNggwu1Jcs9; Thu,  4 Feb 2021 08:26:12 -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 18EE93A1657; Thu,  4 Feb 2021 08:26:11 -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 4DWkSd3vTXzygL; Thu,  4 Feb 2021 17:26:09 +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: <15878309-55BA-4BE0-BD26-060308BA1270@tzi.org>
Date: Thu, 4 Feb 2021 17:26:09 +0100
Cc: RFC Interest <rfc-interest@rfc-editor.org>, tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 634148769.040815-fb00195119750488f05bd53ff7bffc2e
Reply-To: rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EDB03C84-290D-47C3-967C-6F273C57B6B8@tzi.org>
References: <161240956258.5082.18097054694330751435@ietfa.amsl.com> <CAA=duU1c3g0qmNmSN9jpfq3o4Lggxg_vT3xLdmwxAzLPm0r-iQ@mail.gmail.com> <15878309-55BA-4BE0-BD26-060308BA1270@tzi.org>
To: "Andrew G. Malis" <agmalis@gmail.com>, rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/EeFf7lSVYhGrIZ2JbKt5RvM4rxM>
Subject: Re: [Rfc-markdown] [Tools-discuss] [rfc-i] Recommendation 9 from Results and analysis of the survey of I-D authors on formats and tools
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2021 16:26:18 -0000

On 2021-02-04, at 16:44, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> Maybe I should put a simple CLI option for running idnits into the =
`kdrfc` tool...
> Now https://github.com/cabo/kramdown-rfc2629/issues/96

1.3.27: Add -i option to kdrfc, run idnits

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Feb  4 11:39:36 2021
Return-Path: <agmalis@gmail.com>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4B1C3A1773; Thu,  4 Feb 2021 11:39:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 Yzf_ZSpUBT2H; Thu,  4 Feb 2021 11:39:34 -0800 (PST)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 27D5F3A1771; Thu,  4 Feb 2021 11:39:33 -0800 (PST)
Received: by mail-qt1-x829.google.com with SMTP id c1so3330097qtc.1; Thu, 04 Feb 2021 11:39:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+EGXbx0Tj/rMB/YDqic+Y9eIN7UBz+GlYYmNar112cM=; b=QeCmnvKCaSwAFQqYzAsPo1xY6fNSYOhivhWeQud3pEay9Dr4YQU9pyTVk/ZykmTnt9 s5nCe8DdyPj7SesOyPHdRO0FLpa1yp6q5b+ae/nR6ZfY2C9uf6pg668L9EG6tud3v8gD LTJ2O87c2ICMl23zkp7SKKGXgNBaBycqG9Qi91K+jl08xwFas+HX5cpHe0hYuryhfbce fT4SIauRpE5xGR2BQFaK/RVAyW7qHHdBzYCKF6dWHCPH+6pG2aj4IZvsQFl5QeyUUlhs aa3H/deerlHNGk73omZWgR0e4+LDugvcADI2ThUSnaTLAZHIt08HcxbfvdJKU16yMmX2 T9Tw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+EGXbx0Tj/rMB/YDqic+Y9eIN7UBz+GlYYmNar112cM=; b=aLZFmmEhLYjlsYVXeuGUBaZLEEm+CscVBDWhGodAjTxx4CP1q4aNc1Hpq68JUQg3mf JaIk7YW/yQtiINVnQe/GFhowbBvfgp7+PakX9pZ6jldHzrm+ldJcZtHAFcbR4l9piBnR hz6zNXUslGGJv+buwBve6V3gcOXscgnLh7jfCTbpR2NOwjUflez7TYNwg1y4oEiVQqKm mwUCRjSJL6qSChmn7aTyLs5lPVh+J6l3I29kt8SZnsUZEtLplCIFoi0md77yN5y12ks2 Ie03ZbsMcVRrY3gDEKnqK3qXyNEHgcN61pL+BMkhjUZNKmRwAwHJTeVqPlAAsYk+r0aa k64Q==
X-Gm-Message-State: AOAM53134nbXzKUtHDOwxucHRD23avD+UHa2m0dSZvvPsIwJqR9ypD0v fI4m7spwW0IAvrbqVsbk/j9SWNBTfnIlo5hLmtDY9gF40xg=
X-Google-Smtp-Source: ABdhPJysfP/sFBTBBynQHsCa3cu+pwtZXiag10OzhUCOyO1u5p8FhWMaWmmKN61oIxesSN/5ldX7BLZVS/etQ4a5b0A=
X-Received: by 2002:ac8:100b:: with SMTP id z11mr1208999qti.60.1612467568491;  Thu, 04 Feb 2021 11:39:28 -0800 (PST)
MIME-Version: 1.0
References: <161240956258.5082.18097054694330751435@ietfa.amsl.com> <CAA=duU1c3g0qmNmSN9jpfq3o4Lggxg_vT3xLdmwxAzLPm0r-iQ@mail.gmail.com> <15878309-55BA-4BE0-BD26-060308BA1270@tzi.org> <EDB03C84-290D-47C3-967C-6F273C57B6B8@tzi.org>
In-Reply-To: <EDB03C84-290D-47C3-967C-6F273C57B6B8@tzi.org>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 4 Feb 2021 14:39:12 -0500
Message-ID: <CAA=duU1kuYRXR96WzACcOVegn73j=vziOz-X5mGCQaZ8oeJTEg@mail.gmail.com>
To: RFC Markdown <rfc-markdown@ietf.org>
Cc: RFC Interest <rfc-interest@rfc-editor.org>, tools-discuss <tools-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a1c14205ba87dc41"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/fGrp5wRwz4B0A-By30RB2CEanAM>
Subject: Re: [Rfc-markdown] [Tools-discuss] [rfc-i] Recommendation 9 from Results and analysis of the survey of I-D authors on formats and tools
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2021 19:39:36 -0000

--000000000000a1c14205ba87dc41
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Carsten,

Awesome, thanks!

Cheers,
Andy


On Thu, Feb 4, 2021 at 11:26 AM Carsten Bormann <cabo@tzi.org> wrote:

> On 2021-02-04, at 16:44, Carsten Bormann <cabo@tzi.org> wrote:
> >
> > Maybe I should put a simple CLI option for running idnits into the
> `kdrfc` tool...
> > Now https://github.com/cabo/kramdown-rfc2629/issues/96
>
> 1.3.27: Add -i option to kdrfc, run idnits
>
> Gr=C3=BC=C3=9Fe, Carsten
>
>

--000000000000a1c14205ba87dc41
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Carsten,<div><br></div><div>Awesome, thanks!</div><div><br=
></div><div>Cheers,</div><div>Andy</div><div><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Feb 4, 2021 =
at 11:26 AM Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org">cabo@tzi.or=
g</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>On 2021-02-04, at 16:44, Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.or=
g" target=3D"_blank">cabo@tzi.org</a>&gt; wrote:<br>
&gt; <br>
&gt; Maybe I should put a simple CLI option for running idnits into the `kd=
rfc` tool...<br>
&gt; Now <a href=3D"https://github.com/cabo/kramdown-rfc2629/issues/96" rel=
=3D"noreferrer" target=3D"_blank">https://github.com/cabo/kramdown-rfc2629/=
issues/96</a><br>
<br>
1.3.27: Add -i option to kdrfc, run idnits<br>
<br>
Gr=C3=BC=C3=9Fe, Carsten<br>
<br>
</blockquote></div>

--000000000000a1c14205ba87dc41--


From nobody Fri Feb 12 08:49:50 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BAC3A17AE; Fri, 12 Feb 2021 08:49:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 6jCYK20qKSCI; Fri, 12 Feb 2021 08:49:44 -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 512C73A17A7; Fri, 12 Feb 2021 08:49:43 -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 4Dcfc52wL6zyhc; Fri, 12 Feb 2021 17:49:41 +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>
Date: Fri, 12 Feb 2021 17:49:40 +0100
Cc: tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 634841380.868253-fcdf41356b42baf7c61785694eded207
Content-Transfer-Encoding: quoted-printable
Message-Id: <E231E85C-1129-4855-920E-6BE92E9FEEC9@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/ULcRqY4odJP3lBHeXJdnmXsbqhc>
Subject: [Rfc-markdown] 1.3.29: Do not use server-side anchor setup for stand_alone: true
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2021 16:49:48 -0000

This is an emergency workaround for the tools server problem discussed =
in
=
<https://mailarchive.ietf.org/arch/msg/tools-discuss/VqTXuUNnpQJE5rB5_JfU7=
1rMMoo>

Please use `stand_alone: true` in the YAML header to benefit from this =
(*).

A few minor fixes (and a new feature) were also done recently that I =
hadn=E2=80=99t announced:

1.3.28: SVG error handling fixes
1.3.27: Add -i option to kdrfc, run idnits
1.3.26: Avoid dependency for module that needs native build
1.3.25: Work around ERB api deprecation

Gr=C3=BC=C3=9Fe, Carsten

(*) actually, preferably always use stand_alone: true, unless you have a =
broken proxy setup that makes it difficult for you to access the bibxml =
servers.


From nobody Fri Feb 12 15:55:18 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 645D43A10F2 for <rfc-markdown@ietfa.amsl.com>; Fri, 12 Feb 2021 15:55:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 dvouqj16oXur for <rfc-markdown@ietfa.amsl.com>; Fri, 12 Feb 2021 15:55:13 -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 EF98D3A10EC for <rfc-markdown@ietf.org>; Fri, 12 Feb 2021 15:55:12 -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 4Dcr332LnkzyX7; Sat, 13 Feb 2021 00:55:11 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 634866910.800939-c3f8f8a5153d9a9c4f54a71fa4115bb4
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Sat, 13 Feb 2021 00:55:10 +0100
Message-Id: <CF4A1FAB-D9A8-42A8-9729-B6E451EF140F@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/obCjU0W0aGKcFn5G4pPnWHDxGYA>
Subject: [Rfc-markdown] 1.3.30: Use rfc-editor/datatracker for RFC/I-D bibxml fetching
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2021 23:55:16 -0000

1.3.30: Use rfc-editor/datatracker for RFC/I-D bibxml fetching.
(This patch only has an effect on stand_alone: true documents.)

The previous behavior can be reinstated by setting the environment =
variable KRAMDOWN_USE_TOOLS_SERVER to any value.

This emergency patch became necessary as xml2rfc.tools.ietf.org is =
currently serving outdated data, as well as missing updates, in some =
cases for more than a week. =20

Unless people see problems with this change, this patch is likely to =
stay, as the update rates of the =E2=80=9Cofficial=E2=80=9D sources are =
much closer to real-time, and this may count a lot in the final hours of =
the I-D deadline frenzy, which we all cherish.

(If you want to see some of the outdated data, have a look at =
https://www.ietf.org/archive/id/draft-bormann-cbor-notable-tags-03.html =
from today, which for instance references =
http://www.ietf.org/internet-drafts/draft-ietf-cose-rfc8152bis-struct-14.t=
xt, which is 404.  More details at the thread starting at =
https://mailarchive.ietf.org/arch/msg/tools-discuss/AxvlPNoeGRTq92J_fIn4iC=
RN-mI/ .)

Note that this does not replace xml2rfc.tools.ietf.org as bibxml sources =
for other types of documents.  With the patch in 1.3.29, that part seems =
to be limping along fine, however.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Sat Feb 13 12:49:10 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4167D3A0CD8 for <rfc-markdown@ietfa.amsl.com>; Sat, 13 Feb 2021 12:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 V3QH_GzpM6-t for <rfc-markdown@ietfa.amsl.com>; Sat, 13 Feb 2021 12:49:06 -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 8D4AC3A0CD2 for <rfc-markdown@ietf.org>; Sat, 13 Feb 2021 12:49:06 -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 4DdMss1WNdzyY3; Sat, 13 Feb 2021 21:49:05 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 634942144.5118181-caf88522850b2393bdaeae4075cbfa68
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Sat, 13 Feb 2021 21:49:04 +0100
Message-Id: <98999515-87BE-4781-B163-9F2457A201A2@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/Iy-JjSzjb0S_-F8ajOUPrF9kEWE>
Subject: [Rfc-markdown] 1.3.31: Add temporary workaround for draft referencing regression
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Feb 2021 20:49:09 -0000

1.3.31: Add temporary workaround for draft referencing regression

See =
<https://mailarchive.ietf.org/arch/msg/tools-discuss/Ypgqtv6DvzhyBAxavVHWr=
Jz4IyA>

This may be reverted later, but is necessary now with the I-D deadline =
approaching quickly.  I *think* we are now good to go for that despite =
the tools server glitches, please send feedback if we aren=E2=80=99t.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Feb 17 15:31:22 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 779C03A1E62 for <rfc-markdown@ietfa.amsl.com>; Wed, 17 Feb 2021 15:31:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 Q9spp7zQ203k for <rfc-markdown@ietfa.amsl.com>; Wed, 17 Feb 2021 15:31:12 -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 2D16C3A1E3A for <rfc-markdown@ietf.org>; Wed, 17 Feb 2021 15:31:11 -0800 (PST)
Received: from [192.168.217.152] (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 4DgvH14jDXzySW; Thu, 18 Feb 2021 00:31:09 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Thu, 18 Feb 2021 00:31:09 +0100
Message-Id: <6C5F7F04-CB5D-48D9-AB80-737BA1CED989@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/8FKkKIMWSsUyy3s89wi3lMvgbUI>
Subject: [Rfc-markdown] 1.3.33: KRAMDOWN_NO_TARGETS: let xml2rfc fill in targets for RFC and I-D
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2021 23:31:20 -0000

As an alternative approach to the recent RFC/I-D bibxml emergency =
patches, kramdown-rfc now honours the environment variable =
KRAMDOWN_NO_TARGETS by removing target information from all RFC and I-D =
references; xml2rfc will then fill them in again (with a number of =
command line flags that can influence that).  If you don=E2=80=99t set =
the environment variable, you get the previously announced workarounds.  =
Thanks to Martin Thomson for the suggestions and all the help in recent =
updates.

Due to some refactoring, this is a slightly more risky change than I=E2=80=
=99d normally make 120 hours before I-D deadline.
Please don=E2=80=99t hesitate to contact me if there is any surprising =
behaviour.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Feb 18 09:27:09 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB1F53A14B0 for <rfc-markdown@ietfa.amsl.com>; Thu, 18 Feb 2021 09:27:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 W8b64jwnz5-Z for <rfc-markdown@ietfa.amsl.com>; Thu, 18 Feb 2021 09:27:05 -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 D786E3A14AD for <rfc-markdown@ietf.org>; Thu, 18 Feb 2021 09:27:04 -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 4DhM8Q1gQtz1060; Thu, 18 Feb 2021 18:27:02 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 635362021.591537-b2eeaeb2e0743b5cd0123247bb1abec3
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 18 Feb 2021 18:27:01 +0100
Message-Id: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/CQ67vpdwEbjWQjQasIJdvFzbS1M>
Subject: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2021 17:27:09 -0000

RFCXMLv3 introduces a second element for verbatim text beyond
<artwork>, the <sourcecode> element.
So kramdown-rfc needs to decide whether a codeblock turns into
<sourcecode> or into <artwork>.

1.3.34 now maps all code blocks with a language given to sourcecode,
except if the language is one of (ascii-art binary-art call-flow
hex-dump svg).
(This exception list was appropriated from RFC 7991; the current
xml2rfc documentation doesn't mention call-flow or hex-dump.)

So

~~~
/\
\/
~~~

still turns into <artwork>, while

~~~ c
int dezigzag(unsigned int i) {return (i>>1) ^ -(i&1)}
~~~

turns into <sourcecode> (with type=3D"c").

Using the "gi" pseudo-attribute, this automatic choice can be
overridden (use gi=3D"artwork" or gi=3D"sourcecode" in an inline =
attribute
list).

Note that for both artwork and sourcecode, additional attributes need
to be notated as "artwork-foo" (or "sourcecode-foo") in an inline
attribute list, as the codeblock itself turns into a
<figure> around the artwork/sourcecode, so you can have title etc.

An example with an inline attribute list (IAL):

~~~ c
main() { return 1; }
~~~
{: #my-little-c-program artwork-name=3D"myli.c" title=3D"My little C =
program"}

or, to keep the actual source outside the markdown

~~~ c
{::include myli.c}
~~~
{: #my-little-c-program artwork-name=3D"myli.c" title=3D"My little C =
program"}

(kdrfc -c will generate a .v2v3.xml that includes the text, so it can
be directly submitted to the datatracker.)

Note that the conventional type strings listed in [0] are all
lower-case; I'm sorry if this violates your sense of aesthetics as
much as mine :-)

Over at the github issue [77], which this release resolves, we also
discussed using media-type-names (or content-types [1]) as types --
this strikes me as a great convention.

Gr=C3=BC=C3=9Fe, Carsten

[0]: https://www.rfc-editor.org/materials/sourcecode-types.txt
[77]: https://github.com/cabo/kramdown-rfc2629/issues/77
[1]: =
https://www.ietf.org/archive/id/draft-bormann-core-media-content-type-form=
at-02.html



From nobody Thu Feb 18 12:48:55 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB373A1836 for <rfc-markdown@ietfa.amsl.com>; Thu, 18 Feb 2021 12:48:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 qZaXs0aMqa2k for <rfc-markdown@ietfa.amsl.com>; Thu, 18 Feb 2021 12:48:51 -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 023F43A184A for <rfc-markdown@ietf.org>; Thu, 18 Feb 2021 12:48:50 -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 4DhRdD2GBWzydD; Thu, 18 Feb 2021 21:48:48 +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: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org>
Date: Thu, 18 Feb 2021 21:48:47 +0100
X-Mao-Original-Outgoing-Id: 635374127.663709-3124b8a1abcbfc968107083fe444bad0
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9733C7C-F4EF-4FAD-A9C8-C4CD7DA87660@tzi.org>
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/JtuXARpMGAX8FctdRNb_EAXL2Po>
Subject: [Rfc-markdown] 1.3.35: revert to <artwork> if "artwork-align" is set
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2021 20:48:54 -0000

Bizarrely, RFCXMLv3 does not allow an =E2=80=9Calign=E2=80=9D attribute =
on <sourcecode>, while it does on <artwork>.  This, together with the =
automatic assignment of <sourcecode> to appropriately classed code =
blocks added in 1.3.34, creates a backwards compatibility problem. =20

This is now worked around by reverting to <artwork> for any code blocks =
that do have =E2=80=9Cartwork-align=E2=80=9D/=E2=80=9Csourcecode-align=E2=80=
=9D inline attributes, regardless of type.
So if you want your source code to turn up as <sourcecode>, do not =
center/right-adjust any more.

We apologize for the inconvenience.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Feb 18 23:24:12 2021
Return-Path: <miek@miek.nl>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 152A93A1176 for <rfc-markdown@ietfa.amsl.com>; Thu, 18 Feb 2021 23:24:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=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=miek-nl.20150623.gappssmtp.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 htTo4oNeA4Dt for <rfc-markdown@ietfa.amsl.com>; Thu, 18 Feb 2021 23:24:07 -0800 (PST)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 6E1C63A1152 for <rfc-markdown@ietf.org>; Thu, 18 Feb 2021 23:24:06 -0800 (PST)
Received: by mail-ej1-x629.google.com with SMTP id w1so10512508ejf.11 for <rfc-markdown@ietf.org>; Thu, 18 Feb 2021 23:24:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miek-nl.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=hZrZOIScF/tJBnQUiGDRyT/Dq+zVaS1F2d0kkPGQoJk=; b=cAoS05Omuuh/qHIuT7HRMfHzEpHlX2QdpEcE/npmH+8PbOeSAAzhM+7MVdFVqWdGBj xYIXBd2MsgIUyg52+KHH0AIj4lVnq26w/r+TXJSzvu2hB/a/y/puuzQ9aERJ9P4g22Ga xuY/KLnopiZGUl1hOGs1YQd7iMwfivpPRBa/e85R06oz90L7f7j8V6BSKLkXJYSP4QVe ig1WOn0J8mtWSKUhG+E/3J9aXur7QTioXIdnaR/W3sJd01n5zrwF4jC/ahGV03v9cp6a xokqCKp7j+E24VglzOvirTdvtFr7cSA1a7VcA9cnRvSqQ+Wf9OJle/Yo5XHK9FuDRjgt Ynxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=hZrZOIScF/tJBnQUiGDRyT/Dq+zVaS1F2d0kkPGQoJk=; b=mAvYaxEDcckwQ9G1EYAGhF6d6DrgIWLA/RdvO9WmTNmSdVRhPzxrge/MFNHVaLI++t cekdD5xHslaSDMSfaRapTwO9F7ZF2Yizs8NtbK4Xuz8LVKR/4yDF4i2S/qLBVXIVMyuz PWFiGPogYbnCaxmgx23R66+Igast1GcBj2EVbbAuu629yTRnUgkwnqTz+2srv+6TS80z bVouw57+qohRk5QsMkAog86FbpBCYcssn3mVy/yfiCpi56n3fUP8/OMSg8uCACspvJyL wBLHkQFMv9CTGrU+o/XzUbnxRDD+TMtBDd8TvTTdVTLqym+8bXYDZ2QPf7PNnm9V+dwO mpGg==
X-Gm-Message-State: AOAM532NBMcnZAtqlwm9eo0kAg19GaD2F3mvnwKynnteHv7UDdrZZFAN MlkMmr6x+Qo15h5nL77CSW2HwV2R38D5E/er
X-Google-Smtp-Source: ABdhPJwMjrGbT+sOCy9o/+V7Q9+eHW62D82vnznUydnjmiX1SfVRwwypyUFrmEps1exB+22Nxy/NLQ==
X-Received: by 2002:a17:906:5d0b:: with SMTP id g11mr7489506ejt.542.1613719445061;  Thu, 18 Feb 2021 23:24:05 -0800 (PST)
Received: from miek.nl (dhcp-077-251-206-012.chello.nl. [77.251.206.12]) by smtp.gmail.com with ESMTPSA id b6sm3783276ejb.8.2021.02.18.23.24.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Feb 2021 23:24:04 -0800 (PST)
Date: Fri, 19 Feb 2021 08:24:02 +0100
From: Miek Gieben <miek@miek.nl>
To: Carsten Bormann <cabo@tzi.org>
Cc: rfc-markdown@ietf.org
Message-ID: <20210219072402.GA151175@miek.nl>
Mail-Followup-To: Carsten Bormann <cabo@tzi.org>, rfc-markdown@ietf.org
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/s6NdV1agXPfC1QFwDCBq_duBnAc>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2021 07:24:10 -0000

[ Quoting <cabo@tzi.org> in "[Rfc-markdown] 1.3.34: map most cod..." ]
>So
>
>~~~
>/\
>\/
>~~~
>
>still turns into <artwork>, while
>
>~~~ c
>int dezigzag(unsigned int i) {return (i>>1) ^ -(i&1)}
>~~~
>
>turns into <sourcecode> (with type="c").

Note that mmark does exactly the same.

Regarding your other email on the alignment of artwork vs sourcecode, I think that must
be fixed in the schema, rather than working around it from our side.


From nobody Thu Feb 18 23:33:28 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 370C13A1193 for <rfc-markdown@ietfa.amsl.com>; Thu, 18 Feb 2021 23:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 uNvqDOIFVeIc for <rfc-markdown@ietfa.amsl.com>; Thu, 18 Feb 2021 23:33:24 -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 BD6BC3A118F for <rfc-markdown@ietf.org>; Thu, 18 Feb 2021 23:33:24 -0800 (PST)
Received: from [192.168.217.152] (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 4Dhjwy3ChpzyNK; Fri, 19 Feb 2021 08:33:22 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20210219072402.GA151175@miek.nl>
Date: Fri, 19 Feb 2021 08:33:21 +0100
Cc: rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <08FE1EB3-5D3F-41CF-B623-F664DB3746A7@tzi.org>
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org> <20210219072402.GA151175@miek.nl>
To: Miek Gieben <miek@miek.nl>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/zW4IkcfNzGL2HC03FDSv5luth9U>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2021 07:33:27 -0000

On 19. Feb 2021, at 08:24, Miek Gieben <miek@miek.nl> wrote:
>=20
> Regarding your other email on the alignment of artwork vs sourcecode, =
I think that must
> be fixed in the schema, rather than working around it from our side.

Yes.  The question really is on what timescales this can happen.
We have been waiting for some fixes for some time.
RFCEDP is still discussing on one end.
Somebody has to do the xml2rfc fixes on the other side.
Let=E2=80=99s see...

Gr=C3=BC=C3=9Fe, Carsten


From nobody Fri Feb 19 00:06:36 2021
Return-Path: <julian.reschke@gmx.de>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E14C3A11E0 for <rfc-markdown@ietfa.amsl.com>; Fri, 19 Feb 2021 00:06:34 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 JVlSAKDxaTka for <rfc-markdown@ietfa.amsl.com>; Fri, 19 Feb 2021 00:06:33 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 764A13A11D0 for <rfc-markdown@ietf.org>; Fri, 19 Feb 2021 00:06:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1613721988; bh=TZPscIQjReyUmBjxVIzFXS5zVJvD8I2gUHZ8uIAleDA=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=PYzxvM/Xdt3P8z93axyjVnaYF6DMV2tbqQ159qM169m1dIh6/e4BtMMmEM6T5scbb vcoLyYxQYljne9kcug2SAShn/LPHXR+p7+SPsk9Tz7p9/QQ66dXfSfASva9+gG8Gfu ToXvyp6FxQltr2V9C/HXOaxbSjO1iA2/Y2/9VIjY=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([84.171.158.62]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MiaY9-1looGi3HE7-00fkCR for <rfc-markdown@ietf.org>; Fri, 19 Feb 2021 09:06:27 +0100
To: rfc-markdown@ietf.org
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org> <20210219072402.GA151175@miek.nl>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <77684aa0-dcdb-fc38-8d31-86f2f5ae2ede@gmx.de>
Date: Fri, 19 Feb 2021 09:06:24 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <20210219072402.GA151175@miek.nl>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:fOQpNewRlU87/+waP8gAFUG/KEmZi/aK/WlyQmxCSEByHwYiQIX y3DlKM3xwBnU21Q9KFZ6XzByEULFO5gWgsruo9vJcYCXegTZBkxUbc4kx4/pMwzjC4/e80D Xuj9LTUp+bMWEts0H1T2eCLw4vuYCQWtzWkttEwJy397yAeXpYm+ytqFuMSxdN/hS+IQecA 6JrppVYTxeML1P1CPTGaw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:p4KY8ekkH58=:m2/OfgVKW/sVwgB9pejaii Mzl1JTa3trKXh47a5WFrGMxKFXgbuWpvfnRmIXo5sWsksWfM59yBPEucTM8A9Ot8fpPYMikgH kB3Uv28aeUww6f4LaGwpDe+PilAd2cuuq+Zz85k8GHhEMJLD/30Fl2/ZbG9iFI0KxQxpOUs+e Ym3foaDRq2NWgRqfM8zQdIbGZZMmWRxKK0yMRKnHkKF6XKAf+hmbmNa64hKv749QLgkHMPN2F eGNP3oHLfpYv4nWKwMDc32vG3ad/9up6h/E1qTyAQlk+tHxwMuxgoCoHzSYNCbrJo8GaFqzx3 cbpTVlsuJxLXYATYwb6OX+xl7zrusk5BwlEqpbNQwHTBZ6xWR8S0rxzDmUK4dn/lIrZXB+7qi Zz2pxy6cHXAhXCzj+bks9yzHjAXuqSpfwRbmybDT01OKkWU93FnNeoliMCKOl18lFqq+0x/iZ Y1geXoMojWhmEbQ7aGKX5klMJzEQGMQe+BWd7QuPaRI8XdVtpSgrt2lRHMH6xCv3qPkplrzvp Pxn6piTrt0vMv9Jf1cyJFA1EeVZEjHqmD3lYWHXLDtMuf4tRgrq+doPkw5awGID0/UWcRd1hy n08b+V7f2EaBbt34RhdY7BNwhIgrEmCGBpJ+3YxgLTpz8SROB442JjshIaUraHppZ3JEoLrc5 TwN0qmz96q6gIxdnciEbDmr/W/mzfxU3KaQbrWNf1i7tUob55sfWd5JMdyUejvCgALX5JkW4o uIAIRBCOg51CXGiJtkbjsAy3O7238QrisBVsPhek5lEd4XktROVHADaDjB1Nd9kABJSKSSlon vEdG1340Em+UbbTTdvMDcnh7sVdN8ilQ7WbenEC5DkuG1JW+TgwxXSgqDhR/qJdaKLIAlBEfd Y7mWZC/CjTxR5EHp21xw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/OTuEg2VrCZXF16q1t9BKV2Zq3cE>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2021 08:06:34 -0000

Am 19.02.2021 um 08:24 schrieb Miek Gieben:
> [ Quoting <cabo@tzi.org> in "[Rfc-markdown] 1.3.34: map most cod..." ]
>> So
>>
>> ~~~
>> /\
>> \/
>> ~~~
>>
>> still turns into <artwork>, while
>>
>> ~~~ c
>> int dezigzag(unsigned int i) {return (i>>1) ^ -(i&1)}
>> ~~~
>>
>> turns into <sourcecode> (with type=3D"c").
>
> Note that mmark does exactly the same.
>
> Regarding your other email on the alignment of artwork vs sourcecode, I
> think that must
> be fixed in the schema, rather than working around it from our side.
> ...

FWIW, I'm not sure what the use case for not left-aligning source code is?

Slightly related to this: it seems we need to come up with
recommendations about what is artwork and what is sourcecode. For
instance, in the HTTP specs, is a HTTP message example (or a header
field example) artwork or sourcecode?

Best regards, Julian


From nobody Fri Feb 19 00:46:08 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E84233A0D4E for <rfc-markdown@ietfa.amsl.com>; Fri, 19 Feb 2021 00:46:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 wNy9MT4dRKPu for <rfc-markdown@ietfa.amsl.com>; Fri, 19 Feb 2021 00:46:02 -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 13BF83A0D39 for <rfc-markdown@ietf.org>; Fri, 19 Feb 2021 00:46:01 -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 4DhlXm1m9fzyRB; Fri, 19 Feb 2021 09:46:00 +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: <77684aa0-dcdb-fc38-8d31-86f2f5ae2ede@gmx.de>
Date: Fri, 19 Feb 2021 09:45:59 +0100
Cc: rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 635417159.340462-e110aa66ee1b1dc926279df6f341d670
Content-Transfer-Encoding: quoted-printable
Message-Id: <22FFC094-63C4-43E8-8FDA-28832DD7FF28@tzi.org>
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org> <20210219072402.GA151175@miek.nl> <77684aa0-dcdb-fc38-8d31-86f2f5ae2ede@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/-TMLuKxSopzSbB3z90ipkPE4AKU>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2021 08:46:06 -0000

>=20
> FWIW, I'm not sure what the use case for not left-aligning source code =
is?

I had one just yesterday=E2=80=A6

=
https://datatracker.ietf.org/doc/draft-bormann-core-media-content-type-for=
mat/

(In a normal publication I=E2=80=99d use color.)

> Slightly related to this: it seems we need to come up with
> recommendations about what is artwork and what is sourcecode. For
> instance, in the HTTP specs, is a HTTP message example (or a header
> field example) artwork or sourcecode?

I=E2=80=99d say:
Q: Is it meant for machine consumption?
No?  Artwork.

Examples:

PEM, CBOR-diag, JSON data items that can be parsed: source code.
ABNF, CDDL, YANG: source code (but see example above)
Pseudocode, C, Python: source code

Math: artwork
Illustrative excerpts of code for human consumption: artwork
Call-flows (example in RFC 7991), HTTP interactions: artwork
UML stuff, MSCs, flow charts, GANTT charts: artwork

(Deliberately) Bad code (counterexamples): Hmm.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Fri Feb 19 00:48:03 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 949593A1280 for <rfc-markdown@ietfa.amsl.com>; Fri, 19 Feb 2021 00:48:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 21EWedC8BICP for <rfc-markdown@ietfa.amsl.com>; Fri, 19 Feb 2021 00:47:59 -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 0081B3A11CC for <rfc-markdown@ietf.org>; Fri, 19 Feb 2021 00:47:58 -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 4Dhlb14q1dzyRB; Fri, 19 Feb 2021 09:47:57 +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: <22FFC094-63C4-43E8-8FDA-28832DD7FF28@tzi.org>
Date: Fri, 19 Feb 2021 09:47:57 +0100
Cc: rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 635417277.239099-57e524bcbedfcd8850f614d24161ac79
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8D57CFC-EB4A-4F7E-8614-99F39719183A@tzi.org>
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org> <20210219072402.GA151175@miek.nl> <77684aa0-dcdb-fc38-8d31-86f2f5ae2ede@gmx.de> <22FFC094-63C4-43E8-8FDA-28832DD7FF28@tzi.org>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/hkfYoqZYDDlpr8AAmF4LTArSOJY>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2021 08:48:03 -0000

On 2021-02-19, at 09:45, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> =
https://datatracker.ietf.org/doc/draft-bormann-core-media-content-type-for=
mat/

Sorry, my intent here is probably better visible in the current =
editor=E2=80=99s version:

=
https://cabo.github.io/mtct/draft-bormann-core-media-content-type-format.h=
tml

Gr=C3=BC=C3=9Fe, Carsten


From nobody Fri Feb 19 00:53:59 2021
Return-Path: <julian.reschke@gmx.de>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE5F3A120B for <rfc-markdown@ietfa.amsl.com>; Fri, 19 Feb 2021 00:53:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 Bwtc-Qv707v9 for <rfc-markdown@ietfa.amsl.com>; Fri, 19 Feb 2021 00:53:55 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 D960A3A1274 for <rfc-markdown@ietf.org>; Fri, 19 Feb 2021 00:53:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1613724828; bh=BxBm5hrWTVagG2q6R2qTTsYv8AAv28pSiGGoEjiq5VE=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=HYO2sCvSIYMS4UuwPy/ZNdxmDkH2TK8GLEyKK9DunRf8Zy8PHpk/+ARArAaXz3Htg EAXrtMJgAYBX4B1fmiRdvqky3YXhIi08k1WrHiHrnJggoOAg+0ltC4vGwW6i0U8PQM ff3dseJhPGB2aNm1ITeDz7hM7VpWPEMUbYqm75eM=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.182] ([84.171.158.62]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M4JmT-1lCkYv0QEr-000KWk for <rfc-markdown@ietf.org>; Fri, 19 Feb 2021 09:53:48 +0100
To: rfc-markdown@ietf.org
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org> <20210219072402.GA151175@miek.nl> <77684aa0-dcdb-fc38-8d31-86f2f5ae2ede@gmx.de>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <549e34a3-d286-6b76-0a63-a341610aea60@gmx.de>
Date: Fri, 19 Feb 2021 09:53:45 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <77684aa0-dcdb-fc38-8d31-86f2f5ae2ede@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K1:RqxvDNdQHUy9ClF+tUbxwHGP6klWlfwe8ETpWur7s6duYLgL09d 4dbELXzYH1wbdFyhQM373PSbAGPHNQvAtxRGufi4bua4uqAglKsB56bEJanUUgpzut1SrDn 2K4iZ16y7dp/vyyfUMvKRRofOBa0048dj1B20eiTtU4R+fx0G2rQjj8qvbnMNJVTJiHXMKP A2tcrT3M2mSIKyyrg2eEw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:ex9QybS9PlE=:j/u9W+qawzlltQ1Y6aq3It lXT5nEgha4tc9mcq6BtSvH2hPu1om10lYR3zDFPodBzHg1fPBf8YeUIUamvcZAnVrQ+7/TA/3 ANMI2JZFlAZxpi4CD7GPtBxM8Kk9MlYWdPtCqrX1MF3BLdd8GFgv2By3DxoOoIOsifeSFRqc6 OB81Pm9tg7Vm3lIZ+R9RBfWeDg+t71pLyU7nxxJbaigDZgt1ZWjzdwpLDGq4Tz4twdHgfVH19 PnVn3yQVPPhSyqZEBq1KcBRPrqIiyZUq15sxb/tjf4JcpahGdtKdBB1BmopIXpIvP/1Pcmb8L ITDEJgALVrGcavxQBvpUV7kv5aY5z7ZdVn/htHtQCZ7a6i8GyYQk7o0gBQCvzNXXwNeIv4PFT 6+sht66sMc0VTSAMaw11OzJD+PaLIkBi6vd67dc9tkKaVRQWLP+lJeAFAvVR9EyPrAH8mjT8p j9YxdkH3WwA6+ekYLfNm2l0l2BnM620z35k25Y3mI1Aq2E+YXGc3AKEvBQ3fMQoGkI7IRzu5e Y20whzvhSFQYC4zzG2vmr2zN6ND4qURL40ufLr9K3KRy1c9SbVkU9i66SrTdg+X9oBKJrprkI i79dQ59zy3IlHzQ40MQikb24YJngLwxO6oCW0aEQfNuVkpbvbtzfenEGIfEHGCZL9GcWthu4v n5h87pbcr+gvR5tukxA4ufgoYHz2jkbbUWWcfFWNNFOaT/3USSVJkZQbOTd9U+mNmS30lRfUz QhV/lCTMmFP9pLr0POHi7TQH6TPDdWdqyPMB/7n5Zl8QvGjZ3lqz8yXjVaBKo5fVB5aodqcN4 2SSr1tyfDNlAq65ObkGcwWtLW7TSe9P5YgKTle2xvKyPHP2XTGYcXFMjWeAAVSAp8MBMMXcJf qGnuLOCuueaoS4lNU78Q==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/F4hPg-j5nyl_JYPq9pmv8V9ZYts>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2021 08:53:58 -0000

Am 19.02.2021 um 09:06 schrieb Julian Reschke:
> ...
> Slightly related to this: it seems we need to come up with
> recommendations about what is artwork and what is sourcecode. For
> instance, in the HTTP specs, is a HTTP message example (or a header
> field example) artwork or sourcecode?
> ...

-> <https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/195>

Best regards, Julian


From nobody Fri Feb 19 01:03:25 2021
Return-Path: <julian.reschke@gmx.de>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 859013A129D for <rfc-markdown@ietfa.amsl.com>; Fri, 19 Feb 2021 01:03:24 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 ojWS5PuwN0KB for <rfc-markdown@ietfa.amsl.com>; Fri, 19 Feb 2021 01:03:22 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 080883A129E for <rfc-markdown@ietf.org>; Fri, 19 Feb 2021 01:03:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1613725390; bh=yZmoVAS5ivmPT2rmiSQfBk/5cZasViQV7mxSLJZjpuA=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=i+DWpqN1vdlq6Kld+BWffWiqjYAb5IDxLxhT84yZvY9WUoxmFWsN/01q1VEIxwh7U +Y141V+TKxvvr7MWHnJVVhXy82UIdyj525jQqhIa68Un0Xwvsz8SkYl5qRGwQ5uk0i iMXOV9Nxp4ym3CrpB1d6C1vZ+NsDWHua4hEnswT4=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.182] ([84.171.158.62]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MbzuB-1liDq63kSd-00dWJN; Fri, 19 Feb 2021 10:03:09 +0100
To: Carsten Bormann <cabo@tzi.org>
Cc: rfc-markdown@ietf.org
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org> <20210219072402.GA151175@miek.nl> <77684aa0-dcdb-fc38-8d31-86f2f5ae2ede@gmx.de> <22FFC094-63C4-43E8-8FDA-28832DD7FF28@tzi.org> <B8D57CFC-EB4A-4F7E-8614-99F39719183A@tzi.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <bfa621cc-c5fb-581e-3b55-c13615c8c03f@gmx.de>
Date: Fri, 19 Feb 2021 10:03:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <B8D57CFC-EB4A-4F7E-8614-99F39719183A@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:D/ZsslielqJkVXOMqa2s7LJbUJ4r/DZPwH4eY36z8CjBwyGS5qq xc6rZRhRDEUXWaV3EaW5YB8gTJ2xuXlRjIq/1B0buGfXBpjnkoGDzYSqr0+sBlHJoOiHMwL M/I8/T0WdwpeX+750AWJgEowwZ8eS2VvxDSqgexauLbGmZUy2arXNk7jPvlRvdUqomtcd8o GsHEVCrKotAH5HggT8yvA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:pZgI4m4+xqM=:fYfi8bJJUJP/azTBaZxrBK 1pfbF+Vjp1bSF8Uyc5tZGZ2YUpMMiSrdp+gksgmEB9fMJ63/KOCv4o/E/W8mUlVlOEDzxGXIP rCQLWhSAyR/YMtSKP4/xy8pc/NTHrZUf+NFsqlABajgcbZousntPkPIpDmqiQSPkk0tXu9dNu fp8knlf5EjjbjYUpL4TGe3O+LQKtXyyazBmRgGmgWUUOWPnLujHzFG/phGjgKFFx8u/3GMSNE xFhi+9QIxVaiHAZwOiLUoVuDFipx5uvuJQ8N/Xbuar+IcIyeylG7UxvsZDZtqqtQDcUHJ0kAO ioMMhsYsmNOj03nkfZStW8BeM27FYKkPMWqHPAEknv7Y60SivMzuOKXH4lvIUwpANx7toYK59 QcXtZ4HgoCeOsWHMu1HCMnQ9dNUsLyKCKr85Rzf1TT2Gf2jPKCTFPfVy7SlNbA7P/uQFdGaPZ GtKJkLh2Q/CVcLnUmt/WT1gPoZ7KXSimFPn3osekqLOuu62+OF2sYxqXCvYRulFIvf6hPWGLo 3qzVcvRCn8hVQOpoLoB3xJZMJ5uM8qu481JUw/K8OlqbHMrb7AONTNyVWnzJ0eYfs+UDBzub/ jAwE5Mj/SiezK/5tYDWFVDAn2fr80l4J84ef8oomzSqdNS1zVnuih3SO5aGWOLQczh1lRbjU0 ud794Vt0lSl71BiQr0mM0rKySygezRUVLZ6hPAcRCROILa86Xj3fWV9khg6FAR0YBWXkdej5X F3o65RIDd6sxZ9asG0kfUalQSBKvwanczQuVIRz+N7zl0mfMMdYuJ65oums4fgwwNU/UTt67c 76c+4WehlDvy6BopgY0/Vqw03clOSQLONkFWu2xhbHWbqzRh0LO77Y2uUFzSYrdKKcUjwgNkK EIpTwpKav6Qu9BmDrORQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/bn9X1-TaQIQYFTTq-fC2Q6RpkKI>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2021 09:03:25 -0000

Am 19.02.2021 um 09:47 schrieb Carsten Bormann:
> On 2021-02-19, at 09:45, Carsten Bormann <cabo@tzi.org> wrote:
>>
>> https://datatracker.ietf.org/doc/draft-bormann-core-media-content-type-=
format/
>
> Sorry, my intent here is probably better visible in the current editor=
=E2=80=99s version:
>
> https://cabo.github.io/mtct/draft-bormann-core-media-content-type-format=
.html
>
> Gr=C3=BC=C3=9Fe, Carsten

So I see
<https://cabo.github.io/mtct/draft-bormann-core-media-content-type-format.=
html#name-discussion>:

>  7. Discussion
>
> The ABNF given here is provisional and may need some more cleanup: We ne=
ed to unify the various forms of reg-name, token, etc.
> (ABNF just shown for illustration is centered, in an aside, and tagged w=
ith <artwork type=3D"abnf;old"...> in the XML, while the normative ABNF of=
 this memo is left-aligned and tagged with <sourcecode type=3D"abnf"...>.)=
We need to discuss case-insensitivity, which is usually rather insensitive=
.


FWIW, if you cite a specific piece of ABNF from other specs for
illustration, why not use <blockquote> for that? That should make the
distinction very visible.

Best regards, Julian


From nobody Sun Feb 21 11:57:02 2021
Return-Path: <jay@ietf.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13CF73A1069 for <rfc-markdown@ietfa.amsl.com>; Sun, 21 Feb 2021 11:57:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 Ul8roOL-4EGi; Sun, 21 Feb 2021 11:56:57 -0800 (PST)
Received: from jays-mbp.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 097433A1066; Sun, 21 Feb 2021 11:56:56 -0800 (PST)
From: Jay Daley <jay@ietf.org>
Message-Id: <E9362A07-0057-4DF0-B006-C45149F0FC82@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FCF5F385-252A-4CDF-BB2C-B1F766B94F8E"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 22 Feb 2021 08:56:54 +1300
In-Reply-To: <B8D57CFC-EB4A-4F7E-8614-99F39719183A@tzi.org>
Cc: Julian Reschke <julian.reschke@gmx.de>, rfc-markdown@ietf.org
To: Carsten Bormann <cabo@tzi.org>
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org> <20210219072402.GA151175@miek.nl> <77684aa0-dcdb-fc38-8d31-86f2f5ae2ede@gmx.de> <22FFC094-63C4-43E8-8FDA-28832DD7FF28@tzi.org> <B8D57CFC-EB4A-4F7E-8614-99F39719183A@tzi.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/EdEOM22qhJfnVqj1MnI2Os1u4wE>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Feb 2021 19:57:00 -0000

--Apple-Mail=_FCF5F385-252A-4CDF-BB2C-B1F766B94F8E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 19/02/2021, at 9:47 PM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> On 2021-02-19, at 09:45, Carsten Bormann <cabo@tzi.org> wrote:
>>=20
>> =
https://datatracker.ietf.org/doc/draft-bormann-core-media-content-type-for=
mat/
>=20
> Sorry, my intent here is probably better visible in the current =
editor=E2=80=99s version:
>=20
> =
https://cabo.github.io/mtct/draft-bormann-core-media-content-type-format.h=
tml

I=E2=80=99m not sure I understand - do you mean that you want it =
indented to show that you are quoting the ABNF or do mean that you want =
a different alignment.  I ask because I can=E2=80=99t see a different =
alignment.

Jay

>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
> _______________________________________________
> Rfc-markdown mailing list
> Rfc-markdown@ietf.org
> https://www.ietf.org/mailman/listinfo/rfc-markdown

--=20
Jay Daley
IETF Executive Director
jay@ietf.org


--Apple-Mail=_FCF5F385-252A-4CDF-BB2C-B1F766B94F8E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 19/02/2021, at 9:47 PM, Carsten Bormann &lt;<a =
href=3D"mailto:cabo@tzi.org" class=3D"">cabo@tzi.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">On 2021-02-19, at 09:45, Carsten Bormann &lt;<a =
href=3D"mailto:cabo@tzi.org" class=3D"">cabo@tzi.org</a>&gt; wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-bormann-core-media-content-=
type-format/" =
class=3D"">https://datatracker.ietf.org/doc/draft-bormann-core-media-conte=
nt-type-format/</a><br class=3D""></blockquote><br class=3D"">Sorry, my =
intent here is probably better visible in the current editor=E2=80=99s =
version:<br class=3D""><br class=3D""><a =
href=3D"https://cabo.github.io/mtct/draft-bormann-core-media-content-type-=
format.html" =
class=3D"">https://cabo.github.io/mtct/draft-bormann-core-media-content-ty=
pe-format.html</a><br class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>I=E2=80=99m not sure I understand - do you mean =
that you want it indented to show that you are quoting the ABNF or do =
mean that you want a different alignment. &nbsp;I ask because I can=E2=80=99=
t see a different alignment.</div><div><br =
class=3D""></div><div>Jay</div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><br class=3D"">Gr=C3=BC=C3=9Fe,=
 Carsten<br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">Rfc-markdown mailing list<br class=3D""><a =
href=3D"mailto:Rfc-markdown@ietf.org" =
class=3D"">Rfc-markdown@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/rfc-markdown<br =
class=3D""></div></div></blockquote></div><br class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: =
rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: =
rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div>--&nbsp;<br class=3D"">Jay Daley</div><div>IETF =
Executive Director<br class=3D""><a href=3D"mailto:jay@ietf.org" =
class=3D"">jay@ietf.org</a><br class=3D""></div></div></div></div>
</div>
<br class=3D""></body></html>=

--Apple-Mail=_FCF5F385-252A-4CDF-BB2C-B1F766B94F8E--


From nobody Sun Feb 21 16:38:31 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA7F93A08C5; Sun, 21 Feb 2021 16:38:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 2DxDe7GmkUPY; Sun, 21 Feb 2021 16:38:26 -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 A706F3A08C0; Sun, 21 Feb 2021 16:38:23 -0800 (PST)
Received: from [192.168.217.152] (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 4DkNZh0qp8zyhT; Mon, 22 Feb 2021 01:38:20 +0100 (CET)
Content-Type: multipart/alternative; boundary="Apple-Mail=_44A0C4B6-DA27-49D7-82A3-EFC7840B498F"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <E9362A07-0057-4DF0-B006-C45149F0FC82@ietf.org>
Date: Mon, 22 Feb 2021 01:38:19 +0100
Cc: Julian Reschke <julian.reschke@gmx.de>, rfc-markdown@ietf.org, RFC Interest Group <rfc-interest@rfc-editor.org>
Message-Id: <DA36EA61-F136-4C9F-9FA2-B9CBC24A6D7F@tzi.org>
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org> <20210219072402.GA151175@miek.nl> <77684aa0-dcdb-fc38-8d31-86f2f5ae2ede@gmx.de> <22FFC094-63C4-43E8-8FDA-28832DD7FF28@tzi.org> <B8D57CFC-EB4A-4F7E-8614-99F39719183A@tzi.org> <E9362A07-0057-4DF0-B006-C45149F0FC82@ietf.org>
To: Jay Daley <jay@ietf.org>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/1Q-3LEXqH2qK-RFNLK48qVM0ZYs>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2021 00:38:29 -0000

--Apple-Mail=_44A0C4B6-DA27-49D7-82A3-EFC7840B498F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

>> Sorry, my intent here is probably better visible in the current =
editor=E2=80=99s version:
>>=20
>> =
https://cabo.github.io/mtct/draft-bormann-core-media-content-type-format.h=
tml =
<https://cabo.github.io/mtct/draft-bormann-core-media-content-type-format.=
html>
>=20
> I=E2=80=99m not sure I understand - do you mean that you want it =
indented to show that you are quoting the ABNF or do mean that you want =
a different alignment.  I ask because I can=E2=80=99t see a different =
alignment.

I was essentially trying to separate the ABNF quoted for reference from =
the ABNF that is part of this specification.
As you can see, this doesn=E2=80=99t work very well in the HTML (better =
for figure 1, where it is obvious this is centred, than for figure 4).
The distinction is much easier to see in the plaintext, where =
aside/blockquote get much stronger visual support.

So this may not be the perfect example, but it was a case where I was =
trying to center source code.

My criticism of the current grammar is that there are lots of arbitrary =
differences between different contexts in which things can be used, and =
these arbitrary differences seem to be driven by the combination of (1) =
a desire to enforce a weird perception of =E2=80=9Cgood style=E2=80=9D =
with (2) a lack of imagination.  Much less of this would probably have =
happened if the grammar had been properly factorized.  The grammar style =
to repeat everything everywhere seems to suggest one should endlessly =
tweak any single one of the clones so they are all subtly different, =
leading to the current jungle.

CCing rfc-interest, because this is a problem not with, but for writing =
IETF documents in markdown.

Gr=C3=BC=C3=9Fe, Carsten


--Apple-Mail=_44A0C4B6-DA27-49D7-82A3-EFC7840B498F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;" class=3D""><div class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">Sorry, my intent here is =
probably better visible in the current editor=E2=80=99s version:<br =
class=3D""><br class=3D""><a =
href=3D"https://cabo.github.io/mtct/draft-bormann-core-media-content-type-=
format.html" =
class=3D"">https://cabo.github.io/mtct/draft-bormann-core-media-content-ty=
pe-format.html</a><br class=3D""></div></div></blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">I=E2=80=99m not sure I =
understand - do you mean that you want it indented to show that you are =
quoting the ABNF or do mean that you want a different alignment. &nbsp;I =
ask because I can=E2=80=99t see a different =
alignment.</div></div></div></div></blockquote><br class=3D""></div><div>I=
 was essentially trying to separate the ABNF quoted for reference from =
the ABNF that is part of this specification.</div><div>As you can see, =
this doesn=E2=80=99t work very well in the HTML (better for figure 1, =
where it is obvious this is centred, than for figure 4).</div><div>The =
distinction is much easier to see in the plaintext, where =
aside/blockquote get much stronger visual support.</div><div><br =
class=3D""></div><div>So this may not be the perfect example, but it was =
a case where I was trying to center source code.</div><div><br =
class=3D""></div><div>My criticism of the current grammar is that there =
are lots of arbitrary differences between different contexts in which =
things can be used, and these arbitrary differences seem to be driven by =
the combination of (1) a desire to enforce a weird perception of =E2=80=9C=
good style=E2=80=9D with (2) a lack of imagination. &nbsp;Much less of =
this would probably have happened if the grammar had been properly =
factorized. &nbsp;The grammar style to repeat everything everywhere =
seems to suggest one should endlessly tweak any single one of the clones =
so they are all subtly different, leading to the current =
jungle.</div><div><br class=3D""></div><div>CCing rfc-interest, because =
this is a problem not with, but for writing IETF documents in =
markdown.</div><div><br class=3D""></div><div><div>Gr=C3=BC=C3=9Fe, =
Carsten</div><div class=3D""><br class=3D""></div></div></body></html>=

--Apple-Mail=_44A0C4B6-DA27-49D7-82A3-EFC7840B498F--


From nobody Tue Feb 23 13:08:14 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4506C3A0BAB for <rfc-markdown@ietfa.amsl.com>; Tue, 23 Feb 2021 13:08:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.797
X-Spam-Level: 
X-Spam-Status: No, score=-1.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, TRACKER_ID=0.1, URIBL_BLOCKED=0.001] autolearn=no 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 kZrL80BoimYf for <rfc-markdown@ietfa.amsl.com>; Tue, 23 Feb 2021 13:08:09 -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 0497D3A0BA0 for <rfc-markdown@ietf.org>; Tue, 23 Feb 2021 13:08:08 -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 4DlWqC192tzyZ7; Tue, 23 Feb 2021 22:08:07 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mao-Original-Outgoing-Id: 635807286.34206-9d42202613e0aa5366eae4b72b838743
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Tue, 23 Feb 2021 22:08:06 +0100
Message-Id: <B05F1C0A-9248-4142-83F0-AFAB2A3E896F@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/FJkHJJrj0ci_uemB5F5sSEP7Wyg>
Subject: [Rfc-markdown] 1.3.36: new: kramdown-rfc-cache-i-d-bibxml
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2021 21:08:12 -0000

TL;DR: You don=E2=80=99t need the below.
But it can make you faster and work better while offline.

Gr=C3=BC=C3=9Fe, Carsten


Many of us have been using rsync to get copies of the bibxml files on =
xml2rfc.tools.ietf.org so we did not have to wait for kramdown-rfc to =
fetch updates.  However, datatracker currently does not offer rsyncing, =
so you couldn=E2=80=99t get the bibxml3 directory right from the =
horse=E2=80=99s mouth.

Now you can.  1.3.36 comes with a new command:

kramdown-rfc-cache-i-d-bibxml

This does a cache preload: it sends copies of the bibxml for all =
active(*) I-Ds (both numbered and up-to-date references) to your =
KRAMDOWN_REFCACHEDIR.

(The environment variable KRAMDOWN_REFCACHEDIR should point to =
~/.cache/xml2rfc to share a cache between xml2rfc and kramdown-rfc.  If =
it is not set at all, you will be warned, but the command will happily =
proceed with that default.  Kramdown-rfc still defaults to ./.refcache, =
though, so it won=E2=80=99t find the cache...)

The command is rather expensive(**) on the first call (initial pull), =
but quite efficient after that (update pull).

You could put the invocation into your crontab.  Even though it=E2=80=99s =
quite fast, it is probably not worth calling it more than once an hour, =
because the all_id2.txt file on which it builds currently isn=E2=80=99t =
refreshed more often.


kramdown-rfc-cache-i-d-bibxml is not for everyone: it needs at least =
2016=E2=80=99s Ruby 2.4 (***) and an install of the gem =
"net-http-persistent" (not installed as a requirement by default, as it =
may be problematic on some older platforms).


(*) So kramdown-rfc=E2=80=99s existing caching engine will take care of =
your very few references to outdated I-Ds referenced by version number =
and expired I-Ds.

(**) including for datatracker itself =E2=80=94 it makes some 3600 HTTP =
requests in a row on an initial pull.  So don=E2=80=99t do that 20 =
minutes before the I-D deadline =E2=80=94 be prepared, and only do =
update pulls in times of I-D frenzy.
[And now you know why I'm pushing this update a day after the I-D =
deadline :-)]

(***) If you have a Mac, and are using the system Ruby, this means it =
works on Catalina and higher.  We do prefer using a homebrew-installed =
Ruby in any case.


From nobody Fri Feb 26 07:07:51 2021
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E0993A09C0 for <rfc-markdown@ietfa.amsl.com>; Fri, 26 Feb 2021 07:07:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 tAfU3KE7Pf3C for <rfc-markdown@ietfa.amsl.com>; Fri, 26 Feb 2021 07:07:47 -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 F0E6B3A09BC for <rfc-markdown@ietf.org>; Fri, 26 Feb 2021 07:07:46 -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 4DnCh06142zyXV; Fri, 26 Feb 2021 16:07:44 +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: <E294FFDC-9D2E-4AE6-B61B-440539AE232B@tzi.org>
Date: Fri, 26 Feb 2021 16:07:44 +0100
Cc: RFC Interest Group <rfc-interest@rfc-editor.org>
X-Mao-Original-Outgoing-Id: 636044864.204412-30aba237d7007c86673903fc08a59668
Content-Transfer-Encoding: quoted-printable
Message-Id: <5FB26904-1D13-4830-9755-65FDA94D3E13@tzi.org>
References: <20210226092712.GA7967@miek.nl> <0bcd3cac-6fa4-b7e1-63ae-e81380bb07cf@gmx.de> <20210226100116.GA8958@miek.nl> <93495dfb-d515-820e-d9ba-29cf711e5598@gmx.de> <E294FFDC-9D2E-4AE6-B61B-440539AE232B@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/nnwJ9vxYWwv4MdhZUsFVaM-gXKs>
Subject: [Rfc-markdown] 1.3.37: Annotate contributors section (Re: [rfc-i] contacts section?)
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2021 15:07:50 -0000

1.3.37: contributors to be listed in the contributor section can now be =
annotated with text that will be added to that section after their =
contact information.

The text is entered in the =E2=80=9Ccontribution=E2=80=9D entry of the =
contact information for a contributor.
It is markdown and can contain paragraph breaks and other markup, as =
shown below (with some author information as context, which is not shown =
in the rendering).
Note that YAML has the =E2=80=9C|=E2=80=9D syntax that is strongly =
recommended for entering markdown text into YAML entries.

author:
  - name: Carsten Bormann
    org: Universit=C3=A4t Bremen TZI
    email: cabo@tzi.org
contributor:
  - name: Peter Occil
    email: poccil14 at gmail dot com
    contribution: |
      Peter Occil registered tags 30, 264, 265, 268=E2=80=93270
      ({{advanced-arithmetic}}), 38, 257, 266 and 267
      ({{domain-specific}}), and contributed much of the text about
      these tags in this document.
  - name: Jane Doe
    org: To do
    contribution: |
      Further contributors will be listed here as text is added.

      Plase stay tuned.

=E2=9E=94=20

Contributors

   Peter Occil

   Email: poccil14 at gmail dot com

   Peter Occil registered tags 30, 264, 265, 268-270 (Section 6.1), 38,
   257, 266 and 267 (Section 7), and contributed much of the text about
   these tags in this document.

   Jane Doe
   To do

   Further contributors will be listed here as text is added.

   Plase stay tuned.

Note that the text rendition of the XML generated contains some spurious =
empty lines between contact and text; there is no obvious workaround =
until this is fixed in xml2rfc.  The HTML seems fine.

Gr=C3=BC=C3=9Fe, Carsten


> On 2021-02-26, at 13:18, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> V3 has a contributors section.
> Kramdown-rfc can generate that from metadata that look exactly like =
author metadata (so it=E2=80=99s easy to shift back and forward).
> What we don=E2=80=99t have is a way to add annotations to that (no =
extra RFCXML support needed, as the kramdown-rfc result would then look =
a lot like the below).
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
>=20
>> On 26. Feb 2021, at 11:51, Julian Reschke <julian.reschke@gmx.de> =
wrote:
>>=20
>> You can do something like:
>>=20
>> <section name=3D"Contacts">
>> <contact fullname=3D"Sam Whatever" ...>
>> </contact>
>> <t>Sam wrote <xref. .../>.</t>
>> </section>
>=20

