This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
github_auth48_experiment [2021/02/05 12:02] arusso |
github_auth48_experiment [2021/02/05 12:12] arusso |
||
---|---|---|---|
Line 5: | Line 5: | ||
^ ^ RFC 8446 | ^ ^ RFC 8446 | ||
| I-D | [[https:// | | I-D | [[https:// | ||
+ | | I-D approved | ||
| AUTH48 start | | AUTH48 start | ||
| Publication | | Publication | ||
Line 17: | Line 18: | ||
* status of this memo | * status of this memo | ||
* section movement to meet the style guide requirements (e.g., move acks and contribs to appear at the end) | * section movement to meet the style guide requirements (e.g., move acks and contribs to appear at the end) | ||
- | - RFC Editor goes through the EDIT and RFC EDITOR process states and sends an email with a link to the XML file created in step 2 and the edited XML file at the start of AUTH48. | + | - RFC Editor goes through the EDIT and RFC EDITOR process states and sends an email with a link to the XML file created in step 2 and the edited XML file at the start of AUTH48. |
- At the start of AUTH48, the author will create a Pull Request (PR) with the changes proposed by the RPC. The authors respond and point to the repository they created. | - At the start of AUTH48, the author will create a Pull Request (PR) with the changes proposed by the RPC. The authors respond and point to the repository they created. | ||
- The relevant people from the RPC will subscribe to notifications from that repository using the “Watch” button and confirm they are watching. For this test case, Heather, Adam, and Martin will follow along as well. | - The relevant people from the RPC will subscribe to notifications from that repository using the “Watch” button and confirm they are watching. For this test case, Heather, Adam, and Martin will follow along as well. | ||
Line 28: | Line 29: | ||
- If the authors don't approve, they update the RPC's PR and we go back to step 4. | - If the authors don't approve, they update the RPC's PR and we go back to step 4. | ||
- Final approval for the full document needs to result in an explicit email to the the RPC from each author indicating approval. GitHub will be used for editorial discussion, but the final text approval will be done via email. | - Final approval for the full document needs to result in an explicit email to the the RPC from each author indicating approval. GitHub will be used for editorial discussion, but the final text approval will be done via email. | ||
- | |||
- | ==== Relevant Documents ==== | ||
- | |||
- | * **[[https:// | ||
- | * 2018-03-21: approved for publication as an RFC. | ||
- | * 2018-06-14: initiated AUTH48. provided XML file as described in step 2 above. | ||
- | * 2018-08-10: published as RFC 8446 | ||
- | * **[[https:// | ||
- | * 2018-03-01: approved for publication as an RFC. (in MISSREF because of normative references that are not yet approved) | ||
==== Evaluation Criteria (defined in 2018) ==== | ==== Evaluation Criteria (defined in 2018) ==== | ||
Line 67: | Line 59: | ||
* 8.2 weeks | * 8.2 weeks | ||
* Number of questions at start of AUTH48: 58 | * Number of questions at start of AUTH48: 58 | ||
- | [[https:// | ||
=== Notes === | === Notes === |