From mailman-bounces@ietf.org  Sat Jan  1 05:57:22 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08791
	for <rddp-web-archive@ietf.org>; Sat, 1 Jan 2005 05:57:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ckh8V-00076R-LB
	for rddp-web-archive@ietf.org; Sat, 01 Jan 2005 06:09:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CkgEr-00074B-3U
	for rddp-web-archive@ietf.org; Sat, 01 Jan 2005 05:12:01 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: rddp-web-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.8702.1104573795.4100.mailman@lists.ietf.org>
Date: Sat, 01 Jan 2005 05:03:15 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for rddp-web-archive@ietf.org:

List                                     Password // URL
----                                     --------  
rddp@ietf.org                            jOsP      
https://www1.ietf.org/mailman/options/rddp/rddp-web-archive%40ietf.org


From rddp-bounces@ietf.org  Tue Jan  4 09:18:52 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13268
	for <rddp-web-archive@ietf.org>; Tue, 4 Jan 2005 09:18:52 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Clpin-00067Y-2u
	for rddp-web-archive@ietf.org; Tue, 04 Jan 2005 09:31:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClpSM-0001hD-63; Tue, 04 Jan 2005 09:14:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClpQr-00011e-Az
	for rddp@megatron.ietf.org; Tue, 04 Jan 2005 09:13:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12844
	for <rddp@ietf.org>; Tue, 4 Jan 2005 09:13:07 -0500 (EST)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ClpdC-00061i-V4
	for rddp@ietf.org; Tue, 04 Jan 2005 09:25:56 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.211); Tue, 4 Jan 2005 06:12:36 -0800
Received: from red-hub-03.redmond.corp.microsoft.com ([157.54.2.25]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 4 Jan 2005 06:12:26 -0800
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.84]) by red-hub-03.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1264); Tue, 4 Jan 2005 06:12:25 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com
	([157.54.12.81]) by
	win-imc-02.wingroup.windeploy.ntdev.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1289); Tue, 4 Jan 2005 06:12:35 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 4 Jan 2005 06:12:34 -0800
Message-ID: <E6564B8F86852D46A4E98C485FB33B8F0B7EDC19@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Terminate message a security threat?
Thread-Index: AcTyZ3AKaq0QGkKMQvyjhSJeLK+srg==
From: "Jim Pinkerton" <jpink@windows.microsoft.com>
To: "RDDP" <rddp@ietf.org>
X-OriginalArrivalTime: 04 Jan 2005 14:12:35.0312 (UTC)
	FILETIME=[7050E700:01C4F267]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Subject: [rddp] Terminate message a security threat?
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1569982775=="
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc

This is a multi-part message in MIME format.

--===============1569982775==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4F267.6FD91653"

This is a multi-part message in MIME format.

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

=20

To date the security ID doesn't discuss the Terminate Message. It was =
suggested to me by Mallikarjun as part of his detailed review that since =
all other messages are discussed, shouldn't Terminate be?=20

=20

In thinking this through, I don't believe this represents any new =
attacks. If the Remote Peer is sending you a Terminate Message, then =
that =BD of the Stream is terminated. So he just clobbered himself, but =
hasn't been able to affect any other connections - thus this is not a =
security issue. If a third party is able to inject a Terminate Message =
into the data stream, then it is a spoofing attack. The spoofing attack =
and mitigations are already discussed. So I think at best the Terminate =
Message could be added as an example of a spoofing attack, but honestly =
there are a ton of things the spoofer could do, so I'm not sure I'd =
revise the draft just to add another example.

=20

Does anyone see a hole in my reasoning?

=20

=20

Jim

=20

=20

=20


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

<html>

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

</head>

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

<div class=3DSection1>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>To date the security ID doesn&#8217;t discuss the =
Terminate Message.
It was suggested to me by Mallikarjun as part of his detailed review =
that since
all other messages are discussed, shouldn&#8217;t Terminate be? =
</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In thinking this through, I don&#8217;t believe this
represents any new attacks. If the Remote Peer is sending you a =
Terminate
Message, then that =BD of the Stream is terminated. So he just clobbered =
himself,
but hasn&#8217;t been able to affect any other connections &#8211; thus =
this is
not a security issue. If a third party is able to inject a Terminate =
Message
into the data stream, then it is a spoofing attack. The spoofing attack =
and
mitigations are already discussed. So I think at best the Terminate =
Message
could be added as an example of a spoofing attack, but honestly there =
are a ton
of things the spoofer could do, so I&#8217;m not sure I&#8217;d revise =
the
draft just to add another example.</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Does anyone see a hole in my =
reasoning?</span></font></p>

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

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

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

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

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

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

</div>

</body>

</html>

------_=_NextPart_001_01C4F267.6FD91653--


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

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

--===============1569982775==--



From rddp-bounces@ietf.org  Tue Jan  4 12:31:34 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29995
	for <rddp-web-archive@ietf.org>; Tue, 4 Jan 2005 12:31:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ClsjK-00025R-UT
	for rddp-web-archive@ietf.org; Tue, 04 Jan 2005 12:44:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClsLR-0004nQ-2D; Tue, 04 Jan 2005 12:19:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClsJI-00037A-A5
	for rddp@megatron.ietf.org; Tue, 04 Jan 2005 12:17:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27550
	for <rddp@ietf.org>; Tue, 4 Jan 2005 12:17:29 -0500 (EST)
Received: from web51902.mail.yahoo.com ([206.190.39.45])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1ClsVg-0001X9-CG
	for rddp@ietf.org; Tue, 04 Jan 2005 12:30:21 -0500
Received: (qmail 51903 invoked by uid 60001); 4 Jan 2005 17:16:59 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	b=PSsqRL3rk082aew+MCWvbwNtyYRFU5IjmHGUcCTq9r3g1fyLhdGG/lMKYUvOPYrm7YCGYm6LxHwsLgt2v1HCvV1hZgsOu5pPoFPIVZSNOGmprZjhbqCTkAZ5ds739aHQ6u9+vNAc4n/HlnKmOzAAPaXuztYPii1Vjm0ZxzBZ400=
	; 
Message-ID: <20050104171659.51901.qmail@web51902.mail.yahoo.com>
Received: from [216.52.22.7] by web51902.mail.yahoo.com via HTTP;
	Tue, 04 Jan 2005 09:16:59 PST
