Skip to main content

Last Call Review of draft-freed-smtp-limits-06
review-freed-smtp-limits-06-opsdir-lc-dunbar-2023-09-26-00

Request Review of draft-freed-smtp-limits
Requested revision No specific revision (document currently at 07)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2023-10-04
Requested 2023-09-06
Authors Ned Freed , Dr. John C. Klensin
I-D last updated 2023-09-26
Completed reviews Dnsdir Last Call review of -06 by Johan Stenstam (diff)
Opsdir Last Call review of -06 by Linda Dunbar (diff)
Genart Last Call review of -06 by Paul Kyzivat (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request Last Call review on draft-freed-smtp-limits by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/Fu5EZojX6XoXRNP3O35trMQfdpA
Reviewed revision 06 (document currently at 07)
Result Has nits
Completed 2023-09-26
review-freed-smtp-limits-06-opsdir-lc-dunbar-2023-09-26-00
I have reviewed this document as part of the Ops area directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Ops area directors.
Document editors and WG chairs should treat these comments just like any other
last-call comments.

Summary:
This document defines a "Limits" extension for the Simple Mail Transfer
Protocol (SMTP).

The document specifies several limits to be registered with IANA. However, I
don't see the Limit value being specified. Does it mean that the document
simply proposes a new KEYWORD (LIMITS)?

I am not an expert at SMTP, I have some questions:
- The security consideration says that "a malicious server can use limits to
overly constrain clients". Q1: how to prevent clients access malicious server?
Q2: how does setting the KEYWORD LIMIT can help this problem

- Introduction section 6th paragraph says "makes it possible for clients to
avoid server errors and the problems they cause. Q: How can setting the LIMITE
helps Client avoid Server Errors?

Thank you,
Linda Dunbar