Re: iSCSI 4.1 & 4.2

[Mark Bakke <mbakke@cisco.com>]

Julian-

Sorry, I've been unavailable the last few days.  What do you mean
about the note not being concrete?  The string-prep draft says
exactly which additional characters we need for the name-value
(all of the international lower-case equivalent characters
are valid), and the utf8-value specifies that any UTF-8
character is legal (other than \0).

Without adding these, we would have to ditch internationalization
completely within iSCSI names, but since the DNS folks are going
through the pain of internationalizing host and domain names, we
should keep internationalization in iSCSI as well.

--
Mark

Julian Satran wrote:
> 
> Mark,
> 
> John Hufferd has solicited twice input from NDT about their additional requirement.
> I did not hear back from you.
> The attached note does not say anything concrete (are some characters that you need missing?)
> either.
> 
> Julo
> 
>   Mark Bakke <mbakke@cisco.com>
>   Sent by: mbakke@cisco.com                   To:        Julian Satran/Haifa/IBM@IBMIL
>                                               cc:        ips@ece.cmu.edu
>   05/01/2002 08:52 PM                         Subject:        Re: iSCSI 4.1 & 4.2
>   Please respond to Mark Bakke
> 
> 
> Julian-
> 
> Text-value is also used for initiator names, target names,
> and aliases, which are UTF-8 encoded, so they don't fit into
> the current text-value definition.   Here are two more
> text value types we should add.
> 
> --
> Mark
> 
> Julian Satran wrote:
> >
> > text-value: a string defined by the regular expression
> > "[][a-zA-Z0-9.-+@_/\[\]=]*"
> 
> Used by InitiatorName and TargetName:
> 
> name-value: a UTF-8 string, with its valid character set
> defined in draft-ietf-ips-iscsi-string-prep-00.
> 
> Used by InitiatorAlias and TargetAlias:
> 
> utf8-value: any UTF-8 string, terminated by a null character,
> Ranges and comma-separated lists are not allowed for keys
> that use this type.
> 
> --
> Mark

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