Re: [v6ops] [Idr] BGP Identifier

Gert Doering <gert@space.net> Mon, 17 February 2014 10:13 UTC

Return-Path: <gert@Space.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 B1CEA1A0477 for <v6ops@ietfa.amsl.com>; Mon, 17 Feb 2014 02:13:27 -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=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 221fdNNcf3bv for <v6ops@ietfa.amsl.com>; Mon, 17 Feb 2014 02:13:25 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) by ietfa.amsl.com (Postfix) with ESMTP id 1F4931A03C7 for <v6ops@ietf.org>; Mon, 17 Feb 2014 02:13:25 -0800 (PST)
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id CE10162EE1 for <v6ops@ietf.org>; Mon, 17 Feb 2014 11:13:21 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id A2C8962EDF for <v6ops@ietf.org>; Mon, 17 Feb 2014 11:13:21 +0100 (CET)
Received: (qmail 24575 invoked by uid 1007); 17 Feb 2014 11:13:21 +0100
Date: Mon, 17 Feb 2014 11:13:21 +0100
From: Gert Doering <gert@space.net>
To: "Fan, Peng" <fanpeng@chinamobile.com>
Message-ID: <20140217101321.GI75390@Space.Net>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002401cf2bc8$8d1a7a50$a74f6ef0$@chinamobile.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/lNTvbQVhk_7VDNheSHyc2IF5mLQ
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:13:27 -0000

Hi,

On Mon, Feb 17, 2014 at 06:10:57PM +0800, Fan, Peng wrote:
> 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 :)

How do you plan transit network and loopback IP assignment?

See, it's quite doable.

(Assign loopback addresses in a way that you can use the last 32 bits as 
router ID, done)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279