Re: [TLS] WG call for adoption of draft-rescorla-tls-dtls-connection-id

yinxinxing <yinxinxing@huawei.com> Wed, 13 December 2017 03:34 UTC

Return-Path: <yinxinxing@huawei.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58A69126CBF for <tls@ietfa.amsl.com>; Tue, 12 Dec 2017 19:34:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 ZG6sFyWdGCIG for <tls@ietfa.amsl.com>; Tue, 12 Dec 2017 19:34:17 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3C361273E2 for <tls@ietf.org>; Tue, 12 Dec 2017 19:34:16 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 1D368CC635E83 for <tls@ietf.org>; Wed, 13 Dec 2017 03:34:13 +0000 (GMT)
Received: from DGGEML421-HUB.china.huawei.com (10.1.199.38) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 13 Dec 2017 03:34:13 +0000
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.21]) by dggeml421-hub.china.huawei.com ([10.1.199.38]) with mapi id 14.03.0361.001; Wed, 13 Dec 2017 11:34:10 +0800
From: yinxinxing <yinxinxing@huawei.com>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>, "tls@ietf.org" <tls@ietf.org>
Thread-Topic: [TLS] WG call for adoption of draft-rescorla-tls-dtls-connection-id
Thread-Index: AdNzwOHaJTYH9+dDQqSOJuwGJGCUXg==
Date: Wed, 13 Dec 2017 03:34:09 +0000
Message-ID: <DBDF9AE44733284D808F0E585E1919022D15D6E7@dggeml511-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.184.225.248]
Content-Type: multipart/alternative; boundary="_000_DBDF9AE44733284D808F0E585E1919022D15D6E7dggeml511mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/8SQrywyk5gjrg6QjryOjQI_tvRU>
Subject: Re: [TLS] WG call for adoption of draft-rescorla-tls-dtls-connection-id
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Dec 2017 03:34:19 -0000

I also agree adopting this WG draft. This feature will help a lot to solve the NAT rebinding problems in IOT fields. Happy to see that there was a strong WG consensus on adopting the draft in Singapore.

Yin Xinxing

发件人: TLS [mailto:tls-bounces@ietf.org] 代表 Tobias Gondrom
发送时间: 2017年12月13日 11:06
收件人: tls@ietf.org
主题: Re: [TLS] WG call for adoption of draft-rescorla-tls-dtls-connection-id


Hello dear TLS WG and chairs,

From my side a strong support for the adoption of this WG draft.

There are many scenarios, especially in IoT where this draft is essential to maintain the right security association. If we can achieve this, we can dramatically reduce the number of new handshakes and roundtrips in low-power scenarios and thus dramatically reduce power consumption. In battery powered IoT scenarios this can help and dramatically increase the lifetime of a device… (potentially up to a factor of 2-3 longer lifetimes).

Therefore this feature is very important for the success of DTLS in IoT.

Thank you and hope we can progress this extension as soon as possible,

Tobias





> Should have included a date: 13 December 2017.

> On Nov 28, 2017, at 15:17, Sean Turner <sean@sn3rd.com><mailto:sean@sn3rd.com&gt>; wrote:

>

> All,

>

> In Singapore @ IETF100, there was strong WG consensus to adopt draft-rescorla-tls-dtls-connection-id, but we need to confirm this on the list.  Please let us know by X December 2017 whether you oppose adopting this draft and why.

>

> Your chairs: J&S



References:

  *   [TLS] WG call for adoption of draft-rescorla-tls-dtls-connection-id<https://mailarchive.ietf.org/arch/msg/tls/HyYluQWNy097nuwliE4QEinEnso>
Sean Turner <sean@sn3rd.com<mailto:sean@sn3rd.com>>