Last Call Review of draft-ietf-bess-vpls-multihoming-05
review-ietf-bess-vpls-multihoming-05-opsdir-lc-bradner-2020-03-11-00
Request | Review of | draft-ietf-bess-vpls-multihoming |
---|---|---|
Requested revision | No specific revision (document currently at 05) | |
Type | Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2020-03-12 | |
Requested | 2020-02-27 | |
Authors | Bhupesh Kothari , Kireeti Kompella , Wim Henderickx , Florin Balus , Jim Uttaro | |
I-D last updated | 2020-03-11 | |
Completed reviews |
Rtgdir Last Call review of -05
by Ben Niven-Jenkins
Genart Last Call review of -05 by Joel M. Halpern Opsdir Last Call review of -05 by Scott O. Bradner |
|
Assignment | Reviewer | Scott O. Bradner |
State | Completed | |
Request | Last Call review on draft-ietf-bess-vpls-multihoming by Ops Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/IhktuJcgFn1cFd9R7zlUzuJ729E | |
Reviewed revision | 05 | |
Result | Has nits | |
Completed | 2020-03-11 |
review-ietf-bess-vpls-multihoming-05-opsdir-lc-bradner-2020-03-11-00
This is an OPS-DIR review of BGP based Multi-homing in Virtual Private LAN Service - draft-ietf-bess-vpls-multihoming This is a complex document but it is reasonably understandable two minor text questions/suggestions section 3.5 current text: For the use case where a single PE provides connectivity to a set of CEs from which some on multi-homed and others are not, only single pseudowire MAY be established. would it be better to replace the last phrase with "at most one pseudowire MAY be established” or at least "only a single pseudowire MAY be established" later in the same paragraph add an "a" before "single pseudowire" section 6 end of sentence add "the procedures" "...co exist in the network with PEs or Route Reflectors that do support the procedures. on the operations side: I do not see specific operational issues but do worry a bit about the level of complexity getting in the way of reliable configuration and operation but I do not see what can be done about that I trust there will be an associated document that details monitoring hooks (e.g. a YANG module) so that an operator could watch what is going on