RE: [RPRWG] IPoRPR initial draft
"Glenn Parsons" <[email protected]> Tue, 19 Jul 2005 15:49:42 -0400
| Newsgroups | gmane.ietf.iporpr |
|---|---|
| Message-ID | <085091CB2CA14E4B8B163FFC37C84E9D0574930E@zcarhxm0.corp.nortel.com> |
This is a multi-part message in MIME format. --===============1840862314== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C58C9B.01F4C282" This is a multi-part message in MIME format. ------_=_NextPart_001_01C58C9B.01F4C282 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable George, =20 Thanks for the comments. =20 We need to clean up the identification of optional & mandatory in section 1.2 as you suggest. =20 On the DSCP & EXP mapping to service classes, the intent of this document is to define the default mapping. Vendors can do what they want -- but should use the mapping in this document if they want to be 'compliant and interoperable'. We'll add some text to this effect. =20 On ringlet selection, there is no MPLS control of the direction in this document per the charter. To progress this, the plan is to lay out the reasons for doing this in the next document. =20 Cheers, Glenn. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of George Suwala (gsuwala) Sent: Tuesday, July 19, 2005 2:30 PM To: [email protected] Subject: Re: [RPRWG] IPoRPR initial draft Glenn, Marc, Good and easy to read document. Some comments: - 1.2 IEEE 802.17 MAC Service I would specify which 3 parameters are mandatory - Table 3 DSCP Mapping I would add a comment that this is a default mapping, but not the only one possible, vendors could choose to add configuration commands to re-map differently=20 - Table 4 EXP mapping Same comment as for Table 3 - 3.2. Should we say more about control of the ringlet selection? For example a mechanism for MPLS TE backup tunnel (or any other diverse routing path) placement through mapping into the opposite ringlet to the one MAC would select? thanks =20 George ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Ghanwani, Anoop Sent: Monday, July 18, 2005 10:41 AM To: [email protected] Subject: Re: [RPRWG] IPoRPR initial draft =09 =09 =20 Hi Glenn, =20 I think it would really help readability if you can find a way to put the PHB names in...just maybe in parenthesis or even on the line following the DSCP. All that is needed is something like: =20 110000 - EF xxxxxxx - AF11, etc. =20 Otherwise, the reader would be forced to have a copy of=20 the DiffServ RFC handy in order to understand this table. =20 Yes, a clarification with respect to what the table applies to is needed. In fact, you might need a second table to talk about L-LSPs since they encode 3 levels of drop precedence in the EXP bits for AF which then=20 need to be mapped to the 2-levels supported in 802.17. =20 I think it would be better to reword the security section as follows. "This draft does not introduce any new security concerns for IEEE 802.17 networks. Some of the existing vulnerabilities of IEEE 802.17 networks include: ...". =20 Anoop =09 =09 ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Glenn Parsons Sent: Monday, July 18, 2005 9:38 AM To: [email protected] Subject: Re: [RPRWG] IPoRPR initial draft =09 =09 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 ________________________________ 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 =09 =09 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 =09 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 ________________________________ 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 =09 =09 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. ________________________________ 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 =09 =09 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 =09 =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 =09 =09 Folks,=20 The first draft of the IPoRPR basic mapping is attached. 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. =20 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>>=20 ------_=_NextPart_001_01C58C9B.01F4C282 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>IPoRPR initial draft</TITLE> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2900.2668" name=3DGENERATOR></HEAD> <BODY> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>George,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Thanks for the comments.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>We need to clean up the identification of = optional &=20 mandatory in section 1.2 as you suggest.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>On the DSCP & EXP mapping to service = classes, the=20 intent of this document is to define the default mapping. Vendors = can do=20 what they want -- but should use the mapping in this document if they = want=20 to be 'compliant and interoperable'. We'll add some text to = this=20 effect.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>On ringlet selection, there is no MPLS control = of the=20 direction in this document per the charter. To progress this, the = plan is=20 to lay out the reasons for doing this in the next = document.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Cheers,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D490404319-19072005><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> [email protected]=20 [mailto:[email protected]] <B>On Behalf Of </B>George Suwala=20 (gsuwala)<BR><B>Sent:</B> Tuesday, July 19, 2005 2:30 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> <P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN = class=3D910221318-19072005>Glenn,=20 Marc,</SPAN></FONT></P> <P><FONT size=3D+0><FONT face=3DArial><FONT color=3D#0000ff><FONT = size=3D2><SPAN=20 class=3D910221318-19072005>Good and easy to read document. </SPAN>Some=20 comments:</FONT></FONT></FONT></FONT></P> <P><FONT face=3DArial color=3D#0000ff size=3D2>- 1.2 IEEE 802.17 MAC=20 Service</FONT></P> <P><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20 class=3D910221318-19072005>I would specify </SPAN> which 3 = parameters are=20 mandatory</FONT></FONT></FONT></P> <P><FONT face=3DArial color=3D#0000ff size=3D2>- Table 3 DSCP = Mapping</FONT></P> <P><FONT face=3DArial color=3D#0000ff size=3D2>I would add a comment = that this is a=20 default mapping, but not the only one possible, vendors could choose to = add=20 configuration commands to re-map differently </FONT></P> <P><FONT face=3DArial color=3D#0000ff size=3D2>- Table 4 EXP = mapping</FONT></P> <P><FONT face=3DArial color=3D#0000ff size=3D2>Same comment as for Table = 3</FONT></P> <P><SPAN class=3D910221318-19072005><FONT face=3DArial color=3D#0000ff = size=3D2>- 3.2.=20 </FONT></SPAN><SPAN class=3D910221318-19072005><FONT face=3DArial = color=3D#0000ff=20 size=3D2>Should we say more about control of the ringlet selection? For = example a=20 mechanism for MPLS TE backup tunnel (or any other diverse routing path)=20 placement through mapping into the opposite ringlet to the one MAC would = select?</FONT></SPAN></P></DIV> <DIV><SPAN class=3D910221318-19072005></SPAN><FONT face=3DArial><FONT=20 color=3D#0000ff><FONT size=3D2>thanks</FONT></FONT></FONT></DIV> <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT=20 size=3D2></FONT></FONT></FONT> </DIV> <DIV><FONT size=3D+0><FONT size=3D+0><FONT face=3DArial><FONT = color=3D#0000ff><FONT=20 size=3D2>G<SPAN=20 class=3D910221318-19072005>eorge</SPAN></FONT></FONT></FONT></FONT></FONT= ></DIV> <DIV><BR></DIV> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px = solid; 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>Ghanwani,=20 Anoop<BR><B>Sent:</B> Monday, July 18, 2005 10:41 AM<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=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Hi Glenn,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>I think it would really help readability if = you can find=20 a</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>way to put the PHB names in...just maybe in=20 parenthesis</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>or even on the line following the DSCP. = All that=20 is</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>needed is something like:</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN = class=3D776492617-18072005></SPAN><!--StartFragment --><SPAN=20 class=3D776492617-18072005><FONT face=3DArial color=3D#0000ff = size=3D2>110000 -=20 EF</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>xxxxxxx - AF11, etc.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Otherwise, the reader would be forced to have = a copy of=20 </FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>the DiffServ </FONT></SPAN><SPAN=20 class=3D776492617-18072005><FONT face=3DArial color=3D#0000ff = size=3D2>RFC handy in=20 order to understand this table.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Yes, a clarification with respect to what the = table</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>applies to is needed. In fact, you = might need a=20 second</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>table to talk about L-LSPs since they = encode 3=20 levels</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>of drop precedence in the EXP bits for AF = which then=20 </FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>need to be mapped to the 2-levels supported = in=20 802.17.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>I think it would be better to reword the = security=20 section</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>as follows.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>"This draft does not introduce any new = security=20 concerns</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>for IEEE 802.17 networks. Some of the = existing=20 vulnerabilities</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>of IEEE 802.17 networks include:=20 ...".</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D776492617-18072005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Anoop</FONT></SPAN></DIV><FONT face=3DArial = color=3D#0000ff=20 size=3D2></FONT><FONT face=3DArial color=3D#0000ff = size=3D2></FONT><FONT face=3DArial=20 color=3D#0000ff size=3D2></FONT><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> Monday, July 18, 2005 9:38 AM<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><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=20 ASCII 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=20 for 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=20 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=20 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=20 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=20 me 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=20 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=20 94306<BR>Home: +1.650.494.0926<BR> =20 +1.650.856.9801<BR>Cell: +1.650.954.6906<BR>Fax: =20 +1.360.242.5508<BR>Base: [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> = [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=20 are some minor corrections to tables 2 & 3. As a result, = I'd=20 prefer the 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=20 meeting 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 = size=3D2>Glenn</FONT> </P><BR> <P><FONT face=3DArial color=3D#000000=20 size=3D2><<draft-ietf-iporpr-basic-00a.html>> = </FONT><FONT=20 face=3DArial color=3D#000000=20 size=3D2><<draft-ietf-iporpr-basic-00a.txt>>=20 </FONT></P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML> ------_=_NextPart_001_01C58C9B.01F4C282-- --===============1840862314== 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 --===============1840862314==--