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

"Salz, Rich" <rsalz@akamai.com> Wed, 03 October 2018 16:28 UTC

Return-Path: <rsalz@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 6DA1D1312F6; Wed, 3 Oct 2018 09:28:47 -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 bokLTHsvpx28; Wed, 3 Oct 2018 09:28:45 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::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 C52B9131307; Wed, 3 Oct 2018 09:28:45 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w93GRGHr000576; Wed, 3 Oct 2018 17:28:14 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=Xbm2cpnulvMqxZjIKjuYbyc95Jkl7MRPWjfd2E2NirU=; b=ie2zpgtlRDQUc5gjOkQ+BWb+S1+fkOZYxN9vmjX2DBXpqxe7WOqTSHMEIjwx0E30OFW/ Nk+4VsGBn6dl/A85tZigFSheVVay/bUUJj8dqGGy/TwHC1aeYd6P+JSQbEFMamt0i7MU 6nkSXUSsKYZsYOJzF772Tk0+rV8alqw5jOK3cxGs9Pan501bGofi+QpwNopT5dP4rA73 D8SQJdih+uj8KUw5wtJ3Z0pEjtKCzFXgsA9566mk3sFgziAqmtS5Dh4dyE0nCPeMvr2n nPDc3vYsn/y6ksq1/jDKO7VU6NjDFpT/DTGf1bODCiSjKrVBVqfI8HpHzBNYF2AxNvcv fA==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by mx0a-00190b01.pphosted.com with ESMTP id 2mvgu2tp5w-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 03 Oct 2018 17:28:14 +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 w93GKEUZ018459; Wed, 3 Oct 2018 12:28:13 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint1.akamai.com with ESMTP id 2mt4raufeg-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 03 Oct 2018 12:28:13 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 3 Oct 2018 12:28:12 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1365.000; Wed, 3 Oct 2018 12:28:12 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>, "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>, "tls@ietf.org" <tls@ietf.org>, "iana@iana.org" <iana@iana.org>
Thread-Topic: [TLS] Request to register value in TLS extension registry
Thread-Index: AQHUWzYTgYCzmvnTw0+jhiJlS3ncUg==
Date: Wed, 3 Oct 2018 16:28:12 +0000
Message-ID: <A73658AA-5CC2-4858-8CB8-CCF5D897340C@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.11.0.180909
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.34.126]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B27FD646254D2A43B5E9CC2E4B0B1642@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-03_07:, , 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810030155
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-03_07:, , 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810030156
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/keHvZ6xrZTIshbTcfbgmyu0LVWc>
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: Wed, 03 Oct 2018 16:28:47 -0000

Yoav and I (two of the three designated experts) approve the assignment of 26 for TLS-LTS.

Sorry for the delays in getting the workflow worked out, Peter.


On 9/25/18, 2:32 PM, "Peter Gutmann" <pgut001@cs.auckland.ac.nz> 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.