From mter-bounces@ietf.org Wed Dec 21 11:12:58 2005
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 1Ep6aI-0005Ni-Kz; Wed, 21 Dec 2005 11:12:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ep6aG-0005Na-Ij
	for mter@megatron.ietf.org; Wed, 21 Dec 2005 11:12:57 -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 LAA08570
	for <mter@ietf.org>; Wed, 21 Dec 2005 11:11:51 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ep6cu-0003eh-64
	for mter@ietf.org; Wed, 21 Dec 2005 11:15:41 -0500
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-1.cisco.com with ESMTP; 21 Dec 2005 08:12:47 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.99,280,1131350400"; 
	d="scan'208"; a="17854454:sNHT26949176"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id jBLGCHUp017318; 
	Wed, 21 Dec 2005 11:12:42 -0500 (EST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 21 Dec 2005 11:12:33 -0500
Received: from [192.168.1.101] ([10.86.242.118]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 21 Dec 2005 11:12:33 -0500
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <72598028-2F39-4445-9A19-3264FA5CD421@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Date: Wed, 21 Dec 2005 11:11:58 -0500
To: mter@ietf.org
X-Mailer: Apple Mail (2.746.2)
X-OriginalArrivalTime: 21 Dec 2005 16:12:33.0442 (UTC)
	FILETIME=[59BAA020:01C60649]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: "David Kessens \(E-mail\)" <david.kessens@nokia.com>,
	"Bert \(Bert\) Wijnen" <bwijnen@lucent.com>,
	lei.wang@telenor.com, Jaime Miles <Jaime.Miles@Level3.com>
Subject: [Mter] Quick heads-up
X-BeenThere: mter@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-TEchnology Recovery <mter.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mter>,
	<mailto:mter-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mter>
List-Post: <mailto:mter@ietf.org>
List-Help: <mailto:mter-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mter>,
	<mailto:mter-request@ietf.org?subject=subscribe>
Sender: mter-bounces@ietf.org
Errors-To: mter-bounces@ietf.org

Hi,

Thanks for having registered to this list.

Here is a quick heads-up on where we stand.

We had an informal meeting in Vancouver with a number of Service  
Providers that expressed a real interest in working on the  
interactions issues related to the combined use of multiple  
protection/restoration techniques (MPLS FRR and Fast IGP, Graceful  
Restart and IGP, GMPLS P&R and Fast IGP, ...).

The best approach to start the discussion is to produce a problem  
statement.

The problem statement ID is currently in progress co-authored by:
	- Jaime Miles (Level 3)
	- Eiji Oki (NTT)
	- Zubair Ahmad (EQUANT)
	- Lei Wang (Telenor)

The aim of this ID (to be posted early January) is to describe the  
problem statement and start the ball rolling in January so as to  
determine if there is enough interest from the community on this topic.

Stay tuned.

Thanks.

JP, Jean-Louis and Raymond.

_______________________________________________
MTER mailing list
MTER@ietf.org
https://www1.ietf.org/mailman/listinfo/mter



From mter-bounces@ietf.org Thu Dec 22 12:54:19 2005
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 1EpUdv-0005C7-Hm; Thu, 22 Dec 2005 12:54:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EpU2I-00066K-Mi
	for mter@megatron.ietf.org; Thu, 22 Dec 2005 12:15:26 -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 MAA07417
	for <mter@ietf.org>; Thu, 22 Dec 2005 12:14:21 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EpU59-0001jl-Dp
	for mter@ietf.org; Thu, 22 Dec 2005 12:18:24 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id jBMHFFK5010095
	for <mter@ietf.org>; Thu, 22 Dec 2005 11:15:16 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <X5BR5DPK>; Thu, 22 Dec 2005 18:15:13 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508F17387@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: mter@ietf.org
Date: Thu, 22 Dec 2005 16:15:55 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
X-Mailman-Approved-At: Thu, 22 Dec 2005 12:54:17 -0500
Subject: [Mter] FW: Successful BOF document
X-BeenThere: mter@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-TEchnology Recovery <mter.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mter>,
	<mailto:mter-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mter>
List-Post: <mailto:mter@ietf.org>
List-Help: <mailto:mter-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mter>,
	<mailto:mter-request@ietf.org?subject=subscribe>
Sender: mter-bounces@ietf.org
Errors-To: mter-bounces@ietf.org


Hi All,

Have you seen the document that Thomas wrote on how to run a successful
BOF:

http://www.ietf.org/internet-drafts/draft-narten-successful-bof-00.txt

It probably helps you all to prepare well for a possible
BOF. As you can see in the document.... timing is important,
and the IETF meeting is less than 2,5 months away.

Bert

_______________________________________________
MTER mailing list
MTER@ietf.org
https://www1.ietf.org/mailman/listinfo/mter



