Re: [Uta] FW: [Technical Errata Reported] RFC8460 (5889)

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 21 November 2019 02:13 UTC

MIME-Version: 1.0
References: <20191031062109.222B9F40722@rfc-editor.org> <062701d5a009$e2eb9f20$a8c2dd60$@smyslov.net> <063401d5a00c$49396e90$dbac4bb0$@smyslov.net>
In-Reply-To: <063401d5a00c$49396e90$dbac4bb0$@smyslov.net>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 21 Nov 2019 10:13:16 +0800
Message-ID: <CAL0qLwabHZQgAQVbQmOZLijybcUBVyQstKf=iXh7O1cwy0t=kw@mail.gmail.com>
To: Valery Smyslov <valery@smyslov.net>
Cc: uta@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>, Leif Johansson <leifj@sunet.se>, Scott Kitterman <scott@kitterman.com>
Content-Type: multipart/alternative; boundary="000000000000d449420597d1d736"
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/LoLySq-mJIi_5zMKMWf9gLuvm-g>
Subject: Re: [Uta] FW: [Technical Errata Reported] RFC8460 (5889)
Precedence: list

I would guess we can't rectify this oversight via the errata system.  What
got IETF Review was the need for the registration, but not the registration
itself.

I imagine this should either be done through DISPATCH (which is chartered
to do minor housekeeping things like this) or through an AD-sponsored
document that contains only the registration.

-MSK


On Thu, Nov 21, 2019 at 9:37 AM Valery Smyslov <valery@smyslov.net> wrote:

> Hi,
>
> this is an erratum reported by Scott Kitterman about the missing IANA
> registration item for DKIM in RFC8460. The chairs want to know the WG
> opinion on this.
>
> Regards,
> Valery (for the chairs)
>
> -----Original Message-----
> From: RFC Errata System <rfc-editor@rfc-editor.org>
> Sent: Thursday, October 31, 2019 9:21 AM
> To: dmargolis@google.com; alex_brotman@comcast.com; prbinu@yahoo.com;
> janet.jones@microsoft.com; risher@google.com; barryleiba@computer.org;
> aamelnikov@fastmail.fm; adam@nostrum.com; leifj@sunet.se;
> valery@smyslov.net
> Cc: scott@kitterman.com; uta@ietf.org; rfc-editor@rfc-editor.org
> Subject: [Technical Errata Reported] RFC8460 (5889)
>
> The following errata report has been submitted for RFC8460, "SMTP TLS
> Reporting".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid5889
>
> --------------------------------------
> Type: Technical
> Reported by: Scott Kitterman <scott@kitterman.com>
>
> Section: 6.7
>
> Original Text
> -------------
> Item is missing entirely
>
> Corrected Text
> --------------
> 6.7 DKIM Service Type
>
> This document registers a new DKIM Service Type in the DomainKeys
> Identified Mail (DKIM) Parameters registry:
>
> Service Type name: tlsrpt
>
> Reference: RFC 8460
>
> Status Active
>
> Notes
> -----
> The new service type is discussed in Section 3, so it should have been
> added to the registry.  It's an IETF Review required registry, not
> Specification Required, so this can (and should) be addressed in terms at
> least of the registry now.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please use
> "Reply All" to discuss whether it should be verified or rejected. When a
> decision is reached, the verifying party can log in to change the status
> and edit the report, if necessary.
>
> --------------------------------------
> RFC8460 (draft-ietf-uta-smtp-tlsrpt-23)
> --------------------------------------
> Title               : SMTP TLS Reporting
> Publication Date    : September 2018
> Author(s)           : D. Margolis, A. Brotman, B. Ramakrishnan, J. Jones,
> M. Risher
> Category            : PROPOSED STANDARD
> Source              : Using TLS in Applications
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG
>
>

[Uta] FW: [Technical Errata Reported] RFC8460 (58… Valery Smyslov
Re: [Uta] FW: [Technical Errata Reported] RFC8460… Murray S. Kucherawy
Re: [Uta] [Technical Errata Reported] RFC8460 (58… Alexey Melnikov