Re: I-D ACTION:draft-ietf-sasl-plain-05.txt

[Jeffrey Hutzelman <[e-mail]>]

On Wednesday, October 27, 2004 11:09:47 -0700 "Kurt D. Zeilenga" 
<[e-mail]> wrote:

>> and mention the value of the AllowUnassigned
>> flag for each string using MUST.
>
> I cannot find the term "AllowUnassigned flag" anywhere in
> the specification (including normative references).

This term was apparently used in some drafts of nameprep, and is referred
to in RFC3490 and draft-hoffman-rfc3490bis-02.txt.  Unfortunately, those 
references claim that the term is defined in RFC3491 and 
draft-hoffman-rfc3491bis-01.txt, respectively, and neither document defines 
the term.  Neither do stringprep or saslprep.

This flag was used as a parameter to the preparation algorithm in IDN, to 
indicate whether unassigned code points are permitted; it is what 
distinguishes between storage and query strings.  The profile defined by 
SASLprep does make such a distinction, but does not use a formally defined 
"flag".

We should mention in each case whether unassigned code points are permitted 
(query strings) or not (storage strings).  But we should not use a 
reference to an "AllowUnassigned flag" which our stringprep profile does 
not have.

> The text does, however, not only says that strings SHALL
> be prepared in accordance with StringPrep, it describes
> what that means in regards to unassigned code points
> and the two classes of strings.

Then this should be sufficient.

-- Jeff