IETF Logo Mail Archive

Re: [v6ops] [Idr] BGP Identifier

Mitchell Erblich <erblichs@earthlink.net> Sat, 15 February 2014 00:49 UTC

Return-Path: <erblichs@earthlink.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 3520A1A01E2; Fri, 14 Feb 2014 16:49:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level:
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548] 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 WPoEd4F_jE1O; Fri, 14 Feb 2014 16:49:12 -0800 (PST)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 821371A0212; Fri, 14 Feb 2014 16:49:12 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=gjwbHH3s5kyTCpfu1lnK7xTWZ9nYk/I6jx7H41WcfcSpHEAvk1ujB5flWQTPQGPz; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [76.21.83.101] (helo=[10.0.1.2]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <erblichs@earthlink.net>) id 1WETRO-0000jL-8r; Fri, 14 Feb 2014 19:49:10 -0500
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="windows-1252"
From: Mitchell Erblich <erblichs@earthlink.net>
In-Reply-To: <m24n41i6dq.wl%randy@psg.com>
Date: Fri, 14 Feb 2014 16:49:05 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <916A3488-34C9-4A12-BE98-0465978CB41B@earthlink.net>
References: <12AA6714-4BBE-4ACE-8191-AA107D04FBF4@cisco.com> <m2wqgyjifd.wl%randy@psg.com> <CA+b+ERk=DEge0cAxTsFh9Vnd3YC3eg_Pj+JETZzxDfsZAgPYUA@mail.gmail.com> <E62B2F08-F7AE-4307-8586-07A9F8E5584E@earthlink.net> <m24n41i6dq.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1283)
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec79792f28e0e5f181b2a3e71d40ce8c08c8350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 76.21.83.101
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/BNNmyF-DenBRLK-s-do53Ljr3Gw
X-Mailman-Approved-At: Fri, 14 Feb 2014 17:17:49 -0800
Cc: idr wg <idr@ietf.org>, V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] [Idr] 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 00:49:14 -0000

Randy

	A router-id is a router-id.

	Do you think that every protocol that is enabled on the router should have a different router-id?

	So, if you have enabled RIP, OSPFv2, OSPFv3, ISIS, BGP, etc, then for consistency basis, I think the router SHOULD have 1 router-id..

	Now… how many implementations have 1 and why shouldn't an admin attempt to have a router with as few router-ids as possible?  Best 1 unique router-id accross all its enabled and not enabled protocols.

	So, if you redistributes OSPF routes into BGP (RFC 1403), wouldn't is be easier to admin with each router having a single router-id?

	Mitchell Erblich

On Feb 14, 2014, at 4:09 PM, Randy Bush wrote:

>> I think that some LAN protocols prefer a loopback (assume always up)
>> addr and then secondarily an interface addr.
> 
> interesting.  and what LAN protocols use the BGP RouterID? 
> 
> randy

v2.23.0 | Report a Bug | By Email