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

"Salz, Rich" <rsalz@akamai.com> Sat, 14 December 2019 02:35 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 A8742120090; Fri, 13 Dec 2019 18:35:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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] 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 62fZjJqGqc92; Fri, 13 Dec 2019 18:35:58 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 4D836120019; Fri, 13 Dec 2019 18:35:58 -0800 (PST)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xBE2WJN8009899; Sat, 14 Dec 2019 02:35:37 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=pFA91d6zcsfxrU/USU6JcYH89AHxLv6OT2uNPifXqEA=; b=EFSyq0pzxBvhQXGfaUCLqPo+Wgu021Xid7SUPq8HOy11OZp87AJkFuzRx8s6ABgHMjDc DMrVjEauQvpGHFebDKwHkog0DCfTYpcvzywrLLB4E50+0oyESOj2mgVbiJdu7cwqFX7E dy8aXRekAAnPiT/I8ouTqIoTGYgtnOnFlEG6QY2Ch6avBTc3npuZjZaAM1rFNbNHE1m/ sQmr6/cMmePHKAtKASso8BOKM804FWxFZMrYjX0KKvcj01WiuYNSeZRS5R5mfyfkfcLK gIQZoCA8SYK8Z80hLV0uZW2yNNLSAoL80C1SfFftnXDn3unfQAJZMgxr4G8I2TIMsq+Q PQ==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 2wuqbpnxtk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 14 Dec 2019 02:35:37 +0000
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xBE2WdaZ026750; Fri, 13 Dec 2019 21:35:36 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint1.akamai.com with ESMTP id 2wr8a1u0q8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 13 Dec 2019 21:35:36 -0500
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag3mb6.msg.corp.akamai.com (172.27.123.54) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 13 Dec 2019 21:35:35 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 13 Dec 2019 21:35:35 -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; Fri, 13 Dec 2019 21:35:35 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Benjamin Kaduk <kaduk@mit.edu>, "iana@iana.org" <iana@iana.org>
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: [Tls-reg-review] spelling change request in TLS Certificate Types registry
Thread-Index: AQHVsiBS6ZlmzkRsKkGh0n1pvdMQBae46hEA
Date: Sat, 14 Dec 2019 02:35:34 +0000
Message-ID: <C54A7E3C-C6AB-41BA-A71D-2B8166EED5CA@akamai.com>
References: <20191214014601.GM81833@kduck.mit.edu>
In-Reply-To: <20191214014601.GM81833@kduck.mit.edu>
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.112.215]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BBBBF04AD00A014D93201B56CC70D021@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-12-13_09:, , 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-1912140015
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-13_09:2019-12-13,2019-12-13 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 phishscore=0 suspectscore=0 priorityscore=1501 mlxscore=0 malwarescore=0 mlxlogscore=999 adultscore=0 clxscore=1011 lowpriorityscore=0 bulkscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912140014
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/rNoUcWXlSnK_1hU2StN_C15lb9A>
Subject: Re: [Tls-reg-review] 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: Sat, 14 Dec 2019 02:36:00 -0000

wfm

On 12/13/19, 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
    
    _______________________________________________
    tls-reg-review mailing list
    tls-reg-review@ietf.org
    https://www.ietf.org/mailman/listinfo/tls-reg-review