RFC Errata
Found 2 records.
Status: Verified (1)
RFC 8599, "Push Notification with the Session Initiation Protocol (SIP)", May 2019
Source of RFC: sipcore (art)
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.
Status: Reported (1)
RFC 8599, "Push Notification with the Session Initiation Protocol (SIP)", May 2019
Source of RFC: sipcore (art)
Errata ID: 7136
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Alex Vasilchenko
Date Reported: 2022-09-18
Section 1; 4.1.3 says:
In section 1. Introduction it says: Example of a SIP REGISTER request in the flow above: REGISTER sip:alice@example.com SIP/2.0 (the rest part of the message is omitted) In section 4.1.4. Sending Binding-Refresh Requests Using Non-push Mechanism it says: Example of a SIP REGISTER request including a 'sip.pnsreg' media feature tag: REGISTER sip:alice@example.com SIP/2.0 (the rest part of the message is omitted)
It should say:
In section 1. Introduction it should be: Example of a SIP REGISTER request in the flow above: REGISTER sip:example.com SIP/2.0 (the rest part of the message is omitted) In section 4.1.4. Sending Binding-Refresh Requests Using Non-push Mechanism it should be: Example of a SIP REGISTER request including a 'sip.pnsreg' media feature tag: REGISTER sip:example.com SIP/2.0 (the rest part of the message is omitted)
Notes:
The error is in R-URI:
REGISTER sip:alice@example.com SIP/2.0
It should be:
REGISTER sip:example.com SIP/2.0
According to RFC3261 - 10.2 Constructing the REGISTER Request - Request-URI: The Request-URI names the domain of the location service for which the registration is meant (for example, "sip:chicago.com"). The "userinfo" and "@" components of the SIP URI MUST NOT be present.