Search RFCs

RFC Editor

Found 4 records.

Status:Verified (3)

RFC 7852, "Additional Data Related to an Emergency Call", July 2016

Errata ID:6849
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: James Benner
Date Reported: 2022-02-12
Verifier Name: Murray Kucherawy
Date Verified: 2022-05-16

Section 11.7 says:

Example(s):  TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90      00

It should say:

Example(s):  TEL;VALUE=uri;TYPE="main-number,voice";PREF=1:tel:+1-418-656-90      00

Notes:

The type value is specified as "main-number" but in the example is simply "main".

Errata ID:7679
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Tom Hsu
Date Reported: 2023-10-16
Verifier Name: Murray Kucherawy
Date Verified: 2023-11-07

Section 6.1 says:

An example   Call-Info header field for this would be:   Call-Info:  https://www.example.com/23sedde3;       purpose="EmergencyCallData.ProviderInfo"

It should say:

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.

Errata ID:8462
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Randall Gellens
Date Reported: 2025-06-16
Verifier Name: Andy Newton
Date Verified: 2025-06-17

Section 7 says:

<svc:ServiceType>VOIP</svc:ServiceType>

It should say:

<svc:ServiceType>OTT</svc:ServiceType>

Notes:

The value "VOIP" is not registered. The value "OTT" seems appropriate for VoIP providers.

Status:Reported (1)

RFC 7852, "Additional Data Related to an Emergency Call", July 2016

Errata ID:8519
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Robert Stepanek
Date Reported: 2025-07-23

Section Appendix A says:

     <!--       6.1.3     -->     <xs:element name="source">       <xs:complexType>         <xs:sequence>           <xs:element name="parameters">

It should say:

     <!--       6.1.3     -->     <xs:element name="source">       <xs:complexType>         <xs:sequence>           <xs:element name="parameters" minOccurs="0">

Notes:

The XML schema in Appendix A is based on the Relax NG schema defined in RFC 6351. There already is a verified errata 2994 for RFC 6351 which updates the Relax NG schema to define the parameters of the SOURCE property to be optional. The XML schema in RFC 7852 should be updated accordingly.

Note that RFC 7852, Section 11.6. registers the XML schema in the IANA XML Registry, so the XML schema at IANA should be updated as well.

The contents of this errata were originally highlighted by John Scott on the vcarddav and the ecrit mailing lists. See https://mailarchive.ietf.org/arch/msg/ecrit/JPCturATh0WN1rQfyF4M6EAkar0/

Errata for RFC 6351: https://www.rfc-editor.org/errata/eid2994
IANA XML Registry: https://www.iana.org/assignments/xml-registry/xml-registry.xhtml
vCard 4.0 XML Schema at IANA: https://www.iana.org/assignments/xml-registry/schema/vcard-4.0.xsd

Report New Errata