Note: RFC 9131 has been published and this repository has been archived.
This repository is for managing document updates for RFC 9131 during AUTH48.
Please see the license. The IETF Note Well applies.
GitHub features that will be used:
- Issue tracking
- Pull requests
- @mentions
Authors, AD, WG chairs, and document shepherd, 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.
Questions and FYIs from the RFC Editor have been added as issues. Please provide your answers in the comments and use a label to indicate issue status:
- rfced - initial label of RFC Editor questions and FYIs (keep this label if the issue is still active).
- question - a follow-up question has been added to the issue discussion. Use @mention to identify the participant who should answer.
- AD approval required - the resolution of the issue requires the AD to review and approve the change.
- editor-ready - the RFC Editor can update the document and/or close the issue based on the issue discussion.
Feel free to add new issues for new edits and questions.
The editor will close the issue when it has been addressed either by accepting a pull request or simply closing the issue if no changes are needed.
If you would like to submit changes, please create a pull request and identify one or more issues that the pull request closes in the comments.
For the ease of all reviewers, please do not use inline comments on pull requests.
Output files may be viewed here:
- https://www.rfc-editor.org/authors/rfc9131.txt
- https://www.rfc-editor.org/authors/rfc9131.html
- https://www.rfc-editor.org/authors/rfc9131.pdf
To create your own output files, use the xml2rfc webservice and select either the v3-plaintext or v3-HTML output options.
If you would like guidance on using xml2rfc locally, please ask the editor.
Diffs via GitHub:
More information on using GitHub to view diffs can be found here: Comparing commits.
The following diff files are available via www.rfc-editor.org:
- https://www.rfc-editor.org/authors/rfc9131-diff.html (all changes since the document entered the RFC Editor Queue)
- https://www.rfc-editor.org/authors/rfc9131-rfcdiff.html (all changes since the document entered the RFC Editor Queue side by side)
- https://www.rfc-editor.org/authors/rfc9131-auth48diff.html (all changes made in AUTH48)
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/rfc9131
Note that this repo is available only during AUTH48. Before the RFC publication announcement is sent, this repo will be made private and archived.
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.