And the reply from Robert Sparks, IETF tools project manager:
Well, not really. It would be a burden. It's possible to
take it on if it is necessary, but it comes with a cost.
From: Rich Salz <[email protected]>
Date: Thursday, July 27, 2023 at 1:23 PM
To: "[email protected]" <[email protected]>
Subject: FW: [Tools-discuss] File storage
FYI
From: "Salz, Rich" <[email protected]>
Date: Thursday, July 27, 2023 at 1:23 PM
To: tools-discuss <[email protected]>
Subject: [Tools-discuss] File storage
The TLS working group is looking at a document that would build a compression
dictionary from a well-known
Public database, the common CA database,
https://www.ccadb.org/<https://urldefense.com/v3/__https:/www.ccadb.org/__;!!GjvTz_vk!Qvoyr-Mw3NRafFvUJ8-Fbb8cHzfNJ6ri8ms06CNdtMgaenz2PQCaraozu57DcRdOQq2tiVOjPkwxAZghi7Y5sHI7Pmjb$>.
An issue was raised during discussion it might be an issue if the RFC said
“download this file, and do this pre-processing to build the dictionary” as
opposed to storing a copy of the database (immutably) at the IETF, or a text
representation of the dictionary.
Writing it down as an Internet-draft is not feasible. Is storing a file
something the tools system can (should?) handle?
_______________________________________________
TLS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tls
