From rddp-bounces@ietf.org  Tue Apr  5 13:54:22 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12664
	for <rddp-web-archive@ietf.org>; Tue, 5 Apr 2005 13:54:22 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIsO3-0002Un-6M
	for rddp-web-archive@ietf.org; Tue, 05 Apr 2005 14:02:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIsCz-0006er-Mq; Tue, 05 Apr 2005 13:51:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIsCy-0006em-KG
	for rddp@megatron.ietf.org; Tue, 05 Apr 2005 13:51:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12374
	for <rddp@ietf.org>; Tue, 5 Apr 2005 13:51:18 -0400 (EDT)
Received: from fmr16.intel.com ([192.55.52.70] helo=fmsfmr006.fm.intel.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIsL7-0002Mj-Dh
	for rddp@ietf.org; Tue, 05 Apr 2005 13:59:50 -0400
Received: from fmsfmr101.fm.intel.com (fmsfmr101.fm.intel.com [10.1.192.59])
	by fmsfmr006.fm.intel.com (8.12.10/8.12.10/d: major-outer.mc,
	v 1.1 2004/09/17 17:50:56 root Exp $) with ESMTP id j35HpCPl027237
	for <rddp@ietf.org>; Tue, 5 Apr 2005 17:51:12 GMT
Received: from fmsmsxvs042.fm.intel.com (fmsmsxvs042.fm.intel.com
	[132.233.42.128])
	by fmsfmr101.fm.intel.com (8.12.10/8.12.10/d: major-inner.mc,
	v 1.2 2004/09/17 18:05:01 root Exp $) with SMTP id j35HpCU7021421
	for <rddp@ietf.org>; Tue, 5 Apr 2005 17:51:12 GMT
Received: from fmsmsx332.amr.corp.intel.com ([132.233.42.148])
	by fmsmsxvs042.fm.intel.com (SAVSMTP 3.1.7.47) with SMTP id
	M2005040510511129460
	for <rddp@ietf.org>; Tue, 05 Apr 2005 10:51:11 -0700
Received: from fmsmsx402.amr.corp.intel.com ([132.233.42.200]) by
	fmsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 5 Apr 2005 10:51:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 5 Apr 2005 10:51:10 -0700
Message-ID: <6315617889C99D4BA7C14687DEC8DB4E0AAA628B@fmsmsx402.amr.corp.intel.com>
Thread-Topic: Last call comments on MPA draft
Thread-Index: AcU6CA0IKFeKMqjdSK6xlNGi0PjLeQ==
From: "Shah, Hemal" <hemal.shah@intel.com>
To: <rddp@ietf.org>
X-OriginalArrivalTime: 05 Apr 2005 17:51:11.0764 (UTC)
	FILETIME=[0DEBE540:01C53A08]
X-Scanned-By: MIMEDefang 2.44
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 08868c2bcdb53bddcb7cc7e7cf96b038
Subject: [rddp] Last call comments on MPA draft
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1009903712=="
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 04b84659b2acb599bee006e63124a606

This is a multi-part message in MIME format.

--===============1009903712==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C53A08.0DB85183"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C53A08.0DB85183
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

MPA authors,

=20

I am a little bit late for the last call comments (by 12 hours). So, my
apologies for that! In any case, below are my comments on
draft-ietf-rddp-mpa-02.txt:

=20

1.       Section 1.2, Page 7: Bullet 3 and Bullet 4 use terms "DDP data"
and "DDP data chunks". These are not defined terms. They should be
replaced with "DDP Segments" that is defined in the DDP spec.

2.       Section 1.2, Page 7: Bullet 6 refers to ULPDU_Length that is
not defined at this point in the spec. Suggest using "MPA header"
instead of "ULPDU_Length" here. Also, after PAD add the following "(if
any)".

3.       Section 1.2, Page 8: Figure 1 says "IP etc." at the lowest
layer. Suggest removing "etc." from the text as rddp protocols are
designed for IP networks so the lowest layer in Fig 1 is "IP".

4.       Section 2, Page 10: FPDU Alignment and Header Alignment
definition say "TCP segment begins with an FPDU". TCP segment includes
TCP header and TCP payload, so TCP segment always begins with TCP
header. Suggest replacing text "TCP segment begins with an FPDU" with
"TCP segment payload begins with an FPDU".

5.       Section 2, Page 10: MPA-aware TCP definition last line says
"...TCP segments that begin with an FPDU". Suggest replacing it with
"... TCP segments with the payloads that begin with an FPDU."

6.       Section 2, Page 10: MPA definition says "Marker-based ULP PDU
Aligned Framing for TCP protocol". This is not consistent with the draft
title. Suggest to use " MPA - Marker PDU Aligned Framing for TCP" for
the first sentence.

7.       Section 3.1.1, Page 12, first paragraph: This section talks
about the TCP transmit side. The last line in the first paragraph ends
with ".... the DDP segments (FPDUs) posted for transmission.". Suggest
rephrasing the last part to "... FPDUs containing DDP Segments passed
for transmission."

8.       Section 3.1.1, page 12, last paragraph, first sentence ends
".... TCP will use 1460 octet segments in creating FPDUs." TCP does not
create FPDUs, it is MPA that creates the FPDUs. Suggest rephrasing the
end of the sentence.

9.       Section 4, page 14, last paragraph: Last sentence say "The
16-bit "ULPDU_Length" field is large enough to support the largest IP
datagram for IPv4 or IPv6." ULPDU_Length supports FPDUs not IP
datagrams. Suggest rephrasing the last sentence to "The 16-bit
ULPDU_Length field is large enough to support the largest ULPDU that can
fit in the largest IP datagram for IPv4 and IPv6."

10.   Section 4, Page 15: CRC definition need to have a reference to
CRC32C algorithm when it is first used in the paragraph.

11.   Section 4.1, page 15, last paragraph: This paragraph is vague in
terms of that it does not say where the marker is. Suggest the following
rephrasing " FPDUPTR: The FPDU pointer is a relative pointer, 16-bits
long, interpreted as an unsigned integer, that indicates the number of
octets from the "ULPDU_Length" field of the FPDU that contains the
marker to the first octet of the entire marker."=20

12.   Section 5.2, page 20: Figure 5 uses hexadecimal every where except
for the size of Send Data. Suggest "Send Data (0x18 octets of zeros)".
Use "0x18" instead of "24".

13.   Section 5.3.2, page 23: When a marker falls between two FPDUs,
then is it considered in the FPDU size calculation or not? My belief is
it is not considered in the FPDU size. The specification neither says
that nor clarifies that. I believe this section should specify the FPDU
size calculation for that case.

14.   Section 5.4, page 24: This section seems to suggest that CRC has
to be valid for detecting FPDU start using one of the methods described
in 1, 2, or 3. If the CRC is turned off, then which one of these methods
should be used to detect the start of the FPDUs? Do all of them apply or
a sub-set of them apply? The spec does not specify how to detect start
of FPDUs when the CRC is turned off. If all the methods apply when the
CRC is turned off, then add a note saying "There is no requirement to
have valid CRCs for detecting the start of FPDUs using the above methods
when the CRC is turned off."=20

15.   Section 6.1, page 27: The rules for MPA connection startup phase
should go after the definition of "MPA Request frame" and "MPA Reply
Frame". The reason is the rules described use the fields of the MPA
request and reply frames and these fields are defined after. Suggest
moving section 6.1.1 before the rules.

16.   Section 6.1.1: I think we need to add a note here to say "When
markers are not enabled, then the MPA SHOULD NOT enable DDP to recover
out-of-order segments." Currently, the spec does not say that when the
markers are not enabled, then out-of-order segments are not placed.

17.   Section 6.1.1, M bit description: Last sentence in this paragraph
needs rewording. Suggest "When both "MPA Request Frame" and "MPA Reply
Frame" have M bit set to 1, then the markers MUST be added by both
peers."

=20

=20

Hemal =20


