Qi, Yanling | 14 May 2007 23:29

Handling Expected-data-transfer-legnth and CDB transfer-len mismatch

Hi All,

 

We saw an initiator problem where the expected-data-transfer-length and transfer-len inside CDB got mismatched for a write-and-verify (10). The expected-data-transfer-length is 0x4000 but the transfer-len in the CDB is 0. The target completed the request with good status, turned Residual-underflow bit on and set residual-count=0x4000. See frames 16 and 38 in the attached ethereal trace file for details. Did the target handle this error condition correctly?

 

Thanks,

 

--yanling

 

Yanling Qi

Engenio Storage Group - LSI Logic

512-794-3713 (Office)

512-794-3702 (Fax)

yanling.qi <at> lsi.com

 

Attachment (expectedDataLength-transfer-len.pcap): application/octet-stream, 33 KiB
_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips
Eddy Quicksall | 18 May 2007 07:03

Re: StatSN question

It would mean the header and data has been received. The reason is because 
the target can use ExpStatSN to free the resources used to send the Data-in. 
At ERL 0 it is faster to just use the TCP ACK; for ERL > 0 I think there was 
argument given once that the TCP ACK may not really indicate that the data 
was received and hence the ExpStatSN would be used for that purpose (I don't 
really remember that well though).

Eddy

----- Original Message ----- 
From: "Ken Craig" <kcraig <at> istor.com>
To: <ips <at> ietf.org>
Sent: Friday, April 27, 2007 5:23 PM
Subject: [Ips] StatSN question

I have a question about what ExpStatSN means that
I can't find an answer for in the reflector archives
or in any of the RFCs.

I, as an iSCSI Target running at ERL=0, send a
DATA IN PDU with FINAL=1 and a StatSN of 0.  I
receive a SCSI CMD PDU with an ExpStatSN of 1.
Does this mean that the Initiator has received
the PDU BHS and all of the data or is it simply
an acknowledgement that it has received the PDU
BHS?

Thanks,
Ken Craig

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

Ken Craig | 18 May 2007 18:46
Favicon

RE: StatSN question

Eddy,

Thanks for the response.  I've got an Initiator
that is updating ExpStatSn before receiving all
of the data.  I consider that Initiator to be
broken but since the RFC doesn't specifically
state what you said I've got no choice but to
find a way to deal with it.

Ken Craig

-----Original Message-----
From: Eddy Quicksall [mailto:Quicksall_iSCSI <at> Bellsouth.net] 
Sent: Thursday, May 17, 2007 10:03 PM
To: Ken Craig; ips <at> ietf.org
Subject: Re: [Ips] StatSN question

It would mean the header and data has been received. The reason is
because 
the target can use ExpStatSN to free the resources used to send the
Data-in. 
At ERL 0 it is faster to just use the TCP ACK; for ERL > 0 I think there
was 
argument given once that the TCP ACK may not really indicate that the
data 
was received and hence the ExpStatSN would be used for that purpose (I
don't 
really remember that well though).

Eddy

----- Original Message ----- 
From: "Ken Craig" <kcraig <at> istor.com>
To: <ips <at> ietf.org>
Sent: Friday, April 27, 2007 5:23 PM
Subject: [Ips] StatSN question

I have a question about what ExpStatSN means that
I can't find an answer for in the reflector archives
or in any of the RFCs.

I, as an iSCSI Target running at ERL=0, send a
DATA IN PDU with FINAL=1 and a StatSN of 0.  I
receive a SCSI CMD PDU with an ExpStatSN of 1.
Does this mean that the Initiator has received
the PDU BHS and all of the data or is it simply
an acknowledgement that it has received the PDU
BHS?

Thanks,
Ken Craig

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

Julian Satran | 18 May 2007 21:47
Picon
Favicon

Re: StatSN question


ExpStatSN indicates to the target that the initiator has received the status for the task and the target may discard whatever it may have hold for the task.
It also indicates to to the target when it is safe to send the response to a task abort or a "group" abort task management function.
Whether you can you use TCP ack for the same pupose dependes on how you stack is layered and/or how your recovery from end-to-end errors is done.

Julo


"Eddy Quicksall" <Quicksall_iSCSI <at> Bellsouth.net>

18/05/07 08:03

To
"Ken Craig" <kcraig <at> istor.com>, <ips <at> ietf.org>
cc
Subject
Re: [Ips] StatSN question