Date: Tue, 4 Jan 2005 09:16:59 -0800 (PST)
From: Sukanta ganguly <sganguly@yahoo.com>
Subject: Re: [rddp] Terminate message a security threat?
To: Jim Pinkerton <jpink@windows.microsoft.com>, RDDP <rddp@ietf.org>
In-Reply-To: <E6564B8F86852D46A4E98C485FB33B8F0B7EDC19@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id MAA27550
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable

I agree. I don't see much to be added for Terminate
Message. Spoofing is a different issue.=20


SG

--- Jim Pinkerton <jpink@windows.microsoft.com> wrote:

> =20
>=20
> To date the security ID doesn't discuss the
> Terminate Message. It was suggested to me by
> Mallikarjun as part of his detailed review that
> since all other messages are discussed, shouldn't
> Terminate be?=20
>=20
> =20
>=20
> In thinking this through, I don't believe this
> represents any new attacks. If the Remote Peer is
> sending you a Terminate Message, then that =BD of the
> Stream is terminated. So he just clobbered himself,
> but hasn't been able to affect any other connections
> - thus this is not a security issue. If a third
> party is able to inject a Terminate Message into the
> data stream, then it is a spoofing attack. The
> spoofing attack and mitigations are already
> discussed. So I think at best the Terminate Message
> could be added as an example of a spoofing attack,
> but honestly there are a ton of things the spoofer
> could do, so I'm not sure I'd revise the draft just
> to add another example.
>=20
> =20
>=20
> Does anyone see a hole in my reasoning?
>=20
> =20
>=20
> =20
>=20
> Jim
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> > _______________________________________________
> rddp mailing list
> rddp@ietf.org
> https://www1.ietf.org/mailman/listinfo/rddp
>=20



	=09
__________________________________=20
Do you Yahoo!?=20
All your favorites on one personal page =96 Try My Yahoo!
http://my.yahoo.com=20

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


From rddp-bounces@ietf.org  Tue Jan  4 12:49:05 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01588
	for <rddp-web-archive@ietf.org>; Tue, 4 Jan 2005 12:49:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Clt0H-0002Vk-F1
	for rddp-web-archive@ietf.org; Tue, 04 Jan 2005 13:01:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Clsem-0004hs-RT; Tue, 04 Jan 2005 12:39:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Clsck-0003wV-Uh
	for rddp@megatron.ietf.org; Tue, 04 Jan 2005 12:37:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00571
	for <rddp@ietf.org>; Tue, 4 Jan 2005 12:37:35 -0500 (EST)
