IETF Logo Mail Archive

Re: [Dtls-iot] RFC 7539 (ChaCha20 and Poly1305) a SHOULD/MUST implement?

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Thu, 06 August 2015 10:00 UTC

Return-Path: <Hannes.Tschofenig@gmx.net>
X-Original-To: dtls-iot@ietfa.amsl.com
Delivered-To: dtls-iot@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E23FA1B2BDB for <dtls-iot@ietfa.amsl.com>; Thu, 6 Aug 2015 03:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.186
X-Spam-Level:
X-Spam-Status: No, score=-1.186 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 lGOH9JjTPv03 for <dtls-iot@ietfa.amsl.com>; Thu, 6 Aug 2015 03:00:33 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6ABC21B2BD3 for <dtls-iot@ietf.org>; Thu, 6 Aug 2015 03:00:33 -0700 (PDT)
Received: from [217.140.96.140] by 3capp-gmx-bs27.server.lan (via HTTP); Thu, 6 Aug 2015 12:00:26 +0200
MIME-Version: 1.0
Message-ID: <trinity-2aa15f2d-a0c6-4213-bd91-10a6d5ca06e0-1438855226547@3capp-gmx-bs27>
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/html; charset="UTF-8"
Date: Thu, 06 Aug 2015 12:00:26 +0200
Importance: normal
Sensitivity: Normal
In-Reply-To: <55A6456E.4020806@gmx.net>
References: <55A6456E.4020806@gmx.net>
X-UI-Message-Type: mail
X-Priority: 3
X-Provags-ID: V03:K0:egQYfRtVKMoWY0JIVRdYSdX+CBCtACzvQIUj+yHiPxP xBp+SzWJUL9imhdx1dGQ3od/M4V396jHgvmNFszVcufuCJh53T lbmgLl8GNs9OCW8b1XUSqQKa8GJGy5VQn5rLKSXqHz/n5AWRyi kYcdYiiDm+AQ/21Su7Ad1Fn4XpUhTByMci2m8dnaDnZh/TcB7d COk8vGXtV/IZ6JQNSKSqzPbKJZ4QUzrkW2z7LalPjXWyKqUohK omBGyr/77vPNRpzWt6FnjYPcYW0RDSD05cg1T5nZT6rDUJKJwi O68dU8=
X-UI-Out-Filterresults: notjunk:1;V01:K0:IDXSUYklZhw=:1qRE6Zw7rCSa+EY+GlaXva qkfgAFCSn2Qsdr8PMx9hPzlFzxlfE0tbh2GC0bKajFOVAicXuTh6La17F2bZCK3UK41/S81Bl hdjaYUS5l8x9lPh7nz2P+d4Kal7ozWx9451f36GtQS3qdGPhrcy3+/DUXjjmvAUOMsvUD9/lG /OTbMWM0WY8pXd2r2/LsHho8XIK1hpsb9zcxFj8CUpCEM6/ktaXOAYzZR6xd5RjFPSM7UVx4M 9O95BuqowgZb02A1gVjfm0u+cwN7m7rmzQCZV86RGaCfevhhcsdsBc5O0EiSTvWN0JtSIxvVJ M6AaE4/kzH26DMfodCa7vKEYoSqcyRoxR0BA27VYPNpgE23sLkjeH03HGUDK+Dm1vK/dMEZX8 pKKB94Vr2v0hPLxh28UP3p3Zgtf5sG0ur0sPyfnciPy+4yBc7epIDEd2JYwhyLIu4T6x0A9fp RrzSIlSVMQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/2IDtD3lUnuV4fDkaJsU4Dm6-36k>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Dtls-iot] RFC 7539 (ChaCha20 and Poly1305) a SHOULD/MUST implement?
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DTLS for IoT discussion list <dtls-iot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtls-iot/>
List-Post: <mailto:dtls-iot@ietf.org>
List-Help: <mailto:dtls-iot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Aug 2015 10:00:35 -0000

Hi all, Hi Stephen, 
 
I have sent the mail below to this mailing list in an attempt to solicit feedback from the DICE group after creating an issue in the issue tracker at http://trac.tools.ietf.org/wg/dice/trac/ticket/34" target="_blank" rel="nofollow">http://trac.tools.ietf.org/wg/dice/trac/ticket/34
 
I have also posted a message to the CFRG list, see 
 
While I got a little bit of feedback on the CFRG list I am still unsure about how to proceed on this topic. 
 
There does not seem to be strong interest in using ChaCha20 and Poly1305. 
Currently, AES is in used in hardware of many embedded/IoT systems. It is also mandated in various standards, including radio technologies.
To my knowledge there is no hardware support for ChaCha20 and Poly1305 in chips today. 
 
Requiring ChaCha20 and Poly1305 in addition to AES would be possible on paper but will lead to additional flash space.
 
What should we do? 
 
Ciao
Hannes 
Gesendet: Mittwoch, 15. Juli 2015 um 13:35 Uhr
Von: "Hannes Tschofenig" <hannes.tschofenig@gmx.net>
An: "dtls-iot@ietf.org" <dtls-iot@ietf.org>, "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
Betreff: [Dtls-iot] RFC 7539 (ChaCha20 and Poly1305) a SHOULD/MUST implement?
Stephen wrote:

(11) 21: Why not make RFC7539 a SHOULD or MUST right now? Doesn't it
seem like doing so now in a profile would be the right kind of timing?
And that might be our best bet for healing the CCM/GCM rift so I'd like
to check if the WG agree with that idea or not before we go to IETF LC.
(That might justify a separate thread.)

This is really a question for the group to think about. Any comments?

_______________________________________________
dtls-iot mailing list
dtls-iot@ietf.org
https://www.ietf.org/mailman/listinfo/dtls-iot" target="_blank" rel="nofollow">https://www.ietf.org/mailman/listinfo/dtls-iot

v2.23.0 | Report a Bug | By Email