------_=_NextPart_001_01C53A08.0DB85183
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:271253772;
	mso-list-type:hybrid;
	mso-list-template-ids:-1118665222 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1
	{mso-list-id:436481642;
	mso-list-type:hybrid;
	mso-list-template-ids:-1904201428 67698703 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-tab-stop:.25in;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>MPA authors,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I am a little bit late for the last call comments (by =
12
hours). So, my apologies for that! In any case, below are my comments on
draft-ietf-rddp-mpa-02.txt:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>1.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 1.2,
Page 7: Bullet 3 and Bullet 4 use terms &#8220;DDP data&#8221; and =
&#8220;DDP
data chunks&#8221;. These are not defined terms. They should be replaced =
with &#8220;DDP
Segments&#8221; that is defined in the DDP =
spec.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>2.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 1.2,
Page 7: Bullet 6 refers to ULPDU_Length that is not defined at this =
point in
the spec. Suggest using &#8220;MPA header&#8221; instead of =
&#8220;ULPDU_Length&#8221;
here. Also, after PAD add the following &#8220;(if =
any)&#8221;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>3.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 1.2,
Page 8: Figure 1 says &#8220;IP etc.&#8221; at the lowest layer. Suggest
removing &#8220;etc.&#8221; from the text as rddp protocols are designed =
for IP
networks so the lowest layer in Fig 1 is =
&#8220;IP&#8221;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>4.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 2, Page
10: FPDU Alignment and Header Alignment definition say &#8220;TCP =
segment
begins with an FPDU&#8221;. TCP segment includes TCP header and TCP =
payload, so
TCP segment always begins with TCP header. Suggest replacing text =
&#8220;TCP
segment begins with an FPDU&#8221; with &#8220;TCP segment payload =
begins with
an FPDU&#8221;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>5.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 2, Page
10: MPA-aware TCP definition last line says &#8220;&#8230;TCP segments =
that
begin with an FPDU&#8221;. Suggest replacing it with &#8220;&#8230; TCP
segments with the payloads that begin with an =
FPDU.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>6.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 2, Page
10: MPA definition says &#8220;Marker-based ULP PDU Aligned Framing for =
TCP
protocol&#8221;. This is not consistent with the draft title. Suggest to =
use &#8220;
MPA &#8211; Marker PDU Aligned Framing for TCP&#8221; for the first =
sentence.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>7.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 3.1.1,
Page 12, first paragraph: This section talks about the TCP transmit =
side. The
last line in the first paragraph ends with &#8220;&#8230;. the DDP =
segments
(FPDUs) posted for transmission.&#8221;. Suggest rephrasing the last =
part to &#8220;&#8230;
FPDUs containing DDP Segments passed for =
transmission.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>8.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 3.1.1,
page 12, last paragraph, first sentence ends &#8220;&#8230;. TCP will =
use 1460
octet segments in creating FPDUs.&#8221; TCP does not create FPDUs, it =
is MPA
that creates the FPDUs. Suggest rephrasing the end of the =
sentence.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>9.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 4,
page 14, last paragraph: Last sentence say &#8220;The 16-bit =
&#8220;ULPDU_Length&#8221;
field is large enough to support the largest IP datagram for IPv4 or =
IPv6.&#8221;
ULPDU_Length supports FPDUs not IP datagrams. Suggest rephrasing the =
last
sentence to &#8220;The 16-bit ULPDU_Length field is large enough to =
support the
largest ULPDU that can fit in the largest IP datagram for IPv4 and =
IPv6.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>10.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 4, Page
15: CRC definition need to have a reference to CRC32C algorithm when it =
is
first used in the paragraph.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>11.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 4.1,
page 15, last paragraph: This paragraph is vague in terms of that it =
does not
say where the marker is. Suggest the following rephrasing &#8220; =
FPDUPTR: The
FPDU pointer is a relative pointer, 16-bits long, interpreted as an =
unsigned
integer, that indicates the number of octets from the =
&#8220;ULPDU_Length&#8221;
field of the FPDU that contains the marker to the first octet of the =
entire
marker.&#8221; <o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>12.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 5.2,
page 20: Figure 5 uses hexadecimal every where except for the size of =
Send Data.
Suggest &#8220;Send Data (0x18 octets of zeros)&#8221;. Use =
&#8220;0x18&#8221;
instead of &#8220;24&#8221;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>13.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section
5.3.2, page 23: When a marker falls between two FPDUs, then is it =
considered in
the FPDU size calculation or not? My belief is it is not considered in =
the FPDU
size. The specification neither says that nor clarifies that. I believe =
this
section should specify the FPDU size calculation for that =
case.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>14.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 5.4,
page 24: This section seems to suggest that CRC has to be valid for =
detecting FPDU
start using one of the methods described in 1, 2, or 3. If the CRC is =
turned
off, then which one of these methods should be used to detect the start =
of the
FPDUs? Do all of them apply or a sub-set of them apply? The spec does =
not
specify how to detect start of FPDUs when the CRC is turned off. If all =
the
methods apply when the CRC is turned off, then add a note saying =
&#8220;There
is no requirement to have valid CRCs for detecting the start of FPDUs =
using the
above methods when the CRC is turned off.&#8221; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>15.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 6.1,
page 27: The rules for MPA connection startup phase should go after the
definition of &#8220;MPA Request frame&#8221; and &#8220;MPA Reply =
Frame&#8221;.
The reason is the rules described use the fields of the MPA request and =
reply
frames and these fields are defined after. Suggest moving section 6.1.1 =
before
the rules.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>16.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section
6.1.1: I think we need to add a note here to say &#8220;When markers are =
not
enabled, then the MPA SHOULD NOT enable DDP to recover out-of-order =
segments.&#8221;
Currently, the spec does not say that when the markers are not enabled, =
then
out-of-order segments are not placed.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>17.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section
6.1.1, M bit description: Last sentence in this paragraph needs =
rewording.
Suggest &#8220;When both &#8220;MPA Request Frame&#8221; and &#8220;MPA =
Reply Frame&#8221;
have M bit set to 1, then the markers MUST be added by both =
peers.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hemal &nbsp;<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C53A08.0DB85183--


--===============1009903712==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp

--===============1009903712==--



From rddp-bounces@ietf.org  Tue Apr  5 14:19:24 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15255
	for <rddp-web-archive@ietf.org>; Tue, 5 Apr 2005 14:19:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIsmI-0003SQ-9s
	for rddp-web-archive@ietf.org; Tue, 05 Apr 2005 14:27:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIsav-0001vj-4t; Tue, 05 Apr 2005 14:16:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIsau-0001ve-Li
	for rddp@megatron.ietf.org; Tue, 05 Apr 2005 14:16:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14907
	for <rddp@ietf.org>; Tue, 5 Apr 2005 14:16:06 -0400 (EDT)
