Re: [mpls-tp] [PWE3] Proposal of using GAL for PW

liu.guoman@zte.com.cn Thu, 01 July 2010 02:57 UTC

Return-Path: <liu.guoman@zte.com.cn>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF3E53A67FE; Wed, 30 Jun 2010 19:57:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.035
X-Spam-Level:
X-Spam-Status: No, score=-96.035 tagged_above=-999 required=5 tests=[AWL=1.600, 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 saRA0xlOCrnz; Wed, 30 Jun 2010 19:57:22 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id D03793A67AC; Wed, 30 Jun 2010 19:57:21 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 383431105171106; Thu, 1 Jul 2010 10:57:00 +0800 (CST)
Received: from [10.30.3.19] by [192.168.168.15] with StormMail ESMTP id 2748.3041263509; Thu, 1 Jul 2010 10:57:27 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o612v6cT089422; Thu, 1 Jul 2010 10:57:06 +0800 (CST) (envelope-from liu.guoman@zte.com.cn)
In-Reply-To: <AANLkTimCytuac5xZJfY4KlkwZ_zdhHuj6yHXe8achA9J@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF2907B9E2.35C63D34-ON48257753.000F7299-48257753.00105626@zte.com.cn>
From: liu.guoman@zte.com.cn
Date: Thu, 1 Jul 2010 10:56:56 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-07-01 10:57:01, Serialize complete at 2010-07-01 10:57:01
Content-Type: multipart/alternative; boundary="=_alternative 0010562248257753_="
X-MAIL: mse2.zte.com.cn o612v6cT089422
Cc: mpls-tp-bounces@ietf.org, mpls-tp@ietf.org
Subject: Re: [mpls-tp] [PWE3] Proposal of using GAL for PW
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2010 02:57:24 -0000

I think CW should be an option as RFC4448,
don't change it because of other draft's contradiction.
it will affect to compabile with old equipments;

Best regards
liu







"Andrew G. Malis" <agmalis@gmail.com> 
发件人:  mpls-tp-bounces@ietf.org
2010-07-01 00:35

收件人
mpls-tp@ietf.org
抄送

主题
Re: [mpls-tp] [PWE3] Proposal of using GAL for PW






Larry and Feng,

This issue has previously been discussed at length by the working
group, both at the Anaheim meeting and by email, for example in emails
with the subject line "Possible Contradiction re use of GAL in
pwe3-static-pw-status". There was rough consensus that for MPLS-TP
applications and/or when PW OAM is desired, PW implementations are
mature enough (it has been 10 years now, after all) that the time has
come to require the implementation of the CW for all PWs, including
Ethernet.

Cheers,
Andy

On Wed, Jun 30, 2010 at 6:34 AM, HUANG Feng F
<Feng.f.Huang@alcatel-sbell.com.cn> wrote:
>
> it is reasonable to support GAL in MPLS-TP PW OAM, it is more generic, 
because CW is an option RFC4448 for Ethernet over MPLS.
>
> 4.6.  The Control Word
>
> xxxx
>
>
> The features that the control word provides may not be needed for a
>   given Ethernet PW.  For example, ECMP may not be present or active on
>   a given MPLS network, strict frame sequencing may not be required,
>   etc.  If this is the case, the control word provides little value and
>   is therefore optional.  Early Ethernet PW implementations have been
>   deployed that do not include a control word or the ability to process
>   one if present.  To aid in backwards compatibility, future
>   implementations MUST be able to send and receive frames without the
>   control word present.
> xxxx
>
>
>
> B.R.
> Feng Huang
>
>
> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of 
Larry
> Sent: 2010年6月30日 17:38
> To: mpls-tp@ietf.org; pwe3@ietf.org
> Cc: lihan@chinamobile.com
> Subject: [PWE3] Proposal of using GAL for PW
>
> Dear all:
>
>     In section 4.2 in RFC5586, it is defined that GAL MUST NOT be used 
with PWs in MPLS-TP. The PWE3 control word [RFC4385] MUST be present when 
the ACH is used to realize the associated control channel.
>     In real application, a lot of MPLS and MPLS-TP equipments do not 
support control word. It is proposed to use the GAL to identify associated 
control channel in PW layer.
>
> Best regards,
>
>                 Han Li
>
> ********************************************************************
> Han Li, Ph.D
> China Mobile Research Institute
> Unit 2, 28 Xuanwumenxi Ave, Xuanwu District, Beijing 100053, China
> Fax: +86 10 63601087
> MOBILE: 13501093385
> ********************************************************************
>
_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp




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