-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul,
If my memory serves me correct, Richard presented traceroute presto at nanog47 that covered location identifiers. HTH, regards, /virendra 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." > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFLm7t7pbZvCIJx1bcRAin3AJ4r69FiLr+qC6KpVn3pfPnuEWRQCgCeMeRU BbhE1ExSlGBTGU/rWk+3pj4= =TeNX -----END PGP SIGNATURE-----
