Derek Atkins wrote:
Good question. There is a document on the process in general,
and "The Dao of the IETF". As for when a 'bis' document progresses
to Draft or stays at Proposed tends to be a combination of time,
effort, interop, and the amount of changes between the original
and new document. In particular, to go from Proposed to Draft
you generally can NOT add new features...
As an observation, I don't think too many features
have been added since 1999, so I can't see the
problem with that.
Moving to "draft standard" will be a secondary process once we finish
2440bis.
:-(
Okay, to make the later interop testing easier we should now really
consider to make all PGP2 things OPTIONAL or even remove them.
I personally think this is an excellent idea, but...
Eh, we can always drop that when we move to draft. Dropping
"features" is perfectly reasonable in Proposed -> Draft. The main
purpose of the interop testing is to see what's been implemented but
also to weed out what cannot be implemented (or hasn't been
implemented) and drop it from the draft _then_.
So, if we're going to Proposed now, as I suspect we are, then there's
no need to drop RFC1991 compatibility now. We can drop in 6ish months
later when we go to Draft.
That's encouraging. Cryptix already made the decision
several years back to drop pgp2 from our OpenPGP library.
It just doesn't make sense to maintain separate paths in
the code for such a small user base, our users are much
better served with us spending that time on applications.
iang