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

Rene Struik <rstruik.ext@gmail.com> Thu, 06 August 2015 13:27 UTC

Return-Path: <rstruik.ext@gmail.com>
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 8C8971B2F54 for <dtls-iot@ietfa.amsl.com>; Thu, 6 Aug 2015 06:27:37 -0700 (PDT)
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 k_0CDow04rih for <dtls-iot@ietfa.amsl.com>; Thu, 6 Aug 2015 06:27:35 -0700 (PDT)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 CC08F1ACE02 for <dtls-iot@ietf.org>; Thu, 6 Aug 2015 06:27:34 -0700 (PDT)
Received: by ioeg141 with SMTP id g141so80715008ioe.3 for <dtls-iot@ietf.org>; Thu, 06 Aug 2015 06:27:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type; bh=ehXWMdwJto9kmJuL8vkpsjN/d4zIhgjatiCAoWDpQxQ=; b=dLCg7c3eiaNzpve36lgLjKSQAPRq1S5ESRdDFYjhhbt4CicpddcW1Ge7jfCmSsCOJF zAlQL3TyOx0YktIZmbqMy+nkyqdvf1w5yG8poPvpIr5XlyZYQ4WkysZbHpOJCzXNwP22 7TrNmzH294jTmy/FIAJbyNjpX3y+NOUf11LOo8s+hJfJhwH8RQkdDtNTuHgINRSzjl9q b/j8J3xPR8AU9pb67OPa8ljpbYJpaOWwd7MTl7gaJLW7HVitAO5eOhuyncDOHWMfvj28 TJExMKhKVNoYkAuYFsn+bJPq7v5crq0i/RG/LhH/e3iLvKaWdeK0t6Wj1H6THvqby3Ma 34sQ==
X-Received: by 10.107.28.67 with SMTP id c64mr1906176ioc.90.1438867654278; Thu, 06 Aug 2015 06:27:34 -0700 (PDT)
Received: from [192.168.0.14] (CPE7cb21b2cb904-CM7cb21b2cb901.cpe.net.cable.rogers.com. [99.231.49.38]) by smtp.gmail.com with ESMTPSA id q10sm1340820ige.16.2015.08.06.06.27.33 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Aug 2015 06:27:33 -0700 (PDT)
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
References: <55A6456E.4020806@gmx.net> <trinity-2aa15f2d-a0c6-4213-bd91-10a6d5ca06e0-1438855226547@3capp-gmx-bs27>
From: Rene Struik <rstruik.ext@gmail.com>
Message-ID: <55C360B0.8070307@gmail.com>
Date: Thu, 06 Aug 2015 09:27:12 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <trinity-2aa15f2d-a0c6-4213-bd91-10a6d5ca06e0-1438855226547@3capp-gmx-bs27>
Content-Type: multipart/alternative; boundary="------------000905000808060901090908"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/1BNhkgXBJZBEptu8A4fCKCe0iFQ>
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 13:27:37 -0000

Hi Hannes:

I do not think there is any technical or practical reason to add support 
for ChaCha or Poly1305.

For very constrained devices, the required state is quite large, 
per-message key initialization cost is relatively high for short 
message, allowing starting processing of incoming packets
after computation of those per-message keys only, and ChaCha20 keys are 
256-bits. Most underlying transceivers already have AES on board, in 
hardware, and operate using 128-bit keys. Adding another mode does seem 
to impose cost, with unclear technical benefit, both on security and 
performance and implementation cost front.

On a side note: the security of Salsa20/20 has been quite well analyzed 
(see, e.g., [1]), but - to my knowledge - this has not been extended to 
ChaCha.

Best regards, Rene

[1] Ciphers - Salsa20 Secure Against Differential Cryptanalysis (Nicky 
Mouha, Bart Preneel, IACR ePrint 2013-328)

On 8/6/2015 6:00 AM, Hannes Tschofenig wrote:
> 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
> I have also posted a message to the CFRG list, see
> http://www.ietf.org/mail-archive/web/cfrg/current/msg07082.html
> 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
>
>
> _______________________________________________
> dtls-iot mailing list
> dtls-iot@ietf.org
> https://www.ietf.org/mailman/listinfo/dtls-iot


-- 
email: rstruik.ext@gmail.com | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363