Re: [EAI] I-D Action: draft-ietf-eai-mailinglistbis-00.txt

["John R. Levine" <[e-mail]>]

>> Bug in xml2rfc.  They know about it.
>
> Yes, I saw your messages on the xml2rfc list, but as user of
> the online xml2rfc tools I can't tell how to fix your offline
> installation.  For the online tool if I don't like the bibxml
> output I just copy the bibxml snippet and then tweak it until
> I'm satisfied. ;-)

It's an internal reference to another section.  If they don't fix xml2rfc 
before this goes to the RFC Ed, I can do the xref by hand.

>> VERP is per-recipient bounce addresses that embed the recipient's
>> address.  For this doc, I don't see any need to describe it in
>> more detail.
>
> Mostly I have forgotten all VERP and BATV details, but there are
> "local part length" dragons, IIRC. ...

So what?  For this document, all that matters is that it embeds the 
recipient's address, which will include UTF-8 characters if it's an EAI 
address.

>> But this isn't about legacy list tools.  It's about how list
>> tools might change to handle EAI mail.
>
> Where does using a percent-encoded instead of a punycoded <ihost>
> help wrt mailing lists?  So far I think you can either keep UTF-8
> "as is" or "get it right" (= 3987 + 5890).

I still prefer to let other people weigh in on this.

Regards,
John Levine, [e-mail], Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly