Validation for policies created with IPv6 endpoint without SRv6 enable: During our test on an IPv6 CNC cluster, create an SR policy with IPv6 tail end info in the payload but SRv6 is not enabled. Configuration is pushed successfully but it causes the policy flapping. PCE sends create/delete message continuously. Please refer to the attach email discussion for more details. According to XTC team, a policy with IPv6 endpoints but SRv6 is not enabled is not a supported scenario.Question 1: Is it possible we add some validation in the model on CFP side?A similar scenario for transport slice. Our topology is configured as a dual stack topology. When create slice we do not enable SRv6, but as the result of slice creation, policies with IPv4 router TE-ID and IPv6 router TE-ID are created and it also have the policy flapping issue due to SRv6 is not enabled in the ODN attached to the slice.Question 2: What is the best way to communicate the behavior to the user for slice if a dual stack topology is configured?
 Hi Crystal,Please proceed to file CDETS so we can solve the Question 1.We believe validation triggered for Question 1 will solve Question 2.Please let us know if this helps.Regards,Janaki DuggiralaHi Janaki,I have created CSCwh76502 to track.Thanks.-CrystalThank you Crystal, closing this ticket so the issue maybe tracked with the CDETS CSCwh76502