Re: [Lwip] Constrained TCP draft
"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Thu, 20 July 2017 07:54 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 69E17126B72; Thu, 20 Jul 2017 00:54:46 -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 S41NsLfwlkqE; Thu, 20 Jul 2017 00:54:44 -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 EC9C0126557; Thu, 20 Jul 2017 00:54:43 -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 v6K7seJj022268; Thu, 20 Jul 2017 09:54:40 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id F13F91D53C1; Thu, 20 Jul 2017 09:54:39 +0200 (CEST)
Received: from 88.208.109.142 by webmail.entel.upc.edu with HTTP; Thu, 20 Jul 2017 09:54:30 +0200
Message-ID: <0308d71e6407091125c1a34f8fecdc26.squirrel@webmail.entel.upc.edu>
In-Reply-To: <26246e01-0c70-a39d-5654-28935ac4832a@isi.edu>
References: <CAO0Djp0H_UFNrV+=-EHdvPXbA=f5AxDwUPCciSoHR=pbaZhNoA@mail.gmail.com> <26246e01-0c70-a39d-5654-28935ac4832a@isi.edu>
Date: Thu, 20 Jul 2017 09:54:30 +0200
From: Carles Gomez Montenegro <carlesgo@entel.upc.edu>
To: Joe Touch <touch@isi.edu>
Cc: Rahul Jadhav <rahul.ietf@gmail.com>, lwip@ietf.org, draft-gomez-lwig-tcp-constrained-node-networks@ietf.org, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>
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: Delayed for 46:29:06 by milter-greylist-4.3.9 (violet.upc.es [147.83.2.51]); Thu, 20 Jul 2017 09:54:41 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/fZv3swpOLDbDvXNF_yGWsmt0OVE>
Subject: Re: [Lwip] Constrained TCP draft
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 20 Jul 2017 07:54:46 -0000
Hi Joe, Thanks a lot for your feedback. Please find below inline responses: > Hi, all, > > Scanning this doc, I had expected to see some "success criteria" up front. > > In particular, I was expecting that this approach was intended to be > some "minimal" variant of TCP, The very first version of the document had an (admittedly tentative) "intended status" of "Best Current Practice". However, after discussion and feedback from many folks, it was clarified that the best approach for this document would be "Informational", and its home would be the LWIG working group. So the main purpose of the document is to describe how TCP can be configured in a suitable way for constrained devices. The main purpose is not to define new mechanisms or a new TCP variant. If during the process we identify that any new mechanism has to be defined or a TCP specification requires some special modification for constrained devices, TCPM would probably be the best home for that. > subject to the following constraint: > This variant of TCP is intended to be compatible with current TCP, > albeit with lower performance. > > I.e. > > 1) a constrained TCP client would always be able to connect with a > compliant TCP server > > 2) a constrained TCP server would always be able to connect with a > compliant TCP cllient > > 3) #1 and #2 MAY result in reduced performance for that client-server > connection > > 4) #1 and #2 MUST NOT interfere with other client-server connections any > more than other compliant TCP connections (i.e., MUST be "TCP-friendly") > > Is there any analysis or summary of this in the current document? If > not, that's a good place to start, IMO. Currently there is not a summary/analysis of this in the document. In fact, as explained above, we don't intend to actually define a new TCP variant. Anyway, we may consider the possible impact of each of the TCP features/mechanisms analyzed in the document (section 4) on your four items above, and even we might analyze whether any of the existing TCP implementations for constrained devices (section 7) would not comply with any of the four items. > As is discussing this work in TCPM or at least TSVWG. Definitely. By the way, Michael Scharf has joined as an author of the draft. Once again, thanks for your comments. Cheers, Carles > Joe
- [Lwip] Constrained TCP draft Rahul Jadhav
- Re: [Lwip] Constrained TCP draft Carles Gomez Montenegro
- Re: [Lwip] Constrained TCP draft Joe Touch
- Re: [Lwip] Constrained TCP draft Carles Gomez Montenegro
- Re: [Lwip] Constrained TCP draft Joe Touch