RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

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

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

Errata ID: 1008

Status: Verified
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2007-09-09

Throughout the document, when it says:

Author*                      Informational                      [Page X]

It should say:

Camarillo & Blanco           Informational                      [Page X]

Status: Reported (1)

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

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

Errata ID: 4649

Status: Reported
Type: Technical

Reported By: Brett Tate
Date Reported: 2016-03-29

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



Search RFCs
Advanced Search
×