From iporpr-bounces@ietf.org  Mon Feb 28 18:31:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21124
	for <iporpr-web-archive@ietf.org>; Mon, 28 Feb 2005 18:31:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D5uNC-0003o1-2S
	for iporpr-web-archive@ietf.org; Mon, 28 Feb 2005 18:32:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D5uL3-0003xA-D8; Mon, 28 Feb 2005 18:30:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D5uL1-0003vC-3A
	for iporpr@megatron.ietf.org; Mon, 28 Feb 2005 18:30:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20960
	for <iporpr@ietf.org>; Mon, 28 Feb 2005 18:30:04 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5uLo-0003mO-Ps
	for iporpr@ietf.org; Mon, 28 Feb 2005 18:30:59 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j1SNTin15529
	for <iporpr@ietf.org>; Mon, 28 Feb 2005 18:29:44 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1J5B27XT>; Mon, 28 Feb 2005 18:29:45 -0500
Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D02931800@zcarhxm0.corp.nortel.com>
From: "Glenn Parsons" <gparsons@nortel.com>
To: iporpr@ietf.org
Date: Mon, 28 Feb 2005 18:29:20 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C51DED.5E091893"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
Subject: [IPORPR] Recharter IPoRPR WG
X-BeenThere: iporpr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Resilient Packet Rings <iporpr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/iporpr>,
	<mailto:iporpr-request@ietf.org?subject=unsubscribe>
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>
Sender: iporpr-bounces@ietf.org
Errors-To: iporpr-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C51DED.5E091893
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C51DED.5E091893"


------_=_NextPart_001_01C51DED.5E091893
Content-Type: text/plain

Folks,

The IPoRPR WG has been in hibernation for quite some time.  Given the
publication of IEEE 802.17 last year, it is time to shut down this WG...  or
recharter and do something.

Assuming there is some interest in the latter, I have attached a revised
charter proposal that our AD will be reviewing with the IESG shortly.

Let us know if you have any comments.

Cheers,

Glenn Parsons  
gparsons@nortel.com




 



------_=_NextPart_001_01C51DED.5E091893
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>Recharter IPoRPR WG</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Folks,</FONT>
</P>

<P><FONT SIZE=3D2>The IPoRPR WG has been in hibernation for quite some =
time.&nbsp; Given the publication of IEEE 802.17 last year, it is time =
to shut down this WG...&nbsp; or recharter and do something.</FONT></P>

<P><FONT SIZE=3D2>Assuming there is some interest in the latter, I have =
attached a revised charter proposal that our AD will be reviewing with =
the IESG shortly.</FONT></P>

<P><FONT SIZE=3D2>Let us know if you have any comments.</FONT>
</P>

<P><FONT SIZE=3D2>Cheers,</FONT>
</P>

<P><FONT SIZE=3D2>Glenn Parsons&nbsp; </FONT>
<BR><FONT SIZE=3D2>gparsons@nortel.com</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT FACE=3D"Arial" SIZE=3D2 COLOR=3D"#000000"></FONT>&nbsp;

</BODY>
</HTML>
------_=_NextPart_001_01C51DED.5E091893--

------_=_NextPart_000_01C51DED.5E091893
Content-Type: text/plain;
	name="IPoRPR charter Feb 2005.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="IPoRPR charter Feb 2005.txt"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


IP over Resilient Packet Rings (iporpr)

Last Modified: 2005-02-11

Chair(s):
Frank Kastenholz <fkastenholz@juniper.net>
Glenn Parsons <gparsons@nortel.com>

Internet Area Director(s):
Thomas Narten <narten@us.ibm.com>
Margaret Wasserman <margaret@thingmagic.com>

Internet Area Advisor:
Thomas Narten <narten@us.ibm.com>

Technical Advisor(s):
Thomas Narten <narten@us.ibm.com>

Mailing Lists:
General Discussion: iporpr@ietf.org
To Subscribe: iporpr-request@ietf.org
In Body: subscribe iporpr
Archive: http://www.ietf.org/mail-archive/web/iporpr/index.html

Description of Working Group:

