Re: [Uta] FW: [Technical Errata Reported] RFC8460 (5889)
"Murray S. Kucherawy" <superuser@gmail.com> Thu, 21 November 2019 02:13 UTC
Return-Path: <superuser@gmail.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 C467212018B for <uta@ietfa.amsl.com>; Wed, 20 Nov 2019 18:13:32 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 (2048-bit key) header.d=gmail.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 CZSz3koCv-FX for <uta@ietfa.amsl.com>; Wed, 20 Nov 2019 18:13:29 -0800 (PST)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91B52120077 for <uta@ietf.org>; Wed, 20 Nov 2019 18:13:29 -0800 (PST)
Received: by mail-vs1-xe29.google.com with SMTP id u6so1192822vsp.4 for <uta@ietf.org>; Wed, 20 Nov 2019 18:13:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WDz1yslGSMaPhkvWpMpL00YxKzsxUDbTfrhJPaKy3nA=; b=hPrk+QqmtG2ss8Nywl9f6szWZtahpEe1bz7LjxaFD33REnIHayLtp0Gi0P4BZ8lXwN QozgR0T3fVs65oBqMTA1nP4iKgxvz48xHn3LYVevn093SWQ/oqsd6Zv8Uw2ZVMwj3UtU wKfHe32IKsvYjDU7A0e90MaQscEfS+xTr2L1Xba5FhqOUPautkvgdQN0by4iqcZahD+X WBQUqL8lb561Yp8ACZW6KAXcac5OzM817erH2pBk0sOvxJL/TkUOlXXg6XLhCTYeVuIN X9KNI9MGSq7YdjcVsBQ8YXGTwQCUnUtjQRTWCIE1LfsrxSMT23ehtzsOQ8SnawHmSsUq 0j9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WDz1yslGSMaPhkvWpMpL00YxKzsxUDbTfrhJPaKy3nA=; b=XBtAFNMQBX5b11XuVWFXElgiLPZWTnyIPdtN3bbywnHwwYNbkKJLI/qirwvDm5FQtZ DFdQFrHXhXQqaGgDxBh+ZgyjNprs7TXGPKmf7hmS5OgyUyIyS/bYkqKTT6obOPRRIDbu 9AhqKxmy+hS/TB1m6TEsmgqiJR1+zM+f900vAkR/pruPHyV/FxfJC2WoYR07JpWQb0Qs hBnusQa5brDKFB+EOfsHuPrKbF8QbjoXOQN3TWtpwkDw1s+P+UDYZ7VMQ541hcUfy7vO WbAcmaoJRsdSyxAj3tOgwhhTt7WQe0hHyV+MDU8c0K7o5wqXnOnXbrKAY94voQMvEeiN adAw==
X-Gm-Message-State: APjAAAWTM5EDNvWkSr/1D/yyggEQTwElte2rK81R3UI5zsQ+Lht+Ygbs x+fVBaGKbVwTkBcPQbUtA0kpuv9zUE5Kq8m8mcF9dTMM
X-Google-Smtp-Source: APXvYqzu4G6LuzNAWq4YtY6F9K4ENqe+WZlDx+bByowMFqu1wuENDFi3/i6qC5dkMq0+aJlEbJAQJtNvIeDSh9Eea0c=
X-Received: by 2002:a67:e24b:: with SMTP id w11mr4323648vse.7.1574302408524; Wed, 20 Nov 2019 18:13:28 -0800 (PST)
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)
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 02:13:33 -0000
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