[mpls-tp] Problems with SPME as the path segment monitoring tool in MPLS-TP
Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Tue, 06 July 2010 16:40 UTC
Return-Path: <Alexander.Vainshtein@ecitele.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 1C8103A698C for <mpls-tp@core3.amsl.com>;
Tue, 6 Jul 2010 09:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.956
X-Spam-Level:
X-Spam-Status: No, score=-1.956 tagged_above=-999 required=5 tests=[AWL=0.642,
BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 aZ3Qsy-kwfap for
<mpls-tp@core3.amsl.com>; Tue, 6 Jul 2010 09:40:01 -0700 (PDT)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com
[147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id 59BCE3A6878 for
<mpls-tp@ietf.org>; Tue, 6 Jul 2010 09:40:00 -0700 (PDT)
X-AuditID: 93eaf2e7-b7c13ae0000042a1-50-4c335c612d9d
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by
ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id
7F.48.17057.16C533C4; Tue, 6 Jul 2010 19:40:01 +0300 (IDT)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by
ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi;
Tue, 6 Jul 2010 19:40:18 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "koike.yoshinori@lab.ntt.co.jp" <koike.yoshinori@lab.ntt.co.jp>
Date: Tue, 6 Jul 2010 19:39:58 +0300
Thread-Topic: Problems with SPME as the path segment monitoring tool in MPLS-TP
Thread-Index: AcsdKd8OQXHAW3xPQZq3MhQjlI+VXA==
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D37FD7344D@ILPTMAIL02.ecitele.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
boundary="_000_A3C5DF08D38B6049839A6F553B331C76D37FD7344DILPTMAIL02eci_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: [mpls-tp] Problems with SPME as the path segment monitoring tool in
MPLS-TP
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 16:40:05 -0000
Dear Mr. Koike, I've read your draft on path segment monitoring (http://www.ietf.org/id/draft-koike-mpls-tp-temporal-hitless-psm-00.txt) and I think that there is one more potentially fatal issue with the SPME mechanism if it is used for on-demand OAM. (My reading of the draft is that you see on-demand as the primary mode for path segment monitoring as it will be used to localize an observed fault.) To the best of my understanding, setting up a temporal SPME will result in the LSRs within the monitoring segment only looking at the added (stacked) labels and not on the labels of the original LSP. (Actually, the label immediately below the SPME one will have to be set to one expected on the tail end node of the segment for the original LSP). This means that problems stemming from incorrect (or unexpected) treatment of labels of the original LSP by the nodes within the monitored segment may disappear when you set up SPME. This includes HW problems during label look-up, mis-configuration etc. Of course, the inversion of this situation is also possible, .e.g., incorrect or unexpected treatment of SPME labels can result in false detection of a fault where none originally existed. Does this make sense to you? Do you think that I've missed something important? Regards, Sasha
- [mpls-tp] Problems with SPME as the path segment … Alexander Vainshtein
- Re: [mpls-tp] Problems with SPME as the path segm… Yoshinori KOIKE
- Re: [mpls-tp] Problems with SPME as the path segm… Alexander Vainshtein
- Re: [mpls-tp] Problems with SPME as the path segm… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Problems with SPME as the path segm… Huub van Helvoort
- Re: [mpls-tp] Problems with SPME as the path segm… Alexander Vainshtein
- Re: [mpls-tp] Problems with SPME as the path segm… Huub van Helvoort
- [mpls-tp] 答复: Re: Problems with SPME as the path … dai.xuehui
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Problems with SPME as the path segm… zhang.fei3
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Alexander Vainshtein
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… zhang.fei3
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Alexander Vainshtein
- Re: [mpls-tp] Problems with SPME as the path segm… Dan Frost
- Re: [mpls-tp] Problems with SPME as the path segm… Alexander Vainshtein
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Alexander Vainshtein
- Re: [mpls-tp] Problems with SPME as the path segm… Loa Andersson
- Re: [mpls-tp] Problems with SPME as the path segm… Dan Frost
- Re: [mpls-tp] Problems with SPME as the path segm… Alexander Vainshtein
- Re: [mpls-tp] Problems with SPME as the path segm… Loa Andersson
- Re: [mpls-tp] Problems with SPME as the path segm… Huub van Helvoort
- Re: [mpls-tp] Problems with SPME as the path segm… Loa Andersson
- Re: [mpls-tp] Problems with SPME as the path segm… David Allan I
- Re: [mpls-tp] Problems with SPME as the path segm… Loa Andersson
- Re: [mpls-tp] Problems with SPME as the path segm… Huub van Helvoort
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Ben Niven-Jenkins
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Alexander Vainshtein
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Greg Mirsky
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Ben Niven-Jenkins
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… Alexander Vainshtein
- Re: [mpls-tp] Problems with SPME as the path segm… Alexander Vainshtein
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Maarten Vissers
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Problems with SPME as the path segm… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… Alexander Vainshtein
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [mpls-tp] 答复: Re: Problems with SPME as the p… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… neil.2.harrison
- Re: [mpls-tp] Problems with SPME as the path segm… Curtis Villamizar
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… David Allan I
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… David Allan I
- Re: [mpls-tp] Problems with SPME as the path segm… Alexander Vainshtein
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… Stewart Bryant
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… Alexander Vainshtein
- Re: [mpls-tp] Problems with SPME as the path segm… David Allan I
- Re: [mpls-tp] Problems with SPME as the path segm… Maarten Vissers
- Re: [mpls-tp] Problems with SPME as the path segm… Sonny Thorelli