From owner-routing-discussion  Mon Aug 21 19:12:13 2000
Received: from lumen.chromisys.com ([63.102.55.200])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10869
	for <routing-discussion@ietf.org>; Mon, 21 Aug 2000 19:12:13 -0400 (EDT)
Received: by nt_d2300.chromisys.com with Internet Mail Service (5.5.2448.0)
	id <QFK1N2J7>; Mon, 21 Aug 2000 16:12:09 -0700
Message-ID: <BCFB7F5FCA46D3119EE10050048279E0266CA8@nt_d2300.chromisys.com>
From: John Drake <jdrake@calient.net>
To: "'David Oran'" <oran@cisco.com>,
        Routing Area IETF
	 <routing-discussion@ietf.org>
Subject: RE: Routing Area Status Update
Date: Mon, 21 Aug 2000 16:12:09 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"

David,  

I'd prefer keeping the restoration work in the MPLS working group.  This is
a key area for MPLS and MPL(ambda)S networks and logically the next thing
for the MPLS group to work on.  Historically, this is where restoration has
been discussed in the past.  

I've never been clear as to what the IPO work group is supposed to do.  The
UNI might be reasonable, but last week the OIF voted for their UNI to use
RSVP-TE and CR-LDP, so it sounds as though the work, if any, could be done
between the OIF and the MPLS work group.

Thanks,

John
-----Original Message-----
From: David Oran [mailto:oran@cisco.com]
Sent: Friday, August 11, 2000 11:55 AM
To: Routing Area IETF
Subject: Routing Area Status Update


First, Rob and I would like to express our appreciation to all those of you
who have posted suggestions on the list and otherwise participated in the
discussion. The broader and deeper insights we get the better the outcome
will be for structuring the work going forward.

It's been a week since IETF, and everybody at least agrees that we want to
move quickly, so we thought the community deserved a status update on where
we stand on these items. Nothing is finalized to the point that further
discussion and direction changes are precluded, but here is the current
state of affairs:

- We are proceeding toward proposing a new Working Group to handle
generalized comtrol plane issues, as identified in the routing area meeting
(protection/restoration, link characterization, etc.). We are beginning to
talk to potential candidates for chairs of this working group and once we
have good candidates we will proceed with the details of the charter. This
will in all likelihood *not* be the general routing area WG discussed at the
routing-area meeting, but a specific WG for this task, and we are optimistic
that Rob and I will find excellent chairs so we won't have to assume this
problematical role.

- The "Foo-over-MPLS" work is currently under discussion in the IESG and
IAB. The exact form of this work, and which area undertakes it is not
decided. It may be a few more weeks before this settles down. It is not
likely that we will charter the work in the form of "Foo-over-anything" as
some of the list have proposed however, because there is concern that the
encapsulating protocol plays a significant enough role in the details of the
method that we want to make sure no issues surrounding congestion control,
security, scope of deployment, etc. are missed.

- We are in the last stage of getting the IPO WG going. There are one or two
charter items that need a final pass, but this should settle down quite
rapidly.

Dave and Rob.


From owner-routing-discussion  Fri Aug 25 13:33:01 2000
Received: from portcullis.ral.virata.com (mail.rsacom.com [208.209.94.122])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25243
	for <routing-discussion@ietf.org>; Fri, 25 Aug 2000 13:33:01 -0400 (EDT)
Received: from mango.ral.virata.com (mango.ral.virata.com [172.16.1.253])
	by portcullis.ral.virata.com (8.9.3/8.8.5) with ESMTP id EAA23464
	for <routing-discussion@ietf.org>; Fri, 25 Aug 2000 04:57:50 -0400
Received: from cowboy.ral.virata.com (cowboy.ral.virata.com [192.168.1.170])
	by mango.ral.virata.com (8.9.3/8.9.3/Debian/GNU) with ESMTP id NAA22816
	for <routing-discussion@ietf.org>; Fri, 25 Aug 2000 13:32:59 -0400
Received: by cowboy.ral.virata.com with Internet Mail Service (5.5.2650.21)
	id <RA8Q49TM>; Fri, 25 Aug 2000 13:35:35 -0400
Message-ID: <2B31A87FDF5DD411A74200508BD94E4902CFC5@cowboy.ral.virata.com>
From: "Achkinazi, Igor" <iachkinazi@virata.com>
To: routing-discussion@ietf.org
Subject: subscribe
Date: Fri, 25 Aug 2000 13:35:35 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"

subscribe


From owner-routing-discussion  Sat Aug 26 02:35:26 2000
Received: from amsmta06-svc.chello.nl ([213.46.240.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19499
	for <routing-discussion@ietf.org>; Sat, 26 Aug 2000 02:35:26 -0400 (EDT)
Received: from luuk ([212.187.19.93]) by amsmta06-svc.chello.nl
          (InterMail vK.4.02.00.10 201-232-116-110 license 85c33b9378a1845aa5f2088df8e3706e)
          with SMTP id <20000826063535.TFMW4261.amsmta06-svc@luuk>
          for <routing-discussion@ietf.org>;
          Sat, 26 Aug 2000 08:35:35 +0200
Message-ID: <007c01c00f28$06f98c20$021e10ac@luuk>
From: "Luuk Ramaker" <humor@chello.nl>
To: <routing-discussion@ietf.org>
Subject: subscribe
Date: Sat, 26 Aug 2000 08:36:55 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0079_01C00F38.CA486060"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

This is a multi-part message in MIME format.

------=_NextPart_000_0079_01C00F38.CA486060
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

subscribe

------=_NextPart_000_0079_01C00F38.CA486060
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>subscribe</DIV></BODY></HTML>

------=_NextPart_000_0079_01C00F38.CA486060--