IETF Logo Mail Archive

Re: [v6ops] [Idr] BGP Identifier

Shane Amante <shane@castlepoint.net> Wed, 19 February 2014 18:41 UTC

Return-Path: <shane@castlepoint.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 B37AA1A01FB for <v6ops@ietfa.amsl.com>; Wed, 19 Feb 2014 10:41:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=unavailable
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 2n-0dDPsvBPd for <v6ops@ietfa.amsl.com>; Wed, 19 Feb 2014 10:41:38 -0800 (PST)
Received: from mail.tcb.net (mail.tcb.net [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id 620381A014C for <v6ops@ietf.org>; Wed, 19 Feb 2014 10:41:38 -0800 (PST)
Received: from dspam (unknown [127.0.0.1]) by mail.tcb.net (Postfix) with SMTP id 4334F30007A for <v6ops@ietf.org>; Wed, 19 Feb 2014 18:41:35 +0000 (UTC)
Received: from shanes-mbp-5.ciena.com (unknown [205.150.9.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.tcb.net (Postfix) with ESMTPSA id CC4FF300052; Wed, 19 Feb 2014 11:41:29 -0700 (MST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <20140218160639.GC12348@pfrc>
Date: Wed, 19 Feb 2014 10:41:24 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E7D0DA0-0CC0-465C-8BA1-81809B1FEF80@castlepoint.net>
References: <12AA6714-4BBE-4ACE-8191-AA107D04FBF4@cisco.com> <m2iosdta7m.wl%randy@psg.com> <2014021811305909988540@chinamobile.com> <CAL9jLaa6fXL+FFNFgdK257dbHGXqm4YBRfMEocoQPEAczPmH-Q@mail.gmail.com> <00d501cf2c6a$36c995d0$a45cc170$@chinamobile.com> <20140218160639.GC12348@pfrc>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.1827)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Wed Feb 19 11:41:35 2014
X-DSPAM-Confidence: 0.9899
X-DSPAM-Improbability: 1 in 9809 chance of being spam
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 5304fadf42071089216475
X-DSPAM-Factors: 27, Mime-Version*OS+X, 0.01000, Mime-Version*X+#+#+1827, 0.01000, Cc*List+#+ietf.org, 0.01000, From*Amante+shane, 0.01000, Cc*List+v6ops, 0.01000, Cc*idr+wg, 0.01000, Subject*v6ops+BGP, 0.01000, Cc*Ops+#+v6ops, 0.01000, Mime-Version*OS+#+#+7.1, 0.01000, Cc*idr+ietf.org, 0.01000, Mime-Version*Mac+#+#+#+7.1, 0.01000, Cc*wg+#+ietf.org, 0.01000, Cc*V6+#+#+#+ietf.org, 0.01000, On+#+#+2014, 0.01000, Cc*Ops+List, 0.01000, Subject*BGP+Identifier, 0.01000, Cc*idr+#+#+ietf.org, 0.01000, Cc*V6+#+#+v6ops, 0.01000, Mime-Version*7.1+1827, 0.01000, Cc*V6+Ops, 0.01000, Mime-Version*1.0+Mac, 0.01000, From*Shane+#+shane, 0.01000, Cc*Ops+#+#+ietf.org, 0.01000, Cc*idr+#+idr, 0.01000, From*Shane Amante <shane@castlepoint.net>, 0.01000, is+#+a, 0.01000, 2014+#+#+#+AM, 0.01000
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/6Yb_t2c1WmDxpRGMLF3ZC-v0m1g
Cc: idr wg <idr@ietf.org>, V6 Ops List <v6ops@ietf.org>, JAMES <ju1738@att.com>
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: Wed, 19 Feb 2014 18:41:40 -0000

On Feb 18, 2014, at 8:06 AM, Jeffrey Haas <jhaas@pfrc.org> wrote:
> The fact that this number has been able to receive a mapping to a real
> address has been extremely operationally useful.
> 
> What I would instead suggest is finding a mechanism by which the unique
> router-ID can be mapped easily to such addresses.  I don't believe that BGP is
> the right place to do this.

+1

-shane

v2.23.0 | Report a Bug | By Email