Re: [v6ops] [Idr] BGP Identifier

"Fan, Peng" <fanpeng@chinamobile.com> Sun, 16 February 2014 16:28 UTC

Return-Path: <fanpeng@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 0CBCB1A00E6; Sun, 16 Feb 2014 08:28:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.216
X-Spam-Level:
X-Spam-Status: No, score=-0.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RELAY_IS_221=2.222, RP_MATCHES_RCVD=-0.548, T_FILL_THIS_FORM_SHORT=0.01] 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 bYvDWbuYyZtR; Sun, 16 Feb 2014 08:28:39 -0800 (PST)
Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.176.64.232]) by ietfa.amsl.com (Postfix) with SMTP id C56961A002C; Sun, 16 Feb 2014 08:28:38 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.20.21]) by rmmx-oa_allagent02-12002 (RichMail) with SMTP id 2ee25300e6ac8e3-308e3; Mon, 17 Feb 2014 00:26:21 +0800 (CST)
X-RM-TRANSID: 2ee25300e6ac8e3-308e3
Received: from X6X8D79D8F49E2 (unknown[125.97.246.90]) by rmsmtp-oa_rmapp03-12003 (RichMail) with SMTP id 2ee35300e6ac00d-b4a6e; Mon, 17 Feb 2014 00:26:21 +0800 (CST)
X-RM-TRANSID: 2ee35300e6ac00d-b4a6e
From: "Fan, Peng" <fanpeng@chinamobile.com>
To: "'Randy Bush'" <randy@psg.com>, "'Fred Baker'" <fred@cisco.com>
References: <12AA6714-4BBE-4ACE-8191-AA107D04FBF4@cisco.com> <m2wqgyjifd.wl%randy@psg.com>
In-Reply-To: <m2wqgyjifd.wl%randy@psg.com>
Date: Mon, 17 Feb 2014 00:28:32 +0800
Message-ID: <006801cf2b34$22837cd0$678a7670$@chinamobile.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKMyHwF2uN/MFx2cQfT+KJLjKc69QG64jb+mS7we9A=
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/DF6_NV2Fk9I2Vjc2jAsAi9qbtcI
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: Sun, 16 Feb 2014 16:28:42 -0000

Hi Randy, and all,

Thanks for the discussion and sorry for the late. Assigning an id is not a
difficult issue, especially on a single router. But what number is to be
assigned might be an issue, especially in an ISP's large network, in order
to guarantee the uniqueness of the ids. In our network this kind of numeric
resources, e.g. IP addresses and cell phone numbers, is planned in advance
(usually with a careful designed numbering rule), and then delivered to
admins who located at different parts of the network. In the IPv4 world, we
take advantage of an IPv4 address, as it by nature an ideal id and fits into
the 32-bit length, and could be helpful in OAM. So perhaps we can use a
similar approach in an IPv6-only world, then the admins don't have to bother
to worry how to choose the ids. An id is not necessarily an IP address, but
IP address is a perfect candidate for an id.

Thanks and regards,
Peng

> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Randy Bush
> Sent: Friday, February 14, 2014 2:52 PM
> To: Fred Baker
> Cc: idr wg; V6 Ops List
> Subject: Re: [Idr] [v6ops] BGP Identifier
> 
> > http://tools.ietf.org/html/draft-fan-idr-ipv6-bgp-id
> >   "IPv6 BGP Identifier Capability for BGP-4", Peng Fan, Zhenqiang Li,
> >   2014-02-12
> 
> please no.  if you can not assign a unique four octet integer to each
router in
> your network, then you have much bigger problems.  and adding a capability
> and more complexity to try to patch over your inability to configure your
routers
> will just compound your problems.
> 
> randy
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr