Re: Network Naming Conventions

[Leo Bicknell <bicknell () ufp org>]

In a message written on Sat, Mar 13, 2010 at 10:47:28AM -0500, Paul Stewart wrote:
> Open ended questions obviously - looking for many ideas.

I think a key question to ask yourself is who needs to be able to
interpret your names?

Depending on your business, customers, engineers, etc you may have
a good reason to use obscure names, for instance not making it easy
for people to know the speed of interfaces, where your routers are
located, how many routers you have, what brand routers you use, and
so on.  In other cases, you would like as much of that as possible
to be something that someone can guess.

For instance, many ISPs use city names or airport codes.  This can
help your customers decide if the latency numbers are reasonable
or not.  Lots of ISPs also include interface information, often so
an engineer can log in and do a "show int xyz" based on a traceroute
with no intermediate steps to look up which interface the IP is on
and such.

Lastly, "traceroute www.<foo>.com" for a pile of web sites will give
you all sorts of schemes in no time.

There is no "right answer" in the generic, but there is a right answer
for you.

-- 
       Leo Bicknell - bicknell () ufp org - CCIE 3440
        PGP keys at http://www.ufp.org/~bicknell/

Attachment: _bin
Description: