search

ietf-wg-emailcore / emailcore

3 stars 0 forks source link

Meaning of "resolvable FQDN" in Section 2.3.5 #10

Closed ietf-svn-bot closed 2 years ago

ietf-svn-bot commented 3 years ago

keyword_SMTP owner:todd.herr@valimail.com resolution_fixed type_defect | by alexey.melnikov@isode.com

In 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

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com set component to smtp

ietf-svn-bot commented 3 years ago

@todd.herr@valimail.com changed status from new to assigned

ietf-svn-bot commented 3 years ago

@todd.herr@valimail.com set owner to todd.herr@valimail.com

ietf-svn-bot commented 3 years ago

@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.

ietf-svn-bot commented 3 years ago

@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.

ietf-svn-bot commented 3 years ago

@todd.herr@valimail.com commented

Change "In other words" to "In particular"

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com commented

Implemented in -06.

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com changed status from assigned to closed

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com set resolution to fixed