[123702] in North American Network Operators' Group
Re: Network Naming Conventions
daemon@ATHENA.MIT.EDU (Larry Sheldon)
Sat Mar 13 13:27:11 2010
Date: Sat, 13 Mar 2010 12:26:08 -0600
From: Larry Sheldon <LarrySheldon@cox.net>
To: nanog@nanog.org
In-Reply-To: <4B9BBB7C.8030800@gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
For end-point hosts ("servers") I prefer terse topical names for
single-function machines ("Finance", "Purchasing") and some predictable
pattern that ties somehow to the organization for multipurpose machines
("Bluejay", "Parrot").
For network equipment at end points I prefer a string that starts with
the machine's function, ends it an interface identifier, with location
info in the middle. ("rtr-oma-hosp-3rd-peds", "rtr-oma-hosp-3rd-surg").
For network out in the middle I would do the same except expand the
location data a bit and change the I/F infor to a hardware descriptive.
--
Democracy: Three wolves and a sheep voting on the dinner menu.
(A republic, using parliamentary law, protects the minority.)
Requiescas in pace o email
Ex turpi causa non oritur actio
Eppure si rinfresca
ICBM Targeting Information: http://tinyurl.com/4sqczs
http://tinyurl.com/7tp8ml
