User Tools

Site Tools


github_auth48_experiments

Experiments Using GitHub During AUTH48

Introduction

This page summarizes the GitHub experiments that the RPC has held for documents going through AUTH48. Please follow the links to see details of the individual experiments.

To participate in an experiment, please see experiment setup to see if your document may qualify for consideration.

IETF 117 workshop on using GitHub during AUTH48

IETF 114 workshop on using GitHub during AUTH48

Experiments since IETF 114

Based on "Experiment 6" design discussed at the IETF 114 workshop

RFC 9345 RFC 9380 RFC 9366 RFC 9518
I-D draft-ietf-tls-subcerts draft-irtf-cfrg-hash-to-curve draft-ietf-sipcore-multiple-reasons draft-nottingham-avoiding-internet-centralization
Pages submitted 17 175 4 28
I-D approved 2022-10-03 2022-10-02 2022-11-02 2023-09-14
AUTH48 start 2023-01-30 2023-05-03 2023-02-16 2023-12-06
Publication 2023-07-13 2023-08-11 2023-03-07 2023-12-18
GitHub repo https://github.com/rfc-editor/draft-ietf-tls-subcerts https://github.com/rfc-editor/draft-irtf-cfrg-hash-to-curve https://github.com/rfc-editor/draft-ietf-sipcore-multiple-reasons https://github.com/rfc-editor/draft-nottingham-avoiding-internet-centralization
AUTH48 details
Time in state 22.3 weeks 14.1 weeks 2.1 weeks 1.7 weeks
# questions at start 10 21 2 9
Process notes github_exp_9345 github_exp_9380 github_exp_9366 github_exp_9518
Comparing with standard process
Concurrent Avg. AUTH48 time* 3.6 weeks 4.3 weeks 2.2 weeks 4.3 weeks
Avg. AUTH48 time for docs over 100 pages** N/A 5.7 weeks (n=8) N/A N/A
Avg. AUTH48 time for docs less than 30 pages*** 3.3 weeks (n=22) N/A 2.5 weeks (n=13) 3.3 weeks (n=25)

* using standard AUTH48 process for the 3 months preceding publication.
** using standard AUTH48 process and published in months preceding this document.
*** using standard AUTH48 process and published 2 months preceding this document.

In addition: RFC 9444 (draft-ietf-acme-subdomains), approved for publication in March 2023, did not become a GitHub experiment; see the process notes. It was 22 pages and spent 5.7 weeks in AUTH48 in the typical AUTH48 process.

Experiments 2018-2022

RFC 8446 RFC 8829 RFC 9069 RFC 9131 RFC 9245
I-D draft-ietf-tls-tls13-28 draft-ietf-rtcweb-jsep draft-ietf-grow-bmp-local-rib draft-ietf-6man-grand draft-eggert-bcp45bis
Pages submitted 156 115 15 24 11
I-D approved 2018-03-21 2018-03-01
(into MISSREF state)
2021-07-12 2021-07-20 2022-02-25
AUTH48 start 2018-06-14 2020-07-06 2021-10-18 2021-09-15 2022-04-07
Publication 2018-08-10 2021-01-20 2022-02-16 2021-10-01 2022-06-21
GitHub repo https://github.com/tlswg/tls13-rfc https://github.com/rtcweb-wg/jsep https://github.com/rfc-editor/rfc9069-AUTH48 https://github.com/rfc-editor/rfc9131-AUTH48 https://github.com/rfc-editor/draft-eggert-bcp45bis
AUTH48 details
Time in state 8.2 weeks 28.3 weeks 17.3 weeks 2.3 weeks 10.5 weeks
# questions at start 58 60
(yielded 78 issues in GitHub)
12 17 6
Process notes github_exp_8446 github_exp_8829 github_exp_9069 github_exp_9131 github_exp_9245
Comparing with standard process
Concurrent Avg. AUTH48 time* 3.2 weeks 10.1 weeks 12.5 weeks 13.3 weeks 12.7 weeks
Avg. AUTH48 time for docs over 100 pages** 4.4 weeks (n=7) 3.5 weeks (n=6)
Avg. AUTH48 time for docs less than 30 pages** 13.5 weeks (n=7) 7.1 weeks (n=6) 3.4 weeks (n=17)
github_auth48_experiments.txt · Last modified: 2024/02/16 11:17 by arusso