[135469] in North American Network Operators' Group
Re: Network Naming
daemon@ATHENA.MIT.EDU (David DiGiacomo)
Tue Jan 25 18:01:06 2011
From: David DiGiacomo <davidd@corp.nac.net>
To: "nick@flhsi.com" <nick@flhsi.com>
Date: Tue, 25 Jan 2011 18:00:47 -0500
In-Reply-To: <7aeb7ba0$10caab2c$7a5700bb$@com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Nick,=20
I do not believe there is a written standard for naming gear ( or at least =
I have never seen one) Most naming scheme's are usually something arbitrary
RAS gave a pretty good tutorial on traceroutes once, specifically he cover=
ed the topic of interpreting DNS in a traceroute.
I know we are not talking about traceroutes or DNS here but hopefully this =
can give you a little insight into naming your equipment.
http://www.nanog.org/meetings/nanog45/presentations/Sunday/RAS_traceroute_N=
45.pdf
On Jan 25, 2011, at 3:50 PM, Nick Olsen wrote:
> Whats the rule of thumb for naming gear these days=20
> (routers,switches...etc). Or is there one?
>=20
> looks like level3 does something like
> interface.routertype.location.level3.net
>=20
> Nick Olsen
> Network Operations
> (855) FLSPEED x106
>=20
>=20
