RFC: Add `libidn2` support for Punycode Conversion in DNS Functions
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Proposal
Currently, DNS functions introduced by #8072 do not support Punycode conversion. Instead, they either throw an error if the domain name is not ASCII, or they return the result in its Punycode-encoded form without converting it back.
I have started some initial work on this in draft PR #8871.
Impact
Add 👍 to issues you consider important. If others benefit from the changes in this proposal being added, please ask them to add 👍 to it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the DNS functions introduced by #8072 and the initial work in draft PR #8871 first. Done means adding libidn2-backed Punycode conversion so non-ASCII domain names no longer error and returned results are converted from Punycode.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100