From exim@www1.ietf.org Wed Oct 1 09:49:48 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12581 for ; Wed, 1 Oct 2003 09:49:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4hM3-00016f-Ks for ips-archive@odin.ietf.org; Wed, 01 Oct 2003 09:49:25 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h91DnNZR004249 for ips-archive@odin.ietf.org; Wed, 1 Oct 2003 09:49:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4hM2-00016S-RL for ips-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 09:49:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12559 for ; Wed, 1 Oct 2003 09:49:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4hM1-0007DF-00 for ips-web-archive@ietf.org; Wed, 01 Oct 2003 09:49:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A4hM0-0007DB-00 for ips-web-archive@ietf.org; Wed, 01 Oct 2003 09:49:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4hLh-00015K-Ox; Wed, 01 Oct 2003 09:49:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4aLP-0002aL-4t for ips@optimus.ietf.org; Wed, 01 Oct 2003 02:20:15 -0400 Received: from 380gate02out.mcdata.com (mcjekyll.mcdata.com [144.49.6.25]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18323 for ; Wed, 1 Oct 2003 02:20:06 -0400 (EDT) Received: from 380gate02.mcdata.com ([172.18.1.73]) by 380gate02out.mcdata.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 1 Oct 2003 00:09:31 -0600 Received: from ariel.nishansystems.com ([192.100.100.16]) by 380gate02 with InterScan Messaging Security Suite; Wed, 01 Oct 2003 00:09:30 -0600 Received: by ariel.nishansystems.com with Internet Mail Service (5.5.2653.19) id ; Tue, 30 Sep 2003 23:09:29 -0700 Message-ID: From: Joshua Tseng To: "'dan yo'" , Joshua Tseng , ips@ietf.org Subject: RE: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB Date: Tue, 30 Sep 2003 23:09:28 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C387E2.923CC280" X-OriginalArrivalTime: 01 Oct 2003 06:09:31.0707 (UTC) FILETIME=[944F00B0:01C387E2] Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C387E2.923CC280 Content-Type: text/plain The DD mechanisms in iSNS translate easily into WWN-based zoning in the FC fabric. To do port zoning you may have to do some extra work by storing some additional info in vendor-specific fields, but that doesn't mean it can't be done. Remember, iSNS is just basically an information repository, and it can be used to store pretty much anything including proprietary information. Regards, Josh -----Original Message----- From: dan yo [mailto:ipsandude@yahoo.com] Sent: Tuesday, September 30, 2003 9:39 AM To: Joshua Tseng; ips@ietf.org Subject: RE: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB Josh, Base on the same reasoning that iSNS doesn't support the use of IP subnet as an initiator node in a DD, it doesn't support the (Domain_ID,Port_Number) construct in a FC zone, correct? Thanks, Dan Joshua Tseng wrote: Dan, Contact me offline if you want help writing a draft. Regarding your question, in iSNS connectivity between iSCSI devices is established by DD membership. DD membership for an iSCSI device can only be established by iSCSI Name. Portal membership in a DD only indicates the preferred interface for iSCSI sessions, and by itself does not indicate DD membership for any iSCSI device. So the answer is 'no', you cannot establish DD membership by IP subnet. Josh -----Original Message----- From: dan yo [mailto:ipsandude@yahoo.com] Sent: Monday, September 29, 2003 9:37 AM To: Joshua Tseng; ips@ietf.org Subject: RE: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB Joshua, Thanks. Regardinig #2, I would be interested in writing a paper after I have explored more on the interoperability issues in bridging FC zones to iSNS, will definitely need more of your help. I don't believe this qualifies for IETF draft or RFC, but having a more well defined rules in mapping FC zones to iSNS will simplify the job of managing a mixed FC/iSCSI SAN. On a related question, is there a way to specify a IP subnet as an iSCSI Initiator node in a Discovery Domain -- the intent is to allow all the hosts on a subnet to access the targets in the corresponding DD. Regards, Dan Joshua Tseng wrote: Dan, Here are my responses: 1) Yes, as alluded to in the iSNS draft. You understood it well. 2) You are welcome to write a paper or RFC if you desire. I am willing to help you out. 3) Yes. Regards, Josh -----Original Message----- From: dan yo [mailto:ipsandude@yahoo.com] Sent: Sunday, September 28, 2003 10:56 PM To: ips@ietf.org Subject: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB Hi, I would like to get some opinions and thoughts on mapping FC Zone Server DB to iSNS DB in a single or multiple fabrics, mixed protocol SAN switches environment. Based on my understanding of the FC-GS, FC-SW, and the iSNS draft, FC zone objects are mapped to iSNS objects as follow: FC zone maps to iSNS DD (Discovery Domain). FC zone set maps to iSNS DD Set. FC fabric maps to iSNS Network Entity. Assume we have a multi-fabric SAN with mixed FC and iSCSI switches, and FC/iSCSI gateways. We want to create a central iSNS database to store all the devices, where some of the devices are exported from the FC zone DBs, and some are registered from the iSNS capable clients (most likely iSCSI devices). With the central iSNS server, iSNS capable management stations now have a full view of the whole multi-fabric SAN. My questions are: 1. Would iSNS serve well for the above application? 2. When FC Zone DBs are merged or segmented, how the FC Zone DBs are synchronized with the iSNS DB is an implementation issue, but has anybody written any guideline or paper on this? If not, would this subject be a good ietf draft/rfc candidate? 3. Is there any such product on the market from the major SAN switch manufacturers (that exports and maps FC Zone DB to iSNS server)? Thanks, Dan _____ Do you Yahoo!? The New Yahoo! Shopping - with improved product search SPECIAL NOTICE All information transmitted hereby is intended only for the use of the addressee(s) named above and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of confidential and privileged information is prohibited. If the reader of this message is not the intended recipient(s) or the employee or agent responsible for delivering the message to the intended recipient, you are herby notified that you must not read this transmission and that disclosure, copying, printing, distribution or use of any of the information contained in or attached to ! this transmission is STRICTLY PROHIBITED. Anyone who receives confidential and privileged information in error should notify us immediately by telephone and mail the original message to us at the above address and destroy all copies. To the extent any portion of this communication contains public information, no such restrictions apply to that information. (gate01) _____ Do you Yahoo!? The New Yahoo! Shopping - with improved product search _____ Do you Yahoo!? The New Yahoo! Shopping - with improved product search ------_=_NextPart_001_01C387E2.923CC280 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Message
The DD=20 mechanisms in iSNS translate easily into WWN-based zoning in = the FC=20 fabric.  To do port zoning you may have to do some extra work by = storing=20 some additional info in vendor-specific fields, but that doesn't mean = it can't=20 be done.  Remember, iSNS is just basically an information = repository,=20 and it can be used to store pretty much anything including proprietary=20 information.
 
Regards,
Josh
-----Original Message-----
From: dan = yo=20 [mailto:ipsandude@yahoo.com]
Sent: Tuesday, September 30, = 2003 9:39=20 AM
To: Joshua Tseng; ips@ietf.org
Subject: RE: = [Ips] iSNS:=20 question on exporting FC Zone DB to iSNS DB

Josh,
 
Base on the same reasoning that iSNS doesn't support the use of = IP=20 subnet
as an initiator node in a DD, it doesn't support=20 the (Domain_ID,Port_Number)
construct in a FC zone, correct? 
 
Thanks,
Dan

Joshua Tseng <Joshua.Tseng@mcdata.com>=20 wrote:

Dan,

 

Contact = me offline=20 if you want help writing a=20 = draft.           =             =             =             =   =20

 

Regarding your=20 question, in iSNS connectivity between iSCSI devices is established = by DD=20 membership.  DD membership for an iSCSI device can only be = established=20 by iSCSI Name.  Portal membership in a DD only indicates the = preferred=20 interface for iSCSI sessions, and by itself does not indicate DD = membership=20 for any iSCSI device.  So the answer is 'no', you cannot = establish DD=20 membership by IP subnet.

 

Josh

 

-----Original=20 Message-----
From: dan yo=20 [mailto:ipsandude@yahoo.com]
Sent: Monday, September 29, = 2003 9:37=20 AM
To: Joshua = Tseng;=20 ips@ietf.org
Subject: RE:=20 [Ips] iSNS: question on exporting FC Zone DB to iSNS = DB

 

Joshua,

 

Thanks.  =

 

Regardinig #2, = I would be=20 interested in writing a paper after I have=20 explored 

more on the = interoperability=20 issues in bridging FC zones to iSNS, = will

definitely need more of = your=20 help.  I don't believe this qualifies for IETF draft=20

or RFC, but having a = more well=20 defined rules in mapping FC zones to = iSNS 

will simplify the job of = managing a=20 mixed FC/iSCSI SAN.

On a related = question, is there a=20 way to specify a IP subnet as an iSCSI =

Initiator node in a = Discovery Domain --=20 the intent is to allow all the hosts

on a subnet to access = the targets=20 in the corresponding DD.

 

Regards,

Dan


Joshua Tseng=20 <Joshua.Tseng@mcdata.com>=20 wrote:

Dan,

 

Here=20 are my responses:

 

1)      =20 Yes, = as alluded=20 to in the iSNS draft.  You understood it = well.

2)      =20 You = are welcome=20 to write a paper or RFC if you desire.  I am willing to help = you=20 out.

3)      =20 Yes.

 

Regards,

Josh

 

 

 

-----Original=20 Message-----
From: dan yo=20 [mailto:ipsandude@yahoo.com]
Sent: Sunday, September = 28, 2003=20 10:56 PM
To:=20 ips@ietf.org
Subject:=20 [Ips] iSNS: question on exporting FC Zone DB to iSNS = DB

 

Hi,

 

I would like to get=20 some opinions and thoughts on mapping FC Zone = Server=20 DB

to iSNS DB in a = single or=20 multiple fabrics, mixed protocol SAN switches =

environment.

 

Based on my = understanding of the=20 FC-GS, FC-SW, and the iSNS draft, FC zone =

objects are mapped to = iSNS objects as=20 follow:

 

  FC zone maps = to=20 iSNS DD (Discovery Domain).

  FC zone set maps = to=20 iSNS DD Set.

  FC fabric maps to = iSNS Network=20 Entity.

 

Assume we have a=20 multi-fabric SAN with mixed FC and=20 iSCSI switches,

and FC/iSCSI=20 gateways.

We want to create a = central iSNS=20 database to store all the devices,

where some of the = devices=20 are exported from the FC zone DBs, and some=20

are registered from = the iSNS=20 capable clients (most likely iSCSI devices). =20

With the central iSNS = server, iSNS=20 capable management stations now

have a full view of the = whole=20 multi-fabric SAN. 

 

My questions=20 are:

 

1. Would iSNS serve = well for the=20 above application?

2. When FC Zone DBs are = merged or=20 segmented, how the FC Zone DBs

    are = synchronized=20 with the iSNS DB is an implementation issue,=20 but 

    has = anybody=20 written any guideline or paper = on this?

    If not, would=20 this subject be a good ietf draft/rfc = candidate?

3. Is there any such = product on the=20 market from the major SAN switch

    = manufacturers=20 (that exports and maps FC Zone DB to iSNS=20 server)?

 

Thanks,

Dan

 

Do you Yahoo!?
The=20 New Yahoo! Shopping - with improved product = search

SPECIAL NOTICE =

 
All information transmitted hereby is intended only for the use =
of the
addressee(s) =
named above and may contain confidential and =
privileged
information. Any unauthorized review, use, disclosure or =
distribution
of =
confidential and privileged information is prohibited. If the =
reader
of this message =
is not the intended recipient(s) or the employee or =
agent
responsible for =
delivering the message to the intended recipient, you =
are
herby notified =
that you must not read this transmission and that =
disclosure,
copying, printing, distribution or use of any of the information =
contained
in =
or attached to !
 this
 transmission is STRICTLY PROHIBITED.
 
Anyone who receives confidential and privileged =
information in error should
notify us immediately by telephone and mail the =
original message to us at
the above address and destroy all copies.  To the extent =
any portion of this
communication contains public information, no such restrictions =
apply to that
information. =
(gate01)

Do you Yahoo!?
The=20 New Yahoo! Shopping - with improved product=20 search

Do you Yahoo!?
The=20 New Yahoo! Shopping - with improved product=20 search ------_=_NextPart_001_01C387E2.923CC280-- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Wed Oct 1 12:09:38 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21330 for ; Wed, 1 Oct 2003 12:09:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jXP-0002uC-OY for ips-archive@odin.ietf.org; Wed, 01 Oct 2003 12:09:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h91G9F0G011164 for ips-archive@odin.ietf.org; Wed, 1 Oct 2003 12:09:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jXP-0002ty-3q for ips-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 12:09:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21298 for ; Wed, 1 Oct 2003 12:09:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4jXN-0001W9-00 for ips-web-archive@ietf.org; Wed, 01 Oct 2003 12:09:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A4jXN-0001W6-00 for ips-web-archive@ietf.org; Wed, 01 Oct 2003 12:09:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jXB-0002ox-6o; Wed, 01 Oct 2003 12:09:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4jWT-0002lx-T8 for ips@optimus.ietf.org; Wed, 01 Oct 2003 12:08:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21259 for ; Wed, 1 Oct 2003 12:08:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4jWS-0001VT-00 for ips@ietf.org; Wed, 01 Oct 2003 12:08:16 -0400 Received: from mcjekyll.mcdata.com ([144.49.6.25] helo=380gate02out.mcdata.com) by ietf-mx with esmtp (Exim 4.12) id 1A4jWR-0001Uu-00 for ips@ietf.org; Wed, 01 Oct 2003 12:08:15 -0400 Received: from 380gate02.mcdata.com ([172.18.1.73]) by 380gate02out.mcdata.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 1 Oct 2003 10:07:45 -0600 Received: from ariel.nishansystems.com ([192.100.100.16]) by 380gate02 with InterScan Messaging Security Suite; Wed, 01 Oct 2003 10:07:44 -0600 Received: by ariel.nishansystems.com with Internet Mail Service (5.5.2653.19) id ; Wed, 1 Oct 2003 09:07:43 -0700 Message-ID: From: Joshua Tseng To: "'ips@ietf.org'" Subject: RE: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB Date: Wed, 1 Oct 2003 09:07:35 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C38836.20770B70" X-OriginalArrivalTime: 01 Oct 2003 16:07:45.0590 (UTC) FILETIME=[26BAE560:01C38836] Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C38836.20770B70 Content-Type: text/plain The DD mechanisms in iSNS translate easily into WWN-based zoning in the FC fabric. To do port zoning you may have to do some extra work by storing some additional info in vendor-specific fields, but that doesn't mean it can't be done. Remember, iSNS is just basically an information repository, and it can be used to store pretty much anything including proprietary information. Regards, Josh -----Original Message----- From: dan yo [mailto:ipsandude@yahoo.com] Sent: Tuesday, September 30, 2003 9:39 AM To: Joshua Tseng; ips@ietf.org Subject: RE: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB Josh, Base on the same reasoning that iSNS doesn't support the use of IP subnet as an initiator node in a DD, it doesn't support the (Domain_ID,Port_Number) construct in a FC zone, correct? Thanks, Dan Joshua Tseng wrote: Dan, Contact me offline if you want help writing a draft. Regarding your question, in iSNS connectivity between iSCSI devices is established by DD membership. DD membership for an iSCSI device can only be established by iSCSI Name. Portal membership in a DD only indicates the preferred interface for iSCSI sessions, and by itself does not indicate DD membership for any iSCSI device. So the answer is 'no', you cannot establish DD membership by IP subnet. Josh -----Original Message----- From: dan yo [mailto:ipsandude@yahoo.com] Sent: Monday, September 29, 2003 9:37 AM To: Joshua Tseng; ips@ietf.org Subject: RE: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB Joshua, Thanks. Regardinig #2, I would be interested in writing a paper after I have explored more on the interoperability issues in bridging FC zones to iSNS, will definitely need more of your help. I don't believe this qualifies for IETF draft or RFC, but having a more well defined rules in mapping FC zones to iSNS will simplify the job of managing a mixed FC/iSCSI SAN. On a related question, is there a way to specify a IP subnet as an iSCSI Initiator node in a Discovery Domain -- the intent is to allow all the hosts on a subnet to access the targets in the corresponding DD. Regards, Dan Joshua Tseng wrote: Dan, Here are my responses: 1) Yes, as alluded to in the iSNS draft. You understood it well. 2) You are welcome to write a paper or RFC if you desire. I am willing to help you out. 3) Yes. Regards, Josh -----Original Message----- From: dan yo [mailto:ipsandude@yahoo.com] Sent: Sunday, September 28, 2003 10:56 PM To: ips@ietf.org Subject: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB Hi, I would like to get some opinions and thoughts on mapping FC Zone Server DB to iSNS DB in a single or multiple fabrics, mixed protocol SAN switches environment. Based on my understanding of the FC-GS, FC-SW, and the iSNS draft, FC zone objects are mapped to iSNS objects as follow: FC zone maps to iSNS DD (Discovery Domain). FC zone set maps to iSNS DD Set. FC fabric maps to iSNS Network Entity. Assume we have a multi-fabric SAN with mixed FC and iSCSI switches, and FC/iSCSI gateways. We want to create a central iSNS database to store all the devices, where some of the devices are exported from the FC zone DBs, and some are registered from the iSNS capable clients (most likely iSCSI devices). With the central iSNS server, iSNS capable management stations now have a full view of the whole multi-fabric SAN. My questions are: 1. Would iSNS serve well for the above application? 2. When FC Zone DBs are merged or segmented, how the FC Zone DBs are synchronized with the iSNS DB is an implementation issue, but has anybody written any guideline or paper on this? If not, would this subject be a good ietf draft/rfc candidate? 3. Is there any such product on the market from the major SAN switch manufacturers (that exports and maps FC Zone DB to iSNS server)? Thanks, Dan _____ Do you Yahoo!? The New Yahoo! Shopping - with improved product search SPECIAL NOTICE All information transmitted hereby is intended only for the use of the addressee(s) named above and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of confidential and privileged information is prohibited. If the reader of this message is not the intended recipient(s) or the employee or agent responsible for delivering the message to the intended recipient, you are herby notified that you must not read this transmission and that disclosure, copying, printing, distribution or use of any of the information contained in or attached to ! this transmission is STRICTLY PROHIBITED. Anyone who receives confidential and privileged information in error should notify us immediately by telephone and mail the original message to us at the above address and destroy all copies. To the extent any portion of this communication contains public information, no such restrictions apply to that information. (gate01) _____ Do you Yahoo!? The New Yahoo! Shopping - with improved product search _____ Do you Yahoo!? The New Yahoo! Shopping - with improved product search ------_=_NextPart_001_01C38836.20770B70 Content-Type: text/html Message

