[33926] in North American Network Operators' Group
Re: Labeling and naming
daemon@ATHENA.MIT.EDU (Kurt Erik Lindqvist)
Thu Jan 25 06:08:58 2001
Date: Thu, 25 Jan 2001 11:27:50 +0100 (CET)
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
To: Patrick Greenwell <patrick@cybernothing.org>
Cc: nanog@merit.edu
In-Reply-To: <Pine.BSF.4.21.0101240826550.1598-100000@localhost>
Message-ID: <Pine.LNX.4.05.10101251026220.25571-100000@tankgirl.kurtis.pp.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
> > For a project I am currently working on I stumbled upon the following.
> > What is the best way to lable and name equipment?
>
> Choose a naming convention, publish it internally, and stick with it.
Well...that is the project :)
> Some folks like to put airport abbreviations in their labels to attempt to
> indicate the geographic location of systems. I don't as there are cities
> with multiple airports, national and international airport labels can
> conflict, and I frequently find that facilities are actually in different
> cities than the nearest airport.
Agree. Besides, if you things like repeter stations there is not even a
city. Just a location. Still, I am woundering what is the best path. To
write a rule-set or grammar for generating codes, or just creating a list.
> I've got a naming convention somewhere I wrote a while ago if you're
> interested in a starting point...
Absoulutly!
- kurtis -
