Re: [PWE3] Tandem Connection Monitoring in the new PWE3 Chapter

Stewart Bryant <stbryant@cisco.com> Thu, 10 July 2008 10:51 UTC

Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A52F73A6902; Thu, 10 Jul 2008 03:51:11 -0700 (PDT)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBF873A6902 for <pwe3@core3.amsl.com>; Thu, 10 Jul 2008 03:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 cQ1af12lUFL5 for <pwe3@core3.amsl.com>; Thu, 10 Jul 2008 03:51:10 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 7EC5B3A67AB for <pwe3@ietf.org>; Thu, 10 Jul 2008 03:51:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.30,337,1212364800"; d="scan'208";a="13996231"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 10 Jul 2008 10:51:14 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m6AApE4F029635; Thu, 10 Jul 2008 12:51:14 +0200
Received: from stewart-bryants-computer.local (dhcp-10-61-97-218.cisco.com [10.61.97.218]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m6AApEA2022958; Thu, 10 Jul 2008 10:51:14 GMT
Message-ID: <4875E9A4.4060906@cisco.com>
Date: Thu, 10 Jul 2008 11:51:16 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
References: <183DD1B052A11A40B76125E42F1CBAAB12E5A74E@zcarhxm1.corp.nortel.com> <2ECAA42C79676B42AEBAC11229CA7D0C02C5B374@E03MVB2-UKBR.domain1.systemhost.net> <A3C5DF08D38B6049839A6F553B331C76801DE56BB9@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C76801DE56BB9@ILPTMAIL02.ecitele.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1914; t=1215687074; x=1216551074; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=stbryant@cisco.com; z=From:=20Stewart=20Bryant=20<stbryant@cisco.com> |Subject:=20Re=3A=20Tandem=20Connection=20Monitoring=20in=2 0the=20new=20PWE3=20Chapter |Sender:=20; bh=wc6BrXvMHv65xg8pdUXGzG1+uBMpzH4zMukoYp/467c=; b=iCFEw+Jb4vy8pAebK336TttquFL/jxI9pEE25a1xB0Eg4kIX8F1WKOgMCm YiKU6JKFGrLIGAf8XpKXpFl2mZKEG/cAQnz3snEcewI31kIWRp/rFRHpRuyt jVoXq8vk/7;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
Cc: "neil.2.harrison@bt.com" <neil.2.harrison@bt.com>, "pwe3@ietf.org" <pwe3@ietf.org>, Jeremy Brayley <Jeremy.Brayley@ecitele.com>, Danny McPherson <danny@tcb.net>, Alik Shimelmits <Alik.Shimelmits@ecitele.com>
Subject: Re: [PWE3] Tandem Connection Monitoring in the new PWE3 Chapter
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Alexander Vainshtein wrote:
>  Stewart, Danny and all,
>
>   
>> -----Original Message-----
>> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org]
>> On Behalf Of neil.2.harrison@bt.com
>> Sent: Wednesday, July 09, 2008 10:18 PM
>> To: mohand@nortel.com; sajassi@cisco.com
>> Cc: pwe3@ietf.org; stbryant@cisco.com
>> Subject: Re: [PWE3] draft-mohan-pwe3-mpls-eth-oam-iwk-00.txt
>> as WG draft
>>
>>     
> ... snipped ...
>   
>> I've just noticed TCM (Tandem Connection Monitoring) has been added to the
>> PWE3 charter.  I would strongly advise IETF *not* to go here just
>> because others have included this in their standards.  This idea has
>> been around for many years in ITU and there are very good reasons why
>> very little of it is used in practice (I can spell this out if not
>> obvious).
>>
>> Regards, Neil
>>
>>     
> ... snipped to the end...
>
> I wonder how Tandem Connection Monitoring for PWs has made its way into the published Charter
> as one of the milestones. It is not discussed/defined in the Charter itself and it has not been mentioned
> on the WG mailing list for the last 7+ months (including the versions of the Charter posted for the WG
> discussion during the re-chartering process).
>
> I share Neil's concerns about this topic. In particular, Low-Order Path TCM (defined by ITU-T in addition to the
> SONET High-Order Path TCM) is a feature known both for implementation complexity and lack of actual
> deployments... Do we really need more of the same in PWE3?
>
> Regards,
>         Sasha
>
>
>   
Sasha

TCM for PWs is in the JWT report: draft-bryant-mpls-tp-jwt-report-00.pdf

It was added when we were asked to flesh out deliverables to support 
MPLS-TP.

If as you and Neil suggest it's hard to make work, then that will be 
clear if/when
we see drafts defining it, and we can proceed accordingly.

- Stewart



_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3