draft-ietf-spring-sr-yang seems to describe Maximum SID Depth (MSD) as a
read-write attribute that is configurable on the node, but I really wonder
how many vendors actually support changing the MSD on a node.

Suppose a node is capable of pushing a maximum of K labels in h/w and the
node MSD is configured as K, then a SR-TE tunnel on the node can specify up
to K SIDs. This means the node will not be able to push a VPN label, so
cannot do L3VPN/L2VPN. Given that a miss-configuration like would result in
service failure, is there a real motivation for changing MSD on a node?
Should MSD be a node capability instead, like the
'readable-label-stack-depth' defined in the yang draft?

Regards,
Muthu
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring

Reply via email to