Hi Mohamed, Thanks again for your comments. They should be addressed by rev -18.
See my previous message to the list for the details. Thanks, Fabio From: lisp <[email protected]> on behalf of "[email protected]" <[email protected]> Date: Monday, January 28, 2019 at 11:50 PM To: Luigi Iannone <[email protected]>, "[email protected] list" <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [lisp] WG Last Call for LISP-SEC (draft-ietf-lisp-sec-17.txt) Hi Luigi, all, FWIW, please find some comments to this document at : * pdf: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-lisp-sec-17-rev%20Med.pdf * doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-lisp-sec-17-rev%20Med.doc These are easy to fix. Cheers, Med De : lisp [mailto:[email protected]] De la part de Luigi Iannone Envoyé : lundi 28 janvier 2019 14:30 À : [email protected] list Cc : [email protected] Objet : [lisp] WG Last Call for LISP-SEC (draft-ietf-lisp-sec-17.txt) Hi All, since work on bis documents is re-starting to move forward it is about time to move forward other pieces of the LISP ecosystem. As such the LISP Security document has been revised a while ago for two reason: - Make sure is PS quality - Make sure it is compliant with latest changes in the bis documents. The second point has been re-checked by the authors just last week, and seems we are ready to move the document forward. This email open the usual two weeks Working Group Last Call, to end February 11th, 2019. Please review this WG document and let the WG know if you agree that it is ready for handing to the AD. If you have objections, please state your reasons why, and explain what it would take to address your concerns. Thanks Luigi & Joel
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
