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

Peter Gutmann <> Wed, 03 October 2018 06:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 61EF81311EA for <>; Tue, 2 Oct 2018 23:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.199
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Ry_HJfcTCL60 for <>; Tue, 2 Oct 2018 23:17:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 09853131090 for <>; Tue, 2 Oct 2018 23:17:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; q=dns/txt; s=mail; t=1538547435; x=1570083435; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Gwrsf1isVLJ6f2OB6ojOVnZinIGY4H4v8CLlCU7UTTM=; b=R9Q33MY5TzBqWpQ1G788GiizocpB6zFlAqwdY2zxLI1dEhqPWdiYTABD MBUUpNHaIIrfMh0cr6eA9HtwOL0zWeKrcpQUXc2nh/Gn91mxJVETOfM07 G7fPFYwMV443w5EovKBBbZn5kQ2A8v6cWEw3cwJFe4XINsrBWotmhbQtU fj3eAhxlCgvQQywb3YQrBlhK8Zln5DcnZ0D89gqgCdMju+zd4nXNX5YLr 6Dc+nX/kFm3nZuoEk+g4iAlIwRLNaJpeVMKP1UxFQaok1va6ctLlaWxVh EN98i5O3TxnvoNsaETyJy84Nlc3zT0t3DEheLyKxZAMW30Cn9Fb+Z6oa2 w==;
X-IronPort-AV: E=Sophos;i="5.54,334,1534766400"; d="scan'208";a="33380072"
X-Ironport-Source: - Outgoing - Outgoing
Received: from (HELO ([]) by with ESMTP/TLS/AES256-SHA; 03 Oct 2018 19:17:10 +1300
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 3 Oct 2018 19:17:09 +1300
Received: from ([]) by ([]) with mapi id 15.00.1395.000; Wed, 3 Oct 2018 19:17:09 +1300
From: Peter Gutmann <>
To: Benjamin Kaduk <>
CC: "<>" <>
Thread-Topic: [TLS] Request to register value in TLS extension registry
Thread-Index: AQHUOHgQgYCzmvnTw0+jhiJlS3ncUqUBiyFo//85voCACqR6AIAB5qLV
Date: Wed, 3 Oct 2018 06:17:09 +0000
Message-ID: <>
References: <> <> <>,<>
In-Reply-To: <>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [TLS] Request to register value in TLS extension registry
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 03 Oct 2018 06:17:18 -0000

[CC'd back to the TLS list because this affects other TLS work as well]

Benjamin Kaduk <> writes:

>Having looked a bit harder, it seems that perhaps I need to point out that,
>if you want IANA to allocate a value, you need to *ask IANA for it*.  The
> list is not a supported IANA entrypoint;

That's not what the RFC appears to say:

   Specification Required [RFC8126] registry requests are registered
   after a three-week review period on the <>
   mailing list, on the advice of one or more designated experts.


   Registration requests sent to the mailing list for review SHOULD use
   an appropriate subject (e.g., "Request to register value in TLS bar

This is exactly what I did, I sent a registration request to the list for

   Within the review period, the designated experts will either approve
   or deny the registration request, communicating this decision to the
   review list and IANA.

This never happened.

Did anyone actually test RFC 8447 before it was published?  You send a request
to a mailing list that doesn't seem to work, to be reviewed by a secret panel
(well, we know that Rich Salz is one member :-), with no public discussion or
list archives you can examine to see what happened, and in my case no response
to the registration request submitted as per the RFC.