RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Reported (1)

RFC 7976, "Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses", September 2016

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

Errata ID: 5393
Status: Reported
Type: Technical

Reported By: Roland Jesske
Date Reported: 2018-06-15

Section 3 says:

3.  Updates to RFC 7315

   This section implements the update to Section 5.7 of RFC 7315, in
   order to implement the misalignment fixes and the 3GPP requirements
   described in Section 2.

   Old text:

   The P-Associated-URI header field can appear in SIP REGISTER method
   and 2xx resonses [sic].  The P-Called-Party-ID header field can
   appear in SIP INVITE, OPTIONS, PUBLISH, SUBSCRIBE, and MESSAGE
   methods and all responses.  The P-Visited-Network-ID header field can
   appear in all SIP methods except ACK, BYE, and CANCEL and all
   responses.  The P-Access-Network-Info header field can appear in all
   SIP methods except ACK and CANCEL.  The P-Charging-Vector header
   field can appear in all SIP methods except CANCEL.  The
   P-Charging-Function-Addresses header field can appear in all SIP
   methods except ACK and CANCEL.

   New text:

   The P-Associated-URI header field can appear in SIP REGISTER 2xx
   responses.  The P-Called-Party-ID header field can appear in the SIP
   INVITE, OPTIONS, PUBLISH, REFER, SUBSCRIBE, and MESSAGE methods.  The
   P-Visited-Network-ID header field can appear in all SIP methods
   except ACK, BYE, CANCEL, NOTIFY, PRACK, INFO, and UPDATE.  The
   P-Access-Network-Info header field can appear in all SIP methods and
   non-100 responses, except in CANCEL methods, CANCEL responses, and
   ACK methods triggered by non-2xx responses.  The P-Charging-Vector
   header field can appear in all SIP methods and non-100 responses,
   except in CANCEL methods, CANCEL responses, and ACK methods triggered
   by non-2xx responses.  The P-Charging-Function-Addresses header field
   can appear in all SIP methods and non-100 responses, except in CANCEL
   methods, CANCEL responses, and ACK methods.

It should say:

3.  Updates to RFC 7315

   This section implements the update to Section 5.7 of RFC 7315, in
   order to implement the misalignment fixes and the 3GPP requirements
   described in Section 2.

   Old text:

   The P-Associated-URI header field can appear in SIP REGISTER method
   and 2xx resonses [sic].  The P-Called-Party-ID header field can
   appear in SIP INVITE, OPTIONS, PUBLISH, SUBSCRIBE, and MESSAGE
   methods and all responses.  The P-Visited-Network-ID header field can
   appear in all SIP methods except ACK, BYE, and CANCEL and all
   responses.  The P-Access-Network-Info header field can appear in all
   SIP methods except ACK and CANCEL.  The P-Charging-Vector header
   field can appear in all SIP methods except CANCEL.  The
   P-Charging-Function-Addresses header field can appear in all SIP
   methods except ACK and CANCEL.

   New text:

   The P-Associated-URI header field can appear in SIP REGISTER 2xx
   responses.  The P-Called-Party-ID header field can appear in the SIP
   INVITE, OPTIONS, PUBLISH, REFER, SUBSCRIBE, and MESSAGE methods.  The
   P-Visited-Network-ID header field can appear in all SIP methods
   except ACK, BYE, CANCEL, NOTIFY, PRACK, INFO, and UPDATE and all
   responses exept 100.  The
   P-Access-Network-Info header field can appear in all SIP methods and
   non-100 responses, except in CANCEL methods, CANCEL responses, and
   ACK methods triggered by non-2xx responses.  The P-Charging-Vector
   header field can appear in all SIP methods and non-100 responses,
   except in CANCEL methods, CANCEL responses, and ACK methods triggered
   by non-2xx responses.  The P-Charging-Function-Addresses header field
   can appear in all SIP methods and non-100 responses, except in CANCEL
   methods, CANCEL responses, and ACK methods.

Notes:

The Third Generation Partnership Project (3GPP) has identified cases
where the private header field P-Visited-Network-ID SIP private
header extensions, which is defined in RFC 7315 and updated by RFC
7976, needs to be included in SIP requests and responses. This
eratta updates RFC 7976, in order to allow inclusion of the P-
Visited-Network-ID header field in responses exept 100.
The issue was also discussed within a 3GPP - IETF coordination meeting.

Report New Errata