1 / 4

Support for Internationalized Email Addresses (EAI) in X.509 certificates

Support for Internationalized Email Addresses (EAI) in X.509 certificates. Alexey Melnikov <alexey.melnikov@isode.com> draft-ietf-pkix-eai-addresses-00.txt. Background. EAI WG in the Applications Area is working toward completing rfc5335bis/rfc5336bis rfc5336bis defines I18N email format as

Download Presentation

Support for Internationalized Email Addresses (EAI) in X.509 certificates

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Support for Internationalized Email Addresses (EAI) in X.509 certificates Alexey Melnikov <alexey.melnikov@isode.com> draft-ietf-pkix-eai-addresses-00.txt

  2. Background • EAI WG in the Applications Area is working toward completing rfc5335bis/rfc5336bis • rfc5336bis defines I18N email format as • <utf-8>@<utf-8> or <utf-8>@<ascii> • e.g. Aлексей.Мельников@ёлка.мойдомен.РФ • RFC 5280 defines rfc822Name subjectAltName choice for representing RFC 5322 email addresses, but that is not sufficient for the new format

  3. Open Issues • Multiple aliases • for the left hand side of I18N emails • More importantly: multiple aliases for the IDN domains (especially due to IDN 2008) • ёлка.мойдомен.РФ • елка.мойдомен.РФ • N left hand sides in M domains can make a certificate long • UTF8String X.509 type is not widely supported?

  4. Other relates tasks • Update RFC 5280 to use IDNA2008 language?

More Related