[Iot-directorate] Iotdir telechat review of draft-ietf-lwig-tcp-constrained-node-networks-11

Ines Robles via Datatracker <noreply@ietf.org> Tue, 20 October 2020 21:42 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: iot-directorate@ietf.org
Delivered-To: iot-directorate@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 29CC53A13E3; Tue, 20 Oct 2020 14:42:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ines Robles via Datatracker <noreply@ietf.org>
To: iot-directorate@ietf.org
Cc: last-call@ietf.org, lwip@ietf.org, draft-ietf-lwig-tcp-constrained-node-networks.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160323012613.8140.7223450449778019726@ietfa.amsl.com>
Reply-To: Ines Robles <mariainesrobles@googlemail.com>
Date: Tue, 20 Oct 2020 14:42:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-directorate/vKP5b_jsrfi2ndZxHYZGNvD6w6I>
Subject: [Iot-directorate] Iotdir telechat review of draft-ietf-lwig-tcp-constrained-node-networks-11
X-BeenThere: iot-directorate@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mailing list for the IoT Directorate Members <iot-directorate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-directorate/>
List-Post: <mailto:iot-directorate@ietf.org>
List-Help: <mailto:iot-directorate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2020 21:42:06 -0000

Reviewer: Ines Robles
Review result: Ready

Document: draft-ietf-lwig-tcp-constrained-node-networks-11
Reviewer: Ines Robles
Review Date: 2020-10-20

Summary:

This document provides guidance on how to implement and use the Transmission
Control Protocol (TCP) in Constrained-Node Networks  (CNNs), which are a
characterstic of the Internet of Things (IoT).

The document is clear to understand.

Major Issues: None

Minor Issues: None.

Nits:
1- Should section 2 "Conventions used in this document" be removed? I have not
found Normative language into the document 2- Questions: Following my
understanding, the transport features provided by TCP [RFC 8095 - Section
3.1.3] are covered in this document, right? or there some of the mentioned
features that does not apply to CNN?

Thank you for this document,

Ines