RFC 8599, "Push Notification with the Session Initiation Protocol (SIP)", May 2019

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.

Report New Errata