From exim@www1.ietf.org  Mon Mar  1 23:59:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01494
	for <rddp-archive@odin.ietf.org>; Mon, 1 Mar 2004 23:59:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1zx-0003U4-Jq
	for rddp-archive@odin.ietf.org; Mon, 01 Mar 2004 23:59:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i224xHNN013388
	for rddp-archive@odin.ietf.org; Mon, 1 Mar 2004 23:59:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1zx-0003Tr-FN
	for rddp-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 23:59:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01481
	for <rddp-web-archive@ietf.org>; Mon, 1 Mar 2004 23:59:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1zv-0002sW-00
	for rddp-web-archive@ietf.org; Mon, 01 Mar 2004 23:59:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay1z0-0002n2-00
	for rddp-web-archive@ietf.org; Mon, 01 Mar 2004 23:58:21 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1yh-0002ha-00
	for rddp-web-archive@ietf.org; Mon, 01 Mar 2004 23:57:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1yi-0003Q2-Nh; Mon, 01 Mar 2004 23:58:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1xu-0003NT-5v
	for rddp@optimus.ietf.org; Mon, 01 Mar 2004 23:57:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01349
	for <rddp@ietf.org>; Mon, 1 Mar 2004 23:57:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1xr-0002fe-00
	for rddp@ietf.org; Mon, 01 Mar 2004 23:57:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay1wu-0002Y4-00
	for rddp@ietf.org; Mon, 01 Mar 2004 23:56:11 -0500
Received: from mx01.netapp.com ([198.95.226.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1vy-0002Fs-00
	for rddp@ietf.org; Mon, 01 Mar 2004 23:55:10 -0500
Received: from frejya.corp.netapp.com (frejya [10.57.157.119])
	by mx01.netapp.com (8.12.10/8.12.10/NTAP-1.4) with ESMTP id i224sXJC020697;
	Mon, 1 Mar 2004 20:54:33 -0800 (PST)
Received: from svlexc01.hq.netapp.com (svlexc01.corp.netapp.com [10.10.22.171])
	by frejya.corp.netapp.com (8.12.9/8.12.9/NTAP-1.5) with ESMTP id i224sXDe029722;
	Mon, 1 Mar 2004 20:54:33 -0800 (PST)
Received: from tmt.netapp.com ([10.97.6.31]) by silver.hq.netapp.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 1 Mar 2004 23:54:27 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C40012.707F0380"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
Date: Mon, 1 Mar 2004 20:54:07 -0800
Message-ID: <6.0.3.0.2.20040301224523.01b88340@silver.nane.netapp.com>
Thread-Topic: Comments on draft-ietf-rddp-security-01
Thread-Index: AcQAEnFKYlLjNOowTBCTlEk4QlYcaw==
From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
To: "Jim Pinkerton" <jpink@windows.microsoft.com>, <rddp@ietf.org>
Subject: [rddp] Comments on draft-ietf-rddp-security-01
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60

This is a multi-part message in MIME format.

------_=_NextPart_001_01C40012.707F0380
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have reviewed the recent RDDP Security draft
(http://www.ietf.org/internet-drafts/draft-ietf-rddp-security-01.txt)
and have some comments in advance of tomorrow's
working group meeting.

I'd like to open by complimenting the authors on an excellent
second revision. This is a difficult document, but an important
one.

I don't have many high-level comments. The draft seems
well put-together.

One style thing to mention though - there are many, many
references to "later" or other sections, especially in the earlier
ones. I suggest direct section references.

Apostophes and em-dashes seem to have a different ascii
encoding, which appear strangely with certain text tools.
Suggest conventional ascii.

How specifically do we define "Partial Mutual Trust", which
appears relatively early? One way the reader may take it,
is as an authentication guarantee, for both the local application
and remote peer. But who decides "partial", for instance? Is
the motivation primarily to clarify the use of shared resources,
such as the SRQ?

In the introduction, it seems critical to describe the scope of
possible damage if the trust is violated. I believe it is very
different depending on the resource which is the subject of
the trust. System-level damage should be described differently
from damage which merely :-) damages the application. This is
not a very specific recommendation, I know.

I think there are differences between the trust model as described
here, and a privileged/nonprivileged application (at the end of
the Introduction). It might be worthwhile to bring these out.
For example, the trust model seems primarily oriented at wire-based
attacks, while the privileged/nonprivileged application is a local
matter? What interaction do these have?

Sect 4 pargraph 1 last sentence - "should be preserved when
under attack", just delete "when under attack" and say "should
be preserved". Maybe even "must".

4.2.1 refers to a FIFO list of buffers - maybe not FIFO in the
case of SRQs. Perhaps just "list of buffers" here - but also see
comment on 4.2.10.

4.2.2 buffer exposed to "the Internet"? This is vague.

4.2.2 a general comment - this refers to the RI, while I think
it means the Privileged Resource Manager? Overall, I think the
"RI" term is loosely used, for example it's defined only in Figure 1,
and about 2/3 of the time seems to mean the PRM instead of
the RNIC's programmatic interface. In fact, in 7.5.5 it's used to
mean "Remote Invalidation"!

4.2.3 describes page translation tables. Is it worth bringing out
the possibility they are multi-level and therefore possibly shared?

4.2.4 I suggest merging Mike Krause's comment/observation that
the STag does not in itself provide protection, and in fact should
provide efficiency. This is important to understanding that protection
comes from other facilities.

4.2.5 mention that Completion Queues are of bounded size (like
4.2.6) and so the size can be attacked. CQ attack is much more
likely than AEQ attack, in fact.

4.2.8 clarify the RRQ is inbound.

After (or in) 4.2.8, should add the outbound RRQ as well. It's not
easily attacked, but this queue has interesting flow control =
interactions
with sends. If the queue overflows, a head-of-line blocking behavior
could be encountered, which is very different from "normal" operation.

4.2.8.2 it's very important to mention that RDMA Read exposes a
buffer for RDMA Write as well. And describe the possible protection.

4.2.8.2 last paragraph, has a vague use of the phrase "data transmission
or reception". For example, RDMA Writes don't yield a completion at
the data sink, counter to the sentence.

4.2.9 refers to an STag which has only local scope that "may not
be visible from the wire". (pp starting "The next issue"). =3D> This =
"may"
must be a "must" in order for the statement to be true! In fact, if it's
a "may" then a security hole is open.

4.2.10 "send" and "receive" operations - these do not mean "Send" so
are somewhat confusing.

4.2.10 - FIFO order? Perhaps "sequential", in the face of SRQ. The
paragraph goes on to describe this, but not very clearly. I suggest
not using "FIFO" in any case.

Section 5 first paragraph describes when/if the "Local peer" is =
untrusted.
I noticed here that "local peer" isn't defined, and in fact I think it =
means
the local application or ULP? I think it would be worth a pass through =
the
document to be sure all use of the term is consistent. And of course,
defining the term.

Section 6 - it's not clear to me what's an attacker with send-only
capabilities?

Section 7 paragraph 2 - I disagree that connection setup in stream mode
has no new attacks. This is where ULPs may exchange information. If
the information is bad, significant resource issues can clearly result. =
It's
true however that such exchanges are outside the scope of the document,
I just think the document should not state that there are no new =
attacks.

7.1.1 should perhaps introduce the PD more directly. The PD is described
in draft-hilland which is not normative.

7.1.1 goes on to say "should" associate a QP to unique PDs, or shared,
I find this discussion to not be clear. Also I'd suggest incorporating =
Caitlin's
"remote PD" concept, which helps to define the PD and STag scope to a
remote peer.

7.1.2 mentions "allocating STags in an unpredictable way". I want to =
point
out that it is also possible for the application to "advertise" STags in =
such
a way, if it manages its own pool. In fact, this can be much more =
efficient
since STag allocation is not appropriate for the performance path.

7.2.3 MITM attack discussion first says "the only countermeasure" (pp 1)
then says "the best countermeasure" (pp 2). Eh?

I think the summary of 7.2.3 is that MITM attacks should be protected in
the usual way by LLP facilities, and not in DDP/RDMAP. However it may be
worth mentioning that the MPA layer injects a CRC, making this =
nontrivial
(though no more secure).

In 7.4.2, to me, the most usual exposure of a buffer for RDMA Read is to
provide access to NON-stale data - i.e. an actual transfer such as =
client
"writing" data by advertising it for pull. Thus the zeroing memory =
comment
only applies in certain (rare, IMO) cases. The text only generally =
mentions
this by saying "combination of read and write", and could be clearer. =
Maybe
giving a specific example?

7.4.5 great place to mention the (more difficult) flip side - RDMA Write =
into
RDMA Read buffer. This is a definite issue, see my 4.2.8.2 comment.

7.4.6 suggest using the term "aliasing" to help describe the multiple =
STag
situation.

7.4.9 "eaves dropping" is one word. Worth referring to MITM discussion =
here
as well?

7.5.1 define "scarce"? Why wouldn't all resources be under the control =
of
the PRM?

7.5.2.1 mention that if the stream is torn down, then this additionally =
has
the benefit that RNIC resources are released. For example, it cuts off a
misbehaving peer drawing from a Shared RQ.

7.5.2.3 after "The local Peer can protect itself", first bullet mentions =
resize.
Really doesn't it just mean "size"? Also give a hint that safe size is =
>=3D sum
of all queues, etc. as described immediately following.

7.5.2.3 some of the math examples are confusing - "S-RQ" looks like a =
minus
sign but isn't? Also MaxPosted*OnEach*Q is not clear.

7.5.2.4 describes the situation "If the issue is a bug in the Remote =
Peer's
implementation, and not a malicious attack..." - so tell me, how does =
the
local peer know? :-)

7.5.5 has a funny title: "RI an STag Shared on Multiple Streams". Here =
"RI"
has a very different meaning - Remote Invalidate. Even when spelled out,
the title is awkward.

8.1 it's not clear how to protect against replay attacks at the RDDP =
"session"
level. (BTW, session is an undefined term.) Is reply protection purely a
function of transport? This doesn't sound right. By the way, this is =
only
the second mention of "replay" in the draft.

I note that 8.1.3 mentions NFS and its provision of security - =
presumably
referring to RPC's GSSAPI support. This is a good topic to discuss in =
the
NFSv4 working group, but I'm not sure what needs to be mentioned here.
What do the authors have in mind?

I note that section 8.2 is entitled "Recommendations" and describes =
itself
as being geared toward iSCSI requirements. But it has many MUSTs and
the sections seems somewhat more relevant for an iSCSI over RDMA
document, or perhaps a specific RDDP/IPSec layering, rather than a
general RDMA one. Is a second document appropriate?

I have not yet reviewed the appendices.

Again, good job!

Tom.


------_=_NextPart_001_01C40012.707F0380
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6249.1">
<TITLE>Comments on draft-ietf-rddp-security-01</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I have reviewed the recent RDDP Security draft</FONT>

<BR><FONT SIZE=3D2>(<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-rddp-security-01.t=
xt">http://www.ietf.org/internet-drafts/draft-ietf-rddp-security-01.txt</=
A>)</FONT>

<BR><FONT SIZE=3D2>and have some comments in advance of =
tomorrow's</FONT>

<BR><FONT SIZE=3D2>working group meeting.</FONT>
</P>

<P><FONT SIZE=3D2>I'd like to open by complimenting the authors on an =
excellent</FONT>

<BR><FONT SIZE=3D2>second revision. This is a difficult document, but an =
important</FONT>

<BR><FONT SIZE=3D2>one.</FONT>
</P>

<P><FONT SIZE=3D2>I don't have many high-level comments. The draft =
seems</FONT>

<BR><FONT SIZE=3D2>well put-together.</FONT>
</P>

<P><FONT SIZE=3D2>One style thing to mention though - there are many, =
many</FONT>

<BR><FONT SIZE=3D2>references to &quot;later&quot; or other sections, =
especially in the earlier</FONT>

<BR><FONT SIZE=3D2>ones. I suggest direct section references.</FONT>
</P>

<P><FONT SIZE=3D2>Apostophes and em-dashes seem to have a different =
ascii</FONT>

<BR><FONT SIZE=3D2>encoding, which appear strangely with certain text =
tools.</FONT>

<BR><FONT SIZE=3D2>Suggest conventional ascii.</FONT>
</P>

<P><FONT SIZE=3D2>How specifically do we define &quot;Partial Mutual =
Trust&quot;, which</FONT>

<BR><FONT SIZE=3D2>appears relatively early? One way the reader may take =
it,</FONT>

<BR><FONT SIZE=3D2>is as an authentication guarantee, for both the local =
application</FONT>

<BR><FONT SIZE=3D2>and remote peer. But who decides &quot;partial&quot;, =
for instance? Is</FONT>

<BR><FONT SIZE=3D2>the motivation primarily to clarify the use of shared =
resources,</FONT>

<BR><FONT SIZE=3D2>such as the SRQ?</FONT>
</P>

<P><FONT SIZE=3D2>In the introduction, it seems critical to describe the =
scope of</FONT>

<BR><FONT SIZE=3D2>possible damage if the trust is violated. I believe =
it is very</FONT>

<BR><FONT SIZE=3D2>different depending on the resource which is the =
subject of</FONT>

<BR><FONT SIZE=3D2>the trust. System-level damage should be described =
differently</FONT>

<BR><FONT SIZE=3D2>from damage which merely :-) damages the application. =
This is</FONT>

<BR><FONT SIZE=3D2>not a very specific recommendation, I know.</FONT>
</P>

<P><FONT SIZE=3D2>I think there are differences between the trust model =
as described</FONT>

<BR><FONT SIZE=3D2>here, and a privileged/nonprivileged application (at =
the end of</FONT>

<BR><FONT SIZE=3D2>the Introduction). It might be worthwhile to bring =
these out.</FONT>

<BR><FONT SIZE=3D2>For example, the trust model seems primarily oriented =
at wire-based</FONT>

<BR><FONT SIZE=3D2>attacks, while the privileged/nonprivileged =
application is a local</FONT>

<BR><FONT SIZE=3D2>matter? What interaction do these have?</FONT>
</P>

<P><FONT SIZE=3D2>Sect 4 pargraph 1 last sentence - &quot;should be =
preserved when</FONT>

<BR><FONT SIZE=3D2>under attack&quot;, just delete &quot;when under =
attack&quot; and say &quot;should</FONT>

<BR><FONT SIZE=3D2>be preserved&quot;. Maybe even =
&quot;must&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>4.2.1 refers to a FIFO list of buffers - maybe not =
FIFO in the</FONT>

<BR><FONT SIZE=3D2>case of SRQs. Perhaps just &quot;list of =
buffers&quot; here - but also see</FONT>

<BR><FONT SIZE=3D2>comment on 4.2.10.</FONT>
</P>

<P><FONT SIZE=3D2>4.2.2 buffer exposed to &quot;the Internet&quot;? This =
is vague.</FONT>
</P>

<P><FONT SIZE=3D2>4.2.2 a general comment - this refers to the RI, while =
I think</FONT>

<BR><FONT SIZE=3D2>it means the Privileged Resource Manager? Overall, I =
think the</FONT>

<BR><FONT SIZE=3D2>&quot;RI&quot; term is loosely used, for example it's =
defined only in Figure 1,</FONT>

<BR><FONT SIZE=3D2>and about 2/3 of the time seems to mean the PRM =
instead of</FONT>

<BR><FONT SIZE=3D2>the RNIC's programmatic interface. In fact, in 7.5.5 =
it's used to</FONT>

<BR><FONT SIZE=3D2>mean &quot;Remote Invalidation&quot;!</FONT>
</P>

<P><FONT SIZE=3D2>4.2.3 describes page translation tables. Is it worth =
bringing out</FONT>

<BR><FONT SIZE=3D2>the possibility they are multi-level and therefore =
possibly shared?</FONT>
</P>

<P><FONT SIZE=3D2>4.2.4 I suggest merging Mike Krause's =
comment/observation that</FONT>

<BR><FONT SIZE=3D2>the STag does not in itself provide protection, and =
in fact should</FONT>

<BR><FONT SIZE=3D2>provide efficiency. This is important to =
understanding that protection</FONT>

<BR><FONT SIZE=3D2>comes from other facilities.</FONT>
</P>

<P><FONT SIZE=3D2>4.2.5 mention that Completion Queues are of bounded =
size (like</FONT>

<BR><FONT SIZE=3D2>4.2.6) and so the size can be attacked. CQ attack is =
much more</FONT>

<BR><FONT SIZE=3D2>likely than AEQ attack, in fact.</FONT>
</P>

<P><FONT SIZE=3D2>4.2.8 clarify the RRQ is inbound.</FONT>
</P>

<P><FONT SIZE=3D2>After (or in) 4.2.8, should add the outbound RRQ as =
well. It's not</FONT>

<BR><FONT SIZE=3D2>easily attacked, but this queue has interesting flow =
control interactions</FONT>

<BR><FONT SIZE=3D2>with sends. If the queue overflows, a head-of-line =
blocking behavior</FONT>

<BR><FONT SIZE=3D2>could be encountered, which is very different from =
&quot;normal&quot; operation.</FONT>
</P>

<P><FONT SIZE=3D2>4.2.8.2 it's very important to mention that RDMA Read =
exposes a</FONT>

<BR><FONT SIZE=3D2>buffer for RDMA Write as well. And describe the =
possible protection.</FONT>
</P>

<P><FONT SIZE=3D2>4.2.8.2 last paragraph, has a vague use of the phrase =
&quot;data transmission</FONT>

<BR><FONT SIZE=3D2>or reception&quot;. For example, RDMA Writes don't =
yield a completion at</FONT>

<BR><FONT SIZE=3D2>the data sink, counter to the sentence.</FONT>
</P>

<P><FONT SIZE=3D2>4.2.9 refers to an STag which has only local scope =
that &quot;may not</FONT>

<BR><FONT SIZE=3D2>be visible from the wire&quot;. (pp starting =
&quot;The next issue&quot;). =3D&gt; This &quot;may&quot;</FONT>

<BR><FONT SIZE=3D2>must be a &quot;must&quot; in order for the statement =
to be true! In fact, if it's</FONT>

<BR><FONT SIZE=3D2>a &quot;may&quot; then a security hole is =
open.</FONT>
</P>

<P><FONT SIZE=3D2>4.2.10 &quot;send&quot; and &quot;receive&quot; =
operations - these do not mean &quot;Send&quot; so</FONT>

<BR><FONT SIZE=3D2>are somewhat confusing.</FONT>
</P>

<P><FONT SIZE=3D2>4.2.10 - FIFO order? Perhaps &quot;sequential&quot;, =
in the face of SRQ. The</FONT>

<BR><FONT SIZE=3D2>paragraph goes on to describe this, but not very =
clearly. I suggest</FONT>

<BR><FONT SIZE=3D2>not using &quot;FIFO&quot; in any case.</FONT>
</P>

<P><FONT SIZE=3D2>Section 5 first paragraph describes when/if the =
&quot;Local peer&quot; is untrusted.</FONT>

<BR><FONT SIZE=3D2>I noticed here that &quot;local peer&quot; isn't =
defined, and in fact I think it means</FONT>

<BR><FONT SIZE=3D2>the local application or ULP? I think it would be =
worth a pass through the</FONT>

<BR><FONT SIZE=3D2>document to be sure all use of the term is =
consistent. And of course,</FONT>

<BR><FONT SIZE=3D2>defining the term.</FONT>
</P>

<P><FONT SIZE=3D2>Section 6 - it's not clear to me what's an attacker =
with send-only</FONT>

<BR><FONT SIZE=3D2>capabilities?</FONT>
</P>

<P><FONT SIZE=3D2>Section 7 paragraph 2 - I disagree that connection =
setup in stream mode</FONT>

<BR><FONT SIZE=3D2>has no new attacks. This is where ULPs may exchange =
information. If</FONT>

<BR><FONT SIZE=3D2>the information is bad, significant resource issues =
can clearly result. It's</FONT>

<BR><FONT SIZE=3D2>true however that such exchanges are outside the =
scope of the document,</FONT>

<BR><FONT SIZE=3D2>I just think the document should not state that there =
are no new attacks.</FONT>
</P>

