[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [idn] Nameprep & Uniprep



At/À 11:50 2001-08-09 -0400, Edmon you wrote/vous écriviez:
>From: "Marc Blanchet" <Marc.Blanchet@viagenie.qc.ca>
> > - it is sure that this stringprep work is outside of the idn charter. it
> > will be forwarded to the i18n ietf community (mailing list to be found
> > later (there is some works on this these days)) and to the idn wg for
> > information. but work and discussion on the generalized case will be done
> > outside of the idn wg.
>
>This is fine and great.  Then do we want to revisit the Nameprep document to
>change it into an architecture doc that would reference String/Uniprep
>(personally I like the name uniprep more...)?  I think this only makes sense
>as we know that there would be a universal preping mechanism.

- 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.

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...?...
> >