IETF Logo Mail Archive

RE: New Version Notification for draft-zhang-l3vpn-label-sharing-00.txt

"Nagendra Kumar (naikumar)" <naikumar@cisco.com> Fri, 19 July 2013 08:15 UTC

Return-Path: <naikumar@cisco.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8776611E81FF for <l3vpn@ietfa.amsl.com>; Fri, 19 Jul 2013 01:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 iwOqZjR+E71u for <l3vpn@ietfa.amsl.com>; Fri, 19 Jul 2013 01:15:20 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 9D53C11E814F for <l3vpn@ietf.org>; Fri, 19 Jul 2013 01:15:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2920; q=dns/txt; s=iport; t=1374221718; x=1375431318; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=RRVuRsDEH2/y/Dts8GEmJx4nFL5MnKP1BssnjsCM63E=; b=LLI+BoB3F67I83ah7qaNKQF9mGoTK55YSm60mP3E0GuMTVSCW+EIUqlo DHKNlOii2jRZDr5rMWihG/BvTA7YD6TE/9dfm9yPxflWtVoWeulDH+SAu p/Wf3okGmNHZ3nZRsfjA/W6wwwEAdsl1G7I4wgD34sd6BuVJPeEqBZ9or o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAGb06FGtJV2c/2dsb2JhbABagwY1UIMGvUEXdxZ0giQBAQEEIxFDDgQCAQgRBAEBAwIGHQMCAgIwFAEICAIEARIIAYgHDKRVkUaBKI0cgRo4BoJVM24DmQaQJIMSgio
X-IronPort-AV: E=Sophos;i="4.89,700,1367971200"; d="scan'208";a="236845830"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP; 19 Jul 2013 08:15:18 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6J8FHDn031809 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 19 Jul 2013 08:15:17 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.100]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Fri, 19 Jul 2013 03:15:17 -0500
From: "Nagendra Kumar (naikumar)" <naikumar@cisco.com>
To: Mingui Zhang <zhangmingui@huawei.com>, "l3vpn@ietf.org" <l3vpn@ietf.org>
Subject: RE: New Version Notification for draft-zhang-l3vpn-label-sharing-00.txt
Thread-Topic: New Version Notification for draft-zhang-l3vpn-label-sharing-00.txt
Thread-Index: AQHOgS6cBWFI1KLT1U2mnmg/9jFYHplrojgAgAALBLA=
Date: Fri, 19 Jul 2013 08:15:16 +0000
Message-ID: <47E76F08F1BCF5458111C1939C7B9C4610268B3F@xmb-rcd-x03.cisco.com>
References: <4552F0907735844E9204A62BBDD325E7335C721B@nkgeml508-mbx.china.huawei.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E7335C721B@nkgeml508-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.103.238.67]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 08:15:26 -0000

Hi Mingui,

I couldn’t see any point mentioned in this draft on how egress PEs will assign same VPN label for the prefix. 

Can you please share the same?. Sorry, if I am missing something in the doc.

Regards,
nagendra

-----Original Message-----
From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf Of Mingui Zhang
Sent: Friday, July 19, 2013 1:16 PM
To: l3vpn@ietf.org
Subject: FW: New Version Notification for draft-zhang-l3vpn-label-sharing-00.txt

Dear all,

We have submitted a new draft: Label Sharing for Fast PE Protection.

   This draft designs a simple method to be used by SPs to achieve fast PE protection, utilizing the deployment of redundant egress PEs.

Comments are welcome.

Regards,
Mingui

>-----Original Message-----

A new version of I-D, draft-zhang-l3vpn-label-sharing-00.txt
has been successfully submitted by Mingui Zhang and posted to the IETF repository.

Filename:	 draft-zhang-l3vpn-label-sharing
Revision:	 00
Title:		 Label Sharing for Fast PE Protection
Creation date:	 2013-07-12
Group:		 Individual Submission
Number of pages: 12
URL:             http://www.ietf.org/internet-drafts/draft-zhang-l3vpn-label-sharing-00.txt
Status:          http://datatracker.ietf.org/doc/draft-zhang-l3vpn-label-sharing
Htmlized:        http://tools.ietf.org/html/draft-zhang-l3vpn-label-sharing-00


Abstract:
   This document describes a method to be used by Service Providers to
   provide fast protection of VPN connections for a CE. Egress PEs in a
   redundant group always assign the same label for VPN routes from a
   VRF. These egress PEs create a BGP virtual Next Hop (vNH) in the
   domain of the IP/MPLS backbone network as an agent of the CE router.
   Primary and backup tunnels terminated at the vNH are set up by the
   BGP/MPLS IP VPN based on IGP FRR. If the primary egress PE fails, the
   backup egress PEs can recognize the "shared" VPN route label and
   deliver the failure affected packets accordingly.

                                                                                  


The IETF Secretariat

v2.23.0 | Report a Bug | By Email