[j-nsp] Segment Routing Real World Deployment (was: VPC mc-lag)

Mark Tinka mark.tinka at seacom.mu
Mon Jul 9 06:36:11 EDT 2018



On 8/Jul/18 22:35, adamv0025 at netconsultings.com wrote:

> Hold on gents, 
> You are still talking about multi-hop TCP sessions, right? Sessions that
> carry information that is ephemeral to the underlying transport network -why
> would you want those session ever go down as a result of anything going on
> in the underlying transport network -that's a leaky abstraction , not good
> in my opinion.
> You just reroute the multi-hop control-plane TCP session around the failed
> link and move on, failed/flapping link should remain solely a data-plane
> problem right? 
> So in this particular case the VC label remains the same no matter that
> transport labels change in reaction to failed link.
> The PW should go down only in case any of the entities it's bound to goes
> down be it a interface or a bridge-domain at either end (or a whole PE for
> that matter) -and not because there's a problem somewhere in the core. 

We all wake up everyday to keep the backbone up and growing.

A broken backbone will break a pw signal.

Mark.


More information about the juniper-nsp mailing list