search

katzenpost / mixnet_uprising

repository for tracking open tasks
18 stars 1 forks source link

Standardize on lower case provider identifiers. #21

Open Yawning opened 6 years ago

Yawning commented 6 years ago

I just pushed a few changes to lower case Provider identifiers by default.

This should be mandatory behavior at some point, unless people have strong objections to such a thing, primarily because it's intended to serve as the domain component of the e-mail address, and such things are case insensitive anyway.

This could alternatively be formalized as something to be treated as case insensitive by everyone I suppose.

Yawning commented 6 years ago

Related to this, both the provider and the mailproxy will now apply PRECIS (RFC 8265) to the local-part component of addresses. If usernames are not configured as case sensitive (the default, which matches common mail server behavior) the UsernameCaseMapped profile will be used, otherwise it will use UsernameCasePreserved.

For people that are stuck in Python land, there's https://pypi.python.org/pypi/precis-i18n though I can't vouch for how good it is. This only really matters when people want to use non-ASCII characters though.

Yawning commented 6 years ago

My inclination here is to use https://tools.ietf.org/html/rfc5891#section-5 as the normalization method, unless people have strong feelings about this.

Yawning commented 6 years ago

The code side of this is done, this should be documented somewhere.

david415 commented 6 years ago

hmm probably doesn't belong in the end to end spec. perhaps in a document like this one is the right place: https://github.com/katzenpost/docs/blob/master/drafts/user_interface.txt

Yawning commented 6 years ago

The UI spec is mostly concerned with things that only affect the client, this has server/authority side impact, so I'm not sure if that's the right place either.