[Mpls-interop] MPLS-TP OAM requirements - AIS/LockNotif - Can MIPs send "usolicited" OAM messages ?

Martin Vigoureux <martin.vigoureux@alcatel-lucent.com> Sun, 03 May 2009 18:23 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 58BEB3A7125 for <mpls-interop@core3.amsl.com>; Sun, 3 May 2009 11:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.082
X-Spam-Level:
X-Spam-Status: No, score=-6.082 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 7tkX5UFNt5IE for <mpls-interop@core3.amsl.com>; Sun, 3 May 2009 11:23:53 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 23D8428C298 for <mpls-interop@ietf.org>; Sun, 3 May 2009 11:23:30 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.dc-m.alcatel-lucent.com [155.132.6.76]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n43IOtft008049 for <mpls-interop@ietf.org>; Sun, 3 May 2009 20:24:55 +0200
Received: from [135.244.20.132] ([135.244.20.132]) by FRVELSBHS04.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Sun, 3 May 2009 20:24:54 +0200
Message-ID: <49FDE174.7000904@alcatel-lucent.com>
Date: Sun, 03 May 2009 20:24:52 +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: mpls-interop@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 May 2009 18:24:54.0755 (UTC) FILETIME=[74CD9330:01C9CC1C]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: [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: Sun, 03 May 2009 18:23:54 -0000

All,

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 |      |      |
+------+      +------+      +------+      +------+

Therefore can MIPs send OAM messages without having priorly received one
or did I miss something?

regards,
-m