matrix-org / matrix-org/matrix-spec

Domain preparation (avoid "A-Label" in the domain names).

Open
#439 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-S2S feature
Dominant language
HTML
Stars
330
Forks
150
Avg merge
2h 21m
Merged PRs (30d)
3

Description

According the IDNA (https://tools.ietf.org/html/rfc5890) there are a several ways to represent the same domain if we use non-ASCII symbols.
For example, the domain `öbb.at` can be represent by `öbb.at` or `xn--bb-eka.at`. The first form is called U-label and uses unicode symbols. The second form is called A-label and uses only ASCII-symbols.

To convert from an one form to the another uses the `Punycode` algorithm (https://tools.ietf.org/html/rfc3492, https://tools.ietf.org/html/rfc3490#section-4, https://www.unicode.org/reports/tr46/#Compatibility_Processing and online tool https://www.punycoder.com/).

In the specification (https://matrix.org/docs/spec/appendices.html) it is only says that `DNS names for use with Matrix should follow the conventional restrictions for internet hostnames: they should consist of a series of labels separated by ., where each label consists of the alphanumeric characters or hyphens.` So we can have hostnames with non-ASCII symbols.

Should we have a domain preparation step to avoid using the A-label like `xn--bb-eka.at` and always use only U-label like `öbb.at`?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Matrix specification and the IDNA, Punycode, and Unicode TR46 references cited in the issue. Determine whether Matrix should prefer U-labels over A-labels and identify the relevant specification section. Done means reaching a clear decision and documenting the agreed domain-preparation behavior.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.