Resilient Packet Rings (RPR), developed within the IEEE 802.17 RPR WG, =
provides substantial enhancements in both efficiency and flexibility =
over current bi-directional ring topologies. Benefits of resilient =
packet rings include spatial re-use (full utilization of both =
counter-rotating rings) while maintaining protection switching during =
media faults, as well as defined mechanisms for topology discovery, =
congestion control, and protection switching. Reference the IEEE 802.17 =
RPR WG at http://www.ieee802.org/17/ for further information.  IEEE =
802.17-2004 is currently published and work is in progress on bridging =
enhancements.
=20
The IPORPR Working Group will produce two documents:

   1) An IPORPR Framework that describes some of the features and
      characteristics of 802.17 RPR, and how they might be exploited
      by, e.g., IP or MPLS. For example, an RPR ring can be accessed
      in a number of ways: it can be viewed as a "dumb" LAN supporting
      traditional broadcast a la Ethernet (called "basic mode"), or its
      advanced features could be exploited.

   2) An IPORPR definition of how to transport IP over 802.17 RPR in
      "basic mode". This document will cover encapsulation formats
      (e.g., IPv4/IPv6), how to perform address resolution (e.g., =
ARP/ND), IP
      multicast transmission, priority mapping to the RPR=20
      "serviceClass", etc.
=20
There are no formal liaisons between the IPORPR working group and
other standards bodies.  However, cross participation is encouraged in =
the key RPR activities in these standards bodies:
- IEEE 802.17  (http://www.ieee802.org/17/)
- ITU-T SG15 Q9 =
(http://www.itu.int/ITU-T/studygroups/com15/sg15-q9.html)

Goals and Milestones:
Apr 05	=A0=A0	Publish draft Core IP-over-RPR specification =20
May 05	=A0=A0	Publish draft IP-over-802.17 Framework document.=20
Jul 05	=A0=A0	Submit final draft of Core protocol to the IESG for =
Proposed Standard Status.=20
Aug 05	=A0=A0	Submit final draft of Framework to the IESG for =
Informational Status.=20


------_=_NextPart_000_01C51DED.5E091893
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
IPORPR mailing list
IPORPR@ietf.org
https://www1.ietf.org/mailman/listinfo/iporpr

------_=_NextPart_000_01C51DED.5E091893--



From iporpr-bounces@ietf.org  Mon Feb 28 22:28:33 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09160
	for <iporpr-web-archive@ietf.org>; Mon, 28 Feb 2005 22:28:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D5y4e-0008Jz-Qt
	for iporpr-web-archive@ietf.org; Mon, 28 Feb 2005 22:29:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D5y2O-0004Ir-KI; Mon, 28 Feb 2005 22:27:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D5y2M-0004Hb-G5
	for iporpr@megatron.ietf.org; Mon, 28 Feb 2005 22:27:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09020
	for <iporpr@ietf.org>; Mon, 28 Feb 2005 22:27:01 -0500 (EST)
Received: from web88110.mail.re2.yahoo.com ([206.190.37.211])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D5y3B-0008Gv-3Z
	for iporpr@ietf.org; Mon, 28 Feb 2005 22:27:57 -0500
Message-ID: <20050301032653.15736.qmail@web88110.mail.re2.yahoo.com>
Received: from [24.103.59.3] by web88110.mail.re2.yahoo.com via HTTP;
	Mon, 28 Feb 2005 22:26:53 EST
Date: Mon, 28 Feb 2005 22:26:53 -0500 (EST)
From: Albert Herrera <albherre@rogers.com>
Subject: Re: [IPORPR] Recharter IPoRPR WG
To: Glenn Parsons <gparsons@nortel.com>, iporpr@ietf.org
In-Reply-To: <085091CB2CA14E4B8B163FFC37C84E9D02931800@zcarhxm0.corp.nortel.com>
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
X-BeenThere: iporpr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Resilient Packet Rings <iporpr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/iporpr>,
	<mailto:iporpr-request@ietf.org?subject=unsubscribe>
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>
Content-Type: multipart/mixed; boundary="===============0049142884=="
Sender: iporpr-bounces@ietf.org
Errors-To: iporpr-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c

--===============0049142884==
Content-Type: multipart/alternative; boundary="0-1783077310-1109647613=:15526"

--0-1783077310-1109647613=:15526
Content-Type: text/plain; charset=us-ascii

It might be best to use the old drafts (Framework and Core Protocol) as a starting point and modify to reflect where 802.17 is today. It will save us a lot of time specially if we're aiming for April 5 for first draft. Otherwise, we might want to push the dates a bit.
 
Regards,
Albert Herrera
TELUS National Systems


Glenn Parsons <gparsons@nortel.com> wrote:

Folks, 

The IPoRPR WG has been in hibernation for quite some time.  Given the publication of IEEE 802.17 last year, it is time to shut down this WG...  or recharter and do something.

Assuming there is some interest in the latter, I have attached a revised charter proposal that our AD will be reviewing with the IESG shortly.

Let us know if you have any comments. 

Cheers, 

Glenn Parsons  
gparsons@nortel.com 




 

 
IP over Resilient Packet Rings (iporpr)

Last Modified: 2005-02-11

Chair(s):
Frank Kastenholz 
Glenn Parsons 

Internet Area Director(s):
Thomas Narten 
Margaret Wasserman 

Internet Area Advisor:
Thomas Narten 

Technical Advisor(s):
Thomas Narten 

Mailing Lists:
General Discussion: iporpr@ietf.org
To Subscribe: iporpr-request@ietf.org
In Body: subscribe iporpr
Archive: http://www.ietf.org/mail-archive/web/iporpr/index.html

Description of Working Group:

Resilient Packet Rings (RPR), developed within the IEEE 802.17 RPR WG, provides substantial enhancements in both efficiency and flexibility over current bi-directional ring topologies. Benefits of resilient packet rings include spatial re-use (full utilization of both counter-rotating rings) while maintaining protection switching during media faults, as well as defined mechanisms for topology discovery, congestion control, and protection switching. Reference the IEEE 802.17 RPR WG at http://www.ieee802.org/17/ for further information. IEEE 802.17-2004 is currently published and work is in progress on bridging enhancements.

The IPORPR Working Group will produce two documents:

1) An IPORPR Framework that describes some of the features and
characteristics of 802.17 RPR, and how they might be exploited
by, e.g., IP or MPLS. For example, an RPR ring can be accessed
in a number of ways: it can be viewed as a "dumb" LAN supporting
traditional broadcast a la Ethernet (called "basic mode"), or its
advanced features could be exploited.

2) An IPORPR definition of how to transport IP over 802.17 RPR in
"basic mode". This document will cover encapsulation formats
(e.g., IPv4/IPv6), how to perform address resolution (e.g., ARP/ND), IP
multicast transmission, priority mapping to the RPR 
"serviceClass", etc.

