Re: [Mpls-interop] Who will be in Geneva?

Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com> Mon, 01 December 2008 22:16 UTC

Return-Path: <mpls-interop-bounces@ietf.org>
X-Original-To: mpls-interop-archive@ietf.org
Delivered-To: ietfarch-mpls-interop-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D67B13A69B3; Mon, 1 Dec 2008 14:16:58 -0800 (PST)
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 2D1133A6BC4 for <mpls-interop@core3.amsl.com>; Mon, 1 Dec 2008 14:16:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.532
X-Spam-Level:
X-Spam-Status: No, score=-1.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
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 nL0JKV1-RqxO for <mpls-interop@core3.amsl.com>; Mon, 1 Dec 2008 14:16:56 -0800 (PST)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id 41A4D3A69B3 for <mpls-interop@ietf.org>; Mon, 1 Dec 2008 14:16:56 -0800 (PST)
Received: from E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.110]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 1 Dec 2008 22:16:51 +0000
Received: from 217.32.164.184 ([217.32.164.184]) by E03MVB3-UKBR.domain1.systemhost.net ([193.113.197.60]) via Exchange Front-End Server mail.bt.com ([193.113.197.28]) with Microsoft Exchange Server HTTP-DAV ; Mon, 1 Dec 2008 22:16:51 +0000
User-Agent: Microsoft-Entourage/12.14.0.081024
Date: Mon, 01 Dec 2008 22:16:50 +0000
From: Ben Niven-Jenkins <benjamin.niven-jenkins@bt.com>
To: Adrian Farrel <adrian@olddog.co.uk>, <mpls-interop@ietf.org>
Message-ID: <C55A12D2.EB1D%benjamin.niven-jenkins@bt.com>
Thread-Topic: [Mpls-interop] Who will be in Geneva?
Thread-Index: AclUAoG79k/wUVEUG0iikr7nxmko1w==
In-Reply-To: <A79C9B7D57B940FF802C8395F15E232E@your029b8cecfe>
Mime-version: 1.0
X-OriginalArrivalTime: 01 Dec 2008 22:16:51.0831 (UTC) FILETIME=[82D31870:01C95402]
Subject: Re: [Mpls-interop] Who will be in Geneva?
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: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mpls-interop-bounces@ietf.org
Errors-To: mpls-interop-bounces@ietf.org

Adrian,

On 27/11/2008 22:27, "Adrian Farrel" <adrian@olddog.co.uk> wrote:
> I ended up with a modest list of MPLS-TP design team folk willing to
> squander their evenings in Geneva working on drafts. Must be that the Swiss
> night life is too exciting!

Or that there is no Q.Whisky in SG15 ;-)

> Lastly, I would like to see if I can understand the issues with the OAM
> techniques proposed. Can we continue to use TTL? Does the idea of using
> nesting for all OAM segments really hold up? Is the OAM cart in danger of
> driving the protection hobbyhorse (pardon my mixed metaphore).

I'm no OAM expert (I leave that to Tom :-) ) but I am yet to be convinced by
nesting all OAM segments for the reason that it sounds complicated and that
means to me that it will be expensive to run and to scale.  It also sounds
like I'd have to have my network constructed in a particular way to be able
to use OAM which means even in the best run network I will at some point not
be able to run OAM when I need it (and the customer is screaming at me)
because the network wasn't constructed correctly (either by design or actual
configuration != design).

Ben

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