Re: [Ecrit] [Editorial Errata Reported] RFC7852 (7679)

"Murray S. Kucherawy" <superuser@gmail.com> Tue, 07 November 2023 14:51 UTC

MIME-Version: 1.0
References: <20231016235626.6BC8913BB494@rfcpa.amsl.com> <6DDA34C1-A89E-4834-A603-9F21E4C9425D@amsl.com> <CBFE0162-2A24-4327-90B5-478130404D8C@randy.pensive.org>
In-Reply-To: <CBFE0162-2A24-4327-90B5-478130404D8C@randy.pensive.org>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 07 Nov 2023 15:51:26 +0100
Message-ID: <CAL0qLwaFuWDgeeeFAHP2MqA=9Hu5kTSOHjLiWjvKrgZHXUM4Hg@mail.gmail.com>
To: Randall Gellens <rg+ietf@randy.pensive.org>
Cc: Rebecca VanRheenen <rvanrheenen@amsl.com>, tom.hsu@nokia.com, br@brianrosen.net, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, rmarshall@telecomsys.com, a.james.winterbottom@gmail.com, ecrit@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary="00000000000088fd100609911bda"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/wXNqL8dLME8DW68Yf427u9eRKL4>
Subject: Re: [Ecrit] [Editorial Errata Reported] RFC7852 (7679)
Precedence: list

Done.

-MSK

On Wed, Nov 1, 2023 at 11:38 PM Randall Gellens <rg+ietf@randy.pensive.org>
wrote:

> I've reviewed the errata and verified it is correct. However, I do not
> have an rfc-editor login so I am unable to set the status.
>
> --Randall
>
> On 20 Oct 2023, at 11:00, Rebecca VanRheenen wrote:
>
> Hi Murray,
>
> We are unable to verify this erratum that the submitter marked as
> editorial.
> Please note that we have changed the “Type” of the following errata
> report to “Technical”. As Stream Approver, please review and set the
> Status and Type accordingly (see the definitions at
> https://www.rfc-editor.org/errata-definitions/).
>
> You may review the report at:
> https://www.rfc-editor.org/errata/eid 7679
>
> Please see https://www.rfc-editor.org/how-to-verify/ for further
> information on how to verify errata reports.
>
> Further information on errata can be found at:
> https://www.rfc-editor.org/errata.php.
>
> Thank you.
>
> RFC Editor/rv
>
> On Oct 16, 2023, at 4:56 PM, RFC Errata System rfc-editor@rfc-editor.org
> wrote:
>
> The following errata report has been submitted for RFC7852,
> "Additional Data Related to an Emergency Call".
> ------------------------------
>
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7679
> ------------------------------
>
> Type: Editorial
> Reported by: Tom Hsu tom.hsu@nokia.com
>
> Section: 6.1
> Original Text
>
> An example
> Call-Info header field for this would be:
>
> Call-Info: https://www.example.com/23sedde3;
> purpose="EmergencyCallData.ProviderInfo"
> Corrected Text
>
> An example
> Call-Info header field for this would be:
>
> Call-Info: https://www.example.com/23sedde3;
> purpose=EmergencyCallData.ProviderInfo
> Notes
>
> Remove double quote on purpose attribute. It's a token type instead of
> "String" type.
> 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.
> ------------------------------
> RFC7852 (draft-ietf-ecrit-additional-data-38)
>
> Title : Additional Data Related to an Emergency Call
> Publication Date : July 2016
> Author(s) : R. Gellens, B. Rosen, H. Tschofenig, R. Marshall, J.
> Winterbottom
> Category : PROPOSED STANDARD
> Source : Emergency Context Resolution with Internet Technologies
> Area : Applications and Real-Time
> Stream : IETF
> Verifying Party : IESG
>
>

[Ecrit] [Editorial Errata Reported] RFC7852 (7679) RFC Errata System
Re: [Ecrit] [Editorial Errata Reported] RFC7852 (… Rebecca VanRheenen
Re: [Ecrit] [Editorial Errata Reported] RFC7852 (… Randall Gellens
Re: [Ecrit] [Editorial Errata Reported] RFC7852 (… Murray S. Kucherawy