IETF Logo Mail Archive

Re: [v6ops] [Idr] BGP Identifier

Jon Mitchell <jrmitche@puck.nether.net> Sat, 15 February 2014 01:47 UTC

Return-Path: <jrmitche@puck.nether.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 AB4C31A00A7; Fri, 14 Feb 2014 17:47:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-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 WqAZtsOpDN-u; Fri, 14 Feb 2014 17:47:40 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 3881A1A0018; Fri, 14 Feb 2014 17:47:40 -0800 (PST)
Received: from [192.168.1.7] (pool-72-73-23-184.clppva.fios.verizon.net [72.73.23.184]) (authenticated bits=0) by puck.nether.net (8.14.7/8.14.5) with ESMTP id s1F1lavc004489 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 14 Feb 2014 20:47:37 -0500
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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> <916A3488-34C9-4A12-BE98-0465978CB41B@earthlink.net>
From: Jon Mitchell <jrmitche@puck.nether.net>
In-Reply-To: <916A3488-34C9-4A12-BE98-0465978CB41B@earthlink.net>
Message-Id: <1954AEE5-C355-42DD-B102-F25488AFBD7F@puck.nether.net>
Date: Fri, 14 Feb 2014 20:47:22 -0500
To: Mitchell Erblich <erblichs@earthlink.net>
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (11B554a)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.7 (puck.nether.net [204.42.254.5]); Fri, 14 Feb 2014 20:47:37 -0500 (EST)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/Qf1udhCQVOB7_kgNNf3OtTs38fs
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 01:47:41 -0000

> On Feb 14, 2014, at 7:49 PM, Mitchell Erblich <erblichs@earthlink.net> wrote:
> 
> 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..

Well, this seems an interesting argument.  This capability is proposed as a problem for IPv6 only networks needing a 128 bit identifier. 

Randy argues for local assignment of 32 bit identifier as sufficient for BGP and you say not good enough for consistency sake you want all protocols to choose the same loopback based number naming 3 protocols that have 32 bit identifiers, 1 protocol with no identifier, and 1 protocol with 48 bit sys-id.  Since RIP is mentioned, why not throw in EIGRP (32 bit) as well, since this supports IPv6 unlike OSPFv2...

So looking at the list I think we can all say for consistency and simplicity across protocols operator should prefer 32 bit values based on local loopback if IPv4 enabled, or 32 bit self administered numbers if IPv6 only so they can keep one identifier recognizable across all protocols for their routers w/o extending every protocol in the list to support 128 bit identifiers...

-Jon

v2.23.0 | Report a Bug | By Email