search

ietf-wg-emailcore / emailcore

3 stars 0 forks source link

G.7.3. Definition of domain name in Section 2.3.5 #9

Closed ietf-svn-bot closed 2 years ago

ietf-svn-bot commented 3 years ago

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

2.3.5. Domain Names

Only resolvable, fully-qualified domain names (FQDNs) are permitted when domain names are used in SMTP.

John Klensin: Does "in the public DNS" or equivalent need to be added to "resolvable"???

Alexey Melnikov: Does "resolvable" implies that a receiving MTA can or has to try to resolve them (e.g. in RCPT TO) when received, as opposed to resolving them when they need to be used (e.g. relaying to the next hop/ for delivery)

Issue migrated from trac:9 at 2022-01-31 12:33:51 +0000

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Alexey Melnikov wrote:

In regards to John's suggestion to add "in the public DNS", I think I disagree. There are split DNS configurations within enterprises where local FQDN domains are used and the corresponding information is stored in DNS, but this is not exposed to "public DNS". I don't think it is our place to prohibit such use.

I tempted to suggest to drop "resolvable" instead of John's suggestion. And possibly talk about "resolvable" aspects in the A/S document.

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

John Klensin wrote:

More generally, does this section need work to clarify the relationship to private domain names (discussed on SMTP list starting 2013-03-26)

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com changed title from Do FQDN used in SMTP need to be resolvable? to Resolvable FQDN in SMTP and private domain names

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

See also ticket #10

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com changed title from Resolvable FQDN in SMTP and private domain names to G.7.3. Resolvable FQDN in SMTP and private domain names

ietf-svn-bot commented 3 years ago

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

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Alexey: Proposal to drop the word "resolvable" from the quoted sentence in 2.3.5. Text in other sections is inambiguous when resolution needs to be done (e.g. when talking to the text hop), so saying "resolvable" in 2.3.5 doesn't help.

Ned Freed: +1

However no consensus on this so far, so further discussion is needed.

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Splitting the ticket into 2: definition of domain names and ticket #41 (Resolvable FQDN in SMTP and private domain names)

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com changed title from G.7.3. Resolvable FQDN in SMTP and private domain names to G.7.3. Definition of domain name in Section 2.3.5

ietf-svn-bot commented 3 years ago

@vesely@tana.it commented

Discussion: https://mailarchive.ietf.org/arch/msg/emailcore/8ekbkWRntZAXk1xt7GJ_IqlVnN8

ietf-svn-bot commented 3 years ago

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

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com set owner to alexey.melnikov@isode.com

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

There are slight complications because the same section explains what "resolvable" means.

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com commented

-08 removed "resolvable" and made some other changes based on the feedback from the December 2021 interim meeting.

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