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

"Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com> Mon, 11 June 2018 05:59 UTC

Return-Path: <michael.scharf@nokia.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3A0B130EE6 for <tcpm@ietfa.amsl.com>; Sun, 10 Jun 2018 22:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 TYWQur0wiRw9 for <tcpm@ietfa.amsl.com>; Sun, 10 Jun 2018 22:59:55 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0122.outbound.protection.outlook.com [104.47.2.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B56F130E0C for <tcpm@ietf.org>; Sun, 10 Jun 2018 22:59:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=A0vyJBQbNjnHr43kr6PknDS1A9fGSOAXOs9r+PZaav8=; b=Z+OU/WPDr3lgQnN6h7eSKt7lv7KrCzPFMkCbiC7EQehXLcmzv160m7TKXn7U7MEo7GZuJpvEsU5btqA37rXiEf6PmM+ilUjuZ6vC0wyNTMBU4OWCDXsojAMj3IwazprCwiISUppSNwo60oy69u3vjbgZaZe9iTciXlNNdvx0DcY=
Received: from AM5PR0701MB2547.eurprd07.prod.outlook.com (10.173.92.15) by AM5PR0701MB1858.eurprd07.prod.outlook.com (10.167.216.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.863.6; Mon, 11 Jun 2018 05:59:52 +0000
Received: from AM5PR0701MB2547.eurprd07.prod.outlook.com ([fe80::48b9:5449:401e:6d55]) by AM5PR0701MB2547.eurprd07.prod.outlook.com ([fe80::48b9:5449:401e:6d55%9]) with mapi id 15.20.0863.010; Mon, 11 Jun 2018 05:59:52 +0000
From: "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>
To: "tcpm@ietf.org" <tcpm@ietf.org>
CC: Carles Gomez Montenegro <carlesgo@entel.upc.edu>, "jon.crowcroft@cl.cam.ac.uk" <jon.crowcroft@cl.cam.ac.uk>
Thread-Topic: [Fwd: [Lwip] I-D Action: draft-ietf-lwig-tcp-constrained-node-networks-03.txt]
Thread-Index: AQHUAJwbKopQIpl5+kmhGvch9WQLMKRakK6w
Date: Mon, 11 Jun 2018 05:59:52 +0000
Message-ID: <AM5PR0701MB2547E71541E7205C297D6BA593780@AM5PR0701MB2547.eurprd07.prod.outlook.com>
References: <24a42252af5bb9ae009b54d2d66d3032.squirrel@webmail.entel.upc.edu>
In-Reply-To: <24a42252af5bb9ae009b54d2d66d3032.squirrel@webmail.entel.upc.edu>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=michael.scharf@nokia.com;
x-originating-ip: [92.203.189.113]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB1858; 7:kv0XHZKsS/ztmoUh+FGSEgEtPK6G2TJU8GmMJg4ggCmEjtMghC0IJT9UOs8bVoSIqMz7eP+0AL7h9AHkUfayRS4iQKsDVlt0j37rXiSr2QinLJhIOyMzQrT/P/K4wN2bBgXbHmLs5xUdeWq84Sv7dkpJNkDjSDb/TmkH6ol6vz7qViN1R+QqwxFwAIkGj/p3C7RJTDRD0Mnv6yKcRqetXlUJKvpOKMw8TOIPyVbm5z2/3HDR3mLbguYnJTaJAK+R
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:(109105607167333); BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(48565401081)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603328)(7193020); SRVR:AM5PR0701MB1858;
x-ms-traffictypediagnostic: AM5PR0701MB1858:
x-microsoft-antispam-prvs: <AM5PR0701MB1858265A1124BB5A307EBB0093780@AM5PR0701MB1858.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(82608151540597)(109105607167333);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3002001)(3231254)(11241501184)(806099)(944501410)(52105095)(93006095)(93001095)(10201501046)(6055026)(149027)(150027)(6041310)(20161123564045)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:AM5PR0701MB1858; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB1858;
x-forefront-prvs: 070092A9D3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39380400002)(376002)(346002)(396003)(39860400002)(13464003)(199004)(189003)(25786009)(97736004)(2900100001)(478600001)(2351001)(14454004)(316002)(102836004)(6506007)(53546011)(86362001)(7696005)(76176011)(186003)(26005)(966005)(81156014)(476003)(486006)(11346002)(74316002)(446003)(105586002)(106356001)(7736002)(81166006)(33656002)(5250100002)(1730700003)(2501003)(305945005)(561944003)(6116002)(3846002)(5640700003)(3660700001)(9686003)(54906003)(6306002)(8676002)(6436002)(6916009)(99286004)(2473003)(4326008)(55016002)(53936002)(8936002)(68736007)(5660300001)(3280700002)(229853002)(66066001)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:AM5PR0701MB1858; H:AM5PR0701MB2547.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: LnGDVAhZGmMy9IQZjZ2HO1qpnFyYo0oqhExhH2bM4pMeB1cuRjvi9WPLtceh/f58ul6wNwRVuFViSpcDyIfjSKg1XHt0iPLpp2pIsyCE2abDM7IkAk1H4nyA4ZDKdto1Cst1j10mkJV0+qYHCduTDihYSn7i3KoOWjBDGyM+XeU2cIkda2hLIf8WS+zZYWZ9B8g6DLUdW5vttb3aqY0YGVNHLL79MSA4UkmNZDqm77q9xpkGPk2lKpvlUK+AyjbB
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 01862411-c0d9-4610-d85b-08d5cf608cbc
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 01862411-c0d9-4610-d85b-08d5cf608cbc
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jun 2018 05:59:52.7259 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB1858
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/fyqehX3wyVsoN-Syp5swIeV5n30>
Subject: [tcpm] FW: [Fwd: [Lwip] I-D Action: draft-ietf-lwig-tcp-constrained-node-networks-03.txt]
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jun 2018 05:59:59 -0000

To keep the TCPM community in the loop.

The authors really look for feedback (preferably on the LWIG list).

Michael

-----Original Message-----
From: Carles Gomez Montenegro [mailto:carlesgo@entel.upc.edu] 
Sent: Sunday, June 10, 2018 11:19 AM
To: lwip@ietf.org
Cc: Scharf, Michael (Nokia - DE/Stuttgart) <michael.scharf@nokia.com>; jon.crowcroft@cl.cam.ac.uk
Subject: [Fwd: [Lwip] I-D Action: draft-ietf-lwig-tcp-constrained-node-networks-03.txt]

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