The DD mechanisms in iSNS translate easily into WWN-based zoning in the FC fabric.  To do port zoning you may have to do some extra work by storing some additional info in vendor-specific fields, but that doesn't mean it can't be done.  Remember, iSNS is just basically an information repository, and it can be used to store pretty much anything including proprietary information.

 

Regards,

Josh

-----Original Message-----
From: dan yo [mailto:ipsandude@yahoo.com]
Sent: Tuesday, September 30, 2003 9:39 AM
To: Joshua Tseng; ips@ietf.org
Subject: RE: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB

Josh,

 

Base on the same reasoning that iSNS doesn't support the use of IP subnet

as an initiator node in a DD, it doesn't support the (Domain_ID,Port_Number)

construct in a FC zone, correct? 

 

Thanks,

Dan


Joshua Tseng <Joshua.Tseng@mcdata.com> wrote:

Dan,

 

Contact me offline if you want help writing a draft.                                                 

 

Regarding your question, in iSNS connectivity between iSCSI devices is established by DD membership.  DD membership for an iSCSI device can only be established by iSCSI Name.  Portal membership in a DD only indicates the preferred interface for iSCSI sessions, and by itself does not indicate DD membership for any iSCSI device.  So the answer is 'no', you cannot establish DD membership by IP subnet.

 

Josh

 

-----Original Message-----
From: dan yo [mailto:ipsandude@yahoo.com]
Sent: Monday, September 29, 2003 9:37 AM
To: Joshua Tseng; ips@ietf.org
Subject: RE: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB

 

Joshua,

 

Thanks. 

 

Regardinig #2, I would be interested in writing a paper after I have explored 

more on the interoperability issues in bridging FC zones to iSNS, will

definitely need more of your help.  I don't believe this qualifies for IETF draft

or RFC, but having a more well defined rules in mapping FC zones to iSNS 

will simplify the job of managing a mixed FC/iSCSI SAN.

On a related question, is there a way to specify a IP subnet as an iSCSI

Initiator node in a Discovery Domain -- the intent is to allow all the hosts

on a subnet to access the targets in the corresponding DD.

 

Regards,

Dan


Joshua Tseng <Joshua.Tseng@mcdata.com> wrote:

Dan,

 

Here are my responses:

 

1)       Yes, as alluded to in the iSNS draft.  You understood it well.

2)       You are welcome to write a paper or RFC if you desire.  I am willing to help you out.

3)       Yes.

 

Regards,

Josh

 

 

 

-----Original Message-----
From: dan yo [mailto:ipsandude@yahoo.com]
Sent: Sunday, September 28, 2003 10:56 PM
To: ips@ietf.org
Subject: [Ips] iSNS: question on exporting FC Zone DB to iSNS DB

 

Hi,

 

I would like to get some opinions and thoughts on mapping FC Zone Server DB

to iSNS DB in a single or multiple fabrics, mixed protocol SAN switches

environment.

 

Based on my understanding of the FC-GS, FC-SW, and the iSNS draft, FC zone

objects are mapped to iSNS objects as follow:

 

  FC zone maps to iSNS DD (Discovery Domain).

  FC zone set maps to iSNS DD Set.

  FC fabric maps to iSNS Network Entity.

 

Assume we have a multi-fabric SAN with mixed FC and iSCSI switches,

and FC/iSCSI gateways.

We want to create a central iSNS database to store all the devices,

where some of the devices are exported from the FC zone DBs, and some

are registered from the iSNS capable clients (most likely iSCSI devices). 

With the central iSNS server, iSNS capable management stations now

have a full view of the whole multi-fabric SAN. 

 

My questions are:

 

1. Would iSNS serve well for the above application?

2. When FC Zone DBs are merged or segmented, how the FC Zone DBs

    are synchronized with the iSNS DB is an implementation issue, but 

    has anybody written any guideline or paper on this?

    If not, would this subject be a good ietf draft/rfc candidate?

3. Is there any such product on the market from the major SAN switch

    manufacturers (that exports and maps FC Zone DB to iSNS server)?

 

Thanks,

Dan

 

Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

SPECIAL NOTICE 
 
All information transmitted hereby is intended only for the use of the
addressee(s) named above and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution
of confidential and privileged information is prohibited. If the reader
of this message is not the intended recipient(s) or the employee or agent
responsible for delivering the message to the intended recipient, you are
herby notified that you must not read this transmission and that disclosure,
copying, printing, distribution or use of any of the information contained
in or attached to !
 this
 transmission is STRICTLY PROHIBITED.
 
Anyone who receives confidential and privileged information in error should
notify us immediately by telephone and mail the original message to us at
the above address and destroy all copies.  To the extent any portion of this
communication contains public information, no such restrictions apply to that
information. (gate01)

Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

------_=_NextPart_001_01C38836.20770B70-- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Fri Oct 10 15:19:43 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14781 for ; Fri, 10 Oct 2003 15:19:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A82nI-0003se-Rx for ips-archive@odin.ietf.org; Fri, 10 Oct 2003 15:19:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AJJKv8014912 for ips-archive@odin.ietf.org; Fri, 10 Oct 2003 15:19:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A82nI-0003sR-Me for ips-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 15:19:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14773 for ; Fri, 10 Oct 2003 15:19:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A82nH-0000IB-00 for ips-web-archive@ietf.org; Fri, 10 Oct 2003 15:19:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A82nH-0000I7-00 for ips-web-archive@ietf.org; Fri, 10 Oct 2003 15:19:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A82mz-0003rh-02; Fri, 10 Oct 2003 15:19:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A82mR-0003rB-DI for ips@optimus.ietf.org; Fri, 10 Oct 2003 15:18:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14724 for ; Fri, 10 Oct 2003 15:18:19 -0400 (EDT) From: Black_David@emc.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A82mP-0000I4-00 for ips@ietf.org; Fri, 10 Oct 2003 15:18:25 -0400 Received: from unk-for-smtp.isus.emc.com ([128.222.32.10] helo=mxic1.corp.emc.com) by ietf-mx with esmtp (Exim 4.12) id 1A82mP-0000Hr-00 for ips@ietf.org; Fri, 10 Oct 2003 15:18:25 -0400 Received: by mxic1.corp.emc.com with Internet Mail Service (5.5.2653.19) id <4STRG5CQ>; Fri, 10 Oct 2003 15:17:50 -0400 Message-ID: To: ips@ietf.org Date: Fri, 10 Oct 2003 15:17:48 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [Ips] No IPS meeting in Minneapolis Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Due to the absence of significant open technical items to work on, the IP Storage WG will not be meeting in Minneapolis. The WG chairs are continuing to work with our ADs and draft authors on getting our drafts published as RFCs. Thanks, --David (for David & Elizabeth, IPS WG chairs) ---------------------------------------------------- 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 ---------------------------------------------------- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Fri Oct 10 16:08:35 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19249 for ; Fri, 10 Oct 2003 16:08:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A83Yb-0000QN-0M for ips-archive@odin.ietf.org; Fri, 10 Oct 2003 16:08:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AK8CtF001625 for ips-archive@odin.ietf.org; Fri, 10 Oct 2003 16:08:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A83Ya-0000Q8-Lo for ips-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 16:08:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19174 for ; Fri, 10 Oct 2003 16:08:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A83YY-0001Yp-00 for ips-web-archive@ietf.org; Fri, 10 Oct 2003 16:08:10 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A83YY-0001Ym-00 for ips-web-archive@ietf.org; Fri, 10 Oct 2003 16:08:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A83YQ-0000MJ-2s; Fri, 10 Oct 2003 16:08:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A83XS-00008x-Rf for ips@optimus.ietf.org; Fri, 10 Oct 2003 16:07:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19112 for ; Fri, 10 Oct 2003 16:06:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A83XQ-0001X3-00 for ips@ietf.org; Fri, 10 Oct 2003 16:07:01 -0400 Received: from atlrel9.hp.com ([156.153.255.214]) by ietf-mx with esmtp (Exim 4.12) id 1A83XQ-0001Wr-00 for ips@ietf.org; Fri, 10 Oct 2003 16:07:00 -0400 Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.96.64.26]) by atlrel9.hp.com (Postfix) with ESMTP id 7C5FB1C01E2E; Fri, 10 Oct 2003 16:06:53 -0400 (EDT) Received: from dhcp-roseor-bec059.rose.hp.com (dhcp-roseor-bec059.rose.hp.com [15.23.142.59]) by rosemail.rose.hp.com with ESMTP (8.7.1/8.7.3 SMKit7.02) id NAA28074; Fri, 10 Oct 2003 13:06:52 -0700 (PDT) Date: Fri, 10 Oct 2003 13:06:54 -0700 From: "Mallikarjun C." To: Black_David@emc.com, ips@ietf.org Subject: Re: [Ips] No IPS meeting in Minneapolis Message-ID: <489528004.1065791214@dhcp-roseor-bec059.rose.hp.com> In-Reply-To: References: X-Mailer: Mulberry/3.1.0b8 (Win32 Demo) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit David, There are quite a few of us who would like the IPS WG to approve the iSER and DA I-Ds as official WG docs - in order to extend iSCSI's capabilities to be generic RDMA-capable. To that end, the authors of these drafts have requested time for presenting those drafts a short while ago with the co-chairs. It may have crossed this email on the Net. While the authors ideally would like a formal WG meeting for seeking charter enhancements, I can also see that doing so given the seeming lack of other agenda items may not be most efficient. OTOH, I am afraid that this fact would remain the same even for the next IETF in Seoul, aside from the fact that it causes more delay when the authors believe the drafts are ready for WG consideration. Could you please recommend the most optimal course of action to request and enhance the WG charter? Regards. -- Mallikarjun Mallikarjun Chadalapaka Networked Storage Architecture Network Storage Solutions Hewlett-Packard MS 5668 Roseville CA 95747 cbm@rose.hp.com --On Friday, October 10, 2003 3:17 PM -0400 Black_David@emc.com wrote: > Due to the absence of significant open technical items > to work on, the IP Storage WG will not be meeting in > Minneapolis. The WG chairs are continuing to work with > our ADs and draft authors on getting our drafts published > as RFCs. > > Thanks, > --David (for David & Elizabeth, IPS WG chairs) > > ---------------------------------------------------- > 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 > ---------------------------------------------------- > > > _______________________________________________ > 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 From exim@www1.ietf.org Tue Oct 14 15:35:50 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26318 for ; Tue, 14 Oct 2003 15:35:50 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Ux7-0003LT-0A for ips-archive@odin.ietf.org; Tue, 14 Oct 2003 15:35:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EJZSr2012859 for ips-archive@odin.ietf.org; Tue, 14 Oct 2003 15:35:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Ux6-0003LK-RF for ips-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 15:35:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26230 for ; Tue, 14 Oct 2003 15:35:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9Ux5-0006wb-00 for ips-web-archive@ietf.org; Tue, 14 Oct 2003 15:35:27 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A9Ux5-0006wR-00 for ips-web-archive@ietf.org; Tue, 14 Oct 2003 15:35:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Uwh-0003Jp-5B; Tue, 14 Oct 2003 15:35:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9UwZ-0003JQ-T1 for ips@optimus.ietf.org; Tue, 14 Oct 2003 15:34:55 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26138; Tue, 14 Oct 2003 15:34:46 -0400 (EDT) Message-Id: <200310141934.PAA26138@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ips@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 14 Oct 2003 15:34:46 -0400 Subject: [Ips] I-D ACTION:draft-ietf-ips-isns-21.txt Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Storage Working Group of the IETF. Title : Internet Storage Name Service (iSNS) Author(s) : J. Tseng, K. Gibbons, et. al. Filename : draft-ietf-ips-isns-21.txt Pages : 112 Date : 2003-10-14 This document specifies the Internet Storage Name Service (iSNS) protocol, which is used for interaction between iSNS servers and iSNS clients in order to facilitate automated discovery, management, and configuration of iSCSI and Fibre Channel devices (using iFCP gateways) on a TCP/IP network. iSNS provides intelligent storage discovery and management services comparable to those found in Fibre Channel networks, allowing a commodity IP network to function in a similar capacity as a storage area network. iSNS also facilitates a seamless integration of IP and Fibre Channel networks, due to its ability to emulate Fibre Channel fabric services, and manage both iSCSI and Fibre Channel devices. iSNS thereby provides value in any storage network comprised of iSCSI devices, Fibre Channel devices (using iFCP gateways), or any combination thereof. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ips-isns-21.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-ips-isns-21.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-ips-isns-21.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: <2003-10-14133812.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ips-isns-21.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ips-isns-21.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-14133812.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Wed Oct 15 19:15:48 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29333 for ; Wed, 15 Oct 2003 19:15:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9urV-0006bE-V5 for ips-archive@odin.ietf.org; Wed, 15 Oct 2003 19:15:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9FNFP9f025365 for ips-archive@odin.ietf.org; Wed, 15 Oct 2003 19:15:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9urV-0006b2-O1 for ips-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 19:15:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29327 for ; Wed, 15 Oct 2003 19:15:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9urU-0005G1-00 for ips-web-archive@ietf.org; Wed, 15 Oct 2003 19:15:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A9urT-0005Fx-00 for ips-web-archive@ietf.org; Wed, 15 Oct 2003 19:15:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9ur7-0006Zs-NU; Wed, 15 Oct 2003 19:15:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9uqs-0006ZU-Fj for ips@optimus.ietf.org; Wed, 15 Oct 2003 19:14:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29304 for ; Wed, 15 Oct 2003 19:14:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9uqq-0005FY-00 for ips@ietf.org; Wed, 15 Oct 2003 19:14:44 -0400 Received: from palrel13.hp.com ([156.153.255.238]) by ietf-mx with esmtp (Exim 4.12) id 1A9uqq-0005FV-00 for ips@ietf.org; Wed, 15 Oct 2003 19:14:44 -0400 Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.96.64.26]) by palrel13.hp.com (Postfix) with ESMTP id E27431C0178D; Wed, 15 Oct 2003 16:14:43 -0700 (PDT) Received: from swathi.rose.hp.com (dhcp-roseor-bec059.rose.hp.com [15.23.142.59]) by rosemail.rose.hp.com with ESMTP (8.7.1/8.7.3 SMKit7.02) id QAA17978; Wed, 15 Oct 2003 16:14:43 -0700 (PDT) Message-Id: <6.0.0.22.1.20031015155618.029bef98@rosemail.rose.hp.com> X-Sender: cbm@rosemail.rose.hp.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Wed, 15 Oct 2003 16:14:46 -0700 To: From: "Mallikarjun C." Cc: ips@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Ips] iSCSI: length clarifications Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Julian, In reviewing the port name text in section 3.4.2, I noticed the following: a text encoding as a hex-constant (see Section 5.1 Text Format) of the ISID (for SCSI initiator port) or the portal group tag (for SCSI target port) including the initial 0X or 0x and the terminating null (14 bytes). Given that ISID is 6 bytes binary (hence 12 nibbles), I think the 14 bytes account only for length "not including the terminating null". It would be good to fix it if we can. In addition, a less critical (but useful) clarification is for text in section 3.2.6.1 which says "Initiators and targets MUST support the receipt of iSCSI names of up to the maximum length of 223 bytes." I suggest adding the same "not including the terminating null" qualifier at the end of the quoted sentence as well. Regards. -- Mallikarjun Mallikarjun Chadalapaka Networked Storage Architecture Network Storage Solutions Hewlett-Packard, Roseville cbm [at] rose.hp.com _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Thu Oct 16 06:10:49 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26759 for ; Thu, 16 Oct 2003 06:10:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA55Q-0004iD-W1 for ips-archive@odin.ietf.org; Thu, 16 Oct 2003 06:10:30 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9GAASEU018109 for ips-archive@odin.ietf.org; Thu, 16 Oct 2003 06:10:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA55Q-0004i0-KA for ips-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 06:10:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26726 for ; Thu, 16 Oct 2003 06:10:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AA55M-0002s6-00 for ips-web-archive@ietf.org; Thu, 16 Oct 2003 06:10:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AA55L-0002s3-00 for ips-web-archive@ietf.org; Thu, 16 Oct 2003 06:10:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA551-0004eW-Dk; Thu, 16 Oct 2003 06:10:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA54e-0004do-QL for ips@optimus.ietf.org; Thu, 16 Oct 2003 06:09:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26670 for ; Thu, 16 Oct 2003 06:09:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AA54a-0002r1-00 for ips@ietf.org; Thu, 16 Oct 2003 06:09:36 -0400 Received: from d12lmsgate-3.de.ibm.com ([194.196.100.236] helo=d12lmsgate.de.ibm.com) by ietf-mx with esmtp (Exim 4.12) id 1AA54Z-0002qV-00 for ips@ietf.org; Thu, 16 Oct 2003 06:09:35 -0400 Received: from d12relay02.megacenter.de.ibm.com (d12relay02.megacenter.de.ibm.com [9.149.165.196]) by d12lmsgate.de.ibm.com (8.12.10/8.12.8) with ESMTP id h9GA8tXZ051338; Thu, 16 Oct 2003 12:09:03 +0200 Received: from d10ml001.telaviv.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228]) by d12relay02.megacenter.de.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9GA8iWm267620; Thu, 16 Oct 2003 12:08:45 +0200 In-Reply-To: <6.0.0.22.1.20031015155618.029bef98@rosemail.rose.hp.com> To: "Mallikarjun C." Cc: ips@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.2CF2 July 23, 2003 From: "Julian Satran" Message-ID: Date: Thu, 16 Oct 2003 12:08:42 +0200 X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 5.0.9a |January 7, 2002) at 16/10/2003 12:08:45, Serialize complete at 16/10/2003 12:08:45 Content-Type: multipart/alternative; boundary="=_alternative 0037B89AC2256DC1_=" Subject: [Ips] Re: iSCSI: length clarifications Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , This is a multipart message in MIME format. --=_alternative 0037B89AC2256DC1_= Content-Type: text/plain; charset="US-ASCII" makes sense - Julo "Mallikarjun C." 16/10/2003 01:14 To Julian Satran/Haifa/IBM@IBMIL cc ips@ietf.org Subject iSCSI: length clarifications Julian, In reviewing the port name text in section 3.4.2, I noticed the following: a text encoding as a hex-constant (see Section 5.1 Text Format) of the ISID (for SCSI initiator port) or the portal group tag (for SCSI target port) including the initial 0X or 0x and the terminating null (14 bytes). Given that ISID is 6 bytes binary (hence 12 nibbles), I think the 14 bytes account only for length "not including the terminating null". It would be good to fix it if we can. In addition, a less critical (but useful) clarification is for text in section 3.2.6.1 which says "Initiators and targets MUST support the receipt of iSCSI names of up to the maximum length of 223 bytes." I suggest adding the same "not including the terminating null" qualifier at the end of the quoted sentence as well. Regards. -- Mallikarjun Mallikarjun Chadalapaka Networked Storage Architecture Network Storage Solutions Hewlett-Packard, Roseville cbm [at] rose.hp.com --=_alternative 0037B89AC2256DC1_= Content-Type: text/html; charset="US-ASCII"
makes sense - Julo