Received: from [67.118.4.34] (helo=fiona.siliquent.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIsj5-0003Id-Ue
	for rddp@ietf.org; Tue, 05 Apr 2005 14:24:36 -0400
Content-class: urn:content-classes:message
Subject: RE: [rddp] Last call comments on MPA draft
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 5 Apr 2005 11:15:56 -0700
Message-ID: <8508251A6FC08A489844A94261D3693A03944C@fiona.siliquent.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Thread-Topic: [rddp] Last call comments on MPA draft
Thread-Index: AcU6CA0IKFeKMqjdSK6xlNGi0PjLeQAAMHMg
From: "Caitlin Bestler" <caitlinb@siliquent.com>
To: "Shah, Hemal" <hemal.shah@intel.com>, <rddp@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: quoted-printable
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable

Hemal Shah wrote:

14.   Section 5.4, page 24: This section seems to suggest that CRC has
to be valid for detecting FPDU start using one of the methods described
in 1, 2, or 3. If the CRC is turned off, then which one of these methods
should be used to detect the start of the FPDUs? Do all of them apply or
a sub-set of them apply? The spec does not specify how to detect start
of
FPDUs when the CRC is turned off. If all the methods apply when the CRC
is turned off, then add a note saying "There is no requirement to have
valid CRCs for detecting the start of FPDUs using the above methods when
the CRC is turned off."=20


[caitlin]
CRC is disabled only when equivalent protections are available.
Therefore
in this type of context the CRC *is* valid. In no CRC mode the CRC is
*always*
valid, and the FPDU is always valid. If that were not true then CRC
would
not have been disabled.
[/caitlin]

=09
16.   Section 6.1.1: I think we need to add a note here to say
"When markers are not enabled, then the MPA SHOULD NOT enable
DDP to recover out-of-order segments." Currently, the spec does
not say that when the markers are not enabled, then out-of-order
segments are not placed.

[caitlin]
I believe the draft is already clear that out-of-order segments
cannot be delivered to the DDP layer unless there are unambiguous
indicators that it is indeed a valid MPA frame. Merely looking like
one is not enough, because there is nothing to say that the payload
of a DDP Segment could not be a valid MPA frame.

Without markers there is only *one* way to determine that an
out-of-order segment has the starting point of an MPA frame.
You need for CRCs to be disabled *and* to have received the
header of the *prior* MPA frame, but not it's tail. If CRCs
are enabled, then the MPA header is not validated and you
do not know, for certain, how long the MPA frame is. The
discussion on finding iSCSI PDUs is very applicable. Except
that MPA Frames that span multiple TCP segments are very
rare and in fact something that explicitly SHOULD be avoided.
The same tricks for finding iSCSI PDUs without periodic=20
marker insertion are *technically* viable for finding
MPA frames with markers disabled. But it is just as
complex with virtually zero chance of producing any
benefit.

I do not believe that an IETF SHOULD is required to guide=20
implementers into not wasting code space looking for=20
optimizations that have virtually zero benefits.

But  since the burden is entirely on the implementation
there is no real justification for telling them that
they SHOULD NOT do this particular  activity, because
it is only their effort that they are wasting. I don't
see any adverse network impact should someone actually
attempt this extreme example of heroic MPA frame
identification.

[/caitlin]

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp


From rddp-bounces@ietf.org  Wed Apr  6 02:41:16 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06135
	for <rddp-web-archive@ietf.org>; Wed, 6 Apr 2005 02:41:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJ4MK-0000Yh-A7
	for rddp-web-archive@ietf.org; Wed, 06 Apr 2005 02:49:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJ4CE-00075N-8T; Wed, 06 Apr 2005 02:39:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJ4CA-0006w3-17
	for rddp@megatron.ietf.org; Wed, 06 Apr 2005 02:39:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06090
	for <rddp@ietf.org>; Wed, 6 Apr 2005 02:39:20 -0400 (EDT)
Received: from fmr13.intel.com ([192.55.52.67] helo=fmsfmr001.fm.intel.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJ4KR-0000W0-VR
	for rddp@ietf.org; Wed, 06 Apr 2005 02:47:56 -0400
Received: from fmsfmr100.fm.intel.com (fmsfmr100.fm.intel.com [10.1.192.58])
	by fmsfmr001.fm.intel.com (8.12.10/8.12.10/d: major-outer.mc,
	v 1.1 2004/09/17 17:50:56 root Exp $) with ESMTP id j366dBxv023832
	for <rddp@ietf.org>; Wed, 6 Apr 2005 06:39:11 GMT
Received: from fmsmsxvs040.fm.intel.com (fmsmsxvs040.fm.intel.com
	[132.233.42.124])
	by fmsfmr100.fm.intel.com (8.12.10/8.12.10/d: major-inner.mc,
	v 1.2 2004/09/17 18:05:01 root Exp $) with SMTP id j366dB2Y031849
	for <rddp@ietf.org>; Wed, 6 Apr 2005 06:39:11 GMT
Received: from fmsmsx332.amr.corp.intel.com ([132.233.42.148])
	by fmsmsxvs040.fm.intel.com (SAVSMTP 3.1.7.47) with SMTP id
	M2005040523391110292
	for <rddp@ietf.org>; Tue, 05 Apr 2005 23:39:11 -0700
Received: from fmsmsx402.amr.corp.intel.com ([132.233.42.200]) by
	fmsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 5 Apr 2005 23:39:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 5 Apr 2005 23:39:09 -0700
Message-ID: <6315617889C99D4BA7C14687DEC8DB4E0AADAE7A@fmsmsx402.amr.corp.intel.com>
Thread-Topic: Last call comments on SCTP RDMA/DDP Adaptation draft
Thread-Index: AcU6c1ZxT6Egmt4PT9G5s1L8g6FtuA==
From: "Shah, Hemal" <hemal.shah@intel.com>
To: <rddp@ietf.org>
X-OriginalArrivalTime: 06 Apr 2005 06:39:11.0207 (UTC)
	FILETIME=[5768E770:01C53A73]
X-Scanned-By: MIMEDefang 2.44
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f5c1164b9029aa0dd842007e530e24ad
Subject: [rddp] Last call comments on SCTP RDMA/DDP Adaptation draft
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0924987357=="
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 089da5e32269fece1072c9ff54523f20

This is a multi-part message in MIME format.

--===============0924987357==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C53A73.57259DD1"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C53A73.57259DD1
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

SCTP RDMA/DDP Adaptation draft authors,

=20

Below are my comments on draft-ietf-rddp-sctp-01.txt:

=20

1.       Section 2.1, page 5, first paragraph: The last sentence is not
clear on whether the mix traffic is allowed on a single stream
association or not. Suggest rephrasing the sentence to "An application
that needs to mix DDP and non-DDP traffic must use different stream
associations for the DDP traffic and non-DDP traffic."

2.       Section 2.2, page 5, second paragraph, third line: grammatical
correction. Sentence should be "DDP Segments are used for the messages
sent between DDP endpoints."

3.       Section 2.2: The spec does not explicitly state 1:1 mapping of
SCTP payload data chunk and DDP Segment. Suggest adding the following
"Each DDP Segment is exactly contained in one SCTP payload data chunk
with the payload protocol identifier 0x00000001."=20

4.       Section 2.2.1: This section does not say how DDP-SSN is
incremented. Suggest adding the following text "DDP-SSN is increased by
one (modulo 65536) with each DDP message submitted to the SCTP layer."

5.       Section 2.1: Need to add a requirement that DDP-SSN for the DDP
Segments of a DDP message should be same. Suggest adding the text: "The
DDP-SSN field of the Payload Data Chunks of the DDP segments of a DDP
Message MUST be the same."

6.       Section 2.2.1: This section does not mention whether DDP-SSN is
passed to DDP layer or not. For delivery, it is important. Suggest
adding the following text "The adaptation layer passes DDP-SSN to the
DDP layer for the in-order delivery of DDP Messages."

7.       Section 2.2.1: Who maintains DDP-SSN, adaptation layer or DDP
layer? Please clarify it in this section.

8.       Suggest renaming section 2.2.2 to "DDP Segment Payload Data
Chunk".

9.       Suggest renaming section 2.2.3 to "DDP Stream Session Control
Payload Data Chunk".

10.   Section 2.2.3: This section does not say how the length of the
private data is derived. Suggest adding the text "The length of private
data is derived from the length of Payload Data Chunk."

11.   Section 6, third paragraph: This sentence combines two conditions:
MUST NOT with an exception case. It is little bit confusing. Suggest
splitting the sentence into two sentences: "SCTP Data Chunk
fragmentation MUST NOT be used for the cases where IP fragmentation is
not required. SCTP data chunk fragmentation MAY be used to avoid IP
fragmentation."

12.   Section 6, fourth paragraph: Is there any specific formula for
deriving the maximum DDP segment size based on the theoretical maximum
size of the SCTP Data Chunk?

13.   Section 7, third paragraph: in the end says "Typical ULP flow
control will exclusively deal with tagged messages,..". Replace "tagged
messages" with "DDP Messages".

14.   Section 7: Is there any requirement on the adaptation layer on
passing DDP-SSN to DDP layer? If yes, then please specify ("The
adaptation layer SHOULD pass DDP-SSN along with the DDP Segment to the
DDP layer."). If no, then please clarify.

=20

Hemal =20


------_=_NextPart_001_01C53A73.57259DD1
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1512837177;
	mso-list-type:hybrid;
	mso-list-template-ids:-176549400 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:.25in;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>SCTP RDMA/DDP Adaptation draft =
authors,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Below are my comments on =
draft-ietf-rddp-sctp-01.txt:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>1.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 2.1,
page 5, first paragraph: The last sentence is not clear on whether the =
mix
traffic is allowed on a single stream association or not. Suggest =
rephrasing
the sentence to &#8220;An application that needs to mix DDP and non-DDP =
traffic
must use different stream associations for the DDP traffic and non-DDP =
traffic.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>2.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 2.2,
page 5, second paragraph, third line: grammatical correction. Sentence =
should
be &#8220;DDP Segments are used for the messages sent between DDP =
endpoints.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>3.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 2.2:
The spec does not explicitly state 1:1 mapping of SCTP payload data =
chunk and
DDP Segment. Suggest adding the following &#8220;Each DDP Segment is =
exactly
contained in one SCTP payload data chunk with the payload protocol =
identifier
0x00000001.&#8221; <o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>4.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section
2.2.1: This section does not say how DDP-SSN is incremented. Suggest =
adding the
following text &#8220;DDP-SSN is increased by one (modulo 65536) with =
each DDP
message submitted to the SCTP layer.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>5.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 2.1:
Need to add a requirement that DDP-SSN for the DDP Segments of a DDP =
message
should be same. Suggest adding the text: &#8220;The DDP-SSN field of the =
Payload
Data Chunks of the DDP segments of a DDP Message MUST be the =
same.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>6.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section
2.2.1: This section does not mention whether DDP-SSN is passed to DDP =
layer or
not. For delivery, it is important. Suggest adding the following text =
&#8220;The
adaptation layer passes DDP-SSN to the DDP layer for the in-order =
delivery of DDP
Messages.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>7.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section
2.2.1: Who maintains DDP-SSN, adaptation layer or DDP layer? Please =
clarify it
in this section.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>8.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Suggest
renaming section 2.2.2 to &#8220;DDP Segment Payload Data =
Chunk&#8221;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>9.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Suggest
renaming section 2.2.3 to &#8220;DDP Stream Session Control Payload Data =
Chunk&#8221;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>10.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section
2.2.3: This section does not say how the length of the private data is =
derived.
Suggest adding the text &#8220;The length of private data is derived =
from the
length of Payload Data Chunk.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>11.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 6,
third paragraph: This sentence combines two conditions: MUST NOT with an =
exception
case. It is little bit confusing. Suggest splitting the sentence into =
two
sentences: &#8220;SCTP Data Chunk fragmentation MUST NOT be used for the =
cases where
IP fragmentation is not required. SCTP data chunk fragmentation MAY be =
used to
avoid IP fragmentation.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>12.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 6,
fourth paragraph: Is there any specific formula for deriving the maximum =
DDP
segment size based on the theoretical maximum size of the SCTP Data =
Chunk?<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>13.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 7,
third paragraph: in the end says &#8220;Typical ULP flow control will
exclusively deal with tagged messages,..&#8221;. Replace &#8220;tagged =
messages&#8221;
with &#8220;DDP Messages&#8221;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.25in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>14.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Section 7: Is
there any requirement on the adaptation layer on passing DDP-SSN to DDP =
layer? If
yes, then please specify (&#8220;The adaptation layer SHOULD pass =
DDP-SSN along
with the DDP Segment to the DDP layer.&#8221;). If no, then please =
clarify.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hemal &nbsp;<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C53A73.57259DD1--


--===============0924987357==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp

--===============0924987357==--



From rddp-bounces@ietf.org  Wed Apr  6 13:02:40 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05084
	for <rddp-web-archive@ietf.org>; Wed, 6 Apr 2005 13:02:40 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJE3n-0006Lt-1D
	for rddp-web-archive@ietf.org; Wed, 06 Apr 2005 13:11:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJDtk-0001UW-BX; Wed, 06 Apr 2005 13:01:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJDth-0001TS-55
	for rddp@megatron.ietf.org; Wed, 06 Apr 2005 13:00:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04952
	for <rddp@ietf.org>; Wed, 6 Apr 2005 13:00:53 -0400 (EDT)
Received: from [67.118.4.34] (helo=fiona.siliquent.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJE23-0006IQ-98
	for rddp@ietf.org; Wed, 06 Apr 2005 13:09:37 -0400
Content-class: urn:content-classes:message
Subject: RE: [rddp] Last call comments on SCTP RDMA/DDP Adaptation draft
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 6 Apr 2005 10:00:43 -0700
Message-ID: <8508251A6FC08A489844A94261D3693A039486@fiona.siliquent.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Thread-Topic: [rddp] Last call comments on SCTP RDMA/DDP Adaptation draft
Thread-Index: AcU6c1ZxT6Egmt4PT9G5s1L8g6FtuAAU9fCw
From: "Caitlin Bestler" <caitlinb@siliquent.com>
To: "Shah, Hemal" <hemal.shah@intel.com>, <rddp@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: quoted-printable
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: quoted-printable

Hemal,
=20
Thanks for a thorough proofreading.
=20
Most suggestions are noted, and I will update accordingly
after all changes are collected.
=20
There are a few exceptions, noted in-line below.
=20
> 4.       Section 2.2.1: This section does not say how DDP-SSN
>          is incremented. Suggest adding the following text
>          "DDP-SSN is increased by one (modulo 65536) with each
>          DDP message submitted to the SCTP layer."

It is once per SCTP Data Chunk, which would be once per DDP Segment.
That is clear in the definitons section, but I agree that repeating
that definition in section 2.2.1 would improve the document.

> 5.       Section 2.1: Need to add a requirement that DDP-SSN for
>          the DDP Segments of a DDP message should be same. Suggest
>          adding the text: "The DDP-SSN field of the Payload Data
>          Chunks of the DDP segments of a DDP Message MUST be the
same."

The DDP-SSN numbers DDP Segments/SCTP Data Chunks, not messages.

One of its purposes is to allow easy determination when all prior
segments have been received for normal DDP ordering rules. When the
DDP Segment is untagged and has an L bit, it generates a completion.
But only after all prior segments have been received. The difference
with the SCTP adaptation versus MPA is that the SCTP adaptation uses
a 16 bit sequence number with 1 tick per segment rather than a 32 bit
TCP sequence number that has n ticks per segment.

> 6.       Section 2.2.1: This section does not mention whether DDP-SSN
>          is passed to DDP layer or not. For delivery, it is important.
>          Suggest adding the following text "The adaptation layer
passes
>          DDP-SSN to the DDP layer for the in-order delivery of DDP
Messages."=20
	=20

The DDP specification already requires that "ordering information" be
supplied
from the LLP, so no explicit statement is really necessary. But if one
were
added it should be more along the lines of "The adaptation layer passes
DDP-SSN
to the DDP layer as the required LLP ordering information to allow the
DDP layer
to sequence DDP segments properly."=20

This avoids suggesting that the DDP Segments are delivered to the DDP
layer in order.

> 7.       Section 2.2.1: Who maintains DDP-SSN, adaptation layer or
>          DDP layer? Please clarify it in this section.=20

	=20

I'll think about the best clarification. The DDP-SSN is fully equivalent
of
the TCP sequence number, it is the property of the LLP. It is also
basically
equivalent to what the SCTP Stream Sequence Number would have been had
ordered
delivery been used. Unfortunately using ordered chunks would have
undesirable
effects, such as causing many SCTP stacks to hold Data Chunks until they
were
in order. Use of unordered data chunks reduces the complexity of the
required
SCTP functionality and guarantees the SCTP stack will forward the data
chunks
to the adaptation layer as promptly as possible.=20

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp


From rddp-bounces@ietf.org  Wed Apr  6 20:34:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25845
	for <rddp-web-archive@ietf.org>; Wed, 6 Apr 2005 20:34:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJL73-0003UM-PB
	for rddp-web-archive@ietf.org; Wed, 06 Apr 2005 20:43:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJKy2-0000fE-C7; Wed, 06 Apr 2005 20:33:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJKy0-0000f9-3r
	for rddp@megatron.ietf.org; Wed, 06 Apr 2005 20:33:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25814
	for <rddp@ietf.org>; Wed, 6 Apr 2005 20:33:50 -0400 (EDT)
From: Black_David@emc.com
Received: from mailhub.lss.emc.com ([168.159.2.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJL6S-0003Tq-55
	for rddp@ietf.org; Wed, 06 Apr 2005 20:42:36 -0400
Received: from mxic2.corp.emc.com (mxic2.corp.emc.com [128.221.12.9])
	by mailhub.lss.emc.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id
	j370XmZd022209
	for <rddp@ietf.org>; Wed, 6 Apr 2005 20:33:49 -0400 (EDT)
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <FTSZLBWW>; Wed, 6 Apr 2005 20:33:46 -0400
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA0D6174E6@corpmx14.corp.emc.com>
To: rddp@ietf.org
Date: Wed, 6 Apr 2005 20:33:44 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.0.3.0,
	Antispam-Data: 2005.4.6.16
X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, NO_REAL_NAME 0,
	__C230066_P5 0, __CHILD_PORN_NOT_1 0, __CT 0, __CT_TEXT_PLAIN 0,
	__HAS_MSGID 0, __HAS_X_MAILER 0, __IMS_MSGID 0, __IMS_MUA 0,
	__MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: Black_David@emc.com
Subject: [rddp] 
	WG Last Call *Concluded*: Applicability, SCTP Adaptation, MPA
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3

I have now completed my review of these drafts.  I have a bunch
of editorial comments that will be sent to the authors, but here
are the technical ones:

-- draft-ietf-rddp-mpa-02.txt

p.11: "An implementation may accept out of order segments, SACK them
[RFC2018], and pass them to DDP when the reception of the segments
needed to fill in the gaps arrive."  This sentence appears to be wrong -
a SACK'ed segment should be eligible for immediate placement without
waiting for gaps to fill.  I suggest clarifying text to distinguish
placement from delivery, as it's ambiguous which of these "pass them"
was intended to mean.

p. 24: "In certain rare situations, the EMSS may shrink to very small
sizes.  If this occurs, the MPA on TCP sender MUST NOT shrink the MULPDU
below 128 octets and is not required to follow the segmentation rules in
Section 5.3 MPA on TCP Sender Segmentation on page 22."  "very small
sizes" needs to be explicitly specified.  "not required" should be UPPER
CASE.

-- draft-ietf-rddp-applicability-02.txt

No technical comments.

-- draft-ietf-rddp-sctp-01.txt

Section 2.1 - Explain where the type value of 0xC006 comes from.

Section 9 - Tell IANA which registries these values go in.

The WG Last Call on these drafts is now concluded.  I believe that my
comments and Hemal's can be addressed without another WG Last Call.

Draft authors should prepare new versions of the drafts that address
these comments - please double-check with the commenters (Hemal and
myself) that the comments have been successfully addressed.  These
versions of the draft also need to be checked against the ID Checklist
on the IETF web site (e.g., the RDDP SCTP draft currently has one
too many authors).  I will work with our ADs to resolve the issue
of whether MPA is to become an informational vs. standards track RFC
when this next revision of the MPA draft is available.

Thanks,
--David
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------

> -----Original Message-----
> From: rddp-bounces@ietf.org [mailto:rddp-bounces@ietf.org] On 
> Behalf Of Black_David@emc.com
> Sent: Tuesday, March 15, 2005 6:28 PM
> To: rddp@ietf.org
> Subject: [rddp] WG Last Call: Applicability, SCTP Adaptation, MPA
> Importance: High
> 
> The previous WG Last Call went so well that it's time
> to do it again ... so, I hereby announce the RDDP Working
> Group Last Call on the following three drafts:
> 
> Applicability of Remote Direct Memory Access Protocol
>    (RDMA) and Direct Data Placement (DDP)
> 	(draft-ietf-rddp-applicability-02.txt)
> Stream Control Transmission Protocol (SCTP) Remote Direct
>    Memory Access (RDMA) Direct Data Placement (DDP)
>    Adaptation
> 	(draft-ietf-rddp-sctp-01.txt)
> Marker PDU Aligned Framing for TCP Specification 
> 	(draft-ietf-rddp-mpa-02.txt)
> 
> This WG Last Call will run until 11:59pm Eastern Time (US)
> on Monday, April 4th (I was thinking about having it end
> on April 1st [April Fools Day] and decided to pass on that
> opportunity).  The SCTP Adaptation draft is intended to
> become a standards track RFC, the Applicability draft is
> intended to become an informational RFC, and whether the
> MPA draft is to become standards track vs. informational
> will be determined after the conclusion of this WG Last Call.
> 
> Technical comments need to be posted to this mailing list.
> Editorial comments may be sent directly to the primary
> draft authors:
> 
> - Applicability: Caitlin Bestler <cait -at- asomi.com>
> - SCTP Adaptation: Randall R. Stewart <rrs -at- cisco.com> AND
> 		Caitlin Bestler <cait -at- asomi.com>
> - RDMAP: Paul R. Culley <paul.culley -at- hp.com>
> 
> Please copy me (as WG chair - David Black <black_david -at-
> emc.com>) on any editorial comments, just in case something
> initially thought to be editorial turns out to have technical
> content.  The intent is to resolve WG Last Call issues on
> the mailing list, but an RDDP WG meeting in Paris is a
> possibility if it is needed to resolve issues.
> 
> There are other drafts linked to the WG's web page:
> 
> http://www.ietf.org/html.charters/rddp-charter.html
> 
> that may be of interest or relevance in reviewing the three
> drafts for this WG Last Call.
> 
> Many thanks to all whose hard work has gotten us this far,
> --David (RDDP WG chair)
> 
> ----------------------------------------------------
> David L. Black, Senior Technologist
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> black_david@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
> 
> _______________________________________________
> rddp mailing list
> rddp@ietf.org
> https://www1.ietf.org/mailman/listinfo/rddp
> 

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp


From rddp-bounces@ietf.org  Wed Apr 13 16:15:35 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01167
	for <rddp-web-archive@ietf.org>; Wed, 13 Apr 2005 16:15:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLoQm-0002J9-BV
	for rddp-web-archive@ietf.org; Wed, 13 Apr 2005 16:25:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLnqI-0005If-6d; Wed, 13 Apr 2005 15:48:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLnqE-0005I6-FR; Wed, 13 Apr 2005 15:48:02 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27343;
	Wed, 13 Apr 2005 15:48:00 -0400 (EDT)
Message-Id: <200504131948.PAA27343@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 13 Apr 2005 15:48:00 -0400
Cc: rddp@ietf.org
Subject: [rddp] I-D ACTION:draft-ietf-rddp-security-07.txt
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Remote Direct Data Placement Working Group of the IETF.

	Title		: DDP/RDMAP Security
	Author(s)	: J. Pinkerton, et al.
	Filename	: draft-ietf-rddp-security-07.txt
	Pages		: 53
	Date		: 2005-4-13
	
This document analyzes security issues around implementation and 
   use of the Direct Data Placement Protocol(DDP) and Remote Direct 
   Memory Access Protocol (RDMAP). It first defines an architectural 
   model for an RDMA Network Interface Card (RNIC), which can 
   implement DDP or RDMAP and DDP. The document reviews various 
   attacks against the resources defined in the architectural model 
   and the countermeasures that can be used to protect the system. 
   Attacks are grouped into spoofing, tampering, information 
   disclosure, denial of service, and elevation of privilege. 
   Finally, the document concludes with a summary of security 
   services for DDP and RDMAP, such as IPsec.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rddp-security-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rddp-security-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rddp-security-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-4-13162058.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rddp-security-07.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-rddp-security-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-13162058.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp

--NextPart--





From rddp-bounces@ietf.org  Thu Apr 14 20:26:05 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15021
	for <rddp-web-archive@ietf.org>; Thu, 14 Apr 2005 20:26:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMEoy-00037y-KF
	for rddp-web-archive@ietf.org; Thu, 14 Apr 2005 20:36:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMEdi-0007Cj-8N; Thu, 14 Apr 2005 20:24:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMEdf-0007AO-1J
	for rddp@megatron.ietf.org; Thu, 14 Apr 2005 20:24:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14892
	for <rddp@ietf.org>; Thu, 14 Apr 2005 20:24:48 -0400 (EDT)
Received: from [64.186.171.138] (helo=stargate.chelsio.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMEnj-000341-5l
	for rddp@ietf.org; Thu, 14 Apr 2005 20:35:16 -0400
Received: from YOGI.asicdesigners.com (yogi.asicdesigners.com [10.192.160.7])
	by stargate.chelsio.com (8.12.5/8.12.5) with SMTP id j3F0Od6H027630
	for <rddp@ietf.org>; Thu, 14 Apr 2005 17:24:39 -0700
Received: yogi.asicdesigners.com 10.192.160.7 from 10.192.161.85 10.192.161.85
	via HTTP with MS-WebStorage 6.0.6249
Received: from orion by yogi.asicdesigners.com; 14 Apr 2005 17:24:39 -0700
From: Patricio Kaplan <pkaplan@chelsio.com>
To: RDDP <rddp@ietf.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1113524678.418.28.camel@orion.asicdesigners.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Thu, 14 Apr 2005 17:24:38 -0700
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Subject: [rddp] rdmap-03 spec clarification
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit

draft-ietf-rddp-rdmap-03.txt, section 6.1:

"Bits 32-63; Invalidate STag. However, this field is only valid
 for Send with Invalidate and Send with Solicited Event and
 Invalidate Messages (see Figure 4 RDMA Usage of DDP Fields).
 For Send, Send with Solicited Event, RDMA Read Request, and
 Terminate, the Invalidate STag field MUST be set to zero on
 transmit and ignored by the receiver."

Could someone tell me if "ignored by the receiver" means 

1) If it is not zero the receiver MUST NOT generate an error
2) The receiver MUST CHECK that the STag is zero but in case it is 
   it does nothing with it.

thanks in advance,

-patricio kaplan

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp


From rddp-bounces@ietf.org  Fri Apr 15 08:41:13 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26289
	for <rddp-web-archive@ietf.org>; Fri, 15 Apr 2005 08:41:13 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMQIV-0004b1-07
	for rddp-web-archive@ietf.org; Fri, 15 Apr 2005 08:51:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMQ2T-0005gb-Ds; Fri, 15 Apr 2005 08:35:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMQ2R-0005dK-U4
	for rddp@megatron.ietf.org; Fri, 15 Apr 2005 08:35:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25819
	for <rddp@ietf.org>; Fri, 15 Apr 2005 08:35:10 -0400 (EDT)
Received: from ccerelbas01.cce.hp.com ([161.114.21.104])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMQCc-0004Mh-TL
	for rddp@ietf.org; Fri, 15 Apr 2005 08:45:44 -0400
Received: from cceexg11.americas.cpqcorp.net (cceexg11.americas.cpqcorp.net
	[16.81.1.59])
	by ccerelbas01.cce.hp.com (Postfix) with ESMTP id C5A7C2000145;
	Fri, 15 Apr 2005 07:34:58 -0500 (CDT)
Received: from cceexc18.americas.cpqcorp.net ([16.81.1.4]) by
	cceexg11.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 15 Apr 2005 07:34:57 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rddp] rdmap-03 spec clarification
Date: Fri, 15 Apr 2005 07:34:57 -0500
Message-ID: <4D027986353D1341ADA4F2A4F8A170762FF8F24A@cceexc18.americas.cpqcorp.net>
Thread-Topic: [rddp] rdmap-03 spec clarification
Thread-Index: AcVBUgzwx/NAu93wTkq6YlPl+LbQBAAZUKnA
From: "Culley, Paul" <paul.culley@hp.com>
To: "Patricio Kaplan" <pkaplan@chelsio.com>, "RDDP" <rddp@ietf.org>
X-OriginalArrivalTime: 15 Apr 2005 12:34:57.0484 (UTC)
	FILETIME=[888008C0:01C541B7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: quoted-printable

I always thought that "ignored" means don't even look at it; you don't
care what it is.  Checking for zero and then doing nothing is logically
the same as not checking at all...

Paul R. Culley
HP Fellow
281-514-5543
=20

> -----Original Message-----
> From: rddp-bounces@ietf.org [mailto:rddp-bounces@ietf.org] On=20
> Behalf Of Patricio Kaplan
> Sent: Thursday, April 14, 2005 7:25 PM
> To: RDDP
> Subject: [rddp] rdmap-03 spec clarification
>=20
> draft-ietf-rddp-rdmap-03.txt, section 6.1:
>=20
> "Bits 32-63; Invalidate STag. However, this field is only=20
> valid  for Send with Invalidate and Send with Solicited Event=20
> and  Invalidate Messages (see Figure 4 RDMA Usage of DDP Fields).
>  For Send, Send with Solicited Event, RDMA Read Request, and =20
> Terminate, the Invalidate STag field MUST be set to zero on =20
> transmit and ignored by the receiver."
>=20
> Could someone tell me if "ignored by the receiver" means=20
>=20
> 1) If it is not zero the receiver MUST NOT generate an error
> 2) The receiver MUST CHECK that the STag is zero but in case it is=20
>    it does nothing with it.
>=20
> thanks in advance,
>=20
> -patricio kaplan
>=20
> _______________________________________________
> rddp mailing list
> rddp@ietf.org
> https://www1.ietf.org/mailman/listinfo/rddp
>=20

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp


From rddp-bounces@ietf.org  Fri Apr 15 13:16:06 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22662
	for <rddp-web-archive@ietf.org>; Fri, 15 Apr 2005 13:16:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMUaZ-0000u9-Jy
	for rddp-web-archive@ietf.org; Fri, 15 Apr 2005 13:26:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMUNM-0000iu-Cz; Fri, 15 Apr 2005 13:13:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMRtQ-0002YD-Qp
	for rddp@megatron.ietf.org; Fri, 15 Apr 2005 10:34:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05436
	for <rddp@ietf.org>; Fri, 15 Apr 2005 10:33:50 -0400 (EDT)
Message-Id: <200504151433.KAA05436@ietf.org>
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMS3U-0000Lp-Ng
	for rddp@ietf.org; Fri, 15 Apr 2005 10:44:26 -0400
Received: from i8600
	(static-64-222-186-225.man.east.verizon.net[64.222.186.225])
	by comcast.net (sccrmhc13) with SMTP
	id <2005041514334101600a4q47e>; Fri, 15 Apr 2005 14:33:41 +0000
From: "Barry Reinhold\(home\)" <reinholds@comcast.net>
To: "RDDP" <rddp@ietf.org>
Subject: RE: [rddp] rdmap-03 spec clarification
Date: Fri, 15 Apr 2005 10:33:40 -0400
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcVByB4O4Era1GQjTH+r+OwCoTw2NA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2a9ffb6f997442a3b543bcdaf483b990
X-Mailman-Approved-At: Fri, 15 Apr 2005 13:13:02 -0400
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1705506209=="
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 8d89ee9312a95de8ee48d1c94511f1bb

This is a multi-part message in MIME format.

--===============1705506209==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002A_01C541A6.973A8AE0"

This is a multi-part message in MIME format.

------=_NextPart_000_002A_01C541A6.973A8AE0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

>From the conformance testing perspective we send you non-zero values in bits
32-63 using the different RDMA operations specified and expect the DUT to
properly complete the RDMA request. I think this is your case 1. 

I didn't understand your case 2 - could you reword that case please?

 

draft-ietf-rddp-rdmap-03.txt, section 6.1:

 

"Bits 32-63; Invalidate STag. However, this field is only valid  for Send
with Invalidate and Send with Solicited Event and  Invalidate Messages (see
Figure 4 RDMA Usage of DDP Fields).

 For Send, Send with Solicited Event, RDMA Read Request, and  Terminate, the
Invalidate STag field MUST be set to zero on  transmit and ignored by the
receiver."

 

Could someone tell me if "ignored by the receiver" means 

 

1) If it is not zero the receiver MUST NOT generate an error

2) The receiver MUST CHECK that the STag is zero but in case it is 

   it does nothing with it.

 

thanks in advance,

 

-patricio kaplan

 

 

Barry Reinhold

 

reinholds@comcast.net

(603) 659-2569

 


------=_NextPart_000_002A_01C541A6.973A8AE0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>From the =
conformance testing
perspective we send you non-zero values in bits 32-63 using the =
different RDMA
operations specified and expect the DUT to properly complete the RDMA =
request. I
think this is your case 1. <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>I didn&#8217;t =
understand
your case 2 &#8211; could you reword that case =
please?<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>draft-ietf-rddp-rdmap-03.txt,
section 6.1:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>&quot;Bits 32-63; =
Invalidate
STag. However, this field is only valid&nbsp; for Send with Invalidate =
and Send
with Solicited Event and&nbsp; Invalidate Messages (see Figure 4 RDMA =
Usage of
DDP Fields).<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;For Send, =
Send with
Solicited Event, RDMA Read Request, and&nbsp; Terminate, the Invalidate =
STag
field MUST be set to zero on&nbsp; transmit and ignored by the =
receiver.&quot;<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Could someone tell =
me if
&quot;ignored by the receiver&quot; means <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>1) If it is not =
zero the
receiver MUST NOT generate an error<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>2) The receiver =
MUST CHECK
that the STag is zero but in case it is <o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; it =
does nothing
with it.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>thanks in =
advance,<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>-patricio =
kaplan<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Barry Reinhold</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>reinholds@comcast.net</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>(603) 659-2569</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_002A_01C541A6.973A8AE0--




--===============1705506209==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp

--===============1705506209==--





From rddp-bounces@ietf.org  Fri Apr 15 13:31:35 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24509
	for <rddp-web-archive@ietf.org>; Fri, 15 Apr 2005 13:31:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMUpX-0001uc-Cl
	for rddp-web-archive@ietf.org; Fri, 15 Apr 2005 13:42:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMUeh-0004PG-Q4; Fri, 15 Apr 2005 13:30:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMUeg-0004Oz-2J
	for rddp@megatron.ietf.org; Fri, 15 Apr 2005 13:30:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24402
	for <rddp@ietf.org>; Fri, 15 Apr 2005 13:30:57 -0400 (EDT)
Received: from [64.186.171.138] (helo=stargate.chelsio.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMUot-0001ri-Im
	for rddp@ietf.org; Fri, 15 Apr 2005 13:41:33 -0400
Received: from YOGI.asicdesigners.com (yogi.asicdesigners.com [10.192.160.7])
	by stargate.chelsio.com (8.12.5/8.12.5) with SMTP id j3FHUV6H030523; 
	Fri, 15 Apr 2005 10:30:31 -0700
Received: yogi.asicdesigners.com 10.192.160.7 from 10.192.161.85 10.192.161.85
	via HTTP with MS-WebStorage 6.0.6249
Received: from orion by yogi.asicdesigners.com; 15 Apr 2005 10:30:31 -0700
Subject: RE: [rddp] rdmap-03 spec clarification
From: Patricio Kaplan <pkaplan@chelsio.com>
To: "Barry Reinhold(home)" <reinholds@comcast.net>
In-Reply-To: <200504151433.KAA05436@ietf.org>
References: <200504151433.KAA05436@ietf.org>
Content-Type: text/plain; charset=windows-1251
Content-Transfer-Encoding: quoted-printable
Message-Id: <1113586230.418.34.camel@orion.asicdesigners.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Fri, 15 Apr 2005 10:30:31 -0700
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: quoted-printable
Cc: RDDP <rddp@ietf.org>
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: quoted-printable

On Fri, 2005-04-15 at 07:33, Barry Reinhold(home) wrote:
> From the conformance testing perspective we send you non-zero values
> in bits 32-63 using the different RDMA operations specified and expect
> the DUT to properly complete the RDMA request. I think this is your
> case 1.=20
>=20
> I didn=92t understand your case 2 =96 could you reword that case please?
>=20

My question has been answered. Thanks.

I was concerned that some conformance test would send a non-zero value
in the Invalidate STag field and expect the receiver to flag an error.

-patricio kaplan
> =20
>=20
> draft-ietf-rddp-rdmap-03.txt, section 6.1:
>=20
> =20
>=20
> "Bits 32-63; Invalidate STag. However, this field is only valid  for
> Send with Invalidate and Send with Solicited Event and  Invalidate
> Messages (see Figure 4 RDMA Usage of DDP Fields).
>=20
>  For Send, Send with Solicited Event, RDMA Read Request, and=20
> Terminate, the Invalidate STag field MUST be set to zero on  transmit
> and ignored by the receiver."
>=20
> =20
>=20
> Could someone tell me if "ignored by the receiver" means=20
>=20
> =20
>=20
> 1) If it is not zero the receiver MUST NOT generate an error
>=20
> 2) The receiver MUST CHECK that the STag is zero but in case it is=20
>=20
>    it does nothing with it.
>=20
> =20
>=20
> thanks in advance,
>=20
> =20
>=20
> -patricio kaplan
>=20
> =20
>=20
> =20
>=20
> Barry Reinhold
>=20
> =20
>=20
> reinholds@comcast.net
>=20
> (603) 659-2569
>=20
>=20
> =20
>=20
>=20
>=20
> ______________________________________________________________________
> _______________________________________________
> rddp mailing list
> rddp@ietf.org
> https://www1.ietf.org/mailman/listinfo/rddp


