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

Slides:



Advertisements
Similar presentations
A Profile for Trust Anchor Material for the Resource Certificate PKI Geoff Huston SIDR WG IETF 74.
Advertisements

Whois Internationalization Issues John C Klensin.
Internationalizing WHOIS Preliminary Approaches for Discussion Internationalized Registration Data Working Group ICANN Meeting, Brussels, Belgium Jeremy.
Moving Towards Internationalized Domain Names Paul Hoffman Internet Mail Consortium September 7, 2000.
Draft-ietf-eai-mailinglist-00.txt Mailing Lists and Internationalized Addresses IETF66 Montreal – July 11, 2006 Edmon Chung, Afilias
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 VLSM and CIDR Routing Protocols and Concepts – Chapter 6.
You’ve got be kidding! Asking about Japanese Domain Name at this late stage? Masato Minda Japan Registry Services 24 th January 2008, JANOG
Internationalized Domain Name Protocol (IDN) & It’s Test Suite in IPv6 Sunyoung Han, Keecheon Kim Dept. of Computer Science and Engineering Konkuk Univ.,
1 ecompany/amani Amani M. Bin Sewaif Senior Engineer Services Operations & Maintenance Etisalat – Intenet & e Solution November 22,
Introduction to Chinese Domain Name ZHANG Hong Aug 24, 2003.
November 2006IETF67 - ECRIT1 A Dynamic Host Configuration Protocol (DHCP) based Location-to-Service Translation Protocol (LoST) Discovery Procedure draft-polk-ecrit-dhc-lost-discovery-01.
IDN over EPP (IDNPROV) IETF BOF, Washington DC November 2004.
Universal Acceptance of IDN ICANN London |
IDN Standards and Implications Kenny Huang Board, PIR
History of IDN APNIC Beijing 2009 James Seng. Internationalized Domain Names
Internationalization of Domain Names Multilingual Domain Names: Joint ITU / WIPO Symposium International Conference Center of Geneva (CICG) December 6-7,
What's new in the World IMAP/LEMONADE/SIEVE (no DKIM or EAI) Alexey Melnikov.
EAI WG meeting IETF-65, March 20, Agenda 17:40 Welcome, blue sheet, scribe, agenda bashing 17:50 Review of WG charter (approved) 17:55 Problem/framing:
A brief introduction of JET and its activities 25 Mar 2003 Hiro HOTTA
AAA and Mobile IPv6 Franck Le AAA WG - IETF55. Why Diameter support for Mobile IPv6? Mobile IPv6 is a routing protocol and does not deal with issues related.
Rfc3280bis-00 David Cooper, NIST Tim Polk, NIST. Development Process ● October 2004: Tim Polk requested that people submit any issues that needed to be.
Duplicate Address Detection Proxy (draft-costa-6man-dad-proxy-00)
Universal Acceptance of All TLDs ALAC 24 June 2012.
IDN UPDATE Tina Dam ICANN Chief gTLD Registry Liaison Public Forum, Wellington 30 March 2006.
Deployment of IDN In Korea Aug. 23, 2003 Korea Network Information Center.
27 Mar 2000IETF IDN-WG1 Requirements for IDN and its Implementations from Japan Yoshiro YONEYA JPNIC IDN-TF / NTT Software Co.
The original Internationalized Domain Name (IDN) WG set the requirements for international characters in domain names in RFC 3454, RFC3490, RFC3491 and.
Internationalization of Domain Names James Seng CTO, i-DNS.net International co-chair, IETF IDN Working Group.
IPv4 Dependencies in Applications Area Specifications Margaret Wasserman draft-ietf-v6ops-ipv4survey-apps-01.txt.
Downgrading mechanism for Internationalized Address (IMA) draft-yoneya-ima-downgrade-00.txt Kazunori Fujiwara JPRS.
CDB Chris Bonatti (IECA, Inc.) Tel: (+1) Proposed PKI4IPSEC Certificate Management Requirements Document IETF #60 – PKI4IPSEC Working.
Universal Acceptance: APNIC system readiness Byron Ellacott Senior Software Architect.
ADDRESS INTERNATIONALIZATION ( EAI ) ICANN-55 Mar 06, 2016 TF-AIDN Member 35+ Min : 10- Min ( Q & A )
Etisalat/I&eS/SOM/Amani PAGE 1 Amani M. Bin Sewaif Senior Engineer Services Operations & Maintenance Etisalat – Intenet & e Solution
Public Key Infrastructure Using X.509 (PKIX) Working Group
Multilingual Domain Name
STIR Secure Telephone Identity Revisited
IETF 66 EAI WG Testing Report
Advertising Generic Information in IS-IS
56th IETF syslog WG Chair: Chris Lonvick
Address Internationalization
Stefan Santesson Microsoft
IETF 55 IPv6 Working Group IPv6 Node Requirements
Lionel Morand DHCP options for PAA Lionel Morand
Requirements for IPv6 prefix delegation for IETF-55th at Atlanta, Nov.2002 Shin Miyakawa NTT Communications.
IETF 65 Calsify WG March 21, 2006 Dallas, TX.
July 14th, to 1130 hours Vienna, Austria
GeoMesh Blockchain Networking - Slide Presentation
IETF Working Group CSCI 344 Spring 2016 Report <Your name>
Signaling RSVP-TE P2MP LSPs in an Inter-domain Environment draft-ali-mpls-inter-domain-p2mp-rsvp-te-lsp-01.txt Zafar Ali, Cisco Systems.
Signaled PID When Multiplexing Multiple Payloads over RSVP-TE LSPs draft-ali-mpls-sig-pid-multiplexing-case-00.txt Zafar Ali, Cisco Systems.
Virtual Hub-and-Spoke in BGP EVPNs
פחת ורווח הון סוגיות מיוחדות תהילה ששון עו"ד (רו"ח) ספטמבר 2015
JET Meeting Report - Agreement on IDN Registration Policy -
OSPF WG Status IETF 98, Chicago
Multilingual Domain Name
STIR WG IETF-99 PASSPorT Extension for Resource-Priority Authorization (draft-ietf-stir-rph-00) July, 2017 Ray P. Singh, Martin Dolly, Subir Das, and An.
IDN – behind scenes Душан Стојичевић UA ambassador ( Гранси (
Routing Protocols and Concepts – Chapter 6
Requirements for IDN and its Implementations from Japan
RFC 5539 Update Status draft-badra-netconf-rfc5539bis-00
IPWAVE Working Group of IETF, an updated status report
Routing Protocols and Concepts – Chapter 6
Requirements for IDN and its Implementations from Japan
Routing Protocols and Concepts – Chapter 6
Connecting the unconnected
John C Klensin APNIC Beijing, 25 August 2009
Common YANG Data Types draft-schoenw-netmod-rfc6991-bis-01
OSPF WG Status IETF 80, Prague CZ
draft-ietf-ospf-te-link-attr-reuse-04
Presentation transcript:

Alexey Melnikov <alexey.melnikov@isode.com> 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 <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

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?

Other relates tasks Update RFC 5280 to use IDNA2008 language?