All,
I have completed by AD Evaluation of draft-ietf-lisp-introduction
as a part of the IETF publication process. I have some
comments/questions that should be resolved prior to starting an IETF
Last Call. Please let me know if you have any questions on these...1. Section 1 * I am going to try and short-circuit the inevitable question that will arise about the reference [Chiappa]. Since it is a web page, the RFC Editor will be concerned by its long-term stability. Is that the best reference for that text? Anything similar that has been published in a conference/journal/RFC/etc.? * The text uses the terms underlay and overlay without any context (in the summary bullets). This is easily fixed by augmenting the text in the 2nd paragraph to identify which networks form the underlay and the overlay. 2. Section 3 (and a few times in 3.5) : s/inetrworking/internetworking/ 3. Section 3.2 * Is it correct to say that EIDs are only routable at the edge? This seems to contradict the text in section 3.5 that says EIDs may be injected in the global routing system. * I find the PI and PA analogies misleading. EIDs are global, but they may change their point of attachment. If that occurs, you are not guaranteed that your EID space does not change. * In the example, bullet four mistakenly says that the destination address of the outer header is set to RLOC_B2 (it should be RLOC_b1). 4. Section 3.3.1 introduces the term RTR (Reencapsulating Tunnel Routers) with no real description of how it functions or relates to ITRs and ETRs. 5. Section 3.4.3 makes reference to the LISP WG. Given that this document will probably outlive the WG, I would suggest re-wording to remove a direct reference to the WG. 6. Section 3.4 has no discussion of EIDs and NATs. Given the global nature of the mapping system, it would seem that NATs don't play well with LISP. There should be some discussion of that. 7. Section 4.1 * s/requires of a /requires a/ * The discussion of SMR should contain a reference to 6830 or a brief discussion of how the SMR is used. 8. Section 5 * I would suggest having a reference to both the MIP and the NEMO specs when discussing mobility. LISP has the potential to operate in a manner conducive with NEMO if the xTR acts as the NEMO Mobile Router. * Should there be some discussion of the mapping system's TTL mechanism impact on mobility support? 9. Section 9 talks about propagating multicast state as (S-EID, G). Does that mean that multicast in LISP is really only allowed to be SSM? 10. I am surprised that there are 2 Security Consideration sections (7 & 9). I am even more surprised that one says "Nothing new here" and the other actually discusses potential issues with the LISP approach. Regards, Brian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
