IETF Logo Mail Archive

Re: [Mpls-interop] On Req.41

"Malcolm Betts" <betts01@nortel.com> Wed, 01 April 2009 12:40 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 751463A67F9 for <mpls-interop@core3.amsl.com>; Wed, 1 Apr 2009 05:40:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.923
X-Spam-Level:
X-Spam-Status: No, score=-5.923 tagged_above=-999 required=5 tests=[AWL=0.676, 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 UrjoaHZ4lcHu for <mpls-interop@core3.amsl.com>; Wed, 1 Apr 2009 05:40:33 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 7DD643A68D5 for <mpls-interop@ietf.org>; Wed, 1 Apr 2009 05:40:33 -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 n31Cevr11014; Wed, 1 Apr 2009 12:40:57 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: Wed, 01 Apr 2009 08:41:27 -0400
Message-ID: <0BDFFF51DC89434FA33F8B37FCE363D516A265C8@zcarhxm2.corp.nortel.com>
In-Reply-To: <581F790938EF4F68A3DFB19FA5CCFACF@your029b8cecfe>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Mpls-interop] On Req.41
Thread-Index: AcmyUJlLUd7mMpYoQcO4OaesxctV1QAdXRNw
References: <C5F83D1A.149D7%benjamin.niven-jenkins@bt.com> <581F790938EF4F68A3DFB19FA5CCFACF@your029b8cecfe>
From: Malcolm Betts <betts01@nortel.com>
To: Adrian Farrel <adrian@olddog.co.uk>, Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
Cc: mpls-interop@ietf.org
Subject: Re: [Mpls-interop] On Req.41
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: Wed, 01 Apr 2009 12:40:34 -0000

The comment from Adrian raises an interesting point:

Should data plane OAM triggers (e.g. loss of CC, server AIS etc) be
described as a part of the data plane, as implied by Adrian's comment
and draft sprecher:

Or in the OAM draft, as implied by Ben's comment.

I have a slight preference to describing them as part of the data plane
OAM, key point is that we need to be consistent. 


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 Adrian Farrel
Sent: Tuesday, March 31, 2009 6:27 PM
To: Ben Niven-Jenkins; Annamaria Fulignoli; Malis, Andrew G. (Andy)
Cc: mpls-interop@ietf.org
Subject: Re: [Mpls-interop] On Req.41

Hi,

> I would argue protection triggers are likely to be either control 
> plane driven (we have that covered), management plane driven (Eric's 
> draft) or OAM driven (Martin's) draft.

Or, locally, data plane driven.

Please see draft-sprecher-mpls-tp-survive-fwk-01.txt for more details on
protection triggers.

Adrian 

_______________________________________________
Mpls-interop mailing list
Mpls-interop@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-interop

v2.23.0 | Report a Bug | By Email