Re: [v6ops] BGP Identifier

Shane Amante <shane@castlepoint.net> Sat, 15 February 2014 15:53 UTC

Return-Path: <shane@castlepoint.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B40A1A0040 for <v6ops@ietfa.amsl.com>; Sat, 15 Feb 2014 07:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NORMAL_HTTP_TO_IP=0.001] 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 738oLU5-8Cxp for <v6ops@ietfa.amsl.com>; Sat, 15 Feb 2014 07:53:44 -0800 (PST)
Received: from mail.tcb.net (mail.tcb.net [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id 0620E1A00EC for <v6ops@ietf.org>; Sat, 15 Feb 2014 07:53:44 -0800 (PST)
Received: from dspam (unknown [127.0.0.1]) by mail.tcb.net (Postfix) with SMTP id 4F557300082 for <v6ops@ietf.org>; Sat, 15 Feb 2014 15:53:42 +0000 (UTC)
Received: from [172.16.15.4] (97-122-112-90.hlrn.qwest.net [97.122.112.90]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.tcb.net (Postfix) with ESMTPSA id 67F8B30007A; Sat, 15 Feb 2014 08:53:41 -0700 (MST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <570C72FF-349F-4CAF-9EA7-9A847CC0420D@steffann.nl>
Date: Sat, 15 Feb 2014 07:53:39 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <32ACD29A-AF81-498F-B849-A018D928591F@castlepoint.net>
References: <12AA6714-4BBE-4ACE-8191-AA107D04FBF4@cisco.com> <m2wqgyjifd.wl%randy@psg.com> <B4D8E670-3823-468F-AA41-FE14754F168C@steffann.nl> <11C9319C-A886-4B9E-9E8D-6947A73DB08E@castlepoint.net> <69e0019b-c13d-4989-b330-d470c37f2ee2@email.android.com> <13E534FF-C97D-4B07-BA34-E62DED3DBE88@castlepoint.net> <570C72FF-349F-4CAF-9EA7-9A847CC0420D@steffann.nl>
To: Sander Steffann <sander@steffann.nl>
X-Mailer: Apple Mail (2.1827)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Sat Feb 15 08:53:42 2014
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 52ff8d8642078399820781
X-DSPAM-Factors: 27, records+#+#+#+3, 0.40000, in+networks, 0.40000, Steffann+#+steffann, 0.40000, unfamiliar+with, 0.40000, has+#+#+often, 0.40000, can+always, 0.40000, DNS+And, 0.40000, past+#+#+#+found, 0.40000, helpful+in, 0.40000, to+#+the, 0.40000, do+#+the, 0.40000, time+#+#+using, 0.40000, hey+#+#+always, 0.40000, isis+#+#+finding, 0.40000, it+#+#+#+in, 0.40000, wrote+#+use, 0.40000, is+#+#+#+i, 0.40000, do+#+#+problem, 0.40000, wrote+Op, 0.40000, more+#+than, 0.40000, networks+#+I've, 0.40000, that+#+#+#+out, 0.40000, tell+#+#+that, 0.40000, diagnosing+#+#+brokenness, 0.40000, where+#+#+#+is, 0.40000, where+#+#+#+is, 0.40000, in+#+#+#+duplicate, 0.40000
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/DWcNoJvhMwzAKBw9uNHyG6rKYbY
Cc: idr wg <idr@ietf.org>, V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] BGP Identifier
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 15:53:45 -0000

On Feb 15, 2014, at 7:26 AM, Sander Steffann <sander@steffann.nl> wrote:
> Op 15 feb. 2014, om 16:13 heeft Shane Amante <shane@castlepoint.net> het volgende geschreven:
>> On Feb 15, 2014, at 12:55 AM, Randy Bush <randy@psg.com> wrote:
>>> I use this funny thing called DNS. 
>> 
>> And that has what to do with the problem of determining liveness or determining where in the topology is a ROUTER_ID?
> 
> And what does an integer called ROUTER_ID tell you about that?

In my past experience, I have found that -- particularly in new networks that I'm unfamiliar with -- looking at the output of "show (ospf|isis) database extensive", finding a ROUTER_ID that originated the LSA/LSPDU and performing a ping and/or traceroute to it to verify the sanity of where in the topology that ROUTER_ID is located has been helpful in rapidly diagnosing and fixing brokenness.  Yes, I will admit that it is not a panacea (i.e.: it does not help in the case of duplicate ROUTER_ID's), but 99% of the time it's often using that information to figure out where traffic is, or is not, going to.

Look, it's your network, do whatever pleases you.  But, in networks that I've run, having congruency between the ROUTER_ID and a Loopback address has helped more often than not.


> And hey, you can always create records like
>  1.2.3.4.router-id.castlepoint.net IN CNAME router1.somewhere.castlepoint.net

And, when your DNS server is unreachable because you've got a network issue, what then?

-shane