Re: [Ecrit] [Editorial Errata Reported] RFC8148 (6500)

Randall Gellens <rg+ietf@coretechnologyconsulting.com> Mon, 29 March 2021 15:58 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 0FEC83A194E for <ecrit@ietfa.amsl.com>; Mon, 29 Mar 2021 08:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_FORGED_RELAY_MUA_TO_MX=0.01, 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 tPpPH8tgJVv7 for <ecrit@ietfa.amsl.com>; Mon, 29 Mar 2021 08:58:30 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id ECFC13A1949 for <ecrit@ietf.org>; Mon, 29 Mar 2021 08:58:29 -0700 (PDT)
Received: from [99.111.97.181] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Mon, 29 Mar 2021 08:58:24 -0700
From: "Randall Gellens" <rg+ietf@coretechnologyconsulting.com>
To: "RFC Errata System" <rfc-editor@rfc-editor.org>
Cc: br@brianrosen.net, Hannes.Tschofenig@gmx.net, superuser@gmail.com, francesca.palombini@ericsson.com, allison.mankin@gmail.com, roger.marshall@comtechtel.com, lars@eggert.org, ecrit@ietf.org
Date: Mon, 29 Mar 2021 08:58:28 -0700
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <F01FF77E-FD85-48E3-B9C3-3C40D8B3C157@coretechnologyconsulting.com>
In-Reply-To: <20210329083753.E28B4F407C4@rfc-editor.org>
References: <20210329083753.E28B4F407C4@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/83p80ysjD6vtcanpYlOUJ4ZnAGs>
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 15:58:35 -0000

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