This repository is for managing document updates for RFC-to-be 9366 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.
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.
The initial version of draft-ietf-sipcore-multiple-reasons.md is the same as what was approved for publication.
The current version of draft-ietf-tls-subcerts.md has been edited minimally for correctness. See PR #3.
The RFC Production Center's additional suggested updates have been added as PRs. 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 address them. Use the issue labels to indicate their 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.
- rfced-ready - the RFC Editor can update the document and/or close the issue based on the issue discussion.
Feel free to add new issues and PRs for new edits and questions.
The RPC Editor will close an 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 RPC editor creates the PR, the editor expects feedback from the reviewer before merging the PR.
Once the content of the .md file is stable and an XML file has been created, the following files will also be provided:
- https://www.rfc-editor.org/authors/rfc9345.html
- https://www.rfc-editor.org/authors/rfc9345.pdf
- https://www.rfc-editor.org/authors/rfc9345.txt
- https://www.rfc-editor.org/authors/rfc9345.xml
To create your own output files, use the tools webservice and select one of the output options.
Diffs via GitHub:
More information on using GitHub to view diffs can be found here: Comparing commits.
Note that we will use GitHub diff functionality throughout this process. Please view the diffs associated with the various PRs.
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.
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/rfc9366
Note that this repo is available only during AUTH48. Before the RFC publication announcement is sent, this repo will be 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.