Re: [PWE3] Comment on <draft-ietf-pwe3-redundancy-bit-02.txt>

lizhong.jin@zte.com.cn Thu, 31 December 2009 08:55 UTC

Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCE463A6867 for <pwe3@core3.amsl.com>; Thu, 31 Dec 2009 00:55:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.238
X-Spam-Level:
X-Spam-Status: No, score=-99.238 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 RO3b+pTDuEOH for <pwe3@core3.amsl.com>; Thu, 31 Dec 2009 00:55:45 -0800 (PST)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 22EC23A67DD for <pwe3@ietf.org>; Thu, 31 Dec 2009 00:55:44 -0800 (PST)
Received: from [10.30.17.99] by mx6.zte.com.cn with surfront esmtp id 91101397396305; Thu, 31 Dec 2009 16:30:54 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.15] with StormMail ESMTP id 78921.2047936101; Thu, 31 Dec 2009 16:55:17 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id nBV8t4RW064065; Thu, 31 Dec 2009 16:55:04 +0800 (CST) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <mailman.11.1262203202.12493.pwe3@ietf.org>
To: Mustapha.Aissaoui@alcatel-lucent.com, veer.gorla@ericsson.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFCDF7D741.120570CE-ON4825769D.002FDBD6-4825769D.0030F677@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Thu, 31 Dec 2009 16:54:47 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2009-12-31 16:54:53, Serialize complete at 2009-12-31 16:54:53
Content-Type: multipart/alternative; boundary="=_alternative 0030F6754825769D_="
X-MAIL: mse2.zte.com.cn nBV8t4RW064065
Cc: pwe3@ietf.org
Subject: Re: [PWE3] Comment on <draft-ietf-pwe3-redundancy-bit-02.txt>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Dec 2009 08:55:47 -0000

Hi Mustapha:
For the second case, it is suitable to use "MUST" to describe "forward the 
MAC flush message to have the nodes in the VPLS mesh clear all FIB entries 
except those they learn from this node."
I think it should use "may". The alternative method is to use the 
mechanism described in <draft-ietf-l2vpn-vpls-ldp-mac-opt-00>, instead of 
clearing all FIB entries except those learned from the PW associated with 
this signaling session over which MAC flush message is received.

Best Regards
Lizhong Jin 


----------------------------------------------------------------------

Message: 1
Date: Tue, 29 Dec 2009 21:19:34 -0600
From: "AISSAOUI Mustapha" <Mustapha.Aissaoui@alcatel-lucent.com>
Subject: Re: [PWE3] Comment on <
                 draft-ietf-pwe3-redundancy-bit-02.txt>
To: "Veer Gorla" <veer.gorla@ericsson.com>, <pwe3@ietf.org>
Message-ID:
 <4A5028372622294A99B8FFF6BD06EB7B06141412@USDALSMBS03.ad3.ad.alcatel.com>
 
Content-Type: text/plain; charset="us-ascii"

Hi Veer,
sorry for the late reply.
 
Both behaviours are actually possible. 
 
The case described in the draft is when the PE-rs nodes are configured
to not forward the MAC flush message received from the MTU node over the
newly active PW. In this case, it is up to the PE-rs node which had its
PW transition to Standby state to generate a MAC flush to have the nodes
in the VPLS mesh clear FIB entries they learned from this node.
 
The case you describe is when the PE-rs nodes are configured to forward
the MAC flush message received from the MTU node over the newly active
PW. In this case, the PE-rs node which had its PW transition to Active
state must forward the MAC flush message to have the nodes in the VPLS
mesh clear all FIB entries except those they learn from this node.

Let me know if you agree with this and I will add this in the next
revision of the draft.
 
Regards,
Mustapha.

________________________________

                 From: pwe3-bounces@ietf.org 
[mailto:pwe3-bounces@ietf.org] On
Behalf Of Veer Gorla
                 Sent: Wednesday, December 09, 2009 5:54 PM
                 To: pwe3@ietf.org
                 Subject: [PWE3] Comment on <
draft-ietf-pwe3-redundancy-bit-02.txt>
 
 
 
                 Hi,
                 The draft says
                 Sec  4.1 & 4.2 . Standby State... 
                 "If the PW is a spoke in H-VPLS, any MAC addresses 
learned via
the PW should be flushed when it transitions to Standby state. "
 
                 This statement seems like implying that   MAC flush must 
be sent
into the mesh by PE-rs node ( optionally)  inaddition to MTU-s node
based on configuration. 
                 I think  it is better for MAC flush to be triggered by 
newly
active PE-rs node when it is transition to Active State. This could
cover the case when the old-active
                 node goes down and it is unable to send out the flush.
 
 
                 Regards
                 Veer
 


--------------------------------------------------------
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.