3. Updates to RFC 7315

This page preserves the RFC text for the section and adds navigation metadata for the documentation site.

RFC Text

3. Updates to RFC 7315

This section contains the update to Section 5.7 of [RFC7315], in order to implement the misalignment fixes and the 3GPP requirements described in Section 2. In the old text, blank lines have been added for readability.

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 requests.
>
> The P-Visited-Network-ID header field can appear in all SIP requests and the associated non-100 response message except in ACK, BYE, CANCEL, NOTIFY, PRACK, INFO, UPDATE.
>
> The P-Access-Network-Info header field can appear in all SIP requests and the associated non-100 responses, except in CANCEL requests, CANCEL responses, and ACK methods triggered by non-2xx responses.
>
> The P-Charging-Vector header field can appear in all SIP requests and the associated non-100 responses, except in CANCEL requests, CANCEL responses, and ACK requests triggered by non-2xx responses.
>
> The P-Charging-Function-Addresses header field can appear in all SIP methods and the associated non-100 responses, except in CANCEL requests, CANCEL responses, and ACK requests.