Closed ietf-svn-bot closed 2 years ago
@alexey.melnikov@isode.com set component to smtp
@todd.herr@valimail.com changed status from new
to assigned
@todd.herr@valimail.com set owner to todd.herr@valimail.com
@todd.herr@valimail.com commented
I'm of the opinion that the two sentences following that argue for the "for example" meaning of "in other words":
Local nicknames or unqualified names MUST NOT be used. There are two exceptions to the rule requiring FQDNs:
If there's agreement on my interpretation, perhaps changing "In other words" to something like "More specifically", e.g.,
Only resolvable, fully-qualified domain names (FQDNs) are permitted when domain names are used in SMTP. More specifically, names that can be resolved to MX RRs or address (i.e., A or AAAA) RRs (as discussed in Section 5) are permitted, as are CNAME RRs whose targets can be resolved, in turn, to MX or address RRs.
@alexey.melnikov@isode.com commented
I think "More specifically" is still not clear enough for me. Is the list provided exhaustive or is it just showing examples? "More specifically" still sounds like the former to me, but I think the latter was intended.
Also, I don't think these are exceptions from using FQDN. There are no exceptions. MX and CNAME are giving examples of what means to be resolvable.
@todd.herr@valimail.com commented
Change "In other words" to "In particular"
@alexey.melnikov@isode.com commented
Implemented in -06.
@alexey.melnikov@isode.com changed status from assigned
to closed
@alexey.melnikov@isode.com set resolution to fixed
keyword_SMTP
owner:todd.herr@valimail.com
resolution_fixed
type_defect
| by alexey.melnikov@isode.comIn other words, names that can be resolved to MX RRs or address (i.e., A or AAAA) RRs (as discussed in Section 5) are permitted, as are CNAME RRs whose targets can be resolved, in turn, to MX or address RRs.
It is not clear whether "In other words" really meant "for example" or it is was intended that the only labels permitted are those that own records in one of the above RR types.
Issue migrated from trac:10 at 2022-01-31 12:33:57 +0000