It would mean the header and data has been received. The reason is because
the target can use ExpStatSN to free the resources used to send the Data-in.
At ERL 0 it is faster to just use the TCP ACK; for ERL > 0 I think there was
argument given once that the TCP ACK may not really indicate that the data
was received and hence the ExpStatSN would be used for that purpose (I don't
really remember that well though).

Eddy

----- Original Message -----
From: "Ken Craig" <kcraig <at> istor.com>
To: <ips <at> ietf.org>
Sent: Friday, April 27, 2007 5:23 PM
Subject: [Ips] StatSN question


I have a question about what ExpStatSN means that
I can't find an answer for in the reflector archives
or in any of the RFCs.

I, as an iSCSI Target running at ERL=0, send a
DATA IN PDU with FINAL=1 and a StatSN of 0.  I
receive a SCSI CMD PDU with an ExpStatSN of 1.
Does this mean that the Initiator has received
the PDU BHS and all of the data or is it simply
an acknowledgement that it has received the PDU
BHS?

Thanks,
Ken Craig


_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips



_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips
Ken Craig | 18 May 2007 22:05
Favicon

RE: StatSN question

Julian,
 
When you say "target may discard whatever it may have
hold for the task" aren't you saying the same thing as
Eddy.  That the ExpStatSN is an indication that the
Initiator has also received the data since resources would
have been used for the data.
 
Thanks,
Ken Craig
 
 
 -----Original Message-----
From: Julian Satran [mailto:Julian_Satran <at> il.ibm.com]
Sent: Friday, May 18, 2007 12:47 PM
To: Eddy Quicksall
Cc: ips <at> ietf.org; Ken Craig
Subject: Re: [Ips] StatSN question


ExpStatSN indicates to the target that the initiator has received the status for the task and the target may discard whatever it may have hold for the task.
It also indicates to to the target when it is safe to send the response to a task abort or a "group" abort task management function.
Whether you can you use TCP ack for the same pupose dependes on how you stack is layered and/or how your recovery from end-to-end errors is done.

Julo


"Eddy Quicksall" <Quicksall_iSCSI <at> Bellsouth.net>

18/05/07 08:03

To
"Ken Craig" <kcraig <at> istor.com>, <ips <at> ietf.org>
cc
Subject
Re: [Ips] StatSN question





It would mean the header and data has been received. The reason is because
the target can use ExpStatSN to free the resources used to send the Data-in.
At ERL 0 it is faster to just use the TCP ACK; for ERL > 0 I think there was
argument given once that the TCP ACK may not really indicate that the data
was received and hence the ExpStatSN would be used for that purpose (I don't
really remember that well though).

Eddy

----- Original Message -----
From: "Ken Craig" <kcraig <at> istor.com>
To: <ips <at> ietf.org>
Sent: Friday, April 27, 2007 5:23 PM
Subject: [Ips] StatSN question


I have a question about what ExpStatSN means that
I can't find an answer for in the reflector archives
or in any of the RFCs.

I, as an iSCSI Target running at ERL=0, send a
DATA IN PDU with FINAL=1 and a StatSN of 0.  I
receive a SCSI CMD PDU with an ExpStatSN of 1.
Does this mean that the Initiator has received
the PDU BHS and all of the data or is it simply
an acknowledgement that it has received the PDU
BHS?

Thanks,
Ken Craig


_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips



_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips
Julian Satran | 18 May 2007 22:15
Picon
Favicon

RE: StatSN question


Definitely yes (acknowledging the status is equivalent to acking all the data). In addition resources are help to enable status retransmission even in commands that do not have data transfers. Julo


"Ken Craig" <kcraig <at> istor.com>

18/05/07 23:05

To
Julian Satran/Haifa/IBM <at> IBMIL
cc
<ips <at> ietf.org>
Subject
RE: [Ips] StatSN question





Julian,
 
When you say "target may discard whatever it may have
hold for the task" aren't you saying the same thing as
Eddy.  That the ExpStatSN is an indication that the
Initiator has also received the data since resources would
have been used for the data.
 
Thanks,
Ken Craig
 
 
 -----Original Message-----
From: Julian Satran [mailto:Julian_Satran <at> il.ibm.com]
Sent: Friday, May 18, 2007 12:47 PM
To: Eddy Quicksall
Cc: ips <at> ietf.org; Ken Craig
Subject: Re: [Ips] StatSN question


ExpStatSN indicates to the target that the initiator has received the status for the task and the target may discard whatever it may have hold for the task.
It also indicates to to the target when it is safe to send the response to a task abort or a "group" abort task management function.
Whether you can you use TCP ack for the same pupose dependes on how you stack is layered and/or how your recovery from end-to-end errors is done.

