To amplify Dino's response, it is not anticipated that any of the
changes that might still be needed to rfc6833bis would affect rfc8113bis
in any way. Of course the unanticipated can happen, and we will make
sure the IESG is informed if it does.
Yours,
Joel
On 1/22/19 10:33 PM, Dino Farinacci wrote:
Regarding your comment on 6833bis, we are waiting to hear from the reviewers if
the many updates we made are satisfactory.
Dino
On Jan 22, 2019, at 7:28 PM, Ben Campbell <[email protected]> wrote:
Ben Campbell has entered the following ballot position for
draft-ietf-lisp-rfc8113bis-02: 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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.
The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc8113bis/
----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
ยง4: Is 6833bis likely to progress soon? Is their risk of changes there that
might invalidate this statement?
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
