[Tools-discuss] Re: PDF [Re: Tools team meeting tomorrow 9 July 2024 1800 UTC]

Carsten Bormann <cabo@tzi.org> Tue, 09 July 2024 16:18 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68EDDC180B52 for <tools-discuss@ietfa.amsl.com>; Tue, 9 Jul 2024 09:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 6jpBcaLg9pNM for <tools-discuss@ietfa.amsl.com>; Tue, 9 Jul 2024 09:18:30 -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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4F5FC169425 for <tools-discuss@ietf.org>; Tue, 9 Jul 2024 09:18:29 -0700 (PDT)
Received: from clients-pool6-0352.vpn.uni-bremen.de (clients-pool6-0352.vpn.uni-bremen.de [134.102.91.96]) (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 4WJR4L58ZgzDCbT; Tue, 9 Jul 2024 18:18:26 +0200 (CEST)
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: <6357e5da-b634-48d7-810e-5ad52ddf5750@nostrum.com>
Date: Tue, 09 Jul 2024 18:18:26 +0200
X-Mao-Original-Outgoing-Id: 742234706.291847-8c4a1f902627ec24a895b8ff60d49f55
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E8EA541-FC9A-466A-A2B5-55404FD64D77@tzi.org>
References: <336856cc-9986-43ba-bc26-f5c96aaa9521@nostrum.com> <A4157066-C7BA-4560-812A-21DB8A063AC4@tzi.org> <eb2d896c-d246-42c7-97c6-a4b3c7151cd9@nostrum.com> <A0EA194A-556C-421E-9358-39B0885597D1@tzi.org> <6357e5da-b634-48d7-810e-5ad52ddf5750@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Message-ID-Hash: 7VI7YOMJE3VB2DMWMGRWSIPNFFFJDEIO
X-Message-ID-Hash: 7VI7YOMJE3VB2DMWMGRWSIPNFFFJDEIO
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: tools-discuss@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] Re: PDF [Re: Tools team meeting tomorrow 9 July 2024 1800 UTC]
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/TDqJaJB6gH48zX83eA_RVFxM2nA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

> 
> And then the cost of maintaining the store - _updating_ the store when something fundamental changes that demands that we rerender the pdf (the basis becomes _all versions of all drafts in the archive_

… that have XML sources.
That should be some 60000 documents per rerender, or (conservatively) 330 CPU hours (~ two weeks if done sequentially on a single core).
You’d probably want to use a multi-core machine for that, and don’t do global rerenderings every week.

> at that point), and the time it takes to move the collective set of bits repeatedly when bots scrape them and individuals/bots do new blind full-rsyncs. All that can be optimized downwards and towards the edge, but dismissing this as a conversation about <$10/yr is incorrect.

The $10/yr was specifically about potential CPU savings from on-demand rendering.
Render-on-submit simply is easier to implement, and it gives much better results for the users, so I argued that this may be where we want to go.

(It also leads to more correct results, but I’m not going to open that discussion.)

> […on-demand…] Yes, that can (and must) be redesigned to make better use of modern web technologies, and my initial question is about whether we invest in a redesign that moves this to places that help more people more of the time, or if we are far enough along that people can build these locally, closer to the origin.

Redesign for render-up-front is simpler, I’d think.

> Your argument to keep them is to promote reviewing all the formats as if they are going to become RFCs (at least for xml source).

No.  I’m just saying some reviewers (like Marc and I) will use the PDF form, and making them jump through hoops is not what this organization should do.

> That would be better done _before_ submission wouldn't it?

By the authors, yes.  They need to have a reasonable pipeline set up anyway.

However, the **whole point** of putting an I-D on the I-D repository is to enable *others* to review it!

Grüße, Carsten