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

Vishwas Manral <vishwas.ietf@gmail.com> Fri, 02 July 2010 17:31 UTC

Return-Path: <vishwas.ietf@gmail.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 CFC4C28C140; Fri, 2 Jul 2010 10:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.195
X-Spam-Level:
X-Spam-Status: No, score=0.195 tagged_above=-999 required=5 tests=[AWL=-2.051, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_GB2312=1.345]
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 hNQDuwsPdLH7; Fri, 2 Jul 2010 10:31:46 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 53EEB3A6971; Fri, 2 Jul 2010 10:31:00 -0700 (PDT)
Received: by gxk28 with SMTP id 28so678098gxk.31 for <multiple recipients>; Fri, 02 Jul 2010 10:31:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tZ/xh4734lu7MByjhKrkJGu8zn/X1NBC61DXZJD6pvg=; b=rjveMr6VAO1iZVorKyaDqFnRJOWbR8xkOb4mvnaN1GgR7mD92Uxma4HDKTgB1Rf5Kz aK+VR18VoPErSMFGNXqBUsZaCpKb1+IWgKv4nGS21BmRDWdRT/OyVhot7aFSht3S8193 KGoRLGstzqLFLvNSxDHMOyLFPEXImb4VPza/M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ib/vEBh17HPIsYev00etoPHQI/CoxRupw0foYlXFRfjZuFe25xIm87Vu6vIInGCbza 6C1QH6/E6W4Abb5HzPaGP9CExWQcGx0FtopQOWD+X9gh+NVp+OSEnleupnuYFfcZkMei iPySidV0Dw1JhnCy9qBWRiqceKs84ViqzIkPo=
MIME-Version: 1.0
Received: by 10.90.117.19 with SMTP id p19mr1644508agc.16.1278091864187; Fri, 02 Jul 2010 10:31:04 -0700 (PDT)
Received: by 10.150.190.13 with HTTP; Fri, 2 Jul 2010 10:31:04 -0700 (PDT)
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D37F026BC2@ILPTMAIL02.ecitele.com>
References: <1277970374.4c2c47c60602a@gold.itu.ch> <BEB0533F63304E15B8258B4064955590@cnc.intra> <2C2F1EBA8050E74EA81502D5740B4BD6940E809392@SJEXCHCCR02.corp.ad.broadcom.com> <A3C5DF08D38B6049839A6F553B331C76D37F026BC2@ILPTMAIL02.ecitele.com>
Date: Fri, 2 Jul 2010 10:31:04 -0700
Message-ID: <AANLkTikuU4HdjCU347zyI_7_TkTAA30PCid3JwGAEVc-@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "amalis@gmail.com" <amalis@gmail.com>, wanggq <wanggq@dimpt.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "lihan@chinamobile.com" <lihan@chinamobile.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls-tp] =?gb2312?b?W1BXRTNdICC08Li0OiBQcm9wb3NhbCBvZiB1c2luZyBH?= =?gb2312?b?QUwgZm9yIFBX?=
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:31:53 -0000

Hi Sasha,

You are right.

Have a look at the draft for LSP ping over a segment of a MS-PW
http://tools.ietf.org/html/draft-boutros-mpls-lsp-ping-ttl-tlv-01

Thanks,
Vishwas

On Fri, Jul 2, 2010 at 10:21 AM, Alexander Vainshtein
<Alexander.Vainshtein@ecitele.com> wrote:
> Hi all,
> It seems that VCCV Type 2 or Type 3 are the only ways for running OAM on a
> segment of a MS-PW.
> Do I miss something here?
>
> My 2c,
>      Sasha
>
> ________________________________
> From: mpls-tp-bounces@ietf.org [mpls-tp-bounces@ietf.org] On Behalf Of
> Shahram Davari [davari@broadcom.com]
> Sent: Friday, July 02, 2010 8:13 PM
> To: Pei Zhang(联通集团技术部); ruiquan.jing@ties.itu.int; hejia@huawei.com;
> amalis@gmail.com
> Cc: lihan@chinamobile.com; pwe3@ietf.org; wanggq; mpls-tp@ietf.org
> Subject: Re: [mpls-tp] 答复: [PWE3] Proposal of using GAL for PW
>
> 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
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>