#25337: Validate domains against IDNA2008 instead of IDNA2003
-------------------------------+------------------------------
Reporter: JocelynD | Owner: nobody
Type: Uncategorized | Status: new
Component: Forms | Version: 1.8
Severity: Normal | Keywords: domains idn idna
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------
IDNA domains validation is a mess, anyway, it's going forward, and
IDNA2008 refines IDNA2003 proposal to better define what is a valid IDN
domain and what is not.
ICANN/IANA [https://www.icann.org/resources/pages/idn-
guidelines-2011-09-02-en recomends using IDNA2008]
However, python standard lib
[https://docs.python.org/3/library/codecs.html?highlight=idna#module-
encodings.idna only offers IDNA2003] validation in , and one have to use
[https://pypi.python.org/pypi/idna a 3rd party lib] to encode/validate
against IDNA2008.
Currently, on URLValidator, EmailValidator
([https://code.djangoproject.com/ticket/18119 and soon DomainNameValidator
?]), Django relies on Python builtin `str.encode('idna')`.
I don't come with a solution for Django, and I know that Django avoid to
depend on 3rd-party libs.
However I do think that it would be a good thing that Django validates
domains against IDNA2008.
What do you think ?
--
Ticket URL: <https://code.djangoproject.com/ticket/25337>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.9a1b4b581f04d1bc63c7aa975921a809%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
