Folks,

The following are a few comments regarding draft-ietf-lisp-introduction-04. 
Expect further comments in the next few days.

- Section 1 adds no value. I agree with the editor's suggestion to remove.

- Section 2 is empty. So clearly, I agree with the editor's suggestion to 
remove.

- Section 3 contains a few broken definitions. But sooner or later, you will 
need a Glossary. So, I disagree with the editor's suggestion to remove the 
entire section. Please change the name of this section from "Initial Glossary" 
to "Glossary" or "Terminology". Then delete its contents. Then import whatever 
definitions you need, verbatim, from RFCs 6830-6836. This should cover most of 
the terminology that you need. It will also prevent you from redefining words. 
If you find that you still need to define a few terms, please do so.

- Section 4 adds no value. I agree with the editor's suggestion to remove.

- Section 5 adds no value. I agree with the editor's suggestion to remove.

- Section 7.3 needs to be rethought. LISP doesn't provide TE, in the same sense 
that MPLS does. It's quite different.

- Section 7.4 adds no value. I agree with the editor's suggestion to remove.

- Section 7.5 is not in charter. I agree with the editor's suggestion to remove.

- Section 7.7 is not in charter. I agree with the editor's suggestion to remove.

- Section 7.8 adds no value. I agree with the editor's suggestion to remove.

- Appendix A is redundant with Section 3. I agree with the editor's suggestion 
to remove

- Appendix B contains interesting information, but does not contribute to the 
goals of the draft. I agree with the editor's suggestion to remove it.

- Please add a short "Introduction" before the Glossary. It should read as 
follows:

"The Internet is experiencing problems A, B and C. LISP solves this problem by 
doing D, E and F. LISP will solve A, B and C because [....]

   D, E, and F distinguish LISP from existing routing protocols. The 
architectural tradeoffs associated with D, E and F are [....]. 


Standby for more comments.



Ron Bonica

_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to