GitHub AUTH48 experiment: RFC 9345

• https://datatracker.ietf.org/doc/draft-ietf-tls-subcerts/
• Original repo: github repo
• Based on "Experiment 6" design.
• Variance from the design:
  • markdown rather than RFCXML source

The RPC did the following:

• Forked the author's document repo (forked repos are automatically public; they cannot be made private): https://github.com/rfc-editor/draft-ietf-tls-subcerts
• Created the following labels:
  • AD approval required - Document update needs Area Director review
  • question - Further information is requested
  • rfced - RFC Editor question or FYI
  • rfced-ready - RFC Editor may make updates based on issue conclusion
• Changed the name of the base branch ( s/master/rpc-main)
• Used the draft string as the file name until the file was converted to XML (XML was committed as rfc9345.xml).
  This was to make it easier for authors to port changes to the wg repo
• Updated the readme to describe the AUTH48 process.
• Added note well.
  Did not add license.md or contributing.md because the forked repo already had a version of these files.
• Added our set of minimal updates as PR; the RPC accepted the PR (as it contained a basic set of updates to conform with RFC Style, e.g., removing the change log, moving Acknowledgements to the end)
• Added questions with suggested text as PRs
• Added open questions as issues
• Converted to XML and made formatting edits only after the author approved copy edits.

See the readme.

• Edits need to be minimal. Other edits that might normally be done should be addressed as GitHub issues or PRs.

• Please just use the WG repo.
• Submit *all* RPC changes as PRs.
• Every RPC version should be in GitHub, not just on the RPC Web site.