IETF Logo Mail Archive

Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary of Removing postal information from RFCs

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 20 July 2021 13:28 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 11CB03A2294 for <rfc-markdown@ietfa.amsl.com>; Tue, 20 Jul 2021 06:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 pD15aHDDim-e for <rfc-markdown@ietfa.amsl.com>; Tue, 20 Jul 2021 06:28:13 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DA693A2297 for <rfc-markdown@ietf.org>; Tue, 20 Jul 2021 06:28:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 240843899A; Tue, 20 Jul 2021 09:31:30 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 6lGsNSaqL9BY; Tue, 20 Jul 2021 09:31:27 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 1204C38994; Tue, 20 Jul 2021 09:31:27 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 5B46E1F1; Tue, 20 Jul 2021 09:28:07 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, Toerless Eckert <tte@cs.fau.de>, rfc-markdown@ietf.org
In-Reply-To: <DBCC4252-8A2D-473C-82CD-B1B2688586D3@tzi.org>
References: <20210712034838.B461E209AFFB@ary.qy> <6c781dab-7a40-7031-be1c-d77a182f4cf4@gmail.com> <DE0CD982-D4BE-44A6-9234-B53A756E9717@mnot.net> <bbb8302a-4041-35db-ce61-d2a18b8ebeee@taugh.com> <AB6E5013-C14E-4962-8907-17F241971F9D@tzi.org> <20210719171839.GB24216@faui48e.informatik.uni-erlangen.de> <DBCC4252-8A2D-473C-82CD-B1B2688586D3@tzi.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 20 Jul 2021 09:28:07 -0400
Message-ID: <15571.1626787687@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/Ibdn1rwrTqepgYPxjnmQgIHHy4c>
Subject: Re: [Rfc-markdown] Carsten: Re: [rfc-i] summary of Removing postal information from RFCs
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, 20 Jul 2021 13:28:20 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    >> So, what is the relationship kramdown-rfc2629 to this ?
    >>
    >> - Can the kramdown create xmlv3 output ?

    > Yes, via the --v2v3 process in xml2rfc.

Do you think that you'll change to producing pure v3 output at some point?
I understand that might be awhile, or that -3 might become the default before
that point.

I'm just asking about processing plans.

    > With the --v3 (-3) flag, kramdown-rfc2629 produces XML that xml2rfc can
    > process, and that --v2v3 can turn into the current version of v3.
    > This XML is no longer v2 compliant, as it uses the new features of v3.

So it's some kind of v2 / v3 mutt :-)


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email