Jimmy,
On 09/12/2020 11:10, Dongjie (Jimmy) wrote:
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.
the draft clearly says:
"The IP Flex-Algorithm participation advertised in ISIS IP Algorithm
Sub-TLV is topology independent."
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?
there is no such thing as "IPv4 Flex-Algo 128" or "IPv6 Flex-Algo 128".
There is only algo 128.
You are mixing data plane support with algo participation.
If you want an algo to only include nodes that supports specific data
plane, you would need to define a specific algo for it.
thanks,
Peter
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]>
*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 16^th , 2020. Also, review comments are
certainly welcome.
Thanks,
Acee
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr
