RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

RFC 7315, "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3GPP", July 2014

Note: This RFC has been updated by RFC 7913, RFC 7976

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

Errata ID: 4540
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Dongo Yi
Date Reported: 2015-11-20

Section 5.1 says: 

5.1. P-Associated-URI Header Syntax


   The syntax of the P-Associated-URI header field is described as
   follows:

         P-Associated-URI       = "P-Associated-URI" HCOLON
                                  [p-aso-uri-spec]
                                  *(COMMA p-aso-uri-spec)
         p-aso-uri-spec         = name-addr *(SEMI ai-param)
         ai-param               = generic-param

It should say:

5.1. P-Associated-URI Header Syntax


   The syntax of the P-Associated-URI header field is described as
   follows:

         P-Associated-URI       = "P-Associated-URI" HCOLON
                                  (p-aso-uri-spec)
                                  *(COMMA p-aso-uri-spec)
         p-aso-uri-spec         = name-addr *(SEMI ai-param)
         ai-param               = generic-param

Notes:

P-Associated-URI cannot include an empty header value (which was able to be included according to RFC 3455)

- Background.

The policy of P-Associated-URI has been updated from RFC 3455.
RFC 3455 : 4.1.2.2 Procedures at the registrar
...
In case the address-of-record under registration does not have any
other SIP or SIPS URIs associated, the registrar MUST include an
empty P-Associated-URI header value.


RFC 7315 : 4.1.2.2 Procedures at the Registrar
...
If the address-of-record under registration does not have any
associated URIs, the P-Associated-URI header field SHALL NOT be
included.
...

Moreover, we can say RFC 3455 has same errata based on this analysis.

Report New Errata



Advanced Search