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

Randall Gellens <rg+ietf@coretechnologyconsulting.com> Mon, 29 March 2021 20: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 531F43A216F for <ecrit@ietfa.amsl.com>; Mon, 29 Mar 2021 13:59:17 -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 7bAXxiYw3LAg for <ecrit@ietfa.amsl.com>; Mon, 29 Mar 2021 13:59:12 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5F04F3A216D for <ecrit@ietf.org>; Mon, 29 Mar 2021 13:59:12 -0700 (PDT)
Received: from [169.254.239.62] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Mon, 29 Mar 2021 13:59:06 -0700
From: "Randall Gellens" <rg+ietf@coretechnologyconsulting.com>
To: "Brian Rosen" <br@brianrosen.net>
Cc: "Lars Eggert" <lars@eggert.org>, "RFC Errata System" <rfc-editor@rfc-editor.org>, Hannes.Tschofenig@gmx.net, "Murray S. Kucherawy" <superuser@gmail.com>, "Francesca Palombini" <francesca.palombini@ericsson.com>, "Allison Mankin" <allison.mankin@gmail.com>, "Roger Marshall" <roger.marshall@comtechtel.com>, ecrit@ietf.org
Date: Mon, 29 Mar 2021 13:59:10 -0700
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <1C90213B-B0C4-469B-8778-1DA0422F7384@coretechnologyconsulting.com>
In-Reply-To: <362A1747-7C26-45CC-AF70-5C94B063D961@brianrosen.net>
References: <F01FF77E-FD85-48E3-B9C3-3C40D8B3C157@coretechnologyconsulting.com> <309D6418-5163-471C-A4CE-203D1DACB627@eggert.org> <A53AF4D5-9739-49CC-9D41-528B90A35711@coretechnologyconsulting.com> <5C7F3288-ADC1-42E0-AC82-EE10F8734140@brianrosen.net> <362A1747-7C26-45CC-AF70-5C94B063D961@brianrosen.net>
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/5X_WhCepJJ8nS5S40WLq4z4weTk>
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 20:59:17 -0000

Great, thanks.

--Randall

On 29 Mar 2021, at 13:55, Brian Rosen wrote:

> Approve the errata.  IANA will fix it.  I asked, they responded 
> promptly.
>
> Brian
>
>
>> On Mar 29, 2021, at 1:05 PM, Brian Rosen <br@brianrosen.net> wrote:
>>
>> I’ll ask.  This is a simple problem.
>>
>> Brian
>>
>>
>>> On Mar 29, 2021, at 12:59 PM, Randall Gellens 
>>> <rg+ietf@coretechnologyconsulting.com> wrote:
>>>
>>> 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
>>