RE: [RPRWG] IPoRPR initial draft
"Glenn Parsons" <[email protected]> Mon, 18 Jul 2005 12:37:57 -0400
| Newsgroups | gmane.ietf.iporpr |
|---|---|
| Message-ID | <085091CB2CA14E4B8B163FFC37C84E9D056ADBB4@zcarhxm0.corp.nortel.com> |
This is a multi-part message in MIME format. --===============0819150015== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C58BB7.0FF11B90" This is a multi-part message in MIME format. ------_=_NextPart_001_01C58BB7.0FF11B90 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Anoop, =20 On Table 3 we could not really fit the PHB in the ASCII table without making it look too squished, so it was left out. =20 On LSPs, do you simply want to note that mapping applies to E-LSPs? =20 And the security section is intentionally thick since we cannot say there are no risks. But perhaps the line you are looking for is the second sentence in item 4 which should be the closing paragraph of section 7. =20 Cheers, Glenn _____ =20 From: Ghanwani, Anoop [mailto:[email protected]]=20 Sent: Thursday, July 14, 2005 4:57 PM To: Parsons, Glenn [CAR:1A14:EXCH]; [email protected] Subject: RE: [RPRWG] IPoRPR initial draft Hi Glenn, Mark, =20 In Table 3, I think it would be useful to also have=20 the PHB name alongwith the DSCP since the DSCP values are hard to remember...e.g. 000000 (BE), xxxxxx (AF11) ,etc., in the first column of the table. =20 In Sec 5.1.1, I think a distinction needs to be made for E-LSP and L-LSP. With L-LSPs only the drop precedence is encoded in the EXP bits. =20 =20 I'm curious as to why the draft has such a detailed security considerations section even though by itself the draft doesn't introduce any new security concerns. At a minimum, I think a statement to that effect should=20 appear in the security section. =20 Anoop _____ =20 From: [email protected] [mailto:[email protected]] On Behalf Of Glenn Parsons Sent: Tuesday, July 12, 2005 6:16 PM To: [email protected] Subject: Re: [RPRWG] IPoRPR initial draft Thanks David, =20 We can fix most of these I think. =20 Some of them though (e.g., the sections with no section numbers) are part of the IETF front/back matter and cannot be changed (without changing their style). =20 Cheers, Glenn. _____ =20 From: David V James [mailto:[email protected]]=20 Sent: Tuesday, July 12, 2005 7:36 PM To: Parsons, Glenn [CAR:1A14:EXCH] Cc: [email protected] Subject: RE: [RPRWG] IPoRPR initial draft Glen, =20 I got of a few of the excessive capitalization, but I suspect not all. =20 The 802.3 environment seems very hazardous: everyone there seems to get a sticky caps key(:>). =20 Its on the attached pdf. Feel free to discuss, call me into the meeting, or forward as appropriate. =20 DVJ =20 David V. James 3180 South Ct Palo Alto, CA 94306 Home: +1.650.494.0926 +1.650.856.9801 Cell: +1.650.954.6906 Fax: +1.360.242.5508 Base: [email protected]=20 =20 -----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Glenn Parsons Sent: Tuesday, July 12, 2005 1:36 PM To: [email protected] Subject: [RPRWG] IPoRPR initial draft Folks,=20 The first draft of the IPoRPR basic mapping is attached.=20 This version is slightly different from the IETF officially posted version <draft-ietf-iporpr-basic-00.txt> -- there are some minor corrections to tables 2 & 3. As a result, I'd prefer the group reviews this version. Note that the primary review mechanism to submit comments to the IETF IPoRPR mailing list -- and you must be a member to post (and get past the spam filter :-). There is currently no plan for an IPoRPR WG meeting at IETF 63 in Paris. However, there is agenda time at the IEEE 802.17 meeting in San Francisco next week to discuss this draft. =20 Cheers,=20 Glenn=20 <<draft-ietf-iporpr-basic-00a.html>> <<draft-ietf-iporpr-basic-00a.txt>> ------_=_NextPart_001_01C58BB7.0FF11B90 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <TITLE>IPoRPR initial draft</TITLE> <META content=3D"MSHTML 6.00.2900.2668" name=3DGENERATOR></HEAD> <BODY> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D263004002-18072005>Anoop,</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D263004002-18072005></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D263004002-18072005>On Table 3 we could not really fit the PHB in = the ASCII=20 table without making it look too squished, so it was left=20 out.</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D263004002-18072005></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D263004002-18072005>On LSPs, do you simply want to note that = mapping=20 applies to E-LSPs?</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D263004002-18072005></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D263004002-18072005>And the security section is intentionally = thick since=20 we cannot say there are no risks. But perhaps the line you are = looking for=20 is the second sentence in item 4 which should be the closing paragraph = of=20 section 7.</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D263004002-18072005></SPAN></FONT> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D263004002-18072005>Cheers,</SPAN></FONT></DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D263004002-18072005>Glenn</SPAN></FONT></DIV><BR> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> Ghanwani, Anoop=20 [mailto:[email protected]] <BR><B>Sent:</B> Thursday, July 14, 2005 = 4:57=20 PM<BR><B>To:</B> Parsons, Glenn [CAR:1A14:EXCH];=20 [email protected]<BR><B>Subject:</B> RE: [RPRWG] IPoRPR = initial=20 draft<BR></FONT><BR></DIV> <DIV></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Hi Glenn, Mark,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>In Table 3, I think it would be useful to also = have=20 </FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>the PHB name alongwith the DSCP since=20 the</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>DSCP values are hard to = remember...e.g.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>000000 (BE), xxxxxx (AF11) ,etc., in the=20 first</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>column of the table.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>In Sec 5.1.1, I think a distinction needs to be = made</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>for E-LSP and L-LSP. With L-LSPs only the = drop</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>precedence is encoded in the EXP bits. =20 </FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>I'm curious as to why the draft has such a=20 detailed</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>security considerations section even though by=20 itself</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>the draft doesn't introduce any new security=20 concerns.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>At a minimum, I think a statement to that = effect should=20 </FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>appear in </FONT></SPAN><SPAN=20 class=3D559294420-14072005><FONT face=3DArial color=3D#0000ff = size=3D2>the security=20 section.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D559294420-14072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Anoop</FONT></SPAN></DIV><BR> <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> Tuesday, July 12, 2005 6:16 PM<BR><B>To:</B>=20 [email protected]<BR><B>Subject:</B> Re: [RPRWG] IPoRPR = initial=20 draft<BR></FONT><BR></DIV> <DIV></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D653471201-13072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Thanks David,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D653471201-13072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D653471201-13072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>We can fix most of these I = think.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D653471201-13072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D653471201-13072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Some of them though (e.g., the sections with no = section=20 numbers) are part of the IETF front/back matter and cannot be changed = (without=20 changing their style).</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D653471201-13072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D653471201-13072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Cheers,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D653471201-13072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Glenn.</FONT></SPAN></DIV><BR> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> David V James = [mailto:[email protected]]=20 <BR><B>Sent:</B> Tuesday, July 12, 2005 7:36 PM<BR><B>To:</B> Parsons, = Glenn=20 [CAR:1A14:EXCH]<BR><B>Cc:</B> = [email protected]<BR><B>Subject:</B>=20 RE: [RPRWG] IPoRPR initial draft<BR></FONT><BR></DIV> <DIV></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005>Glen,</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005>I got of a few of the excessive = capitalization, but I=20 suspect</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005>not all.</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005>The 802.3 environment seems very hazardous: = everyone=20 there seems</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005>to get a sticky caps = key(:>).</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005>Its on the attached pdf. Feel free to = discuss, call me=20 into the</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005>meeting, or forward as = appropriate.</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20 class=3D281473323-12072005>DVJ</SPAN></FONT></DIV> <DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT> </DIV> <P><FONT size=3D2>David V. James<BR>3180 South Ct<BR>Palo Alto, CA = 94306<BR>Home:=20 +1.650.494.0926<BR> = +1.650.856.9801<BR>Cell:=20 +1.650.954.6906<BR>Fax: +1.360.242.5508<BR>Base:=20 [email protected] <BR><BR> </FONT> </P> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px = solid; MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT = face=3DTahoma=20 size=3D2>-----Original Message-----<BR><B>From:</B> = [email protected]=20 [mailto:[email protected]]<B>On Behalf Of </B>Glenn=20 Parsons<BR><B>Sent:</B> Tuesday, July 12, 2005 1:36 PM<BR><B>To:</B>=20 [email protected]<BR><B>Subject:</B> [RPRWG] IPoRPR = initial=20 draft<BR><BR></FONT></DIV><!-- Converted from text/rtf format --> <P><FONT face=3DArial size=3D2>Folks,</FONT> </P> <P><FONT face=3DArial size=3D2>The first draft of the IPoRPR basic = mapping is=20 attached.</FONT> </P> <P><FONT face=3DArial size=3D2>This version is slightly different from = the IETF=20 officially posted version <draft-ietf-iporpr-basic-00.txt> -- = there are=20 some minor corrections to tables 2 & 3. As a result, I'd = prefer the=20 group reviews this version.</FONT></P> <P><FONT face=3DArial size=3D2>Note that the primary review mechanism = to submit=20 comments to the IETF IPoRPR mailing list -- and you must be a member = to post=20 (and get past the spam filter :-).</FONT></P> <P><FONT face=3DArial size=3D2>There is currently no plan for an = IPoRPR WG meeting=20 at IETF 63 in Paris. </FONT></P> <P><FONT face=3DArial size=3D2>However, there is agenda time at the = IEEE 802.17=20 meeting in San Francisco next week to discuss this draft. = </FONT></P> <P><FONT face=3DArial size=3D2>Cheers,</FONT> <BR><FONT face=3DArial=20 size=3D2>Glenn</FONT> </P><BR> <P><FONT face=3DArial color=3D#000000=20 size=3D2><<draft-ietf-iporpr-basic-00a.html>> </FONT><FONT = face=3DArial color=3D#000000=20 size=3D2><<draft-ietf-iporpr-basic-00a.txt>>=20 </FONT></P></BLOCKQUOTE></BODY></HTML> ------_=_NextPart_001_01C58BB7.0FF11B90-- --===============0819150015== 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 --===============0819150015==--