Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert

liu.guoman@zte.com.cn Thu, 05 August 2010 02:29 UTC

Return-Path: <liu.guoman@zte.com.cn>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD0713A6989 for <mpls@core3.amsl.com>; Wed, 4 Aug 2010 19:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.844
X-Spam-Level:
X-Spam-Status: No, score=-96.844 tagged_above=-999 required=5 tests=[AWL=0.791, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qj6uXpu53SsZ for <mpls@core3.amsl.com>; Wed, 4 Aug 2010 19:29:08 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 8CC5C3A68CE for <mpls@ietf.org>; Wed, 4 Aug 2010 19:29:07 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 3510806486374; Thu, 5 Aug 2010 10:28:48 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.16] with StormMail ESMTP id 14146.2396285197; Thu, 5 Aug 2010 10:20:52 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o752TJYg092820; Thu, 5 Aug 2010 10:29:22 +0800 (CST) (envelope-from liu.guoman@zte.com.cn)
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51AE694DCF@EUSAACMS0703.eamcs.ericsson.se>
To: Autumn Liu <autumn.liu@ericsson.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF2A70FA6A.814FDA95-ON48257776.000CD2DB-48257776.000DD6FC@zte.com.cn>
From: liu.guoman@zte.com.cn
Date: Thu, 05 Aug 2010 10:29:09 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-08-05 10:29:17, Serialize complete at 2010-08-05 10:29:17
Content-Type: multipart/alternative; boundary="=_alternative 000DD6FC48257776_="
X-MAIL: mse2.zte.com.cn o752TJYg092820
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Aug 2010 02:29:10 -0000

hi Autumn,
BTW, Is the PRO information exchanged by control signaling?
if so, this protection solution must not be independent of 
control plane. whether it can violate RFC5464 23.B:
 taking recovery actions independent of the control or
 management plane used to configure the MPLS-TP layer network?

Regards
liu







Autumn Liu <autumn.liu@ericsson.com> 
发件人:  mpls-bounces@ietf.org
2010-08-05 10:09

收件人
"liu.guoman@zte.com.cn" <liu.guoman@zte.com.cn>
抄送
"mpls@ietf.org" <mpls@ietf.org>
主题
Re: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, 
draft-kini-mpls-fast-lsp-alert






Hi Liu,
 
The RRO information is exchanged before the failure, and it is per LSP 
along with each refresh message.
P2MP LSP protection is interesting topic and we can discuss further.
 
Regards,
Autumn
 

From: liu.guoman@zte.com.cn [mailto:liu.guoman@zte.com.cn] 
Sent: Tuesday, August 03, 2010 8:39 PM
To: Autumn Liu
Cc: mpls@ietf.org; mpls-bounces@ietf.org; Sriganesh Kini
Subject: RE: [mpls] Updated drafts - 
draft-kini-mpls-ring-frr-facility-backup, draft-kini-mpls-fast-lsp-alert


Autumn 
thank you for explaining. according to my understanding, when one link 
have failure, PLR node will append to the PRO of per LSP which have been 
affected by the failure in the 
BFD Session of backup tunnel, so that PLR-u will know which LSP need to 
switch its own e-backup tunnel? if so , as PLR may be MIP of some LSP , 
how do it know PRO of per LSP? 
can you need to query the PRO of per LSP by control plane? 
in addtion, for P2MP , when U-PLR received alert message from PLR , U-PLR 
should make service packet bridge both primary LSP and e-backup tunnel at 
the same time. it is very rapid and 
valid solution. do you think so? 
if you can be interested in the p2mp protection solution, we may disscuss 
it in detail in the following time. 

best regards 
liu






Autumn Liu <autumn.liu@ericsson.com> 
2010-08-04 10:35 


收件人
"liu.guoman@zte.com.cn" <liu.guoman@zte.com.cn>, Sriganesh Kini 
<sriganesh.kini@ericsson.com> 
抄送
"mpls@ietf.org" <mpls@ietf.org>, "mpls-bounces@ietf.org" 
<mpls-bounces@ietf.org> 
主题
RE: [mpls] Updated drafts - draft-kini-mpls-ring-frr-facility-backup, 
draft-kini-mpls-fast-lsp-alert








Liu, 
  
The proposed RRO subject tells u-PLR of primary LSP which backup is 
protecting it. When the alert message is received on that backup, the 
u-PLR finds out the primary LSP (protected by the backup) to switch the 
traffic onto the e-backup. 
  
Hope this gives you the clear answer to your question. 
  
Autumn 
 
 

 _______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls




--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.