Re: [Mpls-interop] MPLS-TP OAM requirements - Lock and notification of lock
Huub van Helvoort <hhelvoort@chello.nl> Sun, 03 May 2009 23:07 UTC
Return-Path: <hhelvoort@chello.nl>
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 D30843A6C19 for <mpls-interop@core3.amsl.com>; Sun, 3 May 2009 16:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.283
X-Spam-Level:
X-Spam-Status: No, score=-1.283 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 d4BcF5VEv+IK for <mpls-interop@core3.amsl.com>; Sun, 3 May 2009 16:07:58 -0700 (PDT)
Received: from viefep14-int.chello.at (viefep14-int.chello.at [62.179.121.34]) by core3.amsl.com (Postfix) with ESMTP id 8F5933A6B4D for <mpls-interop@ietf.org>; Sun, 3 May 2009 16:07:57 -0700 (PDT)
Received: from edge01.upc.biz ([192.168.13.236]) by viefep14-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090503230921.PVFJ10055.viefep14-int.chello.at@edge01.upc.biz>; Mon, 4 May 2009 01:09:21 +0200
Received: from McAsterix.local ([24.132.228.153]) by edge01.upc.biz with edge id nB9K1b02w3KDBhC01B9MPH; Mon, 04 May 2009 01:09:21 +0200
X-SourceIP: 24.132.228.153
Message-ID: <49FE241F.5080007@chello.nl>
Date: Mon, 04 May 2009 01:09:19 +0200
From: Huub van Helvoort <hhelvoort@chello.nl>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
References: <0BDFFF51DC89434FA33F8B37FCE363D516FDAE56@zcarhxm2.corp.nortel.com> <42D4A33F1EAE420289ED4EFCA24D19BB@your029b8cecfe> <49FDE0C4.7060807@alcatel-lucent.com>
In-Reply-To: <49FDE0C4.7060807@alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mpls-interop@ietf.org
Subject: Re: [Mpls-interop] MPLS-TP OAM requirements - Lock and notification of lock
X-BeenThere: mpls-interop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hhelvoort@chello.nl
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 23:07:58 -0000
Bonsoir Martin, To continue with the othe rquestion: > See also my e-mail: > MPLS-TP OAM requirements - AIS/LockNotif - Can MIPs send "usolicited" > OAM messages ? The answer was no. > -question: > More generally to the comment above, who should notify and who should > notify whom? > I would tend to say: > the receiving node of a locked direction, informs downstream receiving > nodes of nested LSPs. To be more exact, the sink side of a locked LSP, PW, Section, has to inform its clients. > This is a Fowrward Indication and if we do > so then receiving points MUST indeed be informed of a Lock (c.f. > discussion at the beginning of the e-mail). > Should source points (locking points) do some reverse indication and > notify the source points of the LSPs that are nested in the locked LSP? > (but this maybe falls in the RDI functionality). Isn't this notification already caused by the locking at the far end? Or is the locking only applied in one direction of a bi-directional path? If yes, then the notification is not required. Cheers, Huub. -- ================================================================ Always remember that you are unique...just like everyone else...
- [Mpls-interop] MPLS-TP OAM requirements - Lock an… Malcolm Betts
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Adrian Farrel
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Sprecher, Nurit (NSN - IL/Hod HaSharon)
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Malcolm Betts
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Malcolm Betts
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Malcolm Betts
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Lam, Hing-Kam (Kam)
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Annamaria Fulignoli
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Adrian Farrel
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Huub van Helvoort
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Annamaria Fulignoli
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Lam, Hing-Kam (Kam)
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Martin Vigoureux
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Malcolm Betts
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Malcolm Betts
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Adrian Farrel
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Malcolm Betts
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Lam, Hing-Kam (Kam)
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Malcolm Betts
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Malcolm Betts
- Re: [Mpls-interop] MPLS-TP OAM requirements - Loc… Lam, Hing-Kam (Kam)