_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp


From rddp-bounces@ietf.org Thu Apr 21 08:21:58 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOagw-0007Gr-85; Thu, 21 Apr 2005 08:21:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOagu-0007Gk-1D
	for rddp@megatron.ietf.org; Thu, 21 Apr 2005 08:21:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20253
	for <rddp@ietf.org>; Thu, 21 Apr 2005 08:21:54 -0400 (EDT)
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOasJ-0004qN-3u
	for rddp@ietf.org; Thu, 21 Apr 2005 08:33:43 -0400
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail3.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 21 Apr 2005 05:21:45 -0700
Received: from red-hub-03.redmond.corp.microsoft.com ([157.54.2.25]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1824); 
	Thu, 21 Apr 2005 05:21:42 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.84]) by red-hub-03.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1802); Thu, 21 Apr 2005 05:21:42 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com
	([157.54.12.81]) by
	win-imc-02.wingroup.windeploy.ntdev.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Apr 2005 05:21:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [rddp] I-D ACTION:draft-ietf-rddp-security-07.txt
Date: Thu, 21 Apr 2005 05:21:39 -0700
Message-ID: <E6564B8F86852D46A4E98C485FB33B8F0D40ECFE@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [rddp] I-D ACTION:draft-ietf-rddp-security-07.txt
Thread-Index: AcVAZqxDKDwTXWbdQGuBO+rKkuO0wQGBA2qQ
From: "Jim Pinkerton" <jpink@windows.microsoft.com>
To: <rddp@ietf.org>
X-OriginalArrivalTime: 21 Apr 2005 12:21:41.0604 (UTC)
	FILETIME=[AC98E240:01C5466C]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: afbb91703506ab43c817903f0dd6f23d
