Hello Greg, Answers inline.
Sent from my iPhone > On Apr 1, 2014, at 9:34 PM, Gregory Mirsky <[email protected]> > wrote: > > Dear Authors, et. al, > please find my comments and questions to the latest version below. Thank you > for your kind consideration. > · Would you agree that use case document is more appropriate on > Informational rather than Standard track Indeed. I'll change it for -02. > · Introduction, second para > o Precomputation and instantiation of protection/backup paths is > characteristic of all protection mechanisms, local, segment and end-to-end. > o “The term "protection" is often used as a synonym for FRR.” I think that > it is “local protection” that is being equated and used interchangeably with > FRR. End-to-end protection, whether linear or ring, equally supports 10msec > fault detection as fault detection latency is not characteristic of > protection mechanism but of interval used in continuity check OAM Indeed. I'll fix it in next rev. > · Section 3 > o first sentence s/in/of/ Thanks for the catch. > o Does local protection in SPRING network domain takes into consideration > SID labels. If SID labels are not being considered when pre-calculating > backup tunnels then it is possible that after the switchover end-to-end path > fails. On the other hand, if SID labels being considered, then, in general > case, intermediate node must maintain path information, which is not as > Segment Routing paradigm being defined at this time. > Well now that the draft is not about solutions or specifics of SR, this is not a problem anymore :) More seriously, yes, in SR, you have to pay attention to label allocation when installing your failover entries in the FIB. However I do not see why it leads to having intermediate nodes maintain path information. Can you expand on this part of your comment? Cheers, Pierre. > Regards, > Greg > _______________________________________________ > spring mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/spring
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
