Re: [EAI] I-D Action: draft-ietf-eai-rfc5336bis-12.txt

+1

/d

--
Dave Crocker
bbiw.net

via mobile

_____________________________________________
From: Alexey Melnikov <alexey.melnikov@isode.com>
Sent: Sat Aug 20 10:35:56 PDT 2011
To: Chris Newman <chris.newman@oracle.com>
Cc: ima@ietf.org, Jiankang Yao <healthyao@gmail.com>
Subject: Re: [EAI] I-D Action: draft-ietf-eai-rfc5336bis-12.txt

Chris Newman wrote:

> --On August 18, 2011 14:43:37 +0800 Jiankang Yao <healthyao@gmail.com> 
> wrote:
>
>> ----- Original Message -----
>> From: "Chris Newman" <chris.newman@oracle.com>
>> To: <ima@ietf.org>
>> Sent: Thursday, August 18, 2011 6:04 AM
>> Subject: Re: [EAI] I-D Action: draft-ietf-eai-rfc5336bis-12.txt
>
> ...
>
>>> except the ABNF does not
>>> allow UTF-8 in ESMTP parameter values. So we need:
>>>
>>> esmtp-value =/ UTF8-non-ascii
>>>
>>> added to the ABNF.
>>
>> If your proposed esmtp-value syntax extension in rfc5336bis is used for
>> ORCPT in DSN, then RFC5336bis has already said "
>> If a UTF8SMTPbis-aware SMTP server advertises the Delivery Status
>> Notification (DSN) [RFC3461] extension, it MUST implement
>> [RFC5337bis].
>> "
>>
>> Does it satisfy your expectation?
>
> That creates a contradiction. RFC 5337bis discusses using UTF-8 in the 
> ORCPT parameter value, but 5336bis ABNF presently disallows use of 
> UTF-8 in ESMTP parameter values. We can make the specifications 
> consistent by allowing UTF-8 in ESMTP parameter values.

Good point. I support your proposal.

_____________________________________________

IMA mailing list
IMA@ietf.org
https://www.ietf.org/mailman/listinfo/ima