Richard Patterson

This account is deprecated; find over at @r-pats.bsky.social

[Richard Patterson @RichPatz]

@FernandoGont Acknowledging the problem is the first step!

[NetLdn @netldn]

Tomorrow, 7pm upstairs @ The Wheatsheaf, Fitrovia.

[NetLdn @netldn]

For #NetLdn this week we have 2 fantastic presenters that are guaranteed to entertain: @tstrickx and Jen Linkova:

https://t.co/9IGgLuYsZH

[RIPE 93 - Sofia, Bulgaria @ripemeeting]

That's a wrap for Day 1 of #RIPE89! Today, we welcomed 540 participants onsite and 256 online. We look forward to seeing you for another exciting day tomorrow! And if you missed anything today, check out our Daily Meeting Blog on RIPE Labs: https://t.co/JIsMocaa9W

[Ondrej Filip @ondrejfilip]

Wow! #ripe89
$ traceroute -f 8 -q 1 https://t.co/DvQ3CZDdrz

[Richard Patterson @RichPatz]

@staticyrro In their defence, they've just inherited the behaviour from OpenWRT's DHCPv6 client. Would be nice if we can get it fixed though! (Or even better, for Unifi to start supporting MAP-T)

[Sebastian Castro @secastro]

When the speaker at #RIPE89 greets the plenary in Te Reo Maori, Richard Patterson from Sky. Kia Ora!

[NetLdn @netldn]

It's #NetLdn 57 this Thursday, and we've got two great talks lined up, followed by some interesting discussion I'm sure:

[NetLdn @netldn]

#NetLdn 57 is next week, Thursday 10th of October. Talks start promptly at 1900hrs, upstairs at The Wheatsheaf, Fitzrovia, W1T 1JB

https://t.co/07Qsx17mj6

[NetLdn @netldn]

It's #NetLdn 56 this evening, come along:

[Richard Patterson @RichPatz]

@jwbensley Clarence did point out it's cheaper for hw as it avoids a label table lookup; I think that's only relevant for PEs though.

[Richard Patterson @RichPatz]

@jwbensley I'm almost ready to start considering SRv6, if I were doing a greenfield, once the CRH debacle settles down.

I'm just waiting to be convinced of its benefits over SR-MPLS. Bigger SID space is the obv one, countered with the inefficiency of non-CRH.

[Richard Patterson @RichPatz]

@tomm3h @jwbensley But that's the trade-off with SR that allows it to scale better than RSVP-TE.

[Richard Patterson @RichPatz]

@jwbensley Yeah exactly, and the rest of that 128bits is just wasted space in the SRH/segment list

[Richard Patterson @RichPatz]

@jwbensley Yup, and that's because people perceived this to be an outstanding issue with SRv6. (you asked for reasons why people don't want to s/MPLS/SRv6/g , just giving examples)

Another proposal was a new ethertype to distinguish it from 0x86DD

[NetLdn @netldn]

Tomorrow at #NetLdn:

[Richard Patterson @RichPatz]

@jwbensley 128bits introduces scaling challenges, hence why the IETF has been heavily working on (and arguing about), alternative compressed versions of the SRH

[Richard Patterson @RichPatz]

@jwbensley With SR your signalling is now part of your packet. SR-MPLS can't accidentally leak out of (or into) your network, with SRv6 it can if people mess up filtering.

[NetLdn @netldn]

It's #NetLdn this week, and we're looking for some lightning talks. If you've got something to talk about, please get in touch: https://t.co/ahGTCek38V

[FastNetMon @FastNetMon]

👀 Interesting read about on Sky Broadband UK's Deployment of MAP-T for IP Address Sharing: https://t.co/vjzgw6n443

#NetworkEngineering #Broadband #Internet #InternetProtocol #CGNAT #ISP