Deb Cooley has entered the following ballot position for draft-ietf-lisp-rfc6831bis-08: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6831bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks to Magnus Nyström for their secdir review. I am impressed at the work Vengada Prasad Govindan and the editors have done to clear discusses and address comments during this period of time! I support the discuss ballot by Gorry, that are about the use (or non-use) of BCP 14 language - clearly any requirement that is necessary for interoperability must use BCP 14 language. In addition, the use of the word 'will' might very well be normative, but might be difficult for an implementer to find. I encourage the use of obvious normative language (not necessarily BCP 14 style) to make it clear to an implementer what the actual requirements are to produce a compliant implementation. I support the comment by Ketan especially about the elevation from Experimental to Proposed Standard. The diff between RFC 6831 and this draft appears to be minimal and contains no information about either the outcome of the experiment nor what changes lead to the elevation of the specification. Appendix A lists the actual changes, but a statement in the Introduction which addresses 'why now?' would be useful. Section 13: I support the discuss by Mike Bishop. Normative References: Having a (recently) expired working group draft as a normative reference seems problematic (but necessary?). I am assuming that there is a plan... but if there is not, this draft will not be published as it stands today. _______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