Cc: Allyn Romanow <allyn@cisco.com>, Sara Bitan <sarab@microsoft.com>
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1103028047=="
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1103028047==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5466C.AD83FD2E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5466C.AD83FD2E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

I believe the -07 security draft resolves all outstanding issues per
last call.

=20

Specific changes:

-          updated doc to address "nits" script.

o        New boilerplate in "Status of this Memo"

o        Added IANA considerations section (which is essentially empty).

o        Fixed smart quotes

-          Removed revision history

-          3.1 - removed offending text on Resource Manager

-          6.5.2.3 - changed the first bullet to read "The ULP protocol
allows the Remote Peer to cause the local ULP to reserve..."

-          Updated IETF copyright to 2005.

=20

=20

Jim

=20

=20

=20

=20

> -----Original Message-----

> From: rddp-bounces@ietf.org [mailto:rddp-bounces@ietf.org] On Behalf
Of

> Internet-Drafts@ietf.org

> Sent: Wednesday, April 13, 2005 12:48 PM

> To: i-d-announce@ietf.org

> Cc: rddp@ietf.org

> Subject: [rddp] I-D ACTION:draft-ietf-rddp-security-07.txt

>=20

> A New Internet-Draft is available from the on-line Internet-Drafts

> directories.

> This draft is a work item of the Remote Direct Data Placement Working

