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

Sam Aldrin <aldrin@cisco.com> Sun, 04 July 2010 20:03 UTC

Return-Path: <aldrin@cisco.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 3640E3A67F9; Sun, 4 Jul 2010 13:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.75
X-Spam-Level:
X-Spam-Status: No, score=-8.75 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, 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 3tH9Ct8A9Ry8; Sun, 4 Jul 2010 13:03:34 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id E65A03A6781; Sun, 4 Jul 2010 13:03:33 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmcFANOFMEyrR7Ht/2dsb2JhbACBQ4Fam3BccaIBiSiPbYJcB4FQcgSDeIRCiV8
X-IronPort-AV: E=Sophos; i="4.53,536,1272844800"; d="scan'208,217"; a="153689203"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 04 Jul 2010 20:03:33 +0000
Received: from sjc-aldrin-8712.cisco.com (sjc-aldrin-8712.cisco.com [10.19.202.51]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o64K3Wq7011825; Sun, 4 Jul 2010 20:03:32 GMT
Message-Id: <22F48781-A5E1-4DC7-86AC-DA71A5C3286E@cisco.com>
From: Sam Aldrin <aldrin@cisco.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D37F026BC4@ILPTMAIL02.ecitele.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-30--681097937
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sun, 4 Jul 2010 13:03:32 -0700
References: <1277970374.4c2c47c60602a@gold.itu.ch> <BEB0533F63304E15B8258B4064955590@cnc.intra>, <2C2F1EBA8050E74EA81502D5740B4BD6940E809392@SJEXCHCCR02.corp.ad.broadcom.com> <A3C5DF08D38B6049839A6F553B331C76D37F026BC2@ILPTMAIL02.ecitele.com>, <B6012989-FC7F-494A-8923-6A048FF8ED4A@cisco.com> <A3C5DF08D38B6049839A6F553B331C76D37F026BC3@ILPTMAIL02.ecitele.com>, <D3E79D6D-2759-40EA-A5D4-8F9AB2D8E44C@cisco.com> <A3C5DF08D38B6049839A6F553B331C76D37F026BC4@ILPTMAIL02.ecitele.com>
X-Mailer: Apple Mail (2.936)
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>, =?UTF-8?Q?Pei_Zhang=28=E8=81=94=E9=80=9A=E9=9B=86=E5=9B=A2?=
Subject: Re: [mpls-tp] =?utf-8?b?W1BXRTNdICDnrZTlpI06ICAgUHJvcG9zYWwgb2YgdXNp?= =?utf-8?q?ng_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: Sun, 04 Jul 2010 20:03:36 -0000

Hi Sasha,

Even if it is segment within MSPW, how can SPE advertise type2, due to  
the reason I mentioned earlier?

-sam
On Jul 3, 2010, at 9:20 PM, Alexander Vainshtein wrote:

> Sam,
> Lots of thanks for a prompt response and clarification.
>
> Please note, however, that I have been talking about segment OAM for  
> MS-PWs.
> Regards,
>      Sasha
>
> From: Sam Aldrin [aldrin@cisco.com]
> Sent: Sunday, July 04, 2010 2:17 AM
> To: Alexander Vainshtein
> Cc: Shahram Davari; Pei Zhang(联通集团技术部); ruiquan.jing@ties.itu.int; he 
> jia@huawei.com; amalis@gmail.com; lihan@chinamobile.com;  
> pwe3@ietf.org; wanggq; mpls-tp@ietf.org
> Subject: Re: [PWE3] [mpls-tp] 答复: Proposal of using GAL for PW
>
> Sasha,
>
> Due to the presence of RA label, the packet will be punted at the  
> adjacent SPE/TPE router, which is the end of the segment.
> If you have to ping or trace beyond one segment, i.e. in MSPW, how  
> does the packet get there with RA label in there?
> For that very reason, SPE's do not even advertise type 2 VCCV  
> capability.
>
> -sam
> On Jul 3, 2010, at 1:43 PM, Alexander Vainshtein wrote:
>
>> Sam,
>> Could you please elaborate?
>>
>> Regards,
>>      Sasha
>>
>> From: Sam Aldrin [aldrin@cisco.com]
>> Sent: Friday, July 02, 2010 8:46 PM
>> To: Alexander Vainshtein
>> Cc: Shahram Davari; Pei Zhang(联通集团技术部); ruiquan.jing@ties.itu.int; he 
>> jia@huawei.com; amalis@gmail.com; lihan@chinamobile.com; pwe3@ietf.org 
>> ; wanggq; mpls-tp@ietf.org
>> Subject: Re: [PWE3] [mpls-tp] 答复: Proposal of using GAL for PW
>>
>> In the case of MS-PW, I don't think you can use type2(RA).
>>
>> -sam
>> On Jul 2, 2010, at 10:21 AM, Alexander Vainshtein 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@ti 
>>> es.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
>>
>>
>
>