Options for CS-SR: When a CS policy is configured with auto-color enabled, what is the color that is sent by NSO to CNC? What is the range of valid colors for these policies? Is 0 considered a valid color? 
Hello Sachin,CS SR-TE auto color utilizes Resource Manager to allocate color values based on a resource pool. The color resource pool should first be defined under ralloc:resource-pools -> idalloc:id-pool which should then be referenced from cs-sr-te-resource-pools -> color-pool-name.When defining your resource pool parameters under ralloc:resource-pools, user can specify a range from which allocation will be done. This resource pool allocation range must match the range of the corresponding config node so that a valid value can be allocated. This means for color, it will be 1-4294967295 as you can see in the model:<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">leaf color { tailf:info ; description ; type uint32 {  range ; }}</pre></div></div>As you can see, 0 is not a valid value as it is not within the color range.Please let me know if you have any other questions.Thanks,Isaac KimHi Sachin,To see what the allocated color value is, you can check (OPER DATA) cs-sr-te-policy -> color-oper-data -> color.Thanks,Isaac KimAs discussed in the meeting we will refactor the allocated oper-data from service to plan. You can expect the oper-data to be stored in the following paths::cs-sr-te-plan -> color-oper-data -> color :cs-sr-te-plan ->bidirectional-association-id-oper-data ->working-path-bidirectional-association-idcs-sr-te-plan ->bidirectional-association-id-oper-data ->protect-path-bidirectional-association-idcs-sr-te-plan ->bidirectional-association-id-oper-data ->restore-path-bidirectional-association-idcs-sr-te-plan ->disjoint-group-id-oper-data ->forward-group-idcs-sr-te-plan ->disjoint-group-id-oper-data ->reverse-group-idFixed in M6 Patch Build