IETF Logo Mail Archive

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

Benjamin Kaduk <kaduk@mit.edu> Sat, 14 December 2019 01:46 UTC

Return-Path: <kaduk@mit.edu>
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 A0AA91200A4; Fri, 13 Dec 2019 17:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 qJAPi6N6oigC; Fri, 13 Dec 2019 17:46:26 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 AFFFF120019; Fri, 13 Dec 2019 17:46:26 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id xBE1k1hb003934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Dec 2019 20:46:03 -0500
Date: Fri, 13 Dec 2019 17:46:01 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: iana@iana.org
Cc: iesg@ietf.org, tls-reg-review@ietf.org, ekr@rtfm.com
Message-ID: <20191214014601.GM81833@kduck.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/WqmQ2RgYgzthnIRFKAIAGnVvUro>
Subject: [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 01:46:29 -0000

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

v2.23.0 | Report a Bug | By Email