<P><FONT SIZE=3D2>7.1.1 should perhaps introduce the PD more directly. =
The PD is described</FONT>

<BR><FONT SIZE=3D2>in draft-hilland which is not normative.</FONT>
</P>

<P><FONT SIZE=3D2>7.1.1 goes on to say &quot;should&quot; associate a QP =
to unique PDs, or shared,</FONT>

<BR><FONT SIZE=3D2>I find this discussion to not be clear. Also I'd =
suggest incorporating Caitlin's</FONT>

<BR><FONT SIZE=3D2>&quot;remote PD&quot; concept, which helps to define =
the PD and STag scope to a</FONT>

<BR><FONT SIZE=3D2>remote peer.</FONT>
</P>

<P><FONT SIZE=3D2>7.1.2 mentions &quot;allocating STags in an =
unpredictable way&quot;. I want to point</FONT>

<BR><FONT SIZE=3D2>out that it is also possible for the application to =
&quot;advertise&quot; STags in such</FONT>

<BR><FONT SIZE=3D2>a way, if it manages its own pool. In fact, this can =
be much more efficient</FONT>

<BR><FONT SIZE=3D2>since STag allocation is not appropriate for the =
performance path.</FONT>
</P>

<P><FONT SIZE=3D2>7.2.3 MITM attack discussion first says &quot;the only =
countermeasure&quot; (pp 1)</FONT>

<BR><FONT SIZE=3D2>then says &quot;the best countermeasure&quot; (pp 2). =
Eh?</FONT>
</P>

<P><FONT SIZE=3D2>I think the summary of 7.2.3 is that MITM attacks =
should be protected in</FONT>

<BR><FONT SIZE=3D2>the usual way by LLP facilities, and not in =
DDP/RDMAP. However it may be</FONT>

<BR><FONT SIZE=3D2>worth mentioning that the MPA layer injects a CRC, =
making this nontrivial</FONT>

<BR><FONT SIZE=3D2>(though no more secure).</FONT>
</P>

<P><FONT SIZE=3D2>In 7.4.2, to me, the most usual exposure of a buffer =
for RDMA Read is to</FONT>

<BR><FONT SIZE=3D2>provide access to NON-stale data - i.e. an actual =
transfer such as client</FONT>

<BR><FONT SIZE=3D2>&quot;writing&quot; data by advertising it for pull. =
Thus the zeroing memory comment</FONT>

<BR><FONT SIZE=3D2>only applies in certain (rare, IMO) cases. The text =
only generally mentions</FONT>

<BR><FONT SIZE=3D2>this by saying &quot;combination of read and =
write&quot;, and could be clearer. Maybe</FONT>

<BR><FONT SIZE=3D2>giving a specific example?</FONT>
</P>

<P><FONT SIZE=3D2>7.4.5 great place to mention the (more difficult) flip =
side - RDMA Write into</FONT>

<BR><FONT SIZE=3D2>RDMA Read buffer. This is a definite issue, see my =
4.2.8.2 comment.</FONT>
</P>

<P><FONT SIZE=3D2>7.4.6 suggest using the term &quot;aliasing&quot; to =
help describe the multiple STag</FONT>

<BR><FONT SIZE=3D2>situation.</FONT>
</P>

<P><FONT SIZE=3D2>7.4.9 &quot;eaves dropping&quot; is one word. Worth =
referring to MITM discussion here</FONT>

<BR><FONT SIZE=3D2>as well?</FONT>
</P>

<P><FONT SIZE=3D2>7.5.1 define &quot;scarce&quot;? Why wouldn't all =
resources be under the control of</FONT>

<BR><FONT SIZE=3D2>the PRM?</FONT>
</P>

<P><FONT SIZE=3D2>7.5.2.1 mention that if the stream is torn down, then =
this additionally has</FONT>

<BR><FONT SIZE=3D2>the benefit that RNIC resources are released. For =
example, it cuts off a</FONT>

<BR><FONT SIZE=3D2>misbehaving peer drawing from a Shared RQ.</FONT>
</P>

<P><FONT SIZE=3D2>7.5.2.3 after &quot;The local Peer can protect =
itself&quot;, first bullet mentions resize.</FONT>

<BR><FONT SIZE=3D2>Really doesn't it just mean &quot;size&quot;? Also =
give a hint that safe size is &gt;=3D sum</FONT>

<BR><FONT SIZE=3D2>of all queues, etc. as described immediately =
following.</FONT>
</P>

<P><FONT SIZE=3D2>7.5.2.3 some of the math examples are confusing - =
&quot;S-RQ&quot; looks like a minus</FONT>

<BR><FONT SIZE=3D2>sign but isn't? Also MaxPosted*OnEach*Q is not =
clear.</FONT>
</P>

<P><FONT SIZE=3D2>7.5.2.4 describes the situation &quot;If the issue is =
a bug in the Remote Peer's</FONT>

<BR><FONT SIZE=3D2>implementation, and not a malicious attack...&quot; - =
so tell me, how does the</FONT>

<BR><FONT SIZE=3D2>local peer know? :-)</FONT>
</P>

<P><FONT SIZE=3D2>7.5.5 has a funny title: &quot;RI an STag Shared on =
Multiple Streams&quot;. Here &quot;RI&quot;</FONT>

<BR><FONT SIZE=3D2>has a very different meaning - Remote Invalidate. =
Even when spelled out,</FONT>

<BR><FONT SIZE=3D2>the title is awkward.</FONT>
</P>

<P><FONT SIZE=3D2>8.1 it's not clear how to protect against replay =
attacks at the RDDP &quot;session&quot;</FONT>

<BR><FONT SIZE=3D2>level. (BTW, session is an undefined term.) Is reply =
protection purely a</FONT>

<BR><FONT SIZE=3D2>function of transport? This doesn't sound right. By =
the way, this is only</FONT>

<BR><FONT SIZE=3D2>the second mention of &quot;replay&quot; in the =
draft.</FONT>
</P>

<P><FONT SIZE=3D2>I note that 8.1.3 mentions NFS and its provision of =
security - presumably</FONT>

<BR><FONT SIZE=3D2>referring to RPC's GSSAPI support. This is a good =
topic to discuss in the</FONT>

<BR><FONT SIZE=3D2>NFSv4 working group, but I'm not sure what needs to =
be mentioned here.</FONT>

<BR><FONT SIZE=3D2>What do the authors have in mind?</FONT>
</P>

<P><FONT SIZE=3D2>I note that section 8.2 is entitled =
&quot;Recommendations&quot; and describes itself</FONT>

<BR><FONT SIZE=3D2>as being geared toward iSCSI requirements. But it has =
many MUSTs and</FONT>

<BR><FONT SIZE=3D2>the sections seems somewhat more relevant for an =
iSCSI over RDMA</FONT>

<BR><FONT SIZE=3D2>document, or perhaps a specific RDDP/IPSec layering, =
rather than a</FONT>

<BR><FONT SIZE=3D2>general RDMA one. Is a second document =
appropriate?</FONT>
</P>

<P><FONT SIZE=3D2>I have not yet reviewed the appendices.</FONT>
</P>

<P><FONT SIZE=3D2>Again, good job!</FONT>
</P>

<P><FONT SIZE=3D2>Tom.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C40012.707F0380--

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



From exim@www1.ietf.org  Tue Mar  2 03:18:13 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25524
	for <rddp-archive@odin.ietf.org>; Tue, 2 Mar 2004 03:18:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay560-0005j3-0q
	for rddp-archive@odin.ietf.org; Tue, 02 Mar 2004 03:17:44 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i228Hh5R022003
	for rddp-archive@odin.ietf.org; Tue, 2 Mar 2004 03:17:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay55z-0005io-PA
	for rddp-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 03:17:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25469
	for <rddp-web-archive@ietf.org>; Tue, 2 Mar 2004 03:17:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay55x-0004hb-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:17:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay551-0004YO-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:16:43 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay54R-0004Oe-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:16:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay54P-0005Yd-Sp; Tue, 02 Mar 2004 03:16:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay53o-0005TI-4C
	for rddp@optimus.ietf.org; Tue, 02 Mar 2004 03:15:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25278
	for <rddp@ietf.org>; Tue, 2 Mar 2004 03:15:26 -0500 (EST)
From: Black_David@emc.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay53l-0004Ku-00
	for rddp@ietf.org; Tue, 02 Mar 2004 03:15:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay52r-00049n-00
	for rddp@ietf.org; Tue, 02 Mar 2004 03:14:30 -0500