Received: from 67-118-4-34.ded.pacbell.net ([67.118.4.34]
	helo=fiona.siliquent.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Clsp9-0002Dy-B5
	for rddp@ietf.org; Tue, 04 Jan 2005 12:50:28 -0500
Content-class: urn:content-classes:message
Subject: RE: [rddp] Terminate message a security threat?
Date: Tue, 4 Jan 2005 09:38:59 -0800
MIME-Version: 1.0
Message-ID: <8508251A6FC08A489844A94261D3693A01B6DB@fiona.siliquent.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Thread-Topic: [rddp] Terminate message a security threat?
Thread-Index: AcTyZ3AKaq0QGkKMQvyjhSJeLK+srgAG9Vvg
From: "Caitlin Bestler" <caitlinb@siliquent.com>
To: "Jim Pinkerton" <jpink@windows.microsoft.com>, "RDDP" <rddp@ietf.org>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f8ee348dcc4be4a59bc395f7cd6343ad
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1079395557=="
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 3be09dac38eaa50f02d21c7fcee1128c

This is a multi-part message in MIME format.

--===============1079395557==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4F284.465DAAF0"

This is a multi-part message in MIME format.

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

The only thing I can think of that might be different is that a naive =
implementation
might parse a Terminate message on the assumption that it is validly =
formatted.
It is concievable that certain implementations might be vulnerable to =
specific
incorrect formattings causing internal buffer overflows/etc.   It sounds =
crazy,
but look at some of the web/email related attacks that have been =
diagnosed.
=20
But even that isn't a *new* attack, since deliberate mal-formatting of =
headers
is a known attack, and the mitigation strategy is already known (don't =
make
assumptions about anything that shows up on a wire).
=20
So I'd agree that an extra example might be nice, but there are always =
things
that would be "nice" to add to a draft. If you keep adding them forever =
then
it stays a draft forever. I'd rather have an RFC that was missing some =
examples.
=20
=20
=20


________________________________

	From: rddp-bounces@ietf.org [mailto:rddp-bounces@ietf.org] On Behalf Of =
Jim Pinkerton
	Sent: Tuesday, January 04, 2005 6:13 AM
	To: RDDP
	Subject: [rddp] Terminate message a security threat?
=09
=09

	=20

	To date the security ID doesn't discuss the Terminate Message. It was =
suggested to me by Mallikarjun as part of his detailed review that since =
all other messages are discussed, shouldn't Terminate be?=20

	=20

	In thinking this through, I don't believe this represents any new =
attacks. If the Remote Peer is sending you a Terminate Message, then =
that =BD of the Stream is terminated. So he just clobbered himself, but =
hasn't been able to affect any other connections - thus this is not a =
security issue. If a third party is able to inject a Terminate Message =
into the data stream, then it is a spoofing attack. The spoofing attack =
and mitigations are already discussed. So I think at best the Terminate =
Message could be added as an example of a spoofing attack, but honestly =
there are a ton of things the spoofer could do, so I'm not sure I'd =
revise the draft just to add another example.

	=20

	Does anyone see a hole in my reasoning?

	=20

	=20

	Jim

	=20

	=20

	=20

=20
--
Caitlin Bestler
Director Software Architecture
Siliquent Technologies
caitlinb@siliquent.com
 =20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2523" name=3DGENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: .5in 66.25pt .5in =
66.25pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The <STRONG>only</STRONG> thing I can think of =
that=20
<STRONG>might</STRONG> be different is that a naive=20
implementation</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>might parse a Terminate message on the =
assumption that it=20
is validly formatted.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>It is concievable that certain implementations =
might be=20
vulnerable to specific</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>incorrect formattings causing internal buffer=20
overflows/etc.&nbsp;&nbsp; It sounds crazy,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>but look at some of the web/email related =
attacks that have=20
been diagnosed.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>But even that isn't a *new* attack, since =
deliberate=20
mal-formatting of headers</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>is a known attack, and the mitigation strategy =
is already=20
known (don't make</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>assumptions about anything that shows up on a=20
wire).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>So I'd agree that an extra example might be =
nice, but there=20
are always things</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>that would be "nice" to add to a draft. =
If&nbsp;you keep=20
adding them forever then</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>it stays a draft forever. I'd rather have an =
RFC that was=20
missing some examples.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D353493117-04012005></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D353493117-04012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> rddp-bounces@ietf.org=20
  [mailto:rddp-bounces@ietf.org] <B>On Behalf Of </B>Jim=20
  Pinkerton<BR><B>Sent:</B> Tuesday, January 04, 2005 6:13 =
AM<BR><B>To:</B>=20
  RDDP<BR><B>Subject:</B> [rddp] Terminate message a security=20
  threat?<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">To date the security ID =
doesn=92t=20
  discuss the Terminate Message. It was suggested to me by Mallikarjun =
as part=20
  of his detailed review that since all other messages are discussed, =
shouldn=92t=20
  Terminate be? </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In thinking this =
through, I don=92t=20
  believe this represents any new attacks. If the Remote Peer is sending =
you a=20
  Terminate Message, then that =BD of the Stream is terminated. So he =
just=20
  clobbered himself, but hasn=92t been able to affect any other =
connections =96 thus=20
  this is not a security issue. If a third party is able to inject a =
Terminate=20
  Message into the data stream, then it is a spoofing attack. The =
spoofing=20
  attack and mitigations are already discussed. So I think at best the =
Terminate=20
  Message could be added as an example of a spoofing attack, but =
honestly there=20
  are a ton of things the spoofer could do, so I=92m not sure I=92d =
revise the draft=20
  just to add another example.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Does anyone see a hole =
in my=20
  reasoning?</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Jim</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></BLOCKQUOTE>
<DIV class=3DMsoNormal dir=3Dltr><FONT face=3DArial><FONT size=3D2><FONT =

color=3D#0000ff><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"></SPAN></FONT></FONT></FONT></FONT>&nbsp;</DIV>
<DIV class=3DMsoNormal dir=3Dltr><FONT face=3DArial><FONT size=3D2><FONT =

color=3D#0000ff><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><!-- Converted from =
text/plain format -->
<P><FONT size=3D2>--<BR>Caitlin Bestler<BR>Director Software=20
Architecture<BR>Siliquent=20
Technologies<BR>caitlinb@siliquent.com<BR>&nbsp;</FONT>=20
</P></SPAN></FONT></FONT></FONT></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C4F284.465DAAF0--


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

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

--===============1079395557==--



From rddp-bounces@ietf.org  Tue Jan  4 14:23:02 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09970
	for <rddp-web-archive@ietf.org>; Tue, 4 Jan 2005 14:23:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CluT9-0004ya-Qb
	for rddp-web-archive@ietf.org; Tue, 04 Jan 2005 14:35:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CluCS-0004xR-UD; Tue, 04 Jan 2005 14:18:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CluAH-0003tp-O9
	for rddp@megatron.ietf.org; Tue, 04 Jan 2005 14:16:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09392
	for <rddp@ietf.org>; Tue, 4 Jan 2005 14:16:20 -0500 (EST)
Received: from palrel13.hp.com ([156.153.255.238])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CluMe-0004rb-Mq
	for rddp@ietf.org; Tue, 04 Jan 2005 14:29:12 -0500
Received: from esmail.cup.hp.com (esmail.cup.hp.com [15.0.65.164])
	by palrel13.hp.com (Postfix) with ESMTP id 3AFC11C18239
	for <rddp@ietf.org>; Tue,  4 Jan 2005 11:16:17 -0800 (PST)
Received: from MK73191c.cup.hp.com (mk731916.cup.hp.com [15.8.80.134])
	by esmail.cup.hp.com (8.9.3 (PHNE_29774)/8.8.6) with ESMTP id LAA05822
	for <rddp@ietf.org>; Tue, 4 Jan 2005 11:13:07 -0800 (PST)
Message-Id: <6.2.0.14.2.20050104111525.020af990@esmail.cup.hp.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Tue, 04 Jan 2005 11:16:07 -0800
To: "RDDP" <rddp@ietf.org>
From: Michael Krause <krause@cup.hp.com>
Subject: Re: [rddp] Terminate message a security threat?
In-Reply-To: <E6564B8F86852D46A4E98C485FB33B8F0B7EDC19@WIN-MSG-10.wingro
	up.windeploy.ntdev.microsoft.com>
References: <E6564B8F86852D46A4E98C485FB33B8F0B7EDC19@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1863941081=="
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede

--===============1863941081==
Content-Type: multipart/alternative;
	boundary="=====================_7217638==.ALT"

--=====================_7217638==.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable

At 06:12 AM 1/4/2005, Jim Pinkerton wrote:
>Content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>         boundary=3D"----_=3D_NextPart_001_01C4F267.6FD91653"
>
>
>To date the security ID doesn=92t discuss the Terminate Message. It was=20
>suggested to me by Mallikarjun as part of his detailed review that since=20
>all other messages are discussed, shouldn=92t Terminate be?
>
>In thinking this through, I don=92t believe this represents any new=
 attacks.=20
>If the Remote Peer is sending you a Terminate Message, then that =BD of the=
=20
>Stream is terminated. So he just clobbered himself, but hasn=92t been able=
=20
>to affect any other connections =96 thus this is not a security issue. If a=
=20
>third party is able to inject a Terminate Message into the data stream,=20
>then it is a spoofing attack. The spoofing attack and mitigations are=20
>already discussed. So I think at best the Terminate Message could be added=
=20
>as an example of a spoofing attack, but honestly there are a ton of things=
=20
>the spoofer could do, so I=92m not sure I=92d revise the draft just to add=
=20
>another example.
>
>Does anyone see a hole in my reasoning?

I do not see this as a security threat - at best, just another example of=20
existing issues that should be examined in any robust design.

Mike

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

--=====================_7217638==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<body>
<font size=3D3>At 06:12 AM 1/4/2005, Jim Pinkerton wrote:<br>
<blockquote type=3Dcite class=3Dcite cite=3D"">Content-class:
urn:content-classes:message<br>
Content-Type: multipart/alternative;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>
boundary=3D&quot;----_=3D_NextPart_001_01C4F267.6FD91653&quot;<br><br>
</font><font face=3D"arial" size=3D2>&nbsp;<br>
To date the security ID doesn=92t discuss the Terminate Message. It was
suggested to me by Mallikarjun as part of his detailed review that since
all other messages are discussed, shouldn=92t Terminate be? <br>
&nbsp;<br>
In thinking this through, I don=92t believe this represents any new
attacks. If the Remote Peer is sending you a Terminate Message, then that
=BD of the Stream is terminated. So he just clobbered himself, but hasn=92t
been able to affect any other connections =96 thus this is not a security
issue. If a third party is able to inject a Terminate Message into the
data stream, then it is a spoofing attack. The spoofing attack and
mitigations are already discussed. So I think at best the Terminate
Message could be added as an example of a spoofing attack, but honestly
there are a ton of things the spoofer could do, so I=92m not sure I=92d
revise the draft just to add another example.<br>
&nbsp;<br>
Does anyone see a hole in my reasoning?</font></blockquote><br>
I do not see this as a security threat - at best, just another example of
existing issues that should be examined in any robust design.<br><br>
Mike<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D""><font face=3D"arial" size=3D2=
>
&nbsp;<br>
&nbsp;<br>
Jim<br>
&nbsp;<br>
&nbsp;<br>
&nbsp;<br>
</font><font size=3D3>_______________________________________________<br>
rddp mailing list<br>
rddp@ietf.org<br>
<a href=3D"https://www1.ietf.org/mailman/listinfo/rddp" eudora=3D"autourl">
https://www1.ietf.org/mailman/listinfo/rddp</a></font></blockquote></body>
</html>

--=====================_7217638==.ALT--




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

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

--===============1863941081==--





From rddp-bounces@ietf.org  Wed Jan  5 07:48:53 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29546
	for <rddp-web-archive@ietf.org>; Wed, 5 Jan 2005 07:48:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmAnQ-0003V1-Pv
	for rddp-web-archive@ietf.org; Wed, 05 Jan 2005 08:01:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmAOc-0000mX-Kb; Wed, 05 Jan 2005 07:36:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmAK3-0007p0-B2
	for rddp@megatron.ietf.org; Wed, 05 Jan 2005 07:31:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28336
	for <rddp@ietf.org>; Wed, 5 Jan 2005 07:31:29 -0500 (EST)
Received: from e33.co.us.ibm.com ([32.97.110.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmAWa-0002yj-H1
	for rddp@ietf.org; Wed, 05 Jan 2005 07:44:31 -0500
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
	[9.17.195.106])
	by e33.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j05CUrCO594594
	for <rddp@ietf.org>; Wed, 5 Jan 2005 07:30:53 -0500
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170])
	by d03relay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	j05CUqXN229428 for <rddp@ietf.org>; Wed, 5 Jan 2005 05:30:52 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1])
	by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id
	j05CUqSK016518 for <rddp@ietf.org>; Wed, 5 Jan 2005 05:30:52 -0700
