protocol progress (again!)

Folks,

This is the third time Magnus and I have asked about this,
without getting a clear concensus as to the WG position. 

This time, there's a default that Magnus and I have already 
agreed we'll recommend to the ADs if we don't get clear 
concensus, (but we're not saying which it is just yet, to 
try encourage you to answer:-).

As you know, the position is that the timing of the progression 
of the SASL-SRP draft is now in question, as reflected in the 
last meeting minutes. Since we currently have a mandatory to
implement dependency on this, that leaves us with four options 
as I see it:

A. Do nothing at all - just wait and see what happens and don't
produce any new drafts until the SASL-SRP position is clarified
which will probably take at least months.

B. Quit. We wrap up the WG and allow the protocol draft to
expire, but progress a version of the framework draft to show
we once existed.

C. Change the protocol draft to use something we know won't get
stuck in the IESG for process reasons. Magnus made a specific 
suggestion for this previously that we'd have to finalise on 
the list in the event we get clear concensus on this option
(which we need to get to proceed with it).

D. Finish off the current protocol draft, keeping the use of
SASL-SRP, and let the IESG worry about the process issues, in 
the knowledge that they're really quite likely to either park 
the draft (option A) or push it back to us (resulting in option 
B or C).

Can you express your preference over the next few days? (Note:
In the absence of clear concensus on this emerging over the 
next week, Mangus and I will simply annouce our preferred option 
to the list and the ADs.)

Regards,
Stephen.

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:[email protected]
Ireland                             http://www.baltimore.com