%% You should probably cite draft-li-spring-anycast-sid-service-02 instead of this revision. @techreport{li-spring-anycast-sid-service-01, number = {draft-li-spring-anycast-sid-service-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-li-spring-anycast-sid-service/01/}, author = {Taixin Li and Zhe Chen}, title = {{Anycast SID for Flexible and Robust Service in SRv6}}, pagetotal = 10, year = 2020, month = may, day = 15, abstract = {Segment Routing enables an operator or an application to specify a packet processing program. When Segment Routing is applied to IPv6 data plane, the list of IPv6 SIDs in SRH can specify a series of execution endpoints that hold service functions that process the packet. However, steering traffic dynamically to the different execution endpoints requires a specific "re-encapsulating". This procedure may be complex and take time. This document proposes A-SID (Anycast-SID) based on SRv6 to achieve flexible and robust service provision. It uses anycast SID to identify service functions and locates the service functions based on anycast routing. The proposed solution can stay compatibility with the existing SRv6.}, }