"Mallikarjun C." <cbm@rose.hp.com>

16/10/2003 01:14

To
Julian Satran/Haifa/IBM@IBMIL
cc
ips@ietf.org
Subject
iSCSI: length clarifications





Julian,

In reviewing the port name text in section 3.4.2, I noticed the
following:
a text encoding as a hex-constant (see Section 5.1 Text
Format) of the ISID (for SCSI initiator port) or the
portal group tag (for SCSI target port) including the
initial 0X or 0x and the terminating null (14 bytes).

Given that ISID is 6 bytes binary (hence 12 nibbles), I think the
14 bytes account only for length "not including the terminating
null".  It would be good to fix it if we can.

In addition, a less critical (but useful) clarification is for text in
section 3.2.6.1 which says
"Initiators and targets MUST support the receipt of
iSCSI names of up to the maximum length of 223 bytes."

I suggest adding the same "not including the terminating null"
qualifier at the end of the quoted sentence as well.

Regards.
--
Mallikarjun

Mallikarjun Chadalapaka
Networked Storage Architecture
Network Storage Solutions
Hewlett-Packard, Roseville
cbm [at] rose.hp.com
--=_alternative 0037B89AC2256DC1_=-- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Thu Oct 16 10:20:38 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04960 for ; Thu, 16 Oct 2003 10:20:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA8zD-0004iq-7F for ips-archive@odin.ietf.org; Thu, 16 Oct 2003 10:20:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9GEKJL4018146 for ips-archive@odin.ietf.org; Thu, 16 Oct 2003 10:20:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA8zC-0004ib-Vp for ips-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 10:20:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04934 for ; Thu, 16 Oct 2003 10:20:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AA8zA-0005IZ-00 for ips-web-archive@ietf.org; Thu, 16 Oct 2003 10:20:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AA8zA-0005IW-00 for ips-web-archive@ietf.org; Thu, 16 Oct 2003 10:20:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA8yx-0004gp-2I; Thu, 16 Oct 2003 10:20:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA8xy-0004fQ-Pe for ips@optimus.ietf.org; Thu, 16 Oct 2003 10:19:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04865 for ; Thu, 16 Oct 2003 10:18:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AA8xw-0005HL-00 for ips@ietf.org; Thu, 16 Oct 2003 10:19:00 -0400 Received: from [139.93.4.240] (helo=cnt.cnt.com) by ietf-mx with esmtp (Exim 4.12) id 1AA8xv-0005Gr-00 for ips@ietf.org; Thu, 16 Oct 2003 10:18:59 -0400 Received: from balrog.cnt.com (balrog.cnt.com [139.93.4.21]) by cnt.cnt.com (8.12.8/8.11.3) with SMTP id h9GEH5j6007239 for ; Thu, 16 Oct 2003 09:17:05 -0500 (CDT) Received: by balrog.cnt.com (SMI-8.6/SMI-SVR4) id HAA01601; Thu, 16 Oct 2003 07:18:23 -0700 From: bretk@cnt.cnt.com (Bret Ketchum) Message-Id: <200310161418.HAA01601@balrog.cnt.com> To: ips@ietf.org Date: Thu, 16 Oct 2003 09:18:22 -0500 (CDT) X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Ips] Clarification regarding FCIP-MGMT-MIB Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit All, I'm looking for a little clarification regarding the FCIP-MGMT-MIB and entity identifiers described in the Fibre Channel Over TCP/IP draft and FC-BB-2. Can I believe the MIB's fcipDeviceWWN corresponds to what FC-BB-2 calls a Switch_Name (for the VE_Port) or a Fabric_Name (B_Port)? As the fcipLinkTable is indexed by an fcipEntityId and the fcipLinkTable contains the parameter fcipLinkLocalFcipEntityMode that describes the entity's behavior (B_Port or E_Port) can I say that the fcipEntityId corresponds to what FC-BB-2 calls the VE_Port_Name or B_Access_Name? And if so may a client be interested in what FC-BB-2 calls the FC/FCIP Identifier? Bret _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Thu Oct 16 19:42:36 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00369 for ; Thu, 16 Oct 2003 19:42:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAHl1-0001pi-43 for ips-archive@odin.ietf.org; Thu, 16 Oct 2003 19:42:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9GNgFtZ007047 for ips-archive@odin.ietf.org; Thu, 16 Oct 2003 19:42:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAHl0-0001pa-Sf for ips-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 19:42:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00360 for ; Thu, 16 Oct 2003 19:42:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAHkz-0004Ct-00 for ips-web-archive@ietf.org; Thu, 16 Oct 2003 19:42:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAHky-0004Cp-00 for ips-web-archive@ietf.org; Thu, 16 Oct 2003 19:42:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAHkn-0001oU-JV; Thu, 16 Oct 2003 19:42:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAHkF-0001oE-TW for ips@optimus.ietf.org; Thu, 16 Oct 2003 19:41:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00353 for ; Thu, 16 Oct 2003 19:41:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAHkE-0004Cm-00 for ips@ietf.org; Thu, 16 Oct 2003 19:41:26 -0400 Received: from magic-mail.adaptec.com ([216.52.22.10] helo=magic.adaptec.com) by ietf-mx with esmtp (Exim 4.12) id 1AAHkD-0004CO-00 for ips@ietf.org; Thu, 16 Oct 2003 19:41:25 -0400 Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h9GNemA16086; Thu, 16 Oct 2003 16:40:48 -0700 Received: from aime2k02.adaptec.com (aime2k02.adaptec.com [10.25.8.42]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id QAA18860; Thu, 16 Oct 2003 16:40:45 -0700 (PDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Subject: RE: [Ips] No IPS meeting in Minneapolis Date: Thu, 16 Oct 2003 16:40:45 -0700 Message-ID: <59C7D667A0EADB45866C62DD1B55A0FD71B79A@aime2k02.adaptec.com> Thread-Topic: [Ips] No IPS meeting in Minneapolis Thread-Index: AcOPamfYj44JpeFkSkyzN1H9z/EnhwE0/2dw From: "Carrier, John" To: , Cc: "Mallikarjun C." Content-Transfer-Encoding: quoted-printable Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi David, what is the process for getting the iSER and DA I-Ds considered as WG = documents? Are there any other new items pending? thanks. --jc > -----Original Message----- > From: Mallikarjun C. [mailto:cbm@rose.hp.com] > Sent: Friday, October 10, 2003 1:07 PM > To: Black_David@emc.com; ips@ietf.org > Subject: Re: [Ips] No IPS meeting in Minneapolis >=20 >=20 > David, >=20 > There are quite a few of us who would like the IPS > WG to approve the iSER and DA I-Ds as official WG > docs - in order to extend iSCSI's capabilities to > be generic RDMA-capable. To that end, the authors > of these drafts have requested time for presenting > those drafts a short while ago with the co-chairs. > It may have crossed this email on the Net. >=20 > While the authors ideally would like a formal > WG meeting for seeking charter enhancements, I can > also see that doing so given the seeming lack of other > agenda items may not be most efficient. OTOH, I > am afraid that this fact would remain the same > even for the next IETF in Seoul, aside from the > fact that it causes more delay when the authors > believe the drafts are ready for WG consideration. >=20 > Could you please recommend the most optimal course > of action to request and enhance the WG charter? >=20 > Regards. > -- > Mallikarjun >=20 > Mallikarjun Chadalapaka > Networked Storage Architecture > Network Storage Solutions > Hewlett-Packard MS 5668 > Roseville CA 95747 > cbm@rose.hp.com >=20 >=20 > --On Friday, October 10, 2003 3:17 PM -0400 Black_David@emc.com wrote: >=20 > > Due to the absence of significant open technical items > > to work on, the IP Storage WG will not be meeting in > > Minneapolis. The WG chairs are continuing to work with > > our ADs and draft authors on getting our drafts published > > as RFCs. > > > > Thanks, > > --David (for David & Elizabeth, IPS WG chairs) > > > > ---------------------------------------------------- > > 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 > > ---------------------------------------------------- > > > > > > _______________________________________________ > > Ips mailing list > > Ips@ietf.org > > https://www1.ietf.org/mailman/listinfo/ips >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > Ips mailing list > Ips@ietf.org > https://www1.ietf.org/mailman/listinfo/ips >=20 _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Thu Oct 16 20:20:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01260 for ; Thu, 16 Oct 2003 20:20:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAILi-0003b1-Rc for ips-archive@odin.ietf.org; Thu, 16 Oct 2003 20:20:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9H0KA8l013817 for ips-archive@odin.ietf.org; Thu, 16 Oct 2003 20:20:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAILh-0003ak-RG for ips-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 20:20:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01253 for ; Thu, 16 Oct 2003 20:20:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAILf-0004X7-00 for ips-web-archive@ietf.org; Thu, 16 Oct 2003 20:20:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAILf-0004X4-00 for ips-web-archive@ietf.org; Thu, 16 Oct 2003 20:20:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAILc-0003Zc-5E; Thu, 16 Oct 2003 20:20:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAILQ-0003Yx-4c for ips@optimus.ietf.org; Thu, 16 Oct 2003 20:19:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01250 for ; Thu, 16 Oct 2003 20:19:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAILN-0004X1-00 for ips@ietf.org; Thu, 16 Oct 2003 20:19:49 -0400 Received: from thebe.your-site.com ([140.186.45.26]) by ietf-mx with esmtp (Exim 4.12) id 1AAILN-0004WK-00 for ips@ietf.org; Thu, 16 Oct 2003 20:19:49 -0400 Received: from asomi.com (64-144-5-25.client.dsl.net [64.144.5.25]) by thebe.your-site.com (Postfix) with ESMTP id EF1892458B8; Thu, 16 Oct 2003 20:19:51 -0400 (EDT) Date: Thu, 16 Oct 2003 19:19:46 -0500 Subject: Re: [Ips] No IPS meeting in Minneapolis Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: , , "Mallikarjun C." To: "Carrier, John" From: Caitlin Bestler In-Reply-To: <59C7D667A0EADB45866C62DD1B55A0FD71B79A@aime2k02.adaptec.com> Message-Id: <9CD283C2-0037-11D8-8FB8-003065D48EE0@asomi.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Thursday, October 16, 2003, at 06:40 PM, Carrier, John wrote: > Hi David, > > what is the process for getting the iSER and DA I-Ds considered as WG > documents? Are there any other new items pending? > > thanks. > I also think these documents should be reviewed by the WG. I had major reservations about the first draft, and expressed them. But without it being a WG product, there is no way of having those issues be dealt with. The flaws may or may not be corrected. But if not, the flawed deployment will be cited as an argument against fixing the problem. In any event, the *goal* of defining iSCSI so that it works with general purpose RDMA rather than its own custom RMDA-like features is certainly one that should be endorsed by the IETF. _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Wed Oct 22 13:56:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19682 for ; Wed, 22 Oct 2003 13:56:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACNDI-0002a5-DP for ips-archive@odin.ietf.org; Wed, 22 Oct 2003 13:56:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9MHu4ev009917 for ips-archive@odin.ietf.org; Wed, 22 Oct 2003 13:56:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACNDI-0002Zs-8v for ips-web-archive@optimus.ietf.org; Wed, 22 Oct 2003 13:56:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19633 for ; Wed, 22 Oct 2003 13:55:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACNDF-0000Yw-00 for ips-web-archive@ietf.org; Wed, 22 Oct 2003 13:56:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACNDF-0000Ys-00 for ips-web-archive@ietf.org; Wed, 22 Oct 2003 13:56:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACNCH-0002S0-9T; Wed, 22 Oct 2003 13:55:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACNC4-0002RM-8m for ips@optimus.ietf.org; Wed, 22 Oct 2003 13:54:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19591 for ; Wed, 22 Oct 2003 13:54:37 -0400 (EDT) From: elizabeth.rodriguez@dothill.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACNC1-0000Xc-00 for ips@ietf.org; Wed, 22 Oct 2003 13:54:45 -0400 Received: from mail.dothill.com ([155.254.128.7] helo=dothill.com) by ietf-mx with esmtp (Exim 4.12) id 1ACNC1-0000XY-00 for ips@ietf.org; Wed, 22 Oct 2003 13:54:45 -0400 Received: from exchange.artecon.com (exchange [206.6.182.75]) by dothill.com (8.12.9+Sun/8.12.5) with ESMTP id h9MHrGrT017982 for ; Wed, 22 Oct 2003 10:53:17 -0700 (PDT) Received: by exchange.artecon.com with Internet Mail Service (5.5.2653.19) id <42RVK6CL>; Wed, 22 Oct 2003 10:43:47 -0700 Message-ID: <6E76A781C4D7D511A0C000105A209B59041B54AE@exchange.artecon.com> To: ips@ietf.org Date: Wed, 22 Oct 2003 10:43:46 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Ips] New IMSS WG; IPv6 over Fibre Channel Draft Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Hi all, I would like to announce a new IETF WG -- Internet and Management Support for Storage [IMSS] The charter follows below, but can also be found at http://www.ietf.org/html.charters/imss-charter.html The IMSS working group has been chartered in the OPS area, and will be working on the FC MIBs initially proposed in this working group via the mailing list this past June, per draft http://www.ietf.org/internet-drafts/draft-gai-fc-mibs-00.txt. It will also work on the IPv6 over Fibre Channel draft http://www.ietf.org/internet-drafts/draft-ietf-imss-ipv6-over-fibre-channel- 00.txt initially proposed in the IPv6 working group. IMSS will be holding a session at IETF-58 in Minneapolis, which you are welcome to attend. Information about the working group and the mailing list follow. Thank you, Elizabeth Rodriguez IMSS chair ---- A new IETF working group has been formed in the Operations and Management Area. For additional information, please contact the Area Directors or the WG Chairs. Internet and Management Support for Storage (imss) -------------------------------------------------- Current Status: Active Working Group Chair(s): Elizabeth Rodriguez Operations and Management Area Director(s): Randy Bush Bert Wijnen Operations and Management Area Advisor: Bert Wijnen Technical Advisor(s): Keith McCloghrie Margaret Wasserman David Black Mailing Lists: General Discussion: imss@ietf.org To Subscribe: https://www1.ietf.org/mailman/listinfo/imss Archive: http://www1.ietf.org/mail-archive/working-groups/imss/ Description of Working Group: Fibre Channel is a high speed network technology primarily used for storage networking (i.e., Storage Area Networks [SANs]). Two important aspects of Fibre Channel interact with the Internet: - Fibre Channel can encapsulate and carry IP protocol traffic - Fibre Channel devices can be managed via SNMP The Internet and Management Support for Storage WG (imss) is chartered to address two areas, specifically: - IPv4 over Fibre Channel has been specified in RFC 2625. A corresponding specification for IPv6 is needed. - An initial Fibre Channel Management MIB has been developed by the IP Storage (ips) WG; extensions are needed to encompass management of additional aspects of Fibre Channel, such as zoning. In the future, other storage related MIBs for other storage transports such as INCITS T10 Serial Attached SCSI (SAS) or SCSI command specific MIBs may be proposed. This group would work with the appropriate technical committee(s) in a manner similar to that described for INCITS T11 below. As Fibre Channel standardization is handled by the INCITS T11 Technical Committee (http://www.t11.org), a close working relationship with T11 is essential to the WG's success. In particular: - The IPv6 over Fibre Channel specification will be based on draft-desanti-ipv6-over-fibre-channel-02.txt. This draft was originally developed within a T11 study group and T11 has officially recommended this draft to the IETF. - The WG will not standardize management of Fibre Channel features ahead of their incorporation into appropriate T11 Fibre Channel standards. - The WG will work closely with T11, specifically Task Group T11.5, on the functionality and structure of the MIBs it develops for management of Fibre Channel. In addition to working closely with the INCITS T11 Technical Committee, this Working Group will work closely with IETF IPv6 Working Group as appropriate. In particular, the IPv6 Working Group will be kept informed on the progress and status of the IPv6 over Fibre Channel specification. The IMSS Working Group Last Call announcement will be cross-posted to the IPv6 WG mailing list. Goals and Milestones: Dec 03 Submit IPv6 over Fibre Channel draft to IESG for consideration as Proposed Standard Aug 04 Work with T11.5 to determine what additional Fibre Channel MIBs are needed. Oct 04 Submit Fibre Channel Domain Manager MIB to IESG for consideration as Proposed Standard Oct 04 Submit Fibre Channel Name Server MIB to IESG for consideration as Proposed Standard Jan 05 Submit Extensions for Fibre Channel Interfaces MIB to IESG for consideration as Proposed Standard Jan 05 Review working group charter and determine what additional work, if any, should be undertaken by working group. _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Thu Oct 23 22:39:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00285 for ; Thu, 23 Oct 2003 22:39:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrr5-0000CN-VV for ips-archive@odin.ietf.org; Thu, 23 Oct 2003 22:39:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O2dB80000757 for ips-archive@odin.ietf.org; Thu, 23 Oct 2003 22:39:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrr5-0000C8-QO for ips-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 22:39:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00282 for ; Thu, 23 Oct 2003 22:39:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACrr2-0004HP-00 for ips-web-archive@ietf.org; Thu, 23 Oct 2003 22:39:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACrr2-0004HL-00 for ips-web-archive@ietf.org; Thu, 23 Oct 2003 22:39:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrqv-00008j-3t; Thu, 23 Oct 2003 22:39:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrpw-0008Ew-3G for ips@optimus.ietf.org; Thu, 23 Oct 2003 22:38:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00243 for ; Thu, 23 Oct 2003 22:37:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACrps-0004GN-00 for ips@ietf.org; Thu, 23 Oct 2003 22:37:56 -0400 Received: from mail2.microsoft.com ([131.107.3.124]) by ietf-mx with esmtp (Exim 4.12) id 1ACrps-0004G7-00 for ips@ietf.org; Thu, 23 Oct 2003 22:37:56 -0400 Received: from INET-VRS-02.redmond.corp.microsoft.com ([157.54.8.110]) by mail2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1041); Thu, 23 Oct 2003 19:36:31 -0700 Received: from 157.54.8.155 by INET-VRS-02.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 23 Oct 2003 19:36:31 -0700 Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 23 Oct 2003 19:36:30 -0700 Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069); Thu, 23 Oct 2003 19:36:30 -0700 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.1069); Thu, 23 Oct 2003 19:36:30 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7097.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: [Ips] No IPS meeting in Minneapolis Date: Thu, 23 Oct 2003 19:36:35 -0700 Message-ID: Thread-Topic: [Ips] No IPS meeting in Minneapolis thread-index: AcOPamfYj44JpeFkSkyzN1H9z/EnhwE0/2dwAWZIN/A= From: "Jim Pinkerton" To: "Carrier, John" , , Cc: "Mallikarjun C." X-OriginalArrivalTime: 24 Oct 2003 02:36:30.0432 (UTC) FILETIME=[A1937600:01C399D7] Content-Transfer-Encoding: quoted-printable Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable I also agree that iSER should be made a WG document.=20 David, can you outline the process to do this?=20 Jim > -----Original Message----- > From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Carrier, > John > Sent: Thursday, October 16, 2003 4:41 PM > To: ips@ietf.org; Black_David@emc.com > Cc: Mallikarjun C. > Subject: RE: [Ips] No IPS meeting in Minneapolis >=20 > Hi David, >=20 > what is the process for getting the iSER and DA I-Ds considered as WG > documents? Are there any other new items pending? >=20 > thanks. >=20 > --jc >=20 >=20 > > -----Original Message----- > > From: Mallikarjun C. [mailto:cbm@rose.hp.com] > > Sent: Friday, October 10, 2003 1:07 PM > > To: Black_David@emc.com; ips@ietf.org > > Subject: Re: [Ips] No IPS meeting in Minneapolis > > > > > > David, > > > > There are quite a few of us who would like the IPS > > WG to approve the iSER and DA I-Ds as official WG > > docs - in order to extend iSCSI's capabilities to > > be generic RDMA-capable. To that end, the authors > > of these drafts have requested time for presenting > > those drafts a short while ago with the co-chairs. > > It may have crossed this email on the Net. > > > > While the authors ideally would like a formal > > WG meeting for seeking charter enhancements, I can > > also see that doing so given the seeming lack of other > > agenda items may not be most efficient. OTOH, I > > am afraid that this fact would remain the same > > even for the next IETF in Seoul, aside from the > > fact that it causes more delay when the authors > > believe the drafts are ready for WG consideration. > > > > Could you please recommend the most optimal course > > of action to request and enhance the WG charter? > > > > Regards. > > -- > > Mallikarjun > > > > Mallikarjun Chadalapaka > > Networked Storage Architecture > > Network Storage Solutions > > Hewlett-Packard MS 5668 > > Roseville CA 95747 > > cbm@rose.hp.com > > > > > > --On Friday, October 10, 2003 3:17 PM -0400 Black_David@emc.com wrote: > > > > > Due to the absence of significant open technical items > > > to work on, the IP Storage WG will not be meeting in > > > Minneapolis. The WG chairs are continuing to work with > > > our ADs and draft authors on getting our drafts published > > > as RFCs. > > > > > > Thanks, > > > --David (for David & Elizabeth, IPS WG chairs) > > > > > > ---------------------------------------------------- > > > 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 > > > ---------------------------------------------------- > > > > > > > > > _______________________________________________ > > > 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 > > >=20 > _______________________________________________ > 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 From exim@www1.ietf.org Fri Oct 24 00:50:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03180 for ; Fri, 24 Oct 2003 00:50:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACttq-0001lm-Lm for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 00:50:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O4oAt5006803 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 00:50:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACttq-0001le-Fo for ips-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 00:50:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03156 for ; Fri, 24 Oct 2003 00:49:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACttn-0005Jm-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 00:50:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACttn-0005Jj-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 00:50:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACtth-0001g9-QV; Fri, 24 Oct 2003 00:50:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACtte-0001ej-DT for ips@optimus.ietf.org; Fri, 24 Oct 2003 00:49:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03153 for ; Fri, 24 Oct 2003 00:49:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACttb-0005Jf-00 for ips@ietf.org; Fri, 24 Oct 2003 00:49:55 -0400 Received: from fmr02.intel.com ([192.55.52.25] helo=caduceus.fm.intel.com) by ietf-mx with esmtp (Exim 4.12) id 1ACttb-0005JV-00 for ips@ietf.org; Fri, 24 Oct 2003 00:49:55 -0400 Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37]) by caduceus.fm.intel.com (8.12.9-20030918-01/8.12.9/d: outer.mc,v 1.66 2003/05/22 21:17:36 rfjohns1 Exp $) with ESMTP id h9O4nmTw013420 for ; Fri, 24 Oct 2003 04:49:49 GMT Received: from fmsmsxvs043.fm.intel.com (fmsmsxvs043.fm.intel.com [132.233.42.129]) by petasus.fm.intel.com (8.11.6-20030918-01/8.11.6/d: inner.mc,v 1.35 2003/05/22 21:18:01 rfjohns1 Exp $) with SMTP id h9O4ena28875 for ; Fri, 24 Oct 2003 04:40:49 GMT Received: from fmsmsx332.amr.corp.intel.com ([132.233.42.148]) by fmsmsxvs043.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2003102321491030839 ; Thu, 23 Oct 2003 21:49:10 -0700 Received: from fmsmsx402.amr.corp.intel.com ([132.233.42.200]) by fmsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 23 Oct 2003 21:49:07 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Subject: RE: [Ips] No IPS meeting in Minneapolis Date: Thu, 23 Oct 2003 21:49:07 -0700 Message-ID: <6315617889C99D4BA7C14687DEC8DB4E052186B0@fmsmsx402.fm.intel.com> Thread-Topic: [Ips] No IPS meeting in Minneapolis Thread-Index: AcOPamfYj44JpeFkSkyzN1H9z/EnhwE0/2dwAWZIN/AABJ4KoA== From: "Shah, Hemal" To: "Jim Pinkerton" , "Carrier, John" , , Cc: "Mallikarjun C." X-OriginalArrivalTime: 24 Oct 2003 04:49:07.0888 (UTC) FILETIME=[2896E300:01C399EA] X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) Content-Transfer-Encoding: quoted-printable Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable I am also in agreement here. I believe that iSER should be made a WG document. Hemal -----Original Message----- From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Jim Pinkerton Sent: Thursday, October 23, 2003 9:37 PM To: Carrier, John; ips@ietf.org; Black_David@emc.com Cc: Mallikarjun C. Subject: RE: [Ips] No IPS meeting in Minneapolis I also agree that iSER should be made a WG document.=20 David, can you outline the process to do this?=20 Jim > -----Original Message----- > From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Carrier, > John > Sent: Thursday, October 16, 2003 4:41 PM > To: ips@ietf.org; Black_David@emc.com > Cc: Mallikarjun C. > Subject: RE: [Ips] No IPS meeting in Minneapolis >=20 > Hi David, >=20 > what is the process for getting the iSER and DA I-Ds considered as WG > documents? Are there any other new items pending? >=20 > thanks. >=20 > --jc >=20 >=20 > > -----Original Message----- > > From: Mallikarjun C. [mailto:cbm@rose.hp.com] > > Sent: Friday, October 10, 2003 1:07 PM > > To: Black_David@emc.com; ips@ietf.org > > Subject: Re: [Ips] No IPS meeting in Minneapolis > > > > > > David, > > > > There are quite a few of us who would like the IPS > > WG to approve the iSER and DA I-Ds as official WG > > docs - in order to extend iSCSI's capabilities to > > be generic RDMA-capable. To that end, the authors > > of these drafts have requested time for presenting > > those drafts a short while ago with the co-chairs. > > It may have crossed this email on the Net. > > > > While the authors ideally would like a formal > > WG meeting for seeking charter enhancements, I can > > also see that doing so given the seeming lack of other > > agenda items may not be most efficient. OTOH, I > > am afraid that this fact would remain the same > > even for the next IETF in Seoul, aside from the > > fact that it causes more delay when the authors > > believe the drafts are ready for WG consideration. > > > > Could you please recommend the most optimal course > > of action to request and enhance the WG charter? > > > > Regards. > > -- > > Mallikarjun > > > > Mallikarjun Chadalapaka > > Networked Storage Architecture > > Network Storage Solutions > > Hewlett-Packard MS 5668 > > Roseville CA 95747 > > cbm@rose.hp.com > > > > > > --On Friday, October 10, 2003 3:17 PM -0400 Black_David@emc.com wrote: > > > > > Due to the absence of significant open technical items > > > to work on, the IP Storage WG will not be meeting in > > > Minneapolis. The WG chairs are continuing to work with > > > our ADs and draft authors on getting our drafts published > > > as RFCs. > > > > > > Thanks, > > > --David (for David & Elizabeth, IPS WG chairs) > > > > > > ---------------------------------------------------- > > > 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 > > > ---------------------------------------------------- > > > > > > > > > _______________________________________________ > > > 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 > > >=20 > _______________________________________________ > 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 mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Fri Oct 24 11:23:37 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08657 for ; Fri, 24 Oct 2003 11:23:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3mW-00021J-1p for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 11:23:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OFNGrY007765 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 11:23:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3mV-00021A-SL for ips-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 11:23:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08608 for ; Fri, 24 Oct 2003 11:23:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD3mU-0005Q6-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 11:23:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD3mU-0005Q3-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 11:23:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3mI-0001wL-1C; Fri, 24 Oct 2003 11:23:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3lY-0001m0-2E for ips@optimus.ietf.org; Fri, 24 Oct 2003 11:22:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08510 for ; Fri, 24 Oct 2003 11:22:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD3lX-0005Nm-00 for ips@ietf.org; Fri, 24 Oct 2003 11:22:15 -0400 Received: from e3.ny.us.ibm.com ([32.97.182.103]) by ietf-mx with esmtp (Exim 4.12) id 1AD3lW-0005My-00 for ips@ietf.org; Fri, 24 Oct 2003 11:22:14 -0400 Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.56.224.150]) by e3.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id h9OFLeYJ430672; Fri, 24 Oct 2003 11:21:40 -0400 Received: from d01ml604.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by northrelay02.pok.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h9OFLcgn229400; Fri, 24 Oct 2003 11:21:38 -0400 Importance: Normal MIME-Version: 1.0 To: Cc: "Jim Pinkerton" , "Carrier, John" , , "Mallikarjun C." , "Shah, Hemal" Subject: RE: [Ips] No IPS meeting in Minneapolis X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Mike Ko Date: Fri, 24 Oct 2003 08:21:37 -0700 X-MIMETrack: Serialize by Router on D01ML604/01/M/IBM(Release 6.5|September 18, 2003) at 10/24/2003 11:21:39, Serialize complete at 10/24/2003 11:21:39 Content-Type: text/plain; charset="us-ascii" Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , I also agree that iSER and DA should be made WG documents and I like to know David's view on this. Mike Ko IBM Almaden Research mako@almaden.ibm.com Sent by: ips-admin@ietf.org To: "Jim Pinkerton" , "Carrier, John" , , cc: "Mallikarjun C." Subject: RE: [Ips] No IPS meeting in Minneapolis I am also in agreement here. I believe that iSER should be made a WG document. Hemal -----Original Message----- From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Jim Pinkerton Sent: Thursday, October 23, 2003 9:37 PM To: Carrier, John; ips@ietf.org; Black_David@emc.com Cc: Mallikarjun C. Subject: RE: [Ips] No IPS meeting in Minneapolis I also agree that iSER should be made a WG document. David, can you outline the process to do this? Jim > -----Original Message----- > From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Carrier, > John > Sent: Thursday, October 16, 2003 4:41 PM > To: ips@ietf.org; Black_David@emc.com > Cc: Mallikarjun C. > Subject: RE: [Ips] No IPS meeting in Minneapolis > > Hi David, > > what is the process for getting the iSER and DA I-Ds considered as WG > documents? Are there any other new items pending? > > thanks. > > --jc > > > > -----Original Message----- > > From: Mallikarjun C. [mailto:cbm@rose.hp.com] > > Sent: Friday, October 10, 2003 1:07 PM > > To: Black_David@emc.com; ips@ietf.org > > Subject: Re: [Ips] No IPS meeting in Minneapolis > > > > > > David, > > > > There are quite a few of us who would like the IPS > > WG to approve the iSER and DA I-Ds as official WG > > docs - in order to extend iSCSI's capabilities to > > be generic RDMA-capable. To that end, the authors > > of these drafts have requested time for presenting > > those drafts a short while ago with the co-chairs. > > It may have crossed this email on the Net. > > > > While the authors ideally would like a formal > > WG meeting for seeking charter enhancements, I can > > also see that doing so given the seeming lack of other > > agenda items may not be most efficient. OTOH, I > > am afraid that this fact would remain the same > > even for the next IETF in Seoul, aside from the > > fact that it causes more delay when the authors > > believe the drafts are ready for WG consideration. > > > > Could you please recommend the most optimal course > > of action to request and enhance the WG charter? > > > > Regards. > > -- > > Mallikarjun > > > > Mallikarjun Chadalapaka > > Networked Storage Architecture > > Network Storage Solutions > > Hewlett-Packard MS 5668 > > Roseville CA 95747 > > cbm@rose.hp.com > > > > > > --On Friday, October 10, 2003 3:17 PM -0400 Black_David@emc.com wrote: > > > > > Due to the absence of significant open technical items > > > to work on, the IP Storage WG will not be meeting in > > > Minneapolis. The WG chairs are continuing to work with > > > our ADs and draft authors on getting our drafts published > > > as RFCs. > > > > > > Thanks, > > > --David (for David & Elizabeth, IPS WG chairs) > > > > > > ---------------------------------------------------- > > > 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 > > > ---------------------------------------------------- > > > > > > > > > _______________________________________________ > > > 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 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 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 From exim@www1.ietf.org Fri Oct 24 12:45:38 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16634 for ; Fri, 24 Oct 2003 12:45:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD53t-0001wx-GY for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 12:45:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OGjHga007489 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 12:45:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD53t-0001wi-13 for ips-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 12:45:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16559 for ; Fri, 24 Oct 2003 12:45:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD53q-0000QX-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 12:45:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD53q-0000QU-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 12:45:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD53d-0001r7-Dc; Fri, 24 Oct 2003 12:45:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD4yl-00014i-NO for ips@optimus.ietf.org; Fri, 24 Oct 2003 12:40:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15989 for ; Fri, 24 Oct 2003 12:39:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD4yk-0000DB-00 for ips@ietf.org; Fri, 24 Oct 2003 12:39:58 -0400 Received: from mms2.broadcom.com ([63.70.210.59]) by ietf-mx with esmtp (Exim 4.12) id 1AD4yj-0000D7-00 for ips@ietf.org; Fri, 24 Oct 2003 12:39:57 -0400 Received: from 63.70.210.1 by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (MMS v5.5.3)); Fri, 24 Oct 2003 09:39:47 -0700 Received: from nt-irva-0740.brcm.ad.broadcom.com ( nt-irva-0740.brcm.ad.broadcom.com [10.8.194.53]) by mon-irva-11.broadcom.com (8.9.1/8.9.1) with ESMTP id JAA16679; Fri, 24 Oct 2003 09:39:17 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Ips] No IPS meeting in Minneapolis Date: Fri, 24 Oct 2003 09:39:46 -0700 Message-ID: Thread-Topic: [Ips] No IPS meeting in Minneapolis Thread-Index: AcOPamfYj44JpeFkSkyzN1H9z/EnhwE0/2dwAWZIN/AABJ4KoAAYxRjQ From: "Uri Elzur" To: "Shah, Hemal" , "Jim Pinkerton" , "Carrier, John" , ips@ietf.org, Black_David@emc.com cc: "Mallikarjun C." X-WSS-ID: 13878A59428065-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Let me also voice my support in favor of opening a WG discussion on iSER / DA and adopting iSER and DA as WG docs.=20 Uri -----Original Message----- From: Shah, Hemal [mailto:hemal.shah@intel.com]=20 Sent: Thursday, October 23, 2003 9:49 PM To: Jim Pinkerton; Carrier, John; ips@ietf.org; Black_David@emc.com Cc: Mallikarjun C. Subject: RE: [Ips] No IPS meeting in Minneapolis I am also in agreement here. I believe that iSER should be made a WG document. Hemal -----Original Message----- From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Jim Pinkerton Sent: Thursday, October 23, 2003 9:37 PM To: Carrier, John; ips@ietf.org; Black_David@emc.com Cc: Mallikarjun C. Subject: RE: [Ips] No IPS meeting in Minneapolis I also agree that iSER should be made a WG document.=20 David, can you outline the process to do this?=20 Jim > -----Original Message----- > From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Carrier, > John > Sent: Thursday, October 16, 2003 4:41 PM > To: ips@ietf.org; Black_David@emc.com > Cc: Mallikarjun C. > Subject: RE: [Ips] No IPS meeting in Minneapolis >=20 > Hi David, >=20 > what is the process for getting the iSER and DA I-Ds considered as WG=20 > documents? Are there any other new items pending? >=20 > thanks. >=20 > --jc >=20 >=20 > > -----Original Message----- > > From: Mallikarjun C. [mailto:cbm@rose.hp.com] > > Sent: Friday, October 10, 2003 1:07 PM > > To: Black_David@emc.com; ips@ietf.org > > Subject: Re: [Ips] No IPS meeting in Minneapolis > > > > > > David, > > > > There are quite a few of us who would like the IPS > > WG to approve the iSER and DA I-Ds as official WG > > docs - in order to extend iSCSI's capabilities to > > be generic RDMA-capable. To that end, the authors > > of these drafts have requested time for presenting > > those drafts a short while ago with the co-chairs. > > It may have crossed this email on the Net. > > > > While the authors ideally would like a formal > > WG meeting for seeking charter enhancements, I can > > also see that doing so given the seeming lack of other agenda items=20 > > may not be most efficient. OTOH, I am afraid that this fact would=20 > > remain the same even for the next IETF in Seoul, aside from the > > fact that it causes more delay when the authors > > believe the drafts are ready for WG consideration. > > > > Could you please recommend the most optimal course > > of action to request and enhance the WG charter? > > > > Regards. > > -- > > Mallikarjun > > > > Mallikarjun Chadalapaka > > Networked Storage Architecture > > Network Storage Solutions > > Hewlett-Packard MS 5668 > > Roseville CA 95747 > > cbm@rose.hp.com > > > > > > --On Friday, October 10, 2003 3:17 PM -0400 Black_David@emc.com wrote: > > > > > Due to the absence of significant open technical items > > > to work on, the IP Storage WG will not be meeting in Minneapolis. > > > The WG chairs are continuing to work with our ADs and draft=20 > > > authors on getting our drafts published as RFCs. > > > > > > Thanks, > > > --David (for David & Elizabeth, IPS WG chairs) > > > > > > ---------------------------------------------------- > > > 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 > > > ---------------------------------------------------- > > > > > > > > > _______________________________________________ > > > 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 > > >=20 > _______________________________________________ > 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 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 From exim@www1.ietf.org Fri Oct 24 13:44:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19727 for ; Fri, 24 Oct 2003 13:44:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD5yo-00079g-Fy for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 13:44:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OHi6PI027498 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 13:44:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD5yo-00079N-4Z for ips-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 13:44:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19719 for ; Fri, 24 Oct 2003 13:43:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD5yl-0001XH-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 13:44:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD5yl-0001XE-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 13:44:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD5yj-00076E-8M; Fri, 24 Oct 2003 13:44:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD5yd-000745-SJ for ips@optimus.ietf.org; Fri, 24 Oct 2003 13:43:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19701 for ; Fri, 24 Oct 2003 13:43:45 -0400 (EDT) From: pat_thaler@agilent.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD5yb-0001Ww-00 for ips@ietf.org; Fri, 24 Oct 2003 13:43:53 -0400 Received: from msgbas1x.cos.agilent.com ([192.25.240.36]) by ietf-mx with esmtp (Exim 4.12) id 1AD5yb-0001Ws-00 for ips@ietf.org; Fri, 24 Oct 2003 13:43:53 -0400 Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 6590923539; Fri, 24 Oct 2003 11:43:52 -0600 (MDT) Received: from wcosbh22.cos.agilent.com (wcosbh22.cos.agilent.com [130.29.152.178]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 3D2732B; Fri, 24 Oct 2003 11:43:52 -0600 (MDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Subject: RE: [Ips] No IPS meeting in Minneapolis Date: Fri, 24 Oct 2003 11:43:38 -0600 Message-ID: <1BEBA5E8600DD4119A50009027AF54A0132E05AA@axcs04.cos.agilent.com> Thread-Topic: [Ips] No IPS meeting in Minneapolis Thread-Index: AcOaTld9AYvEWuqGRN6VqNVAJCplDwAB+kKQ To: , , , , , Cc: Content-Transfer-Encoding: quoted-printable Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable I am also in support of making the documents working group documents.=20 Pat -----Original Message----- From: Uri Elzur [mailto:uri@broadcom.com] Sent: Friday, October 24, 2003 9:40 AM To: Shah, Hemal; Jim Pinkerton; Carrier, John; ips@ietf.org; Black_David@emc.com Cc: Mallikarjun C. Subject: RE: [Ips] No IPS meeting in Minneapolis Let me also voice my support in favor of opening a WG discussion on iSER / DA and adopting iSER and DA as WG docs.=20 Uri -----Original Message----- From: Shah, Hemal [mailto:hemal.shah@intel.com]=20 Sent: Thursday, October 23, 2003 9:49 PM To: Jim Pinkerton; Carrier, John; ips@ietf.org; Black_David@emc.com Cc: Mallikarjun C. Subject: RE: [Ips] No IPS meeting in Minneapolis I am also in agreement here. I believe that iSER should be made a WG document. Hemal -----Original Message----- From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Jim Pinkerton Sent: Thursday, October 23, 2003 9:37 PM To: Carrier, John; ips@ietf.org; Black_David@emc.com Cc: Mallikarjun C. Subject: RE: [Ips] No IPS meeting in Minneapolis I also agree that iSER should be made a WG document.=20 David, can you outline the process to do this?=20 Jim > -----Original Message----- > From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Carrier, > John > Sent: Thursday, October 16, 2003 4:41 PM > To: ips@ietf.org; Black_David@emc.com > Cc: Mallikarjun C. > Subject: RE: [Ips] No IPS meeting in Minneapolis >=20 > Hi David, >=20 > what is the process for getting the iSER and DA I-Ds considered as WG=20 > documents? Are there any other new items pending? >=20 > thanks. >=20 > --jc >=20 >=20 > > -----Original Message----- > > From: Mallikarjun C. [mailto:cbm@rose.hp.com] > > Sent: Friday, October 10, 2003 1:07 PM > > To: Black_David@emc.com; ips@ietf.org > > Subject: Re: [Ips] No IPS meeting in Minneapolis > > > > > > David, > > > > There are quite a few of us who would like the IPS > > WG to approve the iSER and DA I-Ds as official WG > > docs - in order to extend iSCSI's capabilities to > > be generic RDMA-capable. To that end, the authors > > of these drafts have requested time for presenting > > those drafts a short while ago with the co-chairs. > > It may have crossed this email on the Net. > > > > While the authors ideally would like a formal > > WG meeting for seeking charter enhancements, I can > > also see that doing so given the seeming lack of other agenda items=20 > > may not be most efficient. OTOH, I am afraid that this fact would=20 > > remain the same even for the next IETF in Seoul, aside from the > > fact that it causes more delay when the authors > > believe the drafts are ready for WG consideration. > > > > Could you please recommend the most optimal course > > of action to request and enhance the WG charter? > > > > Regards. > > -- > > Mallikarjun > > > > Mallikarjun Chadalapaka > > Networked Storage Architecture > > Network Storage Solutions > > Hewlett-Packard MS 5668 > > Roseville CA 95747 > > cbm@rose.hp.com > > > > > > --On Friday, October 10, 2003 3:17 PM -0400 Black_David@emc.com wrote: > > > > > Due to the absence of significant open technical items > > > to work on, the IP Storage WG will not be meeting in Minneapolis. > > > The WG chairs are continuing to work with our ADs and draft=20 > > > authors on getting our drafts published as RFCs. > > > > > > Thanks, > > > --David (for David & Elizabeth, IPS WG chairs) > > > > > > ---------------------------------------------------- > > > 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 > > > ---------------------------------------------------- > > > > > > > > > _______________________________________________ > > > 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 > > >=20 > _______________________________________________ > 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 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 mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Fri Oct 24 15:02:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23254 for ; Fri, 24 Oct 2003 15:02:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7CK-0001sP-9Z for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 15:02:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OJ280H007213 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 15:02:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7CK-0001sG-5T for ips-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 15:02:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23213 for ; Fri, 24 Oct 2003 15:01:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7CH-0002jI-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 15:02:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD7CG-0002jF-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 15:02:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7CD-0001pe-U8; Fri, 24 Oct 2003 15:02:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7BX-0001lt-6U for ips@optimus.ietf.org; Fri, 24 Oct 2003 15:01:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23178; Fri, 24 Oct 2003 15:01:06 -0400 (EDT) From: Black_David@emc.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7BS-0002iY-00; Fri, 24 Oct 2003 15:01:14 -0400 Received: from [168.159.2.31] (helo=MXIC3.corp.emc.com) by ietf-mx with esmtp (Exim 4.12) id 1AD7BS-0002iV-00; Fri, 24 Oct 2003 15:01:14 -0400 Received: by mxic3.corp.emc.com with Internet Mail Service (5.5.2657.72) id ; Fri, 24 Oct 2003 15:01:12 -0400 Message-ID: To: ips@ietf.org, rddp@ietf.org Date: Fri, 24 Oct 2003 15:01:10 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Subject: [Ips] iSCSI over RDMA (iSER and DA) Internet Drafts Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , On the IPS list, Mallikarjun asked: > Could you please recommend the most optimal course > of action to request and enhance the WG charter? IETF being IETF, the world of "rough consensus and running code", I have no idea what "the most optimal course of action" would be, or whether it even exists :-). The scope of an IETF WG's activities and the items on which it works are managed by the Area Directors and the IESG via the WG's charter, among other means. My understanding of the Transport ADs' views is that the IP Storage WG has been very successful in what the WG set out to do, and the time has come to finish up the current work, declare victory and move on (with the WG either going dormant or being concluded). Of course the ADs always reserve the right to change their minds based on new information, etc., and my understanding may be less than perfect. The people advocating addition of work on iSCSI over RDMA seem to be spending a lot of energy on where the work should be done (process) and much less on whether and why it should be done (technical merits). In my experience, these two topics are best pursued in the opposite order. Specifically, the first decision (ADs and IESG as appropriate) should be whether the work is to be done and with what scope; if that is decided in the affirmative, then matters of where and how can then be worked out in a reasonable fashion. Given this, I do have some advice to offer: (1) A promising path towards undertaking iSCSI over RDMA work in the IETF involves a BOF, e.g., in Seoul. Those interested in such a BOF should approach the Transport Area Directors about organizing and holding one (but first read the material on BOFs in RFC 2418). By the time of the Seoul meeting week, the rddp WG should be done or close to done with most of the drafts on which iSCSI over RDMA depends, providing a firmer foundation for the proposed work. - One of the things that inclines ADs and the IESG towards approval of work is the existence of an open community of people interested in the work, the broader the better. IETF meeting weeks are a good opportunity to solicit interest in possible work towards forming/broadening such a community (e.g., hallway discussion). In furtherance of this, in my role as RDDP WG chair I have already promised the iSER/DA draft authors a 5 minute slot in the RDDP WG meeting in Minneapolis to briefly describe what the drafts are about and solicit interest in working on them (e.g., organize an informal meeting [aka "bar BOF"] to discuss further). For those who are new to this topic, the iSER and DA drafts on the topic of iSCSI over RDMA are: http://www.ietf.org/internet-drafts/draft-ko-iwarp-iser-00.txt http://www.ietf.org/internet-drafts/draft-chadalapaka-iwarp-da-00.txt Thanks, --David (IPS WG co-chair, RDDP WG chair) ---------------------------------------------------- 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 ---------------------------------------------------- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Fri Oct 24 15:17:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25063 for ; Fri, 24 Oct 2003 15:17:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7Ql-0004YE-PJ for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 15:17:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OJH3Ke017480 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 15:17:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7Ql-0004Xc-G7 for ips-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 15:17:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25022 for ; Fri, 24 Oct 2003 15:16:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7Qj-0002wY-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 15:17:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD7Qj-0002wT-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 15:17:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7Qj-0004Uj-0r; Fri, 24 Oct 2003 15:17:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7Q1-0004LQ-DB for ips@optimus.ietf.org; Fri, 24 Oct 2003 15:16:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24929 for ; Fri, 24 Oct 2003 15:16:07 -0400 (EDT) From: Black_David@emc.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7Q0-0002vf-00 for ips@ietf.org; Fri, 24 Oct 2003 15:16:16 -0400 Received: from mxic2.corp.emc.com ([128.221.12.9]) by ietf-mx with esmtp (Exim 4.12) id 1AD7Pz-0002vK-00 for ips@ietf.org; Fri, 24 Oct 2003 15:16:15 -0400 Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Fri, 24 Oct 2003 15:15:40 -0400 Message-ID: To: bill@strahm.net, ips@ietf.org Subject: RE: [Ips] No IPS meeting in Minneapolis Date: Fri, 24 Oct 2003 15:15:40 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Bill, > I am not sure how I feel about these becoming WG items... However I do > think it warrants a meeting - if only an hour on Tuesday to allow folks > to propose a charter change to include iSER/DA whatever. > > We have documents > There appears to be interest based on all of the "me too" e-mails > > Seems to be time to discuss this, can we get a meeting scheduled before > the Tuesday deadline ? Could I suggest organizing a lunch of interested people immediately after the RDDP WG meeting on Tuesday in Minneapolis? Scheduling an IPS WG meeting on this short notice that would in practice be a BOF for these drafts isn't likely (IMHO). Also, if such a meeting were to happen, there's a good likelihood that it would be counted against RFC 2418's "two BOF maximum" guideline (be careful what you wish for). In contrast, an informally organized lunch would not count as an official BOF. Since I left it out of my last message, those interested in work on iSER and DA (iSCSI over RDMA) should also be consulting RFC 2418 on working group formation as part of thinking about a future BOF. 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 ---------------------------------------------------- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Fri Oct 24 15:27:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25588 for ; Fri, 24 Oct 2003 15:27:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7aR-0006es-V9 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 15:27:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OJR3hU025594 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 15:27:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7aR-0006ej-Pl for ips-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 15:27:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25559 for ; Fri, 24 Oct 2003 15:26:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7aQ-00032l-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 15:27:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD7aQ-00032i-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 15:27:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7aP-0006cZ-Rd; Fri, 24 Oct 2003 15:27:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7ZY-0006R3-8P for ips@optimus.ietf.org; Fri, 24 Oct 2003 15:26:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25508 for ; Fri, 24 Oct 2003 15:25:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7ZX-00032H-00 for ips@ietf.org; Fri, 24 Oct 2003 15:26:07 -0400 Received: from kairos.dsa.uqam.ca ([132.208.43.57]) by ietf-mx with esmtp (Exim 4.12) id 1AD7ZW-00031d-00 for ips@ietf.org; Fri, 24 Oct 2003 15:26:06 -0400 Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57]) by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h9OIbc114946; Fri, 24 Oct 2003 14:37:38 -0400 From: "bill" To: "'Jim Pinkerton'" , "'Carrier, John'" , , Cc: "'Mallikarjun C.'" Subject: RE: [Ips] No IPS meeting in Minneapolis Date: Fri, 24 Oct 2003 11:58:47 -0700 Message-ID: <000c01c39a60$dce68a60$6501a8c0@mobilebill> 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.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: Content-Transfer-Encoding: 7bit Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I am not sure how I feel about these becoming WG items... However I do think it warrants a meeting - if only an hour on Tuesday to allow folks to propose a charter change to include iSER/DA whatever. We have documents There appears to be interest based on all of the "me too" e-mails Seems to be time to discuss this, can we get a meeting scheduled before the Tuesday deadline ? Bill -----Original Message----- From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Jim Pinkerton Sent: Thursday, October 23, 2003 7:37 PM To: Carrier, John; ips@ietf.org; Black_David@emc.com Cc: Mallikarjun C. Subject: RE: [Ips] No IPS meeting in Minneapolis I also agree that iSER should be made a WG document. David, can you outline the process to do this? Jim > -----Original Message----- > From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Carrier, > John > Sent: Thursday, October 16, 2003 4:41 PM > To: ips@ietf.org; Black_David@emc.com > Cc: Mallikarjun C. > Subject: RE: [Ips] No IPS meeting in Minneapolis > > Hi David, > > what is the process for getting the iSER and DA I-Ds considered as WG > documents? Are there any other new items pending? > > thanks. > > --jc > > > > -----Original Message----- > > From: Mallikarjun C. [mailto:cbm@rose.hp.com] > > Sent: Friday, October 10, 2003 1:07 PM > > To: Black_David@emc.com; ips@ietf.org > > Subject: Re: [Ips] No IPS meeting in Minneapolis > > > > > > David, > > > > There are quite a few of us who would like the IPS > > WG to approve the iSER and DA I-Ds as official WG > > docs - in order to extend iSCSI's capabilities to > > be generic RDMA-capable. To that end, the authors > > of these drafts have requested time for presenting > > those drafts a short while ago with the co-chairs. > > It may have crossed this email on the Net. > > > > While the authors ideally would like a formal > > WG meeting for seeking charter enhancements, I can > > also see that doing so given the seeming lack of other agenda items > > may not be most efficient. OTOH, I am afraid that this fact would > > remain the same even for the next IETF in Seoul, aside from the > > fact that it causes more delay when the authors > > believe the drafts are ready for WG consideration. > > > > Could you please recommend the most optimal course > > of action to request and enhance the WG charter? > > > > Regards. > > -- > > Mallikarjun > > > > Mallikarjun Chadalapaka > > Networked Storage Architecture > > Network Storage Solutions > > Hewlett-Packard MS 5668 > > Roseville CA 95747 > > cbm@rose.hp.com > > > > > > --On Friday, October 10, 2003 3:17 PM -0400 Black_David@emc.com wrote: > > > > > Due to the absence of significant open technical items > > > to work on, the IP Storage WG will not be meeting in Minneapolis. > > > The WG chairs are continuing to work with our ADs and draft > > > authors on getting our drafts published as RFCs. > > > > > > Thanks, > > > --David (for David & Elizabeth, IPS WG chairs) > > > > > > ---------------------------------------------------- > > > 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 > > > ---------------------------------------------------- > > > > > > > > > _______________________________________________ > > > 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 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 mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Fri Oct 24 15:31:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25790 for ; Fri, 24 Oct 2003 15:31:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7eL-0007Xa-33 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 15:31:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OJV5Pm028980 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 15:31:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7eK-0007XL-Sf for ips-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 15:31:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25756 for ; Fri, 24 Oct 2003 15:30:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7eJ-000376-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 15:31:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD7eJ-000373-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 15:31:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7eI-0007Uk-5r; Fri, 24 Oct 2003 15:31:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7dl-0007Ow-Fc for ips@optimus.ietf.org; Fri, 24 Oct 2003 15:30:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25740 for ; Fri, 24 Oct 2003 15:30:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7dk-00036W-00 for ips@ietf.org; Fri, 24 Oct 2003 15:30:28 -0400 Received: from kairos.dsa.uqam.ca ([132.208.43.57]) by ietf-mx with esmtp (Exim 4.12) id 1AD7di-00035b-00 for ips@ietf.org; Fri, 24 Oct 2003 15:30:27 -0400 Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57]) by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id h9OJ8J115127; Fri, 24 Oct 2003 15:08:19 -0400 From: "bill" To: , Subject: RE: [Ips] No IPS meeting in Minneapolis Date: Fri, 24 Oct 2003 12:29:30 -0700 Message-ID: <001401c39a65$25f6c6d0$6501a8c0@mobilebill> 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.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: Content-Transfer-Encoding: 7bit Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I am curious... Why do you think adding two deliverables to an existing WG should count as a BOF. Now if the work were completely unrelated to current IPS work - I'd agree with you. However saying, we need an RFC to discuss porting iSCSI over a new Layer 4 (iSER) with input from an additional WG (RDDP) as the Layer 4 protocol - is unrelated is a stretch. In fact I would expect the first thing for an AD to say if there was an iSER BOF is - why isn't this in IPS ? So my question to you is "Why don't you want to discuss this work in IPS ?" I see a rather strong concensus to at least discuss the iSER/DA work in the IPS - that would be hard to ignore. If the end result is that you want iSCSI to go dormant/shut down - that is fine. However I think there is more work to be done. Bill -----Original Message----- From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of Black_David@emc.com Sent: Friday, October 24, 2003 12:16 PM To: bill@strahm.net; ips@ietf.org Subject: RE: [Ips] No IPS meeting in Minneapolis Bill, > I am not sure how I feel about these becoming WG items... However I do > think it warrants a meeting - if only an hour on Tuesday to allow > folks to propose a charter change to include iSER/DA whatever. > > We have documents > There appears to be interest based on all of the "me too" e-mails > > Seems to be time to discuss this, can we get a meeting scheduled > before the Tuesday deadline ? Could I suggest organizing a lunch of interested people immediately after the RDDP WG meeting on Tuesday in Minneapolis? Scheduling an IPS WG meeting on this short notice that would in practice be a BOF for these drafts isn't likely (IMHO). Also, if such a meeting were to happen, there's a good likelihood that it would be counted against RFC 2418's "two BOF maximum" guideline (be careful what you wish for). In contrast, an informally organized lunch would not count as an official BOF. Since I left it out of my last message, those interested in work on iSER and DA (iSCSI over RDMA) should also be consulting RFC 2418 on working group formation as part of thinking about a future BOF. 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 ---------------------------------------------------- _______________________________________________ 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 From exim@www1.ietf.org Fri Oct 24 16:06:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27325 for ; Fri, 24 Oct 2003 16:06:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8CD-0005XA-NS for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 16:06:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OK656q021252 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 16:06:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8CD-0005Wh-G6 for ips-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 16:06:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27313 for ; Fri, 24 Oct 2003 16:05:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD8CB-0003ba-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 16:06:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD8CB-0003bX-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 16:06:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8C9-0005VP-VV; Fri, 24 Oct 2003 16:06:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8Bh-0005P5-5m for ips@optimus.ietf.org; Fri, 24 Oct 2003 16:05:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27304 for ; Fri, 24 Oct 2003 16:05:22 -0400 (EDT) From: Black_David@emc.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD8Bf-0003bB-00 for ips@ietf.org; Fri, 24 Oct 2003 16:05:31 -0400 Received: from maho3msx2.isus.emc.com ([128.221.11.32] helo=MAHO3MSX2.corp.emc.com) by ietf-mx with esmtp (Exim 4.12) id 1AD8Bb-0003ag-00 for ips@ietf.org; Fri, 24 Oct 2003 16:05:27 -0400 Received: by maho3msx2.isus.emc.com with Internet Mail Service (5.5.2653.19) id ; Fri, 24 Oct 2003 16:04:57 -0400 Message-ID: To: bill@strahm.net, ips@ietf.org Subject: RE: [Ips] No IPS meeting in Minneapolis Date: Fri, 24 Oct 2003 16:04:55 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Bill, > Why do you think adding two deliverables to an existing WG should count > as a BOF. Now if the work were completely unrelated to current IPS work > - I'd agree with you. Please choose your words more carefully, as your message appears to ascribe incorrect statements to me. What I said was that calling a meeting *solely* to discuss possible new work that is not currently on the IPS WG's approved program of work could well count as a BOF. I did *not* say that a BOF is necessary to add work items because in fact a BOF is not in general necessary for that purpose. If the IPS WG had open technical issues in ongoing work that already justified holding a meeting, it would be a straightforward matter to add these drafts to the meeting agenda (as will be done for the RDDP WG meeting, as I noted in a separate message). OTOH, a meeting solely to consider possible new work in the absence of open technical issues in existing WG work items (IMHO) walks like a BOF and quacks like a BOF ... I hope the distinction is clearer now. > However saying, we need an RFC to discuss porting > iSCSI over a new Layer 4 (iSER) with input from an additional WG (RDDP) > as the Layer 4 protocol - is unrelated is a stretch. In fact I would > expect the first thing for an AD to say if there was an iSER BOF is - > why isn't this in IPS ? So my question to you is "Why don't you want to > discuss this work in IPS ?" > > I see a rather strong concensus to at least discuss the iSER/DA work in > the IPS - that would be hard to ignore. I'll leave AD decisions and comments to the ADs, but I'll note that discussion of this work *is* taking place in IPS (i.e., on the mailing list). I would also strongly suggest using the word "interest" rather than "concensus" in this sort of context. > If the end result is that you > want iSCSI to go dormant/shut down - that is fine. However I think > there is more work to be done. As I've already said in a separate message, I think the current focus of discussion should be on the technical merits of whether and why the work should be done rather than where it should to be done (e.g., extension of IPS WG program of work vs. formation of a new WG vs. ???). 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 ---------------------------------------------------- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Fri Oct 24 16:25:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28101 for ; Fri, 24 Oct 2003 16:25:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8Uc-0000wN-T1 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 16:25:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OKP67j003609 for ips-archive@odin.ietf.org; Fri, 24 Oct 2003 16:25:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8Uc-0000w8-Mx for ips-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 16:25:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28095 for ; Fri, 24 Oct 2003 16:24:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD8Ub-0003qc-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 16:25:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD8Ua-0003qZ-00 for ips-web-archive@ietf.org; Fri, 24 Oct 2003 16:25:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8UX-0000tv-Kp; Fri, 24 Oct 2003 16:25:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8UH-0000ox-1F for ips@optimus.ietf.org; Fri, 24 Oct 2003 16:24:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28082 for ; Fri, 24 Oct 2003 16:24:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD8UF-0003qJ-00 for ips@ietf.org; Fri, 24 Oct 2003 16:24:43 -0400 Received: from thebe.your-site.com ([140.186.45.26]) by ietf-mx with esmtp (Exim 4.12) id 1AD8UE-0003q2-00 for ips@ietf.org; Fri, 24 Oct 2003 16:24:42 -0400 Received: from asomi.com (64-144-5-25.client.dsl.net [64.144.5.25]) by thebe.your-site.com (Postfix) with ESMTP id 82B482452D2; Fri, 24 Oct 2003 16:24:46 -0400 (EDT) Date: Fri, 24 Oct 2003 15:24:13 -0500 Subject: Re: [Ips] No IPS meeting in Minneapolis Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: , To: "bill" From: Caitlin Bestler In-Reply-To: <001401c39a65$25f6c6d0$6501a8c0@mobilebill> Message-Id: <08A7CAB3-0660-11D8-8A34-003065D48EE0@asomi.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Friday, October 24, 2003, at 02:29 PM, bill wrote: > I am curious... > > Why do you think adding two deliverables to an existing WG should count > as a BOF. Now if the work were completely unrelated to current IPS > work > - I'd agree with you. However saying, we need an RFC to discuss > porting > iSCSI over a new Layer 4 (iSER) with input from an additional WG (RDDP) > as the Layer 4 protocol - is unrelated is a stretch. In fact I would > expect the first thing for an AD to say if there was an iSER BOF is - > why isn't this in IPS ? So my question to you is "Why don't you want > to > discuss this work in IPS ?" > > I see a rather strong concensus to at least discuss the iSER/DA work in > the IPS - that would be hard to ignore. If the end result is that you > want iSCSI to go dormant/shut down - that is fine. However I think > there is more work to be done. > > Bill > > I agree. From the IPS charter: There is significant interest in using IP-based networks to transport block storage traffic. This group will pursue the pragmatic approach of encapsulating existing protocols, such as SCSI and Fibre Channel, in an IP-based transport or transports. One of the benefits of defining block storage protocols over RDMA is that it automatically encompasses all other reliable IP transports. In my opinion, the current solution of specifying a complex protocol that incorporates *many* transport features into the application protocol is not a desirable final solution. It is a very prudent initial solution. But the final solution should neither lock in application layer simulation of SCTP features over TCP nor encourage the development of ULP-specific hardware/capabilities in preference to application neutral capabilities. I believe it is well within the scope of a plain reading of the current charter to continue the work to define iSCSI over SCTP and/or RDMA. Realistically, I can think of almost no reason to not simply lump the SCTP part under RDMA. One of the reasons I favor working on the problem within the IETF is that it will provide a proper forum for ensuring that iSER is defined such that it can be deployed over iWARP/SCTP and so that it will work on a *generic* iWARP RNIC -- not just one with a specific model of shared receive queue. Given the extensive amount of detailed work that is plainly evident in the submitted drafts there is clearly interest in this type of deployment. It certainly doesn't look to be something they whipped up over a few lunches on their spare time. Now it would have been ideal if a general problem discussion had occurred *first* within an open forum. But even if the draft authors "jumped the gun", we should still thank them for their work and continue the refinement process within an IETF WG, rather than treating it as though it were something totally unrelated to an existing WG. Caitlin Bestler - cait@asomi.com - http://asomi.com/ _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Mon Oct 27 15:13:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05788 for ; Mon, 27 Oct 2003 15:13:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEDjg-0003VO-Ej for ips-archive@odin.ietf.org; Mon, 27 Oct 2003 15:13:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RKD8Ac013470 for ips-archive@odin.ietf.org; Mon, 27 Oct 2003 15:13:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEDjg-0003VB-7n for ips-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 15:13:08 -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 PAA05717 for ; Mon, 27 Oct 2003 15:12:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEDje-0003We-00 for ips-web-archive@ietf.org; Mon, 27 Oct 2003 15:13:06 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AEDje-0003Wa-00 for ips-web-archive@ietf.org; Mon, 27 Oct 2003 15:13:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEDjY-0003Sk-LC; Mon, 27 Oct 2003 15:13:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEDfK-0002QL-E4 for ips@optimus.ietf.org; Mon, 27 Oct 2003 15:08:38 -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 PAA04884; Mon, 27 Oct 2003 15:08:25 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEDfH-0003QW-00; Mon, 27 Oct 2003 15:08:35 -0500 Received: from nwkea-mail-2.sun.com ([192.18.42.14]) by ietf-mx with esmtp (Exim 4.12) id 1AEDfG-0003Pp-00; Mon, 27 Oct 2003 15:08:34 -0500 Received: from centralmail2brm.Central.Sun.COM ([129.147.62.14]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id h9RK7xxA009860; Mon, 27 Oct 2003 12:07:59 -0800 (PST) Received: from binky.central.sun.com (binky.Central.Sun.COM [129.153.128.104]) by centralmail2brm.Central.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id h9RK7v58012282; Mon, 27 Oct 2003 13:07:58 -0700 (MST) Received: from binky.central.sun.com (localhost [127.0.0.1]) by binky.central.sun.com (8.12.5+Sun/8.12.3) with ESMTP id h9RK3qQx003840; Mon, 27 Oct 2003 12:03:52 -0800 (PST) Received: (from nw141292@localhost) by binky.central.sun.com (8.12.5+Sun/8.12.3/Submit) id h9RK3oR7003839; Mon, 27 Oct 2003 12:03:50 -0800 (PST) Date: Mon, 27 Oct 2003 12:03:50 -0800 From: Nicolas Williams To: ipsec@lists.tislabs.com, ietf-sasl@imc.org, ipsec-policy@vpnc.org, ietf-krb-wg@anl.gov, ietf-tls@lists.certicom.com, ietf-ssh@netbsd.org, ietf-cat-wg@lists.stanford.edu, ips@ietf.org Cc: nfsv4@ietf.org Message-ID: <20031027200350.GI24528@binky.central.sun.com> Mail-Followup-To: ipsec@lists.tislabs.com, ietf-sasl@imc.org, ipsec-policy@vpnc.org, ietf-krb-wg@anl.gov, ietf-tls@lists.certicom.com, ietf-ssh@netbsd.org, ietf-cat-wg@lists.stanford.edu, ips@ietf.org, nfsv4@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Followups-To: nfsv4@ietf.org Subject: [Ips] [I-D ACTION:draft-ietf-nfsv4-channel-bindings-00.txt] Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , [Apologies for the cross-post; followups should NOT be cross-posted this widely. Please Cc ONLY the appropriate WG mailing list(s) on any replies. Since I am not subscribed to all of the relevant WGs' mailing lists, please Cc me in all replies.] The NFSv4 WG I-D on channel bindings needs review from several IETF WGs. This I-D, draft-ietf-nfsv4-channel-bindings-00.txt, goes along with the soon to be published draft-ietf-nfsv4-ccm-03.txt (currently: -02). We would appreciate feedback from the Cc'ed WGs on several areas as requested below. Please cc the appropriate WG lists only in your replies. The I-D announcement is included below, including the I-D Abstract. Thanks, Nico Review requests: - From all the cc'ed WGs, the security community in general and the [concluded] CAT WG mailing list: o Please review the generic definition of "channel bindings" in this I-D and the concept of "channel bindings" in general. (Use the CAT WG list and/or the NFSv4 WG list.) - From the IPSEC WG: o Please review the IPsec channel construction in this I-D and the relevant interface requirements. o Please review the IPsec channel bindings construction. (Use the IPSEC WG and/or the IPSP WG lists.) - From the IPSP WG: o Please review the IPsec channel construction in this I-D and the relevant interface requirements. (Use the IPSEC WG and/or the IPSP WG lists.) - From the IPS WG: o Please consider the channel bindings concept as a general solution to the problems with the iSCSI approach to security ("authenticate at iSCSI layer with x, y or z authentication technology, but delegate session integrity/confidentiality protection to IPsec"). See the introduction (section 1) of this I-D for a description of the problem with the iSCSI approach to security. (I realize that I'm late to the iSCSI party - my goal is not to affect the progression of the iSCSI I-Ds to Proposed Standard and publication as RFCs, far from it.) (Use the IPS WG list.) - From the TLS WG: o Please review the construction of channel bindings to TLS channels given in this I-D. (Use the TLS WG list.) - From the SECSH WG: o Please review the construction of channel bindings to SSHv2 channels given in this I-D. (Use the SECSH WG list.) - From the KRB WG: o Please review sections 3.3 and 4.5 of this I-D. (Use the KRB WG list.) - From the SASL WG: o Please review section 3.2 of this I-D. (Use the SASL WG list.) ----- Forwarded message from Internet-Drafts@ietf.org ----- Date: Fri, 24 Oct 2003 10:50:50 -0400 From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-nfsv4-channel-bindings-00.txt To: IETF-Announce: ; Cc: nfsv4@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network File System Version 4 Working Group of the IETF. Title : On the Use of Channel Bindings to Secure Channels Author(s) : N. Williams Filename : draft-ietf-nfsv4-channel-bindings-00.txt Pages : 14 Date : 2003-10-23 This document defines and formalizes the concept of channel bindings to secure layers and defines the actual contents of channel bindings for several secure channels. The concept of channel bindings allows applications to prove that the end-points of two secure channels are the same by binding authentication at one network layer to the session protection negotiation at a lower network layer. The use of channel bindings allows applications to delegate session protection to lower layers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-channel-bindings-00.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-nfsv4-channel-bindings-00.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-nfsv4-channel-bindings-00.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. ----- End forwarded message ----- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Mon Oct 27 19:14:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00067 for ; Mon, 27 Oct 2003 19:14:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEHUu-0004BP-GE for ips-archive@odin.ietf.org; Mon, 27 Oct 2003 19:14:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9S0E89Q016073 for ips-archive@odin.ietf.org; Mon, 27 Oct 2003 19:14:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEHUu-0004BA-Ax for ips-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 19:14:08 -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 TAA00056 for ; Mon, 27 Oct 2003 19:13:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEHUs-0002XC-00 for ips-web-archive@ietf.org; Mon, 27 Oct 2003 19:14:06 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AEHUs-0002X9-00 for ips-web-archive@ietf.org; Mon, 27 Oct 2003 19:14:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEHUn-00049b-Oc; Mon, 27 Oct 2003 19:14:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEHTv-00047H-DV for ips@optimus.ietf.org; Mon, 27 Oct 2003 19:13:07 -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 TAA00034 for ; Mon, 27 Oct 2003 19:12:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEHTt-0002WH-00 for ips@ietf.org; Mon, 27 Oct 2003 19:13:05 -0500 Received: from palrel11.hp.com ([156.153.255.246]) by ietf-mx with esmtp (Exim 4.12) id 1AEHTt-0002W8-00 for ips@ietf.org; Mon, 27 Oct 2003 19:13:05 -0500 Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.96.64.26]) by palrel11.hp.com (Postfix) with ESMTP id CAC751C00819 for ; Mon, 27 Oct 2003 16:13:00 -0800 (PST) Received: from swathi.rose.hp.com (dhcp-roseor-bec059.rose.hp.com [15.23.142.59]) by rosemail.rose.hp.com with ESMTP (8.7.1/8.7.3 SMKit7.02) id QAA27854 for ; Mon, 27 Oct 2003 16:12:59 -0800 (PST) Message-Id: <6.0.0.22.1.20031027160618.05fe5140@rosemail.rose.hp.com> X-Sender: cbm@rosemail.rose.hp.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 27 Oct 2003 16:12:55 -0800 To: ips@ietf.org From: "Mallikarjun C." In-Reply-To: <026501c37628$1b2f9b20$5b8d170f@rose.hp.com> References: <026501c37628$1b2f9b20$5b8d170f@rose.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Ips] iSER paper Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , All: Some requested me for a copy of this paper earlier. The paper is now publicly available at: http://www.acm.org/sigcomm/sigcomm2003/workshop/niceli/papers/NICELI-p10-iSER.pdf FYI. Mallikarjun >----- Original Message ----- >From: "Mallikarjun C." >To: >Sent: Tuesday, September 02, 2003 10:53 AM >Subject: iSER slides for NICELI > > > > All: > > > > I posted the slides I presented recently in the NICELI > > ACM SIGCOMM workshop in Karlsruhe, Germany. > > They are available at: > > > > http://storage-arch.hp.com/study_of_iSER_slides.pdf > > > > These slides present the paper "A study of iSCSI > > Extensions for RDMA (iSER)" by five authors, including > > myself. > > > > It was promised that the paper itself will be posted > > shortly on the ACM website for public access. I will > > see what I can do if that runs into problems. > > -- > > Mallikarjun > > > > Mallikarjun Chadalapaka > > Networked Storage Architecture > > Network Storage Solutions > > Hewlett-Packard MS 5668 > > Roseville CA 95747 > > cbm@rose.hp.com > > > > _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Wed Oct 29 13:56:00 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26680 for ; Wed, 29 Oct 2003 13:56:00 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEvTo-000631-Km for ips-archive@odin.ietf.org; Wed, 29 Oct 2003 13:55:40 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9TIteVE023245 for ips-archive@odin.ietf.org; Wed, 29 Oct 2003 13:55:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEvTo-00062p-Br for ips-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 13:55:40 -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 NAA26616 for ; Wed, 29 Oct 2003 13:55:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEvTm-0000CL-00 for ips-web-archive@ietf.org; Wed, 29 Oct 2003 13:55:38 -0500 Received: from sausage.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AEvTl-0000BX-02 for ips-web-archive@ietf.org; Wed, 29 Oct 2003 13:55:37 -0500 Received: from [132.151.6.22] (helo=optimus.ietf.org) by manatick with esmtp (Exim 4.24) id 1AEvPR-0007L0-HW for ips-web-archive@ietf.org; Wed, 29 Oct 2003 13:51:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEvPK-0005fW-7I; Wed, 29 Oct 2003 13:51:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEvOd-0005dY-H2 for ips@optimus.ietf.org; Wed, 29 Oct 2003 13:50: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 NAA26522 for ; Wed, 29 Oct 2003 13:50:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEvOb-00009f-00 for ips@ietf.org; Wed, 29 Oct 2003 13:50:17 -0500 Received: from web20713.mail.yahoo.com ([66.163.169.154]) by ietf-mx with smtp (Exim 4.12) id 1AEvOa-00009b-00 for ips@ietf.org; Wed, 29 Oct 2003 13:50:16 -0500 Message-ID: <20031029185016.8774.qmail@web20713.mail.yahoo.com> Received: from [66.243.153.70] by web20713.mail.yahoo.com via HTTP; Wed, 29 Oct 2003 10:50:16 PST Date: Wed, 29 Oct 2003 10:50:16 -0800 (PST) From: dan yo To: ips@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1673957680-1067453416=:8233" Subject: [Ips] Full Feature Phase and Digests Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , --0-1673957680-1067453416=:8233 Content-Type: text/plain; charset=us-ascii Hi, I have a question on whether digest (header and data) can appear before the FFP. I found the same question from the archive but couldn't find the answer, could someone confirm. Thanks. Dan An earlier email from archive: I am not sure if this is the place for me to ask this question, so forgive me if I am out of line. Is there a difference between S5: LOGGED_IN and Full Feature Phase (a.k.a. full-feature phase in some parts of the document; it would be nice if they were all the same; I am not a regex guru)? If so, and I understand the digest section, neither the logout or login PDU's will have digests on them. I believe this holds even after the first connection of the session, because later connections are not yet in Full Feature Phase (S5). I.e. Only iSCSI op codes 0x00, 0x01, 0x02, 0x04, 0x05, 0x010, 0x1c-0x1e (maybe) for the initiator, and 0x20, 0x21, 0x22, 0x24, 0x25, 0x31, 0x32, 0x3c-0x3e (maybe), 0x3f for the target (anything not Logout or Login) will have the Digests and they must have them if stated in Login of the session? Am I right? TIA Sincerely, Randy Jennings Data Transit --------------------------------- Do you Yahoo!? Exclusive Video Premiere - Britney Spears --0-1673957680-1067453416=:8233 Content-Type: text/html; charset=us-ascii
Hi,
I have a question on whether digest (header and data) can appear before the FFP.
I found the same question from the archive but couldn't find the answer, could someone confirm.  Thanks.
Dan
 
