Re: [Mpls-interop] MPLS-TP OAM requirements - AIS/LockNotif - Can MIPs send "usolicited" OAM messages ?
"Malcolm Betts" <betts01@nortel.com> Tue, 05 May 2009 13:44 UTC
Return-Path: <BETTS01@nortel.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 1BB403A67DA for <mpls-interop@core3.amsl.com>; Tue, 5 May 2009 06:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.24
X-Spam-Level:
X-Spam-Status: No, score=-6.24 tagged_above=-999 required=5 tests=[AWL=0.359, BAYES_00=-2.599, 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 WaQPC-j+xucf for <mpls-interop@core3.amsl.com>; Tue, 5 May 2009 06:44:42 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 7C4CA3A67AE for <mpls-interop@ietf.org>; Tue, 5 May 2009 06:44:42 -0700 (PDT)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n45Dj9614628; Tue, 5 May 2009 13:45:10 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 05 May 2009 09:46:02 -0400
Message-ID: <0BDFFF51DC89434FA33F8B37FCE363D517038C44@zcarhxm2.corp.nortel.com>
In-Reply-To: <49FF6616.3050905@chello.nl>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mpls-interop] MPLS-TP OAM requirements - AIS/LockNotif - Can MIPs send "usolicited" OAM messages ?
Thread-Index: AcnNBCHP1awuJ2VXTYyy6P/LEGe2YgAg1mTg
References: <C624ADFD.12992%swallow@cisco.com> <49FF6616.3050905@chello.nl>
From: Malcolm Betts <betts01@nortel.com>
To: hhelvoort@chello.nl, George Swallow <swallow@cisco.com>
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: Tue, 05 May 2009 13:44:44 -0000
Agree, see in line. Malcolm Betts Nortel Networks Phone: +1 613 763 7860 (ESN 393) email: betts01@nortel.com -----Original Message----- From: mpls-interop-bounces@ietf.org [mailto:mpls-interop-bounces@ietf.org] On Behalf Of Huub van Helvoort Sent: Monday, May 04, 2009 6:03 PM To: George Swallow Cc: mpls-interop@ietf.org Subject: Re: [Mpls-interop] MPLS-TP OAM requirements - AIS/LockNotif - Can MIPs send "usolicited" OAM messages ? Hello George, You wrote: > I very much agree with Martin here. > > In MPLS-TP the MEG level is not explicit. It is inferred from the LSP > the OAM is received on. In typical LSRs, a Server layer down event, > e.g. The failure of a link results in an "Interface Down Event". When > this occurs all clients of that interface that have registered for the > event would be notified. Further notification of peer entities is the > responsibility of those clients. I agree with this as well. > So to me it makes a great deal of sense to have the MEP serving the > link declare that the IF is down, and have the client MIPs be > responsible for sending any needed OAM messages regarding that event. The notification of the "interface down event" should be accomplished by inserting the OAM message (server failed) in the adaptation function of the server layer MEP. MB> Not convinced that we need an OAM message, we do need a local notification. Regards, Huub. -- ================================================================ Always remember that you are unique...just like everyone else... _______________________________________________ Mpls-interop mailing list Mpls-interop@ietf.org https://www.ietf.org/mailman/listinfo/mpls-interop
- [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