About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section

Re: [enum-wg] ENUM-capable email client?

  • To: John C Klensin <
    >
  • From: Florian Weimer <
    >
  • Date: Mon, 17 Oct 2005 19:23:09 +0200
  • Cc: Carsten Schiefner <
    >,

* John C. Klensin:

> permitting, e.g., 
>    +12345678901234
> 
> as an email address would require changing of every MTA in the
> network before ENUM->email would work reliably.  Such agreement
> is unlikely.  For example, +12345678901234@localhost could be
> a valid email address today, having nothing to do with ENUM.

You would use +12345678901234@localhost, I guess, where the @e164.arpa
part could be supplied by the MUA.  (Of course, e164.arpa should have
a "MX ." RR.)

If you opt for a purely MUA-based approach, you can never-ever put
E.164 addresses in the message header.  ENUM email addresses would
remain second-class citizens, just like internationalized domain names
implemented with IDNA.




 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community