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

"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Sun, 10 March 2019 07:56 UTC

Return-Path: <carlesgo@entel.upc.edu>
X-Original-To: lwip@ietfa.amsl.com
Delivered-To: lwip@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 2729012787E; Sat, 9 Mar 2019 23:56:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id lrOCpyWr-gTB; Sat, 9 Mar 2019 23:56:20 -0800 (PST)
Received: from dash.upc.es (dash.upc.es []) (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 9F2F0126DFA; Sat, 9 Mar 2019 23:56:19 -0800 (PST)
Received: from entelserver.upc.edu (entelserver.upc.es []) by dash.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id x2A7uA7k052331; Sun, 10 Mar 2019 08:56:10 +0100
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu []) by entelserver.upc.edu (Postfix) with ESMTP id 2680B1D53C1; Sun, 10 Mar 2019 08:56:10 +0100 (CET)
Received: from by webmail.entel.upc.edu with HTTP; Sun, 10 Mar 2019 08:56:10 +0100
Message-ID: <d214f6f937a1b9192310e615e3880a3f.squirrel@webmail.entel.upc.edu>
Date: Sun, 10 Mar 2019 08:56:10 +0100
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: lwip@ietf.org, tcpm@ietf.org
Cc: michael.scharf@hs-esslingen.de, 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.100.2 at dash
X-Virus-Status: Clean
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.3.9 (dash.upc.es []); Sun, 10 Mar 2019 08:56:10 +0100 (CET)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/hyZibu6PcJc5QGLdxbrnK3BkeD4>
Subject: [Lwip] [Fwd: I-D Action: draft-ietf-lwig-tcp-constrained-node-networks-05.txt]
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Sun, 10 Mar 2019 07:56:23 -0000

Dear LWIP and TCPM WGs,

First of all, thanks to everyone who provided feedback on revision -04 of
our "TCP Usage Guidance in the Internet of Things (IoT)" draft.

Please find below the pointers to an update of the draft (revision -05),
based on the comments received.

Main changes:

o  Addressed comments by Yoshifumi Nishida
o  Removed mentioning MD5 as an example (comment by David Black)
o  Added memory footprint details of TCP implementations (Contiki-NG
   and lwIP 2.1.2) provided by Rahul Jadhav in the Annex [1]
o  Addressed comments by Ilpo Jarvinen throughout the whole document
o  Improved the RIOT section in the Annex, based on feedback from
   Emmanuel Baccelli

[1] Rahul kindly performed memory footprint measurements for the sake of
this draft (feel free to visit https://github.com/nyrahul/sizeof)

The authors believe that the document is now ready for WGLC.


Carles (on behalf of all authors)

---------------------------- Original Message ----------------------------
Subject: [Lwip] I-D Action:
From:    internet-drafts@ietf.org
Date:    Sun, March 10, 2019 8:39 am
To:      i-d-announce@ietf.org
Cc:      lwip@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts
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-05.txt
	Pages           : 26
	Date            : 2019-03-09

   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:

There are also htmlized versions available at:

A diff from the previous version is available at:

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:

Lwip mailing list