This repository is for managing document updates for RFC XXXX during AUTH48. This is part of the pilot 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:
- Issue tracking
- Pull requests (PRs)
- @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.
This document is being edited in RFCXML. Your approval means you approve both the content and format of the document, and the RFC is ready for publication.
The initial version of rfcXXXX.xml is a copy of the Internet-Draft (in XML) as it was approved for publication. A PR has been created that contains all the edits made by the RFC Production Center. This emulates the starting state of the current AUTH48 procedure. For the issues, provide your answers in the comments or add PRs to address them.
Feel free to add new issues and PRs for new edits and questions. Use @mention to identify the participant who should answer.
For any PRs created by the RFC Production Center, the editor expects feedback from at least one reviewer before merging the PR. We expect the other relevant parties will speak up if they disagree with any update.
The RFC 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.
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.
In addition to the files available in GitHub, the following files are available for your review:
- https://www.rfc-editor.org/authors/rfcNNNN.html
- https://www.rfc-editor.org/authors/rfcNNNN.pdf
- https://www.rfc-editor.org/authors/rfcNNNN.txt
- https://www.rfc-editor.org/authors/rfcNNNN.xml
To create your own output files, use the IETF Author Tools webservice.
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/rfcNNNN-diff.html (all changes since the document entered the RFC Editor Queue)
- https://www.rfc-editor.org/authors/rfcNNNN-rfcdiff.html (side-by-side view of all changes since the document entered the RFC Editor Queue)
Authors 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.
ADs - To approve any changes that are beyond editorial, please reply to the AUTH48 email (using REPLY ALL) so everyone is aware of the approval.
The details of the AUTH48 status of the document are here: https://www.rfc-editor.org/auth48/rfcNNNN
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 and CC auth48archive@rfc-editor.org. Note that push events will send notification messages to auth48archive@rfc-editor.org.
If for some reason a participant (including the RPC) wants to stop using GitHub and wants to use the current AUTH48 procedure, this can be accomodated. We have structured the repo and the pilot process to align with the current process and we can transition the AUTH48 from GitHub to email.