RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Reported (2)

RFC 5502, "The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem", April 2009

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

Errata ID: 4648

Status: Reported
Type: Technical

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

Section 6 says:

EQUAL, HCOLON, SEMI, name-addr, addr-spec, and generic-param are
defined in RFC 3261 [2].

It should say:

EQUAL, HCOLON, SEMI, name-addr, addr-spec, and generic-param are
defined in RFC 3261 [2].

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

Notes:

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

Errata ID: 4827

Status: Reported
Type: Technical

Reported By: Dale R. Worley
Date Reported: 2016-10-11

Section 6 says:

   sessioncase-param        = "sescase" EQUAL "orig" / "term"
   registration-state-param = "regstate" EQUAL "unreg" / "reg"

It should say:

   sessioncase-param        = "sescase" EQUAL ( "orig" / "term" )
   registration-state-param = "regstate" EQUAL ( "unreg" / "reg" )

Notes:

The ABNF as written does not take into account that concatenation binds tighter than alternation.

Report New Errata



Search RFCs
Advanced Search
×