> Group of the IETF.

>=20

>     Title       : DDP/RDMAP Security

>     Author(s)   : J. Pinkerton, et al.

>     Filename    : draft-ietf-rddp-security-07.txt

>     Pages       : 53

>     Date        : 2005-4-13

>=20

> This document analyzes security issues around implementation and

>    use of the Direct Data Placement Protocol(DDP) and Remote Direct

>    Memory Access Protocol (RDMAP). It first defines an architectural

>    model for an RDMA Network Interface Card (RNIC), which can

>    implement DDP or RDMAP and DDP. The document reviews various

>    attacks against the resources defined in the architectural model

>    and the countermeasures that can be used to protect the system.

>    Attacks are grouped into spoofing, tampering, information

>    disclosure, denial of service, and elevation of privilege.

>    Finally, the document concludes with a summary of security

>    services for DDP and RDMAP, such as IPsec.

>=20

> A URL for this Internet-Draft is:

> http://www.ietf.org/internet-drafts/draft-ietf-rddp-security-07.txt

>=20

> To remove yourself from the I-D Announcement list, send a message to

> i-d-announce-request@ietf.org with the word unsubscribe in the body of
the

> message.

> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce

> to change your subscription settings.

>=20

>=20

> Internet-Drafts are also available by anonymous FTP. Login with the

