[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Feasibility of using Class E space for public unicast (was re: 44/8)

Subject: Feasibility of using Class E space for public unicast (was re: 44/8)
From: list at satchell.net (Stephen Satchell)
Date: Sat, 27 Jul 2019 15:07:55 -0700
In-reply-to: <[email protected]>
References: <CAP-guGXkT9O_sB5yhZP5XtjkDkz4MQctg-Vdqj33ofYRYTeXeQ@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

On 7/27/19 2:18 PM, Randy Bush wrote:
> something is broken on the nanog list.  usually we have this discussion
> twice a year.  this time it may have been a couple of years gap.  what
> broke?


44/8.  Sucked up all the oxygen.

References:
- 44/8
  - From: bill at herrin.us (William Herrin)
- 44/8
  - From: andrew.brant at me.com (andrew.brant)
- 44/8
  - From: SNaslund at medline.com (Naslund, Steve)
- 44/8
  - From: owen at delong.com (Owen DeLong)
- Feasibility of using Class E space for public unicast (was re: 44/8)
  - From: dougb at dougbarton.us (Doug Barton)
- Feasibility of using Class E space for public unicast (was re: 44/8)
  - From: bzs at theworld.com (bzs at theworld.com)
- Feasibility of using Class E space for public unicast (was re: 44/8)
  - From: randy at psg.com (Randy Bush)

Prev by Date: Feasibility of using Class E space for public unicast (was re: 44/8)
Next by Date: really amazon?
Previous by thread: Feasibility of using Class E space for public unicast (was re: 44/8)
Next by thread: 44/8
Index(es):
- Date
- Thread