[EAI] POP (draft-ietf-eai-rfc5721bis-05), SASLPrep, and Stringprep

[John C Klensin <[e-mail]>]

Hi.

Just checking that what this document says is what everyone
wants...

Section 3.2 of draft-ietf-eai-rfc5721bis-05 is very heavily
dependent on SASLprep [RFC4013], including MUST requirements.
SASLPrep is, in turn, dependent on Stringprep, which is tied to
Unicode 3.2.   Questions:

(1) Could someone who is closer to SASLPrep and the PRECIS work
tell us whether they are comfortable with this or whether the
text in this spec should be modified somewhat?  If any changes
are likely to be completely compatible, I don't think there is a
problem.  However,...

(2) If changes are needed, should Section 3.2 be rewritten to
explicitly allow conformance with the successors of 4013 as an
alternative?  I think that would require only a few changes of
wording.

(3) Or are we better off just leaving this alone and monitoring
any 4013bis efforts to make sure they contain provisions to
explicitly update our spec when the time comes?

These are just questions --if the WG is ok with things as they
are, so am I.  But I can see this causing questions during IETF
Last Call and want to be sure we have considered the issue.

    john