Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt ( comment )

lizhong.jin@zte.com.cn Thu, 17 March 2011 15:22 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 8BC3C3A6954 for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 08:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.962
X-Spam-Level:
X-Spam-Status: No, score=-100.962 tagged_above=-999 required=5 tests=[AWL=-0.877, 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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxlf0SA6xxco for <pwe3@core3.amsl.com>; Thu, 17 Mar 2011 08:22:53 -0700 (PDT)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 785BC3A6920 for <pwe3@ietf.org>; Thu, 17 Mar 2011 08:22:51 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 50831397396305; Thu, 17 Mar 2011 23:23:30 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.15] with StormMail ESMTP id 84746.8276511994; Thu, 17 Mar 2011 23:24:15 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id p2HFO8So094616; Thu, 17 Mar 2011 23:24:08 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <C9A769B4.185D0%andrew.g.malis@one.verizon.com>
To: "Malis, Andrew G. (Andy)" <andrew.g.malis@verizon.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF180D60E5.9BB7A5F8-ON48257856.00547ABE-48257856.00549BDD@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Thu, 17 Mar 2011 23:23:54 +0800
X-MIMETrack: S/MIME Sign by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-17 23:24:10, Serialize by Notes Client on JinLiZhong127666/user/zte_ltd(Release 6.5.6|March 06, 2007) at 2011-03-17 23:24:10, Serialize complete at 2011-03-17 23:24:10, S/MIME Sign failed at 2011-03-17 23:24:10: The cryptographic key was not found, Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-03-17 23:24:12, Serialize complete at 2011-03-17 23:24:12
Content-Type: multipart/alternative; boundary="=_alternative 00549BDA48257856_="
X-MAIL: mse02.zte.com.cn p2HFO8So094616
Cc: Loa Andersson <loa.andersson@ericsson.com>, "lmartini@cisco.com" <lmartini@cisco.com>, "pwe3@ietf.org" <pwe3@ietf.org>, George Swallow <swallow@cisco.com>, Ross Callon <rcallon@juniper.net>, "Malis, Andrew G. (Andy)" <andrew.g.malis@verizon.com>
Subject: Re: [PWE3] WG Poll on draft-jin-pwe3-cbit-negotiation-03.txt ( comment )
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, 17 Mar 2011 15:22:54 -0000

Andy,
Thanks for the suggestion, and will do the presentation at MPLS.

Lizhong
 

"Malis, Andrew G. (Andy)" <andrew.g.malis@verizon.com> wrote on 2011-03-17 
19:33:08:

> Lizhong,
> 
> Thanks. Since this affects LDP, you should ask for time on the MPLS 
> WG’s agenda to present it there in addition to presenting it in PWE3.
> 
> Cheers,
> Andy
> 
> On 3/16/11 23:07 , "lizhong.jin@zte.com.cn" <lizhong.jin@zte.com.cn> 
wrote:

> 
> Hi Andy, 
> Thank you very much. We have uploaded the 04 version. Please get it 
> from the following link: 
> http://tools.ietf.org/html/draft-jin-pwe3-cbit-negotiation-04.txt 
> 
> Regards 
> Lizhong 
> 
> 
> amalis@gmail.com wrote on 2011-03-07 23:52:22:
> 
> > Lizhong,
> > 
> > There's been a lot of support for WG adoption of this draft. Please
> > update the draft to -04 to reflect the discussion on the list (before
> > the window closes in a week) and we'll announce the adoption in
> > Prague, followed by having you issue the WG version of the draft.
> > 
> > Thanks,
> > Andy
> > 
> > On Thu, Mar 3, 2011 at 10:41 AM,  <lizhong.jin@zte.com.cn> wrote:
> > >
> > > Luca,
> > > After discussing with the authors, we decide to add the wait for 
label
> > > release before sending label request, this wouldn't harm and bring 
some
> > > secure.
> > >
> > > Then are you OK with the following text?
> > >
> > > When Local PE changes its control word from NOT PREFERRED to 
PREFERRED and
> > > only if it already received the remote label mapping message with 
C-bit=0,
> > > additional procedure will be added as follow:
> > > -i Local PE MUST send a label withdraw message to remote PE if it 
has
> > > previously sent a label mapping, and wait until receiving a label 
release
> > > from the remote PE.
> > > -ii Local PE MUST send a label request message to remote PE, andwait 
until
> > > receiving a label mapping message containing the remote PE 
configured
> > > control word setting.
> > > -iii After receiving remote PE label mapping with control word 
setting,
> > > Local PE MUST follow procedures defined in [RFC4447] section 6 
> when sending
> > > it's label mapping message.
> > >
> > > Correspondingly, the modified procedure of PE in figure 1 will be as
> > > follows:
> > >
> > > 1. PE2 changes locally configured control word to PREFERRED.
> > > 2. PE2 will then send label withdraw message to PE1.
> > > 3. PE1 MUST send label release in reply to label withdraw 
> message from PE2.
> > > 4. Upon receipt of Label release message from PE1, PE2 MUST send 
label
> > > request messages to PE1 although it already received the label 
> mapping with
> > > C-bit=0.
> > > 5. PE1 MUST send label mapping message with C-bit=1 again to 
PE2(Note: PE1
> > > MUST send label mapping with locally configured CW parameter).
> > > 6. PE2 receives the label mapping from PE1 and updates the remote 
label
> > > binding information. PE2 MUST wait for PE1 label binding before 
> sending its
> > > label binding with C-bit set, only if it previously had a label 
> binding with
> > > C-bit = 0 from PE1.
> > > 7. PE2 will send label mapping to PE1 with C-bit=1.
> > >
> > > It is to be noted that the above assume that PE1 is configured to 
support
> > > CW, however in step 5 if PE1 doesn't support CW, PE1 would send the 
label
> > > mapping message with C-bit =0, this would result in PE2 in step 
> 7 sending a
> > > label mapping with C-bit=0 as per [RFC4447] CW negotiation 
procedure.
> > >
> > > Thanks
> > > Lizhong
> > >
> > >
> > > ------------send by Luca 
> Martini-------------------------------------------
> > > Matthew & Andy,
> > >
> > >
> > > Although I support clarifying this procedure , I believe this 
document
> > > needs some work.
> > > In section 3 for example :
> > >
> > >    When Local PE changes its control word from NOT PREFERRED to
> > >    PREFERRED and only if it already received the remote label 
mapping
> > >    message with C-bit=0, additional procedure will be added as 
follow:
> > >
> > >          -i. Local PE sends label withdraw message to the remote if 
it
> > >              already sends label mapping message, for it has changed 
its
> > >              control word parameter.
> > >
> > >         -ii. Local PE MUST send a label request messages to peer PE 
to
> > >              get peer's configured control word parameter before 
sending
> > >              new label mapping message to peer PE.
> > >
> > >        -iii. After receiving the new label mapping message from peer 
PE
> > >              and updating the remote label binding information, the
> > >              Local PE should send label mapping to peer PE according 
to
> > >              procedures defined in [RFC4447].
> > >
> > > What does the item i) mean ? the English is not clear.
> > > Why does the PE have to do ii) ?
> > >
> > > All we really need is a statement on how the c-bit negotiation state
> > > machine can be reset if one end has changed "his mind" .
> > >
> > > Can we fix this document before  issuing the -00 WG draft version ?
> > >
> > > Thanks.
> > > Luca
> > >
> 


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