IETF Logo Mail Archive

[Idr] draft-bashandy-idr-bgp-repair-label-03

Xuxiaohu <xuxiaohu@huawei.com> Mon, 26 March 2012 08:23 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B399F21F855A for <idr@ietfa.amsl.com>; Mon, 26 Mar 2012 01:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.849
X-Spam-Level:
X-Spam-Status: No, score=0.849 tagged_above=-999 required=5 tests=[AWL=1.094, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wpqtTfhKYUeb for <idr@ietfa.amsl.com>; Mon, 26 Mar 2012 01:23:34 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2014921F8576 for <idr@ietf.org>; Mon, 26 Mar 2012 01:23:31 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AER77164; Mon, 26 Mar 2012 04:23:30 -0400 (EDT)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 26 Mar 2012 01:20:52 -0700
Received: from SZXEML416-HUB.china.huawei.com (10.82.67.155) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 26 Mar 2012 01:20:50 -0700
Received: from SZXEML525-MBS.china.huawei.com ([169.254.8.158]) by szxeml416-hub.china.huawei.com ([10.82.67.155]) with mapi id 14.01.0323.003; Mon, 26 Mar 2012 16:20:43 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: draft-bashandy-idr-bgp-repair-label-03
Thread-Index: Ac0LKG62Z0oP7mVyTVmtlZw8K92vMQ==
Date: Mon, 26 Mar 2012 08:20:43 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02CDF6D3@szxeml525-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.24.1.68]
Content-Type: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE02CDF6D3szxeml525mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 26 Mar 2012 01:25:31 -0700
Subject: [Idr] draft-bashandy-idr-bgp-repair-label-03
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 08:23:36 -0000

Hi co-authors of the abvove draft,



In you draft, it said"As usual, each PE allocates a local label for each prefix it can reach through an external neighbor CE. This is the primary label used for normal traffic forwarding." and "To provide repair path information to all PEs, the PE also allocates a repair label to the prefix if it can reach that prefix via an external neighbor."



Does it mean the external path which the repair label is associated with is a best external path? If so, could you explain what's difference between the above draft and this draft (http://tools.ietf.org/html/draft-xu-idr-best-external-loop-avoidance-00).



BR,

Xiaohu

v2.23.0 | Report a Bug | By Email