From mailnull@www1.ietf.org  Wed Jan 15 10:22:54 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29851
	for <iporpr-archive@odin.ietf.org>; Wed, 15 Jan 2003 10:22:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h0FFbZv18517
	for iporpr-archive@odin.ietf.org; Wed, 15 Jan 2003 10:37:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FFbZJ18514
	for <iporpr-web-archive@optimus.ietf.org>; Wed, 15 Jan 2003 10:37:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29791
	for <iporpr-web-archive@ietf.org>; Wed, 15 Jan 2003 10:22:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FFXoJ17670;
	Wed, 15 Jan 2003 10:33:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FFU7J17441
	for <iporpr@optimus.ietf.org>; Wed, 15 Jan 2003 10:30:07 -0500
Received: from mailwest.unispherenetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29451
	for <iporpr@ietf.org>; Wed, 15 Jan 2003 10:14:55 -0500 (EST)
Received: by uniwest1.unispherenetworks.com with Internet Mail Service (5.5.2653.19)
	id <C2R784RZ>; Wed, 15 Jan 2003 10:18:17 -0500
Received: from fkastenholzpc1.juniper.net (fkastenholzpc1.dhcp.west.unispherenetworks.com [10.10.132.71]) by mailwest2.unispherenetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id VDJN27MK; Wed, 15 Jan 2003 10:10:10 -0500
Message-Id: <5.1.1.5.2.20030115100445.00b05db8@uniwest2>
X-Sender: fkastenholz@uniwest2
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Wed, 15 Jan 2003 10:18:09 -0500
To: iporpr@ietf.org
From: Frank Kastenholz <fkastenholz@juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [IPORPR] IPoRPR status
Sender: iporpr-admin@ietf.org
Errors-To: iporpr-admin@ietf.org
X-BeenThere: iporpr@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/iporpr>,
	<mailto:iporpr-request@ietf.org?subject=unsubscribe>
List-Id: IP over Resilient Packet Rings <iporpr.ietf.org>
List-Post: <mailto:iporpr@ietf.org>
List-Help: <mailto:iporpr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/iporpr>,
	<mailto:iporpr-request@ietf.org?subject=subscribe>

Just to let folks know

1. Albert Herrera has resigned as cochair of the working group.
   Albert was instrumental in getting the working group up and
   running and has been an asset to the group. The group as a
   whole will miss his technical contributions and I'll miss
   his cochairing. Albert - thanks for all the work you've
   done and good luck in your future endeavors. I'm sure we'll
   meet up again.

2. The ADs are going to be appointing a replacement for Albert.
   I do not know their time-table for this. Any questions on 
   this should be directed to the ADs since WG chairs serve
   at the sole discretion of the AD...

3. Albert was intending to be the primary editor on the framework
   draft for revising it with regard to the 'core' protocol work
   we've done. Obviously, he will no longer be able to perform that
   task.  So we're looking for an editor for that document.
   Some folks in the past had indicated interest in performing
   this role. If they could get in touch with me privately,
   I'd appreciate it.

4. The core-protocol draft has been out there for a while. I've
   received one email with comments on the technical content
   of the draft (and am currently editing the document to reflect
   those comments). I'd appreciate more comments and review...

5. I also received some comments with regard to whether we should
   do the core document or not. I _think_ that this issue was
   resolved (that we should do the document), but I'd like to 
   postpone any discussion on this issue until we get a new 
   cochair since me acting as sole chair for a discussion 
   affecting the future of a draft I edited is not appropriate.

6. There do not seem to be any issues facing the WG that would require
   that we meet at the upcomming IETF meeting (which is March 16-21
   in San Francisco). Is this true? Does anyone have anything that
   they think needs a face-to-face meeting?

Frank Kastenholz
co-chair, IPoRPR
_______________________________________________
IPORPR mailing list
IPORPR@ietf.org
https://www1.ietf.org/mailman/listinfo/iporpr



