Dear authors,
here are couple of comments to draft-zhu-lsr-isis-sr-vtn-flexalgo:
1. whether we want to flood VTN specific link data in IGPs or not is
something that deserves its own discussion.
2. Nevertheless, the proposed encoding does not seem to be a fortunate one:
a) it hijacks the L2 bundle member TLV for VTN data. I don't see the
need for that.
b) the proposed mechanism to associate the VTN specific link data with
the VTN itself by the use of the link affinities is a very user
unfriendly way of doing it. If the VTN need only the low latency
optimization, provisioning additional affinities seems like a
unnecessary provisioning price that would need to be paid by the user
for the encoding deficiency. You want to flood the VTN specific link
data, put the VTN ID in it.
thanks,
Peter
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr
