RE: Several iSCSI protocol questions

[Bill Studenmund <wrstuden@wasabisystems.com>]

On Fri, 30 Aug 2002, Tony Battersby wrote:

> > -----Original Message-----
> > From: Black_David@emc.com [mailto:Black_David@emc.com]
> > Sent: Friday, August 30, 2002 10:05 AM
> > To: tonyb@cybernetics.com; ips@ece.cmu.edu
> > Subject: RE: Several iSCSI protocol questions
> > Such a target is broken (if an AHS is allowed, the target has to
> > expect that it might be present and be prepared to do whatever
> > is necessary), and should be fixed.
>
>
> Let me give a better example: Section 9.2.2.1, AHSType, lists "60- 63
> Non-iSCSI extensions".  What should the target do if it comes across an AHS
> with an AHSType of 60?  Is there some other document specifying what these
> codes mean?

I had taken those AHS types to be vendor-specific. As such, I think it's
wrong for the initiator to have used one of them before negotiating with
the target to use it. And since negotiation happens before FFP, well,
there should be no qestion on if it's been negotiated or not. :-)

Take care,

Bill