On Sun, Oct 16, 2022 at 5:28 PM Daniel Sterling
wrote:
> Does anyone have any stories about working with or near John they would
> like to share with the list? It would definitely make my day to hear more
> about the early internet
>
A good book on the topic of the early internet is "Where Wizar
> Does anyone have any stories about working with or near John they
> would like to share with the list? It would definitely make my day
> to hear more about the early internet
somewhere around i have a protocol violation ticket he issued.
---
Who says that routing unallocated address space is u
One of the best things about this list is first hand accounts of our
internet lore
Does anyone have any stories about working with or near John they would
like to share with the list? It would definitely make my day to hear more
about the early internet
Thanks,
Dan
On Sun, Oct 16, 2022, 8:01 PM
>
> Early unix had a similar philosophical debate. Everything is a simple
> file (including most devices), make commands which do one thing and
> do it well so they can be connected together in new ways (an almost
> prescient view on the ubiquity of multi-cpu/core systems), when in
> doubt gener
On October 16, 2022 at 14:18 ra...@psg.com (Randy Bush) wrote:
> my favorite is
>
> It's perfectly appropriate to be upset. I thought of it in a slightly
> different way--like a space that we were exploring and, in the early days,
> we figured out this consistent path through the space: IP
On 10/16/22 15:55, Nathan Angelacos wrote:
I got on the "interwebs" just before Al Gore invented the internet (no
political statement, just that is the way it was back then.) 15 3.5"
floppy disks, a 33Mhz 486, slackware, (and a really reliable USRobotics
modem.)
About the same time for me, m
On Sun, 2022-10-16 at 13:23 -0700, Randy Bush wrote:
> it's been 24 years, and we still live in his shadow and stand on his
> shoulders. we try not to stand on his toes.
>
> randy
I got on the "interwebs" just before Al Gore invented the internet (no
political statement, just that is the way it
As the coauthors of the 2019 NSF-supported report that contributed to the
current momentum toward overcoming the barriers RPKI adoption, a prior posting
asked for our assessment of the changes. Our apologies that we won't be able
to join you at this NANOG. We hope to put together some type of
On Sun, Oct 16, 2022 at 2:21 PM Randy Bush wrote:
>
> my favorite is
>
> It's perfectly appropriate to be upset. I thought of it in a slightly
> different way--like a space that we were exploring and, in the early days,
> we figured out this consistent path through the space: IP, TCP, and so on.
my favorite is
It's perfectly appropriate to be upset. I thought of it in a slightly
different way--like a space that we were exploring and, in the early days,
we figured out this consistent path through the space: IP, TCP, and so on.
What's been happening over the last few years is that the IETF
On Sun, 16 Oct 2022, 23:24 Randy Bush, wrote:
> it's been 24 years, and we still live in his shadow and stand on his
> shoulders. we try not to stand on his toes.
>
"A name indicates what we seek. An address indicates where it is. A route
indicates how we get there." Jon Postel
> randy
>
.
This situation isn’t helped by RIR policies that require you to announce the
aggregate in region even if the more specifics are scattered around the world.
The whole territorial exclusivity game played by some RIRs may well cause more
harm than good at this point.
Yes, I realize this is a reve
it's been 24 years, and we still live in his shadow and stand on his
shoulders. we try not to stand on his toes.
randy
On Sun, Oct 16, 2022 at 1:01 AM Matthew Petach wrote:
> Their assumption that *everyone* would hear the more specifics,
> and thus the traffic would flow to the right island location was the
> "failure to understand BGP" that I was commenting on, and noting
> that while it is entirely correct to d
On Tue, Oct 11, 2022 at 7:03 PM William Herrin wrote:
> On Tue, Oct 11, 2022 at 5:32 PM Matthew Petach
> wrote:
> [...]
> All TCP/IP routing is more-specific route first. That is the expected
> behavior. I honestly don't fathom your view that BGP is or should be
> different from that norm. If th
15 matches
Mail list logo
