Re: [idn] Nameprep & Uniprep

["Edmon" <edmon@neteka.com>]

From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
> - uniprep/stringprep is a larger problem that may take a lot of time to do
> and will consider things that are not related to idn.
> - I think stringprep should not be in sync with the idn work.
>

But doesnt that defeat part of the purpose for uniprep as being a universal
prep mechanism that one of the most important identifiers on the internet,
the DNS doesnt even refer to it or use it?
I understand that uniprep is a larger problem, and I also understand the
time pressure seemingly surrounding this wg, but I think it is important
that ONCE it actually is there, it will be used by the DNS.  We should have
some provisions for it.  That is my main point.
Edmon

> Marc.
>
>
>
> > > >Anyway, these are my thoughts:
> > > >
> > > >Uniprep - Unicode Identifier Preparations
> > > >Nameprep - Domain Name Preparations
> > > >
> > > >Uniprep will be a looser specification for general Unicode
Identifiers.
> > > >
> > > >Nameprep will be include mandatory compliance with Uniprep and then
on
> >top
> > > >of it will include some or all of the following:
> > > >- additional mandatory preparations specifically for domain names
(might
> > > >not be required)
> > > >- Optional elements for zone operators
> > > >     - TS Conversion
> > > >     - Jpchar
> > > >     - Hangulchar
> > > >     - others...
> > > >
> > > >In other words, most of the existing Nameprep might be moved to
Uniprep,
> > > >while Nameprep becomes an architectural document for prepping domain
> >names
> > > >which references to Uniprep and the other language specific mappings,
> >plus
> > > >possibly some additional preparations specifically for domain names.
> > > >
> > > >Does this make sense?
> > > >
> > > >Edmon
> > > >
> > > >PS. perhaps Uniprep might better be discussed outside of the IDN
> >wg...?...
> > >
>