Re: iSCSI: AHS Length field for Responses?

To: Michael Schoberg <michael_schoberg@cnt.com>
Subject: Re: iSCSI: AHS Length field for Responses?
From: "Julian Satran" <Julian_Satran@il.ibm.com>
Date: Tue, 23 Apr 2002 08:13:57 +0300
Cc: "IPS Reflector (E-mail)" <ips@ece.cmu.edu>, owner-ips@ece.cmu.edu
Content-Type: multipart/alternative; boundary="=_alternative 001C6D46C2256BA4_="
Sender: owner-ips@ece.cmu.edu

It is only a semantic element and enables a common parser for all headers - and who nows - they might be needed in the future.

Julo

Michael Schoberg <michael_schoberg@cnt.com>
Sent by: owner-ips@ece.cmu.edu

04/23/2002 01:54 AM
Please respond to Michael Schoberg

To: "IPS Reflector (E-mail)" <ips@ece.cmu.edu>
cc:
Subject: iSCSI: AHS Length field for Responses?

Why do all the T->I response messages have the 'TotalAHSLength' field?
Section 9.2 states:

"iSCSI response PDUs do not have AH Segments."

Shouldn't responses have those bytes "reserved"?

Thanks.

Prev by Date: iSCSI: AHS Length field for Responses?
Next by Date: Re: iSCSI: Questions regarding text parameter 'Reject' and 'Irrelevant' usage
Prev by thread: iSCSI: AHS Length field for Responses?
Next by thread: Re: iSCSI: Questions regarding text parameter 'Reject' and 'Irrelevant' usage
Index(es):
- Date
- Thread

Home

Last updated: Tue Apr 23 02:18:28 2002
9755 messages in chronological order