RE: Is DDP header requred?
"Pat Thaler" <[email protected]> Mon, 7 May 2007 18:53:49 -0700
| Newsgroups | gmane.ietf.rddp |
|---|---|
| Message-ID | <87AC500EEF9B9344B4A8D8A017C2F45537F236@NT-SJCA-0752.brcm.ad.broadcom.com> |
This is a multi-part message in MIME format. --===============0824041127== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C79113.BC5FD99F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C79113.BC5FD99F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable As far as I recall, we made providing the header a "SHOULD" to allow for extreme cases where ddp didn't have enough resources to save the header. I.e. if ddp used a shared resource to save bad headers and had multiple errors that exhausted that space. The RDMAP draft isn't specifying DDP so the "SHOULD" in DDP should take precidence.=20 =20 The YES in the header column in RDMAP can be understood as informative about the usual behavior (the SHOULD is normally followed) and not the equivalent of a MUST. =20 Pat ________________________________ From: bbr [mailto:[email protected]]=20 Sent: Monday, May 07, 2007 4:26 PM To: RDDP Subject: [rddp] Is DDP header requred? DDP and RDMAP appear to provide conflicting information as to whether or not a DDP header is required when DDP detects an invalid STAG. =20 Draft 07 of DDP in clause 7.1 states: =20 If the DDP layer detects any of the receive errors listed in this=20 section, it MUST cease placing the remainder of the DDP Segment and=20 report the error(s) to the ULP. The DDP layer SHOULD include in the=20 error report the DDP Header, the type of error, and the length of=20 the DDP segment, if available. =20 =20 Draft 07 or RDMAP in figure 10 for a DDP error places a "YES" in the column that identifies the DDP header as being required. =20 The question is "Does she or doesn't she".... Have to provide the DDP header? =20 Barry Reinhold (603) 868-8411 [email protected] <mailto:[email protected]>=20 =20 ------_=_NextPart_001_01C79113.BC5FD99F Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20 "urn:schemas-microsoft-com:vml" xmlns:o =3D=20 "urn:schemas-microsoft-com:office:office" xmlns:w =3D=20 "urn:schemas-microsoft-com:office:word" xmlns:m =3D=20 "http://schemas.microsoft.com/office/2004/12/omml"><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2900.3059" name=3DGENERATOR> <STYLE>@font-face { font-family: Cambria Math; } @font-face { font-family: Calibri; } @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; } P.MsoNormal { FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: = "Calibri","sans-serif" } LI.MsoNormal { FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: = "Calibri","sans-serif" } DIV.MsoNormal { FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: = "Calibri","sans-serif" } A:link { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } A:visited { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.EmailStyle17 { COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: = personal-compose } P.Default { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: = "Courier New"; mso-style-name: Default } LI.Default { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: = "Courier New"; mso-style-name: Default } DIV.Default { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: = "Courier New"; mso-style-name: Default } .MsoChpDefault { mso-style-type: export-only } DIV.Section1 { page: Section1 } </STYLE> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></HEAD> <BODY lang=3DEN-US vLink=3Dpurple link=3Dblue> <DIV><FONT face=3DArial color=3D#000080 size=3D2><SPAN = class=3D800404301-08052007>As far=20 as I recall, we made providing the header a "SHOULD" to allow for = extreme=20 cases where ddp didn't have enough resources to save the header. I.e. if = ddp=20 used a shared resource to save bad headers and had multiple errors that=20 exhausted that space. The RDMAP draft isn't specifying DDP so the = "SHOULD" in=20 DDP should take precidence. </SPAN></FONT></DIV> <DIV><FONT face=3DArial color=3D#000080 size=3D2><SPAN=20 class=3D800404301-08052007></SPAN></FONT> </DIV> <DIV><FONT face=3DArial color=3D#000080 size=3D2><SPAN = class=3D800404301-08052007>The=20 YES in the header column in RDMAP can be understood as informative about = the=20 usual behavior (the SHOULD is normally followed) and not the equivalent = of a=20 MUST.</SPAN></FONT></DIV> <DIV><FONT face=3DArial color=3D#000080 size=3D2><SPAN=20 class=3D800404301-08052007></SPAN></FONT> </DIV> <DIV><FONT face=3DArial color=3D#000080 size=3D2><SPAN=20 class=3D800404301-08052007>Pat</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> bbr = [mailto:[email protected]]=20 <BR><B>Sent:</B> Monday, May 07, 2007 4:26 PM<BR><B>To:</B>=20 RDDP<BR><B>Subject:</B> [rddp] Is DDP header = requred?<BR></FONT><BR></DIV> <DIV></DIV> <DIV class=3DSection1> <P class=3DMsoNormal>DDP and RDMAP appear to provide conflicting = information as to=20 whether or not a DDP header is required when DDP detects an invalid=20 STAG.<o:p></o:p></P> <P class=3DMsoNormal><o:p> </o:p></P> <P class=3DMsoNormal>Draft 07 of DDP in clause 7.1 = states:<o:p></o:p></P> <P class=3DMsoNormal><o:p> </o:p></P> <P class=3DDefault><SPAN style=3D"FONT-SIZE: 10pt">If the DDP layer = detects any of=20 the receive errors listed in this <o:p></o:p></SPAN></P> <P class=3DDefault><SPAN style=3D"FONT-SIZE: 10pt">section, it MUST = cease placing=20 the remainder of the DDP Segment and <o:p></o:p></SPAN></P> <P class=3DDefault><SPAN style=3D"FONT-SIZE: 10pt">report the error(s) = to the ULP.=20 The DDP layer SHOULD include in the <o:p></o:p></SPAN></P> <P class=3DDefault><SPAN style=3D"FONT-SIZE: 10pt">error report the DDP = Header, the=20 type of error, and the length of <o:p></o:p></SPAN></P> <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt">the DDP segment, if = available.=20 </SPAN> <o:p></o:p></P> <P class=3DMsoNormal><o:p> </o:p></P> <P class=3DMsoNormal>Draft 07 or RDMAP in figure 10 for a DDP error = places a “YES”=20 in the column that identifies the DDP header as being = required.<o:p></o:p></P> <P class=3DMsoNormal><o:p> </o:p></P> <P class=3DMsoNormal>The question is “Does she or = doesn’t she”…. Have to=20 provide the DDP header?<o:p></o:p></P> <P class=3DMsoNormal><o:p> </o:p></P> <P class=3DMsoNormal><SPAN=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'">Barry=20 Reinhold<o:p></o:p></SPAN></P> <P class=3DMsoNormal><SPAN=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New = Roman','serif'">(603) 868-8411<o:p></o:p></SPAN></P> <P class=3DMsoNormal><SPAN=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman','serif'"><A=20 href=3D"mailto:[email protected]"><SPAN=20 style=3D"COLOR: = blue">[email protected]</SPAN></A><o:p></o:p></SPAN></P> <P class=3DMsoNormal><o:p> </o:p></P></DIV></BODY></HTML> ------_=_NextPart_001_01C79113.BC5FD99F-- --===============0824041127== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ rddp mailing list [email protected] https://www1.ietf.org/mailman/listinfo/rddp --===============0824041127==--