Reviewer: Brian Carpenter Review result: Ready with Issues Gen-ART Last Call review of draft-ietf-bess-mvpn-expl-track-10
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>. Document: draft-ietf-bess-mvpn-expl-track-10.txt Reviewer: Brian Carpenter Review Date: 2018-10-02 IETF LC End Date: 2018-10-09 IESG Telechat date: Summary: Ready with issues -------- Comments: --------- I agree with the point raised in the Routing Area review (be explicit about the updated sections of RFC 6514, 6625, and 7524). Minor issues: ------------- As I understand it, if a network only partially supports the new (LIR-pF) flag, it doesn't work properly. So we find at the end of section 2: ....the ingress node can conclude that the egress node originating that Leaf A-D route does not support the LIR-pF flag. The software at the ingress node SHOULD detect this, and should have a way of alerting the operator that the deployment is not properly configured. I don't see why this is only a SHOULD, and I don't see why the operator alert is not a MUST too. Surely the operator always needs to be alerted? _______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
