Hi Mark, As for segment routing, several of our NREN partners have SR up and running in their backbones. We in GÉANT (the backbone that connects these NRENs) are looking toward deploying SR across our entire backbone in the medium term.
Can't comment on MC-LAG though. :) Br, Niall Niall Donaghy Senior Network Engineer GÉANT T: +44 (0)1223 371393 M: +44 (0) 7557770303 Skype: niall.donaghy-dante PGP Key ID: 0x77680027 nic-hdl: NGD-RIPE Networks • Services • People Learn more at www.geant.org GÉANT Vereniging (Association) is registered with the Chamber of Commerce in Amsterdam with registration number 40535155 and operates in the UK as a branch of GÉANT Vereniging. Registered office: Hoekenrode 3, 1102BR Amsterdam, The Netherlands. UK branch address: City House, 126-130 Hills Road, Cambridge CB2 1PQ, UK. -----Original Message----- From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Mark Tinka Sent: 03 July 2018 21:42 To: Gert Doering <g...@greenie.muc.de> Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] VPC mc-lag On 3/Jul/18 22:29, Gert Doering wrote: > Since side A does not know that side B is actually a "MC-LAG" (if side > B does things right) not sure where you expect problems. > > A proper MC-LAG is not really that much different from "a LAG across a > stacked set of switches" or "a LAG across different line cards" - just > the coupling/learning protocol between the entities involved differs. As far as the theory goes, yes, I'm with you... But like with Segment Routing, who has actually done it? And more importantly, done it to be doing anything else at 3AM in lieu of waiting for a call from the NOC? Mark.
_______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
