[EAI] rfc5336bis-02 - scope questions

["Ernie Dainow" <[e-mail]>]

Comment 1.
In Section 3.2, the following statement is made:

   This document applies only when an UTF8SMTPbis-aware client is trying
   to send an internationalized message to a server which requires the
   UTF8SMTPbis extensions to handle it.

In Section 3.4, the following statement seems to be out of scope.

   An "internationalized message" as defined in the appendix of this
   specification MUST NOT be sent to an SMTP server that does not
   support UTF8SMTPbis. Such a message should be rejected by a server
   if it lacks the support of UTF8SMTPbis.

What is the context for the following? 

   When messages are rejected because the RCPT command requires an ASCII
   address,

Since our scope is only UTF8SMTPbis servers, when would the server ever
reject a non-ASCII address? 

If this whole section is meant to cover the following case, it needs to be
more fully explained that we are talking about the SMTP server in the
middle.

UTF8SMTPbis client --> UTF8SMTPbis server --> legacy SMTP server
              <------------------- reject

Comment 2.
In Section 3.6.4.2, the phrase "and some clients might crash" does not seem
to be appropriate in a standards document. It is unnecessary and should just
be removed.

   If the SMTP client does not support the UTF8SMTPbis extension, but
   receives a UTF-8 string in a reply, it may not be able to properly
   report the reply to the user, and some clients might crash.
   Internationalized messages in replies are only allowed in the
   commands under the situations described above.  Under any other
   circumstances, UTF-8 text MUST NOT appear in the reply.


-Ernie


 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5419 (20100902) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com