Julo

"Eddy Quicksall" <Quicksall_iSCSI <at> Bellsouth.net>

18/05/07 08:03


To
"Ken Craig" <kcraig <at> istor.com>, <ips <at> ietf.org>
cc
Subject
Re: [Ips] StatSN question







It would mean the header and data has been received. The reason is because
the target can use ExpStatSN to free the resources used to send the Data-in.
At ERL 0 it is faster to just use the TCP ACK; for ERL > 0 I think there was
argument given once that the TCP ACK may not really indicate that the data
was received and hence the ExpStatSN would be used for that purpose (I don't
really remember that well though).

Eddy

----- Original Message -----
From: "Ken Craig" <kcraig <at> istor.com>
To: <ips <at> ietf.org>
Sent: Friday, April 27, 2007 5:23 PM
Subject: [Ips] StatSN question


I have a question about what ExpStatSN means that
I can't find an answer for in the reflector archives
or in any of the RFCs.

I, as an iSCSI Target running at ERL=0, send a
DATA IN PDU with FINAL=1 and a StatSN of 0.  I
receive a SCSI CMD PDU with an ExpStatSN of 1.
Does this mean that the Initiator has received
the PDU BHS and all of the data or is it simply
an acknowledgement that it has received the PDU
BHS?

Thanks,
Ken Craig


_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips



_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips
iscsiperson | 19 May 2007 22:05
Picon
Favicon

Re: StatSN question

In the original message, Ken did NOT say that the "S" bit was set to 1 in the last Data-In PDU.
 
According to the RFC (3270) - Section 10.7.3"
 
"The fields StatSN, Status, and Residual Count only have meaningful content if the S bit is set to 1 and their values are defined in Section 10.4 SCSI Response."
 
My interpretation of that section would be that the iSCSI Initiator should NOT have sent ExpStatSN=1, until the SCSI Response PDU was received.
 
Take Care,
 
Greg Alvey
Solution Technoloy
 
 
-----Original Message-----
From: Julian_Satran <at> il.ibm.com
To: kcraig <at> istor.com
Cc: ips <at> ietf.org
Sent: Fri, 18 May 2007 1:15 PM
Subject: RE: [Ips] StatSN question

