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

"Shahram Davari" <davari@broadcom.com> Fri, 02 July 2010 17:14 UTC

Return-Path: <davari@broadcom.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 9760528C11A; Fri, 2 Jul 2010 10:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.742
X-Spam-Level:
X-Spam-Status: No, score=-1.742 tagged_above=-999 required=5 tests=[AWL=0.404, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152]
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 X5rowQI5p4ks; Fri, 2 Jul 2010 10:13:59 -0700 (PDT)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by core3.amsl.com (Postfix) with ESMTP id 9E35828C117; Fri, 2 Jul 2010 10:13:59 -0700 (PDT)
Received: from [10.16.192.232] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Fri, 02 Jul 2010 10:14:01 -0700
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB02.corp.ad.broadcom.com ([10.16.192.232]) with mapi; Fri, 2 Jul 2010 10:14:01 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: =?utf-8?B?UGVpIFpoYW5nKOiBlOmAmumbhuWbouaKgOacr+mDqCk=?= <hq-zhangp@chinaunicom.cn>, "ruiquan.jing@ties.itu.int" <ruiquan.jing@ties.itu.int>, "hejia@huawei.com" <hejia@huawei.com>, "amalis@gmail.com" <amalis@gmail.com>
Date: Fri, 2 Jul 2010 10:13:58 -0700
Thread-Topic: =?utf-8?B?W21wbHMtdHBdIOetlOWkjTogIFtQV0UzXSBQcm9wb3NhbCBvZiB1c2luZyBH?= =?utf-8?B?QUwgZm9yIFBX?=
Thread-Index: AcsY8jy3E4ibl9LESky5Kv5d0XVs8wA0UU5gABGWheA=
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6940E809392@SJEXCHCCR02.corp.ad.broadcom.com>
References: <1277970374.4c2c47c60602a@gold.itu.ch> <BEB0533F63304E15B8258B4064955590@cnc.intra>
In-Reply-To: <BEB0533F63304E15B8258B4064955590@cnc.intra>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 6030C1D210017114269-01-01
Content-Type: multipart/alternative; boundary=_000_2C2F1EBA8050E74EA81502D5740B4BD6940E809392SJEXCHCCR02co_
Cc: "lihan@chinamobile.com" <lihan@chinamobile.com>, "pwe3@ietf.org" <pwe3@ietf.org>, wanggq <wanggq@dimpt.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] =?utf-8?b?562U5aSNOiAgW1BXRTNdIFByb3Bvc2FsIG9mIHVzaW5n?= =?utf-8?q?_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: Fri, 02 Jul 2010 17:14:02 -0000

Good. In that case you could use VCCV type 2 or 3.

Thx
SD

From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Pei Zhang(???????)
Sent: Friday, July 02, 2010 1:52 AM
To: ruiquan.jing@ties.itu.int; hejia@huawei.com; amalis@gmail.com
Cc: lihan@chinamobile.com; pwe3@ietf.org; wanggq; mpls-tp@ietf.org
Subject: [mpls-tp] 答复: [PWE3] Proposal of using GAL for PW


Hi,

The CW on many applications is also option in our network.

Thanks,
Pei

-----邮件原件-----
发件人: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] 代表 ruiquan.jing@ties.itu.int
发送时间: 2010年7月1日 15:46
收件人: hejia@huawei.com; amalis@gmail.com
抄送: lihan@chinamobile.com; pwe3@ietf.org; mpls-tp@ietf.org
主题: Re: [mpls-tp] [PWE3] Proposal of using GAL for PW


Hi all,

I agree with Jia and Luca. As CW is defined as OPTIONAL, there are many
applications of PW without CW in our network.
So I support the Proposal of using GAL for PW OAM.

Best regards

Ruiquan Jing

China¡¡Telecom  Beijing  Research¡¡Institute


> -----Original Message-----
> From: mpls-tp-bounces@ietf.org
> [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Jia HE
> Sent: Thursday, July 01, 2010 1:31 PM
> To: Andrew G. Malis
> Cc: lihan@chinamobile.com; pwe3@ietf.org; HUANG Feng F;
> mpls-tp@ietf.org
> Subject: Re: [mpls-tp] [PWE3] Proposal of using GAL for PW
>
> 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
> >
> _______________________________________________
> mpls-tp mailing list
> mpls-tp@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls-tp
>
_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp