IETF Logo Mail Archive

Re: [rfc-i] [Rswg] Is there any issue with removing the `<format` element from references served at bib.ietf.org

Carsten Bormann <cabo@tzi.org> Wed, 18 January 2023 10:28 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E602C14CE44; Wed, 18 Jan 2023 02:28:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.185
X-Spam-Level:
X-Spam-Status: No, score=-4.185 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b9iRrXAVw6vC; Wed, 18 Jan 2023 02:28:38 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8197EC14CE3D; Wed, 18 Jan 2023 02:28:38 -0800 (PST)
Received: from client-0027.vpn.uni-bremen.de (client-0027.vpn.uni-bremen.de [134.102.107.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Nxhn03KGXzDCg0; Wed, 18 Jan 2023 11:28:36 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <87cbb1cc-adb1-3084-b663-ff3ed9e6f870@nostrum.com>
Date: Wed, 18 Jan 2023 11:28:36 +0100
Cc: Julian Reschke <julian.reschke@gmx.de>, "rswg@rfc-editor.org" <rswg@rfc-editor.org>
X-Mao-Original-Outgoing-Id: 695730515.8943141-e97e7462c19f55327d8365170639a878
Content-Transfer-Encoding: quoted-printable
Message-Id: <A71FF678-5589-40D9-9FA9-0D49083FA17C@tzi.org>
References: <dd4d6fb0-b37d-5163-fbb7-22780f04945d@nostrum.com> <87cbb1cc-adb1-3084-b663-ff3ed9e6f870@nostrum.com>
To: RFC Interest <rfc-interest@rfc-editor.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/1Z-70o0fvcgMi03_CVT_0lXs1_U>
Subject: Re: [rfc-i] [Rswg] Is there any issue with removing the `<format` element from references served at bib.ietf.org
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2023 10:28:44 -0000

On 2023-01-17, at 22:15, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> If there's no response by the end of the week, we plan to take action.

Data point: one of the next versions of kramdown-rfc is slated to have code that transmogrifies any remaining bib.ietf.org <format elements into @target attributes.
Let’s see who beats whom on this feature on the timeline :-)

Grüße, Carsten

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