Received: from srexchimc2.lss.emc.com ([168.159.100.11] helo=srexchimc2.eng.emc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay51g-0003sd-00
	for rddp@ietf.org; Tue, 02 Mar 2004 03:13:16 -0500
Received: from MAHO3MSX2.corp.emc.com (maho3msx2.isus.emc.com [128.221.11.32]) by srexchimc2.eng.emc.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id GD38BBXF; Tue, 2 Mar 2004 03:12:47 -0500
Received: by maho3msx2.isus.emc.com with Internet Mail Service (5.5.2653.19)
	id <FK9AJHZN>; Tue, 2 Mar 2004 03:12:47 -0500
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA7A5688@corpmx14.us.dg.com>
X-Sybari-Trust: bdebc29a 1d8c424f d02de4bf 0000013d
To: rddp@ietf.org
Date: Tue, 2 Mar 2004 03:12:41 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [rddp] RDDP status of drafts
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

Here's what the WG chair believes the current status of
drafts in the RDDP WG to be (if anything seems wrong here,
please let me know):

IETF RDDP WG Draft Status - March 2004, Seoul IETF meetings
-----------------------------------------------------------

-- Problem Statement and Architecture

draft-ietf-rddp-problem-statement-03.txt
draft-ietf-rddp-arch-04.txt

To become Informational RFCs.

Finished WG Last Call, and have been revised to respond to comments
from our Area Director.  Further IESG discussion has generated
additional comments that will require further revisions.

-- Main Protocols

DDP (draft-ietf-rddp-ddp-02.txt)
RDMAP (draft-ietf-rddp-rdmap-01.txt)

To become Proposed Standard RFCs.

No technical issues meriting substantial meeting time.  Waiting
on security draft (which will probably generate revisions to
the security considerations sections in these drafts)
before going to WG Last Call

-- Applicability Statement

draft-ietf-rddp-applicability-01.txt

To become an Informational RFC.

Believed to be in good shape - please review.

-- SCTP Mapping

draft-ietf-rddp-sctp-00.txt

To become a Proposed Standard RFC.

Despite the -00 version number, this is the fourth version of this draft,
and
it is relatively mature.

-- TCP Mapping

draft-ietf-rddp-mpa-00.txt

To become an Informational RFC.

The major open issues in this draft involve connection initiation/
startup.  Substantial meeting time allocated to make progress.

draft-cully-mpa-issuesresponses-00.txt

Will not become an RFC.  This draft describes issues raised about
MPA and the views of the MPA authors on those issues.

-- Security

draft-ietf-rddp-security-01.txt

Whether this will be Informational vs. Proposed Standard is TBD.
This draft is on the critical path to completing the DDP and RDMAP
drafts.  Substantial meeting time has been allocated to it.


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



From exim@www1.ietf.org  Tue Mar  2 03:40:20 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26499
	for <rddp-archive@odin.ietf.org>; Tue, 2 Mar 2004 03:40:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay5RN-0007yq-Mq
	for rddp-archive@odin.ietf.org; Tue, 02 Mar 2004 03:39:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i228dnb2030660
	for rddp-archive@odin.ietf.org; Tue, 2 Mar 2004 03:39:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay5RL-0007yF-1u
	for rddp-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 03:39:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26387
	for <rddp-web-archive@ietf.org>; Tue, 2 Mar 2004 03:39:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay5RI-0007Wm-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:39:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay5QA-0007I4-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:38:35 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay5PX-00079s-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:37:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Ay5Lw-0003aF-D8
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 03:34:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay5Lp-0007DA-Va; Tue, 02 Mar 2004 03:34:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay5LA-00076N-O5
	for rddp@optimus.ietf.org; Tue, 02 Mar 2004 03:33:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26148
	for <rddp@ietf.org>; Tue, 2 Mar 2004 03:33:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay5L8-0006im-00
	for rddp@ietf.org; Tue, 02 Mar 2004 03:33:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay5KB-0006c6-00
	for rddp@ietf.org; Tue, 02 Mar 2004 03:32:24 -0500
Received: from mx01.netapp.com ([198.95.226.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay5Ji-0006VJ-00
	for rddp@ietf.org; Tue, 02 Mar 2004 03:31:54 -0500
Received: from hawk.corp.netapp.com (hawk [10.57.156.122])
	by mx01.netapp.com (8.12.10/8.12.10/NTAP-1.4) with ESMTP id i228VOJC017800;
	Tue, 2 Mar 2004 00:31:24 -0800 (PST)
Received: from svlexc01.hq.netapp.com (svlexc01.corp.netapp.com [10.10.22.171])
	by hawk.corp.netapp.com (8.12.9/8.12.9/NTAP-1.5) with ESMTP id i228VN8L006402;
	Tue, 2 Mar 2004 00:31:23 -0800 (PST)
Received: from tmt.netapp.com ([10.97.6.31]) by silver.hq.netapp.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 2 Mar 2004 03:31:16 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C40030.BA76E200"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
Subject: Re: [rddp] RDDP status of drafts
Date: Tue, 2 Mar 2004 00:28:40 -0800
Message-ID: <6.0.3.0.2.20040302032316.01c51488@silver.nane.netapp.com>
Thread-Topic: [rddp] RDDP status of drafts
Thread-Index: AcQAMLui5b6N+3E4RoSPEAdoWYDb6w==
From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
To: <Black_David@emc.com>, "Renato Recio" <recio@us.ibm.com>
Cc: <rddp@ietf.org>
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

------_=_NextPart_001_01C40030.BA76E200
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I believe there are some in-progress edits on the RDMAP
authors' plate, but the document wasn't resubmitted before
the meeting. Renato, can you confirm?

Tom.

At 03:12 AM 3/2/2004, Black_David@emc.com wrote:
>Here's what the WG chair believes the current status of
>drafts in the RDDP WG to be (if anything seems wrong here,
>please let me know):
>
>IETF RDDP WG Draft Status - March 2004, Seoul IETF meetings
>-----------------------------------------------------------
>
>-- Problem Statement and Architecture
>
>draft-ietf-rddp-problem-statement-03.txt
>draft-ietf-rddp-arch-04.txt
>
>To become Informational RFCs.
>
>Finished WG Last Call, and have been revised to respond to comments
>from our Area Director.  Further IESG discussion has generated
>additional comments that will require further revisions.
>
>-- Main Protocols
>
>DDP (draft-ietf-rddp-ddp-02.txt)
>RDMAP (draft-ietf-rddp-rdmap-01.txt)
>
>To become Proposed Standard RFCs.
>
>No technical issues meriting substantial meeting time.  Waiting
>on security draft (which will probably generate revisions to
>the security considerations sections in these drafts)
>before going to WG Last Call
>
>-- Applicability Statement
>
>draft-ietf-rddp-applicability-01.txt
>
>To become an Informational RFC.
>
>Believed to be in good shape - please review.
>
>-- SCTP Mapping
>
>draft-ietf-rddp-sctp-00.txt
>
>To become a Proposed Standard RFC.
>
>Despite the -00 version number, this is the fourth version of this =
draft,
>and
>it is relatively mature.
>
>-- TCP Mapping
>
>draft-ietf-rddp-mpa-00.txt
>
>To become an Informational RFC.
>
>The major open issues in this draft involve connection initiation/
>startup.  Substantial meeting time allocated to make progress.
>
>draft-cully-mpa-issuesresponses-00.txt
>
>Will not become an RFC.  This draft describes issues raised about
>MPA and the views of the MPA authors on those issues.
>
>-- Security
>
>draft-ietf-rddp-security-01.txt
>
>Whether this will be Informational vs. Proposed Standard is TBD.
>This draft is on the critical path to completing the DDP and RDMAP
>drafts.  Substantial meeting time has been allocated to it.
>
>
>_______________________________________________
>rddp mailing list
>rddp@ietf.org
>https://www1.ietf.org/mailman/listinfo/rddp


------_=_NextPart_001_01C40030.BA76E200
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6249.1">
<TITLE>Re: [rddp] RDDP status of drafts</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I believe there are some in-progress edits on the =
RDMAP</FONT>

<BR><FONT SIZE=3D2>authors' plate, but the document wasn't resubmitted =
before</FONT>

<BR><FONT SIZE=3D2>the meeting. Renato, can you confirm?</FONT>
</P>

<P><FONT SIZE=3D2>Tom.</FONT>
</P>

<P><FONT SIZE=3D2>At 03:12 AM 3/2/2004, Black_David@emc.com =
wrote:</FONT>

<BR><FONT SIZE=3D2>&gt;Here's what the WG chair believes the current =
status of</FONT>

<BR><FONT SIZE=3D2>&gt;drafts in the RDDP WG to be (if anything seems =
wrong here,</FONT>

<BR><FONT SIZE=3D2>&gt;please let me know):</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;IETF RDDP WG Draft Status - March 2004, Seoul =
IETF meetings</FONT>

<BR><FONT =
SIZE=3D2>&gt;-----------------------------------------------------------<=
/FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;-- Problem Statement and Architecture</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;draft-ietf-rddp-problem-statement-03.txt</FONT>

<BR><FONT SIZE=3D2>&gt;draft-ietf-rddp-arch-04.txt</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;To become Informational RFCs.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;Finished WG Last Call, and have been revised to =
respond to comments</FONT>

<BR><FONT SIZE=3D2>&gt;from our Area Director.&nbsp; Further IESG =
discussion has generated</FONT>

<BR><FONT SIZE=3D2>&gt;additional comments that will require further =
revisions.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;-- Main Protocols</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;DDP (draft-ietf-rddp-ddp-02.txt)</FONT>

<BR><FONT SIZE=3D2>&gt;RDMAP (draft-ietf-rddp-rdmap-01.txt)</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;To become Proposed Standard RFCs.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;No technical issues meriting substantial meeting =
time.&nbsp; Waiting</FONT>

<BR><FONT SIZE=3D2>&gt;on security draft (which will probably generate =
revisions to</FONT>

<BR><FONT SIZE=3D2>&gt;the security considerations sections in these =
drafts)</FONT>

<BR><FONT SIZE=3D2>&gt;before going to WG Last Call</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;-- Applicability Statement</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;draft-ietf-rddp-applicability-01.txt</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;To become an Informational RFC.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;Believed to be in good shape - please =
review.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;-- SCTP Mapping</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;draft-ietf-rddp-sctp-00.txt</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;To become a Proposed Standard RFC.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;Despite the -00 version number, this is the =
fourth version of this draft,</FONT>

<BR><FONT SIZE=3D2>&gt;and</FONT>

<BR><FONT SIZE=3D2>&gt;it is relatively mature.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;-- TCP Mapping</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;draft-ietf-rddp-mpa-00.txt</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;To become an Informational RFC.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;The major open issues in this draft involve =
connection initiation/</FONT>

<BR><FONT SIZE=3D2>&gt;startup.&nbsp; Substantial meeting time allocated =
to make progress.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;draft-cully-mpa-issuesresponses-00.txt</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;Will not become an RFC.&nbsp; This draft =
describes issues raised about</FONT>

<BR><FONT SIZE=3D2>&gt;MPA and the views of the MPA authors on those =
issues.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;-- Security</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;draft-ietf-rddp-security-01.txt</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;Whether this will be Informational vs. Proposed =
Standard is TBD.</FONT>

<BR><FONT SIZE=3D2>&gt;This draft is on the critical path to completing =
the DDP and RDMAP</FONT>

<BR><FONT SIZE=3D2>&gt;drafts.&nbsp; Substantial meeting time has been =
allocated to it.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT =
SIZE=3D2>&gt;_______________________________________________</FONT>

<BR><FONT SIZE=3D2>&gt;rddp mailing list</FONT>

<BR><FONT SIZE=3D2>&gt;rddp@ietf.org</FONT>

<BR><FONT SIZE=3D2>&gt;<A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/rddp">https://www1.ietf.or=
g/mailman/listinfo/rddp</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C40030.BA76E200--

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



From exim@www1.ietf.org  Tue Mar  2 12:03:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19340
	for <rddp-archive@odin.ietf.org>; Tue, 2 Mar 2004 12:03:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDI6-0007zm-DF
	for rddp-archive@odin.ietf.org; Tue, 02 Mar 2004 12:02:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i22H2kr9030733
	for rddp-archive@odin.ietf.org; Tue, 2 Mar 2004 12:02:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDI6-0007zE-69
	for rddp-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 12:02:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19335
	for <rddp-web-archive@ietf.org>; Tue, 2 Mar 2004 12:02:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDI4-0003SF-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 12:02:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyDHB-0003L2-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 12:01:50 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDGr-0003Cp-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 12:01:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDGc-0007bB-5H; Tue, 02 Mar 2004 12:01:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDG0-0007Oa-8i
	for rddp@optimus.ietf.org; Tue, 02 Mar 2004 12:00:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19257
	for <rddp@ietf.org>; Tue, 2 Mar 2004 12:00:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDFy-0003AG-00
	for rddp@ietf.org; Tue, 02 Mar 2004 12:00:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyDF1-00031P-00
	for rddp@ietf.org; Tue, 02 Mar 2004 11:59:35 -0500
Received: from thebe.your-site.com ([140.186.45.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDE6-0002na-00
	for rddp@ietf.org; Tue, 02 Mar 2004 11:58:39 -0500
Received: from [192.168.0.2] (64-144-5-25.client.dsl.net [64.144.5.25])
	by thebe.your-site.com (Postfix) with ESMTP
	id DBADB247232; Tue,  2 Mar 2004 11:47:11 -0500 (EST)
In-Reply-To: <B459CE1AFFC52D4688B2A5B842CA35EA7A5688@corpmx14.us.dg.com>
References: <B459CE1AFFC52D4688B2A5B842CA35EA7A5688@corpmx14.us.dg.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <129181D2-6C69-11D8-9E31-003065D48EE0@asomi.com>
Content-Transfer-Encoding: 7bit
Cc: rddp@ietf.org
From: Caitlin Bestler <cait@asomi.com>
Subject: Re: [rddp] RDDP status of drafts
Date: Tue, 2 Mar 2004 10:45:54 -0600
To: Black_David@emc.com
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: 7bit
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Mar 2, 2004, at 2:12 AM, Black_David@emc.com wrote:

> -- SCTP Mapping
>
> draft-ietf-rddp-sctp-00.txt
>
> To become a Proposed Standard RFC.
>
> Despite the -00 version number, this is the fourth version of this 
> draft,
> and it is relatively mature.

Earlier I raised the question as to whether the TCP and
SCTP adaptations should be brought into alignment on
support for Active-Active session initiation.

I believe the consensus from reflector discussion was that
it was not worthwhile to add this functionality to MPA/TCP.

I suggest a quick poll at the WG meeting and/or reflector as
to whether the Active-Active support should be removed from
the SCTP mapping. As that legal sessions are defined by an
enumeration of legal patterns, removing one is a very simple
edit should that be the consensus.

I personally remain ambivalent on the issue, seeing both the
merits of flexibility and of eliminating test cases.



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



From exim@www1.ietf.org  Tue Mar  2 12:23:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20285
	for <rddp-archive@odin.ietf.org>; Tue, 2 Mar 2004 12:23:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDbQ-0002pi-5Z
	for rddp-archive@odin.ietf.org; Tue, 02 Mar 2004 12:22:44 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i22HMin2010884
	for rddp-archive@odin.ietf.org; Tue, 2 Mar 2004 12:22:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDbQ-0002pM-0t
	for rddp-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 12:22:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20278
	for <rddp-web-archive@ietf.org>; Tue, 2 Mar 2004 12:22:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDbO-0006F3-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 12:22:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyDaZ-00067t-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 12:21:51 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDZo-0005zx-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 12:21:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDZn-0002jW-2J; Tue, 02 Mar 2004 12:21:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDZW-0002iV-LY
	for rddp@optimus.ietf.org; Tue, 02 Mar 2004 12:20:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20241
	for <rddp@ietf.org>; Tue, 2 Mar 2004 12:20:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDZV-0005yK-00
	for rddp@ietf.org; Tue, 02 Mar 2004 12:20:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyDYa-0005r4-00
	for rddp@ietf.org; Tue, 02 Mar 2004 12:19:49 -0500
Received: from thebe.your-site.com ([140.186.45.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDY8-0005jI-00
	for rddp@ietf.org; Tue, 02 Mar 2004 12:19:20 -0500
Received: from [192.168.0.2] (64-144-5-25.client.dsl.net [64.144.5.25])
	by thebe.your-site.com (Postfix) with ESMTP
	id 6EA1124A4D8; Tue,  2 Mar 2004 11:54:20 -0500 (EST)
In-Reply-To: <6.0.3.0.2.20040301224523.01b88340@silver.nane.netapp.com>
References: <6.0.3.0.2.20040301224523.01b88340@silver.nane.netapp.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <120C197E-6C6A-11D8-9E31-003065D48EE0@asomi.com>
Content-Transfer-Encoding: 7bit
Cc: "Jim Pinkerton" <jpink@windows.microsoft.com>, <rddp@ietf.org>
From: Caitlin Bestler <cait@asomi.com>
Subject: Re: [rddp] Comments on draft-ietf-rddp-security-01
Date: Tue, 2 Mar 2004 10:53:03 -0600
To: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: 7bit
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Mar 1, 2004, at 10:54 PM, Talpey, Thomas wrote:

>
> In the introduction, it seems critical to describe the scope of
>  possible damage if the trust is violated. I believe it is very
>  different depending on the resource which is the subject of
>  the trust. System-level damage should be described differently
>  from damage which merely :-) damages the application. This is
>  not a very specific recommendation, I know.
>
> I think there are differences between the trust model as described
>  here, and a privileged/nonprivileged application (at the end of
>  the Introduction). It might be worthwhile to bring these out.
>  For example, the trust model seems primarily oriented at wire-based
>  attacks, while the privileged/nonprivileged application is a local
>  matter? What interaction do these have?
>

I think the key here is advising the developer to consider the
scope of vulnerability that any successful attack would expose.

It is one thing to trust your peer if the worst thing your peer
can do is corrupt a single session that exists only to provide
services to that peer. It is quite another thing to trust your
peer if you are a kernel daemon with full root privileges to
the entire file system and access to all of physical memory.

The wide the scope of damage that your application can do when
compromised the more important it is that you *only* enable
RNIC access *precisely* to the extent required. At the opposite
extreme a daemon which fetched content for any requester and
only supported a single client per daemon instance could be
quite liberal in its exposure of its own memory.


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



From exim@www1.ietf.org  Tue Mar  2 12:43:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20832
	for <rddp-archive@odin.ietf.org>; Tue, 2 Mar 2004 12:43:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDum-0004OT-Iq
	for rddp-archive@odin.ietf.org; Tue, 02 Mar 2004 12:42:44 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i22HgiR1016886
	for rddp-archive@odin.ietf.org; Tue, 2 Mar 2004 12:42:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDum-0004OH-At
	for rddp-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 12:42:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20824
	for <rddp-web-archive@ietf.org>; Tue, 2 Mar 2004 12:42:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDuk-0000q7-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 12:42:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyDtq-0000j8-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 12:41:46 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDt8-0000bZ-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 12:41:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDt8-0004Fm-Jy; Tue, 02 Mar 2004 12:41:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyDsq-0004Ea-KX
	for rddp@optimus.ietf.org; Tue, 02 Mar 2004 12:40:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20789
	for <rddp@ietf.org>; Tue, 2 Mar 2004 12:40:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDsp-0000al-00
	for rddp@ietf.org; Tue, 02 Mar 2004 12:40:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyDrx-0000U4-00
	for rddp@ietf.org; Tue, 02 Mar 2004 12:39:50 -0500
Received: from email-out2.iomega.com ([147.178.1.83] helo=email.iomega.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyDrZ-0000MR-00
	for rddp@ietf.org; Tue, 02 Mar 2004 12:39:25 -0500
Received: from royntex03.iomegacorp.com (unknown [147.178.90.122])
	by email.iomega.com (Postfix) with ESMTP
	id 9C3742517; Tue,  2 Mar 2004 10:38:49 -0700 (MST)
Received: from sdontex01.iomegacorp.com ([147.178.169.12]) by royntex03.iomegacorp.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 2 Mar 2004 10:38:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.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] RDDP status of drafts
Date: Tue, 2 Mar 2004 09:38:48 -0800
Message-ID: <BD1BC124E179504395C7305EC78E47DC75A7DB@sdontex01.iomegacorp.com>
Thread-Topic: [rddp] RDDP status of drafts
Thread-Index: AcQAeE6LOVcVUQBxSdqeLzF8Fw0X0QABBaHg
From: "Sukanta Ganguly" <ganguly@iomega.com>
To: "Caitlin Bestler" <cait@asomi.com>, <Black_David@emc.com>
Cc: <rddp@ietf.org>
X-OriginalArrivalTime: 02 Mar 2004 17:38:49.0577 (UTC) FILETIME=[38B8E590:01C4007D]
Content-Transfer-Encoding: quoted-printable
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Caitlin,
   Even though for the consensus I will say that it is OK to remove the
TCP SCTP adaptation for the Active-Active requirements, I still think it
is worth the effort to probably have a separate effort in defining those
elements for Active-Active model and also a mix of an active-active and
an active-passive for a good failover solution that can be coined in
this area.
   The more I think about the more it makes sense to have some sort of a
standardization in this area for a "near-zero packet loss architecture"
to be defined under this arena. This may become a generic mechanism so
that can it can applied to a non-rdma space too.

Thanks
SG


-----Original Message-----
From: Caitlin Bestler [mailto:cait@asomi.com]=20
Sent: Tuesday, March 02, 2004 8:46 AM
To: Black_David@emc.com
Cc: rddp@ietf.org
Subject: Re: [rddp] RDDP status of drafts


On Mar 2, 2004, at 2:12 AM, Black_David@emc.com wrote:

> -- SCTP Mapping
>
> draft-ietf-rddp-sctp-00.txt
>
> To become a Proposed Standard RFC.
>
> Despite the -00 version number, this is the fourth version of this=20
> draft,
> and it is relatively mature.

Earlier I raised the question as to whether the TCP and
SCTP adaptations should be brought into alignment on
support for Active-Active session initiation.

I believe the consensus from reflector discussion was that
it was not worthwhile to add this functionality to MPA/TCP.

I suggest a quick poll at the WG meeting and/or reflector as
to whether the Active-Active support should be removed from
the SCTP mapping. As that legal sessions are defined by an
enumeration of legal patterns, removing one is a very simple
edit should that be the consensus.

I personally remain ambivalent on the issue, seeing both the
merits of flexibility and of eliminating test cases.



_______________________________________________
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 exim@www1.ietf.org  Tue Mar  2 21:10:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20774
	for <rddp-archive@odin.ietf.org>; Tue, 2 Mar 2004 21:10:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyLpe-0007xN-0Q
	for rddp-archive@odin.ietf.org; Tue, 02 Mar 2004 21:09:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2329vpM030581
	for rddp-archive@odin.ietf.org; Tue, 2 Mar 2004 21:09:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyLpd-0007xA-MJ
	for rddp-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 21:09:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20741
	for <rddp-web-archive@ietf.org>; Tue, 2 Mar 2004 21:09:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyLpb-0005Qp-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 21:09:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyLog-0005IB-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 21:09:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyLnn-0005A3-00
	for rddp-web-archive@ietf.org; Tue, 02 Mar 2004 21:08:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyLnm-0007V7-Om; Tue, 02 Mar 2004 21:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyLmp-0007I7-QX
	for rddp@optimus.ietf.org; Tue, 02 Mar 2004 21:07:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20652
	for <rddp@ietf.org>; Tue, 2 Mar 2004 21:07:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyLmn-00051M-00
	for rddp@ietf.org; Tue, 02 Mar 2004 21:07:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyLlx-0004sZ-00
	for rddp@ietf.org; Tue, 02 Mar 2004 21:06:11 -0500
Received: from mx01.netapp.com ([198.95.226.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyLl8-0004aY-00
	for rddp@ietf.org; Tue, 02 Mar 2004 21:05:18 -0500
Received: from hawk.corp.netapp.com (hawk [10.57.156.122])
	by mx01.netapp.com (8.12.10/8.12.10/NTAP-1.4) with ESMTP id i2324iJC017081
	for <rddp@ietf.org>; Tue, 2 Mar 2004 18:04:44 -0800 (PST)
Received: from svlexc01.hq.netapp.com (svlexc01.corp.netapp.com [10.10.22.171])
	by hawk.corp.netapp.com (8.12.9/8.12.9/NTAP-1.5) with ESMTP id i2324i8L001629
	for <rddp@ietf.org>; Tue, 2 Mar 2004 18:04:44 -0800 (PST)
Received: from tmt.netapp.com ([10.58.52.209]) by silver.hq.netapp.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 2 Mar 2004 21:04:39 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C400C3.E2635580"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
Date: Tue, 2 Mar 2004 18:03:58 -0800
Message-ID: <6.0.3.0.2.20040302200752.01b3f848@silver.nane.netapp.com>
Thread-Topic: MPA Reject frame
Thread-Index: AcQAw+PFhRl/gL1EQHCPW72//adD2Q==
From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
To: <rddp@ietf.org>
Subject: [rddp] MPA Reject frame
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

------_=_NextPart_001_01C400C3.E2635580
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have a comment on an issue posted to the mailing list and
replied to in =
<http://www.ietf.org/internet-drafts/draft-culley-mpa-issueresponses-00.t=
xt>
(Pasted below for reference) The proposal was for an
explicit MPA reject frame, and the response argues that
this is not necessary.

This document, in effect, counters that "reject" is to be
an upper layer issue, that is, private data should carry the
rejection, followed by a connection close. This does not
address the proposal.

The desire is to provide a ULP *independent* mechanism to
support rejection of incoming MPA/RDDP connection requests.
Implementing explicit rejection in MPA requires only a single
bit in the MPA Request/Response header.

It's not at all practical to use a connection closure to indicate
reject, even after an MPA frame. MPA initiators cannot be
expected to wait for a connection closure during startup, nor
could they discern between MPA frames received prior to it,
should it occur.

To leave reject out of the MPA connection, and leave the
issue to upper layers, would invoke many ULP changes, and
wire-level incompatibilities. Incorporation of reject into MPA
is by far the better, and more interoperable, choice.

Tom.


>4  Adding a "rejected connection" bit
>
>   Arkady Kanevsky submitted a comment to the reflector, quoted
>   below:
>
>        The MPA draft now defines very nicely an Initiator/Responder
>        sequence. But it looks deficient for a broad set of ULPs.
>        Most of the client-server ULP uses two type of Responses:
>        "accept" and "reject". The MPA draft does not provide a way
>        to differentiate between these 2 responses.
>
>        Here is one example of an application use. One of the common
>        way the private data is used is to negotiate RDMA Read
>        credits for a connection to be used by RDDP. An Initiator
>        passes in private data a requested RDMA credits. Responder
>        either accepts a connection or rejects a request specifying
>        how many RDMA Read credits it can support.
>
>        Currently the Responder has 2 legal choices.
>        One it can terminate a connection.
>        This does not convey any information to the Initiator.
>
>        The second choice is to generate Responder Frame even though
>        RDMA Read credits requested can not be satisfied.
>        This will establish connection but it can not be used as
>        intended by the Initiator. Initiator can either tear down the
>        established stream mode connection or use connection with
>        Responder RDMA credits supported.
>
>        This is de-facto ULP protocol since Responder Frame will
>        include the RDMA Read credits it can support. On top of that
>        both sides have to agree on the action they will take.
>
>        While ULP can use a protocol over private data to
>        differentiate between accept and reject, given a commonality
>        of this semantic for ULPs we can use one bit from the
>        Reserved area of MPA frame for the Responder frame to
>        differentiate between accept and reject responses.
>
>        Proposal:
>
>        for Responder MPA frame the 1st Reserved bit to be used as
>        accept/reject bit. 0 for accept, 1 for reject.
>
>        The bit will be called Type (T) in figure 7 {of the MPA
>        draft}.
>
>
>   Arkady is mostly correct in his analysis, but he may have missed
>   one point; that is that the initiator has the opportunity and
>   right to examine the private data in the MPA Response Frame before
>   binding DDP to MPA.  It may either complete the connection setup
>   by binding DDP (for an "accepted" connection), or tear the
>   connection down (for a "rejected" connection).  It is also legal
>   for the responder to tear the connection down immediately after
>   sending a "rejected" MPA Response Frame.  In either case, no DDP
>   connection is actually established until both sides have seen the
>   private data in the MPA Response Frame.  In both cases the
>   initiator can get a "reason" for a rejected connection.  The
>   choice is up to the ULP and can be encoded into the response
>   private data just as easily as in a specific bit.
>
>        Note: it is also legal for the responder to tear down the TCP
>        connection before sending a response frame, although this
>        offers no opportunity to send a "rejected reason".  Again the
>        choice is up to the ULP.
>
>   Putting the accept/reject bit in a standard place would be useful
>   if MPA or another standard layer needed to examine that bit for
>   its own uses.  As currently defined, however, MPA must send
>   private data to the ULP for examination, and depends on the ULP
>   for the next step (continue or teardown).  So MPA could not do
>   anything with that bit other than pass it on to the ULP.
>
>   The author believes that defining an "accept/reject" bit is not
>   necessary, that the response private data allows all the room for
>   such information necessary (including more detailed reasons if the
>   ULP needs them).  Adding such a bit would also require adding
>   another input and output command parameter to the MPA ULP
>   interface which may be insufficient for many applications anyway.




------_=_NextPart_001_01C400C3.E2635580
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6249.1">
<TITLE>MPA Reject frame</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I have a comment on an issue posted to the mailing =
list and</FONT>

<BR><FONT SIZE=3D2>replied to in &lt;<A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-culley-mpa-issuerespons=
es-00.txt">http://www.ietf.org/internet-drafts/draft-culley-mpa-issueresp=
onses-00.txt</A>&gt;</FONT>

<BR><FONT SIZE=3D2>(Pasted below for reference) The proposal was for =
an</FONT>

<BR><FONT SIZE=3D2>explicit MPA reject frame, and the response argues =
that</FONT>

<BR><FONT SIZE=3D2>this is not necessary.</FONT>
</P>

<P><FONT SIZE=3D2>This document, in effect, counters that =
&quot;reject&quot; is to be</FONT>

<BR><FONT SIZE=3D2>an upper layer issue, that is, private data should =
carry the</FONT>

<BR><FONT SIZE=3D2>rejection, followed by a connection close. This does =
not</FONT>

<BR><FONT SIZE=3D2>address the proposal.</FONT>
</P>

<P><FONT SIZE=3D2>The desire is to provide a ULP *independent* mechanism =
to</FONT>

<BR><FONT SIZE=3D2>support rejection of incoming MPA/RDDP connection =
requests.</FONT>

<BR><FONT SIZE=3D2>Implementing explicit rejection in MPA requires only =
a single</FONT>

<BR><FONT SIZE=3D2>bit in the MPA Request/Response header.</FONT>
</P>

<P><FONT SIZE=3D2>It's not at all practical to use a connection closure =
to indicate</FONT>

<BR><FONT SIZE=3D2>reject, even after an MPA frame. MPA initiators =
cannot be</FONT>

<BR><FONT SIZE=3D2>expected to wait for a connection closure during =
startup, nor</FONT>

<BR><FONT SIZE=3D2>could they discern between MPA frames received prior =
to it,</FONT>

<BR><FONT SIZE=3D2>should it occur.</FONT>
</P>

<P><FONT SIZE=3D2>To leave reject out of the MPA connection, and leave =
the</FONT>

<BR><FONT SIZE=3D2>issue to upper layers, would invoke many ULP changes, =
and</FONT>

<BR><FONT SIZE=3D2>wire-level incompatibilities. Incorporation of reject =
into MPA</FONT>

<BR><FONT SIZE=3D2>is by far the better, and more interoperable, =
choice.</FONT>
</P>

<P><FONT SIZE=3D2>Tom.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt;4&nbsp; Adding a &quot;rejected connection&quot; =
bit</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; Arkady Kanevsky submitted a comment =
to the reflector, quoted</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; below:</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =
MPA draft now defines very nicely an Initiator/Responder</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
sequence. But it looks deficient for a broad set of ULPs.</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Most =
of the client-server ULP uses two type of Responses:</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;accept&quot; and &quot;reject&quot;. The MPA draft does not =
provide a way</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to =
differentiate between these 2 responses.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Here =
is one example of an application use. One of the common</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; way =
the private data is used is to negotiate RDMA Read</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
credits for a connection to be used by RDDP. An Initiator</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; passes =
in private data a requested RDMA credits. Responder</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; either =
accepts a connection or rejects a request specifying</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how =
many RDMA Read credits it can support.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Currently the Responder has 2 legal choices.</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; One it =
can terminate a connection.</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This =
does not convey any information to the Initiator.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =
second choice is to generate Responder Frame even though</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RDMA =
Read credits requested can not be satisfied.</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This =
will establish connection but it can not be used as</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
intended by the Initiator. Initiator can either tear down the</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
established stream mode connection or use connection with</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Responder RDMA credits supported.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This =
is de-facto ULP protocol since Responder Frame will</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
include the RDMA Read credits it can support. On top of that</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; both =
sides have to agree on the action they will take.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; While =
ULP can use a protocol over private data to</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
differentiate between accept and reject, given a commonality</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of =
this semantic for ULPs we can use one bit from the</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Reserved area of MPA frame for the Responder frame to</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
differentiate between accept and reject responses.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Proposal:</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for =
Responder MPA frame the 1st Reserved bit to be used as</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
accept/reject bit. 0 for accept, 1 for reject.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =
bit will be called Type (T) in figure 7 {of the MPA</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft}.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; Arkady is mostly correct in his =
analysis, but he may have missed</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; one point; that is that the =
initiator has the opportunity and</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; right to examine the private data in =
the MPA Response Frame before</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; binding DDP to MPA.&nbsp; It may =
either complete the connection setup</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; by binding DDP (for an =
&quot;accepted&quot; connection), or tear the</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; connection down (for a =
&quot;rejected&quot; connection).&nbsp; It is also legal</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; for the responder to tear the =
connection down immediately after</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; sending a &quot;rejected&quot; MPA =
Response Frame.&nbsp; In either case, no DDP</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; connection is actually established =
until both sides have seen the</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; private data in the MPA Response =
Frame.&nbsp; In both cases the</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; initiator can get a =
&quot;reason&quot; for a rejected connection.&nbsp; The</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; choice is up to the ULP and can be =
encoded into the response</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; private data just as easily as in a =
specific bit.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Note: =
it is also legal for the responder to tear down the TCP</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
connection before sending a response frame, although this</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; offers =
no opportunity to send a &quot;rejected reason&quot;.&nbsp; Again =
the</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; choice =
is up to the ULP.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; Putting the accept/reject bit in a =
standard place would be useful</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; if MPA or another standard layer =
needed to examine that bit for</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; its own uses.&nbsp; As currently =
defined, however, MPA must send</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; private data to the ULP for =
examination, and depends on the ULP</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; for the next step (continue or =
teardown).&nbsp; So MPA could not do</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; anything with that bit other than =
pass it on to the ULP.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; The author believes that defining an =
&quot;accept/reject&quot; bit is not</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; necessary, that the response private =
data allows all the room for</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; such information necessary =
(including more detailed reasons if the</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; ULP needs them).&nbsp; Adding such a =
bit would also require adding</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; another input and output command =
parameter to the MPA ULP</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; interface which may be insufficient =
for many applications anyway.</FONT>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C400C3.E2635580--

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



From exim@www1.ietf.org  Wed Mar  3 09:55:15 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01457
	for <rddp-archive@odin.ietf.org>; Wed, 3 Mar 2004 09:55:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyXln-0005sR-HF
	for rddp-archive@odin.ietf.org; Wed, 03 Mar 2004 09:54:47 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23EsleA022584
	for rddp-archive@odin.ietf.org; Wed, 3 Mar 2004 09:54:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyXln-0005sB-9f
	for rddp-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 09:54:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01439
	for <rddp-web-archive@ietf.org>; Wed, 3 Mar 2004 09:54:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyXll-0002rZ-00
	for rddp-web-archive@ietf.org; Wed, 03 Mar 2004 09:54:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyXkv-0002gL-00
	for rddp-web-archive@ietf.org; Wed, 03 Mar 2004 09:53:54 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyXk5-0002VV-00
	for rddp-web-archive@ietf.org; Wed, 03 Mar 2004 09:53:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyXk5-0005lh-4O; Wed, 03 Mar 2004 09:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyXje-0005kV-T5
	for rddp@optimus.ietf.org; Wed, 03 Mar 2004 09:52:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01301
	for <rddp@ietf.org>; Wed, 3 Mar 2004 09:52:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyXjb-0002RR-00
	for rddp@ietf.org; Wed, 03 Mar 2004 09:52:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyXiA-00026g-00
	for rddp@ietf.org; Wed, 03 Mar 2004 09:51:03 -0500
Received: from palrel12.hp.com ([156.153.255.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyXh4-0001rl-00
	for rddp@ietf.org; Wed, 03 Mar 2004 09:49:54 -0500
Received: from esmail.cup.hp.com (esmail.cup.hp.com [15.0.65.164])
	by palrel12.hp.com (Postfix) with ESMTP id DC57C1C01C89
	for <rddp@ietf.org>; Wed,  3 Mar 2004 06:49:29 -0800 (PST)
Received: from mk731915.cup.hp.com ([15.8.80.111])
	by esmail.cup.hp.com (8.11.1/8.8.6) with ESMTP id i23Edl023705
	for <rddp@ietf.org>; Wed, 3 Mar 2004 06:39:47 -0800 (PST)
Message-Id: <5.1.0.14.2.20040303064522.023c5ca0@15.13.130.73>
X-Sender: krause@15.13.130.73
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 03 Mar 2004 06:46:03 -0800
To: rddp@ietf.org
From: Michael Krause <krause@cup.hp.com>
Subject: RE: [rddp] RDDP status of drafts
In-Reply-To: <BD1BC124E179504395C7305EC78E47DC75A7DB@sdontex01.iomegacor
 p.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


Concur that removal is fine at this time.  If there is demonstrated need at 
later date, then an update can be generated.

Mike



At 09:38 AM 3/2/2004 -0800, Sukanta Ganguly wrote:
>Caitlin,
>    Even though for the consensus I will say that it is OK to remove the
>TCP SCTP adaptation for the Active-Active requirements, I still think it
>is worth the effort to probably have a separate effort in defining those
>elements for Active-Active model and also a mix of an active-active and
>an active-passive for a good failover solution that can be coined in
>this area.
>    The more I think about the more it makes sense to have some sort of a
>standardization in this area for a "near-zero packet loss architecture"
>to be defined under this arena. This may become a generic mechanism so
>that can it can applied to a non-rdma space too.
>
>Thanks
>SG
>
>
>-----Original Message-----
>From: Caitlin Bestler [mailto:cait@asomi.com]
>Sent: Tuesday, March 02, 2004 8:46 AM
>To: Black_David@emc.com
>Cc: rddp@ietf.org
>Subject: Re: [rddp] RDDP status of drafts
>
>
>On Mar 2, 2004, at 2:12 AM, Black_David@emc.com wrote:
>
> > -- SCTP Mapping
> >
> > draft-ietf-rddp-sctp-00.txt
> >
> > To become a Proposed Standard RFC.
> >
> > Despite the -00 version number, this is the fourth version of this
> > draft,
> > and it is relatively mature.
>
>Earlier I raised the question as to whether the TCP and
>SCTP adaptations should be brought into alignment on
>support for Active-Active session initiation.
>
>I believe the consensus from reflector discussion was that
>it was not worthwhile to add this functionality to MPA/TCP.
>
>I suggest a quick poll at the WG meeting and/or reflector as
>to whether the Active-Active support should be removed from
>the SCTP mapping. As that legal sessions are defined by an
>enumeration of legal patterns, removing one is a very simple
>edit should that be the consensus.
>
>I personally remain ambivalent on the issue, seeing both the
>merits of flexibility and of eliminating test cases.
>
>
>
>_______________________________________________
>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


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



From exim@www1.ietf.org  Mon Mar 15 10:05:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01106
	for <rddp-archive@odin.ietf.org>; Mon, 15 Mar 2004 10:05:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2teA-0007NU-6j
	for rddp-archive@odin.ietf.org; Mon, 15 Mar 2004 10:04:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2FF4sFF028360
	for rddp-archive@odin.ietf.org; Mon, 15 Mar 2004 10:04:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2teA-0007NL-2L
	for rddp-web-archive@optimus.ietf.org; Mon, 15 Mar 2004 10:04:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01068
	for <rddp-web-archive@ietf.org>; Mon, 15 Mar 2004 10:04:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2te7-0003t8-00
	for rddp-web-archive@ietf.org; Mon, 15 Mar 2004 10:04:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2tdE-0003n9-00
	for rddp-web-archive@ietf.org; Mon, 15 Mar 2004 10:03:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2tcL-0003h2-00
	for rddp-web-archive@ietf.org; Mon, 15 Mar 2004 10:03:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2tcL-0006NR-FF; Mon, 15 Mar 2004 10:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2tcD-0006Gw-ED
	for rddp@optimus.ietf.org; Mon, 15 Mar 2004 10:02:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00919
	for <rddp@ietf.org>; Mon, 15 Mar 2004 10:02:50 -0500 (EST)
From: Black_David@emc.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2tcB-0003dA-00
	for rddp@ietf.org; Mon, 15 Mar 2004 10:02:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2taL-0003Ux-00
	for rddp@ietf.org; Mon, 15 Mar 2004 10:00:57 -0500
Received: from maho3msx2.corp.emc.com ([128.221.11.32])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2tZU-0003I9-00
	for rddp@ietf.org; Mon, 15 Mar 2004 10:00:05 -0500
Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <GZRHNQFA>; Mon, 15 Mar 2004 09:59:33 -0500
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA7A56FB@corpmx14.us.dg.com>
To: rddp@ietf.org
Date: Mon, 15 Mar 2004 09:59:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [rddp] RDDP Seoul minutes coming
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

Everyone,

I apologize for the delay in publication of the Seoul
minutes.  Between travel and an untimely death in my
family, I've been delayed in getting them out - I hope
to get to them sometime this week.

Let me take the opportunity to set some expectations
and make some requests about the minutes when they appear.
Attendance in Seoul was significantly down from our usual,
but some important tentative conclusions appear to have
been reached.  In order to solidify the conclusions (or
change them if they are wrong), I'm going to request
that when the minutes appear, people respond to the minutes
*only* to correct errors or omissions regarding what
actually happened in Seoul.

Instead, I will take all of the important issues discussed
in Seoul and issue a separate email on each with the goal
of driving each one to closure (consensus call) on the list.
It is important that the issues receive list discussion, but
I want to try to structure the discussion so that it leads
to conclusions.

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
----------------------------------------------------


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



From exim@www1.ietf.org  Mon Mar 22 08:59:55 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24936
	for <rddp-archive@odin.ietf.org>; Mon, 22 Mar 2004 08:59:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Pxf-00034Y-9e
	for rddp-archive@odin.ietf.org; Mon, 22 Mar 2004 08:59:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MDxRLl011811
	for rddp-archive@odin.ietf.org; Mon, 22 Mar 2004 08:59:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Pxf-00034Q-3n
	for rddp-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 08:59:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24932
	for <rddp-web-archive@ietf.org>; Mon, 22 Mar 2004 08:59:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Pxd-0004Wi-00
	for rddp-web-archive@ietf.org; Mon, 22 Mar 2004 08:59:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Pwl-0004SJ-00
	for rddp-web-archive@ietf.org; Mon, 22 Mar 2004 08:58:32 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5PwH-0004NJ-00
	for rddp-web-archive@ietf.org; Mon, 22 Mar 2004 08:58:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5PwG-0002t4-TT; Mon, 22 Mar 2004 08:58:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Pvm-0002ro-76
	for rddp@optimus.ietf.org; Mon, 22 Mar 2004 08:57:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24857
	for <rddp@ietf.org>; Mon, 22 Mar 2004 08:57:28 -0500 (EST)
From: Black_David@emc.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Pvk-0004LN-00
	for rddp@ietf.org; Mon, 22 Mar 2004 08:57:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Puu-0004Ft-00
	for rddp@ietf.org; Mon, 22 Mar 2004 08:56:37 -0500
Received: from mxic2.corp.emc.com ([128.221.12.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Pu8-00044I-00
	for rddp@ietf.org; Mon, 22 Mar 2004 08:55:48 -0500
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <H1JWS2MB>; Mon, 22 Mar 2004 08:55:13 -0500
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA7A575C@corpmx14.us.dg.com>
To: rddp@ietf.org
Date: Mon, 22 Mar 2004 08:55:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [rddp] DRAFT Seoul minutes
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

Please respond to this message *only* to correct mistakes/
omissions about what happened in Seoul or to ask clarifying
questions.  There are five major issues (numbered in the minutes)
about which I will be sending out individual emails.  Please
wait for them before discussing these issues, as we need to
drive most of them to rough consensus on the list well before
the San Diego meeting in August, although the IPsec requirements
issue may be difficult.

Thanks,
--David

RDDP WG meeting minutes - DRAFT 
IETF-59, Seoul
March 3, 15:30-17:30
-------------------------------

Many thanks to Tom Talpey for taking these minutes.

The agenda was: 

- Agenda Bashing and Administrivia (5 min) 
        - Blue Sheets 
        - NOTE WELL 

- Status of drafts (5 min) 

- Applicability Statement (5 min) 
        (draft-ietf-rddp-applicability-01.txt) 

        Mostly a status update. 

- DDP and RDMAP drafts (10 min) 
        (draft-ietf-rddp-ddp-02.txt, draft-ietf-rddp-rdmap-01.txt) 

        Mostly a status update. 

- SCTP Mapping (5 min) 
        (draft-ietf-rddp-sctp-00.txt) 

        Despite the -00 version number, this is the fourth version 
        of this draft, and it is relatively mature. 

- TCP mapping (30 min) 
        (draft-ietf-rddp-mpa-00.txt, 
        draft-culley-mpa-issueresponses-00.txt) 

        The mpa-issueresponses draft is a separate draft from the 
        MPA authors describing issues raised in MPA and proposed approaches.


- Security (60 min) 
        (draft-ietf-rddp-security-01.txt) 

        Time allocated reflects the importance of progress on this draft. 

----- 

Agenda bashed - no changes 
Blue sheets, Note Wells, etc. 

- Status of drafts (David Black, WG chair): 

  Problem Statement, architecture documents are in IESG discussion. 
  Feedback from IESG is in-progress and docs will be revised. 

  Main protocols (DDP, RDMAP): No open issues. Changes are expected 
  in the Security Considerations, however. 

  Applicability Statement: Probably in good shape, but please take a 
  new look in light of current progress. 

  SCTP mapping: One open issue - need for active/active startup?
  The plan is to discuss this in context of MPA, and provide the
  same functionality via TCP and SCTP for consistency. This document
  will be a Proposed Standard RFC. 

  MPA (TCP mapping): Open issues revolve completely around startup, 
  not operation. To be discussed today. This document will be an 
  Informational RFC. 

  Security mapping: WG chair has consulted with Area Director - this
  will be a Proposed Standard RFC.  Because it covers endpoint behavior,
  it's appropriate for a standards draft. Also, the IPsec mapping is
  applicable to multiple transport protocols, so its text can and
  should be shared in a single RFC. 

- TCP Mapping (MPA) discussion. (David Black presenting for Paul Culley) 
  (see presentation C-MPA update040225.ppt) 

  (1) Fast FPDU return (responder need not wait for first pdu). 
  Tentative proposal: leave as-is (responder must wait). 
  No dissension in room.  This is not needed for client/server,
  as the server expects to wait for the client.  Need to take
  proposal to the list. 

  (2) Active/Active startup. Tentative proposal: leave as-is (no 
  support for active/active). No dissension in room. Note, no 
  known applications require it.  Need to take proposal to the list.

  (3) Rejected Connection bit. Dissension expressed, this leads to 
  interoperability issues because it forces a ULP to interpret private 
  data to figure out that the connection setup failed, and requires
  MPA to handle TCP close specially (more detail in mail to list).
  General agreement in room to include this bit. Further discussion: 

  Q: If MPA does not do "teardown", why is the bit needed to 
   free resources at MPA layer? 
  A: Practically speaking, implementations will allocate and free 
   resources in MPA (e.g. connection model in kernel), this enables 
   layering and better control. 
  A: The bit will prevent some timed-wait resource consumption issues,
   if used properly (this is about cooperating systems, not malicious
   resource consumption attacks).

  Rough consensus in room to include the bit. Take to list. 

  See presentation for other nits in-progress.

  NOTE: separate list consensus call emails will be sent to start and
      focus discussion on issues (1) thru (3).  Please wait for them!

- Security discussion (Ellen Deleganes): 
  (see presentation D-RDDP Security presentation 040302.ppt) 

  New author, Sara Bitan, joins Jim Pinkerton and Ellen. 

  What's new in -01. (Changes listed in the presentation.) 

  Main change, the document has been reorganized. This is in 
  response to comments, and all feedback is welcomed. 

  The term "Partial Trust" was changed - needed a crisper meaning. 
  Now called "Partial Mutual Trust". Defines a cooperative set of 
  streams.  Discussion: what does this mean? Concept seems better
  but the name is still problematic. Basically, it seems to define
  a set of assumptions that can allow simplification (efficiency) for 
  cooperative streams. Trusting that they will not attack one 
  another - but still protecting the server. 

  "Queue"-level granularity is new (and useful) new text. But, 
  the word "queue" may have to go, because the doc will be 
  normative. We can't assume a queue in normative text. Or, add 
  text such as "the use of the word 'queue' does not imply that
  this implementation actually contains a queue"... 

  New section - "security services for RDDP" - has a list of attacks 
  listed - good progress. 

  One issue in Security section - now mentions SSL. This will require 
  more text because of ordering issues. SSL is a bad match because 
  of its stream orientation. Also, is there an issue to check w/NFSv4 
  WG? Take to NFSv4 WG meeting next day.

  Section 9 - Should we require IPsec, and therefore implement 
  this section, or make it optional? Suggestion that it be made 
  "mandatory-to-implement, optional-to-use." It was observed that 
  IPS had a similar section because it needed it. Also, now that 
  there is the IKEv2 specification to refer to, the problem is no longer 
  so difficult to document. Go look at IKEv2 and new "Crypto Suites 
  draft" now entering Last Call. In this case, the section becomes 
  unnecessary, and an IKEv2 reference will be adequate. 

  (4) Core question: Should we say that IPsec is mandatory for RDDP? 
  Secondary question: What parts do we actually require? (IKEv2?) 
  Take to list! Also, take to NFSv4 WG the next day. (NFS has no 
  such requirement currently, and has its own RPCSEC_GSS security 
  support). 

  The mandatory security item generated significant discussion but was 
  highly inconclusive. It was observed that mandatory-to-implement 
  would be a significant enhancement to the review approval process. 

  Appendix A - remove or keep? No conclusion, but possibly best to remove? 
  May want to keep some of it - taxonomy, etc., which contains useful 
  raw material for a revised Summary section. Summary section: perhaps 
  have a "Clip and Save" list of MUSTs and SHOULDs, etc. 

  Partial placement text additions are still an open issue. (e.g. place
code, 
  via RDMA into a buffer, then attack the server in some other fashion to 
  run that code) Draft should note these as a risk and state that buffer
  overflow protection is actually stronger with RDMA, and why (byte-level
  protection with bounds).

  (5) Need to address "protection for shared RQ" problem. The security draft

  makes a "valiant" attempt to make it a ULP issue - but can't. Exhaustion 
  of receive buffers is a key attack. Is this the job of each and every ULP,

  or RDDP's? Probably the latter.  OTOH, there is general discomfort with
  specifying this in a fashion that would require checking it in the fast
  receive path (e.g., in a hardware-optimized implementation). 

  Scenario - server mis-implements resource management, bug in one 
  handler drags down others. E.g., a multiprotocol server with busted 
  filesystem component kills HTTP, etc. "Unsafe by design", i.e. RDDP 
  should not impose non-uniform controls. 

  The goal is to specify a functionality that is guaranteed to exist, 
  though possibly overridable given sufficient trust.  Absence of any
  required control here doesn't line up with the Partial Mutual Trust
  concept discussed earlier.
 
  Proposed approach: Require a default implementation of this protection,
  as part of the Privileged Resource Manager. Consumers can override it,
  but the base function is always provided.

  Does a similar situation exist for CQs? 
  (Response: yes, with suppressed completions, underprovision is desirable!)

  NOTE: separate list consensus call emails will be sent to start and
      focus discussion on issues (4) and (5).  Please wait for them!

---- 

At the end of the session, the Area Director commented he was glad to 
see significant work being done in meeting, and was pleased with the 
progress. 

<adjourns 17:05> 


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



From exim@www1.ietf.org  Wed Mar 24 10:40:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01587
	for <rddp-archive@odin.ietf.org>; Wed, 24 Mar 2004 10:40:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6AUL-0005a8-Vl
	for rddp-archive@odin.ietf.org; Wed, 24 Mar 2004 10:40:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OFeHZQ021452
	for rddp-archive@odin.ietf.org; Wed, 24 Mar 2004 10:40:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6AUL-0005Zv-OM
	for rddp-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 10:40:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01563
	for <rddp-web-archive@ietf.org>; Wed, 24 Mar 2004 10:40:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6AUJ-0004Oa-00
	for rddp-web-archive@ietf.org; Wed, 24 Mar 2004 10:40:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ASp-00047J-00
	for rddp-web-archive@ietf.org; Wed, 24 Mar 2004 10:38:46 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ARE-0003m6-00
	for rddp-web-archive@ietf.org; Wed, 24 Mar 2004 10:37:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ARB-0004tX-IX; Wed, 24 Mar 2004 10:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6AR6-0004s9-4J
	for rddp@optimus.ietf.org; Wed, 24 Mar 2004 10:36:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01171
	for <rddp@ietf.org>; Wed, 24 Mar 2004 10:36:52 -0500 (EST)
From: Black_David@emc.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6AR3-0003jq-00
	for rddp@ietf.org; Wed, 24 Mar 2004 10:36:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6AOH-00031h-00
	for rddp@ietf.org; Wed, 24 Mar 2004 10:34:08 -0500
Received: from mxic2.corp.emc.com ([128.221.12.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6AHD-0000uJ-00; Wed, 24 Mar 2004 10:26:43 -0500
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <HSHHQQ7G>; Wed, 24 Mar 2004 10:26:07 -0500
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA7A5795@corpmx14.us.dg.com>
To: rddp@ietf.org, minutes@ietf.org
Date: Wed, 24 Mar 2004 10:26:05 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [rddp] RDDP WG Seoul minutes
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

RDDP WG meeting minutes
IETF-59, Seoul
March 3, 15:30-17:30
-----------------------

Many thanks to Tom Talpey for taking these minutes.

The agenda was: 

- Agenda Bashing and Administrivia (5 min) 
        - Blue Sheets 
        - NOTE WELL 

- Status of drafts (5 min) 

- Applicability Statement (5 min) 
        (draft-ietf-rddp-applicability-01.txt) 

        Mostly a status update. 

- DDP and RDMAP drafts (10 min) 
        (draft-ietf-rddp-ddp-02.txt, draft-ietf-rddp-rdmap-01.txt) 

        Mostly a status update. 

- SCTP Mapping (5 min) 
        (draft-ietf-rddp-sctp-00.txt) 

        Despite the -00 version number, this is the fourth version 
        of this draft, and it is relatively mature. 

- TCP mapping (30 min) 
        (draft-ietf-rddp-mpa-00.txt, 
        draft-culley-mpa-issueresponses-00.txt) 

        The mpa-issueresponses draft is a separate draft from the 
        MPA authors describing issues raised in MPA and proposed approaches.


- Security (60 min) 
        (draft-ietf-rddp-security-01.txt) 

        Time allocated reflects the importance of progress on this draft. 

----- 

Agenda bashed - no changes 
Blue sheets, Note Wells, etc. 

- Status of drafts (David Black, WG chair): 

  Problem Statement, architecture documents are in IESG discussion. 
  Feedback from IESG is in-progress and docs will be revised. 

  Main protocols (DDP, RDMAP): No open issues. Changes are expected 
  in the Security Considerations, however. 

  Applicability Statement: Probably in good shape, but please take a 
  new look in light of current progress. 

  SCTP mapping: One open issue - need for active/active startup?
  The plan is to discuss this in context of MPA, and provide the
  same functionality via TCP and SCTP for consistency. This document
  will be a Proposed Standard RFC. 

  MPA (TCP mapping): Open issues revolve completely around startup, 
  not operation. To be discussed today. This document will be an 
  Informational RFC. 

  Security mapping: WG chair has consulted with Area Director - this
  will be a Proposed Standard RFC.  Because it covers endpoint behavior,
  it's appropriate for a standards draft. Also, the IPsec mapping is
  applicable to multiple transport protocols, so its text can and
  should be shared in a single RFC. 

- TCP Mapping (MPA) discussion. (David Black presenting for Paul Culley) 
  (see presentation C-MPA update040225.ppt) 

  (1) Fast FPDU return (responder need not wait for first pdu). 
  Tentative proposal: leave as-is (responder must wait). 
  No dissension in room.  This is not needed for client/server,
  as the server expects to wait for the client.  Need to take
  proposal to the list. 

  (2) Active/Active startup. Tentative proposal: leave as-is (no 
  support for active/active). No dissension in room.  Note, no 
  known applications require it.  Need to take proposal to the list.

  (3) Rejected Connection bit. Dissension expressed, this leads to 
  interoperability issues because it forces a ULP to interpret private 
  data to figure out that the connection setup failed, and requires
  MPA to handle TCP close specially (more detail in mail to list).
  Further discussion: 

  Q: If MPA does not do "teardown", why is the bit needed to 
   free resources at MPA layer? 
  A: Practically speaking, implementations will allocate and free 
   resources in MPA (e.g. connection model in kernel), this enables 
   layering and better control. 
  A: The bit will prevent some timed-wait resource consumption issues,
   if used properly (this is about cooperating systems, not malicious
   resource consumption attacks).

  Rough consensus in room to include the bit. Take to list. 

  See presentation for other nits in-progress (will be taken care
  of in next revision of draft).

  NOTE: separate list consensus call emails will be sent to start and
      focus discussion on issues (1) thru (3).  Please wait for them!

- Security discussion (Ellen Deleganes): 
  (see presentation D-RDDP Security presentation 040302.ppt) 

  New author, Sara Bitan, joins Jim Pinkerton and Ellen. 

  Main change, the document has been reorganized. This is in 
  response to comments, and all feedback is welcomed. 

  The term "Partial Trust" was changed - needed a crisper meaning. 
  Now called "Partial Mutual Trust". Defines a cooperative set of 
  streams.  Discussion: what does this mean? Concept seems better
  but the name is still problematic. Basically, it seems to define
  a set of assumptions that can allow simplification (efficiency) for 
  cooperative streams. Trusting that they will not attack one 
  another - but still protecting the server. 

  "Queue"-level granularity is new (and useful) text. But, 
  the word "queue" may have to go, because the doc will be 
  normative. We can't assume a queue in normative text. Or, add 
  text such as "the use of the word 'queue' does not imply that
  this implementation actually contains a queue"... 

  New section - "security services for RDDP" - has a list of attacks 
  listed - good progress. 

  One issue in Security section - now mentions SSL. This will require 
  more text because of ordering issues. SSL is a bad match because 
  of its stream orientation.

  Section 9 - Should we require IPsec, and therefore implement 
  this section, or make it optional? Suggestion that it be made 
  "mandatory-to-implement, optional-to-use." It was observed that 
  IPS had a similar section because it needed it. Also, now that 
  there is the IKEv2 specification to refer to, the problem is no longer 
  so difficult to document.  Look at IKEv2 and new "Cryptographic
  Algorithms for IKEv2" draft.  If these are used this section in
  the RDDP security draft may not be necessary, as an IKEv2
  reference will be adequate. 

  (4) Core question: Should we say that IPsec is mandatory for RDDP? 
  Secondary question: What parts do we actually require? (IKEv2?) 
  Take to list! Also, take to NFSv4 WG the next day. (NFS has no 
  such requirement currently, and has its own RPCSEC_GSS security 
  support). 

  The mandatory security item generated significant discussion but was 
  highly inconclusive. It was observed that mandatory-to-implement 
  would be a significant enhancement to the review approval process. 

  Appendix A - remove or keep? No conclusion, but possibly best to remove? 
  May want to keep some of it - taxonomy, etc., which contains useful 
  raw material for a revised Summary section. Summary section: perhaps 
  have a summarized list of MUST and SHOULD requirements, etc. 

  Partial placement text additions are an open issue. (e.g. place code, 
  via RDMA into a buffer, then attack the server in some other fashion to 
  run that code) Draft should note these as a risk and state that buffer
  overflow protection is actually stronger with RDMA, and why (byte-level
  protection with bounds).

  (5) Need to address "protection for shared RQ" problem. The security draft

  makes a "valiant" attempt to make it a ULP issue - but can't. Exhaustion 
  of receive buffers is a key attack. Is this the job of each and every ULP,

  or RDDP's? Probably the latter.  OTOH, there is general discomfort with
  specifying this in a fashion that would require checking it in the fast
  receive path (e.g., in hardware in a hardware-optimized implementation). 

  Scenario - server mis-implements resource management, bug in one 
  handler drags down others. E.g., a multiprotocol server with busted 
  filesystem component kills HTTP, etc. "Unsafe by design", i.e. RDDP 
  should not impose non-uniform controls. 

  The goal is to specify a functionality that is guaranteed to exist, 
  though possibly overridable given sufficient trust.  Absence of any
  required control here doesn't line up with the Partial Mutual Trust
  concept discussed earlier.
 
  Proposed approach: Require a default implementation of this protection,
  as part of the Privileged Resource Manager. Privileged protocols can
  override it, but the base function is always provided.

  Does a similar situation exist for CQs? 
  (Response: yes, with suppressed completions, underprovision is desirable!)

  NOTE: separate list consensus call emails will be sent to start and
      focus discussion on issues (4) and (5).  Please wait for them!

---- 

At the end of the session, the Area Director commented he was glad to 
see significant work being done in meeting, and was pleased with the 
progress. 

<adjourns 17:05> 


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



From exim@www1.ietf.org  Wed Mar 24 12:21:59 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07588
	for <rddp-archive@odin.ietf.org>; Wed, 24 Mar 2004 12:21:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6C4K-00011D-1b
	for rddp-archive@odin.ietf.org; Wed, 24 Mar 2004 12:21:32 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OHLWNs003915
	for rddp-archive@odin.ietf.org; Wed, 24 Mar 2004 12:21:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6C4J-000114-Tl
	for rddp-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 12:21:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07580
	for <rddp-web-archive@ietf.org>; Wed, 24 Mar 2004 12:21:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6C4I-00056g-00
	for rddp-web-archive@ietf.org; Wed, 24 Mar 2004 12:21:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6C3V-00052g-00
	for rddp-web-archive@ietf.org; Wed, 24 Mar 2004 12:20:41 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6C2q-0004xc-00
	for rddp-web-archive@ietf.org; Wed, 24 Mar 2004 12:20:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6C2r-0000tz-5k; Wed, 24 Mar 2004 12:20:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6C2B-0000qo-2S
	for rddp@optimus.ietf.org; Wed, 24 Mar 2004 12:19:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07431
	for <rddp@ietf.org>; Wed, 24 Mar 2004 12:19:16 -0500 (EST)
From: Black_David@emc.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6C29-0004sF-00
	for rddp@ietf.org; Wed, 24 Mar 2004 12:19:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6C1G-0004jE-00
	for rddp@ietf.org; Wed, 24 Mar 2004 12:18:23 -0500
Received: from mxic2.corp.emc.com ([128.221.12.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6C0M-0004ZU-00
	for rddp@ietf.org; Wed, 24 Mar 2004 12:17:26 -0500
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <HSHHQX9V>; Wed, 24 Mar 2004 12:16:46 -0500
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA7A579A@corpmx14.us.dg.com>
To: rddp@ietf.org
Date: Wed, 24 Mar 2004 12:16:44 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [rddp] MPA startup sequence issues (1) and (2)
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

This is the first of several emails whose goal is to achieve
mailing list consensus on issues discussed in Seoul.  This
email covers issues (1) and (2), which concern permissible
startup sequences for MPA.  The Seoul minutes say:

  (1) Fast FPDU return (responder need not wait for first pdu). 
  Tentative proposal: leave as-is (responder must wait). 
  No dissension in room.  This is not needed for client/server,
  as the server expects to wait for the client.  Need to take
  proposal to the list. 

  (2) Active/Active startup. Tentative proposal: leave as-is (no 
  support for active/active). No dissension in room.  Note, no 
  known applications require it.  Need to take proposal to the list.

For both of these issues, the rationale for not supporting
the expanded functionality (Fast FPDU return, Active/Active
startup) centers around practical issues for dual-stack
implementations.  draft-culley-mpa-issueresponses-00.txt
contains an extensive discussion of these implementations,
why they're of interest, and the difficulties that these
two features pose to that class of implementation, which
the WG clearly considers to be important.

In other words, this is a "what is reasonable to build
in practice" engineering rationale, as opposed to a "what
is possible in principle" design rationale, which is a good
way to go about making decisions in the IETF.  For the
purpose of starting discussion, since Caitlin Bestler is
the only person I can recall strongly advocating these
two features, I believe that there is rough consensus
not to support them (and hence also not to support them
in the SCTP mapping for consistency).

Not supporting these features means senders MUST NOT
attempt them, and they are an error case at the receiver
if they occur.

For further discussion ...

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
----------------------------------------------------

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



From exim@www1.ietf.org  Thu Mar 25 11:25:55 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05032
	for <rddp-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:25:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xfb-00005n-BI
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 11:25:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PGPRWW000349
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 11:25:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xfb-00005Y-3h
	for rddp-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 11:25:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05026
	for <rddp-web-archive@ietf.org>; Thu, 25 Mar 2004 11:25:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XfZ-0004rD-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 11:25:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Xeh-0004oc-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 11:24:31 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XeC-0004mB-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 11:24:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XeD-0008St-4f; Thu, 25 Mar 2004 11:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xdc-0008P0-Pj
	for rddp@optimus.ietf.org; Thu, 25 Mar 2004 11:23:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04920
	for <rddp@ietf.org>; Thu, 25 Mar 2004 11:23:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xdb-0004jn-00
	for rddp@ietf.org; Thu, 25 Mar 2004 11:23:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Xck-0004hg-00
	for rddp@ietf.org; Thu, 25 Mar 2004 11:22:30 -0500
Received: from mail.ttlc.net ([66.94.32.4] helo=lampreynetworks.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XcM-0004er-00
	for rddp@ietf.org; Thu, 25 Mar 2004 11:22:06 -0500
Received: from i8600 [64.222.186.225] by lampreynetworks.com with ESMTP
  (SMTPD32-7.07) id A73F18B2008C; Thu, 25 Mar 2004 11:22:23 -0500
From: "Barry Reinhold" <bbr@lampreynetworks.com>
To: "RDDP" <rddp@ietf.org>
Date: Thu, 25 Mar 2004 11:21:51 -0500
Message-ID: <001401c41285$4b289e40$467fa8c0@i8600>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [rddp] silent dropping of TCP segment
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

MPA clause 9, error semantics, states that an MPA aware TCP
implementation may silently drop a TCP segment when MPA detects a CRC
error. The goal of this TCP segment dropping would be to avoid forcing
the teardown of the stream by having TCP retransmit the segment.

However, clause 5.1.2 on page 11 requires that 

"The TCP layer MUST have committed to keeping each segment before it can
be passed to the MPA." 

I assume "committed" means that TCP ACKs the segment. Thus the segment
is ACKed before it is delivered to MPA. If this is the proper
understanding I don't see how "MPA" can silently drop a segment, since
by the time it can detect a CRC error TCP has already committed to it.

It is not clear to me why there is a "MUST" in clause 5.1.2. It would
seem desirable to allow MPA some control over when the ACK is to be
generated.

I would like to see the "MUST" removed from clause 5.1.2. 

Barry Reinhold
Lamprey Networks
bbr@lampreynetworks.com
(603) 868-8411
 




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



From exim@www1.ietf.org  Thu Mar 25 12:20:50 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08462
	for <rddp-archive@odin.ietf.org>; Thu, 25 Mar 2004 12:20:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YWk-0006N8-LK
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 12:20:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PHKMub024474
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 12:20:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YWj-0006MY-Dc
	for rddp-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 12:20:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08357
	for <rddp-web-archive@ietf.org>; Thu, 25 Mar 2004 12:20:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YWh-0001SF-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 12:20:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6YV2-00018j-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 12:18:37 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YTV-0000qJ-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 12:17:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YTV-00063U-Le; Thu, 25 Mar 2004 12:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YSy-00061M-AG
	for rddp@optimus.ietf.org; Thu, 25 Mar 2004 12:16:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07909
	for <rddp@ietf.org>; Thu, 25 Mar 2004 12:16:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YSw-0000jy-00
	for rddp@ietf.org; Thu, 25 Mar 2004 12:16:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6YRZ-0000Wi-00
	for rddp@ietf.org; Thu, 25 Mar 2004 12:15:02 -0500
Received: from ztxmail05.ztx.compaq.com ([161.114.1.209])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YQW-0000Jq-00
	for rddp@ietf.org; Thu, 25 Mar 2004 12:13:56 -0500
Received: from cceexg13.americas.cpqcorp.net (cceexg13.americas.cpqcorp.net [16.81.1.35])
	by ztxmail05.ztx.compaq.com (Postfix) with ESMTP
	id A5F65CCC8; Thu, 25 Mar 2004 11:13:25 -0600 (CST)
Received: from cceexc18.americas.cpqcorp.net ([16.81.1.4]) by cceexg13.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.6673);
	 Thu, 25 Mar 2004 11:13:25 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.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] silent dropping of TCP segment
Date: Thu, 25 Mar 2004 11:13:23 -0600
Message-ID: <4D027986353D1341ADA4F2A4F8A170762D470E47@cceexc18.americas.cpqcorp.net>
Thread-Topic: [rddp] silent dropping of TCP segment
Thread-Index: AcQShbAzCcwr0f3OTJ21LNRUzg9R7AABZKxA
From: "Culley, Paul" <paul.culley@hp.com>
To: "Barry Reinhold" <bbr@lampreynetworks.com>, "RDDP" <rddp@ietf.org>
X-OriginalArrivalTime: 25 Mar 2004 17:13:25.0275 (UTC) FILETIME=[7BAB1EB0:01C4128C]
Content-Transfer-Encoding: quoted-printable
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

The use of "committed" does not imply that a segment is acknowledged,
only that this is the one that will be kept (a future segment with the
same sequence numbers will not be passed to MPA).

Any implementation that intends to drop segments based on CRC errors,
must be sufficiently integrated with TCP to insure that such segments
are not acknowledged; and thus will be re-transmitted.

I don't think that just deleting the MUST is sufficient, since there are
other implications, (and I'm not sure I remember them all).  I'm open to
suggestions...

Paul R. Culley
HP Fellow
281-514-5543


> -----Original Message-----
> From: rddp-admin@ietf.org [mailto:rddp-admin@ietf.org] On=20
> Behalf Of Barry Reinhold
> Sent: Thursday, March 25, 2004 10:22 AM
> To: RDDP
> Subject: [rddp] silent dropping of TCP segment
>=20
>=20
> MPA clause 9, error semantics, states that an MPA aware TCP=20
> implementation may silently drop a TCP segment when MPA=20
> detects a CRC error. The goal of this TCP segment dropping=20
> would be to avoid forcing the teardown of the stream by=20
> having TCP retransmit the segment.
>=20
> However, clause 5.1.2 on page 11 requires that=20
>=20
> "The TCP layer MUST have committed to keeping each segment=20
> before it can be passed to the MPA."=20
>=20
> I assume "committed" means that TCP ACKs the segment. Thus=20
> the segment is ACKed before it is delivered to MPA. If this=20
> is the proper understanding I don't see how "MPA" can=20
> silently drop a segment, since by the time it can detect a=20
> CRC error TCP has already committed to it.
>=20
> It is not clear to me why there is a "MUST" in clause 5.1.2.=20
> It would seem desirable to allow MPA some control over when=20
> the ACK is to be generated.
>=20
> I would like to see the "MUST" removed from clause 5.1.2.=20
>=20
> Barry Reinhold
> Lamprey Networks
> bbr@lampreynetworks.com
> (603) 868-8411
> =20
>=20
>=20
>=20
>=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 exim@www1.ietf.org  Thu Mar 25 12:35:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09687
	for <rddp-archive@odin.ietf.org>; Thu, 25 Mar 2004 12:35:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YlN-0008Fq-CM
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 12:35:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PHZTK7031729
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 12:35:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YlN-0008Fg-8Q
	for rddp-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 12:35:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09649
	for <rddp-web-archive@ietf.org>; Thu, 25 Mar 2004 12:35:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YlL-0002jY-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 12:35:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6YkU-0002gH-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 12:34:35 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Yjv-0002d8-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 12:33:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Yjw-0008Ab-Cc; Thu, 25 Mar 2004 12:34:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YjH-00082m-IQ
	for rddp@optimus.ietf.org; Thu, 25 Mar 2004 12:33:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09504
	for <rddp@ietf.org>; Thu, 25 Mar 2004 12:33:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YjF-0002a8-00
	for rddp@ietf.org; Thu, 25 Mar 2004 12:33:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6YiH-0002Ve-00
	for rddp@ietf.org; Thu, 25 Mar 2004 12:32:18 -0500
Received: from sphere.barak.net.il ([212.150.48.98])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YhN-0002Q5-00
	for rddp@ietf.org; Thu, 25 Mar 2004 12:31:22 -0500
Received: from [192.168.122.42] ([82.166.6.94]) by sphere.barak.net.il
          (InterMail vK.4.04.00.00 201-232-137 license e5bc39f1001e7dfa47fa92d56cd12779)
          with ESMTP id <20040325173009.XSVL931.sphere@[82.166.6.94]>;
          Thu, 25 Mar 2004 19:30:09 +0200
In-Reply-To: <4D027986353D1341ADA4F2A4F8A170762D470E47@cceexc18.americas.cpqcorp.net>
References: <4D027986353D1341ADA4F2A4F8A170762D470E47@cceexc18.americas.cpqcorp.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <28337F8B-7E82-11D8-AD7B-000393814604@asomi.com>
Content-Transfer-Encoding: 7bit
Cc: "Barry Reinhold" <bbr@lampreynetworks.com>, "RDDP" <rddp@ietf.org>
From: Caitlin Bestler <cait@asomi.com>
Subject: Re: [rddp] silent dropping of TCP segment
Date: Thu, 25 Mar 2004 19:30:49 +0200
To: "Culley, Paul" <paul.culley@hp.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Mar 25, 2004, at 7:13 PM, Culley, Paul wrote:

> The use of "committed" does not imply that a segment is acknowledged,
> only that this is the one that will be kept (a future segment with the
> same sequence numbers will not be passed to MPA).
>
> Any implementation that intends to drop segments based on CRC errors,
> must be sufficiently integrated with TCP to insure that such segments
> are not acknowledged; and thus will be re-transmitted.
>
> I don't think that just deleting the MUST is sufficient, since there 
> are
> other implications, (and I'm not sure I remember them all).  I'm open 
> to
> suggestions...
>
> Paul R. Culley
> HP Fellow
> 281-514-5543

The way I've interpreted those clauses is that the TCP Layer
should only present a segment for placement that it has
*decided* to ack, and (as you state) will not be accepting
a further retransmission of.

The MPA driven "drop" essentially *reverses* that decision.

You could quibble about whether a decision that can be
overridden by MPA qualifies as "committed" or not. But
I believe the concept is fairly simply, it's just a matter of
agreeing on the right terms, or agreeing that the words
that are already there are compatible with what was meant.


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



From exim@www1.ietf.org  Thu Mar 25 13:11:15 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12064
	for <rddp-archive@odin.ietf.org>; Thu, 25 Mar 2004 13:11:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZJV-0004fO-TM
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 13:10:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PIAjnY017894
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 13:10:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZJT-0004dV-SE
	for rddp-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 13:10:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12033
	for <rddp-web-archive@ietf.org>; Thu, 25 Mar 2004 13:10:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZJH-0005Zi-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 13:10:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ZIU-0005Wh-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 13:09:43 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZHk-0005TF-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 13:08:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZHk-0004W2-UX; Thu, 25 Mar 2004 13:08:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZFO-00041o-Kb
	for rddp@optimus.ietf.org; Thu, 25 Mar 2004 13:06:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11798
	for <rddp@ietf.org>; Thu, 25 Mar 2004 13:06:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZFM-0005Hn-00
	for rddp@ietf.org; Thu, 25 Mar 2004 13:06:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ZET-00058R-00
	for rddp@ietf.org; Thu, 25 Mar 2004 13:05:34 -0500
Received: from palrel10.hp.com ([156.153.255.245])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZDZ-000508-00
	for rddp@ietf.org; Thu, 25 Mar 2004 13:04:37 -0500
Received: from esmail.cup.hp.com (esmail.cup.hp.com [15.0.65.164])
	by palrel10.hp.com (Postfix) with ESMTP id 074C41C027E3
	for <rddp@ietf.org>; Thu, 25 Mar 2004 10:04:37 -0800 (PST)
Received: from MK731916.cup.hp.com ([15.244.197.45])
	by esmail.cup.hp.com (8.9.3 (PHNE_29774)/8.8.6) with ESMTP id JAA12345
	for <rddp@ietf.org>; Thu, 25 Mar 2004 09:54:28 -0800 (PST)
Message-Id: <6.0.3.0.2.20040325095644.01eb0260@15.13.130.73>
X-Sender: krause@15.13.130.73
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Thu, 25 Mar 2004 10:02:47 -0800
To: "RDDP" <rddp@ietf.org>
From: Michael Krause <krause@cup.hp.com>
Subject: Re: [rddp] silent dropping of TCP segment
In-Reply-To: <001401c41285$4b289e40$467fa8c0@i8600>
References: <001401c41285$4b289e40$467fa8c0@i8600>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

At 08:21 AM 3/25/2004, Barry Reinhold wrote:
>MPA clause 9, error semantics, states that an MPA aware TCP
>implementation may silently drop a TCP segment when MPA detects a CRC
>error. The goal of this TCP segment dropping would be to avoid forcing
>the teardown of the stream by having TCP retransmit the segment.
>
>However, clause 5.1.2 on page 11 requires that
>
>"The TCP layer MUST have committed to keeping each segment before it can
>be passed to the MPA."
>
>I assume "committed" means that TCP ACKs the segment.

Yes.

>Thus the segment is ACKed before it is delivered to MPA.

In a well-layered implementation this is true.

>If this is the proper understanding I don't see how "MPA" can silently 
>drop a segment, since
>by the time it can detect a CRC error TCP has already committed to it.

Because it is not a well-layered implementation if an MPA-aware TCP 
implementation is used.  This has also been called a rototilled 
implementation in that a design might calculate the CRC, etc. while also 
calculating the checksums in parallel as the data arrives.   Such a design 
is making an optimization for performance reasons (don't have to scan the 
data twice) and therefore has an opportunity to detect the CRC within its 
implementation and not generate a TCP ACK.

>It is not clear to me why there is a "MUST" in clause 5.1.2. It would
>seem desirable to allow MPA some control over when the ACK is to be
>generated.

The specification assume a well-layered implementation from an architecture 
perspective (per the original charter discussions) and has normative text 
using only that perspective.

>I would like to see the "MUST" removed from clause 5.1.2.

I disagree per the logic provided above within this e-mail.

Mike


>Barry Reinhold
>Lamprey Networks
>bbr@lampreynetworks.com
>(603) 868-8411
>
>
>
>
>
>_______________________________________________
>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 exim@www1.ietf.org  Thu Mar 25 13:14:50 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12308
	for <rddp-archive@odin.ietf.org>; Thu, 25 Mar 2004 13:14:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZN0-00051S-IU
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 13:14:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PIEMRx019300
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 13:14:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZN0-00051C-D6
	for rddp-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 13:14:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12278
	for <rddp-web-archive@ietf.org>; Thu, 25 Mar 2004 13:14:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZMy-0005pd-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 13:14:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ZM3-0005lY-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 13:13:23 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZLC-0005iL-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 13:12:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZLE-0004jr-67; Thu, 25 Mar 2004 13:12:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZJR-0004dP-2A
	for rddp@optimus.ietf.org; Thu, 25 Mar 2004 13:10:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12021
	for <rddp@ietf.org>; Thu, 25 Mar 2004 13:10:28 -0500 (EST)
From: pat_thaler@agilent.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZJF-0005ZN-00
	for rddp@ietf.org; Thu, 25 Mar 2004 13:10:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ZIS-0005WA-00
	for rddp@ietf.org; Thu, 25 Mar 2004 13:09:40 -0500
Received: from msgbas1x.cos.agilent.com ([192.25.240.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZHT-0005Sb-00
	for rddp@ietf.org; Thu, 25 Mar 2004 13:08:39 -0500
Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237])
	by msgbas1x.cos.agilent.com (Postfix) with ESMTP
	id 21A6C27B02; Thu, 25 Mar 2004 11:08:34 -0700 (MST)
Received: from wcosbh22.cos.agilent.com (wcosbh22.cos.agilent.com [130.29.152.178])
	by relcos2.cos.agilent.com (Postfix) with ESMTP
	id 0A705274; Thu, 25 Mar 2004 11:08:34 -0700 (MST)
Received: from wcosmb02.cos.agilent.com ([130.29.152.96]) by wcosbh22.cos.agilent.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 25 Mar 2004 11:08:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rddp] silent dropping of TCP segment
Date: Thu, 25 Mar 2004 11:08:26 -0700
Message-ID: <CA56AF7C40BC6540BA471AD2CC8F305709C660@wcosmb02.cos.agilent.com>
Thread-Topic: [rddp] silent dropping of TCP segment
Thread-Index: AcQShaPGKkSIMp5UTGKan3K3B+PmHgADUaiQ
To: <bbr@lampreynetworks.com>, <rddp@ietf.org>
X-OriginalArrivalTime: 25 Mar 2004 18:08:33.0279 (UTC) FILETIME=[2F6478F0:01C41294]
Content-Transfer-Encoding: quoted-printable
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

The reason there is a MUST in the statement from 5.1.2 is that we want =
to ensure that once MPA validates a segment and passes it to DDP that it =
won't get that segment from TCP again.=20

Committed meant a commitment to MPA and not an ACK. In DDP and RDMAP =
ordering rules, we assume that once the received data stream is complete =
to a given point that no placements from before that point will be made. =


The statement needs some clarification to allow an exception for the =
case where an MPA aware TCP learns that MPA dropped the segment due to a =
CRC error.

Regards,
Pat

-----Original Message-----
From: rddp-admin@ietf.org [mailto:rddp-admin@ietf.org]On Behalf Of Barry
Reinhold
Sent: Thursday, March 25, 2004 8:22 AM
To: RDDP
Subject: [rddp] silent dropping of TCP segment


MPA clause 9, error semantics, states that an MPA aware TCP
implementation may silently drop a TCP segment when MPA detects a CRC
error. The goal of this TCP segment dropping would be to avoid forcing
the teardown of the stream by having TCP retransmit the segment.

However, clause 5.1.2 on page 11 requires that=20

"The TCP layer MUST have committed to keeping each segment before it can
be passed to the MPA."=20

I assume "committed" means that TCP ACKs the segment. Thus the segment
is ACKed before it is delivered to MPA. If this is the proper
understanding I don't see how "MPA" can silently drop a segment, since
by the time it can detect a CRC error TCP has already committed to it.

It is not clear to me why there is a "MUST" in clause 5.1.2. It would
seem desirable to allow MPA some control over when the ACK is to be
generated.

I would like to see the "MUST" removed from clause 5.1.2.=20

Barry Reinhold
Lamprey Networks
bbr@lampreynetworks.com
(603) 868-8411
=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 exim@www1.ietf.org  Thu Mar 25 13:36:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13124
	for <rddp-archive@odin.ietf.org>; Thu, 25 Mar 2004 13:36:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZiK-00081i-Uc
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 13:36:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PIaObI030850
	for rddp-archive@odin.ietf.org; Thu, 25 Mar 2004 13:36:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZiK-00081V-Pl
	for rddp-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 13:36:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13094
	for <rddp-web-archive@ietf.org>; Thu, 25 Mar 2004 13:36:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZiI-00071Q-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 13:36:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ZhJ-0006yB-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 13:35:22 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZgN-0006vF-00
	for rddp-web-archive@ietf.org; Thu, 25 Mar 2004 13:34:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZgN-0007ns-G0; Thu, 25 Mar 2004 13:34:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZeS-0007ez-U4
	for rddp@optimus.ietf.org; Thu, 25 Mar 2004 13:32:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12920
	for <rddp@ietf.org>; Thu, 25 Mar 2004 13:32:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZeQ-0006lV-00
	for rddp@ietf.org; Thu, 25 Mar 2004 13:32:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ZdP-0006hX-00
	for rddp@ietf.org; Thu, 25 Mar 2004 13:31:19 -0500
Received: from angel.barak.net.il ([212.150.48.109])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZcS-0006cb-00
	for rddp@ietf.org; Thu, 25 Mar 2004 13:30:20 -0500
Received: from [192.168.122.42] ([82.166.6.94]) by angel.barak.net.il
          (InterMail vK.4.04.00.03 201-232-140-20030416 license e5bc39f1001e7dfa47fa92d56cd12779)
          with ESMTP id <20040325182854.YPUW1069.angel@[82.166.6.94]>;
          Thu, 25 Mar 2004 20:28:54 +0200
In-Reply-To: <001401c41285$4b289e40$467fa8c0@i8600>
References: <001401c41285$4b289e40$467fa8c0@i8600>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <63676680-7E8A-11D8-AD7B-000393814604@asomi.com>
Content-Transfer-Encoding: 7bit
Cc: "RDDP" <rddp@ietf.org>
From: Caitlin Bestler <cait@asomi.com>
Subject: Re: [rddp] silent dropping of TCP segment
Date: Thu, 25 Mar 2004 20:29:44 +0200
To: "Barry Reinhold" <bbr@lampreynetworks.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Mar 25, 2004, at 6:21 PM, Barry Reinhold wrote:

>
> It is not clear to me why there is a "MUST" in clause 5.1.2. It would
> seem desirable to allow MPA some control over when the ACK is to be
> generated.
>
> I would like to see the "MUST" removed from clause 5.1.2.
>

As noted previously, clarifying that the MPA layer MAY be able to
reverse a prior dtermination by the TCP layer that a segment was
valid might be worthwhile.

But simply dropping the language is the wrong way to do it.
There are two important constraints that I believe the same
language is part of:

a) the TCP layer MUST NOT pass duplicate segments to the
MPA layer multiple times (shifting the responsiblity for detecting
duplicates up a layer).

b) a rototilled implementation MUST NOT attempt to do "cut
through" placing. It cannot be a DDP Segment until *after*
it is a valid TCP Segment or SCTP Data Chunk.



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



From exim@www1.ietf.org  Fri Mar 26 08:21:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18628
	for <rddp-archive@odin.ietf.org>; Fri, 26 Mar 2004 08:21:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6rGe-0003Xp-9X
	for rddp-archive@odin.ietf.org; Fri, 26 Mar 2004 08:21:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QDL0Y8013621
	for rddp-archive@odin.ietf.org; Fri, 26 Mar 2004 08:21:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6rGe-0003Xc-1f
	for rddp-web-archive@optimus.ietf.org; Fri, 26 Mar 2004 08:21:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18605
	for <rddp-web-archive@ietf.org>; Fri, 26 Mar 2004 08:20:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6rGc-0001WE-00
	for rddp-web-archive@ietf.org; Fri, 26 Mar 2004 08:20:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6rFh-0001NV-00
	for rddp-web-archive@ietf.org; Fri, 26 Mar 2004 08:20:02 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6rEj-0001EB-00
	for rddp-web-archive@ietf.org; Fri, 26 Mar 2004 08:19:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6rEj-0003MH-2Z; Fri, 26 Mar 2004 08:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6rE8-0003L2-2p
	for rddp@optimus.ietf.org; Fri, 26 Mar 2004 08:18:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18504
	for <rddp@ietf.org>; Fri, 26 Mar 2004 08:18:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6rE7-00019a-00
	for rddp@ietf.org; Fri, 26 Mar 2004 08:18:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6rDM-00011t-00
	for rddp@ietf.org; Fri, 26 Mar 2004 08:17:37 -0500
Received: from mail.ttlc.net ([66.94.32.4] helo=lampreynetworks.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6rCf-0000sc-00
	for rddp@ietf.org; Fri, 26 Mar 2004 08:16:53 -0500
Received: from i8600 [64.222.186.225] by lampreynetworks.com with ESMTP
  (SMTPD32-7.07) id AD584DA9014A; Fri, 26 Mar 2004 08:17:12 -0500
From: "Barry Reinhold" <bbr@lampreynetworks.com>
To: "RDDP" <rddp@ietf.org>
Date: Fri, 26 Mar 2004 08:16:39 -0500
Message-ID: <006501c41334$9628cd20$467fa8c0@i8600>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [rddp] iWARP Association conference call - March 31st 1:30 PM EST (1.5 hrs)
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Event: iWARP Association conference call

Purpose: 
To see if there is sufficient interest to justify 
the establishment of a "light weight" association that 
will address iWARP conformance and interoperability testing needs. 

Time and Date: 
March 31st, 1:30 PM EST (anticipated time 1.5 hrs)

Call number/code: To obtain the call number/code 
email your request to bbr@lampreynetworks.com. 

Background:
The availability of detailed conformance suites and effective venues
for interoperability testing can provide a reduction in the market
acceptance cycle of a technology. Historically, conformance tests
for new technologies have become available only after a significant
number of products are already in the market place,
limiting their effectiveness. The goal of this effort is to establish
an industry wide association that will enable the timely
development of conformance test suites and interoperability procedures.
 
In discussions over the past month with a number
of different developers within the iWARP community a set
of primary objectives surfaced, as well as some secondary
objectives. Based on these objectives an initial proposal for
a "light weight" association is presented along with the
anticipated services it would offer. This is intended to be
a starting point for discussion, not a fixed proposal.
 
Primary Objectives: (Appeared to be common across most parties)

The development of timely conformance like tests that will foster
a common understanding of the standard, and enhance interoperability. 
The tests would be designed to help engineering and QA teams 
perform design verification work and would not be structured as 
a "logo" program.  (See not on logo program below)

To enable "effective" interoperability testing, such that developers 
have more options to test against other products in a simple manner.

Secondary Objectives: (These are additional areas of interest expressed
by
different individuals during calls over the past month. They are listed
as 
secondary objectives in that a smaller number of people have express
interest.)

Address the need to increase market awareness of iWARP in an effort to 
reduce the potential entrenchment of current technologies (technology
marketing).

Development and maintenance of an open source implementation of the
iWARP protocol stack.

Establish a common API (DAPL) by which test tools could interface 
with implementations and drive  move involved test processes. 

Establishment of an open and independent logo testing suite


Proposed Structure - The iWARP Association is proposed as a
non-incorporated
entity which organization can join by signing a document that outlines
the basic
rights and responsibilities of the signing parties. The legal and
financial 
transactions, though outlined in "the document", would be between
individual
organizations and a service provider. The association is envisioned
as a limited time entity that creates the necessary technology and
processes for iWARP testing and then is either transformed into a
more formal industry trade association or terminated depending on
perceived value and needs as the technology matures. This model is
along the same lines as the RDMA consortium.

Anticipated services/deliverables to be provided: (initial list)

iWARP conformance test specification - A document containing a complete
list of conformance statements from the iWARP specifications
(rdma, ddp, mpa, others?), along with the associated assertions and
test algorithms. This document would be the basis by which an interested
party could implement an iWARP conformance test suite. The document
would provide a openly reviewed specification detailing how to test a
device
for iWARP conformance.

An implementation of the test suite on some tool - The iWARP conformance
test specification is designed to encourage vendors interested in
creating
iWARP test tools to implement the detailed conformance tests. However,
since commercial vendors may not see sufficient market demand for the
product in the desired time frame, an implementation of the test suite
will
be done (if needed). 

A conformance test service - The primary goal of this effort is to
create
the infrastructure that will allow multiple labs to provide iWARP
testing.
However, a 3rd party testing service will be provided until these
services
can be easily obtained elsewhere.

Organization and running of periodic interoperability test events -
These are
standard "plugfest" type events where products are brought to a common
location and tested in a "community" setting. 

iWARP interoperability Net  - A Virtual Private Network that enables
members to achieve a level of interoperability testing on an ad-hoc
basis
without having to leave their own labs.

Member Involvement - The association is anticipated to be "light weight"
in
terms of the amount of time and resources a member is required to invest
in it.
However, members who wish to address some of the secondary objectives
outlined above may choose to form task forces within the context of the
association.

Cost Structure - A multilevel cost structure is envisioned that allows
companies
to participate at different cost points. All memberships would allow
participation
in interoperability events, additional costs would be associated with
test services
and the test tool.

Other Organizational Structures
Trade Association - An incorporated entity with a board of directors
that would
address a wider range of issues related to iWARP technology. Examples
are the
FCIA and the IBTA.

Agenda for the conference call:
1. Roll call
2. Presentation of the vision
3. Open discussion of the proposed objective and structure
4. Discussion of any additional concerns
5. Defining next steps

Objectives:
1.To obtain sufficient "sense of direction" that a small team of people
would be able to put together a detailed proposal for an iWARP
association
that addresses costs associated with different services.
2. To establish a date for a second conference call or organizational
meeting.

 


Barry Reinhold
Lamprey Networks
bbr@lampreynetworks.com
(603) 868-8411
 




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



From exim@www1.ietf.org  Fri Mar 26 15:57:50 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14482
	for <rddp-archive@odin.ietf.org>; Fri, 26 Mar 2004 15:57:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6yOH-0004DR-QZ
	for rddp-archive@odin.ietf.org; Fri, 26 Mar 2004 15:57:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2QKvLKx016205
	for rddp-archive@odin.ietf.org; Fri, 26 Mar 2004 15:57:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6yOH-0004DI-LA
	for rddp-web-archive@optimus.ietf.org; Fri, 26 Mar 2004 15:57:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14462
	for <rddp-web-archive@ietf.org>; Fri, 26 Mar 2004 15:57:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6yOF-0006Pg-00
	for rddp-web-archive@ietf.org; Fri, 26 Mar 2004 15:57:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6yNW-0006MV-00
	for rddp-web-archive@ietf.org; Fri, 26 Mar 2004 15:56:35 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6yMz-0006Hu-00
	for rddp-web-archive@ietf.org; Fri, 26 Mar 2004 15:56:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6yMz-00045D-27; Fri, 26 Mar 2004 15:56:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6yMC-00044L-2I
	for rddp@optimus.ietf.org; Fri, 26 Mar 2004 15:55:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14305
	for <rddp@ietf.org>; Fri, 26 Mar 2004 15:55:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6yMA-0006DY-00
	for rddp@ietf.org; Fri, 26 Mar 2004 15:55:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6yLD-00069i-00
	for rddp@ietf.org; Fri, 26 Mar 2004 15:54:13 -0500
Received: from mx01.netapp.com ([198.95.226.53])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6yKH-000636-00
	for rddp@ietf.org; Fri, 26 Mar 2004 15:53:13 -0500
Received: from frejya.corp.netapp.com (frejya [10.57.157.119])
	by mx01.netapp.com (8.12.10/8.12.10/NTAP-1.4) with ESMTP id i2QKqhZh003924
	for <rddp@ietf.org>; Fri, 26 Mar 2004 12:52:43 -0800 (PST)
Received: from svlexc01.hq.netapp.com (svlexc01.corp.netapp.com [10.57.156.135])
	by frejya.corp.netapp.com (8.12.9/8.12.9/NTAP-1.5) with ESMTP id i2QKqgbc001381
	for <rddp@ietf.org>; Fri, 26 Mar 2004 12:52:43 -0800 (PST)
Received: from tmt.netapp.com ([10.97.6.39]) by silver.hq.netapp.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 26 Mar 2004 15:52:40 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C41374.46E89C00"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
Subject: Re: [rddp] MPA startup sequence issues (1) and (2)
Date: Fri, 26 Mar 2004 12:51:50 -0800
Message-ID: <6.0.3.0.2.20040326154759.01c4fd88@silver.nane.netapp.com>
Thread-Topic: [rddp] MPA startup sequence issues (1) and (2)
Thread-Index: AcQTdEdG5KuLh0zJRIGhOURe2lp3cw==
From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
To: <rddp@ietf.org>
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

------_=_NextPart_001_01C41374.46E89C00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Okay, I'll bite! :-)

Both the proposed behaviors are appropriate and the spec
should retain them. There is no present motivation which
warrants the added complexity they would entail.

Tom.

At 12:16 PM 3/24/2004, Black_David@emc.com wrote:
>This is the first of several emails whose goal is to achieve
>mailing list consensus on issues discussed in Seoul.  This
>email covers issues (1) and (2), which concern permissible
>startup sequences for MPA.  The Seoul minutes say:
>
>  (1) Fast FPDU return (responder need not wait for first pdu).=20
>  Tentative proposal: leave as-is (responder must wait).=20
>  No dissension in room.  This is not needed for client/server,
>  as the server expects to wait for the client.  Need to take
>  proposal to the list.=20
>
>  (2) Active/Active startup. Tentative proposal: leave as-is (no=20
>  support for active/active). No dissension in room.  Note, no=20
>  known applications require it.  Need to take proposal to the list.
>
>For both of these issues, the rationale for not supporting
>the expanded functionality (Fast FPDU return, Active/Active
>startup) centers around practical issues for dual-stack
>implementations.  draft-culley-mpa-issueresponses-00.txt
>contains an extensive discussion of these implementations,
>why they're of interest, and the difficulties that these
>two features pose to that class of implementation, which
>the WG clearly considers to be important.
>
>In other words, this is a "what is reasonable to build
>in practice" engineering rationale, as opposed to a "what
>is possible in principle" design rationale, which is a good
>way to go about making decisions in the IETF.  For the
>purpose of starting discussion, since Caitlin Bestler is
>the only person I can recall strongly advocating these
>two features, I believe that there is rough consensus
>not to support them (and hence also not to support them
>in the SCTP mapping for consistency).
>
>Not supporting these features means senders MUST NOT
>attempt them, and they are an error case at the receiver
>if they occur.
>
>For further discussion ...
>
>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
>----------------------------------------------------
>
>_______________________________________________
>rddp mailing list
>rddp@ietf.org
>https://www1.ietf.org/mailman/listinfo/rddp


------_=_NextPart_001_01C41374.46E89C00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6249.1">
<TITLE>Re: [rddp] MPA startup sequence issues (1) and (2)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Okay, I'll bite! :-)</FONT>
</P>

<P><FONT SIZE=3D2>Both the proposed behaviors are appropriate and the =
spec</FONT>

<BR><FONT SIZE=3D2>should retain them. There is no present motivation =
which</FONT>

<BR><FONT SIZE=3D2>warrants the added complexity they would =
entail.</FONT>
</P>

<P><FONT SIZE=3D2>Tom.</FONT>
</P>

<P><FONT SIZE=3D2>At 12:16 PM 3/24/2004, Black_David@emc.com =
wrote:</FONT>

<BR><FONT SIZE=3D2>&gt;This is the first of several emails whose goal is =
to achieve</FONT>

<BR><FONT SIZE=3D2>&gt;mailing list consensus on issues discussed in =
Seoul.&nbsp; This</FONT>

<BR><FONT SIZE=3D2>&gt;email covers issues (1) and (2), which concern =
permissible</FONT>

<BR><FONT SIZE=3D2>&gt;startup sequences for MPA.&nbsp; The Seoul =
minutes say:</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp; (1) Fast FPDU return (responder need not =
wait for first pdu). </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp; Tentative proposal: leave as-is (responder =
must wait). </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp; No dissension in room.&nbsp; This is not =
needed for client/server,</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp; as the server expects to wait for the =
client.&nbsp; Need to take</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp; proposal to the list. </FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp; (2) Active/Active startup. Tentative =
proposal: leave as-is (no </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp; support for active/active). No dissension =
in room.&nbsp; Note, no </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp; known applications require it.&nbsp; Need =
to take proposal to the list.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;For both of these issues, the rationale for not =
supporting</FONT>

<BR><FONT SIZE=3D2>&gt;the expanded functionality (Fast FPDU return, =
Active/Active</FONT>

<BR><FONT SIZE=3D2>&gt;startup) centers around practical issues for =
dual-stack</FONT>

<BR><FONT SIZE=3D2>&gt;implementations.&nbsp; =
draft-culley-mpa-issueresponses-00.txt</FONT>

<BR><FONT SIZE=3D2>&gt;contains an extensive discussion of these =
implementations,</FONT>

<BR><FONT SIZE=3D2>&gt;why they're of interest, and the difficulties =
that these</FONT>

<BR><FONT SIZE=3D2>&gt;two features pose to that class of =
implementation, which</FONT>

<BR><FONT SIZE=3D2>&gt;the WG clearly considers to be important.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;In other words, this is a &quot;what is =
reasonable to build</FONT>

<BR><FONT SIZE=3D2>&gt;in practice&quot; engineering rationale, as =
opposed to a &quot;what</FONT>

<BR><FONT SIZE=3D2>&gt;is possible in principle&quot; design rationale, =
which is a good</FONT>

<BR><FONT SIZE=3D2>&gt;way to go about making decisions in the =
IETF.&nbsp; For the</FONT>

<BR><FONT SIZE=3D2>&gt;purpose of starting discussion, since Caitlin =
Bestler is</FONT>

<BR><FONT SIZE=3D2>&gt;the only person I can recall strongly advocating =
these</FONT>

<BR><FONT SIZE=3D2>&gt;two features, I believe that there is rough =
consensus</FONT>

<BR><FONT SIZE=3D2>&gt;not to support them (and hence also not to =
support them</FONT>

<BR><FONT SIZE=3D2>&gt;in the SCTP mapping for consistency).</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;Not supporting these features means senders MUST =
NOT</FONT>

<BR><FONT SIZE=3D2>&gt;attempt them, and they are an error case at the =
receiver</FONT>

<BR><FONT SIZE=3D2>&gt;if they occur.</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;For further discussion ...</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT SIZE=3D2>&gt;Thanks,</FONT>

<BR><FONT SIZE=3D2>&gt;--David</FONT>

<BR><FONT =
SIZE=3D2>&gt;----------------------------------------------------</FONT>

<BR><FONT SIZE=3D2>&gt;David L. Black, Senior Technologist</FONT>

<BR><FONT SIZE=3D2>&gt;EMC Corporation, 176 South St., Hopkinton, =
MA&nbsp; 01748</FONT>

<BR><FONT SIZE=3D2>&gt;+1 (508) =
293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; FAX: +1 (508) 293-7786</FONT>

<BR><FONT =
SIZE=3D2>&gt;black_david@emc.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; Mobile: +1 (978) 394-7754</FONT>

<BR><FONT =
SIZE=3D2>&gt;----------------------------------------------------</FONT>

<BR><FONT SIZE=3D2>&gt;</FONT>

<BR><FONT =
SIZE=3D2>&gt;_______________________________________________</FONT>

<BR><FONT SIZE=3D2>&gt;rddp mailing list</FONT>

<BR><FONT SIZE=3D2>&gt;rddp@ietf.org</FONT>

<BR><FONT SIZE=3D2>&gt;<A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/rddp">https://www1.ietf.or=
g/mailman/listinfo/rddp</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C41374.46E89C00--

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



From exim@www1.ietf.org  Sat Mar 27 23:02:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14601
	for <rddp-archive@odin.ietf.org>; Sat, 27 Mar 2004 23:02:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7RV6-0002ML-KW
	for rddp-archive@odin.ietf.org; Sat, 27 Mar 2004 23:02:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2S42K2I009061
	for rddp-archive@odin.ietf.org; Sat, 27 Mar 2004 23:02:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7RV3-0002Lz-KI
	for rddp-web-archive@optimus.ietf.org; Sat, 27 Mar 2004 23:02:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14596
	for <rddp-web-archive@ietf.org>; Sat, 27 Mar 2004 23:02:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7RV0-0004i3-00
	for rddp-web-archive@ietf.org; Sat, 27 Mar 2004 23:02:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7RU7-0004dS-00
	for rddp-web-archive@ietf.org; Sat, 27 Mar 2004 23:01:20 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7RTn-0004Xx-00
	for rddp-web-archive@ietf.org; Sat, 27 Mar 2004 23:00:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7RTo-0002JK-FK; Sat, 27 Mar 2004 23:01:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7RT6-0002IV-7C
	for rddp@optimus.ietf.org; Sat, 27 Mar 2004 23:00:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14544
	for <rddp@ietf.org>; Sat, 27 Mar 2004 23:00:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7RT2-0004WR-00
	for rddp@ietf.org; Sat, 27 Mar 2004 23:00:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7RS4-0004R3-00
	for rddp@ietf.org; Sat, 27 Mar 2004 22:59:13 -0500
Received: from enigma.barak.net.il ([212.150.48.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7RR9-0004Gd-00
	for rddp@ietf.org; Sat, 27 Mar 2004 22:58:15 -0500
Received: from [192.168.122.42] ([82.166.6.94]) by enigma.barak.net.il
          (InterMail vK.4.04.00.00 201-232-137 license e5bc39f1001e7dfa47fa92d56cd12779)
          with ESMTP id <20040328035717.XOA20514.enigma@[82.166.6.94]>
          for <rddp@ietf.org>; Sun, 28 Mar 2004 05:57:17 +0200
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <B459CE1AFFC52D4688B2A5B842CA35EA7A579A@corpmx14.us.dg.com>
References: <B459CE1AFFC52D4688B2A5B842CA35EA7A579A@corpmx14.us.dg.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0CC0CFE6-806C-11D8-8006-000393814604@asomi.com>
Content-Transfer-Encoding: 7bit
From: "Caitlin Bestler" <cait@asomi.com>
Subject: Re: [rddp] MPA startup sequence issues (1) and (2)
Date: Sun, 28 Mar 2004 05:57:36 +0200
To: RDDP <rddp@ietf.org>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Black_David@emc.com said:
> This is the first of several emails whose goal is to achieve
> mailing list consensus on issues discussed in Seoul.  This
> email covers issues (1) and (2), which concern permissible
> startup sequences for MPA.  The Seoul minutes say:
>
>   (1) Fast FPDU return (responder need not wait for first pdu).
>   Tentative proposal: leave as-is (responder must wait).
>   No dissension in room.  This is not needed for client/server,
>   as the server expects to wait for the client.  Need to take
>   proposal to the list.

The additional discussion that clarified the problem being finding
DDP Segments should probably be incorprated. The justification
giving initially was incorrect because it assume the active side
had not chosen an endpoint, when in fact it would typically
have done so. The problem is not in processing these DDP
Segments, its in finding them.

In any event, the class of application that I was concerned with
are "quick fetchers", such as a possible RDMA-HTTP server.
It has since occurred to me that the ULP for such servers
can solve the problem using the current specification by
simply having the side that is passive for TCP be the initiator
for MPA. This class of application will not typically need the
Private Data to select an Endpoint (care in selecting an Endpoint
is a characteristic of a connection that will last a long time,
not a get-in/get-out service).

>
>   (2) Active/Active startup. Tentative proposal: leave as-is (no
>   support for active/active). No dissension in room.  Note, no
>   known applications require it.  Need to take proposal to the list.
>

I'll make the change in the SCTP draft sometime in the next week
or so. I remain ambivalent on the issue. Technically it is not a
justifiable restriction. On the other hand it is not a needed
capability. The consensus seems to favor reducing the test
cases, which strikes me as a valid rationale.

In any event, when the one application that actually comes
along that needs it, we can at least say that we gave them
a chance to object.



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



From exim@www1.ietf.org  Sun Mar 28 16:03:17 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04647
	for <rddp-archive@odin.ietf.org>; Sun, 28 Mar 2004 16:03:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hQf-0006Y6-Tc
	for rddp-archive@odin.ietf.org; Sun, 28 Mar 2004 16:02:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2SL2njT025170
	for rddp-archive@odin.ietf.org; Sun, 28 Mar 2004 16:02:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hQf-0006Xt-Pq
	for rddp-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 16:02:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04638
	for <rddp-web-archive@ietf.org>; Sun, 28 Mar 2004 16:02:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hQe-0006HP-00
	for rddp-web-archive@ietf.org; Sun, 28 Mar 2004 16:02:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7hPg-000696-00
	for rddp-web-archive@ietf.org; Sun, 28 Mar 2004 16:01:49 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hOu-0005zR-00
	for rddp-web-archive@ietf.org; Sun, 28 Mar 2004 16:01:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hOv-0006Na-EL; Sun, 28 Mar 2004 16:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hOt-0006Mv-Kt
	for rddp@optimus.ietf.org; Sun, 28 Mar 2004 16:00:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04496
	for <rddp@ietf.org>; Sun, 28 Mar 2004 16:00:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hOr-0005yr-00
	for rddp@ietf.org; Sun, 28 Mar 2004 16:00:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7hNj-0005pl-00
	for rddp@ietf.org; Sun, 28 Mar 2004 15:59:48 -0500
Received: from e32.co.us.ibm.com ([32.97.110.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hMm-0005bj-00
	for rddp@ietf.org; Sun, 28 Mar 2004 15:58:48 -0500
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11])
	by e32.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i2SKwG0Y311840;
	Sun, 28 Mar 2004 15:58:16 -0500
Received: from d03nm115.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82])
	by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i2SKwCvr330250;
	Sun, 28 Mar 2004 13:58:16 -0700
In-Reply-To: <B459CE1AFFC52D4688B2A5B842CA35EA7A5795@corpmx14.us.dg.com>
To: Black_David@emc.com
Cc: rddp@ietf.org
MIME-Version: 1.0
Subject: Re: [rddp] RDDP WG Seoul minutes
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
From: John Hufferd <hufferd@us.ibm.com>
Message-ID: <OF65689339.EAB9940E-ON08256E65.00707353-08256E65.00720EB1@us.ibm.com>
Date: Sun, 28 Mar 2004 12:46:03 -0800
X-MIMETrack: Serialize by Router on D03NM115/03/M/IBM(Release 6.0.2CF2HF168 | December 5, 2003) at
 03/28/2004 13:58:15,
	Serialize complete at 03/28/2004 13:58:15
Content-Type: multipart/alternative; boundary="=_alternative 00720DB008256E65_="
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60

This is a multipart message in MIME format.
--=_alternative 00720DB008256E65_=
Content-Type: text/plain; charset="US-ASCII"

David,
In addition to the information you stated below:

 Section 9 - Should we require IPsec, and therefore implement 
  this section, or make it optional? Suggestion that it be made 
  "mandatory-to-implement, optional-to-use." It was observed that 
  IPS had a similar section because it needed it. Also, now that 
  there is the IKEv2 specification to refer to, the problem is no longer 
  so difficult to document.  Look at IKEv2 and new "Cryptographic
  Algorithms for IKEv2" draft.  If these are used this section in
  the RDDP security draft may not be necessary, as an IKEv2
  reference will be adequate. 

  (4) Core question: Should we say that IPsec is mandatory for RDDP? 
  Secondary question: What parts do we actually require? (IKEv2?) 
  Take to list! Also, take to NFSv4 WG the next day. (NFS has no 
  such requirement currently, and has its own RPCSEC_GSS security 
  support). 

  The mandatory security item generated significant discussion but was 
  highly inconclusive. It was observed that mandatory-to-implement 
  would be a significant enhancement to the review approval process. 

There also was a discussion about the additional touching/moving of data 
that would be required for things like RPCSEC_GSS security.  The 
discussion focused around: if IPSec was used then the 
cryptographic/encryption action could be taken before the data was placed 
so that no additional touching/moving of the data would be needed after 
the data was delivered.  Since the elimination of the extra 
movement/touching is the major focus of RDMA, it maybe seen as a sever 
reduction in the promises of RDMA to use anything other than IPSec to 
secure an interaction.

Anyway, this was also one of the conversation threads that we talked about 
bringing to the list for additional discussion.

.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/System Group, San Jose CA
Main Office: (408) 256-0403, Tie: 276-0403, eFax: (408) 904-4688
Alt Office: (408) 997-6136, Cell: (408) 499-9702
Internet Address: hufferd@us.ibm.com
--=_alternative 00720DB008256E65_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">David,</font>
<br><font size=2 face="sans-serif">In addition to the information you stated
below:</font>
<br>
<br><font size=2><tt>&nbsp;Section 9 - Should we require IPsec, and therefore
implement <br>
 &nbsp;this section, or make it optional? Suggestion that it be made <br>
 &nbsp;&quot;mandatory-to-implement, optional-to-use.&quot; It was observed
that <br>
 &nbsp;IPS had a similar section because it needed it. Also, now that <br>
 &nbsp;there is the IKEv2 specification to refer to, the problem is no
longer <br>
 &nbsp;so difficult to document. &nbsp;Look at IKEv2 and new &quot;Cryptographic<br>
 &nbsp;Algorithms for IKEv2&quot; draft. &nbsp;If these are used this section
in<br>
 &nbsp;the RDDP security draft may not be necessary, as an IKEv2<br>
 &nbsp;reference will be adequate. <br>
<br>
 &nbsp;(4) Core question: Should we say that IPsec is mandatory for RDDP?
<br>
 &nbsp;Secondary question: What parts do we actually require? (IKEv2?)
<br>
 &nbsp;Take to list! Also, take to NFSv4 WG the next day. (NFS has no <br>
 &nbsp;such requirement currently, and has its own RPCSEC_GSS security
<br>
 &nbsp;support). <br>
<br>
 &nbsp;The mandatory security item generated significant discussion but
was <br>
 &nbsp;highly inconclusive. It was observed that mandatory-to-implement
<br>
 &nbsp;would be a significant enhancement to the review approval process.
</tt></font>
<br>
<br><font size=2 face="sans-serif">There also was a discussion about the
additional touching/moving of data that would be required for things like
RPCSEC_GSS security. &nbsp;The discussion focused around: if IPSec was
used then the cryptographic/encryption action could be taken before the
data was placed so that no additional touching/moving of the data would
be needed after the data was delivered. &nbsp;Since the elimination of
the extra movement/touching is the major focus of RDMA, it maybe seen as
a sever reduction in the promises of RDMA to use anything other than IPSec
to secure an interaction.</font>
<br>
<br><font size=2 face="sans-serif">Anyway, this was also one of the conversation
threads that we talked about bringing to the list for additional discussion.</font>
<br>
<br><font size=2 face="sans-serif">.<br>
.<br>
John L. Hufferd<br>
Senior Technical Staff Member (STSM)<br>
IBM/System Group, San Jose CA<br>
Main Office: (408) 256-0403, Tie: 276-0403, eFax: (408) 904-4688<br>
Alt Office: (408) 997-6136, Cell: (408) 499-9702<br>
Internet Address: hufferd@us.ibm.com</font>
--=_alternative 00720DB008256E65_=--

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



From exim@www1.ietf.org  Mon Mar 29 10:42:15 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08860
	for <rddp-archive@odin.ietf.org>; Mon, 29 Mar 2004 10:42:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7ytY-000153-MD
	for rddp-archive@odin.ietf.org; Mon, 29 Mar 2004 10:41:49 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TFfmJ4004151
	for rddp-archive@odin.ietf.org; Mon, 29 Mar 2004 10:41:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7ytY-00014s-A1
	for rddp-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 10:41:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08849
	for <rddp-web-archive@ietf.org>; Mon, 29 Mar 2004 10:41:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7ytV-0005PC-00
	for rddp-web-archive@ietf.org; Mon, 29 Mar 2004 10:41:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7ysd-0005FL-00
	for rddp-web-archive@ietf.org; Mon, 29 Mar 2004 10:40:51 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7yro-00055W-00
	for rddp-web-archive@ietf.org; Mon, 29 Mar 2004 10:40:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yro-0000yH-OS; Mon, 29 Mar 2004 10:40:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yrM-0000uO-BG
	for rddp@optimus.ietf.org; Mon, 29 Mar 2004 10:39:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08723
	for <rddp@ietf.org>; Mon, 29 Mar 2004 10:39:28 -0500 (EST)
From: Black_David@emc.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7yrJ-00053C-00
	for rddp@ietf.org; Mon, 29 Mar 2004 10:39:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7yqS-0004uJ-00
	for rddp@ietf.org; Mon, 29 Mar 2004 10:38:37 -0500
Received: from mxic2.corp.emc.com ([128.221.12.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7ypY-0004dC-00
	for rddp@ietf.org; Mon, 29 Mar 2004 10:37:40 -0500
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <H41ANN81>; Mon, 29 Mar 2004 10:36:56 -0500
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA7A57E0@corpmx14.us.dg.com>
To: hufferd@us.ibm.com
Cc: rddp@ietf.org
Subject: RE: [rddp] RDDP WG Seoul minutes
Date: Mon, 29 Mar 2004 10:35:39 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

John,

> There also was a discussion about the additional touching/moving of data
> that would be required for things like RPCSEC_GSS security.  The
discussion
> focused around: if IPSec was used then the cryptographic/encryption action
> could be taken before the data was placed so that no additional
> touching/moving of the data would be needed after the data was delivered.
> Since the elimination of the extra movement/touching is the major focus
> of RDMA, it maybe seen as a sever reduction in the promises of RDMA to
> use anything other than IPSec to secure an interaction.

The minutes have been submitted.  That discussion was a bit on the
inconclusive side, in part because NFSv4 now has an RPCSEC_GSS mode
that assumes use of IPsec and hence does not secure the transmitted
data.  IMHO, the stronger case for IPsec over RPCSEC_GSS is that the
former can protect the RDDP headers (DDP, RDMAC), whereas the latter
cannot (assuming that we rule out some ugly passing of security info
from NFS down to RDDP).  Let me know if you want me to try to edit/change
the submitted minutes.

> Anyway, this was also one of the conversation threads that we talked
> about bringing to the list for additional discussion.

That will happen in the context of the IPsec requirements issue [(4) in
the minutes] that will be coming to the list ... although I'd like to try
to close out a few of the other issues before opening that Pandora's box ...

Thanks,
--David

-----Original Message-----
From: John Hufferd [mailto:hufferd@us.ibm.com] 
Sent: Sunday, March 28, 2004 3:46 PM
To: Black_David@emc.com
Cc: rddp@ietf.org
Subject: Re: [rddp] RDDP WG Seoul minutes



David, 
In addition to the information you stated below: 

 Section 9 - Should we require IPsec, and therefore implement 
 this section, or make it optional? Suggestion that it be made 
 "mandatory-to-implement, optional-to-use." It was observed that 
 IPS had a similar section because it needed it. Also, now that 
 there is the IKEv2 specification to refer to, the problem is no longer 
 so difficult to document.  Look at IKEv2 and new "Cryptographic
 Algorithms for IKEv2" draft.  If these are used this section in
 the RDDP security draft may not be necessary, as an IKEv2
 reference will be adequate. 

 (4) Core question: Should we say that IPsec is mandatory for RDDP? 
 Secondary question: What parts do we actually require? (IKEv2?) 
 Take to list! Also, take to NFSv4 WG the next day. (NFS has no 
 such requirement currently, and has its own RPCSEC_GSS security 
 support). 

 The mandatory security item generated significant discussion but was 
 highly inconclusive. It was observed that mandatory-to-implement 
 would be a significant enhancement to the review approval process. 

There also was a discussion about the additional touching/moving of data
that would be required for things like RPCSEC_GSS security.  The discussion
focused around: if IPSec was used then the cryptographic/encryption action
could be taken before the data was placed so that no additional
touching/moving of the data would be needed after the data was delivered.
Since the elimination of the extra movement/touching is the major focus of
RDMA, it maybe seen as a sever reduction in the promises of RDMA to use
anything other than IPSec to secure an interaction. 

Anyway, this was also one of the conversation threads that we talked about
bringing to the list for additional discussion. 

.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/System Group, San Jose CA
Main Office: (408) 256-0403, Tie: 276-0403, eFax: (408) 904-4688
Alt Office: (408) 997-6136, Cell: (408) 499-9702
Internet Address: hufferd@us.ibm.com

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



From exim@www1.ietf.org  Mon Mar 29 20:19:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07520
	for <rddp-archive@odin.ietf.org>; Mon, 29 Mar 2004 20:19:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B87u4-0004h2-CK
	for rddp-archive@odin.ietf.org; Mon, 29 Mar 2004 20:18:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U1IuQv018037
	for rddp-archive@odin.ietf.org; Mon, 29 Mar 2004 20:18:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B87u4-0004gq-6a
	for rddp-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 20:18:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07511
	for <rddp-web-archive@ietf.org>; Mon, 29 Mar 2004 20:18:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B87u2-0002hS-00
	for rddp-web-archive@ietf.org; Mon, 29 Mar 2004 20:18:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B87t1-0002Z0-00
	for rddp-web-archive@ietf.org; Mon, 29 Mar 2004 20:17:51 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B87sC-0002QM-00
	for rddp-web-archive@ietf.org; Mon, 29 Mar 2004 20:17:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B87sD-0004b3-Ix; Mon, 29 Mar 2004 20:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B87rz-0004Zs-1Y
	for rddp@optimus.ietf.org; Mon, 29 Mar 2004 20:16:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07400
	for <rddp@ietf.org>; Mon, 29 Mar 2004 20:16:44 -0500 (EST)
From: Black_David@emc.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B87rw-0002Od-00
	for rddp@ietf.org; Mon, 29 Mar 2004 20:16:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B87qy-0002F1-00
	for rddp@ietf.org; Mon, 29 Mar 2004 20:15:45 -0500
Received: from maho3msx2.corp.emc.com ([128.221.11.32])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B87py-0001zM-00
	for rddp@ietf.org; Mon, 29 Mar 2004 20:14:42 -0500
Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <H4D9Y5B5>; Mon, 29 Mar 2004 20:14:04 -0500
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA7A57F4@corpmx14.us.dg.com>
To: cait@asomi.com, rddp@ietf.org
Date: Mon, 29 Mar 2004 20:14:01 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [rddp] MPA  issues (1) and (2) - rough consensus
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

I'm going to go ahead and call consensus on these issues.  I
believe the rough consensus of the RDDP WG is that FAST FPDU
return (responder need not wait for first pdu) and Active/Active
startup are not to be added to the transport mappings (both
MPA and the SCTP mappings).  Both drafts should contain
language indicating that these design choices were considered
and rejected.  For Fast FPDU return, I think Caitlin's request
for some of this discussion is reasonable:

> The additional discussion that clarified the problem being finding
> DDP Segments should probably be incorporated. The justification
> giving initially was incorrect because it assume the active side
> had not chosen an endpoint, when in fact it would typically
> have done so. The problem is not in processing these DDP
> Segments, its in finding them.

I would ask the MPA authors to get Caitlin's approval for the
text that is added on this point.

Any further objections to this rough consensus should be posted
to the list.

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
----------------------------------------------------

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



From exim@www1.ietf.org  Mon Mar 29 20:26:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07895
	for <rddp-archive@odin.ietf.org>; Mon, 29 Mar 2004 20:26:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B880r-0005Mo-R2
	for rddp-archive@odin.ietf.org; Mon, 29 Mar 2004 20:25:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U1PvIY020624
	for rddp-archive@odin.ietf.org; Mon, 29 Mar 2004 20:25:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B880r-0005MZ-NX
	for rddp-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 20:25:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07873
	for <rddp-web-archive@ietf.org>; Mon, 29 Mar 2004 20:25:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B880p-0003kW-00
	for rddp-web-archive@ietf.org; Mon, 29 Mar 2004 20:25:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B87zr-0003cA-00
	for rddp-web-archive@ietf.org; Mon, 29 Mar 2004 20:24:56 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B87yz-0003Tv-00
	for rddp-web-archive@ietf.org; Mon, 29 Mar 2004 20:24:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B87z0-0005FI-FH; Mon, 29 Mar 2004 20:24:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B87yn-0005DI-Lp
	for rddp@optimus.ietf.org; Mon, 29 Mar 2004 20:23:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07773
	for <rddp@ietf.org>; Mon, 29 Mar 2004 20:23:47 -0500 (EST)
From: Black_David@emc.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B87yl-0003Re-00
	for rddp@ietf.org; Mon, 29 Mar 2004 20:23:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B87xo-0003IG-00
	for rddp@ietf.org; Mon, 29 Mar 2004 20:22:48 -0500
Received: from mxic2.corp.emc.com ([128.221.12.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B87wv-00031c-00
	for rddp@ietf.org; Mon, 29 Mar 2004 20:21:53 -0500
Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <H41A3KFY>; Mon, 29 Mar 2004 20:21:24 -0500
Message-ID: <B459CE1AFFC52D4688B2A5B842CA35EA7A57F5@corpmx14.us.dg.com>
To: rddp@ietf.org
Date: Mon, 29 Mar 2004 20:21:24 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [rddp] MPA issue (3): Rejected Connection bit
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

Moving on to issue (3), the Seoul minutes say:

  (3) Rejected Connection bit. Dissension expressed, this leads to 
  interoperability issues because it forces a ULP to interpret private 
  data to figure out that the connection setup failed, and requires
  MPA to handle TCP close specially (more detail in mail to list).
  Further discussion: 

  Q: If MPA does not do "teardown", why is the bit needed to 
   free resources at MPA layer? 
  A: Practically speaking, implementations will allocate and free 
   resources in MPA (e.g. connection model in kernel), this enables 
   layering and better control. 
  A: The bit will prevent some timed-wait resource consumption issues,
   if used properly (this is about cooperating systems, not malicious
   resource consumption attacks).

  Rough consensus in room to include the bit. Take to list.

I suggest to the WG that the right thing to do is include this bit
because it produces better behavior in an important error case for
cooperative clients where something is misconfigured.  This bit
allows the RDDP layers to immediately know that a connection setup
has failed and release/reuse any resources committed to it without
waiting for a ULP to look at the private data that came back.  It
also ties the fact that the connection is closing with the
associated private data unambiguously (both can be immediately
logged at RDDP level).  Yes, this is optimizing an error case,
but it seems to be common enough/of sufficient concern to be
worth spending a bit on.  That was where the discussion among
the subset of us who were in Seoul wound up.

Comments?  I intend to let the technical discussion run on this
before trying to call consensus on the list.

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
----------------------------------------------------


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



From exim@www1.ietf.org  Tue Mar 30 14:11:03 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05389
	for <rddp-archive@odin.ietf.org>; Tue, 30 Mar 2004 14:11:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8OdA-00044L-GU
	for rddp-archive@odin.ietf.org; Tue, 30 Mar 2004 14:10:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2UJAa6Y015637
	for rddp-archive@odin.ietf.org; Tue, 30 Mar 2004 14:10:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8OdA-000444-9r
	for rddp-web-archive@optimus.ietf.org; Tue, 30 Mar 2004 14:10:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05312
	for <rddp-web-archive@ietf.org>; Tue, 30 Mar 2004 14:10:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8Od7-00016f-00
	for rddp-web-archive@ietf.org; Tue, 30 Mar 2004 14:10:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8Obj-0000iR-00
	for rddp-web-archive@ietf.org; Tue, 30 Mar 2004 14:09:08 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8OZk-0000Jk-00
	for rddp-web-archive@ietf.org; Tue, 30 Mar 2004 14:07:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8OZg-0003J4-Ih; Tue, 30 Mar 2004 14:07:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8OZF-0003H4-R8
	for rddp@optimus.ietf.org; Tue, 30 Mar 2004 14:06:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05088
	for <rddp@ietf.org>; Tue, 30 Mar 2004 14:06:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8OZD-0000Ec-00
	for rddp@ietf.org; Tue, 30 Mar 2004 14:06:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8OYF-000068-00
	for rddp@ietf.org; Tue, 30 Mar 2004 14:05:31 -0500
Received: from mail.ttlc.net ([66.94.32.4] helo=lampreynetworks.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8OXN-0007lq-00
	for rddp@ietf.org; Tue, 30 Mar 2004 14:04:37 -0500
Received: from i8600 [64.222.186.225] by lampreynetworks.com with ESMTP
  (SMTPD32-7.07) id A4E0A5D8006A; Tue, 30 Mar 2004 14:05:04 -0500
From: "Barry Reinhold" <bbr@lampreynetworks.com>
To: "RDDP" <rddp@ietf.org>
Date: Tue, 30 Mar 2004 14:04:25 -0500
Message-ID: <002101c41689$d50e6ec0$467fa8c0@i8600>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [rddp] Reminder of initial conference call associated with starting iWARP test effort
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Event: Conference call discussing establishment of an organization to
drive iWARP conformance and interoperability issues.
Date: Wednesday March 31st
Time: 1:30 PM EST
Call Number/Participant code:  email bbr@lampreynetworks.com

Barry Reinhold
Lamprey Networks
bbr@lampreynetworks.com
(603) 868-8411
 




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



From exim@www1.ietf.org  Tue Mar 30 18:55:07 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07693
	for <rddp-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:55:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riw-0006WI-F7
	for rddp-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HFdOiO008921
	for rddp-archive@odin.ietf.org; Tue, 17 Feb 2004 10:39:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7Jj-0002IU-3T
	for rddp-web-archive@optimus.ietf.org; Tue, 17 Feb 2004 10:39:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06184
	for <rddp-web-archive@ietf.org>; Tue, 17 Feb 2004 10:39:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At7JX-0001GN-00
	for rddp-web-archive@ietf.org; Tue, 17 Feb 2004 10:39:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1At7IX-0001AS-00
	for rddp-web-archive@ietf.org; Tue, 17 Feb 2004 10:38:10 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1At7HZ-00015q-00
	for rddp-web-archive@ietf.org; Tue, 17 Feb 2004 10:37:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7HW-0001K2-LI; Tue, 17 Feb 2004 10:37:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1At7HM-0001EM-Kq
	for rddp@optimus.ietf.org; Tue, 17 Feb 2004 10:36:56 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05789;
	Tue, 17 Feb 2004 10:36:52 -0500 (EST)
Message-Id: <200402171536.KAA05789@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rddp@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 17 Feb 2004 10:36:52 -0500
Subject: [rddp] I-D ACTION:draft-ietf-rddp-ddp-02.txt,.pdf
Sender: rddp-admin@ietf.org
Errors-To: rddp-admin@ietf.org
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Id: IETF Remote Direct Data Placement (rddp) WG <rddp.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--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		: Direct Data Placement over Reliable Transports
	Author(s)	: H. Shah
	Filename	: draft-ietf-rddp-ddp-02.txt,.pdf
	Pages		: 37
	Date		: 2004-2-17
	
The Direct Data Placement protocol provides information to Place the 
incoming data directly into an upper layer protocol's receive buffer 
without intermediate buffers. This removes excess CPU and memory 
utilization associated with transferring data through the 
intermediate buffers.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ddp-02.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-ddp-02.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:	<2004-2-17104210.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rddp-ddp-02.txt

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

Content-Type: text/plain
Content-ID:	<2004-2-17104210.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



