From mter-bounces@ietf.org Mon Feb 13 08:56:56 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8eCG-0007yK-1u; Mon, 13 Feb 2006 08:56:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8eCD-0007xY-9d for mter@megatron.ietf.org; Mon, 13 Feb 2006 08:56:53 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21333 for ; Mon, 13 Feb 2006 08:55:07 -0500 (EST) Received: from protext01.itu.ch ([156.106.192.41]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8ePn-0000t0-2d for mter@ietf.org; Mon, 13 Feb 2006 09:10:58 -0500 Received: from protext01.itu.ch ([156.106.192.41]) by protext01.itu.ch with Microsoft SMTPSVC(5.0.2195.6713); Mon, 13 Feb 2006 14:56:39 +0100 Received: From mail5.itu.ch ([156.106.192.21]) by protext01.itu.ch (WebShield SMTP v4.5 MR1a); id 1139838999285; Mon, 13 Feb 2006 14:56:39 +0100 Received: from Puppy ([156.106.205.35]) by mail5.itu.ch (8.13.5/8.13.5) with SMTP id k1DDuc0f265172 for ; Mon, 13 Feb 2006 14:56:38 +0100 (MET) Message-ID: <05ad01c630a5$e0ef6400$36cd6a9c@Puppy> From: "Adrian Farrel" To: Date: Mon, 13 Feb 2006 14:00:25 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (mail5.itu.ch [156.106.192.21]); Mon, 13 Feb 2006 14:56:39 +0100 (MET) X-OriginalArrivalTime: 13 Feb 2006 13:56:39.0957 (UTC) FILETIME=[502E0C50:01C630A5] X-Spam-Score: 0.0 (/) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 Content-Transfer-Encoding: 7bit Subject: [Mter] Dead or alive? X-BeenThere: mter@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Multi-TEchnology Recovery List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mter-bounces@ietf.org Errors-To: mter-bounces@ietf.org What is the status of MTER? Thanks, Adrian _______________________________________________ MTER mailing list MTER@ietf.org https://www1.ietf.org/mailman/listinfo/mter From mter-bounces@ietf.org Mon Feb 13 10:11:41 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8fMb-0006F9-B7; Mon, 13 Feb 2006 10:11:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8fMZ-0006EO-P8 for mter@megatron.ietf.org; Mon, 13 Feb 2006 10:11:39 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28719 for ; Mon, 13 Feb 2006 10:09:55 -0500 (EST) Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8faC-0003WY-8z for mter@ietf.org; Mon, 13 Feb 2006 10:25:45 -0500 Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 13 Feb 2006 16:11:29 +0100 Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k1DFB25w027338; Mon, 13 Feb 2006 16:11:26 +0100 (MET) Received: from xbh-rtp-211.amer.cisco.com ([64.102.31.102]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 13 Feb 2006 16:11:03 +0100 Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 13 Feb 2006 10:11:00 -0500 Received: from [192.168.1.101] ([10.86.242.147]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 13 Feb 2006 10:11:00 -0500 In-Reply-To: <05ad01c630a5$e0ef6400$36cd6a9c@Puppy> References: <05ad01c630a5$e0ef6400$36cd6a9c@Puppy> Mime-Version: 1.0 (Apple Message framework v746.2) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <465D7861-6E17-4B5D-BB4F-C4A4D673E8DF@cisco.com> Content-Transfer-Encoding: 7bit From: JP Vasseur Subject: Re: [Mter] Dead or alive? Date: Mon, 13 Feb 2006 10:10:29 -0500 To: Adrian Farrel X-Mailer: Apple Mail (2.746.2) X-OriginalArrivalTime: 13 Feb 2006 15:11:00.0070 (UTC) FILETIME=[B29D4860:01C630AF] X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit Cc: mter@ietf.org X-BeenThere: mter@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-TEchnology Recovery List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mter-bounces@ietf.org Errors-To: mter-bounces@ietf.org Hi Adrian, A draft is "under progress" that should trigger the discussion. No BOF scheduled for this IETF. Thanks. JP. On Feb 13, 2006, at 9:00 AM, Adrian Farrel wrote: > What is the status of MTER? > > Thanks, > Adrian > > _______________________________________________ > MTER mailing list > MTER@ietf.org > https://www1.ietf.org/mailman/listinfo/mter _______________________________________________ MTER mailing list MTER@ietf.org https://www1.ietf.org/mailman/listinfo/mter From mter-bounces@ietf.org Tue Feb 28 17:31:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEDNO-0004lt-27; Tue, 28 Feb 2006 17:31:26 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEDNN-0004jt-63 for mter@ietf.org; Tue, 28 Feb 2006 17:31:25 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEDNL-0002zR-SV for mter@ietf.org; Tue, 28 Feb 2006 17:31:25 -0500 Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 28 Feb 2006 14:31:24 -0800 X-IronPort-AV: i="4.02,154,1139212800"; d="scan'208"; a="258557555:sNHT33452814" Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k1SMVJXl027080; Tue, 28 Feb 2006 14:31:20 -0800 (PST) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 28 Feb 2006 17:31:19 -0500 Received: from [10.86.104.179] ([10.86.104.179]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 28 Feb 2006 17:31:19 -0500 Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <49F0ECD8-F080-4DC1-9CD3-0363258A4972@cisco.com> Content-Transfer-Encoding: 7bit From: JP Vasseur Date: Tue, 28 Feb 2006 17:30:42 -0500 To: mter@ietf.org X-Mailer: Apple Mail (2.746.2) X-OriginalArrivalTime: 28 Feb 2006 22:31:19.0174 (UTC) FILETIME=[B1D2E260:01C63CB6] X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: "David Kessens \(E-mail\)" , lei.wang@telenor.com, "Bert \(Bert\) Wijnen" , Jaime Miles Subject: [Mter] Time to start the discussion ? X-BeenThere: mter@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-TEchnology Recovery List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mter-bounces@ietf.org Hi, It took a little while to come up with a clear problem statement but we now have an I-D (http://www.ietf.org/internet-drafts/draft-ahmad- mter-problem-statement-00.txt (thanks to the authors)) that will hopefully trigger some discussion with the objective to see whether there is enough interest to pursue this work at the IETF. The draft has been structured so as to first show three scenarios where various recovery mechanisms could be used in combination. This does not aim to cover all possible cases but some pretty common deployment scenario for the sake of illustration. Then various Multi- TEchnology Recovery (MTER) issues are discussed. What is the objective of this work ? Let's start with the set of non-objective first ... * There is no intention to come up with protocols extensions that are being worked out in existing WGs (ISIS, IDR, CCAMP, ....) * Discuss implementation-specific issues Now the objectives ... What has been shown through the three MTER deployment cases making use of multiple recovery mechanisms in combination is the following: -> There are cases where being able to identify the root failure cause would significantly improve various recovery metrics such as the convergence time, required backup capacity, ... and so on. Do we need to work on such mechanisms at the IETF is an open question ? -> MIBs and OAM tools have been defined for most of the recovery techniques (IGP, BGP, MPLS FRR, GMPLS, ... ) and there are clearly no such tool for the aspects related to their combined use. It looks like the availability of such tools would help Service Providers to manage, tune and troubleshooting their network. Again, feed-backs from this ML are critical to see how to move forward and if the community expressed some interest. Thanks for your feed-backs. JP, Jean-Louis and Raymond. _______________________________________________ MTER mailing list MTER@ietf.org https://www1.ietf.org/mailman/listinfo/mter