[123722] in North American Network Operators' Group
Re: Network Naming Conventions
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Sat Mar 13 20:41:26 2010
Date: Sat, 13 Mar 2010 17:40:52 -0800
From: Leo Bicknell <bicknell@ufp.org>
To: NANOG list <nanog@nanog.org>
Mail-Followup-To: NANOG list <nanog@nanog.org>
In-Reply-To: <C0A98BB6DAFAAB46A78BBA2C51B98F3E01079C91@nexus.nexicomgroup.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--PEIAKu/WMn1b1Hv9
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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.
--=20
Leo Bicknell - bicknell@ufp.org - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
--PEIAKu/WMn1b1Hv9
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)
iQIVAwUBS5w+pLN3O8aJIdTMAQKMERAAmZkD/I+aBgCwL/RzUAqX2AEMrW1BdH1w
Z2omeV1IRhN494grk//IkdCbLQcoHnCBOigns7zL4ZbO2wjADhIxxa7v/H0aykO6
AQv0/kX+cNjWaQx4gdhNTxPx02DADcIEjCHBDMLb2pz7Qt6pHkWW/sEx+Pt/VQ67
43BUoJHnG5ctCdtFTxb9dbFKkxKceEevRlddKLEvHYF8pIHBz9MqteK18YfsQWFZ
fZQ+vELX+0+NI9og2iOzENz5pvKrMDdF1XEZvLy5Q1mE/iGJ+sM6pGaocFSU0NHG
NCe2mJNg4icBVVfBLN4kmVCuEZmsDvFvIbny/Qlhb59lYuiEMUvd84pygpg4rMi6
Ly0FUP8MUIbfFg7P7ZFBQkT7xnAkwmt5U8Ik0buI+VKoeICr8VuA+fCyNHvpGq/Q
0PShPvQ8qSRcuPFnfB/h6UJMLCYOf5gxgiR6o9PEYyDxprHwE86SInahx14RsCQS
nk4HZ++cTSUResDaxgzP/FMe67w1Ix/SWUskn5EWNvNOj9F4tqzT2EXbVYDo5J1a
om/RtzinuVFRV6TwXLmbGPIo8kEE++k3AeJ9ng2DHlSzOEWr10pDKcz26P8E72Hf
LgDtkV24LEPynbyt6MrcD0iAqL0xS01vQpMpmrZmHZb9pATXok4Cm1lIkcSDmvhL
Z6piw9lGhLQ=
=2OMH
-----END PGP SIGNATURE-----
--PEIAKu/WMn1b1Hv9--
