Good question! Especially since we have a "chicken and
egg" issue here.  Personally, I'de like to see some
"example executions" of the current draft to get a
better understanding of how it works... and to spot
potential issues.

However, in the real (well, maybe ideal is a better
word) software engineering world, the "use cases"
would represent an expected "walk through" of the
application functionality ... from which requirements
would be derived ... then the applications, protocols,
etc would be implemented.

Interestingly enough, we already have the end-product.
 Hence, my interest in "examples" of the current
draft. I'de rather take what we've got and analyse the
"use cases" to determine suitability than to try to
re-derive the draft from scratch, although some might
disagree with me here :)

Since you put out the question Dick, what do you
propose?

--
James

--- Dick Hardt <[EMAIL PROTECTED]> wrote:

> Great to hear that James!
> 
> I think it would be useful for us all to agree what
> a use case is. :-)
> 
> On 23-Jan-06, at 11:29 AM, James Benedict wrote:
> 
> > If no one else volunteers, then i'll do it.  I'm
> > working on some use cases for myself anyways...
> still
> > trying to get a picture in my head of exactly what
> > this protocol is doing.
> >
> > I think in pretty (or at least ASCII) pictures :)
> >
> > --
> > James
> >
> > --- John Merrells <[EMAIL PROTECTED]> wrote:
> >
> >>
> >> If people want to offer up some use cases i'll
> >> wrangle them into an
> >> ID...
> >>
> >> (I'd rather somebody else did the editing on this
> >> draft though...)
> >>
> >> John
> >>
> >>
> >> _______________________________________________
> >> dix mailing list
> >> [email protected]
> >> https://www1.ietf.org/mailman/listinfo/dix
> >>
> >
> >
> > _______________________________________________
> > dix mailing list
> > [email protected]
> > https://www1.ietf.org/mailman/listinfo/dix
> >
> >
> 
> 
> _______________________________________________
> dix mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/dix
> 


_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix

Reply via email to