IETF Logo Mail Archive

Re: [v6ops] [Idr] BGP Identifier

"UTTARO, JAMES" <ju1738@att.com> Mon, 17 February 2014 15:53 UTC

Return-Path: <ju1738@att.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 679C71A0502; Mon, 17 Feb 2014 07:53:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level:
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 VxV09VfoIYPE; Mon, 17 Feb 2014 07:53:49 -0800 (PST)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 818091A0507; Mon, 17 Feb 2014 07:53:49 -0800 (PST)
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-7.2.1-0) with ESMTP id b8032035.2ac0d0052940.2848596.00-2437.7947596.nbfkord-smmo05.seg.att.com (envelope-from <ju1738@att.com>); Mon, 17 Feb 2014 15:53:47 +0000 (UTC)
X-MXL-Hash: 5302308b42ac272f-7ef366ae0b5dc6619311f68523019213c1665cb8
Received: from unknown [144.160.229.24] (EHLO alpi155.enaf.aldc.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-7.2.1-0) over TLS secured channel with ESMTP id d6032035.0.2848356.00-2179.7946900.nbfkord-smmo05.seg.att.com (envelope-from <ju1738@att.com>); Mon, 17 Feb 2014 15:53:18 +0000 (UTC)
X-MXL-Hash: 5302306e628e96f1-88ebdcbe81aed40c2e5a9316f523ae7dd22fc697
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id s1HFrGDv003001; Mon, 17 Feb 2014 10:53:16 -0500
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id s1HFr7cC002787 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Feb 2014 10:53:12 -0500
Received: from MISOUT7MSGHUBAC.ITServices.sbc.com (MISOUT7MSGHUBAC.itservices.sbc.com [130.9.129.147]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Mon, 17 Feb 2014 15:52:55 GMT
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUBAC.ITServices.sbc.com ([130.9.129.147]) with mapi id 14.03.0174.001; Mon, 17 Feb 2014 10:52:54 -0500
From: "UTTARO, JAMES" <ju1738@att.com>
To: Randy Bush <randy@psg.com>, "Fan, Peng" <fanpeng@chinamobile.com>
Thread-Topic: [Idr] [v6ops] BGP Identifier
Thread-Index: AQHPK4HukH+sv9yQ+kSGj1ZIvBEoEZq5ExoAgABt7ACAAAzhgIAABBwAgAAHYcA=
Date: Mon, 17 Feb 2014 15:52:53 +0000
Message-ID: <B17A6910EEDD1F45980687268941550F0633735A@MISOUT7MSGUSR9I.ITServices.sbc.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>
In-Reply-To: <m21tz22fyz.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.53.251]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=StMnHoy0 c=1 sm=1 a=dhB6nF3YHL5t/Ixux6cINA==:17 a]
X-AnalysisOut: [=ofMgfj31e3cA:10 a=Ml6WOlLKuc4A:10 a=BLceEmwcHowA:10 a=kj9]
X-AnalysisOut: [zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=e_BCuZGg8]
X-AnalysisOut: [NsA:10 a=48vgC7mUAAAA:8 a=yyzX4cs7Mzi1HQJBC4AA:9 a=CjuIK1q]
X-AnalysisOut: [_8ugA:10 a=lZB815dzVvQA:10 a=WEfm6-8eHTEN4XfZ:21 a=IFZ0Xh6]
X-AnalysisOut: [NAL3Oz8jK:21]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <ju1738@att.com>
X-SOURCE-IP: [144.160.229.24]
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/-9hbeVRMPwjeuS9aF0koZK-mGJo
X-Mailman-Approved-At: Mon, 17 Feb 2014 19:33:44 -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: Mon, 17 Feb 2014 15:53:51 -0000

We 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

v2.23.0 | Report a Bug | By Email