[Mpls-interop] MPLS-TP OAM requirements - Client failure notifications

"Malcolm Betts" <betts01@nortel.com> Fri, 01 May 2009 20:03 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 CFB643A6C87 for <mpls-interop@core3.amsl.com>; Fri, 1 May 2009 13:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.162
X-Spam-Level:
X-Spam-Status: No, score=-6.162 tagged_above=-999 required=5 tests=[AWL=0.436, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 k5vU7EV4McXk for <mpls-interop@core3.amsl.com>; Fri, 1 May 2009 13:03:51 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id CAA0C3A67FD for <mpls-interop@ietf.org>; Fri, 1 May 2009 13:03:50 -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 n41K4JB05679 for <mpls-interop@ietf.org>; Fri, 1 May 2009 20:04:19 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9CA98.221BC900"
Date: Fri, 01 May 2009 16:05:10 -0400
Message-ID: <0BDFFF51DC89434FA33F8B37FCE363D516FDAEB4@zcarhxm2.corp.nortel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: MPLS-TP OAM requirements - Client failure notifications
Thread-Index: AcnKmCLVQIHsaVxSTn2DxoKYCagrYw==
From: Malcolm Betts <betts01@nortel.com>
To: mpls-interop@ietf.org
Subject: [Mpls-interop] MPLS-TP OAM requirements - Client failure notifications
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: Fri, 01 May 2009 20:03:51 -0000

To address the comments from Adrian I suggest that we replace the first
paragraph of section 2.2.9
2.2.9.  Client Failure Indication

   The MPLS-TP OAM toolset MUST provide a function to enable the
   propagation of client fault condition information, across the MPLS-TP
   network, if the client layer OAM mechanisms do not provide an alarm
   notification/propagation mechanism.
with them following:
2.2.9.  Client Failure Indication 

The MPLS-TP OAM toolset MUST provide a function to enable the
transparent propagation of information pertaining to a client fault
condition detected at the ingress to a PW, LSP or Section, across the
MPLS-TP network.

The requirement to support the tool is not dependent on the capability
of the client.  If a client supports failure notifications we need not
use this tool.  However the tool is always available. 


Malcolm Betts
Nortel Networks
Phone: +1 613 763 7860 (ESN 393)
email: betts01@nortel.com