IP Algorithm SUBTLV indicate the participation for particular flex algo by node. Participation doesn't depend on whether it support ipv4 prefix or ipv6 prefix. Node which doesn't support particular family will not install that family route.
Regards Parag Juniper Business Use Only From: Lsr <[email protected]> On Behalf Of Dongjie (Jimmy) Sent: Wednesday, December 9, 2020 3:40 PM To: Acee Lindem (acee) <[email protected]>; lsr <[email protected]> Subject: Re: [Lsr] WG Adoption Call for "IGP Flexible Algorithms (Flex-Algorithm) In IP Networks" - draft-bonica-lsr-ip-flexalgo-01 [External Email. Be cautious of content] Hi authors, Here is one comment following the previous discussion on the mail list and the IETF meeting. The IP Algorithm TLV is defined to advertise the IP Flex-Algorithm participation information, there is no separate TLV for IPv4 or IPv6 Flex-Algo participation. If some nodes participate in IPv4 Flex-Algo 128, and some of these nodes participate in IPv6 Flex-Algo 128, how to ensure that the path computed for IPv6 Flex-Algo will not use the nodes which only participate in IPv4 Flex-Algo 128? Best regards, Jie From: Lsr [mailto:[email protected]] On Behalf Of Acee Lindem (acee) Sent: Wednesday, December 2, 2020 5:13 AM To: lsr <[email protected]<mailto:[email protected]>> Subject: [Lsr] WG Adoption Call for "IGP Flexible Algorithms (Flex-Algorithm) In IP Networks" - draft-bonica-lsr-ip-flexalgo-01 This IP Flex Algorithm draft generated quite a bit of discussion on use cases and deployment prior to IETF 109 and there was generally support for WG adoption. This begins a two week WG adoption call. Please indicate your support or objection to WG adoption on this list prior to 12:00 AM UTC on December 16th, 2020. Also, review comments are certainly welcome. Thanks, Acee
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
