> Then we really have to write up use cases, settle on requirements and > decide on the protocol.
The original use case documents covered this specific situation. We decided to expand the use cases for future use, I think, which then led to trying to solve all the problems listed there in the first swack, and as one problem set. Part of this was merging all the different use cases into a single set of use case drafts that make the problem set appear (maybe) more unified than it really is. It's perhaps more logical to look at the use cases we have and break them back down into "now," and "later," and along clear lines of requirement sets. I don't think we've actually done that work yet. :-) Russ _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
