RE: Recharter IPoRPR WG
"Albert Herrera" <[email protected]> Mon, 14 Mar 2005 22:11:15 -0500
| Newsgroups | gmane.ietf.iporpr |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============1576088314== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5290C.A63A5D88" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5290C.A63A5D88 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Glenn, =20 I know we're encouraging cross participation between the standards = bodies but we really need a free and easy flow of information between = IPORPR, IEEE 802.17 and ITU-T SG15 on established and developing = specifications specially for those working towards RFCs within the IETF. = I know we casually discussed this a while back but we don't have a mechanism nor an = official notice from the other standards bodies as to how we are to = facilitate this. =20 We have to address this before starting work on the drafts. =20 Thanks, Albert =20 Albert Herrera TELUS National Systems =20 =20 ________________________________ From: [email protected] [mailto:[email protected]] On = Behalf Of Glenn Parsons Sent: Monday, March 14, 2005 12:06 PM To: [email protected] Cc: [email protected]; [email protected]; [email protected]; = [email protected] Subject: RE: [IPORPR] Recharter IPoRPR WG =09 =09 Italo,=20 Thanks for the review.=20 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.=20 Cheers,=20 Glenn.=20 -----Original Message-----=20 From: [email protected] [mailto:[email protected]]=20 Sent: Monday, March 14, 2005 8:16 AM=20 To: Parsons, Glenn [CAR:1A14:EXCH]=20 Cc: [email protected]; [email protected]; [email protected]; = [email protected]=20 Subject: RE: [IPORPR] Recharter IPoRPR WG=20 Glenn,=20 I think that the group should also cover the mapping of MPLS over RPR.=20 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".=20 Best regards, Italo=20 Description of Working Group:=20 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:=20 1) An IPORPR Framework that describes some of the features and=20 characteristics of 802.17 RPR, and how they might be exploited=20 by, e.g., IP or MPLS. For example, an RPR ring can be accessed=20 in a number of ways: it can be viewed as a "dumb" LAN supporting=20 traditional broadcast a la Ethernet (called "basic mode"), or its = advanced features could be exploited.=20 2) An IPORPR definition of how to transport IP and MPLS over 802.17 = RPR in=20 "basic mode". This document will cover encapsulation formats=20 (e.g., IPv4/IPv6, MPLS), how to perform address resolution (e.g., = ARP/ND), IP=20 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/)=20 - ITU-T SG15 Q9 = (http://www.itu.int/ITU-T/studygroups/com15/sg15-q9.html)=20 - ITU-T SG15 Q11 = (http://www.itu.int/ITU-T/studygroups/com15/sg15-q11.html)=20 - ITU-T SG15 Q12 = (http://www.itu.int/ITU-T/studygroups/com15/sg15-q12.html)=20 -----Original Message-----=20 From: [email protected] [mailto:[email protected]]On Behalf = Of Glenn Parsons=20 Sent: Tuesday, March 01, 2005 00:29=20 To: [email protected]=20 Subject: [IPORPR] Recharter IPoRPR WG=20 Folks,=20 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_01C5290C.A63A5D88 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>RE: [IPORPR] Recharter IPoRPR WG</TITLE> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2800.1491" name=3DGENERATOR></HEAD> <BODY> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005>Glenn,</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005>I know we're encouraging cross participation = between=20 the standards bodies but we really need</SPAN></FONT><FONT face=3DArial=20 color=3D#0000ff size=3D2><SPAN class=3D588265302-15032005> a free = and=20 easy flow of information between IPORPR, IEEE 802.17 and ITU-T = SG15 on=20 established and developing specifications specially for those working = towards=20 RFCs within the IETF. I know we casually discussed this a while back but = we=20 don't have a mechanism nor an official notice from the other standards = bodies as=20 to how we are to facilitate this.</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005>We have to address this before starting work = on=20 the drafts.</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005>Thanks,</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005>Albert</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005>Albert Herrera</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005>TELUS National Systems</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D588265302-15032005> </SPAN></FONT></DIV><BR> <BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> [email protected]=20 [mailto:[email protected]] <B>On Behalf Of </B>Glenn=20 Parsons<BR><B>Sent:</B> Monday, March 14, 2005 12:06 PM<BR><B>To:</B>=20 [email protected]<BR><B>Cc:</B> [email protected]; [email protected];=20 [email protected]; [email protected]<BR><B>Subject:</B> RE: [IPORPR] = Recharter=20 IPoRPR WG<BR></FONT><BR></DIV> <DIV></DIV> <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=20 can see that is not completely clear from the latest version of the=20 charter.</FONT></P> <P><FONT size=3D2>And the intent is coordination with all of ITU-T = SG15 with Q9=20 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:=20 [email protected] [<A=20 = href=3D"mailto:[email protected]">mailto:[email protected]</A>]=20 </FONT><BR><FONT size=3D2>Sent: Monday, March 14, 2005 8:16 AM</FONT> = <BR><FONT=20 size=3D2>To: Parsons, Glenn [CAR:1A14:EXCH]</FONT> <BR><FONT = size=3D2>Cc:=20 [email protected]; [email protected]; [email protected]; = [email protected]</FONT>=20 <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=20 over RPR.</FONT> </P> <P><FONT size=3D2>Moreover, regarding ITU SG15 relationships, I think = we need to=20 include also Q.11/15 and Q.12/15 in addition to Q.9/15 because all of = these=20 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=20 RPR WG, provides substantial enhancements in both efficiency and = flexibility=20 over current bi-directional ring topologies. Benefits of resilient = packet=20 rings include spatial re-use (full utilization of both = counter-rotating rings)=20 while maintaining protection switching during media faults, as well as = defined=20 mechanisms for topology discovery, congestion control, and protection=20 switching. Reference the IEEE 802.17 RPR WG at <A=20 href=3D"http://www.ieee802.org/17/" = target=3D_blank>http://www.ieee802.org/17/</A>=20 for further information. IEEE 802.17-2004 is currently published = and=20 work is in progress on bridging enhancements.</FONT></P> <P><FONT size=3D2>The IPORPR Working Group will produce two = documents:</FONT>=20 </P> <P><FONT size=3D2> 1) An IPORPR Framework that describes = some of the=20 features and</FONT> <BR><FONT size=3D2> =20 characteristics of 802.17 RPR, and how they might be exploited</FONT>=20 <BR><FONT size=3D2> by, e.g., IP or = MPLS. For=20 example, an RPR ring can be accessed</FONT> <BR><FONT=20 size=3D2> in a number of ways: it can be = viewed as=20 a "dumb" LAN supporting</FONT> <BR><FONT = size=3D2> =20 traditional broadcast a la Ethernet (called "basic mode"), or = its</FONT>=20 <BR><FONT size=3D2> advanced features = could be=20 exploited.</FONT> </P> <P><FONT size=3D2> 2) An IPORPR definition of how to = transport IP=20 and MPLS over 802.17 RPR in</FONT> <BR><FONT=20 size=3D2> "basic mode". This document = will cover=20 encapsulation formats</FONT> <BR><FONT = size=3D2> =20 (e.g., IPv4/IPv6, MPLS), how to perform address resolution (e.g., = ARP/ND),=20 IP</FONT> <BR><FONT size=3D2> multicast=20 transmission, priority mapping to the RPR</FONT> <BR><FONT=20 size=3D2> "serviceClass", etc.</FONT> = </P> <P><FONT size=3D2>There are no formal liaisons between the IPORPR = working group=20 and other standards bodies. However, cross participation is = encouraged=20 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/"=20 target=3D_blank>http://www.ieee802.org/17/</A>)</FONT> <BR><FONT = size=3D2>- ITU-T=20 SG15 Q9 (<A = href=3D"http://www.itu.int/ITU-T/studygroups/com15/sg15-q9.html"=20 = target=3D_blank>http://www.itu.int/ITU-T/studygroups/com15/sg15-q9.html</= A>)</FONT>=20 <BR><FONT size=3D2>- ITU-T SG15 Q11 (<A=20 href=3D"http://www.itu.int/ITU-T/studygroups/com15/sg15-q11.html"=20 = target=3D_blank>http://www.itu.int/ITU-T/studygroups/com15/sg15-q11.html<= /A>)</FONT>=20 <BR><FONT size=3D2>- ITU-T SG15 Q12 (<A=20 href=3D"http://www.itu.int/ITU-T/studygroups/com15/sg15-q12.html"=20 = target=3D_blank>http://www.itu.int/ITU-T/studygroups/com15/sg15-q12.html<= /A>)</FONT>=20 </P> <P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT = size=3D2>From:=20 [email protected] [<A=20 = href=3D"mailto:[email protected]">mailto:[email protected]</A= >]On=20 Behalf Of Glenn Parsons</FONT> <BR><FONT size=3D2>Sent: Tuesday, March = 01, 2005=20 00:29</FONT> <BR><FONT size=3D2>To: [email protected]</FONT> <BR><FONT=20 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=20 hibernation for quite some time. Given the publication of IEEE = 802.17=20 last year, it is time to shut down this WG... or recharter and = do=20 something. Assuming there is some interest in the latter, I have = attached a=20 revised charter proposal that our AD will be reviewing with the IESG = shortly.=20 Let us know if you have any comments. Cheers, Glenn Parsons=20 = [email protected]</FONT></P><BR><BR><BR><BR><BR><BR><BR></BLOCKQUOTE></= BODY></HTML> ------_=_NextPart_001_01C5290C.A63A5D88-- --===============1576088314== 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 --===============1576088314==--