There are no formal liaisons between the IPORPR working group and
other standards bodies. However, cross participation is encouraged in the key RPR activities in these standards bodies:
- IEEE 802.17 (http://www.ieee802.org/17/)
- ITU-T SG15 Q9 (http://www.itu.int/ITU-T/studygroups/com15/sg15-q9.html)

Goals and Milestones:
Apr 05    Publish draft Core IP-over-RPR specification 
May 05    Publish draft IP-over-802.17 Framework document. 
Jul 05    Submit final draft of Core protocol to the IESG for Proposed Standard Status. 
Aug 05    Submit final draft of Framework to the IESG for Informational Status. 

_______________________________________________
IPORPR mailing list
IPORPR@ietf.org
https://www1.ietf.org/mailman/listinfo/iporpr


--0-1783077310-1109647613=:15526
Content-Type: text/html; charset=us-ascii

<DIV>It might be best to use the old drafts (Framework and Core Protocol) as a starting point and modify to reflect where 802.17 is today. It will save us a lot of time specially if we're aiming for April 5 for first draft. Otherwise, we might want to push the dates a bit.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Regards,</DIV>
<DIV>Albert Herrera</DIV>
<DIV>TELUS National Systems</DIV>
<DIV><BR><BR><B><I>Glenn Parsons &lt;gparsons@nortel.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">
<META content="MS Exchange Server version 5.5.2658.2" name=Generator>
<P><FONT size=2>Folks,</FONT> </P>
<P><FONT size=2>The IPoRPR WG has been in hibernation for quite some time.&nbsp; Given the publication of IEEE 802.17 last year, it is time to shut down this WG...&nbsp; or recharter and do something.</FONT></P>
<P><FONT size=2>Assuming there is some interest in the latter, I have attached a revised charter proposal that our AD will be reviewing with the IESG shortly.</FONT></P>
<P><FONT size=2>Let us know if you have any comments.</FONT> </P>
<P><FONT size=2>Cheers,</FONT> </P>
<P><FONT size=2>Glenn Parsons&nbsp; </FONT><BR><FONT size=2>gparsons@nortel.com</FONT> </P><BR><BR><BR>
<P><FONT size=2></FONT> </P>
<P><FONT face=Arial color=#000000 size=2></FONT> <BR>IP over Resilient Packet Rings (iporpr)<BR><BR>Last Modified: 2005-02-11<BR><BR>Chair(s):<BR>Frank Kastenholz <FKASTENHOLZ@JUNIPER.NET><BR>Glenn Parsons <GPARSONS@NORTEL.COM><BR><BR>Internet Area Director(s):<BR>Thomas Narten <NARTEN@US.IBM.COM><BR>Margaret Wasserman <MARGARET@THINGMAGIC.COM><BR><BR>Internet Area Advisor:<BR>Thomas Narten <NARTEN@US.IBM.COM><BR><BR>Technical Advisor(s):<BR>Thomas Narten <NARTEN@US.IBM.COM><BR><BR>Mailing Lists:<BR>General Discussion: iporpr@ietf.org<BR>To Subscribe: iporpr-request@ietf.org<BR>In Body: subscribe iporpr<BR>Archive: http://www.ietf.org/mail-archive/web/iporpr/index.html<BR><BR>Description of Working Group:<BR><BR>Resilient Packet Rings (RPR), developed within the IEEE 802.17 RPR WG, provides substantial enhancements in both efficiency and flexibility over current bi-directional ring topologies. Benefits of resilient packet rings include spatial re-use (full utilization of both
 counter-rotating rings) while maintaining protection switching during media faults, as well as defined mechanisms for topology discovery, congestion control, and protection switching. Reference the IEEE 802.17 RPR WG at http://www.ieee802.org/17/ for further information. IEEE 802.17-2004 is currently published and work is in progress on bridging enhancements.<BR><BR>The IPORPR Working Group will produce two documents:<BR><BR>1) An IPORPR Framework that describes some of the features and<BR>characteristics of 802.17 RPR, and how they might be exploited<BR>by, e.g., IP or MPLS. For example, an RPR ring can be accessed<BR>in a number of ways: it can be viewed as a "dumb" LAN supporting<BR>traditional broadcast a la Ethernet (called "basic mode"), or its<BR>advanced features could be exploited.<BR><BR>2) An IPORPR definition of how to transport IP over 802.17 RPR in<BR>"basic mode". This document will cover encapsulation formats<BR>(e.g., IPv4/IPv6), how to perform address reso!
 lution
 (e.g., ARP/ND), IP<BR>multicast transmission, priority mapping to the RPR <BR>"serviceClass", etc.<BR><BR>There are no formal liaisons between the IPORPR working group and<BR>other standards bodies. However, cross participation is encouraged in the key RPR activities in these standards bodies:<BR>- IEEE 802.17 (http://www.ieee802.org/17/)<BR>- ITU-T SG15 Q9 (http://www.itu.int/ITU-T/studygroups/com15/sg15-q9.html)<BR><BR>Goals and Milestones:<BR>Apr 05 &nbsp;&nbsp; Publish draft Core IP-over-RPR specification <BR>May 05 &nbsp;&nbsp; Publish draft IP-over-802.17 Framework document. <BR>Jul 05 &nbsp;&nbsp; Submit final draft of Core protocol to the IESG for Proposed Standard Status. <BR>Aug 05 &nbsp;&nbsp; Submit final draft of Framework to the IESG for Informational Status. <BR><BR>_______________________________________________<BR>IPORPR mailing list<BR>IPORPR@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/iporpr<BR></P></BLOCKQUOTE>
--0-1783077310-1109647613=:15526--


--===============0049142884==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
IPORPR mailing list
IPORPR@ietf.org
https://www1.ietf.org/mailman/listinfo/iporpr

--===============0049142884==--



