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

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 16 October 2023 23:56 UTC

Return-Path: <wwwrun@rfcpa.amsl.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 680E9C1519BE for <ecrit@ietfa.amsl.com>; Mon, 16 Oct 2023 16:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AUXMYL-KJPuv for <ecrit@ietfa.amsl.com>; Mon, 16 Oct 2023 16:56:26 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 911C4C14CF12 for <ecrit@ietf.org>; Mon, 16 Oct 2023 16:56:26 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 6BC8913BB494; Mon, 16 Oct 2023 16:56:26 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: tom.hsu@nokia.com, rg+ietf@randy.pensive.org, br@brianrosen.net, Hannes.Tschofenig@gmx.net, rmarshall@telecomsys.com, a.james.winterbottom@gmail.com, ecrit@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231016235626.6BC8913BB494@rfcpa.amsl.com>
Date: Mon, 16 Oct 2023 16:56:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/hFzsdXwKw6aHTHYnT8hCZiGnaSE>
Subject: [Ecrit] [Editorial Errata Reported] RFC7852 (7679)
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Emergency Context Resolution with Internet Technologies <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, 16 Oct 2023 23:56:30 -0000

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