[Last-Call] Opsdir last call review of draft-freed-smtp-limits-06
Linda Dunbar via Datatracker <noreply@ietf.org> Tue, 26 September 2023 22:36 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: last-call@ietf.org
Delivered-To: last-call@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DA60AC137385; Tue, 26 Sep 2023 15:36:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-freed-smtp-limits.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 11.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <169576780686.45174.6422080959425764343@ietfa.amsl.com>
Reply-To: Linda Dunbar <linda.dunbar@futurewei.com>
Date: Tue, 26 Sep 2023 15:36:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/9hgFlUi00hdmQ7qCXHHSKOsh0zA>
Subject: [Last-Call] Opsdir last call review of draft-freed-smtp-limits-06
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Sep 2023 22:36:46 -0000
Reviewer: Linda Dunbar Review result: Has Nits 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
- [Last-Call] Opsdir last call review of draft-free… Linda Dunbar via Datatracker
- Re: [Last-Call] Opsdir last call review of draft-… John C Klensin