I agree that LISP has built in service chaining support through using LISP RTRs as described by Dino.
But there are other, protocol independent ways of achieving the same behaviour, see the work being presented at the SFC BOF https://datatracker.ietf.org/meeting/88/agenda/sfc/ Yves On 04/11/13 23:00, "Dino Farinacci" <[email protected]> wrote: >> Could someone explain to me how to use LISP solution to provide route >>path control? For example, in a VN, ingress NVE MUST forward the packets >>to another NVE at which a tenant system runs firewall software. The >>second NVE then forwards to the packets to the third NVE where an >>attached TS has the address that matches the destination address in the >>inner address on the packets. >> >> Lucy > >LISP has a decapsaltor/encasulator component called an RTR. An RTR can >give you suboptimal paths by choice if you want to route around failures, >congestion points, or use policy paths. You can find details in >http://datatracker.ietf.org/doc/draft-farinacci-lisp-te. > >But yes, you can have an RTR co-located with a firewall, laod-balancer, >and NAT type middle devices. > >Dino > >_______________________________________________ >nvo3 mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
