Alvaro Retana has entered the following ballot position for draft-ietf-trill-smart-endnodes-10: Discuss
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-trill-smart-endnodes/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- This document feels tightly coupled with draft-ietf-trill-directory-assisted-encap, even though there are no cross-references. If I understand the mechanisms correctly, a Smart Endnode (discussed in this draft) can then do directory assisted encapsulation (described in draft-ietf-trill-directory-assisted-encap). In fact, the encapsulation/decapsulation seems to be the main motivation in defining a Smart Endnode. I think then that this document also falls short in the exploration of potential issues, so I am also balloting DISCUSS. The same cases that I pointed at for draft-ietf-trill-directory-assisted-encap [1] are applicable here -- with the added caveat that the Smart Endnode, in general, has other sources of information (learning, etc.), which means that there are potentially more doors to close. The Multi-homing Scenario (Section 6) adds some complexity to the ability to check whether the Ingress RBridge is set correctly in the encapsulation. It would be nice to explore this case a little further and highlight the issues as the topologies get more complex. As I wrote in [1], I don't think that there are easy mitigations for these issues, but at least mentioning them so that operators are aware of the risk would be enough to clear this DISCUSS. Given that the authors partially overlap, it may be a good idea to solve the issue in this document (which is the general case) and then just have the other one point this way. [1] https://mailarchive.ietf.org/arch/msg/trill/xZvEj_9FtSgHSp4DnKCVxr670gc/?qid=1e5a9496ac80237a3f7cc6aeea09d24d _______________________________________________ trill mailing list trill@ietf.org https://www.ietf.org/mailman/listinfo/trill
