My kids complained once that my husband and I knew too much about technology; we were the wrong generation.

[wollman@mastodon.social]

@wendynather I once worked for Dave Clark, I think he's like 82 now. I've still got a few decades to go, thankfully.

[wendynather@infosec.exchange]

@paul_ipv6 Do you think you’ll ever be forgiven?

[paul_ipv6@infosec.exchange]

@wendynather

not by anyone who's used the internet.

[petrillic@hachyderm.io]

@paul_ipv6 @wendynather look I had a hand in IPv6, and well… mind you our proposal didn’t win but still. I feel weirdly responsible for the shambles.

[paul_ipv6@infosec.exchange]

@petrillic @wendynather

i personally thought TUBA was the expedient choice but that wasn't how the IETF rolled.

[plzupgrademe@fedi.txw.ca]

@petrillic@hachyderm.io @paul_ipv6@infosec.exchange @wendynather@infosec.exchange what was your hand in it? I want to know who there was like “Hexadecimal, everyone loves that right?”/0D/0A

[petrillic@hachyderm.io]

@paul_ipv6 @wendynather it was. And PIP (our proposal) was the super future looking. So they decided to go with a monstrosity composed of a bunch of different things none of which are wrong necessarily but which don’t tell a cohesive story. Combine that with the introduction of NAT and… well here we are 30 years later.

[paul_ipv6@infosec.exchange]

@petrillic @wendynather

yup. i think that certain things in IPv6 were improvements and did let us learn from some of the lessons of IPv4. that said, it also suffered from too many people who decided it that if we'd done it in v4, it must be wrong and needed to be ripped out. that, plus the attitude that "we're smarter than you and if you think you need something like DHCP, you must be an idiot and you're running your network wrong" didn't help with enterprise or large vendors.

as you say, the IETF saying "NAT is evil so we won't even try to support it", yet it did solve lots of the issues for lots of folks, gave the IETF a credibilty problem and NAT a solid foot in the door.

we're doing better now than we were 25 years ago but i sure hope we've learned some lessons.

[johntimaeus@infosec.exchange]

@petrillic @paul_ipv6 @wendynather

At least you (hopefully) weren't responsible for ATM.

[paul_ipv6@infosec.exchange]

@johntimaeus @petrillic @wendynather

nope. avoided ATM. did have to do flame delay for a bit.

[petrillic@hachyderm.io]

@johntimaeus @paul_ipv6 @wendynather well actually… not responsible but did deploy a lot of it with Fore Systems and then Xylan when I was at Optical Data Systems.

The future is so bright it goes 155!

Or 25 if you’re some weirdo at IBM.

[petrillic@hachyderm.io]

@paul_ipv6 @johntimaeus @wendynather we also used the X.25 network PADs for out of band access at Sprintlink.

[paul_ipv6@infosec.exchange]

@petrillic @johntimaeus @wendynather

mae--east etherswitches were bad enough.

[johntimaeus@infosec.exchange]

@petrillic @paul_ipv6 @wendynather

Recently (last year) found my certificates for Xylan OmniSwitch Engineer. Thinking I should put them back on the CV.

Did you ever do the training at the Dover NH location?

[petrillic@hachyderm.io]

@paul_ipv6 @johntimaeus @wendynather the garage era. Then DEC Gigaswitches

[paul_ipv6@infosec.exchange]

@johntimaeus @petrillic @wendynather

there are certain things you never put on your resume for fear someone might ask you to do it again.

i once built/programmed a nortel meridian PBX. never again.

[petrillic@hachyderm.io]

@johntimaeus @paul_ipv6 @wendynather I didn’t. Spent most of my time with engineering in Callabasas? I think.

[paul_ipv6@infosec.exchange]

@petrillic @johntimaeus @wendynather

yup. boone garage. good times.

[petrillic@hachyderm.io]

@paul_ipv6 @johntimaeus @wendynather we all make mistakes

[petrillic@hachyderm.io]

@paul_ipv6 @johntimaeus @wendynather there was a time when you could fit all the backbone engineers in the world in a bus. And sometimes we did.