> Of Gustav Ulander > Sent: Wednesday, July 04, 2018 10:46 PM > > Has anyone actually managed to verify a business case with SR? Im guessing > those mentioned bellow did? > How I see it, currently the only feasible business case to go with SR is if you outgrew your scaling limits with regards to the amount of RSVP state or you plan on deploying a solution that will not scale using "stateful" RSVP. (so in other words only if you have to). Cause clearly if you are looking at SR you already have a valid business case for TE, and in my opinion the only business reason why would one not leverage the years of development and debugging done for RSVP and become a pioneer in SR is if there's an absolute need. If you're using RSVP solely for TE purposes and not to enforce QOS and it's contained within a single AS/IGP-domain then it's fairly easy, and with SR some of the complexity is still there it's just moved around.
adam netconsultings.com ::carrier-class solutions for the telecommunications industry:: _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
