Collaborating with SONiC routing WG- we have introduced the prefix independent convergence into SONiC. Current FRR / SONiC’s routes handling come from data center use cases. But routing domain is another story due to the scale and the introduction of VPN routes. Since the DCN solution leads to prolonged routes convergence time at network outages- the traffic loss would be significant. This is one of the key infrastructure enhancements required to extend SONiC domain from data center to routing use cases. \n\nIn this talk- we introduces how we reformat FRR/ SONiC routing domain related data structure:\n- Decouple prefix information with next hop information\n- Decouple next hop information and VPN context information. \n- Introduce next hop group ID and VPN context ID programming from FRR to SONiC\nWe introduce e quick fix based on existing routing information to minimize traffic loss window. We also use BFD to detect BGP next hop connectivity.