Re: [Ecrit] [Editorial Errata Reported] RFC8148 (6500)
Randall Gellens <rg+ietf@coretechnologyconsulting.com> Mon, 29 March 2021 16:59 UTC
Return-Path: <rg+ietf@coretechnologyconsulting.com>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B74E3A1AE5 for <ecrit@ietfa.amsl.com>; Mon, 29 Mar 2021 09:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 RhrABkiTWBPV for <ecrit@ietfa.amsl.com>; Mon, 29 Mar 2021 09:59:21 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 4FBF13A1AEA for <ecrit@ietf.org>; Mon, 29 Mar 2021 09:59:21 -0700 (PDT)
Received: from [169.254.190.213] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Mon, 29 Mar 2021 09:59:15 -0700
From: Randall Gellens <rg+ietf@coretechnologyconsulting.com>
To: Lars Eggert <lars@eggert.org>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, br@brianrosen.net, Hannes.Tschofenig@gmx.net, superuser@gmail.com, francesca.palombini@ericsson.com, allison.mankin@gmail.com, roger.marshall@comtechtel.com, ecrit@ietf.org
Date: Mon, 29 Mar 2021 09:59:11 -0700
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <A53AF4D5-9739-49CC-9D41-528B90A35711@coretechnologyconsulting.com>
In-Reply-To: <309D6418-5163-471C-A4CE-203D1DACB627@eggert.org>
References: <F01FF77E-FD85-48E3-B9C3-3C40D8B3C157@coretechnologyconsulting.com> <309D6418-5163-471C-A4CE-203D1DACB627@eggert.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/2MS2WGxHEsmn7lP-i9bAAOeZLcU>
Subject: Re: [Ecrit] [Editorial Errata Reported] RFC8148 (6500)
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ecrit/>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Mar 2021 16:59:26 -0000
My point is just that I do not know if an errata is sufficient to cause IANA to make the change. If it is, that's fine; if it isn't, what is the procedure? An email to IANA perhaps? --Randall On 29 Mar 2021, at 9:35, Lars Eggert wrote: > I didn’t see the change controller listed on the IANA page, which is > why I filed the errata. > > -- > Sent from a mobile device; please excuse typos. > >> On Mar 29, 2021, at 18:58, Randall Gellens >> <rg+ietf@coretechnologyconsulting.com> wrote: >> >> This does seem like an obvious typo that was missed before >> publication. I'm not sure if an errata is the best way of addressing >> it, rather than having IANA update the MIME Media Type Registration >> for application/EmergencyCall.VEDS+xml. >> >> --Randall >> >>> On 29 Mar 2021, at 1:37, RFC Errata System wrote: >>> >>> The following errata report has been submitted for RFC8148, >>> "Next-Generation Vehicle-Initiated Emergency Calls". >>> >>> -------------------------------------- >>> You may review the report below and at: >>> https://www.rfc-editor.org/errata/eid6500 >>> >>> -------------------------------------- >>> Type: Editorial >>> Reported by: Lars Eggert <lars@eggert.org> >>> >>> Section: 14.1 >>> >>> Original Text >>> ------------- >>> Change controller: The IESG <ietf@ietf.org> >>> >>> >>> Corrected Text >>> -------------- >>> Change controller: The IESG <iesg@ietf.org> >>> >>> >>> Notes >>> ----- >>> The current text has the email address of the "IETF discuss" list >>> for the IESG, which is incorrect. >>> >>> 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. >>> >>> -------------------------------------- >>> RFC8148 (draft-ietf-ecrit-car-crash-23) >>> -------------------------------------- >>> Title : Next-Generation Vehicle-Initiated Emergency >>> Calls >>> Publication Date : May 2017 >>> Author(s) : R. Gellens, B. Rosen, H. Tschofenig >>> Category : PROPOSED STANDARD >>> Source : Emergency Context Resolution with Internet >>> Technologies >>> Area : Applications and Real-Time >>> Stream : IETF >>> Verifying Party : IESG
- Re: [Ecrit] [Editorial Errata Reported] RFC8148 (… Randall Gellens
- Re: [Ecrit] [Editorial Errata Reported] RFC8148 (… Lars Eggert
- Re: [Ecrit] [Editorial Errata Reported] RFC8148 (… Randall Gellens
- Re: [Ecrit] [Editorial Errata Reported] RFC8148 (… Brian Rosen
- Re: [Ecrit] [Editorial Errata Reported] RFC8148 (… Brian Rosen
- Re: [Ecrit] [Editorial Errata Reported] RFC8148 (… Randall Gellens
- Re: [Ecrit] [Editorial Errata Reported] RFC8148 (… Brian Rosen
- Re: [Ecrit] [Editorial Errata Reported] RFC8148 (… Lars Eggert