IETF Logo Mail Archive

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

John Heasley <heas@shrubbery.net> Sun, 17 May 2015 02:49 UTC

Return-Path: <heas@shrubbery.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01D3E1A8925; Sat, 16 May 2015 19:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.212
X-Spam-Level:
X-Spam-Status: No, score=-4.212 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id doa9HCCYA9YW; Sat, 16 May 2015 19:49:45 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id B13A51A8924; Sat, 16 May 2015 19:49:45 -0700 (PDT)
Received: from [100.121.87.58] (250.sub-70-215-14.myvzw.com [70.215.14.250]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by guelah.shrubbery.net (Postfix) with ESMTPSA id 1E7625AFC7; Sun, 17 May 2015 02:49:45 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: John Heasley <heas@shrubbery.net>
X-Mailer: iPad Mail (12F69)
In-Reply-To: <CABg5FUVTSJNF2NOeN1m9ESUzQo3HVNu-fut5PTuHZ+LTigD4eQ@mail.gmail.com>
Date: Sat, 16 May 2015 22:49:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEBB5F68-5A6B-472F-BDAC-997D9250CEA2@shrubbery.net>
References: <CANL=f0h9ZV+SPr+2vcx2dEk4O9MxBAZJEU7xgHZDC=ep2g2r-g@mail.gmail.com> <m2bnhlwaov.wl%randy@psg.com> <20150516015819.5849234.74476.67011@gmail.com> <CANL=f0gAfs9f-Jt7r3bxMfB7f3Ta+funv8nvmkiCmFsQfGHTcg@mail.gmail.com> <CA+b+ERmY46GHLJUhi5PzwyVJ4Wcns_R11QXC=oLMzAXrYi-v2g@mail.gmail.com> <CABg5FUV5Z+S_m6V7=dB_cuOZpDV-MS_cV+mhwERtjaNCiNfT2w@mail.gmail.com> <CA+b+ERmCpjbBmNAeFyNm6_KTWtOB41Zge559O4jbtEjwKG+yXg@mail.gmail.com> <CABg5FUVSq4Xunivo3tBNh0=x+W=ZOD9pUYGWs18EcuXiFG-4MQ@mail.gmail.com> <CA+b+ER=m_LttyMumi+JLd1cfTLqk16RAQgfbX4qmxGAh1k5Wxw@mail.gmail.com> <CANL=f0iPLinA6Qr8-r6mev4474UZT9g5Bjng_6+f7xPZ2zdfVg@mail.gmail.com> <FC7F6336-4846-4C4C-B002-4DE255F10B2A@exa-networks.co.uk> <89600117-8199-45E0-BB06-C69E94091C17@shrubbery.net> <CABg5FUVTSJNF2NOeN1m9ESUzQo3HVNu-fut5PTuHZ+LTigD4eQ@mail.gmail.com>
To: Dinesh Dutt <ddutt@cumulusnetworks.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/2wxNR6WJeruu2B5ChhriNyAZkNk>
Cc: idr wg <idr@ietf.org>, Robert Raszuk <robert@raszuk.net>, "idr-bounces@ietf.org" <idr-bounces@ietf.org>
Subject: Re: [Idr] draft-walton-bgp-hostname-capability-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 May 2015 02:49:47 -0000

Am 16.05.2015 um 19:07 schrieb Dinesh Dutt <ddutt@cumulusnetworks.com>:
> 
> 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.

 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.

v2.23.0 | Report a Bug | By Email