Dear all, This discussion focusses on an potential aspect of evolving documents that I didn't forsee, perhaps it helps if I clarify what I am looking for. 1) EDs do *not* carry the label of IETF-wide consensus, afterall, such consensus currently is not part not part of the potential publication process for EDs. 2) EDs are probably unsuitable for protocol specifications or protocol extensions, because of (1) 3) Where EDs can really shine is that they provide stable URLs with a short identifier (like the RFCs and BCPs) that can be referenced. I'm interested to see if we can develop a document type that can reflects a working group's understanding of a certain problem spaces (like tls settings, cyphers, bgp filters), has received review from subject matter experts (the working group participants), the WG chairs and perhaps the AD. If these people agree that something is worthwhile publishing on the stable URL; why not? Especially in context of elaborating on security aspects I believe there can be value in a more expedient publishing process. I'm looking for something that is a step up from a wiki page anyone can edit without supervision, something slightly different than a draft as drafts are what they are (maybe drafts are what a WG can promote to ED?). In any case, I'd like to have an open discussion whether we can device a mechanism that addresses some things that aren't exactly the best fit for the currently available options. I'm not interested to create something that could update RFCs. I suspect EDs can exist to provide more context around RFCs, such as use case documents, implementation reports, security-related recommendation. Kind regards, Job
