Hi all, I have one question and one comment regarding Section 3 of the draft<https://datatracker.ietf.org/doc/html/draft-bashandy-rtgwg-segment-routing-uloop-15#section-3>.
This section says (verbatim): The computation to turn a post-convergence path into a loop-free list of segments is outside the scope of this document. It is a local behavior at a node. In a future revision of this document, we may provide a reference approach to compute loop-avoiding policies for link up, link metric increase, link down, link metric decrease, node up, and node down events. TI-LFA Repair Tunnel I have checked the history of the draft, and the quoted text above did not change from the -00 version of the draft (posted on 12-May-2017). Question: Is there any intention to provide "a reference approach for computing loop-avoiding policies" (like what has been done in Section 6 of the TI-LFA draft)? Comment: The last sentence of the section is incomplete and out of context. Regards, Sasha Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
