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

Huub van Helvoort <hhelvoort@chello.nl> Thu, 01 July 2010 08:00 UTC

Return-Path: <hhelvoort@chello.nl>
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 454A33A67C3; Thu, 1 Jul 2010 01:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.082
X-Spam-Level:
X-Spam-Status: No, score=-1.082 tagged_above=-999 required=5 tests=[AWL=-0.933, BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45]
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 WAi0IgarVvMl; Thu, 1 Jul 2010 01:00:16 -0700 (PDT)
Received: from fep19.mx.upcmail.net (fep19.mx.upcmail.net [62.179.121.39]) by core3.amsl.com (Postfix) with ESMTP id 3F9C03A679F; Thu, 1 Jul 2010 01:00:15 -0700 (PDT)
Received: from edge02.upcmail.net ([192.168.13.237]) by viefep19-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100701080025.JCSY17503.viefep19-int.chello.at@edge02.upcmail.net>; Thu, 1 Jul 2010 10:00:25 +0200
Received: from McAsterix.local ([77.250.51.60]) by edge02.upcmail.net with edge id cY0Q1e00f1Hw6VZ02Y0RVT; Thu, 01 Jul 2010 10:00:25 +0200
X-SourceIP: 77.250.51.60
Message-ID: <4C2C4620.7060108@chello.nl>
Date: Thu, 01 Jul 2010 09:39:12 +0200
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: Luca Martini <lmartini@cisco.com>
References: <474656.11843.qm@web15604.mail.cnb.yahoo.com> <FF8F3C1FD6EDF74CB6DD38B90FDEBADB061722C7@CNSHGSMBS01.ad4.ad.alcatel.com> <AANLkTikY-AXFJtxBPEf30i3xrqd93La7VGRXPEUe93wj@mail.gmail.com> <4C2C0A08.4060904@cisco.com>
In-Reply-To: <4C2C0A08.4060904@cisco.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
X-Cloudmark-Analysis: v=1.1 cv=K3uBg944YaUT+Qsu6bWO0a0V3uPy4DQNslbdoMCD4tw= c=1 sm=0 a=t6_7XfzNdKwA:10 a=GQCbJdZ--msA:10 a=_l4uJm6h9gAA:10 a=Ptvsf80qAAAA:8 a=48vgC7mUAAAA:8 a=R5C9hjxsAAAA:8 a=OLZQc8AWAAAA:8 a=LCB-FYsazXqLKMzxKC4A:9 a=gKa_8AWQzo_bpHwc83AA:7 a=8WyxezcRt_3q1kEVo-6gUTkNKaAA:4 a=mFyHDrcPJccA:10 a=lZB815dzVvQA:10 a=hFj-Mf0cM8IA:10 a=ZZIWsLRtCrFYY3Wx:21 a=F_QnSSwYj2sPp45B:21 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: pwe3@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
Reply-To: hhelvoort@chello.nl
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 08:00:22 -0000

Ciao Luca,

You wrote:

> I have to disagree that there was any consensus about this issue.
> If anything , there was consensus that there is no written statement 
> that we must to use the CW in MPLS-TP.

I agree with this.

> At the end we needed more input from service providers that have 
> deployed PWs. The point is not whether there is hardware support for the 
> CW, but whether we even want to use it in many cases where it adds 
> absolutely no value. For example ATM PWs in cell mode , where it add 
> almost 10% overhead with no benefit. Another case where the CW is not 
> useful is the ethernet PW without network link load balancing, where we 
> add 4 bytes to every packet just to occasionally send a status , or OAM 
> message.
> 
> I would like to propose update the rfc5586 to allow the use of the GAL 
> in PWs without the CW.

I  support this

> This makes the use of the GAL very symmetric among PWs and MPLS-TP LSPs. 
> This makes it easy to process by hardware based implementations.

I agree, consistency is very important, it causes less mistakes
in maintaining a network., and also for implementations (HW and SW).

Best regards, Huub.


> Andrew G. Malis wrote:
>> 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

-- 
================================================================
                  http://www.van-helvoort.eu/
================================================================
Always remember that you are unique...just like everyone else...