On June 5, 2022 at 7:23:03 PM, Sharon Barkai wrote: Sharon:
Hi! ... > I am attaching such a narrower problem rephrasing draft. > Was wondering if this direction is acceptable in your view. The updated Introduction is clearer, but maybe because I know what you want to do -- the first couple of paragraphs still contain a lot of words that give the impression that the document is about satisfying the geolocation and tracking threats. In fact, the forth paragraph starts by saying that the "issues are resolved by dataflow virtualization, or communication indirection...LISP overlay network-virtualization can offer such a solution". This is a bold claim that will need to be substantiated. It would serve the document if an analysis in line with rfc6973 of how LISP can address the specific threats is included. The (short) Privacy Considerations section in rfc6833bis includes some information that may be useful to build from. OTOH, rfc7835 leaves out any privacy considerations by arguing that "privacy definitions may vary for different scenarios". Well, you have one such scenario. It is important that it is made clear which aspects of the system are out of scope for LISP and are provided as an example. To be clear, I want to explicitly see the words "out of scope" prominently mentioned. The Notes help a little, but there is still a lot more detail than is necessary for a LISP document. For example, the AAA flow diagram, application packet formats, etc. In summary, I think the introduction helps, but there is still a lot of work to be done. BTW, to facilitate my review of the changes, I expect an inline reply to the comments. Thanks! Alvaro. _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
