[Lwip] [Fwd: I-D Action: draft-ietf-lwig-tcp-constrained-node-networks-03.txt]

"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Sun, 10 June 2018 09:19 UTC

Return-Path: <carlesgo@entel.upc.edu>
X-Original-To: lwip@ietfa.amsl.com
Delivered-To: lwip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD20E130E23 for <lwip@ietfa.amsl.com>; Sun, 10 Jun 2018 02:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o59I0EGyccbC for <lwip@ietfa.amsl.com>; Sun, 10 Jun 2018 02:19:15 -0700 (PDT)
Received: from violet.upc.es (violet.upc.es [147.83.2.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12842130E24 for <lwip@ietf.org>; Sun, 10 Jun 2018 02:19:13 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by violet.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w5A9IcxR032229; Sun, 10 Jun 2018 11:18:38 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id 219AD1D53C1; Sun, 10 Jun 2018 11:18:38 +0200 (CEST)
Received: from 83.37.3.130 by webmail.entel.upc.edu with HTTP; Sun, 10 Jun 2018 11:18:38 +0200
Message-ID: <24a42252af5bb9ae009b54d2d66d3032.squirrel@webmail.entel.upc.edu>
Date: Sun, 10 Jun 2018 11:18:38 +0200
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: lwip@ietf.org
Cc: michael.scharf@nokia.com, jon.crowcroft@cl.cam.ac.uk
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.99.2 at violet
X-Virus-Status: Clean
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.3.9 (violet.upc.es [147.83.2.51]); Sun, 10 Jun 2018 11:18:38 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/9ZmAd4QKPW0V6BX6N07jL-Rgqds>
Subject: [Lwip] [Fwd: I-D Action: draft-ietf-lwig-tcp-constrained-node-networks-03.txt]
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Lightweight IP stack <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: Sun, 10 Jun 2018 09:19:18 -0000

Dear LWIG WG,

As you can see below, we have updated the LWIG TCP draft. Comments are
welcome!

On the other hand, while we believe the document is starting to be quite
complete, we would like to take the opportunity to ask you a few
questions:

1.- With regard to the constrained TCP implementations survey in the
Annex, please let us know if you would object against presence in the
Annex of any of the currently covered implementations, or if you think
others may need to be included.

2.- So far, we have not been able to find or receive much content for the
“Data size” row in the summary table. A nice exception to this is RAM
usage measurement results on the RIOT TCP implementation, that have been
kindly provided by Simon Brummer. However, as getting similar information
for the rest of implementations appears to be difficult, our proposal
would be removing this row from the table (as shown in the current draft
version), while keeping the "Code size" row in. RAM usage details for the
RIOT TCP implementation have been included anyway as a table footnote.
Would anyone object to this approach?

3.- If you are aware of specific code vulnerabilities that may arise when
implementing TCP for constrained devices, please let us know.

Thanks,

Carles, Jon, Michael


---------------------------- Original Message ----------------------------
Subject: [Lwip] I-D Action:
draft-ietf-lwig-tcp-constrained-node-networks-03.txt
From:    internet-drafts@ietf.org
Date:    Sun, June 10, 2018 10:36 am
To:      i-d-announce@ietf.org
Cc:      lwip@ietf.org
--------------------------------------------------------------------------


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Light-Weight Implementation Guidance WG
of the IETF.

        Title           : TCP Usage Guidance in the Internet of Things (IoT)
        Authors         : Carles Gomez
                          Jon Crowcroft
                          Michael Scharf
	Filename        : draft-ietf-lwig-tcp-constrained-node-networks-03.txt
	Pages           : 24
	Date            : 2018-06-10

Abstract:
   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).
   Such environments require a lightweight TCP implementation and may
   not make use of optional functionality.  This document explains a
   number of known and deployed techniques to simplify a TCP stack as
   well as corresponding tradeoffs.  The objective is to help embedded
   developers with decisions on which TCP features to use.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lwig-tcp-constrained-node-networks/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-lwig-tcp-constrained-node-networks-03
https://datatracker.ietf.org/doc/html/draft-ietf-lwig-tcp-constrained-node-networks-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lwig-tcp-constrained-node-networks-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
Lwip mailing list
Lwip@ietf.org
https://www.ietf.org/mailman/listinfo/lwip