Re: [TLS] Request to register value in TLS extension registry

Benjamin Kaduk <bkaduk@akamai.com> Tue, 25 September 2018 18:42 UTC

Return-Path: <bkaduk@akamai.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 B28CE128CF2; Tue, 25 Sep 2018 11:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, 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=akamai.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 NKcZ8EmRpfcY; Tue, 25 Sep 2018 11:42:37 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 4E51F129AB8; Tue, 25 Sep 2018 11:42:26 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w8PIfeue025830; Tue, 25 Sep 2018 19:42:21 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=jan2016.eng; bh=sQkNqkrUbXAc2We0epzgr49SObgm0A4XzhNGbn3rG78=; b=dpp2fv3fUK64F7CE4JKId68wwLIFtPuwu6UOZZyZ4ltUuUltdt2QW1IFZ5Q+cl43huk9 FMcQCMjXjg59C+WlHae7NlsstoUEEly2MVHxQ7kz6JPmdOXA1f72O8aL5dUdJIuKHaP0 V4oYR2qlzBuFWL+g74gyHP9qTW2TEIQCcL10Rbg0P8pSaLKxuGM8qEvbVkeYDrLT5UZH jwkL+ls/QfgPFcyWdBHjVGdHN/JaX1eule2qVlJtQx7AAx7ynRkzc1dQiB+gKpU5mqcz wK8u2+pCokvyfjQnoztcOAZmuNdqC9IdXgn+mhOu/Jwkvu4MkTNxKC8fgylqp2jHHz3t sA==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by mx0b-00190b01.pphosted.com with ESMTP id 2mq5ruujux-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 25 Sep 2018 19:42:21 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w8PIZJvs023228; Tue, 25 Sep 2018 14:42:20 -0400
Received: from prod-mail-relay10.akamai.com ([172.27.118.251]) by prod-mail-ppoint1.akamai.com with ESMTP id 2mnh2v2gxa-1; Tue, 25 Sep 2018 14:42:20 -0400
Received: from bos-lpczi.kendall.corp.akamai.com (bos-lpczi.kendall.corp.akamai.com [172.19.17.86]) by prod-mail-relay10.akamai.com (Postfix) with ESMTP id 3135E234D1; Tue, 25 Sep 2018 18:42:20 +0000 (GMT)
Received: from bkaduk by bos-lpczi.kendall.corp.akamai.com with local (Exim 4.86_2) (envelope-from <bkaduk@akamai.com>) id 1g4sHr-0004sv-F9; Tue, 25 Sep 2018 13:42:19 -0500
Date: Tue, 25 Sep 2018 13:42:19 -0500
From: Benjamin Kaduk <bkaduk@akamai.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Cc: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>, "tls@ietf.org" <tls@ietf.org>
Message-ID: <20180925184219.GD19845@akamai.com>
References: <1534764197914.55986@cs.auckland.ac.nz> <1537900287727.4977@cs.auckland.ac.nz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1537900287727.4977@cs.auckland.ac.nz>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-25_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=959 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809250182
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-25_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=992 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809250183
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/1ToPuiWamQBTGSWnejYvfTtmZXI>
Subject: Re: [TLS] Request to register value in TLS extension registry
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: Tue, 25 Sep 2018 18:42:40 -0000

On Tue, Sep 25, 2018 at 06:32:32PM +0000, Peter Gutmann wrote:
> I wrote:
> 
> >Now that RFC 8447 is published, I'd like to request the addition of extension
> >ID 26 for TLS-LTS:
> >
> >https://datatracker.ietf.org/doc/draft-gutmann-tls-lts/
> >
> >This extension has been waiting for quite some time for the publication of
> >8447, so it's already in use by implementations.
> 
> As per RFC 8447, I requested allocation of extension ID 26 for TLS-LTS on 20
> August. The RFC says:
> 
>   Specification Required [RFC8126] registry requests are registered after a
>   three-week review period
> 
> It's now been more than the three weeks listed in the RFC, what happens now?
> Can I list the extension as allocated in the LTS draft?

Most certainly not!  I quote:

   Registration requests that are undetermined for a period longer than
   21 days can be brought to the IESG's attention (using the
   <iesg@ietf.org> mailing list) for resolution.

-Ben