RFC Errata
RFC 8599, "Push Notification with the Session Initiation Protocol (SIP)", May 2019
Source of RFC: sipcore (art)See Also: RFC 8599 w/ inline errata
Errata ID: 8136
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Babar
Date Reported: 2024-10-12
Verifier Name: RFC Editor
Date Verified: 2024-10-24
Section 4.1.4 says:
Example of a SIP REGISTER response including a 'sip.pnsreg' media feature tag and a 'sip.pnsreq' feature-capability indicator: If the UA receives a 2xx response to the REGISTER request that contains a Feature-Caps header field with a 'sip.pnsreq' feature- capability indicator, If the UA receives a 2xx response to the REGISTER request that does not contain a Feature-Caps header field with a 'sip.pnsreq' feature- capability indicator,
It should say:
Example of a SIP REGISTER response including a 'sip.pnsreg' media feature tag and a 'sip.pnsreg' feature-capability indicator: If the UA receives a 2xx response to the REGISTER request that contains a Feature-Caps header field with a 'sip.pnsreg' feature- capability indicator, If the UA receives a 2xx response to the REGISTER request that does not contain a Feature-Caps header field with a 'sip.pnsreg' feature- capability indicator,
Notes:
“sip.pnsreq” should be “sip.pnsreg” in the three sentences in this report.