{"id":2412,"date":"2023-09-06T20:35:46","date_gmt":"2023-09-07T03:35:46","guid":{"rendered":"https:\/\/self-issued.info\/?p=2412"},"modified":"2023-09-06T20:35:46","modified_gmt":"2023-09-07T03:35:46","slug":"adoption-time-and-lessons-learned","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=2412","title":{"rendered":"Adoption Time! And Lessons Learned\u2026"},"content":{"rendered":"

\"IETF<\/span>I’ve had two different IETF specifications adopted by two different working groups in the last two days – a pleasant coincidence! Yesterday, the COSE “typ” (type) Header Parameter<\/a> specification was adopted by the COSE working group. Today, the OAuth 2.0 Protected Resource Metadata<\/a> specification was adopted by the OAuth working group. Their journeys from individual drafts to working group drafts couldn’t have been more different!<\/p>\n

As I was musing with Phil Hunt<\/a>, who wrote the original individual draft of OAuth 2.0 Protected Resource Metadata<\/a> with me, I\u2019m pretty sure that this is the longest time from writing an individual draft to it becoming a working group draft<\/a> in my experience: August 3, 2016 to September 6, 2023 \u2013 seven years and a month!<\/p>\n

Whereas, the time from the individual draft of COSE “typ” (type) Header Parameter<\/a> to the first working group draft<\/a> was only three months: July 8, 2023 to September 5, 2023. Which got me thinking… Is that the fastest progression I’ve had?<\/p>\n

It turns out that my fastest time from individual draft to working group draft was for the JWK Thumbprint URI specification which I wrote with Kristina Yasuda<\/a>. It went from individual draft<\/a> to working group draft<\/a> in only two months: November 24, 2021 to January 28, 2022. (And it became RFC 9278<\/a> on August 9, 2022 – less than nine months from start to finish, which I believe is also a personal record.)<\/p>\n

Ironically, while OAuth 2.0 Protected Resource Metadata took over seven years from individual to working group drafts, a closely-related draft, OAuth 2.0 Discovery (which became RFC 8414<\/a>) was previously my fastest from individual draft<\/a> to working group draft<\/a>: 2.5 months! (The journey to becoming an RFC took 2.5 years.)<\/p>\n

The other relative speed demon was Proof-Of-Possession Semantics for JSON Web Tokens (JWTs): 3.5 months from individual draft<\/a> to working group draft<\/a> and two years from start to RFC 7800<\/a>.<\/p>\n\n

What are my takeaways from all these musings about starting things?<\/p>\n