An earlier email from archive:
 
I am not sure if this is the place for me to ask this question, so forgive me if I am out of line.
Is there a difference between S5: LOGGED_IN and Full Feature Phase (a.k.a. full-feature phase in some parts of the document; it would be nice if they were all the same; I am not a regex guru)?
If so, and I understand the digest section, neither the logout or login PDU's will have digests on them. I believe this holds even after the first connection of the session, because later connections are not yet in Full Feature Phase (S5).
 
I.e. Only iSCSI op codes 0x00, 0x01, 0x02, 0x04, 0x05, 0x010, 0x1c-0x1e (maybe) for the initiator, and 0x20, 0x21, 0x22, 0x24, 0x25, 0x31, 0x32, 0x3c-0x3e (maybe), 0x3f for the target (anything not Logout or Login) will have the Digests and they must have them if stated in Login of the session?

Am I right?

TIA

Sincerely,

Randy Jennings

Data Transit

Do you Yahoo!?
Exclusive Video Premiere - Britney Spears --0-1673957680-1067453416=:8233-- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Wed Oct 29 14:30:07 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29556 for ; Wed, 29 Oct 2003 14:30:06 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEw0p-0000Y9-56 for ips-archive@odin.ietf.org; Wed, 29 Oct 2003 14:29:47 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9TJTl7c002113 for ips-archive@odin.ietf.org; Wed, 29 Oct 2003 14:29:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEw0o-0000Xr-WE for ips-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 14:29: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 OAA29509 for ; Wed, 29 Oct 2003 14:29:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEw0m-0001Gi-00 for ips-web-archive@ietf.org; Wed, 29 Oct 2003 14:29:44 -0500 Received: from sausage.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AEvww-000191-01 for ips-web-archive@ietf.org; Wed, 29 Oct 2003 14:25:46 -0500 Received: from [132.151.6.22] (helo=optimus.ietf.org) by manatick with esmtp (Exim 4.24) id 1AEvrS-0000QG-Tp for ips-web-archive@ietf.org; Wed, 29 Oct 2003 14:20:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEvrP-0008Ee-4X; Wed, 29 Oct 2003 14:20:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEvqb-0008BD-8N for ips@optimus.ietf.org; Wed, 29 Oct 2003 14:19:13 -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 OAA28564 for ; Wed, 29 Oct 2003 14:19:02 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEvqY-0000rm-00 for ips@ietf.org; Wed, 29 Oct 2003 14:19:10 -0500 Received: from mail4.microsoft.com ([131.107.3.122]) by ietf-mx with esmtp (Exim 4.12) id 1AEvqX-0000qL-00 for ips@ietf.org; Wed, 29 Oct 2003 14:19:09 -0500 Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 29 Oct 2003 11:18:38 -0800 Received: from 157.54.8.155 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 29 Oct 2003 11:18:37 -0800 Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 29 Oct 2003 11:18:37 -0800 Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 29 Oct 2003 11:18:25 -0800 Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069); Wed, 29 Oct 2003 11:18:36 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7097.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------InterScan_NT_MIME_Boundary" Subject: RE: [Ips] Full Feature Phase and Digests Date: Wed, 29 Oct 2003 11:18:35 -0800 Message-ID: Thread-Topic: [Ips] Full Feature Phase and Digests thread-index: AcOeTeAtt114XAKlS+eWBp8OUnl4QAAA3fug From: "Lakshmi Ramasubramanian" To: "dan yo" , X-OriginalArrivalTime: 29 Oct 2003 19:18:36.0495 (UTC) FILETIME=[739155F0:01C39E51] Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C39E51.721A9878" ------_=_NextPart_001_01C39E51.721A9878 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Header\Data digest can be used only in FFP. =20 -lakshmi ________________________________ From: ips-admin@ietf.org [mailto:ips-admin@ietf.org] On Behalf Of dan yo Sent: Wednesday, October 29, 2003 10:50 AM To: ips@ietf.org Subject: [Ips] Full Feature Phase and Digests Hi, I have a question on whether digest (header and data) can appear before the FFP. I found the same question from the archive but couldn't find the answer, could someone confirm. Thanks. Dan =20 An earlier email from archive: =20 I am not sure if this is the place for me to ask this question, so forgive me if I am out of line.=20 Is there a difference between S5: LOGGED_IN and Full Feature Phase (a.k.a. full-feature phase in some parts of the document; it would be nice if they were all the same; I am not a regex guru)? If so, and I understand the digest section, neither the logout or login PDU's will have digests on them. I believe this holds even after the first connection of the session, because later connections are not yet in Full Feature Phase (S5). =20 I.e. Only iSCSI op codes 0x00, 0x01, 0x02, 0x04, 0x05, 0x010, 0x1c-0x1e (maybe) for the initiator, and 0x20, 0x21, 0x22, 0x24, 0x25, 0x31, 0x32, 0x3c-0x3e (maybe), 0x3f for the target (anything not Logout or Login) will have the Digests and they must have them if stated in Login of the session? Am I right? TIA Sincerely, Randy Jennings Data Transit ________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears =20 ------_=_NextPart_001_01C39E51.721A9878 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Header\Data digest can be used only in=20 FFP.
 
 -lakshmi

