Domain names for ISP infrastructure links

Philip J. Nesser II pjnesser at
Tue Jan 7 20:53:59 UTC 1997

Alex.Bligh supposedly said:
> > But instead of h0/0, use h0-0; s2-6; etc...
> as well. We use something very roughly like (I've, urm, simplifed
> this, i.e. written down what we ought to use)
> <2 letter POP code> <router number> - <1 let card type> <card no>
>   - <i/f number> [ - <sub i/f number> [ - <DLCI num> ]]
>   [ <2 letter POP code> <router number> ]
> So
> TH1-S2-3-4-5-ME6

Well I think this is the best suggestion I have seen but I have a few

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.

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?

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,
not for privacy but for administrative ease.  If I upgrade a connection I
don't want to have to remember to change my DNS entries.

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
to set up a formal registration process with the IANA for 2(or 3) letter
pop codes to be consistant?

--->  Phil

More information about the NANOG mailing list