Re: [v6ops] [Idr] BGP Identifier
"lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com> Tue, 18 February 2014 11:36 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 8A3A41A0480; Tue, 18 Feb 2014 03:36:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.375
X-Spam-Level:
X-Spam-Status: No, score=0.375 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6, 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 Ew7284S6lqcU; Tue, 18 Feb 2014 03:36:42 -0800 (PST)
Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.176.64.232]) by ietfa.amsl.com (Postfix) with SMTP id 936E51A060D; Tue, 18 Feb 2014 03:36:40 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.20.12]) by rmmx-oa_allagent02-12002 (RichMail) with SMTP id 2ee253034538c21-5ac21; Tue, 18 Feb 2014 19:34:16 +0800 (CST)
X-RM-TRANSID: 2ee253034538c21-5ac21
Received: from lizhenqiang (unknown[10.2.52.133]) by rmsmtp-oa_rmapp02-12002 (RichMail) with SMTP id 2ee253034534311-fc8f6; Tue, 18 Feb 2014 19:34:16 +0800 (CST)
X-RM-TRANSID: 2ee253034534311-fc8f6
Date: Tue, 18 Feb 2014 19:36:26 +0800
From: "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
To: "UTTARO, JAMES" <ju1738@att.com>, Randy Bush <randy@psg.com>
References: <12AA6714-4BBE-4ACE-8191-AA107D04FBF4@cisco.com>, <m2iosdta7m.wl%randy@psg.com>, <2014021810513701058825@chinamobile.com>, <B17A6910EEDD1F45980687268941550F06341989@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: <201402181936265926758@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart620801886436_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/SHDXqh4WO4TxIDARgOU7Dg41amw
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 11:36:45 -0000
Thank you very much for your information, Jim.We also have some tools to help us to plan and operate our networks. However at present none of the tools can satisfy the requirment of this draft. Anyway, you do not think it is a problem to plan the 32-bit BGP ID for a very large scale IPv6-only network? lizhenqiang@chinamobile.com From: UTTARO, JAMESDate: 2014-02-18 19:27To: lizhenqiang@chinamobile.com; Randy BushCC: 'idr wg'; 'V6 Ops List'; 'Robert Raszuk'Subject: RE: [Idr] [v6ops] BGP Identifier We have developed numerous configuration tools that create/mod PE, RR configs. We also have lots of tools that speak to the network in a live sense to get health, stats … All of the raw material is readily available. TBH I cannot speak to you about our solutions in anymore depth.. Jim Uttaro From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of lizhenqiang@chinamobile.com Sent: Monday, February 17, 2014 9:52 PM To: Randy Bush Cc: 'idr wg'; 'V6 Ops List'; 'Robert Raszuk' Subject: Re: [Idr] [v6ops] BGP Identifier Tell me please the large provider that you know has his own automatic configuration tools. I would like to contact him to learn from him. lizhenqiang@chinamobile.com From: Randy Bush Date: 2014-02-18 10:40 To: lizhenqiang@chinamobile.com CC: fanpeng; 'idr wg'; 'V6 Ops List'; 'Robert Raszuk' Subject: Re: [Idr] [v6ops] BGP Identifier > Do you have such tools to config your network? Or do you know the > vendor that provide such tools?Indeed, such programmatic generation > tools are good for network plan. But the logic in the tools is > complecated especially for a very large network with hierarchical > operation as Peng Fan mentioned. there are products in the space, but the large providers i know who configure programatically developed their own. there are not enough large providers not suffering from 'not invented here' to make a reasonable customer base for serious software development. but it pays for itself, so smart folk who develop it. randy
- [v6ops] BGP Identifier Fred Baker (fred)
- Re: [v6ops] BGP Identifier Randy Bush
- Re: [v6ops] [Idr] BGP Identifier Robert Raszuk
- Re: [v6ops] BGP Identifier Sander Steffann
- Re: [v6ops] BGP Identifier Jared Mauch
- Re: [v6ops] BGP Identifier Rajiv Asati (rajiva)
- Re: [v6ops] BGP Identifier Owen DeLong
- Re: [v6ops] [Idr] BGP Identifier Randy Bush
- Re: [v6ops] [Idr] BGP Identifier Mitchell Erblich
- Re: [v6ops] [Idr] BGP Identifier Mitchell Erblich
- Re: [v6ops] [Idr] BGP Identifier Jon Mitchell
- Re: [v6ops] BGP Identifier Shane Amante
- Re: [v6ops] BGP Identifier Randy Bush
- Re: [v6ops] BGP Identifier Sander Steffann
- Re: [v6ops] BGP Identifier Shane Amante
- Re: [v6ops] BGP Identifier Sander Steffann
- Re: [v6ops] BGP Identifier Shane Amante
- Re: [v6ops] BGP Identifier Nick Hilliard
- Re: [v6ops] [Idr] BGP Identifier David Farmer
- Re: [v6ops] [Idr] BGP Identifier Sander Steffann
- Re: [v6ops] BGP Identifier Owen DeLong
- Re: [v6ops] [Idr] BGP Identifier Randy Bush
- Re: [v6ops] [Idr] BGP Identifier Fan, Peng
- Re: [v6ops] [Idr] BGP Identifier Shane Amante
- Re: [v6ops] [Idr] BGP Identifier Robert Raszuk
- Re: [v6ops] [Idr] BGP Identifier Christopher Morrow
- Re: [v6ops] [Idr] BGP Identifier Fan, Peng
- Re: [v6ops] [Idr] BGP Identifier Gert Doering
- Re: [v6ops] [Idr] BGP Identifier Randy Bush
- Re: [v6ops] [Idr] BGP Identifier Fan, Peng
- Re: [v6ops] [Idr] BGP Identifier Fan, Peng
- Re: [v6ops] [Idr] BGP Identifier Randy Bush
- Re: [v6ops] [Idr] BGP Identifier joel jaeggli
- Re: [v6ops] [Idr] BGP Identifier David Farmer
- Re: [v6ops] [Idr] BGP Identifier lizhenqiang@chinamobile.com
- Re: [v6ops] [Idr] BGP Identifier lizhenqiang@chinamobile.com
- Re: [v6ops] [Idr] BGP Identifier Randy Bush
- Re: [v6ops] [Idr] BGP Identifier lizhenqiang@chinamobile.com
- Re: [v6ops] [Idr] BGP Identifier lizhenqiang@chinamobile.com
- Re: [v6ops] [Idr] BGP Identifier Randy Bush
- Re: [v6ops] [Idr] BGP Identifier Christopher Morrow
- Re: [v6ops] [Idr] BGP Identifier Fan, Peng
- Re: [v6ops] [Idr] BGP Identifier UTTARO, JAMES
- Re: [v6ops] [Idr] BGP Identifier Christopher Morrow
- Re: [v6ops] [Idr] BGP Identifier lizhenqiang@chinamobile.com
- Re: [v6ops] [Idr] BGP Identifier lizhenqiang@chinamobile.com
- Re: [v6ops] [Idr] BGP Identifier joel jaeggli
- Re: [v6ops] [Idr] BGP Identifier George Michaelson
- Re: [v6ops] [Idr] BGP Identifier joel jaeggli
- Re: [v6ops] [Idr] BGP Identifier Randy Bush
- Re: [v6ops] [Idr] BGP Identifier Fan, Peng
- Re: [v6ops] [Idr] BGP Identifier Randy Bush
- Re: [v6ops] [Idr] BGP Identifier lizhenqiang@chinamobile.com
- Re: [v6ops] [Idr] BGP Identifier Jared Mauch
- Re: [v6ops] [Idr] BGP Identifier Fan, Peng
- Re: [v6ops] [Idr] BGP Identifier UTTARO, JAMES
- Re: [v6ops] [Idr] BGP Identifier Jeffrey Haas
- Re: [v6ops] [Idr] BGP Identifier lizhenqiang@chinamobile.com
- Re: [v6ops] [Idr] BGP Identifier Shane Amante
- Re: [v6ops] [Idr] BGP Identifier Randy Bush
- Re: [v6ops] [Idr] BGP Identifier joel jaeggli
- Re: [v6ops] [Idr] BGP Identifier Jeffrey Haas
- Re: [v6ops] [Idr] BGP Identifier Robert Raszuk
- Re: [v6ops] [Idr] BGP Identifier Jeffrey Haas