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

Jia HE <hejia@huawei.com> Thu, 01 July 2010 05:30 UTC

Return-Path: <hejia@huawei.com>
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 CFD143A6812; Wed, 30 Jun 2010 22:30:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.708
X-Spam-Level: ***
X-Spam-Status: No, score=3.708 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1]
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 MuHMynwvGvB3; Wed, 30 Jun 2010 22:30:43 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 74A743A67A7; Wed, 30 Jun 2010 22:30:42 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4V007025Z7BX@szxga03-in.huawei.com>; Thu, 01 Jul 2010 13:30:43 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4V00HHD5Z7ZV@szxga03-in.huawei.com>; Thu, 01 Jul 2010 13:30:43 +0800 (CST)
Received: from h48726 ([10.70.77.157]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L4V00HZB5Z660@szxml04-in.huawei.com>; Thu, 01 Jul 2010 13:30:42 +0800 (CST)
Date: Thu, 01 Jul 2010 13:30:42 +0800
From: Jia HE <hejia@huawei.com>
To: "Andrew G. Malis" <amalis@gmail.com>
Message-id: <066b01cb18de$8c2ac290$9d4d460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: base64
X-Priority: 3
X-MSMail-priority: Normal
References: <474656.11843.qm@web15604.mail.cnb.yahoo.com> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB061722C7@CNSHGSMBS01.ad4.ad.alcatel.com> <AANLkTikY-AXFJtxBPEf30i3xrqd93La7VGRXPEUe93wj@mail.gmail.com>
Cc: lihan@chinamobile.com, pwe3@ietf.org, HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>, 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 05:30:54 -0000

Hi Andy,

The problem is there do exist applications of PW without CW in the network. By adding GAL for PW OAM it dosen't impact the services on the wire and will align the OAM process for both LSP and PW in MPLS-TP environment.

Since MPLS-TP covers both LSP and PW, it is better to consider them together for easy implementations.

 

B.R.
Jia


----- Original Message ----- 
From: "Andrew G. Malis" <amalis@gmail.com>
To: "HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn>cn>; "Larry" <larryli888@yahoo.com.cn>
Cc: <lihan@chinamobile.com>om>; <pwe3@ietf.org>rg>; <mpls-tp@ietf.org>
Sent: Thursday, July 01, 2010 12:27 AM
Subject: Re: [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
>> ********************************************************************
>>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>