[Lwip] Martin Duke's No Objection on draft-ietf-lwig-tcp-constrained-node-networks-13: (with COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Fri, 30 October 2020 23:13 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: lwip@ietf.org
Delivered-To: lwip@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D37923A07BD; Fri, 30 Oct 2020 16:13:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-lwig-tcp-constrained-node-networks@ietf.org, lwig-chairs@ietf.org, lwip@ietf.org, Zhen Cao <zhencao.ietf@gmail.com>, zhencao.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <160409962484.7286.4325679774046861026@ietfa.amsl.com>
Date: Fri, 30 Oct 2020 16:13:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/a3JN-Ymgh4y0jWZODMUTAowD5P4>
Subject: [Lwip] Martin Duke's No Objection on draft-ietf-lwig-tcp-constrained-node-networks-13: (with COMMENT)
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Lightweight IP stack. Official mailing list for IETF LWIG Working Group." <lwip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lwip>, <mailto:lwip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lwip/>
List-Post: <mailto:lwip@ietf.org>
List-Help: <mailto:lwip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lwip>, <mailto:lwip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 23:13:46 -0000

Martin Duke has entered the following ballot position for
draft-ietf-lwig-tcp-constrained-node-networks-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-lwig-tcp-constrained-node-networks/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for addressing my DISCUSS.

Original comments, since resolved:

Please address the tsv review comments.

Sec 4.2.3
 s/Disabling Delayed ACKs at the
   sender allows an immediate ACK/Disabling Delayed ACKs at the
   request sender allows an immediate ACK

Sec 4.3.1
   When a multiple-segment window is used, the receiver will need to
   manage the reception of possible out-of-order received segments,
   requiring sufficient buffer space.

It's worth pointing out here that even a 1 MSS window should also manage
out-of-order arrival, as the sender may send multiple sub-MSS packets that fit
in the window. (On the other hand, the receiver is free to simply drop the
out-of-order segment, thus forcing a retransmission).

Sec 4.3.3.1
s/since with SACK recovery/since SACK recovery