I don't think we should stress "independent" any more than we should stress trying to find a one size fits all solution. While there may be different use-cases, there is also a huge amount of commonality between what any of the solutions needs to achieve. So maybe lets just say "other protocols & proposals". Note - while my name is down against this section, I don't want to monopolize the whole 15m. If anybody anticipates wanting to speak during this period - please contact me and we can divide up the time - plus leave time for others to speak from the floor... or move into the following open discussion earlier than scheduled. cheers Pieter Hintjens wrote: > On Tue, Nov 3, 2009 at 7:28 PM, Salvatore Loreto > <salvatore.loreto at ericsson.com> wrote: > >> You are absolutely right, maybe alternative is not the right word, >> I should have used something like "different" prospective or >> even more explicitly "different problem/solution space"! > > What we have, I think, are a set of independent specification projects > in progress, each addressing part of the overall problem space. That > leads us to questions of what exactly their problem spaces are, what > their status is in terms of implementation and proof, and what scope > there is for coordination, competition and/or interoperability. > > Greg, Ian, does that sound right or am I being presumptuous here? > > -Pieter > _______________________________________________ > hybi mailing list > hybi at ietf.org > https://www.ietf.org/mailman/listinfo/hybi
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.