On Mon, 27 Apr 2009, Karsten Bräckelmann wrote:
> On Mon, 2009-04-27 at 16:10 -0400, Adam Katz wrote:
> > Since email addresses contain everything a valid domain can contain,
> > the user.AT.domain.tld (which is really user.at.domain.tld since
> > domains are not case-sensitive) could be ambiguous if the "user" or
> > the "domain" contains ".at." in itself, or whatever workaround we
> > create. My proposed workaround is ".real-at." and an incremented
> > numeric suffix like ".real-at2." if needed.
>
> You are aware there's a ccTLD .at? :)
>
>
> > (Oh crap, is this a draft for an RFC?)
>
> This pretty much was one of my first thoughts, too. I vaguely recall
> coming across such an RFC before. Hope someone else can point it out.
>
There is RFC-1035 (section 8) encoding of e-mail addresses for DNS
usage (EG the SOA record or RP record) which could be used here.
Slight potential for confusion but at least a starting point.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
