RE: Recharter IPoRPR WG
"Glenn Parsons" <[email protected]> Mon, 14 Mar 2005 12:05:33 -0500
| Newsgroups | gmane.ietf.iporpr |
|---|---|
| Message-ID | <085091CB2CA14E4B8B163FFC37C84E9D029318BB@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. --===============0675816313== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C528B8.3BA70B37" 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_001_01C528B8.3BA70B37 Content-Type: text/plain Italo, Thanks for the review. IP and MPLS encapsulation over RPR are in charter -- though I can see that is not completely clear from the latest version of the charter. And the intent is coordination with all of ITU-T SG15 with Q9 being the coordination point as it has been in the past. Cheers, Glenn. -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Monday, March 14, 2005 8:16 AM To: Parsons, Glenn [CAR:1A14:EXCH] Cc: [email protected]; [email protected]; [email protected]; [email protected] Subject: RE: [IPORPR] Recharter IPoRPR WG Glenn, I think that the group should also cover the mapping of MPLS over RPR. Moreover, regarding ITU SG15 relationships, I think we need to include also Q.11/15 and Q.12/15 in addition to Q.9/15 because all of these three questions are currently considering RPR. Below you can find a proposed revised version of the "Description of Working Group". Best regards, Italo 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 and MPLS over 802.17 RPR in "basic mode". This document will cover encapsulation formats (e.g., IPv4/IPv6, MPLS), 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) - ITU-T SG15 Q11 (http://www.itu.int/ITU-T/studygroups/com15/sg15-q11.html) - ITU-T SG15 Q12 (http://www.itu.int/ITU-T/studygroups/com15/sg15-q12.html) -----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Glenn Parsons Sent: Tuesday, March 01, 2005 00:29 To: [email protected] Subject: [IPORPR] Recharter IPoRPR WG 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_01C528B8.3BA70B37 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>RE: [IPORPR] Recharter IPoRPR WG</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>Italo,</FONT> </P> <P><FONT SIZE=3D2>Thanks for the review.</FONT> </P> <P><FONT SIZE=3D2>IP and MPLS encapsulation over RPR are in charter -- = though I can see that is not completely clear from the latest version = of the charter.</FONT></P> <P><FONT SIZE=3D2>And the intent is coordination with all of ITU-T SG15 = with Q9 being the coordination point as it has been in the past.</FONT> </P> <P><FONT SIZE=3D2>Cheers,</FONT> <BR><FONT SIZE=3D2>Glenn.</FONT> </P> <P><FONT SIZE=3D2>-----Original Message-----</FONT> <BR><FONT SIZE=3D2>From: [email protected] [<A = HREF=3D"mailto:[email protected]">mailto:[email protected]</A>] = </FONT> <BR><FONT SIZE=3D2>Sent: Monday, March 14, 2005 8:16 AM</FONT> <BR><FONT SIZE=3D2>To: Parsons, Glenn [CAR:1A14:EXCH]</FONT> <BR><FONT SIZE=3D2>Cc: [email protected]; [email protected]; = [email protected]; [email protected]</FONT> <BR><FONT SIZE=3D2>Subject: RE: [IPORPR] Recharter IPoRPR WG</FONT> </P> <BR> <P><FONT SIZE=3D2>Glenn,</FONT> </P> <P><FONT SIZE=3D2>I think that the group should also cover the mapping = of MPLS over RPR.</FONT> </P> <P><FONT SIZE=3D2>Moreover, regarding ITU SG15 relationships, I think = we need to include also Q.11/15 and Q.12/15 in addition to Q.9/15 = because all of these three questions are currently considering = RPR.</FONT></P> <P><FONT SIZE=3D2>Below you can find a proposed revised version of the = "Description of Working Group".</FONT> </P> <P><FONT SIZE=3D2>Best regards, Italo</FONT> </P> <P><FONT SIZE=3D2>Description of Working Group:</FONT> </P> <P><FONT SIZE=3D2>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 <A = HREF=3D"http://www.ieee802.org/17/" = TARGET=3D"_blank">http://www.ieee802.org/17/</A> for further = information. IEEE 802.17-2004 is currently published and work is = in progress on bridging enhancements.</FONT></P> <P><FONT SIZE=3D2>The IPORPR Working Group will produce two = documents:</FONT> </P> <P><FONT SIZE=3D2> 1) An IPORPR Framework that describes = some of the features and</FONT> <BR><FONT SIZE=3D2> characteristics of = 802.17 RPR, and how they might be exploited</FONT> <BR><FONT SIZE=3D2> by, e.g., IP or MPLS. = For example, an RPR ring can be accessed</FONT> <BR><FONT SIZE=3D2> in a number of ways: = it can be viewed as a "dumb" LAN supporting</FONT> <BR><FONT SIZE=3D2> traditional broadcast = a la Ethernet (called "basic mode"), or its</FONT> <BR><FONT SIZE=3D2> advanced features = could be exploited.</FONT> </P> <P><FONT SIZE=3D2> 2) An IPORPR definition of how to = transport IP and MPLS over 802.17 RPR in</FONT> <BR><FONT SIZE=3D2> "basic = mode". This document will cover encapsulation formats</FONT> <BR><FONT SIZE=3D2> (e.g., IPv4/IPv6, = MPLS), how to perform address resolution (e.g., ARP/ND), IP</FONT> <BR><FONT SIZE=3D2> multicast = transmission, priority mapping to the RPR</FONT> <BR><FONT SIZE=3D2> = "serviceClass", etc.</FONT> </P> <P><FONT SIZE=3D2>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:</FONT></P> <P><FONT SIZE=3D2>- IEEE 802.17 (<A = HREF=3D"http://www.ieee802.org/17/" = TARGET=3D"_blank">http://www.ieee802.org/17/</A>)</FONT> <BR><FONT SIZE=3D2>- ITU-T SG15 Q9 (<A = HREF=3D"http://www.itu.int/ITU-T/studygroups/com15/sg15-q9.html" = TARGET=3D"_blank">http://www.itu.int/ITU-T/studygroups/com15/sg15-q9.htm= l</A>)</FONT> <BR><FONT SIZE=3D2>- ITU-T SG15 Q11 (<A = HREF=3D"http://www.itu.int/ITU-T/studygroups/com15/sg15-q11.html" = TARGET=3D"_blank">http://www.itu.int/ITU-T/studygroups/com15/sg15-q11.ht= ml</A>)</FONT> <BR><FONT SIZE=3D2>- ITU-T SG15 Q12 (<A = HREF=3D"http://www.itu.int/ITU-T/studygroups/com15/sg15-q12.html" = TARGET=3D"_blank">http://www.itu.int/ITU-T/studygroups/com15/sg15-q12.ht= ml</A>)</FONT> </P> <P><FONT SIZE=3D2>-----Original Message-----</FONT> <BR><FONT SIZE=3D2>From: [email protected] [<A = HREF=3D"mailto:[email protected]">mailto:[email protected]</= A>]On Behalf Of Glenn Parsons</FONT> <BR><FONT SIZE=3D2>Sent: Tuesday, March 01, 2005 00:29</FONT> <BR><FONT SIZE=3D2>To: [email protected]</FONT> <BR><FONT SIZE=3D2>Subject: [IPORPR] Recharter IPoRPR WG</FONT> </P> <BR> <P><FONT SIZE=3D2>Folks,</FONT> <BR><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. 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]</FONT></P> <BR> <BR> <BR> <BR> <BR> <BR> <BR> </BODY> </HTML> ------_=_NextPart_001_01C528B8.3BA70B37-- --===============0675816313== 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 --===============0675816313==--