IPoRPR comments
"Glenn Parsons" <[email protected]> Thu, 21 Jul 2005 18:30:25 -0400
| Newsgroups | gmane.ietf.iporpr |
|---|---|
| Message-ID | <085091CB2CA14E4B8B163FFC37C84E9D057BAAFA@zcarhxm0.corp.nortel.com> |
This is a multi-part message in MIME format. --===============1600942348== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C58E43.C43FEDFA" This is a multi-part message in MIME format. ------_=_NextPart_001_01C58E43.C43FEDFA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Folks, I reviewed the basic mode draft with the IEEE 802.17 WG today. Many = thanks to this group for their detailed review! Below I have included a summary of the comments that the group made on = the document. The plan is to incorporate these comments within the next version of the = draft -- along with the various other comments that I have acknowledged = on the mailing list. I would expect that a new version would be issued after the next IETF = meeting in August. Cheers, Glenn. Comments from IEEE 802.17 WG meeting: * add a description of basic mapping in a new Introduction section * change end of section 1.1: There is a TTL in the IEEE 802.17 frame headers. This TTL is used to = measure and limit lifetime of frames on a ring. * Delete in 1.1: There are fairness and bandwidth-management elements. =20 * Delete in 1.1: When the fault clears, the ring reverts to normal operation. * Change in 1.1: 'best' to default * Change in 1.1: any of several algorithms -> any algorithm * Change in 1.1: There are three service classes: Class A provides committed bandwidth = and low delay and jitter, class B has committed and excess bandwidth = components and bounded delay and jitter, and class C is best-effort. * 1.2.1: change to 'This may also be...' * 1.2.2 and throughout: change Ethernet type & Ethertype -> protocol = type * Remove period in 1.2.2 * 1.2.3: change: Class A traffic has precedence over class B and class C traffic at the = ingress to the ring and in transit. * Make 2.1.7 text the same as 2.1.9 * Split right column in Table 3 into mark_fe, serviceClass and text = description (e.g., EIR/CIR) * Delete 2.5 * Change: 2.6 Ringlet and Direction Selection -> 2.6 Ringlet Selection = -- and change in text * In 2.6 Delete: The advanced version of this specification may change = this. * 3.2: change 'class a0 & a1' to 'class a' * 5: delete=20 As with IPv6, the intent is to allow the IEEE 802.17 network to be = treated as a simple Ethernet LAN. * Modify table 4 as table 3 * Delete 6 * In 7, move last sentence to beginning. * Consider various editorial comments that will be forwarded to the = editor ------_=_NextPart_001_01C58E43.C43FEDFA Content-Type: text/html; charset="iso-8859-1" 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=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 6.5.7232.55"> <TITLE>IPoRPR comments</TITLE> </HEAD> <BODY> <!-- Converted from text/rtf format --> <P><FONT SIZE=3D2 FACE=3D"Arial">Folks,</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">I reviewed the basic mode draft with = the IEEE 802.17 WG today. Many thanks to this group for their = detailed review!</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">Below I have included a summary of the = comments that the group made on the document.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">The plan is to incorporate these = comments within the next version of the draft -- along with the various = other comments that I have acknowledged on the mailing list.</FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">I would expect that a new version would = be issued after the next IETF meeting in August.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">Cheers,</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Glenn.</FONT> </P> <BR> <P><U><B><FONT FACE=3D"Arial">Comments from IEEE 802.17 WG = meeting:</FONT></B></U> </P> <UL> <UL> <LI><FONT SIZE=3D2 FACE=3D"Arial">add a description of basic mapping in = a new Introduction section</FONT></LI> <LI><FONT SIZE=3D2 FACE=3D"Arial">change end of section 1.1:<BR> <SPAN LANG=3D"en"></SPAN></FONT><SPAN LANG=3D"en"><FONT = COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">There is a TTL in the IEEE = 802.17 frame headers. This TTL is used to measure and limit lifetime of = frames on a ring.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Delete in 1.1:<BR> There are fairness and bandwidth-management = elements. </FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Delete in 1.1:<BR> When the fault clears, the ring reverts to normal = operation.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Change in 1.1: ‘best’ to = default</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Change in 1.1: any of several algorithms -> any = algorithm</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Change in 1.1:</FONT><BR> </SPAN><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">There are three service classes: Class A provides = committed bandwidth and low delay and jitter, class B has committed and = excess bandwidth components and bounded delay and jitter, and class C is = best-effort.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">1.2.1: change to ‘This may also = be…’</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">1.2.2 and throughout: change Ethernet type & = Ethertype -> protocol type</FONT></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Remove period in 1.2.2</FONT></SPAN><SPAN = LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">1.2.3: change:<BR> </FONT></SPAN><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Class A traffic has precedence over class B and class C = traffic at the ingress to the ring and in transit.</FONT></SPAN><SPAN = LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Make 2.1.7 text the same as 2.1.9</FONT></SPAN><SPAN = LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Split right column in Table 3 into mark_fe, serviceClass = and text description (e.g., EIR/CIR)</FONT></SPAN><SPAN = LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Delete 2.5</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Change: 2.6=A0Ringlet and Direction Selection -> = 2.6=A0Ringlet Selection -- and change in text</FONT></SPAN><SPAN = LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">In 2.6 Delete: </FONT></SPAN><SPAN LANG=3D"en"> = <FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">The advanced version of = this specification may change this.</FONT></SPAN><SPAN = LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">3.2: change ‘class a0 & a1’ to = ‘class a’</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">5: delete<BR> As with IPv6, the intent is to allow the IEEE 802.17 network to be = treated as a simple Ethernet LAN.</FONT></SPAN><SPAN = LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Modify table 4 as table 3</FONT></SPAN><SPAN = LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Delete 6</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">In = 7, move last sentence to beginning.</FONT></SPAN><SPAN = LANG=3D"en-us"></SPAN></LI> <LI><SPAN LANG=3D"en"><FONT COLOR=3D"#000000" SIZE=3D2 = FACE=3D"Arial">Consider various editorial comments that will be = forwarded to the editor<BR> <BR> </FONT></SPAN><SPAN LANG=3D"en-us"></SPAN></LI> <BR> </UL></UL> </BODY> </HTML> ------_=_NextPart_001_01C58E43.C43FEDFA-- --===============1600942348== 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 --===============1600942348==--