Found 2 records.

Status: Verified (1)

RFC 3515, "The Session Initiation Protocol (SIP) Refer Method", April 2003

Note: This RFC has been updated by RFC 7647, RFC 8217

Errata ID: 4898
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Marianne MOHALI
Date Reported: 2017-01-03
Verifier Name: Orie Steele
Date Verified: 2024-03-29

Section 2.1 says:

Refer-To: <sip:bob@biloxi.example.net?Accept-Contact=sip:bobsdesk.
       biloxi.example.net&Call-ID%3D55432%40alicepc.atlanta.example.com>

It should say:

Refer-To: <sip:bob@biloxi.example.net?Accept-Contact=sip:bobsdesk.
       biloxi.example.net&Call-ID=55432%40alicepc.atlanta.example.com>

Notes:

The "=" between the header name (hname) and the value (hvalue) in the headers component of the URI does not have to be in the percent-coded format as part of the ABNF of the headers component defined in RFC3261:
sip:user:password@host:port;uri-parameters?headers
headers = "?" header *( "&" header )
header = hname "=" hvalue
hname = 1*( hnv-unreserved / unreserved / escaped )
hvalue = *( hnv-unreserved / unreserved / escaped )
hnv-unreserved = "[" / "]" / "/" / "?" / ":" / "+" / "$"

Status: Reported (1)

RFC 3515, "The Session Initiation Protocol (SIP) Refer Method", April 2003

Note: This RFC has been updated by RFC 7647, RFC 8217

Errata ID: 4652
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Brett Tate
Date Reported: 2016-03-30

Section 2.1 says:

The Refer-To header field MAY be encrypted as part of end-to-end
encryption.

It should say:

If the URI contains a comma, question mark or semicolon, the URI
MUST be enclosed in angle brackets (< and >).

The Refer-To header field MAY be encrypted as part of end-to-end
encryption.

Notes:

If addr-spec is used when there are parameters, it is ambiguous if the parameters are URI parameters or header parameters. For consistency with RFC 3261 section 20, the same bracket rule is indicated even if comma and question mark do not cause an issue.

Report New Errata