Re: [rddp] MPA startup sequence issues (1) and (2)
"Talpey, Thomas" <Thomas.Talpey@netapp.com> Fri, 26 March 2004 20:57 UTC
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
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). > 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
- [rddp] MPA startup sequence issues (1) and (2) Black_David
- Re: [rddp] MPA startup sequence issues (1) and (2) Talpey, Thomas
- Re: [rddp] MPA startup sequence issues (1) and (2) Caitlin Bestler