Received: from d03nm132.boulder.ibm.com (d03nm132.boulder.ibm.com
	[9.17.195.172])
	by d03av04.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id
	j05CUqZs016512 for <rddp@ietf.org>; Wed, 5 Jan 2005 05:30:52 -0700
To: rddp@ietf.org
X-Mailer: Lotus Notes Release 6.5.1IBM February 19, 2004
Message-ID: <OF76244C0D.3D0ADC5D-ON87256F80.00443944-65256F80.0045041A@us.ibm.com>
From: Krishna Kumar <kumarkr@us.ibm.com>
Date: Wed, 5 Jan 2005 18:00:50 +0530
X-MIMETrack: Serialize by Router on D03NM132/03/M/IBM(Release 6.51HF338 | June
	21, 2004) at 01/05/2005 05:30:51
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Subject: [rddp] Question on RDMAP Spec
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1817854184=="
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15

--===============1817854184==
Content-type: multipart/alternative; 
	Boundary="0__=08BBE513DFD7BFD48f9e8a93df938690918c08BBE513DFD7BFD4"
Content-Disposition: inline

--0__=08BBE513DFD7BFD48f9e8a93df938690918c08BBE513DFD7BFD4
Content-type: text/plain; charset=US-ASCII





Hi,

Please excuse me if this is a wrong question, I am new to this area.

I am going through the rddp-rdmap-02.txt and saw that Fig 3 RDDP
Control header shows 4 bits for Opcode, while Figure 4 and Figure 5
uses 5 bits for RDMA opcode.

Why this discrepancy ?

Thanks,

- KK
--0__=08BBE513DFD7BFD48f9e8a93df938690918c08BBE513DFD7BFD4
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline

<html><body>
<p>Hi,<br>
<br>
Please excuse me if this is a wrong question, I am new to this area.<br>
<br>
I am going through the rddp-rdmap-02.txt and saw that Fig 3 RDDP<br>
Control header shows 4 bits for Opcode, while Figure 4 and Figure 5<br>
uses 5 bits for RDMA opcode.<br>
<br>
Why this discrepancy ?<br>
<br>
Thanks,<br>
<br>
- KK<br>
</body></html>
--0__=08BBE513DFD7BFD48f9e8a93df938690918c08BBE513DFD7BFD4--



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

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

--===============1817854184==--




From rddp-bounces@ietf.org  Wed Jan  5 09:08:44 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05380
	for <rddp-web-archive@ietf.org>; Wed, 5 Jan 2005 09:08:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmC2l-0005LP-1B
	for rddp-web-archive@ietf.org; Wed, 05 Jan 2005 09:21:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmBlW-0003Sc-MV; Wed, 05 Jan 2005 09:03:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmBfG-0001ug-LT
	for rddp@megatron.ietf.org; Wed, 05 Jan 2005 08:57:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04367
	for <rddp@ietf.org>; Wed, 5 Jan 2005 08:57:28 -0500 (EST)
Received: from ztxmail05.ztx.compaq.com ([161.114.1.209])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmBrq-00053g-DT
	for rddp@ietf.org; Wed, 05 Jan 2005 09:10:30 -0500
Received: from cceexg11.americas.cpqcorp.net (cceexg11.americas.cpqcorp.net
	[16.81.1.59])
	by ztxmail05.ztx.compaq.com (Postfix) with ESMTP id B1D46CED8;
	Wed,  5 Jan 2005 07:56:56 -0600 (CST)
Received: from cceexc18.americas.cpqcorp.net ([16.81.1.4]) by
	cceexg11.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 5 Jan 2005 07:56:56 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [rddp] Question on RDMAP Spec
Date: Wed, 5 Jan 2005 07:56:55 -0600
Message-ID: <4D027986353D1341ADA4F2A4F8A170762F48169C@cceexc18.americas.cpqcorp.net>
Thread-Topic: [rddp] Question on RDMAP Spec
Thread-Index: AcTzJPuUKkeZzymWRnaOZ51QYfaAvwACFsBA
From: "Culley, Paul" <paul.culley@hp.com>
To: "Krishna Kumar" <kumarkr@us.ibm.com>, <rddp@ietf.org>
X-OriginalArrivalTime: 05 Jan 2005 13:56:56.0569 (UTC)
	FILETIME=[6B31D690:01C4F32E]
