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

Peter Gutmann <> Thu, 04 October 2018 03:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3EECB130DD5 for <>; Wed, 3 Oct 2018 20:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3] 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 D-vwFsuVueC2 for <>; Wed, 3 Oct 2018 20:18:34 -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 65754130DD6 for <>; Wed, 3 Oct 2018 20:18:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; q=dns/txt; s=mail; t=1538623114; x=1570159114; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=6H69mtBF1phK1/VpSrvFwyjhxemwAoKa6hYo4SBoj38=; b=Fwd7PXy5POUi4uQch8UwhXLlgSlhzmZnzxiPwY2RbhdMWFHgMHvax2UR eNf0pN+tThHt+TGKFr8Q547jafve6id+ycCUXJUzOs60vvp60BShGX+2z IaQkTtcRXOUAw1EEX/B8nPlJA8B/CFgK918vFrbU5kx9EINN/L34LiApK 3seyK31xxmzNIIyCEeG+kQ+cdPlSRTDR52yp6SWDo9bRM8IXISlrXdeKT QFJnTPct+aTFNByfAm5jGvFjPHYA1OZTWdK2Ogjnq+CrRLubu3Hw/+77R ffPpQy6RW2sPg7t0EoBYnl06P8DwMv0KoKjDmabs3Ren1cOM+xmdkV3Ez g==;
X-IronPort-AV: E=Sophos;i="5.54,338,1534766400"; d="scan'208";a="33526659"
X-Ironport-Source: - Outgoing - Outgoing
Received: from ([]) by with ESMTP/TLS/AES256-SHA; 04 Oct 2018 16:18:32 +1300
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 4 Oct 2018 16:18:32 +1300
Received: from ([]) by ([]) with mapi id 15.00.1395.000; Thu, 4 Oct 2018 16:18:31 +1300
From: Peter Gutmann <>
To: Benjamin Kaduk <>
CC: "<>" <>
Thread-Topic: [TLS] Request to register value in TLS extension registry
Thread-Index: AQHUOHgQgYCzmvnTw0+jhiJlS3ncUqUBiyFo//85voCACqR6AIAB5qLV///fuICAAYC9UQ==
Date: Thu, 4 Oct 2018 03:18:31 +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: Thu, 04 Oct 2018 03:18:36 -0000

Benjamin Kaduk <> writes:

>if you think you have followed the proper procedure, why did you not act on 
>the escalation procedure I pointed out to you previously, rather than 
>continuing to complain on the TLS WG list?

Because I wanted to get it fixed for others who may be going down the same 
path in the future, not just myself.  I could have also directly contacted
people to try and get it resolved, but that wouldn't help the next person
who's faced with the same issue.  Thus my attempt to try and point out 
problems so they can be cleared up for others in the future.