IETF Logo Mail Archive

Re: [v6ops] [Idr] BGP Identifier

Randy Bush <randy@psg.com> Mon, 17 February 2014 10:25 UTC

Return-Path: <randy@psg.com>
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 6A0C21A03C3; Mon, 17 Feb 2014 02:25:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 FJojVpsLArH4; Mon, 17 Feb 2014 02:25:48 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id BB78F1A00DD; Mon, 17 Feb 2014 02:25:48 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WFLOQ-00024C-SU; Mon, 17 Feb 2014 10:25:43 +0000
Date: Mon, 17 Feb 2014 18:25:40 +0800
Message-ID: <m21tz22fyz.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Fan, Peng" <fanpeng@chinamobile.com>
In-Reply-To: <002401cf2bc8$8d1a7a50$a74f6ef0$@chinamobile.com>
References: <12AA6714-4BBE-4ACE-8191-AA107D04FBF4@cisco.com> <m2wqgyjifd.wl%randy@psg.com> <006801cf2b34$22837cd0$678a7670$@chinamobile.com> <m2a9dqfr6k.wl%randy@psg.com> <009e01cf2b8b$26a43d20$73ecb760$@chinamobile.com> <CA+b+ERnD8yeeT-KzNZzJU4ZJYqMSW9YjD5JYdwhDR=dPHfuSkw@mail.gmail.com> <002401cf2bc8$8d1a7a50$a74f6ef0$@chinamobile.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/LKQxMYwgG2GeE_JbtV1rUzNLGO4
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: Mon, 17 Feb 2014 10:25:50 -0000

> Yes that is a possible solution for troubleshooting, once the router_id has
> been determined. But how do you determine at first the value of a.b.c.d when
> there is no ipv4 address to be referred to, especially in an automatic
> manner? Beforehand planning work for the ids for the entire network is
> something I am concerned with :)

all your comments are symptoms of the insanity of trying to configure a
large network manually.  this went out of fashion in the last century,
and we do not try to compensate for insanity through protocol
modification.

randy

v2.23.0 | Report a Bug | By Email