RE: Design draft role, implementation requirements (Was: latest draft snapshot)

Do you disagree with putting a summary of requirements section
somewhere in the framework? 

If you do disagree, why?

Bora 

> -----Original Message-----
> From: James Kempf [mailto:[email protected]] 
> Sent: Friday, March 04, 2005 9:50 AM
> To: Bora Akyol; 'Jari Arkko'; 'Tschofenig Hannes'
> Cc: [email protected]
> Subject: Re: [Mobike] Design draft role, implementation 
> requirements (Was: latest draft snapshot)
> 
> 
> > I am fine with that, the problem is that this framework document is 
> > not sufficiently concise in the requirements area so that I can go 
> > ahead and write code off of.
> >
> 
> A framework document isn't ever sufficiently concise to write 
> code off of.
> It should be sufficiently concise to guide the design of the 
> protocol, which should be sufficiently precise to write code 
> off of. Or, at least, that is my understanding of the usual 
> relationship between framework documents and code design 
> (i.e. Proposed Standard) documents.
> 
> 
>             jak
>