> username

> "anonymous" and a password of your e-mail address. After logging in,

> type "cd internet-drafts" and then

>     "get draft-ietf-rddp-security-07.txt".

>=20

> A list of Internet-Drafts directories can be found in

> http://www.ietf.org/shadow.html

> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

>=20

>=20

> Internet-Drafts can also be obtained by e-mail.

>=20

> Send a message to:

>     mailserv@ietf.org.

> In the body type:

>     "FILE /internet-drafts/draft-ietf-rddp-security-07.txt".

>=20

> NOTE:     The mail server at ietf.org can return the document in

>     MIME-encoded form by using the "mpack" utility.  To use this

>     feature, insert the command "ENCODING mime" before the "FILE"

>     command.  To decode the response(s), you will need "munpack" or

>     a MIME-compliant mail reader.  Different MIME-compliant mail
readers

>     exhibit different behavior, especially when dealing with

>     "multipart" MIME messages (i.e. documents which have been split

>     up into multiple messages), so check your local documentation on

>     how to manipulate these messages.

>=20

>=20

> Below is the data which will enable a MIME compliant mail reader

> implementation to automatically retrieve the ASCII version of the

> Internet-Draft.


------_=_NextPart_001_01C5466C.AD83FD2E
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:.5in 77.95pt .5in 77.95pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I believe the -07 security draft resolves all =
outstanding
issues per last call.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Specific changes:</span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.75in;text-indent:-.25in'><font size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>updated doc to address &#8220;nits&#8221; =
script.</span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:1.25in;text-indent:-.25in'><font size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>o<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>New boilerplate in &#8220;Status of this =
Memo&#8221;</span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:1.25in;text-indent:-.25in'><font size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>o<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>Added IANA considerations section (which is
essentially empty).</span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:1.25in;text-indent:-.25in'><font size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>o<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>Fixed smart quotes</span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.75in;text-indent:-.25in'><font size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>Removed revision history</span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.75in;text-indent:-.25in'><font size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>3.1 &#8211; removed offending text on Resource
Manager</span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.75in;text-indent:-.25in'><font size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>6.5.2.3 &#8211; changed the first bullet to =
read &#8220;The
ULP protocol allows the Remote Peer to cause the local ULP to =
reserve...&#8221;</span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:.75in;text-indent:-.25in'><font size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>-<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>Updated IETF copyright to =
2005.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&nbsp;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Jim</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&nbsp;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&nbsp;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&nbsp;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&nbsp;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; -----Original Message-----</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; From: rddp-bounces@ietf.org [mailto:rddp-bounces@ietf.org] =
On
Behalf Of</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Internet-Drafts@ietf.org</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Sent: Wednesday, April 13, 2005 12:48 PM</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; To: i-d-announce@ietf.org</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Cc: rddp@ietf.org</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Subject: [rddp] I-D =
ACTION:draft-ietf-rddp-security-07.txt</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; A New Internet-Draft is available from the on-line =
Internet-Drafts</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; directories.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; This draft is a work item of the Remote Direct Data =
Placement
Working</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Group of the IETF.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; =
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
DDP/RDMAP Security</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; Author(s)&nbsp;&nbsp; : J. Pinkerton, et =
al.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp; : =
draft-ietf-rddp-security-07.txt</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; =
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 53</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; =
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
2005-4-13</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; This document analyzes security issues around =
implementation and</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;use of the Direct Data Placement =
Protocol(DDP)
and Remote Direct</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;Memory Access Protocol (RDMAP). It first =
defines
an architectural</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;model for an RDMA Network Interface Card =
(RNIC),
which can</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;implement DDP or RDMAP and DDP. The =
document
reviews various</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;attacks against the resources defined in =
the
architectural model</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;and the countermeasures that can be used =
to
protect the system.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;Attacks are grouped into spoofing, =
tampering,
information</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;disclosure, denial of service, and =
elevation of
privilege.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;Finally, the document concludes with a =
summary
of security</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp;services for DDP and RDMAP, such as =
IPsec.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; A URL for this Internet-Draft is:</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; =
http://www.ietf.org/internet-drafts/draft-ietf-rddp-security-07.txt</span=
></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; To remove yourself from the I-D Announcement list, send a =
message
to</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; i-d-announce-request@ietf.org with the word unsubscribe in =
the
body of the</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; message.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; You can also visit
https://www1.ietf.org/mailman/listinfo/I-D-announce</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; to change your subscription settings.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Internet-Drafts are also available by anonymous FTP. Login =
with
the</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; username</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &quot;anonymous&quot; and a password of your e-mail =
address. After
logging in,</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; type &quot;cd internet-drafts&quot; and =
then</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; &quot;get
draft-ietf-rddp-security-07.txt&quot;.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; A list of Internet-Drafts directories can be found =
in</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; http://www.ietf.org/shadow.html</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; or =
ftp://ftp.ietf.org/ietf/1shadow-sites.txt</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Internet-Drafts can also be obtained by =
e-mail.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Send a message to:</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; mailserv@ietf.org.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; In the body type:</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; &quot;FILE
/internet-drafts/draft-ietf-rddp-security-07.txt&quot;.</span></font></p>=


<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; NOTE:&nbsp;&nbsp;&nbsp;&nbsp; The mail server at ietf.org =
can
return the document in</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; MIME-encoded form by using the
&quot;mpack&quot; utility.&nbsp; To use this</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; feature, insert the command =
&quot;ENCODING
mime&quot; before the &quot;FILE&quot;</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; command.&nbsp; To decode the =
response(s), you
will need &quot;munpack&quot; or</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; a MIME-compliant mail reader.&nbsp; =
Different
MIME-compliant mail readers</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; exhibit different behavior, especially =
when
dealing with</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; &quot;multipart&quot; MIME messages =
(i.e.
documents which have been split</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; up into multiple messages), so check =
your local
documentation on</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; &nbsp;&nbsp;&nbsp; how to manipulate these =
messages.</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; </span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Below is the data which will enable a MIME compliant mail =
reader</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; implementation to automatically retrieve the ASCII version =
of the</span></font></p>

<p class=3DMsoPlainText><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>&gt; Internet-Draft.</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C5466C.AD83FD2E--


--===============1103028047==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp

--===============1103028047==--




From rddp-bounces@ietf.org Fri Apr 22 15:55:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DP4FF-0003S8-5B; Fri, 22 Apr 2005 15:55:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DP4FA-0003Qg-U8; Fri, 22 Apr 2005 15:55:16 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18643;
	Fri, 22 Apr 2005 15:55:15 -0400 (EDT)
Message-Id: <200504221955.PAA18643@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 22 Apr 2005 15:55:14 -0400
Cc: rddp@ietf.org
Subject: [rddp] I-D ACTION:draft-ietf-rddp-rdmap-04.txt
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Remote Direct Data Placement Working Group of the IETF.

	Title		: An RDMA Protocol Specification
	Author(s)	: R. Recio, et al.
	Filename	: draft-ietf-rddp-rdmap-04.txt
	Pages		: 77
	Date		: 2005-4-22
	
This document defines a Remote Direct Memory Access Protocol 
      (RDMAP) that operates over the Direct Data Placement Protocol (DDP 
      protocol).  RDMAP provides read and write services directly to 
      applications and enables data to be transferred directly into ULP 
      Buffers without intermediate data copies. It also enables a kernel 
      bypass implementation.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rddp-rdmap-04.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rddp-rdmap-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rddp-rdmap-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-4-22162329.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rddp-rdmap-04.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-rddp-rdmap-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-22162329.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rddp mailing list
rddp@ietf.org
https://www1.ietf.org/mailman/listinfo/rddp

--NextPart--






