RE: ISCSI: question about text command data

["Lee Xing" <lxing@Crossroads.com>]

Agree with Santosh, Paul, Mark and Dev.  The statement on page 64 of
v.07 "Every key=value pair (including the last or only pair) MUST be
followed by null (0x00) delimiter." implies **one** null should be used.
It's better to explicitly address that EXACTLY one null MUST be used to
separate "key=value" pairs.  Also, using two nulls (0x00) after the last
or only "key=value" pair is handy for programmers.

Thanks.


Lee
Crossroads Systems, Inc.

-----Original Message-----
From: Santosh Rao [mailto:santoshr@cup.hp.com]
Sent: Tuesday, September 18, 2001 1:36 PM
To: ietf-ips
Subject: Re: ISCSI: question about text command data


I agree with Paul, Mark, Dev that the spec must require that login
"key=value"
pairs MUST be seperated by EXACTLY 1 null (0x00) delimiter. Failure to
comply
results in the target detecting a format error on the login PDU.

- Santosh


Dev wrote:

> Yes. The spec should specifically state that there has to 'exactly one
NULL
> character'.
>
> Deva
> Adaptec
>
> -----Original Message-----
> From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On Behalf Of
> CONGDON,PAUL (HP-Roseville,ex1)
> Sent: Tuesday, September 18, 2001 8:11 AM
> To: 'Steve Senum'; ietf-ips
> Subject: RE: ISCSI: question about text command data
>
> I disagree.  There is no reason why the spec shouldn't be very
specific
> about what behavior to take.  In the interest of simplicity, the spec
should
> state 'exactly one null character' as Mark and Buck request.   If
people
> follow the spec, there won't be a need to invoke costly error
response.
>
> Paul
>
> -----Original Message-----
> From: Steve Senum [mailto:ssenum@cisco.com]
> Sent: Monday, September 17, 2001 8:27 AM
> To: ietf-ips
> Subject: Re: ISCSI: question about text command data
>
> Mark,
>
> I agree with Julian on this issue.
>
> Steve Senum
>
> Mark Bakke wrote:
> >
> > Julian-
> >
> > Wouldn't it be simpler to just say "exactly one".  The last
> > part of Buck's question mentioned that he didn't see why
> > anyone would want more than one, and nobody responded saying
> > they did.
> >
> > Thanks,
> >
> > Mark
> >
> > Julian Satran wrote:
> > >
> > > I've changed it the text to "at least one" to avoid errors hard to
list.
> > >
> > > Julo
> > >
> > > "Buck Landry" <blandry@Crossroads.com>@ece.cmu.edu on 13-09-2001
> 01:25:36
> > >
> > > Please respond to "Buck Landry" <blandry@Crossroads.com>
> > >
> > > Sent by:  owner-ips@ece.cmu.edu
> > >
> > > To:   <ips@ece.cmu.edu>
> > > cc:
> > > Subject:  ISCSI: question about text command data
> > >
> > > I have a small question about what separates the "key=value" pairs
in
> > > the data segment of an iscsi text command.  On pg. 78 of the iscsi
v7-90
> > > draft (2.10.5), it states:
> > >
> > > >>>
> > > Every key=value pair (including the last or only pair) MUST be
followed
> > > by null (0x00) delimiter.
> > > <<<
> > >
> > > The question: is it legal to have *more* than one null char
between
> > > key=value pairs?  (no, I don't know why anybody would particularly
want
> > > to do this.)
> > >
> > > Thanks,
> > > buck
> >
> > --
> > Mark A. Bakke
> > Cisco Systems
> > mbakke@cisco.com
> > 763.398.1054