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

[Randall Gellens <[e-mail]>]

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 
>> <[e-mail]> 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 <[e-mail]>
>>
>> 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
>>