Re: [bess] Rtgdir last call review of draft-ietf-bess-mvpn-fast-failover-11

2020-10-28 Thread Adrian Farrel
Hi again, Thanks for rapid convergence. All good. Adrian Section 3 notes that the procedure (presumably the procedure defined in this section) is OPTIONAL. I didn't see anything similar in sections 4 and 5 stating that those procedures are optional. Presumably, since this document

Re: [bess] Rtgdir last call review of draft-ietf-bess-mvpn-fast-failover-11

2020-10-28 Thread Adrian Farrel
Hello Greg, Thanks for this. I’m cutting down to places where we still need to interact. Look for [af] and blue text. Nothing alarming. Best, Adrian Section 3 notes that the procedure (presumably the procedure defined in this section) is OPTIONAL. I didn't see anything similar in

Re: [bess] Rtgdir last call review of draft-ietf-bess-mvpn-fast-failover-11

2020-10-20 Thread Greg Mirsky
Hi Adrian, thank you for the review, detailed questions, and helpful suggestions. I'll work through and respond within several days. Regards, Greg On Mon, Oct 19, 2020 at 1:09 PM Adrian Farrel via Datatracker < nore...@ietf.org> wrote: > Reviewer: Adrian Farrel > Review result: Has Issues > >

[bess] Rtgdir last call review of draft-ietf-bess-mvpn-fast-failover-11

2020-10-19 Thread Adrian Farrel via Datatracker
Reviewer: Adrian Farrel Review result: Has Issues Hello, I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request.