Re: [TLS] early code points assigned (was Re: early code point assignment for draft-ietf-tls-certificate-compression)

Nico Williams <nico@cryptonector.com> Thu, 24 May 2018 19:46 UTC

Return-Path: <nico@cryptonector.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 5833B12EB12; Thu, 24 May 2018 12:46:32 -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, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 4lSAU0Rzf9aM; Thu, 24 May 2018 12:46:30 -0700 (PDT)
Received: from homiemail-a73.g.dreamhost.com (homie-sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D375412EB11; Thu, 24 May 2018 12:46:30 -0700 (PDT)
Received: from homiemail-a73.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a73.g.dreamhost.com (Postfix) with ESMTP id 6DD1458000931; Thu, 24 May 2018 12:46:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=nO+M2XB4VpVJ0r tDTkEq7YpdLuY=; b=UIM09jOOi21b8THwegfBwFud3R2KCvNzBbzIIrMC9e05pd OwrgHzKZ4vV4tuL34EGCry4w6HPe51C4FvMJkEcYM10nncsoqw2AyCZjdll+7bYF gAtqFDJGT6JKN7sTo4+bq6Cjn09XwoMkfhQmCgeUnfDfr0rezXAirZxL8Dw4U=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a73.g.dreamhost.com (Postfix) with ESMTPSA id E804958000934; Thu, 24 May 2018 12:46:27 -0700 (PDT)
Date: Thu, 24 May 2018 14:46:26 -0500
From: Nico Williams <nico@cryptonector.com>
To: Adam Langley <agl@imperialviolet.org>
Cc: Peter Gutmann <pgut001@cs.auckland.ac.nz>, draft-ietf-tls-certificate-compression@ietf.org, tls@ietf.org
Message-ID: <20180524194624.GC14446@localhost>
References: <54EDD7A6-6B15-4C6E-9181-12438F060C67@sn3rd.com> <A04F3B59-960C-4947-846F-EC988E6353FA@sn3rd.com> <9E57701A-E98C-4DEF-B0C3-EE563D1AFBB7@sn3rd.com> <1527132197784.15190@cs.auckland.ac.nz> <CAMfhd9VMJ5g0gDD2V9=BwPyW_u16OVhe77ftrLV2=rt7tWjQ=Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAMfhd9VMJ5g0gDD2V9=BwPyW_u16OVhe77ftrLV2=rt7tWjQ=Q@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/UHRO-buOUYpc6mBHTOrJFgdoqVo>
Subject: Re: [TLS] early code points assigned (was Re: early code point assignment for draft-ietf-tls-certificate-compression)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
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, 24 May 2018 19:46:32 -0000

On Thu, May 24, 2018 at 09:30:59AM -0700, Adam Langley wrote:
> On Wed, May 23, 2018 at 8:23 PM Peter Gutmann <pgut001@cs.auckland.ac.nz>
> wrote:
> > That's going to cause clashes with implementations that use that value for
> > TLS-LTS, it would be better to use a value other than 26 that isn't
> already in
> > use.
> 
> Obviously I'm not adverse to using the occasional, non-IANA code point. But
> they need to be picked randomly and outside the dense, IANA area.
> Otherwise, this is certain to happen in short order.

Why can't we make it so IANA does early codepoint assignment?

Nico
--