From: ips-admin@ietf.org=20 [mailto:ips-admin@ietf.org] On Behalf Of dan yo
Sent:=20 Wednesday, October 29, 2003 10:50 AM
To:=20 ips@ietf.org
Subject: [Ips] Full Feature Phase and=20 Digests

Hi,
I have a question on whether digest (header and data) can appear = before the=20 FFP.
I found the same question from the archive but couldn't find = the=20 answer, could someone confirm.  Thanks.
Dan
 
An earlier email from archive:
 
I am not sure if this is the place for me to ask = this=20 question, so forgive me if I am out of line.
Is there a difference between S5: LOGGED_IN and Full = Feature=20 Phase (a.k.a. full-feature phase in some parts of the document; it would = be nice=20 if they were all the same; I am not a regex guru)?
If so, and I understand the digest section, neither = the logout=20 or login PDU's will have digests on them. I believe this holds even = after the=20 first connection of the session, because later connections are not yet = in Full=20 Feature Phase (S5).
 
I.e. Only iSCSI op codes 0x00, 0x01, 0x02, 0x04, = 0x05, 0x010,=20 0x1c-0x1e (maybe) for the initiator, and 0x20, 0x21, 0x22, 0x24, 0x25, = 0x31,=20 0x32, 0x3c-0x3e (maybe), 0x3f for the target (anything not Logout or = Login) will=20 have the Digests and they must have them if stated in Login of the=20 session?

