[hybi] requirements document is a milestone (was Re: Ticket#1 Http Compliance)

[Salvatore Loreto <[e-mail]>]

(as chair)

I am not going to spend time to describe the benefit and the opportunity 
to have a list of requirements
before starting to design a protocol!

this wg agreed to have a requirement document, and we have it in the 
charter as mailestone:
http://tools.ietf.org/wg/hybi/charters

I agree with the Anne proposal to indicate if to satisfy a requirement 
are necessary change to the
current version or the protocol.
This is a really good proposal!

I do not think that we should be afraid to the change the current protocol,
in fact as someone as highlighted in another thread
"/we do not yet believe that Web Sockets are at the point where breaking 
changes are yet a problem/"

so I invite everybody to provide only constructive feedback to the 
discussion and moreover not
start a discussion related to the process in a thread related to a 
technical issue!!!
This "Ticket#1 Http Compliance" thread is to discuss the opportunity for 
the protocol to be
HTTP compliant until both ends have agreed that the HTTP connection has 
been upgraded.
If do not want this requirement (that by the way was already discussed 
during the face to face
meeting in Anaheim) please just say it, perhaps explaining why not... 
and we will consider
your opinion as well all the other opinion that will be provided!

If you do want talk about it, please start a separate thread with a 
clear subject!


cheers
Sal


On 5/13/10 3:53 PM, Anne van Kesteren wrote:
> On Thu, 13 May 2010 14:33:20 +0200, Greg Wilkins<[e-mail]>  wrote:
>    
>> Is it a requirement to have a requirements document?
>>      
> I don't know, but in my experience going back to requirements when there
> already is a draft specification is counter-productive. We'll get the same
> debates, only now with more meta. I, for one, am not looking forward to it.
>
>
>    


-- 
Salvatore Loreto
www.sloreto.com