Re: [Mpls-interop] MPLS-TP OAM requirements - AIS/LockNotif - Can MIPs send "usolicited" OAM messages ?
Martin Vigoureux <martin.vigoureux@alcatel-lucent.com> Mon, 04 May 2009 09:40 UTC
Return-Path: <Martin.Vigoureux@alcatel-lucent.com>
X-Original-To: mpls-interop@core3.amsl.com
Delivered-To: mpls-interop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A23FA3A6A42 for <mpls-interop@core3.amsl.com>; Mon, 4 May 2009 02:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.633
X-Spam-Level:
X-Spam-Status: No, score=-3.633 tagged_above=-999 required=5 tests=[AWL=-1.384, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 3K283rn9d0Pf for <mpls-interop@core3.amsl.com>; Mon, 4 May 2009 02:40:05 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id A078D3A697D for <mpls-interop@ietf.org>; Mon, 4 May 2009 02:40:05 -0700 (PDT)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.dc-m.alcatel-lucent.com [155.132.6.78]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n449fJU5022751; Mon, 4 May 2009 11:41:27 +0200
Received: from [172.27.205.135] ([172.27.205.135]) by FRVELSBHS06.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 4 May 2009 11:41:21 +0200
Message-ID: <49FEB841.2010808@alcatel-lucent.com>
Date: Mon, 04 May 2009 11:41:21 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: hhelvoort@chello.nl
References: <49FDE174.7000904@alcatel-lucent.com> <49FE253E.5060803@chello.nl>
In-Reply-To: <49FE253E.5060803@chello.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 04 May 2009 09:41:21.0644 (UTC) FILETIME=[7B8AFAC0:01C9CC9C]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
Cc: mpls-interop@ietf.org
Subject: Re: [Mpls-interop] MPLS-TP OAM requirements - AIS/LockNotif - Can MIPs send "usolicited" OAM messages ?
X-BeenThere: mpls-interop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF MPLS Interoperability Design Team <mpls-interop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-interop>, <mailto:mpls-interop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-interop>
List-Post: <mailto:mpls-interop@ietf.org>
List-Help: <mailto:mpls-interop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-interop>, <mailto:mpls-interop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2009 09:40:06 -0000
Huub, please see in-line. regards, -m Huub van Helvoort a écrit : > Bonsoir Martin, > > You wrote: > >> as part of the discussion on AIS/Lock Notification, >> the server layer MEPs, detecting a fault/lock condition, should >> inform (the MEPs of) the client layers relying on that >> server layer and which are affected by the condition. >> >> However as I understand it is not the MEP (sMEP) of the >> server layer that sends a notification to the client layers >> MEPs (cMEP) but the MIP (cMIP) of the client layer which >> is hosted on the same node than the MEP (sMEP). >> See the figure below (where the double dashed line is >> an LSP, and the ~ line represents an LSP nested in the >> other LSP. >> >> +------+ +------+ +------+ +------+ >> | |------| |------| cMIP |~~~~~~| cMEP | >> | | | | | ^ | | | >> | | | | | | | | | >> | | | | | | | | | >> | |======| |======| sMEP | | | >> +------+ +------+ +------+ +------+ > > I modified the figure to align with what you wrote. [mvx] thx. In fact the double dashed line was already there but with quite some spacing between the top and bottom. > >> Therefore can MIPs send OAM messages without having priorly received one >> or did I miss something? > > No, a MIP can only respond to messages it receives from a MEP > that has the same MEG level, i.e. exists in the same path. > > In your figure the cMIP ignores messages sent by sMEP. but then, how does a Lock condition of the lower LSP is notified to cMEP? > > Cheers, Huub. >
- [Mpls-interop] MPLS-TP OAM requirements - AIS/Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - AIS… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - AIS… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - AIS… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - AIS… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - AIS… George Swallow
- Re: [Mpls-interop] MPLS-TP OAM requirements - AIS… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - AIS… Malcolm Betts