Merge branch 'plants-00'

Author: davidben

.gitignore

@@ -1,23 +1,24 @@
+*~
+/*-[0-9][0-9].xml
+archive.json
+draft-ietf-plants-merkle-tree-certs.xml
+Gemfile.lock
+/.gems/
 *.html
+/.idea/
+/lib
+/.*.mk
+/node_modules/
+package-lock.json
 *.pdf
 *.redxml
+/.refcache
+report.xml
 *.swp
+.tags
 *.txt
 *.upload
-*~
-.tags
-/*-[0-9][0-9].xml
-/.*.mk
-/.gems/
-/.refcache
 /.venv/
-/.vscode/
-/lib
-/node_modules/
 /versioned/
-Gemfile.lock
-archive.json
-draft-davidben-tls-merkle-tree-certs.xml
-package-lock.json
-report.xml
+/.vscode/
 !requirements.txt

CONTRIBUTING.md

@@ -15,10 +15,13 @@ repository constitutes Contributions to the IETF Standards Process
 You agree to comply with all applicable IETF policies and procedures, including,
 BCP 78, 79, the TLP, and the TLP rules regarding code components (e.g. being
 subject to a Simplified BSD License) in Contributions.
+
+
 ## Working Group Information
 
-Discussion of this work occurs on the [PKI, Logs, And Tree Signatures mailing list](mailto:plants@ietf.org)
-([archive](https://mailarchive.ietf.org/arch/browse/plants/),
+Discussion of this work occurs on the [PKI, Logs, And Tree Signatures
+Working Group mailing list](mailto:plants@ietf.org)
+([archive](https://mailarchive.ietf.org/arch/browse/plants),
 [subscribe](https://www.ietf.org/mailman/listinfo/plants)).
 In addition to contributions in GitHub, you are encouraged to participate in
 discussions there.
@@ -28,3 +31,26 @@ technical issues needs to occur on the mailing list.
 
 You might also like to familiarize yourself with other
 [Working Group documents](https://datatracker.ietf.org/wg/plants/documents/).
+
+## How to Contribute
+
+Contributions can be made by creating pull requests, opening an issue, or
+posting to the working group mailing list. See above for the email address
+and a note about policy.
+
+Here are two ways to create a pull request ("PR"):
+
+- Copy the repository and make a pull request using the Git command-line
+tool, using the [GitHub documentation](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) if needed.
+
+- You can use the GitHub UI as follows:
+  - View the draft source
+  - Select the pencil icon to edit the file (usually top-right on the screen)
+  - Make edits
+  - Select "Commit changes"
+  - Add a title and explanatory text
+  - Select "Propose"
+  - When prompted, click on "Create Pull Request"
+
+Document authors/editors are often happy to accept contributions of text,
+and might be willing to help you through the process. Email them and ask.

README.md

@@ -1,21 +1,22 @@
+<!-- regenerate: on (set to off if you edit this file) -->
+
 # Merkle Tree Certificates
 
-This is the working area for the individual Internet-Draft, "Merkle Tree Certificates".
+This is the working area for the IETF [PLANTS Working Group](https://datatracker.ietf.org/group/plants/documents/) Internet-Draft, "Merkle Tree Certificates".
 
-* [Editor's Copy](https://davidben.github.io/merkle-tree-certs/#go.draft-davidben-tls-merkle-tree-certs.html)
-* [Datatracker Page](https://datatracker.ietf.org/doc/draft-davidben-tls-merkle-tree-certs)
-* [Individual Draft](https://datatracker.ietf.org/doc/html/draft-davidben-tls-merkle-tree-certs)
-* [Compare Editor's Copy to Individual Draft](https://davidben.github.io/merkle-tree-certs/#go.draft-davidben-tls-merkle-tree-certs.diff)
+* [Editor's Copy](https://davidben.github.io/merkle-tree-certs/#go.draft-ietf-plants-merkle-tree-certs.html)
+* [Datatracker Page](https://datatracker.ietf.org/doc/draft-ietf-plants-merkle-tree-certs)
+* [Working Group Draft](https://datatracker.ietf.org/doc/html/draft-ietf-plants-merkle-tree-certs)
+* [Compare Editor's Copy to Working Group Draft](https://davidben.github.io/merkle-tree-certs/#go.draft-ietf-plants-merkle-tree-certs.diff)
 
 
 ## Contributing
 
 See the
 [guidelines for contributions](https://github.com/davidben/merkle-tree-certs/blob/main/CONTRIBUTING.md).
 
-Contributions can be made by creating pull requests.
-The GitHub interface supports creating pull requests using the Edit (✏) button.
-
+The contributing file also has tips on how to make contributions, if you
+don't already know how to do that.
 
 ## Command Line Usage
 

draft-davidben-tls-merkle-tree-certs.md draft-ietf-plants-merkle-tree-certs.mddraft-davidben-tls-merkle-tree-certs.md renamed to draft-ietf-plants-merkle-tree-certs.md

@@ -1,21 +1,21 @@
 ---
 title: Merkle Tree Certificates
-docname: draft-davidben-tls-merkle-tree-certs-latest
+docname: draft-ietf-plants-merkle-tree-certs-latest
 submissiontype: IETF
 category: std
 number:
 date:
 consensus: true
 v: 3
 area: "Security"
-workgroup: "PLANTS Working Group"
+workgroup: "PKI, Logs, And Tree Signatures"
 venue:
-  group: PLANTS
-  type: Working Group
-  mail: plants@ietf.org
-  arch: https://mailarchive.ietf.org/arch/browse/plants/
+  group: "PKI, Logs, And Tree Signatures"
+  type: "Working Group"
+  mail: "plants@ietf.org"
+  arch: "https://mailarchive.ietf.org/arch/browse/plants"
   github: "davidben/merkle-tree-certs"
-  latest: "https://davidben.github.io/merkle-tree-certs/draft-davidben-tls-merkle-tree-certs.html"
+  latest: "https://davidben.github.io/merkle-tree-certs/draft-ietf-plants-merkle-tree-certs.html"
 
 author:
  -
@@ -192,8 +192,6 @@ This document describes Merkle Tree certificates, a new form of X.509 certificat
 
 # Introduction
 
-Authors' Note: This is an early draft of a proposal with many parts. We expect most details will change as the proposal evolves. This document has a concrete specification of these details, but this is only intended as a starting point, and to help convey the overall idea. The name of the draft says "tls" to keep continuity with earlier iterations of this work, but the protocol itself is not TLS-specific.
-
 In Public Key Infrastructures (PKIs) that use Certificate Transparency (CT) {{?RFC6962}} for a public logging requirement, an authenticating party must present Signed Certificate Timestamps (SCTs) alongside certificates. CT policies often require two or more SCTs per certificate {{APPLE-CT}} {{CHROME-CT}}, each of which carries a signature. These signatures are in addition to those in the certificate chain itself.
 
 Current signature schemes can use as few as 32 bytes per key and 64 bytes per signature {{?RFC8032}}, but post-quantum replacements are much larger. For example, ML-DSA-44 {{?FIPS204=DOI.10.6028/NIST.FIPS.204}} uses 1,312 bytes per public key and 2,420 bytes per signature. ML-DSA-65 uses 1,952 bytes per public key and 3,309 bytes per signature. Even with a directly-trusted intermediate ({{Section 7.5 of ?I-D.ietf-tls-trust-anchor-ids}}), two SCTs and a leaf certificate signature adds 7,260 bytes of authentication overhead with ML-DSA-44 and 9,927 bytes with ML-DSA-65.
@@ -2133,3 +2131,8 @@ In draft-04, there is no fast issuance mode. In draft-05, frequent, non-landmark
 - Fixes to ASN.1 module
 
 - Make log entry more friendly to single-pass verification
+
+## Since draft-davidben-tls-merkle-tree-certs-10
+{:numbered="false"}
+
+- Adopted by working group