IETF Logo Mail Archive

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

Robert Raszuk <robert@raszuk.net> Sat, 16 May 2015 13:03 UTC

Return-Path: <rraszuk@gmail.com>
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 26CC71A039C for <idr@ietfa.amsl.com>; Sat, 16 May 2015 06:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 5gs8W7T8n7xY for <idr@ietfa.amsl.com>; Sat, 16 May 2015 06:03:27 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD4641A0105 for <idr@ietf.org>; Sat, 16 May 2015 06:03:26 -0700 (PDT)
Received: by obcus9 with SMTP id us9so95812560obc.2 for <idr@ietf.org>; Sat, 16 May 2015 06:03:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=KyUrIJ5wKEISa1eUoKiFRg1kYZZsV1OZ1yomWq7eCjI=; b=YRcvNtwayjPP2xbabmHMZ4cdbxdJ8XzGIrGSta/LlJzsno9aZV3PYlFUfZxyisRLQE Ce4exzSjdlIbyqKm0d0Ccg0mbEOomOEAERdiRkekHRdfNftEftCS2r/ktUfwNecQUEll PDelKfpYX/ECG9rxluNnnQf0XQwNqYV06ps2iEwbK8dzxifmxCuzmSAL0npFLOFL6ybI 36KjvN6YeRfYshvijkvQP1UNNVDO0Ffd9aYhSLmmtOzQ9uyjPlTWfOVOupuMb2re64ko yeKQrLbYMJa8Jz2dx9X66G0eDWbpZ94JyCkY44BPhqTLRJZitEWppMMB7M0a6Ef0MWIS OhFg==
MIME-Version: 1.0
X-Received: by 10.60.82.67 with SMTP id g3mr12403099oey.29.1431781406302; Sat, 16 May 2015 06:03:26 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.202.179.193 with HTTP; Sat, 16 May 2015 06:03:26 -0700 (PDT)
In-Reply-To: <CANL=f0iPLinA6Qr8-r6mev4474UZT9g5Bjng_6+f7xPZ2zdfVg@mail.gmail.com>
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>
Date: Sat, 16 May 2015 15:03:26 +0200
X-Google-Sender-Auth: PXujYxVxQaRIK5WLI6L-D4Ic6Sk
Message-ID: <CA+b+ERmpCfa2ns5bfd7FJvsG_-5jGX+_QG9oBzK0b8GD1yhveg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Daniel Walton <dwalton@cumulusnetworks.com>
Content-Type: multipart/alternative; boundary="047d7b676d521e6a360516329628"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/Eb8K85ixbxamI6jbF9QJoctu3nM>
Cc: idr wg <idr@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: Sat, 16 May 2015 13:03:28 -0000

​Hi Daniel,​



> If DNS is down how does that make knowing the hostname of a LL BGP peer
> useless?
>

​It was not clear from the draft that you would use those to resolve names
also locally (say via temporary caching into hosts file) when learned by
BGP.

I think while the extension you are proposing is indeed minor I would
personnaly see this being solved in general v6 case not just for BGP as
Rajiv mentioned.

Btw are you not running LLDP already on the interfaces ? If so the peer
name is already there. If not adding OpenLLDP (http://open-lldp.org/)
should be a mater of minutes :)


> This sounds far more heavy handed and would be solving a problem that
> we are not attempting to solve :) I just need to know the hostnames of my
> peers.

But it also solves your problem automagically - that is why I have
mentioned it here for consideration of the group.


Cheers,
R.

v2.23.0 | Report a Bug | By Email