> Beside the crypto document there is a call for adoption for the impact > document and a WG last call for the EID block management guidelines.
I just went through draft-saucez-lisp-impact-07.txt. Section 3 has some really good research and is explained well to understand the conclusion of the research. I applaud the authors for that. A comment or request for a reference, since you are talking about multicast replication engineering here you may want to add lisp-te as a reference here: > Even though it is its main goal, LISP is more than just a scalability > solution, it is also a tool to provide both incoming and outgoing > traffic engineering [S11], can be used as an IPv6 transition at the > routing level, and for inter-domain multicast [RFC6831], > [I-D.coras-lisp-re]. You should also add to this: > [I-D.coras-lisp-re] and [CDM12] propose a technique to construct xTR > based inter-domain multicast distribution trees. That there are signaling approaches like you indicated in RFC6831 as well as using LISP to signal in a reference to lisp-mr-signalling as well as using a signal-free approach as in lisp-signal-free-multicast. Those references would prove useful to readers. Other than that, this is a really well written document and ready for next step IMO. Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
