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

Miek Gieben <miek@miek.nl> Tue, 20 July 2021 14:27 UTC

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 54A1A3A24AE for <rfc-markdown@ietfa.amsl.com>; Tue, 20 Jul 2021 07:27:31 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 HTd5jFm2vUFF for <rfc-markdown@ietfa.amsl.com>; Tue, 20 Jul 2021 07:27:25 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 748593A24AC for <rfc-markdown@ietf.org>; Tue, 20 Jul 2021 07:27:25 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id w14so28655194edc.8 for <rfc-markdown@ietf.org>; Tue, 20 Jul 2021 07:27:25 -0700 (PDT)
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=m7ld4PnVVZuidrAraLVUrvj2uR65DkoP1LduY/TQpew=; b=GWuoNmCBMKC7SUJjf3vzqQNu+iywSAeP44OuVSwYqZ2ZqDYOaSz7wBWOGrV9crLIr6 4mj8t31JZBk5RGKAFN4HS21ZpWfVFeER2WzFkqGuC1AXDWH5RTJYHxahC4bId8FY1HLb Jz5mtU6bCcPtd1r44C1d9EGpZOQX3hNUaZ9KzE6v8wQcO+6QaNxE1E7wksLchEyncrVb jTTDqXPLnWc/vL3OnOfAoJAxtxZcyGDMUdw9rp/iTmgg9jYlxb651zpfoTFaBakYK0Zc TpTxBV1msKmz07ij0u46r4NBDjUmWMv4OQlXq6m85ndBS58SIXgEmMIDRIjll0x4lBXY reiA==
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=m7ld4PnVVZuidrAraLVUrvj2uR65DkoP1LduY/TQpew=; b=YCYNI4uDsLzOpIO186veP88RQUdLonR7wHu2btdRP5c5YAVE0rOlACjF3u1KAN0+QV 9/VN0KtC1oEGUNLmojESVk9yIHv6iTzN3ygyutl1IBaoqtLgxlu7C/lMKsx9IQF27JFV mr0XF8oI5LlcX1JisbyUOv18lbVExy2rE+GYHgAk9x/f3funSNU2Wv1xx/uKjNJN4x5w LwUuaS0ThftqUtkBmC526RZ4wxArIrd0/GJSFNEh1Vg2ld9nUF6lXBkhtxU6WIseHcQe ez5+xoD9XetcZS6DnBQyUSQv0Pha9ka3+nDGng757D+Vxmw8T9SOsV12kSgGmhQ6NT8N rKzg==
X-Gm-Message-State: AOAM531Jcogn6iWDoG3dQ/GkbqPGlWWLqIxvgAztRtdQHlsCpDXv8eVi iAOuEvxmqJI8A+VTj0kKA77KkA==
X-Google-Smtp-Source: ABdhPJzQMXAMLaD5+XOhAz42BO735gAMsZKMkxc5IUfN7InLtq0yVdl31xwOnmW/HY+CCv29Timv8A==
X-Received: by 2002:aa7:d514:: with SMTP id y20mr41312062edq.371.1626791242266; Tue, 20 Jul 2021 07:27:22 -0700 (PDT)
Received: from miek.nl (dhcp-077-251-206-012.chello.nl. [77.251.206.12]) by smtp.gmail.com with ESMTPSA id p23sm9386058edt.71.2021.07.20.07.27.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Jul 2021 07:27:21 -0700 (PDT)
Date: Tue, 20 Jul 2021 16:27:18 +0200
From: Miek Gieben <miek@miek.nl>
To: Carsten Bormann <cabo@tzi.org>
Cc: Toerless Eckert <tte@cs.fau.de>, rfc-markdown@ietf.org
Message-ID: <20210720142718.GA21843@miek.nl>
Mail-Followup-To: Carsten Bormann <cabo@tzi.org>, Toerless Eckert <tte@cs.fau.de>, rfc-markdown@ietf.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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Disposition: inline
In-Reply-To: <DBCC4252-8A2D-473C-82CD-B1B2688586D3@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/DSnPB_B30GcRlaReGQhNw1vGPRU>
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 14:27:32 -0000

[ Quoting <cabo@tzi.org> in "Re: [Rfc-markdown] Carsten: Re: [rf..." ]
>CCing RFC-markdown...
>
>> On 19. Jul 2021, at 19:18, Toerless Eckert <tte@cs.fau.de> wrote:
>>
>> So, what is the relationship kramdown-rfc2629 to this ?
>>
>> - Can the kramdown create xmlv3 output ?
>
>Yes, via the --v2v3 process in xml2rfc.

FWIW mmark opted to just output v3 XML directly (I've deleted the whole XML2 rendering),
but this does require to be up to date with xml2rfc.

Postalline is supported.

/Miek

--
Miek Gieben