Hi authors, Thanks for bringing SRv6 SID swaping idea in the distributed scenario.
I think there is valid case when the target prefix originated from remote domain is invisible or unreachable to the intermediate nodes of the local domain, and the intermediate nodes of the local domain have routes to the REPLACE SID allocated by the border node of the local domain. However, the question as I raised at the meeting, REPLACEB6 may be not necessary, because it is the local behavior of the BGP speaker to swap a single SID or a segment list. It may be not appropriate to advertise prefix with REPLACE behavior to the upstream neighbor at time-1, and re-advertise the same prefix with REPLACEB6 behavior at time-2 just because its forwarding information is changed from a single outgoing SID to a SID list. Otherwise, it will cause excessive advertisement overhead in the network. Just like MPLS BGP-LU, the difference of a single outgoing label or an outgoing label stack at the local node is not aware by upstream node. There may be some reasons for re-advertisement, such as the need to announce a new metric, but these reasons do not support the need for REPLACEB6. Regards, PSF _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
