Hi Jürgen, Thank you for your review and comments. Please see my replies as follows : 1. How is this extension deployed? [Yisong] It is deployed in networks where SR MPLS or SRv6 is used for unicast and PIM is used for multicast. 2. Can it be deployed incrementally or do all multicast routers have to understand the RPF Vector Attributes in the PIM Join packet to work properly? [Yisong] PIM MoFRR based on TILFA depending on the RPF Vector Attributes in the PIM join packet for RPF routing lookup, if the multicast router cannot understand the attributes, then it will not be possible to select the secondary upstream multicast hop (UMH) as expected, and the secondary multicast tree cannot be established. 3. And are there any further recommendations about debugging operational or deployment errors, are there procedures to verify that the calculated alternative routes or is this no different than with other fast multicast reroute mechanisms? [Yisong] PIM can select the secondary upstream relying on unicast repair path and establish the secondary multicast tree hop by hop. This mechanism is no different from existing multicast fast rerouting, except that the secondary upstream is selected based on unicast SR TILFA repair path instead of the unicast LFA repair path. We'll update a new version according to your comments. If you have further comments, please let us know. Best Regards Yisong Reviewer: Jürgen Schönwälder Review result: Has Nits I have reviewed draft-ietf-pim-mofrr-tilfa-05.txt. I am not deep into multicast routing and hence I look at the document from a general operational perspective. I found the document to be well written, the example topology to outline the limitations of existing approaches is much appreciated. How is this extension deployed? Can it be deployed incrementally or do all multicast routers have to understand the RPF Vector Attributes in the PIM Join packet to work properly? And are there any further recommendations about debugging operational or deployment errors, are there procedures to verify that the calculated alternative routes or is this no different than with other fast multicast reroute mechanisms? Editorial nits: - The acronym SID is used well before it is introduced on page 8, please introduce the acronyms where they are first used. |
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
