IETF Logo Mail Archive

RE: FW: [Ips] Recent comments about FCoE and iSCSI

"John Hufferd" <jhufferd@Brocade.COM> Thu, 26 April 2007 04:51 UTC

Return-path: <ips-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HgvxS-0006JW-Pn; Thu, 26 Apr 2007 00:51:54 -0400
Received: from ips by megatron.ietf.org with local (Exim 4.43) id 1HgvxR-0006Dy-En for ips-confirm+ok@megatron.ietf.org; Thu, 26 Apr 2007 00:51:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HgvxR-0006Dq-4y for ips@ietf.org; Thu, 26 Apr 2007 00:51:53 -0400
Received: from mx20.brocade.com ([66.243.153.19]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgvxQ-0000yx-GX for ips@ietf.org; Thu, 26 Apr 2007 00:51:53 -0400
Received: from discus.brocade.com ([192.168.126.240]) by mx20.brocade.com with ESMTP; 25 Apr 2007 21:51:51 -0700
X-IronPort-AV: i="4.14,452,1170662400"; d="gif'147?scan'147,208,217,147"; a="8646152:sNHT40399919"
Received: from HQ-EXCHFE-3.corp.brocade.com (unknown [192.168.126.212]) by discus.brocade.com (Postfix) with ESMTP id C469B23836B; Wed, 25 Apr 2007 21:50:40 -0700 (PDT)
Received: from hq-exch-1.corp.brocade.com ([10.3.8.21]) by HQ-EXCHFE-3.corp.brocade.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Apr 2007 21:51:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: FW: [Ips] Recent comments about FCoE and iSCSI
Date: Wed, 25 Apr 2007 21:51:50 -0700
Message-ID: <39BA3BC178B4394DB184389E88A97F8C022C5CC4@hq-exch-1.corp.brocade.com>
In-Reply-To: <368FBF3D8437A748BA8222526BF9309901ACBF42@aime2k302.adaptec.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: FW: [Ips] Recent comments about FCoE and iSCSI
Thread-Index: AceHbhab+EXeFVfgQWiH7jzYWydYaAAKX7IQAAKlUiAABWKvIA==
From: "John Hufferd" <jhufferd@Brocade.COM>
To: "Sandars, Ken" <ken_sandars@adaptec.com>, "Eddy Quicksall" <Quicksall_iSCSI@Bellsouth.net>, "Julian Satran" <Julian_Satran@il.ibm.com>
X-OriginalArrivalTime: 26 Apr 2007 04:51:52.0652 (UTC) FILETIME=[9B8BE0C0:01C787BE]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: abb8110dde048486ea2be9c769692569
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>
Content-Type: multipart/mixed; boundary="===============0503422998=="
Errors-To: ips-bounces@ietf.org

Ken,

The term FCoE has as its primary component FC.  Consider the possibility
that the DCE Link from the Host connects to a switch/device that is able
to deal with the FC part of the FCoE.

 

.

.

.

John L Hufferd

Sr. Executive Director of Technology

jhufferd@brocade.com <mailto:jhufferd@brocade.com> 

Office Phone: (408) 333-5244; eFAX: (408) 904-4688

Alt Office Phone: (408) 997-6136; Cell: (408) 627-9606

 

________________________________

From: Sandars, Ken [mailto:ken_sandars@adaptec.com] 
Sent: Wednesday, April 25, 2007 6:41 PM
To: John Hufferd; Eddy Quicksall; Julian Satran
Cc: ips@ietf.org
Subject: RE: FW: [Ips] Recent comments about FCoE and iSCSI

 

Hey John,

 

[Hufferd] Many servers are asking for an evolutionary way to combine
their Networking connections from the Server.  The customers I have
dealt with do NOT want to rip out FC, they want to provide a single Link
for transport of all networking needs, including storage, exiting their
servers.


I'm not sure what you are saying here. Are you saying servers should
have a single type of physical network connection, presumably ethernet?
How does that align with not wanting to rip out FC?

 

Thanks

Ken


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

v2.8.10 | Report a Bug | By Email