Re: [core] Call for adoption of draft-tschofenig-core-coap-tcp-tls

Simon Lemay <simon.lemay@gmail.com> Tue, 10 November 2015 16:59 UTC

Return-Path: <simon.lemay@gmail.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 080D61B3ABB for <core@ietfa.amsl.com>; Tue, 10 Nov 2015 08:59:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 dg1nWyq2yrUz for <core@ietfa.amsl.com>; Tue, 10 Nov 2015 08:59:23 -0800 (PST)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 5CDA91B3AB6 for <core@ietf.org>; Tue, 10 Nov 2015 08:59:23 -0800 (PST)
Received: by oige206 with SMTP id e206so1597826oig.2 for <core@ietf.org>; Tue, 10 Nov 2015 08:59:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=+I5QvW3LiKi6x0bwbLBI58G/iPK9ICBnVTqpCZTjTP0=; b=b4ObZ5X8QIxcbrt4CLKBWsfheNkTUinmmn16EilwNQt2IJjgBG8vaa8YtgUqyy//h9 WPNiugkOVSeWElcOXvrHcSqmCw2bgUvL19+b9FaChtMK5KeeCQhhrp4Ip2AJdssu/+gr /Fzn222YpB3BrvOvTN6U70U3Bni2TnBsmatJt36T0MUDR5eDozXCtHaOk+FMpBB4ZqJ9 x4b/hqlKuZsCP3HJT+u1urw0D18AsSOpMcVSs+24n+qXI3euwsV8RWlsRc3eJ729wu9b oqnD+dbjKRdLMywYiBgHzyAr2Yy0QKE11f0IH2RSomzkkWPCRTf8a1QKtNe9k8RIAA2Q Zvcg==
X-Received: by 10.202.184.130 with SMTP id i124mr1925502oif.122.1447174762590; Tue, 10 Nov 2015 08:59:22 -0800 (PST)
MIME-Version: 1.0
References: <CAPRuP3nArCc8av5PFn_XbgpPoUcgqmEH5Fq48TN6=xmzAFKgbA@mail.gmail.com> <BLUPR0301MB2081530D03081E81839311A5D3170@BLUPR0301MB2081.namprd03.prod.outlook.com> <CAN9CcB9rbFoF5bDRbNs=KL45FftK+KHwbXokwWP50rLSjG_Ugg@mail.gmail.com> <1A4BDE47622E4F98B4D1F378B4FDAC5A@WeiGengyuPC>
In-Reply-To: <1A4BDE47622E4F98B4D1F378B4FDAC5A@WeiGengyuPC>
From: Simon Lemay <simon.lemay@gmail.com>
Date: Tue, 10 Nov 2015 16:59:12 +0000
Message-ID: <CALfOQQ6G3kZhZNptuMbtZ22VDaUci+w0kHPHzQ_S3cOQ19oTkQ@mail.gmail.com>
To: weigengyu <weigengyu@bupt.edu.cn>, Core <core@ietf.org>
Content-Type: multipart/alternative; boundary="001a113ce0f2a6f92f052432a17f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/f7tK5JihVB1wjaBksQfdXXJ02PA>
Subject: Re: [core] Call for adoption of draft-tschofenig-core-coap-tcp-tls
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2015 16:59:27 -0000

+1 for adoption
On Mon, Nov 9, 2015 at 05:34 weigengyu <weigengyu@bupt.edu.cn> wrote:

> Hi all,
>
> +1.  It is important.
>
> And one question.
> Does it need to give more specifications about the UDP-to-TCP and
> TCP-to-UDP gateways?
>
> Regards,
>
> Gengyu WEI
> Network Technology Center
> School of Computer
> Beijing University of Posts and Telecommunications
>
> *From:* Julien Vermillard <jvermillard@gmail.com>
> *Sent:* Sunday, November 08, 2015 3:14 PM
> *To:* Core <core@ietf.org>
> *Subject:* Re: [core] Call for adoption of
> draft-tschofenig-core-coap-tcp-tls
>
>
> +1
>
> We suffer the same issues between our servers and our cellular modems.
> On some network we need to go down to 20 seconds.
>
> Julien
>
> Le sam. 7 nov. 2015 22:17, Juan Perez <juanpere@microsoft.com> a écrit :
>
>> +1
>>
>>
>>
>> It is important for us (at Microsoft Azure IoT) that this document gets
>> adopted.  Additionally, as part of the OMA LWM2M group, it’s important that
>> CoAP supports TCP/TLS as a standard to enable internet/cloud scenarios.
>>
>>
>>
>> We’ve run tests between worldwide Azure and non-Azure data centers and
>> have found that a UDP keep-alive is required no more than every 30 seconds
>> in order to maintain reachability between clients and servers.
>>
>>
>>
>> Thanks,
>>
>> Juan
>>
>>
>>
>> *From:* Andrew Mcgregor [mailto:andrewmcgr@google.com]
>> *Sent:* Monday, November 2, 2015 8:38 PM
>> *To:* Core <core@ietf.org>
>> *Subject:* [core] Call for adoption of draft-tschofenig-core-coap-tcp-tls
>>
>>
>>
>> The sense of the room at IETF 94 was that we should adopt this as a
>> working group document.
>>
>>
>>
>> This is the corresponding mailing list call, open until November 16.
>>
>>
>>
>>         Title           : A TCP and TLS Transport for the Constrained
>> Application Protocol (CoAP)
>>         Authors         : Carsten Bormann
>>                           Simon Lemay
>>                           Valik Solorzano Barboza
>>                           Hannes Tschofenig
>>         Filename        : draft-tschofenig-core-coap-tcp-tls-05.txt
>>         Pages           : 12
>>         Date            : 2015-11-02
>>
>> Abstract:
>>    The Hypertext Transfer Protocol (HTTP) was designed with TCP as the
>>    underlying transport protocol.  The Constrained Application Protocol
>>    (CoAP), while inspired by HTTP, has been defined to make use of UDP
>>    instead of TCP.  Therefore, reliable delivery and a simple congestion
>>    control and flow control mechanism are provided by the message layer
>>    of the CoAP protocol.
>>
>>    A number of environments benefit from the use of CoAP directly over a
>>    reliable byte stream such as TCP, which already provides these
>>    services.  This document defines the use of CoAP over TCP as well as
>>    CoAP over TLS.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-tschofenig-core-coap-tcp-tls/
>>
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-tschofenig-core-coap-tcp-tls-05
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-tschofenig-core-coap-tcp-tls-05
>>
>>
>>
>> --
>>
>> Andrew McGregor | SRE | andrewmcgr@google.com | +61 4 1071 2221
>> _______________________________________________
>> core mailing list
>> core@ietf.org
>> https://www.ietf.org/mailman/listinfo/core
>>
> ------------------------------
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>