On 2019-08-01 11:47 -0500, Gavin Brown <[email protected]> wrote:
Forgive my ignorance, but what's the difference between a Draft Standard and a
Proposed Standard?
"Draft Standard" was mostly discontinued in 2011, so just "Standard".
But basically the difference between Proposed Standard and just Standard
is verified existence of at least two independent operating
implementations **with widespread deployment and successful operational
experience.**
(emphasis mine for the last part, because, if back to EPP discussion,
one has to think about what widespread means in case of closed business
setup like registry-registrar, do you count by number of registries?
number of registrars? number of domains affected by the change? etc.)
In more details, see RFC6410:
This document changes the Internet Standards Process defined in RFC
2026 [1]. In recent years, the Internet Engineering Task Force
(IETF) witnessed difficulty advancing documents through the maturity
levels: Proposed Standard, Draft Standard, and finally Standard.
....
The primary aspect of this change is to revise the requirements for
advancement beyond Proposed Standard. RFC 2026 [1] requires a report
that documents interoperability between at least two implementations
from different code bases as an interim step ("Draft Standard")
before a specification can be advanced further to the third and final
maturity level ("Standard") based on widespread deployment and use.
In contrast, this document requires measuring interoperability
through widespread deployment of multiple implementations from
different code bases, thus condensing the two separate metrics into
one.
....
This document replaces the three-tier maturity ladder defined in RFC
2026 [1] with a two-tier maturity ladder. Specifications become
Internet Standards through a set of two maturity levels known as the
"Standards Track". These maturity levels are "Proposed Standard" and
"Internet Standard".
--
Patrick Mevzek
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext
