IETF Logo Mail Archive

Re: [PWE3] Some comments on draft-jc-pwe3-mpls-tp-static-checking-00

Lizhong Jin<lizhong.jin@zte.com.cn> Wed, 28 March 2012 20:26 UTC

Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9850F21E80A3 for <pwe3@ietfa.amsl.com>; Wed, 28 Mar 2012 13:26:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.599
X-Spam-Level:
X-Spam-Status: No, score=-100.599 tagged_above=-999 required=5 tests=[AWL=-0.514, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
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 uH9EoEJvJBci for <pwe3@ietfa.amsl.com>; Wed, 28 Mar 2012 13:26:13 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id A9D9321E8019 for <pwe3@ietf.org>; Wed, 28 Mar 2012 13:26:12 -0700 (PDT)
Received: from [192.168.164.15] by mx5.zte.com.cn with surfront esmtp id 286201397396305; Thu, 29 Mar 2012 03:50:49 +0800 (CST)
Received: from [10.30.3.21] by [192.168.164.15] with StormMail ESMTP id 70127.1789518762; Thu, 29 Mar 2012 04:11:22 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id q2SKQ4mC032992; Thu, 29 Mar 2012 04:26:04 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <4090125F3B48764B84FB3439456F00E90F9904B4@BL2PRD0510MB363.namprd05.prod.outlook.com>
To: Kingston Selvaraj <KingstonS@ipinfusion.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF9BFF4E92.72FE3FF9-ONC12579CF.006EBA75-C12579CF.00703C5C@zte.com.cn>
From: Lizhong Jin <lizhong.jin@zte.com.cn>
Date: Wed, 28 Mar 2012 21:25:47 +0100
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-03-29 04:26:04, Serialize complete at 2012-03-29 04:26:04
Content-Type: multipart/alternative; boundary="=_alternative 00703C5CC12579CF_="
X-MAIL: mse02.zte.com.cn q2SKQ4mC032992
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] Some comments on draft-jc-pwe3-mpls-tp-static-checking-00
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 28 Mar 2012 20:26:13 -0000

Hi Kingston,
Thank you for the comments, see inline below.

Regards
Lizhong
 

Kingston Selvaraj <KingstonS@ipinfusion.com> wrote 2012/03/28 19:13:03:

> Hi Authors,
> 
> Couple of comments and questions regarding this draft.
> 
> 1.       This draft doesn’t cover the operational details of 
multi-segment PW.
[Lizhong] yes, MS-PW should be included, and will update in next version.

> 
> 2.       Draft says that, PE will start transmitting the GAP message
> immediately after PW configuration and PSN tunnel is UP. 
> Let us consider a scenario where in PW is configured in PE1  (of 
> course the PSN tunnel is UP) and  not configured in other side of PE 
(PE2). 
> What will happen in this scenario?. Will the GAP message will be 
> transmitted only thrice and will be stopped by PE1?
> Or will it always be re-transmitted by PE1? 
[Lizhong] in that case, PE1 will continue sending GAP message, until PE2 
is also configured. After PE1/PE2 getting both local and remote 
information, and finished checking, then it will send suppress message to 
stop the message procedure. Will rephrase the draft to make this more 
clear.

> 
> Regards,
> S. Kingston Smiler.

v2.27.8 | Report a Bug | By Email | System Status