search

ietf-wg-emailcore / emailcore

3 stars 0 forks source link

G.7.13. Possible SEND, SAML, SOML Loose End #20

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_task | by alexey.melnikov@isode.com

For example:

4.1.4. Order of Commands

The MAIL command (or the obsolete SEND, SOML, or SAML commands)

Is there any reason to not clean those commands out of this entirely, replacing them with, e.g., a strong reference to Appendix F.6.

Issue migrated from trac:20 at 2022-01-31 12:35:00 +0000

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 changed title from Cleanup of text about obsolete SEND, SAML and SOML commands to G.7.13. Possible SEND, SAML, SOML Loose End

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Suggested "no further changes and close the ticket" on the mailing list.

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Ned Freed wrote:

Clients SHOULD NOT provide SEND, SAML, or SOML as services. Servers
MAY implement them.  If they are implemented by servers, the
implementation model specified in RFC 821 MUST be used and the
command names MUST be published in the response to the EHLO command.

This last paragraph omits the possibility of them being implemented but not enabled. I also don't see any point to saying that servers MAY implement them. How about:

Clients SHOULD NOT provide SEND, SAML, or SOML as services. If
a server implements them, the implementation model specified in RFC 821
MUST be used and the names of any commands that are enabled MUST be
published in the response to the EHLO command.
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

Final suggestion as per IETF 111 session:

Clients SHOULD NOT use SEND, SAML, or SOML commands. If a server implements them, the implementation model specified in RFC 821 MUST be used and the names of any commands that are enabled MUST be published in the response to the EHLO command.

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com commented

Fully resolved in draft-ietf-emailcore-rfc5321bis-05.

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