.AOLPlainTextBody { margin: 0px; font-family: Tahoma, Verdana, Arial, Sans-Serif; font-size: 12px; color: #000; background-color: #fff; } .AOLPlainTextBody pre { font-size: 9pt; } .AOLInlineAttachment { margin: 10px; } .AOLAttachmentHeader { font: 11px arial; border: 1px solid #7DA8D4; background: #F9F9F9; } .AOLAttachmentHeader .Title { font: 11px arial; background: #B5DDFA; padding: 3px 3px 3px 3px; } .AOLAttachmentHeader .FieldLabel { font: 11px arial; color: #000000; padding: 1px 10px 1px 9px; background: #F9F9F9; } .AOLAttachmentHeader .FieldValue { font: 11px arial; color: #000000; background: #F9F9F9; } .AOLAttachmentHeader a, .AOLImage a { color: #2864B4; text-decoration: none; } .AOLAttachmentHeader a:hover, .AOLImage a:hover { color: #2864B4; text-decoration: underline; } .AOLWebSuiteCompose .AOLPicturesFullSizeLink, .AOLWebSuite .AOLPicturesFullSizeLink { height: 1px; width: 1px; overflow: hidden; } body { background-color: white; font-family: "Verdana"; font-size: 10pt; border: 0px; } .AOLWebSuiteCompose p { margin: 0px; padding: 0px; } img.managedImg { width: 0px; height: 0px; } img.placeholder { width: 275px; height: 206px; background: #F4F4F4 center center no-repeat; border: 1px solid #DADAD6 !important; }

Definitely yes (acknowledging the status is equivalent to acking all the data). In addition resources are help to enable status retransmission even in commands that do not have data transfers. Julo


"Ken Craig" <kcraig <at> istor.com>
18/05/07 23:05
To
Julian Satran/Haifa/IBM <at> IBMIL
cc
<ips <at> ietf.org>
Subject
RE: [Ips] StatSN question





Julian,
 
When you say "target may discard whatever it may have
hold for the task" aren't you saying the same thing as
Eddy.  That the ExpStatSN is an indication that the
Initiator has also received the data since resources would
have been used for the data.
 
Thanks,
Ken Craig
 
 
 -----Original Message-----
From: Julian Satran [mailto:Julian_Satran <at> il.ibm.com]
Sent: Friday, May 18, 2007 12:47 PM
To: Eddy Quicksall
Cc: ips <at> ietf.org; Ken Craig
Subject: Re: [Ips] StatSN question


ExpStatSN indicates to the target that the initiator has received the status for the task and the target may discard whatever it may have hold for the task.
It also indicates to to the target when it is safe to send the response to a task abort or a "group" abort task management function.
Whether you can you use TCP ack for the same pupose dependes on how you stack is layered and/or how your recovery from end-to-end errors is done.

Julo

"Eddy Quicksall" <Quicksall_iSCSI <at> Bellsouth.net>
18/05/07 08:03

To
"Ken Craig" <kcraig <at> istor.com>, <ips <at> ietf.org>
cc
Subject
Re: [Ips] StatSN question







It would mean the header and data has been received. The reason is because
the target can use ExpStatSN to free the resources used to send the Data-in.
At ERL 0 it is faster to just use the TCP ACK; for ERL > 0 I think there was
argument given once that the TCP ACK may not really indicate that the data
was received and hence the ExpStatSN would be used for that purpose (I don't
really remember that well though).

Eddy

----- Original Message -----
From: "Ken Craig" <kcraig <at> istor.com>
To: <ips <at> ietf.org>
Sent: Friday, April 27, 2007 5:23 PM
Subject: [Ips] StatSN question


I have a question about what ExpStatSN means that
I can't find an answer for in the reflector archives
or in any of the RFCs.

I, as an iSCSI Target running at ERL=0, send a
DATA IN PDU with FINAL=1 and a StatSN of 0.  I
receive a SCSI CMD PDU with an ExpStatSN of 1.
Does this mean that the Initiator has received
the PDU BHS and all of the data or is it simply
an acknowledgement that it has received the PDU
BHS?

Thanks,
Ken Craig


_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips



_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________ Ips mailing list Ips <at> ietf.org https://www1.ietf.org/mailman/listinfo/ips
AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com.
_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips
Sandars, Ken | 21 May 2007 04:34
Favicon

RE: StatSN question

Hi Ken,

Interesting initiator. If it is truly issuing an ExpStatSN which
acknowledges a response which has not been sent by the target, the
implementers should be directed to section 3.2.2.2 of RFC3720.

Is it possible that the target is not initialising its StatSN counter
correctly? Your example refers to a StatSN of 0 for the Data-In PDU
(which I am assuming also has the S bit set). Have a read of section
10.13.4 and ensure the target is incrementing StatSN correctly.

HTH,
Ken

-----Original Message-----
From: Ken Craig [mailto:kcraig <at> istor.com] 
Sent: Saturday, 19 May 2007 02:47
To: Eddy Quicksall; ips <at> ietf.org
Subject: RE: [Ips] StatSN question

Eddy,

Thanks for the response.  I've got an Initiator that is updating
ExpStatSn before receiving all of the data.  I consider that Initiator
to be broken but since the RFC doesn't specifically state what you said
I've got no choice but to find a way to deal with it.

Ken Craig

-----Original Message-----
From: Eddy Quicksall [mailto:Quicksall_iSCSI <at> Bellsouth.net]
Sent: Thursday, May 17, 2007 10:03 PM
To: Ken Craig; ips <at> ietf.org
Subject: Re: [Ips] StatSN question

It would mean the header and data has been received. The reason is
because 
the target can use ExpStatSN to free the resources used to send the
Data-in. 
At ERL 0 it is faster to just use the TCP ACK; for ERL > 0 I think there
was 
argument given once that the TCP ACK may not really indicate that the
data 
was received and hence the ExpStatSN would be used for that purpose (I
don't 
really remember that well though).

Eddy

----- Original Message ----- 
From: "Ken Craig" <kcraig <at> istor.com>
To: <ips <at> ietf.org>
Sent: Friday, April 27, 2007 5:23 PM
Subject: [Ips] StatSN question

I have a question about what ExpStatSN means that
I can't find an answer for in the reflector archives
or in any of the RFCs.

I, as an iSCSI Target running at ERL=0, send a
DATA IN PDU with FINAL=1 and a StatSN of 0.  I
receive a SCSI CMD PDU with an ExpStatSN of 1.
Does this mean that the Initiator has received
the PDU BHS and all of the data or is it simply
an acknowledgement that it has received the PDU
BHS?

Thanks,
Ken Craig

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

Ken Craig | 21 May 2007 19:16
Favicon

RE: StatSN question

Ken,

My iSCSI Target has been working for the last
couple of years with all of the Initiators I
have been able to get a hold of.  I guess I
should have been more explicit in my example.
The Initiator negotiated a 256K
MaxRecvDataSegmentLength of 256K then sent a
128K Read command which allowed me to send all
of the data in one PDU.  The DATA IN PDU had
the Status and Final bits set with Command
Status of Good.  It wasn't until I had a
situation where a few of the Ethernet Frames
with the rest of the data for this particular
DATA IN PDU were stalled for ~.5 second (due
to what I think was the Initiator not opening
up its window size) that the problem was seen.  

Ken Craig

-----Original Message-----
From: Sandars, Ken [mailto:ken_sandars <at> adaptec.com] 
Sent: Sunday, May 20, 2007 7:34 PM
To: Ken Craig; Eddy Quicksall; ips <at> ietf.org
Subject: RE: [Ips] StatSN question

Hi Ken,

Interesting initiator. If it is truly issuing an ExpStatSN which
acknowledges a response which has not been sent by the target, the
implementers should be directed to section 3.2.2.2 of RFC3720.

Is it possible that the target is not initialising its StatSN counter
correctly? Your example refers to a StatSN of 0 for the Data-In PDU
(which I am assuming also has the S bit set). Have a read of section
10.13.4 and ensure the target is incrementing StatSN correctly.

HTH,
Ken

-----Original Message-----
From: Ken Craig [mailto:kcraig <at> istor.com] 
Sent: Saturday, 19 May 2007 02:47
To: Eddy Quicksall; ips <at> ietf.org
Subject: RE: [Ips] StatSN question

Eddy,

Thanks for the response.  I've got an Initiator that is updating
ExpStatSn before receiving all of the data.  I consider that Initiator
to be broken but since the RFC doesn't specifically state what you said
I've got no choice but to find a way to deal with it.

Ken Craig

-----Original Message-----
From: Eddy Quicksall [mailto:Quicksall_iSCSI <at> Bellsouth.net]
Sent: Thursday, May 17, 2007 10:03 PM
To: Ken Craig; ips <at> ietf.org
Subject: Re: [Ips] StatSN question

It would mean the header and data has been received. The reason is
because 
the target can use ExpStatSN to free the resources used to send the
Data-in. 
At ERL 0 it is faster to just use the TCP ACK; for ERL > 0 I think there
was 
argument given once that the TCP ACK may not really indicate that the
data 
was received and hence the ExpStatSN would be used for that purpose (I
don't 
really remember that well though).

Eddy

----- Original Message ----- 
From: "Ken Craig" <kcraig <at> istor.com>
To: <ips <at> ietf.org>
Sent: Friday, April 27, 2007 5:23 PM
Subject: [Ips] StatSN question

I have a question about what ExpStatSN means that
I can't find an answer for in the reflector archives
or in any of the RFCs.

I, as an iSCSI Target running at ERL=0, send a
DATA IN PDU with FINAL=1 and a StatSN of 0.  I
receive a SCSI CMD PDU with an ExpStatSN of 1.
Does this mean that the Initiator has received
the PDU BHS and all of the data or is it simply
an acknowledgement that it has received the PDU
BHS?

Thanks,
Ken Craig

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

Internet-Drafts | 23 May 2007 00:50
Picon
Favicon

I-D ACTION:draft-ietf-ips-iscsi-impl-guide-08.txt

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		: iSCSI Corrections and Clarifications
	Author(s)	: M. Chadalapaka
	Filename	: draft-ietf-ips-iscsi-impl-guide-08.txt,.pdf
	Pages		: 49
	Date		: 2007-5-22
	
iSCSI is a SCSI transport protocol and maps the SCSI 
     architecture and command sets onto TCP/IP.  RFC 3720 defines 
     the iSCSI protocol.  This document compiles the 
     clarifications to the original protocol definition in RFC 
     3720 to serve as a companion document for the iSCSI 
     implementers. This document updates RFC 3720 and the text in 
     this document supersedes the text in RFC 3720 when the two 
     differ.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ips-iscsi-impl-guide-08.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-iscsi-impl-guide-08.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 <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ips-iscsi-impl-guide-08.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.
Attachment: message/external-body, 144 bytes
_______________________________________________
Ips mailing list
Ips <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ips

Gmane