Re: [Idr] draft-walton-bgp-hostname-capability-00

[Dinesh Dutt <[e-mail]>]

Hi John,

I appreciate your taking the time to provide alternate suggestions.

On Sat, May 16, 2015 at 7:49 PM, John Heasley <[e-mail]> wrote:

> Am 16.05.2015 um 19:07 schrieb Dinesh Dutt <[e-mail]>:
> >
> > In the data center, you've met the other side, and its you. I don't
> think I said that carrying the hostname was a BGP problem. We see it as a
> way to simplify operations in the DC, by supplementing numbers with names,
> >
>
> If you want to give it a name, then do so in your config. Ie: 'neighbor
> 1.2.3.4 name peerWhoICallJoe' provides 'clear ip bgp peerWhoICallJoeNet',
> usw.
>

Interestingly, what you suggest is where we began originally. But this
makes the box configuration specific to each box. In the data center,
making the configuration as cookie-cutter as possible to ease automation is
a fairly fundamental goal given the size of the network.

Dinesh

>
>  If i am malicious, which i am, and automated, which i may be, i can
> change the name every April Fools day - or every day - or after every
> reboot - or it might move to another device. Your managment should be based
> on a name that you control and is meaningful to _you_. Even if i like the
> like the idea of referring to a peer by name, i want it to be the name/ID
> that i know it by ... In my CRM/database, not whatever goofy name the peer
> has given to the device.
>
>