RFC 5360, "A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)", October 2008

Note: This RFC has been updated by RFC 8217

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

Section 5.9.3 says:

The following is an example of a Permission-Missing header field:

It should say:

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

The following is an example of a Permission-Missing header field:

Notes:

Comma and semicolon can cause decode ambiguities when the header contains addr-spec values instead of name-addr values. For consistency with RFC 3261 section 20, the same bracket rule is indicated to resolve the ambiguity.

Report New Errata