TracketPacer 🚀hello please enjoy this dramatic word-for-word reading of RFC 1925
Thomas Kumlehn@tracketpacer April 1st, but gooood
Eleanor Saitta
Eliot Lear@dymaxion @pixelpartner @tracketpacer
Ross really needed to have a 4(a) and 4(b) as follows: (a) “Ignore academia at your peril”. Slow start and header compression came from neither an operator nor a vendor. (b) network equipment vendors can't force end systems to implement a single line of code.
@eliotlear
Sure, although I would argue that many advances from academia happened either because a) specific problems became well-enough specified that they could be worked on in an academic without deep context, b) because folks from industry went into academia, or c) because many academic networks grew big enough to provide "real" operator experience.
Not saying it shouldn't have been an April 1st RFC, of course, just that it reflects a lot of my experience in security, with those caveats.
@pixelpartner @tracketpacer
@dymaxion If Academia and Industry could post their relationship statuses, they would both indicate, “It's complicated". In security, quite frankly my best time spent is with academics who aren't hawking wears at me. I particularly like the WEIS crowd for that. If you haven't attended, WEIS, I highly encourage it. Also, check out the ANRP prize winners. I have a favorite right now- Aqsa Kashaf @ CMU knows more about hidden dependencies than anyone.
@eliotlear
I should dip my head in again. The last time I went to an academic security event was, I realize, like eight years ago now. At the time, most of what I saw was just irrelevant. Very much agree on the "not trying to sell you stuff" bit, though; that part was lovely.
I should dip my head in again. The last time I went to an academic security event was, I realize, like eight years ago now. At the time, most of what I saw was just irrelevant. Very much agree on the "not trying to sell you stuff" bit, though; that part was lovely.