[c-nsp] Segment Routing

[Aaron]

Thanks Mark,

 

Help me here…  what is the “worry” with LDP that you speak of.  I don’t see the worry in LDP… it seems to do its thing without much intervention from me at all.  About LDPv6, I’m assuming that ldpv6 is related to ipv6…. I’ve been testing 6VPE (ipv6 over top of mpls l3vpn) and it seems fine with my underlying ldp…so I’m not sure what to understand about that.

 

As for the second point of TE… I guess since I’ve never done any MPLS-TE or RSVP-TE, I will have trouble seeing the benefit of SR over traditional RSVP-TE… but I will take note of your point.  So would you say that if I learn about RSVP-TE and what I can accomplish with it, that I should NOT move in that direction, but spend time deploying SR and then benefit from the easier TE ?  

 

Thanks again Mark, 

 

-Aaron

 

From: Mark Tees [mailto:marktees at gmail.com] 
Sent: Tuesday, January 3, 2017 10:42 PM
To: Aaron <aaron1 at gvtc.com>
Cc: Mohammad Khalil <eng_mssk at hotmail.com>; Patrick Cole <z at amused.net>; CiscoNSP List <CiscoNSP_list at hotmail.com>; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Segment Routing

 

Two benefits I can think of:

 

 Label distribution without having to worry about LDP or LDPv6.

 

Easy TE cases without having to worry about the state that comes with RSVP-TE.



On Wednesday, 4 January 2017, Aaron <aaron1 at gvtc.com <mailto:aaron1 at gvtc.com> > wrote:

I run an MPLS network for an ISP and have heard about SR/SPRING but I don't
know much about it.

What would you tell someone like me as to how I would benefit from SR/SPRING
in my MPLS network ?   ...and if there isn't immediate benefit, are there
inevitable long-term benefits that I could reap by moving towards a segment
routed mpls network ?

-Aaron


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net <javascript:;> 
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/



-- 
Regards,

Mark L. Tees