Re: [mpls-tp] MPLS-TP LSP questions

David Allan I <david.i.allan@ericsson.com> Wed, 02 March 2011 00:04 UTC

Return-Path: <david.i.allan@ericsson.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 47CFC3A6B55 for <mpls-tp@core3.amsl.com>; Tue, 1 Mar 2011 16:04:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.474
X-Spam-Level:
X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.124, 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 7JwsuKTBPHRA for <mpls-tp@core3.amsl.com>; Tue, 1 Mar 2011 16:04:52 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 6AE123A6962 for <mpls-tp@ietf.org>; Tue, 1 Mar 2011 16:04:52 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p2205Aco007075 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 1 Mar 2011 18:05:55 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.208]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 1 Mar 2011 19:04:51 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: Velan S <velantechie@gmail.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Tue, 01 Mar 2011 19:04:50 -0500
Thread-Topic: [mpls-tp] MPLS-TP LSP questions
Thread-Index: AcvX3P8picTAiMt0Rl6pq3vCIn+dsgAj/Y2Q
Message-ID: <60C093A41B5E45409A19D42CF7786DFD51CFB47441@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTikqgFVrFaOp1Q4P0vKm9F1pZu+VC54NFj-P_zMT@mail.gmail.com>
In-Reply-To: <AANLkTikqgFVrFaOp1Q4P0vKm9F1pZu+VC54NFj-P_zMT@mail.gmail.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_60C093A41B5E45409A19D42CF7786DFD51CFB47441EUSAACMS0703e_"
MIME-Version: 1.0
Subject: Re: [mpls-tp] MPLS-TP LSP questions
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: Wed, 02 Mar 2011 00:04:53 -0000

HI:

First I beleive it is safe to assume both TP and traditional LSPs will exist in an LSR.
If no OAM messages are running on one of the LSPs, a mis-merge cannot be detected.

If OAM is run on both what a node would see is an "unexpected encapsulation". See section 3.5.2 of the CC-CV-RDI draft...

I hope that helps
Dave



________________________________
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf Of Velan S
Sent: Monday, February 28, 2011 10:49 PM
To: mpls-tp@ietf.org
Subject: [mpls-tp] MPLS-TP LSP questions

Hi Experts,

I quickly wanted to check with you all,

Can both,  MPLS-TP LSP and traditional MPLS LSP, exist in a LSR?  If both can exist, there is possibility of merging of these LSPs at a LSR.  How can we detect such merging LSPs?

Thanks in advance.
S.Velan