Hey Peter and Lsr, At the risk of being called troublemaker by Les again :) can you refresh my failing memory how UPA would work in case of Inter-AS option C (where original next hops are maintained for service routes across two or more ASNs) and reachability to next hops is redistributed (often with labels) between ASBRs ?
On a similar note how UPAs travel (if at all) between backbone area and remote areas in the single AS case ? While reading mail from Bruno I also realized a bit more complex case where someone may use service routes in service BGP over "seamless MPLS 3107/LU routes by BGP over IGP. In such cases signalling remote PE going down is not going to help much I am afraid. - - - As to the draft I think just adding a sentence that it should be used/enabled only for encapsulated services at ingress to the service nodes. And actually to expand on what Bruno mentioned in the last note next hop validation can in some implementations be enabled to resolve in different RIBs on a per SAFI basis. But how BGP (or any other app) takes such triggers is indeed outside of scope of the current draft IMO. Thx, R,
_______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
