Errata Search
RFC Number:		Errata ID:
Source of RFC		Status:	All/Any Verified+Reported Verified Reported Held for Document Update Rejected
Area Acronym:	All/Any app art gen int ops rai rtg sec tsv wit	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy Editorial	Date Submitted:
Summary Table Full Records

RFC 5002, "The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)", August 2007

Note: This RFC has been updated by RFC 8217

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: gen

---

Errata ID: 4649
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Brett Tate
Date Reported: 2016-03-29
Held for Document Update by: Lars Eggert
Date Held: 2023-08-11

Section 5 says:

The following is an example of a P-Profile-Key header field that
contains a Wildcarded Public Service Identity:

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 P-Profile-Key header field that
contains a Wildcarded Public Service Identity:

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