Re: [Tls-reg-review] Request to register TLS integrity only cipher suites for TLS 1.3

Nick Sullivan <nick@cloudflare.com> Tue, 11 December 2018 18:38 UTC

Return-Path: <nick@cloudflare.com>
X-Original-To: tls-reg-review@ietfa.amsl.com
Delivered-To: tls-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8B0130F06 for <tls-reg-review@ietfa.amsl.com>; Tue, 11 Dec 2018 10:38:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.46
X-Spam-Level:
X-Spam-Status: No, score=-3.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 UPPZ-n98sVFY for <tls-reg-review@ietfa.amsl.com>; Tue, 11 Dec 2018 10:38:02 -0800 (PST)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 43C0B130F02 for <tls-reg-review@ietf.org>; Tue, 11 Dec 2018 10:38:02 -0800 (PST)
Received: by mail-ot1-x32a.google.com with SMTP id i20so15078274otl.0 for <tls-reg-review@ietf.org>; Tue, 11 Dec 2018 10:38:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+sXyJ+H+VXGHZWgRIm8GMfTEly1peojvr9IT6MLSMYw=; b=JMk/TtxyeS33hxJqY5+FfV764Vxx/y+bHmz/dU9CRRN0lkj0xapkQLE/OvaDL4e8JH uoTKBSVqNZ8epkR3zd6Cl9FAihrR9UWEzI98z+hKD41bi408m8tpsygEpXrnmlwpRsQq hsoHSP6QHUihS+bHZn4p4Xi5f0ZrDcLyDJ2Ys=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+sXyJ+H+VXGHZWgRIm8GMfTEly1peojvr9IT6MLSMYw=; b=TntT+1fLtLvo4Pyq8qVVcWge0Iwd0IBywa2XaqydJujlPNhzKNQU6WXi+DsuA1lpon M5muPLx10mtOVlxGGRIlkq45TkMqoTZZ0+NuLvjb5GCJLf1LYZXHzpiCtXijaZnoZctu ZsKRMYolTFBYoO6R96NZu1SwnyH4sxrjVAooJPZYHeXO+a+YX8PQ7UNEzdsDBZ8qqd5Y SQr18hErsxwqPVM+D1+/S6aE2LgqVsWYB+T7q+cyy8EYntWUBuADasC8Nd6zX5kmQ7Kl j0e0EMl/mXiwJIhJgZC3HZqP2I2tK6ZuOtmKC/GSvNP6XOBvOfKVzCuP+rWKxinVyeUc 3miA==
X-Gm-Message-State: AA+aEWa5GooN1eN8ISME1rTPTW6DWA708fj0l85T+AEOQo6wTRJsBdzb OKs4DGSK3HHBKi2562FEQoB7K9EUn2frm2cKYnCL+w==
X-Google-Smtp-Source: AFSGD/Wx+ShxaNWGn7hgqQegZ9IeG4ah/4kJz3+ikk2FFcyIVHPpgSTkpSDIqubL/7s2fVKh5HEpxQks9xfbC4n8Tsg=
X-Received: by 2002:a9d:64c8:: with SMTP id n8mr12903173otl.115.1544553481471; Tue, 11 Dec 2018 10:38:01 -0800 (PST)
MIME-Version: 1.0
References: <CF6744AC-9E92-4E91-8652-790682B39EF8@akamai.com>
In-Reply-To: <CF6744AC-9E92-4E91-8652-790682B39EF8@akamai.com>
From: Nick Sullivan <nick@cloudflare.com>
Date: Tue, 11 Dec 2018 18:37:50 +0000
Message-ID: <CAFDDyk-p3s1k+zE=_aXO7qc9qoJz3wh3nRfRbeOS25v6Neqw9w@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: tls-reg-review@ietf.org
Content-Type: multipart/alternative; boundary="00000000000099b22b057cc361e0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/F1nIHQqA9zZ9VmARxqrhiaFwqyg>
Subject: Re: [Tls-reg-review] Request to register TLS integrity only cipher suites for TLS 1.3
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TLS REVIEW <tls-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls-reg-review/>
List-Post: <mailto:tls-reg-review@ietf.org>
List-Help: <mailto:tls-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2018 18:38:05 -0000

I guess there's no requirement for a TLS 1.3 ciphersuite to be literal
AEAD, is there?

It should be fine to assign two "not recommended" points.

On Tue, Dec 11, 2018 at 6:32 PM Salz, Rich <rsalz@akamai.com> wrote:

> Seems legit to me.  Anyone else have a view?
>
> On 12/5/18, 2:54 PM, "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
> wrote:
>
>         > Contact Name:
>         > Nancy Cam-Winget
>         >
>         > Contact Email:
>         > ncamwing@cisco.com
>         >
>         > Type of Assignment:
>         > "Not Recommended" TLS Cipher suite assignment
>         >
>         > Registry:
>         > TLS 1.3 cipher suite
>         >
>         > Description:
>         > At least two IoT (ODVA and IEC) forums are requesting the need
> for
>         > enabling TLS 1.3 with integrity only protection in the data
> plane.
>         > Under security considerations, we are not recommending this
> cipher
>         > suite to be widely used and note that no privacy is provided
> when this
>         > cipher suite is used and several use cases have been noted where
>         > privacy is not required.
>         >
>         > Additional Info:
>         > We have noted the use cases and security (and privacy)
> considerations
>         > in
> https://tools.ietf.org/html/draft-camwinget-tls-ts13-macciphersuites-01
> as well as how the cipher suite would be used with
>         > TLS 1.3
>
>
>
>     _______________________________________________
>     tls-reg-review mailing list
>     tls-reg-review@ietf.org
>     https://www.ietf.org/mailman/listinfo/tls-reg-review
>
>
> _______________________________________________
> tls-reg-review mailing list
> tls-reg-review@ietf.org
> https://www.ietf.org/mailman/listinfo/tls-reg-review
>