Progressing RFCs 5343, 5590, 5591, and 6353 to Internet Standard
status-change-5343-5590-5591-6353-to-internet-standard-00
| The information below is for an old version of the document |
| Document |
Proposed status change
|
|
Progressing RFCs 5343, 5590, 5591, and 6353 to Internet Standard
Snapshot
|
|
Last updated |
|
2014-01-03 |
|
Moves to Internet Standard |
|
RFC5591, RFC5590, RFC6353, RFC5343 |
|
State |
|
AD Review
|
| IESG |
Telechat date |
|
(None)
|
|
Shepherding AD |
|
Sean Turner
|
|
Send notices to |
|
wjhns1@hardakers.net, j.schoenwaelder@jacobs-university.de, ietfdbh@comcast.net, mundy@tislabs.com
|
RFCs 5343, 5590, 5591, 6353 and currently have an IETF standards
status of Draft Standard, which is now an obsolete status. This
note requests reclassifying it to Internet Standard.
(1) There are at least two independent interoperating implementations
with widespread deployment and successful operational experience.
Based on the IR (Interoperability Report)
(http://www.ietf.org/iesg/implementation/report-rfc5343-5590-5591-5953.txt)
there are at least two independent interoperating implementations with
widespread and successful operation experience.
(2) There are no errata against the specification that would cause a
new implementation to fail to interoperate with deployed ones.
There are no errata against RFC 5343, RFC 5590, RFC 5591, and
RFC 6353.
(3) There are no unused features in the specification that greatly
increase implementation complexity.
We believe there are no unused features in the specification that
greatly increase implementation complexity.
(4) If the technology required to implement the specification
requires patented or otherwise controlled technology, then the
set of implementations must demonstrate at least two independent,
separate and successful uses of the licensing process.
The criteria is N/A.