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

"HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn> Tue, 06 July 2010 08:01 UTC

Return-Path: <Feng.f.Huang@alcatel-sbell.com.cn>
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 6A6E93A68CF; Tue, 6 Jul 2010 01:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.736
X-Spam-Level:
X-Spam-Status: No, score=0.736 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, 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 jQSnP+momt9r; Tue, 6 Jul 2010 01:01:13 -0700 (PDT)
Received: from cnshjsmin03.alcatel-sbell.com.cn (cnshjsmin03.alcatel-sbell.com.cn [211.144.215.47]) by core3.amsl.com (Postfix) with ESMTP id 655DB3A68E8; Tue, 6 Jul 2010 01:01:12 -0700 (PDT)
X-AuditID: ac189297-b7b7eae000007cbb-84-4c32e232c820
Received: from cnshgsbhs02.ad4.ad.alcatel.com ( [172.24.146.147]) by cnshjsmin03.alcatel-sbell.com.cn (Symantec Brightmail Gateway) with SMTP id 9B.09.31931.232E23C4; Tue, 6 Jul 2010 15:58:42 +0800 (HKT)
Received: from CNSHGSMBS01.ad4.ad.alcatel.com ([172.24.146.171]) by cnshgsbhs02.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 6 Jul 2010 16:01:11 +0800
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB1CE1.659F4FB6"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 6 Jul 2010 16:01:10 +0800
Message-ID: <FF8F3C1FD6EDF74CB6DD38B90FDEBADB061D2ABB@CNSHGSMBS01.ad4.ad.alcatel.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76D37F569BB4@ILPTMAIL02.ecitele.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PWE3] [mpls-tp] Proposal of using GAL for PW
Thread-Index: AcsZyGN0IxBPyQW3RsiJBXvOYSLH1gCUsC9QAABmbbAAASc48AAHTcHgACiXOmA=
References: <2C2F1EBA8050E74EA81502D5740B4BD6940E809263@SJEXCHCCR02.corp.ad.broadcom.com><C8529DB4.4489A%giles.heron@gmail.com><2C2F1EBA8050E74EA81502D5740B4BD6940E80926C@SJEXCHCCR02.corp.ad.broadcom.com><4C2DB03F.7000709@cisco.com><15740615FC9674499FBCE797B011623F0B730021@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com><A3C5DF08D38B6049839A6F553B331C76D37F569A3D@ILPTMAIL02.ecitele.com><15740615FC9674499FBCE797B011623F0B730196@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <A3C5DF08D38B6049839A6F553B331C76D37F569BB4@ILPTMAIL02.ecitele.com>
From: "HUANG Feng F" <Feng.f.Huang@alcatel-sbell.com.cn>
To: "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>, "BUSI ITALO" <Italo.Busi@alcatel-lucent.com>
X-OriginalArrivalTime: 06 Jul 2010 08:01:11.0384 (UTC) FILETIME=[65F31580:01CB1CE1]
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: lihan@chinamobile.com, mpls-tp@ietf.org, pwe3@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: Tue, 06 Jul 2010 08:01:14 -0000

Dear Sasha,
   In MPLS-TP transport network environment, because it is strict connected oriented, ECMP is not supported.
B.R.
Feng
 


________________________________

From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Alexander Vainshtein
Sent: 2010年7月5日 20:42
To: BUSI ITALO
Cc: lihan@chinamobile.com; stbryant@cisco.com; pwe3@ietf.org; mpls-tp@ietf.org
Subject: Re: [PWE3] [mpls-tp] Proposal of using GAL for PW



Italo,

Lots of thanks for a prompt response. However, IMHO it is not correct.

 

E.g., BFD for MPLS LSP (as defined RFC 5884) and BFD in VCCV (as defined in RFC 5885) will provide correct connectivity failure indications regardless of ECMP based on MPLS stack hashing because the same label stack will be used by user traffic and OAM packets. 

 

Do you think I’ve missed something?

 

Regards,

     Sasha

 

From: BUSI, ITALO (ITALO) [mailto:italo.busi@alcatel-lucent.com] 
Sent: Monday, July 05, 2010 3:29 PM
To: Alexander Vainshtein; stbryant@cisco.com; Shahram Davari
Cc: lihan@chinamobile.com; pwe3@ietf.org; mpls-tp@ietf.org
Subject: RE: [PWE3] [mpls-tp] Proposal of using GAL for PW

 

Sasha,

 

what you say is correct but it is applicable to any environment where you use OAM together with ECMP. I do not see anything specific with GAL and PW.

 

Italo

	 

	
________________________________


	From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com] 
	Sent: lunedì 5 luglio 2010 10.39
	To: BUSI, ITALO (ITALO); stbryant@cisco.com; Shahram Davari
	Cc: lihan@chinamobile.com; pwe3@ietf.org; mpls-tp@ietf.org
	Subject: RE: [PWE3] [mpls-tp] Proposal of using GAL for PW

	Hi all,

	IMHO and FWIW, while RFC 5586  (5886 looks like a typo to me) does not place any restrictions on using GAL in non-TP environments, its usefulness in these environments (where various forms of multipath, including usage of entropy labels,  cannot be precluded) for OAM purposes is somewhat problematic: 

	Adding GAL to the label stack changes this for the multipath mechanisms based on stack hashing, and fate-sharing of OAM and user traffic packets is not guaranteed any more.

	 

	My 2c,

	     Sasha

	 

	From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of BUSI, ITALO (ITALO)
	Sent: Monday, July 05, 2010 11:17 AM
	To: stbryant@cisco.com; Shahram Davari
	Cc: lihan@chinamobile.com; pwe3@ietf.org; mpls-tp@ietf.org
	Subject: Re: [PWE3] [mpls-tp] Proposal of using GAL for PW

	 

	I agree with Stewart.

	 

	The GAL MUST be at the BoS in MPLS-TP where ECMP is not applicable and entroy labels MUST NOT be used.

	 

	In other MPLS environments (e.g., where entropy labels are used), RFC 5886 does not place any restriction on the position of the GAL within the label stack.

	 

	Italo

		 

________________________________

		From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Stewart Bryant
		Sent: venerdì 2 luglio 2010 11.24
		To: Shahram Davari
		Cc: Andy Malis; mpls-tp@ietf.org; lihan@chinamobile.com; pwe3@ietf.org; HUANG, Feng F (Feng)
		Subject: Re: [mpls-tp] [PWE3] Proposal of using GAL for PW

		On 01/07/2010 19:35, Shahram Davari wrote: 

		!mmm so if one used entropy then they can’t have OAM?

		-SD

		
		Not so. The GAL goes above the entropy label (S=0), so gets parsed first. This works for both PHP and not PHP, and both LSP and PW.
		
		- Stewart