Re: [v6ops] [Idr] BGP Identifier

"lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com> Tue, 18 February 2014 02:33 UTC

Return-Path: <lizhenqiang@chinamobile.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 CA83E1A030B; Mon, 17 Feb 2014 18:33:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.225
X-Spam-Level:
X-Spam-Status: No, score=-0.225 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RELAY_IS_221=2.222, RP_MATCHES_RCVD=-0.548] 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 7R_Hq1LiDFZe; Mon, 17 Feb 2014 18:33:11 -0800 (PST)
Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.176.64.232]) by ietfa.amsl.com (Postfix) with SMTP id DB6201A0317; Mon, 17 Feb 2014 18:33:09 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.20.12]) by rmmx-oa_allagent01-12001 (RichMail) with SMTP id 2ee15302c5e3bd4-f2bd4; Tue, 18 Feb 2014 10:30:59 +0800 (CST)
X-RM-TRANSID: 2ee15302c5e3bd4-f2bd4
Received: from lizhenqiang (unknown[10.2.52.133]) by rmsmtp-oa_rmapp02-12002 (RichMail) with SMTP id 2ee25302c5e2c63-f48f9; Tue, 18 Feb 2014 10:30:59 +0800 (CST)
X-RM-TRANSID: 2ee25302c5e2c63-f48f9
Date: Tue, 18 Feb 2014 10:33:09 +0800
From: "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
To: =?ISO-8859-1?B?VVRUQVJPLCBKQU1FUw==?= <ju1738@att.com>, "Randy Bush" <randy@psg.com>, fanpeng <fanpeng@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>, <m21tz22fyz.wl%randy@psg.com>, <B17A6910EEDD1F45980687268941550F0633735A@MISOUT7MSGUSR9I.ITServices.sbc.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 0, 108[cn]
Mime-Version: 1.0
Message-ID: <201402181033092475009@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart002576354625_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/uVFeUvJbzkLqpOd-eXRKMGyUGFg
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: Tue, 18 Feb 2014 02:33:14 -0000






Yes we do if we could.

Zhenqiang Li

 From: UTTARO, JAMESDate: 2014-02-17 23:52To: Randy Bush; Fan, PengCC: 'idr wg'; 'V6 Ops List'; 'Robert Raszuk'Subject: Re: [Idr] [v6ops] BGP IdentifierWe endeavor to automate as much as possible as manual/human manipulation usually results in a big error at some point..
 
Jim Uttaro
 
-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Randy Bush
Sent: Monday, February 17, 2014 5:26 AM
To: Fan, Peng
Cc: 'idr wg'; 'V6 Ops List'; 'Robert Raszuk'
Subject: Re: [Idr] [v6ops] BGP Identifier
 
> 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
 
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr
 
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr