Re: RFC 4408 Errata - PermError on invalid domains after macro expansion

On 10/25/2011 06:50 AM, Frank Ellermann wrote:
> Sigh, at least I tried it.  It puts a burden on you
> to allow only "sound" local parts working with all
> (or most) 4408 implementations.  And it will be very
> interesting when you permit any "sound" UTF8SMTPBIS
> local parts -- the IETF "EAI" RFCs are in Last Call.
>
> So far I'm not aware of any SPF EAI implementations.
The "troublesome" localpart macro at worst causes PermError.  For 
v=spf3, I think (perhaps wrongly) that domain-spec should be UTF-8.  
Failing that, we could add an option for the localpart macro to expand 
non-ascii localparts as punycode.  And exp= records should be 
internationalizable, perhaps by assuming UTF-8 (of which US-ASCII, the 
current 4408 requirement, is a subset).