IETF Logo Mail Archive

Re: [TLS] PR#345: IANA Considerations

Benjamin Kaduk <bkaduk@akamai.com> Tue, 17 November 2015 17:53 UTC

Return-Path: <bkaduk@akamai.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 680421B2D16 for <tls@ietfa.amsl.com>; Tue, 17 Nov 2015 09:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level:
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.585, 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 uoY1TCBvKdjI for <tls@ietfa.amsl.com>; Tue, 17 Nov 2015 09:53:43 -0800 (PST)
Received: from prod-mail-xrelay07.akamai.com (prod-mail-xrelay07.akamai.com [23.79.238.175]) by ietfa.amsl.com (Postfix) with ESMTP id CB4E71B2D39 for <tls@ietf.org>; Tue, 17 Nov 2015 09:53:43 -0800 (PST)
Received: from prod-mail-xrelay07.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 4582F43349D; Tue, 17 Nov 2015 17:53:42 +0000 (GMT)
Received: from prod-mail-relay11.akamai.com (prod-mail-relay11.akamai.com [172.27.118.250]) by prod-mail-xrelay07.akamai.com (Postfix) with ESMTP id 2FB7343346A; Tue, 17 Nov 2015 17:53:42 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; s=a1; t=1447782822; bh=dFksnNmmsF7o/g1DRikVXMhTuG0fYlT/U4aJ2Eb4YmU=; l=584; h=To:References:Cc:From:Date:In-Reply-To:From; b=IXekAZCMkV6G0r1BJSb8oYxUYn6uISEiHGxc1AWOwex8AzGmNLw0Ay0dlz8nvrl7U 3Rvs/PToH2foR7gt8iMuTwo3HWnypMjQDATOcGE6lc7lorD3tQ+XgMNPlj6ZjAHwVU DXACssmuAqK0EVOnYwleYi8CTTdJsjynZHUGsDD0=
Received: from [172.19.0.25] (bos-lpczi.kendall.corp.akamai.com [172.19.0.25]) by prod-mail-relay11.akamai.com (Postfix) with ESMTP id F19D1202C; Tue, 17 Nov 2015 17:53:41 +0000 (GMT)
To: Joe Salowey <jsalowey@tableau.com>
References: <CABcZeBNMkJSQAm0gFZdecG8Nf+df+heP2V_u9pXGJmb7jV4BcQ@mail.gmail.com> <CABcZeBOD71keb_yE4EumgkOxXfOCnsniLrhDa3tHzsioE2E2bw@mail.gmail.com> <EAA07156-6F05-488B-A3E5-175100989449@sn3rd.com> <CABcZeBMn4BcpYLgoqFb=PuW92jnfhEK8cw7nStZEyh9RDdN6XQ@mail.gmail.com> <A61BBA75-2594-4DF7-8EF6-887B2F001DA1@sn3rd.com> <7276DA5B-0563-4D70-A611-96A2E80CAECB@tableau.com>
From: Benjamin Kaduk <bkaduk@akamai.com>
Message-ID: <564B69A5.2030205@akamai.com>
Date: Tue, 17 Nov 2015 11:53:41 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <7276DA5B-0563-4D70-A611-96A2E80CAECB@tableau.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/auwuBQj07yr1k-78mlTjyct_xi8>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] PR#345: IANA Considerations
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 17 Nov 2015 17:53:45 -0000

On 11/17/2015 10:46 AM, Joe Salowey wrote:
> I think the TLS 1.3 IANA considerations should just deal with setting up the recommended column and marking it for the cipher suites/extensions that are described in the 1.3 document.  Other cipher suites/extensions  can be marked as recommended through other documents.  
>

That would seem to leave a number of things in limbo until this
hypothetical other document or documents come out.  It seems more
responsible in some sense to make the registry be in a
coherent/consistent state from the time its structure is modified.

-Ben

v2.23.0 | Report a Bug | By Email