Re: [mpls-tp] MPLS-TP LSP questions
Velan S <velantechie@gmail.com> Wed, 02 March 2011 05:13 UTC
Return-Path: <velantechie@gmail.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 BCE063A6A30 for <mpls-tp@core3.amsl.com>; Tue, 1 Mar 2011 21:13:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 jMnPTVy1RC0y for <mpls-tp@core3.amsl.com>; Tue, 1 Mar 2011 21:13:51 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 7A1A23A69E4 for <mpls-tp@ietf.org>; Tue, 1 Mar 2011 21:13:51 -0800 (PST)
Received: by wyb42 with SMTP id 42so5932249wyb.31 for <mpls-tp@ietf.org>; Tue, 01 Mar 2011 21:14:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=A26xYLJmu3o2KXnng9M5446W2QUzhJStjTB+OCrp8XY=; b=REgQXcrRbkLN7GNqDQtzj6Hj/gO4Rz837Koy+qPQCw4bEblaCz/J8/J8UdRyS8BNlS rsvcVz1xaSMTvPjdiNSxj6MYJcycxOs5/eDvGM5pylODQO2VkNVPcC4FRXOX9lwG8uDp aC2P1V4RxsvCkcvUWfCPgRibnveJqD2Q2Zloo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Mx5ndoCb0YkXIX9aJ2gpbcGZJq4MQlPHox8JKQfhS9sCo7rUnZjvtEgnBTrrpN4CRK apH60VUY68Vk+FXctepdiRpixonAqS9lBxArm6KUpZXDkiIWTD7cs7Er0uXxBRVK4Ykh 48mMYJkJkScrm4j/Du3suXsvAalzwJLkHHfpo=
MIME-Version: 1.0
Received: by 10.227.71.129 with SMTP id h1mr7013775wbj.25.1299042895591; Tue, 01 Mar 2011 21:14:55 -0800 (PST)
Received: by 10.227.11.133 with HTTP; Tue, 1 Mar 2011 21:14:55 -0800 (PST)
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD51CFB47441@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTikqgFVrFaOp1Q4P0vKm9F1pZu+VC54NFj-P_zMT@mail.gmail.com> <60C093A41B5E45409A19D42CF7786DFD51CFB47441@EUSAACMS0703.eamcs.ericsson.se>
Date: Tue, 01 Mar 2011 21:14:55 -0800
Message-ID: <AANLkTikS=k021vot_wwHztWFDAuT_+Nrep4M0BOEK1W=@mail.gmail.com>
From: Velan S <velantechie@gmail.com>
To: David Allan I <david.i.allan@ericsson.com>
Content-Type: multipart/alternative; boundary="90e6ba47644956f8af049d78feb9"
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
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 05:13:52 -0000
Hi David and NH, Thanks for detailed points on this item. I will investigate how this mis-merge can be detected from the "See section". On Tue, Mar 1, 2011 at 4:04 PM, David Allan I <david.i.allan@ericsson.com>wrote: > 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 > >
- [mpls-tp] MPLS-TP LSP questions Velan S
- Re: [mpls-tp] MPLS-TP LSP questions neil.2.harrison
- Re: [mpls-tp] MPLS-TP LSP questions David Allan I
- Re: [mpls-tp] MPLS-TP LSP questions Velan S