X-Spam-Score: 0.6 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2137302180=="
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f

This is a multi-part message in MIME format.

--===============2137302180==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4F32E.6ABDDDD6"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4F32E.6ABDDDD6
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

By my reading, all three figures use 4 bits.
=20
Paul R. Culley
HP Fellow
281-514-5543
=20


________________________________

	From: rddp-bounces@ietf.org [mailto:rddp-bounces@ietf.org] On
Behalf Of Krishna Kumar
	Sent: Wednesday, January 05, 2005 6:31 AM
	To: rddp@ietf.org
	Subject: [rddp] Question on RDMAP Spec
=09
=09

	Hi,
=09
	Please excuse me if this is a wrong question, I am new to this
area.
=09
	I am going through the rddp-rdmap-02.txt and saw that Fig 3 RDDP
	Control header shows 4 bits for Opcode, while Figure 4 and
Figure 5
	uses 5 bits for RDMA opcode.
=09
	Why this discrepancy ?
=09
	Thanks,
=09
	- KK
=09


------_=_NextPart_001_01C4F32E.6ABDDDD6
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D495124913-05012005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>By my reading, all three figures use 4=20
bits.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Paul R. =
Culley</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>HP Fellow</FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>281-514-5543</FONT></DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> rddp-bounces@ietf.org=20
  [mailto:rddp-bounces@ietf.org] <B>On Behalf Of </B>Krishna=20
  Kumar<BR><B>Sent:</B> Wednesday, January 05, 2005 6:31 =
AM<BR><B>To:</B>=20
  rddp@ietf.org<BR><B>Subject:</B> [rddp] Question on RDMAP=20
  Spec<BR></FONT><BR></DIV>
  <DIV></DIV>
  <P>Hi,<BR><BR>Please excuse me if this is a wrong question, I am new =
to this=20
  area.<BR><BR>I am going through the rddp-rdmap-02.txt and saw that Fig =
3=20
  RDDP<BR>Control header shows 4 bits for Opcode, while Figure 4 and =
Figure=20
  5<BR>uses 5 bits for RDMA opcode.<BR><BR>Why this discrepancy=20
  ?<BR><BR>Thanks,<BR><BR>- KK<BR></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C4F32E.6ABDDDD6--


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

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

--===============2137302180==--



From rddp-bounces@ietf.org  Wed Jan  5 12:48:56 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25423
	for <rddp-web-archive@ietf.org>; Wed, 5 Jan 2005 12:48:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CmFTs-0005OF-Nk
	for rddp-web-archive@ietf.org; Wed, 05 Jan 2005 13:02:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmFEH-0006bN-LR; Wed, 05 Jan 2005 12:45:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmFBs-0005uk-QS
	for rddp@megatron.ietf.org; Wed, 05 Jan 2005 12:43:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24958
	for <rddp@ietf.org>; Wed, 5 Jan 2005 12:43:21 -0500 (EST)
Received: from atlrel6.hp.com ([156.153.255.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmFOK-0004xW-L6
	for rddp@ietf.org; Wed, 05 Jan 2005 12:56:27 -0500
Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.43.209.160])
	by atlrel6.hp.com (Postfix) with ESMTP id F2B84136DB
	for <rddp@ietf.org>; Wed,  5 Jan 2005 12:43:12 -0500 (EST)
Received: from [127.0.0.1] (pal1nai162213.nsr.hp.com [15.244.162.213])
	by rosemail.rose.hp.com (Postfix) with ESMTP id EE9B8806E
	for <rddp@ietf.org>; Wed,  5 Jan 2005 09:43:11 -0800 (PST)
Message-ID: <41DC2737.8050705@rose.hp.com>
Date: Wed, 05 Jan 2005 09:43:19 -0800
From: "Mallikarjun C." <cbm@rose.hp.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: RDDP <rddp@ietf.org>
Subject: Re: [rddp] Terminate message a security threat?
References: <E6564B8F86852D46A4E98C485FB33B8F0B7EDC19@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<6.2.0.14.2.20050104111525.020af990@esmail.cup.hp.com>
In-Reply-To: <6.2.0.14.2.20050104111525.020af990@esmail.cup.hp.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: quoted-printable
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: quoted-printable

Thanks Jim for patiently working through all the comments.

The note I wrote to Jim was:

"It may be worth dealing with for two reasons - (1) Terminate has a role=20
in DoS attacks, (2) the current description of DDP/RDMAP message=20
processing is seemingly comprehensive but is not due to the exclusion of=20
Terminate."

Wrt #1 above, it so far appears that the WG believes that Terminate is=20
not any worse than other security threats that were discussed.  I can go=20
with this, some new text (summarizing the sentiments on this thread) &=20
to address #2 might still be appropriate.  However, I will leave it to=20
the authors at this point, I expect to be slow in responding to emails=20
for the next 2 weeks.

Mallikarjun

Mallikarjun Chadalapaka
Networked Storage Architecture
Network Storage Solutions
Hewlett-Packard MS 5668
Roseville CA 95747
cbm [at] rose.hp.com


Michael Krause wrote:
> At 06:12 AM 1/4/2005, Jim Pinkerton wrote:
>=20
>> Content-class: urn:content-classes:message
>> Content-Type: multipart/alternative;
>>          boundary=3D"----_=3D_NextPart_001_01C4F267.6FD91653"
>>
>> =20
>> To date the security ID doesn=92t discuss the Terminate Message. It wa=
s=20
>> suggested to me by Mallikarjun as part of his detailed review that=20
>> since all other messages are discussed, shouldn=92t Terminate be?
>> =20
>> In thinking this through, I don=92t believe this represents any new=20
>> attacks. If the Remote Peer is sending you a Terminate Message, then=20
>> that =BD of the Stream is terminated. So he just clobbered himself, bu=
t=20
>> hasn=92t been able to affect any other connections =96 thus this is no=
t a=20
>> security issue. If a third party is able to inject a Terminate Message=
=20
>> into the data stream, then it is a spoofing attack. The spoofing=20
>> attack and mitigations are already discussed. So I think at best the=20
>> Terminate Message could be added as an example of a spoofing attack,=20
>> but honestly there are a ton of things the spoofer could do, so I=92m=20
>> not sure I=92d revise the draft just to add another example.
>> =20
>> Does anyone see a hole in my reasoning?
>=20
>=20
> I do not see this as a security threat - at best, just another example=20
> of existing issues that should be examined in any robust design.
>=20
> Mike
>=20
>> =20
>> =20
>> Jim
>> =20
>> =20
>> =20
>> _______________________________________________
>> rddp mailing list
>> rddp@ietf.org
>> https://www1.ietf.org/mailman/listinfo/rddp
>=20
>=20
> -----------------------------------------------------------------------=
-
>=20
> _______________________________________________
> rddp mailing list
> rddp@ietf.org
> https://www1.ietf.org/mailman/listinfo/rddp


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


From rddp-bounces@ietf.org  Thu Jan 20 11:21:12 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10697
	for <rddp-web-archive@ietf.org>; Thu, 20 Jan 2005 11:21:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CrfJI-0002cE-AX
	for rddp-web-archive@ietf.org; Thu, 20 Jan 2005 11:37:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Crevr-0007R7-RD; Thu, 20 Jan 2005 11:13:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CremP-0005lF-CI
	for rddp@megatron.ietf.org; Thu, 20 Jan 2005 11:03:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09386
	for <rddp@ietf.org>; Thu, 20 Jan 2005 11:03:26 -0500 (EST)
Received: from mail.ttlc.net ([66.94.32.4] helo=lampreynetworks.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Crf25-00027I-En
	for rddp@ietf.org; Thu, 20 Jan 2005 11:19:43 -0500
Received: from i8600 [64.222.186.225] by lampreynetworks.com with ESMTP
	(SMTPD32-7.07) id A61F1C1E00EA; Thu, 20 Jan 2005 11:02:39 -0500
From: "Barry Reinhold" <bbr@lampreynetworks.com>
To: "Renato Recio" <recio@us.ibm.com>
Date: Thu, 20 Jan 2005 11:02:26 -0500
Message-ID: <001601c4ff09$74ba4710$6901a8c0@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.1441
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: iwarp-tech@iol.unh.edu, RDDP <rddp@ietf.org>
Subject: [rddp] Inconsistent size issue
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit

I believe that the size of the RESERVED field following the TERMINATE
CONTROL in a TERMINATE HEADER is incorrect. It is documented as being 8
bits (under figure 9), but it should be 13 bits (as depicted in figure
7).

If this is wrong please let me know.

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




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


From rddp-bounces@ietf.org  Mon Jan 24 05:09:12 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23342
	for <rddp-web-archive@ietf.org>; Mon, 24 Jan 2005 05:09:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ct1QH-0005yN-3W
	for rddp-web-archive@ietf.org; Mon, 24 Jan 2005 05:26:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ct18a-0002fO-QA; Mon, 24 Jan 2005 05:08:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ct17Z-0002Wr-TC
	for rddp@megatron.ietf.org; Mon, 24 Jan 2005 05:06:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23194
	for <rddp@ietf.org>; Mon, 24 Jan 2005 05:06:55 -0500 (EST)
Received: from e35.co.us.ibm.com ([32.97.110.133])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ct1O3-0005u0-B8
	for rddp@ietf.org; Mon, 24 Jan 2005 05:23:59 -0500
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com
	[9.17.195.11])
	by e35.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j0OA6AZ7268514
	for <rddp@ietf.org>; Mon, 24 Jan 2005 05:06:13 -0500
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	j0OA6Awn403408 for <rddp@ietf.org>; Mon, 24 Jan 2005 03:06:10 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1])
	by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id
	j0OA69rP013810 for <rddp@ietf.org>; Mon, 24 Jan 2005 03:06:09 -0700
Received: from d03nm132.boulder.ibm.com (d03nm132.boulder.ibm.com
	[9.17.195.172])
	by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id
	j0OA68sx013784; Mon, 24 Jan 2005 03:06:08 -0700
In-Reply-To: <001601c4ff09$74ba4710$6901a8c0@i8600>
Subject: Re: [rddp] Inconsistent size issue
To: "Barry Reinhold" <bbr@lampreynetworks.com>
X-Mailer: Lotus Notes Release 6.5.1IBM February 19, 2004
Message-ID: <OF16C1E3DE.1BEA8F38-ON87256F93.00376FF3-65256F93.0037C5AD@us.ibm.com>
From: Krishna Kumar <kumarkr@us.ibm.com>
Date: Mon, 24 Jan 2005 15:36:05 +0530
X-MIMETrack: Serialize by Router on D03NM132/03/M/IBM(Release 6.51HF338 | June
	21, 2004) at 01/24/2005 03:06:08
MIME-Version: 1.0
X-Spam-Score: 0.8 (/)
X-Scan-Signature: b84f8c8fba0e1389e5eb998b64078964
Cc: Renato Recio <recio@us.ibm.com>, iwarp-tech@iol.unh.edu,
        RDDP <rddp@ietf.org>
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0088575071=="
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 3f3e54d3c03ed638c06aa9fa6861237e

--===============0088575071==
Content-type: multipart/related; 
	Boundary="0__=08BBE500DFA4E9638f9e8a93df938690918c08BBE500DFA4E963"

--0__=08BBE500DFA4E9638f9e8a93df938690918c08BBE500DFA4E963
Content-type: multipart/alternative; 
	Boundary="1__=08BBE500DFA4E9638f9e8a93df938690918c08BBE500DFA4E963"

--1__=08BBE500DFA4E9638f9e8a93df938690918c08BBE500DFA4E963
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable






Yes, it does look like a typo.

- KK



                                                                       =
    
             "Barry Reinhold"                                          =
    
             <bbr@lampreynetwo                                         =
    
             rks.com>                                                  =
 To 
             Sent by:                  Renato Recio/Austin/IBM@IBMUS   =
    
             rddp-bounces@ietf                                         =
 cc 
             .org                      iwarp-tech@iol.unh.edu, RDDP    =
    
                                       <rddp@ietf.org>                 =
    
                                                                   Subj=
ect 
             01/20/2005 09:32          [rddp] Inconsistent size issue  =
    
             PM                                                        =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    
                                                                       =
    




I believe that the size of the RESERVED field following the TERMINATE
CONTROL in a TERMINATE HEADER is incorrect. It is documented as being 8=

bits (under figure 9), but it should be 13 bits (as depicted in figure
7).

If this is wrong please let me know.

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





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

--1__=08BBE500DFA4E9638f9e8a93df938690918c08BBE500DFA4E963
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

<html><body>
<p>Yes, it does look like a typo.<br>
<br>
- KK<br>
<br>
<img src=3D"cid:10__=3D08BBE500DFA4E9638f9e8a93df938@us.ibm.com" width=3D=
"16" height=3D"16" alt=3D"Inactive hide details for &quot;Barry Reinhol=
d&quot; &lt;bbr@lampreynetworks.com&gt;">&quot;Barry Reinhold&quot; &lt=
;bbr@lampreynetworks.com&gt;<br>
<br>
<br>

<table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">=

<tr valign=3D"top"><td style=3D"background-image:url(cid:20__=3D08BBE50=
0DFA4E9638f9e8a93df938@us.ibm.com); background-repeat: no-repeat; " wid=
th=3D"40%">
<ul>
<ul>
<ul>
<ul><b><font size=3D"2">&quot;Barry Reinhold&quot; &lt;bbr@lampreynetwo=
rks.com&gt;</font></b><font size=3D"2"> </font><br>
<font size=3D"2">Sent by: rddp-bounces@ietf.org</font>
<p><font size=3D"2">01/20/2005 09:32 PM</font></ul>
</ul>
</ul>
</ul>
</td><td width=3D"60%">
<table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">=

<tr valign=3D"top"><td width=3D"1%" valign=3D"middle"><img src=3D"cid:3=
0__=3D08BBE500DFA4E9638f9e8a93df938@us.ibm.com" border=3D"0" height=3D"=
1" width=3D"58" alt=3D""><br>
<div align=3D"right"><font size=3D"2">To</font></div></td><td width=3D"=
100%"><img src=3D"cid:30__=3D08BBE500DFA4E9638f9e8a93df938@us.ibm.com" =
border=3D"0" height=3D"1" width=3D"1" alt=3D""><br>
<font size=3D"2">Renato Recio/Austin/IBM@IBMUS</font></td></tr>

<tr valign=3D"top"><td width=3D"1%" valign=3D"middle"><img src=3D"cid:3=
0__=3D08BBE500DFA4E9638f9e8a93df938@us.ibm.com" border=3D"0" height=3D"=
1" width=3D"58" alt=3D""><br>
<div align=3D"right"><font size=3D"2">cc</font></div></td><td width=3D"=
100%"><img src=3D"cid:30__=3D08BBE500DFA4E9638f9e8a93df938@us.ibm.com" =
border=3D"0" height=3D"1" width=3D"1" alt=3D""><br>
<font size=3D"2">iwarp-tech@iol.unh.edu, RDDP &lt;rddp@ietf.org&gt;</fo=
nt></td></tr>

<tr valign=3D"top"><td width=3D"1%" valign=3D"middle"><img src=3D"cid:3=
0__=3D08BBE500DFA4E9638f9e8a93df938@us.ibm.com" border=3D"0" height=3D"=
1" width=3D"58" alt=3D""><br>
<div align=3D"right"><font size=3D"2">Subject</font></div></td><td widt=
h=3D"100%"><img src=3D"cid:30__=3D08BBE500DFA4E9638f9e8a93df938@us.ibm.=
com" border=3D"0" height=3D"1" width=3D"1" alt=3D""><br>
<font size=3D"2">[rddp] Inconsistent size issue</font></td></tr>
</table>

<table border=3D"0" cellspacing=3D"0" cellpadding=3D"0">
<tr valign=3D"top"><td width=3D"58"><img src=3D"cid:30__=3D08BBE500DFA4=
E9638f9e8a93df938@us.ibm.com" border=3D"0" height=3D"1" width=3D"1" alt=
=3D""></td><td width=3D"336"><img src=3D"cid:30__=3D08BBE500DFA4E9638f9=
e8a93df938@us.ibm.com" border=3D"0" height=3D"1" width=3D"1" alt=3D""><=
/td></tr>
</table>
</td></tr>
</table>
<br>
<tt>I believe that the size of the RESERVED field following the TERMINA=
TE<br>
CONTROL in a TERMINATE HEADER is incorrect. It is documented as being 8=
<br>
bits (under figure 9), but it should be 13 bits (as depicted in figure<=
br>
7).<br>
<br>
If this is wrong please let me know.<br>
<br>
Barry Reinhold<br>
Lamprey Networks<br>
bbr@lampreynetworks.com<br>
(603) 868-8411<br>
 <br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
rddp mailing list<br>
rddp@ietf.org<br>
</tt><tt><a href=3D"https://www1.ietf.org/mailman/listinfo/rddp">https:=
//www1.ietf.org/mailman/listinfo/rddp</a></tt><tt><br>
</tt><br>
</body></html>=


--1__=08BBE500DFA4E9638f9e8a93df938690918c08BBE500DFA4E963--


--0__=08BBE500DFA4E9638f9e8a93df938690918c08BBE500DFA4E963
Content-type: image/gif; 
	name="graycol.gif"
Content-Disposition: inline; filename="graycol.gif"
Content-ID: <10__=08BBE500DFA4E9638f9e8a93df938@us.ibm.com>
Content-transfer-encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhEAAQAKECAMzMzAAAAP///wAAACH5BAEAAAIALAAAAAAQABAAAAIXlI+py+0PopwxUbpu
ZRfKZ2zgSJbmSRYAIf4fT3B0aW1pemVkIGJ5IFVsZWFkIFNtYXJ0U2F2ZXIhAAA7

--0__=08BBE500DFA4E9638f9e8a93df938690918c08BBE500DFA4E963
Content-type: image/gif; 
	name="pic01927.gif"