Am I right?

TIA

Sincerely,

Randy Jennings

Data Transit

Do you Yahoo!?
Exclusive Video Premiere - Britney=20 Spears ------_=_NextPart_001_01C39E51.721A9878-- --------------InterScan_NT_MIME_Boundary-- _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips From exim@www1.ietf.org Fri Oct 31 23:24:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00773 for ; Fri, 31 Oct 2003 23:24:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFnJ4-0007Ze-W2 for ips-archive@odin.ietf.org; Fri, 31 Oct 2003 23:24:11 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA14OAWt029114 for ips-archive@odin.ietf.org; Fri, 31 Oct 2003 23:24:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFnJ4-0007ZU-2V for ips-web-archive@optimus.ietf.org; Fri, 31 Oct 2003 23:24: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 XAA00759 for ; Fri, 31 Oct 2003 23:23:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFnJ1-00042S-00 for ips-web-archive@ietf.org; Fri, 31 Oct 2003 23:24:07 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFnJ1-00042O-00 for ips-web-archive@ietf.org; Fri, 31 Oct 2003 23:24:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFnIw-0007YC-RV; Fri, 31 Oct 2003 23: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 1AFnI3-0007WN-T7 for ips@optimus.ietf.org; Fri, 31 Oct 2003 23:23:07 -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 XAA00752 for ; Fri, 31 Oct 2003 23:22:47 -0500 (EST) From: wrstuden@wasabisystems.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFnHt-000420-00 for ips@ietf.org; Fri, 31 Oct 2003 23:22:57 -0500 Received: from mononoke.wasabisystems.com ([151.199.66.145]) by ietf-mx with esmtp (Exim 4.12) id 1AFnHt-00041r-00 for ips@ietf.org; Fri, 31 Oct 2003 23:22:57 -0500 Received: by mononoke.wasabisystems.com (Postfix, from userid 1021) id 7391640134; Fri, 31 Oct 2003 23:22:47 -0500 (EST) Date: Fri, 31 Oct 2003 19:19:38 -0800 (PST) X-X-Sender: wrstuden@neverwinter.home-net.icnt.net To: dan yo Cc: ips@ietf.org Subject: Re: [Ips] Full Feature Phase and Digests In-Reply-To: <20031029185016.8774.qmail@web20713.mail.yahoo.com> Message-ID: References: <20031029185016.8774.qmail@web20713.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: ips-admin@ietf.org Errors-To: ips-admin@ietf.org X-BeenThere: ips@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IP Storage List-Post: List-Help: List-Subscribe: , On Wed, 29 Oct 2003, dan yo wrote: > Hi, > I have a question on whether digest (header and data) can appear before > the FFP. As far as I know, No. > I found the same question from the archive but couldn't find the answer, could someone confirm. Thanks. > Dan > > An earlier email from archive: > > I am not sure if this is the place for me to ask this question, so > forgive me if I am out of line. > Is there a difference between S5: LOGGED_IN and Full Feature Phase > (a.k.a. full-feature phase in some parts of the document; it would be > nice if they were all the same; I am not a regex guru)? Yes. S6 (IN_LOGOUT) and S7 (LOGOUT_REQUESTED) are also in Full Feature Phase. I think S8 (CLEANUP_WAIT) also would be FFP, but I'm not sure how many PDUs get transmitted. > If so, and I understand the digest section, neither the logout or login > PDU's will have digests on them. I believe this holds even after the > first connection of the session, because later connections are not yet > in Full Feature Phase (S5). I think the better way to think about this is to consider when the PDU was sent. The connection enters FFP: (initiator) after processing the Login Response that correctly (*) transitions out of login; (target) after sending the Login Response that transitions out of login. (*) The initiator should make sure it is happy with the Login RSP of course. For instance, if it hadn't set 'T' on the Login Request, it shouldn't honor 'T' on the RSP. As logout PDUs are sent after transitioning out of login, they should have digests. > I.e. Only iSCSI op codes 0x00, 0x01, 0x02, 0x04, 0x05, 0x010, 0x1c-0x1e (maybe) for the initiator, and 0x20, 0x21, 0x22, 0x24, 0x25, 0x31, 0x32, 0x3c-0x3e (maybe), 0x3f for the target (anything not Logout or Login) will have the Digests and they must have them if stated in Login of the session? > > Am I right? Not quite. Think of digests as each controled by a boolean, which is set at the end of login processing (if digests were negotiated of course). If the header_digest boolean is set, all PDUs must have a header. If the data_digest boolean is set, all PDUs with data segments must have data digests. The difference between the two views is a matter of how the receive logic is built. If you're in FFP and doing header digests, you evaluate the digest before you look at the opcode. You have to do this because until you know the header digest is ok, you can't trust the opcode! Think about the case where transmission corruption changed the opcode for a PDU, and made an FFP-phase PDU look like a login PDU. If we looked at the opcode before the header digest and made a decision based on opcode, we would look at this as a Login PDU, not pull the digest out of the command stream, and look at potentially erronious ahs and data segment length values. And then start processing commands that may not have been commands. :-) That's how an initiator and a target need to think about this. That said, I know that Data Transit make protocol analyzers. For an analyzer, I think it's fine to know that Login PDUs don't have digests, and everything else does. The only place this makes a difference is the corner case where an initiator sends a Login Request PDU after FFP. If header digests have been negotiated, it needs to add a header digest, then the target will reject the PDU. ;-) Since this is an error case, if an analyzer doesn't carry state for the whole connection, it's ok for it to not know FFP and then just make a choice based on opcode. Ethereal does this, and it's fine. Take care, Bill _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips