Brian,
Your description of the process omitted the most
time-consuming part:
for {each normative reference}
if {at lower maturity level AND downref acceptable}
then {write justification why downref is acceptable}
else {repeat process recursively to bring reference to DS}
A while ago Tero Kivinen wrote a script for automatically finding
the required documents; according to the script, to bring IPsec to
DS you'd need to upgrade somewhere between 70 and 400 (if I recall
correctly) documents. (The number is fuzzy because older documents
didn't separate normative and informative references. And some of
those references could be justified as acceptable downrefs or
re-classified as informative.)
Whatever the correct figure is (it's anyway dozens of documents),
it's also quite obvious that nobody will ever do the process.
For RFC 2195 (an extension to IMAP), you'd probably need to bring
IMAP to DS first.
Best regards,
Pasi
-----Original Message-----
From: ext Brian E Carpenter [mailto:brc(_at_)zurich(_dot_)ibm(_dot_)com]
Sent: 06 September, 2006 12:57
To: Frank Ellermann
Cc: ietf(_at_)ietf(_dot_)org
Subject: Re: what happened to newtrk?
Okay, let's nail this, I like to see 2195 and 3464 as DS,
what exactly can I do ?
3464 is already DS according to the RFC Index.
For 2195, write and publish an interoperability report, and
if {all mandatory and optional features shown to interoperate}
then {send a request to reclassify RFC 2195 to the IESG}
else {publish a draft-ellermann-2195bis with
non-interoperable features removed};
{send a request to approve it as DS to the IESG}
It's better if you find a willing AD first, and work with him
or her instead of the IESG as group.
Brian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf