RE: [Ips] iSER: draft-ietf-ips-iser-05.txt
"John Hufferd" <jhufferd@Brocade.COM> Tue, 29 November 2005 19:52 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhBWQ-0007g2-Mx; Tue, 29 Nov 2005 14:52:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhBWO-0007fd-NK for ips@megatron.ietf.org; Tue, 29 Nov 2005 14:52:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26731 for <ips@ietf.org>; Tue, 29 Nov 2005 14:51:25 -0500 (EST)
Received: from f112.brocade.com ([66.243.153.112] helo=blasphemy.brocade.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EhBqT-0001EP-TT for ips@ietf.org; Tue, 29 Nov 2005 15:12:59 -0500
Received: from hq-ex-5.corp.brocade.com (hq-ex-5 [192.168.38.35]) by blasphemy.brocade.com (Postfix) with ESMTP id C8948142FD; Tue, 29 Nov 2005 11:51:52 -0800 (PST)
Received: from hq-ex-6.corp.brocade.com ([192.168.38.36]) by hq-ex-5.corp.brocade.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 29 Nov 2005 11:51:52 -0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ips] iSER: draft-ietf-ips-iser-05.txt
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Tue, 29 Nov 2005 11:51:52 -0800
Message-ID: <EE86A2987768164188932981F6EBE69E01DD0274@hq-ex-6.brocade.com>
Thread-Topic: [Ips] iSER: draft-ietf-ips-iser-05.txt
Thread-Index: AcX1GXDcwQIxEI6YR0CtVD8fEhC7sQAAES9g
From: John Hufferd <jhufferd@Brocade.COM>
To: Sanjay Goyal <sanjayg@ivivity.com>
X-OriginalArrivalTime: 29 Nov 2005 19:51:52.0593 (UTC) FILETIME=[581B3810:01C5F51E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: quoted-printable
Cc: ips@ietf.org
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org
Sanjay, One of the reasons that I, for one, thought this approach was a good idea was that I felt that it was possible that a software version of iWARP could be made available. Even though it might not be appropriate for Server to Server communications, it might be very useful for workstations (desktops/laptops) to use software iWARP when communicating to a server that has and RNIC. In the workstation to iWARP server situation, the workstation often has all the MIPS it needs for this operation, and though not efficient for the workstation to use software iWARP (probably no one will notice anyway), it enables server efficiencies since the server can use iWARP via its RNIC. The same thought is appropriate when the workstation (Initiator) is contacting a Storage (Target) system that might have an RNIC. In that case the Initiator might prefer to use normal iSCSI, but the Target would prefer to use iSER. In other situations with RNICs, some vendors are producing RNICs that also support native iSCSI (especially if they want to sell product today). These RNICs can often support iSCSI as well as iSER. In some cases, the iSCSI path has been optimized for that specific task, and will operate as well as, or perhaps in some cases better than iSER (depending on the implementation and HW used). . . . John L Hufferd Sr. Executive Director of Technology Brocade Communications Systems, Inc jhufferd@brocade.com Office Phone: (408) 333-5244; eFAX: (408) 904-4688 Alt Office Phone: (408) 997-6136; Cell: (408) 627-9606 -----Original Message----- From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On Behalf Of Mike Ko Sent: Tuesday, November 29, 2005 11:15 AM To: Sanjay Goyal Cc: ips@ietf.org Subject: RE: [Ips] iSER: draft-ietf-ips-iser-05.txt Sanjay, The initiator may well reject the RDMAExtensions offer from the target, but we don't want to preclude the possibility that the initiator might want to accommodate the target and choose to support iSER instead. Mike To: "Mike Ko" <mako@almaden.ibm.com> cc: <ips@ietf.org> Subject: RE: [Ips] iSER: draft-ietf-ips-iser-05.txt Mike, I understand that, the point I was trying to make was if Initiator prefers iSCSI mode, why would it change its mind after it gets RDMAExtensions key from Target. -Sanjay _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips
- [Ips] iSER: draft-ietf-ips-iser-05.txt Sanjay Goyal
- Re: [Ips] iSER: draft-ietf-ips-iser-05.txt Mike Ko
- RE: [Ips] iSER: draft-ietf-ips-iser-05.txt Sanjay Goyal
- RE: [Ips] iSER: draft-ietf-ips-iser-05.txt Mike Ko
- RE: [Ips] iSER: draft-ietf-ips-iser-05.txt John Hufferd