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

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 21 November 2019 03:00 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23B51120840 for <uta@ietfa.amsl.com>; Wed, 20 Nov 2019 19:00:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, 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 (1024-bit key) header.d=isode.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 xAD9ar_4BMx7 for <uta@ietfa.amsl.com>; Wed, 20 Nov 2019 19:00:10 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id CB8B51207FF for <uta@ietf.org>; Wed, 20 Nov 2019 19:00:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1574305209; d=isode.com; s=june2016; i=@isode.com; bh=zCYMQtlMvhlXpZcUaiG9SSP36w+EaTfsPUtJFOYy/Ts=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Idd23F/GgW5KIaU+ZE2P6edGq8Pw6sdHdDL0kdUNiq0ZnCHK+vFPIOHXtNmic29spSd9ts nAk1Cag71EjQkid0ztaiUkWA4on5fGJF3JoqoXY2HXjl0IbfRvM6e+3oxe2ghsvOCJk7He l8NwI6amiMKVc5roo5AkN/uOUjFswEE=;
Received: from [31.133.147.241] (dhcp-93f1.meeting.ietf.org [31.133.147.241]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <XdX9uABbdxf1@waldorf.isode.com>; Thu, 21 Nov 2019 03:00:08 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (16G102)
In-Reply-To: <CAL0qLwabHZQgAQVbQmOZLijybcUBVyQstKf=iXh7O1cwy0t=kw@mail.gmail.com>
Date: Thu, 21 Nov 2019 11:00:05 +0800
Cc: Valery Smyslov <valery@smyslov.net>, uta@ietf.org, Leif Johansson <leifj@sunet.se>, Scott Kitterman <scott@kitterman.com>
Message-Id: <160065F4-FE47-411A-8395-355159BD12F9@isode.com>
References: <20191031062109.222B9F40722@rfc-editor.org> <062701d5a009$e2eb9f20$a8c2dd60$@smyslov.net> <063401d5a00c$49396e90$dbac4bb0$@smyslov.net> <CAL0qLwabHZQgAQVbQmOZLijybcUBVyQstKf=iXh7O1cwy0t=kw@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="Apple-Mail-828931C1-2378-4836-AAE2-AAE97703C795"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/fdCGfs6wO0jIlj3HndwOdGfZnX0>
Subject: Re: [Uta] [Technical Errata Reported] RFC8460 (5889)
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 03:00:12 -0000

> On 21 Nov 2019, at 10:13, Murray S. Kucherawy <superuser@gmail.com> wrote:
> 
> 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.

Right. If there is urgency in fixing this, I can also do an IESG management item to get IESG to approve 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
>>