From nobody Mon Mar 29 10:05:33 2021 Return-Path: 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 1393B3A1B0F for ; Mon, 29 Mar 2021 10:05:31 -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 2_2alsmTwgIz for ; Mon, 29 Mar 2021 10:05:26 -0700 (PDT) Received: from mail-qv1-xf33.google.com (mail-qv1-xf33.google.com [IPv6:2607:f8b0:4864:20::f33]) (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 323DB3A1B17 for ; Mon, 29 Mar 2021 10:05:25 -0700 (PDT) Received: by mail-qv1-xf33.google.com with SMTP id q9so6795694qvm.6 for ; Mon, 29 Mar 2021 10:05:25 -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=ZTioDTSCuBYbZdySZQU+pWWbFvaRHyWvXFoN5Mab1ks=; b=J4gB0HTj6pDl3XePHTZkqZVLc7/ahvRim5OhKScHq2DV8R+IFmbZw/GhGFg1v+uxhC BkYxtuWVlp7Sn+xKqGarUPFXLUwV4xHYWrupQVzyExoslXOgQtyJQEA7gyLa+q4tZmed 6a8GO5z/7RkKBm5odt3qsAVrdraKlG2+xb1//Ks9zcefdOVV1UtMSH6vlCTUwXF2S5P3 S4uvrDg2OSiiQz/vWOCZytpf3F72m/4dV5L/fi7C36exNh4VV+TnElQ1npCJc+1rI4hX hTYCNMBCEC9xMlFg3pazOZ9gY6NZIvyebeudEA1VpSo8rmcymhImyM7/ziteoCG5Aq5L Nsaw== 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=ZTioDTSCuBYbZdySZQU+pWWbFvaRHyWvXFoN5Mab1ks=; b=jhIVWkr1f3rZHR1WNZVemQGEcTv7QVJZNF3i4jvfhmkQAd7Aj1ROE2wGiE31a1kLZ7 UdkQ3BiaQ1oZg2SK3BbuyvTWzkONGLaTGnNl+pl/o3RSW513y7spf29R7volubQlxO+p tQ0hnyFrGAsikn7M0YI9fL3KcN2dxkTHUBpHjQ0is/hODVLC52QJOzIl+OsRBV8bV+Hy KMMk1wlIAmAp3HlwQiA8krPxdKfK8nLCl5bJVAZMZKMbHRgM6q8xlh1uxewrIok0eEEK oo8G+4NSWz+7wCMG3JriQbUVCoTKKWyG4o9nayhummsPIEDzVOKOLAwUr6GpVgqG4p/U 4dnA== X-Gm-Message-State: AOAM5302CDOOTFIgqbC0awyea+3L3FgcaRh3REv1AmOg8f2UyZoT4uwz Jo8BtbDa5RzpE65zssuzl4iB2A== X-Google-Smtp-Source: ABdhPJx4Uu23dBMY5qAr1VVFZAwMBvEgZh2L0gtURmdb2hjF8quka4N7V39wn1NDO9Utmbh0LGpFMg== X-Received: by 2002:ad4:540a:: with SMTP id f10mr26042442qvt.26.1617037523242; Mon, 29 Mar 2021 10:05:23 -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 k28sm13810136qki.101.2021.03.29.10.05.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Mar 2021 10:05:22 -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 In-Reply-To: Date: Mon, 29 Mar 2021 13:05:21 -0400 Cc: Lars Eggert , RFC Errata System , Hannes.Tschofenig@gmx.net, "Murray S. Kucherawy" , Francesca Palombini , Allison Mankin , Roger Marshall , ecrit@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <5C7F3288-ADC1-42E0-AC82-EE10F8734140@brianrosen.net> References: <309D6418-5163-471C-A4CE-203D1DACB627@eggert.org> To: Randall Gellens X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: Re: [Ecrit] [Editorial Errata Reported] RFC8148 (6500) X-BeenThere: ecrit@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2021 17:05:31 -0000 I=E2=80=99ll ask. This is a simple problem. Brian > On Mar 29, 2021, at 12:59 PM, Randall Gellens = wrote: >=20 > 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? >=20 > --Randall >=20 > On 29 Mar 2021, at 9:35, Lars Eggert wrote: >=20 >> I didn=E2=80=99t see the change controller listed on the IANA page, = which is why I filed the errata. >>=20 >> --=20 >> Sent from a mobile device; please excuse typos. >>=20 >>> On Mar 29, 2021, at 18:58, Randall Gellens = wrote: >>>=20 >>> =EF=BB=BFThis 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. >>>=20 >>> --Randall >>>=20 >>>> On 29 Mar 2021, at 1:37, RFC Errata System wrote: >>>>=20 >>>> The following errata report has been submitted for RFC8148, >>>> "Next-Generation Vehicle-Initiated Emergency Calls". >>>>=20 >>>> -------------------------------------- >>>> You may review the report below and at: >>>> https://www.rfc-editor.org/errata/eid6500 >>>>=20 >>>> -------------------------------------- >>>> Type: Editorial >>>> Reported by: Lars Eggert >>>>=20 >>>> Section: 14.1 >>>>=20 >>>> Original Text >>>> ------------- >>>> Change controller: The IESG >>>>=20 >>>>=20 >>>> Corrected Text >>>> -------------- >>>> Change controller: The IESG >>>>=20 >>>>=20 >>>> Notes >>>> ----- >>>> The current text has the email address of the "IETF discuss" list = for the IESG, which is incorrect. >>>>=20 >>>> 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. >>>>=20 >>>> -------------------------------------- >>>> 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