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

Peter Gutmann <pgut001@cs.auckland.ac.nz> Tue, 25 September 2018 18:32 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
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 C2B7C128CB7; Tue, 25 Sep 2018 11:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=auckland.ac.nz
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 As5K8PGLmezG; Tue, 25 Sep 2018 11:32:46 -0700 (PDT)
Received: from mx4-int.auckland.ac.nz (mx4-int.auckland.ac.nz [130.216.125.246]) (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 4F6841294D0; Tue, 25 Sep 2018 11:32:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1537900359; x=1569436359; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=taPibVY7e6AF/8hxxqxYRZO9Z12BCTniZ+rCkmwJC14=; b=vNC4ONNYqsf9tJUGerHngPmbaeu8Fzx/KhRo6vjG6IZi3nEGc//isBn1 I5YjheSuO16yukkSQw6DMUTgFmeCyNSnwqsuRS3cxyifh2xWGcsFq8L2a hVLFiHgWofeo/E1hMgkf8g3idpxqhVlZcnMOOh0a0iyPf3j/+d/ljss12 FPcCF+qRCY1gs8ywtWzUoMiCEM4Lj22OAJbUj7yeuT8fYQQ8nFBs6rYlA 9n+A0tWkPz4Icsac9F5kuWBXi25brbebJeqG0OTr6/O/F0tgg1jNtbd9+ mEXDpOUOYj5R+tSu8un+3Kqv6vFMnQwf3sBViT/r21AKM3Cghv4tZ/5DP g==;
X-IronPort-AV: E=Sophos;i="5.54,303,1534766400"; d="scan'208";a="32299191"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 10.6.3.4 - Outgoing - Outgoing
Received: from uxcn13-tdc-c.uoa.auckland.ac.nz ([10.6.3.4]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 26 Sep 2018 06:32:33 +1200
Received: from uxcn13-ogg-d.UoA.auckland.ac.nz (10.6.2.5) by uxcn13-tdc-c.UoA.auckland.ac.nz (10.6.3.4) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 26 Sep 2018 06:32:33 +1200
Received: from uxcn13-ogg-d.UoA.auckland.ac.nz ([10.6.2.5]) by uxcn13-ogg-d.UoA.auckland.ac.nz ([10.6.2.5]) with mapi id 15.00.1395.000; Wed, 26 Sep 2018 06:32:33 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>, "tls@ietf.org" <tls@ietf.org>
Thread-Topic: Request to register value in TLS extension registry
Thread-Index: AQHUOHgQgYCzmvnTw0+jhiJlS3ncUqUBiyFo
Date: Tue, 25 Sep 2018 18:32:32 +0000
Message-ID: <1537900287727.4977@cs.auckland.ac.nz>
References: <1534764197914.55986@cs.auckland.ac.nz>
In-Reply-To: <1534764197914.55986@cs.auckland.ac.nz>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/7udI-VnusKaVe3u37wdFUz5H5ok>
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:32:49 -0000

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?

Peter.