Re: How should a target respond if it receives a TEXT command before a LOGIN?

[julian_satran@il.ibm.com]

1. A text command before the login... what for?

In the normal sequence of events it could happen only if the Login command
is dropped - and
it is hard to see how this can happen.

The login phase is a long linked set of commands (there can't be several
outstanding) that have one singe Initiator task tag.
Text before login is an error.


2. If I'll see another vote for a 0,1 flip in the WN - I'll change it (1
and 0 have equal weight with me and with many of the implementers close to
me) -:)


Julo


Mark Burton <markb@ordern.com> on 27/02/2001 13:31:56

Please respond to Mark Burton <markb@ordern.com>

To:   ips@ece.cmu.edu
cc:
Subject:  How should a target respond if it receives a TEXT command before
      a LOGIN?





The choice seems to be one of:

1 - reject with format error -- not really true as the TEXT command
    may actually contain valid information

2 - reject with full feature phase error -- again, not really true as
    TEXT commands are allowed in the login phase

3 - just ignore -- unhelpful

Any ideas?

BTW - I second the proposal that the sense of the
what-comes-next-is-a-data-segment bit in the WN word should be
inverted.

Regards,

Mark