I reviewed today's slides and the Jabber logs and have a few comments: Does the introduction document try to do too much?
Would simpler be better in this case? My thought is that as an introduction, it should address: * The background problem/proposed solution. * "what's in it for me" - the use cases that this architectural change brings to the table. * The life of the packet to introduce all the elements in context demonstrating their use. Many of the other sections, for example, 7, 11, and 12 all seem to be more applicable and relate more to the architecture than the intro document. Paul
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
