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

Brian Rosen <br@brianrosen.net> Mon, 29 March 2021 20:55 UTC

Return-Path: <br@brianrosen.net>
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 381383A215F for <ecrit@ietfa.amsl.com>; Mon, 29 Mar 2021 13:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.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 eJSe2nqDyz9N for <ecrit@ietfa.amsl.com>; Mon, 29 Mar 2021 13:55:14 -0700 (PDT)
Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (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 B72803A215D for <ecrit@ietf.org>; Mon, 29 Mar 2021 13:55:14 -0700 (PDT)
Received: by mail-qv1-xf2f.google.com with SMTP id t5so7152594qvs.5 for <ecrit@ietf.org>; Mon, 29 Mar 2021 13:55:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NSmzAxsPnikPgQWAUmZgHGKE6dk7sO4ez1j0odd2sCM=; b=ihg1n+5cVt8y07a/ad+6H7v/9+T13KbXxSs5N6e6w5oSD+j8SvRvNbFagz5ZFd7cTq 8mCFdSm2ZMtHoT/Rw+ZrwKKy97OWDqc9gRtyOklXhZBpplEq8QhJxqY/NTu2cSdQ9Q0S iyrN4wkjSEitLTyHYnvXKjZgTLS4rXCogslQwzxKoYEvPAceWvpdVy7QHkxs4OEWRphg behEv+XVZxe+XswtHk3VqAoyMC0Ch9e5gR80hFIFYy7Wcops54BCpS3jwSC2SJFcZPBV qYWTSg+gAvUzJ0TPqYU5OBMv00vXQIQR98lsNQgeSOItn1lD74sl26TfWX8hnuX/DmLK MpJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NSmzAxsPnikPgQWAUmZgHGKE6dk7sO4ez1j0odd2sCM=; b=WESKnR+fbOAwtLs0bhALNfKaGNxR14nHmIkzW+cdtqwt4PuRke4u5H4A5JM9+730ib qKRgN4JR7AcXb5+2wMeE8afNfVgs0b4n39bHXhg058tiiYlHpsOgXQ8WGv5kc0dZEvaM GdGqjhI8QFtmx2BcOg/JCwb8sj5fpi1VrLirg8Cm0slD9waik7LB9PJgPMGSTjQhtPxc uCoRGP4d35KsBNWu6YLIjneufYsNKEXuE16ecOXH267R0IHvdEJ3xieZXDUzysN0mnx1 UZmV4Gtotvqa8Tkc//5pf8hrJZi6psmiKFRIbTlHhNZbpD2qgzcXlhdxm5KNIa6svYXM ajSA==
X-Gm-Message-State: AOAM532Q6eGSL30ecj+bJVNrSWmw78FqZRYaa3CGjAK8lfcAp9QAihIH 2j9AUxICrr39O5kJ7AdQJaOk2g==
X-Google-Smtp-Source: ABdhPJzIJjiZZNAqHS4UbwSuF24Qx3yhLVjCP+WduBf3HHTwyescOOLGeHPX+ejAK9NzGR6ZzBuV+Q==
X-Received: by 2002:a05:6214:18d2:: with SMTP id cy18mr27217378qvb.50.1617051313093; Mon, 29 Mar 2021 13:55:13 -0700 (PDT)
Received: from brians-mbp.lan (dynamic-acs-24-154-119-158.zoominternet.net. [24.154.119.158]) by smtp.gmail.com with ESMTPSA id u63sm11926755qtd.40.2021.03.29.13.55.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Mar 2021 13:55:12 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <5C7F3288-ADC1-42E0-AC82-EE10F8734140@brianrosen.net>
Date: Mon, 29 Mar 2021 16:55:10 -0400
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
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: Randall Gellens <rg+ietf@coretechnologyconsulting.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/AeSO_ggHyMwyoj4W_HUHpr2dAQ4>
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:55:20 -0000

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
>