[saag] Re: NIST
Carsten Bormann <[email protected]>
| Newsgroups | gmane.ietf.saag |
|---|---|
| Message-ID | <[email protected]> |
On 2025-02-07, at 19:51, Bret Jordan <[email protected]> wrote: > > how the process is supposed to work to get work done in other SDOs/SSOs published in the IETF as an RFC. I’m not sure whether you actually mean it when you say “in the IETF”. There are multiple streams of RFCs, and the IETF stream is one of them. So I would translate “in the IETF” into “in the IETF stream”, and we generally only publish documents in the IETF stream that have IETF consensus. I would expect IETF to have change control over such a document. An alternative way to publish RFCs from work of other SDOs (or organizations in general) is to publish not in the IETF stream, but in the Independent Stream. IESG can still advise the ISE (Independent Stream Editor) not to publish if it believes the document would be detrimental to the Internet or that it is an end-run around a WG. The ISE usually runs their own review process; this is not like giving the IETF change control but still amounts to a bit of what has been humorously called “adult supervision”. Grüße, Carsten _______________________________________________ saag mailing list -- [email protected] To unsubscribe send an email to [email protected]