IETF Logo Mail Archive

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

"Sabrina Tanamal via RT" <iana-prot-param@iana.org> Wed, 12 December 2018 23:12 UTC

Return-Path: <iana-shared@icann.org>
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 DFD78130F7B for <tls-reg-review@ietfa.amsl.com>; Wed, 12 Dec 2018 15:12:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.178
X-Spam-Level:
X-Spam-Status: No, score=-3.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 qkQmJHoV3zdG for <tls-reg-review@ietfa.amsl.com>; Wed, 12 Dec 2018 15:12:37 -0800 (PST)
Received: from smtp01.icann.org (smtp01.icann.org [192.0.46.81]) (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 E5CEF130F24 for <tls-reg-review@ietf.org>; Wed, 12 Dec 2018 15:12:36 -0800 (PST)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (Postfix) with ESMTP id 0240BE0AAC; Wed, 12 Dec 2018 23:12:36 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id BCA7B204A8; Wed, 12 Dec 2018 23:12:35 +0000 (UTC)
RT-Owner: amanda.baber
From: Sabrina Tanamal via RT <iana-prot-param@iana.org>
Reply-To: iana-prot-param@iana.org
In-Reply-To: <rt-4.4.3-23334-1544633480-1124.1132414-37-0@icann.org>
References: <RT-Ticket-1132414@icann.org> <CFEF8F6B-9136-4B4C-B6DE-0E635786A240@akamai.com> <rt-4.4.3-21493-1544578196-1273.1132414-37-0@icann.org> <B8FCF390-4B0A-46BC-B3AB-E92A7C7D4FCF@akamai.com> <rt-4.4.3-23334-1544633480-1124.1132414-37-0@icann.org>
Message-ID: <rt-4.4.3-4154-1544656355-1253.1132414-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1132414
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: sabrina.tanamal@icann.org
CC: jmvisoky@ra.rockwell.com, ncamwing@cisco.com, tls-reg-review@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 12 Dec 2018 23:12:35 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/NoVWx_m1q76fV84uMnQCwcmbO10>
Subject: [Tls-reg-review] [IANA #1132414] Re: 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
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: Wed, 12 Dec 2018 23:12:40 -0000

Hi Rich, all, 

Sorry we have one more question. Can you let us know how to fill in the "DTLS-OK" column in the TLS Cipher Suites registry?

Thanks,

Sabrina Tanamal (filling in for Amanda)
Senior IANA Services Specialist

On Wed Dec 12 16:51:20 2018, rsalz@akamai.com wrote:
> To avoid creating new holes, how about right after dragonfly:
> 0xC0,0xB3       TLS_ECCPWD_WITH_AES_256_CCM_SHA384      Y       N
> [RFC-harkins-tls-dragonfly-03]
> 0xC0,0xB4-FF    Unassigned
> 
> On 12/11/18, 8:29 PM, "Amanda Baber via RT" <iana-prot-
> param@iana.org> wrote:
> 
> Hi Rich,
> 
> Which values should we assign? There are a number of ranges available,
> and I haven't been able to find any text in RFC 8447 or RFC 8446 that
> identifies which section is for "Not Recommended" assignments:
> 
> https://www.iana.org/assignments/tls-parameters/tls-
> parameters.xhtml#tls-parameters-4
> 
> Thanks for your patience,
> 
> Amanda Baber
> Lead IANA Services Specialist
> 
> On Tue Dec 11 20:34:22 2018, rsalz@akamai.com wrote:
> > We discussed this and approve.  Please assign two numbers in the "not
> > recommended" space.
> >
> > Thanks!
> >
> > 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
> >
> >
> 
> 
>

v2.23.0 | Report a Bug | By Email