Sure, but getting all that in one diagram really requires a papyrus
scroll. I'll leave that to a more accomplished digital artist.
Regards
Brian Carpenter
On 28-Feb-22 19:13, Joel M. Halpern wrote:
I would have thought that the primary thread that would be useful to be
shown for a draft is:
Individual draft
discussion and improvement
WG adoption (no details, just that it usually occurs)
discussion and improvement
WG Last Call w/ discussion
AD Review w/ discussion
IETF Last Call w/ discussion
IESG Approval w/ discussion
editing
Publication
With some notation somewhere that advancement along that sequence is not
guaranteed.
Yours,
Joel
On 2/28/2022 1:03 AM, Brian Carpenter wrote:
There are quite a few things missing. The challenge is where to stop,
and how much detail do you want in tutorial diagram.
Regards,
Brian Carpenter
(via tiny screen & keyboard)
On Mon, 28 Feb 2022, 17:52 touch@xxxxxxxxxxxxxx
<mailto:touch@xxxxxxxxxxxxxx>, <touch@xxxxxxxxxxxxxx
<mailto:touch@xxxxxxxxxxxxxx>> wrote:
I think you left out WGLC.
Joe
—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com <http://www.strayalpha.com>
On Feb 27, 2022, at 7:44 PM, Brian E Carpenter
<brian.e.carpenter@xxxxxxxxx <mailto:brian.e.carpenter@xxxxxxxxx>>
wrote:
On 28-Feb-22 14:15, Michael Richardson wrote:
I think that 97% of how an internet-draft becomes an RFC will not
be changing
as a result of the RSCE.
I'd say 100%. I'm no good at videos or poetry, but I can work
LibreOffice.
An attempt at a diagram (two pages) is at
https://www.cs.auckland.ac.nz/~brian/id-flow.pdf
<https://www.cs.auckland.ac.nz/~brian/id-flow.pdf>
As far as AUTH48 goes, it corresponds to current practice.
I'm more than happy to put the source file on github if anybody's
interested.
Brian
_______________________________________________
rfc-interest mailing list
rfc-interest@xxxxxxxxxxxxxx <mailto:rfc-interest@xxxxxxxxxxxxxx>
https://www.rfc-editor.org/mailman/listinfo/rfc-interest
<https://www.rfc-editor.org/mailman/listinfo/rfc-interest>
