IETF Logo Mail Archive

Re: [irsg] The RPC's roadmap regarding GitHub

Carsten Bormann <cabo@tzi.org> Tue, 08 September 2026 16:34 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: wgchairs@mail2.ietf.org
Delivered-To: wgchairs@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B5F0F13732B64 for <wgchairs@mail2.ietf.org>; Tue, 8 Sep 2026 09:34:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1788885292; bh=hSxSqx2kyJpyro7KaB2+ZuHRqvI3GiJmEidoMSjYHTI=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=FuDs8uJq7E/RL9ExQbSUsGPf09/KFh+w5UXoGBLICIJ1wkkdnA7srWqEnQJ7/+Rfl 9IN61Lwj1lsAZqNxeM83LsbFMl0k1RQ3zZQYuICWYGDpd7F4wB66VTNhpWCozjuThW rLNIKZex2sVjKgkJUF39HrEdmIMn56LJxiix0gBk=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=tzi.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5Ylk3qSUXFo for <wgchairs@mail2.ietf.org>; Tue, 8 Sep 2026 09:34:50 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id E789913732B52 for <wgchairs@ietf.org>; Tue, 8 Sep 2026 09:34:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tzi.org; s=2019; t=1788885289; bh=hSxSqx2kyJpyro7KaB2+ZuHRqvI3GiJmEidoMSjYHTI=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=rvRTkikWS/Rd6zLXANkjFbvcNuHOfpcEZI3RbFWr6hMxAoG78gz7qymCMdKQ81hm6 kJ48ksPyn40nnc4peSnZlRGDwdNSc0AQ5btobCCLOOR32E2hxO77rlII3ju8MYUJJh WMRupZmVZlE3D+eGjpe4Gt62ik2s8ipYvr286TLeXD5ToQDr+uP9dCioSOnF3/bMZd CgH9iAGTY4pziH1NJhWv6BMPY9sIIIN49gjtiNRC6a2wVCuBeA463Vqaiki/aX9CtK TFYhE8HZg8oKTn5l0zKojmUuwE1WA5hLSKBGCtGbksxe8EEwjm6uQjDPmw6EnTWec4 3AKKoPp63FJHQ==
Received: from smtpclient.apple (p5089a12b.dip0.t-ipconnect.de [80.137.161.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: cabo) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4hfV0850gHzDCcl; Tue, 8 Sep 2026 18:34:48 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.700.51.1.1\))
Subject: Re: [irsg] The RPC's roadmap regarding GitHub
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <a8fbfcd3-5cad-4220-8174-b98be49cf44f@staff.rfc-editor.org>
Date: Tue, 08 Sep 2026 18:34:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5271353-412D-4CC9-9410-C6B302DD17D4@tzi.org>
References: <cf16dc44-dee6-417b-8796-84c24b5adf2b@staff.rfc-editor.org> <3XgIjBtmulQvGkAdWqil1TCywq8fUnwW3zwTFZSiT4p9VSYN9ZetdsgKu9gMKYtA9Nr1dkOdezlqFxYBi2RxwUATD6Xi7-Fyu39_qcY6qaQ=@ounsworth.ca> <CAKoiRuYUnP=q2=k4-s+9DLevvGdJb0ZRTaQfUOfKRUTRb5bTTg@mail.gmail.com> <HqiiuJF4nNXWjWYEqb6kHXCjp3UpemWPiwSZf2wz4imoBEbFC2bkmO2Zv8uzWQS8yOz1YrfCcXZbHeXWX-rZEU8qAtw3anw-5FaINjoxHs8=@ounsworth.ca> <DM4PR11MB5469B15B9B542AAC2B5068F6B5D32@DM4PR11MB5469.namprd11.prod.outlook.com> <CAKoiRubA0_CKgCfkD2QWmyNOd8619mGqiWOyRRvUg6f+LLgdhA@mail.gmail.com> <DM4PR11MB546927926B965E915DA2D9ABB5D32@DM4PR11MB5469.namprd11.prod.outlook.com> <CAKoiRua-=rJ4xhO9FxN=3STbiax9YRb7HJ=HDV_C6h_GSs9MJg@mail.gmail.com> <a8fbfcd3-5cad-4220-8174-b98be49cf44f@staff.rfc-editor.org>
To: Jean Mahoney <jmahoney@staff.rfc-editor.org>
X-Mailer: Apple Mail (2.3864.700.51.1.1)
X-FromAuthMilter: ok
Message-ID-Hash: NSLWZG3EBND66NA6TOUWYPFWE7HB3NFH
X-Message-ID-Hash: NSLWZG3EBND66NA6TOUWYPFWE7HB3NFH
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-wgchairs.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Rohan Mahy <rohan.mahy@gmail.com>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, Mike Ounsworth <mike=40ounsworth.ca@dmarc.ietf.org>, WG Chairs <wgchairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/7tXPwCDSUtJYF5WqP2CrZTluaHs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Owner: <mailto:wgchairs-owner@ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Subscribe: <mailto:wgchairs-join@ietf.org>
List-Unsubscribe: <mailto:wgchairs-leave@ietf.org>

On Aug 6, 2026, at 00:01, Jean Mahoney <jmahoney@staff.rfc-editor.org> wrote:
> 
> [JM] And the answer I received for that issue is that kramdown-rfc can already put included files in the markdown output when you run the following two commands (although it doesn't put markers around included content):
> 
>   kramdown-rfc mydraft.md >mydraft.xml
> 
>   kramdown-rfc-extract-markdown mydraft.xml >mydraft-files-inline.md

Ah.
Let’s come up markers for that!

(Not entirely trivial, because ::include does not necessarily create exactly one figure.
I need to dig up the source of RFC 7400, which was mostly written in the form machine-generated includes…)

Grüße, Carsten

v2.46.0 | Report a Bug | By Email | System Status