Yeah, just learning that... got a *tonne* of offline replies.

Planets won't work well, simpson characters we'll run out very
quickly.... umm.. forgot the rest.  We were looking for something that
makes sense to the function of the box itself and scales up (as per some
other folks point)....

Some of the suggestions around kinda what we have today but with some
changes are what'll we'll debate internally.

Take care,

Paul



-----Original Message-----
From: Ravi Pina [mailto:r...@cow.org]
Sent: March-13-10 2:01 PM
To: Paul Stewart
Cc: NANOG list
Subject: Re: Network Naming Conventions

Heh.

Host naming discussions is like religion and politics at parties.
It only leads to someone going home crying, red wine spilled all
over their new dress, and a black eye.

Not in that order.

-r

On Sat, Mar 13, 2010 at 10:47:28AM -0500, Paul Stewart wrote:
> Hi Folks...
>
>
>
> With many changes going on this year in our network, I figured it's a
> good time to revisit our naming conventions used in our networks.
>
>
>
> Today, we use the following example:
>
>
>
> Core1-rtr-to-ge1-1-1-vl20.nexicom.net
>
>
>
> Core box #1, rtr=router, to=location, ge1-1-1=interface, vl20=vlan etc
> etc....
>
>
>
> Going forward, I'd like to examine a better method to identify the
> devices.... does anyone have published standards on what they use or
> that of other networks and maybe even why they chose those methods?
The
> core of the network is fairly easy for us to look at different changes
> where you have interfaces, subinterfaces, locations etc. to deal with.
>
>
>
> But what do folks do for "aggregation devices" such as dial-up
shelves,
> BAS devices etc?
>
>
>
> Finally, we have a fair amount of gear (that we own) at customer
> premises that act as either a managed device or a demarcation point
....
> how to you name those today?
>
>
>
> Open ended questions obviously - looking for many ideas.
>
>
>
> ;)
>
>
>
> Paul
>
>
>
>
>
>
>
>
>
------------------------------------------------------------------------
----
>
> "The information transmitted is intended only for the person or entity
to which it is addressed and contains confidential and/or privileged
material. If you received this in error, please contact the sender
immediately and then destroy this transmission, including all
attachments, without copying, distributing or disclosing same. Thank
you."




----------------------------------------------------------------------------

"The information transmitted is intended only for the person or entity to which 
it is addressed and contains confidential and/or privileged material. If you 
received this in error, please contact the sender immediately and then destroy 
this transmission, including all attachments, without copying, distributing or 
disclosing same. Thank you."

Reply via email to