[mpls] a question about draft-cheung-mpls-tp-mesh-protection-01
liu.guoman@zte.com.cn Fri, 30 July 2010 08:15 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 5723328C274; Fri, 30 Jul 2010 01:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.736
X-Spam-Level:
X-Spam-Status: No, score=-99.736 tagged_above=-999 required=5 tests=[AWL=2.102, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 ID2ciGbW-GNB; Fri, 30 Jul 2010 01:15:29 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 589FF28C275; Fri, 30 Jul 2010 01:15:28 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 205951570495873; Fri, 30 Jul 2010 16:13:30 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 79973.3500714166; Fri, 30 Jul 2010 16:14:58 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o6U7dNSr023884; Fri, 30 Jul 2010 16:06:56 +0800 (CST) (envelope-from liu.guoman@zte.com.cn)
To: ryoo@etri.re.kr, cts@etri.re.kr
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFE7007A09.78197DEB-ON48257770.0029A032-48257770.002CB81C@zte.com.cn>
From: liu.guoman@zte.com.cn
Date: Fri, 30 Jul 2010 16:06:30 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-30 16:06:44, Serialize complete at 2010-07-30 16:06:44
Content-Type: multipart/alternative; boundary="=_alternative 002CB81948257770_="
X-MAIL: mse2.zte.com.cn o6U7dNSr023884
Cc: mpls@ietf.org, mpls-tp@ietf.org
Subject: [mpls] a question about draft-cheung-mpls-tp-mesh-protection-01
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: Fri, 30 Jul 2010 08:15:36 -0000
hi, today I reviewed your this draft, I have a few questions for mesh protection 1 in section 3, In my mind, there is a sentence : In both cases, 1:1 or 1+1 protection may be used. if there use 1+1 protection for each working path. it is no necessary to apply mesh protection. beacause the bandwidth resource of protection is equal to the sum of bandwidth resource of all protected path. so I think 1+1 protection should not be used in the mesh protection. do you think so? 2 about the Shared node SEN will send the protection locking message requesting LoP to the end node of protected LSP. IMO, as SEN node is MIP of the protected LSP , it can't generate unsolicit OAM packet to send other node. so how to generate the protection locking message requesting LOP in the SEN node ? Maybe i miss something important? thank you best regards liu -------------------------------------------------------- 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.
- Re: [mpls] a question about draft-cheung-mpls-tp-… Ryoo, Jeong-dong
- [mpls] a question about draft-cheung-mpls-tp-mesh… liu.guoman
- Re: [mpls] a question about draft-cheung-mpls-tp-… Taesik Cheung
- Re: [mpls] a question about draft-cheung-mpls-tp-… liu.guoman
- Re: [mpls] a question about draft-cheung-mpls-tp-… liu.guoman
- Re: [mpls] a question about draft-cheung-mpls-tp-… Ryoo, Jeong-dong
- Re: [mpls] a question about draft-cheung-mpls-tp-… Ryoo, Jeong-dong
- Re: [mpls] a question about draft-cheung-mpls-tp-… Ryoo, Jeong-dong
- Re: [mpls] a question about draft-cheung-mpls-tp-… liu.guoman
- Re: [mpls] a question about draft-cheung-mpls-tp-… liu.guoman