Domain names for ISP infrastructure links

Dorian R. Kim dorian at cic.net
Tue Jan 7 21:45:55 UTC 1997


On Tue, 7 Jan 1997, Philip J. Nesser II wrote:

> 1.  I really like the addition of the final pop-router combo so its easy to
> follow connections.  This has been missing in other suggestions so I am
> curious as to what others think.

I'm puzzled. Connections go from router to router. How does it help to say
routerb-x-y-z-routerc.blah.net when routerc will show up as the next hop in
the traceroute?

> 2.  Using an fixed width format as proposed keeps the maximum length (not
> including the domain suffix) short. Assuming 2 digit router/interface
> numbers and a four digit DLCI, the max length is 24 characters.  (Even if
> we allow 3 digits to router numbers we max at 29).  I would propose to add
> a little more information in the form of 1 letter types in from of the
> numbers (like a 'd' before the DLCI number).  Looking at the example above
> is marginally okay because all field are present but what if there was
> either no subinterface or no DLCI, how would you tell what the last number
> is supposed to mean?

As long as we are going to code router specific things in the DNS, they are
going to be a wide variety of thing to indicate.

We use the following scheme.

<routername> - <interface  designation> <slot number> - <card slot number> 
[<port number> [s <sub-interface number>].<pop>.cic.net.

where interface designation is [fddi|hssi|ser|ether|fastether|atm|token|pos]
i.e.

um1-fastether3-0-0s1.ann-arbor.cic.net

is the 1st sub interface of fastethernet in slot 3, card slot 0, port 0 of um1
router at our Ann Arbor POP.

> 3.  How do people feel about putting the speed of the link in the DNS name,
> I have seen one yea and one nay.  I am ambivilant, but leaning towards no,

Speed of the link is not important IMO.

> 4. Are people actually interested in pursuing this formally?  If a spec was
> written would you change your DNS names to conform?  Would you be willing

That depends on what's agreed on. Beauty is in the eye of the beholder, and so
are names.

> to set up a formal registration process with the IANA for 2(or 3) letter
> pop codes to be consistant?

If you wanted that, why not take the airport codes as many have already done?

-dorian







More information about the NANOG mailing list