RFC 3325, "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks", November 2002Source of RFC: sip (rai)
See Also: RFC 3325 w/ inline errata
Errata ID: 3744
Publication Format(s) : TEXT
Reported By: Brett Tate
Date Reported: 2013-10-08
Verifier Name: Richard Barnes
Date Verified: 2014-02-15
Section 9.1 says:
A P-Asserted-Identity header field value MUST consist of exactly one name-addr or addr-spec.
It should say:
A P-Asserted-Identity header field value MUST consist of exactly one name-addr or addr-spec. If the URI contains a comma, the URI MUST be enclosed in angle brackets (< and >).
While the P-Asserted-Identity and P-Preferred-Identity header fields have an ambiguity only for "," (not for ";" and "?"), we note that usage of ";" and "?" also must be enclosed in angle brackets to preserve consistency with the RFC 3261 section 20 bracket rule.