Re: iSCSI: Case-sensitivity in iSCSI names

["Julian Satran" <Julian_Satran@il.ibm.com>]

John,

Case insesitive is bad for I18N

Julo

"John Hufferd" <hufferd@us.ibm.com> on 18-07-2001 08:53:56

Please respond to "John Hufferd" <hufferd@us.ibm.com>

To:   Mark Bakke <mbakke@cisco.com>
cc:   IPS <ips@ece.cmu.edu>
Subject:  Re: iSCSI: Case-sensitivity in iSCSI names





Mark,
You are talking about things that are entered by administrators.  They will
have a lot of finger checks.  I do not see why we would like to encourage
admin problems by making these things Case Sensitive.  Imagine, one
administrator trying to tell another over the phone, what the name should
be used.

I would vote for Case insensitive names.

.
.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/SSG San Jose Ca
Main Office (408) 256-0403, Tie: 276-0403,  eFax: (408) 904-4688
Home Office (408) 997-6136
Internet address: hufferd@us.ibm.com


Mark Bakke <mbakke@cisco.com>@ece.cmu.edu on 07/17/2001 01:28:52 PM

Sent by:  owner-ips@ece.cmu.edu


To:   IPS <ips@ece.cmu.edu>
cc:
Subject:  iSCSI: Case-sensitivity in iSCSI names




We are attempting to wrap up all of the issues surrounding
the creation and comparison of iSCSI initiator and target
names.  One of these is whether the names are case-sensitive.

The last naming & discovery draft stated that the names are
case-insensitive; this was to allow better transcribability
in cases where names were communicated outside the automated
discovery processes.

This comes at some expense, particularly since these names
are defined to allow UTF-8 encoding of international character
sets.  Initiators and targets would have to include code to
compare these sets.

To simplify implementation and interoperability, it has been
recommended that we make iSCSI names case-sensitive instead.

I am fine with doing this, and I think that we could even
get some of the usability back by adding these rules:

- iSCSI names MUST be case-sensitive, and compared strictly
  byte-for-byte.

- iSCSI names SHOULD be generated in a case-insensitive
  manner.

I'm not sure how to properly word the latter, but the intent
is that someone generating the names would not produce both:

  iqn.9.com.cisco.myiscsithing

and

  iqn.9.com.cisco.MyIscsiThing

since a user would be likely to confuse these.  Again, it doesn't
affect the protocol itself, just its usability.


Any thoughts?  Will it hurt anyone's plans if iSCSI names were
case-sensitive?



--
Mark A. Bakke
Cisco Systems
mbakke@cisco.com
763.398.1054