[17421] in North American Network Operators' Group
Re: (*F) Re: USAC and SPIN
daemon@ATHENA.MIT.EDU (Jared Mauch)
Mon Jun 1 10:52:21 1998
Date: Mon, 1 Jun 1998 10:45:37 -0400
From: Jared Mauch <jared@puck.nether.net>
To: Jim Fleming <JimFleming@unety.net>,
"'jamie@dilbert.ais.net'" <jamie@dilbert.ais.net>
Cc: "nanog@merit.edu" <nanog@merit.edu>
In-Reply-To: <01BD8D3E.F611EAA0@webster.unir.net>; from Jim Fleming on Mon, Jun 01, 1998 at 09:23:38AM -0500
On Mon, Jun 01, 1998 at 09:23:38AM -0500, Jim Fleming wrote:
> On Monday, June 01, 1998 4:18 AM, James Rishaw[SMTP:jamie@dilbert.ais.net]
> 3. I often wonder if people that configure routers know how routing
> *should* work.
> Do people that drive cars know how cars work ? Do they care ?
>
> Maybe we should create a Top Level Domain named .SPIN. That
> TLD could be used to register the free SPIN numbers at the second level.
> For example, Bell Atlantic might have 143001398.SPIN for Pennsylvania.
> A TXT Record could be included in the DNS to contain the name
> "Pennsylvania" for the SPIN number.
>
> After registering a SPIN number, an ISP could add A records for their
> ASNs and OUI information. Since an A record is a general purpose
> container for 32 bit quantities, a single A record can be used to hold
> an ASN in the low 16 bits. Another A record can hold the 24 bit OUI
> in the low 24 bits. With this, the following DNS entries would return
> A records:
>
> ASN.143001398.SPIN
> OUI.143001398.SPIN
Even *fewer* people understand how dns works, nor can configure
it properly. This is easy to tell, log lame delegations on your
nameserver. Or log the "invalid" hostnames stuff, folks with _/, etc..
in their dns entries.
- Jared
