RFC Errata
Found 2 records.
Status: Verified (2)
RFC 7852, "Additional Data Related to an Emergency Call", July 2016
Source of RFC: ecrit (art)
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.