This repository is for managing document updates for RFC 9518 during AUTH48. This is an experiment of a GitHub-based process for AUTH48, and it emulates the current AUTH48 procedure.
Please see the License. The IETF Note Well applies.
GitHub features that will be used:
Author and ISE, please ensure that your GitHub notification settings are set such that you can participate promptly in discussions of issues and pull requests. For more information, please see Configuring notifications.
This document is being edited in kramdown-rfc markdown. Once the content is stable, the markdown will be converted to RFCXML and formatted as an RFC. Your final approval means you approve both the content and format see "Approving the Document" below for more information.
The initial version of draft-nottingham-avoiding-internet-centralization-14.md is the same as what was approved for publication. Various PRs and issues have been added to the repo. PRs have been added to contain the RFC Production Center's edits and suggested updates. Open-ended questions and FYIs have been added as issues. Please approve the PRs or propose alternate updates. For the issues, provide your answers in the comments or add PRs to resolve them.
Please provide your answers in the comments and use a label to indicate issue status:
Feel free to add new issues and PRs for new edits and questions. Use @mention to identify the participant who should answer.
If the RFC Editor creates the PR, the editor expects feedback from at least one reviewer before merging the PR. We expect the other relevant parties will comment on the PR if they disagree with any update suggested.
The RFC Editor will close the issue when it has been addressed either by accepting a pull request or simply by closing the issue if no changes are needed.
We have merged a [PR] (https://github.com/rfc-editor/draft-nottingham-avoiding-internet-centralization/pull/1) to encapsulate the necessary changes to take the document from I-D to RFC-to-be. All other edits and suggested changes can be reviewed as PRs and Issues.
If you would like to submit changes beyond those raised by the RPC, please create a pull request and identify one or more issues that the pull request closes in the comments.
If the RFC Editor creates the PR in response to issue comments, the RFC Editor will assign a reviewer for the PR and will expect feedback from the reviewer before merging the PR.
Once the content of the .md file is stable, the RPC will create an XML file. The following files will be provided for your review at that time:
To create your own output files, use the IETF Author Tools webservice.
If you would like guidance on using xml2rfc locally, please ask the RFC Editor.
More information on using GitHub to view diffs can be found here: Comparing commits.
Once the XML and output files have been created, the following diff files are available via www.rfc-editor.org:
This document is being edited in kramdown-rfc markdown. Once the content is stable, the markdown will be converted to RFCXML and formatted as an RFC. Your final approval means you approve both the content and the format.
To approve your RFC for publication, please reply to the AUTH48 email stating that you approve this RFC for publication. Please use REPLY ALL, as all the parties CC’ed on the message need to see your approval.
The details of the AUTH48 status of the document are here: https://www.rfc-editor.org/auth48/rfc9518
Note that this repo is available only during AUTH48. This repo will be archived after the RFC publication announcement is sent.
For any questions or concerns, please contact rfc-editor@rfc-editor.org. Note that push events will send notification messages to rfc-editor@rfc-editor.org.
If for some reason a participant wants to stop using GitHub and wants to use the current AUTH48 procedure, this can be accomodated. We have structured the repo and the experimental process to align with the current process and we can transition the AUTH48 from GitHub to email.