Recharter IPoRPR WG
"Glenn Parsons" <[email protected]> Mon, 28 Feb 2005 18:29:20 -0500
| Newsgroups | gmane.ietf.iporpr |
|---|---|
| Message-ID | <085091CB2CA14E4B8B163FFC37C84E9D02931800@zcarhxm0.corp.nortel.com> |
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 [email protected] ------_=_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. Given the publication of IEEE 802.17 last year, it is time = to shut down this WG... 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 </FONT> <BR><FONT SIZE=3D2>[email protected]</FONT> </P> <BR> <BR> <BR> <P><FONT SIZE=3D2> </FONT> </P> <P><FONT FACE=3D"Arial" SIZE=3D2 COLOR=3D"#000000"></FONT> </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 IP over Resilient Packet Rings (iporpr) Last Modified: 2005-02-11 Chair(s): Frank Kastenholz <[email protected]> Glenn Parsons <[email protected]> Internet Area Director(s): Thomas Narten <[email protected]> Margaret Wasserman <[email protected]> Internet Area Advisor: Thomas Narten <[email protected]> Technical Advisor(s): Thomas Narten <[email protected]> Mailing Lists: General Discussion: [email protected] To Subscribe: [email protected] 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 _______________________________________________ IPORPR mailing list [email protected] https://www1.ietf.org/mailman/listinfo/iporpr ------_=_NextPart_000_01C51DED.5E091893--