Subject: [art] Question regarding RFC 8098

From: Peter Occil <[email-masked]>
Date: Wed, 18 Jul 2018 12:58:34 -0400

RFC 8098’s definition of the Original-Recipient and Final-Recipient header fields appears not to take into account the utf-8-type-addr token defined in RFC 6533.  There seems to be a conflict between them since RFC 8098 now allows comments (and folding white space) to appear after the address in those header fields, and since utf-8-type-addr appears to technically allow parentheses (comment delimiters) to appear in address.  As a result, the following examples are ambiguous:

Original-Recipient: utf-8; paren([email-masked])

Original-Recipient: utf-8; [email-masked](.com)

In addition, the following examples may or may not be parse errors:

Original-Recipient: utf-8; paren(address)[email-masked]

Original-Recipient: utf-8; parenaddress)[email-masked]

Original-Recipient: utf-8; paren([email-masked]

How this conflict and/or ambiguity is to be resolve should be discussed further.

--Peter