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

"Amanda Baber via RT" <iana-matrix@iana.org> Mon, 16 December 2019 22:55 UTC

RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-matrix@iana.org>
Reply-To: iana-matrix@iana.org
In-Reply-To: <CALaySJLJYGnOKfK2JFg7t+b4NBkCX7irBgCYFyyDzZ9bbLZgOw@mail.gmail.com>
References: <RT-Ticket-1158450@icann.org> <20191214014601.GM81833@kduck.mit.edu> <CALaySJLJYGnOKfK2JFg7t+b4NBkCX7irBgCYFyyDzZ9bbLZgOw@mail.gmail.com>
Message-ID: <rt-4.4.3-24012-1576536955-1590.1158450-37-0@icann.org>
To: barryleiba@computer.org, kaduk@mit.edu, rsalz@akamai.com
CC: tls-reg-review@ietf.org, iesg@ietf.org, ekr@rtfm.com
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
Date: Mon, 16 Dec 2019 22:55:56 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/8YJQhold-Qvavxu-zc_JMtY7Cp4>
Subject: [Tls-reg-review] [IANA #1158450] spelling change request in TLS Certificate Types registry

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
> >

[Tls-reg-review] spelling change request in TLS C… Benjamin Kaduk
Re: [Tls-reg-review] spelling change request in T… Salz, Rich
Re: [Tls-reg-review] spelling change request in T… Barry Leiba
[Tls-reg-review] [IANA #1158450] spelling change … Amanda Baber via RT
Re: [Tls-reg-review] [IANA #1158450] spelling cha… Salz, Rich
[Tls-reg-review] [IANA #1158450] spelling change … Amanda Baber via RT