Hi, After only looking at diff on recent versions, I had the opportunity to re-read the whole -19.
Please find below some editorial comments. §2 " TI-LFA paths are activated from the instant the PLR detects a failure in a local link and remain in effect until the Interior Gateway Protocol (IGP) convergence at the PLR is fully achieved." [...] " TI-LFA paths are applied from the moment the PLR detects failure of a local link and until IGP convergence at the PLR is completed." Both sentences seem redundant to me. May be factorizing? --- §2 May be :s/ directred/ directed :s/T-LFA/TI-LFA --- §6 OLD: The TI-LFA repair path (RP) "RP" is never used in the document. So may be NEW: The TI-LFA repair path --- §6 "downstream node in PCP » PCP has never been defined. May be :s/PCP/PCPath --- §7 "7. Building TI-LFA repair lists » It seems to me that this section is (only) about building repair paths for Segment Routing Segments. (while in the general case, other type of FIB entries could be protected e.g., IPv4, IPv6, LDP) So may be NEW: Building TI-LFA repair lists for SR Segments Alternatively, covering the IPv4, IPv6 and LDP cases but it's beyond an editorial comment. --- §7.2 The active segment is an adjacency segment "However, this method may not provide the expected post-convergence path to the final destination as the expected post-convergence path may not go through F." I'm not at ease with this sentence which is mixing "post-convergence path" from the PLR to the destination, as used in the whole document, and the updated TE path from the SR source node to the destination. The PLR has zero ability to compute post-convergence TE Path, as it's not aware to the TE constraints. I would propose to move that sentence at the end of §7.2 and replace it with NEW: Note that any method is incapable of providing the post-convergence TE path that will be recomputed by the SR source node. --- §7.2.1 OLD: where RL(F) is the repair path for destination F. NEW: where RL(F) is the repair list for destination F. (by definition of RL, cf §1) Thanks, Regards, --Bruno ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ rtgwg mailing list -- rtgwg@ietf.org To unsubscribe send an email to rtgwg-le...@ietf.org