Content-Disposition: inline; filename="pic01927.gif"
Content-ID: <20__=08BBE500DFA4E9638f9e8a93df938@us.ibm.com>
Content-transfer-encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhWABDALP/AAAAAK04Qf79/o+Gm7WuwlNObwoJFCsoSMDAwGFsmIuezf///wAAAAAAAAAA
AAAAACH5BAEAAAgALAAAAABYAEMAQAT/EMlJq704682770RiFMRinqggEUNSHIchG0BCfHhOjAuh
EDeUqTASLCbBhQrhG7xis2j0lssNDopE4jfIJhDaggI8YB1sZeZgLVA9YVCpnGagVjV171aRVrYR
RghXcAGFhoUETwYxcXNyADJ3GlcSKGAwLwllVC1vjIUHBWsFilKQdI8GA5IcpApeJQt8L09lmgkH
LZikoU5wjqcyAMMFrJIDPAKvCFletKSev1HBw8KrxtjZ2tvc3d5VyKtCKW3jfz4uMKmq3xu4N0nK
BVoJQmx2LGVOmrqNjjJf2hHAQo/eDwJGTKhQMcgQEEAnEjFS98+RnW3smGkZU6ncCWav/4wYOnAI
TihRL/4FEwbp28BXMMcoscQCVxlepL4IGDSCyJyVQOu0o7CjmLN50OZlqWmyFy5/6yBBuji0AxFR
M00oQAqNIstqI6qKHUsWRAEAvagsmfUEAImyxgbmUpJk3IklNUtJOUAVLoUr1+wqDGTE4zk+T6FG
uQb3SizBCwatiiUgCBN8vrz+zFjVyQ8FWkOlg4NQiZMB5QS8QO3mpOaKnL0Z2EKvNMSILEThKhCg
zMKPVxYJh23qm9KNW7pArPynMqZDiErsTMqI+LRi3QAgkFUbXpuFKhSYZALd0O5RKa2z9EYKBbpb
qxIKsjUPRgD7I2XYV6wyrOw92ykExP8NW4URhknC5dKGE4v4NENQj2jXjmfNgOZDaXb5glRmXQ33
YEWQYNcZFnrYcIQLNzyTFDQNkXIff0ExVlY4srziQk43inZgL4rwxxINMvpFFAz1KOODHiu+4aEw
NEjFl5B3JIKWKF3k6I9bfUGp5ZZcdunll5IA4cuHvQQJ5gcsoCWOOUwgltIwAKRxJgbIkJAQZEq0
2YliZnpZZ4BH3CnYOXldOUOfQoYDqF1LFHbXCrO8xmRsfoXDXJ6ChjCAH3QlhJcT6VWE6FCkfCco
CgrMFsROrIEX3o2whVjWDjoJccN3LdggSGXLCdLEgHr1lyU3O3QxhgohNKXJCWv8JQr/PDdaqd6w
2rj1inLiGeiCJoDspAoQlYE6QWLSECehcWIYxIQES6zhbn1iImTHEQyqJ4eIxJJoUBc+3CbBuwZE
V5cJPPkIjFDdeEabQbd6WgICTxiiz0f5dBKquXF6k4senwEhYGnKEFJeGrxUZy8dB8gmAXI/sPvH
ESfCwVt5hTgYiqQqtdRNHQIU1PJ33ZqmzgE90OwLaoJcnMop1WiMmgkPHQRIrwgFuNV90A3doNKT
mrKIN07AnGcI9BQjhCBN4RfA1qIZnMqorJCogKfGQnxSCDilTVIA0yl5ciTovgLuBDKFUDE9aQcw
9SA+rjSNf9/M1gxrj6VwDTS0IUSElMzBfsj0NFXR2kwsV1A5IF1grLgLL/r1R40BZEnuBWgmQEyb
jqRwSAt6bqMCOFkvKFN2GPPkUzIm/SCF8z8pVzpbjVnMsy0vOr1hw3SaSRUhpY09v0z0J1FnwzPl
fmh+xl4WtR0zGu24I4KbMQm3lnVu2oNWxI9W/lcyzA+mCKF4DBikxb/+UWtOGRiFP8qEwAayIgIA
Ow==

--0__=08BBE500DFA4E9638f9e8a93df938690918c08BBE500DFA4E963
Content-type: image/gif; 
	name="ecblank.gif"
Content-Disposition: inline; filename="ecblank.gif"
Content-ID: <30__=08BBE500DFA4E9638f9e8a93df938@us.ibm.com>
Content-transfer-encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhEAABAIAAAAAAAP///yH5BAEAAAEALAAAAAAQAAEAAAIEjI8ZBQA7

--0__=08BBE500DFA4E9638f9e8a93df938690918c08BBE500DFA4E963--



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

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

--===============0088575071==--




From rddp-bounces@ietf.org  Mon Jan 31 09:52:09 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07932
	for <rddp-web-archive@ietf.org>; Mon, 31 Jan 2005 09:52:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CvdCO-0005Gg-TV
	for rddp-web-archive@ietf.org; Mon, 31 Jan 2005 10:10:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cvcqm-0004wE-Jk; Mon, 31 Jan 2005 09:48:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvcjs-0003hP-6j
	for rddp@megatron.ietf.org; Mon, 31 Jan 2005 09:41:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06397
	for <rddp@ietf.org>; Mon, 31 Jan 2005 09:41:14 -0500 (EST)
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvd1o-0004uX-TO
	for rddp@ietf.org; Mon, 31 Jan 2005 09:59:50 -0500
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail1.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.1289); 
	Mon, 31 Jan 2005 06:40:43 -0800
Received: from red-hub-01.redmond.corp.microsoft.com ([157.54.7.71]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 31 Jan 2005 06:40:40 -0800
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.84]) by red-hub-01.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1289); Mon, 31 Jan 2005 06:40:41 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com
	([157.54.12.81]) by
	win-imc-02.wingroup.windeploy.ntdev.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1289); Mon, 31 Jan 2005 06:40:41 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 31 Jan 2005 06:40:40 -0800
Message-ID: <E6564B8F86852D46A4E98C485FB33B8F0BEF3646@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: iwarp-tech Inconsistent size issue
Thread-Index: AcT/CabjRbUqmmH0Q1+9TCiQcR3/SAImShFA
From: "Jim Pinkerton" <jpink@windows.microsoft.com>
To: "Barry Reinhold" <bbr@lampreynetworks.com>,
        "Renato Recio" <recio@us.ibm.com>
X-OriginalArrivalTime: 31 Jan 2005 14:40:41.0680 (UTC)
	FILETIME=[D69F7D00:01C507A2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: quoted-printable
Cc: iwarp-tech@iol.unh.edu, RDDP <rddp@ietf.org>
Subject: [rddp] RE: iwarp-tech Inconsistent size issue
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rddp>,
	<mailto:rddp-request@ietf.org?subject=subscribe>
Sender: rddp-bounces@ietf.org
Errors-To: rddp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable


I agree.

Jim



> -----Original Message-----
> From: owner-iwarp-tech@io.iol.unh.edu [mailto:owner-iwarp-
> tech@io.iol.unh.edu] On Behalf Of Barry Reinhold
> Sent: Thursday, January 20, 2005 8:02 AM
> To: Renato Recio
> Cc: RDDP; iwarp-tech@iol.unh.edu
> Subject: iwarp-tech Inconsistent size issue
>=20
> I believe that the size of the RESERVED field following the TERMINATE
> CONTROL in a TERMINATE HEADER is incorrect. It is documented as being
8
> bits (under figure 9), but it should be 13 bits (as depicted in figure
> 7).
>=20
> If this is wrong please let me know.
>=20
> Barry Reinhold
> Lamprey Networks
> bbr@lampreynetworks.com
> (603) 868-8411
>=20
>=20
>=20


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


