Re: Last Call - and wsc-usecases

> > At the time, I said that meant we needed to move the last call of
> > wsc-usecases back substantially, and I did so.
> 
> I think having it in June makes sense; we should be able to proceed
> on the issues in time for that.

But it's not "finalized" til the next November. That's the part that 
shifted. 

> BTW, we need to think about who takes the lead on getting back to
> the various commentors with explanations of what we did.  I'd hope
> Bill takes this on as part of his overall role.

I think you need to say a lot more about what has to happen here. Got 
another process pointer? I'm unfamiliar with what "getting back to" 
requires, or even usually entails. 

> Well, wsc-usecases is a note in the first place.  There's nothing in
> the process to keep us from updating it.  The Last Call is, however,
> a promise toward the community that we're not planning to do major
> changes to the note once the Last Call (and handling of LC comments)
> is over.

Is adding to the list of security context data "major"? If not, then I'm 
OK with that. 

> The main question that the current schedule creates in my mind is
> whether the "initial consensus on recommendations" milestone is even
> close to being realistic.


If we don't have an initial concensus by July, we slip the end date of our 
charter (recommendations by June 08). We have no more slack in our 
schedule. What process do we need to invoke if we see that happeneing?

If you think we need another f2f, please do start the discussion/planning. 
Be warned, my September schedule is a train wreak (so perhaps the first 
step is a questionnaire to get a feel from the group about who would come 
to one, when). 

        Mez