Re: [Tls-reg-review] [IANA #1158450] spelling change request in TLS Certificate Types registry

"Salz, Rich" <rsalz@akamai.com> Tue, 17 December 2019 14:02 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: tls-reg-review@ietfa.amsl.com
Delivered-To: tls-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EAFF120112; Tue, 17 Dec 2019 06:02:25 -0800 (PST)
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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 XrbedI2JUg0I; Tue, 17 Dec 2019 06:02:22 -0800 (PST)
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 691281200B3; Tue, 17 Dec 2019 06:02:22 -0800 (PST)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id xBHE02ep030908; Tue, 17 Dec 2019 14:01:58 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=6m5p+kgy43Bvx5fDis+F113U75ROaWuoSau6ZtekS3w=; b=VDvuoXj1Bgrike1t42apq9DeKjjGtfUXPGGUDV4/RodkmkfYgYkvR0BBtW0KMjdLBu8K +20MdNeEAuJUdno7apZXWoXd+fhffw70QJxpqG97P/YEw6q7g/kuiKdVXupJfqG1BI+I vLzyymUnglqirCcNaI5WSfT2rz+YXJtUlTyWSv7YBPH1hazPzo8vLtAQ7wXjic+PTcWl +bFTQ26Ld/kVv/oCJytG4AdZ15Cn7WapvtVQhab4Em+OS5dUqKJKkjqFvMo/4roPbXlj cEPuLdJM1zMyxOt/DgHti9G0m2j/BZ6LNK+/BAApbXo7G1KhxWsBaF9xCISzS+zZsosq uQ==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 2wvqvumhxe-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 17 Dec 2019 14:01:57 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xBHDl297015321; Tue, 17 Dec 2019 09:01:56 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.31]) by prod-mail-ppoint2.akamai.com with ESMTP id 2wvuy0v8wx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 17 Dec 2019 09:01:55 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 17 Dec 2019 09:01:53 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([172.27.123.103]) by usma1ex-dag1mb3.msg.corp.akamai.com ([172.27.123.103]) with mapi id 15.00.1473.005; Tue, 17 Dec 2019 09:01:53 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: "iana-matrix@iana.org" <iana-matrix@iana.org>, "barryleiba@computer.org" <barryleiba@computer.org>, "kaduk@mit.edu" <kaduk@mit.edu>
CC: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "ekr@rtfm.com" <ekr@rtfm.com>
Thread-Topic: [IANA #1158450] spelling change request in TLS Certificate Types registry
Thread-Index: AQHVtGP8YPtMFYeaaEqAXSz46FJeBae+XEgA
Date: Tue, 17 Dec 2019 14:01:52 +0000
Message-ID: <502E3555-1CA2-428C-B0E7-B7D7C655DBEF@akamai.com>
References: <RT-Ticket-1158450@icann.org> <20191214014601.GM81833@kduck.mit.edu> <CALaySJLJYGnOKfK2JFg7t+b4NBkCX7irBgCYFyyDzZ9bbLZgOw@mail.gmail.com> <rt-4.4.3-24012-1576536955-1590.1158450-37-0@icann.org>
In-Reply-To: <rt-4.4.3-24012-1576536955-1590.1158450-37-0@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.20.0.191208
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.115.193]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F6C2DDEA631FAC47BB0D8BD4475B0DC5@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-12-17_02:, , 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-1911140001 definitions=main-1912170119
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-17_02:2019-12-17,2019-12-17 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 priorityscore=1501 malwarescore=0 spamscore=0 mlxscore=0 suspectscore=0 bulkscore=0 phishscore=0 clxscore=1011 lowpriorityscore=0 mlxlogscore=999 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912170120
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/oTMZbUeRetu6IxGiapYLfwOMQ7A>
Subject: Re: [Tls-reg-review] [IANA #1158450] spelling change request in TLS Certificate Types registry
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TLS REVIEW <tls-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls-reg-review/>
List-Post: <mailto:tls-reg-review@ietf.org>
List-Help: <mailto:tls-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Dec 2019 14:02:25 -0000

I don't see a need to wait, but I don't see it as a big deal so whatever IANA prefers is fine with me.

´╗┐On 12/16/19, 5:56 PM, "Amanda Baber via RT" <iana-matrix@iana.org>; wrote:

    Hi,
    
    Should we wait to make the change until there's an errata report to refer to, or should we make the change now and refer to 8446?
    
    thanks,
    Amanda
    
    On Sat Dec 14 14:48:53 2019, barryleiba@computer.org wrote:
    > No-brainer here, yes.  Process-wise, for completeness, I think we
    > should consider this to be an erratum in 8446, in that it neglected to
    > include an IANA action for this.  I think it makes sense to submit an
    > errata report to add it, mark that report as "verified", and ask IANA
    > to make the change.
    > 
    > Barry
    > 
    > On Fri, Dec 13, 2019 at 8:46 PM Benjamin Kaduk <kaduk@mit.edu>; wrote:
    > >
    > > Hi all,
    > >
    > > RFC 8446 deliberately changed the spelling for the TLS Certificate
    > > type
    > > assigned value 0 (listed at
    > > https://www.iana.org/assignments/tls-extensiontype-values/tls-
    > > extensiontype-values.xhtml#tls-extensiontype-values-3),
    > > from "X.509" to "X509" (no dot).  This was done to improve the
    > > compatibility of the protocol description language with automated
    > > processing tools.  Since the name is not a protocol constant and
    > > merely a
    > > descriptive mnemonic, I propose that we update the name listed in the
    > > registry accordingly.  Adding [RFC8446] as a reference at the same
    > > time
    > > also seems plausible.  Comments welcome!
    > >
    > > Thanks,
    > >
    > > Ben
    > >