IETF Logo Mail Archive

[TLS] Are we holding TLS wrong?

David Schinazi <dschinazi.ietf@gmail.com> Thu, 08 November 2018 02:14 UTC

Return-Path: <dschinazi.ietf@gmail.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 B302A130DC2; Wed, 7 Nov 2018 18:14:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 3xVXw6HHQPef; Wed, 7 Nov 2018 18:14:41 -0800 (PST)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (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 3408F1292F1; Wed, 7 Nov 2018 18:14:38 -0800 (PST)
Received: by mail-pl1-x631.google.com with SMTP id f12-v6so7582117plo.1; Wed, 07 Nov 2018 18:14:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=4poedo27GxCs499Dkm05dd7N6lwwoFg/rvRo8Z+GceA=; b=YgudYbNjaTbmPsjRxndo+HUq3GmLzwAqVfNSChk1MMFZUdvvs4eEe3Vygnv/DsPxNo mWAW7tONKs36DMjLPJxBpgUuRz2nmUGqRKK5DCHUT5VbEwp5++DKNuMEmuSIJO7fGijo LO+QV8F+WJF30xYVGEyT2+B2nu3TxIuPtPJ3FnAKgX48nsi1BAvudq1Kn/jpq8rkA34p +UUr9L+2JlbjQ0oMdUzaGRdB4AKYnhk3Drd6iG6Fs+HJL34Jueh+3UqnC3T5sEW2NTw/ lXpLCdZFZiKesqKCTwHhxK/atON3iHPqr0oRp7WiVK2Ft8EUy5SRfgezWWnADFXgslZ6 /Dew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=4poedo27GxCs499Dkm05dd7N6lwwoFg/rvRo8Z+GceA=; b=abUOm+F9djwa4fejx1s1uNuLRoA8R+rEUS3lZ9FRa8s6bnQF2/VePeDDYXuMT28ZeH +J5bTXVGw0K8LbcBSL4ONQujlBGh3xkPXTWu5fhwHYt6ZY9UgioPeAP83FEWzcIGezkw yRIkpxExABjGfIMhGECteDsHkHqNd3m1U+W1vIvSc16C5zni7lEcbbv64ywY67x7xFxq v96I+6Tgv4R1Rxp/UsHG5jN+NZn9F3wHzJ1+Acn42hodMmdXMq5i0YIYi9+mlVUnbU4z untGXWaelclUIXrh1svm00LeK3z4cz4Z5oI1Zfn4qV4W4YkCDDqAbhpb4lUzeW8ry9wN xe/A==
X-Gm-Message-State: AGRZ1gKDmZ1AW/Cax9wpyOFOR6N64KZqOFY/LzHkdNtR6iX3o/HmTmZw dSgrQwU99ucuvFFooLzUY8WW+o++KbG+qlE9XxgbKBdM
X-Google-Smtp-Source: AJdET5eO1VvwiTDG/5Oh5rXM2RKCTXka9MYy8t9APjASnhvbuKmtw25qN64vdNxmgwsXa4Nxo4TrFhm9RTOSIYwq8A8=
X-Received: by 2002:a17:902:9698:: with SMTP id n24-v6mr2791069plp.9.1541643277265; Wed, 07 Nov 2018 18:14:37 -0800 (PST)
MIME-Version: 1.0
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 08 Nov 2018 09:14:25 +0700
Message-ID: <CAPDSy+7-ceNNLJpFK0Z4SitBaUgxTpxiea8Z0QtpeSr+MNLKFg@mail.gmail.com>
To: tls@ietf.org
Cc: draft-ietf-babel-dtls@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e96eb3057a1dcbf4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/tIaK0rgm5zCVuYmLm5qsCIvKXKw>
Subject: [TLS] Are we holding TLS wrong?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 08 Nov 2018 02:14:44 -0000

Hi everyone,

Over in the Babel working group we have a draft about securing Babel with
DTLS:
https://tools.ietf.org/html/draft-ietf-babel-dtls-01

It's 5 pages long, could any TLS experts please give it a quick read and
let us know if we're using DTLS correctly?

Also, should the document contain guidance such as which DTLS version to
use?

Thanks,
David

v2.23.0 | Report a Bug | By Email