hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.2.3 SIP interface to VoiceXML media services | The AS may support control of the MRFC for voice dialogs by the use of RFC 5552 [145].
The media control commands are carried between the AS and the MRFC either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces.
The AS shall provide remote prompts and scripts to the MRFC using the AS-MRFC Cr interface.
Data shall be returned to the AS from the MRFC by either use of the AS-MRFC Cr interface (subclause 4.1 of RFC 5552 [145]), via the ISC interface (subclause 4.2 of RFC 5552 [145]) or via the Mr' interface. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.2.4 Media control channel framework and packages | The AS may support control of the MRFC for interactive voice response by the use of RFC 6231 [147] and RFC 6230 [146].
The AS shall provide remote prompts, media control commands and scripts to the MRFC using the AS-MRFC Cr interface.
The AS shall implement the control client role as described in RFC 6230 [146]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.3 Ad-hoc conferences | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.3.1 General | An AS may support control of the MRFC for ad-hoc conferencing. An AS supporting control of the MRFC for ad-hoc conferencing shall support one or more of the following methods:
- RFC 4240 [144] conference service; or
- RFC 6230 [146] and RFC 6505 [148]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.3.2 Basic network media services with SIP | The AS may support control of the MRFC for basic conferencing by the use of RFC 4240 [144] and the conference service described in RFC 4240 [144] subclause 5.
The media control commands are carried between the AS and the MRFC either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.3.3 Media control channel framework and packages | The AS may support control of the MRFC for conference mixing by the use of RFC 6505 [148] and RFC 6230 [146].
An AS may support control of the MRFC for floor controlled conferences (as specified in 3GPP TS 24.147 [8B]), via the use of RFC 6230 [146] together with appropriate packages. The packages, or extensions to existing packages using RFC 6230 [146] framework are not specified in this release.
An AS may support control of the MRFC for session-mode messaging conferences (as specified in 3GPP TS 24.247 [8F]), via the use of RFC 6230 [146] together with appropriate packages. The packages, or extensions to existing packages using RFC 6230 [146] framework are not specified in this release.
The AS shall provide media control commands to the MRFC using the AS-MRFC Cr interface.
The AS shall implement the control client role as described in RFC 6230 [146]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.4 Transcoding | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.4.1 General | An AS may support control of the MRFC for transcoding. An AS supporting control of the MRFC for transcoding shall support one or more of the following methods:
- RFC 4240 [144] conference service; or
- RFC 6230 [146] and RFC 6505 [148]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.4.2 Basic network media services with SIP | The AS may support control of the MRFC for transcoding by the use of RFC 4240 [144] and the conference service described in RFC 4240 [144] subclause 5.
The media control commands are carried between the AS and the MRFC either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.2.4.3 Media control channel framework and packages | The AS may support control of the MRFC for transcoding by the use of RFC 6505 [148] and RFC 6230 [146].
The AS shall provide media control commands to the MRFC using the AS-MRFC Cr interface.
The AS shall implement the control client role as described in RFC 6230 [146]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3 Procedures at the MRFC | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.1 General | An MRFC required to generate charging information and authorize requests from an AS for specific media operations and media usage shall support RFC 6230 [146] together with appropriate packages.
NOTE: This is in addition to the charging related procedures in clause 5 and to the charging information and authorisation requests, defined in 3GPP TS 32.260 [17] which provide charging information and authorisation for SIP session and SDP information.
An MRFC may support delegated XML (such as CCXML or SCXML) script execution from an AS. An MRFC supporting delegation of XML script execution shall use RFC 6230 [146] together with appropriate packages.
The packages, or extensions to existing packages using RFC 6230 [146] framework above are not specified in this release.
The MRFC may support the media server resource publish interface as defined by RFC 6917 [192]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.2 Tones and announcements | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.2.1 General | An MRFC may support control of tones and announcements. An MRFC supporting control of tones and announcements shall support one or more of the following methods:
- RFC 4240 [144] announcement service;
- RFC 5552 [145]; or
- RFC 6230 [146] and RFC 6231 [147]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.2.2 Basic network media services with SIP | The MRFC may support control of basic announcements by the use of RFC 4240 [144] and the announcement service described in RFC 4240 [144] subclause 3.
The media control commands are received from the AS either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces.
The MRFC shall fetch remote prompts from the AS using the AS-MRFC Cr interface.
The MRFC acts as the media server described in RFC 4240 [144]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.2.3 SIP interface to VoiceXML media services | The MRFC may support control of voice dialogs by the use of RFC 5552 [145].
The media control commands are received from the AS either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces.
The MRFC shall fetch via the AS-MRFC Cr interface the remote prompts and scripts from the address included in the "voicexml" URI parameter, if received, in the Request-URI of the SIP INVITE request.
Data shall be returned to the AS from the MRFC by either use of the AS-MRFC Cr interface (subclause 4.1 of RFC 5552 [145]), via the ISC interface (subclause 4.2 of RFC 5552 [145]) or via the Mr' interface.
The MRFC acts as the VoiceXML media server described in RFC 5552 [145]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.2.4 Media control channel framework and packages | The MRFC may support control of interactive voice response by the use of RFC 6231 [147] and RFC 6230 [146].
The MRFC shall fetch remote prompts and scripts from the MRFC using the AS-MRFC Cr interface. The MRFC shall send media control command responses and notifications to the AS using the AS-MRFC Cr interface.
The MRFC shall implement the control server role as described in RFC 6230 [146]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.3 Ad-hoc conferences | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.3.1 General | An MRFC may support control of ad-hoc conferencing. An MRFC supporting control of ad-hoc conferencing shall support one or more of the following methods:
- RFC 4240 [144] conference service; or
- RFC 6230 [146] and RFC 6505 [148]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.3.2 Basic network media services with SIP | The MRFC may support control of basic conferencing by the use of RFC 4240 [144] and the conference service described in RFC 4240 [144] subclause 5.
The media control commands are received from the AS either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces.
The MRFC acts as the media server described in RFC 4240 [144]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.3.3 Media control channel framework and packages | The MRFC may support control of conference mixing by the use of RFC 6505 [148] and RFC 6230 [146].
An MRFC may support control of floor controlled conferences (as specified in 3GPP TS 24.147 [8B]), via the use of RFC 6230 [146] together with appropriate packages. The packages, or extensions to existing packages using RFC 6230 [146] framework are not specified in this release. In addition, the MRFC may support the procedures for a multi-stream multiparty multimedia conference using simulcast defined in 3GPP TS 26.114 [9B] annex S.
An MRFC may support control of session-mode messaging conferences (as specified in 3GPP TS 24.247 [8F]), via the use of RFC 6230 [146] together with appropriate packages. The packages, or extensions to existing packages using RFC 6230 [146] framework are not specified in this release.
The MRFC shall send media control command responses and notifications to the AS using the AS-MRFC Cr interface.
The MRFC shall implement the control server role as described in RFC 6230 [146]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.4 Transcoding | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.4.1 General | An MRFC may support control of transcoding. An MRFC supporting control of transcoding shall support one or more of the following methods:
- RFC 4240 [144] conference service;
- RFC 6230 [146] and RFC 6505 [148]; or
- RFC 4117 [166]. This is detailed in subclause 5.7.5.6. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.4.2 Basic network media services with SIP | The MRFC may support control of transcoding by the use of RFC 4240 [144] and the conference service described in RFC 4240 [144] subclause 5.
The media control commands are received from the AS either directly over the Mr' interface or via the S-CSCF over the ISC and Mr interfaces.
The MRFC acts as the media server described in RFC 4240 [144]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.3.4.3 Media control channel framework and packages | The MRFC may support control of transcoding by the use of RFC 6505 [148] and RFC 6230 [146].
The MRFC shall send media control command responses and notifications to the AS using the AS-MRFC Cr interface.
The MRFC shall implement the control server role as described in RFC 6230 [146]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 10.4 Procedures at the MRB | The MRB shall support: a) the in-line unaware MRB interface. as defined in RFC 5917 [192]. The MRB may support: a) the media server resource publish interface; and b) the media server resource consumer interface; as defined in RFC 6917 [192]. Annex A (normative): Profiles of IETF RFCs for 3GPP usage A.1 Profiles A.1.1 Relationship to other specifications This annex contains a profile to the IETF specifications which are referenced by this specification, and the PICS proformas underlying profiles do not add requirements to the specifications they are proformas for. This annex provides a profile specification according to both the current IETF specifications for SIP, SDP and other protocols (as indicated by the "RFC status" column in the tables in this annex) which are referenced by this specification and to the 3GPP specifications using SIP (as indicated by the "Profile status" column in the tables in this annex. In the "RFC status" column the contents of the referenced specification takes precedence over the contents of the entry in the column. In the "Profile status" column, there are a number of differences from the "RFC status" column. Where these differences occur, these differences take precedence over any requirements of the IETF specifications. Where specification concerning these requirements exists in the main body of the present document, the main body of the present document takes precedence. Where differences occur in the "Profile status" column, the "Profile status" normally gives more strength to a "RFC status" and is not in contradiction with the "RFC status", e.g. it may change an optional "RFC status" to a mandatory "Profile status". If the "Profile status" weakens the strength of a "RFC status" then additionally this will be indicated by further textual description in the present document. For all IETF specifications that are not referenced by this document or that are not mentioned within the 3GPP profile of SIP and SDP, the generic rules as defined by RFC 3261 [26] and in addition the rules in clauses 5 and 6 of this specification apply, e.g. - a proxy which is built in accordance to this specification passes on any unknown method, unknown header field or unknown header field parameter after applying procedures such as filtering, insertion of P-Asserted-Identity header field, etc.; - an UA which is built in accordance to this specification will - handle received unknown methods in accordance to the procedures defined in RFC 3261 [26], e.g. respond with a 501 (Not Implemented) response; and - handle unknown header fields and unknown header field parameters in accordance to the procedures defined in RFC 3261 [26], e.g. respond with a 420 (Bad Extension) if an extension identified by an option-tag in the Require header field of the received request is not supported by the UA. A.1.2 Introduction to methodology within this profile This subclause does not reflect dynamic conformance requirements but static ones. In particular, a condition for support of a PDU parameter does not reflect requirements about the syntax of the PDU (i.e. the presence of a parameter) but the capability of the implementation to support the parameter. In the sending direction, the support of a parameter means that the implementation is able to send this parameter (but it does not mean that the implementation always sends it). In the receiving direction, it means that the implementation supports the whole semantic of the parameter that is described in the main part of this specification. As a consequence, PDU parameter tables in this subclause are not the same as the tables describing the syntax of a PDU in the reference specification, e.g. RFC 3261 [26] tables 2 and 3. It is not rare to see a parameter which is optional in the syntax but mandatory in subclause below. The various statii used in this subclause are in accordance with the rules in table A.1. Table A.1: Key to status codes Status code Status name Meaning m mandatory the capability shall be supported. It is a static view of the fact that the conformance requirements related to the capability in the reference specification are mandatory requirements. This does not mean that a given behaviour shall always be observed (this would be a dynamic view), but that it shall be observed when the implementation is placed in conditions where the conformance requirements from the reference specification compel it to do so. For instance, if the support for a parameter in a sent PDU is mandatory, it does not mean that it shall always be present, but that it shall be present according to the description of the behaviour in the reference specification (dynamic conformance requirement). o optional the capability may or may not be supported. It is an implementation choice. n/a not applicable it is impossible to use the capability. No answer in the support column is required. x prohibited (excluded) It is not allowed to use the capability. This is more common for a profile. c <integer> conditional the requirement on the capability ("m", "o", "n/a" or "x") depends on the support of other optional or conditional items. <integer> is the identifier of the conditional expression. o.<integer> qualified optional for mutually exclusive or selectable options from a set. <integer> is the identifier of the group of options, and the logic of selection of the options. i irrelevant capability outside the scope of the given specification. Normally, this notation should be used in a base specification ICS proforma only for transparent parameters in received PDUs. However, it may be useful in other cases, when the base specification is in fact based on another standard. In the context of this specification the "i" status code mandates that the implementation does not change the content of the parameter. It is an implementation option if the implementation acts upon the content of the parameter (e.g. by setting filter criteria to known or unknown parts of parameters in order to find out the route a message has to take). It must be understood, that this 3GPP SIP profile does not list all parameters which an implementation will treat as indicated by the status code "irrelevant". In general an implementation will pass on all unknown messages, header fields and header field parameters, as long as it can perform its normal behaviour. The following additional comments apply to the interpretation of the tables in this Annex. NOTE 1: The tables are constructed according to the conventional rules for ICS proformas and profile tables. NOTE 2: The notation (either directly or as part of a conditional) of "m" for the sending of a parameter and "i" for the receipt of the same parameter, may be taken as indicating that the parameter is passed on transparently, i.e. without modification. Where a conditional applies, this behaviour only applies when the conditional is met. As an example, the profile for the MGCF is found by first referring to clause 4.1, which states "The MGCF shall provide the UA role". Profiles are divided at the top level into the two roles in table A.2, user agent and proxy. The UA role is defined in subclause A.2.1 and the proxy role is defined in subclause A.2.2. More specific roles are listed in table A.3, table A.3A, table A.3B and table A.3C. The MGCF role is item 6 in table A.3 (the MGCF role is not found in table A.3A or table A.3B). Therefore, all profile entries for the MGCF are found by searching for A.3/6 in subclause A.2.1. As a further example, to look up support of the Reason header field, table A.4 item 38 lists the Resaon header field as a major capability that is optional for the user agent role. A subsequent search for A.4/38 in subclause A.2.1 shows that the Reason header field is optional for a user agent role to send and receive for ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, PUBLISH, REFER, REGISTER, SUBSCRIBE, and UPDATE requests. Also, table A.162 item 48 lists the Reason header field as a major capability that is optional for the proxy role. A subsequent search for A.162/48 in subclause A.2.2 shows that, if supported, the Reason header field is mandatory to send and irrelevant to receive for ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, PUBLISH, REFER, REGISTER, SUBSCRIBE, and UPDATE requests. A.1.3 Roles Table A.2: Roles Item Roles Reference RFC status Profile status 1 User agent [26] o.1 o.1 2 Proxy [26] o.1 o.1 o.1: It is mandatory to support exactly one of these items. NOTE: For the purposes of the present document it has been chosen to keep the specification simple by the tables specifying only one role at a time. This does not preclude implementations providing two roles, but an entirely separate assessment of the tables shall be made for each role. Table A.3: Roles specific to this profile Item Roles Reference RFC status Profile status 1 UE 5.1 n/a o.1 1A UE containing UICC 5.1 n/a c5 1B UE without UICC 5.1 n/a c5 2 P-CSCF 5.2 n/a o.1 2A P-CSCF (IMS-ALG) [7] n/a c6 3 I-CSCF 5.3 n/a o.1 3A void 4 S-CSCF 5.4 n/a o.1 5 BGCF 5.6 n/a o.1 6 MGCF 5.5 n/a o.1 7 AS 5.7 n/a o.1 7A AS acting as terminating UA, or redirect server 5.7.2 n/a c2 7B AS acting as originating UA 5.7.3 n/a c2 7C AS acting as a SIP proxy 5.7.4 n/a c2 7D AS performing 3rd party call control 5.7.5 n/a c2 8 MRFC 5.8 n/a o.1 8A MRB 5.8A n/a o.1 9 IBCF 5.10 n/a o.1 9A IBCF (THIG) 5.10.4 n/a c4 9B IBCF (IMS-ALG) 5.10.5, 5.10.7 n/a c4 9C IBCF (Screening of SIP signalling) 5.10.6 n/a c4 9D IBCF (Privacy protection) 5.10.8 n/a c4 10 Additional routeing functionality Annex I n/a c3 11 E-CSCF 5.11 n/a o.1 11A E-CSCF acting as UA 5.11.1, 5.11.2, 5.11.3 n/a c7 11B E-CSCF acting as a SIP Proxy 5.11.1, 5.11.2 n/a c7 12 LRF 5.12 n/a o.1 13 ISC gateway function 5.13 n/a o.1 13A ISC gateway function (THIG) 5.13.4 n/a c8 13B ISC gateway function (IMS-ALG) 5.13.5 n/a c8 13C ISC gateway function (Screening of SIP signalling) 5.13.6 n/a c8 14 Gm based WIC [8Z] n/a o.1 15 Transit function I.3 n/a c9 c2: IF A.3/7 THEN o.2 ELSE n/a - - AS. c3: IF A.3/3 OR A.3/4 OR A.3/5 OR A.3/6 OR A.3/9 THEN o ELSE o.1 - - I-CSCF, S-CSCF, BGCF, MGCF, IBCF. c4: IF A.3/9 THEN o.3 ELSE n/a - - IBCF. c5: IF A.3/1 THEN o.4 ELSE n/a - - UE. c6: IF A.3/2 THEN o ELSE n/a - - P-CSCF. c7: IF A.3/11 THEN o.5 ELSE n/a - - E-CSCF. c8: IF A.3/13 THEN o ELSE n/a - - ISC gateway function. c9 IF A.3/3 OR A.3/4 OR A.3/5 OR A.3/6 OR A.3/9 THEN o ELSE o.1 - - I-CSCF, S-CSCF, BGCF, MGCF, IBCF. o.1: It is mandatory to support exactly one of these items. o.2: It is mandatory to support at least one of these items. o.3: It is mandatory to support at least one of these items. o.4 It is mandatory to support exactly one of these items. o.5: It is mandatory to support exactly one of these items. NOTE: For the purposes of the present document it has been chosen to keep the specification simple by the tables specifying only one role at a time. This does not preclude implementations providing two roles, but an entirely separate assessment of the tables shall be made for each role. Table A.3A: Roles specific to additional capabilities Item Roles Reference RFC status Profile status 1 Presence server 3GPP TS 24.141 [8A] n/a c1 2 Presence user agent 3GPP TS 24.141 [8A] n/a c2 3 Resource list server 3GPP TS 24.141 [8A] n/a c3 4 Watcher 3GPP TS 24.141 [8A] n/a c4 11 Conference focus 3GPP TS 24.147 [8B] n/a c11 12 Conference participant 3GPP TS 24.147 [8B] n/a c6 21 CSI user agent 3GPP TS 24.279 [8E] n/a c7 22 CSI application server 3GPP TS 24.279 [8E] n/a c8 31 Messaging application server 3GPP TS 24.247 [8F] n/a c5 32 Messaging list server 3GPP TS 24.247 [8F] n/a c5 33 Messaging participant 3GPP TS 24.247 [8F] n/a c2 33A Page-mode messaging participant 3GPP TS 24.247 [8F] n/a c2 33B Session-mode messaging participant 3GPP TS 24.247 [8F] n/a c2 34 Session-mode messaging intermediate node 3GPP TS 24.247 [8F] n/a c5 50 Multimedia telephony service participant 3GPP TS 24.173 [8H] n/a c2 50A Multimedia telephony service application server 3GPP TS 24.173 [8H] n/a c9 51 Message waiting indication subscriber UA 3GPP TS 24.606 [8I] n/a c2 52 Message waiting indication notifier UA 3GPP TS 24.606 [8I] n/a c3 53 Advice of charge application server 3GPP TS 24.647 [8N] n/a c8 54 Advice of charge UA client 3GPP TS 24.647 [8N] n/a c2 55 Ut reference point XCAP server for supplementary services 3GPP TS 24.623 [8P] n/a c3 56 Ut reference point XCAP client for supplementary services 3GPP TS 24.623 [8P] n/a c2 57 Customized alerting tones application server 3GPP TS 24.182 [8Q] n/a c8 58 Customized alerting tones UA client 3GPP TS 24.182 [8Q] n/a c2 59 Customized ringing signal application server 3GPP TS 24.183 [8R] n/a c8 60 Customized ringing signal UA client 3GPP TS 24.183 [8R] n/a c2 61 SM-over-IP sender 3GPP TS 24.341 [8L] n/a c2 62 SM-over-IP receiver 3GPP TS 24.341 [8L] n/a c2 63 IP-SM-GW 3GPP TS 24.341 [8L] n/a c1 71 IP-SM-GW 3GPP TS 29.311 [15A] n/a c10 81 MSC Server enhanced for ICS 3GPP TS 24.292 [8O] n/a c12 81A MSC server enhanced for SRVCC using SIP interface 3GPP TS 24.237 [8M] n/a c12 81B MSC server enhanced for DRVCC using SIP interface 3GPP TS 24.237 [8M] n/a c12 82 ICS user agent 3GPP TS 24.292 [8O] n/a c2 83 SCC application server 3GPP TS 24.292 [8O] n/a c9 84 EATF 3GPP TS 24.237 [8M] n/a c12 85 In-dialog overlap signalling application server Annex N.2, Annex N.3.3 n/a c9 86 In-dialog overlap signalling UA client Annex N.2, Annex N.3.3 n/a c2 87 Session continuity controller UE 3GPP TS 24.337 [8ZC] n/a c2 88 ATCF (proxy) 3GPP TS 24.237 [8M] n/a c13 (note 4) 89 ATCF (UA) 3GPP TS 24.237 [8M] n/a c12 (note 4) 91 Malicious communication identification application server 3GPP TS 24.616 [8S] n/a c9 92 USSI UE 3GPP TS 24.390 [8W] n/a c2 92A USSI UE supporting user-initiated USSD operations 3GPP TS 24.390 [8W] n/a c17 92B USSI UE supporting network-initiated USSD operations 3GPP TS 24.390 [8W] n/a c17 93 USSI AS 3GPP TS 24.390 [8W] n/a c3 93A USSI AS supporting user-initiated USSD operations 3GPP TS 24.390 [8W] n/a c18 93B USSI AS supporting network-initiated USSD operations 3GPP TS 24.390 [8W] n/a c18 94 TP UE 3GPP TS 24.103 [7G] n/a c14 95 eP-CSCF (P-CSCF enhanced for WebRTC) 3GPP TS 24.371 [8Z] n/a c15 101 Business trunking in static mode of operation application server 3GPP TS 24.525 [8ZA] n/a c16 102 MCPTT client 3GPP TS 24.379 [8ZE] n/a c19 103 MCPTT server 3GPP TS 24.379 [8ZE] n/a c20 c1: IF A.3/7A AND A.3/7B THEN o ELSE n/a - - AS acting as terminating UA, or redirect server and AS acting as originating UA. c2: IF A.3/1 THEN o ELSE n/a - - UE. c3: IF A.3/7A THEN o ELSE n/a - - AS acting as terminating UA, or redirect server. c4: IF A.3/1 OR A.3/7B THEN o ELSE n/a - - UE or AS acting as originating UA. c5: IF A.3/7D AND A.3/8 THEN o ELSE n/a - - AS performing 3rd party call control and MRFC (note 2). c6: IF A.3/1 OR A.3A/11 THEN o ELSE n/a - - UE or conference focus. c7: IF A.3/1 THEN o ELSE n/a - - UE. c8: IF A.3/7D THEN o ELSE n/a - - AS performing 3rd party call control. c9: IF A.3/7A OR A.3/7B OR A.3/7C OR A.3/7D THEN o ELSE n/a - - AS acting as terminating UA, or redirect server, AS acting as originating UA, AS acting as a SIP proxy, AS performing 3rd party call control. c10: IF A.3/7A OR A.3/7B OR A.3/7D THEN o ELSE n/a - - AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control. c11: IF A.3/7D THEN o ELSE n/a - - AS performing 3rd party call control. c12: IF A.2/1 THEN o ELSE n/a - - UA. c13: IF A.2/2 THEN o ELSE n/a - - proxy. c14: IF A.3/1 OR A.3A/11 THEN o ELSE n/a - - UE or conference focus. c15: IF A.3/2A THEN o ELSE n/a - - P-CSCF (IMS-ALG). c16: IF A.3/7A OR A.3/7B THEN o ELSE n/a - - AS acting as terminating UA, or redirect server, AS acting as originating UA. c17: IF A.3A/92 THEN o.1 ELSE n/a - - USSI UE. c18: IF A.3A/93 THEN o.2 ELSE n/a - - USSI AS. c19: IF A.3/1 THEN o ELSE n/a - - UE. c20: IF A.3/7 THEN o ELSE n/a - - AS. o.1: It is mandatory to support at least one of these items. o.2: It is mandatory to support at least one of these items. NOTE 1: For the purposes of the present document it has been chosen to keep the specification simple by the tables specifying only one role at a time. This does not preclude implementations providing two roles, but an entirely separate assessment of the tables shall be made for each role. NOTE 2: The functional split between the MRFC and the AS for page-mode messaging is out of scope of this document and they are assumed to be collocated. NOTE 3: A.3A/63 is an AS providing the IP-SM-GW role to support the transport level interworking defined in 3GPP TS 24.341 [8L]. A.3A/71 is an AS providing the IP-SM-GW role to support the service level interworking for messaging as defined in 3GPP TS 29.311 [15A]. NOTE 4: An ATCF shall support both the ATCF (proxy) role and the ATCF (UA) role. Table A.3B: Roles with respect to access technology Item Value used in P-Access-Network-Info header field Reference RFC status Profile status 1 3GPP-GERAN [52] 4.4 o c1 2 3GPP-UTRAN-FDD [52] 4.4 o c1 3 3GPP-UTRAN-TDD [52] 4.4 o c1 4 3GPP2-1X [52] 4.4 o c1 5 3GPP2-1X-HRPD [52] 4.4 o c1 6 3GPP2-UMB [52] 4.4 o c1 7 3GPP-E-UTRAN-FDD [52] 4.4 o c1 8 3GPP-E-UTRAN-TDD [52] 4.4 o c1 8A 3GPP-E-UTRAN-ProSe-UNR subclause 7.2A.4 n/a c1 8B 3GPP-NR-FDD subclause 7.2A.4 n/a c1 8C 3GPP-NR-TDD subclause 7.2A.4 n/a c1 8D 3GPP-NR-U-FDD subclause 7.2A.4 n/a c1 8E 3GPP-NR-U-TDD subclause 7.2A.4 n/a c1 8F 3GPP-NR-ProSe-L2UNR subclause 7.2A.4 n/a c1 8G 3GPP-NR-ProSe-L3UNR subclause 7.2A.4 n/a c1 8W 3GPP-NR-SAT subclause 7.2A.4 n/a c1 8WA 3GPP-NR(LEO) subclause 7.2A.4 n/a c1 8WB 3GPP-NR(MEO) subclause 7.2A.4 n/a c1 8WC 3GPP-NR(GEO) subclause 7.2A.4 n/a c1 8WD 3GPP-NR(OTHERSAT) subclause 7.2A.4 n/a c1 8WE 3GPP-WB-E-UTRAN(LEO) subclause 7.2A.4 n/a c1 8WF 3GPP-WB-E-UTRAN(MEO) subclause 7.2A.4 n/a c1 8WG 3GPP-WB-E-UTRAN(GEO) subclause 7.2A.4 n/a c1 8WH 3GPP-WB-E-UTRAN(OTHERSAT) subclause 7.2A.4 n/a c1 8WI 3GPP-NB-IoT(LEO) subclause 7.2A.4 n/a c1 8WJ 3GPP-NB-IoT(MEO) subclause 7.2A.4 n/a c1 8WK 3GPP-NB-IoT(GEO) subclause 7.2A.4 n/a c1 8WL 3GPP-NB-IoT(OTHERSAT) subclause 7.2A.4 n/a c1 8WM 3GPP-LTE-M(LEO) subclause 7.2A.4 n/a c1 8WN 3GPP-LTE-M(MEO) subclause 7.2A.4 n/a c1 8WO 3GPP-LTE-M(GEO) subclause 7.2A.4 n/a c1 8WP 3GPP-LTE-M(OTHERSAT) subclause 7.2A.4 n/a c1 8X 3GPP‑NR‑REDCAP subclause 7.2A.4 n/a c1 9 3GPP2-1X-Femto [52] 4.4 o c1 11 IEEE-802.11 [52] 4.4 o c1 12 IEEE-802.11a [52] 4.4 o c1 13 IEEE-802.11b [52] 4.4 o c1 14 IEEE-802.11g [52] 4.4 o c1 15 IEEE-802.11n [52] 4.4 o c1 16 IEEE-802.11ac [52] 4.4 o c1 21 ADSL [52] 4.4 o c1 22 ADSL2 [52] 4.4 o c1 23 ADSL2+ [52] 4.4 o c1 24 RADSL [52] 4.4 o c1 25 SDSL [52] 4.4 o c1 26 HDSL [52] 4.4 o c1 27 HDSL2 [52] 4.4 o c1 28 G.SHDSL [52] 4.4 o c1 29 VDSL [52] 4.4 o c1 30 IDSL [52] 4.4 o c1 31 xDSL subclause 7.2A.4 o c1 41 DOCSIS [52] 4.4 o c1 51 DVB-RCS2 [52] 4.4 o c1 52 3GPP-UTRAN [52] 4.4 o c2 53 3GPP-E-UTRAN [52] 4.4 o c2 54 3GPP-WLAN [52] 4.4 o c2 55 3GPP-GAN [52] 4.4 o c2 56 3GPP-HSPA [52] 4.4 o c2 57 3GPP2 [52] 4.4 o c2 58 untrusted-non-3GPP-VIRTUAL-EPC subclause 7.2A.4 n/a c2 59 VIRTUAL-no-PS subclause 7.2A.4 n/a c2 60 WLAN-no-PS subclause 7.2A.4 n/a c2 61 3GPP-NR Subclause 7.2A.4 n/a c2 62 3GPP-NR-U Subclause 7.2A.4 n/a c2 63 3GPP-NR-SAT Subclause 7.2A.4 n/a c2 63A 3GPP-NR(LEO) Subclause 7.2A.4 n/a c2 63B 3GPP-NR(MEO) Subclause 7.2A.4 n/a c2 63C 3GPP-NR(GEO) Subclause 7.2A.4 n/a c2 63D 3GPP-NR(OTHERSAT) Subclause 7.2A.4 n/a c2 63E 3GPP-WB-E-UTRAN(LEO) Subclause 7.2A.4 n/a c2 63F 3GPP-WB-E-UTRAN(MEO) Subclause 7.2A.4 n/a c2 63G 3GPP-WB-E-UTRAN(GEO) Subclause 7.2A.4 n/a c2 63H 3GPP-WB-E-UTRAN(OTHERSAT) Subclause 7.2A.4 n/a c2 63I 3GPP-NB-IoT(LEO) Subclause 7.2A.4 n/a c2 63J 3GPP-NB-IoT(MEO) Subclause 7.2A.4 n/a c2 63K 3GPP-NB-IoT(GEO) Subclause 7.2A.4 n/a c2 63L 3GPP-NB-IoT(OTHERSAT) Subclause 7.2A.4 n/a c2 63M 3GPP-LTE-M(LEO) Subclause 7.2A.4 n/a c2 63N 3GPP-LTE-M(MEO) Subclause 7.2A.4 n/a c2 63O 3GPP-LTE-M(GEO) Subclause 7.2A.4 n/a c2 63P 3GPP-LTE-M(OTHERSAT) Subclause 7.2A.4 n/a c2 c1: If A.3/1 OR A.3/2 THEN o.1 ELSE n/a - - UE or P-CSCF. c2: If A.3/2 THEN o.1 ELSE n/a - - P-CSCF. o.1: It is mandatory to support at least one of these items. Table A.3C: Modifying roles Item Roles Reference RFC status Profile status 1 UE performing the functions of an external attached network 4.1 2 UE performing the functions of an external attached network operating in static mode 4.1 NOTE: This table identifies areas where the behaviour is modified from that of the underlying role. Subclause 4.1 indicates which underlying roles are modified for this behaviour. Table A.3D: Roles with respect to security mechanism Item Security mechanism Reference RFC status Profile status 1 IMS AKA plus IPsec ESP clause 4.2B.1 n/a c1 2 SIP digest plus check of IP association clause 4.2B.1 n/a c2 3 SIP digest plus Proxy Authentication clause 4.2B.1 n/a c2 4 SIP digest with TLS clause 4.2B.1 n/a c2 5 NASS-IMS bundled authentication clause 4.2B.1 n/a c2 6 GPRS-IMS-Bundled authentication clause 4.2B.1 n/a c2 7 Trusted node authentication clause 4.2B.1 n/a c3 8 SIP over TLS with client certificate authentication clause 4.2B.1 n/a c6 20 End-to-end media security using SDES clause 4.2B.2 o c5 20A End-to-access-edge media security for MSRP using TLS and certificate fingerprints clause 4.2B.2 n/a c4 20B End-to-access-edge media security for BFCP using TLS and certificate fingerprints clause 4.2B.2 n/a c4 20C End-to-access-edge media security for UDPTL using DTLS and certificate fingerprints clause 4.2B.2 n/a c4 21 End-to-end media security using KMS clause 4.2B.2 o c5 22 End-to-end media security for MSRP using TLS and KMS clause 4.2B.2 o c5 30 End-to-access-edge media security using SDES clause 4.2B.2 n/a c4 31 End-to-access-edge media security for RTP media using DTLS-SRTP and certificate fingerprints clause 4.2B.2 n/a c7 c1: IF (A.3/1A OR A.3/2 OR A.3/3 OR A.3/4) THEN m ELSE IF A.3/1B THEN o ELSE n/a - - UE containing UICC or P-CSCF or I-CSCF or S-CSCF, UE without UICC. c2: IF (A.3/1 OR A.3/2 OR A.3/3 OR A.3/4) THEN o ELSE n/a - - UE or P-CSCF or I-CSCF or S-CSCF. c3: IF (A.3/3 OR A.3/4) THEN o ELSE n/a - - I-CSCF or S-CSCF. c4: IF (A.3/1 OR A.3/2A) THEN o ELSE n/a - - UE or P-CSCF (IMS-ALG). c5: IF A.3/1 THEN o - - UE. c6: IF A.3C/2 THEN m ELSE o - - UE performing the functions of an external attached network operating in static mode. c7: IF (A.3/14 OR A.3A/95) THEN m ELSE IF (A.3/1 OR A.3/2A) THEN o ELSE n/a - - Gm based WIC or eP-CSCF or UE or P-CSCF (IMS-ALG). A.2 Profile definition for the Session Initiation Protocol as used in the present document A.2.1 User agent role A.2.1.1 Introduction This subclause contains the ICS proforma tables related to the user role. They need to be completed only for UA implementations: Prerequisite: A.2/1 - - user agent role. A.2.1.2 Major capabilities Table A.4: Major capabilities Item Does the implementation support Reference RFC status Profile status Capabilities within main protocol 1 client behaviour for registration? [26] subclause 10.2 o c3 2 registrar? [26] subclause 10.3 o c4 2A registration of multiple contacts for a single address of record [26] 10.2.1.2, 16.6 o o 2B initiating a session? [26] subclause 13 o o 2C initiating a session which require local and/or remote resource reservation? [30] o c43 3 client behaviour for INVITE requests? [26] subclause 13.2 c18 c18 4 server behaviour for INVITE requests? [26] subclause 13.3 c18 c18 5 session release? [26] subclause 15.1 c18 c18 6 timestamping of requests? [26] subclause 8.2.6.1 o o 7 authentication between UA and UA? [26] subclause 22.2, [287] c34 c34 8 authentication between UA and registrar? [26] subclause 22.2, [287] o c74 8A authentication between UA and proxy? [26] 20.28, 22.3, [287] o c75 9 server handling of merged requests due to forking? [26] 8.2.2.2 m m 10 client handling of multiple responses due to forking? [26] 13.2.2.4 m m 11 insertion of date in requests and responses? [26] subclause 20.17 o o 12 downloading of alerting information? [26] subclause 20.4 o o Extensions 13 SIP INFO method and package framework? [25] o c100 13A legacy INFO usage? [25] 2, 3 o c90 14 reliability of provisional responses in SIP? [27] c19 c44 15 the REFER method? [36] o c33 15A clarifications for the use of REFER with RFC6665? [231] c121 c121 15B explicit subscriptions for the REFER method? [232] o o 16 integration of resource management and SIP? [30] [64] c19 c44 17 the SIP UPDATE method? [29] c5 c44 19 SIP extensions for media authorization? [31] o c14 20 SIP specific event notification? [28] o c13 22 acting as the notifier of event information? [28] c2 c15 22A a clarification on the use of GRUUs in the SIP event notification framework? [233] c122 c122 23 acting as the subscriber to event information? [28] c2 c16 24 session initiation protocol extension header field for registering non-adjacent contacts? [35] o c6 25 private extensions to the Session Initiation Protocol (SIP) for network asserted identity within trusted networks? [34] o m 26 a privacy mechanism for the Session Initiation Protocol (SIP)? [33] o m 26A request of privacy by the inclusion of a Privacy header indicating any privacy option? [33] c9 c11 26B application of privacy based on the received Privacy header? [33] c9 n/a 26C passing on of the Privacy header transparently? [33] c9 c12 26D application of the privacy option "header" such that those headers which cannot be completely expunged of identifying information without the assistance of intermediaries are obscured? [33] 5.1 c10 c27 26E application of the privacy option "session" such that anonymization for the session(s) initiated by this message occurs? [33] 5.2 c10 c27 26F application of the privacy option "user" such that user level privacy functions are provided by the network? [33] 5.3 c10 c27 26G application of the privacy option "id" such that privacy of the network asserted identity is provided by the network? [34] 7 c10 n/a 26H application of the privacy option "history" such that privacy of the History-Info header is provided by the network? [66] 7.2 c37 c37 27 a messaging mechanism for the Session Initiation Protocol (SIP)? [50] o c7 28 session initiation protocol extension header field for service route discovery during registration? [38] o c17 29 compressing the session initiation protocol? [55] o c8 30 private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP)? [52] o m 30A act as first entity within the trust domain for asserted identity? [34] c96 c97 30B act as entity within trust network that can route outside the trust network? [34] c96 c97 30C act as entity passing on identity transparently independent of trust domain? [34] c96 c98 31 the P-Associated-URI header extension? [52] 4.1, [52A] 4 c21 c22 32 the P-Called-Party-ID header extension? [52] 4.2, [52A] 4 c21 c23 33 the P-Visited-Network-ID header extension? [52] 4.3, [52A] 4 c21 c24 34 the P-Access-Network-Info header extension? [52] 4.4, [52A] 4, [234] 2 c21 c25 35 the P-Charging-Function-Addresses header extension? [52] 4.5, [52A] 4 c21 c26 36 the P-Charging-Vector header extension? [52] 4.6, [52A] 4 c21 c26 37 security mechanism agreement for the session initiation protocol? [48] o c20 37A mediasec header field parameter for marking security mechanisms related to media? Subclause 7.2A.7 n/a c101 38 the Reason header field for the session initiation protocol? [34A] o c68 38A carrying Q.850 codes in Reason header fields in SIP (Session Initiation Protocol) responses? [130] o c82 38B the location parameter for the SIP Reason header field? [255] o c131 38C Handling of Identity Header Errors for Secure Telephone Identity Revisited (STIR) (carrying STIR codes in Reason header fields in SIP responses)? [294] o c137 38D Multiple SIP Reason Header Field Values? [296] o c138 39 an extension to the session initiation protocol for symmetric response routeing? [56A] o c62 40 caller preferences for the session initiation protocol? [56B] C29 c29 40A the proxy-directive within caller-preferences? [56B] 9.1 o.5 o.5 40B the cancel-directive within caller-preferences? [56B] 9.1 o.5 o.5 40C the fork-directive within caller-preferences? [56B] 9.1 o.5 o.5 40D the recurse-directive within caller-preferences? [56B] 9.1 o.5 o.5 40E the parallel-directive within caller-preferences? [56B] 9.1 o.5 o.5 40F the queue-directive within caller-preferences? [56B] 9.1 o.5 o.5 41 an event state publication extension to the session initiation protocol? [70] o c30 42 SIP session timer? [58] c19 c19 43 the SIP Referred-By mechanism? [59] o c33 44 the Session Inititation Protocol (SIP) "Replaces" header? [60] c19 c38 (note 1) 45 the Session Inititation Protocol (SIP) "Join" header? [61] c19 c19 (note 1) 46 the callee capabilities? [62] o c35 47 an extension to the session initiation protocol for request history information? [66] o o 47A application of the "mp" optional header field parameter? [66] o o 47B application of the "rc" optional header field parameter? [66] o o 47C application of the "np" optional header field parameter? [66] o o 48 Rejecting anonymous requests in the session initiation protocol? [67] o o 49 session initiation protocol URIs for applications such as voicemail and interactive voice response? [68] o o 49A Session Initiation Protocol (SIP) cause URI parameter for service number translation? [230] c118 c118 50 Session Initiation Protocol's (SIP) non-INVITE transactions? [84] m m 51 the P-User-Database private header extension? [82] 4 o c94 52 a uniform resource name for services? [69] n/a c39 53 obtaining and using GRUUs in the Session Initiation Protocol (SIP)? [93] o c40 (note 2) 55 the Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)? [96] o c42 56 the SIP P-Profile-Key private header extension? [97] n/a n/a 57 managing client initiated connections in SIP? [92] o c45 58 indicating support for interactive connectivity establishment in SIP? [102] o c46 59 multiple-recipient MESSAGE requests in the session initiation protocol? [104] c47 c48 60 SIP location conveyance? [89] o c49 60A the Location Source parameter for the SIP Geolocation header field? [xxx] o c134 61 referring to multiple resources in the session initiation protocol? [105] c50 c50 62 conference establishment using request-contained lists in the session initiation protocol? [106] c51 c52 63 subscriptions to request-contained resource lists in the session initiation protocol? [107] c53 c53 64 dialstring parameter for the session initiation protocol uniform resource identifier? [103] o c19 65 the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular? [111] o c60 66 the SIP P-Early-Media private header extension for authorization of early media? [109] 8 o c58 67 number portability parameters for the 'tel' URI? [112] o c54 67A assert or process carrier indication? [112] o c55 67B local number portability? [112] o c57 69 extending the session initiation protocol Reason header for preemption events [115] c69 c69 70 communications resource priority for the session initiation protocol? [116] o c70 70A inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol? [116] 4.2 c72 c72 70B inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol? [116] 4.2 c72 c72 71 addressing an amplification vulnerability in session initiation protocol forking proxies? [117] o c87 72 the remote application identification of applying signalling compression to SIP [79] 9.1 o c8 73 a session initiation protocol media feature tag for MIME application subtypes? [120] o c59 74 SIP extension for the identification of services? [121] o c61 75 a framework for consent-based communications in SIP? [125] c76 c76 75A a relay within the framework for consent-based communications in SIP? [125] c77 c78 75B a recipient within the framework for consent-based communications in SIP? [125] c80 c79 76 a mechanism for transporting user-to user-call control information in SIP? [126] o c81 76A interworking ISDN call control user information with SIP? [126A] c109 c109 77 The SIP P-Private-Network-Indication private-header (P-Header)? [134] o o 78 the SIP P-Served-User private header for the 3GPP IM CN subsystem? [133] 6 o c93 79 the SIP P-Served-User header extension for Originating CDIV session case? [239] 4 c126 c127 80 marking SIP messages to be logged? [140] o c85 81 the 199 (Early Dialog Terminated) response code) [142] o c86 82 message body handling in SIP? [150] m m 83 indication of support for keep-alive [143] o c88 84 SIP Interface to VoiceXML Media Services? [145] o c89 85 common presence and instant messaging (CPIM): message format? [151] o c91 86 instant message disposition notification? [157] o c91 87 requesting answering modes for SIP? [158] o c60 89 the early session disposition type for SIP? [74B] o o 91 The Session-ID header? [162] o c102 92 correct transaction handling for 2xx responses to Session Initiation Protocol INVITE requests? [163] c18 c18 93 addressing Record-Route issues in the Session Initiation Protocol (SIP)? [164] n/a n/a 94 essential correction for IPv6 ABNF and URI comparison in RFC3261? [165] m m 95 suppression of session initiation protocol REFER method implicit subscription? [173] o c99 96 Alert-Info URNs for the Session Initiation Protocol? [175] o o 97 multiple registrations? Subclause 3.1 n/a c103 98 the SIP P-Refused-URI-List private-header? [183] o c104 99 request authorization through dialog Identification in the session initiation protocol? [184] o c105 100 indication of features supported by proxy? [190] o c106 101 registration of bulk number contacts? [191] o c107 102 media control channel framework? [146] o c108 103 S-CSCF restoration procedures? Subclause 4.14 n/a c110 104 SIP overload control? [198] o c112 104A feedback control? [199] c113 c113 104B distribution of load filters? [201] c113 c114 105 handling of a 380 (Alternative service) response? Subclauses 5.1.2A.1.1, 5.1.3.1, 5.1.6.8, and 5.2.10 n/a c111 106 indication of adjacent network in the Via "received-realm" header field parameter? [208] o c115 107 PSAP callback indicator? [209] o c116 108 SIP URI parameter to indicate traffic leg? [225] o c117 109 PCF or PCRF based P-CSCF restoration? Subclause 4.14.2 n/a c119 110 UDM/HSS or HSS based P-CSCF restoration? Subclause 4.14.2 n/a c120 111 the Relayed-Charge header field extension? Subclause 7.2.12 n/a c123 112 resource sharing? Subclause 4.15 n/a c124 113 the Cellular-Network-Info header extension? Subclause 7.2.15 n/a c125 114 the Priority-Share header field extension? Subclause 7.2.16 n/a c128 115 the Response-Source header field extension? Subclause 7.2.17 n/a o 116 authenticated identity management in the Session Initiation Protocol? [252] o c129 117 a SIP response code for unwanted calls extension? [254] o o 118 the 3GPP PS data off extension Subclause 4.17 n/a c130 119 Content-ID header field in Session Initiation Protocol (SIP)? [256] o o 120 Next-Generation Pan-European eCall emergency service? [244] o c62 121 the Attestation-Info header field extension? Subclause 7.2.18 n/a c132 122 the Origination-Id header field extension? Subclause 7.2.19 n/a c132 123 Dynamic services interactions? Subclause 4.18 n/a c133 124 the Additional-Identity header field extension? Subclause 7.2.20 n/a c135 125 RLOS? Subclause 4.19 n/a c136 126 the Priority-Verstat header field extension? Subclause 7.2.21 n/a c72 127 Transfer of an updated MSD for PSAP callback? Subclause 5.1.6B n/a c62 c2: IF A.4/20 THEN o.1 ELSE n/a - - SIP specific event notification extension. c3: IF A.3/1 OR A.3/4 OR A.3A/81 THEN m ELSE n/a - - UE or S-CSCF functional entity or MSC Server enhanced for ICS. c4: IF A.3/4 THEN m ELSE IF A.3/7 THEN o ELSE n/a - - S-CSCF or AS functional entity. c5: IF A.4/16 THEN m ELSE o - - integration of resource management and SIP extension. c6: IF A.3/4 OR A.3/1 OR A.3A/81 THEN m ELSE n/a. - - S-CSCF or UE or MSC Server enhanced for ICS. c7: IF A.3/1 OR A.3/4 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/9B OR A.3/13B OR A.3A/83 OR A.3A/89 THEN m ELSE n/a - - UA or S-CSCF or AS acting as terminating UA or AS acting as originating UA or AS performing 3rd party call control or IBCF (IMS-ALG), ISC gateway function (IMS-ALG), SCC application server, ATCF (UA). c8: IF A.3/1 THEN (IF (A.3B/1 OR A.3B/2 OR A.3B/3 OR A.3B/4 OR A.3B/5 OR A.3B/6 OR A.3B/7 OR A.3B/8 OR A.3B/11 OR A.3B/12 OR A.3B/13 OR A.3B/14 OR A.3B/15) THEN m ELSE o) ELSE n/a - - UE behaviour (based on P-Access-Network-Info usage). c9: IF A.4/26 THEN o.2 ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c10: IF A.4/26B THEN o.3 ELSE n/a - - application of privacy based on the received Privacy header. c11: IF A.3/1 OR A.3/6 OR A.3A/81 OR A.3A/81A OR A.3A/81B THEN o ELSE IF A.3/9B OR A.3/13B THEN m ELSE n/a - - UE or MGCF, IBCF (IMS-ALG), ISC gateway function (IMS-ALG), MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c12: IF A.3/7D OR A3A/84 OR A.3A/89 THEN m ELSE n/a - - AS performing 3rd-party call control, EATF, ATCF (UA). c13: IF A.3/1 OR A.3/2 OR A.3/4 OR A.3/9B OR A.3/11 OR A.3/12 OR A.3/13B OR A.3A/81 THEN m ELSE o - - UE or S-CSCF or IBCF (IMS-ALG) or E-CSCF or LRF or ISC gateway function (IMS-ALG) or MSC Server enhanced for ICS. c14: IF A.3/1 AND A4/2B AND (A.3B/1 OR A.3B/2 OR A.3B/3) THEN m ELSE IF A.3/2 THEN o ELSE n/a – UE and initiating sessions and GPRS IP-CAN or P-CSCF. c15: IF A.4/20 AND (A.3/4 OR A.3/9B OR A.3/11 OR A.3/13B) THEN m ELSE o – SIP specific event notification extensions and S-CSCF or IBCF (IMS-ALG) or E-CSCF or ISC gateway function (IMS-ALG). c16: IF A.4/20 AND (A.3/1 OR A.3/2 OR A.3/9B OR A.3/12 OR A.3/13B OR A.3A/81) THEN m ELSE o - - SIP specific event notification extension and UE or P-CSCF or IBCF (IMS-ALG) or MSC Server enhanced for ICS or LRF or ISC gateway function (IMS-ALG). c17: IF A.3/1 OR A.3/4 OR A.3A/81 THEN m ELSE n/a - - UE or S-CSCF or MSC Server enhanced for ICS. c18: IF A.4/2B THEN m ELSE n/a - - initiating sessions. c19: IF A.4/2B THEN o ELSE n/a - - initiating sessions. c20: IF A.3/1 AND (A.3D/1 OR A.3D/4) THEN m ELSE n/a - - UE and (IMS AKA plus IPsec ESP or SIP digest with TLS). c21: IF A.4/30 THEN o.4 ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP). c22: IF A.4/30 AND (A.3/1 OR A.3/4 OR A.3A/81) THEN m ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and S-CSCF or UE or MSC Server enhanced for ICS. c23: IF A.4/30 AND (A.3/1 OR A.3A/81) THEN o ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and UE or MSC Server enhanced for ICS. c24: IF A.4/30 AND (A.3/4 OR A.3A/81 OR A.3A/81A) THEN m ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and S-CSCF or MSC Server enhanced for ICS or MSC server enhanced for SRVCC using SIP interface. c25: IF A.4/30 AND (A.3A/81 OR A.3/4 OR A.3/6 OR A.3/7A OR A.3/7D OR A.3/9B OR A.3/13B OR A3A/84 OR A.3A/81A OR A.3A/81B) THEN m ELSE IF A.4/30 AND A.3/1 AND (A.3B/1OR A.3B/2 OR A.3B/3 OR A.3B/4 OR A.3B/5 OR A.3B/6 OR A.3A/7 OR A.3A/8 OR A.3B/11OR A.3B/12 OR A.3B/13 OR A.3B/14 OR A.3A/15 OR A.3B/41) THEN m ELSE IF A4/30 AND A.3/1 AND (A.3B/21 OR A.3B/22 OR A.3B/23 OR A.3B/24 OR A.3B/25 OR A.3B/26 OR A.3A/27 OR A.3A/28 OR A.3B/29 OR A.3B/30) THEN o ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP), MSC Server enhanced for ICS, S-CSCF, MGCF or AS acting as terminating UA or AS acting as third-party call controller or IBCF (IMS-ALG), ISC gateway function (IMS-ALG), UE, EATF, P-Access-Network-Info values or MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c26: IF A.4/30 AND (A.3A/81 OR (A.3/4 AND A.4/2) OR A.3/6 OR A.3/7A OR A.3/7B or A.3/7D OR A.3/9B OR A.3/13B OR A3A/84 OR A.3A/89 OR A.3A/81A OR A.3A/81B) THEN m ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) MSC Server enhanced for ICS, S-CSCF, registrar, MGCF, AS acting as a terminating UA, or AS acting as an originating UA, or AS acting as third-party call controller, IBCF (IMS-ALG), ISC gateway function (IMS-ALG), EATF, ATCF (UA), MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c27: IF A.3/7D OR A.3/9D THEN o ELSE x - - AS performing 3rd party call control, IBCF (Privacy). c29: IF A.4/40A OR A.4/40B OR A.4/40C OR A.4/40D OR A.4/40E OR A.4/40F THEN m ELSE n/a - - support of any directives within caller preferences for the session initiation protocol. c30: IF A.3A/1 OR A.3A/2 THEN m ELSE IF A.3/1 OR A.3/11A OR A.3/2A THEN o ELSE n/a - - presence server, presence user agent, UE, AS, E-CSCF acting as UA, P-CSCF (IMS-ALG). c33: IF A.3/9B OR A.3/12 OR A.3/13B OR A.3A/81 OR A.3A/11 OR A.3A/12 OR A.4/44 OR A.3A/81A OR A.3A/81B THEN m ELSE o - - IBCF (IMS-ALG) or LRF or ISC gateway function (IMS-ALG) or MSC Server enhanced for ICS or conference focus or conference participant or the Session Inititation Protocol (SIP) "Replaces" header, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c34: IF A.4/44 OR A.4/45 OR A.3/9B OR A.3/13 THEN m ELSE n/a - - the Session Inititation Protocol (SIP) "Replaces" header or the Session Inititation Protocol (SIP) "Join" header or IBCF (IMS-ALG) or ISC gateway function (IMS-ALG). c35: IF A.3/4 OR A.3/9B OR A.3/13B OR A.3A/82 OR A.3A/83 OR A.3A/21 OR A.3A/22 OR A3A/84 THEN m ELSE IF (A.3/1 OR A.3/6 OR A.3/7 OR A.3/8 OR A.3A/81 OR A.3A/81A OR A.3A/81B) THEN o ELSE n/a - - S-CSCF or IBCF (IMS-ALG) or ISC gateway function (IMS-ALG) functional entities or ICS user agent or SCC application server or CSI user agent or CSI application server, UE or MGCF or AS or MRFC functional entity or MSC Server enhanced for ICS or EATF or MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c37 IF A.4/47 THEN o.3 ELSE n/a - - an extension to the session initiation protocol for request history information. c38: IF A.4/2B AND (A.3A/11 OR A.3A/12 OR A.3/7D) THEN m ELSE IF A.4/2B THEN o ELSE n/a - - initiating sessions, conference focus, conference participant, AS performing 3rd party call control. c39: IF A.3/1 THEN m ELSE IF A.3/7B OR A.3/7D OR A.3/9 THEN o ELSE n/a - - UE, AS acting as an originating UA, or AS acting as third-party call controller, IBCF. c40 IF A.3/4 OR (A.3/1 AND NOT A.3C/1) OR A.3A/81 OR A.4/22 THEN m ELSE IF (A.3/7A OR A.3/7B OR A.3/7D) THEN o ELSE n/a - - S-CSCF, UE, UE performing the functions of an external attached network, MSC Server enhanced for ICS, notifier of event information, AS, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control. c42: IF A.3/1 THEN n/a ELSE o - - UE. c43: IF A.4/2B THEN o ELSE n/a - - initiating sessions. c44: IF A.4/2C THEN m ELSE o - - initiating a session which require local and/or remote resource reservation. c45: IF A.4/97 THEN m ELSE n/a - - multiple registrations. c46 IF A.3/1 OR A.3/4 THEN o ELSE n/a - - UE, S-CSCF. c47: IF A.4/27 THEN o ELSE n/a - - a messaging mechanism for the Session Initiation Protocol (SIP). c48: IF A.3A/32 AND A.4/27 THEN m ELSE IF A.4/27 THEN o ELSE n/a - - messaging list server, a messaging mechanism for the Session Initiation Protocol (SIP). c49: IF A.3/1 OR A.3/9B OR A.3/13B OR A.3A/81 OR A.3/11 OR A.3/12 OR A3A/84 THEN m ELSE o - - UE, IBCF (IMS-ALG), ISC gateway function (IMS-ALG), MSC Server enhanced for ICS, E-CSCF, LRF, EATF. c50: IF A.3A/81 OR A.3A/81A OR A.3A/81B THEN n/a ELSE IF A.4/15 THEN o ELSE n/a - - MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface, the REFER method. c51: IF A.4/2B THEN o ELSE n/a - - initiating a session. c52: IF A.3A/11 AND A.4/2B THEN m ELSE IF A.4/2B THEN o ELSE n/a - - conference focus, initiating a session. c53: IF A.3A/81 THEN n/a ELSE IF A.4/20 THEN o ELSE n/a - - MSC Server enhanced for ICS, SIP specific event notification. c54: IF A.3/1 OR A.3/6 OR A.3/7A OR A.3/7D OR A.3/9 THEN o, ELSE n/a - - UE, MGCF, AS acting as originating UA, AS performing 3rd party call control, IBCF. c55: IF A.4/67 THEN m ELSE n/a - - number portability parameters for the 'tel' URI. c57: IF A.4/67 THEN m ELSE n/a - - number portability parameters for the 'tel' URI. c58: IF A.3/9B OR A.3/13B OR A.3/6 OR A.3A/81 OR A.3A/81A OR A.3A/81B THEN m ELSE o - - IBCF (IMS-ALG), ISC gateway function (IMS-ALG), MGCF, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c59: IF A.3/4 THEN m ELSE IF (A.3/1 OR A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/8) THEN o ELSE n/a - - S-CSCF, UE, MGCF, AS, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, or MRFC. c60: IF A.3/9B OR A.3/13B THEN m ELSE IF A.3/1 OR A.3/7A OR A.3/7B OR A.3/7D THEN o ELSE n/a - - IBCF (IMS-ALG), ISC gateway function (IMS-ALG), UE, AS acting as terminating UA, AS acting as originating UA, AS performing 3rd party call control. c61: IF (A.3/1 OR A.3A/81 OR A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/8 OR A.3/9B OR A.3/13 OR A3A/84 OR A.3A/81A OR A.3A/81B) THEN o ELSE n/a - - UE, MSC Server enhanced for ICS, MGCF, AS, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, or MRFC or IBCF (IMS-ALG), ISC gateway function (IMS-ALG), EATF, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c62: IF A.3/1 THEN o ELSE n/a - - UE. c68: IF A.3/2A OR A.3/9 OR A.4/69 OR A.3A/83 THEN m ELSE o - - P-CSCF (IMS-ALG), IBCF, extending the session initiation protocol Reason header for preemption events and Q.850 causes, SCC application server. c69: IF A.4/70 THEN o ELSE n/a - - communications resource priority for the session initiation protocol. c70: IF A.3/9B OR A.3/13B OR A.3A/102 OR A.3A/103 THEN m ELSE IF A.3/1 OR A.3/6 OR A.3/7 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3A/81 OR A.3A/81A OR A.3A/81B THEN o ELSE n/a - - IBCF (IMS-ALG), ISC gateway function (IMS-ALG), MCPTT client, MCPTT server, UE, MGCF, AS, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c72: IF A.4/70 THEN o ELSE n/a - - communications resource priority for the session initiation protocol c74: IF A.3/4 OR A.3/1 THEN o ELSE n/a. - - S-CSCF or UE. c75: IF A.3/1 THEN o ELSE n/a. - - UE. c76: IF A.4/75A OR A.4/75B THEN m ELSE n/a - - a relay within the framework for consent-based communications in SIP, a recipient within the framework for consent-based communications in SIP. c77: IF A.4/59 OR A.4/61 OR A.4/62 OR A.4/63 THEN m ELSE o - - multiple-recipient MESSAGE requests in the session initiation protocol, referring to multiple resources in the session initiation protocol, conference establishment using request-contained lists in the session initiation protocol, subscriptions to request-contained resource lists in the session initiation protocol. c78: IF (A.4/59 OR A.4/61 OR A.4/62 OR A.4/63) AND (A.3A/11 OR A.3A/31) THEN m ELSE o - - multiple-recipient MESSAGE requests in the session initiation protocol, referring to multiple resources in the session initiation protocol, conference establishment using request-contained lists in the session initiation protocol, subscriptions to request-contained resource lists in the session initiation protocol, conference focus, messaging application server. c79: IF A.3/9B OR A.3/13B OR (A.3/1 AND (A.4/2B OR A.4/15 OR A.4/20 OR A.4/27)) THEN m ELSE IF A.3/6 OR A.3/7A OR A.3/7D THEN o ELSE n/a - - IBCF (IMS-ALG), ISC gateway function (IMS-ALG), UE, initiating a session, the REFER method, SIP specific event notification, a messaging mechanism for the Session Initiation Protocol (SIP), AS acting as terminating UA, or redirect server, AS performing 3rd party call control. c80: IF A.4/2B OR A.4/15 OR A.4/20 OR A.4/27 THEN m ELSE n/a - - initiating a session, the REFER method, SIP specific event notification, a messaging mechanism for the Session Initiation Protocol (SIP). c81: IF A.3/1 OR A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D THEN o ELSE IF A.3/9B OR A.3/13B THEN m ELSE n/a - - UE, MGCF, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, IBCF (IMS-ALG), ISC gateway function (IMS-ALG). c82: IF A.3/6 OR A.3A/81 OR A.3A/81A OR A.3A/81B THEN m ELSE n/a - - MGCF, MSC server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c85: IF A.3/1 OR A.3/6 OR A.3A/81 OR A.3A/81A OR A.3A/81B OR A.3/2 OR A.3/7B THEN m ELSE n/a - - UE, MGCF, MSC Server enhanced for ICS, MSC Server enhanced for SRVCC using SIP interface, MSC Server enhanced for DRVCC using SIP interface, P-CSCF, AS acting as originating UA. c86: IF A.4/3 OR A.4/4 THEN m ELSE n/a - - client behaviour for INVITE requests, server behaviour for INVITE requests. c87: IF A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C THEN m ELSE o - - IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling). c88: IF A.3/1 OR A.3/2 THEN m ELSE o - - UE, P-CSCF. c89: IF A.3/7A OR A.3/8 THEN o ELSE n/a - - AS performing 3rd party call control, MRFC. c90: IF A.4/13 OR A.3A/53 OR A.3A/54 OR A.3A/91 OR A.3A/85 OR A.3A/86 THEN m ELSE o - - SIP INFO method and package framework, advice of charge application server, advice of charge UA client, malicious communication identification application server, in-dialog overlap signalling application server, in-dialog overlap signalling UA client. c91: IF A.3A/61 OR A.3A/62 OR A.3A/63 OR A.3A/71 THEN m ELSE o - - SM-over-IP sender, SM-over-IP receiver, IP-SM-GW, IP-SM-GW. c93: IF A.3/7B OR A.3/7D OR A3A/84 THEN o ELSE n/a - - AS acting as originating UA, AS performing 3rd party call control, EATF. c94: IF A.3/4 OR A.3/7A OR A.3/7D THEN o ELSE n/a - - S-CSCF and AS acting as terminating UA or redirect server or AS performing 3rd party call control. c96: IF A.4/30 THEN o ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c97: IF (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) AND A.4/30 THEN m ELSE IF (A.3/7D OR A.3/11 OR A.3C/1) AND A.4/30 THEN o ELSE n/a - - IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), AS performing 3rd party call control, E-CSCF, UE performing the functions of an external attached network and extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c98: IF A.3/7D OR A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C OR A.3C/1 OR A3A/84 OR A.3A/89 THEN m ELSE n/a - - AS performing 3rd party call control, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE performing the functions of an external attached network, EATF, ATCF (UA). c99: IF A.4/15 AND (A.3/9B OR A.3/9C OR A.13/B OR A.13/C) THEN m ELSE IF A.4/15 THEN o ELSE n/a - - the REFER method, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling). c100: IF A.3/6 OR A.3A/57 OR A.3A/58 OR A.3A/59 OR A.3A/60 OR A.3A/81 OR A.3A/81A OR A.3A/81B THEN m ELSE o - - MGCF, customized alerting tones application server, customized alerting tones UA client, customized ringing signal application server, customized ringing signal UA client, MSC server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c101: IF A.3D/30 OR A.3D/20A OR A.3D/20B OR A.3D/20C OR A.3D/31 THEN m ELSE n/a - - end-to-access-edge media security using SDES, end-to-access-edge media security for MSRP using TLS and certificate fingerprints, end-to-access-edge media security for BFCP using TLS and certificate fingerprints, end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints, end-to-access-edge media security for RTP media using DTLS-SRTP and certificate fingerprints. c102: IF A.3A/11 OR A.3A/12 OR A.3/9 THEN m ELSE n/a - - conference focus, conference participant, IBCF. c103: IF A.3/1 THEN o ELSE IF A.3/2 OR A.3/4 THEN m ELSE n/a - - UE, P-CSCF, S-CSCF. c104: IF A.3/9B OR A.3/13B THEN m ELSE IF A.3/7A OR A.3/7B OR A.3/7D THEN o ELSE n/a - - IBCF (IMS-ALG), ISC gateway function (IMS-ALG), AS acting as terminating UA, AS acting as originating UA, AS performing 3rd party call control. c105: IF A.3/9B OR A.3/13B OR A.3A/82 OR A.3A/83 OR A.3A/87 OR A.3A/89 THEN m ELSE o - - IBCF (IMS-ALG), ISC gateway function (IMS-ALG), ICS user agent, SCC application server, Session continuity controller UE, ATCF (UA). c106: IF A.3A/50A OR A.3A/83 OR A.3A/89 THEN m ELSE o - - Multimedia telephony application server, SCC application server, ATCF (UA). c107: IF A.3C/1 OR A.4/2 THEN o ELSE n/a - - UE performing the functions of an external attached network, registrar. c108: IF A.3/7 OR A.3/8 OR A.3/8A THEN o ELSE n/a - - AS, MRFC, MRB. c109: IF A.4/76 THEN o ELSE n/a - - a mechanism for transporting user to user call control information in SIP. c110: IF A.3/1 THEN m ELSE IF A.3/2 OR A.3/3 OR A.3/4 THEN o ELSE n/a - - UE, P-CSCF, I-CSCF, S-CSCF. c111: IF A.3/1 OR A.3/2 THEN m ELSE n/a - - UE, P-CSCF. c112: IF NOT (A.3/1 AND NOT A.3C/1) THEN o ELSE n/a - - not UE, UE performing the functions of an external attached network. c113: IF A.4/104 THEN o.7 ELSE n/a - - SIP overload control. c114: IF A.4/104 THEN IF A.3/4 OR A.3/7 OR A.3/10 THEN o.7 ELSE n/a - - SIP overload control, S-CSCF, AS, additional routeing functionality. c115: IF A.3/6 OR A.3/9 OR A.3/7 THEN o ELSE n/a - - MGCF, IBCF, AS c116: IF (A.3/1 AND A.4/127) OR A.3/2A OR A.3/6 OR A.3/7 OR A.3/9 THEN o ELSE IF (A.3/1 AND NOT A.4/127) THEN x ELSE n/a - - UE, transfer of an updated MSD for PSAP callback, P-CSCF (IMS-ALG), MGCF, AS, IBCF, UE, not transfer of an updated MSD for PSAP callback. c117 IF A.3/2 OR A.3/4 OR OR A.3/9 OR A.3A/81 OR A.3A/83 OR A.3A/89 OR A.3A/81A THEN o ELSE n/a - - P-CSCF, S-CSCF, IBCF, MSC server enhanced for ICS, SCC application server, ATCF (UA), MSC server enhanced for SRVCC using SIP interface. c118: IF A.4/49 THEN o ELSE n/a - - session initiation protocol URIs for applications such as voicemail and interactive voice response (NOTE 3). c119: IF A.3/2A OR A.3/9 THEN o ELSE n/a - - P-CSCF (IMS-ALG), IBCF. c120: IF A.3/2A OR A.3/9 THEN o ELSE n/a - - P-CSCF (IMS-ALG), IBCF. c121: IF A.4/15 THEN m ELSE n/a - - the REFER method. c122: IF A.4/22 THEN m ELSE n/a - - act as a notifier. c123: IF A.4/111 AND (A.3/7A OR A.3/7B OR A.3/9A OR A.3/9B OR A.3/13A OR A.3/13B) THEN m ELSE IF A.3/4 OR A.3/7 OR A.3A/102 THEN o ELSE n/a.-.-.the Relayed-Charge header field extension, AS acting as terminating UA, or redirect server, AS acting as originating UA, IBCF (THIG), IBCF (IMS-ALG), ISC gateway function (THIG), ISC gateway function (THIG), S-CSCF, AS, transit function. c124: IF A.3/2A OR A.3/9B OR A.3/7 THEN o ELSE n/a - - P-CSCF (IMS-ALG), I-BCF (IMS-ALG), AS. c125: IF (A.3/4 OR A.3/6 OR A.3/7A OR A.3/7D OR A.3/9B OR A.3/13B OR A.3A/84 OR A.3A/89 OR A.3/2A OR A.3/8 OR A.3/11A) THEN m ELSE IF A.3/1 AND (A.3B/11 OR A.3B/12 OR A.3B/13 OR A.3B/14 OR A.3B/15) AND (A.3B/1 OR A.3B/2 OR A.3B/3 OR A.3B/4 OR A.3B/5 OR A.3B/6 OR A.3B/7 OR A.3B/8 OR A.3B/9) THEN m ELSE n/a. - - S-CSCF, MGCF, AS acting as terminating UA, AS acting as third-party call controller, IBCF (IMS-ALG), ISC gateway function (IMS-ALG), EATF, ATCF acting as UA, P-CSCF (IMS-ALG), MRFC, E-CSCF acting as UA, UE. c126: IF A.4/78 THEN o ELSE n/a - - the SIP P-Served-User private header for the 3GPP IM CN subsystem. c127: IF A.4/78 THEN m ELSE n/a - - the SIP P-Served-User private header for the 3GPP IM CN subsystem. c128: IF A.3/2A OR A.3/9B OR A.3/7 OR A.3A/103 THEN o ELSE n/a - - P-CSCF (IMS-ALG), IBCF (IMS-ALG), AS, MCPTT server. c129 IF A.3/6 OR A.3/7 OR A.3/9 OR A.3A/81 OR A.3A/81A OR A.3A/81B THEN o ELSE n/a - - MGCF, AS, IBCF, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c130: IF A.3/1 OR A.3/7 THEN o ELSE n/a - - UE, AS, c131: IF A.3/6 OR A.3A/81 OR A.3A/81A OR A.3A/81B THEN o ELSE n/a - - MGCF, MSC server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c132: IF A.3/6 OR A.3/7 OR A.3/9 THEN o ELSE n/a - - MGCF, AS, IBCF. c133: IF A.3/2 OR A.3/7 OR A.3/9 THEN o ELSE n/a - - P-CSCF, AS, IBCF. c134 IF A.4/60 THEN o ELSE n/a - - the Geolocation header field c135: IF A.3/1 OR A.3/2 OR A.3/7 OR A.3/9 THEN o ELSE n/a - - UE, P-CSCF, AS, IBCF. c136: IF A.3/1 THEN o ELSE n/a - - UE. c137: IF A.3/7 OR A.3/9 THEN o ELSE n/a - - AS, IBCF. c138: IF A.4/38C AND (A.3/7 OR A.3/9) THEN m ELSE n/a - - Multiple SIP Reason Header Field Values (carrying STIR codes in Reason header fields in SIP responses), AS, IBCF. o.1: At least one of these capabilities is supported. o.2: At least one of these capabilities is supported. o.3: At least one of these capabilities is supported. o.4: At least one of these capabilities is supported. o.5: At least one of these capabilities is supported. o.6: It is mandatory to support at least one of these items. o.7: At least one of these capabilities is supported. NOTE 1: An AS acting as a proxy may be outside the trust domain, and therefore not able to support the capability for that reason; in this case it is perfectly reasonable for the header to be passed on transparently, as specified in the PDU parts of the profile. NOTE 2: If a UE is unable to become engaged in a service that potentially requires the ability to identify and interact with a specific UE even when multiple UEs share the same single Public User Identity then the UE support can be "o" instead of "m". Examples include telemetry applications, where point-to-point communication is desired between two users. NOTE 3: AS performing a service number translation (eg. Freephone) Prerequisite A.4/20 - - SIP specific event notification Table A.4A: Supported event packages Item Does the implementation support Subscriber Notifier Ref. RFC status Profile status Ref. RFC status Profile status 1 reg event package? [43] c1 c3 [43] c2 c4 1A reg event package extension for GRUUs? [94] c1 c25 [94] c2 c4 2 refer package? [36] 3 c13 c13 [36] 3 c13 c13 3 presence package? [74] 6 c1 c5 [74] 6 c2 c6 4 eventlist with underlying presence package? [75], [74] 6 c1 c7 [75], [74] 6 c2 c8 5 presence.winfo template-package? [72] 4 c1 c9 [72] 4 c2 c10 6 xcap-diff package? [77] 4 c1 c11 [77] 4 c2 c12 7 conference package? [78] 3 c1 c21 [78] 3 c1 c22 8 message-summary package? [65] c1 c23 [65] 3 c2 c24 9 poc-settings package? [110] c1 c26 [110] c2 c27 11 dialog event package? [171] c1 c14 [171] c2 c15 12 load-control package? [201] c29 c30 [201] c29 c31 c1: IF A.4/23 THEN o ELSE n/a - - acting as the subscriber to event information. c2: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c3: IF A.3/1 OR A.3A/81 OR A.3/2 THEN m ELSE IF A.3/7 THEN o ELSE n/a - - UE, MSC Server enhanced for ICS, P-CSCF, AS. c4: IF A.3/4 THEN m ELSE IF A.3C/1 THEN o ELSE n/a - - S-CSCF, UE performing the functions of an external attached network. c5: IF A.3A/3 OR A.3A/4 THEN m ELSE IF A.4/23 OR A.3/12 THEN o ELSE n/a - - resource list server or watcher, acting as the subscriber to event information, LRF. c6: IF A.3A/1 THEN m ELSE IF A.4/22 OR A.3/11A THEN o ELSE n/a - - presence server, acting as the notifier of event information, E-CSCF acting as UA. c7: IF A.3A/4 THEN m ELSE IF A.4/23 THEN o ELSE n/a - - watcher, acting as the subscriber to event information. c8: IF A.3A/3 THEN m ELSE IF A.4/22 THEN o ELSE n/a - - resource list server, acting as the notifier of event information. c9: IF A.3A/2 THEN m ELSE IF A.4/23 THEN o ELSE n/a - - presence user agent, acting as the subscriber to event information. c10: IF A.3A/1 THEN m ELSE IF A.4/22 THEN o ELSE n/a - - presence server, acting as the notifier of event information. c11: IF A.3A/2 OR A.3A/4 OR A.3A/56 THEN o ELSE IF A.4/23 THEN o ELSE n/a - - presence user agent or watcher or Ut reference point XCAP client for supplementary services, acting as the subscriber to event information. c12: IF A.3A/1 OR A.3A/3 OR A.3A/55 THEN m ELSE IF A.4/22 THEN o ELSE n/a - - presence server or resource list server or Ut reference point XCAP server for supplementary services, acting as the notifier of event information. c13: IF A.4/15 THEN m ELSE n/a - - the REFER method. c14: IF A.3/12 OR A.3A/87 THEN m ELSE IF A.3/1 OR A.3/7B OR A.3/7D THEN o ELSE n/a - - LRF, session continuity controller UE, UE, AS acting as originating UA, AS performing 3rd party call control. c15: IF A.3/11 OR A.3A/83 THEN m ELSE IF A.3/1 OR A.3/7A OR A.3/7D THEN o ELSE n/a - - E-CSCF, SCC application server, UE, AS acting as terminating UA, or redirect server, AS performing 3rd party call control. c21: IF A.3A/12 THEN m ELSE IF A.4/23 THEN o ELSE n/a - - conference participant or acting as the subscriber to event information. c22: IF A.3A/11 THEN m ELSE IF A.4/22 THEN o ELSE n/a - - conference focus or acting as the notifier of event information. c23: IF A.3A/52 THEN m ELSE (A.3/1 OR A.3/7A OR A.3/7B) AND A.4/23 THEN o ELSE n/a - - message waiting indication subscriber UA, UE, AS acting as terminating UA, or redirect server, AS acting as originating UA all as subscriber of event information. c24: IF A.3A/52 THEN m ELSE (A.3/1 OR A.3/7A OR A.3/7B) AND A.4/22 THEN o ELSE n/a - - message waiting indication notifier UA, UE, AS acting as terminating UA, or redirect server, AS acting as originating UA all as notifier of event information. c25: IF A.4A/1 THEN (IF A.3/1 AND A.4/53 THEN m ELSE o) ELSE n/a - - reg event package, UE, reg event package extension for GRUUs. c26: IF (A.3/7B OR A.3/1) AND (A.4/23 OR A.4/41) THEN o ELSE n/a - - AS acting as originating UA, UE, acting as the subscriber to event information, an event state publication extension to the session initiation protocol. c27: IF (A.4/22 OR A.4/41) AND A.3/1 THEN o ELSE n/a - - UE, acting as the notifier of event information, an event state publication extension to the session initiation protocol. c28: IF A.3/1 OR A.3A/81 OR A.3/2 OR A.3/7B THEN m ELSE n/a - - UE, MSC Server enhanced for ICS, P-CSCF, AS acting as originating UA. c29: IF A.4/104B THEN m ELSE n/a - - distribution of load filters. c30: IF A.4/104B THEN IF A.3/4 OR A.3/7 OR A.3/9 THEN m ELSE n/a - - distribution of load filters. S-CSCF, IBCF, AS. c31: IF A.4/104B THEN If A.3/7 THEN m ELSE n/a - - distribution of load filters, AS. Prerequisite A.4/13 - - SIP INFO method and package framework. Table A.4B: Supported info packages Item Does the implementation support Sender Receiver Ref. RFC status Profile status Ref. RFC status Profile status 1 DTMF info package? 7.12.1 n/a c1 7.12.1 n/a c1 2 g.3gpp.mid-call? [8M] n/a c2 [8M] n/a c3 3 g.3gpp.ussd? [8W] n/a c4 [8W] n/a c4 4 g.3gpp.current-location-discovery info package ? subclause 7.12.2.1 n/a c5 subclause 7.12.2.1 n/a c6 5 EmergencyCallData.eCall.MSD Info-Package [244] 14.9 m c7 [244] 14.9 m c7 c1: IF A.3/6 OR A.3A/57 OR A.3A/58 OR A.3A/59 OR A.3A/60 THEN m ELSE o - - MGCF, customized alerting tones application server, customized alerting tones UA client, customized ringing signal application server, customized ringing signal UA client. c2: IF A.3A/83 THEN o ELSE n/a - - SCC application server. c3: IF A.3A/81 OR A.3A/81B THEN o ELSE n/a - - MSC server enhanced for ICS, MSC server enhanced for DRVCC using SIP interface. c4: IF A.3A/92 OR A.3A/93 THEN m ELSE n/a - - USSI UE, USSI AS. c5: IF A.3/11A OR A.3/2A THEN o ELSE n/a - - E-CSCF acting as UA, P-CSCF (IMS-ALG). c6: IF (A.3/1 AND (A.3B/11 OR A.3B/12 OR A.3B/13 OR A.3B/14 OR A.3B/15)) OR A.3/2A THEN o ELSE n/a - - UE, IEEE-802.11, IEEE-802.11a, IEEE-802.11b, IEEE-802.11g, IEEE-802.11n, IEEE-802.11ac, P-CSCF (IMS-ALG). c7: IF (A.3/1 AND A.4/120) THEN m ELSE n/a - - UE, Next-Generation Pan-European eCall emergency service. Table A.4C: Supported media control packages Item Does the implementation support Sender Receiver Ref. RFC status Profile status Ref. RFC status Profile status 1 msc-ivr/1.0 [147] c1 [147] c2 2 msc-mixer/1.0 [148] c1 [148] c2 3 mrb-publish/1.0 [192] c3 [192] c4 c1: IF A.3/7D THEN o ELSE n/a - - AS performing 3rd party call control. c2: IF A.3/8 THEN o ELSE n/a - - MRFC. c3: IF A.3/8 THEN o ELSE n/a - - MRFC. c4: IF A.3/8A THEN o ELSE n/a - - MRB. A.2.1.3 PDUs Table A.5: Supported methods Item PDU Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 ACK request [26] 13 c10 c10 [26] 13 c11 c11 2 BYE request [26] 15.1 c12 c12 [26] 15.1 c12 c12 3 BYE response [26] 15.1 c12 c12 [26] 15.1 c12 c12 4 CANCEL request [26] 9 m m [26] 9 m m 5 CANCEL response [26] 9 m m [26] 9 m m 6 INFO request [25] 4.2 c21 c21 [25] 4.2 c21 c21 7 INFO response [25] 4.2 c21 c21 [25] 4.2 c21 c21 8 INVITE request [26] 13 c10 c10 [26] 13 c11 c11 9 INVITE response [26] 13 c11 c11 [26] 13 c10 c10 9A MESSAGE request [50] 4 c7 c7 [50] 7 c7 c7 9B MESSAGE response [50] 4 c7 c7 [50] 7 c7 c7 10 NOTIFY request [28] 8.1.2 c4 c4 [28] 8.1.2 c3 c3 11 NOTIFY response [28] 8.1.2 c3 c3 [28] 8.1.2 c4 c4 12 OPTIONS request [26] 11 m m [26] 11 m m 13 OPTIONS response [26] 11 m m [26] 11 m m 14 PRACK request [27] 6 c5 c5 [27] 6 c5 c5 15 PRACK response [27] 6 c5 c5 [27] 6 c5 c5 15A PUBLISH request [70] 11.1.3 c20 c20 [70] 11.1.3 c20 c20 15B PUBLISH response [70] 11.1.3 c20 c20 [70] 11.1.3 c20 c20 16 REFER request [36] 3 c1 c1 [36] 3 c1 c1 17 REFER response [36] 3 c1 c1 [36] 3 c1 c1 18 REGISTER request [26] 10 c8 c8 [26] 10 c9 c9 19 REGISTER response [26] 10 c9 c9 [26] 10 c8 c8 20 SUBSCRIBE request [28] 8.1.1 c3 c3 [28] 8.1.1 c4 c4 21 SUBSCRIBE response [28] 8.1.1 c4 c4 [28] 8.1.1 c3 c3 22 UPDATE request [29] 6.1 c6 c6 [29] 6.2 c6 c6 23 UPDATE response [29] 6.2 c6 c6 [29] 6.1 c6 c6 c1: IF A.4/15 THEN m ELSE n/a - - the REFER method extension. c3: IF A.4/23 THEN m ELSE n/a - - recipient for event information. c4: IF A.4/22 THEN m ELSE n/a - - notifier of event information. c5: IF A.4/14 THEN m ELSE n/a - - reliability of provisional responses extension. c6: IF A.4/17 THEN m ELSE n/a - - the SIP update method extension. c7: IF A.4/27 THEN m ELSE n/a - - the SIP MESSAGE method. c8: IF A.4/1 THEN m ELSE n/a - - client behaviour for registration. c9: IF A.4/2 THEN m ELSE n/a - - registrar. c10: IF A.4/3 THEN m ELSE n/a - - client behaviour for INVITE requests. c11: IF A.4/4 THEN m ELSE n/a - - server behaviour for INVITE requests. c12: IF A.4/5 THEN m ELSE n/a - - session release. c20: IF A.4/41 THEN m ELSE n/a - - event state publication extension. c21: IF A.4/13 OR A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. A.2.1.4 PDU parameters A.2.1.4.1 Status-codes Table A.6: Supported status-codes Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 100 (Trying) [26] 21.1.1 c21 c21 [26] 21.1.1 c11 c11 101 1xx response [26] 21.1 p21 p21 [26] 21.1 p21 p21 101A 18x response [26] 21.1 p21 p21 [26] 21.1 p21 p21 2 180 (Ringing) [26] 21.1.2 c2 c2 [26] 21.1.2 c1 c1 3 181 (Call Is Being Forwarded) [26] 21.1.3 c2 c2 [26] 21.1.3 c1 c1 4 182 (Queued) [26] 21.1.4 c2 c2 [26] 21.1.4 c1 c1 5 183 (Session Progress) [26] 21.1.5 c34 c34 [26] 21.1.5 c1 c1 5A 199 (Early Dialog Terminated) [142] 11.1 c32 c32 [142] 11.1 c32 c32 102 2xx response [26] 21.2 p22 p22 [26] 21.1 p22 p22 6 200 (OK) [26] 21.2.1 m m [26] 21.2.1 m m 7 202 (Accepted) [28] 8.3.1 c36 c36 [28] 8.3.1 c37 c37 103 3xx response [26] 21.3 p23 p23 [26] 21.1 p23 p23 8 300 (Multiple Choices) [26] 21.3.1 m m [26] 21.3.1 m m 9 301 (Moved Permanently) [26] 21.3.2 m m [26] 21.3.2 m m 10 302 (Moved Temporarily) [26] 21.3.3 m m [26] 21.3.3 m m 11 305 (Use Proxy) [26] 21.3.4 m m [26] 21.3.4 m m 12 380 (Alternative Service) [26] 21.3.5 m m [26] 21.3.5 m m 104 4xx response [26] 21.4 p24 p24 [26] 21.4 p24 p24 13 400 (Bad Request) [26] 21.4.1 m m [26] 21.4.1 m m 14 401 (Unauthorized) [26] 21.4.2 o c12 [26] 21.4.2 m m 15 402 (Payment Required) [26] 21.4.3 n/a n/a [26] 21.4.3 n/a n/a 16 403 (Forbidden) [26] 21.4.4 m m [26] 21.4.4 m m 17 404 (Not Found) [26] 21.4.5 m m [26] 21.4.5 m m 18 405 (Method Not Allowed) [26] 21.4.6 m m [26] 21.4.6 m m 19 406 (Not Acceptable) [26] 21.4.7 m m [26] 21.4.7 m m 20 407 (Proxy Authentication Required) [26] 21.4.8 o o [26] 21.4.8 m m 21 408 (Request Timeout) [26] 21.4.9 c2 c2 [26] 21.4.9 m m 22 410 (Gone) [26] 21.4.10 m m [26] 21.4.10 m m 22A 412 (Conditional Request Failed) [70] 11.2.1 c20 c20 [70] 11.2.1 c20 c20 23 413 (Request Entity Too Large) [26] 21.4.11 m m [26] 21.4.11 m m 24 414 (Request-URI Too Large) [26] 21.4.12 m m [26] 21.4.12 m m 25 415 (Unsupported Media Type) [26] 21.4.13 m m [26] 21.4.13 m m 26 416 (Unsupported URI Scheme) [26] 21.4.14 m m [26] 21.4.14 m m 26A 417 (Unknown Resource Priority) [116] 4.6.2 c24 c24 [116] 4.6.2 c24 c24 27 420 (Bad Extension) [26] 21.4.15 m c13 [26] 21.4.15 m m 28 421 (Extension Required) [26] 21.4.16 o o [26] 21.4.16 i i 28A 422 (Session Interval Too Small) [58] 6 c7 c7 [58] 6 c7 c7 29 423 (Interval Too Brief) [26] 21.4.17 c4 c4 [26] 21.4.17 m m 29A 424 (Bad Location Information) [89] 4.2 c23 c23 [89] 4.2 c23 c23 29AA 428 Use Identity Header [252] 6.2.2 c40 c40 [252] 6.2.2 c40 c40 29B 429 (Provide Referrer Identity) [59] 5 c8 c8 [59] 5 c9 c9 29C 430 (Flow Failed) [92] 11 n/a n/a [92] 11 c22 c22 29D 433 (Anonymity Disallowed) [67] 4 c14 c14 [67] 4 c14 c14 29DA 436 Bad Identity Info [252] 6.2.2 c40 c40 [252] 6.2.2 c40 c40 29DB 437 Unsupported Credential [252] 6.2.2 c40 c40 [252] 6.2.2 c40 c40 29DC 438 Invalid Identity Header [252] 6.2.2 c40 c40 [252] 6.2.2 c40 c40 29E 439 (First Hop Lacks Outbound Support) [92] 11 c28 c28 [92] 11 c29 c29 29F 440 (Max Breadth Exceeded) [117] 5 n/a c30 [117] 5 c31 c31 29G 469 (Bad INFO Package) [25] 4.2 c33 c33 [25] 4.2 c33 c33 29H 470 (Consent Needed) [125] 5.9.2 c26 c26 [125] 5.9.2 c27 c27 30 480 (Temporarily Unavailable) [26] 21.4.18 m m [26] 21.4.18 m m 31 481 (Call/Transaction Does Not Exist) [26] 21.4.19 m m [26] 21.4.19 m m 32 482 (Loop Detected) [26] 21.4.20 m m [26] 21.4.20 m m 33 483 (Too Many Hops) [26] 21.4.21 m m [26] 21.4.21 m m 34 484 (Address Incomplete) [26] 21.4.22 o o [26] 21.4.22 m m 35 485 (Ambiguous) [26] 21.4.23 o o [26] 21.4.23 m m 36 486 (Busy Here) [26] 21.4.24 m m [26] 21.4.24 m m 37 487 (Request Terminated) [26] 21.4.25 m m [26] 21.4.25 m m 38 488 (Not Acceptable Here) [26] 21.4.26 m m [26] 21.4.26 m m 39 489 (Bad Event) [28] 8.3.2 c3 c3 [28] 8.3.2 c3 c3 40 491 (Request Pending) [26] 21.4.27 m m [26] 21.4.27 m m 41 493 (Undecipherable) [26] 21.4.28 m m [26] 21.4.28 m m 41A 494 (Security Agreement Required) [48] 2 c5 c5 [48] 2 c6 c6 105 5xx response [26] 21.5 p25 p25 [26] 21.5 p25 p25 42 500 (Internal Server Error) [26] 21.5.1 m m [26] 21.5.1 m m 43 501 (Not Implemented) [26] 21.5.2 m m [26] 21.5.2 m m 44 502 (Bad Gateway) [26] 21.5.3 o o [26] 21.5.3 m m 45 503 (Service Unavailable) [26] 21.5.4 m m [26] 21.5.4 m m 46 504 (Server Time-out) [26] 21.5.5 m m [26] 21.5.5 m m 47 505 (Version not supported) [26] 21.5.6 m m [26] 21.5.6 m m 48 513 (Message Too Large) [26] 21.5.7 m m [26] 21.5.7 m m 49 580 (Precondition Failure) [30] 8 c35 c35 [30] 8 c35 c35 106 6xx response [26] 21.6 p26 p26 [26] 21.6 p26 p26 50 600 (Busy Everywhere) [26] 21.6.1 m m [26] 21.6.1 m m 51 603 (Decline) [26] 21.6.2 c10 c10 [26] 21.6.2 m m 52 604 (Does Not Exist Anywhere) [26] 21.6.3 m m [26] 21.6.3 m m 53 606 (Not Acceptable) [26] 21.6.4 m m [26] 21.6.4 m m 54 607 (Unwanted) [254] o c38 [254] o c39 c1: IF A.5/9 THEN m ELSE n/a - - INVITE response. c2: IF A.5/9 THEN o ELSE n/a - - INVITE response. c3: IF A.4/20 THEN m ELSE n/a - - SIP specific event notification extension. c4: IF A.5/19 OR A.5/21 THEN m ELSE n/a - - REGISTER response or SUBSCRIBE response. c5: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. c6: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. c7: IF A.4/42 AND (A.5/9 OR A.5/23) THEN m ELSE n/a - - the SIP session timer AND (INVITE response OR UPDATE response). c8: IF A.4/43 AND A.5/17 THEN o ELSE n/a - - the SIP Referred-By mechanism and REFER response. c9: IF A.4/43 AND A.5/17 THEN m ELSE n/a - - the SIP Referred-By mechanism and REFER response. c10: IF A.4/44 THEN m ELSE o - - the Session Inititation Protocol (SIP) "Replaces" header. c11: IF A.5/3 OR A.5/9 OR A.5/9B OR A.5/11OR A.5/13 OR A.5/15 OR A.5/15B OR A.5/17 OR A.5/19 OR A.5/21 OR A.5/23 THEN m ELSE n/a - - BYE response or INVITE response or MESSAGE response or NOTIFY response or OPTIONS response or PRACK response or PUBLISH response or REFER response or REGISTER response or SUBSCRIBE response or UPDATE response. c12: IF A.3/4 THEN m ELSE o - - S-CSCF. c13: IF A.3/1 OR A.3/2 OR A.3/4 THEN m ELSE o - - UE, P-CSCF, S-CSCF. c14: IF A.4/48 THEN m ELSE n/a - - rejecting anonymous requests in the session initiation protocol. c20: IF A.4/41 THEN m ELSE n/a - - an event state publication extension to the session initiation protocol. c21: IF A.5/3 OR A.5/9 OR A.5/9B OR A.5/11 or A.5/13 OR A.5/15 OR A.5/15B OR A.5/17 OR A.5/19 OR A.5/21 OR A.5/23 THEN o ELSE n/a - - BYE response or INVITE response or MESSAGE response or NOTIFY response or OPTIONS response or PRACK response or PUBLISH response or REFER response or REGISTER response or SUBSCRIBE response or UPDATE response. c22: IF A.4/57 THEN m ELSE n/a - - managing client initiated connections in SIP. c23: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c24: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c26: IF A.4/75B THEN m ELSE n/a - - a recipient within the framework for consent-based communications in SIP. c27: IF A.4/75A THEN m ELSE n/a - - a relay within the framework for consent-based communications in SIP. c28: IF A.4/2 AND A.4/57 THEN m ELSE n/a - - registrar, managing client initiated connections in SIP. c29: IF A.4/1 AND A.4/57 THEN m ELSE n/a - - client behaviour for registration, managing client initiated connections in SIP. c30: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling). c31: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c32: IF A.5/9 AND A.4/81 THEN m ELSE n/a - - INVITE response and 199 (Early Dialog Terminated) response. c33: IF A.4/13 THEN m ELSE n/a - - SIP INFO method and package framework. c34: IF A.4/16 OR A.3/6 THEN m ELSE IF A.5/9 THEN o ELSE n/a - - initiating a session which require local and/or remote resource reservation, MGCF, INVITE response. c35: IF A.4/16 THEN m ELSE n/a - - integration of resource management and SIP. c36: IF A.5/9B THEN m ELSE n/a - - MESSAGE response. c37: IF A.4/20 OR OR A.5/9B OR A.5/17 THEN m ELSE n/a - - SIP specific event notification extension or MESSAGE response or the REFER response. c.38: IF A.4/117 THEN o ELSE n/a - - a SIP response code for unwanted calls extension. c.39: IF A.4/117 THEN m ELSE n/a - - a SIP response code for unwanted calls extension. c.40 IF A.4/116 THEN m ELSE n/a - authenticated identity management in the Session Initiation Protocol p21: A.6/2 OR A.6/3 OR A.6/4 OR A.6/5 OR A.6/5A - - 1xx response. p22: A.6/6 OR A.6/7 - - 2xx response. p23: A.6/8 OR A.6/9 OR A.6/10 OR A.6/11 OR A.6/12 - - 3xx response. p24: A.6/13 OR A.6/14 OR A.6/15 OR A.6/16 OR A.6/17 OR A.6/18 OR A.6/19 OR A.6/20 OR A.6/21 OR A.6/22 OR A.6/22A OR A.6/23 OR A.6/24 OR A.6/25 OR A.6/26 OR A.6/26A OR A.6/27 OR A.6/28 OR A.6/28A OR A.6/29 OR A.6/29A OR A.6/29B OR A.6/29C OR A.6/29D OR A.6/29E OR A.6/29F OR A.6/29G OR A.6/29H OR A.6/30 OR A.6/31 OR A.6/32 OR A.6/33 OR A.6/34 OR A.6/35 OR A.6/36 OR A.6/436 OR A.6/38 OR A.6/39 OR A.6/40 OR A.6/41 OR A.6/41A. - 4xx response. p25: A.6/42 OR A.6/43 OR A.6/44 OR A.6/45 OR A.6/46 OR A.6/47 OR A.6/48 OR A.6/49 - - 5xx response p26: A.6/50 OR A.6/51 OR A.6/52 OR A.6/53 - - 6xx response. A.2.1.4.2 ACK method Prerequisite A.5/1 – ACK request Table A.7: Supported header fields within the ACK request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Contact [56B] 9.2 c9 c9 [56B] 9.2 c10 c10 2 Allow-Events [28] 8.2.2 c1 c1 [28] 8.2.2 c2 c2 3 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 4 Call-ID [26] 20.8 m m [26] 20.8 m m 5 Cellular-Network-Info 7.2.15 n/a c26 7.2.15 n/a c27 6 Content-Disposition [26] 20.11 o o [26] 20.11 m m 7 Content-Encoding [26] 20.12 o o [26] 20.12 m m 7A Content-ID [256] 3.2 o c29 [256] 3.2 m c30 8 Content-Language [26] 20.13 o o [26] 20.13 m m 9 Content-Length [26] 20.14 m m [26] 20.14 m m 10 Content-Type [26] 20.15 m m [26] 20.15 m m 11 CSeq [26] 20.16 m m [26] 20.16 m m 12 Date [26] 20.17 c4 c4 [26] 20.17 m m 13 From [26] 20.20 m m [26] 20.20 m m 13A Max-Breadth [117] 5.8 n/a c14 [117] 5.8 c15 c15 14 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c16 15 MIME-Version [26] 20.24 o o [26] 20.24 m m 15A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c19 c20 [52] 4.4, [52A] 4, [234] 2 c19 c21 15C Privacy [33] 4.2 c6 n/a [33] 4.2 c6 n/a 15D P-Charging-Vector [52] 4.6, [52A] 4 c22 c23 [52] 4.6, [52A] 4 c22 c23 15E Priority-Share Subclause 7.2.16 n/a c28 Subclause 7.2.16 n/a c28 16 Proxy-Authorization [26] 20.28 c5 c5 [26] 20.28 n/a n/a 17 Proxy-Require [26] 20.29 o n/a [26] 20.29 n/a n/a 17A Reason [34A] 2 c8 c8 [34A] 2 c8 c8 17B Record-Route [26] 20.30 n/a c16 [26] 20.30 n/a c16 17C Recv-Info [25] 5.2.3 c17 c17 [25] 5.2.3 c17 c17 17D Reject-Contact [56B] 9.2 c9 c9 [56B] 9.2 c10 c10 17E Relayed-Charge 7.2.12 n/a c24 7.2.12 n/a c24 17F Request-Disposition [56B] 9.1 c9 c9 [56B] 9.1 c10 c10 18 Require [26] 20.32 n/a n/a [26] 20.32 n/a n/a 18A Resource-Priority [116] 3.1 c11 c11 [116] 3.1 c11 c11 18B Resource-Share Subclause 7.2.13 n/a c25 Subclause 7.2.13 n/a c25 19 Route [26] 20.34 m m [26] 20.34 n/a c16 19A Session-ID [162] o c18 [162] o c18 20 Timestamp [26] 20.38 c7 c7 [26] 20.38 m m 21 To [26] 20.39 m m [26] 20.39 m m 22 User-Agent [26] 20.41 o o [26] 20.41 m m 23 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c2: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c6: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c8: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c9: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c10: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c11: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c14: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling). c15: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c16: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c17: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c18: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c19: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c20: IF A.4/34 AND A.3/1 OR A.3/2A OR A.3/7 OR A.3A/81 OR A.3A/81A OR A.3A/81B THEN o ELSE n/a - - the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG), AS, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c21: IF A.4/34 AND A.3/1 OR A.3/7 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE, AS. c22: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c23: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c24: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c25: IF A.4/112 THEN o ELSE n/a - - resource sharing. c26: IF A.4/113 AND A.3/1 OR A.3/2A OR A.3/7 THEN o ELSE n/a - - the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG), AS. c27: IF A.4/113 AND A.3/7 THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS. c28: IF A.4/114 THEN o ELSE n/a - - priority sharing. c29: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c30: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). Prerequisite A.5/1 – ACK request Table A.8: Supported message bodies within the ACK request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.1.4.3 BYE method Prerequisite A.5/2 - - BYE request Table A.9: Supported header fields within the BYE request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o o [26] 20.1 m m 1A Accept-Contact [56B] 9.2 c18 c18 [56B] 9.2 c22 c22 2 Accept-Encoding [26] 20.2 o o [26] 20.2 m m 3 Accept-Language [26] 20.3 o o [26] 20.3 m m 3A Allow [26] 20.5 o o [26] 20.5 m m 4 Allow-Events [28] 8.2.2 c1 c1 [28] 8.2.2 c2 c2 5 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 6 Call-ID [26] 20.8 m m [26] 20.8 m m 6A Cellular-Network-Info 7.2.15 n/a c35 7.2.15 n/a c36 7 Content-Disposition [26] 20.11 o o [26] 20.11 m m 8 Content-Encoding [26] 20.12 o o [26] 20.12 m m 8A Content-ID [256] 3.2 o c37 [256] 3.2 m c38 9 Content-Language [26] 20.13 o o [26] 20.13 m m 10 Content-Length [26] 20.14 m m [26] 20.14 m m 11 Content-Type [26] 20.15 m m [26] 20.15 m m 12 CSeq [26] 20.16 m m [26] 20.16 m m 13 Date [26] 20.17 c4 c4 [26] 20.17 m m 14 From [26] 20.20 m m [26] 20.20 m m 14A Geolocation [89] 4.1 c23 c23 [89] 4.1 c23 c23 14B Geolocation-Routing [89] 4.2 c23 c23 [89] 4.2 c23 c23 14C Max-Breadth [117] 5.8 n/a c29 [117] 5.8 c30 c30 15 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c31 16 MIME-Version [26] 20.24 o o [26] 20.24 m m 16A P-Access-Network-Info [52] 4.4, [234] 2 c9 c10 [52] 4.4, [234] 2 c9 c11 16B P-Asserted-Identity [34] 9.1 n/a n/a [34] 9.1 c6 c6 16C P-Charging-Function-Addresses [52] 4.5 c13 c14 [52] 4.5 c13 c14 16D P-Charging-Vector [52] 4.6 c12 c34 [52] 4.6 c12 c34 16F P-Preferred-Identity [34] 9.2 c6 x [34] 9.2 n/a n/a 16G Privacy [33] 4.2 c7 n/a [33] 4.2 c7 c7 17 Proxy-Authorization [26] 20.28 c5 c5 [26] 20.28 n/a n/a 18 Proxy-Require [26] 20.29 o n/a [26] 20.29 n/a n/a 18A Reason [34A] 2 c17 c21 [34A] 2 c24 c24 19 Record-Route [26] 20.30 n/a c31 [26] 20.30 n/a c31 19A Referred-By [59] 3 c19 c19 [59] 3 c20 c20 19B Reject-Contact [56B] 9.2 c18 c18 [56B] 9.2 c22 c22 19C Relayed-Charge 7.2.12 n/a c33 7.2.12 n/a c33 19D Request-Disposition [56B] 9.1 c18 c18 [56B] 9.1 c22 c22 20 Require [26] 20.32 m m [26] 20.32 m m 20A Resource-Priority [116] 3.1 c25 c25 [116] 3.1 c25 c25 21 Route [26] 20.34 m m [26] 20.34 n/a c31 21A Security-Client [48] 2.3.1 c15 c15 [48] 2.3.1 n/a n/a 21B Security-Verify [48] 2.3.1 c16 c16 [48] 2.3.1 n/a n/a 21C Session-ID [162] o c32 [162] o c32 22 Supported [26] 20.37 o o [26] 20.37 m m 23 Timestamp [26] 20.38 c8 c8 [26] 20.38 m m 24 To [26] 20.39 m m [26] 20.39 m m 25 User-Agent [26] 20.41 o o [26] 20.41 o o 25A User-to-User [126] 7 c26 c26 [126] 7 c26 c26 26 Via [26] 20.42 m m [20] 20.42 m m c1: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c2: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c6: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c7: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c9: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c10: IF A.4/34 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG) or AS. c11: IF A.4/34 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the P-Access-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA, AS acting as third-party call controller or EATF. c12: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c13: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c14: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c15: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note). c16: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c17: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c18: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c19: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c20: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c21: IF A.3/2 THEN m ELSE IF A.4/38 THEN o ELSE n/a - - P-CSCF, the Reason header field for the session initiation protocol. c22: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c23: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c24: IF A.4/38 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c25: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c26: IF A.4/76 THEN o ELSE n/a - - transporting user to user information for call centers using SIP. c29: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c30: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c31: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c32: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c33: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c34: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c35: IF A.4/113 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG) or AS. c36: IF A.4/113 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the Cellular-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA, AS acting as third-party call controller or EATF. c37: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c38: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19]. Prerequisite A.5/2 - - BYE request Table A.10: Supported message bodies within the BYE request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 XML Schema for PSTN [11B] n/a c1 [11B] n/a c1 2 VoiceXML expr / namelist data [145] 4.2 m c2 [145] 4.2 m c2 3 application/vnd.3gpp.ussd [8W] n/a c3 [8W] n/a c4 4 application/sdp [30] 8 o c5 [30] 8 m c6 5 application/vnd.etsi.aoc+xml [8N] 4.7.2 n/a c7 [8N] 4.7.2 n/a c8 c1: IF A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/9B OR A.3/13B THEN o ELSE n/a - - MGCF, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, IBCF (IMS-ALG), ISC gateway function (IMS-ALG). c2: IF A.4/84 THEN m ELSE n/a - - SIP Interface to VoiceXML Media Services. c3: IF A.3A/93 OR A.3/9 OR A.3/2 OR A.3A/89 THEN m ELSE n/a - - USSI AS, IBCF, P-CSCF, ATCF (UA). c4: IF A.3A/92 OR A.3/9 OR A.3/2 OR A.3A/89 THEN m ELSE n/a - - USSI UE, IBCF, P-CSCF, ATCF (UA). c5: IF A.4/16 THEN o ELSE n/a - - integration of resource management and SIP. c6: IF A.4/16 THEN m ELSE n/a - - integration of resource management and SIP. c7 IF A.3A/53 THEN m ELSE n/a - - Advice of charge application server. c8 IF A.3A/54 THEN m ELSE n/a - - Advice of charge UA client. TableA.11: Void Prerequisite A.5/3 - - BYE response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.11A: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/3 - - BYE response for all remaining status-codes Table A.12: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c11 c11 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Cellular-Network-Info 7.2.15 n/a c19 7.2.15 n/a c20 2 Content-Disposition [26] 20.11 o o [26] 20.11 m m 3 Content-Encoding [26] 20.12 o o [26] 20.12 m m 3A Content-ID [256] 3.2 o c21 [256] 3.2 m c22 4 Content-Language [26] 20.13 o o [26] 20.13 m m 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 m m 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 c1 c1 [26] 20.17 m m 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c12 c12 [89] 4.3 c12 c12 10 MIME-Version [26] 20.24 o o [26] 20.24 m m 10A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c5 c6 [52] 4.4, [52A] 4, [234] 2 c5 c7 10B P-Asserted-Identity [34] 9.1 n/a n/a [34] 9.1 c3 c3 10C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c9 c10 [52] 4.5, [52A] 4 c9 c10 10D P-Charging-Vector [52] 4.6, [52A] 4 c8 c18 [52] 4.6, [52A] 4 c8 c18 10F P-Preferred-Identity [34] 9.2 c3 x [34] 9.2 n/a n/a 10G Privacy [33] 4.2 c4 n/a [33] 4.2 c4 c4 10H Relayed-Charge 7.2.12 n/a c17 7.2.12 n/a c17 10I Require [26] 20.32 m m [26] 20.32 m m 10J Server [26] 20.35 o o [26] 20.35 o o 10K Session-ID [162] o c16 [162] o c16 11 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 o o [26] 20.41 o o 12B User-to-User [126] 7 c13 c13 [126] 7 c13 c13 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 o (note) o (note) [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c4: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c5: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c6: IF A.4/34 AND (A.3/1 OR A.3/2A ORA.3/7) THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG), or AS. c7: IF A.4/34 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the P-Access-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA, AS acting as third-party call controller or EATF. c8: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c10: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.6/18 THEN m ELSE o - - 405 (Method Not Allowed). c12: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c13: IF A.4/76 THEN o ELSE n/a - - transporting user to user information for call centers using SIP. c16: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c17: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c18: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c19: IF A.4/113 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG), or AS. c20: IF A.4/113 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the Cellular-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA, AS acting as third-party call controller or EATF. c21: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c22: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL. Prerequisite A.5/3 - - BYE response Prerequisite: A.6/102 - - Additional for 2xx response Table A.13: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c5 c5 [116] 3.2 c5 c5 0B Allow-Events [28] 8.2.2 c3 c3 [28] 8.2.2 c4 c4 1 Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 4 Supported [26] 20.37 o m [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c3: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c4: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c5: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.5/3 - - BYE response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.13A: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.5/3 - - BYE response Prerequisite: A.6/103 OR A.6/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.14: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0B Contact [26] 20.10 o (note) o [26] 20.10 m m NOTE: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL. Prerequisite A.5/3 - - BYE response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.15: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/3 - - BYE response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.16: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.17: Void Prerequisite A.5/3 - - BYE response Prerequisite: A.6/19 - - Additional for 407 (Proxy Authentication Required) response Table A.18: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 6 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/3 - - BYE response Prerequisite A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.19: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/3 - - BYE response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.19A: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.5/3 - - BYE response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.20: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/3 - - BYE response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.20A: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.21: Void Prerequisite A.5/3 - - BYE response Prerequisite: A.6/6 - - Additional for 200 (OK) response Table A.22: Supported message bodies within the BYE response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 VoiceXML expr / namelist data [145] 4.2 o c1 [145] 4.2 o c1 2 application/vnd.etsi.aoc+xml [8N] 4.7.2 n/a c2 [8N] 4.7.2 n/a c3 c1: IF A.4/84 THEN o ELSE n/a - - SIP Interface to VoiceXML Media Services. c2 IF A.3A/53 THEN m ELSE n/a - - Advice of charge application server. c3 IF A.3A/54 THEN m ELSE n/a - - Advice of charge UA client. A.2.1.4.4 CANCEL method Prerequisite A.5/4 - - CANCEL request Table A.23: Supported header fields within the CANCEL request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Contact [56B] 9.2 c9 c9 [56B] 9.2 c11 c11 5 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 6 Call-ID [26] 20.8 m m [26] 20.8 m m 8 Content-Length [26] 20.14 m m [26] 20.14 m m 8A Content-Type [26] 20.15 c22 c22 [26] 20.15 o o 9 CSeq [26] 20.16 m m [26] 20.16 m m 10 Date [26] 20.17 c4 c4 [26] 20.17 m m 11 From [26] 20.20 m m [26] 20.20 m m 11A Max-Breadth [117] 5.8 n/a c16 [117] 5.8 c17 c17 12 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c18 14 Privacy [33] 4.2 c6 n/a [33] 4.2 c6 n/a 15 Reason [34A] 2 c7 c10 [34A] 2 c12 c12 16 Record-Route [26] 20.30 n/a c18 [26] 20.30 n/a c18 17 Reject-Contact [56B] 9.2 c9 c9 [56B] 9.2 c11 c11 17A Relayed-Charge 7.2.12 n/a c21 7.2.12 n/a c21 17B Request-Disposition [56B] 9.1 c9 c9 [56B] 9.1 c11 c11 17C Resource-Priority [116] 3.1 c13 c13 [116] 3.1 c13 c13 18 Route [26] 20.34 m m [26] 20.34 n/a c18 18A Session-ID [162] o c19 [162] o c19 19 Supported [26] 20.37 o o [26] 20.37 m m 20 Timestamp [26] 20.38 c8 c8 [26] 20.38 m m 21 To [26] 20.39 m m [26] 20.39 m m 22 User-Agent [26] 20.41 o o [26] 20.41 o o 23 Via [26] 20.42 m m [26] 20.42 m m c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c6: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c8: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c9: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c10: IF A.3/2 THEN m ELSE IF A.4/38 THEN o ELSE n/a - - P-CSCF, the Reason header field for the session initiation protocol. c11: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c12: IF A.4/38 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c13: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c16: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c17: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c18: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c19: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c21: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c22: IF A.4/16 OR A.24/1 THEN m ELSE o - - integration of resource management and SIP or XML Schema for PSTN. Prerequisite A.5/4 - - CANCEL request Table A.24: Supported message bodies within the CANCEL request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 XML Schema for PSTN [11B] c1 [11B] c1 2 application/sdp [30] 8 o c2 [30] 8 m c3 c1: IF A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/9B OR A.3/13B THEN o ELSE n/a - - MGCF, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, IBCF (IMS-ALG), ISC gateway function (IMS-ALG). c2: IF A.4/16 THEN o ELSE n/a - - integration of resource management and SIP. c3: IF A.4/16 THEN m ELSE n/a - - integration of resource management and SIP. Prerequisite A.5/5 - - CANCEL response for all status-codes Table A.25: Supported header fields within the CANCEL response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 5C Privacy [33] 4.2 c3 n/a [33] 4.2 c3 n/a 5D Relayed-Charge 7.2.12 n/a c8 7.2.12 n/a c8 5E Session-ID [162] o c6 [162] o c6 6 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 7 To [26] 20.39 m m [26] 20.39 m m 7A User-Agent [26] 20.41 o o [26] 20.41 o o 8 Via [26] 20.42 m m [26] 20.42 m m 9 Warning [26] 20.43 o (note) o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c6: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c8: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL. Prerequisite A.5/5 - - CANCEL response Prerequisite: A.6/102 - - Additional for 2xx response Table A.26: Supported header fields within the CANCEL response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 4 Supported [26] 20.37 o m [26] 20.37 m m c1: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.5/5 - - CANCEL response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.26A: Supported header fields within the CANCEL response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o O 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Table A.27: Void Prerequisite A.5/5 - - CANCEL response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.28: Supported header fields within the CANCEL response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.29: Void Table A.30: Void Prerequisite A.5/5 - - CANCEL response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.30A: Supported header fields within the CANCEL response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.5/5 - - CANCEL response Table A.31: Supported message bodies within the CANCEL response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.1.4.5 Void A.2.1.4.6 INFO method Prerequisite A.5/6 - - INFO request Table A.32: Supported header fields within the INFO request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o o [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o o [26] 20.2 m m 3 Accept-Language [26] 20.3 o o [26] 20.3 m m 4 Allow [26] 20.5 o o [26] 20.5 m m 5 Allow-Events [28] 8.2.2 c1 c1 [28] 8.2.2 c2 c2 6 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 7 Call-ID [26] 20.8 m m [26] 20.8 m m 7A Call-Info [26] 20.9 o o [26] 20.9 o o 8 Cellular-Network-Info 7.2.15 n/a c45 7.2.15 n/a c46 9 Content-Disposition [26] 20.11 o o [26] 20.11 m m 10 Content-Encoding [26] 20.12 o o [26] 20.12 m m 10A Content-ID [256] 3.2 o c47 [256] 3.2 m c48 11 Content-Language [26] 20.13 o o [26] 20.13 m m 12 Content-Length [26] 20.14 m m [26] 20.14 m m 13 Content-Type [26] 20.15 m m [26] 29.15 m m 14 CSeq [26] 20.16 m m [26] 20.16 m m 15 Date [26] 20.17 c4 c4 [26] 20.17 m m 16 From [26] 20.20 m m [26] 20.20 m m 17 Geolocation [89] 4.1 c29 c29 [89] 4.1 c29 c29 17A Geolocation-Routing [89] 4.2 c29 c29 [89] 4.2 c29 c29 18 Info-Package [25] 7.2 c42 c42 [25] 7.2 c42 c42 19 Max-Breadth [117] 5.8 n/a c39 [117] 5.8 c40 c40 20 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c41 21 MIME-Version [26] 20.24 o o [26] 20.24 m m 22 P-Access-Network-Info [52] 4.4, [234] 2 c15 c16 [52] 4.4, [234] 2 c15 c17 23 P-Charging-Function-Addresses [52] 4.5 c20 c21 [52] 4.5 c20 c21 24 P-Charging-Vector [52] 4.6 c18 c19 [52] 4.6 c18 c19 26 Privacy [33] 4.2 c12 c12 [33] 4.2 c12 c12 27 Proxy-Authorization [26] 20.28 c5 c5 [26] 20.28 n/a n/a 28 Proxy-Require [26] 20.29 o n/a [26] 20.29 n/a n/a 29 Reason [34A] 2 c6 c6 [34A] 2 c6 c6 30 Record-Route [26] 20.30 n/a c41 [26] 20.30 n/a c41 31 Referred-By [59] 3 c25 c25 [59] 3 c26 c26 32 Relayed-Charge 7.2.12 n/a c44 7.2.12 n/a c44 33 Request-Disposition [56B] 9.1 c24 c24 [56B] 9.1 c28 c28 34 Require [26] 20.32 m m [26] 20.32 m m 35 Resource-Priority [116] 3.1 c30 c30 [116] 3.1 c30 c30 36 Route [26] 20.34 m m [26] 20.34 n/a c41 37 Security-Client [48] 2.3.1 c22 c22 [48] 2.3.1 n/a n/a 38 Security-Verify [48] 2.3.1 c23 c23 [48] 2.3.1 n/a n/a 38A Session-ID [162] o c43 [162] o c43 39 Subject [26] 20.35 o o [26] 20.36 o o 40 Supported [26] 20.37 m m [26] 20.37 m m 41 Timestamp [26] 20.38 c10 c10 [26] 20.38 m m 42 To [26] 20.39 m m [26] 20.39 m m 43 User-Agent [26] 20.41 o o [26] 20.41 o o 44 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c2: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c6: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c10: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c12: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c15: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c16: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c17: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c18: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c19: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c20: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c21: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c22: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media? (note 2). c23: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c24 IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c25: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c26: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c28: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c29: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c30: IF A.4/70A THEN m ELSE n/a - - inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c39: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c40: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c41: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c42: IF A.4/13A THEN n/a ELSE m - - legacy INFO usage. c43: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c44: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c45: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c46: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c47: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c48: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE 2: Support of this header field in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header field in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19]. Prerequisite A.5/6 - - INFO request Table A.33: Supported message bodies within the INFO request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Info-Package [25] m m [25] m m 2 application/vnd.etsi.aoc+xml [8N] 4.7.2 n/a c1 [8N] 4.7.2 n/a c2 3 application/EmergencyCallData.eCall.MSD [244] 14.3 m c3 [244] 14.3 m c4 4 application/EmergencyCallData.Control+xml [244] 14.4 m c3 [244] 14.4 m c3 c1: IF A.3A/53 THEN m ELSE n/a - - Advice of charge application server. c2: IF A.3A/54 THEN m ELSE n/a - - Advice of charge UA client. c3: IF (A.3/1 AND A.4/120) THEN m ELSE IF ((A.3/2A OR A.3/11A OR A.3A/84) AND A.4/120) THEN i ELSE n/a - - UE, Next-Generation Pan-European eCall emergency service, P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF. c4: IF ((A.3/2A OR A.3/11A OR A.3A/84) AND A.4/120) THEN i ELSE n/a - - P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF, Next-Generation Pan-European eCall emergency service. Prerequisite A.5/7 - - INFO response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.34: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/7 - - INFO response for all remaining status-codes Table A.35: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c12 c12 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Call-Info [26] 20.9 o o [26] 20.9 o o 2A Cellular-Network-Info 7.2.15 n/a c19 7.2.15 n/a c20 3 Content-Disposition [26] 20.11 o o [26] 20.11 m m 4 Content-Encoding [26] 20.12 o o [26] 20.12 m m 4A Content-ID [256] 3.2 o c21 [256] 3.2 m c22 5 Content-Language [26] 20.13 o o [26] 20.13 m m 6 Content-Length [26] 20.14 m m [26] 20.14 m m 7 Content-Type [26] 20.15 m m [26] 20.15 m m 8 CSeq [26] 20.16 m m [26] 20.16 m m 9 Date [26] 20.17 c1 c1 [26] 20.17 m m 10 From [26] 20.20 m m [26] 20.20 m m 11 Geolocation-Error [89] 4.3 c14 c14 [89] 4.3 c14 c14 12 MIME-Version [26] 20.24 o o [26] 20.24 m m 13 Organization [26] 20.25 o o [26] 20.25 o o 14 P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c5 c6 [52] 4.4, [52A] 4, [234] 2 c5 c7 15 P-Charging-Function-Addresses [52] 4.5, [52A] 4 c10 c11 [52] 4.5, [52A] 4 c10 c11 16 P-Charging-Vector [52] 4.6, [52A] 4 c8 c9 [52] 4.6, [52A] 4 c8 c9 18 Privacy [33] 4.2 c4 c4 [33] 4.2 c4 c4 18A Relayed-Charge 7.2.12 n/a c18 7.2.12 n/a c18 19 Require [26] 20.32 m m [26] 20.32 m m 20 Server [26] 20.35 o o [26] 20.35 o o 20A Session-ID [162] o c17 [162] o c17 21 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 22 To [26] 20.39 m m [26] 20.39 m m 23 User-Agent [26] 20.41 o o [26] 20.41 o o 24 Via [26] 20.42 m m [26] 20.42 m m 25 Warning [26] 20.43 o o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c4: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c5: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c8: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.6/18 THEN m ELSE o - - 405 (Method Not Allowed). c14: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c17: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c18: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c19: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c20: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c21: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c22: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). Prerequisite A.5/7 - - INFO response Prerequisite: A.6/102 - - Additional for 2xx response Table A.36: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o o [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o o [26] 20.2 m m 3 Accept-Language [26] 20.3 o o [26] 20.3 m m 4 Accept-Resource-Priority [116] 3.2 c5 c5 [116] 3.2 c5 c5 5 Allow-Events [28] 8.2.2 c3 c3 [28] 8.2.2 c4 c4 6 Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 9 Supported [26] 20.37 o o [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c3: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c4: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c5: IF A.4/70A THEN m ELSE n/a - - inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. Prerequisite A.5/7 - - INFO response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.37: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.5/7 - - INFO response Prerequisite: A.6/103 - - Additional for 3xx or 485 (Ambiguous) response Table A.37A: Void Prerequisite A.5/7 - - INFO response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.38: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/7 - - INFO response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480 (Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.39: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.40: Void Prerequisite A.5/7 - - INFO response Prerequisite: A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.41: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/7 - - INFO response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.41A: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70A THEN m ELSE n/a - - inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. Prerequisite A.5/7 - - INFO response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.42: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/7 - - INFO response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.42A: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.43: Void Table A.44: Void Prerequisite A.5/7 - - INFO response Table A.45: Supported message bodies within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.1.4.7 INVITE method Prerequisite A.5/8 - - INVITE request Table A.46: Supported header fields within the INVITE request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o c47 [26] 20.1 m m 1A Accept-Contact [56B] 9.2 c24 c24 [56B] 9.2 c32 c32 2 Accept-Encoding [26] 20.2 o o [26] 20.2 m m 3 Accept-Language [26] 20.3 o o [26] 20.3 m m 3A Additional-Identity 7.2.20 n/a c75 7.2.20 n/a c76 4 Alert-Info [26] 20.4 o o [26] 20.4 c1 c1 5 Allow [26] 20.5, [26] 5.1 o (note 1) o [26] 20.5, [26] 5.1 m m 6 Allow-Events [28] 8.2.2 c2 c2 [28] 8.2.2 c53 c53 6A Attestation-Info 7.2.18 n/a c71 7.2.18 n/a c71 7 Answer-Mode [158] c49 c49 [158] c50 c50 8 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 9 Call-ID [26] 20.8 m m [26] 20.8 m m 10 Call-Info [26] 20.9 o o [26] 20.9 o o 10A Cellular-Network-Info 7.2.15 n/a c63 7.2.15 n/a c64 11 Contact [26] 20.10 m m [26] 20.10 m m 12 Content-Disposition [26] 20.11 o o [26] 20.11 m m 13 Content-Encoding [26] 20.12 o o [26] 20.12 m m 13A Content-ID [256] 3.2 o c69 [256] 3.2 m c70 14 Content-Language [26] 20.13 o o [26] 20.13 m m 15 Content-Length [26] 20.14 m m [26] 20.14 m m 16 Content-Type [26] 20.15 m m [26] 20.15 m m 17 CSeq [26] 20.16 m m [26] 20.16 m m 18 Date [26] 20.17 c4 c4 [26] 20.17 m m 19 Expires [26] 20.19 o o [26] 20.19 o o 19A Feature-Caps [190] c59 c59 [190] c58 c58 20 From [26] 20.20 m m [26] 20.20 m m 20A Geolocation [89] 4.1 c33 c33 [89] 4.1 c33 c33 20B Geolocation-Routing [89] 4.2 c33 c33 [89] 4.2 c33 c33 20C History-Info [66] 4.1 c31 c31 [66] 4.1 c31 c31 20D Identity [252] 4 c68 c68 [252] 4 c68 c68 21 In-Reply-To [26] 20.21 o o [26] 20.21 o o 21A Join [61] 7.1 c30 c30 [61] 7.1 c30 c30 21B Max-Breadth [117] 5.8 n/a c45 [117] 5.8 c46 c46 22 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c52 23 MIME-Version [26] 20.24 o o [26] 20.24 m m 23A Min-SE [58] 5 c26 c26 [58] 5 c25 c25 24 Organization [26] 20.25 o o [26] 20.25 o o 24AA Origination-Id 7.2.19 n/a c72 7.2.19 n/a c72 24A P-Access-Network-Info [52] 4.4, [234] 2 c15 c16 [52] 4.4, [234] 2 c15 c17 24B P-Asserted-Identity [34] 9.1 n/a c65 [34] 9.1 c7 c7 24C P-Asserted-Service [121] 4.1 n/a c67 [121] 4.1 c38 c38 24D P-Called-Party-ID [52] 4.2 x x [52] 4.2 c13 c13 24E P-Charging-Function-Addresses [52] 4.5 c20 c21 [52] 4.5 c20 c21 24F P-Charging-Vector [52] 4.6 c18 c19 [52] 4.6 c18 c19 24H P-Early-Media [109] 8 c34 c34 [109] 8 c34 c34 25 P-Media-Authorization [31] 5.1 n/a n/a [31] 5.1 c11 c12 25A P-Preferred-Identity [34] 9.2 c7 c5 [34] 9.2 n/a n/a 25B P-Preferred-Service [121] 4.2 c37 c36 [121] 4.2 n/a n/a 25C P-Private-Network-Indication [134] c42 c42 [134] c42 c42 25D P-Profile-Key [97] 5 n/a n/a [97] 5 n/a n/a 25E P-Served-User [133] 6 c51 c51 [133] 6 c51 c51 25F P-User-Database [82] 4 n/a n/a [82] 4 n/a n/a 25G P-Visited-Network-ID [52] 4.3 x (note 3) x [52] 4.3 c14 n/a 26 Priority [26] 20.26 o o [26] 20.26 o o 26AA Priority-Share Subclause 7.2.16 n/a c66 Subclause 7.2.16 n/a c66 26AB Priority-Verstat Subclause 7.2.21 n/a c77 Subclause 7.2.21 n/a c78 26A Privacy [33] 4.2 c9 c9 [33] 4.2 c9 c9 26B Priv-Answer-Mode [158] c49 c49 [158] c50 c50 27 Proxy-Authorization [26] 20.28 c6 c6 [26] 20.28 n/a n/a 28 Proxy-Require [26] 20.29 o (note 2) o (note 2) [26] 20.29 n/a n/a 28A Reason [34A] 2 c8 c8 [34A] 2 c8 c55 29 Record-Route [26] 20.30 n/a c52 [26] 20.30 m m 29A Recv-Info [25] 5.2.3 c48 c48 [25] 5.2.3 c48 c48 30 Referred-By [59] 3 c27 c27 [59] 3 c28 c28 31 Reject-Contact [56B] 9.2 c24 c24 [56B] 9.2 c32 c32 31A Relayed-Charge 7.2.12 n/a c61 7.2.12 n/a c61 31B Replaces [60] 6.1 c29 c29 [60] 6.1 c29 c29 31C Reply-To [26] 20.31 o o [26] 20.31 o o 31D Request-Disposition [56B] 9.1 c24 c24 [56B] 9.1 c32 c32 32 Require [26] 20.32 m m [26] 20.32 m m 32A Resource-Priority [116] 3.1 c35 c35 [116] 3.1 c35 c35 32B Restoration-Info Subclause 7.2.11 n/a n/a Subclause 7.2.11 n/a c60 32C Resource-Share Subclause 7.2.13 n/a c62 Subclause 7.2.13 n/a c62 33 Route [26] 20.34 m m [26] 20.34 n/a c52 33A Security-Client [48] 2.3.1 c22 c22 [48] 2.3.1 n/a n/a 33B Security-Verify [48] 2.3.1 c23 c23 [48] 2.3.1 n/a n/a 33DA Service-Interact-Info Subclause 7.2.14 n/a c73 Subclause 7.2.14 n/a c74 33D Session-Expires [58] 4 c25 c25 [58] 4 c25 c25 33E Session-ID [162] o c54 [162] o c54 34 Subject [26] 20.36 o o [26] 20.36 o o 35 Supported [26] 20.37 m m [26] 20.37 m m 35A Target-Dialog [184] 7 c56 c56 [184] 7 c57 c57 36 Timestamp [26] 20.38 c10 c10 [26] 20.38 m m 37 To [26] 20.39 m m [26] 20.39 m m 37A Trigger-Consent [125] 5.11.2 c39 c39 [125] 5.11.2 c40 c40 38 User-Agent [26] 20.41 o o [26] 20.41 o o 38A User-to-User [126] 7 c41 c41 [126] 7 c41 c41 39 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/12 THEN m ELSE n/a - - downloading of alerting information. c2: IF A.4/22 THEN m ELSE n/a - - acting as the notifier of event information. c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.3/1 AND A.4/25 THEN o ELSE n/a - - UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c6: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c7: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c8: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c9: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c10: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c11: IF A.4/19 THEN m ELSE n/a - - SIP extensions for media authorization. c12: IF A.3/1 AND A.4/19 THEN m ELSE n/a - - UE, SIP extensions for media authorization. c13: IF A.4/32 THEN o ELSE n/a - - the P-Called-Party-ID extension. c14: IF A.4/33 THEN o ELSE n/a - - the P-Visited-Network-ID extension. c15: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c16: IF A.4/34 AND (A.3/1 OR A.3/2A OR A.3/7 OR A.3A/81 OR A.3A/81A OR A.3A/81B OR A.3/6) THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG), the AS, the MSC server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface or MGCF. c17: IF A.4/34 AND (A.3/2A OR A.3A/81 OR A.3/7A OR A.3/7D OR A3A/84 OR A.3/6) THEN m ELSE n/a - - the P-Access-Network-Info header extension and P-CSCF (IMS-ALG), the MSC server enhanced for ICS, AS acting as terminating UA, AS acting as third-party call controller, EATF or MGCF. c18: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c19: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c20: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c21: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c22: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 4). c23: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c24: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c25: IF A.4/42 THEN m ELSE n/a - - the SIP session timer. c26: IF A.4/42 THEN o ELSE n/a - - the SIP session timer. c27: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c28: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c29: IF A.4/44 THEN m ELSE n/a - - the Session Inititation Protocol (SIP) "Replaces" header. c30: IF A.4/45 THEN m ELSE n/a - - the Session Inititation Protocol (SIP) "Join" header. c31: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c32: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c33: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c34: IF A.4/66 THEN m ELSE n/a - - The SIP P-Early-Media private header extension for authorization of early media. c35: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c36: IF (A.3/1 OR A.3A/81 OR A.3A/81A OR A.3A/81B) AND A.4/74 THEN o ELSE n/a - - UE, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface and SIP extension for the identification of services. c37: IF A.4/74 THEN o ELSE n/a - - SIP extension for the identification of services. c38: IF A.4/74 THEN m ELSE n/a - - SIP extension for the identification of services. c39: IF A.4/75A THEN m ELSE n/a - - a relay within the framework for consent-based communications in SIP. c40: IF A.4/75B THEN m ELSE n/a - - a recipient within the framework for consent-based communications in SIP. c41: IF A.4/76 THEN o ELSE n/a - - transporting user to user information for call centers using SIP. c42: IF A.4/77 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c45: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c46: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c47: IF A.3/1 AND A.4/2B THEN m ELSE o - - UE and initiating a session. c48: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c49: IF A.4/87 THEN o ELSE n/a - - requesting answering modes for SIP. c50: IF A.4/87 THEN m ELSE n/a - - requesting answering modes for SIP. c51: IF A.4/78 THEN m ELSE n/a - - the SIP P-Served-User private header. c52: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c53: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c54: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c55: IF A.4/38 THEN IF A.3A/83 THEN m ELSE o ELSE n/a - - the Reason header field for the session initiation protocol, SCC application server. c56: IF A.4/99 THEN o ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c57: IF A.4/99 THEN m ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c58: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c59: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c60: IF A. 4/109 THEN o ELSE n/a - - PCRF based P-CSCF restoration. c61: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c62: IF A.4/112 THEN o ELSE n/a - - resource sharing. c63: IF A.4/113 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG) or the AS. c64: IF A.4/113 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE IF A.4/113 AND A.3/6 THEN o ELSE n/a - - the Cellular-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA or AS acting as third-party call controller, EATF or MGCF. c65: IF A.4/25 AND (A.3/6 OR A.3/7B OR A.3/8 OR A.3A/81 OR A.3A/81A OR A.3A/81B OR A.3A/83 OR A.3A/89) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and MGCF, AS acting as originating UA, MRFC, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface, SCC application server, ATCF (UA). c66: IF A.4/114 THEN o ELSE n/a - - priority sharing. c67: IF A.4/74 AND A.3/7B THEN o ELSE n/a - - SIP extension for the identification of services and AS acting as originating UA. c68: IF A.4/116 AND (A.3/7 OR A.3/9) THEN m ELSE n/a - - authenticated identity management in the Session Initiation Protocol, AS, IBCF. c69: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c70: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c71: IF A.4/121 AND (A.3/6 OR A.3/7 OR A.3/9) THEN m ELSE n/a - - the Attestation-Info header field extension, MGCF, AS, IBCF. c72: IF A.4/122 AND (A.3/6 OR A.3/7 OR A.3/9) THEN m ELSE n/a - - the Origination-Id header field extension, MGCF, AS, IBCF. c73: IF A.4/123 AND (A.3/7 OR A.3/9) THEN m ELSE n/a - - Dynamic services interactions, AS, IBCF. c74: IF A.4/123 AND (A.3/2 OR A.3/7 OR A.3/9) THEN m ELSE n/a - - Dynamic services interactions, P-CSCF, AS, IBCF. c75: IF A.4/124 THEN o ELSE n/a - - the Additional-Identity header field extension. c76: IF A.4/124 THEN m ELSE n/a - - the Additional-Identity header field extension. c77: IF A.4/70 AND A.4/126 AND A.3/9 THEN m ELSE n/a - - communications resource priority for the session initiation protocol, the Priority-Verstat header field extension, IBCF. c78: IF A.4/70 AND A.4/126 THEN o ELSE n/a - - communications resource priority for the session initiation protocol, the Priority-Verstat header field extension. o.1: At least one of these shall be supported. NOTE 1: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL. NOTE 2: No distinction has been made in these tables between first use of a request on a From/To/Call-ID combination, and the usage in a subsequent one. Therefore the use of "o" etc. above has been included from a viewpoint of first usage. NOTE 3: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT. NOTE 4: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19]. Prerequisite A.5/8 - - INVITE request Table A.47: Supported message bodies within the INVITE request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 XML Schema for PSTN [11B] c1 [11B] c1 2 application/vnd.3gpp.ussd [8W] c2 [8W] c3 3 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c4 [8ZE] n/a c4 4 application/vnd.etsi.aoc+xml [8N] 4.7.2 n/a c5 [8N] 4.7.2 n/a c6 5 application/EmergencyCallData.eCall.MSD [244] 14.3 m c7 [244] 14.3 m c8 c1: IF A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/9B OR A.3/13B THEN o ELSE n/a - - MGCF, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, IBCF (IMS-ALG), ISC gateway function (IMS-ALG). c2: IF A.3A/92A OR A.3A/93B OR A.3/9 OR A.3/2 OR A.3A/89 THEN m ELSE n/a - - USSI UE supporting user-initiated USSD operations, USSI AS supporting network-initiated USSD operations, IBCF, P-CSCF, ATCF (UA). c3: IF A.3A/93A OR A.3A/92B OR A.3/9 OR A.3/2 OR A.3A/89 THEN m ELSE n/a - - USSI AS supporting user-initiated USSD operations, USSI UE supporting network-initiated USSD operations, IBCF, P-CSCF, ATCF (UA). c4: IF A.3A/102 OR A.3A/103 THEN m ELSE n/a - - MCPTT client, MCPTT server. c5 IF A.3A/53 THEN m ELSE n/a - - Advice of charge application server. c6 IF A.3A/54 THEN m ELSE n/a - - Advice of charge UA client. c7: IF (A.3/1 AND A.4/120) THEN m ELSE IF ((A.3/2A OR A.3/11A OR A.3A/84) AND A.4/120) THEN i ELSE n/a - - UE, Next-Generation Pan-European eCall emergency service, P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF. c8: IF ((A.3/2A OR A.3/11A OR A.3A/84 OR A.3/12) AND A.4/120) THEN i ELSE n/a - - P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF, LRF, Next-Generation Pan-European eCall emergency service. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.48: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/9 - - INVITE response for all remaining status-codes Table A.49: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c12 c12 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Call-Info [26] 20.9 o o [26] 20.9 o o 1B Cellular-Network-Info 7.2.15 n/a c20 7.2.15 n/a c21 2 Content-Disposition [26] 20.11 o o [26] 20.11 m m 3 Content-Encoding [26] 20.12 o o [26] 20.12 m m 3A Content-ID [256] 3.2 o c23 [256] 3.2 m c24 4 Content-Language [26] 20.13 o o [26] 20.13 m m 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 m m 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 c1 c1 [26] 20.17 m m 8ª Expires [26] 20.19 o o [26] 20.19 o o 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c14 c14 [89] 4.3 c14 c14 9B History-Info [66] 4.1 c13 c13 [66] 4.1 c13 c13 10 MIME-Version [26] 20.24 o o [26] 20.24 m m 11 Organization [26] 20.25 o o [26] 20.25 o o 11A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c5 c6 [52] 4.4, [52A] 4, [234] 2 c5 c7 11B P-Asserted-Identity [34] 9.1 n/a c22 [34] 9.1 c3 c3 11C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c10 c11 [52] 4.5, [52A] 4 c11 c11 11D P-Charging-Vector [52] 4.6, [52A] 4 c8 c9 [52] 4.6, [52A] 4 c8 c9 11F P-Preferred-Identity [34] 9.2 c3 x [34] 9.2 n/a n/a 11G Privacy [33] 4.2 c4 c4 [33] 4.2 c4 c4 11H Relayed-Charge 7.2.12 n/a c19 7.2.12 n/a c19 11I Reply-To [26] 20.31 o o [26] 20.31 o o 11J Require [26] 20.32 m m [26] 20.32 m m 11K Server [26] 20.35 o o [26] 20.35 o o 11LA Service-Interact-Info Subclause 7.2.14 n/a c25 Subclause 7.2.14 n/a c26 11L Session-ID [162] o c18 [162] o c18 12 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 13 To [26] 20.39 m m [26] 20.39 m m 13A User-Agent [26] 20.41 o o [26] 20.41 o o 13B User-to-User [126] 7 c15 c15 [126] 7 c15 c15 14 Via [26] 20.42 m m [26] 20.42 m m 15 Warning [26] 20.43 o (note) o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c4: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c5: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c6: IF A.4/34 AND (A.3/1 OR A.3/2A OR A.3/7 OR A.3A/81 OR A.3/81A OR A.3A/81B) THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG), AS or MSC server enhanced for ICS or MSC Server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c7: IF A.4/34 AND (A.3/2A OR A.3A/81 OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the P-Access-Network-Info header extension and P-CSCF (IMS-ALG), MSC server enhanced for ICS, AS acting as terminating UA, AS acting as third-party call controller or EATF. c8: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.6/102 OR A.6/18 THEN m ELSE o - - 2xx response, 405 (Method Not Allowed). c13: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c14: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c15: IF A.4/76 THEN o ELSE n/a - - transporting user to user information for call centers using SIP. c18: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c19: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c20: IF A.4/113 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG) or AS. c21: IF A.4/113 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the Cellular-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA, AS acting as third-party call controller or EATF. c22: IF A.4/25 AND (A.3/6 OR A.3/7B OR A.3/8 OR A.3A/81 OR A.3A/81A OR A.3A/81B OR A.3A/83 OR A.3A/89) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and MGCF, AS acting as originating UA, MRFC, MSC Server enhanced for ICS, MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface, SCC application server, ATCF (UA). c23: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c24: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c25: IF A.4/123 AND (A.3/7 OR A.3/9) THEN m ELSE n/a - - Dynamic services interactions, AS, IBCF. c26: IF A.4/123 AND (A.3/2 OR A.3/7 OR A.3/9) THEN m ELSE n/a - - Dynamic services interactions, P-CSCF, AS, IBCF. NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/101A - - Additional for 18x response Table A.50: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Contact [26] 20.10 o m [26] 20.10 m m 4A Feature-Caps [190] c17 c17 [190] c16 c16 5 P-Answer-State [111] c13 c13 [111] c13 c13 5A P-Early-Media [109] 8 c14 c14 [109] 8 c14 c14 6 P-Media-Authorization [31] 5.1 n/a n/a [31] 5.1 c11 c12 6AA Priority-Share Subclause 7.2.16 n/a c19 Subclause 7.2.16 n/a c19 6A Reason [130], [294] o c15 [130], [294] o c15 7 Record-Route [26] 20.30 o m [26] 20.30 m m 8 Recv-Info [25] 5.2.3 c4 c4 [25] 5.2.3 c4 c4 8A Resource-Share Subclause 7.2.13 n/a c18 Subclause 7.2.13 n/a c18 9 RSeq [27] 7.1 c2 m [27] 7.1 c3 m c2: IF A.4/14 THEN o ELSE n/a - - reliability of provisional responses in SIP. c3: IF A.4/14 THEN m ELSE n/a - - reliability of provisional responses in SIP. c4: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c11: IF A.4/19 THEN m ELSE n/a - - SIP extensions for media authorization. c12: IF A.3/1 AND A.4/19 THEN m ELSE n/a - - UE, SIP extensions for media authorization. c13: IF A.4/65 THEN m ELSE n/a - - the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular. c14: IF A.4/66 THEN m ELSE n/a - - the SIP P-Early-Media private header extension for authorization of early media. c15: IF A.4/38A OR A.4/38C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes). c16: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c17: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c18: IF A.4/112 THEN o ELSE n/a - - resource sharing. c19: IF A.4/114THEN o ELSE n/a - - priority sharing. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/2 - - Additional for 180 (Ringing) response Table A.50A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Alert-Info [26] 20.4 o c1 [26] 20.4 o c1 c1: IF A.4/96 THEN m ELSE o - - Alert-Info URNs for the Session Initiation Protocol. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/5A - - Additional for 199 (Early Dialog Terminated) response Table A.50B: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Contact [26] 20.10 o m [26] 20.10 m m 5 Reason [130], [294] o c5 [130], [294] o c5 7 Record-Route [26] 20.30 o m [26] 20.30 m m 8 Recv-Info [25] 5.2.3 c4 c4 [25] 5.2.3 c4 c4 9 RSeq [27] 7.1 c2 m [27] 7.1 c3 m c2: IF A.4/14 THEN o ELSE n/a - - reliability of provisional responses in SIP. c3: IF A.4/14 THEN m ELSE n/a - - reliability of provisional responses in SIP. c4: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c5: IF A.4/38A OR A.4/38C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes). Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/102 - - Additional for 2xx response Table A.51: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o o [26] 20.1 m m 1A Accept-Encoding [26] 20.2 o o [26] 20.2 m m 1B Accept-Language [26] 20.3 o o [26] 20.3 m m 1C Accept-Resource-Priority [116] 3.2 c15 c15 [116] 3.2 c15 c15 2 Allow-Events [28] 8.2.2 c3 c3 [28] 8.2.2 c4 c4 3 Answer-Mode [158] c6 c6 [158] c7 c7 4 Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 6 Contact [26] 20.10 m m [26] 20.10 m m 6A Feature-Caps [190] c18 c18 [190] c17 c17 7 P-Answer-State [111] c14 c14 [111] c14 c14 8 P-Media-Authorization [31] 5.1 n/a n/a [31] 5.1 c11 c12 8AA Priority-Share Subclause 7.2.16 n/a c20 Subclause 7.2.16 n/a c20 8A Priv-Answer-Mode [158] c6 c6 [158] c7 c7 8B Reason [294] o c21 [294] o c21 9 Record-Route [26] 20.30 m m [26] 20.30 m m 9A Recv-Info [25] 5.2.3 c5 c5 [25] 5.2.3 c5 c5 9B Resource-Share Subclause 7.2.13 n/a c19 Subclause 7.2.13 n/a c19 10 Session-Expires [58] 4 c13 c13 [58] 4 c13 c13 13 Supported [26] 20.37 m m [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c3: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c4: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c5: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c6 IF A.4/87 THEN o ELSE n/a - - requesting answering modes for SIP. c7 IF A.4/87 THEN m ELSE n/a - - requesting answering modes for SIP. c11: IF A.4/19 THEN m ELSE n/a - - SIP extensions for media authorization. c12: IF A.3/1 AND A.4/19 THEN m ELSE n/a - - UE, SIP extensions for media authorization. c13: IF A.4/42 THEN m ELSE n/a - - the SIP session timer. c14: IF A.4/65 THEN m ELSE n/a - - the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular. c15: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c17: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c18: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c19: IF A.4/112 THEN m ELSE n/a - - resource sharing. c20: IF A.4/114THEN o ELSE n/a - - priority sharing. c21: IF A.4/38C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes). Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.51A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Reason [130], [294] o c1 [130], [294] o c1 3 Response-Source 7.2.17 n/a c2 7.2.17 n/a c2 c1: IF A.4/38A OR A.4/38C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes). c2: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/103 OR A.6/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.52: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Contact [26] 20.10 o (note 1) o [26] 20.10 m m NOTE: The strength of this requirement is RECOMMENDED rather than OPTIONAL. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.53: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 6 Proxy-Authenticate [26] 20.27 c3 c3 [26] 20.27 c3 c3 13 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/16 - - Additional for 403 (Forbidden) response Table A.53A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 P-Refused-URI-List [183] c1 c1 [183] c1 c1 c1: IF A.4/98 THEN m ELSE n/a -- The SIP P-Refused-URI-List private-header. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 600 (Busy Everywhere), 603 (Decline) response Table A.54: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 8 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.55: Void Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/20 - - Additional for 407 (Proxy Authentication Required) response Table A.56: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 6 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 11 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/21 - - Additional for 408 (Request timeout) response Table A.56A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.57: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.57A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.58: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 10 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.58A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/28A - - Additional for 422 (Session Interval Too Small) response Table A.58B: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Min-SE [58] 5 c1 c1 [58] 5 c1 c1 c1: IF A.4/42 THEN o ELSE n/a - - the SIP session timer. Table A.59: Void Table A.60: Void Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/29H - - Additional for 470 (Consent Needed) response Table A.60A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Permission-Missing [125] 5.9.3 m m [125] 5.9.3 m m Prerequisite A.5/9 - - INVITE response Prerequisite: A.6/45 - - 503 (Service Unavailable) Table A.61: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 8 Retry-After [26] 20.33 o o [26] 20.33 o m Table A.61A: Void Prerequisite A.5/9 - - INVITE response Table A.62: Supported message bodies within the INVITE response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 XML Schema for PSTN [11B] c1 [11B] c1 2 Recipient list [183] c2 c2 [183] c2 c2 3 3GPP IM CN subsystem XML body subclause 7.6 n/a c3 subclause 7.6 n/a c4 (note) 4 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c5 [8ZE] n/a c5 5 application/vnd.etsi.aoc+xml [8N] 4.7.2 n/a c6 [8N] 4.7.2 n/a c7 6 application/EmergencyCallData.Control+xml [244] 14.4 m c8 [244] 14.4 m c9 c1: IF A.3/6 OR A.3/7A OR A.3/7B OR A.3/7D OR A.3/9B OR A.3/13B THEN o ELSE n/a - - MGCF, AS acting as terminating UA, or redirect server, AS acting as originating UA, AS performing 3rd party call control, IBCF (IMS-ALG), ISC gateway function (IMS-ALG). c2: IF A.3/9B OR A.3/13B THEN m ELSE IF A.3/7A OR A.3/7B OR A.3/7D THEN o ELSE n/a - - IBCF (IMS-ALG), ISC gateway function (IMS-ALG), AS acting as terminating UA, AS acting as originating UA, AS performing 3rd party call control. c3: IF A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C OR (A.4/103 AND A.3/2) OR (A.4/103 AND A.3/4) THEN m ELSE n/a - - IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), S-CSCF restoration procedures, P-CSCF, S-CSCF. c4: IF A.3/1 OR A.3/2 OR A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C THEN m ELSE IF A.3/4 THEN o ELSE n/a - - UE, P-CSCF, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), S-CSCF. c5: IF A.3A/102 OR A.3A/103 THEN M ELSE n/a - - MCPTT client, MCPTT server. c6 IF A.3A/53 THEN m ELSE n/a - - Advice of charge application server. c7 IF A.3A/54 THEN m ELSE n/a - - Advice of charge UA client. c8: IF ((A.3/2A OR A.3/11A OR A.3A/84) AND A.4/120) THEN i ELSE n/a - - P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF, Next-Generation Pan-European eCall emergency service. c9: IF (A.3/1 AND A.4/120) THEN m ELSE IF ((A.3/2A OR A.3/11A OR A.3A/84) AND A.4/120) THEN i ELSE n/a - - UE, Next-Generation Pan-European eCall emergency service, P-CSCF (IMS-ALG), E-CSCF acting as UA, EATF. NOTE: If a IBCF (IMS-ALG) or a IBCF (Screening of SIP signalling) is unable to receive a 3GPP IM CN subsystem XML body from a S-CSCF in a serving network then the IBCF (IMS-ALG) or the IBCF (Screening of SIP signalling) support can be "o" instead of "m". Examples include an S-CSCF supporting S-CSCF restoration procedures. A.2.1.4.7A MESSAGE method Prerequisite A.5/9A - - MESSAGE request Table A.62A: Supported header fields within the MESSAGE request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Contact [56B] 9.2 c24 c24 [56B] 9.2 c28 c28 1AA Additional-Identity 7.2.20 n/a c58 7.2.20 n/a c59 1A Allow [26] 20.5 o o [26] 20.5 m m 2 Allow-Events [28] 8.2.2 c1 c1 [28] 8.2.2 c2 c2 2A Attestation-Info 7.2.18 n/a c54 7.2.18 n/a c54 3 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 4 Call-ID [26] 20.8 m m [26] 20.8 m m 5 Call-Info [26] 20.9 o o [26] 20.9 o o 5A Cellular-Network-Info 7.2.15 n/a c47 7.2.15 n/a c48 6 Content-Disposition [26] 20.11 o o [26] 20.11 m m 7 Content-Encoding [26] 20.12 o o [26] 20.12 m m 7A Content-ID [256] 3.2 o c52 [256] 3.2 m c53 8 Content-Language [26] 20.13 o o [26] 20.13 m m 9 Content-Length [26] 20.14 m m [26] 20.14 m m 10 Content-Type [26] 20.15 m m [26] 29.15 m m 11 CSeq [26] 20.16 m m [26] 20.16 m m 12 Date [26] 20.17 c4 c4 [26] 20.17 m m 13 Expires [26] 20.19 o o [26] 20.19 o o 13A Feature-Caps [190] c45 c45 [190] c44 c44 14 From [26] 20.20 m m [26] 20.20 m m 14A Geolocation [89] 4.1 c29 c29 [89] 4.1 c29 c29 14B Geolocation-Routing [89] 4.2 c29 c29 [89] 4.2 c29 c29 14C History-Info [66] 4.1 c27 c27 [66] 4.1 c27 c27 14D Identity [252] 4 c51 c51 [252] 4 c51 c51 15 In-Reply-To [26] 20.21 o o [26] 20.21 o o 15A Max-Breadth [117] 5.8 n/a c39 [117] 5.8 c40 c40 16 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c42 17 MIME-Version [26] 20.24 o o [26] 20.24 m m 18 Organization [26] 20.25 o o [26] 20.25 o o 18AA Origination-Id 7.2.19 n/a c55 7.2.19 n/a c55 18A P-Access-Network-Info [52] 4.4, [234] 2 c15 c16 [52] 4.4, [234] 2 c15 c16 18B P-Asserted-Identity [34] 9.1 n/a c49 [34] 9.1 c11 c11 18C P-Asserted-Service [121] 4.1 n/a c50 [121] 4.1 c33 c33 18D P-Called-Party-ID [52] 4.2 x x [52] 4.2 c13 c13 18E P-Charging-Function-Addresses [52] 4.5 c20 c21 [52] 4.5 c20 c21 18F P-Charging-Vector [52] 4.6 c18 c19 [52] 4.6 c18 c19 18H P-Preferred-Identity [34] 9.2 c11 c7 [34] 9.2 n/a n/a 18I P-Preferred-Service [121] 4.2 c32 c31 [121] 4.2 n/a n/a 18J P-Private-Network-Indication [134] c36 c36 [134] c36 c36 18K P-Profile-Key [97] 5 n/a n/a [97] 5 n/a n/a 18L P-Served-User [133] 6 c41 c41 [133] 6 c41 c41 18M P-User-Database [82] 4 n/a n/a [82] 4 n/a n/a 18N P-Visited-Network-ID [52] 4.3 x (note 1) x [52] 4.3 c14 n/a 19 Priority [26] 20.26 o o [26] 20.26 o o 19A Privacy [33] 4.2 c12 c12 [33] 4.2 c12 c12 20 Proxy-Authorization [26] 20.28 c5 c5 [26] 20.28 n/a n/a 21 Proxy-Require [26] 20.29 o n/a [26] 20.29 n/a n/a 21A Reason [34A] 2 c6 c6 [34A] 2 c6 c6 22A Referred-By [59] 3 c25 c25 [59] 3 c26 c26 23 Reject-Contact [56B] 9.2 c24 c24 [56B] 9.2 c28 c28 23A Relayed-Charge 7.2.12 n/a c46 7.2.12 n/a c46 23B Reply-To [26] 20.31 o o [26] 20.31 o o 23C Request-Disposition [56B] 9.1 c24 c24 [56B] 9.1 c28 c28 24 Require [26] 20.32 m m [26] 20.32 m m 24A Resource-Priority [116] 3.1 c30 c30 [116] 3.1 c30 c30 25 Route [26] 20.34 m m [26] 20.34 n/a n/a 25A Security-Client [48] 2.3.1 c22 c22 [48] 2.3.1 n/a n/a 25B Security-Verify [48] 2.3.1 c23 c23 [48] 2.3.1 n/a n/a 25CA Service-Interact-Info Subclause 7.2.14 n/a c56 Subclause 7.2.14 n/a c57 25C Session-ID [162] o c43 [162] o c43 26 Subject [26] 20.35 o o [26] 20.36 o o 27 Supported [26] 20.37 c9 m [26] 20.37 m m 28 Timestamp [26] 20.38 c10 c10 [26] 20.38 m m 29 To [26] 20.39 m m [26] 20.39 m m 29A Trigger-Consent [125] 5.11.2 c34 c34 [125] 5.11.2 c35 c35 30 User-Agent [26] 20.41 o o [26] 20.41 o o 31 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c2: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c6: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c7: IF A.3/1 AND A.4/25 THEN o ELSE n/a - - UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c9: IF A.4/14 THEN m ELSE o - - support of reliable transport. c10: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c11: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c12: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c13: IF A.4/32 THEN o ELSE n/a - - the P-Called-Party-ID extension. c14: IF A.4/33 THEN o ELSE n/a - - the P-Visited-Network-ID extension. c15: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c16: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c17: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c18: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c19: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c20: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c21: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c22: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 2). c23: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c24: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c25: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c26: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c27: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c28: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c29: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c30: IF A.4/70A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c31: IF A.3/1 AND A.4/74 THEN o ELSE n/a - - UE and SIP extension for the identification of services. c32: IF A.4/74 THEN o ELSE n/a - - SIP extension for the identification of services. c33: IF A.4/74 THEN m ELSE n/a - - SIP extension for the identification of services. c34: IF A.4/75A THEN m ELSE n/a - - a relay within the framework for consent-based communications in SIP. c35: IF A.4/75B THEN m ELSE n/a - - a recipient within the framework for consent-based communications in SIP. c36: IF A.4/77 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c39: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c40: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c41: IF A.4/78 THEN m ELSE n/a - - the SIP P-Served-User private header. c42: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c43: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c44: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c45: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c46: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c47: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c48: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c49: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC. c50: IF A.4/74 AND A.3/7B THEN o ELSE n/a - - SIP extension for the identification of services and AS acting as originating UA. c51: IF A.4/116 AND (A.3/7 OR A.3/9) THEN m ELSE n/a - - authenticated identity management in the Session Initiation Protocol, AS, IBCF. c52: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c53: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c54: IF A.4/121 AND (A.3/6 OR A.3/7 OR A.3/9) THEN m ELSE n/a - - the Attestation-Info header field extension, MGCF, AS, IBCF. c55: IF A.4/122 AND (A.3/6 OR A.3/7 OR A.3/9) THEN m ELSE n/a - - the Origination-Id header field extension, MGCF, AS, IBCF. c56: IF A.4/123 AND (A.3/7 OR A.3/9) THEN m ELSE n/a - - Dynamic services interactions, AS, IBCF. c57: IF A.4/123 AND (A.3/2 OR A.3/7 OR A.3/9) THEN m ELSE n/a - - Dynamic services interactions, P-CSCF, AS, IBCF. c58: IF A.4/124 THEN o ELSE n/a - - the Additional-Identity header field extension. c59: IF A.4/124 THEN m ELSE n/a - - the Additional-Identity header field extension. NOTE 1: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT. NOTE 2: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19]. Prerequisite A.5/9A - - MESSAGE request Table A.62B: Supported message bodies within the MESSAGE request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 permission document [125] 5.4 c1 c1 [125] 5.4 c2 c2 2 application/vnd.3gpp.sms [4D] c3 c3 [4D] c3 c3 3 message/cpim [151] c4 c4 [151] c4 c4 4 message/imdn+xml [157] c5 c5 [157] c5 c5 5 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c6 [8ZE] n/a c6 6 application/vnd.3gpp.mcptt-mbms-usage-info+xml [8ZE] n/a c6 [8ZE] n/a c6 7 application/vnd.3gpp.mcptt-location-info+xml [8ZE] n/a c6 [8ZE] n/a c6 8 application/vnd.3gpp.mcptt-floor-request+xml [8ZE] n/a c7 [8ZE] n/a c7 9 application/vnd.3gpp.mcptt-affiliation-command+xml [8ZE] n/a c6 [8ZE] n/a c6 c1: IF A.4/75A THEN m ELSE n/a - - a relay within the framework for consent-based communications in SIP. c2: IF A.4/75B THEN m ELSE n/a - - a recipient within the framework for consent-based communications in SIP. c3: IF A.3A/61 OR A.3A/62 OR A.3A/63 THEN m ELSE o - - an SM-over-IP sender or an SM-over-IP receiver or an IP-SM-GW for SMS over IP. c4: IF A.3A/71 AND A.4/85 THEN m ELSE n/a - - common presence and instant messaging (CPIM): message format. c5: IF A.3A/71 AND A.4/86 THEN m ELSE n/a - - instant message disposition notification. c6: IF A.3A/102 OR A.3A/103 THEN m ELSE n/a - - MCPTT client, MCPTT server. c7: IF A.3A/103 THEN m ELSE n/a - - MCPTT server. Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.62BA: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/9B - - MESSAGE response for all remaining status-codes Table A.62C: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c12 c12 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Call-Info [26] 20.9 o o [26] 20.9 o o 2A Cellular-Network-Info 7.2.15 n/a c19 7.2.15 n/a c20 3 Content-Disposition [26] 20.11 o (note 1) o (note 1) [26] 20.11 m (note 1) m (note 1) 4 Content-Encoding [26] 20.12 o (note 1) o (note 1) [26] 20.12 m (note 1) m (note 1) 4A Content-ID [256] 3.2 o c22 [256] 3.2 m c23 5 Content-Language [26] 20.13 o (note 1) o (note 1) [26] 20.13 m (note 1) m (note 1) 6 Content-Length [26] 20.14 m (note 1) m (note 1) [26] 20.14 m (note 1) m (note 1) 7 Content-Type [26] 20.15 m (note 1) m (note 1) [26] 20.15 m (note 1) m (note 1) 8 CSeq [26] 20.16 m m [26] 20.16 m m 9 Date [26] 20.17 c1 c1 [26] 20.17 m m 9A Expires [26] 20.19 o o [26] 20.19 o o 10 From [26] 20.20 m m [26] 20.20 m m 10A Geolocation-Error [89] 4.3 c14 c14 [89] 4.3 c14 c14 10B History-Info [66] 4.1 c13 c13 [66] 4.1 c13 c13 11 MIME-Version [26] 20.24 o (note 1) o (note 1) [26] 20.24 m (note 1) m (note 1) 12 Organization [26] 20.25 o o [26] 20.25 o o 12A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c5 c6 [52] 4.4, [52A] 4, [234] 2 c5 c7 12B P-Asserted-Identity [34] 9.1 n/a c21 [34] 9.1 c3 c3 12C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c10 c11 [52] 4.5, [52A] 4 c10 c11 12D P-Charging-Vector [52] 4.6, [52A] 4 c8 c9 [52] 4.6, [52A] 4 c8 c9 12F P-Preferred-Identity [34] 9.2 c3 x [34] 9.2 n/a n/a 12G Privacy [33] 4.2 c4 c4 [33] 4.2 c4 c4 12H Relayed-Charge 7.2.12 n/a c18 7.2.12 n/a c18 12I Reply-To [26] 20.31 o o [26] 20.31 o o 12J Require [26] 20.32 m m [26] 20.32 m m 13 Server [26] 20.35 o o [26] 20.35 o o 13AA Service-Interact-Info Subclause 7.2.14 n/a c24 Subclause 7.2.14 n/a c25 13A Session-ID [162] o c17 [162] o c17 14 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 15 To [26] 20.39 m m [26] 20.39 m m 16 User-Agent [26] 20.41 o o [26] 20.41 o o 17 Via [26] 20.42 m m [26] 20.42 m m 18 Warning [26] 20.43 o o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c4: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c5: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c8: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.6/18 THEN m ELSE o - - 405 (Method Not Allowed). c13: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c14: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c17: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c18: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c19: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c20: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c21: IF A.4/25 AND (A.3/7B OR A.3/8 OR A.3A/83 OR A.3A/89) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC, SCC application server, ATCF (UA). c22: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c23: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c24: IF A.4/123 AND (A.3/7 OR A.3/9) THEN m ELSE n/a - - Dynamic services interactions, AS, IBCF. c25: IF A.4/123 AND (A.3/2 OR A.3/7 OR A.3/9) THEN m ELSE n/a - - Dynamic services interactions, P-CSCF, AS, IBCF. NOTE 1: RFC 3428 [50] clause 7 states that all 2xx class responses to a MESSAGE request must not include any body, therefore for 2xx responses to the MESSAGE request the values on Sending side for "RFC status" and "Profile status" are "x", the values for Receiving side for "RFC status" and "Profile Status" are "n/a". RFC 3261 [26] subclause 7.4 states that all responses may contain bodies, therefore for all responses to the MESSAGE request other than 2xx responses, the values on Sending side for "RFC status" and "Profile status" are "o", the values for Receiving side for "RFC status" and "Profile Status" are "m". Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/102 - - Additional for 2xx response Table A.62D: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c5 c5 [116] 3.2 c5 c5 1 Allow-Events [28] 8.2.2 c3 c3 [28] 8.2.2 c4 c4 2 Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 3 Feature-Caps [190] c8 c8 [190] c7 c7 3A Reason [294] o c9 [294] o c9 6 Supported [26] 20.37 o o [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c3: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c4: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c5: IF A.4/70A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c7: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c8: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c9: IF A.4/38C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes). Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.62DA: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 1A Reason [294] o c2 [294] o c2 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? c2: IF A.4/38C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes). Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/103 - - Additional for 3xx or 485 (Ambiguous) response Table A.62E: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Contact [26] 20.10 o (note) o [26] 20.10 m m NOTE: The strength of this requirement is RECOMMENDED rather than OPTIONAL. Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.62F: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.62G: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.62H: Void Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/20 - - Additional for 407 (Proxy Authentication Required) response Table A.62I: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 6 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Table A.62IA: Void Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.62J: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.62JA: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.62K: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.62L: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.62M: Void Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/29H - - Additional for 470 (Consent Needed) response Table A.62MA: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Permission-Missing [125] 5.9.3 m m [125] 5.9.3 m m Prerequisite A.5/9B - - MESSAGE response Prerequisite: A.6/46 - - Additional for 504 (Server Time-out) response Table A.62MB: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.5/9B - - MESSAGE response Table A.62N: Supported message bodies within the MESSAGE response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.1.4.8 NOTIFY method Prerequisite A.5/10 - - NOTIFY request Table A.63: Supported header fields within the NOTIFY request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o o [26] 20.1 m m 1A Accept-Contact [56B] 9.2 c19 c19 [56B] 9.2 c23 c23 2 Accept-Encoding [26] 20.2 o o [26] 20.2 m m 3 Accept-Language [26] 20.3 o o [26] 20.3 m m 3A Allow [26] 20.5 o o [26] 20.5 m m 4 Allow-Events [28] 8.2.2 c1 c1 [28] 8.2.2 c2 c2 5 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 6 Call-ID [26] 20.8 m m [26] 20.8 m m 6A Call-Info [26] 20.9 o o [26] 20.9 c25 c25 6B Cellular-Network-Info 7.2.15 n/a c38 7.2.15 n/a c39 6C Contact [26] 20.10 m m [26] 20.10 m m 7 Content-Disposition [26] 20.11 o o [26] 20.11 m m 8 Content-Encoding [26] 20.12 o o [26] 20.12 m m 8A Content-ID [256] 3.2 o c41 [256] 3.2 m c42 9 Content-Language [26] 20.13 o o [26] 20.13 m m 10 Content-Length [26] 20.14 m m [26] 20.14 m m 11 Content-Type [26] 20.15 m m [26] 20.15 m m 12 CSeq [26] 20.16 m m [26] 20.16 m m 13 Date [26] 20.17 c4 c4 [26] 20.17 m m 14 Event [28] 8.2.1 m m [28] 8.2.1 m m 14A Feature-Caps [190] c35 c35 [190] c34 c34 15 From [26] 20.20 m m [26] 20.20 m m 15A Geolocation [89] 4.1 c24 c24 [89] 4.1 c24 c24 15B Geolocation-Routing [89] 4.2 c24 c24 [89] 4.2 c24 c24 15C History-Info [66] 4.1 c22 c22 [66] 4.1 c22 c22 15D Max-Breadth [117] 5.8 n/a c26 [117] 5.8 c27 c27 16 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c32 17 MIME-Version [26] 20.24 o o [26] 20.24 m m 17A P-Access-Network-Info [52] 4.4, [234] 2 c10 c11 [52] 4.4, [234] 2 c10 c12 17B P-Asserted-Identity [34] 9.1 n/a c40 [34] 9.1 c6 c6 17C P-Charging-Function-Addresses [52] 4.5 c14 c15 [52] 4.5 c14 c15 17D P-Charging-Vector [52] 4.6 c13 c36 [52] 4.6 c13 c36 17F P-Preferred-Identity [34] 9.2 c6 x [34] 9.2 n/a n/a 17G Privacy [33] 4.2 c7 n/a [33] 4.2 c7 c7 18 Proxy-Authorization [26] 20.28 c5 c5 [26] 20.28 n/a n/a 19 Proxy-Require [26] 20.29 o n/a [26] 20.29 n/a n/a 19A Reason [34A] 2 c18 c18 [34A] 2 c18 c18 20 Record-Route [26] 20.30 n/a c32 [26] 20.30 c9 c9 20A Referred-By [59] 3 c20 c20 [59] 3 c21 c21 20B Reject-Contact [56B] 9.2 c19 c19 [56B] 9.2 c23 c23 20C Relayed-Charge 7.2.12 n/a c37 7.2.12 n/a c37 20D Request-Disposition [56B] 9.1 c19 c19 [56B] 9.1 c23 c23 21 Require [26] 20.32 m m [26] 20.32 m m 22A Resource-Priority [116] 3.1 c29 c29 [116] 3.1 c29 c29 22B Security-Client [48] 2.3.1 c16 c16 [48] 2.3.1 n/a n/a 22C Security-Verify [48] 2.3.1 c17 c17 [48] 2.3.1 n/a n/a 22D Session-ID [162] o c33 [162] o c33 22 Route [26] 20.34 m m [26] 20.34 n/a c32 23 Subscription-State [28] 8.2.3 m m [28] 8.2.3 m m 24 Supported [26] 20.37 o o [26] 20.37 m m 25 Timestamp [26] 20.38 c8 c8 [26] 20.38 m m 26 To [26] 20.39 m m [26] 20.39 m m 27 User-Agent [26] 20.41 o o [26] 20.41 o o 28 Via [26] 20.42 m m [26] 20.42 m m 29 Warning [26] 20.43 o o [26] 20.43 o o c1: IF A.4/20 THEN o ELSE n/a - - SIP specific event notification extension. c2: IF A.4/20 THEN m ELSE n/a - - SIP specific event notification extension. c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c6: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c7: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c9: IF A.4/15 OR A.4/20 THEN m ELSE n/a - - the REFER method extension or SIP specific event notification extension. c10: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c11: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c12: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c13: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c14: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c15: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c16: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note). c17: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c18: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c19: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c20: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c21: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c22: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c23: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c24: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c25: IF A.4/63 THEN m ELSE o - - subscriptions to request-contained resource lists in the session initiation protocol. c26: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c27: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c29: IF A.4/70A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c32:: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c33: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c34: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c35: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c36: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c37: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c38: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c39: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c40: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC. c41: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c42: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19]. Prerequisite A.5/10 - - NOTIFY request Table A.64: Supported message bodies within the NOTIFY request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 sipfrag [37] 2 c1 c1 [37] c1 c1 2 event package (see NOTE) [28] m m [28] m m c1: IF A.4/15 THEN m ELSE o - - the REFER method extension NOTE: The appropriate body specified for the supported event package (see table A.4A) is supported. Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.64A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/11 - - NOTIFY response for all remaining status-codes Table A.65: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c11 c11 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Cellular-Network-Info 7.2.15 n/a c18 7.2.15 n/a c19 2 Content-Disposition [26] 20.11 o o [26] 20.11 m m 3 Content-Encoding [26] 20.12 o o [26] 20.12 m m 3A Content-ID [256] 3.2 o c21 [256] 3.2 m c22 4 Content-Language [26] 20.13 o o [26] 20.13 m m 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 m m 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 c1 c1 [26] 20.17 m m 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c12 c12 [89] 4.3 c12 c12 10 MIME-Version [26] 20.24 o o [26] 20.24 m m 10A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c5 c6 [52] 4.4, [52A] 4, [234] 2 c5 c7 10B P-Asserted-Identity [34] 9.1 n/a c20 [34] 9.1 c3 c3 10C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c9 c10 [52] 4.5, [52A] 4 c9 c10 10D P-Charging-Vector [52] 4.6, [52A] 4 c8 c16 [52] 4.6, [52A] 4 c8 c16 10F P-Preferred-Identity [34] 9.2 c3 x [34] 9.2 n/a n/a 10G Privacy [33] 4.2 c4 n/a [33] 4.2 c4 c4 10H Relayed-Charge 7.2.12 n/a c17 7.2.12 n/a c17 10I Require [26] 20.32 m m [26] 20.32 m m 10J Server [26] 20.35 o o [26] 20.35 o o 10K Session-ID [162] o c15 [162] o c15 11 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 o o [26] 20.41 o o 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 o (note) o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c4: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c5: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c8: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c10: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.6/18 THEN m ELSE o - - 405 (Method Not Allowed). c12: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c15: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c16: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c17: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c18: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c19: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c20: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC. c21: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c22: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL. Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/102 - - Additional for 2xx response Table A.66: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c6 c6 [116] 3.2 c6 c6 0B Allow-Events [28] 8.2.2 c4 c4 [28] 8.2.2 c5 c5 1 Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 1A Contact [26] 20.10 o o [26] 20.10 m m 1B Feature-Caps [190] c8 c8 [190] c8 c8 2 Record-Route [26] 20.30 c3 c3 [26] 20.30 c3 c3 5 Supported [26] 20.37 m m [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c3: IF A.4/15 OR A.4/20 THEN m ELSE n/a - - the REFER method extension or SIP specific event notification extension. c4: IF A.4/20 THEN o ELSE n/a - - SIP specific event notification extension. c5: IF A.4/20 THEN m ELSE n/a - - SIP specific event notification extension. c6: IF A.4/70A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c8: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.66A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/103 - - Additional for 3xx response Table A.67: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Contact [26] 20.10 m m [26] 20.10 m m Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.68: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.69: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.70: Void Table A.71: Void Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/21 - - Additional for 408 (Request timeout) response Table A.71A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.5/11 - - NOTIFY response Prerequisite A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.72: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.72A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/27 - - Addition for 420 (Bad Extension) response Table A.73: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.73A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.74: Void Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/35 - - Additional for 485 (Ambigious) response Table A.74A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Contact [26] 20.10 o o [26] 20.10 m m Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/39 - - Additional for 489 (Bad Event) response Table A.75: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Allow-Events [28] 8.2.2 m m [28] 8.2.2 m m Prerequisite A.5/11 - - NOTIFY response Prerequisite: A.6/46 - - Additional for 504 (Server Time-out) response Table A.75A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.5/11 - - NOTIFY response Table A.76: Supported message bodies within the NOTIFY response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.1.4.9 OPTIONS method Prerequisite A.5/12 - - OPTIONS request Table A.77: Supported header fields within the OPTIONS request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 m m 1A Accept-Contact [56B] 9.2 c21 c21 [56B] 9.2 c26 c26 2 Accept-Encoding [26] 20.2 m m [26] 20.2 m m 3 Accept-Language [26] 20.3 m m [26] 20.3 m m 3A Allow [26] 20.5 o o [26] 20.5 m m 4 Allow-Events [28] 8.2.2 c24 c24 [28] 8.2.2 c1 c1 5 Authorization [26] 20.7 c2 c2 [26] 20.7 c2 c2 6 Call-ID [26] 20.8 m m [26] 20.8 m m 7 Call-Info [26] 20.9 o o [26] 20.9 o o 7A Cellular-Network-Info 7.2.15 n/a c44 7.2.15 n/a c45 8 Contact [26] 20.10 o o [26] 20.10 o o 9 Content-Disposition [26] 20.11 o o [26] 20.11 m m 10 Content-Encoding [26] 20.12 o o [26] 20.12 m m 10A Content-ID [256] 3.2 o c48 [256] 3.2 m c49 11 Content-Language [26] 20.13 o o [26] 20.13 m m 12 Content-Length [26] 20.14 m m [26] 20.14 m m 13 Content-Type [26] 20.15 m m [26] 20.15 m m 14 CSeq [26] 20.16 m m [26] 20.16 m m 15 Date [26] 20.17 c3 c3 [26] 20.17 m m 15A Feature-Caps [190] c42 c42 [190] c41 c41 16 From [26] 20.20 m m [26] 20.20 m m 16A Geolocation [89] 4.1 c27 c27 [89] 4.1 c27 c27 16B Geolocation-Routing [89] 4.2 c27 c27 [89] 4.2 c27 c27 16C History-Info [66] 4.1 c25 c25 [66] 4.1 c25 c25 16D Max-Breadth [117] 5.8 n/a c31 [117] 5.8 c32 c32 17 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c39 18 MIME-Version [26] 20.24 o o [26] 20.24 m m 19 Organization [26] 20.25 o o [26] 20.25 o o 19A P-Access-Network-Info [52] 4.4, [234] 2 c11 c12 [52] 4.4, [234] 2 c11 c13 19B P-Asserted-Identity [34] 9.1 n/a c46 [34] 9.1 c6 c6 19C P-Asserted-Service [121] 4.1 n/a c47 [121] 4.1 c30 c30 19D P-Called-Party-ID [52] 4.2 x x [52] 4.2 c9 c9 19E P-Charging-Function-Addresses [52] 4.5 c16 c17 [52] 4.5 c16 c17 19F P-Charging-Vector [52] 4.6 c14 c15 [52] 4.6 c14 c15 19H P-Preferred-Identity [34] 9.2 c6 c4 [34] 9.2 n/a n/a 19I P-Preferred-Service [121] 4.2 c29 c28 [121] 4.2 n/a n/a 19J P-Private-Network-Indication [134] c34 c34 [134] c34 c34 19K P-Profile-Key [97] 5 n/a n/a [97] 5 n/a n/a 19L P-Served-User [133] 6 c38 c38 [133] 6 c38 c38 19M P-User-Database [82] 4 n/a n/a [82] 4 n/a n/a 19N P-Visited-Network-ID [52] 4.3 x (note 2) x [52] 4.3 c10 n/a 19O Privacy [33] 4.2 c8 c8 [33] 4.2 c8 c8 20 Proxy-Authorization [26] 20.28 c5 c5 [26] 20.28 n/a n/a 21 Proxy-Require [26] 20.29 o o (note 1) [26] 20.29 n/a n/a 21A Reason [34A] 2 c20 c20 [34A] 2 c20 c20 22 Record-Route [26] 20.30 n/a c39 [26] 20.30 n/a c39 22A Recv-Info [25] 5.2.3 c37 c37 [25] 5.2.3 c37 c37 22B Referred-By [59] 3 c22 c22 [59] 3 c23 c23 22C Reject-Contact [56B] 9.2 c21 c21 [56B] 9.2 c26 c26 22D Relayed-Charge 7.2.12 n/a c43 7.2.12 n/a c43 22E Request-Disposition [56B] 9.1 c21 c21 [56B] 9.1 c26 c26 23 Require [26] 20.32 m m [26] 20.32 m m 23A Resource-Priority [116] 3.1 c33 c33 [116] 3.1 c33 c33 24 Route [26] 20.34 m m [26] 20.34 n/a n/a 24A Security-Client [48] 2.3.1 c18 c18 [48] 2.3.1 n/a n/a 24B Security-Verify [48] 2.3.1 c19 c19 [48] 2.3.1 n/a n/a 24C Session-ID [162] o c40 [162] o c40 25 Supported [26] 20.37 c6 c6 [26] 20.37 m m 26 Timestamp [26] 20.38 c7 c7 [26] 20.38 m m 27 To [26] 20.39 m m [26] 20.39 m m 28 User-Agent [26] 20.41 o o [26] 20.41 o o 29 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c3: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c4: IF A.3/1 AND A.4/25 THEN o ELSE n/a - - UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c5: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c6: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c7: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c8: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c9: IF A.4/32 THEN o ELSE n/a - - the P-Called-Party-ID extension. c10: IF A.4/33 THEN o ELSE n/a - - the P-Visited-Network-ID extension. c11: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c12: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c13: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller or EATF. c14: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c15: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c16: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c17: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c18: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 3). c19: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c20: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c21: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c22: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c23: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c24: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c25: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c26: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c27: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c28: IF (A.3/1 OR A.3A/81) AND A.4/74 THEN o ELSE n/a - - UE, MSC Server enhanced for ICS and SIP extension for the identification of services. c29: IF A.4/74 THEN o ELSE n/a - - SIP extension for the identification of services. c30: IF A.4/74 THEN m ELSE n/a - - SIP extension for the identification of services. c31: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13) THEN m ELSE IF A.3/1 AND NOT A.3C/1 - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c32: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c33: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c34: IF A.4/77 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c37: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c38: IF A.4/78 THEN m ELSE n/a - - the SIP P-Served-User private header. c39: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c40: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c41: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c42: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c43: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c44: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c45: IF A.4/113 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller or EATF. c46: IF A.4/25 AND (A.3/7B OR A.3/8 OR A.3A/81A) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC, MSC server enhanced for SRVCC using SIP interface. c47: IF A.4/74 AND A.3/7B THEN o ELSE n/a - - SIP extension for the identification of services and AS acting as originating UA. c48: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c49: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE 1: No distinction has been made in these tables between first use of a request on a From/To/Call-ID combination, and the usage in a subsequent one. Therefore the use of "o" etc. above has been included from a viewpoint of first usage. NOTE 2: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT. NOTE 3: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19]. Prerequisite A.5/12 - - OPTIONS request Table A.78: Supported message bodies within the OPTIONS request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Table A.79: Void Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.79A: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/13 - - OPTIONS response for all remaining status-codes Table A.80: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c12 c12 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Call-Info [26] 20.9 o o [26] 20.9 o o 1B Cellular-Network-Info 7.2.15 n/a c20 7.2.15 n/a c21 2 Content-Disposition [26] 20.11 o o [26] 20.11 m m 3 Content-Encoding [26] 20.12 o o [26] 20.12 m m 3A Content-ID [256] 3.2 o c23 [256] 3.2 m c24 4 Content-Language [26] 20.13 o o [26] 20.13 m m 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 m m 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 c1 c1 [26] 20.17 m m 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c14 c14 [89] 4.3 c14 c14 9B History-Info [66] 4.1 c13 c13 [66] 4.1 c13 c13 10 MIME-Version [26] 20.24 o o [26] 20.24 m m 11 Organization [26] 20.25 o o [26] 20.25 o o 11A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c5 c6 [52] 4.4, [52A] 4, [234] 2 c5 c7 11B P-Asserted-Identity [34] 9.1 n/a c22 [34] 9.1 c3 c3 11C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c10 c11 [52] 4.5, [52A] 4 c10 c11 11D P-Charging-Vector [52] 4.6, [52A] 4 c8 c9 [52] 4.6, [52A] 4 c8 c9 11F P-Preferred-Identity [34] 9.2 c3 x [34] 9.2 n/a n/a 11G Privacy [33] 4.2 c4 c4 [33] 4.2 c4 c4 11H Recv-Info [25] 5.2.3 c17 c17 [25] 5.2.3 c17 c17 11I Relayed-Charge 7.2.12 n/a c19 7.2.12 n/a c19 11J Require [26] 20.32 m m [26] 20.32 m m 11K Server [26] 20.35 o o [26] 20.35 o o 11L Session-ID [162] o c18 [162] o c18 12 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 13 To [26] 20.39 m m [26] 20.39 m m 13A User-Agent [26] 20.41 o o [26] 20.41 o o 14 Via [26] 20.42 m m [26] 20.42 m m 15 Warning [26] 20.43 o (note) o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c4: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c5: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c7: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller, or EATF. c8: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.6/102 OR A.6/18 THEN m ELSE o - - 2xx response, 405 (Method Not Allowed). c13: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c14: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c17: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c18: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c19: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c20: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c21: IF A.4/113 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller, or EATF. c22: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC. c23: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c24: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL. Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/102 - - Additional for 2xx response Table A.81: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 m m 1A Accept-Encoding [26] 20.2 m m [26] 20.2 m m 1B Accept-Language [26] 20.3 m m [26] 20.3 m m 1C Accept-Resource-Priority [116] 3.2 c14 c14 [116] 3.2 c14 c14 2 Allow-Events [28] 8.2.2 c3 c3 [28] 8.2.2 c4 c4 3 Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 5 Contact [26] 20.10 o o [26] 20.10 o o 6 Feature-Caps [190] c16 c16 [190] c15 c15 7 Recv-Info [25] 5.2.3 c6 c6 [25] 5.2.3 c6 c6 12 Supported [26] 20.37 m m [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c3: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c4: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c6: IF A.4/13 THEN m ELSE n/a - - SIP INFO method and package framework. c14: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c15: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c16: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.81A: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/103 OR A.6/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.82: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Contact [26] 20.10 o (note) o [26] 20.10 m m NOTE: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL. Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.83: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 10 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response. Table A.84: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.85: Void Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/20 - - Additional for 407 (Proxy Authentication Required) response Table A.86: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 8 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Table A.86A: Void Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.87: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.87A: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.88: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 7 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/28 OR A.6/41A - - Additional 421 (Extension Required), 494 (Security Agreement Required) response Table A.88A: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.89: Void Prerequisite A.5/13 - - OPTIONS response Prerequisite: A.6/46 - - Additional for 504 (Server Time-out) response Table A.89A: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.5/13 - - OPTIONS response Table A.90: Supported message bodies within the OPTIONS response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 application/cccex [9B] n/a c1 [9B] n/a c2 c1: IF A.3A/12 THEN o ELSE n/a - - conference participant. c2: IF A.3A/11 THEN o ELSE n/a - - conference focus. A.2.1.4.10 PRACK method Prerequisite A.5/14 - - PRACK request Table A.91: Supported header fields within the PRACK request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o o [26] 20.1 m m 1A Accept-Contact [56B] 9.2 c15 c15 [56B] 9.2 c18 c18 2 Accept-Encoding [26] 20.2 o o [26] 20.2 m m 3 Accept-Language [26] 20.3 o o [26] 20.3 m m 3A Allow [26] 20.5 o o [26] 20.5 m m 4 Allow-Events [28] 8.2.2 c1 c1 [28] 8.2.2 c2 c2 5 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 6 Call-ID [26] 20.8 m m [26] 20.8 m m 6A Cellular-Network-Info 7.2.15 n/a c41 7.2.15 n/a c42 7 Content-Disposition [26] 20.11 o o [26] 20.11 m m 8 Content-Encoding [26] 20.12 o o [26] 20.12 m m 8A Content-ID [256] 3.2 o c44 [256] 3.2 m c45 9 Content-Language [26] 20.13 o o [26] 20.13 m m 10 Content-Length [26] 20.14 m m [26] 20.14 m m 11 Content-Type [26] 20.15 m m [26] 20.15 m m 12 CSeq [26] 20.16 m m [26] 20.16 m m 13 Date [26] 20.17 c4 c4 [26] 20.17 m m 14 From [26] 20.20 m m [26] 20.20 m m 14A Max-Breadth [117] 5.8 n/a c21 [117] 5.8 c22 c22 15 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c34 16 MIME-Version [26] 20.24 o o [26] 20.24 m m 16A P-Access-Network-Info [52] 4.4, [234] 2 c9 c10 [52] 4.4, [234] 2 c9 c11 16B P-Charging-Function-Addresses [52] 4.5 c13 c14 [52] 4.5 c13 c14 16C P-Charging-Vector [52] 4.6 c12 c40 [52] 4.6 c12 c40 16E P-Early-Media [109] 8 c39 c39 [109] 8 c39 c39 16EA Priority-Share Subclause 7.2.16 n/a c43 Subclause 7.2.16 n/a c43 16F Privacy [33] 4.2 c6 n/a [33] 4.2 c6 n/a 17 Proxy-Authorization [26] 20.28 c5 c5 [26] 20.28 n/a n/a 18 Proxy-Require [26] 20.29 o n/a [26] 20.29 n/a n/a 19 RAck [27] 7.2 m m [27] 7.2 m m 19A Reason [34A] 2 c7 c7 [34A] 2 c7 c7 20 Record-Route [26] 20.30 n/a c34 [26] 20.30 n/a c34 20A Recv-Info [25] 5.2.3 c35 c35 [25] 5.2.3 c35 c35 20B Referred-By [59] 3 c16 c16 [59] 3 c17 c17 20C Reject-Contact [56B] 9.2 c15 c15 [56B] 9.2 c18 c18 20D Relayed-Charge 7.2.12 n/a c37 7.2.12 n/a c37 20E Request-Disposition [56B] 9.1 c15 c15 [56B] 9.1 c18 c18 21 Require [26] 20.32 m m [26] 20.32 m m 21A Resource-Priority [116] 3.1 c33 c33 [116] 3.1 c33 c33 21B Resource-Share Subclause 7.2.13 n/a c38 Subclause 7.2.13 n/a c38 22 Route [26] 20.34 m m [26] 20.34 n/a c34 22A Session-ID [162] o c36 [162] o c36 23 Supported [26] 20.37 o o [26] 20.37 m m 24 Timestamp [26] 20.38 c8 c8 [26] 20.38 m m 25 To [26] 20.39 m m [26] 20.39 m m 26 User-Agent [26] 20.41 o o [26] 20.41 o o 27 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c2: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c6: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c8: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c9: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c10: IF A.4/34 AND (A.3/1 OR A.3/2A OR A.3/7 OR A.3A/81) THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE, P-CSCF (IMS-ALG), AS or MSC server enhanced for ICS. c11: IF A.4/34 AND (A.3/2A OR A.3A/81 OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the P-Access-Network-Info header extension and P-CSCF (IMS-ALG), MSC server enhanced for ICS, AS acting as terminating UA, AS acting as third-party call controller or EATF. c12: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c13: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c14: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c15: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c16: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c17: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c18: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c21: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c22: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c33: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c34: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c35: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c36: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c37: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c38 IF A.4/112 THEN o ELSE n/a - - resource sharing. c39: IF A.4/66 THEN m ELSE n/a - - The SIP P-Early-Media private header extension for authorization of early media. c40: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c41: IF A.4/113 AND (A.3/1 OR A.3/2A OR A.3/7) THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE, P-CSCF (IMS-ALG) or AS. c42: IF A.4/113 AND (A.3/2A OR A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the Cellular-Network-Info header extension and P-CSCF (IMS-ALG), AS acting as terminating UA or AS acting as third-party call controller or EATF. c43: IF A.4/114 THEN o ELSE n/a - - priority sharing. c44: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c45: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). Prerequisite A.5/14 - - PRACK request Table A.92: Supported message bodies within the PRACK request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Table A.93: Void Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.93A: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/15 - - PRACK response for all remaining status-codes Table A.94: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c9 c9 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Cellular-Network-Info 7.2.15 n/a c17 7.2.15 n/a c18 2 Content-Disposition [26] 20.11 o o [26] 20.11 m m 3 Content-Encoding [26] 20.12 o o [26] 20.12 m m 3A Content-ID [256] 3.2 o c19 [256] 3.2 m c20 4 Content-Language [26] 20.13 o o [26] 20.13 m m 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 m m 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 c1 c1 [26] 20.17 m m 9 From [26] 20.20 m m [26] 20.20 m m 10 MIME-Version [26] 20.24 o o [26] 20.24 m m 10A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c3 c4 [52] 4.4, [52A] 4, [234] 2 c3 c5 10B P-Charging-Function-Addresses [52] 4.5, [52A] 4 c7 c8 [52] 4.5, [52A] 4 c7 c8 10C P-Charging-Vector [52] 4.6, [52A] 4 c6 c16 [52] 4.6, [52A] 4 c6 c16 10F Privacy [33] 4.2 c2 n/a [33] 4.2 c2 n/a 10G Recv-Info [25] 5.2.3 c13 c13 [25] 5.2.3 c13 c13 10H Relayed-Charge 7.2.12 n/a c15 7.2.12 n/a c15 10I Require [26] 20.32 m m [26] 20.32 m m 10J Server [26] 20.35 o o [26] 20.35 o o 10K Session-ID [162] o c14 [162] o c14 11 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 o o [26] 20.41 o o 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 o (note) o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c3: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c4: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c5: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller or EATF. c6: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c7: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c8: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c9: IF A.6/18 THEN m ELSE o - - 405 (Method Not Allowed) c13: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c14: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c15: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c16: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c17: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c18: IF A.4/113 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller or EATF. c19: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c20: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: RFC 3261 [26] gives the status of this header as SHOULD rather than OPTIONAL. Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/102 - - Additional for 2xx response Table A.95: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c14 c14 [116] 3.2 c14 c14 0B Allow-Events [28] 8.2.2 c3 c3 [28] 8.2.2 c4 c4 0C Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 0D P-Early-Media [109] 8 c5 c5 [109] 8 c5 c5 1 Priority-Share Subclause 7.2.16 n/a c16 Subclause 7.2.16 n/a c16 2A Resource-Share Subclause 7.2.13 n/a c15 Subclause 7.2.13 n/a c15 3 Supported [26] 20.37 m m [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c3: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c4: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c5: IF A.4/66 THEN m ELSE n/a - - the SIP P-Early-Media private header extension for authorization of early media. c14: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c15: IF A.4/112 THEN o ELSE n/a - - resource sharing. c16: IF A.4/114 THEN o ELSE n/a - - priority sharing. Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.95A: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/103 OR A.6/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.96: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Contact [26] 20.10 o (note) o [26] 20.10 m m NOTE: RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL. Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.97: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response. Table A.98: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.99: Void Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/20 - - Additional for 407 (Proxy Authentication Required) response Table A.100: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 6 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.101: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.101A: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.102: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/15 - - PRACK response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.102A: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.103: Void Prerequisite A.5/15 - - PRACK response Table A.104: Supported message bodies within the PRACK response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.1.4.10A PUBLISH method Prerequisite A.5/15A – PUBLISH request Table A.104A: Supported header fields within the PUBLISH request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Contact [56B] 9.2 c22 c22 [56B] 9.2 c28 c28 2 Allow [26] 20.5 o o [26] 20.5 m m 3 Allow-Events [28] 8.2.2 c1 c1 [28] 8.2.2 c2 c2 4 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 5 Call-ID [26] 20.8 m m [26] 20.8 m m 6 Call-Info [26] 20.9 o o [26] 20.9 o o 6A Cellular-Network-Info 7.2.15 n/a c43 7.2.15 n/a c44 6B Contact [70] 4 o o [70] 6 n/a n/a 7 Content-Disposition [26] 20.11 o o [26] 20.11 m m 8 Content-Encoding [26] 20.12 o o [26] 20.12 m m 8A Content-ID [256] 3.2 o c47 [256] 3.2 m c48 9 Content-Language [26] 20.13 o o [26] 20.13 m m 10 Content-Length [26] 20.14 m m [26] 20.14 m m 11 Content-Type [26] 20.15 m m [26] 20.15 m m 12 CSeq [26] 20.16 m m [26] 20.16 m m 13 Date [26] 20.17 c4 c4 [26] 20.17 m m 14 Event [70] 4, 6 m m [70] 4, 6 m m 15 Expires [26] 20.19, [70] 4, 5, 6 o o [26] 20.19, [70] 4, 5, 6 m m 15A Feature-Caps [190] c41 c41 [190] c40 c40 16 From [26] 20.20 m m [26] 20.20 m m 16A Geolocation [89] 4.1 c38 c38 [89] 4.1 c38 c38 16B Geolocation-Routing [89] 4.2 c38 c38 [89] 4.2 c38 c38 16C History-Info [66] 4.1 c27 c27 [66] 4.1 c27 c27 17 In-Reply-To [26] 20.21 o o [26] 20.21 o o 17A Max-Breadth [117] 5.8 n/a c23 [117] 5.8 c24 c24 18 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c37 19 MIME-Version [26] 20.24 o o [26] 20.24 m m 20 Organization [26] 20.25 o o [26] 20.25 o o 21 P-Access-Network-Info [52] 4.4, [234] 2 c15 c16 [52] 4.4, [234] 2 c15 c17 22 P-Asserted-Identity [34] 9.1 n/a c45 [34] 9.1 c11 c11 22A P-Asserted-Service [121] 4.1 n/a c46 [121] 4.1 c31 c31 23 P-Called-Party-ID [52] 4.2 x x [52] 4.2 c13 c13 24 P-Charging-Function-Addresses [52] 4.5 c20 c21 [52] 4.5 c20 c21 25 P-Charging-Vector [52] 4.6 c18 c19 [52] 4.6 c18 c19 26 P-Preferred-Identity [34] 9.2 c11 c7 [34] 9.2 n/a n/a 26A P-Preferred-Service [121] 4.2 c31 c30 [121] 4.2 n/a n/a 26B P-Private-Network-Indication [134] c33 c33 [134] c33 c33 26C P-Profile-Key [97] 5 n/a n/a [97] 5 n/a n/a 26D P-Served-User [133] 6 c36 c36 [133] 6 c36 c36 26E P-User-Database [82] 4 n/a n/a [82] 4 n/a n/a 27 P-Visited-Network-ID [52] 4.3 x (note 3) x [52] 4.3 c14 n/a 28 Priority [26] 20.26 o o [26] 20.26 o o 29 Privacy [33] 4.2 c12 c12 [33] 4.2 c12 c12 30 Proxy-Authorization [26] 20.28 c5 c5 [26] 20.28 n/a n/a 31 Proxy-Require [26] 20.29 o n/a [26] 20.29 n/a n/a 32 Reason [34A] 2 c8 c8 [34A] 2 c8 c8 33A Referred-By [59] 3 c25 c25 [59] 3 c26 c26 34 Reject-Contact [56B] 9.2 c22 c22 [56B] 9.2 c28 c28 34A Relayed-Charge 7.2.12 n/a c42 7.2.12 n/a c42 34B Reply-To [26] 20.31 o o [26] 20.31 o o 35 Request-Disposition [56B] 9.1 c22 c22 [56B] 9.1 c28 c28 36 Require [26] 20.32 m m [26] 20.32 m m 36A Resource-Priority [116] 3.1 c29 c29 [116] 3.1 c29 c29 37 Route [26] 20.34 m m [26] 20.34 n/a c37 38 Security-Client [48] 2.3.1 c9 c9 [48] 2.3.1 n/a n/a 39 Security-Verify [48] 2.3.1 c10 c10 [48] 2.3.1 n/a n/a 39A Session-ID [162] o c39 [162] o c39 40 SIP-If-Match [70] 11.3.2 o o [70] 11.3.2 m m 41 Subject [26] 20.36 o o [26] 20.36 o o 42 Supported [26] 20.37, [26] 7.1 o o [26] 20.37, [26] 7.1 m m 43 Timestamp [26] 20.38 c6 c6 [26] 20.38 m m 44 To [26] 20.39 m m [26] 20.39 m m 45 User-Agent [26] 20.41 o o [26] 20.41 o o 46 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c2: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c6: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c7: IF A.3/1 AND A.4/25 THEN o ELSE n/a - - UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c8: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c9: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 1). c10: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c11: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c12: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c13: IF A.4/32 THEN o ELSE n/a - - the P-Called-Party-ID extension. c14: IF A.4/33 THEN o ELSE n/a - - the P-Visited-Network-ID extension. c15: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c16: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c17: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c18: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c19: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c20: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c21: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c22: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c23: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c24: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c25: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c26: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c27: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c28: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c29: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c30: IF (A.3/1 OR A.3A/81) AND A.4/74 THEN o ELSE n/a - - UE, MSC Server enhanced for ICS and SIP extension for the identification of services. c31: IF A.4/74 THEN o ELSE n/a - - SIP extension for the identification of services. c32: IF A.4/74 THEN m ELSE n/a - - SIP extension for the identification of services. c33: IF A.4/77 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c36: IF A.4/78 THEN m ELSE n/a - - the SIP P-Served-User private header. c37: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c38: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c39: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c40: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c41: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c42: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c43: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c44: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c45: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC. c46: IF A.4/74 AND A.3/7B THEN o ELSE n/a - - SIP extension for the identification of services and AS acting as originating UA. c47: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c48: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE 1: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. NOTE 2: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT. Prerequisite A.5/15A - - PUBLISH request Table A.104B: Supported message bodies within the PUBLISH request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c1 [8ZE] n/a c1 2 application/poc-settings+xml [110] o c2 [110] o c3 3 application/pidf+xml (NOTE) [242] o c1 [242] o c3 c1: IF A.3A/102 OR A.3A/103 THEN m ELSE n/a - - MCPTT client, MCPTT server. c2: IF A.3A/102 THEN m ELSE n/a - - MCPTT client. c3: IF A.3A/103 THEN m ELSE n/a - - MCPTT server. NOTE: The application/pidf+xml is extended by 3GPP TS 24.379 [8ZE]. Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.104BA: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/15B - - PUBLISH response for all remaining status-codes Table A.104C: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c12 c12 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Call-Info [26] 24.9 o o [26] 24.9 m m 2A Cellular-Network-Info 7.2.15 n/a c19 7.2.15 n/a c20 3 Content-Disposition [26] 20.11 o o [26] 20.11 m m 4 Content-Encoding [26] 20.12 o o [26] 20.12 m m 4A Content-ID [256] 3.2 o c22 [256] 3.2 m c23 5 Content-Language [26] 20.13 o o [26] 20.13 m m 6 Content-Length [26] 20.14 m m [26] 20.14 m m 7 Content-Type [26] 20.15 m m [26] 20.15 m m 8 CSeq [26] 20.16 m m [26] 20.16 m m 9 Date [26] 20.17 c1 c1 [26] 20.17 m m 9A Expires [26] 20.19 [70] 4, 5, 6 o o [26] 20.19 [70] 4, 5, 6 o o 10 From [26] 20.20 m m [26] 20.20 m m 10A Geolocation-Error [89] 4.3 c16 c16 [89] 4.3 c16 c16 10B History-Info [66] 4.1 c13 c13 [66] 4.1 c13 c13 11 MIME-Version [26] 20.24 o o [26] 20.24 m m 12 Organization [26] 20.25 o o [26] 20.25 o o 13 P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c5 c6 [52] 4.4, [52A] 4, [234] 2 c5 c7 14 P-Asserted-Identity [34] 9.1 n/a c21 [34] 9.1 c3 c3 15 P-Charging-Function-Addresses [52] 4.5, [52A] 4 c10 c11 [52] 4.5, [52A] 4 c10 c11 16 P-Charging-Vector [52] 4.6, [52A] 4 c8 c9 [52] 4.6, [52A] 4 c8 c9 17 P-Preferred-Identity [34] 9.2 c3 x [34] 9.2 n/a n/a 18 Privacy [33] 4.2 c4 c4 [33] 4.2 c4 c4 18A Relayed-Charge 7.2.12 n/a c18 7.2.12 n/a c18 19 Require [26] 20.32 m m [26] 20.32 m m 20 Server [26] 20.35 o o [26] 20.35 o o 20A Session-ID [162] o c17 [162] o c17 21 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 22 To [26] 20.39 m m [26] 20.39 m m 23 User-Agent [26] 20.41 o o [26] 20.41 o o 24 Via [26] 20.42 m m [26] 20.42 m m 25 Warning [26] 20.43 o o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c4: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c5: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c8: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.6/18 THEN m ELSE o - - 405 (Method Not Allowed). c13: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c16: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c17: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c18: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c19: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c20: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c21: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC. c22: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c23: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL. Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/102 - - Additional for 2xx response Table A.104D: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 3 Expires [26] 20.19, [70] 4, 5, 6 m m [26] 20.19, [70] 4, 5, 6 m m 3A Feature-Caps [190] c8 c8 [190] c7 c7 4 SIP-Etag [70] 11.3.1 m m [70] 11.3.1 m m 5 Supported [26] 20.37 m m [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c7: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c8: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/6 - - Additional for 200 (OK) response Table A.104DAA: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.104DA: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/103 OR A.6/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.104E: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Contact [26] 20.10 o o [26] 20.10 m m Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/8 OR A.6/9 OR A.6/10 OR A.6/11OR A.6/12 – Additional for 401 (Unauthorized) response Table A.104F: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 5 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.104G: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.104H: Void Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/20 - - Additional for 407 (Proxy Authentication Required) response Table A.104I: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 5 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Table A.104IA: Void Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.104J: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.104JA: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.104K: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.104L: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/29 - - Additional for 423 (Interval Too Brief) response Table A.104M: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Min-Expires [26] 20.23, [70] 5, 6 m m [26] 20.23, [70] 5, 6 m m Table A.104N: Void Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/39 - - Additional for 489 (Bad Event) response Table A.104O: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Allow-Events [28] 8.2.2 m m [28] 8.2.2 m m Prerequisite A.5/15B - - PUBLISH response Prerequisite: A.6/46 - - Additional for 504 (Server Time-out) response Table A.104OA: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.5/15B - - PUBLISH response Table A.104P: Supported message bodies within the PUBLISH response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.1.4.11 REFER method Prerequisite A.5/16 - - REFER request Table A.105: Supported header fields within the REFER request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept [26] 20.1 o o [26] 20.1 m m 0B Accept-Contact [56B] 9.2 c22 c22 [56B] 9.2 c25 c25 0C Accept-Encoding [26] 20.2 o o [26] 20.2 m m 1 Accept-Language [26] 20.3 o o [26] 20.3 m m 1AA Additional-Identity 7.2.20 n/a c54 7.2.20 n/a c55 1A Allow [26] 20.5 o o [26] 20.5 m m 2 Allow-Events [28] 8.2.2 c1 c1 [28] 8.2.2 c2 c2 3 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 4 Call-ID [26] 20.8 m m [26] 20.8 m m 4A Cellular-Network-Info 7.2.15 n/a c48 7.2.15 n/a c49 5 Contact [26] 20.10 m m [26] 20.10 m m 5A Content-Disposition [26] 20.11 o o [26] 20.11 m m 5B Content-Encoding [26] 20.12 o o [26] 20.12 m m 5BA Content-ID [256] 3.2 o c52 [256] 3.2 m c53 5C Content-Language [26] 20.13 o o [26] 20.13 m m 6 Content-Length [26] 20.14 m m [26] 20.14 m m 7 Content-Type [26] 20.15 m m [26] 20.15 m m 8 CSeq [26] 20.16 m m [26] 20.16 m m 9 Date [26] 20.17 c4 c4 [26] 20.17 m m 10 Expires [26] 20.19 o o [26] 20.19 o o 10A Feature-Caps [190] c46 c46 [190] c45 c45 11 From [26] 20.20 m m [26] 20.20 m m 11A Geolocation [89] 4.1 c26 c26 [89] 4.1 c26 c26 11B Geolocation-Routing [89] 4.2 c26 c26 [89] 4.2 c26 c26 11C History-Info [66] 4.1 c24 c24 [66] 4.1 c24 c24 11D Max-Breadth [117] 5.8 n/a c30 [117] 5.8 c31 c31 12 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c39 13 MIME-Version [26] 20.24 o o [26] 20.24 m m 14 Organization [26] 20.25 o o [26] 20.25 o o 14A P-Access-Network-Info [52] 4.4, [234] 2 c12 c13 [52] 4.4, [234] 2 c12 c14 14B P-Asserted-Identity [34] 9.1 n/a c50 [34] 9.1 c8 c8 14C P-Asserted-Service [121] 4.1 n/a c51 [121] 4.1 c29 c29 14D P-Called-Party-ID [52] 4.2, [52A] 4 x x [52] 4.2, [52A] 4 c10 c10 14E P-Charging-Function-Addresses [52] 4.5 c17 c18 [52] 4.5 c17 c18 14F P-Charging-Vector [52] 4.6 c15 c16 [52] 4.6 c15 c16 14H P-Preferred-Identity [34] 9.2 c8 c7 [34] 9.2 n/a n/a 14I P-Preferred-Service [121] 4.2 c28 c27 [121] 4.2 n/a n/a 14J P-Private-Network-Indication [134] c36 c36 [134] c36 c36 14K P-Profile-Key [97] 5 n/a n/a [97] 5 n/a n/a 14L P-Served-User [133] 6 c41 c41 [133] 6 c41 c41 14M P-User-Database [82] 4 n/a n/a [82] 4 n/a n/a 14N P-Visited-Network-ID [52] 4.3 x (note 1) x [52] 4.3 c11 n/a 14O Privacy [33] 4.2 c9 c9 [33] 4.2 c9 c9 15 Proxy-Authorization [26] 20.28 c5 c5 [26] 20.28 n/a n/a 16 Proxy-Require [26] 20.29 o n/a [26] 20.29 n/a n/a 16A Reason [34A] 2 c21 c21 [34A] 2 c21 c21 17 Record-Route [26] 20.30 n/a c39 [26] 20.30 m m 17A Refer-Sub [173] 4 c40 c40 [173] 4 c40 c40 18 Refer-To [36] 3 m m [36] 3 m m 18A Referred-By [59] 3 c23 c23 [59] 3 c23 c23 18B Reject-Contact [56B] 9.2 c22 c22 [56B] 9.2 c25 c25 18C Relayed-Charge 7.2.12 n/a c47 7.2.12 n/a c47 18D Request-Disposition [56B] 9.1 c22 c22 [56B] 9.1 c25 c25 19 Require [26] 20.32 m m [26] 20.32 m m 19A Resource-Priority [116] 3.1 c33 c33 [116] 3.1 c33 c33 20 Route [26] 20.34 m m [26] 20.34 n/a c39 20A Security-Client [48] 2.3.1 c19 c19 [48] 2.3.1 n/a n/a 20B Security-Verify [48] 2.3.1 c20 c20 [48] 2.3.1 n/a n/a 20C Session-ID [162] o c42 [162] o c42 21 Supported [26] 20.37, [26] 7.1 o o [26] 20.37, [26] 7.1 m m 21A Target-Dialog [184] 7 c43 c43 [184] 7 c44 c44 22 Timestamp [26] 20.38 c6 c6 [26] 20.38 m m 23 To [26] 20.39 m m [26] 20.39 m m 23A Trigger-Consent [125] 5.11.2 c34 c34 [125] 5.11.2 c35 c35 24 User-Agent [26] 20.41 o o [26] 20.41 o o 25 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c2: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c6: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c7: IF A.3/1 AND A.4/25 THEN o ELSE n/a - - UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c8: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c9: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c10: IF A.4/32 THEN o ELSE n/a - - the P-Called-Party-ID extension. c11: IF A.4/33 THEN o ELSE n/a - - the P-Visited-Network-ID extension. c12: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c13: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c14: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c15: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c16: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c17: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c18: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c19: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 2). c20: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c21: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c22: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c23: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By Mechanism. c24: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c25: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c26: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c27: IF (A.3/1 OR A.3A/81) AND A.4/74 THEN o ELSE n/a - - UE, MSC Server enhanced for ICS and SIP extension for the identification of services. c28: IF A.4/74 THEN o ELSE n/a - - SIP extension for the identification of services. c29: IF A.4/74 THEN m ELSE n/a - - SIP extension for the identification of services. c30: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c31: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c33: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c34: IF A.4/75A THEN m ELSE n/a - - a relay within the framework for consent-based communications in SIP. c35: IF A.4/75B THEN m ELSE n/a - - a recipient within the framework for consent-based communications in SIP. c36: IF A.4/77 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c39: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c40: IF A.4/95 THEN m ELSE n/a - - suppression of session initiation protocol REFER method implicit subscription. c41: IF A.4/78 THEN m ELSE n/a - - the SIP P-Served-User private header. c42: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c43: IF A.4/99 THEN o ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c44: IF A.4/99 THEN m ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c45: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c46: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c47: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c48: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c49: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c50: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC. c51: IF A.4/74 AND A.3/7B THEN o ELSE n/a - - SIP extension for the identification of services and AS acting as originating UA. c52: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c53: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c54: IF A.4/124 THEN o ELSE n/a - - the Additional-Identity header field extension. c55: IF A.4/124 THEN m ELSE n/a - - the Additional-Identity header field extension. NOTE 1: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT. NOTE 2: Support of this header field in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header field in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19]. Prerequisite A.5/16 - - REFER request Table A.106: Supported message bodies within the REFER request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 application/vnd.3gpp.mid-call+xml [8M] D n/a o [8M] D n/a o 2 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c1 [8ZE] n/a c1 c1: IF A.3A/102 OR A.3A/103 THEN m ELSE n/a - - MCPTT client, MCPTT server. Table A.107: Void Prerequisite A.5/17 - - REFER response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.107A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/17 - - REFER response for all remaining status-codes Table A.108: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c12 c12 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Cellular-Network-Info 7.2.15 n/a c20 7.2.15 n/a c21 1B Content-Disposition [26] 20.11 o o [26] 20.11 m m 2 Content-Encoding [26] 20.12 o o [26] 20.12 m m 2A Content-ID [256] 3.2 o c23 [256] 3.2 m c24 3 Content-Language [26] 20.13 o o [26] 20.13 m m 4 Content-Length [26] 20.14 m m [26] 20.14 m m 5 Content-Type [26] 20.15 m m [26] 20.15 m m 6 CSeq [26] 20.16 m m [26] 20.16 m m 7 Date [26] 20.17 c1 c1 [26] 20.17 m m 8 From [26] 20.20 m m [26] 20.20 m m 8A Geolocation-Error [89] 4.3 c15 c15 [89] 4.3 c15 c15 8B History-Info [66] 4.1 c14 c14 [66] 4.1 c14 c14 9 MIME-Version [26] 20.24 o o [26] 20.24 m m 10 Organization [26] 20.25 o o [26] 20.25 o o 10A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c5 c6 [52] 4.4, [52A] 4, [234] 2 c5 c7 10B P-Asserted-Identity [34] 9.1 n/a c22 [34] 9.1 c3 c3 10C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c10 c11 [52] 4.5, [52A] 4 c10 c11 10D P-Charging-Vector [52] 4.6, [52A] 4 c8 c9 [52] 4.6, [52A] 4 c8 c9 10F P-Preferred-Identity [34] 9.2 c3 x [34] 9.2 n/a n/a 10G Privacy [33] 4.2 c4 c4 [33] 4.2 c4 c4 10H Relayed-Charge 7.2.12 n/a c19 7.2.12 n/a c19 10I Require [26] 20.32 m m [26] 20.32 m m 10J Server [26] 20.35 o o [26] 20.35 o o 10K Session-ID [162] o c18 [162] o c18 11 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 o o [26] 20.41 o o 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 o (note) o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c4: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c5: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c8: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.6/18 THEN m ELSE o - - 405 (Method Not Allowed) c14: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c15: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c18: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c19: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c20: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info extension and UE. c21: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c22: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC. c23: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c24: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL. Prerequisite A.5/17 - - REFER response Prerequisite: A.6/102 - - Additional for 2xx response Table A.109: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c12 c12 [116] 3.2 c12 c12 1 Allow-Events [28] 8.2.2 c3 c3 [28] 8.2.2 c4 c4 2 Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 2A Contact [26] 20.10 m m [26] 20.10 m m 3 Feature-Caps [190] c15 c15 [190] c14 c14 5 Record-Route [26] 20.30 m m [26] 20.30 m m 6 Refer-Sub [173] 4 c13 c13 [173] 4 c13 c13 8 Supported [26] 20.37 m m [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c3: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c4: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c12: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c13: IF A.4/95 THEN m ELSE n/a - - suppression of session initiation protocol REFER method implicit subscription. c14: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c15: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. Prerequisite A.5/17 - - REFER response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.109A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0 Contact [26] 20.10 o o [26] 20.10 m m 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Table A.110: Void Prerequisite A.5/17 - - REFER response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.111: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 10 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/17 - - REFER response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.112: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 6 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.113: Void Prerequisite A.5/17 - - REFER response Prerequisite: A.6/20 - - Additional for 407 (Proxy Authentication Required) response Table A.114: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 8 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Table A.114A: Void Prerequisite A.5/17 - - REFER response Prerequisite: A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.115: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/17 - - REFER response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.115A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. Prerequisite A.5/17 - - REFER response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.116: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 8 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/17 - - REFER response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.116A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.117: Void Prerequisite A.5/17 - - REFER response Prerequisite: A.6/29H - - Additional for 470 (Consent Needed) response Table A.117A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Permission-Missing [125] 5.9.3 m m [125] 5.9.3 m m Prerequisite A.5/17 - - REFER response Prerequisite: A.6/46 - - Additional for 504 (Server Time-out) response Table A.117B: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.5/17 - - REFER response Table A.118: Supported message bodies within the REFER response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.1.4.12 REGISTER method Prerequisite A.5/18 - - REGISTER request Table A.119: Supported header fields within the REGISTER request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o o [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o o [26] 20.2 m m 3 Accept-Language [26] 20.3 o o [26] 20.3 m m 3A Allow [26] 20.5 o o [26] 20.5 m m 4 Allow-Events [28] 8.2.2 c27 c27 [28] 8.2.2 c1 c1 5 Authorization [26] 20.7, [49] c2 c29 [26] 20.7, [49] m c22 6 Call-ID [26] 20.8 m m [26] 20.8 m m 7 Call-Info [26] 20.9 o o [26] 20.9 o o 7A Cellular-Network-Info 7.2.15 n/a c43 7.2.15 n/a c44 8 Contact [26] 20.10 o m [26] 20.10 m m 9 Content-Disposition [26] 20.11 o o [26] 20.11 m m 10 Content-Encoding [26] 20.12 o o [26] 20.12 m m 10A Content-ID [256] 3.2 o c45 [256] 3.2 m c46 11 Content-Language [26] 20.13 o o [26] 20.13 m m 12 Content-Length [26] 20.14 m m [26] 20.14 m m 13 Content-Type [26] 20.15 m m [26] 20.15 m m 14 CSeq [26] 20.16 m m [26] 20.16 m m 15 Date [26] 20.17 c3 c3 [26] 20.17 m m 16 Expires [26] 20.19 o o [26] 20.19 m m 16A Feature-Caps [190] c40 c40 [190] c39 c39 17 From [26] 20.20 m m [26] 20.20 m m 17A Geolocation [89] 4.1 c31 c31 [89] 4.1 c31 c31 17B Geolocation-Routing [89] 4.2 c31 c31 [89] 4.2 c31 c31 17C History-Info [66] 4.1 c28 c28 [66] 4.1 c28 c28 17D Max-Breadth [117] 5.8 n/a c35 [117] 5.8 c36 c36 18 Max-Forwards [26] 20.22 m m [26] 20.22 n/a n/a 19 MIME-Version [26] 20.24 o o [26] 20.24 m m 20 Organization [26] 20.25 o o [26] 20.25 o o 20A P-Access-Network-Info [52] 4.4, [234] 2 c12 c13 [52] 4.4, [234] 2 c12 c14 20B P-Charging-Function-Addresses [52] 4.5 c17 c18 [52] 4.5 c17 c18 20C P-Charging-Vector [52] 4.6 c15 c16 [52] 4.6 c15 c16 20E P-User-Database [82] 4 n/a n/a [82] 4 c30 c30 20F P-Visited-Network-ID [52] 4.3 x (note 2) x [52] 4.3 c10 c11 20G Path [35] 4 c4 c5 [35] 4 m c6 20H Privacy [33] 4.2 c9 n/a [33] 4.2 c9 n/a 21 Proxy-Authorization [26] 20.28 c8 c8 [26] 20.28 n/a n/a 22 Proxy-Require [26] 20.29 o o (note 1) [26] 20.29 n/a n/a 22A Reason [34A] 2 c23 c23 [34A] 2 c23 c23 22B Recv-Info [25] 5.2.3 c37 c37 [25] 5.2.3 c37 c37 22C Referred-By [59] 3 c25 c25 [59] 3 c26 c26 22D Relayed-Charge 7.2.12 n/a c41 7.2.12 n/a c41 22E Request-Disposition [56B] 9.1 c24 c24 [56B] 9.1 n/a n/a 23 Require [26] 20.32 m m [26] 20.32 m m 23A Resource-Priority [116] 3.1 c32 c32 [116] 3.1 c32 c32 23B Resource-Share Subclause 7.2.13 n/a c42 Subclause 7.2.13 n/a c42 24 Route [26] 20.34 o x [26] 20.34 n/a n/a 24A Security-Client [48] 2.3.1 c19 c20 [48] 2.3.1 n/a n/a 24B Security-Verify [48] 2.3.1 c20 c20 [48] 2.3.1 c21 n/a 24C Session-ID [162] o c38 [162] o c38 25 Supported [26] 20.37 o c29 [26] 20.37 m m 26 Timestamp [26] 20.38 c7 c7 [26] 20.38 c7 c7 27 To [26] 20.39 m m [26] 20.39 m m 28 User-Agent [26] 20.41 o o [26] 20.41 o o 29 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c2: IF A.4/8 THEN m ELSE n/a - - authentication between UA and registrar. c3: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c4: IF A.4/24 THEN o ELSE n/a - - session initiation protocol extension header field for registering non-adjacent contacts. c5: IF A.4/24 THEN x ELSE n/a - - session initiation protocol extension header field for registering non-adjacent contacts. c6: IF A.3/4 THEN m ELSE n/a. - - S-CSCF. c7: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c8: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c9: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c10: IF A.4/33 THEN o ELSE n/a - - the P-Visited-Network-ID extension. c11: IF A.4/33 THEN m ELSE n/a - - the P-Visited-Network-ID extension. c12: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c13: IF A.4/34 AND (A.3/1 OR A.3/4) THEN o ELSE n/a - - the P-Access-Network-Info header extension and UE or S-CSCF. c14: IF A.4/34 AND (A.3/4 OR A.3/7A) THEN m ELSE n/a - - the P-Access-Network-Info header extension and S-CSCF or AS acting as terminating UA. c15: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c16: IF A.4/36 OR A.3/4 THEN m ELSE n/a - - the P-Charging-Vector header extension (including S-CSCF as registrar). c17: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c18: IF A.4/35 OR A.3/4 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension (including S-CSCF as registrar). c19: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 3). c20: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c21: IF A.4/37 AND A.4/2 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol and registrar. c22: IF A.3/4 THEN m ELSE n/a - - S-CSCF. c23: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c24: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c25: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c26: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c27: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c28: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c29: IF (A.3/1 OR A.3A/81) THEN m ELSE o - - UE, MSC Server enhanced for ICS. c30: IF A.4/48 THEN m ELSE n/a - - the P-User-Database private header extension. c31: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c32: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c35: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE n/a - - IF A.4/71 AND (A.3/9B OR A.3/9C) THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling). c36: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c37: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c38: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c39: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c40: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c41: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c42: IF A.4/112 AND A.3/2 THEN o ELSE n/a - - resource sharing, AS. c43: IF A.4/113 AND (A.3/1 OR A.3/4) THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE or S-CSCF. c44: IF A.4/113 AND (A.3/4 OR A.3/7A) THEN m ELSE n/a - - the Cellular-Network-Info header extension and S-CSCF or AS acting as terminating UA. c45: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c46: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE 1: No distinction has been made in these tables between first use of a request on a From/To/Call-ID combination, and the usage in a subsequent one. Therefore the use of "o" etc. above has been included from a viewpoint of first usage. NOTE 2: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT. NOTE 3: Support of this header field in this method is dependent on the security mechanism and the security architecture which is implemented. Prerequisite A.5/18 - - REGISTER request Table A.120: Supported message bodies within the REGISTER request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 message/sip [26] 27.5 n/a c1 [26] 27.5 n/a c2 2 3GPP IM CN subsystem XML body subclause 7.6 n/a c1 subclause 7.6 n/a c2 3 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c3 [8ZE] n/a c3 c1: IF A.3/4 THEN o ELSE n/a - - S-CSCF. c2: IF A.3/7 THEN o ELSE n/a - - AS. c3: IF A.3A/102 OR A.3A/103 THEN m ELSE n/a - - MCPTT client, MCPTT server. Table A.121: Void Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.121A: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/19 - - REGISTER response for all remaining status-codes Table A.122: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c8 c8 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Call-Info [26] 20.9 o o [26] 20.9 o o 2 Content-Disposition [26] 20.11 o o [26] 20.11 m m 3 Content-Encoding [26] 20.12 o o [26] 20.12 m m 3A Content-ID [256] 3.2 o c15 [256] 3.2 m c16 4 Content-Language [26] 20.13 o o [26] 20.13 m m 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 m m 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 c1 c1 [26] 20.17 m m 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c10 c10 [89] 4.3 c10 c10 9B History-Info [66] 4.1 c9 c9 [66] 4.1 c9 c9 10 MIME-Version [26] 20.24 o o [26] 20.24 m m 11 Organization [26] 20.25 o o [26] 20.25 o o 11A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c3 n/a [52] 4.4, [52A] 4, [234] 2 c3 n/a 11B P-Charging-Function-Addresses [52] 4.5, [52A] 4 c6 c7 [52] 4.5, [52A] 4 c6 c7 11C P-Charging-Vector [52] 4.6, [52A] 4 c4 c5 [52] 4.6, [52A] 4 c4 c5 11E Privacy [33] 4.2 c2 n/a [33] 4.2 c2 n/a 11F Relayed-Charge 7.2.12 n/a c14 7.2.12 n/a c14 11G Require [26] 20.32 m m [26] 20.32 m m 11H Server [26] 20.35 o o [26] 20.35 o o 11I Session-ID [162] o c13 [162] o c13 12 Timestamp [26] 20.38 c2 c2 [26] 20.38 m m 13 To [26] 20.39 m m [26] 20.39 m m 13A User-Agent [26] 20.41 o o [26] 20.41 o o 14 Via [26] 20.42 m m [26] 20.42 m m 15 Warning [26] 20.43 o (note) o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c3: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c4: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c5: IF A.4/36 OR A.3/4 THEN m ELSE n/a - - the P-Charging-Vector header extension (including S-CSCF as registrar). c6: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c7: IF A.4/35 OR A.3/4 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension (including S-CSCF as registrar). c8: IF A.6/18 THEN m ELSE o - - 405 (Method Not Allowed). c9: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c10: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c13: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c14: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c15: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c16: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL. Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/102 - - Additional for 2xx response Table A.123: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o o [26] 20.1 o o 1A Accept-Encoding [26] 20.2 o o [26] 20.2 m m 1B Accept-Language [26] 20.3 o o [26] 20.3 m m 1C Accept-Resource-Priority [116] 3.2 c14 c14 [116] 3.2 c14 c14 2 Allow-Events [28] 8.2.2 c12 c12 [28] 8.2.2 c13 c13 3 Authentication-Info [26] 20.6 c6 c6 [26] 20.6 c7 c7 5 Contact [26] 20.10 o o [26] 20.10 m m 5A Feature-Caps [190] c18 c18 [190] c17 c17 5B Flow-Timer [92] 11 c15 c15 [92] 11 c15 c15 5C P-Associated-URI [52] 4.1 c8 c9 [52] 4.1 c10 c11 6 Path [35] 4 c3 c3 [35] 4 c4 c4 7 Security-Server Subclause 7.2A.7 n/a x Subclause 7.2A.7 n/a c16 8 Service-Route [38] 5 c5 c5 [38] 5 c5 c5 9 Supported [26] 20.37 m m [26] 20.37 m m c1: IF (A.3/4 AND A.4/2) THEN m ELSE n/a. - - S-CSCF acting as registrar. c2: IF A.3/4 OR A.3/1 THEN m ELSE n/a. - - S-CSCF or UE. c3: IF A.4/24 THEN m ELSE n/a - - session initiation protocol extension header field for registering non-adjacent contacts. c4: IF A.4/24 THEN o ELSE n/a - - session initiation protocol extension header field for registering non-adjacent contacts. c5: IF A.4/28 THEN m ELSE n/a - - session initiation protocol extension header field for service route discovery during registration. c6: IF A.4/8 THEN o ELSE n/a - - authentication between UA and registrar. c7: IF A.4/8 THEN m ELSE n/a - - authentication between UA and registrar. c8: IF A.4/2 AND A.4/31 THEN m ELSE n/a - - P-Associated-URI header extension and registrar. c9: IF A.3/1 AND A.4/31 THEN m ELSE n/a - - P-Associated-URI header extension and S-CSCF. c10: IF A.4/31 THEN o ELSE n/a - - P-Associated-URI header extension. c11: IF A.4/31 AND A.3/1 THEN m ELSE n/a - - P-Associated-URI header extension and UE. c12: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c13: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c14: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c15: IF A.4/57 THEN m ELSE n/a - - managing client initiated connections in SIP. c16: IF A.4/37A THEN m ELSE n/a - - mediasec header field parameter for marking security mechanisms related to media. c17: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c18: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.123A: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/103 OR A.6/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.124: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Contact [26] 20.10 o (note) o [26] 20.10 m m Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.125: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 c1 x [26] 20.27 c1 x 6 Security-Server [48] 2 x x [48] 2 n/a c2 10 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/8 THEN m ELSE n/a - - support of authentication between UA and registrar. c2: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.126: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 6 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.127: Void Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/20 - - Additional for 407 (Proxy Authentication Required) response Table A.128: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Proxy-Authenticate [26] 20.27 c1 x [26] 20.27 c1 x 9 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/8 THEN m ELSE n/a - - support of authentication between UA and registrar. Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.129: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.129A: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.130: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 8 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.130A: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c2 c2 [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. c2: IF A.4/37 AND A.4/2 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol and registrar. Prerequisite A.5/19 - - REGISTER response Prerequisite: A.6/29 - - Additional for 423 (Interval Too Brief) response Table A.131: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Min-Expires [26] 20.23 m m [26] 20.23 m m Table A.132: Void Prerequisite A.5/19 - - REGISTER response Table A.133: Supported message bodies within the REGISTER response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.1.4.13 SUBSCRIBE method Prerequisite A.5/20 - - SUBSCRIBE request Table A.134: Supported header fields within the SUBSCRIBE request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o o [26] 20.1 m m 1A Accept-Contact [56B] 9.2 c22 c22 [56B] 9.2 c26 c26 2 Accept-Encoding [26] 20.2 o o [26] 20.2 m m 3 Accept-Language [26] 20.3 o o [26] 20.3 m m 3A Allow [26] 20.5 o o [26] 20.5 m m 4 Allow-Events [28] 8.2.2 o o [28] 8.2.2 m m 5 Authorization [26] 20.7 c3 c3 [26] 20.7 c3 c3 6 Call-ID [26] 20.8 m m [26] 20.8 m m 6A Call-Info [26] 20.9 o o [26] 20.9 o o 6B Cellular-Network-Info 7.2.15 n/a c48 7.2.15 n/a c49 6C Contact [26] 20.10 m m [26] 20.10 m m 7 Content-Disposition [26] 20.11 o o [26] 20.11 m m 8 Content-Encoding [26] 20.12 o o [26] 20.12 m m 8A Content-ID [256] 3.2 o c52 [256] 3.2 m c53 9 Content-Language [26] 20.13 o o [26] 20.13 m m 10 Content-Length [26] 20.14 m m [26] 20.14 m m 11 Content-Type [26] 20.15 m m [26] 20.15 m m 12 CSeq [26] 20.16 m m [26] 20.16 m m 13 Date [26] 20.17 c4 c4 [26] 20.17 m m 14 Event [28] 8.2.1 m m [28] 8.2.1 m m 15 Expires [26] 20.19 o (note 1) o (note 1) [26] 20.19 m m 15A Feature-Caps [190] c46 c46 [190] c45 c45 16 From [26] 20.20 m m [26] 20.20 m m 16A Geolocation [89] 4.1 c27 c27 [89] 4.1 c27 c27 16B Geolocation-Routing [89] 4.2 c27 c27 [89] 4.2 c27 c27 16C History-Info [66] 4.1 c25 c25 [66] 4.1 c25 c25 16D Max-Breadth [117] 5.8 n/a c38 [117] 5.8 c39 c39 17 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c41 18 MIME-Version [26] 20.24 o o [26] 20.24 m m 18A Organization [26] 20.25 o o [26] 20.25 o o 18B P-Access-Network-Info [52] 4.4, [234] 2 c12 c13 [52] 4.4, [234] 2 c12 c14 18C P-Asserted-Identity [34] 9.1 n/a c50 [34] 9.1 c6 c6 18D P-Asserted-Service [121] 4.1 n/a c51 [121] 4.1 c32 c32 18E P-Called-Party-ID [52] 4.2 x x [52] 4.2 c10 c10 18F P-Charging-Function-Addresses [52] 4.5 c17 c18 [52] 4.5 c17 c18 18G P-Charging-Vector [52] 4.6 c15 c16 [52] 4.6 c15 c16 18I P-Preferred-Identity [34] 9.2 c6 c7 [34] 9.2 n/a n/a 18J P-Preferred-Service [121] 4.2 c31 c30 [121] 4.2 n/a n/a 18K P-Private-Network-Indication [134] c35 c35 [134] c35 c35 18L P-Profile-Key [97] 5 n/a n/a [97] 5 n/a n/a 18M P-Served-User [133] 6 c40 c40 [133] 6 c40 c40 18N P-User-Database [82] 4 n/a n/a [82] 4 n/a n/a 18O P-Visited-Network-ID [52] 4.3 x (note 2) x [52] 4.3 c11 n/a 18P Priority [26] 20.26 o o [26] 20.26 o o 18Q Privacy [33] 4.2 c9 c9 [33] 4.2 c9 c9 19 Proxy-Authorization [26] 20.28 c5 c5 [26] 20.28 n/a n/a 20 Proxy-Require [26] 20.29 o n/a [26] 20.29 n/a n/a 20A Reason [34A] 2 c21 c21 [34A] 2 c21 c21 21 Record-Route [26] 20.30 n/a c41 [26] 20.30 m m 21A Referred-By [59] 3 c23 c23 [59] 3 c24 c24 21B Reject-Contact [56B] 9.2 c22 c22 [56B] 9.2 c26 c26 21C Relayed-Charge 7.2.12 n/a c47 7.2.12 n/a c47 21D Request-Disposition [56B] 9.1 c22 c22 [56B] 9.1 c26 c26 22 Require [26] 20.32 m m [26] 20.32 m m 22A Resource-Priority [116] 3.1 c29 c29 [116] 3.1 c29 c29 23 Route [26] 20.34 m m [26] 20.34 n/a c41 23A Security-Client [48] 2.3.1 c19 c19 [48] 2.3.1 n/a n/a 23B Security-Verify [48] 2.3.1 c20 c20 [48] 2.3.1 n/a n/a 23C Session-ID [162] o c42 [162] o c42 24 Supported [26] 20.37 o o [26] 20.37 m m 24A Target-Dialog [184] 7 c43 c43 [184] 7 c44 c44 25 Timestamp [26] 20.38 c8 c8 [26] 20.38 m m 26 To [26] 20.39 m m [26] 20.39 m m 26A Trigger-Consent [125] 5.11.2 c33 c33 [125] 5.11.2 c34 c34 27 User-Agent [26] 20.41 o o [26] 20.41 o o 28 Via [26] 20.42 m m [26] 20.42 m m c3: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c4: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c5: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c6: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c7: IF A.3/1 AND A.4/25 THEN o ELSE n/a - - UE and private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c8: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c9: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c10: IF A.4/32 THEN o ELSE n/a - - the P-Called-Party-ID extension. c11: IF A.4/33 THEN o ELSE n/a - - the P-Visited-Network-ID extension. c12: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c13: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c14: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c15: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c16: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c17: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c18: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c19: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 3). c20: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c21: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c22: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c23: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c24: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c25: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c26: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c27: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c29: IF A.4/70A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c30: IF (A.3/1 OR A.3A/81) AND A.4/74 THEN o ELSE n/a - - UE, MSC Server enhanced for ICS and SIP extension for the identification of services. c31: IF A.4/74 THEN o ELSE n/a - - SIP extension for the identification of services. c32: IF A.4/74 THEN m ELSE n/a - - SIP extension for the identification of services. c33: IF A.4/75A THEN m ELSE n/a - - a relay within the framework for consent-based communications in SIP. c34: IF A.4/75B THEN m ELSE n/a - - a recipient within the framework for consent-based communications in SIP. c35: IF A.4/77 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c38: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c39: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c40: IF A.4/78 THEN m ELSE n/a - - the SIP P-Served-User private header. c41: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c42: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c43: IF A.4/99 THEN o ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c44: IF A.4/99 THEN m ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c45: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c46: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c47: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c48: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c49: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c50: IF A.4/25 AND (A.3/7B OR A.3/8 OR A.3A/81) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC, MSC Server enhanced for ICS. c51: IF A.4/74 AND A.3/7B THEN o ELSE n/a - - SIP extension for the identification of services and AS acting as originating UA. c52: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c53: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE 1: The strength of this requirement is RECOMMENDED rather than OPTIONAL. NOTE 2: The strength of this requirement in RFC 7315 [52] is SHOULD NOT, rather than MUST NOT. NOTE 3: Support of this header field in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header field in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19]. Prerequisite A.5/20 - - SUBSCRIBE request Table A.135: Supported message bodies within the SUBSCRIBE request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c1 [8ZE] n/a c1 2 application/simple-filter+xml [243] o c1 [243] n/a c1 c1 IF A.3A/102 OR A.3A/103 THEN m ELSE n/a - - MCPTT client, MCPTT server. Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.135A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/21 - - SUBSCRIBE response for all remaining status-codes Table A.136: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c12 c12 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Call-Info [26] 20.9 o o [26] 20.9 o o 1B Cellular-Network-Info 7.2.15 n/a c19 7.2.15 n/a c20 2 Content-Disposition [26] 20.11 o o [26] 20.11 m m 3 Content-Encoding [26] 20.12 o o [26] 20.12 m m 3A Content-ID [256] 3.2 o c22 [256] 3.2 m c23 4 Content-Language [26] 20.13 o o [26] 20.13 m m 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 m m 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 c1 c1 [26] 20.17 m m 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c14 c14 [89] 4.3 c14 c14 9B History-Info [66] 4.1 c13 c13 [66] 4.1 c13 c13 10 MIME-Version [26] 20.24 o o [26] 20.24 m m 10A Organization [26] 20.25 o o [26] 20.25 o o 10B P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c5 c6 [52] 4.4, [52A] 4, [234] 2 c5 c7 10C P-Asserted-Identity [34] 9.1 n/a c21 [34] 9.1 c3 c3 10D P-Charging-Function-Addresses [52] 4.5, [52A] 4 c10 c11 [52] 4.5, [52A] 4 c10 c11 10E P-Charging-Vector [52] 4.6, [52A] 4 c8 c9 [52] 4.6, [52A] 4 c8 c9 10G P-Preferred-Identity [34] 9.2 c3 x [34] 9.2 n/a n/a 10H Privacy [33] 4.2 c4 c4 [33] 4.2 c4 c4 10I Relayed-Charge 7.2.12 n/a c18 7.2.12 n/a c18 10J Require [26] 20.32 m m [26] 20.32 m m 10K Server [26] 20.35 o o [26] 20.35 o o 10L Session-ID [162] o c17 [162] o c17 11 Timestamp [26] 20.38 m m [26] 20.38 c2 c2 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 o o [26] 20.41 o o 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 o (note) o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/25 THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c4: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c5: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c6: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c7: IF A.4/34 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c8: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.6/18 THEN m ELSE o - - 405 (Method Not Allowed). c13: IF A.4/47 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c14: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c17: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c18: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c19: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info extension and UE. c20: IF A.4/113 AND (A.3/7A OR A.3/7D) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller. c21: IF A.4/25 AND (A.3/7B OR A.3/8) THEN o ELSE n/a - - private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks and AS acting as originating UA, MRFC. c22: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c23: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL. Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/102 - - Additional for 2xx response Table A.137: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c5 c5 [116] 3.2 c5 c5 0B Allow-Events [28] 8.2.2 o o [28] 8.2.2 m m 1 Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 1A Contact [26] 20.10 m m [26] 20.10 m m 2 Expires [26] 20.19 m m [26] 20.19 m m 2A Feature-Caps [190] c8 c8 [190] c7 c7 3 Record-Route [26] 20.30 m m [26] 20.30 m m 6 Supported [26] 20.37 m m [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c5: IF A.4/70A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c7: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c8: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.137A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/103 OR A.6/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.138: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Contact [26] 20.10 m (note) m [26] 20.10 m m NOTE: The strength of this requirement is RECOMMENDED rather than MANDATORY for a 485 response. Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.139: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480 (Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.140: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.141: Void Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/20 - - Additional for 407 (Proxy Authentication Required) response Table A.142: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 6 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Table A.142A: Void Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.143: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.143A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.144: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.144A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/29 - - Additional for 423 (Interval Too Brief) response Table A.145: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Min-Expires [26] 20.23 m m [26] 20.23 m m Table A.146: Void Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/29H - - Additional for 470 (Consent Needed) response Table A.146A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Permission-Missing [125] 5.9.3 m m [125] 5.9.3 m m Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/39 - - Additional for 489 (Bad Event) response Table A.147: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Allow-Events [28] 8.2.2 m m [28] 8.2.2 m m Table A.148: Void Prerequisite A.5/21 - - SUBSCRIBE response Prerequisite: A.6/46 - - Additional for 504 (Server Time-out) response Table A.148A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.5/21 - - SUBSCRIBE response Table A.149: Supported message bodies within the SUBSCRIBE response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.1.4.14 UPDATE method Prerequisite A.5/22 - - UPDATE request Table A.150: Supported header fields within the UPDATE request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o o [26] 20.1 m m 1A Accept-Contact [56B] 9.2 c20 c20 [56B] 9.2 c24 c24 2 Accept-Encoding [26] 20.2 o o [26] 20.2 m m 3 Accept-Language [26] 20.3 o o [26] 20.3 m m 4 Allow [26] 20.5 o o [26] 20.5 m m 5 Allow-Events [28] 8.2.2 c2 c2 [28] 8.2.2 c3 c3 6 Authorization [26] 20.7 c4 c4 [26] 20.7 c4 c4 7 Call-ID [26] 20.8 m m [26] 20.8 m m 8 Call-Info [26] 20.9 o o [26] 20.9 o o 8A Cellular-Network-Info 7.2.15 n/a c40 7.2.15 n/a c41 9 Contact [26] 20.10 m m [26] 20.10 m m 10 Content-Disposition [26] 20.11 o o [26] 20.11 m m 11 Content-Encoding [26] 20.12 o o [26] 20.12 m m 11A Content-ID [256] 3.2 o c43 [256] 3.2 m c44 12 Content-Language [26] 20.13 o o [26] 20.13 m m 13 Content-Length [26] 20.14 m m [26] 20.14 m m 14 Content-Type [26] 20.15 m m [26] 20.15 m m 15 CSeq [26] 20.16 m m [26] 20.16 m m 16 Date [26] 20.17 c5 c5 [26] 20.17 m m 16A Feature-Caps [190] c37 c37 [190] c36 c36 17 From [26] 20.20 m m [26] 20.20 m m 17A Geolocation [89] 4.1 c25 c25 [89] 4.1 c25 c25 17B Geolocation-Routing [89] 4.2 c25 c25 [89] 4.2 c25 c25 17C Max-Breadth [117] 5.8 n/a c29 [117] 5.8 c30 c30 18 Max-Forwards [26] 20.22 m m [26] 20.22 n/a c31 19 MIME-Version [26] 20.24 o o [26] 20.24 m m 19A Min-SE [58] 5 c21 c21 [58] 5 c21 c21 20 Organization [26] 20.25 o o [26] 20.25 o o 20A P-Access-Network-Info [52] 4.4, [234] 2 c11 c12 [52] 4.4, [234] 2 c11 c13 20B P-Charging-Function-Addresses [52] 4.5 c16 c17 [52] 4.5 c16 c17 20C P-Charging-Vector [52] 4.6 c14 c15 [52] 4.6 c14 c15 20E P-Early-Media [109] 8 c26 c26 [109] 8 c26 c26 20EA Priority-Share Subclause 7.2.16 n/a c42 Subclause 7.2.16 n/a c42 20F Privacy [33] 4.2 c6 n/a [33] 4.2 c6 n/a 21 Proxy-Authorization [26] 20.28 c10 c10 [26] 20.28 n/a n/a 22 Proxy-Require [26] 20.29 o n/a [26] 20.29 n/a n/a 22A Reason [34A] 2 c8 c8 [34A] 2 c8 c8 23 Record-Route [26] 20.30 n/a c31 [26] 20.30 n/a c31 23A Recv-Info [25] 5.2.3 c34 c34 [25] 5.2.3 c34 c34 23B Referred-By [59] 3 c22 c22 [59] 3 c23 c23 23C Reject-Contact [56B] 9.2 c20 c20 [56B] 9.2 c24 c24 23D Relayed-Charge 7.2.12 n/a c38 7.2.12 n/a c38 23E Request-Disposition [56B] 9.1 c20 c20 [56B] 9.1 c24 c24 24 Require [26] 20.32 m m [26] 20.32 m m 24A Resource-Priority [116] 3.1 c33 c33 [116] 3.1 c33 c33 24B Resource-Share Subclause 7.2.13 n/a c39 Subclause 7.2.13 n/a c39 25 Route [26] 20.34 m m [26] 20.34 n/a c31 25A Security-Client [48] 2.3.1 c18 c18 [48] 2.3.1 n/a n/a 25B Security-Verify [48] 2.3.1 c19 c19 [48] 2.3.1 n/a n/a 25C Session-Expires [58] 4 c21 c21 [58] 4 c21 c21 25D Session-ID [162] o c35 [162] o c35 26 Supported [26] 20.37 o o [26] 20.37 m m 27 Timestamp [26] 20.38 c9 c9 [26] 20.38 m m 28 To [26] 20.39 m m [26] 20.39 m m 29 User-Agent [26] 20.41 o o [26] 20.41 o o 30 Via [26] 20.42 m m [26] 20.42 m m c2: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c3: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c4: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c5: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c6: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.4/38 THEN o ELSE n/a - - the Reason header field for the session initiation protocol. c9: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c10: IF A.4/8A THEN m ELSE n/a - - authentication between UA and proxy. c11: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c12: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c13: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller or EATF. c14: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c15: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c16: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c17: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c18: IF A.4/37 OR A.4/37A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note). c19: IF A.4/37 OR A.4/37A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c20: IF A.4/40 THEN o ELSE n/a - - caller preferences for the session initiation protocol. c21: IF A.4/42 THEN m ELSE n/a - - the SIP session timer. c22: IF A.4/43 THEN m ELSE n/a - - the SIP Referred-By mechanism. c23: IF A.4/43 THEN o ELSE n/a - - the SIP Referred-By mechanism. c24: IF A.4/40 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c25: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c26: IF A.4/66 THEN m ELSE n/a - - the SIP P-Early-Media private header extension for authorization of early media. c29: IF A.4/71 AND (A.3/9B OR A.3/9C OR A.3/13B OR A.3/13C) THEN m ELSE IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - addressing an amplification vulnerability in session initiation protocol forking proxies, IBCF (IMS-ALG), IBCF (Screening of SIP signalling), ISC gateway function (IMS-ALG), ISC gateway function (Screening of SIP signalling), UE, UE performing the functions of an external attached network. c30: IF A.4/71 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c31: IF A.3/1 AND NOT A.3C/1 THEN n/a ELSE o - - UE, UE performing the functions of an external attached network. c33: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c34: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c35: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c36: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c37: IF A.4/100 AND A.3/1 AND NOT A.3C/1 THEN n/a ELSE IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy, UE, UE performing the functions of an external attached network. c38: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c39: IF A.4/112 THEN o ELSE n/a - - resource sharing. c40: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c41: IF A.4/113 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller or EATF. c42: IF A.4/114 THEN o ELSE n/a - - priority sharing. c43: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c44: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: Support of this header field in this method is dependent on the security mechanism and the security architecture which is implemented. Use of this header field in this method is not appropriate to the security mechanism defined by 3GPP TS 33.203 [19]. Prerequisite A.5/22 - - UPDATE request Table A.151: Supported message bodies within the UPDATE request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/1 - - Additional for 100 (Trying) response Table A.151A: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 m m 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. Prerequisite A.5/23 - - UPDATE response for all remaining status-codes Table A.152: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 c11 c11 [26] 20.5 m m 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Call-Info [26] 20.9 o o [26] 20.9 o o 1B Cellular-Network-Info 7.2.15 n/a c19 7.2.15 n/a c20 1C Contact [26] 20.10 o o [26] 20.10 o o 2 Content-Disposition [26] 20.11 o o [26] 20.11 m m 3 Content-Encoding [26] 20.12 o o [26] 20.12 m m 3A Content-ID [256] 3.2 o c21 [256] 3.2 m c22 4 Content-Language [26] 20.13 o o [26] 20.13 m m 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 m m 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 c1 c1 [26] 20.17 m m 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c13 c13 [89] 4.3 c13 c13 10 MIME-Version [26] 20.24 o o [26] 20.24 m m 10A Organization [26] 20.25 o o [26] 20.25 o o 10B P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c4 c5 [52] 4.4, [52A] 4, [234] 2 c4 c6 10C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c9 c10 [52] 4.5, [52A] 4 c9 c10 10D P-Charging-Vector [52] 4.6, [52A] 4 c7 c8 [52] 4.6, [52A] 4 c7 c8 10F Privacy [33] 4.2 c3 n/a [33] 4.2 c3 n/a 10G Recv-Info [25] 5.2.3 c16 c16 [25] 5.2.3 c16 c16 10H Relayed-Charge 7.2.12 n/a c18 7.2.12 n/a c18 10I Require [26] 20.31 m m [26] 20.31 m m 10J Server [26] 20.35 o o [26] 20.35 o o 10K Session-ID [162] o c17 [162] o c17 11 Timestamp [26] 20.38 c12 c12 [26] 20.38 c2 c2 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 o o [26] 20.41 o o 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 o (note) o [26] 20.43 o o c1: IF A.4/11 THEN o ELSE n/a - - insertion of date in requests and responses. c2: IF A.4/6 THEN m ELSE n/a - - timestamping of requests. c3: IF A.4/26 THEN o ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c4: IF A.4/34 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c5: IF A.4/34 AND A.3/1 THEN m ELSE n/a - - the P-Access-Network-Info header extension and UE. c6: IF A.4/34 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the P-Access-Network-Info header extension and AS acting as terminating UA, AS acting as third-party call controller or EATF. c7: IF A.4/36 THEN o ELSE n/a - - the P-Charging-Vector header extension. c8: IF A.4/36 THEN m ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.4/35 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c10: IF A.4/35 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.6/18 THEN m ELSE o - - 405 (Method Not Allowed) c12: IF A.4/6 THEN o ELSE n/a - - timestamping of requests. c13: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c16: IF A.4/13 THEN m ELSE IF A.4/13A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c17: IF A.4/91 THEN m ELSE n/a - - the Session-ID header. c18: IF A.4/111 THEN m ELSE n/a - - the Relayed-Charge header field extension. c19: IF A.4/113 AND A.3/1 THEN m ELSE n/a - - the Cellular-Network-Info header extension and UE. c20: IF A.4/113 AND (A.3/7A OR A.3/7D OR A3A/84) THEN m ELSE n/a - - the Cellular-Network-Info header extension and AS acting as terminating UA or AS acting as third-party call controller or EATF. c21: IF A.4/119 THEN o ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). c22: IF A.4/119 THEN m ELSE n/a - - Content-ID header field in Session Initiation Protocol (SIP). NOTE: For a 488 (Not Acceptable Here) response, RFC 3261 [26] gives the status of this header field as SHOULD rather than OPTIONAL. Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/102 - - Additional for 2xx response Table A.153: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept [26] 20.1 o o [26] 20.1 m m 0B Accept-Encoding [26] 20.2 o o [26] 20.2 m m 0C Accept-Language [26] 20.3 o o [26] 20.3 m m 0D Accept-Resource-Priority [116] 3.2 c14 c14 [116] 3.2 c14 c14 1 Allow-Events [28] 8.2.2 c4 c4 [28] 8.2.2 c5 c5 2 Authentication-Info [26] 20.6 c1 c1 [26] 20.6 c2 c2 3 Contact [26] 20.10 m m [26] 20.10 m m 3A Feature-Caps [190] c16 c16 [190] c16 c16 3B P-Early-Media [109] 8 c6 c6 [109] 8 c6 c6 3C Priority-Share Subclause 7.2.16 n/a c18 Subclause 7.2.16 n/a c18 3E Resource-Share Subclause 7.2.13 n/a c17 Subclause 7.2.13 n/a c17 4 Session-Expires [58] c3 c3 [58] c3 c3 6 Supported [26] 20.37 m m [26] 20.37 m m c1: IF A.4/7 THEN o ELSE n/a - - authentication between UA and UA. c2: IF A.4/7 THEN m ELSE n/a - - authentication between UA and UA. c3: IF A.4/42 THEN m ELSE n/a - - the SIP session timer c4: IF A.4/22 THEN o ELSE n/a - - acting as the notifier of event information. c5: IF A.4/23 THEN m ELSE n/a - - acting as the subscriber to event information. c6: IF A.4/66 THEN m ELSE n/a - - the SIP P-Early-Media private header extension for authorization of early media. c14: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c16: IF A.4/100 THEN m ELSE n/a - - indication of features supported by proxy. c17: IF A.4/112 THEN o ELSE n/a - - resource sharing. c18: IF A.4/114 THEN o ELSE n/a - - priority sharing. Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/103 OR A.6/104 OR A.6/105 OR A.6/106 - - Additional for 3xx – 6xx response Table A.153A: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 o o [26] 20.18 o o 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.4/115 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/103 OR A.6/35 - - Additional for 3xx, 485 (Ambiguous) response Table A.154: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Contact [26] 20.10 o o [26] 20.10 o o Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/14 - - Additional for 401 (Unauthorized) response Table A.154A: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 m m c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/17 OR A.6/23 OR A.6/30 OR A.6/36 OR A.6/42 OR A.6/45 OR A.6/50 OR A.6/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.155: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Retry-After [26] 20.33 o o [26] 20.33 o o Table A.156: Void Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/20 - - Additional for 407 (Proxy Authentication Required) response Table A.157: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 c1 c1 [26] 20.27 c1 c1 8 WWW-Authenticate [26] 20.44 o o [26] 20.44 o o c1: IF A.4/7 THEN m ELSE n/a - - support of authentication between UA and UA. Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/25 - - Additional for 415 (Unsupported Media Type) response Table A.158: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 o.1 o.1 [26] 20.1 m m 2 Accept-Encoding [26] 20.2 o.1 o.1 [26] 20.2 m m 3 Accept-Language [26] 20.3 o.1 o.1 [26] 20.3 m m o.1 At least one of these capabilities is supported. Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.158A: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.4/70 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/27 - - Additional for 420 (Bad Extension) response Table A.159: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 7 Unsupported [26] 20.40 m m [26] 20.40 m m Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/28 OR A.6/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.159A: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 x x [48] 2 c1 c1 c1: IF A.4/37 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.5/23 - - UPDATE response Prerequisite: A.6/28A - - Additional for 422 (Session Interval Too Small) response Table A.159B: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Min-SE [58] 5 c1 c1 [58] 5 c1 c1 c1: IF A.4/42 THEN m ELSE n/a - - the SIP session timer. Table A.160: Void Prerequisite A.5/23 - - UPDATE response Table A.161: Supported message bodies within the UPDATE response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2 Proxy role A.2.2.1 Introduction This subclause contains the ICS proforma tables related to the proxy role. They need to be completed only for proxy implementations. Prerequisite: A.2/2 - - proxy role A.2.2.2 Major capabilities Table A.162: Major capabilities Item Does the implementation support Reference RFC status Profile status Capabilities within main protocol 3 initiate session release? [26] 16 x c27 4 stateless proxy behaviour? [26] 16.11 o.1 c29 5 stateful proxy behaviour? [26] 16.2 o.1 c28 6 forking of initial requests? [26] 16.1 c1 c31 7 support of indication of TLS connections in the Record-Route header on the upstream side? [26] 16.7 o n/a 8 support of indication TLS connections in the Record-Route header on the downstream side? [26] 16.7 o n/a 8A authentication between UA and proxy? [26] 20.28, 22.3, [287] o c85 9 insertion of date in requests and responses? [26] 20.17 o o 10 suppression or modification of alerting information data? [26] 20.4 o o 11 reading the contents of the Require header before proxying the request or response? [26] 20.32 o o 12 adding or modifying the contents of the Require header before proxying the REGISTER request or response [26] 20.32 o m 13 adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER? [26] 20.32 o o 14 being able to insert itself in the subsequent transactions in a dialog (record-routing)? [26] 16.6 o c2 15 the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing? [26] 16.7 c3 c3 16 reading the contents of the Supported header before proxying the response? [26] 20.37 o o 17 reading the contents of the Unsupported header before proxying the 420 response to a REGISTER? [26] 20.40 o m 18 reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER? [26] 20.40 o o 19 the inclusion of the Error-Info header in 3xx - 6xx responses? [26] 20.18 o o 19A reading the contents of the Organization header before proxying the request or response? [26] 20.25 o o 19B adding or concatenating the Organization header before proxying the request or response? [26] 20.25 o o 19C reading the contents of the Call-Info header before proxying the request or response? [26] 20.9 o o 19D adding or concatenating the Call-Info header before proxying the request or response? [26] 20.9 o o 19E delete Contact headers from 3xx responses prior to relaying the response? [26] 20 o o 19F proxy reading the contents of a body or including a body in a request or response? [26] o c88 19G proxy modifying the content of a body 3GPP TS 24.237 [8M] n/a c103 Extensions 20 SIP INFO method and package framework? [25] o o 20A legacy INFO usage? [25] 2, 3 o o 21 reliability of provisional responses in SIP? [27] o i 22 the REFER method? [36] o o 22A clarifications for the use of REFER with RFC6665? [231] c113 c113 22B explicit subscriptions for the REFER method? [232] o o 23 integration of resource management and SIP? [30] [64] o i 24 the SIP UPDATE method? [29] c4 i 26 SIP extensions for media authorization? [31] o c7 27 SIP specific event notification [28] o i 28 a clarification on the use of GRUUs in the SIP event notification framework? [232] n/a n/a 29 Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts [35] o c6 30 private extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks [34] o m 30A act as first entity within the trust domain for asserted identity? [34] c5 c9 30B act as entity within trust network that can route outside the trust network? [34] c5 c9 30C act as entity passing on identity transparently independent of trust domain? [34] c5 c96 31 a privacy mechanism for the Session Initiation Protocol (SIP) [33] o m 31A request of privacy by the inclusion of a Privacy header [33] n/a n/a 31B application of privacy based on the received Privacy header [33] c10 c12 31C passing on of the Privacy header transparently [33] c10 c13 31D application of the privacy option "header" such that those headers which cannot be completely expunged of identifying information without the assistance of intermediaries are obscured? [33] 5.1 x x 31E application of the privacy option "session" such that anonymization for the session(s) initiated by this message occurs? [33] 5.2 n/a n/a 31F application of the privacy option "user" such that user level privacy functions are provided by the network? [33] 5.3 n/a n/a 31G application of the privacy option "id" such that privacy of the network asserted identity is provided by the network? [34] 7 c11 c12 31H application of the privacy option "history" such that privacy of the History-Info header is provided by the network? [66] 7.2 c34 c34 32 Session Initiation Protocol Extension Header Field for Service Route Discovery During Registration [38] o c30 33 a messaging mechanism for the Session Initiation Protocol (SIP) [50] o m 34 Compressing the Session Initiation Protocol [55] o c7 35 private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP)? [52] o m 36 the P-Associated-URI header extension? [52] 4.1, [52A] 4 c14 c15 37 the P-Called-Party-ID header extension? [52] 4.2, [52A] 4` c14 c16 38 the P-Visited-Network-ID header extension? [52] 4.3, [52A] 4, [52B] 3 c14 c17 39 reading, or deleting the P-Visited-Network-ID header before proxying the request or response? [52] 4.3 c18 n/a 41 the P-Access-Network-Info header extension? [52] 4.4, [52A] 4, [234] 2 c14 c19 42 act as first entity within the trust domain for access network information? [52] 4.4 c20 c21 43 act as subsequent entity within trust network for access network information that can route outside the trust network? [52] 4.4 c20 c22 44 the P-Charging-Function-Addresses header extension? [52] 4.5, [52A] 4 c14 m 44A adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response? [52] 4.6 c25 c26 45 the P-Charging-Vector header extension? [52] 4.6, [52A] 4 c14 m 46 adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response? [52] 4.6 c23 c24 47 security mechanism agreement for the session initiation protocol? [48] o c7 47A mediasec header field parameter for marking security mechanisms related to media? Subclause 7.2A.7 n/a c99 48 the Reason header field for the session initiation protocol [34A] o c78 48A carrying Q.850 codes in reason header fields in SIP (Session Initiation Protocol) responses? [130] o o 48B the location parameter for the SIP Reason header field? [255] o o 48C Handling of Identity Header Errors for Secure Telephone Identity Revisited (STIR) (carrying STIR codes in Reason header fields in SIP responses)? [294] o c130 48D Multiple SIP Reason Header Field Values? [296] o c131 49 an extension to the session initiation protocol for symmetric response routeing [56A] o m 50 caller preferences for the session initiation protocol? [56B] c33 c33 50A the proxy-directive within caller-preferences? [56B] 9.1 o.4 o.4 50B the cancel-directive within caller-preferences? [56B] 9.1 o.4 o.4 50C the fork-directive within caller-preferences? [56B] 9.1 o.4 c32 50D the recurse-directive within caller-preferences? [56B] 9.1 o.4 o.4 50E the parallel-directive within caller-preferences? [56B] 9.1 o.4 c32 50F the queue-directive within caller-preferences? [56B] 9.1 o.4 o.4 51 an event state publication extension to the session initiation protocol? [70] o m 52 SIP session timer? [58] o o 53 the SIP Referred-By mechanism? [59] o o 54 the Session Inititation Protocol (SIP) "Replaces" header? [60] o o 55 the Session Inititation Protocol (SIP) "Join" header? [61] o o 56 the callee capabilities? [62] o o 57 an extension to the session initiation protocol for request history information? [66] o o 57A application of the "mp" optional header field parameter? [66] o o 57B application of the "rc" optional header field parameter? [66] o o 57C application of the "np" optional header field parameter? [66] o o 58 Rejecting anonymous requests in the session initiation protocol? [67] o o 59 session initiation protocol URIs for applications such as voicemail and interactive voice response [68] o o 59A Session Initiation Protocol (SIP) cause URI parameter for service number translation? [230] c111 c111 60 the P-User-Database private header extension? [82] o c95 61 Session initiation protocol's non-INVITE transactions? [84] m m 62 a uniform resource name for services [69] n/a c35 63 obtaining and using GRUUs in the Session Initiation Protocol (SIP) [93] o c36 65 the Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)? [96] o o (note2) 66 the SIP P-Profile-Key private header extension? [97] o c41 66A making the first query to the database in order to populate the P-Profile-Key header? [97] c38 c39 66B using the information in the P-Profile-Key header? [97] c38 c40 67 managing client initiated connections in SIP? [92] 11 o c42 68 indicating support for interactive connectivity establishment in SIP? [102] o o 69 multiple-recipient MESSAGE requests in the session initiation protocol [104] n/a n/a 70 SIP location conveyance? [89] o c94 70A addition or modification of location in a SIP method? [89] c44 c45 70B passes on locations in SIP method without modification? [89] c44 c46 71 referring to multiple resources in the session initiation protocol? [105] n/a n/a 72 conference establishment using request-contained lists in the session initiation protocol? [106] n/a n/a 73 subscriptions to request-contained resource lists in the session initiation protocol? [107] n/a n/a 74 dialstring parameter for the session initiation protocol uniform resource identifier? [103] o n/a 75 the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular? [111] o c60 76 the SIP P-Early-Media private header extension for authorization of early media? [109] 8 o c51 77 number portability parameters for the 'tel' URI? [112] o c47 77A assert or process carrier indication? [112] o c48 77B local number portability? [112] o c50 79 extending the session initiation protocol Reason header for preemption events [115] c79 c79 80 communications resource priority for the session initiation protocol? [116] o c80 80A inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol? [116] 4.2 c82 c82 80B inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol? [116] 4.2 c82 c82 81 addressing an amplification vulnerability in session initiation protocol forking proxies? [117] c52 c52 82 the remote application identification of applying signalling compression to SIP [79] 9.1 o c7 83 a session initiation protocol media feature tag for MIME application subtypes? [120] o c53 84 SIP extension for the identification of services? [121] o c54 84A act as authentication entity within the trust domain for asserted service? [121] c55 c56 85 a framework for consent-based communications in SIP? [125] o m 86 a mechanism for transporting user-to-user call control information in SIP? [126] o c84 87 the SIP P-Private-Network-Indication private-header (P-Header)? [134] o o 88 the SIP P-Served-User private header in the 3GG IM CN subsystem? [133] 6 o o 89 the SIP P-Served-User header extension for Originating CDIV session case? [239] 4 c126 c126 90 marking SIP messages to be logged? [140] o m 91 the 199 (Early Dialog Terminated) response code [142] o c90 92 message body handling in SIP? [150] o c89 93 indication of support for keep-alive? [143] o c51 94 SIP Interface to VoiceXML Media Services? [145] o c91 95 common presence and instant messaging (CPIM): message format? [151] o o 96 instant message disposition notification? [157] o o 97 requesting answering modes for SIP? [158] o o 97A adding, deleting or reading the Answer-Mode header or Priv-Answer-Mode before proxying the request or response? [158] o c92 99 the early session disposition type for SIP? [74B] i i 101 The Session-ID header? [162] o o 102 correct transaction handling for 2xx responses to Session Initiation Protocol INVITE requests? [163] m m 103 addressing Record-Route issues in the Session Initiation Protocol (SIP)? [164] o o 104 essential correction for IPv6 ABNF and URI comparison in RFC3261? [165] m m 105 suppression of session initiation protocol REFER method implicit subscription? [173] o c100 106 Alert-Info URNs for the Session Initiation Protocol? [175] o o 107 multiple registrations? Subclause 3.1 n/a c101 108 the SIP P-Refused-URI-List private-header? [183] o c102 109 request authorization through dialog Identification in the session initiation protocol? [184] o o 110 indication of features supported by proxy? [190] o c104 111 registration of bulk number contacts? [191] o c105 112 media control channel framework? [146] n/a n/a 113 S-CSCF restoration procedures? Subclause 4.14 n/a n/a 114 SIP overload control? [198] o o 114A feedback control? [199] c106 c106 114B distribution of load filters? [201] n/a n/a 115 handling of a 380 (Alternative service) response? Subclause 5.2.10 n/a n/a 116 indication of adjacent network in the Via "received-realm" header field parameter? [208] o c107 117 PSAP callback indicator? [209] o c108 118 SIP URI parameter to indicate traffic leg? [225] o c109 119 PCF or PCRF based P-CSCF restoration? Subclause 4.14.2 n/a c110 120 UDM/HSS or HSS based P-CSCF restoration? Subclause 4.14.2 n/a c112 121 the Relayed-Charge header field extension? Subclause 7.2.12 n/a c114 122 resource sharing? Subclause 4.15 n/a c115 123 the Cellular-Network-Info header extension? Subclause 7.2.15 n/a c116 124 the Priority-Share header field extension? Subclause 7.2.16 n/a c127 125 the Response-Source header field extension? Subclause 7.2.17 n/a o 126 authenticated identity management in the Session Initiation Protocol? [252] o c128 127 a SIP response code for unwanted calls extension? [254] o o 128 the Attestation-Info header field extension? Subclause 7.2.18 n/a o 129 the Origination-Id header field extension? Subclause 7.2.19 n/a o 130 Dynamic services interactions? Subclause 4.18 n/a c128 131 the Additional-Identity header field extension? Subclause 7.2.20 n/a o 132 RLOS? Subclause 4.19 n/a c129 133 the Priority-Verstat header field extension? Subclause 7.2.21 n/a c82 c1: IF A.162/5 THEN o ELSE n/a - - stateful proxy behaviour. c2: IF A.3/2 OR A.3/9A OR A.3/4 OR A.3/13A OR A.3A/88 THEN m ELSE o - - P-CSCF, IBCF (THIG), S-CSCF, ISC gateway function (THIG), ATCF (proxy). c3: IF (A.162/7 AND NOT A.162/8) OR (NOT A.162/7 AND A.162/8) THEN m ELSE IF A.162/14 THEN o ELSE n/a - - TLS interworking with non-TLS else proxy insertion. c4: IF A.162/23 THEN m ELSE o - - integration of resource management and SIP. c5: IF A.162/30 THEN o ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c6: IF A.3/2 OR A.3/9A OR A.3A/88 THEN m ELSE n/a - - P-CSCF, IBCF (THIG), ATFC (proxy). c7: IF A.3/2 AND (A.3D/1 OR A.3D/4) THEN m ELSE n/a - - P-CSCF and (IMS AKA plus IPsec ESP or SIP digest with TLS). c9: IF (A.3/2 OR A.3/4 OR A.3/9A OR A.3/13A) AND A.162/30 THEN m ELSE IF A.3/7C AND A.162/30 THEN o ELSE n/a - - P-CSCF or S-CSCF or IBCF (THIG) or ISC gateway function (THIG) or AS acting as proxy and extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks (NOTE 1). c10: IF A.162/31 THEN o.2 ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c11: IF A.162/31B THEN o ELSE x - - application of privacy based on the received Privacy header. c12: IF A.162/31 AND A.3/4 THEN m ELSE IF A.3/11 THEN o ELSE n/a - - S-CSCF, E-CSCF. c13: IF A.162/31 AND (A.3/2 OR A.3/3 OR A.3/7C OR A.3/9A OR A.3/13A OR A.3A/88) THEN m ELSE n/a - - P-CSCF, I-CSCF, AS acting as a SIP proxy or IBCF (THIG), ISC gateway function (THIG), ATCF (proxy). c14: IF A.162/35 THEN o.3 ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP). c15: IF A.162/35 AND (A.3/2 OR A.3/3 OR A.3/9A OR A.3/13A) THEN m ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and P-CSCF or I-CSCF or IBCF (THIG) or ISC gateway function (THIG). c16: IF A.162/35 AND (A.3/2 OR A.3/3 OR A.3/4 OR A.3/9A OR A.3/13A) THEN m ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and P-CSCF or I-CSCF or S-CSCF or IBCF (THIG) or ISC gateway function (THIG). c17: IF A.162/35 AND (A.3/2 OR A.3/3 OR A.3/9A OR A.3/13A) THEN m ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and P-CSCF or I-CSCF or IBCF (THIG) or ISC gateway function (THIG). c18: IF A.162/38 THEN o ELSE n/a - - the P-Visited-Network-ID header extension. c19: IF A.162/35 AND (A.3/2 OR A.3.3 OR A.3/4 OR A.3/7 THEN m ELSE n/a - - private header extensions to the session initiation protocol for the 3rd-Generation Partnership Project (3GPP) and P-CSCF, I-CSCF, S-CSCF, AS acting as a proxy. c20: IF A.162/41 THEN o ELSE n/a - - the P-Access-Network-Info header extension. c21: IF A.162/41 AND A.3/2 THEN m ELSE n/a - - the P-Access-Network-Info header extension and P-CSCF. c22: IF A.162/41 AND A.3/4 THEN m ELSE n/a - - the P-Access-Network-Info header extension and S-CSCF. c23: IF A.162/45 THEN o ELSE n/a - - the P-Charging-Vector header extension. c24: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c25: IF A.162/44 THEN o ELSE n/a - - the P-Charging-Function-Addresses header extension. c26: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function Addresses header extension. c27: IF A.3/2 OR A.3/4 THEN m ELSE x - - P-CSCF or S-CSCF. c28: IF A.3/2 OR A.3/3 OR A.3/4 THEN m ELSE o.8 - - P-CSCF or I-CSCF or S-CSCF. c29: IF A.3/2 OR A.3/4 THEN n/a ELSE IF A.3/3 THEN o ELSE o.8 - - P-CSCF or S-CSCF or I-CSCF. c30: IF A.3/2 o ELSE i - - P-CSCF. c31: IF A.3/4 THEN m ELSE x - - S-CSCF. c32: IF A.3/4 THEN m ELSE o.4 - - S-CSCF. c33: IF A.162/50A OR A.162/50B OR A.162/50C OR A.162/50D OR A.162/50E OR A.162/50F THEN m ELSE n/a - - support of any directives within caller preferences for the session initiation protocol. c34: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c35: IF A.3/2 OR A.3/11 THEN m ELSE IF A.3/7C OR A.3/9 OR A.3/13A THEN o ELSE n/a - - P-CSCF, E-CSCF, AS acting as proxy, IBCF, ISC gateway function (THIG). c36: IF A.3/4 THEN m ELSE n/a - - S-CSCF. c38: IF A.162/66 THEN o ELSE n/a - - the SIP P-Profile-Key private header. c39: IF A.162/66 AND (A.3/3 OR A.3/9A) THEN m ELSE n/a - - the SIP P-Profile-Key private header, I-CSCF or IBCF (THIG). c40: IF A.162/66 AND A.3/4 THEN m ELSE n/a - - the SIP P-Profile-Key private header, S-CSCF. c41: IF A.3/3 OR A.3/4 OR A.3/9A THEN o ELSE n/a - - I-CSCF or S-CSCF or IBCF (THIG). c42: IF A.162/107 THEN m ELSE n/a - - multiple registrations. c44: IF A.162/70 THEN o.5 ELSE n/a - - SIP location conveyance. c45: IF A.3/11 THEN m ELSE IF A.162/70 AND A.3/7C THEN o.6 ELSE n/a - - E-CSCF, SIP location conveyance, AS acting as a SIP proxy. c46: IF A.162/70 AND A.3/2 OR A.3/3 OR A.3/5 OR A.3/10 OR A.3A/88 THEN m ELSE IF A.162/70 AND A.3/7C THEN o.6 ELSE n/a - - SIP location conveyance, P-CSCF, I-CSCF, S-CSCF, BGCF, additional routeing functionality, ATCF (proxy). c47: IF A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C THEN o ELSE n/a - - I-CSCF, S-CSCF, BGCF, AS acting as a SIP proxy. c48: IF A.162/77 THEN m ELSE n/a - - number portability parameters for the 'tel' URI. c50: IF A.162/77 THEN m ELSE n/a - - number portability parameters for the 'tel' URI. c51: IF A.3/2 THEN m ELSE o - - P-CSCF. c52: IF A.162/6 THEN m ELSE o - - forking of initial requests. c53: IF A.3/4 THEN m ELSE n/a - - S-CSCF. c54: IF A.3/3 OR A.3/4 OR A.3/7 OR A.3/2 OR A.3/9A OR A.3/13A THEN m ELSE n/a - - I-CSCF, S-CSCF, BGCF, P-CSCF. IBCF (THIG), ISC gateway function (THIG). c55: IF A.162/84 THEN o ELSE n/a - - SIP extension for the identification of services. c56: IF A.3/4 AND A.162/84 THEN m ELSE n/a - - S-CSCF and SIP extension for the identification of services. c60: IF A.3/2 OR A.3/3 OR A.3/4 THEN o ELSE n/a - - P-CSCF, I-CSCF, S-CSCF. c78: IF A.3/2 OR A.3/4 OR A.3/9 OR A.162/79 OR A.162/3 THEN m ELSE o - - P-CSCF, S-CSCF, IBCF, extending the session initiation protocol Reason header for preemption events, initiate session release. c79: IF A.162/80 THEN o ELSE n/a - - communications resource priority for the session initiation protocol. c80: IF A.3/2 OR A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/13A THEN o ELSE n/a - - P-CSCF, I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, ISC gateway function (THIG). c82: IF A.162/80 THEN o ELSE n/a - - communications resource priority for the session initiation protocol. c84: A.3/2 OR A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/11 OR A.3/13A THEN o ELSE n/a - - P-CSCF, I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). c85: IF A.3/2 OR A.3/3 OR A.3/4 THEN o ELSE x - - P-CSCF, I-CSCF, S-CSCF. c88: IF A.3/2 OR A.3/4 OR A.3/7 OR A.3/7C OR A.3/9C OR A.3/11 OR A.3/13C OR A.3A/88 THEN m ELSE o - - P-CSCF, S-CSCF, AS, AS acting as a SIP proxy, IBCF (Screening of SIP signalling), E-CSCF, ISC gateway function (Screening of SIP signalling), ATCF (proxy). c89: IF A.162/19F THEN m ELSE n/a - - proxy reading the contents of a body or including a body in a request or response. c90: IF A.3/4 THEN m ELSE i - - S-CSCF. c91: IF A.3/4 THEN o ELSE n/a - - S-CSCF. c92: IF A.162/92 THEN o ELSE n/a - - requesting answering modes for SIP. c94: IF A.3/11 THEN m ELSE o - - E-CSCF. c95: IF A.3/3 OR A.3/4 OR A.3/7C THEN o ELSE n/a - - I-CSCF, S-CSCF, AS acting as a SIP proxy. c96: IF A.3/2 OR A.3/11 OR A.3A/88 THEN m ELSE n/a - - P-CSCF, E-CSCF, ATCF (proxy). c99: IF A.3/2A AND (A.3D/30 OR A.3D/20A OR A.3D/20B OR A.3D/20C OR A.3D/31) THEN m ELSE n/a - - P-CSCF (IMS-ALG) and end-to-access-edge media security using SDES, end-to-access-edge media security for MSRP using TLS and certificate fingerprints, end-to-access-edge media security for BFCP using TLS and certificate fingerprints, end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints, end-to-access-edge media security for RTP media using DTLS-SRTP and certificate fingerprints. c100: IF A.4/22 THEN o ELSE n/a - - the REFER method. c101: IF A.3/2 OR A.3/4 THEN m ELSE n/a - - P-CSCF, S-CSCF. c102: IF A.3/9B THEN m ELSE IF A.3/7A OR A.3/7B OR A.3/7D THEN o ELSE n/a - - IBCF (IMS-ALG), AS acting as terminating UA, AS acting as originating UA, AS performing 3rd party call control. c103: IF A.3A/88 THEN m ELSE n/a - - ATCF (proxy). c104: IF A.3/2 OR A.3A/50A OR A.3A/83 OR A.3A/88 THEN m ELSE o - - P-CSCF, Multimedia telephony application server, SCC application server, ATCF (proxy). c105: IF A.3/2 OR A.3/3 OR A.3/9 THEN o ELSE n/a - - P-CSCF, I-CSCF, IBCF. c106: IF A.162/114 THEN o.9 ELSE n/a - - SIP overload control. c107: IF A.162/115 THEN o.9 ELSE n/a - - indication of adjacent network in the Via "received-realm" header field parameter. c108: IF A.3/2 OR A.3/3 OR A.3/4 OR A.3/7 OR A.3/9 THEN o ELSE n/a - - P-CSCF, I-CSCF, S-CSCF, AS, IBCF. c109: IF A.3/2 OR A.3/4 OR A.3/5 OR A.3/9 OR A.3/10 OR A.3A/83 OR A.3A/88 OR A.3/3 THEN o ELSE n/a - - P-CSCF, S-CSCF, BGCF, IBCF, Additional routeing functionality, SCC application server, ATCF (proxy), I-CSCF. c110: IF A.3/2 OR A.3/4 OR A.3/9 THEN o ELSE n/a - - P-CSCF, S-CSCF, IBCF. c111: IF A.162/59 THEN o ELSE n/a - - session initiation protocol URIs for applications such as voicemail and interactive voice response (NOTE 3). c112: IF A.3/2 OR A.3/4 OR A.3/9 THEN o ELSE n/a - - P-CSCF, S-CSCF, IBCF. c113: IF A.162/22 THEN m ELSE n/a - - the REFER method. c114: IF A.3/4 OR A.3/7 OR A.3A/102 THEN o ELSE n/a.-.-.S-CSCF, AS, transit function. c115: IF A.3/2 OR A.3/7C OR A.3/9 THEN o ELSE n/a - - P-CSCF, AS acting as a SIP proxy, IBCF. c116: IF A.3/2 OR A.3.3 OR A.3/4 OR A.3/7C OR A.3/9 OR A.3/11B OR A.3A/88 OR A.3/5 THEN m ELSE n/a - - P-CSCF, I-CSCF, S-CSCF, AS acting as a proxy, IBCF, E-CSCF acting as a SIP Proxy, ATCF (proxy), BGCF. c126: IF A.162/88 THEN o ELSE n/a - - the SIP P-Served-User private header for the 3GPP IM CN subsystem. c127: IF A.3/2 OR A.3/7C OR A.3/9 THEN o ELSE n/a - - P-CSCF, AS acting as a SIP proxy, IBCF. c128: IF A.3/7 OR A.3/9 THEN o ELSE n/a - - AS, IBCF. c129: IF A.3/2 OR A.3/4 THEN o ELSE n/a - - P-CSCF, S-CSCF. c130: IF A.3/4 OR A.3/7C OR A.3/9 THEN o ELSE n/a - - S-CSCF, AS acting as a SIP proxy, IBCF. c131: IF A.162/48C AND (A.3/4 OR A.3/7C OR A.3/9) THEN o ELSE n/a - - Multiple SIP Reason Header Field Values (carrying STIR codes in Reason header fields in SIP responses), S-CSCF, AS acting as a SIP proxy, IBCF. o.1: It is mandatory to support at least one of these items. o.2: It is mandatory to support at least one of these items. o.3: It is mandatory to support at least one of these items. o.4 At least one of these capabilities is supported. o.5: It is mandatory to support exactly one of these items. o.6: It is mandatory to support exactly one of these items. o.7: It is mandatory to support at least one of these items. o.8 It is mandatory to support at least one of these items. o.9: At least one of these capabilities is supported. NOTE 1: An AS acting as a proxy may be outside the trust domain, and therefore not able to support the capability for that reason; in this case it is perfectly reasonable for the header to be passed on transparently, as specified in the PDU parts of the profile. NOTE 2: Not applicable over Gm reference point (UE – P-CSCF). NOTE 3: AS performing a service number translation (e.g. Freephone) A.2.2.3 PDUs Table A.163: Supported methods Item PDU Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 ACK request [26] 13 m m [26] 13 m m 2 BYE request [26] 16 m m [26] 16 m m 3 BYE response [26] 16 m m [26] 16 m m 4 CANCEL request [26] 16.10 m m [26] 16.10 m m 5 CANCEL response [26] 16.10 m m [26] 16.10 m m 6 INFO request [25] 4.2 c2 c2 [25] 4.2 c2 c2 7 INFO response [25] 4.2 c2 c2 [25] 4.2 c2 c2 8 INVITE request [26] 16 m m [26] 16 m m 9 INVITE response [26] 16 m m [26] 16 m m 9A MESSAGE request [50] 4 c5 c5 [50] 7 c5 c5 9B MESSAGE response [50] 4 c5 c5 [50] 7 c5 c5 10 NOTIFY request [28] 8.1.2 c3 c3 [28] 8.1.2 c3 c3 11 NOTIFY response [28] 8.1.2 c3 c3 [28] 8.1.2 c3 c3 12 OPTIONS request [26] 16 m m [26] 16 m m 13 OPTIONS response [26] 16 m m [26] 16 m m 14 PRACK request [27] 6 c6 c6 [27] 6 c6 c6 15 PRACK response [27] 6 c6 c6 [27] 6 c6 c6 15A PUBLISH request [70] 11.1.1 c20 c20 [70] 11.1.1 c20 c20 15B PUBLISH response [70] 11.1.1 c20 c20 [70] 11.1.1 c20 c20 16 REFER request [36] 3 c1 c1 [36] 3 c1 c1 17 REFER response [36] 3 c1 c1 [36] 3 c1 c1 18 REGISTER request [26] 16 m m [26] 16 m m 19 REGISTER response [26] 16 m m [26] 16 m m 20 SUBSCRIBE request [28] 8.1.1 c3 c3 [28] 8.1.1 c3 c3 21 SUBSCRIBE response [28] 8.1.1 c3 c3 [28] 8.1.1 c3 c3 22 UPDATE request [29] 7 c4 c4 [29] 7 c4 c4 23 UPDATE response [29] 7 c4 c4 [29] 7 c4 c4 c1: IF A.162/22 THEN m ELSE n/a - - the REFER method. c2: IF A.162/20 OR A.162/20A THEN m ELSE n/a - - SIP INFO method and package framework, legacy INFO usage. c3: IF A.162/27 THEN m ELSE n/a - - SIP specific event notification. c4: IF A.162/24 THEN m ELSE n/a - - the SIP UPDATE method. c5: IF A.162/33 THEN m ELSE n/a - - the SIP MESSAGE method. c6: IF A.162/21 THEN m ELSE n/a - - reliability of provisional responses. c20: IF A.4/51 THEN m ELSE n/a A.2.2.4 PDU parameters A.2.2.4.1 Status-codes Table A.164: Supported-status codes Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 100 (Trying) [26] 21.1.1 c1 c1 [26] 21.1.1 c2 c2 101 1xx response [26] 21.1 p21 p21 [26] 21.1 p21 p21 101A 18x response [26] 21.1 p21 p21 [26] 21.1 p21 p21 2 180 (Ringing) [26] 21.1.2 c3 c3 [26] 21.1.2 c3 c3 3 181 (Call Is Being Forwarded) [26] 21.1.3 c3 c3 [26] 21.1.3 c3 c3 4 182 (Queued) [26] 21.1.4 c3 c3 [26] 21.1.4 c3 c3 5 183 (Session Progress) [26] 21.1.5 c3 c3 [26] 21.1.5 c3 c3 5A 199 (Early Dialog Terminated) [142] 11.1 c32 c32 [142] 11.1 c32 c32 102 2xx response [26] 21.2 p22 p22 [26] 21.1 p22 p22 6 200 (OK) [26] 21.2.1 m m [26] 21.2.1 i m 7 202 (Accepted) [28] 8.3.1 c34 c34 [28] 8.3.1 c34 c34 103 3xx response [26] 21.3 p23 p23 [26] 21.1 p23 p23 8 300 (Multiple Choices) [26] 21.3.1 m m [26] 21.3.1 i i 9 301 (Moved Permanently) [26] 21.3.2 m m [26] 21.3.2 i i 10 302 (Moved Temporarily) [26] 21.3.3 m m [26] 21.3.3 i i 11 305 (Use Proxy) [26] 21.3.4 m m [26] 21.3.4 i i 12 380 (Alternative Service) [26] 21.3.5 m m [26] 21.3.5 i i 104 4xx response [26] 21.4 p24 p24 [26] 21.4 p24 p24 13 400 (Bad Request) [26] 21.4.1 m m [26] 21.4.1 i i 14 401 (Unauthorized) [26] 21.4.2 m m [26] 21.4.2 i c10 15 402 (Payment Required) [26] 21.4.3 n/a n/a [26] 21.4.3 n/a n/a 16 403 (Forbidden) [26] 21.4.4 m m [26] 21.4.4 i i 17 404 (Not Found) [26] 21.4.5 m m [26] 21.4.5 i i 18 405 (Method Not Allowed) [26] 21.4.6 m m [26] 21.4.6 i i 19 406 (Not Acceptable) [26] 21.4.7 m m [26] 21.4.7 i i 20 407 (Proxy Authentication Required) [26] 21.4.8 m m [26] 21.4.8 i i 21 408 (Request Timeout) [26] 21.4.9 c3 c3 [26] 21.4.9 i i 22 410 (Gone) [26] 21.4.10 m m [26] 21.4.10 i i 22A 412 (Conditional Request Failed) [70] 11.2.1 c20 c20 [70] 11.2.1 c19 c19 23 413 (Request Entity Too Large) [26] 21.4.11 m m [26] 21.4.11 i i 24 414 (Request-URI Too Large) [26] 21.4.12 m m [26] 21.4.12 i i 25 415 (Unsupported Media Type) [26] 21.4.13 m m [26] 21.4.13 i i 26 416 (Unsupported URI Scheme) [26] 21.4.14 m m [26] 21.4.14 i i 26A 417 (Unknown Resource Priority) [116] 4.6.2 c25 c25 [116] 4.6.2 c25 c25 27 420 (Bad Extension) [26] 21.4.15 m m [26] 21.4.15 i i 28 421 (Extension Required) [26] 21.4.16 m m [26] 21.4.16 i i 28A 422 (Session Interval Too Small) [58] 6 c8 c8 [58] 6 c8 c8 29 423 (Interval Too Brief) [26] 21.4.17 c5 c5 [26] 21.4.17 c6 c6 29A 424 (Bad Location Information) [89] 4.2 c23 c23 [89] 4.2 c24 c24 29AA 428 Use Identity Header [252] 6.2.2 m m [252] 6.2.2 c35 c35 29B 429 (Provide Referrer Identity) [59] 5 c9 c9 [59] 5 c9 c9 29C 430 (Flow Failed) [92] 11 o c21 [92] 11 m c22 29D 433 (Anonymity Disallowed) [67] 4 c14 c14 [67] 4 c14 c14 29DA 436 Bad Identity Info [252] 6.2.2 m m [252] 6.2.2 c35 c35 29DB 437 Unsupported Credential [252] 6.2.2 m m [252] 6.2.2 c35 c35 29DC 438 Invalid Identity Header [252] 6.2.2 m m [252] 6.2.2 c35 c35 29E 439 (First Hop Lacks Outbound Support) [92] 11 c28 c28 [92] 11 c29 c29 29F 440 (Max Breadth Exceeded) [117] 5 c30 c30 [117] 5 c31 c31 29G 469 (Bad INFO Package) [25] 4.2 c33 c33 [25] 4.2 c33 c33 29H 470 (Consent Needed) [125] 5.9.2 c26 c26 [125] 5.9.2 c27 c27 30 480 (Temporarily not available) [26] 21.4.18 m m [26] 21.4.18 i i 31 481 (Call /Transaction Does Not Exist) [26] 21.4.19 m m [26] 21.4.19 i i 32 482 (Loop Detected) [26] 21.4.20 m m [26] 21.4.20 i i 33 483 (Too Many Hops) [26] 21.4.21 m m [26] 21.4.21 i i 34 484 (Address Incomplete) [26] 21.4.22 m m [26] 21.4.22 i i 35 485 (Ambiguous) [26] 21.4.23 m m [26] 21.4.23 i i 36 486 (Busy Here) [26] 21.4.24 m m [26] 21.4.24 i i 37 487 (Request Terminated) [26] 21.4.25 m m [26] 21.4.25 i i 38 488 (Not Acceptable Here) [26] 21.4.26 m m [26] 21.4.26 i i 39 489 (Bad Event) [28] 8.3.2 c4 c4 [28] 8.3.2 c4 c4 40 491 (Request Pending) [26] 21.4.27 m m [26] 21.4.27 i i 41 493 (Undecipherable) [26] 21.4.28 m m [26] 21.4.28 i i 41A 494 (Security Agreement Required) [48] 2 c7 c7 [48] 2 n/a n/a 105 5xx response [26] 21.5 p25 p25 [26] 21.5 p25 p25 42 500 (Internal Server Error) [26] 21.5.1 m m [26] 21.5.1 i i 43 501 (Not Implemented) [26] 21.5.2 m m [26] 21.5.2 i i 44 502 (Bad Gateway) [26] 21.5.3 m m [26] 21.5.3 i i 45 503 (Service Unavailable) [26] 21.5.4 m m [26] 21.5.4 i i 46 504 (Server Time-out) [26] 21.5.5 m m [26] 21.5.5 i i 47 505 (Version not supported) [26] 21.5.6 m m [26] 21.5.6 i i 48 513 (Message Too Large) [26] 21.5.7 m m [26] 21.5.7 i i 49 580 (Precondition Failure) [30] 8 m m [30] 8 i i 106 6xx response [26] 21.6 p26 p26 [26] 21.6 p26 p26 50 600 (Busy Everywhere) [26] 21.6.1 m m [26] 21.6.1 i i 51 603 (Decline) [26] 21.6.2 m m [26] 21.6.2 i i 52 604 (Does Not Exist Anywhere) [26] 21.6.3 m m [26] 21.6.3 i i 53 606 (Not Acceptable) [26] 21.6.4 m m [26] 21.6.4 i i 54 607 (Unwanted) [254] m m [254] i i c1: IF A.163/3 OR A.163/9 OR A.163/9B OR A.163/11 OR A.163/13 OR A.163/15 OR A.163/15B OR A.163/17 OR A.163/19 OR A.163/21 OR A.163/23 AND A.162/5 THEN m ELSE n/a - - BYE response or INVITE response or MESSAGE response or NOTIFY response or OPTIONS response or PRACK response or PUBLISH response or REFER response or REGISTER response or SUBSCRIBE response or UPDATE response, stateful proxy. c2: IF A.163/3 OR A.163/9 OR A.163/9B OR A.163/11 OR A.163/13 OR A.163/15 OR A.163/15B OR A.163/17 OR A.163/19 OR A.163/21 OR A.163/23 THEN (IF A.162/5 THEN m ELSE i) ELSE n/a - - BYE response or INVITE response or MESSAGE response or NOTIFY response or OPTIONS response or PRACK response or PUBLISH response or REFER response or REGISTER response or SUBSCRIBE response or UPDATE response, stateful proxy. c3: IF A.163/9 THEN m ELSE n/a - - INVITE response. c4: IF A.162/27 THEN m ELSE n/a - - SIP specific event notification. c5: IF A.163/19 OR A.163/21 THEN m ELSE n/a - - REGISTER response or SUBSCRIBE response. c6: IF A.163/19 OR A.163/21 THEN i ELSE n/a - - REGISTER response or SUBSCRIBE response. c7: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. c8: IF A.162/52 THEN m ELSE n/a - - the SIP session timer. c9: IF A.162/53 AND A.163/17 THEN m ELSE n/a - - the SIP Referred-By mechanism and REFER response. c10: IF A.3/2 THEN m ELSE i - - P-CSCF. c14: IF A.162/58 THEN m ELSE n/a - - rejecting anonymous requests in the session initiation protocol. c19: IF A.162/51 THEN i ELSE n/a - - an event state publication extension to the session initiation protocol. c20: IF A.162/51 THEN m ELSE n/a - - an event state publication extension to the session initiation protocol. c21: IF A.4/57 AND A.3/2 THEN o ELSE n/a - - managing client initiated connections in SIP, P-CSCF. c22: IF A.4/57 AND A.3/4 THEN m ELSE i - - managing client initiated connections in SIP, S-CSCF. c23: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c24: IF A.162/70 THEN i ELSE n/a - - SIP location conveyance. c25: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c26: IF A.162/85 THEN m ELSE n/a - - a framework for consent-based communications in SIP. c27: IF A.162/85 THEN i ELSE n/a - - a framework for consent-based communications in SIP. c28: IF A.162/57 AND THEN m ELSE n/a - - managing client initiated connections in SIP. c29: IF A.162/57 AND THEN i ELSE n/a - - managing client initiated connections in SIP. c30: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c31: IF A.162/81 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c32: IF A.162/91 AND A.163/9 THEN m ELSE n/a - - INVITE response and 199 (Early Dialog Terminated) response. c33 IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c34: IF A.162/27 OR A.163/9B OR A.163/17 THEN m ELSE n/a - - SIP specific event notification or MESSAGE response or REFER response. c35 IF A.162/126 THEN m ELSE i - authenticated identity management in the Session Initiation Protocol p21: A.164/2 OR A.164/3 OR A.164/4 OR A.164/5 OR A.164/5A - - 1xx response p22: A.164/6 OR A.164/7 - - 2xx response p23: A.164/8 OR A.164/9 OR A.164/10 OR A.164/11 OR A.164/12 - - 3xx response p24: A.164/13 OR A.164/14 OR A.164/15 OR A.164/16 OR A.164/17 OR A.164/18 OR A.164/19 OR A.164/20 OR A.164/21 OR A.164/22 OR A.164/22A OR A.164/23 OR A.164/24 OR A.164/25 OR A.164/26 OR A.164/26A OR A.164/27 OR A.164/28 OR A.164/28A OR A.164/29 OR A.164/29A OR A.164/29B OR A.164/29C OR A.164/29D OR A.164/29E OR A.164/29F OR A.164/29G OR A.164/29H OR A.164/30 OR A.164/31 OR A.164/32 OR A.164/33 OR A.164/34 OR A.164/35 OR A.164/36 OR A.164/436 OR A.164/38 OR A.164/39 OR A.164/40 OR A.164/41 OR A.164/41A. - - 4xx response p25: A.164/42 OR A.164/43 OR A.164/44 OR A.164/45 OR A.164/46 OR A.164/47 OR A.164/48 OR A.164/49 - - 5xx response p26: A.164/50 OR A.164/51 OR A.164/52 OR A.164/53 - - 6xx response A.2.2.4.2 ACK method Prerequisite A.163/1 - - ACK request Table A.165: Supported header fields within the ACK request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Contact [56B] 9.2 c10 c10 [56B] 9.2 c11 c11 2 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 3 Authorization [26] 20.7 m m [26] 20.7 i i 4 Call-ID [26] 20.8 m m [26] 20.8 m m 5 Cellular-Network-Info 7.2.15 n/a c27 7.2.15 n/a c28 6 Content-Disposition [26] 20.11 m m [26] 20.11 i i 7 Content-Encoding [26] 20.12 m m [26] 20.12 i i 8 Content-Language [26] 20.13 m m [26] 20.13 i i 9 Content-Length [26] 20.14 m m [26] 20.14 m m 10 Content-Type [26] 20.15 m m [26] 20.15 i c3 11 CSeq [26] 20.16 m m [26] 20.16 m m 12 Date [26] 20.17 m m [26] 20.17 c2 c2 13 From [26] 20.20 m m [26] 20.20 m m 13A Max-Breadth [117] 5.8 c15 c15 [117] 5.8 c16 c16 14 Max-Forwards [26] 20.22 m m [26] 20.22 m m 15 MIME-Version [26] 20.24 m m [26] 20.24 i c3 15A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c20 c20 [52] 4.4, [52A] 4, [234] 2 c21 c21 15BA Priority-Share Subclause 7.2.16 n/a c29 Subclause 7.2.16 n/a c29 15C Privacy [33] 4.2 c6 c6 [33] 4.2 c7 c7 15D P-Charging-Vector [52] 4.6, [52A] 4 c22 c22 [52] 4.6, [52A] 4 c23 c23 16 Proxy-Authorization [26] 20.28 m m [26] 20.28 c4 c4 17 Proxy-Require [26] 20.29 m m [26] 20.29 m m 17A Reason [34A] 2 c8 c8 [34A] 2 c9 c9 17B Record-Route [26] 20.30 m m [26] 20.30 c26 c26 17C Recv-Info [25] 5.2.3 c17 c17 [25] 5.2.3 c18 c18 17D Reject-Contact [56B] 9.2 c10 c10 [56B] 9.2 c11 c11 17E Relayed-Charge 7.2.12 n/a c24 7.2.12 n/a c24 17F Request-Disposition [56B] 9.1 c10 c10 [56B] 9.1 c11 c11 18 Require [26] 20.32 m m [26] 20.32 c5 c5 18A Resource-Priority [116] 3.1 c12 c12 [116] 3.1 c12 c47 18B Resource-Share Subclause 4.15 n/a c25 Subclause 4.15 n/a c25 19 Route [26] 20.34 m m [26] 20.34 m m 19A Session-ID [162] c19 c19 [162] c19 c19 20 Timestamp [26] 20.38 m m [26] 20.38 i i 21 To [26] 20.39 m m [26] 20.39 m m 22 User-Agent [26] 20.41 m m [26] 20.41 i i 23 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.3/2 OR A.3/4 THEN m ELSE i - - P-CSCF or S-CSCF. c4: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c8: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c9: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c10: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c11: IF A.162/50 THEN i ELSE n/a - - caller preferences for the session initiation protocol. c12: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c15: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c16: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c17: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c18: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c19: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c20: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c21: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c22: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c23: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c24: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c25: IF A.162/122 THEN o ELSE n/a - - resource sharing. c26: IF A.162/14 THEN o ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c27: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c28: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c29: IF A.162/124 THEN o ELSE n/a - - priority sharing. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/1 - - ACK request Table A.166: Supported message bodies within the ACK request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.3 BYE method Prerequisite A.163/2 - - BYE request Table A.167: Supported header fields within the BYE request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 1A Accept-Contact [56B] 9.2 c22 c22 [56B] 9.2 c23 c23 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i 3A Allow [26] 20.5 m m [26] 20.5 i i 4 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 5 Authorization [26] 20.7 m m [26] 20.7 i i 6 Call-ID [26] 20.8 m m [26] 20.8 m m 6A Cellular-Network-Info 7.2.15 n/a c37 7.2.15 n/a c38 7 Content-Disposition [26] 20.11 m m [26] 20.11 i c3 8 Content-Encoding [26] 20.12 m m [26] 20.12 i c3 9 Content-Language [26] 20.13 m m [26] 20.13 i c3 10 Content-Length [26] 20.14 m m [26] 20.14 m m 11 Content-Type [26] 20.15 m m [26] 20.15 i c3 12 CSeq [26] 20.16 m m [26] 20.16 m m 13 Date [26] 20.17 m m [26] 20.17 c2 c2 14 From [26] 20.20 m m [26] 20.20 m m 14A Geolocation [89] 4.1 c26 c26 [89] 4.1 c27 c27 14B Geolocation-Routing [89] 4.1 c26 c26 [89] 4.1 c27 c27 14C Max-Breadth [117] 5.8 c33 c33 [117] 5.8 c34 c34 15 Max-Forwards [26] 20.22 m m [26] 20.22 m m 16 MIME-Version [26] 20.24 m m [26] 20.24 i c3 16A P-Access-Network-Info [52] 4.4, [234] 2 c13 c13 [52] 4.4, [234] 2 c14 c14 16B P-Asserted-Identity [34] 9.1 c9 c9 [34] 9.1 c10 c10 16C P-Charging-Function-Addresses [52] 4.5 c17 c17 [52] 4.5 c18 c18 16D P-Charging-Vector [52] 4.6 c15 c15 [52] 4.6 c16 c16 16F P-Preferred-Identity [34] 9.2 x x [34] 9.2 c8 n/a 16G Privacy [33] 4.2 c11 c11 [33] 4.2 c12 c12 17 Proxy-Authorization [26] 20.28 m m [26] 20.28 c4 c4 18 Proxy-Require [26] 20.29 m m [26] 20.29 m m 18A Reason [34A] 2 c20 c20 [34A] 2 c21 c21 19 Record-Route [26] 20.30 m m [26] 20.30 c7 c7 19A Referred-By [59] 3 c24 c24 [59] 3 c25 c25 19B Reject-Contact [56B] 9.2 c22 c22 [56B] 9.2 c23 c23 19C Relayed-Charge 7.2.12 n/a c36 7.2.12 n/a c36 19D Request-Disposition [56B] 9.1 c22 c22 [56B] 9.1 c23 c23 20 Require [26] 20.32 m m [26] 20.32 c5 c5 20A Resource-Priority [116] 3.1 c28 c28 [116] 3.1 c28 c28 21 Route [26] 20.34 m m [26] 20.34 m m 21A Security-Client [48] 2.3.1 x x [48] 2.3.1 c19 c19 21B Security-Verify [48] 2.3.1 x x [48] 2.3.1 c19 c19 21C Session-ID [162] c35 c35 [162] c35 c35 22 Supported [26] 20.37 m m [26] 20.37 c6 c6 23 Timestamp [26] 20.38 m m [26] 20.38 i i 24 To [26] 20.39 m m [26] 20.39 m m 25 User-Agent [26] 20.41 m m [26] 20.41 i i 25A User-to-User [126] 7 c29 c29 [126] 7 c30 c30 26 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.3/2 OR A.3/4 THEN m ELSE i - - P-CSCF or S-CSCF. c4: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c9: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c10: IF A.162/30A OR A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c11: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c12: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c13: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c16: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c17: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c18: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c19: IF A.162/47 OR A.162/47A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c20: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c21: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c22: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c23: IF A.162/50 THEN i ELSE n/a - - caller preferences for the session initiation protocol. c24: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c25: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c26: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c27: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c28: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c29: IF A.162/86 THEN m - - transporting user to user information for call centers using SIP. c30: IF A.162/86 THEN i - - transporting user to user information for call centers using SIP. c33: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c34: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c35: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c36: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c37: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c38: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/2 - - BYE request Table A.168: Supported message bodies within the BYE request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 XML Schema for PSTN [11B] n/a c1 [11B] n/a i 2 VoiceXML expr / namelist data [145] 4.2 m c2 [145] 4.2 m c2 3 application/vnd.3gpp.ussd [8W] n/a m [8W] n/a i c1: A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/11 OR A.3/13A THEN m ELSE n/a - - I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). c2: IF A.162/94 THEN m ELSE n/a - - SIP Interface to VoiceXML Media Services. Table A.169: Void Prerequisite A.163/3 - - BYE response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.169A: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/3 - - BYE response Table A.170: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Cellular-Network-Info 7.2.15 n/a c23 7.2.15 n/a c24 2 Content-Disposition [26] 20.11 m m [26] 20.11 i c2 3 Content-Encoding [26] 20.12 m m [26] 20.12 i c2 4 Content-Language [26] 20.13 m m [26] 20.13 i c2 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 i c2 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 m m [26] 20.17 c1 c1 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c15 c15 [89] 4.3 c16 c16 10 MIME-Version [26] 20.24 m m [26] 20.24 i c2 10A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c12 c12 [52] 4.4, [52A] 4, [234] 2 c13 c13 10B P-Asserted-Identity [34] 9.1 c4 c4 [34] 9.1 c5 c5 10C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c10 c10 [52] 4.5, [52A] 4 c11 c11 10D P-Charging-Vector [52] 4.6, [52A] 4 c8 c8 [52] 4.6, [52A] 4 c9 c9 10F P-Preferred-Identity [34] 9.2 x x [34] 9.2 c3 n/a 10G Privacy [33] 4.2 c6 c6 [33] 4.2 c7 c7 10H Relayed-Charge 7.2.12 n/a c22 7.2.12 n/a c22 10I Require [26] 20.32 m m [26] 20.32 c14 c14 10J Server [26] 20.35 m m [26] 20.35 i i 10K Session-ID [162] c21 c21 [162] c21 c21 11 Timestamp [26] 20.38 m m [26] 20.38 i i 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 m m [26] 20.41 i i 12B User-to-User [126] 7 c17 c17 [126] 7 c18 c18 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.3/2 OR A.3/4 THEN m ELSE i - - P-CSCF or S-CSCF. c3: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c4: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c5: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c6: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c8: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c10: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c12: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c13: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c15: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c16: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c17: IF A.162/86 THEN m - - transporting user to user information for call centers using SIP. c18: IF A.162/86 THEN i - - transporting user to user information for call centers using SIP. c21: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c22: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c23: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. Prerequisite A.163/3 - - BYE response Prerequisite: A.164/102 - - Additional for 2xx response Table A.171: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c4 c4 [116] 3.2 c4 c4 0B Allow-Events [28] 8.2.2 m m [28] 8.2.2 i c1 1 Authentication-Info [26] 20.6 m m [26] 20.6 i i 2 Record-Route [26] 20.30 m m [26] 20.30 c3 c3 5 Supported [26] 20.37 m m [26] 20.37 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c3: IF A.162/15 THEN o ELSE i - - the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.163/3 - - BYE response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.171A: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.163/3 - BYE response Prerequisite: A.164/103 OR A.164/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.172: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Contact [26] 20.10 m m [26] 20.10 c1 c1 c1: IF A.162/19E THEN m ELSE i - - deleting Contact headers. Prerequisite A.163/3 - - BYE response Prerequisite: A.164/14 - - Additional for 401 (Unauthorized) response Table A.173: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/3 - - BYE response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.174: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.175: Void Prerequisite A.163/3 - - BYE response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.176: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/3 - - BYE response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) response Table A.177: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/3 - - BYE response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.177A: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.163/3 - - BYE response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.178: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/3 - - BYE response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.178A: Supported header fields within the BYE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.179: Void Prerequisite A163/3 - - BYE response Prerequisite: A.164/6 - - Additional for 200 (OK) response Table A.180: Supported message bodies within the BYE response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 VoiceXML expr / namelist data [145] 4.2 o c1 [145] 4.2 o c1 c1: IF A.162/94 THEN o ELSE n/a - - SIP Interface to VoiceXML Media Services. A.2.2.4.4 CANCEL method Prerequisite A.163/4 - - CANCEL request Table A.181: Supported header fields within the CANCEL request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Contact [56B] 9.2 c10 c10 [56B] 9.2 c11 c11 5 Authorization [26] 20.7 m m [26] 20.7 i i 6 Call-ID [26] 20.8 m m [26] 20.8 m m 8 Content-Length [26] 20.14 m m [26] 20.14 m m 8A Content-Type [26] 20.15 c21 c21 [26] 20.15 o o 9 CSeq [26] 20.16 m m [26] 20.16 m m 10 Date [26] 20.17 m m [26] 20.17 c2 c2 11 From [26] 20.20 m m [26] 20.20 m m 11A Max-Breadth [117] 5.8 c15 c15 [117] 5.8 c16 c16 12 Max-Forwards [26] 20.22 m m [26] 20.22 m m 14 Privacy [33] 4.2 c3 c3 [33] 4.2 c4 c4 15 Reason [34A] 2 c8 c8 [34A] 2 c9 c9 16 Record-Route [26] 20.30 m m [26] 20.30 c7 c7 17 Reject-Contact [56B] 9.2 c10 c10 [56B] 9.2 c11 c11 17A Relayed-Charge 7.2.12 n/a c20 7.2.12 n/a c20 17B Request-Disposition [56B] 9.1 c10 c10 [56B] 9.1 c11 c11 17C Resource-Priority [116] 3.1 c12 c12 [116] 3.1 c12 c12 18 Route [26] 20.34 m m [26] 20.34 m m 18A Session-ID [162] c17 c17 [162] c17 c17 19 Supported [26] 20.37 m m [26] 20.37 c6 c6 20 Timestamp [26] 20.38 m m [26] 20.38 i i 21 To [26] 20.39 m m [26] 20.39 m m 22 User-Agent [26] 20.41 m m [26] 20.41 i i 23 Via [26] 20.42 m m [26] 20.42 m m c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c4: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c9: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c10: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c11: IF A.162/50 THEN i ELSE n/a - - caller preferences for the session initiation protocol. c12: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c15: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c16: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c17: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c20: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c21: IF A.162/23 OR A.182/1 THEN m ELSE o - - integration of resource management and SIP or XML schema for PSTN. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/4 - - CANCEL request Table A.182: Supported message bodies within the CANCEL request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 XML Schema for PSTN [11B] c1 [11B] i c1: A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/11 OR A.3/13A THEN m ELSE n/a - - I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). Prerequisite A.163/5 - - CANCEL response for all status-codes Table A.183: Supported header fields within the CANCEL response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 m m [26] 20.17 c1 c1 5 From [26] 20.20 m m [26] 20.20 m m 5C Privacy [33] 4.2 c2 c2 [33] 4.2 c3 c3 5D Relayed-Charge 7.2.12 n/a c9 7.2.12 n/a c9 5C Session-ID [162] c6 c6 [162] c6 c6 6 Timestamp [26] 20.38 m m [26] 20.38 i i 7 To [26] 20.39 m m [26] 20.39 m m 7A User-Agent [26] 20.41 o [26] 20.41 o 8 Via [26] 20.42 m m [26] 20.42 m m 9 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c3: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c6: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c9: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. Prerequisite A.163/5 - - CANCEL response Prerequisite: A.164/102 - - Additional for 2xx response Table A.184: Supported header fields within the CANCEL response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c4 c4 [116] 3.2 c4 c4 2 Record-Route [26] 20.30 m m [26] 20.30 c3 c3 4 Supported [26] 20.37 m m [26] 20.37 i i c3: IF A.162/15 THEN o ELSE i - - the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.163/5 - - CANCEL response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.184A: Supported header fields within the CANCEL response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Table A.185: Void Prerequisite A.163/5 - - CANCEL response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional 404 (Not Found), 413 (Request for Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.186: Supported header fields within the CANCEL response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Retry-After [26] 20.33 m m [26] 20.33 i i Prerequisite A.163/5 - - CANCEL response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.186A: Supported header fields within the CANCEL response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Table A.187: Void Table A.188: Void Prerequisite A.163/5 - - CANCEL response Table A.189: Supported message bodies within the CANCEL response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.5 Void A.2.2.4.6 INFO method Prerequisite A.163/6 - - INFO request Table A.190: Supported header fields within the INFO request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i 4 Allow [26] 20.5 m m [50] 10 i i 5 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 6 Authorization [26] 20.7 m m [26] 20.7 i i 7 Call-ID [26] 20.8 m m [26] 20.8 m m 7A Call-Info [26] 20.9 m m [26] 20.9 c3 c3 8 Cellular-Network-Info 7.2.15 n/a c54 7.2.15 n/a c55 9 Content-Disposition [26] 20.11 m m [26] 20.11 i i 10 Content-Encoding [26] 20.12 m m [26] 20.12 i i 11 Content-Language [26] 20.13 m m [26] 20.13 i i 12 Content-Length [26] 20.14 m m [26] 20.14 m m 13 Content-Type [26] 20.15 m m [26] 20.15 i i 14 CSeq [26] 20.16 m m [26] 20.16 m m 15 Date [26] 20.17 m m [26] 20.17 c2 c2 16 From [26] 20.20 m m [26] 20.20 m m 17 Geolocation [89] 4.1 c36 c36 [89] 4.1 c37 c37 17A Geolocation-Routing [89] 4.1 c36 c36 [89] 4.1 c37 c37 18 Info-Package [25] 7.2 c50 c50 [25] 7.2 c51 c51 19 Max-Breadth [117] 5.8 c48 c48 [117] 5.8 c49 c49 20 Max-Forwards [26] 20.22 m m [26] 20.22 m m 21 MIME-Version [26] 20.24 m m [26] 20.24 i i 22 P-Access-Network-Info [52] 4.4, [234] 2 c23 c23 [52] 4.4, [234] 2 c24 c24 23 P-Charging-Function-Addresses [52] 4.5 c21 c21 [52] 4.5 c22 c22 24 P-Charging-Vector [52] 4.6 c19 c19 [52] 4.6 c20 c20 26 Privacy [33] 4.2 c12 c12 [33] 4.2 c13 c13 27 Proxy-Authorization [26] 20.28 m m [26] 20.28 c8 c8 28 Proxy-Require [26] 20.29 m m [26] 20.29 m m 29 Reason [34A] 2 c26 c26 [34A] 2 c27 c27 30 Record-Route [26] 20.30 m m [26] 20.30 c7 c7 31 Referred-By [59] 3 c30 c30 [59] 3 c31 c31 32 Relayed-Charge 7.2.12 n/a c53 7.2.12 n/a c53 33 Request-Disposition [56B] 9.1 c28 c28 [56B] 9.1 c28 c28 34 Require [26] 20.32 m m [26] 20.32 c5 c5 35 Resource-Priority [116] 3.1 c38 c38 [116] 3.1 c38 c38 36 Route [26] 20.34 m m [26] 20.34 m m 37 Security-Client [48] 2.3.1 x x [48] 2.3.1 c25 c25 38 Security-Verify [48] 2.3.1 x x [48] 2.3.1 c25 c25 38A Session-ID [162] c52 c52 [162] c52 c52 39 Subject [26] 20.36 m m [26] 20.36 i i 40 Supported [26] 20.37 m m [26] 20.37 c6 c6 41 Timestamp [26] 20.38 m m [26] 20.38 i i 42 To [26] 20.39 m m [26] 20.39 m m 43 User-Agent [26] 20.41 m m [26] 20.41 i i 44 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c12: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c13: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c19: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c20: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c21: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c22: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c23: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c25: IF A.162/47 OR A.162/47A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c26: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c27: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c28: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c30: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c31: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c36: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c37: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c38: IF A.162/80A THEN m ELSE n/a - - inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c48: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c49: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c50: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c51: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c52: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c53: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c54: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c55: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/6 - - INFO request Table A.191: Supported message bodies within the INFO request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Info-Package [25] m m [25] i i Prerequisite A.163/7 - - INFO response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.192: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/7 - - INFO response for all remaining status-codes Table A.193: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Call-Info [26] 20.9 m m [26] 20.9 c3 c3 2A Cellular-Network-Info 7.2.15 n/a c23 7.2.15 n/a c24 3 Content-Disposition [26] 20.11 m m [26] 20.11 i i 4 Content-Encoding [26] 20.12 m m [26] 20.12 i i 5 Content-Language [26] 20.13 m m [26] 20.13 i i 6 Content-Length [26] 20.14 m m [26] 20.14 m m 7 Content-Type [26] 20.15 m m [26] 20.15 i i 8 CSeq [26] 20.16 m m [26] 20.16 m m 9 Date [26] 20.17 m m [26] 20.17 c1 c1 10 From [26] 20.20 m m [26] 20.20 m m 11 Geolocation-Error [89] 4.3 c17 c17 [89] 4.3 c18 c18 12 MIME-Version [26] 20.24 m m [26] 20.24 i i 13 Organization [26] 20.25 m m [26] 20.25 c2 c2 14 P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c13 c13 [52] 4.4, [52A] 4, [234] 2 c14 c14 15 P-Charging-Function-Addresses [52] 4.5, [52A] 4 c11 c11 [52] 4.5, [52A] 4 c12 c12 16 P-Charging-Vector [52] 4.6, [52A] 4 c9 c9 [52] 4.6, [52A] 4 c10 c10 18 Privacy [33] 4.2 c7 c7 [33] 4.2 c8 c8 18A Relayed-Charge 7.2.12 n/a c22 7.2.12 n/a c22 19 Require [26] 20.32 m m [26] 20.32 c15 c15 20 Server [26] 20.35 m m [26] 20.35 i i 20A Session-ID [162] c21 c21 [162] c21 c21 21 Timestamp [26] 20.38 i i [26] 20.38 i i 22 To [26] 20.39 m m [26] 20.39 m m 23 User-Agent [26] 20.41 m m [26] 20.41 i i 24 Via [26] 20.42 m m [26] 20.42 m m 25 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c3: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c7: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c9: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c11: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c13: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c17: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c18: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c21: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c22: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c23: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. Prerequisite A.163/7 - - INFO response Prerequisite: A.164/102 - - Additional for 2xx response Table A.194: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i 4 Accept-Resource-Priority [116] 3.2 c4 c4 [116] 3.2 c4 c4 5 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 6 Authentication-Info [26] 20.6 m m [26] 20.6 i i 8 Record-Route [26] 20.30 m m [26] 20.30 c5 c5 9 Supported [26] 20.37 m m [26] 20.37 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c4: IF A.162/80A THEN m ELSE n/a - - inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c5: IF A.162/15 THEN o ELSE i - - the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. Prerequisite A.163/7 - - INFO response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.195: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.163/7 - - INFO response Prerequisite: A.164/103 OR A.164/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.195A: Void Prerequisite A.163/7 - - INFO response Prerequisite: A.164/14 - - Additional for 401 (Unauthorized) response Table A.196: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/7 - - INFO response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.197: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.198: Void Prerequisite A.163/7 - - INFO response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) Table A.199: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/7 - - INFO response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.199A: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80A THEN m ELSE n/a - - inclusion of INFO, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. Prerequisite A.163/7 - - INFO response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.200: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/7 - - INFO response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.200A: Supported header fields within the INFO response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.201: Void Table A.202: Void Prerequisite A.163/7 - - INFO response Table A.203: Supported message bodies within the INFO response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.7 INVITE method Prerequisite A.163/8 - - INVITE request Table A.204: Supported header fields within the INVITE request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 1A Accept-Contact [56B] 9.2 c34 c34 [56B] 9.2 c34 c35 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i 3A Additional-Identity 7.2.20 n/a c85 7.2.20 n/a c85 4 Alert-Info [26] 20.4 c2 c2 [26] 20.4 c3 c3 5 Allow [26] 20.5 m m [26] 20.5 i i 6 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 7 Answer-Mode [158] c67 c67 [158] c68 c68 7A Attestation-Info 7.2.18 n/a c82 7.2.18 n/a c82 8 Authorization [26] 20.7 m m [26] 20.7 i i 9 Call-ID [26] 20.8 m m [26] 20.8 m m 10 Call-Info [26] 20.9 m m [26] 20.9 c12 c12 10A Cellular-Network-Info 7.2.15 n/a c78 7.2.15 n/a c79 11 Contact [26] 20.10 m m [26] 20.10 i i 12 Content-Disposition [26] 20.11 m m [26] 20.11 i c6 13 Content-Encoding [26] 20.12 m m [26] 20.12 i c6 14 Content-Language [26] 20.13 m m [26] 20.13 i c6 15 Content-Length [26] 20.14 m m [26] 20.14 m m 16 Content-Type [26] 20.15 m m [26] 20.15 i c6 17 CSeq [26] 20.16 m m [26] 20.16 m m 18 Date [26] 20.17 m m [26] 20.17 c4 c4 19 Expires [26] 20.19 m m [26] 20.19 i i 19A Feature-Caps [190] c73 c73 [190] c73 c73 20 From [26] 20.20 m m [26] 20.20 m m 20A Geolocation [89] 4.1 c47 c47 [89] 4.1 c48 c48 20B Geolocation-Routing [89] 4.1 c47 c47 [89] 4.1 c48 c48 20C History-Info [66] 4.1 c43 c43 [66] 4.1 c43 c43 20D Identity [252] 4 c81 c81 [252] 4 c81 c81 21 In-Reply-To [26] 20.21 m m [26] 20.21 i i 21A Join [61] 7.1 c41 c41 [61] 7.1 c42 c42 21B Max-Breadth [117] 5.8 c63 c63 [117] 5.8 c64 c64 22 Max-Forwards [26] 20.22 m m [26] 20.22 m m 23 MIME-Version [26] 20.24 m m [26] 20.24 i c6 23A Min-SE [58] 5 o o [58] 5 o o 24 Organization [26] 20.25 m m [26] 20.25 c5 c5 24AA Origination-Id 7.2.19 n/a c83 7.2.19 n/a c83 24A P-Access-Network-Info [52] 4.4, [234] 2 c28 c28 [52] 4.4, [234] 2 c29 c30 24B P-Asserted-Identity [34] 9.1 c15 c15 [34] 9.1 c16 c16 24C P-Asserted-Service [121] 4.1 c53 c53 [121] 4.1 c54 c54 24D P-Called-Party-ID [52] 4.2 c19 c19 [52] 4.2 c20 c21 24E P-Charging-Function-Addresses [52] 4.5 c26 c27 [52] 4.5 c26 c27 24F P-Charging-Vector [52] 4.6 c24 c24 [52] 4.6 c25 c25 24H P-Early-Media [109] 8 o c50 [109] 8 o c50 25 P-Media-Authorization [31] 5.1 c9 x [31] 5.1 n/a n/a 25A P-Preferred-Identity [34] 9.2 x c69 [34] 9.2 c14 c14 25B P-Preferred-Service [121] 4.2 x x [121] 4.2 c52 c52 25C P-Private-Network-Indication [134] c59 c59 [134] c59 c59 25D P-Profile-Key [97] 5 c45 c45 [97] 5 c46 c46 25E P-Served-User [133] 6 c60 c60 [133] 6 c60 c60 25F P-User-Database [82] 4 c44 c44 [82] 4 c44 c44 25G P-Visited-Network-ID [52] 4.3 c22 o [52] 4.3 c23 o 26 Priority [26] 20.26 m m [26] 20.26 i c74 26AA Priority-Share Subclause 7.2.16 n/a c80 Subclause 7.2.16 n/a c80 26A Privacy [33] 4.2 c17 c17 [33] 4.2 c18 c18 26AB Priority-Verstat Subclause 7.2.21 n/a c86 Subclause 7.2.21 n/a c86 26B Priv-Answer-Mode [158] c67 c67 [158] c68 c68 27 Proxy-Authorization [26] 20.28 m m [26] 20.28 c13 c13 28 Proxy-Require [26] 20.29, [34] 4 m m [26] 20.29, [34] 4 m m 28A Reason [34A] 2 c32 c32 [34A] 2 c33 c33 29 Record-Route [26] 20.30 m m [26] 20.30 c11 c11 29A Recv-Info [25] 5.2.3 c65 c65 [25] 5.2.3 c66 c66 30 Referred-By [59] 3 c37 c37 [59] 3 c38 c38 31 Reject-Contact [56B] 9.2 c34 c34 [56B] 9.2 c34 c35 31A Relayed-Charge 7.2.12 n/a c76 7.2.12 n/a c76 31B Replaces [60] 6.1 c39 c39 [60] 6.1 c40 c40 31C Reply-To [26] 20.31 m m [26] 20.31 i i 31D Request-Disposition [56B] 9.1 c34 c34 [56B] 9.1 c34 c34 32 Require [26] 20.32 m m [26] 20.32 c7 c7 32A Resource-Priority [116] 3.1 c49 c49 [116] 3.1 c49 c49 32B Restoration-Info Subclause 7.2.11 n/a c75 Subclause 7.2.11 n/a c75 32C Resource-Share Subclause 4.15 n/a c77 Subclause 4.15 n/a c77 33 Route [26] 20.34 m m [26] 20.34 m m 33A Security-Client [48] 2.3.1 x x [48] 2.3.1 c31 c31 33B Security-Verify [48] 2.3.1 x x [48] 2.3.1 c31 c31 33DA Service-Interact-Info Subclause 7.2.14 n/a c84 Subclause 7.2.14 n/a c84 33D Session-Expires [58] 4 c36 c36 [58] 4 c36 c36 33E Session-ID [162] c70 c70 [162] c70 c70 34 Subject [26] 20.36 m m [26] 20.36 i i 35 Supported [26] 20.37 m m [26] 20.37 c8 c8 35A Target-Dialog [184] 7 c71 c71 [184] 7 c72 c72 36 Timestamp [26] 20.38 m m [26] 20.38 i i 37 To [26] 20.39 m m [26] 20.39 m m 37A Trigger-Consent [125] 5.11.2 c55 c55 [125] 5.11.2 c56 c56 38 User-Agent [26] 20.41 m m [26] 20.41 i i 38A User-to-User [126] 7 c57 c57 [126] 7 c58 c58 39 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/10 THEN n/a ELSE m - - suppression or modification of alerting information data. c3: IF A.162/10 THEN m ELSE i - - suppression or modification of alerting information data. c4: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c5: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c6: IF A.3/2 OR A.3/4 THEN m ELSE i - - P-CSCF or S-CSCF. c7: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c8: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c9: IF A.162/26 THEN m ELSE n/a - - SIP extensions for media authorization. c11: IF A.162/14 THEN m ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c12: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c13: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c14: IF A.162/30A OR A.162/30C THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c15: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c16: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c17: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c18: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c19: IF A.162/37 THEN m ELSE n/a - - the P-Called-Party-ID header extension. c20: IF A.162/37 THEN i ELSE n/a - - the P-Called-Party-ID header extension. c21: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a - - the P-Called-Party-ID header extension and P-CSCF or (I-CSCF or IBCF (THIG)). c22: IF A.162/38 THEN m ELSE n/a - - the P-Visited-Network-ID header extension. c23: IF A.162/39 THEN m ELSE i - - reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c24: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c25: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c26: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c27: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c28: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c29: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c30: IF A.162/43 OR (A.162/41 AND A.3/2) THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension (with or without P-CSCF). c31: IF A.162/47 OR A.162/47A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c32: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c33: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c34: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c35: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a - - caller preferences for the session initiation protocol, and S-CSCF. c36: IF A.162/52 THEN m ELSE n/a - - the SIP session timer. c37: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c38: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c39: IF A.162/54 THEN m ELSE n/a - - the Session Inititation Protocol (SIP) "Replaces" header. c40: IF A.162/54 THEN i ELSE n/a - - the Session Inititation Protocol (SIP) "Replaces" header. c41: IF A.162/55 THEN m ELSE n/a - - the Session Inititation Protocol (SIP) "Join" header. c42: IF A.162/55 THEN i ELSE n/a - - the Session Inititation Protocol (SIP) "Join" header. c43: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c44: IF A.162/60 THEN m ELSE n/a - - the P-User-Database private header extension. c45: IF A.162/66A THEN m ELSE n/a - - making the first query to the database in order to populate the P-Profile-Key header. c46: IF A.162/66B THEN m ELSE n/a - - using the information in the P-Profile-Key header. c47: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c48: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c49: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c50: IF A.162/76 THEN m ELSE n/a - - the SIP P-Early-Media private header extension for authorization of early media. c52: IF A.162/84A THEN m ELSE n/a - - act as authentication entity within the trust domain for asserted service. c53: IF A.162/84 THEN m ELSE n/a - - SIP extension for the identification of services. c54: IF A.162/84 OR A.162/30B THEN m ELSE i - - SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network. c55: IF A.162/85 THEN m ELSE n/a - - a framework for consent-based communications in SIP. c56: IF A.162/85 THEN i ELSE n/a - - a framework for consent-based communications in SIP. c57: IF A.162/86 THEN m - - transporting user to user information for call centers using SIP. c58: IF A.162/86 THEN i - - transporting user to user information for call centers using SIP. c59: IF A.162/87 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c60: IF A.162/88 THEN m - - the SIP P-Served-User private header. c63: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c64: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c65: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c66: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c67: IF A.162/97 THEN m ELSE n/a - - requesting answering modes for SIP. c68: IF NOT A.162/97 THEN n/a ELSE IF A.162/97A THEN m ELSE i - - requesting answering modes for SIP, adding, deleting or reading the Answer-Mode header or Priv-Answer-Mode header before proxying the request or response. c69: IF A.162/30C THEN m ELSE x - - act as entity passing on identity transparently independent of trust domain. c70: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c71: IF A.162/109 THEN m ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c72: IF A.162/109 THEN i ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c73: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c74: IF A.162/115 THEN m ELSE i - - PSAP callback indicator. c75: IF A.162/119 THEN o ELSE n/a - - PCRF based P-CSCF restoration. c76: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c77: IF A.162/122 THEN o ELSE n/a - - resource sharing. c78: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c79: IF A.162/43 OR (A.162/41A AND A.3/2) THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension (with or without P-CSCF). c80: IF A.162/124 THEN o ELSE n/a - - priority sharing. c81: IF A.162/126 THEN o ELSE n/a - - authenticated identity management in the Session Initiation Protocol. c82: IF A.162/128 THEN o ELSE n/a - - the Attestation-Info header field extension. c83: IF A.162/129 THEN o ELSE n/a - - the Origination-Id header field extension. c84: IF A.162/130 THEN m ELSE n/a - - Dynamic services interactions. c85: IF A.162/131 THEN o ELSE n/a - - the Additional-Identity header field extension. c86: IF A.162/80 AND A.162/133 THEN o ELSE n/a - - communications resource priority for the session initiation protocol, the Priority-Verstat header field extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/8 - - INVITE request Table A.205: Supported message bodies within the INVITE request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 XML Schema for PSTN [11B] n/a c1 [11B] n/a i 2 application/vnd.3gpp.ussd [8W] n/a m [8W] n/a i 3 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c1 [8ZE] n/a i c1: A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/11 OR A.3/13A THEN m ELSE n/a - - I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.206: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/9 - - INVITE response for all remaining status-codes Table A.207: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Call-Info [26] 20.9 m m [26] 20.9 c4 c4 1B Cellular-Network-Info 7.2.15 n/a c27 7.2.15 n/a c28 2 Content-Disposition [26] 20.11 m m [26] 20.11 i c3 3 Content-Encoding [26] 20.12 m m [26] 20.12 i c3 4 Content-Language [26] 20.13 m m [26] 20.13 i c3 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 i c3 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 m m [26] 20.17 c1 c1 8A Expires [26] 20.19 m m [26] 20.19 i i 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c24 c24 [89] 4.3 c24 c24 9B History-Info [66] 4.1 c17 c17 [66] 4.1 c17 c17 10 MIME-Version [26] 20.24 m m [26] 20.24 i c3 11 Organization [26] 20.25 m m [26] 20.25 c2 c2 11A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c14 c14 [52] 4.4, [52A] 4, [234] 2 c15 c15 11B P-Asserted-Identity [34] 9.1 c6 c6 [34] 9.1 c7 c7 11C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c12 c12 [52] 4.5, [52A] 4 c13 c13 11D P-Charging-Vector [52] 4.6, [52A] 4 c10 c10 [52] 4.6, [52A] 4 c11 c11 11F P-Preferred-Identity [34] 9.2 x x [34] 9.2 c5 n/a 11G Privacy [33] 4.2 c8 c8 [33] 4.2 c9 c9 11H Relayed-Charge 7.2.12 n/a c26 7.2.12 n/a c26 11I Reply-To [26] 20.31 m m [26] 20.31 i i 11J Require [26] 20.32 m m [26] 20.32 c16 c16 11K Server [26] 20.35 m m [26] 20.35 i i 11LA Service-Interact-Info Subclause 7.2.14 n/a c29 Subclause 7.2.14 n/a c29 11L Session-ID [162] c25 c25 [162] c25 c25 12 Timestamp [26] 20.38 m m [26] 20.38 i i 13 To [26] 20.39 m m [26] 20.39 m m 13A User-Agent [26] 20.41 m m [26] 20.41 i i 13B User-to-User [126] 7 c20 c20 [126] 7 c21 c21 14 Via [26] 20.42 m m [26] 20.42 m m 15 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c3: IF A.3/2 OR A.3/4 THEN m ELSE i - - P-CSCF or S-CSCF. c4: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c5: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c6: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c7: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c8: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c9: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c10: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c11: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c12: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c13: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c14: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c16: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c17: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c18: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c19: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c20: IF A.162/86 THEN m - - transporting user to user information for call centers using SIP. c21: IF A.162/86 THEN i - - transporting user to user information for call centers using SIP. c24: IF A.4/60 THEN m ELSE n/a - - SIP location conveyance. c25: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c26: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c27: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c28: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c29: IF A.162/130 THEN m ELSE n/a - - Dynamic services interactions. Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/101A - - Additional for 18x response Table A.208: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Contact [26] 20.10 m m [26] 20.10 i i 4A Feature-Caps [190] c19 c19 [190] c19 c19 5 P-Answer-State [111] c13 c13 [111] c14 c14 5A P-Early-Media [109] 8 o c11 [109] 8 o c11 6 P-Media-Authorization [31] 5.1 c9 x [31] 5.1 n/a n/a 6AA Priority-Share Subclause 7.2.16 n/a c21 Subclause 7.2.16 n/a c21 6A Reason [130], [294] o c18 [130], [294] o c18 7 Record-Route [26] 20.30 m m [26] 20.30 c15 c15 8 Recv-Info [25] 5.2.3 c16 c16 [25] 5.2.3 c17 c17 8A Resource-Share Subclause 4.15 n/a c20 Subclause 4.15 n/a c20 9 RSeq [27] 7.1 m m [27] 7.1 i i c9: IF A.162/26 THEN m ELSE n/a - - SIP extensions for media authorization. c11: IF A.162/76 THEN m ELSE n/a - - the SIP P-Early-Media private header extension for authorization of early media. c13: IF A.162/75 THEN m ELSE n/a - - the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular. c14: IF A.162/75 THEN i ELSE n/a - - the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular. c15: IF A.162/14 THEN m ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c16: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c17: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c18: IF A.162/48A OR A.162/48C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes). c19: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c20: IF A.162/122 THEN o ELSE n/a - - resource sharing. c21: IF A.162/124 THEN o ELSE n/a - - priority sharing. Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/2 - - Additional for 180 (Ringing) response Table A.208A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Alert-Info [26] 20.4 m m [26] 20.4 i i Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/5A - - Additional for 199 (Early Dialog Terminated) response Table A.208B: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Contact [26] 20.10 m m [26] 20.10 i i 5 Reason [130], [294] o c18 [130], [294] o c18 7 Record-Route [26] 20.30 m m [26] 20.30 c15 c15 8 Recv-Info [25] 5.2.3 c16 c16 [25] 5.2.3 c17 c17 9 RSeq [27] 7.1 m m [27] 7.1 i i c15: IF A.162/14 THEN m ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c16: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c17: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c18: IF A.162/48A OR A.162/48C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes). Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/102 - - Additional for 2xx response Table A.209: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 1A Accept-Encoding [26] 20.2 m m [26] 20.2 i i 1B Accept-Language [26] 20.3 m m [26] 20.3 i i 1C Accept-Resource-Priority [116] 3.2 c12 c12 [116] 3.2 c12 c12 2 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 3 Answer-Mode [158] c19 c19 [158] c20 c20 4 Authentication-Info [26] 20.6 m m [26] 20.6 i i 6 Contact [26] 20.10 m m [26] 20.10 i i 6A Feature-Caps [190] c22 c22 [190] c22 c22 7 P-Answer-State [111] c13 c13 [111] c14 c14 7A P-Visited-Network-ID [52B] 3 o o [52B] 3 o o 8 P-Media-Authorization [31] 5.1 c9 x [31] 5.1 n/a n/a 8AA Priority-Share Subclause 7.2.16 n/a c24 Subclause 7.2.16 n/a c24 8A Priv-Answer-Mode [158] c19 c19 [158] c20 c20 8B Reason [294] o c25 [294] o c25 9 Record-Route [26] 20.30 m m [26] 20.30 c3 c3 9A Recv-Info [25] 5.2.3 c17 c17 [25] 5.2.3 c18 c18 9B Resource-Share Subclause 4.15 n/a c23 Subclause 4.15 n/a c23 10 Session-Expires [58] 4 c11 c11 [58] 4 c11 c11 13 Supported [26] 20.37 m m [26] 20.37 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c3: IF A.162/14 THEN m ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c9: IF A.162/26 THEN m ELSE n/a - - SIP extensions for media authorization. c11: IF A.162/52 THEN m ELSE n/a - - the SIP session timer. c12: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c13: IF A.162/75 THEN m ELSE n/a - - the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular. c14: IF A.162/75 THEN i ELSE n/a - - the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular. c17: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c18: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c19: IF A.162/97 THEN m ELSE n/a - - requesting answering modes for SIP. c20: IF NOT A.162/97 THEN n/a ELSE IF A.162/97A THEN m ELSE i - - requesting answering modes for SIP, adding, deleting or reading the Answer-Mode header or Priv-Answer-Mode header before proxying the request or response. c22: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c23: IF A.162/122 THEN o ELSE n/a - - resource sharing. c24: IF A.162/124 THEN o ELSE n/a - - priority sharing. c25: IF A.162/48C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes). Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.209A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Reason [130], [294] o c1 [130], [294] o c1 3 Response-Source 7.2.17 n/a c2 7.2.17 n/a c2 c1: IF A.162/48A OR A.162/48C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying Q.850 or STIR codes). c2: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/103 OR A.164/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.210: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Contact [26] 20.10 m m [26] 20.10 c1 c1 c1: IF A.162/19E THEN m ELSE i - - deleting Contact headers. Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/14 - - Additional for 401 (Unauthorized) response Table A.211: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 6 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 15 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/9 - - INVITE response Prerequisite: A.6/16 - - Additional for 403 (Forbidden) response Table A.211A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 P-Refused-URI-List [183] c1 c1 [183] c1 c1 c1: IF A.162/108 THEN m ELSE n/a -- The SIP P-Refused-URI-List private-header. Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 600 (Busy Everywhere), 603 (Decline) response Table A.212: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 8 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.213: Void Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.214: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 6 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 11 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/21 - - Additional for 408 (Request timeout) response Table A.214A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a c2 c1: IF A.162/120 THEN o ELSE n/a - - HSS based P-CSCF restoration. c2: IF A.162/120 THEN m ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) response Table A.215: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.215A: Supported header field s within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.216: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 10 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.216A: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.16/9 - - INVITE response Prerequisite: A.164/28A - - Additional for 422 (Session Interval Too Small) response Table A.216B: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Min-SE [58] 5 c1 c1 [58] 5 c1 c1 c1: IF A.162/52 THEN m ELSE n/a - - the SIP session timer. Table A.217: Void Table A.217A: Void Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/29H - - Additional for 470 (Consent Needed) response Table A.217AA: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Permission-Missing [125] 5.9.3 m m [125] 5.9.3 m m Prerequisite A.163/9 - - INVITE response Prerequisite: A.164/45 - - 503 (Service Unavailable) Table A.217B: Supported header fields within the INVITE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 8 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.217C: void Prerequisite A.163/9 - - INVITE response Table A.218: Supported message bodies within the INVITE response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 XML Schema for PSTN [11B] c1 [11B] i 2 Recipient List [183] c2 c2 [183] c3 c3 3 3GPP IM CN subsystem XML body subclause 7.6 n/a c4 subclause 7.6 n/a c5 4 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c1 [8ZE] n/a i c1: A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/11 OR A.3/13A THEN m ELSE n/a - - I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). c2 IF A.3/9B THEN m ELSE IF A.3/7A OR A.3/7B OR A.3/7D THEN m ELSE n/a - - IBCF (IMS-ALG), AS acting as terminating UA, AS acting as originating UA, AS performing 3rd party call control. c3 IF A.3/9B THEN m ELSE IF A.3/7A OR A.3/7B OR A.3/7D THEN i ELSE n/a - - IBCF (IMS-ALG), AS acting as terminating UA, AS acting as originating UA, AS performing 3rd party call control. c4: IF A.3/2 OR (A.3/9 AND NOT A.3/9B) OR A.3A/88 THEN m ELSE n/a - - P-CSCF, IBCF, IBCF (IMS-ALG), ATCF (proxy). c5: IF A.3/2 OR (A.3/9 AND NOT A.3/9B) OR A.3A/88 THEN i ELSE n/a - - P-CSCF, IBCF, IBCF (IMS-ALG), ATCF (proxy). A.2.2.4.7A MESSAGE method Prerequisite A.163/9A - - MESSAGE request Table A.218A: Supported header fields within the MESSAGE request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Contact [56B] 9.2 c28 c28 [56B] 9.2 c28 c29 1AA Additional-Identity 7.2.20 n/a c79 7.2.20 n/a c79 1A Allow [26] 20.5 m m [50] 10 i i 2 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 2A Attestation-Info 7.2.18 n/a c76 7.2.18 n/a c76 3 Authorization [26] 20.7 m m [26] 20.7 i i 4 Call-ID [26] 20.8 m m [26] 20.8 m m 5 Call-Info [26] 20.9 m m [26] 20.9 c4 c4 5A Cellular-Network-Info 7.2.15 n/a c73 7.2.15 n/a c74 6 Content-Disposition [26] 20.11 m m [26] 20.11 i i 7 Content-Encoding [26] 20.12 m m [26] 20.12 i i 8 Content-Language [26] 20.13 m m [26] 20.13 i i 9 Content-Length [26] 20.14 m m [26] 20.14 m m 10 Content-Type [26] 20.15 m m [26] 20.15 i i 11 CSeq [26] 20.16 m m [26] 20.16 m m 12 Date [26] 20.17 m m [26] 20.17 c2 c2 13 Expires [26] 20.19 m m [26] 20.19 I i 13A Feature-Caps [190] c71 c71 [190] c71 c71 14 From [26] 20.20 m m [26] 20.20 m m 14A Geolocation [89] 4.1 c36 c36 [89] 4.1 c37 c37 14B History-Info [66] 4.1 c32 c32 [66] 4.1 c32 c32 14C Geolocation-Routing [89] 4.1 c36 c36 [89] 4.1 c37 c37 14D Identity [252] 4 c75 c75 [252] 4 c75 c75 15 In-Reply-To [26] 20.21 m m [50] 10 i i 15A Max-Breadth [117] 5.8 c48 c48 [117] 5.8 c49 c49 16 Max-Forwards [26] 20.22 m m [26] 20.22 m m 17 MIME-Version [26] 20.24 m m [26] 20.24 i i 18 Organization [26] 20.25 m m [26] 20.25 c3 c3 18AA Origination-Id 7.2.19 n/a c77 7.2.19 n/a c77 18A P-Access-Network-Info [52] 4.4, [234] 2 c23 c23 [52] 4.4, [234] 2 c24 c24 18B P-Asserted-Identity [34] 9.1 c10 c10 [34] 9.1 c11 c11 18C P-Asserted-Service [121] 4.1 c40 c40 [121] 4.1 c41 c41 18D P-Called-Party-ID [52] 4.2 c14 c14 [52] 4.2 c15 c16 18E P-Charging-Function-Addresses [52] 4.5 c21 c21 [52] 4.5 c22 c22 18F P-Charging-Vector [52] 4.6 c19 c19 [52] 4.6 c20 c20 18H P-Preferred-Identity [34] 9.2 x c69 [34] 9.2 c9 c9 18I P-Preferred-Service [121] 4.2 x x [121] 4.2 c39 c39 18J P-Private-Network-Indication [134] c44 c44 [134] c44 c44 18K P-Profile-Key [97] 5 c34 c34 [97] 5 c35 c35 18L P-Served-User [133] 6 c45 c45 [133] 6 c45 c45 18M P-User-Database [82] 4 c33 c33 [82] 4 c33 c33 18N P-Visited-Network-ID [52] 4.3 c17 o [52] 4.3 c18 o 19 Priority [26] 20.26 m m [26] 20.26 i c50 19A Privacy [33] 4.2 c12 c12 [33] 4.2 c13 c13 20 Proxy-Authorization [26] 20.28 m m [26] 20.28 c8 c8 21 Proxy-Require [26] 20.29 m m [26] 20.29 m m 21A Reason [34A] 2 c26 c26 [34A] 2 c27 c27 22A Referred-By [59] 3 c30 c30 [59] 3 c31 c31 23 Reject-Contact [56B] 9.2 c28 c28 [56B] 9.2 c28 c29 23A Relayed-Charge 7.2.12 n/a c72 7.2.12 n/a c72 23B Reply-To [26] 20.31 m m [26] 20.31 i i 23C Request-Disposition [56B] 9.1 c28 c28 [56B] 9.1 c28 c28 24 Require [26] 20.32 m m [26] 20.32 c5 c5 24A Resource-Priority [116] 3.1 c38 c38 [116] 3.1 c38 c38 25 Route [26] 20.34 m m [26] 20.34 m m 25A Security-Client [48] 2.3.1 x x [48] 2.3.1 c25 c25 25B Security-Verify [48] 2.3.1 x x [48] 2.3.1 c25 c25 25D Service-Interact-Info Subclause 7.2.14 n/a c78 Subclause 7.2.14 n/a c78 26 Subject [26] 20.36 m m [26] 20.36 i i 25C Session-ID [162] c70 c70 [162] c70 c70 27 Supported [26] 20.37 m m [26] 20.37 c6 c6 28 Timestamp [26] 20.38 m m [26] 20.38 i i 29 To [26] 20.39 m m [26] 20.39 m m 29A Trigger-Consent [125] 5.11.2 c42 c42 [125] 5.11.2 c43 c43 30 User-Agent [26] 20.41 m m [26] 20.41 i i 31 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c4: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c8: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c9: IF A.162/30A OR A.162/30C THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c10: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c11: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c12: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c13: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c14: IF A.162/37 THEN m ELSE n/a - - the P-Called-Party-ID header extension. c15: IF A.162/37 THEN i ELSE n/a - - the P-Called-Party-ID header extension. c16: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a - - the P-Called-Party-ID header extension and P-CSCF or (I-CSCF or IBCF (THIG)). c17: IF A.162/38 THEN m ELSE n/a - - the P-Visited-Network-ID header extension. c18: IF A.162/39 THEN m ELSE i - - reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c19: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c20: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c21: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c22: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c23: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c25: IF A.162/47 OR A.162/47A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c26: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c27: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c28: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c29: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a - - caller preferences for the session initiation protocol, and S-CSCF. c30: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c31: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c32: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c33: IF A.162/60 THEN m ELSE n/a - - the P-User-Database private header extension. c34: IF A.162/66A THEN m ELSE n/a - - making the first query to the database in order to populate the P-Profile-Key header. c35: IF A.162/66B THEN m ELSE n/a - - using the information in the P-Profile-Key header. c36: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c37: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c38: IF A.162/80A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c39: IF A.162/84A THEN m ELSE n/a - - act as authentication entity within the trust domain for asserted service. c40: IF A.162/84 THEN m ELSE n/a - - SIP extension for the identification of services. c41: IF A.162/84 OR A.162/30B THEN m ELSE i - - SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network. c42: IF A.162/85 THEN m ELSE n/a - - a framework for consent-based communications in SIP. c43: IF A.162/85 THEN i ELSE n/a - - a framework for consent-based communications in SIP. c44: IF A.162/87 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c45: IF A.162/88 THEN m ELSE n/a - - the SIP P-Served-User private header. c48: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c49: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c50: IF A.162/115 THEN m ELSE i - - PSAP callback indicator. c69: IF A.162/30C THEN m ELSE x - - act as entity passing on identity transparently independent of trust domain. c70: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c71: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c72: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c73: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c74: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c75: IF A.162/126 THEN o ELSE n/a - - authenticated identity management in the Session Initiation Protocol. c76: IF A.162/128 THEN o ELSE n/a - - the Attestation-Info header field extension. c77: IF A.162/129 THEN o ELSE n/a - - the Origination-Id header field extension. c78: IF A.162/130 THEN m ELSE n/a - - Dynamic services interactions. c79: IF A.162/131 THEN o ELSE n/a - - the Additional-Identity header field extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/9A - - MESSAGE request Table A.218B: Supported message bodies within the MESSAGE request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 permission document [125] 5.4 c1 c1 [125] 5.4 c2 c2 2 application/vnd.3gpp.sms [4D] m m [4D] i i 2 message/cpim [151] c3 c3 [151] c4 c4 3 message/imdn+xml [157] c5 c5 [157] c6 c6 4 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c7 [8ZE] n/a i 5 application/vnd.3gpp.mcptt-mbms-usage-info+xml [8ZE] n/a c7 [8ZE] n/a i 6 application/vnd.3gpp.mcptt-location-info+xml [8ZE] n/a c7 [8ZE] n/a i 7 application/vnd.3gpp.mcptt-floor-request+xml [8ZE] n/a c7 [8ZE] n/a i 8 application/vnd.3gpp.mcptt-affiliation-command+xml [8ZE] n/a c7 [8ZE] n/a i c1: IF A.162/85 THEN m ELSE n/a - - a framework for consent-based communications in SIP. c2: IF A.162/85 THEN i ELSE n/a - - a framework for consent-based communications in SIP. c3: IF A.162/95 THEN m ELSE n/a - - common presence and instant messaging (CPIM): message format. c4: IF A.162/95 THEN i ELSE n/a - - common presence and instant messaging (CPIM): message format. c5: IF A.162/96 THEN m ELSE n/a - - instant message disposition notification. c6: IF A.162/96 THEN i ELSE n/a - - instant message disposition notification. c7: A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/11 OR A.3/13A THEN m ELSE n/a - - I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.218BA: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/9B - - MESSAGE response for all remaining status-codes Table A.218C: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Call-Info [26] 20.9 m m [26] 20.9 c3 c3 2A Cellular-Network-Info 7.2.15 n/a c23 7.2.15 n/a c24 3 Content-Disposition [26] 20.11 m m [26] 20.11 i i 4 Content-Encoding [26] 20.12 m m [26] 20.12 i i 5 Content-Language [26] 20.13 m m [26] 20.13 i i 6 Content-Length [26] 20.14 m m [26] 20.14 m m 7 Content-Type [26] 20.15 m m [26] 20.15 i i 8 CSeq [26] 20.16 m m [26] 20.16 m m 9 Date [26] 20.17 m m [26] 20.17 c1 c1 9A Expires [26] 20.19 m m [26] 20.19 i i 10 From [26] 20.20 m m [26] 20.20 m m 10A Geolocation-Error [89] 4.3 c17 c17 [89] 4.3 c18 c18 10B History-Info [66] 4.1 c16 c16 [66] 4.1 c16 c16 11 MIME-Version [26] 20.24 m m [26] 20.24 i i 12 Organization [26] 20.25 m m [26] 20.25 c2 c2 12A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c13 c13 [52] 4.4, [52A] 4, [234] 2 c14 c14 12B P-Asserted-Identity [34] 9.1 c5 c5 [34] 9.1 c6 c6 12C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c11 c11 [52] 4.5, [52A] 4 c12 c12 12D P-Charging-Vector [52] 4.6, [52A] 4 c9 c9 [52] 4.6, [52A] 4 c10 c10 12F P-Preferred-Identity [34] 9.2 x x [34] 9.2 c4 n/a 12G Privacy [33] 4.2 c7 c7 [33] 4.2 c8 c8 12H Relayed-Charge 7.2.12 n/a c22 7.2.12 n/a c22 12I Reply-To [26] 20.31 m m [26] 20.31 i i 12J Require [26] 20.32 m m [26] 20.32 c15 c15 13 Server [26] 20.35 m m [26] 20.35 i i 13AA Service-Interact-Info Subclause 7.2.14 n/a c25 Subclause 7.2.14 n/a c25 13A Session-ID [162] c21 c21 [162] c21 c21 14 Timestamp [26] 20.38 i i [26] 20.38 i i 15 To [26] 20.39 m m [26] 20.39 m m 16 User-Agent [26] 20.41 m m [26] 20.41 i i 17 Via [26] 20.42 m m [26] 20.42 m m 18 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c3: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c4: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c5: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c6: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c7: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c9: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c11: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c13: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c16: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c17: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c18: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c21: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c22: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c23: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c25: IF A.162/130 THEN m ELSE n/a - - Dynamic services interactions. Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/102 - - Additional for 2xx response Table A.218D: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c4 c4 [116] 3.2 c4 c4 1 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 2 Authentication-Info [26] 20.6 m m [26] 20.6 i i 3 Feature-Caps [190] c6 c6 [190] c6 c6 3A Reason [294] o c7 [294] o c7 4 P-Visited-Network-ID [52B] 3 o o [52B] 3 o o 6 Supported [26] 20.37 m m [26] 20.37 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c4: IF A.162/80A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c6: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c7: IF A.162/48C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes). Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.218DA: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 1A Reason [294] o c2 [294] o c2 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses. c2: IF A.4/38C THEN o ELSE n/a - - use of the Reason header field in Session Initiation Protocol (SIP) responses (carrying STIR codes). Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/103 OR A.164/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.218E: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Contact [26] 20.10 m m [26] 20.10 c1 c1 c1: IF A.162/19E THEN m ELSE i - - deleting Contact headers. Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/14 - - Additional for 401 (Unauthorized) response Table A.218F: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.218G: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.218H: Void Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.218I: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Table 218IA: Void Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) Table A.218J: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.218JA: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.218K: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.218L: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.218M: Void Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/29H - - Additional for 470 (Consent Needed) response Table A.218MA: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Permission-Missing [125] 5.9.3 m m [125] 5.9.3 m m Prerequisite A.163/9B - - MESSAGE response Prerequisite: A.164/46 - - Additional for 504 (Server Time-out) response Table A.218MB: Supported header fields within the MESSAGE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.163/9B - - MESSAGE response Table A.218N: Supported message bodies within the MESSAGE response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.8 NOTIFY method Prerequisite A.163/10 - - NOTIFY request Table A.219: Supported header fields within the NOTIFY request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 1A Accept-Contact [56B] 9.2 c21 c21 [56B] 9.2 c22 c22 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i 3A Allow [26] 20.5 m m [26] 20.5 i i 4 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 5 Authorization [26] 20.7 m m [26] 20.7 i i 6 Call-ID [26] 20.8 m m [26] 20.8 m m 6A Call-Info [26] 20.9 m m [26] 20.9 c28 c28 6B Cellular-Network-Info 7.2.15 n/a c43 7.2.15 n/a c44 6C Contact [26] 20.10 m m [26] 20.10 i i 7 Content-Disposition [26] 20.11 m m [26] 20.11 i i 8 Content-Encoding [26] 20.12 m m [26] 20.12 i i 9 Content-Language [26] 20.13 m m [26] 20.13 i i 10 Content-Length [26] 20.14 m m [26] 20.14 m m 11 Content-Type [26] 20.15 m m [26] 20.15 i i 12 CSeq [26] 20.16 m m [26] 20.16 m m 13 Date [26] 20.17 m m [26] 20.17 c2 c2 14 Event [28] 8.2.1 m m [28] 8.2.1 m m 14A Feature-Caps [190] c41 c41 [190] c41 c41 15 From [26] 20.20 m m [26] 20.20 m m 15A Geolocation [89] 4.1 c26 c26 [89] 4.1 c27 c27 15B Geolocation-Routing [89] 4.1 c26 c26 [89] 4.1 c27 c27 15C History-Info [66] 4.1 c25 c25 [66] 4.1 c25 c25 15D Max-Breadth [117] 5.8 c29 c29 [117] 5.8 c30 c30 16 Max-Forwards [26] 20.22 m m [26] 20.22 m m 17 MIME-Version [26] 20.24 m m [26] 20.24 i i 17A P-Access-Network-Info [52] 4.4, [234] 2 c16 c16 [52] 4.4. [234] 2 c17 c17 17B P-Asserted-Identity [34] 9.1 c8 c8 [34] 9.1 c9 c9 17C P-Charging-Function-Addresses [52] 4.5 c14 c14 [52] 4.5 c15 c15 17D P-Charging-Vector [52] 4.6 c12 c12 [52] 4.6 c13 c13 17F P-Preferred-Identity [34] 9.2 x x [34] 9.2 c3 n/a 17G Privacy [33] 4.2 c10 c10 [33] 4.2 c11 c11 18 Proxy-Authorization [26] 20.28 m m [26] 20.28 c4 c4 19 Proxy-Require [26] 20.29 m m [26] 20.29 m m 19A Reason [34A] 2 c19 c19 [34A] 2 c20 c20 20 Record-Route [26] 20.30 m m [26] 20.30 c7 c7 20A Referred-By [59] 3 c23 c23 [59] 3 c24 c24 20B Reject-Contact [56B] 9.2 c21 c21 [56B] 9.2 c22 c22 20C Relayed-Charge 7.2.12 n/a c42 7.2.12 n/a c42 20D Request-Disposition [56B] 9.1 c21 c21 [56B] 9.1 c22 c22 21 Require [26] 20.32 m m [26] 20.32 c5 c5 22 Route [26] 20.34 m m [26] 20.34 m m 22A Security-Client [48] 2.3.1 x x [48] 2.3.1 c18 c18 22B Security-Verify [48] 2.3.1 x x [48] 2.3.1 c18 c18 22C Session-ID [162] c40 c40 [162] c40 c40 23 Subscription-State [28] 8.2.3 m m [28] 8.2.3 i i 24 Supported [26] 20.37 m m [26] 20.37 c6 c6 24A Resource-Priority [116] 3.1 c36 c36 [116] 3.1 c36 c36 25 Timestamp [26] 20.38 m m [26] 20.38 i i 26 To [26] 20.39 m m [26] 20.39 m m 27 User-Agent [26] 20.41 m m [26] 20.41 i i 28 Via [26] 20.42 m m [26] 20.42 m m 29 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c4: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN (IF A.162/22 OR A.162/27 THEN m ELSE o) ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog or (the REFER method or SIP specific event notification). c8: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c9: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c10: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c11: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c12: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c13: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c14: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c15: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c16: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c17: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c18: IF A.162/47 OR A.162/47A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c19: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c20: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c21: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c22: IF A.162/50 THEN i ELSE n/a - - caller preferences for the session initiation protocol. c23: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c24: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c25: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c26: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c27: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c28: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c29: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c30: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c36: IF A.162/80A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c40: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c41: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c42: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c43: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c44: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/10 - - NOTIFY request Table A.220: Supported message bodies within the NOTIFY request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 sipfrag [37] 2 m m [37] 2 i i 2 event package [28] m m [28] i i Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.220A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/11 - - NOTIFY response for all remaining status-codes Table A.221: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Cellular-Network-Info 7.2.15 n/a c20 7.2.15 n/a c21 2 Content-Disposition [26] 20.11 m m [26] 20.11 i i 3 Content-Encoding [26] 20.12 m m [26] 20.12 i i 4 Content-Language [26] 20.13 m m [26] 20.13 i i 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 i i 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 m m [26] 20.17 c1 c1 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c14 c14 [89] 4.3 c15 c15 10 MIME-Version [26] 20.24 m m [26] 20.24 i i 10A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c11 c11 [52] 4.4, [52A] 4, [234] 2 c12 c12 10B P-Asserted-Identity [34] 9.1 c3 c3 [34] 9.1 c4 c4 10C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c9 c9 [52] 4.5, [52A] 4 c10 c10 10D P-Charging-Vector [52] 4.6, [52A] 4 c7 c7 [52] 4.6, [52A] 4 c8 c8 10F P-Preferred-Identity [34] 9.2 x x [34] 9.2 c2 n/a 10G Privacy [33] 4.2 c5 c5 [33] 4.2 c6 c6 10H Relayed-Charge 7.2.12 n/a c19 7.2.12 n/a c19 10I Require [26] 20.32 m m [26] 20.32 c13 c13 10J Server [26] 20.35 m m [26] 20.35 i i 10K Session-ID [162] c18 c18 [162] c18 c18 11 Timestamp [26] 20.38 m m [26] 20.38 i i 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 m m [26] 20.41 i i 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c3: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c4: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c5: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c6: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c7: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c8: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c9: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c10: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c11: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c12: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c13: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c14: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c15: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c18: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c19: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c20: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c21: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/102 - - Additional for 2xx response Table A.222: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c4 c4 [116] 3.2 c4 c4 0B Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 1 Authentication-Info [26] 20.6 m m [26] 20.6 i i 1A Contact [26] 20.10 m m [26] 20.10 i i 1B Feature-Caps [190] c6 c6 [190] c6 c6 2 Record-Route [26] 20.30 m m [26] 20.30 c3 c3 5 Supported [26] 20.37 m m [26] 20.37 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c3: IF A.162/15 THEN m ELSE i - - the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/80A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c6: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.222A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/103 - - Additional for 3xx response Table A.223: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Contact [26] 20.10 m m [26] 20.10 c1 c1 c1: IF A.162/19E THEN m ELSE i - - deleting Contact headers. Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/14 - - Additional for 401 (Unauthorized) response Table A.224: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.225: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.226: Void Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.227: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Table A.227A: Void Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) response Table A.228: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.228A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.229: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.229A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.230: Void Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/35 - - Additional for 485 (Ambigious) response Table A.230A: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Contact [26] 20.10 m m [26] 20.10 i i Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/39 - - Additional for 489 (Bad Event) response Table A.231: Supported header fields within the NOTIFY response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/11 - - NOTIFY response Prerequisite: A.164/46 - - Additional for 504 (Server Time-out) response Table A.231A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.163/11 - - NOTIFY response Table A.232: Supported message bodies within the NOTIFY response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.9 OPTIONS method Prerequisite A.163/12 - - OPTIONS request Table A.233: Supported header fields within the OPTIONS request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 1A Accept-Contact [56B] 9.2 c28 c28 [56B] 9.2 c28 c29 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i 3A Allow [26] 20.5 m m [26] 20.5 i i 4 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 5 Authorization [26] 20.7 m m [26] 20.7 i i 6 Call-ID [26] 20.8 m m [26] 20.8 m m 7 Call-Info [26] 20.9 m m [26] 20.9 c4 c4 7A Cellular-Network-Info 7.2.15 n/a c59 7.2.15 n/a c60 8 Contact [26] 20.10 m m [26] 20.10 i i 9 Content-Disposition [26] 20.11 m m [26] 20.11 i i 10 Content-Encoding [26] 20.12 m m [26] 20.12 i i 11 Content-Language [26] 20.13 m m [26] 20.13 i i 12 Content-Length [26] 20.14 m m [26] 20.14 m m 13 Content-Type [26] 20.15 m m [26] 20.15 i i 14 CSeq [26] 20.16 m m [26] 20.16 m m 15 Date [26] 20.17 m m [26] 20.17 c2 c2 15A Feature-Caps [190] c57 c57 [190] c57 c57 16 From [26] 20.20 m m [26] 20.20 m m 16A Geolocation [89] 4.1 c36 c36 [89] 4.1 c37 c37 16B Geolocation-Routing [89] 4.1 c36 c36 [89] 4.1 c37 c37 16C History-Info [66] 4.1 c32 c32 [66] 4.1 c32 c32 16D Max-Breadth [117] 5.8 c41 c41 [117] 5.8 c42 c42 17 Max-Forwards [26] 20.22 m m [26] 20.22 m m 18 MIME-Version [26] 20.24 m m [26] 20.24 i i 19 Organization [26] 20.25 m m [26] 20.25 c3 c3 19A P-Access-Network-Info [52] 4.4, [234] 2 c23 c23 [52] 4.4, [234] 2 c24 c24 19B P-Asserted-Identity [34] 9.1 c10 c10 [34] 9.1 c11 c11 19C P-Asserted-Service [121] 4.1 c39 c39 [121] 4.1 c40 c40 19D P-Called-Party-ID [52] 4.2 c14 c14 [52] 4.2 c15 c16 19E P-Charging-Function-Addresses [52] 4.5 c21 c21 [52] 4.5 c22 c22 19F P-Charging-Vector [52] 4.6 c19 c19 [52] 4.6 c20 c20 19H P-Preferred-Identity [34] 9.2 x c54 [34] 9.2 c9 c55 19I P-Preferred-Service [121] 4.2 x x [121] 4.2 c38 c38 19J P-Private-Network-Indication [134] c48 c48 [134] c48 c48 19K P-Profile-Key [97] 5 c34 c34 [97] 5 c35 c35 19L P-Served-User [133] 6 c49 c49 [133] 6 c49 c49 19M P-User-Database [82] 4 c33 c33 [82] 4 c33 c33 19N P-Visited-Network-ID [52] 4.3 c17 o [52] 4.3 c18 o 19O Privacy [33] 4.2 c12 c12 [33] 4.2 c13 c13 20 Proxy-Authorization [26] 20.28 m m [26] 20.28 c8 c8 21 Proxy-Require [26] 20.29 m m [26] 20.29 m m 21A Reason [34A] 2 c26 c26 [34A] 2 c27 c27 22 Record-Route [26] 20.30 m m [26] 20.30 c7 c7 22A Recv-Info [25] 5.2.3 c52 c52 [25] 5.2.3 c53 c53 22B Referred-By [59] 3 c30 c30 [59] 3 c31 c31 22C Reject-Contact [56B] 9.2 c28 c28 [56B] 9.2 c28 c29 22D Relayed-Charge 7.2.12 n/a c58 7.2.12 n/a c58 22E Request-Disposition [56B] 9.1 c28 c28 [56B] 9.1 c28 c28 23 Require [26] 20.32 m m [26] 20.32 c5 c5 23A Resource-Priority [116] 3.1 c47 c47 [116] 3.1 c47 c47 24 Route [26] 20.34 m m [26] 20.34 m m 24A Security-Client [48] 2.3.1 x x [48] 2.3.1 c25 c25 24B Security-Verify [48] 2.3.1 x x [48] 2.3.1 c25 c25 24C Session-ID [162] c56 c56 [162] c56 c56 25 Supported [26] 20.37 m m [26] 20.37 c6 c6 26 Timestamp [26] 20.38 m m [26] 20.38 i i 27 To [26] 20.39 m m [26] 20.39 m m 28 User-Agent [26] 20.41 m m [26] 20.41 i i 29 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c4: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c9: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c10: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c11: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c12: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c13: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c14: IF A.162/37 THEN m ELSE n/a - - the P-Called-Party-ID header extension. c15: IF A.162/37 THEN i ELSE n/a - - the P-Called-Party-ID header extension. c16: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a - - the P-Called-Party-ID header extension and P-CSCF or (I-CSCF or IBCF (THIG)). c17: IF A.162/38 THEN m ELSE n/a - - the P-Visited-Network-ID header extension. c18: IF A.162/39 THEN m ELSE i - - reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c19: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c20: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c21: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c22: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c23: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c25: IF A.162/47 OR A.162/47A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c26: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c27: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c28: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c29: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a - - caller preferences for the session initiation protocol, and S-CSCF. c30: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c31: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c32: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c33: IF A.162/60 THEN m ELSE n/a - - the P-User-Database private header extension. c34: IF A.162/66A THEN m ELSE n/a - - making the first query to the database in order to populate the P-Profile-Key header. c35: IF A.162/66B THEN m ELSE n/a - - using the information in the P-Profile-Key header. c36: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c37: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c38: IF A.162/84A THEN m ELSE n/a - - act as authentication entity within the trust domain for asserted service. c39: IF A.162/84 THEN m ELSE n/a - - SIP extension for the identification of services. c40: IF A.162/84 OR A.162/30B THEN m ELSE i - - SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network. c41: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c42: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c47: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c48: IF A.162/87 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c49: IF A.162/88 THEN m ELSE n/a - - the SIP P-Served-User private header. c52: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c53: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c54: IF A.162/30C THEN m ELSE x - - act as entity passing on identity transparently independent of trust domain. c55: IF A.162/30A OR A.162/30C THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c56: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c57: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c58: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c59: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c60: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/12 - - OPTIONS request Table A.234: Supported message bodies within the OPTIONS request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Table A.235: Void Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.235A: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/13 - - OPTIONS response for all remaining status-codes Table A.236: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Call-Info [26] 20.9 m m [26] 20.9 c3 c3 1B Cellular-Network-Info 7.2.15 n/a c25 7.2.15 n/a c26 2 Content-Disposition [26] 20.11 m m [26] 20.11 i i 3 Content-Encoding [26] 20.12 m m [26] 20.12 i i 4 Content-Language [26] 20.13 m m [26] 20.13 i i 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 i i 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 m m [26] 20.17 c1 c1 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c17 c17 [89] 4.3 c18 c18 9B History-Info [66] 4.1 c16 c16 [66] 4.1 c16 c16 10 MIME-Version [26] 20.24 m m [26] 20.24 i i 11 Organization [26] 20.25 m m [26] 20.25 c2 c2 11A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c13 c13 [52] 4.4, [52A] 4, [234] 2 c14 c14 11B P-Asserted-Identity [34] 9.1 c5 c5 [34] 9.1 c6 c6 11C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c11 c11 [52] 4.5, [52A] 4 c12 c12 11D P-Charging-Vector [52] 4.6, [52A] 4 c9 c9 [52] 4.6, [52A] 4 c10 c10 11F P-Preferred-Identity [34] 9.2 x x [34] 9.2 c4 n/a 11G Privacy [33] 4.2 c7 c7 [33] 4.2 c8 c8 11H Recv-Info [25] 5.2.3 c21 c21 [25] 5.2.3 c22 c22 11I Relayed-Charge 7.2.12 n/a c24 7.2.12 n/a c24 11J Require [26] 20.32 m m [26] 20.32 c15 c15 11K Server [26] 20.35 m m [26] 20.35 i i 11K Session-ID [162] c23 c23 [162] c23 c23 12 Timestamp [26] 20.38 m m [26] 20.38 i i 13 To [26] 20.39 m m [26] 20.39 m m 13A User-Agent [26] 20.41 m m [26] 20.41 i i 14 Via [26] 20.42 m m [26] 20.42 m m 15 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c3: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c4: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c5: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c6: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c7: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c9: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c11: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c13: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c16: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c17: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c18: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c21: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c22: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c23: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c24: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c25: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c26: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/102 - - Additional for 2xx response Table A.237: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 1A Accept-Encoding [26] 20.2 m m [26] 20.2 i i 1B Accept-Language [26] 20.3 m m [26] 20.3 i i 1C Accept-Resource-Priority [116] 3.2 c12 c12 [116] 3.2 c12 c12 2 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 3 Authentication-Info [26] 20.6 m m [26] 20.6 i i 5 Contact [26] 20.10 m m [26] 20.10 i i 6 Feature-Caps [190] c14 c14 [190] c14 c14 7 Recv-Info [25] 5.2.3 c7 c7 [25] 5.2.3 c8 c8 9 Record-Route [26] 20.30 m m [26] 20.30 c3 c3 12 Supported [26] 20.37 m m [26] 20.37 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c3: IF A.162/15 THEN o ELSE i - - the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c7: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c8: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c12: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c14: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.237A: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/103 OR A.164/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.238: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Contact [26] 20.10 m m [26] 20.10 c1 c1 c1: IF A.162/19E THEN m ELSE i - - deleting Contact headers. Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/14 - - Additional for 401 (Unauthorized) response Table A.239: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 10 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.240: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.241: Void Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.242: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Table A.242A: Void Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) response Table A.243: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.243A: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.244: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 7 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.244A: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.245: Void Prerequisite A.163/13 - - OPTIONS response Prerequisite: A.164/46 - - Additional for 504 (Server Time-out) response Table A.245A: Supported header fields within the OPTIONS response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.163/13 - - OPTIONS response Table A.246: Supported message bodies within the OPTIONS response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.10 PRACK method Prerequisite A.163/14 - - PRACK request Table A.247: Supported header fields within the PRACK request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 1A Accept-Contact [56B] 9.2 c18 c18 [56B] 9.2 c19 c19 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i 3A Allow [26] 20.5 m m [26] 20.5 i i 4 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 5 Authorization [26] 20.7 m m [26] 20.7 i i 6 Call-ID [26] 20.8 m m [26] 20.8 m m 6A Cellular-Network-Info 7.2.15 n/a c51 7.2.15 n/a c52 7 Content-Disposition [26] 20.11 m m [26] 20.11 i c3 8 Content-Encoding [26] 20.12 m m [26] 20.12 i c3 9 Content-Language [26] 20.13 m m [26] 20.13 i c3 10 Content-Length [26] 20.14 m m [26] 20.14 m m 11 Content-Type [26] 20.15 m m [26] 20.15 i c3 12 CSeq [26] 20.16 m m [26] 20.16 m m 13 Date [26] 20.17 m m [26] 20.17 c2 c2 14 From [26] 20.20 m m [26] 20.20 m m 14A Max-Breadth [117] 5.8 c26 c26 [117] 5.8 c27 c27 15 Max-Forwards [26] 20.22 m m [26] 20.22 m m 16 MIME-Version [26] 20.24 m m [26] 20.24 i c3 16A P-Access-Network-Info [52] 4.4, [234] 2 c14 c14 [52] 4.4, [234] 2 c15 c15 16B P-Charging-Function-Addresses [52] 4.5 c12 c12 [52] 4.5 c13 c13 16C P-Charging-Vector [52] 4.6 c10 c10 [52] 4.6 c11 c11 16E P-Early-Media [109] 8 o c22 [109] 8 o c22 16EA Priority-Share Subclause 7.2.16 n/a c53 Subclause 7.2.16 n/a c53 16F Privacy [33] 4.2 c8 c8 [33] 4.2 c9 c9 17 Proxy-Authorization [26] 20.28 m m [26] 20.28 c4 c4 18 Proxy-Require [26] 20.29 m m [26] 20.29 m m 19 RAck [27] 7.2 m m [27] 7.2 i i 19A Reason [34A] 2 c16 c16 [34A] 2 c17 c17 20 Record-Route [26] 20.30 m m [26] 20.30 c7 c7 20A Recv-Info [25] 5.2.3 c28 c28 [25] 5.2.3 c29 c29 20B Referred-By [59] 3 c20 c20 [59] 3 c21 c21 20C Reject-Contact [56B] 9.2 c18 c18 [56B] 9.2 c19 c19 20D Relayed-Charge 7.2.12 n/a c49 7.2.12 n/a c49 20E Request-Disposition [56B] 9.1 c18 c18 [56B] 9.1 c19 c19 21 Require [26] 20.32 m m [26] 20.32 c5 c5 21A Resource-Priority [16] 3.1 c47 c47 [116] 3.1 c47 c47 21B Resource-Share Subclause 4.15 n/a c50 Subclause 4.15 n/a c50 22 Route [26] 20.34 m m [26] 20.34 m m 22A Session-ID [162] c48 c48 [162] c48 c48 23 Supported [26] 20.37 m m [26] 20.37 c6 c6 24 Timestamp [26] 20.38 m m [26] 20.38 i i 25 To [26] 20.39 m m [26] 20.39 m m 26 User-Agent [26] 20.41 m m [26] 20.41 i i 27 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.3/2 OR A.3/4 THEN m ELSE i - - P-CSCF or S-CSCF. c4: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c9: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c10: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c11: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c12: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c13: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c14: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c16: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c17: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c18: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c19: IF A.162/50 THEN i ELSE n/a - - caller preferences for the session initiation protocol. c20: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c21: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c22: IF A.162/76 THEN m ELSE n/a - - the SIP P-Early-Media private header extension for authorization of early media. c26: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c27: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c28: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c29: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c47: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c48: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c49: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c50: IF A.4/112 THEN o ELSE n/a - - resource sharing. c51: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c52: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c53: IF A.162/124 THEN o ELSE n/a - - priority sharing. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/14 - - PRACK request Table A.248: Supported message bodies within the PRACK request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Table A.249: Void Prerequisite A.163/15 - - PRACK response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.249A: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/15 - - PRACK response for all remaining status-codes Table A.250: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Cellular-Network-Info 7.2.15 n/a c18 7.2.15 n/a c19 2 Content-Disposition [26] 20.11 m m [26] 20.11 i c2 3 Content-Encoding [26] 20.12 m m [26] 20.12 i c2 4 Content-Language [26] 20.13 m m [26] 20.13 i c2 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 i c2 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 m m [26] 20.17 c1 c1 9 From [26] 20.20 m m [26] 20.20 m m 10 MIME-Version [26] 20.24 m m [26] 20.24 i c2 10A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c9 c9 [52] 4.4, [52A] 4, [234] 2 c10 c10 10B P-Charging-Function-Addresses [52] 4.5, [52A] 4 c7 c7 [52] 4.5, [52A] 4 c8 c8 10C P-Charging-Vector [52] 4.6, [52A] 4 c5 c5 [52] 4.6, [52A] 4 c6 c6 10F Privacy [33] 4.2 c3 c3 [33] 4.2 c4 c4 10G Recv-Info [25] 5.2.3 c14 c14 [25] 5.2.3 c15 c15 10H Relayed-Charge 7.2.12 n/a c17 7.2.12 n/a c17 10I Require [26] 20.32 m m [26] 20.32 c11 c11 10J Server [26] 20.35 m m [26] 20.35 i i 10K Session-ID [162] c16 c16 [162] c16 c16 11 Timestamp [26] 20.38 m m [26] 20.38 i i 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 m m [26] 20.41 i i 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.3/2 OR A.3/4 THEN m ELSE i - - P-CSCF or S-CSCF. c3: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c4: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c5: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c6: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c7: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c8: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c9: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c10: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c11: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c14: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c15: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c16: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c17: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c18: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c19: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. Prerequisite A.163/15 - - PRACK response Prerequisite: A.164/102 - - Additional for 2xx response Table A.251: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 0B Authentication-Info [26] 20.6 m m [26] 20.6 i i 0C Accept-Resource-Priority [116] 3.2 c12 c12 [116] 3.2 c12 c12 0D P-Early-Media [109] 8 o c4 [109] 8 o c4 0E Priority-Share Subclause 7.2.16 n/a c14 Subclause 7.2.16 n/a c14 1 Record-Route [26] 20.30 m m [26] 20.30 c3 c3 2 Recv-Info [25] 5.2.3 c6 c6 [25] 5.2.3 c7 c7 2A Resource-Share Subclause 4.15 n/a c13 Subclause 4.15 n/a c13 3 Supported [26] 20.37 m m [26] 20.37 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c3: IF A.162/15 THEN o ELSE i - - the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/76 THEN m ELSE n/a - - the SIP P-Early-Media private header extension for authorization of early media. c6: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c7: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c12: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c13: IF A.4/112 THEN o ELSE n/a - - resource sharing. c14: IF A.162/124 THEN o ELSE n/a - - priority sharing. Prerequisite A.163/3 - - PRACK response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.251A: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.163/15 - - PRACK response Prerequisite: A.164/103 OR A.164/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.252: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Contact [26] 20.10 m m [26] 20.10 c1 c1 c1: IF A.162/19E THEN m ELSE i - - deleting Contact headers. Prerequisite A.163/15 - - PRACK response Prerequisite: A.164/14 - - Additional for 401 (Unauthorized) response Table A.253: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/15 - - PRACK response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.254: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.255: Void Prerequisite A.163/15 - - PRACK response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.256: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/15 - - PRACK response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) response Table A.257: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/15 - - PRACK response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.257A: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. Prerequisite A.163/15 - - PRACK response Prerequisite: A.164/27 - - Addition for 420 (Bad Extension) response Table A.258: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/15 - - PRACK response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.258A: Supported header fields within the PRACK response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.259: Void Prerequisite A.163/15 - - PRACK response Table A.260: Supported message bodies within the PRACK response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.10A PUBLISH method Prerequisite A.163/15A - - PUBLISH request Table A.260A: Supported header fields within the PUBLISH request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Contact [56B] 9.2 c28 c28 [56B] 9.2 c28 c29 2 Allow [26] 20.5 m m [26] 20.5 i i 3 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c29 c29 4 Authorization [26] 20.7 m m [26] 20.7 i i 5 Call-ID [26] 20.8 m m [26] 20.8 m m 6 Call-Info [26] 24.9 m m [26] 24.9 c4 c4 6A Cellular-Network-Info 7.2.15 n/a c72 7.2.15 n/a c73 6B Contact [70] 4 o o [70] 6 n/a n/a 7 Content-Disposition [26] 20.11 m m [26] 20.11 i i 8 Content-Encoding [26] 20.12 m m [26] 20.12 i i 9 Content-Language [26] 20.13 m m [26] 20.13 i i 10 Content-Length [26] 20.14 m m [26] 20.14 m m 11 Content-Type [26] 20.15 m m [26] 20.15 i i 12 CSeq [26] 20.16 m m [26] 20.16 m m 13 Date [26] 20.17 m m [26] 20.17 c2 c2 14 Event [70] 4, 6 m m [70] 4, 6 m m 15 Expires [26] 20.19, [70] 4, 5, 6 m m [26] 20.19, [70] 4, 5, 6 i i 15A Feature-Caps [190] c70 c70 [190] c70 c70 16 From [26] 20.20 m m [26] 20.20 m m 16A Geolocation [89] 4.1 c46 c46 [89] 4.1 c47 c47 16B Geolocation-Routing [89] 4.1 c46 c46 [89] 4.1 c47 c47 16C History-Info [66] 4.1 c32 c32 [66] 4.1 c32 c32 17 In-Reply-To [26] 20.21 m m [26] 20.21 i i 17A Max-Breadth [117] 5.8 c44 c44 [117] 5.8 c45 c45 18 Max-Forwards [26] 20.22 m m [26] 20.22 m m 19 MIME-Version [26] 20.24 m m [26] 20.24 i i 20 Organization [26] 20.25 m m [26] 20.25 c3 c3 21 P-Access-Network-Info [52] 4.4, [234] 2 c23 c23 [52] 4.4, [234] 2 c24 c24 22 P-Asserted-Identity [34] 9.1 c10 c10 [34] 9.1 c11 c11 22A P-Asserted-Service [121] 4.1 c38 c38 [121] 4.1 c39 c39 23 P-Called-Party-ID [52] 4.2 c14 c14 [52] 4.2 c15 c16 24 P-Charging-Function-Addresses [52] 4.5 c21 c21 [52] 4.5 c22 c22 25 P-Charging-Vector [52] 4.6 c19 c19 [52] 4.6 c20 c20 26 P-Preferred-Identity [34] 9.2 x c69 [34] 9.2 c9 c9 26A P-Preferred-Service [121] 4.2 x x [121] 4.2 c37 c37 26B P-Private-Network-Indication [134] c40 c40 [134] c40 c40 26C P-Profile-Key [97] 5 c34 c34 [97] 5 c35 c35 26D P-Served-User [133] 6 c41 c41 [133] 6 c41 c41 26E P-User-Database [82] 4 c33 c33 [82] 4 c33 c33 27 P-Visited-Network-ID [52] 4.3 c17 o [52] 4.3 c18 o 28 Priority [26] 20.26 m m [26] 20.26 i c50 29 Privacy [33] 4.2 c12 c12 [33] 4.2 c13 c13 30 Proxy-Authorization [26] 20.28 m m [26] 20.28 c7 c7 31 Proxy-Require [26] 20.29 m m [26] 20.29 m m 32 Reason [34A] 2 c8 c8 [34A] 2 c1 c1 33 Referred-By [59] 3 c30 c30 [59] 3 c31 c31 34 Reject-Contact [56B] 9.2 c27 c27 [56B] 9.2 c27 c28 34A Relayed-Charge 7.2.12 n/a c71 7.2.12 n/a c71 34B Reply-To [26] 20.31 m m [26] 20.31 i i 35 Request-Disposition [56B] 9.1 c27 c27 [56B] 9.1 c27 c27 36 Require [26] 20.32 m m [26] 20.32 c5 c5 36A Resource-Priority [116] 3.1 c36 c36 [116] 3.1 c36 c36 37 Route [26] 20.34 m m [26] 20.34 m m 38 Security-Client [48] 2.3.1 x x [48] 2.3.1 c25 c25 39 Security-Verify [48] 2.3.1 x x [48] 2.3.1 c25 c25 39A Session-ID [162] c48 c48 [162] c48 c48 40 SIP-If-Match [70] 11.3.2 m m [70] 11.3.2 i i 41 Subject [26] 20.36 m m [26] 20.36 i i 42 Supported [26] 20.37 m m [26] 20.37 c6 c6 43 Timestamp [26] 20.38 m m [26] 20.38 i i 44 To [26] 20.39 m m [26] 20.39 m m 45 User-Agent [26] 20.41 m m [26] 20.41 i i 46 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c4: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c7: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c8: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c9: IF A.162/30A OR A.162/30C THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c10: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c11: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c12: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c13: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c14: IF A.162/37 THEN m ELSE n/a - - the P-Called-Party-ID header extension. c15: IF A.162/37 THEN i ELSE n/a - - the P-Called-Party-ID header extension. c16: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a - - the P-Called-Party-ID header extension and P-CSCF or (I-CSCF or IBCF (THIG). c17: IF A.162/38 THEN m ELSE n/a - - the P-Visited-Network-ID header extension. c18: IF A.162/39 THEN m ELSE i - - reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c19: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c20: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c21: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c22: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c23: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c25: IF A.162/47 OR A.162/47A THEN o ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media (note 1). c27: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c28: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a - - caller preferences for the session initiation protocol, and S-CSCF. c29: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension (note 2). c30: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c31: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c32: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c33: IF A.162/60 THEN m ELSE n/a - - the P-User-Database private header extension. c34: IF A.162/66A THEN m ELSE n/a - - making the first query to the database in order to populate the P-Profile-Key header. c35: IF A.162/66B THEN m ELSE n/a - - using the information in the P-Profile-Key header. c36: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c37: IF A.162/84A THEN m ELSE n/a - - act as authentication entity within the trust domain for asserted service. c38: IF A.162/84 THEN m ELSE n/a - - SIP extension for the identification of services. c39: IF A.162/84 OR A.162/30B THEN m ELSE i - - SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network. c40: IF A.162/87 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c41: IF A.162/88 THEN m ELSE n/a - - the SIP P-Served-User private header. c44: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c45: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c46: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c47: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c48: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c69: IF A.162/30C THEN m ELSE x - - act as entity passing on identity transparently independent of trust domain. c50: IF A.162/115 THEN m ELSE i - - PSAP callback indicator. c70: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c71: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c72: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c73: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. NOTE 1: Support of this header in this method is dependent on the security mechanism and the security architecture which is implemented. NOTE 2: c29 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/15A - - PUBLISH request Table A.260B: Supported message bodies within the PUBLISH request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c1 [8ZE] n/a c1 2 application/poc-settings+xml [110] o c1 [110] o c1 3 application/pidf+xml [242] o c1 [242] o c1 c1: A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/11 OR A.3/13A THEN m ELSE n/a - - I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.260BA: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/15B - - PUBLISH response for all remaining status-codes Table A.260C: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Call-Info [26] 24.9 m m [26] 24.9 c3 c3 2A Cellular-Network-Info 7.2.15 n/a c23 7.2.15 n/a c24 3 Content-Disposition [26] 20.11 m m [26] 20.11 i i 4 Content-Encoding [26] 20.12 m m [26] 20.12 i i 5 Content-Language [26] 20.13 m m [26] 20.13 i i 6 Content-Length [26] 20.14 m m [26] 20.14 m m 7 Content-Type [26] 20.15 m m [26] 20.15 i i 8 CSeq [26] 20.16 m m [26] 20.16 m m 9 Date [26] 20.17 m m [26] 20.17 c1 c1 9A Expires [26] 20.19 [70] 4, 5, 6 m m [26] 20.19 [70] 4, 5, 6 i i 10 From [26] 20.20 m m [26] 20.20 m m 10A Geolocation-Error [89] 4.3 c19 c19 [89] 4.3 c20 c20 10B History-Info [66] 4.1 c16 c16 [66] 4.1 c16 c16 11 MIME-Version [26] 20.24 m m [26] 20.24 i i 12 Organization [26] 20.25 m m [26] 20.25 c2 c2 13 P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c13 c13 [52] 4.4, [52A] 4, [234] 2 c14 c14 14 P-Asserted-Identity [34] 9.1 c5 c5 [34] 9.1 c6 c6 15 P-Charging-Function-Addresses [52] 4.5, [52A] 4 c11 c11 [52] 4.5, [52A] 4 c12 c12 16 P-Charging-Vector [52] 4.6, [52A] 4 c9 c9 [52] 4.6, [52A] 4 c10 c10 17 P-Preferred-Identity [34] 9.2 x x [34] 9.2 c4 n/a 18 Privacy [33] 4.2 c7 c7 [33] 4.2 c8 c8 18A Relayed-Charge 7.2.12 n/a c22 7.2.12 n/a c22 19 Require [26] 20.32 m m [26] 20.32 c15 c15 20 Server [26] 20.35 m m [26] 20.35 i i 20A Session-ID [162] c21 c21 [162] c21 c21 21 Timestamp [26] 20.38 m m [26] 20.38 i i 22 To [26] 20.39 m m [26] 20.39 m m 23 User-Agent [26] 20.41 m m [26] 20.41 i i 24 Via [26] 20.42 m m [26] 20.42 m m 25 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c3: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c4: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c5: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c6: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c7: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c8: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c9: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c10: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c11: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c12: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c13: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c15: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c16: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c19: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c20: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c21: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c22: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c23: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c24: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/102 - - Additional for 2xx response Table A.260D: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Authentication-Info [26] 20.6 m m [26] 20.6 i i 3 Expires [26] 20.19, [70] 4, 5, 6 m m [26] 20.19, [70] 4, 5, 6 i i 3A Feature-Caps [190] c6 c6 [190] c6 c6 4 SIP-Etag [70] 11.3.1 m m [70] 11.3.1 i i 5 Supported [26] 20.37 m m [26] 20.37 i i c6: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/6 - - Additional for 200 (OK) response Table A.260DAA: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.260DA: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/103 OR A.164/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.260E: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Contact [26] 20.10 m m [26] 20.10 c1 c1 c1: IF A.162/19E THEN m ELSE i - - deleting Contact headers. Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/8 OR A.164/9 OR A.164/10 OR A.164/11 OR A.164/12 - - Additional for 401 (Unauthorized) response Table A.260F: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 5 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.260G: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.260H: Void Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.260I: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 5 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Table A.260IA: Void Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) response Table A.260J: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.260JA: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.260K: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.260L: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/29 - - Additional for 423 (Interval Too Brief) response Table A.260M: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Min-Expires [26] 20.23, [70] 5, 6 m m [26] 20.23, [70] 5, 6 i i Table A.260N: Void Prerequisite A.163/15B - - PUBLISH response Prerequisite: A.164/39 - - Additional for 489 (Bad Event) response Table A.260O: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Allow-Events [28] 8.2.2 m m [28] 8.2.2 i i Prerequisite A.163/17 - - PUBLISH response Prerequisite: A.164/46 - - Additional for 504 (Server Time-out) response Table A.260OA: Supported header fields within the PUBLISH response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.163/17 - - PUBLISH response Table A.260P: Supported message bodies within the PUBLISH response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.11 REFER method Prerequisite A.163/16 - - REFER request Table A.261: Supported header fields within the REFER request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept [26] 20.1 m m [26] 20.1 i i 0B Accept-Contact [56B] 9.2 c27 c27 [56B] 9.2 c27 c28 0C Accept-Encoding [26] 20.2 m m [26] 20.2 i i 1 Accept-Language [26] 20.3 m m [26] 20.3 i i 1AA Additional-Identity 7.2.20 n/a c77 7.2.20 n/a c77 1A Allow [26] 20.5 m m [26] 20.5 i i 2 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 3 Authorization [26] 20.7 m m [26] 20.7 i i 4 Call-ID [26] 20.8 m m [26] 20.8 m m 4A Cellular-Network-Info 7.2.15 n/a c75 7.2.15 n/a c76 5 Contact [26] 20.10 m m [26] 20.10 i i 5A Content-Disposition [26] 20.11 m m [26] 20.11 i i 5B Content-Encoding [26] 20.12 m m [26] 20.12 i i 5C Content-Language [26] 20.13 m m [26] 20.13 i i 6 Content-Length [26] 20.14 m m [26] 20.14 m m 7 Content-Type [26] 20.15 m m [26] 20.15 i i 8 CSeq [26] 20.16 m m [26] 20.16 m m 9 Date [26] 20.17 m m [26] 20.17 c2 c2 10 Expires [26] 20.19 m m [26] 20.19 i i 10A Feature-Caps [190] cj cj [190] cj cj 11 From [26] 20.20 m m [26] 20.20 m m 11A Geolocation [89] 4.1 c35 c35 [89] 4.1 c36 c36 11B Geolocation-Routing [89] 4.1 c35 c35 [89] 4.1 c36 c36 11C History-Info [66] 4.1 c31 c31 [66] 4.1 c31 c31 11D Max-Breadth [117] 5.8 c40 c40 [117] 5.8 c41 c41 12 Max-Forwards [26] 20.22 m m [26] 20.22 m m 13 MIME-Version [26] 20.24 m m [26] 20.24 i i 14 Organization [26] 20.25 m m [26] 20.25 c3 c3 14A P-Access-Network-Info [52] 4.4, [234] 2 c22 c22 [52] 4.4, [234] 2 c23 c23 14B P-Asserted-Identity [34] 9.1 c9 c9 [34] 9.1 c10 c10 14C P-Asserted-Service [121] 4.1 c38 c38 [121] 4.1 c39 c39 14D P-Called-Party-ID [52] 4.2, [52A] 4 c13 c13 [52] 4.2, [52A] 4 c14 c15 14E P-Charging-Function-Addresses [52] 4.5 c20 c20 [52] 4.5 c21 c21 14F P-Charging-Vector [52] 4.6 c18 c18 [52] 4.6 c19 c19 14H P-Preferred-Identity [34] 9.2 x c69 [34] 9.2 c8 c8 14I P-Preferred-Service [121] 4.2 x x [121] 4.2 c37 c37 14J P-Private-Network-Indication [134] c50 c50 [134] c50 c50 14K P-Profile-Key [97] 5 c33 c33 [97] 5 c34 c34 14L P-Served-User [133] 6 c53 c53 [133] 6 c53 c53 14M P-User-Database [82] 4 c32 c32 [82] 4 c32 c32 14N P-Visited-Network-ID [52] 4.3 c16 o [52] 4.3 c17 o 14O Privacy [33] 4.2 c11 c11 [33] 4.2 c12 c12 15 Proxy-Authorization [26] 20.28 m m [26] 20.28 c4 c4 16 Proxy-Require [26] 20.29 m m [26] 20.29 m m 16A Reason [34A] 2 c25 c25 [34A] 2 c26 c26 17 Record-Route [26] 20.30 m m [26] 20.30 c7 c7 17A Refer-Sub [173] 4 c54 c54 [173] 4 c55 c55 18 Refer-To [36] 3 c3 c3 [36] 3 c4 c4 18A Referred-By [59] 3 c29 c29 [59] 3 c30 c30 18B Reject-Contact [56B] 9.2 c27 c27 [56B] 9.2 c27 c28 18C Relayed-Charge 7.2.12 n/a c74 7.2.12 n/a c74 18D Request-Disposition [56B] 9.1 c27 c27 [56B] 9.1 c27 c27 19 Require [26] 20.32 m m [26] 20.32 c5 c5 19A Resource-Priority [116] 3.1 c47 c47 [116] 3.1 c47 c47 20 Route [26] 20.34 m m [26] 20.34 m m 20A Security-Client [48] 2.3.1 x x [48] 2.3.1 c24 c24 20B Security-Verify [48] 2.3.1 x x [48] 2.3.1 c24 c24 20C Session-ID [162] c70 c70 [162] c70 c70 21 Supported [26] 20.37 m m [26] 20.37 c6 c6 21A Target-Dialog [184] 7 c71 c71 [184] 7 c72 c72 22 Timestamp [26] 20.38 m m [26] 20.38 i i 23 To [26] 20.39 m m [26] 20.39 m m 23A Trigger-Consent [125] 5.11.2 c48 c48 [125] 5.11.2 c49 c49 24 User-Agent [26] 20.41 m m [26] 20.41 i i 25 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c4: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN m ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/30A OR A.162/30C THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c9: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c10: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c11: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c12: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c13: IF A.162/37 THEN m ELSE n/a - - the P-Called-Party-ID header extension. c14: IF A.162/37 THEN i ELSE n/a - - the P-Called-Party-ID header extension. c15: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a - - the P-Called-Party-ID header extension and P-CSCF or (I-CSCF or IBCF (THIG). c16: IF A.162/38 THEN m ELSE n/a - - the P-Visited-Network-ID header extension. c17: IF A.162/39 THEN m ELSE i - - reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c18: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c19: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c20: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c21: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c22: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c23: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/47 OR A.162/47A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c25: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c26: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c27: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c28: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a - - caller preferences for the session initiation protocol, and S-CSCF. c29: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c30: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c31: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c32: IF A.162/60 THEN m ELSE n/a - - the P-User-Database private header extension. c33: IF A.162/66A THEN m ELSE n/a - - making the first query to the database in order to populate the P-Profile-Key header. c34: IF A.162/66B THEN m ELSE n/a - - using the information in the P-Profile-Key header. c35: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c36: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c37: IF A.162/84A THEN m ELSE n/a - - act as authentication entity within the trust domain for asserted service. c38: IF A.162/84 THEN m ELSE n/a - - SIP extension for the identification of services. c39: IF A.162/84 OR A.162/30B THEN m ELSE i - - SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network. c40: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c41: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c47: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c48: IF A.162/85 THEN m ELSE n/a - - a framework for consent-based communications in SIP. c49: IF A.162/85 THEN i ELSE n/a - - a framework for consent-based communications in SIP. c50: IF A.162/87 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c53: IF A.162/88 THEN m ELSE n/a - - the SIP P-Served-User private header. c54: IF A.162/105 THEN m ELSE n/a - - suppression of session initiation protocol REFER method implicit subscription. c55: IF A.162/105 THEN i ELSE n/a - - suppression of session initiation protocol REFER method implicit subscription. c69: IF A.162/30C THEN m ELSE x - - act as entity passing on identity transparently independent of trust domain. c70: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c71: IF A.162/109 THEN m ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c72: IF A.162/109 THEN i ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c73: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c74: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c75: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c76: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c77: IF A.162/131 THEN o ELSE n/a - - the Additional-Identity header field extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/16 - - REFER request Table A.262: Supported message bodies within the REFER request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 application/vnd.3gpp.mid-call+xml [8M] D n/a i [8M] D n/a i 2 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c1 [8ZE] n/a i c1: A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/11 OR A.3/13A THEN m ELSE n/a - - I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). Table A.263: Void Prerequisite A.163/17 - - REFER response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.263A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/17 - - REFER response for all remaining status-codes Table A.264: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Cellular-Network-Info 7.2.15 n/a c22 7.2.15 n/a c23 1B Contact [26] 20.10 m m [26] 20.10 i i 1C Content-Disposition [26] 20.11 m m [26] 20.11 i i 2 Content-Encoding [26] 20.12 m m [26] 20.12 i i 3 Content-Language [26] 20.13 m m [26] 20.13 i i 4 Content-Length [26] 20.14 m m [26] 20.14 m m 5 Content-Type [26] 20.15 m m [26] 20.15 i i 6 CSeq [26] 20.16 m m [26] 20.16 m m 7 Date [26] 20.17 m m [26] 20.17 c1 c1 8 From [26] 20.20 m m [26] 20.20 m m 8A Geolocation-Error [89] 4.3 c16 c16 [89] 4.3 c17 c17 8B History-Info [66] 4.1 c15 c15 [66] 4.1 c15 c15 9 MIME-Version [26] 20.24 m m [26] 20.24 i i 10 Organization [26] 20.25 m m [26] 20.25 c2 c2 10A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c12 c12 [52] 4.4, [52A] 4, [234] 2 c13 c13 10B P-Asserted-Identity [34] 9.1 c4 c4 [34] 9.1 c5 c5 10C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c10 c10 [52] 4.5, [52A] 4 c11 c11 10D P-Charging-Vector [52] 4.6, [52A] 4 c8 c8 [52] 4.6, [52A] 4 c9 c9 10F P-Preferred-Identity [34] 9.2 x x [34] 9.2 c3 n/a 10G Privacy [33] 4.2 c6 c6 [33] 4.2 c7 c7 10H Relayed-Charge 7.2.12 n/a c21 7.2.12 n/a c21 10I Require [26] 20.32 m m [26] 20.32 c14 c14 10J Server [26] 20.35 m m [26] 20.35 i i 10K Session-ID [162] c20 c20 [162] c20 c20 11 Timestamp [26] 20.38 m m [26] 20.38 i i 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 m m [26] 20.41 i i 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c3: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c4: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c5: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c6: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c8: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c10: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c12: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c13: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c15: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c16: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c17: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c20: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c21: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c22: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c23: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. Prerequisite A.163/17 - - REFER response Prerequisite: A.164/102 - - Additional for 2xx response Table A.265: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c12 c12 [116] 3.2 c12 c12 1 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 2 Authentication-Info [26] 20.6 m m [26] 20.6 i i 3 Feature-Caps [190] c14 c14 [190] c14 c14 5 Record-Route [26] 20.30 m m [26] 20.30 c3 c3 6 Refer-Sub [173] 4 c4 c4 [173] 4 c5 c5 8 Supported [26] 20.37 m m [26] 20.37 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c3: IF A.162/15 THEN m ELSE i - - the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/105 THEN m ELSE n/a - - suppression of session initiation protocol REFER method implicit subscription. c5: IF A.162/105 THEN I ELSE n/a - - suppression of session initiation protocol REFER method implicit subscription. c12: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c14: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. Prerequisite A.163/17 - - REFER response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.265A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Table A.266: Void Prerequisite A.163/17 - - REFER response Prerequisite: A.164/8 OR A.164/9 OR A.164/10 OR A.164/11 OR A.164/12 - - Additional for 401 (Unauthorized) response Table A.267: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 10 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/17 - - REFER response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.268: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 6 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.269: Void Prerequisite A.163/17 - - REFER response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.270: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Table A.270A: Void Prerequisite A.163/17 - - REFER response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) response Table A.271: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/17 - - REFER response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.271A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. Prerequisite A.163/17 - - REFER response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.272: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 8 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/17 - - REFER response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.272A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Table A.273: Void Prerequisite A.163/17 - - REFER response Prerequisite: A.164/29H - - Additional for 470 (Consent Needed) response Table A.273A: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Permission-Missing [125] 5.9.3 m m [125] 5.9.3 m m Prerequisite A.163/17 - - REFER response Prerequisite: A.164/46 - - Additional for 504 (Server Time-out) response Table A.273AA: Supported header fields within the REFER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.163/17 - - REFER response Table A.274: Supported message bodies within the REFER response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.12 REGISTER method Prerequisite A.163/18 - - REGISTER request Table A.275: Supported header fields within the REGISTER request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i 3A Allow [26] 20.5 m m [26] 20.5 i i 4 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 5 Authorization [26] 20.7, [49] m m [26] 20.7, [49] i i 6 Call-ID [26] 20.8 m m [26] 20.8 m m 7 Call-Info [26] 20.9 m m [26] 20.9 c2 c2 7A Cellular-Network-Info 7.2.15 n/a c39 7.2.15 n/a c40 8 Contact [26] 20.10 m m [26] 20.10 i i 9 Content-Disposition [26] 20.11 m m [26] 20.11 i i 10 Content-Encoding [26] 20.12 m m [26] 20.12 i i 11 Content-Language [26] 20.13 m m [26] 20.13 i i 12 Content-Length [26] 20.14 m m [26] 20.14 m m 13 Content-Type [26] 20.15 m m [26] 20.15 i i 14 CSeq [26] 20.16 m m [26] 20.16 m m 15 Date [26] 20.17 m m [26] 20.17 m m 16 Expires [26] 20.19 m m [26] 20.19 i i 16A Feature-Caps [190] c36 c36 [190] c36 c36 17 From [26] 20.20 m m [26] 20.20 m m 17A Geolocation [89] 4.1 c26 c26 [89] 4.1 c27 c27 17B Geolocation-Routing [89] 4.1 c26 c26 [89] 4.1 c27 c27 17C History-Info [66] 4.1 c24 c24 [66] 4,1 c24 c24 17D Max-Breadth [117] 5.8 c31 c31 [117] 5.8 c32 c32 18 Max-Forwards [26] 20.22 m m [26] 20.22 m m 19 MIME-Version [26] 20.24 m m [26] 20.24 i i 20 Organization [26] 20.25 m m [26] 20.25 c3 c3 20A P-Access-Network-Info [52] 4.4, [234] 2 c16 c16 [52] 4.4, [234] 2 c17 c17 20B P-Charging-Function-Addresses [52] 4.5 c14 c14 [52] 4.5 c15 c15 20C P-Charging-Vector [52] 4.6 c12 c12 [52] 4.6 c13 c13 20E P-User-Database [82] 4 c25 c25 [82] 4 n/a n/a 20F P-Visited-Network-ID [52] 4.3 c10 c10 [52] 4.3 c11 c11 20G Path [35] 4.2 c6 c6 [35] 4.2 c6 c6 20H Privacy [33] 4.2 c8 c8 [33] 4.2 c9 c9 21 Proxy-Authorization [26] 20.28 m m [26] 20.28 c7 c7 22 Proxy-Require [26] 20.29 m m [26] 20.29 m m 22A Reason [34A] 2 c19 c19 [34A] 2 c20 c20 22B Recv-Info [25] 5.2.3 c33 c33 [25] 5.2.3 c34 c34 22C Referred-By [59] 3 c22 c22 [59] 3 c23 c23 22D Relayed-Charge 7.2.12 n/a c37 7.2.12 n/a c37 22E Request-Disposition [56B] 9.1 c21 c21 [56B] 9.1 c21 c21 23 Require [26] 20.32 m m [26] 20.32 c4 c4 23A Resource-Priority [116] 3.1 c28 c28 [116] 3.1 c28 c28 23B Resource-Share Subclause 4.15 n/a c38 Subclause 4.15 n/a c38 24 Route [26] 20.34 m m [26] 20.34 m m 24A Security-Client [48] 2.3.1 x x [48] 2.3.1 c18 c18 24B Security-Verify [48] 2.3.1 x x [48] 2.3.1 c18 c18 24C Session-ID [162] c35 c35 [162] c35 c35 25 Supported [26] 20.37 m m [26] 20.37 c5 c5 26 Timestamp [26] 20.38 m m [26] 20.38 i i 27 To [26] 20.39 m m [26] 20.39 m m 28 User-Agent [26] 20.41 m m [26] 20.41 i i 29 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c3: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c4: IF A.162/11 OR A.162/12 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c5: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c6: IF A.162/29 THEN m ELSE n/a - - PATH header support. c7: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c8: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c9: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c10: IF A.162/38 THEN m ELSE n/a - - the P-Visited-Network-ID header extension. c11: IF A.162/39 THEN m ELSE i - - reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c12: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c13: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c14: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c15: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c16: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c17: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c18: IF A.162/47 OR 162/47A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c19: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c20: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c21: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c22: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c23: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c24: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c25: IF A.162/60 THEN m ELSE n/a - - the P-User-Database private header extension. c26: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c27: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c28: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c31: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c32: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c33: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c34: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c35: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c36: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c37: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c38: IF A.162/122 THEN m ELSE n/a - - resource sharing. c39: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c40: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/18 - - REGISTER request Table A.276: Supported message bodies within the REGISTER request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 3GPP IM CN subsystem XML body subclause 7.6 n/a m subclause 7.6 n/a i Table A.277: Void Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.277A: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/19 - - REGISTER response for all remaining status-codes Table A.278: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Call-Info [26] 20.9 m m [26] 20.9 c2 c2 2 Content-Disposition [26] 20.11 m m [26] 20.11 i i 3 Content-Encoding [26] 20.12 m m [26] 20.12 i i 4 Content-Language [26] 20.13 m m [26] 20.13 i i 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 i i 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 m m [26] 20.17 m m 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c13 c13 [89] 4.3 c14 c14 9B History-Info [66] 4.1 c12 c12 [66] 4.1 c12 c12 10 MIME-Version [26] 20.24 m m [26] 20.24 i i 11 Organization [26] 20.25 m m [26] 20.25 c1 c1 11A P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c9 c9 [52] 4.4, [52A] 4, [234] 2 c10 c10 11B P-Charging-Function-Addresses [52] 4.5, [52A] 4 c7 c7 [52] 4.5, [52A] 4 c8 c8 11C P-Charging-Vector [52] 4.6, [52A] 4 c5 c5 [52] 4.6, [52A] 4 c6 c6 11E Privacy [33] 4.2 c3 c3 [33] 4.2 c4 c4 11F Relayed-Charge 7.2.12 n/a c18 7.2.12 n/a c18 11G Require [26] 20.32 m m [26] 20.32 c11 c11 11H Server [26] 20.35 m m [26] 20.35 i i 11I Session-ID [162] c17 c17 [162] c17 c17 12 Timestamp [26] 20.38 m m [26] 20.38 i i 13 To [26] 20.39 m m [26] 20.39 m m 13A User-Agent [26] 20.41 m m [26] 20.41 i i 14 Via [26] 20.42 m m [26] 20.42 m m 15 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c2: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c3: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c4: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c5: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c6: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c7: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c8: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c9: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c10: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c11: IF A.162/11 OR A.162/12 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c12: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c13: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c14: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c17: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c18: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/102 - - Additional for 2xx response Table A.279: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 1A Accept-Encoding [26] 20.2 m m [26] 20.2 i i 1B Accept-Language [26] 20.3 m m [26] 20.3 i i 1C Accept-Resource-Priority [116] 3.2 c11 c11 [116] 3.2 c11 c11 2 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 3 Authentication-Info [26] 20.6 m m [26] 20.6 i i 5 Contact [26] 20.10 m m [26] 20.10 i i 5A Feature-Caps [190] c16 c16 [190] c16 c16 5B Flow-Timer [92] 11 c12 c12 [92] 11 c13 c14 5C P-Associated-URI [52] 4.1 c8 c8 [52] 4.1 c9 c10 6 Path [35] 4.2 c3 c3 [35] 4.2 c4 c4 7 Security-Server Subclause 7.2A.7 n/a c15 Subclause 7.2A.7 n/a n/a 8 Service-Route [38] 5 c5 c5 [38] 5 c6 c7 9 Supported [26] 20.37 m m [26] 20.37 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c3: IF A.162/29 THEN m ELSE n/a - - Path extension support. c4: IF A.162/29 THEN i ELSE n/a - - Path extension support. c5: IF A.162/32 THEN m ELSE n/a - - Service-Route extension support. c6: IF A.162/32 THEN i ELSE n/a - - Service-Route extension support. c7: IF A.162/32 THEN (IF A.3/2 THEN m ELSE i) ELSE n/a - - Service-Route extension and P-CSCF. c8: IF A.162/36 THEN m ELSE n/a - - the P-Associated-URI extension. c9: IF A.162/36 THEN i ELSE n/a - - the P-Associated-URI extension. c10: IF A.162/36 AND A.3/2 THEN m ELSE IF A.162/36 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a - - the P-Associated-URI extension and P-CSCF or I-CSCF or IBCF (THIG). c11: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. c12: IF A.162/67 THEN m ELSE n/a - - managing client initiated transactions in SIP. c13: IF A.162/67 THEN m ELSE n/a - - managing client initiated transactions in SIP, P-CSCF, I-CSCF. c14: IF A.162/67 AND A.3/2 THEN m ELSE IF A.162/67 AND A.3/3 THEN i ELSE n/a - - managing client initiated transactions in SIP, P-CSCF, I-CSCF. c15: IF A.162/47A THEN m ELSE n/a - - mediasec header field parameter for marking security mechanisms related to media. c16: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.279A: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/103 OR A.164/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.280: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Contact [26] 20.10 m m [26] 20.10 c2 c2 c2: IF A.162/19E THEN m ELSE i - - deleting Contact headers. Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/14 - - Additional for 401 (Unauthorized) response Table A.281: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 6 Security-Server [48] 2 x c1 [48] 2 n/a n/a 10 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.282: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 6 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.283: Void Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.284: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 9 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) response Table A.285: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.285A: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80B THEN m ELSE n/a - - inclusion of CANCEL, BYE, REGISTER and PUBLISH in communications resource priority for the session initiation protocol. Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.286: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 8 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/17 THEN m ELSE i. Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.286A: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.163/19 - - REGISTER response Prerequisite: A.164/29 - - Additional for 423 (Interval Too Brief) response Table A.287: Supported header fields within the REGISTER response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Min-Expires [26] 20.23 m m [26] 20.23 i i Table A.288: Void Prerequisite A.163/19 - - REGISTER response Table A.289: Supported message bodies within the REGISTER response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.13 SUBSCRIBE method Prerequisite A.163/20 - - SUBSCRIBE request Table A.290: Supported header fields within the SUBSCRIBE request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 1A Accept-Contact [56B] 9.2 c27 c27 [56B] 9.2 c27 c28 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i 3A Allow [26] 20.5 m m [26] 20.5 i i 4 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 5 Authorization [26] 20.7 m m [26] 20.7 i i 6 Call-ID [26] 20.8 m m [26] 20.8 m m 6A Call-Info [26] 20.9 m m [26] 20.9 c73 c73 6B Cellular-Network-Info 7.2.15 n/a c76 7.2.15 n/a c77 6C Contact [26] 20.10 m m [26] 20.10 i i 7 Content-Disposition [26] 20.11 m m [26] 20.11 i i 8 Content-Encoding [26] 20.12 m m [26] 20.12 i i 9 Content-Language [26] 20.13 m m [26] 20.13 i i 10 Content-Length [26] 20.14 m m [26] 20.14 m m 11 Content-Type [26] 20.15 m m [26] 20.15 i i 12 CSeq [26] 20.16 m m [26] 20.16 m m 13 Date [26] 20.17 m m [26] 20.17 c2 c2 14 Event [28] 8.2.1 m m [28] 8.2.1 m m 15 Expires [26] 20.19 m m [26] 20.19 i i 15A Feature-Caps [190] c74 c74 [190] c74 c74 16 From [26] 20.20 m m [26] 20.20 m m 16A Geolocation [89] 4.1 c35 c35 [89] 4.1 c36 c36 16B Geolocation-Routing [89] 4.1 c35 c35 [89] 4.1 c36 c36 16C History-Info [66] 4.1 c31 c31 [66] 4.1 c31 c31 16D Max-Breadth [117] 5.8 c47 c47 [117] 5.8 c48 c48 17 Max-Forwards [26] 20.22 m m [26] 20.22 m m 18 MIME-Version [26] 20.24 m m [26] 20.24 i i 18A Organization [26] 20.25 m m [26] 20.25 c3 c3 18B P-Access-Network-Info [52] 4.4, [234] 2 c22 c22 [52] 4.4, [234] 2 c23 c23 18C P-Asserted-Identity [34] 9.1 c9 c9 [34] 9.1 c10 c10 18D P-Asserted-Service [121] 4.1 c39 c39 [121] 4.1 c40 c40 18E P-Called-Party-ID [52] 4.2 c13 c13 [52] 4.2 c14 c15 18F P-Charging-Function-Addresses [52] 4.5 c20 c20 [52] 4.5 c21 c21 18G P-Charging-Vector [52] 4.6 c18 c18 [52] 4.6 c19 c19 18I P-Preferred-Identity [34] 9.2 x c69 [34] 9.2 c8 c8 18J P-Preferred-Service [121] 4.2 x x [121] 4.2 c38 c38 18K P-Private-Network-Indication [134] c43 c43 [134] c43 c43 18L P-Profile-Key [97] 5 c33 c33 [97] 5 c34 c34 18M P-Served-User [133] 6 c44 c44 [133] 6 c44 c44 18N P-User-Database [82] 4 c32 c32 [82] 4 c32 c32 18O P-Visited-Network-ID [52] 4.3 c16 o [52] 4.3 c17 o 18P Priority [26] 20.26 m m [26] 20.26 i c50 18Q Privacy [33] 4.2 c11 c11 [33] 4.2 c12 c12 19 Proxy-Authorization [26] 20.28 m m [26] 20.28 c4 c4 20 Proxy-Require [26] 20.29 m m [26] 20.29 m m 20A Reason [34A] 2 c25 c25 [34A] 2 c26 c26 21 Record-Route [26] 20.30 m m [26] 20.30 c7 c7 21A Referred-By [59] 3 c29 c29 [59] 3 c30 c30 21B Reject-Contact [56B] 9.2 c27 c27 [56B] 9.2 c27 c28 21C Relayed-Charge 7.2.12 n/a c75 7.2.12 n/a c75 21D Request-Disposition [56B] 9.1 c27 c27 [56B] 9.1 c27 c27 22 Require [26] 20.32 m m [26] 20.32 c5 c5 22A Resource-Priority [116] 3.1 c37 c37 [116] 3.1 c37 c37 23 Route [26] 20.34 m m [26] 20.34 m m 23A Security-Client [48] 2.3.1 x x [48] 2.3.1 c24 c24 23B Security-Verify [48] 2.3.1 x x [48] 2.3.1 c24 c24 23C Session-ID [162] c70 c70 [162] c70 c70 24 Supported [26] 20.37 m m [26] 20.37 c6 c6 24A Target-Dialog [184] 7 c71 c71 [184] 7 c72 c72 25 Timestamp [26] 20.38 m m [26] 20.38 i i 26 To [26] 20.39 m m [26] 20.39 m m 26A Trigger-Consent [125] 5.11.2 c41 c41 [125] 5.11.2 c42 c42 27 User-Agent [26] 20.41 m m [26] 20.41 i i 28 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c4: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN m ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/30A OR A.162/30C THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity, act as entity passing on identity transparently independent of trust domain. c9: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c10: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c11: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c12: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c13: IF A.162/37 THEN m ELSE n/a - - the P-Called-Party-ID header extension. c14: IF A.162/37 THEN i ELSE n/a - - the P-Called-Party-ID header extension. c15: IF A.162/37 AND A.3/2 THEN m ELSE IF A.162/37 AND (A.3/3 OR A.3/9A) THEN i ELSE n/a - - the P-Called-Party-ID header extension and P-CSCF or I-CSCF or IBCF (THIG). c16: IF A.162/38 THEN m ELSE n/a - - the P-Visited-Network-ID header extension. c17: IF A.162/39 THEN m ELSE i - - reading, or deleting the P-Visited-Network-ID header before proxying the request or response. c18: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c19: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c20: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c21: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c22: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c23: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c24: IF A.162/47 OR A.162/47A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c25: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c26: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c27: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c28: IF A.162/50 AND A.4/3 THEN m ELSE IF A.162/50 AND NOT A.4/3 THEN i ELSE n/a - - caller preferences for the session initiation protocol, and S-CSCF. c29: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c30: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c31: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c32: IF A.162/60 THEN m ELSE n/a - - the P-User-Database private header extension. c33: IF A.162/66A THEN m ELSE n/a - - making the first query to the database in order to populate the P-Profile-Key header. c34: IF A.162/66B THEN m ELSE n/a - - using the information in the P-Profile-Key header. c35: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c36: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c37: IF A.162/80A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c38: IF A.162/84A THEN m ELSE n/a - - act as authentication entity within the trust domain for asserted service. c39: IF A.162/84 THEN m ELSE n/a - - SIP extension for the identification of services. c40: IF A.162/84 OR A.162/30B THEN m ELSE i - - SIP extension for the identification of services or subsequent entity within trust network that can route outside the trust network. c41: IF A.162/85 THEN m ELSE n/a - - a framework for consent-based communications in SIP. c42: IF A.162/85 THEN i ELSE n/a - - a framework for consent-based communications in SIP. c43: IF A.162/87 THEN m ELSE n/a - - the SIP P-Private-Network-Indication private-header (P-Header). c44 IF A.162/88 THEN m ELSE n/a - - the SIP P-Served-User private header. c47: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c48: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c50: IF A.162/115 THEN m ELSE i - - PSAP callback indicator. c69: IF A.162/30C THEN m ELSE x - - act as entity passing on identity transparently independent of trust domain. c70: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c71: IF A.162/109 THEN m ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c72: IF A.162/109 THEN i ELSE n/a - - request authorization through dialog Identification in the session initiation protocol. c73: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header field. c74: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c75: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c76: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c77: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/20 - - SUBSCRIBE request Table A.291: Supported message bodies within the SUBSCRIBE request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 application/vnd.3gpp.mcptt-info+xml [8ZE] n/a c1 [8ZE] n/a i 2 application/simple-filter+xml [243] o c1 [243] n/a i c1: A.3/3 OR A.3/4 OR A.3/5 OR A.3/7C OR A.3/9A OR A.3/10 OR A.3/11 OR A.3/13A THEN m ELSE n/a - - I-CSCF, S-CSCF, BGCF, AS acting as proxy, IBCF (THIG), additional routeing functionality, E-CSCF, ISC gateway function (THIG). Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.291A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/21 - - SUBSCRIBE response for all remaining status-codes Table A.292: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Call-Info [26] 20.9 m m [26] 20.9 c23 c23 1B Cellular-Network-Info 7.2.15 n/a c25 7.2.15 n/a c26 2 Content-Disposition [26] 20.11 m m [26] 20.11 i i 3 Content-Encoding [26] 20.12 m m [26] 20.12 i i 4 Content-Language [26] 20.13 m m [26] 20.13 i i 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 i i 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 m m [26] 20.17 c1 c1 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c20 c20 [89] 4.3 c21 c21 9B History-Info [66] 4.1 c15 c15 [66] 4.1 c15 c15 10 MIME-Version [26] 20.24 m m [26] 20.24 i i 10A Organization [26] 20.25 m m [26] 20.25 c2 c2 10B P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c12 c12 [52] 4.4, [52A] 4, [234] 2 c13 c13 10C P-Asserted-Identity [34] 9.1 c4 c4 [34] 9.1 c5 c5 10D P-Charging-Function-Addresses [52] 4.5, [52A] 4 c10 c10 [52] 4.5, [52A] 4 c11 c11 10E P-Charging-Vector [52] 4.6, [52A] 4 c8 c8 [52] 4.6, [52A] 4 c9 c9 10G P-Preferred-Identity [34] 9.2 x x [34] 9.2 c3 n/a 10H Privacy [33] 4.2 c6 c6 [33] 4.2 c7 c7 10I Relayed-Charge 7.2.12 n/a c24 7.2.12 n/a c24 10J Require [26] 20.32 m m [26] 20.32 c14 c14 10K Server [26] 20.35 m m [26] 20.35 i i 10L Session-ID [162] c22 c22 [162] c22 c22 11 Timestamp [26] 20.38 m m [26] 20.38 i i 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 m m [26] 20.41 i i 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c3: IF A.162/30A THEN m ELSE n/a - - act as first entity within the trust domain for asserted identity. c4: IF A.162/30 THEN m ELSE n/a - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks. c5: IF A.162/30A or A.162/30B THEN m ELSE i - - extensions to the Session Initiation Protocol (SIP) for asserted identity within trusted networks or subsequent entity within trust network that can route outside the trust network. c6: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c7: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c8: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c9: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c10: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c11: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c12: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c13: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c14: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c15: IF A.162/57 THEN m ELSE n/a - - an extension to the session initiation protocol for request history information. c16: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c17: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c20: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c21: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c22: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c23: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header field. c24: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c25: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c26: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/102 - - Additional for 2xx response Table A.293: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept-Resource-Priority [116] 3.2 c4 c4 [116] 3.2 c4 c4 0B Allow-Events [28] 8.2.2 m m [28] 8.2.2 i i 1 Authentication-Info [26] 20.6 m m [26] 20.6 i i 1A Contact [26] 20.10 m m [26] 20.10 i i 2 Expires [26] 20.19 m m [26] 20.19 i i 2A Feature-Caps [190] c6 c6 [190] c6 c6 3 Record-Route [26] 20.30 m m [26] 20.30 c3 c3 6 Supported [26] 20.37 m m [26] 20.37 i i c3: IF A.162/15 THEN m ELSE i - - the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/80A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. c6: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.293A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/103 OR A.164/35 - - Additional for 3xx or 485 (Ambiguous) response Table A.294: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Contact [26] 20.10 m m [26] 20.10 c1 c1 c1: IF A.162/19E THEN m ELSE i - - deleting Contact headers. Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/14 - - Additional for 401 (Unauthorized) response Table A.295: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480 (Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.296: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.297: Void Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.298: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Table A.298A: Void Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) response Table A.299: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.299A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80A THEN m ELSE n/a - - inclusion of MESSAGE, SUBSCRIBE, NOTIFY in communications resource priority for the session initiation protocol. Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.300: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.300A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/29 - - Additional for 423 (Interval Too Brief) response Table A.301: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Min-Expires [26] 20.23 m m [26] 20.23 i i Table A.302: Void Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/29H - - Additional for 470 (Consent Needed) response Table A.302A: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Permission-Missing [125] 5.9.3 m m [125] 5.9.3 m m Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/39 - - Additional for 489 (Bad Event) response Table A.303: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Table A.303A: Void Prerequisite A.163/21 - - SUBSCRIBE response Prerequisite: A.164/46 - - Additional for 504 (Server Time-out) response Table A.303B: Supported header fields within the SUBSCRIBE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Restoration-Info subclause 7.2.11 n/a c1 subclause 7.2.11 n/a n/a c1: IF A.4/110 THEN o ELSE n/a - - HSS based P-CSCF restoration. Prerequisite A.163/21 - - SUBSCRIBE response Table A.304: Supported message bodies within the SUBSCRIBE response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.2.2.4.14 UPDATE method Prerequisite A.163/22 - - UPDATE request Table A.305: Supported header fields within the UPDATE request Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 1A Accept-Contact [56B] 9.2 c21 c21 [56B] 9.2 c22 c22 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i 4 Allow [26] 20.5 m m [26] 20.5 i i 5 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 6 Authorization [26] 20.7 m m [26] 20.7 i i 7 Call-ID [26] 20.8 m m [26] 20.8 m m 8 Call-Info [26] 20.9 m m [26] 20.9 c8 c8 8A Cellular-Network-Info 7.2.15 n/a c52 7.2.15 n/a c53 9 Contact [26] 20.10 m m [26] 20.10 i i 10 Content-Disposition [26] 20.11 m m [26] 20.11 c4 c4 11 Content-Encoding [26] 20.12 m m [26] 20.12 c4 c4 12 Content-Language [26] 20.13 m m [26] 20.13 c4 c4 13 Content-Length [26] 20.14 m m [26] 20.14 m m 14 Content-Type [26] 20.15 m m [26] 20.15 c4 c4 15 CSeq [26] 20.16 m m [26] 20.16 m m 16 Date [26] 20.17 m m [26] 20.17 c2 c2 16A Feature-Caps [190] c49 c49 [190] c49 c49 17 From [26] 20.20 m m [26] 20.20 m m 17A Geolocation [89] 4.1 c26 c26 [89] 4.1 c27 c27 17B Geolocation-Routing [89] 4.1 c26 c26 [89] 4.1 c27 c27 17C Max-Breadth [117] 5.8 c32 c32 [117] 5.8 c33 c33 18 Max-Forwards [26] 20.22 m m [26] 20.22 m m 19 MIME-Version [26] 20.24 m m [26] 20.24 i c4 19A Min-SE [58] 5 c23 c23 [58] 5 c23 c23 20 Organization [26] 20.25 m m [26] 20.25 c3 c3 20A P-Access-Network-Info [52] 4.4, [234] 2 c16 c16 [52] 4.4, [234] 2 c17 c17 20B P-Charging-Function-Addresses [52] 4.5 c14 c14 [52] 4.5 c15 c15 20C P-Charging-Vector [52] 4.6 c12 c12 [52] 4.6 c13 c13 20E P-Early-Media [109] 8 o c28 [109] 8 o c28 20EA Priority-Share Subclause 7.2.16 n/a c54 Subclause 7.2.16 n/a c54 20F Privacy [33] 4.2 c10 c10 [33] 4.2 c11 c11 21 Proxy-Authorization [26] 20.28 m m [26] 20.28 c9 c9 22 Proxy-Require [26] 20.29 m m [26] 20.29 m m 22A Reason [34A] 2 c19 c19 [34A] 2 c20 c20 23 Record-Route [26] 20.30 m m [26] 20.30 c7 c7 23A Recv-Info [25] 5.2.3 c34 c34 [25] 5.2.3 c35 c35 23B Referred-By [59] 3 c24 c24 [59] 3 c25 c25 23C Reject-Contact [56B] 9.2 c21 c21 [56B] 9.2 c22 c22 23D Relayed-Charge 7.2.12 n/a c50 7.2.12 n/a c50 23E Request-Disposition [56B] 9.1 c21 c21 [56B] 9.1 c22 c22 24 Require [26] 20.32 m m [26] 20.32 c5 c5 24A Resource-Priority [116] 3.1 c47 c47 [116] 3.1 c47 c47 24B Resource-Share Subclause 4.15 n/a c51 Subclause 4.15 n/a c51 25 Route [26] 20.34 m m [26] 20.34 m m 25A Security-Client [48] 2.3.1 x x [48] 2.3.1 c18 c18 25B Security-Verify [48] 2.3.1 x x [48] 2.3.1 c18 c18 25C Session-Expires [58] 4 c23 c23 [58] 4 c23 c23 25D Session-ID [162] c48 c48 [162] c48 c48 26 Supported [26] 20.37 m m [26] 20.37 c6 c6 27 Timestamp [26] 20.38 m m [26] 20.38 i i 28 To [26] 20.39 m m [26] 20.39 m m 29 User-Agent [26] 20.41 m m [26] 20.41 i i 30 Via [26] 20.42 m m [26] 20.42 m m c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c2: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c3: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c4: IF A.3/2 OR A.3/4 THEN m ELSE i - - P-CSCF or S-CSCF. c5: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c6: IF A.162/16 THEN m ELSE i - - reading the contents of the Supported header before proxying the response. c7: IF A.162/14 THEN o ELSE i - - the requirement to be able to insert itself in the subsequent transactions in a dialog. c8: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c9: IF A.162/8A THEN m ELSE i - - authentication between UA and proxy. c10: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c11: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c12: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c13: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c14: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c15: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c16: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c17: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c18: IF A.162/47 OR A.162/47A THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol or mediasec header field parameter for marking security mechanisms related to media. c19: IF A.162/48 THEN m ELSE n/a - - the Reason header field for the session initiation protocol. c20: IF A.162/48 THEN i ELSE n/a - - the Reason header field for the session initiation protocol. c21: IF A.162/50 THEN m ELSE n/a - - caller preferences for the session initiation protocol. c22: IF A.162/50 THEN i ELSE n/a - - caller preferences for the session initiation protocol. c23: IF A.162/52 THEN m ELSE n/a - - the SIP session timer. c24: IF A.162/53 THEN i ELSE n/a - - the SIP Referred-By mechanism. c25: IF A.162/53 THEN m ELSE n/a - - the SIP Referred-By mechanism. c26: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c27: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c28: IF A.162/76 THEN m ELSE n/a - - the SIP P-Early-Media private header extension for authorization of early media. c32: IF A.162/81 THEN m ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies. c33: IF A.162/81 AND A.162/6 THEN m ELSE IF A.162/81 AND NOT A.162/6 THEN i ELSE n/a - - addressing an amplification vulnerability in session initiation protocol forking proxies, forking of initial requests. c34: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c35: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c47: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c48: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c49: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c50: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c51: IF A.162/122 THEN o ELSE n/a - - resource sharing. c52: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c53: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c54: IF A.162/124 THEN o ELSE n/a - - priority sharing. NOTE: c1 refers to the UA role major capability as this is the case of a proxy that also acts as a UA specifically for SUBSCRIBE and NOTIFY. Prerequisite A.163/22 - - UPDATE request Table A.306: Supported message bodies within the UPDATE request Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/1 - - Additional for 100 (Trying) response Table A.306A: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Call-ID [26] 20.8 m m [26] 20.8 m m 2 Content-Length [26] 20.14 m m [26] 20.14 m m 3 CSeq [26] 20.16 m m [26] 20.16 m m 4 Date [26] 20.17 c1 c1 [26] 20.17 c2 c2 5 From [26] 20.20 m m [26] 20.20 m m 6 To [26] 20.39 m m [26] 20.39 m m 7 Via [26] 20.42 m m [26] 20.42 m m c1: IF (A.162/9 AND A.162/5) OR A.162/4 THEN m ELSE n/a - - stateful proxy behaviour that inserts date, or stateless proxies. c2: IF A.162/4 THEN i ELSE m - - Stateless proxy passes on. Prerequisite A.163/22 - - UPDATE response for all remaining status-codes Table A.307: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Allow [26] 20.5 m m [26] 20.5 i i 1 Call-ID [26] 20.8 m m [26] 20.8 m m 1A Call-Info [26] 20.9 m m [26] 20.9 c4 c4 1B Cellular-Network-Info 7.2.15 n/a c22 7.2.15 n/a c23 1C Contact [26] 20.10 m m [26] 20.10 i i 2 Content-Disposition [26] 20.11 m m [26] 20.11 i c3 3 Content-Encoding [26] 20.12 m m [26] 20.12 i c3 4 Content-Language [26] 20.13 m m [26] 20.13 i c3 5 Content-Length [26] 20.14 m m [26] 20.14 m m 6 Content-Type [26] 20.15 m m [26] 20.15 i c3 7 CSeq [26] 20.16 m m [26] 20.16 m m 8 Date [26] 20.17 m m [26] 20.17 c1 c1 9 From [26] 20.20 m m [26] 20.20 m m 9A Geolocation-Error [89] 4.3 c14 c14 [89] 4.3 c15 c15 10 MIME-Version [26] 20.24 m m [26] 20.24 i c3 10A Organization [26] 20.25 m m [26] 20.25 c2 c2 10B P-Access-Network-Info [52] 4.4, [52A] 4, [234] 2 c11 c11 [52] 4.4, [52A] 4, [234] 2 c12 c12 10C P-Charging-Function-Addresses [52] 4.5, [52A] 4 c9 c9 [52] 4.5, [52A] 4 c10 c10 10D P-Charging-Vector [52] 4.6, [52A] 4 c7 c7 [52] 4.6, [52A] 4 c8 c8 10F Privacy [33] 4.2 c5 c5 [33] 4.2 c6 c6 10G Recv-Info [25] 5.2.3 c18 c18 [25] 5.2.3 c19 c19 10H Relayed-Charge 7.2.12 n/a c21 7.2.12 n/a c21 10I Require [26] 20.32 m m [26] 20.32 c13 c13 10J Server [26] 20.35 m m [26] 20.35 i i 10K Session-ID [162] c20 c20 [162] c20 c20 11 Timestamp [26] 20.38 m m [26] 20.38 i i 12 To [26] 20.39 m m [26] 20.39 m m 12A User-Agent [26] 20.41 m m [26] 20.41 i i 13 Via [26] 20.42 m m [26] 20.42 m m 14 Warning [26] 20.43 m m [26] 20.43 i i c1: IF A.162/9 THEN m ELSE i - - insertion of date in requests and responses. c2: IF A.162/19A OR A.162/19B THEN m ELSE i - - reading, adding or concatenating the Organization header. c3: IF A.3/2 OR A.3/4 THEN m ELSE i - - P-CSCF or S-CSCF. c4: IF A.162/19C OR A.162/19D THEN m ELSE i - - reading, adding or concatenating the Call-Info header. c5: IF A.162/31 THEN m ELSE n/a - - a privacy mechanism for the Session Initiation Protocol (SIP). c6: IF A.162/31D OR A.162/31G THEN m ELSE IF A.162/31C THEN i ELSE n/a - - application of the privacy option "header" or application of the privacy option "id" or passing on of the Privacy header transparently. c7: IF A.162/45 THEN m ELSE n/a - - the P-Charging-Vector header extension. c8: IF A.162/46 THEN m ELSE IF A.162/45 THEN i ELSE n/a - - adding, deleting, reading or modifying the P-Charging-Vector header before proxying the request or response or the P-Charging-Vector header extension. c9: IF A.162/44 THEN m ELSE n/a - - the P-Charging-Function-Addresses header extension. c10: IF A.162/44A THEN m ELSE IF A.162/44 THEN i ELSE n/a - - adding, deleting or reading the P-Charging-Function-Addresses header before proxying the request or response, or the P-Charging-Function-Addresses header extension. c11: IF A.162/43 THEN x ELSE IF A.162/41 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c12: IF A.162/43 THEN m ELSE IF A.162/41 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the P-Access-Network-Info header extension. c13: IF A.162/11 OR A.162/13 THEN m ELSE i - - reading the contents of the Require header before proxying the request or response or adding or modifying the contents of the Require header before proxying the request or response for methods other than REGISTER. c14: IF A.162/70 THEN m ELSE n/a - - SIP location conveyance. c15: IF A.162/70A THEN m ELSE IF A.162/70B THEN i ELSE n/a - - addition or modification of location in a SIP method, passes on locations in SIP method without modification. c18: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c19: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c20: IF A.162/101 THEN m ELSE n/a - - the Session-ID header. c21: IF A.162/121 THEN m ELSE n/a - - the Relayed-Charge header field extension. c22: IF A.162/43 THEN x ELSE IF A.162/123 THEN m ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. c23: IF A.162/43 THEN m ELSE IF A.162/123 THEN i ELSE n/a - - act as subsequent entity within trust network for access network information that can route outside the trust network, the Cellular-Network-Info header extension. Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/102 - - Additional for 2xx response Table A.308: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 0A Accept [26] 20.1 m m [26] 20.1 i i 0B Accept-Encoding [26] 20.2 m m [26] 20.2 i i 0C Accept-Language [26] 20.3 m m [26] 20.3 i i 0D Accept-Resource-Priority [116] 3.2 c12 c12 [116] 3.2 c12 c12 1 Allow-Events [28] 8.2.2 m m [28] 8.2.2 c1 c1 2 Authentication-Info [26] 20.6 m m [26] 20.6 i i 3 Contact [26] 20.10 m m [26] 20.10 i i 3A Feature-Caps [190] c14 c14 [190] c14 c14 3B P-Early-Media [109] 8 o c10 [109] 8 o c11 3BA Priority-Share Subclause 7.2.16 n/a c16 Subclause 7.2.16 n/a c16 3C Record-Route [26] 20.30 m m [26] 20.30 c3 c3 3D Recv-Info [25] 5.2.3 c5 c5 [25] 5.2.3 c6 c6 3E Resource-Share Subclause 4.15 n/a c15 Subclause 4.15 n/a c15 4 Session-Expires [58] 4 c4 c4 [58] 4 c4 c4 6 Supported [26] 20.37 m m [26] 20.37 i i c1: IF A.4/20 THEN m ELSE i - - SIP specific event notification extension. c3: IF A.162/15 THEN o ELSE i - - the requirement to be able to use separate URIs in the upstream direction and downstream direction when record routeing. c4: IF A.162/52 THEN m ELSE n/a - - the SIP session timer. c5: IF A.162/20 THEN m ELSE n/a - - SIP INFO method and package framework. c6: IF A.162/20 THEN i ELSE n/a - - SIP INFO method and package framework. c10: IF A.162/76 THEN m ELSE n/a - - the SIP P-Early-Media private header extension for authorization of early media. c11: IF A.162/76 THEN (IF A.3/2 THEN m ELSE i) ELSE n/a - - P-CSCF, using the information in the P-Early-Media header. c12: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. c14: IF A.162/110 THEN m ELSE n/a - - indication of features supported by proxy. c15: IF A.162/122 THEN o ELSE n/a - - resource sharing. c16: IF A.162/124 THEN o ELSE n/a - - priority sharing. Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/103 OR A.164/104 OR A.164/105 OR A.164/106 - - Additional for 3xx – 6xx response Table A.308A: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Error-Info [26] 20.18 m m [26] 20.18 i i 2 Response-Source 7.2.17 n/a c1 7.2.17 n/a c1 c1: IF A.162/125 THEN o ELSE n/a - - use of the Response-Source header field in SIP error responses? Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/103 or A.164/35 - - Additional for 3xx, 485 (Ambiguous) response Table A.309: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 2 Contact [26] 20.10 m m [26] 20.10 c1 c1 c1: IF A.162/19E THEN m ELSE i - - deleting Contact headers. Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/14 - - Additional for 401 (Unauthorized) response Table A.309A: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 6 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/17 OR A.164/23 OR A.164/30 OR A.164/36 OR A.164/42 OR A.164/45 OR A.164/50 OR A.164/51 - - Additional for 404 (Not Found), 413 (Request Entity Too Large), 480(Temporarily not available), 486 (Busy Here), 500 (Internal Server Error), 503 (Service Unavailable), 600 (Busy Everywhere), 603 (Decline) response Table A.310: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 5 Retry-After [26] 20.33 m m [26] 20.33 i i Table A.311: Void Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/20 - - Additional for 407 (Proxy Authentication Required) response Table A.312: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 4 Proxy-Authenticate [26] 20.27 m m [26] 20.27 m m 8 WWW-Authenticate [26] 20.44 m m [26] 20.44 i i Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/25 - - Additional for 415 (Unsupported Media Type) response Table A.313: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept [26] 20.1 m m [26] 20.1 i i 2 Accept-Encoding [26] 20.2 m m [26] 20.2 i i 3 Accept-Language [26] 20.3 m m [26] 20.3 i i Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/26A - - Additional for 417 (Unknown Resource-Priority) response Table A.313A: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Accept-Resource-Priority [116] 3.2 c1 c1 [116] 3.2 c1 c1 c1: IF A.162/80 THEN m ELSE n/a - - communications resource priority for the session initiation protocol. Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/27 - - Additional for 420 (Bad Extension) response Table A.314: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 7 Unsupported [26] 20.40 m m [26] 20.40 c3 c3 c3: IF A.162/18 THEN m ELSE i - - reading the contents of the Unsupported header before proxying the 420 response to a method other than REGISTER. Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/28 OR A.164/41A - - Additional for 421 (Extension Required), 494 (Security Agreement Required) response Table A.314A: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 3 Security-Server [48] 2 c1 c1 [48] 2 n/a n/a c1: IF A.162/47 THEN m ELSE n/a - - security mechanism agreement for the session initiation protocol. Prerequisite A.163/23 - - UPDATE response Prerequisite: A.164/28A - - Additional for 422 (Session Interval Too Small) response Table A.314B: Supported header fields within the UPDATE response Item Header field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 Min-SE [58] 5 c1 c1 [58] 5 c1 c1 c1: IF A.162/52 THEN m ELSE n/a - - the SIP session timer. Table A.315: Void Prerequisite A.163/23 - - UPDATE response Table A.316: Supported message bodies within the UPDATE response Item Header Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 A.3 Profile definition for the Session Description Protocol as used in the present document A.3.1 Introduction Void. A.3.2 User agent role This subclause contains the ICS proforma tables related to the user agent role. They need to be completed only for UA implementations. Prerequisite: A.2/1 -- user agent role A.3.2.1 Major capabilities Table A.317: Major capabilities Item Does the implementation support Reference RFC status Profile status Capabilities within main protocol Extensions 22 integration of resource management and SIP? [30] [64] o c14 23 grouping of media lines? [53] c3 c3 24 mapping of media streams to resource reservation flows? [54] o c1 25 SDP bandwidth modifiers for RTCP bandwidth? [56] o o (NOTE 1) 26 TCP-based media transport in the session description protocol? [83] o c2 27 interactive connectivity establishment? [289], [290] o c4 28 session description protocol format for binary floor control protocol streams? [108] o o 29 extended RTP profile for real-time transport control protocol (RTCP)-based feedback (RTP/AVPF)? [135] o c5 30 SDP capability negotiation? [137] o c6 31 Session Description Protocol (SDP) extension for setting up audio media streams over circuit-switched bearers in the Public Switched Telephone Network (PSTN)? [155] o c7 32 miscellaneous capabilities negotiation in the Session Description Protocol (SDP)? [156] o c7 33 transport independent bandwidth modifier for the Session Description Protocol? [152] o c8 34 Secure Real-time Transport Protocol (SRTP)? [169] o c15 35 MIKEY-TICKET? [170] o c10 36 SDES? [168] o c9 37 end-to-access-edge media security using SDES? 7.5.2 n/a c16 37A end-to-access-edge media security for MSRP using TLS and certificate fingerprints? 7.5.2 n/a c22 37B end-to-access-edge media security for BFCP using TLS and certificate fingerprints? 7.5.2 n/a c23 37C end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints? 7.5.2 n/a c24 37D end-to-access-edge media security for RTP media using DTLS-SRTP and certificate fingerprints? 7.5.2 n/a c40 38 SDP media capabilities negotiation? [172] o c12 39 Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)? [166] o c13 40 Message Session Relay Protocol? [178] o c17 40A Connection establishment for media anchoring for the message session relay protocol? [214] o c26 41 a SDP offer/answer mechanism to enable file transfer? [185] o o 42 optimal media routeing [11D] n/a c18 43 ECN for RTP over UDP [188] o c19 44 T.38 FAX? [202] n/a c20 45 support for reduced-size RTCP? [204] o o 46 RTCP extended reports? [205] o o 47 maximum receive SDU size? [9B] o o 48 the SDP content attribute? [206] o c21 49 a general mechanism for RTP header extensions? [210] o o 50 negotiation of generic image attributes in the session description protocol (SDP)? [211] o o 51 connection-oriented media transport over the TLS protocol in the SDP? [241] o c25 52 UDPTL over DTLS? [217] o c27 53 telepresence? [7G] o o 54 SCTP over DTLS? [219] o c28 55 DTLS-SRTP? [222], [223] o c41 56 STUN Usage for Consent Freshness? [224] o c29 57 Alternate Connectivity (ALTC) Attribute? [228] o c30 58 3GPP MTSI RTCP-APP adaptation? [9B] n/a o 59 3GPP MTSI Pre-defined Region-of-Interest (ROI)? [9B] n/a o 60 3GPP MTSI Arbitrary Region-of-Interest (ROI)? [9B] n/a o 61 multiplexing RTP data and control packets on a single port [237], [237A] o o 61A Exclusive RTP and RTCP multiplexed on one port (a=rtcp-mux-only)? [246] o c34 62 SDP-based data channel negotiation? [238] o c31 63 Media plane optimization for WebRTC? [8Z] n/a c32 64 Enhanced bandwidth negotiation mechanism? [9B] n/a o 65 an SDP offer/answer mechanism to negotiate DTLS protected media? [240] o c33 66 Using simulcast in SDP and RTP sessions? [249] o c35 67 RTP payload format restrictions? [250] o c36 68 Compact Concurrent Codec Negotiation and Capabilities? [9B] n/a c35 69 3GPP MTSI Delay Budget Information (DBI)? [9B] n/a c37 70 Access Network Bitrate Recommendation (ANBR)? [9B] n/a c38 71 Framework for Live Uplink Streaming (FLUS)? [276] n/a c39 72 IMS data channels? [297], [9B] n/a c42 c1: IF A.3/1 THEN m ELSE n/a - - UE role. c2: IF A.3/9B AND A.3/13B THEN m ELSE IF A.3/1 OR A.3/2A OR A.3/6 OR A.3/7 THEN o ELSE n/a - - IBCF (IMS-ALG), ISC gateway function (IMS-ALG), UE, P-CSCF (IMS-ALG), MGCF, AS. c3: IF A.317/24 OR A.317/53 THEN m ELSE o - - mapping of media streams to resource reservation flows, telepresence. c4: IF A.3/9B OR A.3/13B THEN m ELSE IF A.3/1 OR A.3/6 THEN o ELSE n/a - - IBCF (IMS-ALG), application gateway function (IMS-ALG), UE, MGCF. c5: IF A.3A/50 OR A.3A/50A OR A.3/6 OR A.3/9B OR A.3A/89 OR A.3A/11 OR A.3A/12 THEN m ELSE o - - multimedia telephony service participant, multimedia telephony service application server, MGCF, IBCF (IMS-ALG), ATCF (UA), conference focus, conference participant. c6: IF A.3A/50 OR A.3A/50A OR A.3/6 OR A.3/9B OR A.3/13B OR A.3A/89 THEN m ELSE o - - multimedia telephony service participant, multimedia telephony service application server, MGCF, IBCF (IMS-ALG), application gateway function (IMS-ALG), ATCF (UA). c7: IF A.3A/82 OR A.3A/83 THEN m ELSE o - - ICS user agent, SCC application server. c8: IF A.317/25 AND (A.3/1 OR A.3/6 OR A.3A/89) THEN o ELSE n/a - - SDP bandwidth modifiers for RTCP bandwidth, UE, MGCF, ATCF (UA). c9: IF A.3D/30 OR A.3D/20 THEN m ELSE n/a - - end-to-access-edge media security using SDES, end-to-end media security using SDES. c10: IF A.3D/21 OR A.3D/22 THEN m ELSE n/a - - end-to-end media security using KMS, end-to-end media security for MSRP using TLS and KMS. c12: IF A.3A/82 OR A.3A/83 THEN m ELSE o - - ICS user agent, SCC application server. c13: IF IF A.3/7D OR A.3/8 THEN o else n/a - - AS performing 3rd party call control or MRFC. c14: IF A.4/2C THEN m ELSE o - - initiating a session which require local and/or remote resource reservation. c15: IF A.3D/20 OR A.3D/21 OR A.3D/30 THEN m ELSE n/a - - end-to-end media security using SDES, end-to-end media security using KMS, end-to-access-edge media security using SDES. c16: If A.3D/30 THEN m ELSE n/a - - end-to-access-edge media security using SDES. c17: IF A.3A/33B OR A.3A/34 THEN m ELSE IF A.3A/8 OR A.3A/9 OR A.3/2A THEN o ELSE n/a - - session-mode messaging participant, session-mode messaging intermediate node, IBCF, MRFC, P-CSCF (IMS-ALG). c18: IF A.3/2A OR A.3/6 OR A.3/7 OR A.3/9B OR A.3A/89 OR A.3/13B THEN o ELSE n/a - - P-CSCF (IMS-ALG), MGCF, AS, IBCF (IMS-ALG), ATCF (UA), application gateway function (IMS-ALG). c19: IF A.3/2A OR A.3/6 OR A.3/8 OR A.3/9B OR A.3A/81 OR A.3A/89 OR A.3/13B OR A.3A/81A OR A.3A/81B THEN o ELSE n/a - - P-CSCF (IMS-ALG), MGCF, MRFC, IBCF (IMS-ALG), MSC Server enhanced for ICS, ATCF (UA), application gateway function (IMS-ALG), MSC server enhanced for SRVCC using SIP interface, MSC server enhanced for DRVCC using SIP interface. c20: IF A.3/1 OR A.3/6 THEN o ELSE n/a - - UE, MGCF. c21: IF A.3A/57 OR A.3A/58 OR A.3A/59 OR A.3A/60 OR A.3/2A OR A.3/9B OR A.3A/11 OR A.3A/12 THEN m ELSE o - - Customized alerting tones application server, Customized alerting tones UA client, Customized ringing signal application server, Customized ringing signal UA client, P-CSCF (IMS-ALG), IBCF (IMS-ALG), conference focus, conference participant. c22: If A.3D/20A THEN m ELSE n/a - - end-to-access-edge media security for MSRP using TLS and certificate fingerprints. c23: If A.3D/20B THEN m ELSE n/a - - end-to-access-edge media security for BFCP using TLS and certificate fingerprints. c24: If A.3D/20C THEN m ELSE n/a - - end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints. c25: IF (A.317/37A AND A.317/40) OR (A.317/37B AND A.317/28) OR (A.317/37C AND A.317/52) OR (A.317/37D AND A.317/55) THEN m ELSE o - - end-to-access-edge media security for MSRP using TLS and certificate fingerprints, message session relay protocol, end-to-access-edge media security for BFCP using TLS and certificate fingerprints, session description protocol format for binary floor control protocol streams, end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints, UDPTL over DTLS, end-to-access-edge media security for RTP media using DTLS-SRTP and certificate fingerprints, DTLS-SRTP. c26: IF A.317/40 THEN m ELSE n/a - - message session relay protocol. c27: IF A.317/37C THEN m ELSE o - - end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints. c28: IF (A.3/1 AND A.317/53) OR A.3/14 OR A.3A/95 THEN m ELSE o - - UE, telepresence, Gm based WIC, eP-CSCF. c29: IF A.3/14 OR A.3A/95 THEN m ELSE o - - Gm based WIC, eP-CSCF. c30: IF A.3A/81 OR A.3/9B OR A.3/2A THEN o ELSE n/a - - UE performing the functions of an external attached network, IBCF (IMS-ALG), P-CSCF (IMS-ALG). c31: IF A.3/14 OR A.3A/95 THEN o ELSE n/a - - Gm based WIC, eP-CSCF. c32: IF A.3A/95 OR A.3/9B THEN o ELSE n/a - - eP-CSCF, IMS-ALG. c33: IF A.317/52 OR A.317/54 OR A.317/55 THEN m ELSE n/a - - UDPTL over DTLS, SCTP over DTLS, DTLS-SRTP. c34: IF A.3/14 OR A.3A/95 THEN m ELSE n/a - - Gm based WIC, eP-CSCF. c35: IF A.3A/11 OR A.3A/12 THEN o ELSE n/a - - conference focus, conference participant. c36: IF A.317/66 AND (A.3A/11 OR A.3A/12) THEN o ELSE n/a - - Using simulcast in SDP and RTP sessions, conference focus, conference participant. c37: IF A.3/1 OR A.3/2A OR A.3/8 OR A.3/9B THEN o ELSE n/a - - UE, P-CSCF (IMS-ALG), MRFC, IBCF (IMS-ALG). c38: IF A.3/1 THEN o ELSE n/a - - UE. c39: IF A.3/1 OR A.3/2 THEN o ELSE n/a - - UE, P-CSCF. c40: IF A.3D/31 THEN m ELSE n/a - - end-to-access-edge media security for RTP media using DTLS-SRTP and certificate fingerprints. c41: IF A.3D/31 THEN m ELSE o - - end-to-access-edge media security for RTP media using DTLS-SRTP and certificate fingerprints. c42: IF A.3/1 OR A.3/8 OR A.3A/50A THEN o ELSE n/a - - UE, MRFC, Multimedia telephony service application server. NOTE 1: For "video" and "audio" media types that utilise RTP/RTCP, if the RTCP bandwidth level for the session is different than the default RTCP bandwidth as specified in RFC 3556 [56], then, it shall be specified. For other media types, it may be specified. A.3.2.2 SDP types Table A.318: SDP types Item Type Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status Session level description 1 v= (protocol version) [39] 5.1 m m [39] 5.1 m m 2 o= (owner/creator and session identifier) [39] 5.2 m m [39] 5.2 m m 3 s= (session name) [39] 5.3 m m [39] 5.3 m m 4 i= (session information) [39] 5.4 o c2 [39] 5.4 m c3 5 u= (URI of description) [39] 5.5 o c4 [39] 5.5 o n/a 6 e= (email address) [39] 5.6 o c4 [39] 5.6 o n/a 7 p= (phone number) [39] 5.6 o c4 [39] 5.6 o n/a 8 c= (connection information) [39] 5.7 c5 c5 [39] 5.7 m m 9 b= (bandwidth information) [39] 5.8 o o [39] 5.8 m m Time description (one or more per description) 10 t= (time the session is active) [39] 5.9 m m [39] 5.9 m m 11 r= (zero or more repeat times) [39] 5.10 o c4 [39] 5.10 o n/a Session level description (continued) 12 z= (time zone adjustments) [39] 5.11 o n/a [39] 5.11 o n/a 13 k= (encryption key) [39] 5.12 x x [39] 5.12 n/a n/a 14 a= (zero or more session attribute lines) [39] 5.13 o o [39] 5.13 m m Media description (zero or more per description) 15 m= (media name and transport address) [39] 5.14 m m [39] 5.14 m m 16 i= (media title) [39] 5.4 o c2 [39] 5.4 o c3 17 c= (connection information) [39] 5.7 c1 c1 [39] 5.7 m m 18 b= (bandwidth information) [39] 5.8 o o [39] 5.8 m m 19 k= (encryption key) [39] 5.12 x x [39] 5.12 n/a n/a 20 a= (zero or more media attribute lines) [39] 5.13 o o [39] 5.13 m m c1: IF (A.318/15 AND NOT A.318/8) THEN m ELSE IF (A.318/15 AND A.318/8) THEN o ELSE n/a - - "c=" contained in session level description and SDP contains media descriptions. c2: IF A.3/6 THEN x ELSE o - - MGCF. c3: IF A.3/6 THEN n/a ELSE m - - MGCF. c4: IF A.3/6 THEN x ELSE n/a - - MGCF. c5: IF A.318/17 THEN o ELSE m - - "c=" contained in all media description. Prerequisite A.318/14 OR A.318/20 - - a= (zero or more session/media attribute lines) Table A.319: zero or more session / media attribute lines (a=) Item Field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 category (a=cat) [39] 6 c8 c8 [39] 6 c9 c9 2 keywords (a=keywds) [39] 6 c8 c8 [39] 6 c9 c9 3 name and version of tool (a=tool) [39] 6 c8 c8 [39] 6 c9 c9 4 packet time (a=ptime) [39] 6 c10 c10 [39] 6 c11 c11 5 maximum packet time (a=maxptime) [39] 6 (NOTE 1) c10 c10 [39] 6 (NOTE 1) c11 c11 6 receive-only mode (a=recvonly) [39] 6 o o [39] 6 m m 7 send and receive mode (a=sendrecv) [39] 6 o o [39] 6 m m 8 send-only mode (a=sendonly) [39] 6 o o [39] 6 m m 8A Inactive mode (a=inactive) [39] 6 o o [39] 6 m m 9 whiteboard orientation (a=orient) [39] 6 c10 c10 [39] 6 c11 c11 10 conference type (a=type) [39] 6 c8 c8 [39] 6 c9 c9 11 character set (a=charset) [39] 6 c8 c8 [39] 6 c9 c9 12 language tag (a=sdplang) [39] 6 o o [39] 6 m m 13 language tag (a=lang) [39] 6 o o [39] 6 m m 14 frame rate (a=framerate) [39] 6 c10 c10 [39] 6 c11 c11 15 quality (a=quality) [39] 6 c10 c10 [39] 6 c11 c11 16 format specific parameters (a=fmtp) [39] 6 c10 c10 [39] 6 c11 c11 17 rtpmap attribute (a=rtpmap) [39] 6 c10 c10 [39] 6 c11 c11 18 current-status attribute (a=curr) [30] 5 c1 c1 [30] 5 c2 c2 19 desired-status attribute (a=des) [30] 5 c1 c1 [30] 5 c2 c2 20 confirm-status attribute (a=conf) [30] 5 c1 c1 [30] 5 c2 c2 21 media stream identification attribute (a=mid) [53] 3 c3 c3 [53] 3 c4 c4 22 group attribute (a=group) [53] 4 c5 c5 [53] 3 c6 c6 23 setup attribute (a=setup) [83] 4 c7 c45 [83] 4 c7 c45 24 connection attribute (a=connection) [83] 5 c7 c7 [83] 5 c7 c7 24A DTLS association ID attribute (a=tls-id) [240] 4 c62 c62 [240] 4 c62 c62 25 IP addresses (a=candidate) [290] c12 c12 [290] c13 c13 26 floor control server determination (a=floorctrl) [108] 4 c14 c14 [108] 4 c14 c14 27 conference id (a=confid) [108] 5 c14 c14 [108] 5 c14 c14 28 user id (a=userid) [108] 5 c14 c14 [108] 5 c14 c14 29 association between streams and floors (a=floorid) [108] 6 c14 c14 [108] 6 c14 c14 30 RTCP feedback capability attribute (a=rtcp-fb) [135] 4.2 c15 c15 [135] 4.2 c15 c15 31 extension of the rtcp-fb attribute (a=rtcp-fb) [136] 7.1, [188] 6.2, [251] 9 c15 c15 [136] 7.1, [251] 9 c15 c15 32 supported capability negotiation extensions (a=csup) [137] 3.3.1 c16 c16 [137] 3.3.1 c16 c16 33 required capability negotiation extensions (a=creq) [137] 3.3.2 c16 c16 [137] 3.3.2 c16 c16 34 attribute capability (a=acap) [137] 3.4.1 c16 c16 [137] 3.4.1 c16 c16 35 transport protocol capability (a=tcap) [137] 3.4.2 c16 c16 [137] 3.4.2 c16 c16 36 potential configuration (a=pcfg) [137] 3.5.1 [172] 3.3.6 c16 c16 [137] 3.5.1 [172] 3.3.6 c16 c16 37 actual configuration (a=acfg) [137] 3.5.2 c16 c16 [137] 3.5.2 c16 c16 38 connection data capability (a=ccap) [156] 3.1 c17 c17 [156] 3.1 c18 c18 39 maximum packet rate (a=maxprate) [152] 6.3 c19 c19 [152] 6.3 c19 c19 40 crypto attribute (a=crypto) [168] c20 c20 [168] c20 c20 41 key management attribute (a=key-mgmt) [167] c21 c21 [167] c21 c21 42 3GPP_e2ae-security-indicator (a=3ge2ae) 7.5.2 c22 c22 7.5.2 c22 c22 43 media capability (a=rmcap) [172] 3.3.1 c23 c23 [172] 3.3.1 c23 c23 43A media capability (a=omcap) [172] 3.3.1 c23 c23 [172] 3.3.1 c23 c23 44 media format capability (a=mfcap) [172] 3.3.2 c23 c23 [172] 3.3.2 c23 c23 45 media-specific capability (a=mscap) [172] 3.3.3 c23 c23 [172] 3.3.3 c23 c23 46 latent configuration (a=lcfg) [172] 3.3.5 c44 c44 [172] 3.3.5 c44 c44 47 session capability (a=sescap) [172] 3.3.8 c24 c24 [172] 3.3.8 c24 c24 48 msrp path (a=path) [178] c25 c25 [178] c25 c25 49 file selector (a=file-selector) [185] 6 c27 c27 [185] 6 c28 c28 50 file transfer identifier (a= file-transfer-id) [185] 6 c26 c26 [185] 6 c28 c28 51 file disposition (a=file-disposition) [185] 6 c26 c26 [185] 6 c28 c28 52 file date (a=file-date) [185] 6 c26 c26 [185] 6 c28 c28 53 file icon (a=file-icon [185] 6 c26 c26 [185] 6 c28 c28 54 file range (a=file-range) [185] 6 c26 c26 [185] 6 c28 c28 55 optimal media routeing visited realm (a=visited-realm) 7.5.3 c29 c29 7.5.3 c29 c29 56 optimal media routeing secondary realm (a=secondary-realm) 7.5.3 c29 c29 7.5.3 c29 c29 57 optimal media routeing media level checksum (a=omr-m-cksum) 7.5.3 c29 c29 7.5.3 c29 c29 58 optimal media routeing session level checksum (a=omr-s-cksum) 7.5.3 c29 c29 7.5.3 c29 c29 59 optimal media routeing codecs (a=omr-codecs) 7.5.3 c29 c29 7.5.3 c29 c29 60 optimal media routeing media attributes (a=omr-m-att) 7.5.3 c29 c29 7.5.3 c29 c29 61 optimal media routeing session attributes (a=omr-s-att) 7.5.3 c29 c29 7.5.3 c29 c29 62 optimal media routeing media bandwidth (a=omr-m-bw) 7.5.3 c29 c29 7.5.3 c29 c29 63 optimal media routeing session bandwidth (a=omr-s-bw) 7.5.3 c29 c29 7.5.3 c29 c29 64 ecn-attribute (a=ecn-capable-rtp) [188] c30 c30 [188] c30 c30 65 T38 FAX Protocol version (a=T38FaxVersion) [202] n/a c31 [202] n/a c31 66 T38 FAX Maximum Bit Rate (a=T38MaxBitRate) [202] n/a c31 [202] n/a c31 67 T38 FAX Rate Management (a=T38FaxRateManagement) [202] n/a c31 [202] n/a c31 68 T38 FAX Maximum Buffer Size (a=T38FaxMaxBuffer) [202] n/a c31 [202] n/a c31 69 T38 FAX Maximum Datagram Size (a=T38FaxMaxDatagram) [202] n/a c31 [202] n/a c31 70 T38 FAX maximum IFP frame size (a=T38FaxMaxIFP) [202] n/a c32 [202] n/a c32 71 T38 FAX UDP Error Correction Scheme (a=T38FaxUdpEC) [202] n/a c32 [202] n/a c32 72 T38 FAX UDP Error Correction Depth (a=T38FaxUdpECDepth) [202] n/a c32 [202] n/a c32 73 T38 FAX UDP FEC Maximum Span (a=T38FaxUdpFECMaxSpan) [202] n/a c32 [202] n/a c32 74 T38 FAX Modem Type (a=T38ModemType) [202] n/a c32 [202] n/a c32 75 T38 FAX Vendor Info (a=T38VendorInfo) [202] n/a c32 [202] n/a c32 76 reduced-size RTCP (a=rtcp-rsize) [204] c33 c33 [204] c34 c34 77 RTP control protocol extended report parameters (a=rtcp-xr) [205] c35 c35 [205] c36 c36 78 maximum receive SDU size (a=3gpp_MaxRecvSDUSize) [9B] c37 c37 [9B] c38 c38 79 content (a=content) [206] c39 c39 [206] c39 c39 80 generic header extension map definition (a=extmap) [210] c40 c40 [210] c41 c41 81 image attribute (a=imageattr) [211] c42 c42 [211] c43 c43 82 fingerprint (a=fingerprint) [241] c46 c46 [241] c46 c46 83 msrp-cema (a=msrp-cema) [214] c47 c47 [214] c47 c47 84 sctp-port (a=sctp-port) [219] c48 c48 [219] c48 c48 84A max-message-size (a=max-message-size) [219] c68 c68 [219] c48 c48 85 CS correlation (a=cs-correlation) [155] 5.2.3.1 c49 c49 [155] 5.2.3.1 c49 c49 86 Alternate Connectivity (ALTC) Attribute (a=altc) [228] o c50 [228] o c50 87 3GPP MTSI RTCP-APP adaptation (a=3gpp_mtsi_app_adapt) [9B] n/a c51 [9B] n/a c52 88 3GPP MTSI Pre-defined Region-of-Interest (ROI) (a=predefined_ROI) [9B] n/a c53 [9B] n/a c54 89 RTP and RTCP multiplexed on one port (a=rtcp-mux) [237], [237A] c55 c55 [237], [237A] c55 c55 90 data channel mapping (a=dcmap) [238] c56 c56 [238] c56 c56 91 data channel subprotocol specific attributes (a=dcsa) [238] c55 c56 [238] c56 c56 92 Media plane optimization for WebRTC Contact (a= tra-contact) 7.5.4 c57 c57 7.5.4 c57 c57 93 Media plane optimization for WebRTC m-line (a= tra-m-line) 7.5.4 c58 c58 7.5.4 c58 c58 94 Media plane optimization for WebRTC attribute (a= tra-att) 7.5.4 c57 c57 7.5.4 c57 c57 95 Media plane optimization for WebRTC bandwidth (a= tra-bw) 7.5.4 c57 c57 7.5.4 c57 c57 96 Media plane optimization for WebRTC SCTP-association (a= tra-SCTP-association) 7.5.4 c58 c58 7.5.4 c58 c58 97 Media plane optimization for WebRTC media line number (a= tra-media-line-number) 7.5.4 c59 c59 7.5.4 c59 c59 98 Enhanced bandwidth negotiation mechanism (a=bw-info) [9B] n/a c60 [9B] n/a c61 99 Exclusive RTP and RTCP multiplexed on one port (a=rtcp-mux-only) [246] c63 c63 [246] c63 c63 100 Simulcast stream description (a=simulcast) [249] 6.1 c64 c64 [249] 6.1 c64 c64 101 Restriction identifier (a=rid) [250] 10 c65 c65 [250] 10 c66 c66 102 3GPP compact concurrent codec capabilities (a=ccc-list) [9B] n/a c67 [9B] n/a c67 103 Delay Budget Information (DBI) RTCP feedback type (a=rtcp-fb:* 3gpp-delay-budget) [9B] 6.2.8 n/a c69 [9B] 6.2.8 n/a c69 104 ANBR Support attribute (a=anbr) [9B] n/a c70 [9B] n/a c70 105 Label attribute (a=label) [277] 4 o c71 [277] 4 o c71 106 3GPP QoS hint attribute (a=3gpp-qos-hint) [9B] 6.2.7.4 n/a c72 [9B] 6.2.7.4 n/a c72 107 3GPP bootstrap data channel used by attribute (a=3gpp-bdc-used-by) [9B] 6.2.12 n/a c73 [9B] 6.2.12 n/a c73 108 IMS data channel requesting application attribute (3gpp-req-app) [9B] 6.2.13 n/a c74 [9B] 6.2.13 n/a c74 c1: IF A.317/22 AND A.318/20 THEN o ELSE n/a - - integration of resource management and SIP, media level attribute name "a=". c2: IF A.317/22 AND A.318/20 THEN m ELSE n/a - - integration of resource management and SIP, media level attribute name "a=". c3: IF A.317/23 AND A.318/20 THEN o ELSE n/a - - grouping of media lines, media level attribute name "a=". c4: IF A.317/23 AND A.318/20 THEN m ELSE n/a - - grouping of media lines, media level attribute name "a=". c5: IF A.317/23 AND A.318/14 THEN o ELSE n/a - - grouping of media lines, session level attribute name "a=". c6: IF A.317/23 AND A.318/14 THEN m ELSE n/a - - grouping of media lines, session level attribute name "a=". c7: IF A.317/26 AND A.318/20 THEN m ELSE n/a - - TCP-based media transport in the session description protocol, media level attribute name "a=". c8: IF A.318/14 THEN o ELSE x - - session level attribute name "a=". c9: IF A.318/14 THEN m ELSE n/a - - session level attribute name "a=". c10: IF A.318/20 THEN o ELSE x - - media level attribute name "a=". c11: IF A.318/20 THEN m ELSE n/a - - media level attribute name "a=". c12: IF A.317/27 AND A.318/20 THEN o ELSE n/a - - candidate IP addresses, media level attribute name "a=". c13: IF A.317/27 AND A.318/20 THEN m ELSE n/a - - candidate IP addresses, media level attribute name "a=". c14: IF A.317/28 AND A.318/20 THEN m ELSE n/a - - session description protocol format for binary floor control protocol streams, media level attribute name "a=". c15: IF (A.317/29 AND A.318/20) THEN m ELSE n/a - - extended RTP profile for real-time transport control protocol (RTCP)-based feedback (RTP/AVPF), media level attribute name "a=". c16: IF A.317/30 AND A.318/20 THEN m ELSE n/a - - SDP capability negotiation, media level attribute name "a=". c17: IF A.317/32 AND A.318/20 THEN o ELSE n/a - - miscellaneous capabilities negotiation in the Session Description Protocol (SDP), media level attribute name "a=". c18: IF A.317/32 AND A.318/20 THEN m ELSE n/a - - miscellaneous capabilities negotiation in the Session Description Protocol (SDP), media level attribute name "a=". c19: IF A.317/33 AND (A.318/14 OR A.318/20) THEN o ELSE n/a - - bandwidth modifier packet rate parameter, media or session level attribute name "a=". c20: IF A.317/34 AND A.317/36 AND A.318/20 THEN m ELSE n/a - - Secure Real-time Transport Protocol, media plane security using SDES, media level attribute name "a=". c21: IF ((A.317/34 AND A.3D/21) OR A.3D/22) AND A.317/35 AND A.318/20 THEN m ELSE n/a - - Secure Real-time Transport Protocol, end-to-end media security using KMS, end-to-end media security for MSRP using TLS and KMS, MIKEY-TICKET, media level attribute name "a=". c22: IF (A.317/37 OR A.317/37A OR A.317/37B OR A.317/37C OR A.317/37D) AND A.318/20 THEN m ELSE n/a - - end-to-access edge media security using SDES, end-to-access-edge media security for MSRP using TLS and certificate fingerprints, end-to-access-edge media security for BFCP using TLS and certificate fingerprints, end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints, end-to-access-edge media security for RTP media using DTLS-SRTP and certificate fingerprints, media level attribute name "a=". c23: IF A.317/38 THEN m ELSE n/a - - SDP media capabilities negotiation. c24: IF A.317/38 AND A.318/14 THEN m ELSE n/a - - SDP media capabilities negotiation, session level attribute name "a=". c25: IF A.317/40 AND A.318/20 THEN m ELSE n/a - - message session relay protocol, media level attribute name "a=". c26: IF A.317/41 AND A.318/20 THEN o ELSE n/a - - a SDP offer/answer mechanism to enable file transfer, media level attribute name "a=". c27: IF A.317/41 AND A.318/20 AND (A.3A/31 OR A.3A/33) THEN m ELSE IF A.317/41 AND A.318/20 AND NOT (A.3A/31 OR A.3A/33) THEN o ELSE n/a - - a SDP offer/answer mechanism to enable file transfer, media level attribute name "a=", messaging application server, messaging participant. c28: IF A.317/41 AND A.318/20 THEN m ELSE n/a - - a SDP offer/answer mechanism to enable file transfer, media level attribute name "a=". c29: IF A.317/42 AND A.318/20 THEN o ELSE n/a - - optimal media routeing, media level attribute name "a=". c30: IF A.317/43 THEN m ELSE n/a - - ECN for RTP over UDP, media level attribute name "a=". c31: IF A.317/44 AND A.318/20 THEN m ELSE n/a - - T.38 FAX, media level attribute name "a=". c32: IF A.317/44 AND A.318/20 THEN o ELSE n/a - - T.38 FAX, media level attribute name "a=". c33: IF A.317/45 AND A.318/20 THEN o ELSE n/a - - support for reduced-size RTCP, media level attribute name "a=". c34: IF A.317/45 AND A.318/20 THEN m ELSE n/a - - support for reduced-size RTCP, media level attribute name "a=". c35: IF A.317/46 AND A.318/20 AND A.318/14 THEN o ELSE n/a - - RTCP extended reports, media level attribute name "a=", session level attribute name "a=". c36: IF A.317/46 AND A.318/20 AND A.318/14 THEN m ELSE n/a - - RTCP extended reports, media level attribute name "a=", session level attribute name "a=". c37: IF A.317/47 AND A.318/20 AND A.318/14 THEN o ELSE n/a - - maximum receive SDU size, media level attribute name "a=", session level attribute name "a=". c38: IF A.317/47 AND A.318/20 AND A.318/14 THEN m ELSE n/a - - maximum receive SDU size, media level attribute name "a=", session level attribute name "a=". c39: IF A.317/48 AND A.318/20 THEN m ELSE n/a - - the SDP content attribute, media level attribute name "a=". c40: IF A.317/49 AND A.318/20 AND A.318/14 THEN o ELSE n/a - - a general mechanism for RTP header extensions, media level attribute name "a=", session level attribute name "a=". c41: IF A.317/49 AND A.318/20 AND A.318/14 THEN m ELSE n/a - - a general mechanism for RTP header extensions, media level attribute name "a=", session level attribute name "a=". c42: IF A.317/50 AND A.318/20 THEN o ELSE n/a - - negotiation of generic image attributes in the session description protocol (SDP), media level attribute name "a=". c43: IF A.317/50 AND A.318/20 THEN m ELSE n/a - - negotiation of generic image attributes in the session description protocol (SDP), media level attribute name "a=". c44: IF A.317/38 AND A.318/20 THEN m ELSE n/a - - SDP media capabilities negotiation, media level attribute name "a=". c45: IF (A.317/26 OR A.317/52) AND A.318/20 THEN m ELSE n/a - - TCP-based media transport in the session description protocol, UDPTL over DTLS, media level attribute name "a=". c46: IF (A.317/51 OR A.317/55) AND A.318/20 AND A.318/14 THEN m ELSE n/a - - connection-oriented media transport over the TLS protocol in the SDP, DTLS-SRTP, media level attribute name "a=", session level attribute name "a=". c47: IF A.317/40A AND A.318/20 THEN m ELSE n/a - - connection establishment for media anchoring for the message session relay protocol, media level attribute name "a=". c48: IF A.317/54 AND A.318/20 THEN m ELSE n/a - - SCTP over DTLS, media level attribute name "a=". c49: IF A.317/31 AND A.318/20 THEN m ELSE n/a - - Session Description Protocol (SDP) extension for setting up audio media streams over circuit-switched bearers in the Public Switched Telephone Network (PSTN) and SIP, media level attribute name "a=". c50: IF A.317/57 AND A.318/20 THEN o ELSE n/a - - Alternate Connectivity (ALTC) Attribute, media level attribute name "a=" c51: IF A.317/58 AND A.318/20 THEN o ELSE n/a - - 3GPP MTSI RTCP-APP adaptation, media level attribute name "a=". c52: IF A.317/58 AND A.318/20 THEN m ELSE n/a - - 3GPP MTSI RTCP-APP adaptation, media level attribute name "a=". c53: IF A.317/59 AND A.318/20 THEN o ELSE n/a - - 3GPP MTSI Pre-defined Region-of-Interest (ROI), media level attribute name "a=". c54: IF A.317/59 AND A.318/20 THEN m ELSE n/a - - 3GPP MTSI Pre-defined Region-of-Interest (ROI), media level attribute name "a=". c55: IF A.317/61 AND A.318/20 THEN m ELSE n/a - - multiplexing RTP data and control packets on a single port, media level attribute name "a=". c56: IF A.317/62 AND A.318/20 THEN m ELSE n/a - - SDP-based data channel negotiation, media level attribute name "a=". c57: IF A.317/63 AND (A.318/14 OR A.318/20) THEN o ELSE n/a - -, Media plane optimization for WebRTC session or media level attribute name "a=". c58: IF A.317/63 AND A.318/20 THEN o ELSE n/a - -, Media plane optimization for WebRTC media level attribute name "a=". c59: IF A.317/63 AND A.318/14 THEN o ELSE n/a - -, Media plane optimization for WebRTC session level attribute name "a=". c60: IF A.317/64 AND A.318/20 THEN o ELSE n/a - - Enhanced bandwidth negotiation mechanism, media level attribute name "a=". c61: IF A.317/64 AND A.318/20 THEN m ELSE n/a - - Enhanced bandwidth negotiation mechanism, media level attribute name "a=". c62: IF (A.317/52 OR A.317/54 OR A.317/55) AND A.318/20 THEN m ELSE n/a - - UDPTL over DTLS, SCTP over DTLS, DTLS-SRTP, media level attribute name "a=". c63: IF A.317/61A AND A.318/20 THEN m ELSE n/a - - Exclusive RTP and RTCP multiplexed on one port (a=rtcp-mux-only), media level attribute name "a=". c64: IF A.317/66 AND A.318/20 THEN m ELSE n/a - - Using simulcast in SDP and RTP sessions, media level attribute name "a=". c65: IF A.317/67 AND A.318/20 THEN o ELSE n/a - - RTP payload format restrictions, media level attribute name "a=". c66: IF A.317/67 AND A.318/20 THEN m ELSE n/a - - RTP payload format restrictions, media level attribute name "a=". c67: IF A.317/68 AND A.318/14 THEN o ELSE n/a - - Compact Concurrent Codec Negotiation and Capabilities, session level attribute name "a=". c68: IF A.317/54 AND A.318/20 THEN o ELSE n/a - - SCTP over DTLS, media level attribute name "a=". c69: IF A.317/69 AND A.318/20 THEN m ELSE n/a - - Delay Budget Information (DBI), media level attribute name "a=". c70: IF A.317/70 AND A.318/20 THEN m ELSE n/a - - Access Network Bitrate Recommendation (ANBR), media level attribute name "a=". c71: IF A.317/71 AND A.318/20 THEN m ELSE n/a - - Framework for Live Uplink Streaming (FLUS), media level attribute name "a=". c72: IF (A.317/71 OR A.317/72) AND A.318/20 THEN o ELSE n/a - - Framework for Live Uplink Streaming (FLUS), IMS data channels, media level attribute name "a=". c73: IF A.317/72 AND A.318/20 THEN o ELSE n/a - - IMS data channels, media level attribute name "a=". c74: IF A.317/72 AND A.318/20 THEN m ELSE n/a - - IMS data channels, media level attribute name "a=". NOTE 1: Further specification of the usage of this attribute is defined by specifications relating to individual codecs. Prerequisite A.319/80 - - a= generic header extension map definition (a=extmap) Table A.319A: RTP header extensions Item Field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 coordination of video orientation (urn:3gpp:video-orientation) [9B] n/a o [9B] n/a o 2 higher granularity coordination of video orientation (urn:3gpp:video-orientation:6) [9B] n/a c1 [9B] n/a c1 3 video region-of-interest predefined-roi-sent (urn:3gpp: predefined-roi-sent) [9B] n/a c2 [9B] n/a c2 4 video region-of-interest arbitrary-roi-sent (urn:3gpp:roi-sent) [9B] n/a c3 [9B] n/a c3 c1: IF A.319A/1 THEN o ELSE n/a - - coordination of video orientation. c2: IF A.317/59 THEN o ELSE n/a - - 3GPP MTSI Pre-defined Region-of-Interest (ROI). c3: IF A.317/60 THEN o ELSE n/a - - 3GPP MTSI Arbitrary Region-of-Interest (ROI). A.3.2.3 Void Table A.320: Void Table A.321: Void Table A.322: Void Table A.323: Void Table A.324: Void Table A.325: Void Table A.326: Void Table A.327: Void A.3.2.4 Void Table A.327A: Void A.3.3 Proxy role This subclause contains the ICS proforma tables related to the user role. They need to be completed only for proxy implementations. Prerequisite: A.2/2 -- proxy role A.3.3.1 Major capabilities Table A.328: Major capabilities Item Does the implementation support Reference RFC status Profile status Capabilities within main protocol 0A application of session policy? 6.2, 6.3 x c2 Extensions 1 integration of resource management and SIP? [30] [64] o n/a 2 grouping of media lines? [53] c3 x 3 mapping of media streams to resource reservation flows? [54] o x 4 SDP bandwidth modifiers for RTCP bandwidth? [56] o c1 5 TCP-based media transport in the session description protocol? [83] o c11 6 interactive connectivity establishment? [289], [290] o c4 7 session description protocol format for binary floor control protocol streams? [108] o o 8 extended RTP profile for real-time transport control protocol (RTCP)-based feedback (RTP/AVPF)? [135] o c5 9 SDP capability negotiation? [137] o c9 10 Session Description Protocol (SDP) extension for setting up audio media streams over circuit-switched bearers in the Public Switched Telephone Network (PSTN)? [155] o c6 11 miscellaneous capabilities negotiation in the Session Description Protocol (SDP)? [156] o c6 14 Secure Real-time Transport Protocol (SRTP)? [169] o o 15 MIKEY-TICKET? [170] o o 16 SDES? [168] o o 17 end-to-access edge media security using SDES? 7.5.2 n/a n/a 17A end-to-access-edge media security for MSRP using TLS and certificate fingerprints? 7.5.2 n/a n/a 17B end-to-access-edge media security for BFCP using TLS and certificate fingerprints? 7.5.2 n/a n/a 17C end-to-access-edge media security for UDPTL using DTLS and certificate fingerprints? 7.5.2 n/a n/a 17D end-to-access-edge media security for RTP media using DTLS-SRTP and certificate fingerprints? 7.5.2 n/a n/a 18 SDP media capabilities negotiation? [172] o c8 19 Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)? [166] m i 20 Message Session Relay Protocol? [178] o o 20A Connection establishment for media anchoring for the message session relay protocol? [214] o c12 21 a SDP offer/answer mechanism to enable file transfer? [185] o o 22 optimal media routeing? [11D] n/a o 23 ECN for RTP over UDP? [188] o c10 24 T.38 FAX? [202] n/a o 25 support for reduced-size RTCP? [204] o o 26 RTCP extended reports? [205] o o 27 maximum receive SDU size? [9B] o o 28 the SDP content attribute [206] o o 29 a general mechanism for RTP header extensions? [210] o o 30 negotiation of generic image attributes in the session description protocol (SDP)? [211] o o 31 connection-oriented media transport over the TLS protocol in the SDP? [241] o o 32 UDPTL over DTLS? [217] o o 33 telepresence? [7G] o o 34 SCTP over DTLS? [219] o o 35 DTLS-SRTP? [222], [223] o o 36 STUN Usage for Consent Freshness? [224] o o 38 3GPP MTSI RTCP-APP adaptation? [9B] n/a o 39 3GPP MTSI Pre-defined Region of Interest (ROI)? [9B] n/a o 40 3GPP MTSI Arbitrary Region-of-Interest (ROI)? [9B] n/a o 41 multiplexing RTP data and control packets on a single port [237], [237A] o o 42 Media plane optimization for WebRTC 7.5.4 n/a o 43 Enhanced bandwidth negotiation mechanism [9B] n/a o 45 an SDP offer/answer mechanism to negotiate DTLS protected media? [240] o c13 46 Using simulcast in SDP and RTP sessions? [249] o o 47 RTP payload format restrictions? [250] o o 48 Compact Concurrent Codec Negotiation and Capabilities? [9B] n/a o 49 3GPP MTSI Delay Budget Information (DBI)? [9B] n/a c14 50 Access Network Bitrate Recommendation (ANBR)? [9B] n/a c15 51 Framework for Live Uplink Streaming (FLUS)? [276] n/a c15 52 IMS data channels? [297], [9B] n/a o c1: IF A.3/2 OR A.3A/88 THEN m ELSE n/a - - P-CSCF, ATCF (proxy). c2: IF A.3/2 OR A.3/4 THEN o ELSE x – P-CSCF, S-CSCF. c3: IF A.328/3 THEN m ELSE o - - mapping of media streams to resource reservation flows. c4: IF A.3/2 OR A.3/4 THEN m ELSE n/a - - P-CSCF, S-CSCF. c5: IF (A.3A/50A AND A.3/7C) OR A.3/2 OR A.3/4 OR A.3A/88 THEN m ELSE n/a - - multimedia telephony service application server as AS acting as a SIP proxy, P-CSCF, S-CSCF, ATCF (proxy). c6: IF (A.3A/83 AND A.3/7C) OR A.3/4 THEN m ELSE IF A.3A/88 THEN i ELSE n/a - - SCC application server, AS acting as a SIP proxy, S-CSCF, ATCF (proxy). c7: IF A.328/18 THEN m ELSE o - - SDP media capabilities negotiation. c8: IF A.3/2 OR A.3/4 THEN m ELSE IF A.3A/88 THEN i ELSE o - - P-CSCF, S-CSCF, ATCF (proxy). c9: IF (A.3A/50A AND A.3/7C) OR A.3/2 OR A.3/4 OR A.328/18 OR A.3A/88 THEN m ELSE n/a - - multimedia telephony service application server as AS acting as a SIP proxy, P-CSCF, S-CSCF, SDP media capabilities negotiation, ATCF (proxy). c10: IF A.3A/88 THEN o ELSE i - - ATCF (proxy). c11: IF A.3/2 OR A.3/4 OR A.3A/88 THEN m ELSE n/a - - P-CSCF, S-CSCF, ATCF (proxy). c12: IF A.328/20 THEN m ELSE n/a - - message session relay protocol. c13: IF A.328/32 OR A.328/34 OR A.328/35 THEN m ELSE n/a - - UDPTL over DTLS, SCTP over DTLS, DTLS-SRTP. c14: IF A.3/2 OR A.3/4 THEN o ELSE n/a - - P-CSCF, S-CSCF. c15: IF A.3/2 THEN o ELSE n/a - - P-CSCF A.3.3.2 SDP types Table A.329: SDP types Item Type Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status Session level description 1 v= (protocol version) [39] 5.1 m m [39] 5.1 m m 2 o= (owner/creator and session identifier). [39] 5.2 m m [39] 5.2 i i 3 s= (session name) [39] 5.3 m m [39] 5.3 i i 4 i= (session information) [39] 5.4 m m [39] 5.4 i i 5 u= (URI of description) [39] 5.5 m m [39] 5.5 i i 6 e= (email address) [39] 5.6 m m [39] 5.6 i i 7 p= (phone number) [39] 5.6 m m [39] 5.6 i i 8 c= (connection information) [39] 5.7 m m [39] 5.7 i i 9 b= (bandwidth information) [39] 5.8 m m [39] 5.8 i i Time description (one or more per description) 10 t= (time the session is active) [39] 5.9 m m [39] 5.9 i i 11 r= (zero or more repeat times) [39] 5.10 m m [39] 5.10 i i Session level description (continued) 12 z= (time zone adjustments) [39] 5.11 m m [39] 5.11 i i 13 k= (encryption key) [39] 5.12 m m [39] 5.12 i i 14 a= (zero or more session attribute lines) [39] 5.13 m m [39] 5.13 i i Media description (zero or more per description) 15 m= (media name and transport address) [39] 5.14 m m [39] 5.14 m m 16 i= (media title) [39] 5.4 m m [39] 5.4 i i 17 c= (connection information) [39] 5.7 m m [39] 5.7 i i 18 b= (bandwidth information) [39] 5.8 m m [39] 5.8 i c1 19 k= (encryption key) [39] 5.12 m m [39] 5.12 i i 20 a= (zero or more media attribute lines) [39] 5.13 m m [39] 5.13 i c1 c1: IF A.328/0A THEN m ELSE i - - application of session policy. Prerequisite A.329/14 OR A.329/20 - - a= (zero or more session/media attribute lines) Table A.330: zero or more session / media attribute lines (a=) Item Field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 category (a=cat) [39] 6 m m [39] 6 i i 2 keywords (a=keywds) [39] 6 m m [39] 6 i i 3 name and version of tool (a=tool) [39] 6 m m [39] 6 i i 4 packet time (a=ptime) [39] 6 m m [39] 6 i c9 5 maximum packet time (a=maxptime) [39] 6 (NOTE 1) m m [39] 6 (NOTE 1) i c9 6 receive-only mode (a=recvonly) [39] 6 m m [39] 6 i c9 7 send and receive mode (a=sendrecv) [39] 6 m m [39] 6 i c9 8 send-only mode (a=sendonly) [39] 6 m m [39] 6 i c9 8A Inactive mode (a=inactive) [39] 6 m m [39] 6 i c9 9 whiteboard orientation (a=orient) [39] 6 m m [39] 6 i c9 10 conference type (a=type) [39] 6 m m [39] 6 i i 11 character set (a=charset) [39] 6 m m [39] 6 i i 12 language tag (a=sdplang) [39] 6 m m [39] 6 i c9 13 language tag (a=lang) [39] 6 m m [39] 6 i c9 14 frame rate (a=framerate) [39] 6 m m [39] 6 i c9 15 quality (a=quality) [39] 6 m m [39] 6 i c9 16 format specific parameters (a=fmtp) [39] 6 m m [39] 6 i c9 17 rtpmap attribute (a=rtpmap) [39] 6 m m [39] 6 i c9 18 current-status attribute (a=curr) [30] 5 m m [30] 5 c2 c2 19 desired-status attribute (a=des) [30] 5 m m [30] 5 c2 c2 20 confirm-status attribute (a=conf) [30] 5 m m [30] 5 c2 c2 21 media stream identification attribute (a=mid) [53] 3 c5 x [53] 3 c6 x 22 group attribute (a=group) [53] 4 c5 x [53] 4 c6 x 23 setup attribute (a=setup) [83] 4 c7 c50 [83] 4 c8 c51 24 connection attribute (a=connection) [83] 5 c7 c7 [83] 5 c8 c8 24A DTLS association ID attribute (a=tls-id) [240] 4 c72 c72 [240] 4 c72 c72 25 candidate IP addresses (a=candidate) [290] c9 c9 [290] c10 c10 26 floor control server determination (a=floorctrl) [108] 4 c11 c11 [108] 4 c12 c13 27 conference id (a=confid) [108] 5 c11 c11 [108] 5 c12 c13 28 user id (a=userid) [108] 5 c11 c11 [108] 5 c12 c13 29 association between streams and floors (a=floorid) [108] 6 c11 c11 [108] 6 c12 c13 30 RTCP feedback capability attribute (a=rtcp-fb) [135] 4.2 c14 c14 [135] 4.2 c15 c15 31 extension of the rtcp-fb attribute (a=rtcp-fb) [136] 7.1 [188] 6.2, [251] 9 c14 c14 [136] 7.1, [251] 9 c15 c15 32 supported capability negotiation extensions (a=csup) [137] 3.3.1 c16 c16 [137] 3.3.1 c17 c17 33 required capability negotiation extensions (a=creq) [137] 3.3.2 c16 c16 [137] 3.3.2 c17 c17 34 attribute capability (a=acap) [137] 3.4.1 c16 c16 [137] 3.4.1 c17 c17 35 transport protocol capability (a=tcap) [137] 3.4.2 c16 c16 [137] 3.4.2 c17 c17 36 potential configuration (a=pcfg) [137] 3.5.1 [172] 3.3.6 c16 c16 [137] 3.5.1 [172] 3.3.6 c17 c17 37 actual configuration (a=acfg) [137] 3.5.2 c16 c16 [137] 3.5.2 c17 c17 38 connection data capability (a=ccap) [156] 3.1 c18 c18 [156] 3.1 c19 c19 40 crypto attribute (a=crypto) [168] c20 c20 [167] c20 c20 41 key management attribute (a=key-mgmt) [167] c21 c21 [168] c22 c22 42 3GPP_e2ae-security-indicator (a=3ge2ae) 7.5.2 c23 c23 7.5.2 c23 c23 43 media capability (a=rmcap) [172] 3.3.1 c24 c24 [172] 3.3.1 c26 c26 43A media capability (a=omcap) [172] 3.3.1 c24 c24 [172] 3.3.1 c26 c26 44 media format capability (a=mfcap) [172] 3.3.2 c24 c24 [172] 3.3.2 c26 c26 45 media-specific capability (a=mscap) [172] 3.3.3 c24 c24 [172] 3.3.3 c26 c26 46 latent configuration (a=lcfg) [172] 3.3.5 c48 c48 [172] 3.3.5 c49 c49 47 session capability (a=sescap) [172] 3.3.8 c25 c25 [172] 3.3.8 c27 c27 48 msrp path (a=path) [178] c28 c28 [178] c29 c29 49 file selector (a=file-selector) [185] 6 c30 c30 [185] 6 c31 c31 50 file transfer identifier (a= file-transfer-id) [185] 6 c30 c30 [185] 6 c31 c31 51 file disposition (a=file-disposition) [185] 6 c30 c30 [185] 6 c31 c31 52 file date (a=file-date) [185] 6 c30 c30 [185] 6 c31 c31 53 file icon (a=file-icon [185] 6 c30 c30 [185] 6 c31 c31 54 file range (a=file-range) [185] 6 c30 c30 [185] 6 c31 c31 55 optimal media routeing visited realm (a=visited-realm) 7.5.3 c32 c32 7.5.3 c33 c33 56 optimal media routeing secondary realm (a=secondary-realm) 7.5.3 c32 c32 7.5.3 c33 c33 57 optimal media routeing media level checksum (a=omr-m-cksum) 7.5.3 c32 c32 7.5.3 c33 c33 58 optimal media routeing session level checksum (a=omr-s-cksum) 7.5.3 c32 c32 7.5.3 c33 c33 59 optimal media routeing codecs (a=omr-codecs) 7.5.3 c32 c32 7.5.3 c33 c33 60 optimal media routeing media attributes (a=omr-m-att) 7.5.3 c32 c32 7.5.3 c33 c33 61 optimal media routeing session attributes (a=omr-s-att) 7.5.3 c32 c32 7.5.3 c33 c33 62 optimal media routeing media bandwidth (a=omr-m-bw) 7.5.3 c32 c32 7.5.3 c33 c33 63 optimal media routeing session bandwidth (a=omr-s-bw) 7.5.3 c32 c32 7.5.3 c33 c33 64 ecn-attribute (a=ecn-capable-rtp) [188] c34 c34 [188] c34 c34 65 T38 FAX Protocol version (a=T38FaxVersion) [202] n/a c35 [202] n/a c36 66 T38 FAX Maximum Bit Rate (a=T38MaxBitRate) [202] n/a c35 [202] n/a c36 67 T38 FAX Rate Management (a=T38FaxRateManagement) [202] n/a c35 [202] n/a c36 68 T38 FAX Maximum Buffer Size (a=T38FaxMaxBuffer) [202] n/a c35 [202] n/a c36 69 T38 FAX Maximum Datagram Size (a=T38FaxMaxDatagram) [202] n/a c35 [202] n/a c36 70 T38 FAX maximum IFP frame size (a=T38FaxMaxIFP) [202] n/a c35 [202] n/a c36 71 T38 FAX UDP Error Correction Scheme (a=T38FaxUdpEC) [202] n/a c35 [202] n/a c36 72 T38 FAX UDP Error Correction Depth (a=T38FaxUdpECDepth) [202] n/a c35 [202] n/a c36 73 T38 FAX UDP FEC Maximum Span (a=T38FaxUdpFECMaxSpan) [202] n/a c35 [202] n/a c36 74 T38 FAX Modem Type (a=T38ModemType) [202] n/a c35 [202] n/a c36 75 T38 FAX Vendor Info (a=T38VendorInfo) [202] n/a c35 [202] n/a c36 76 reduced-size RTCP (a=rtcp-rsize) [204] c37 c37 [204] c38 c38 77 RTP control protocol extended report parameters (a=rtcp-xr) [205] c39 c39 [205] c40 c40 78 maximum receive SDU size (a=3gpp_MaxRecvSDUSize) [9B] c41 c41 [9B] c42 c42 79 content (a=content) [206] c43 c43 [206] c43 c43 80 generic header extension map definition (a=extmap) [210] c44 c44 [210] c45 c45 81 image attribute (a=imageattr) [211] c46 c46 [211] c47 c47 82 fingerprint (a=fingerprint) [241] c52 c52 [241] c53 c53 83 msrp-cema (a=msrp-cema) [214] c54 c54 [214] c55 c55 84 sctp-port (a=sctp-port) [219] c56 c56 [219] c56 c56 84A max-message-size (a=max-message-size) [219] c56 c56 [219] c56 c56 85 CS correlation (a=cs-correlation) [155] 5.2.3.1 c57 c57 [155] 5.2.3.1 c57 c57 87 3GPP MTSI RTCP-APP adaptation (a=3gpp_mtsi_app_adapt) [9B] n/a c58 [9B] n/a c59 88 3GPP MTSI Pre-defined Region-of-Interest (ROI) (a=predefined_ROI) [9B] n/a c60 [9B] n/a c61 89 RTP and RTCP multiplexed on one port (a=rtcp-mux) [237], [237A] c62 c62 [237], [237A] c63 c63 92 Media plane optimization for WebRTC Contact (a= tra-contact) 7.5.4 c64 c64 7.5.4 c65 c65 93 Media plane optimization for WebRTC m-line (a= tra-m-line) 7.5.4 c66 c66 7.5.4 c67 c67 94 Media plane optimization for WebRTC attribute (a= tra-att) 7.5.4 c64 c64 7.5.4 c65 c65 95 Media plane optimization for WebRTC bandwidth (a= tra-bw) 7.5.4 c64 c64 7.5.4 c65 c65 98 Media plane optimization for WebRTC SCTP-association (a= tra-SCTP-association) 7.5.4 c66 c66 7.5.4 c67 c67 97 Media plane optimization for WebRTC media line number (a= tra-media-line-number) 7.5.4 c68 c68 7.5.4 c69 c69 98 Enhanced bandwidth negotiation mechanism (a=bw-info) [9B] n/a c70 [9B] n/a c71 99 Exclusive RTP and RTCP multiplexed on one port (a=rtcp-mux-only) [246] c62 c62 [246] c63 c63 100 Simulcast stream description (a=simulcast) [249] 6.1 c73 c73 [249] 6.1 c74 c74 101 Restriction identifier (a=rid) [250] 10 c75 c75 [250] 10 c76 c76 102 3GPP compact concurrent codec capabilities (a=ccc-list) [9B] n/a c77 [9B] n/a c78 103 Delay Budget Information (DBI) RTCP feedback type (a=rtcp-fb:* 3gpp-delay-budget) [9B] 6.2.8 n/a c79 [9B] 6.2.8 n/a c79 104 ANBR Support attribute (a=anbr) [9B] n/a c80 [9B] n/a c80 105 Label attribute (a=label) [277] 4 o c81 [277] 4 o c81 106 3GPP QoS hint attribute (a=3gpp-qos-hint) [9B] 6.2.7.4 n/a c82 [9B] n/a c82 107 3GPP bootstrap data channel used by attribute (a=3gpp-bdc-used-by) [9B] 6.2.12 n/a c83 [9B] 6.2.12 n/a c83 108 IMS data channel requesting application attribute (3gpp-req-app) [9B] 6.2.13 n/a c84 [9B] 6.2.13 n/a c84 c2: IF A.328/1 THEN m ELSE i - - integration of resource management and SIP. c5: IF A.328/2 THEN m ELSE n/a - - grouping of media lines. c6: IF A.328/3 THEN m ELSE IF A.328/2 THEN i ELSE n/a - - mapping of media streams to resource reservation flows, grouping of media lines. c7: IF A.328/5 THEN m ELSE n/a. c8: IF A.328/5 THEN i ELSE n/a. c9: IF A.329/20 AND A.328/0A THEN m ELSE i - - media level attribute name "a=" and application of session policy. c9: IF A.328/6 THEN m ELSE n/a - - interactive connectivity establishment. c10: IF A.328/1 AND A.328/6 THEN m ELSE IF A.328/6 THEN i ELSE n/a - - integration of resource management and SIP, interactive connectivity establishment. c11: IF A.328/7 THEN m ELSE n/a - - session description protocol format for binary floor control protocol streams. c12: IF A.328/7 THEN i ELSE n/a - - session description protocol format for binary floor control protocol streams. c13: IF A.328/7 AND A.328/0A AND A.329/20 THEN m ELSE IF A.328/7 AND A.329/20 THEN i ELSE n/a - - session description protocol format for binary floor control protocol streams, media level attribute name "a=" and application of session policy. c14: IF (A.328/8 AND A.329/20) THEN m ELSE n/a - - extended RTP profile for real-time transport control protocol (RTCP)-based feedback (RTP/AVPF), media level attribute name "a=". c15: IF (A.328/8 AND A.329/20) THEN i ELSE n/a - - extended RTP profile for real-time transport control protocol (RTCP)-based feedback (RTP/AVPF), media level attribute name "a=". c16: IF A.328/9 AND A.329/20 THEN m ELSE n/a - - SDP capability negotiation, media level attribute name "a=". c17: IF A.328/9 AND A.329/20 THEN i ELSE n/a - - SDP capability negotiation, media level attribute name "a=". c18: IF A.328/11 AND A.329/20 THEN o ELSE n/a - - miscellaneous capabilities negotiation in the Session Description Protocol (SDP), media level attribute name "a=". c19: IF A.328/11 AND A.329/20 THEN m ELSE n/a - - miscellaneous capabilities negotiation in the Session Description Protocol (SDP), media level attribute name "a=". c20: IF A.328/14 AND A.328/16 AND A.329/20 THEN m ELSE n/a - - Secure Real-time Transport Protocol, media plane security using SDES, media level attribute name "a=". c21: IF ((A.328/14 AND A.3D/21) OR A.3D/22) AND A.328/15 AND A.329/20 THEN m ELSE n/a - - Secure Real-time Transport Protocol, media plane security using KMS, end-to-end media security for MSRP using TLS and KMS, MIKEY-TICKET, media level attribute name "a=". c22: IF ((A.328/14 AND A.3D/21) OR A.3D/22) AND A.328/15 AND A.329/20 THEN i ELSE n/a - - Secure Real-time Transport Protocol, media plane security using KMS, end-to-end media security for MSRP using TLS and KMS, MIKEY-TICKET, media level attribute name "a=". c23: IF A.328/17 AND A.329/20 THEN m ELSE n/a - - end to access edge media security, media level attribute name "a=". c24: IF A.328/18 THEN m ELSE n/a - - SDP media capabilities negotiation. c25: IF A.328/18 AND A.329/14 THEN m ELSE n/a - - SDP media capabilities negotiation, session level attribute name "a=". c26: IF A.328/18 AND A.328/0A THEN m ELSE IF A.328/18 THEN i ELSE n/a - - SDP media capabilities negotiation, application of session policy. c27: IF A.328/18 AND A.329/14 AND A.328/0A THEN m ELSE IF A.328/18 AND A.329/14 THEN i ELSE n/a - - SDP media capabilities negotiation, session level attribute name "a=", application of session policy. c28: IF A.328/20 AND A.329/20 THEN m ELSE n/a - - message session relay protocol, media level attribute name "a=". c29: IF A.328/20 AND A.329/20 THEN i ELSE n/a - - message session relay protocol, media level attribute name "a=". c30: IF A.328/21 AND A.329/20 THEN m ELSE n/a - - a SDP offer/answer mechanism to enable file transfer, media level attribute name "a=". c31: IF A.328/21 AND A.329/20 THEN i ELSE n/a - - a SDP offer/answer mechanism to enable file transfer, media level attribute name "a=". c32: IF A.328/22 AND A.329/20 THEN m ELSE n/a - - optimal media routeing, media level attribute name "a=". c33: IF A.328/22 AND A.329/20 THEN i ELSE n/a - - optimal media routeing, media level attribute name "a=". c34: IF A.328/23 THEN m ELSE i - - ECN for RTP over UDP, media level attribute name "a=". c35: IF A.328/24 AND A.329/20 THEN m ELSE n/a - - T.38 FAX, media level attribute name "a=". c36: IF A.328/24 AND A.329/20 THEN i ELSE n/a - - T.38 FAX, media level attribute name "a=". c37: IF A.328/25 AND A.329/20 THEN m ELSE n/a. - - support for reduced-size RTCP, media level attribute name "a=". c38: IF A.328/25 AND A.329/20 THEN i ELSE n/a - - support for reduced-size RTCP, media level attribute name "a=". c39: IF A.328/26 AND A.329/20 AND A.329/14 THEN m ELSE n/a -- RTCP extended reports, media level attribute name "a=", session level attribute name "a=". c40: IF A.328/26 AND A.329/20 AND A.329/14 THEN i ELSE n/a -- RTCP extended reports, media level attribute name "a=", session level attribute name "a=". c41: IF A.328/27 AND A.329/20 AND A.329/14 THEN m ELSE n/a -- maximum receive SDU size, media level attribute name "a=", session level attribute name "a=". c42: IF A.328/27 AND A.329/20 AND A.329/14 THEN i ELSE n/a -- maximum receive SDU size, media level attribute name "a=", session level attribute name "a=". c43: IF A.328/28 AND A.329/20 THEN m ELSE n/a - - the SDP content attribute, media level attribute name "a=". c44: IF A.328/29 AND A.329/20 AND A.329/14 THEN m ELSE n/a - - a general mechanism for RTP header extensions, media level attribute name "a=", session level attribute name "a=". c45: IF A.328/29 AND A.329/20 AND A.329/14 THEN i ELSE n/a - - a general mechanism for RTP header extensions, media level attribute name "a=", session level attribute name "a=". c46: IF A.328/30 AND A.329/20 THEN m ELSE n/a - - negotiation of generic image attributes in the session description protocol (SDP), media level attribute name "a=". c47: IF A.328/30 AND A.329/20 THEN i ELSE n/a - - negotiation of generic image attributes in the session description protocol (SDP), media level attribute name "a=". c48: IF A.328/18 AND A.329/20 THEN m ELSE n/a - - SDP media capabilities negotiation, media level attribute name "a=". c49: IF A.328/18 AND A.329/20 AND A.328/0A THEN m ELSE IF A.328/18 AND A.329/20 THEN i ELSE n/a - - SDP media capabilities negotiation, media level attribute name "a=", application of session policy. c50: IF (A.328/5 OR A.328/32) THEN m ELSE n/a -- TCP-based media transport in the session description protocol, UDPTL over DTLS. c51: IF (A.328/5 OR A.328/32) THEN i ELSE n/a -- TCP-based media transport in the session description protocol, UDPTL over DTLS. c52: IF (A.328/82 OR A.328/34) AND A.329/20 AND A.329/14 THEN m ELSE n/a -- connection-oriented media transport over the TLS protocol in the SDP, DTLS-SRTP, media level attribute name "a=", session level attribute name "a=". c53: IF (A.328/83 OR A.328/34) AND A.329/20 AND A.329/14 THEN i ELSE n/a -- connection-oriented media transport over the TLS protocol in the SDP, DTLS-SRTP, media level attribute name "a=", session level attribute name "a=". c54: IF A.328/20A AND A.329/20 THEN m ELSE n/a -- connection establishment for media anchoring for the message session relay protocol, media level attribute name "a=". c55: IF A.328/20A AND A.329/20 THEN i ELSE n/a -- connection establishment for media anchoring for the message session relay protocol, media level attribute name "a=". c56: IF A.328/33 AND A.329/20 THEN i ELSE n/a -- SCTP on top of DTLS, media level attribute name "a=". c57: IF A.318/10 AND A.329/20 THEN m ELSE n/a - - Session Description Protocol (SDP) extension for setting up audio media streams over circuit-switched bearers in the Public Switched Telephone Network (PSTN) and SIP, media level attribute name "a=". c58: IF A.328/38 AND A.329/20 THEN m ELSE n/a -- 3GPP MTSI RTCP-APP adaptation, media level attribute name "a=". c59: IF A.328/38 AND A.329/20 THEN i ELSE n/a -- 3GPP MTSI RTCP-APP adaptation, media level attribute name "a=". c60: IF A.328/39 AND A.329/20 THEN o ELSE n/a - - 3GPP MTSI Pre-defined Region-of-Interest (ROI), media level attribute name "a=". c61: IF A.328/39 AND A.329/20 THEN m ELSE n/a - - 3GPP MTSI Pre-defined Region-of-Interest (ROI), media level attribute name "a=". c62: IF A.328/41 AND A.329/20 AND A.329/14 THEN m ELSE n/a -- multiplexing RTP data and control packets on a single port, media level attribute name "a=", session level attribute name "a=". c63: IF A.328/41 AND A.329/20 AND A.329/14 THEN i ELSE n/a -- multiplexing RTP data and control packets on a single port, media level attribute name "a=", session level attribute name "a=". c64: IF A.328/42 AND (A.329/14 OR A.329/20) THEN m ELSE n/a - -, Media plane optimization for WebRTC session or media level attribute name "a=". c65: IF A. A.328/42 AND (A.329/14 OR A.329/20) THEN i ELSE n/a - -, Media plane optimization for WebRTC session or media level attribute name "a=". c66: IF A.328/42 AND A.329/20 THEN m ELSE n/a - -, Media plane optimization for WebRTC media level attribute name "a=". c67: IF A.328/42 AND A.329/20 THEN i ELSE n/a - -, Media plane optimization for WebRTC media level attribute name "a=". c68: IF A.328/42 AND A.329/14 THEN m ELSE n/a - -, Media plane optimization for WebRTC session level attribute name "a=". c69: IF A.328/42 AND A.329/14 THEN i ELSE n/a - -, Media plane optimization for WebRTC session level attribute name "a=". c70: IF A.328/43 AND A.329/20 THEN o ELSE n/a - - Enhanced bandwidth negotiation mechanism, media level attribute name "a=". c71: IF A.328/43 AND A.329/20 THEN m ELSE n/a - - Enhanced bandwidth negotiation mechanism, media level attribute name "a=". c72: IF (A.328/32 OR A.328/34 OR A.328/35) AND A.329/20 THEN m ELSE n/a - - UDPTL over DTLS, SCTP over DTLS, DTLS-SRTP, media level attribute name "a=". c73: IF A.328/46 AND A.329/20 THEN m ELSE n/a - - Using simulcast in SDP and RTP sessions, media level attribute name "a=". c74: IF A.328/46 AND A.329/20 THEN i ELSE n/a - - Using simulcast in SDP and RTP sessions, media level attribute name "a=". c75: IF A.328/47 AND A.329/20 THEN o ELSE n/a - - RTP payload format restrictions, media level attribute name "a=". c76: IF A.328/47 AND A.329/20 THEN i ELSE n/a - - RTP payload format restrictions, media level attribute name "a=". c77: IF A.328/48 AND A.329/14 THEN o ELSE n/a - - Compact Concurrent Codec Negotiation and Capabilities, session level attribute name "a=". c78: IF A.328/48 AND A.329/14 THEN i ELSE n/a - - Compact Concurrent Codec Negotiation and Capabilities, session level attribute name "a=". c79: IF A.328/49 AND A.329/20 m ELSE n/a - - Delay Budget Information (DBI), media level attribute name "a=". c80: IF A.328/50 AND A.329/20 THEN m ELSE n/a - - Access Network Bitrate Recommendation (ANBR), media level attribute name "a=". c81: IF A.328/51 AND A.329/20 THEN m ELSE n/a - - Framework for Live Uplink Streaming (FLUS), media level attribute name "a=". c82: IF (A.328/51 OR A.328/52) AND A.329/20 THEN o ELSE n/a - - Framework for Live Uplink Streaming (FLUS), IMS data channels, media level attribute name "a=". c83: IF A.328/53 AND A.329/20 THEN o ELSE n/a - - IMS data channels, media level attribute name "a=". c84: IF A.328/53 AND A.329/20 THEN m ELSE n/a - - IMS data channels, media level attribute name "a=". NOTE 1: Further specification of the usage of this attribute is defined by specifications relating to individual codecs. Prerequisite A.330/80 - - a= generic header extension map definition (a=extmap) Table A.330A: RTP header extensions Item Field Sending Receiving Ref. RFC status Profile status Ref. RFC status Profile status 1 coordination of video orientation (urn:3gpp:video-orientation) [9B] n/a m [9B] n/a i 2 higher granularity coordination of video orientation (urn:3gpp:video-orientation:6) [9B] n/a m [9B] n/a i 3 video region-of-interest predefined-roi-sent (urn:3gpp:predefined-roi-sent) [9B] n/a m [9B] n/a i 4 video region-of-interest arbitrary-roi-sent (urn:3gpp:roi-sent) [9B] n/a m [9B] n/a i A.3.3.3 Void Table A.331: Void Table A.332: Void Table A.333: Void Table A.334: Void Table A.335: Void Table A.336: Void Table A.337: Void Table A.338: Void A.3.3.4 Void Table A.339: Void A.4 Profile definition for other message bodies as used in the present document Void. Annex B (normative): IP-Connectivity Access Network specific concepts when using GPRS to access IM CN subsystem B.1 Scope The present annex defines IP-CAN specific requirements for a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is General Packet Radio Service (GPRS). The GPRS IP-CAN has a core network: - with SGSN connected to GGSN providing a UE with a PDP context for the IM CN subsystem-related signalling and media; or - with SGSN connected to S-GW and S-GW connected to P-GW providing the UE with a PDP context for the IM CN subsystem-related signalling and media. NOTE: The UE is unaware of how the network provides the UE with a PDP context for the IM CN subsystem-related signalling and media. The core network can be supported by GERAN and UTRAN radio access networks. The present annex also defines procedures for invoking CS domain services. B.2 GPRS aspects when connected to the IM CN subsystem B.2.1 Introduction A UE accessing the IM CN subsystem, and the IM CN subsystem itself, utilise the services provided by the core network to provide packet-mode communication between the UE and the IM CN subsystem. Requirements for the UE on the use of these packet-mode services are specified in this clause. Requirements for the core network in support of this communication are specified in 3GPP TS 29.061 [11], 3GPP TS 29.207 [12] and 3GPP TS 29.212 [13B]. When using the GPRS IP-CAN, each IP-CAN bearer is provided by a PDP context. B.2.2 Procedures at the UE B.2.2.1 PDP context activation and P-CSCF discovery Prior to communication with the IM CN subsystem, the UE shall: a) if not attached for GPRS services yet, perform a GPRS attach procedure as specified in 3GPP TS 24.008 [8]; b) ensure that a PDP context used for SIP signalling according to the APN and GGSN or P-GW selection criteria described in 3GPP TS 23.060 [4] and 3GPP TS 27.060 [10A] is available. This PDP context shall remain active throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the deregistration. As a result, the PDP context provides the UE with information that makes the UE able to construct an IPv4 or an IPv6 address; NOTE 1: During the PDP context activation procedure, the UE and the core network negotiate whether the UE or the GPRS IP-CAN is responsible for the resource reservation applicable to all PDP contexts within the activated PDP address/APN pair, as described in 3GPP TS 24.008 [8]. When the bearer establishment is controlled by the UE, the UE shall choose one of the following options when performing establishment of this PDP context: I. A dedicated PDP context for SIP signalling: The UE shall indicate to the core network that this is a PDP context intended to carry IM CN subsystem-related signalling only by setting the IM CN Subsystem Signalling Flag. The UE may also use this PDP context for DNS and DHCP signalling according to the static packet filters as described in 3GPP TS 29.061 [11]. The UE can also set the Signalling Indication attribute within the QoS information element; II. A general-purpose PDP context: The UE may decide to use a general-purpose PDP Context to carry IM CN subsystem-related signalling. The UE shall indicate to the core network that this is a general-purpose PDP context by not setting the IM CN Subsystem Signalling Flag. The UE may carry both signalling and media on the general-purpose PDP context. The UE can also set the Signalling Indication attribute within the QoS information element. NOTE 2: When the bearer establishment is controlled by the GPRS IP-CAN, the core network follows the procedures described in 3GPP TS 29.061 [11] in order to establish a dedicated PDP context for SIP signalling. If the UE supports the optional configuration parameter "Access_Point_Name_Parameter_Reading_Rule", as defined in 3GPP TS 24.167 [8G] and has been configured with this parameter, then the UE shall use it to retrieve the access point name to use in the PDP context activation procedure. The UE indicates the IM CN Subsystem Signalling Flag within the Protocol Configuration Options information element of the ACTIVATE PDP CONTEXT REQUEST message or ACTIVATE SECONDARY PDP CONTEXT REQUEST message. Upon successful signalling PDP context establishment the UE receives an indication in the form of IM CN Subsystem Signalling Flag within the Protocol Configuration Options information element. If the flag is not received, the UE shall consider the PDP context as a general-purpose PDP context. The encoding of the IM CN Subsystem Signalling Flag within the Protocol Configuration Options information element is described in 3GPP TS 24.008 [8]. The UE can indicate a request for prioritised handling over the radio interface by setting the Signalling Indication attribute (see 3GPP TS 23.107 [4A]). The general QoS negotiation mechanism and the encoding of the Signalling Indication attribute within the QoS information element are described in 3GPP TS 24.008 [8]; and NOTE 3: A general-purpose PDP Context can carry both IM CN subsystem signalling and media, in case the media does not need to be authorized by Policy and Charging control mechanisms as defined in 3GPP TS 29.212 [13B] and Service Based Local Policy mechanisms defined in 3GPP TS 29.207 [12] and the media stream is not mandated by the P-CSCF to be carried in a separate PDP Context. c) acquire a P-CSCF address(es). The methods for P-CSCF discovery are: I. When using IPv4, employ the Dynamic Host Configuration Protocol (DHCP) RFC 2132 [20F], the DHCPv4 options for SIP servers RFC 3361 [35A], and RFC 3263 [27A] as described in subclause 9.2.1. When using IPv6, employ Dynamic Host Configuration Protocol for IPv6 (DHCPv6) RFC 3315 [40], the DHCPv6 options for SIP servers RFC 3319 [41] and DHCPv6 options for Domain Name Servers (DNS) RFC 3646 [56C] as described in subclause 9.2.1. II. Transfer P-CSCF address(es) within the PDP context activation procedure. The UE shall indicate the request for a P-CSCF address within the Protocol Configuration Options information element of the ACTIVATE PDP CONTEXT REQUEST message or ACTIVATE SECONDARY PDP CONTEXT REQUEST message. If the UE is provided with a list of P-CSCF IPv4 or IPv6 addresses in the ACTIVATE PDP CONTEXT ACCEPT message or ACTIVATE SECONDARY PDP CONTEXT ACCEPT message, the UE shall assume that the list is ordered top-down with the first P-CSCF address within the Protocol Configuration Options information element as the P-CSCF address having the highest preference and the last P-CSCF address within the Protocol Configuration Options information element as the P-CSCF address having the lowest preference. III. The UE selects a P-CSCF from the list (see 3GPP TS 31.103 [15B]) stored in the ISIM. IV. The UE selects a P-CSCF from the list in IMS management object. The UE shall use method IV to select a P-CSCF, if: - a P-CSCF is to be discovered in the home network; - the UE is roaming; and - the IMS management object contains the P-CSCF list. The UE shall use method III to select the P-CSCF, if: - a P-CSCF is to be discovered in the home network; - the UE is roaming; - either the UE does not contain the IMS management object, or the UE contains the IMS management object, but the IMS management object does not contain the P-CSCF list; and - the ISIM residing in the UICC supports the P-CSCF list. The UE can freely select method I or II for P-CSCF discovery, if: - the UE is in the home network; or - the UE is roaming and the P-CSCF is to be discovered in the visited network. The UE can select method IV, if: - the UE is in the home network; and - the IMS management object contains the P-CSCF list. In case method I is selected and several P-CSCF addresses or FQDNs are provided to the UE, the selection of P-CSCF address or FQDN shall be performed as indicated in RFC 3361 [35A] when using IPv4 or RFC 3319 [41] when using IPv6. If sufficient information for P-CSCF address selection is not available, selection of the P-CSCF address by the UE is implementation specific. NOTE 4: The UE decides whether the P-CSCF is to be discovered in the serving network or in the home network based on local configuration, e.g. whether the application on the UE is permitted to use local breakout. If the UE is designed to use I above, but receives P-CSCF address(es) according to II, then the UE shall either ignore the received address(es), or use the address(es) in accordance with II, and not proceed with the DHCP request according to I. If the UE is configured to use Option II above and detects that all P-CSCFs known by the UE have been used when the UE selects a different P-CSCF as a result of: - receiving 305 (Use Proxy) to the REGISTER request; - receiving 504 (Server Time-out); or - expiration of the timer F at the UE, then the UE should: - release IP-CAN bearer that is used only for the transport of SIP signalling and that are not used for other non-IMS applications, except emergency IP-CAN bearers; - perform a new P-CSCF discovery procedure as described in subslause 9.2.1; and - perform the procedures for initial registration as described in subclause 5.1.1.2. NOTE 5: The UE may not be able to release the IP-CAN bearer if the IP-CAN bearer is in use by other applications. When using IPv4, the UE may request a DNS Server IPv4 address(es) via RFC 2132 [20F] or by the Protocol Configuration Options information element when activating a PDP context according to 3GPP TS 27.060 [10A]. When using IPv6, the UE may request a DNS Server IPv6 address(es) via RFC 3315 [40] and RFC 3646 [56C] or by the Protocol Configuration Options information element when activating a PDP context according to 3GPP TS 27.060 [10A]. The encoding of the request and response for IPv4 or IPv6 address(es) for DNS server(s) and list of P-CSCF address(es) within the Protocol Configuration Options information element is described in 3GPP TS 24.008 [8]. When: - the UE obtains a PDP context used for SIP signalling by performing handover of the connection from another IP-CAN; - the IP address of the UE is not changed during the handover; and - the UE already communicates with the IM CN subsystem via the connection with the other IP-CAN, e.g. the UE determines that its contact with host portion set to the UE IP address (or FQDN of the UE) associated with the connection with the other IP-CAN has been bound to a public user identity; the UE shall continue using the P-CSCF address(es) acquired in the other IP-CAN. B.2.2.1A Modification of a PDP context used for SIP signalling The PDP context shall not be modified from a dedicated PDP context for SIP signalling to a general-purpose PDP context or vice versa. The IM CN Subsystem Signalling Flag shall not be set in the Protocol Configuration Options information element of the MODIFY PDP CONTEXT REQUEST message. The UE shall not indicate the request for a P-CSCF address within the Protocol Configuration Options information element of the MODIFY PDP CONTEXT REQUEST message. The UE shall ignore P-CSCF address(es) if received in the Protocol Configuration Options information element of the MODIFY PDP CONTEXT RESPONSE message. B.2.2.1B Re-establishment of the PDP context for SIP signalling If the UE registered a public user identity with an IP address allocated for the APN of the PDP context used for SIP signalling, the PDP context used for SIP signalling is deactivated as result of signalling from the core network (e.g. no longer available as a result of a successful GPRS routeing area update procedure) and: i) if the signalling from the core network results in requiring the UE to initiate activation of the PDP context used for SIP signalling; or ii) if the UE needs to continue having a public user identity registered with an IP address allocated for the APN; and the UE is allowed to send: - ACTIVATE PDP CONTEXT REQUEST message; or - ACTIVATE SECONDARY PDP CONTEXT REQUEST message, to activate the PDP context for SIP signalling, the UE shall: A) if the non-access stratum is performing the PDP context activation procedure for the APN triggered as result of the signalling from the core network, wait until the PDP context activation procedure for the APN finishes; and B) perform the procedures in subclause B.2.2.1, bullets a), b) and c). If: - none of the bullets i) and ii) of this subclause evaluate to true; - the UE is not allowed to send the ACTIVATE (SECONDARY) PDP CONTEXT REQUEST message; - the procedures in bullet B) of this subclause were unable to ensure that the PDP context used for SIP signalling is available; or - the procedures in bullet B) of this subclause were unable to acquire any P-CSCF address(es); and if the PDP context used for SIP signalling was a dedicated PDP context for SIP signalling as described in subclause B.2.2.1, the UE shall deactivate all PDP contexts established as a result of SIP signalling according to the 3GPP TS 24.008 [8]. NOTE: 3GPP TS 24.008 [8] specifies conditions that prevent the UE from sending an ACTIVATE (SECONDARY) PDP CONTEXT REQUEST message. If all PDP contexts for the APN were deactivated at the start of this subclause and the procedures in bullet B) of this subclause ensured that the PDP context used for SIP signalling is available and acquired the P-CSCF address(es), the UE shall perform a new initial registration according to subclause 5.1.1.2. B.2.2.1C P-CSCF restoration procedure A UE supporting the P-CSCF restoration procedure performs one of the following procedures: A. if the UE used method II for P-CSCF discovery and if the UE receives one or more P-CSCF address(es) in the Protocol Configuration Options information element of a MODIFY PDP CONTEXT REQUEST message and the one or more P-CSCF addresse(s) do not include the address of the currently used P-CSCF, then the UE shall acquire a different P-CSCF address from the one or more P-CSCF addresse(s) in the MODIFY PDP CONTEXT REQUEST message. If more than one P-CSCF address with the same container identifier (i.e. "P-CSCF IPv6 Address" or "P-CSCF IPv4 Address") are included, then the UE shall assume that the more than one P-CSCF addresses with the same container identifier are prioritised with the first P-CSCF address with the same container identifier within the Protocol Configuration Options information element as the P-CSCF address with the highest priority. If the UE used method II for P-CSCF discovery and if the UE has previously sent the "P-CSCF Re-selection support" PCO indicator at PDP Context Activation and if the UE receives one or more P-CSCF address(es) in the Protocol Configuration Options information element of a MODIFY PDP CONTEXT REQUEST message, then the UE shall acquire a P-CSCF address from the one or more P-CSCF addresse(s) in the MODIFY PDP CONTEXT REQUEST message. If more than one P-CSCF address with the same container identifier (i.e. "P-CSCF IPv6 Address" or "P-CSCF IPv4 Address") are included, then the UE shall assume that the more than one P-CSCF addresses with the same container identifier are prioritised with the first P-CSCF address with the same container identifier within the Protocol Configuration Options information element as the P-CSCF address with the highest priority; B. if the UE uses RFC 6223 [143] as part of P-CSCF restoration procedures, and if the P-CSCF fails to respond to a keep-alive request, then the UE shall acquire a different P-CSCF address using one of the methods I, III and IV for P-CSCF discovery described in the subclause B.2.2.1. If the UE has an ongoing session and acquired the new P-CSCF address by using procedure A described above, the UE may wait until the UE has detected that the ongoing session has ended before performing an initial registration as specified in subclause 5.1. In all other cases, when the UE has acquired the P-CSCF address, the UE not having an ongoing session shall perform an initial registration as specified in subclause 5.1. NOTE 1: For UEs using procedure A described above, the network ensures that P-CSCF address(es) in the Protocol Configuration Options information element of a MODIFY PDP CONTEXT REQUEST is sent only during P-CSCF restoration procedures as defined in subclause 5 of 3GPP TS 23.380 [7D]. NOTE 2: The P-CSCF can be completely unreachable, so it is up to UE implementation to detect the end of an ongoing session, e.g. using media plane inactivity detection. Services depending on signalling such as CW and MT calls will not work during this time. B.2.2.2 Session management procedures The existing procedures for session management as described in 3GPP TS 24.008 [8] shall apply while the UE is connected to the IM CN subsystem. B.2.2.3 Mobility management procedures The existing procedures for mobility management as described in 3GPP TS 24.008 [8] shall apply while the UE is connected to the IM CN subsystem. B.2.2.4 Cell selection and lack of coverage The existing mechanisms and criteria for cell selection as described in 3GPP TS 25.304 [9] and 3GPP TS 44.018 [20] shall apply while the UE is connected to the IM CN subsystem. B.2.2.5 PDP contexts for media B.2.2.5.1 General requirements The UE can establish media streams that belong to different SIP sessions on the same PDP context. During establishment of a session, the UE establishes data streams(s) for media related to the session. Such data stream(s) may result in activation of additional PDP context(s). Such additional PDP context(s) shall be established as secondary PDP contexts associated to the PDP context used for signalling. Such secondary PDP contexts for media can be established either by the UE or the core network. If the bearer establishment is controlled by the UE, the UE starts reserving its local resources whenever it has sufficient information about the media streams, media authorization and used codecs available as specified in 3GPP TS 24.008 [8]. NOTE 1: If the bearer establishment is controlled by the GPRS IP-CAN, the resource reservation requests are initiated by the core network after the P-CSCF has authorised the respective IP flows and provided the QoS requirements over the Rx interface to the PCRF, as described in 3GPP TS 29.214 [13D]. NOTE 2: When the UE has to allocate bandwidth for RTP and RTCP in a PDP context, the UE uses the rules as those outlined in 3GPP TS 29.213 [13C]. B.2.2.5.1A Activation or modification of PDP contexts for media by the UE If the UE is configured not to initiate resource allocation for media according to 3GPP TS 24.167 [8G] and both UE and the core network are allowed to establish the secondary PDP contents, then the UE shall refrain from establishing the secondary PDP context(s) for media and from modifying existing PDP contexts for media until the UE considers that the network did not initiate resource allocation for the media. If the UE receives indication within the SDP according to RFC 3524 [54] that media stream(s) belong to group(s), the media stream(s) shall be set up on separate PDP contexts according to the indication of grouping of media streams. The UE may freely group media streams to PDP context(s) in case no indication of grouping of media streams is received from the P-CSCF. If the capabilities of the originating UE prevents it from establishment of additional PDP contexts according to the media grouping attributes given by the P-CSCF in accordance with RFC 3524 [54], the UE will not establish such grouping of media streams. Instead, the originating UE shall negotiate media parameters for the session according to RFC 3264 [27B]. If the capabilities of the terminating UE prevents it from establishment of additional PDP contexts according to the media grouping attributes given by the P-CSCF in accordance with RFC 3524 [54], the UE will not establish such grouping of media streams. Instead, the terminating UE shall the UE shall handle such SDP offers in accordance with RFC 3388 [53]. The UE can receive a media authorization token in the P-Media-Authorization header field from the P-CSCF according to RFC 3313 [31]. If a media authorization token is received in the P-Media-Authorization header field when a SIP session is initiated, the UE shall: - either use existing PDP context(s) where another media authorization token is already in use and no indication of grouping of media streams is required; or - establish separate PDP context(s) for the media; or - use an existing PDP context where media authorization token is not in use and no indication of grouping of media streams is required. When a UE modifies a PDP context to indicate a new media authorization token: - either as a result of establishment of an additional SIP session; or - modification of media streams for an ongoing SIP session; the UE shall include all media authorization tokens and all flow identifiers for all ongoing SIP sessions that use this particular PDP context. If a media authorization token is received in subsequent messages for the same SIP session, the UE shall: - use the existing PDP context(s) for media; - modify the existing PDP context(s) for media; or - establish additional PDP context(s) for media. If either background or interactive QoS class is needed for the media, then the UE does not need to use the authorization token even if it receives one. In this case the UE may reuse an existing PDP context and it does not need to request PDP context modification unless it needs to modify the QoS. If existing PDP context(s) where another media authorization token is already in use is re-used for the media, or separate PDP context(s) is established for the media, the UE shall proceed as follows: - when a SIP session is terminated, the media authorization token is no longer valid and the UE shall not include it in future GPRS session management messages. The UE shall send a MODIFY PDP CONTEXT REQUEST message updating the binding information by deleting the media authorization token and the corresponding flow identifiers that are no longer valid. If a SIP session is terminated and no other SIP sessions are using the PDP context, the UE shall either update the binding information as described above or deactivate the PDP context; - the UE shall transparently pass the media authorization token received from the P-CSCF in a response to an INVITE request at originating setup or in the INVITE request at terminating setup to the core network. The UE shall signal it by inserting it within the Traffic Flow Template information element in the ACTIVATE SECONDARY PDP CONTEXT REQUEST message or the MODIFY PDP CONTEXT REQUEST message; - to identify to the core network which flow(s) (identified by m-lines within the SDP) that are transferred within a particular PDP context, the UE shall set the flow identifier(s) within the Traffic Flow Template information element in the ACTIVATE SECONDARY PDP CONTEXT REQUEST message or the MODIFY PDP CONTEXT REQUEST message. Detailed description of how the flow identifiers are constructed is provided in 3GPP TS 29.207 [12]; - if the UE receives several media authorization tokens from the P-CSCF within the same SIP request or response, the first instance of the media authorization token shall be sent to the core network, and subsequent instances are discarded by the UE; and - the UE shall not include the IM CN Subsystem Signalling Flag when a PDP context for media is established or modified. The encoding of the media authorization token and the flow identifiers within the Traffic Flow Template information element is described in 3GPP TS 24.008 [8]. B.2.2.5.1B Activation or modification of PDP contexts for media by the core network If the UE receives an activation request for a PDP context which is associated with the PDP context used for signalling, the UE shall, based on the information contained in the Traffic Flow Template information element, correlate the media PDP context with a currently ongoing SIP session establishment or SIP session modification. If the UE receives a modification request for a PDP context that is used for one or more media streams in an ongoing SIP session, the UE shall: 1) modify the related PDP context in accordance with the received modification request. B.2.2.5.1C Deactivation of PDP context for media When a data stream for media related to a session is released, if the PDP context transporting the data stream is no longer needed and if the PDP context has been activated by the UE, then the UE deactivates the PDP context. NOTE: The PDP context can be needed e.g. for other data streams of a session or for other applications in the UE. B.2.2.5.2 Special requirements applying to forked responses NOTE 1: The procedures in this subclause only apply when the UE requests activation and modification of media bearers. In the case where the core network activates and modifies the media bearers the network takes care of the handling of media bearers in the case of forking. Since the UE does not know that forking has occurred until a second, provisional response arrives, the UE sets up the PDP context(s) as required by the initial response received. If a subsequent provisional response is received, different alternative actions may be performed depending on the requirements in the SDP answer: 1) the bearer requirements of the subsequent SDP can be accommodated by the existing PDP context(s). The UE performs no activation or modification of PDP contexts. 2) the subsequent SDP introduces different QoS requirements or additional IP flows. The UE modifies the existing PDP context(s), if necessary, according to subclause B.2.2.5.1A. 3) the subsequent SDP introduces one or more additional IP flows. The UE establishes additional PDP context(s) according to subclause B.2.2.5.1A. NOTE 2: When several forked responses are received, the resources requested by the UE is are the "logical OR" of the resources indicated in the multiple responses to avoid allocation of unnecessary resources. The UE does not request more resources than proposed in the original INVITE request. NOTE 3: When service-based local policy is applied, the UE receives the same authorization token for all forked requests/responses related to the same SIP session. When a final answer is received for one of the early dialogs, the UE proceeds to set up the SIP session. The UE shall release all the unneeded radio/bearer resources. Therefore, upon the reception of the first final 200 (OK) response for the INVITE request (in addition to the procedures defined in RFC 3261 [26] subclause 13.2.2.4), the UE shall: 1) in case PDP context(s) were established or modified as a consequence of the INVITE request and forked provisional responses that are not related to the accepted 200 (OK) response, delete the PDP context(s) or modify the delete the PDP context(s) back to their original state. B.2.2.5.3 Unsuccessful situations One of the Go, Gq, Rx and Gx interface related error codes can be received by the UE in the ACTIVATE SECONDARY PDP CONTEXT REJECT message or the MODIFY PDP CONTEXT REJECT message. If the UE receives a Go, Gq, Rx and Gx interface related error code, the UE shall either handle the resource reservation failure as described in subclause 6.1.1 or retransmit the message up to three times. The Go, Gq, Rx and Gx interface related error codes are further specified in 3GPP TS 29.207 [12], 3GPP TS 29.209 [13A], 3GPP TS 29.214 [13D] and 3GPP TS 29.212 [13B]. B.2.2.6 Emergency service B.2.2.6.1 General Emergency bearers are defined for use in emergency calls in GPRS IP-CAN and core network support of these bearers is indicated to the UE in NAS signalling. Where the UE recognises that a call request is an emergency call and the core network supports emergency bearers, the UE shall use these bearers for both signalling and media on emergency calls made using the IM CN subsystem. Some jurisdictions allow emergency calls to be made when the UE does not contain an ISIM or USIM, or where the credentials are not accepted. Additionally, where the UE is in state GMM-REGISTERED.LIMITED-SERVICE and GMM-REGISTERED.PLMN-SEARCH, a normal ATTACH has been attempted but it can also be assumed that a registration in the IM CN subsystem will also fail. In such cases, subject to the lower layers indicating that the network does support emergency bearer services in limited service state (see 3GPP TS 25.331 [9A]), the procedures for emergency calls without registration can be applied, as defined in subclause 5.1.6.8.2. If the GPRS authentication procedure has already succeeded during the latest normal or emergency ATTACH procedure, the UE shall perform an initial emergency registration, as described in subclause 5.1.6.2 before attempting an emergency call as described in subclause 5.1.6.8.3. NOTE 1: The UE can determine that GPRS authentication procedure has succeeded during the emergency ATTACH procedure when an integrity protection algorithm is received in the RRC signalling SECURITY MODE COMMAND message (see 3GPP TS 25.331 [9A]). When activating a PDP context to perform emergency registration, the UE shall request a PDP context for emergency bearer services as defined in 3GPP TS 24.008 [8]. The procedures for PDP context activation and P-CSCF discovery, as described in subclause B.2.2.1 of this specification apply accordingly. In order to find out whether the UE is attached to the home PLMN or to the visited PLMN, the UE shall compare the MCC and MNC values derived from its IMSI with the MCC and MNC of the PLMN the UE is attached to. If the MCC and MNC of the PLMN the UE is attached to donot match with the MCC and MNC derived from the IMSI, then for the purpose of emergency calls in the IM CN subsystem the UE shall consider to be attached to a VPLMN. NOTE 2: In this respect an equivalent HPLMN, as defined in 3GPP TS 23.122 [4C] will be considered as a visited network. If the dialled number is equal to an emergency number stored in the ME, in the USIM or in the Local Emergency Number List (as defined in 3GPP TS 24.008 [8]), then the UE shall recognize a number as for an emergency call and performs the procedures in subclause B.2.2.6.1A. NOTE 3: The Extended Local Emergency Numbers List (see 3GPP TS 24.301 [8J]) does not apply in this IP-CAN. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.2A.1.1 and subclause 5.1.3.1, if: - the 380 (Alternate Service) response contains a Contact header field; - the value of the Contact header field is a service URN; and - the service URN has a top-level service type of "sos"; then the UE determines that "emergency service information is included" as described 3GPP TS 23.167 [4B]. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.3.1 if the 380 (Alternate Service) response does not contain a Contact header field with service URN that has a top-level service type of "sos", then the UE determines that "no emergency service information is included" as described 3GPP TS 23.167 [4B]. If the "emergency service information is included" as described 3GPP TS 23.167 [4B]: 1) if the URN in the Contact header field matches an emergency service URN in table B.2.2.6.1, then the type of emergency service is the value corresponding to the matching entry in table B.2.2.6.1; and 2) if the URN in the Contact header field does not match any emergency service URN in table B.2.2.6.1, then the type of emergency service is not identified. NOTE 4: In bullet 2), the URN in the Contact header field either contains "no emergency subservice type" as described in 3GPP TS 23.167 [4B] triggering an emergency call, or contains an "emergency subservice type that does not map into an emergency service category for the CS domain" as described in 3GPP TS 23.167 [4B] triggering a normal call when the dialled number is available or triggering an emergency call when the dialled number is not available. The country specific URN is an example of a "emergency subservice type that does not map into an emergency service category for the CS domain". When the emergency registration expires, the UE should disconnect the PDP context for emergency bearer services as defined in 3GPP TS 24.008 [8]. Upon receiving a 3xx other than 380 (Alternative service), 4xx, 5xx or 6xx response to an INVITE request for a UE detectable emergency call, the UE shall perform domain selection as specified in 3GPP TS 23.167 [4B] annex H, to re-attempt the emergency call. B.2.2.6.1A Type of emergency service derived from emergency service category value The type of emergency service for an emergency number is derived from the settings of the emergency service category value (bits 1 to 5 of the emergency service category value as specified in subclause 10.5.4.33 of 3GPP TS 24.008 [8]). Table B.2.2.6.1 below specifies mappings between a type of emergency service and an emergency service URN. The UE shall use the mapping to match an emergency service URN and a type of emergency service. If a dialled number is an emergency number but does not map to a type of emergency service the service URN shall be "urn:service:sos". Table B.2.2.6.1: Mapping between type of emergency service and emergency service URN Type of emergency service Emergency service URN Police urn:service:sos.police Ambulance urn:service:sos.ambulance Fire Brigade urn:service:sos.fire Marine Guard urn:service:sos.marine Mountain Rescue urn:service:sos.mountain NOTE 1: It is not possible for a UE to indicate more than one type of emergency service in an emergency service URN. If an IP-CAN, capable of providing local emergency numbers, did not provide a local emergency number that matches the dialled number (see subclause 5.1.6.1) and multiple types of emergency service can be derived for a dialled number from the information configured on the USIM then: - if the UE is in the HPLMN, the UE shall map any one of these types of emergency service to an emergency service URN as specified in table B.2.2.6.1; and - if the UE is in the VPLMN, the UE shall select "urn:service:sos". NOTE 2: If the Non-3GPP emergency number indicator within the Non-3GPP NW provided policies IE (see 3GPP TS 24.008 [8]) provided through registration procedures over 3GPP access is set to "use of non-3GPP emergency numbers permitted", the UE also considers WLAN provided local emergency numbers (see 3GPP TS 24.302 [8U], subclause 4.7). If the Non-3GPP NW provided policies IE provided through registration procedures over 3GPP access is set to "use of non-3GPP emergency numbers not permitted", the UE does not consider WLAN provided local emergency numbers. If the Non-3GPP NW provided policies IE is not provided through registration procedures over 3GPP access, the UE does not consider WLAN provided local emergency numbers. If an IP-CAN, capable of providing local emergency numbers, provided a local emergency number that matches the dialled number (see subclause 5.1.6.1), and: - if the UE can derive one or more types of emergency service from the information received from the IP-CAN for the dialled number and the UE cannot derive types of emergency service from the information configured on the USIM for the dialled number; or - if the UE is able to derive identical types of emergency service from both the information received from the IP-CAN for the dialled number and from the information configured on the USIM for the dialled number, then the UE shall map any one of these emergency service types to an emergency service URN as specified in table B.2.2.6.1. NOTE 3: How the UE resolves clashes where an emergency number is associated with one or more different types of emergency service configured in the USIM and in information received from the core network, is implementation dependent. B.2.2.6.1B Type of emergency service derived from extended local emergency number list Void B.2.2.6.2 eCall type of emergency service The UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". B.2.2.6.3 Current location discovery during an emergency call Void. B.2A Usage of SDP B.2A.0 General NOTE: When: - establishing a session which is not an emergency session; or - modifying a session which is not an emergency session; and if the IMSVoPS indicator is received in the "Network feature support" Information Element (see 3GPP TS 24.008 [8]), the UE constructs SDP based on the restrictions indicated in the IMSVoPS indicator. Regardless whether the IMSVoPS indicator indicating voice is supported or not, m-lines can be set to "audio" and exclude voice codecs from the SDP answer or SDP offer. B.2A.1 Impact on SDP offer / answer of activation or modification of PDP contexts for media by the core network If due to the activation of PDP context from the core network the related SDP media description needs to be changed the UE shall update the related SDP information by sending, within a SIP request, a new SDP offer for each of the existing SIP dialogs, If the UE receives a modification request from the core network for a PDP context that is used for one or more media streams in an ongoing SIP session, the UE shall: 1) if, due to the modification of the PDP context, the related SDP media description need to be changed, update the related SDP information by sending, with in a SIP request, a new SDP offer for each of the existing SIP dialogs , and respond to the PDP context modification request. NOTE: The UE can decide to indicate additional media streams as well as additional or different codecs in the SDP offer than those used in the already ongoing session. B.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE If the UE receives an SDP offer where the SDP offer includes all media streams for which the originating side indicated its local preconditions as met, if the precondition mechanism is supported by the terminating UE and the IP-CAN performs network-initiated resource reservation for the terminating UE and the available resources are not sufficient for the received offer the terminating UE shall indicate its local preconditions and provide the SDP answer to the originating side without waiting for resource reservation. NOTE 1: If the resource reservation is controlled by the GPRS IP-CAN, the resource reservation request is initiated by the core network after the P-CSCF has authorised the respective IP flows and provided the QoS requirements over the Rx interface to the PCRF as described in 3GPP TS 29.214 [13D]. NOTE 2: During the PDP context activation procedure the UE and the core network negotiate whether the UE or the GPRS IP-CAN is responsible for the resource reservation applicable to all PDP contexts within the activated PDP address/APN pair as described in 3GPP TS 24.008 [8]. B.2A.3 Emergency service NOTE: When establishing an emergency session or when modifying an emergency session, the IMSVoPS indicator does not influence handling of SDP offer and SDP answer. B.3 Application usage of SIP B.3.1 Procedures at the UE B.3.1.0 Registration and authentication The UE shall perform reregistration of a previously registered public user identity bound to any one of its contact addresses when changing to an IP-CAN for which usage is specified in annex R. The reregistration is performed using the new IP-CAN. NOTE 1: This document does not specify how the UE detects that the used IP-CAN has changed. The information that is forcing the reregistration is also used to generate the content for the P-Access-Network-Info header field. NOTE 2: The UE will send the reregistration irrespective of whether it has a SIP dialog or not. If the UE supports the 3GPP PS data off, then the UE shall in all REGISTER requests include the "+g.3gpp.ps-data-off" header field parameter defined in subclause 7.9.8 set to a value indicating the 3GPP PS data off status. When the UE sends a REGISTER request, if the 3GPP PS data off status is "active", then the UE shall only include media feature tags associated with services that are 3GPP PS data off exempt services in the g.3gpp.icsi-ref media feature tag, as defined in subclause 7.9.2 and RFC 3840 [62], for the IMS communication services it intends to use. If the UE is registered, and the 3GPP PS data off status is changed or the UE is provided by the network with a new list of 3GPP PS data off exempt services while the 3GPP PS data off status is "active", then the UE shall perform a reregistration of the previously registered public user identity. B.3.1.0a IMS_Registration_handling policy The IMS_Registration_handling policy indicates whether the UE deregisters from IMS after a configured amount of time after receiving an indication that the IMS Voice over PS Session is not supported. The UE may support the IMS_Registration_handling policy. If the UE supports the IMS_Registration_handling policy, the UE may support being configured with the IMS_Registration_handling policy using one or more of the following methods: a) the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and c) the IMS_Registration_Policy node of 3GPP TS 24.167 [8G]. If the UE is configured with both the IMS_Registration_Policy node of 3GPP TS 24.167 [8G] and the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the IMS_Registration_Policy node of the EFIMSConfigData file shall take precedence. NOTE 1: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [15B]. If the UE is registered with IMS and the IMSVoPS indicator, provided by the lower layers (see 3GPP TS 24.301 [8J]), indicates voice is not supported, the UE shall: A) if the Stay_Registered_When_VoPS_Not_Supported leaf indicates requirement to stay registered, the UE needs not to deregister and maintains the registration as required for IMS services; or NOTE 2: The UE will periodically refresh the registration when needed. B) if the Stay_Registered_When_VoPS_Not_Supported leaf indicates requirement to deregister and the Deregistration_Timer leaf used to configure the NoVoPS-dereg timer defined in table 7.8.1 contains a timer value for the time to wait before deregistrerting from IMS, start a timer with the value indicated in the policy and: a) if the timer expires before the UE receives an indication from the lower layers that IMS voice is supported: 1) if there is no ongoing IMS session, either performs reregistration as specified in subclause 5.1.1.4 and shall only include feature tags associated with services that are independent of the IMSVoPS indicator or deregister from the IMS following the procedures specified in subclause 5.1.1.6; or 2) if there is ongoing IMS session, and i) if the UE does not receive indication from the lower layer that the IMS voice is supported before the ongoing IMS session is terminated, either performs reregistration as specified in subclause 5.1.1.4 and shall only include feature tags associated with services that are independent of IMSVoPS indicator or deregister from the IMS following the procedures specified in subclause 5.1.1.6 as soon as the ongoing IMS based service is terminated ; or ii) if the UE receives indication from the lower layer that the IMS voice is supported before the ongoing IMS session is terminated, cancel the timer; or NOTE 3: How the UE selects reregistration or deregistration is implementation dependent (e.g., SMS service) b) if the UE receives an indication from the lower layers that IMS voice is supported before the timer expires, cancel the timer. If the IMS_Registration_handling policy is not configured, the UE behaviour is implementation specific. B.3.1.1 P-Access-Network-Info header field The UE shall always include the P-Access-Network-Info header field where indicated in subclause 5.1. B.3.1.1A Cellular-Network-Info header field Not applicable. B.3.1.2 Availability for calls The UE indicates to the non-access stratum the status of being available for voice over PS when: 1) the UE is capable of receiving any (but not necessarily all) of the media types which the CS domain supports, such that the media type can also be used when accessing the IM CN subsystem using the current IP-CAN; 2) if the media type of item 1 is an "audio" media type, the UE supports codecs suitable for (conversational) speech, the "audio" media type is not restricted from inclusion in an SDP message according to the media type restriction policy as specified in subclause 6.1.1, and: a) 3GPP PS data off status is "inactive"; b) 3GPP PS data off status is "active", the UE is in the HPLMN or the EHPLMN, and MMTEL voice is a 3GPP PS data off exempt service; or c) 3GPP PS data off status is "active", the UE is in the VPLMN, the UE is configured with an indication that MMTEL voice is a 3GPP PS data off exempt service in a VPLMN, and MMTEL voice is a 3GPP PS data off roaming exempt service; and 3) the UE determines a contact has been bound to a public user identity using the IP-CAN, such that this contact is expected to be used for the delivery of incoming requests in the IM CN subsystem relating to such media. The UE indicates to the non-access stratum the status of being not available for voice over PS when these conditions are no longer met. NOTE: The status of being not available for voice over PS is used for domain selection for UE originating sessions / calls specified in 3GPP TS 23.221 [6] subclause 7.2a. B.3.1.2A Availability for SMS The UE determines that the UE is able to use SMS using IMS if the UE: I) is capable of using the MIME type "application/vnd.3gpp.sms" (see 3GPP TS 24.341 [8L]), such that the MIME type can also be used when accessing the IM CN subsystem using the current IP-CAN; II) supports the role of an SM-over-IP sender (see 3GPP TS 24.341 [8L]); IIA) determines the PDP context used for SIP signalling exists; III) determines a contact has been bound to a public user identity using the IP-CAN, such that this contact is expected to be used for the delivery of incoming requests in the IM CN subsystem relating to such media; IV) the UE does not determine that SMS over IP is restricted in 3GPP TS 24.341 [8L] subclause 5.2.1.3; and V) the 3GPP PS data off status is: - "inactive"; - "active", the UE is in the HPLMN or the EHPLMN, and SMS over IMS is a 3GPP PS data off exempt service; or - "active", the UE is in the VPLMN, the UE is configured with an indication that SMS over IMS is a 3GPP PS data off exempt service in a VPLMN, and SMS over IMS is a 3GPP PS data off roaming exempt service. When above criteria are not matched, the UE determines that SMS using IMS is unavailable. NOTE: The status that SMS using IMS is unavailable is used for domain selection for UE originating SMS specified in 3GPP TS 23.221 [6] subclause 7.2c. B.3.1.3 Authorization header field Void. B.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Upon receiving an INVITE request not including the "precondition" option-tag in the Supported header field and not including the "precondition" option-tag in the Require header field, and the IP-CAN performs network-initiated resource reservation for the UE, the UE: 1) if the INVITE request contains an SDP offer and the local resources required at the terminating UE for the received SDP offer are not available: a) shall not alert the user; and b) shall send 183 (Session Progress) response to the INVITE request without waiting for resource reservation and without alerting the user. If the INVITE request includes a Supported header field indicating support of reliable provisional responses, the UE shall send the 183 (Session Progress) response reliably. In the 183 (Session Progres) response, the UE shall include an SDP answer; and 2) if the INVITE request does not contain an SDP offer and the INVITE request includes a Supported header field indicating support of reliable provisional responses: a) shall generate an SDP offer; and b) if the local resources required at the terminating UE for the generated SDP offer are not available: A) shall not alert the user; and B) shall reliably send 183 (Session Progress) response to the INVITE request without waiting for resource reservation and without alerting the user. In the 183 (Session Progres) response, the UE shall include the generated SDP offer. Upon successful reservation of local resources, if the precondition mechanism is not used by the terminating UE, the UE can send 180 (Ringing) response to the INVITE request and can alert the user. B.3.1.5 3GPP PS data off If the 3GPP PS data off status is "active" the UE shall only send initial requests that: 1) are associated with a 3GPP IMS service which enforces 3GPP PS data off; NOTE: These services are specified in 3GPP TS 22.011 [1C], and enforcement of 3GPP PS data off is described in the respective service specifications. 2) are associated with an emergency service; or 3) are associated with 3GPP PS data off exempt services configured in the UE using one or more of the following methods: - the non_3GPP_ICSIs_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G] is not configured; - the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the VPLMN; - the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] is not configured; or - the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the VPLMN. If the UE is configured with both the non_3GPP_ICSIs_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. If the UE is configured with both the non_3GPP_ICSIs_roaming_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. If the 3GPP PS data off status changes from "inactive" to "active" the UE shall release all dialogs that 1) are not associated with a 3GPP IMS service which enforces 3GPP PS data off; NOTE: These services are specified in 3GPP TS 22.011 [1C], and enforcement of 3GPP PS data off is described in the respective service specifications. 2) are not associated with an emergency service; and 3) are not associated with 3GPP data off exempt services configured in the UE using one or more of the following methods: - the non_3GPP_ICSIs_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G] is not configured; - the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the VPLMN;- the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] is not configured; or - the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the VPLMN. If the UE is configured with both the non_3GPP_ICSIs_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. If the UE is configured with both the non_3GPP_ICSIs_roaming_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. B.3.1.6 Transport mechanisms No additional requirements are defined. B.3.1.7 RLOS Not applicable. B.3.2 Procedures at the P-CSCF B.3.2.0 Registration and authentication Void. B.3.2.1 Determining network to which the originating user is attached In order to determine from which network the request was originated the P-CSCF shall check the MCC and MNC fields received in the P-Access-Network-Info header field. NOTE: The above check can be against more than one MNC code stored in the P-CSCF. B.3.2.2 Location information handling Void. B.3.2.3 Prohibited usage of PDN connection for emergency bearer services If the P-CSCF detects that a UE uses a PDN connection for emergency bearer services for a non-emergency REGISTER request, the P-CSCF shall reject that request by a 403 (Forbidden) response. NOTE: By assigning specific IP address ranges for a PDN connection for emergency bearer services and configuring those ranges in P-CSCF, the P-CSCF can detect based on the registered Contact address if UE uses an emergency PDN connection for initial registration. B.3.2.5 Void B.3.2.6 Resource sharing If P-CSCF supports resource sharing, PCC is supported for this access technology and if according to local policy, the P-CSCF shall apply the procedures in subclause L.3.2.6. B.3.2.7 Priority sharing If P-CSCF supports priority sharing, PCC is supported for this access technology and if according to operator policy, the P-CSCF shall apply the procedures in subclause L.3.2.7. B.3.2.8 RLOS Not applicable. B.3.3 Procedures at the S-CSCF B.3.3.1 Notification of AS about registration status Not applicable B.3.3.2 RLOS Not applicable. B.4 3GPP specific encoding for SIP header field extensions B.4.1 Void B.5 Use of circuit-switched domain When an emergency call is to be set up over the CS domain, the UE shall attempt it according to the procedures described in 3GPP TS 24.008 [8]. NOTE: 3GPP TS 24.301 [8J] specifies additional requirements for the UE in determining the type of setup message the UE sends to the network when an emergency call is to be set up over the CS domain. Annex C (normative): UICC and USIM Aspects for access to the IM CN subsystem C.1 Scope This clause describes the UICC and USIM aspects for access to the IM CN subsystem. Additional requirements related to UICC usage for access to the IM CN subsystem are described in 3GPP TS 33.203 [19]. C.2 Derivation of IMS parameters from USIM In case the UE is loaded with a UICC that contains a USIM but does not contain an ISIM, the UE shall: - generate a private user identity; - generate a temporary public user identity; and - generate a home network domain name to address the SIP REGISTER request to. All these three parameters are derived from the IMSI parameter in the USIM, according to the procedures described in 3GPP TS 23.003 [3]. Also in this case, the UE shall derive new values every time the UICC is changed, and shall discard existing values if the UICC is removed. NOTE: If there is an ISIM and a USIM on a UICC, the ISIM is used for authentication to the IM CN subsystem, as described in 3GPP TS 33.203 [19]. See also subclause 5.1.1.1A. C.3 ISIM Location in 3GPP Systems For 3GPP systems, if ISIM is present, it is contained in UICC. C.3A UICC access to IMS If the UE supports the UICC access to IMS USAT feature defined in 3GPP TS 31.111 [15D] the following procedures in addition to the UE procedures in this specification apply. If the EFUICCIARI contains a list of IARIs associated with active applications installed on the UICC in either the USIM or the ISIM, then when performing the user-initiated registration procedure as described in subclause 5.1.1.2 the UE shall include in the REGISTER request the list of IARIs associated with active applications installed on the UICC in addition to any IARI values for active applications installed on the ME in g.3gpp.iari-ref media feature tag(s) in the Contact header field of the REGISTER request as defined in subclause 7.9.3 and RFC 3840 [62]. If the UE receives from the UICC an initial request for a dialog or a standalone transaction then after decapsulating the request as specified in 3GPP TS 31.111 [15D] the UE shall send the request to the IM CN subsystem as specified in subclause 5.1.2A. When the UE receives from the UICC subsequent requests or responses related to dialogs or transactions already established for UICC applications then after decapsulating the request or response as specified in 3GPP TS 31.111 [15D] the UE shall send the request or response to the IM CN subsystem as specified in subclause 5.1.2A. NOTE: The encapsulated requests and responses transferred between the UICC and UE are complete and valid SIP requests and responses compliant with RFC 3261 [26]. When sending requests or responses received from the UICC to the IM CN subsystem the UE shall modify or include any header fields necessary (such as Route, Via, Contact) in order to conform with the procedures in this specification. C.4 Update of IMS parameters on the UICC 3GPP TS 31.102 [15C] and 3GPP TS 31.103 [15B] specify the file structure and contents for the preconfigured parameters stored on the USIM and ISIM, respectively, necessary to initiate the registration to the IM CN subsystem. Any of these parameters can be updated via Data Download or a USAT application, as described in 3GPP TS 31.111 [15D]. If one ore more EFs are changed and a REFRESH command is issued by the UICC, then the UE reads the updated parameters from the UICC as specified for the REFRESH command in 3GPP TS 31.111 [15D]. If the UE supports the UICC access to IMS USAT feature defined in 3GPP TS 31.111 [15D] and the EFUICCIARI changes in either the USIM or the ISIM, the UE shall perform the user-initiated reregistration procedure as described in subclause 5.1.1.4 with the new values of the IARI parameter(s) residing on the UICC. In case of changes to EFs other than the EFUICCIARI, the UE is not required to perform deregistration but it shall wait for the network-initated deregistration procedures to occur as described in subclause 5.4.1.5 unless the user initiates deregistration procedures as described in subclause 5.1.1.6. From this point onwards the normal initial registration procedures can occur. Annex D (normative): Void Annex E (normative): IP-Connectivity Access Network specific concepts when using xDSL, Fiber or Ethernet to access IM CN subsystem E.1 Scope The present annex defines IP-CAN specific requirements for a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is xDSL, Fiber or Ethernet. NOTE: Fixed-broadband access in this Annex refers to xDSL, Fiber and Ethernet accesses. E.2 Fixed broadband aspects when connected to the IM CN subsystem E.2.1 Introduction A UE accessing the IM CN subsystem, and the IM CN subsystem itself, utilise the services provided by the fixed-broadband access network to provide packet-mode communication between the UE and the IM CN subsystem. Requirements for the IP Edge node, defined in ETSI ES 282 001 [138]in support of this communication are outside the scope of this document and specified elsewhere. From the UEs perspective, it is assumed that one or more IP-CAN bearer(s) are provided, in the form of connection(s) managed by the layer 2 (e.g. DSL modem supporting the UE). In the first instance, it is assumed that the IP-CAN bearer(s) is (are) statically provisioned between the UE and the IP Edge node, defined in ETSI ES 282 001 [138], according to the user's subscription. It is out of the scope of the current Release to specify whether a single IP-CAN bearer is used to convey both signalling and media flows, or whether several PVC connections are used to isolate various types of IP flows (signalling flows, conversational media, non conversational media…). The end-to-end characteristics of the fixed-broadband IP-CAN bearer depend on the type of access network, and on network configuration. The description of the network PVC termination (e.g., located in the DSLAM, in the BRAS…) is out of the scope of this annex. E.2.2 Procedures at the UE E.2.2.1 Activation and P-CSCF discovery Fixed-broadband bearer(s) is (are) statically provisioned in the current Release. Unless a static IP address is allocated to the UE, prior to communication with the IM CN subsystem, the UE shall perform a Network Attachment procedure depending on the used fixed-broadband access type. When using a fixed-broadband access, both IPv4 and IPv6 UEs may access the IM CN subsystem. The UE may request a DNS Server IPv4 address(es) via RFC 2132 [20F] or a DNS Server IPv6 address(es) via RFC 3315 [40]. The methods for P-CSCF discovery are: I. When using IPv4, employ the Dynamic Host Configuration Protocol (DHCP) RFC 2132 [20F], the DHCPv4 options for SIP servers RFC 3361 [35A], and RFC 3263 [27A] as described in subclause 9.2.1. When using IPv6, employ Dynamic Host Configuration Protocol for IPv6 (DHCPv6) RFC 3315 [40], the DHCPv6 options for SIP servers RFC 3319 [41] and DHCPv6 options for Domain Name Servers (DNS) RFC 3646 [56C] as described in subclause 9.2.1. In case the DHCP server provides several P-CSCF addresses or FQDNs to the UE, the UE shall select the P-CSCF address or FQDN as indicated in RFC 3319 [41]. If sufficient information for P-CSCF address selection is not available, selection of the P-CSCF address by the UE is implementation specific. II. The UE selects a P-CSCF from the list in the IMS management object as specified in 3GPP TS 24.167 [8G]. The UE shall use method II to select a P-CSCF if the IMS management object contains the P-CSCF list. Otherwise, the UE shall use method I to select a P-CSCF. E.2.2.1A Modification of a fixed-broadband connection used for SIP signalling Not applicable. E.2.2.1B Re-establishment of a fixed-broadband connection used for SIP signalling Not applicable. E.2.2.1C P-CSCF restoration procedure A UE supporting the P-CSCF restoration procedure uses the keep-alive procedures described in RFC 6223 [143]. If the P-CSCF fails to respond to keep-alive requests the UE shall acquire a different P-CSCF address using any of the methods described in the subclause E.2.2.1 and perform an initial registration as specified in subclause 5.1. E.2.2.2 Void E.2.2.3 Void E.2.2.4 Void E.2.2.5 Fixed-broadband bearer(s) for media E.2.2.5.1 General requirements The UE can establish media streams that belong to different SIP sessions on the same fixed-broadband bearer. E.2.2.5.1A Activation or modification of fixed-broadband bearers for media by the UE If the UE receives indication within the SDP according to RFC 3524 [54] that media stream(s) belong to group(s), and if several fixed-broadband bearers are available to the UE for the session, the media stream(s) may be sent on separate fixed-broadband bearers according to the indication of grouping. The UE may freely group media streams to fixed-broadband bearers in case no indication of grouping is received from the P-CSCF. If the UE receives media grouping attributes in accordance with RFC 3524 [54] that it cannot provide within the available fixed-broadband bearer(s), then the UE shall handle such SDP offers in accordance with RFC 3388 [53]. The UE can receive a media authorization token in the P-Media-Authorization header field from the P-CSCF according to RFC 3313 [31]. If a media authorization token is received in the P-Media-Authorization header field when a SIP session is initiated, the UE shall reuse the existing fixed-broadband bearer(s) and ignore the media authorization token. E.2.2.5.1B Activation or modification of fixed-broadband bearers for media by the network Not applicable. E.2.2.5.1C Deactivation of fixed-broadband bearers for media Not applicable. E.2.2.5.2 Special requirements applying to forked responses Since the UE is unable to perform bearer modification, forked responses place no special requirements on the UE. E.2.2.5.3 Unsuccessful situations Not applicable. E.2.2.6 Emergency service E.2.2.6.1 General If attached to network via fixed-broadband access technology, the UE shall always consider being attached to its home operator's network for the purpose of emergency calls. NOTE: In fixed-broadband the UE is unable to receive any indication from the network, that would allow the UE to determine, whether it is currently attached to its home operator's network or to a different network, so the UE assumes itself always attached to the home operator's network when connected via fixed-broadband access technology. E.2.2.6.1A Type of emergency service derived from emergency service category value Not applicable. E.2.2.6.1B Type of emergency service derived from extended local emergency number list Not applicable. E.2.2.6.2 eCall type of emergency service The UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". E.2.2.6.3 Current location discovery during an emergency call Void. E.2A Usage of SDP E.2A.0 General Not applicable. E.2A.1 Impact on SDP offer / answer of activation or modification of xDSL bearer for media by the network Not applicable. E.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE Not applicable. E.2A.3 Emergency service No additional procedures defined. E.3 Application usage of SIP E.3.1 Procedures at the UE E.3.1.0 Registration and authentication In order to reach IMS in some access networks, the UE may support: - address and/or port number conversions provided by a NA(P)T or NA(P)T-PT as described in annex F and annex K; and - UE requested FTT-IMS establishment procedure specified in 3GPP TS 24.322 [8Y]. If a UE supports one or both of these capabilities then a UE may progressively try them to overcome failure to reach the IMS. Use of these capabilities shall have the following priority order: 1) UE uses neither capability because reaching the IMS without an intervening NA(P)T, NA(P)T-PT, or tunnel is preferred. 2) UE may use address and/or port number conversions provided by a NA(P)T or NA(P)T-PT as described in either annex F or annex K. 3) UE may use the UE requested FTT-IMS establishment procedure specified in 3GPP TS 24.322 [8Y]. If the UE uses the UE-requested FTT-IMS establishment procedure specified in 3GPP TS 24.322 [8Y], the UE considers itself to: - be configured to send keep-alives; - be directly connected to an IP-CAN for which usage of NAT is defined; and - be behind a NAT. Optional procedures apply when the UE is supporting traversal of restrictive non-3GPP access network using STUN/TURN/ICE, as follows: a) the protection of SIP messages is provided by utilizing TLS as defined in 3GPP TS 33.203 [19]; b) the mechanisms specified in this annex shall only be applicable when the IP traffic to the IMS core does not traverse through the Evolved Packet Core (EPC); c) the UE shall establish the TLS connection to the P-CSCF on port 443 as defined in 3GPP TS 33.203 [19]. The UE shall use SIP digest with TLS for registration as specified in subclause 5.1. If the TLS connection is established successfully, the UE sends SIP signalling over the TLS connection to the P-CSCF; d) the UE shall support the keep-alive procedures described in RFC 6223 [143]; NOTE 1: If the UE is configured to use an HTTP proxy, the UE use the HTTP CONNECT method specified in RFC 2817 [220] to request the HTTP proxy to establish the TCP connection with the P-CSCF. Once the UE has received a positive reply from the proxy that the TCP connection has been established, the UE initiates the TLS handshake with the P-CSCF and establishes the TLS connection. e) the procedures described in subclause K.5.2 apply with the additional procedures described in the present subclause; f) when using the ICE procedures for traversal of restrictive non-3GPP access network, the UE shall support the ICE TCP as specified in RFC 6544 [131] and TURN TCP as specified in RFC 6062 [221]. g) if the UE is configured to use TURN over TCP on port 80, the UE shall establish the TCP connection to TURN server on port 80. If the UE is configured to use TURN over TLS on port 443, the UE shall establish the TLS connection to the TURN server on port 443 as defined in 3GPP TS 33.203 [19]. If the UE is configured to use both, the UE should prefer to use TURN over TCP on port 80 to avoid TLS overhead; h) if the connection is established successfully, the UE sends TURN control messages and media packets over the connection as defined in RFC 5766 [101]. NOTE 2: If the UE is configured to use an HTTP proxy, the UE use the HTTP CONNECT method specified in RFC 2817 [220] to request the HTTP proxy to establish the TCP connection with the TURN server. Then, if the UE is configured to use TURN over TLS on port 443 and the UE has received a positive reply from the proxy that the TCP connection has been established, the UE initiates the TLS handshake with the TURN server and establishes the TLS connection. E.3.1.0a IMS_Registration_handling policy Not applicable. E.3.1.1 P-Access-Network-Info header field The UE may, but need not, include the P-Access-Network-Info header field where indicated in subclause 5.1. E.3.1.1A Cellular-Network-Info header field Not applicable. E.3.1.2 Availability for calls Not applicable. E.3.1.2A Availability for SMS Void. E.3.1.3 Authorization header field When using SIP digest or SIP digest without TLS, the UE need not include an Authorization header field on sending a REGISTER request, as defined in subclause 5.1.1.2.1. NOTE: In case the Authorization header field is absent, the mechanism only supports that one public user identity is associated with only one private user identity. The public user identity is set so that it is possible to derive the private user identity from the public user identity by removing SIP URI scheme and the following parts of the SIP URI if present: port number, URI parameters, and To header field parameters. Therefore, the public user identity used for registration in this case cannot be shared across multiple UEs. Deployment scenarios that require public user identities to be shared across multiple UEs that don't include an private user identity in the initial REGISTER request can be supported as follows: - Assign each sharing UE a unique public user identity to be used for registration, - Assign the shared public user identitiess to the implicit registration set of the unique registering public user identities assigned to each sharing UE. E.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Not applicable. E.3.1.5 3GPP PS data off Not applicable. E.3.1.6 Transport mechanisms No additional requirements are defined. E.3.1.7 RLOS Not applicable. E.3.2 Procedures at the P-CSCF E.3.2.0 Registration and authentication The P-CSCF may support UEs connected via restrictive non-3GPP access network. If the P-CSCF supports UEs connected via restrictive non-3GPP access network, when the P-CSCF receives a 200 (OK) response to a REGISTER request, if the contact address of REGISTER request contains an IP address assigned by the EFTF, and the UE's Via header field contains a "keep" header field parameter, then the P-CSCF shall add a value to the "keep" header field parameter of the UE's Via header field of the 200 (OK) response as defined in RFC 6223 [143]. Optional procedures apply when the P-CSCF is supporting traversal of restrictive non-3GPP access network using STUN/TURN/ICE, as follows: NOTE: In this scenario, the restrictive non-3GPP access network coexists with NA(P)T device located in the customer premises domain: a) the protection of SIP messages is provided by utilizing TLS as defined in 3GPP TS 33.203 [19]; b) the P-CSCF supporting these additional procedures should use SIP digest with TLS as defined in subclause 5 and the P-CSCF should inserts an IMS-ALG on the media plane; c) the mechanisms specified in this annex shall only be applicable when the IP traffic to the IMS core does not traverse through the Evolved Packet Core (EPC); d) the P-CSCF shall support the procedures defined in subclause 5.2, with the exception that the P-CSCF shall use SIP over TLS on port 443 as defined in 3GPP TS 33.203 [19]; e) when the UE has indicated support of the keep-alive mechanism defined in RFC 6223 [143], the P-CSCF shall indicate to the UE that it supports the keep-alive mechanism; and f) the IMS-ALG in the P-CSCF shall support ICE procedures, as defined in subclause 6.7.2.7. E.3.2.1 Determining network to which the originating user is attached In order to determine from which network the request was originated the P-CSCF shall check if the location information received in the network provided and/or UE provided "dsl-location", "eth-location" or "fiber-location" parameter in the P-Access-Network-Info header field(s) belongs to a location in the same country. NOTE 1: If local policy does not require the insertion of P-Access-Network-Info header field in the P-CSCF even if it is missing in the received initial request, the P-CSCF can assume that the request is initiated by fixed broadband UE in the same country. NOTE 2: If the location information in the network provided and UE provided "dsl-location", "eth-location" or "fiber-location" parameters (in a request that includes two P-Access-Network-Info header fields) is contradictory, or the two P-Access-Network-Info header fields indicate different access types the P-CSCF ignores either the network provided or the UE provided information according to operator policy. E.3.2.2 Location information handling Upon receipt of an initial request for a dialog or standalone transaction or an unknown method, the P-CSCF based on local policy may include a P-Access-Network-Info header field.The value of the "dsl-location", "eth-location" or "fiber-location" parameter shall be the value as received in the Location-Information header in the User-Data Answer command as specified in ETSI ES 283 035 [98]. NOTE: The way the P-CSCF deduce that the request comes from a UE connected through xDSL access is implementation dependent. E.3.2.3 Void E.3.2.4 Void E.3.2.5 Void E.3.2.6 Resource sharing Not applicable. E.3.2.7 Priority sharing Not applicable. E.3.2.8 RLOS Not applicable. E.3.3 Procedures at the S-CSCF E.3.3.1 Notification of AS about registration status Not applicable E.3.3.2 RLOS Not applicable. E.4 3GPP specific encoding for SIP header field extensions E.4.1 Void E.5 Use of circuit-switched domain There is no CS domain in this access technology. Annex F (normative): Additional procedures in support for hosted NAT NOTE: This subclause describes the mechanism for support of the hosted NAT scenario. This does not preclude other mechanisms but they are out of the scope of this annex. F.1 Scope This annex describes the UE and P-CSCF procedures in support of hosted NAT. In this scenario, both the media flows and the SIP signalling both traverse a NA(P)T device located in the customer premises domain. The term "hosted NAT" is used to address this function. When receiving an initial SIP REGISTER request without integrity protection, the P-CSCF can, determine whether to perform the hosted NAT procedures for the user identified by the REGISTER request by comparing the address information in the top-most SIP Via header field with the IP level address information from where the request was received. The P-CSCF will use the hosted NAT procedure only when the address information do not match. NOTE: There is no need for the P-CSCF to resolve a domain name in the Via header field when UDP encapsulated tunnel mode for IPsec is used. The resolution of a domain name in the Via header field is not required by RFC 3261 [26]. In order to provide hosted NAT traversal for SIP REGISTER requests without integrity protection and the associated responses, the P-CSCF makes use of the "received" header field parameter as described in RFC 3261 [26] and, in addition, if UDP is used, makes use of the "rport" header field parameter as described in RFC 3581 [56A]. The hosted NAT traversal for protected SIP messages is provided by applying UDP encapsulation to IPSec packets in accordance with RFC 3948 [63A]. Alternativly to the procedures defined in subclause F.2 which are employed to support the hosted NAT scenario where the security solution is based on UDP encapsulated IPSec as defined in 3GPP TS 33.203 [19], subclause F.4 provides procedures for NAT traversal for security solutions that are not defined in 3GPP TS 33.203 [19]. Use of such security solutions is outside the scope of this document. F.2 Application usage of SIP F.2.1 UE usage of SIP F.2.1.1 General This subclause describes the UE SIP procedures for supporting hosted NAT scenarios. The description enhances the procedures specified in subclause 5.1. The UE shall support the symmetric response routeing mechanism according to RFC 3581 [56A]. F.2.1.2 Registration and authentication F.2.1.2.1 General The text in subclause 5.1.1.1 applies without changes F.2.1.2.1A Parameters contained in the ISIM The text in subclause 5.1.1.1A applies without changes F.2.1.2.1B Parameters provisioned to a UE without ISIM or USIM The text in subclause 5.1.1.1B applies without changes. F.2.1.2.2 Initial registration The procedures described in subclause 5.1.1.2.1 apply with the additional procedures described in the present subclause. NOTE 1: In accordance with the definitions given in subclause 3.1 the IP address acquired initially by the UE in a hosted NAT scenario is the UE private IP address. On sending a REGISTER request, the UE shall populate the header fields as indicated in subclause 5.1.1.2.1 with the exceptions of subitems c) and d) which are modified as follows The UE shall populate: c) a Contact header field according to the following rules: if the REGISTER request is sent without integrity protection, the Contact header field shall be set to include SIP URI(s) containing the private IP address of the UE in the hostport parameter or FQDN. If the UE supports GRUU, the UE shall include a "+sip.instance" header field parameter containing the instance ID. If the REGISTER request is integrity protected, the UE shall include the public IP address or FQDNin the hostport parameter. The UE shall only use a FQDN in a protected REGISTER request, if it is ensured that the FQDN resolves to the public IP address of the NAT. If the UE supports GRUU, the UE shall include a "+sip.instance" header field parameter containing the instance ID. The UE shall include all supported ICSI values (coded as specified in subclause 7.2A.8.2) in a g.3gpp.icsi-ref media feature tag as defined in subclause 7.9.2 and RFC 3840 [62] for the IMS communication services it intends to use, and IARI values (coded as specified in subclause 7.2A.9.2), for the IMS applications it intends to use in a g.3gpp.iari-ref media feature tag as defined in subclause 7.9.3 and RFC 3840 [62]; NOTE 2: The UE will learn its public IP address from the "received" header field parameter in the topmost Via header field in the 401 (Unauthorized) response to the unprotected REGISTER request. d) a Via header field according to the following rules: if the REGISTER request is sent without integrity protection, the Via header field shall be set to include the private IP address or FQDN of the UE in the sent-by field. If the REGISTER request is integrity protected, the UE shall include the public IP address or FQDN in the sent-by field. The UE shall only use a FQDN in a protected REGISTER request, if it is ensured that the FQDN resolves to the public IP address of the NAT. Unless the UE has been configured to not send keep-alives, it shall include a "keep" header field parameter with no value in the Via header field, in order to indicate support of sending keep-alives associated with, the registration, as described in RFC 6223 [143]; NOTE 3: If the UE specifies a FQDN in the host parameter in the Contact header field and in the sent-by field in the Via header field of an unprotected REGISTER request, this FQDN will not be subject to any processing by the P-CSCF or other entities within the IM CN subsystem. The means to ensure that the FQDN resolves to the public IP address of the NAT are outside of the scope of this specification. One option for resolving this is local configuration. If IMS AKA is used as a security mechanism, on sending a REGISTER request, as defined in subclause 5.1.1.2.1, the UE shall additionally populate the header fields as defined in subclause 5.1.1.2.2, with the exceptions of subitems c), and d) which are modified as follows: d) the Security-Client header field set to specify the security mechanisms the UE supports, the IPsec layer algorithms the UE supports and the parameters needed for the security association setup. The UE shall support the setup of two pairs of security associations as defined in 3GPP TS 33.203 [19]. The syntax of the parameters needed for the security association setup is specified in Annex H of 3GPP TS 33.203 [19]. The UE shall support the "ipsec-3gpp" security mechanism, as specified in RFC 3329 [48]. The UE shall support the IPSec layer algorithms for integrity protection and for encryption as defined in 3GPP TS 33.203 [19], and shall announce support for them according to the procedures defined in RFC 3329 [48]. In addition to transport mode the UE shall support UDP encapsulated tunnel mode as per RFC 3948 [63A] and shall announce support for both modes as described in TS 33.203 [19]; When a 401 (Unauthorized) response to a REGISTER is received and this response is received without integrity protection, the procedures described in subclause 5.1.1.2.1 apply with the following additions: The UE shall compare the IP address in the "received" header field parameter with the corresponding value in the sent-by parameter in the topmost Via header field to detect if the UE is behind a NAT. If the comparison indicates that the respective values are the same, the UE concludes that it is not behind a NAT. - If the UE is not behind a NAT, the UE shall proceed with the procedures described in subclause 5.1 of the main body of this specification; - If the UE is behind a NAT, the UE shall verify using the Security-Server header field that mode "UDP-enc-tun" is selected. If the verification succeeds the UE shall store the IP address contained in the "received" header field parameter as the UE public IP address. If the verification does not succeed the UE shall abort the registration. When the UE detects that it is behind a NAT, the UE may include a transport=tcp URI parameter in the Contact header when it sends a protected REGISTER. NOTE 4: The UE includes a transport=tcp parameter to ensure that P-CSCF uses TCP connection when it receives an initial request for a dialog or a request for a standalone transaction destined for the UE. In addition, when a 401 (Unauthorized) response to a REGISTER is received (with or without integrity protection) the UE shall behave as described in subclause F.2.1.2.5. When the UE, that is behind a NAT, receives a 400 (Bad Request) response with 301 Warning header field indicating "incompatible network address format" to the unprotected REGISTER request, the UE shall randomly select new values for the protected server port and the protected client port, and perform new initiate registration procedure by sending an unprotected REGISTER request containing the new values in the Security-Client header field. NOTE 5: This release of the present document does not specify any specific procedures for bulk number registration according to RFC 6140 [191]for hosted NAT scenarios. F.2.1.2.3 Initial subscription to the registration-state event package The procedures described in subclause 5.1.1.3 apply with the additional procedures described in subclause F.2.1.4.1. F.2.1.2.4 User-initiated reregistration The procedures described in subclause 5.1.1.4.1 apply with the additional procedures described in the present subclause. On sending a REGISTER request that does not contain a challenge response, the UE shall populate the header fields as indicated in subclause 5.1.1.4.1 with the exception of subitems c) and d) which are modified as follows. The UE shall populate: c) a Contact header field set to include SIP URI(s) that contain(s) in the hostport parameter the public IP address of the UE or FQDN, and containing the instance ID of the UE in the "+sip.instance" header field parameter, if the UE supports GRUU. The UE shall only use a FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT. The UE shall include all supported ICSI values (coded as specified in subclause 7.2A.8.2) in a g.3gpp.icsi-ref media feature tag as defined in subclause 7.9.2 and RFC 3840 [62] for the IMS communication services it intends to use, and IARI values (coded as specified in subclause 7.2A.9.2), for the IMS applications it intends to use in a g.3gpp.iari-ref media feature tag as defined in subclause 7.9.3 and RFC 3840 [62]. If the UE has detected it is behind a NAT, the UE may include a transport=tcp URI parameter in the Contact header; d) a Via header field set to include the public IP address or FQDN of the UE in the sent-by field. The UE shall only use a FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT. For the TCP, the response is received on the TCP connection on which the request was sent. If the UE previously has previously negotiated sending of keep-alives associated with the registration, it shall include a "keep" header field parameter with no value in the Via header field, in order to indicate continous support to send keep-alives, as described in RFC 6223 [143]; NOTE 1: The means to ensure that the FQDN resolves to the public IP address of the NAT are outside of the scope of this specification. One option for resolving this is local configuration. When the UE, that is behind a NAT, receives a 400 (Bad Request) response with 301 Warning header field indicating "incompatible network address format" to the REGISTER request that does not contain a challenge response, the UE shall randomly select a new value for the protected client port, and send the REGISTER request containing the new values in the Security-Client header field. NOTE 2: The protected server port stays fixed for a UE until all public user identities of the UE have been de-registered. NOTE 3: This release of the present document does not specify any specific procedures for bulk number re-registration according to RFC 6140 [191] for hosted NAT scenarios. F.2.1.2.5 Authentication F.2.1.2.5.1 IMS AKA - general The procedures of subclause 5.1.1.5.1 apply with with the additional procedures described in the present subclause. On receiving a 401 (Unauthorized) response to the REGISTER request and the response is deemed to be valid, the UE shall behave as of subclause 5.1.1.5.1 with the exception of subitem 3) which is modified as follows. The UE shall: 3) send another REGISTER request using the temporary set of security associations to protect the message. The header fields are populated as defined for the initial request (see subclause F.2.1.2.2), with the addition that the UE shall include an Authorization header field containing the private user identity and the authentication challenge response calculated by the UE using RES and other parameters, as described in RFC 3310 [49] when AKAv1 is used or as described in RFC 4169 [227] when AKAv2 is used. The UE shall also insert the Security-Client header field that is identical to the Security-Client header field that was included in the previous REGISTER request (i.e. the REGISTER request that was challenged with the received 401 (Unauthorized) response). The UE shall also insert the Security-Verify header field into the request, by mirroring in it the content of the Security-Server header field received in the 401 (Unauthorized) response. The UE shall set the Call-ID of the integrity protected REGISTER request which carries the authentication challenge response to the same value as the Call-ID of the 401 (Unauthorized) response which carried the challenge. Whenever the 200 (OK) response is not received before the temporary SIP level lifetime of the temporary set of security associations expires or a 403 (Forbidden) response is received, the UE shall consider the registration to have failed. The UE shall delete the temporary set of security associations it was trying to establish, and use the old set of security associations. The UE should send an unprotected REGISTER request according to the procedure specified in subclause F.2.1.2.2 if the UE considers the old set of security associations to be no longer active at the P-CSCF. F.2.1.2.5.2 Void F.2.1.2.5.3 IMS AKA abnormal cases The text in subclause 5.1.1.5.3 applies without changes. F.2.1.2.5.4 SIP digest – general Not applicable. F.2.1.2.5.5 SIP digest – abnormal procedures Not applicable. F.2.1.2.5.6 SIP digest with TLS – general Not applicable. F.2.1.2.5.7 SIP digest with TLS – abnormal procedures Not applicable. F.2.1.2.5.8 Abnormal procedures for all security mechanisms The text in subclause 5.1.1.5.8 applies without changes. F.2.1.2.5A Network-initiated re-authentication The text in subclause 5.1.1.5A applies without changes. F.2.1.2.5B Change of IPv6 address due to privacy The text in subclause 5.1.1.5B applies without changes. F.2.1.2.6 User-initiated deregistration The procedures of subclause 5.1.1.6.1 apply with with the additional procedures described in the present subclause. On sending a REGISTER request, the UE shall populate the header fields as indicated in subclause 5.1.1.6 with the exception of subitems d) and e) which are modified as follows. The UE shall populate: c) a Contact header field set to either the value of "*" or SIP URI(s) that contain(s) in the hostport parameter the IP address of the UE or FQDN; and containing the instance ID of the UE in the "+sip.instance" header field parameter, if the UE supports GRUU. The UE shall only use a FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT; d) a Via header field set to include the IP address or FQDN of the UE in the sent-by field. The UE shall only use a FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT; NOTE 1: In case of hosted NAT traversal only the UE public IP addresses are bound to security associations. NOTE 2: The means to ensure that the FQDN resolves to the public IP address of the NAT are outside of the scope of this specification. One option for resolving this is local configuration. NOTE 3: This release of the present document does not specify any specific procedures for bulk number re-registration according to RFC 6140 [191] for hosted NAT scenarios.F.2.1.2.7 Network-initiated deregistration The procedures of subclause 5.1.1.7 apply with with the additional procedures described in the present subclause. Upon receipt of a NOTIFY request on the dialog which was generated during subscription to the reg event package as described in subclause 5.1.1.3, including one or more <registration> element(s) which were registered by this UE with: - the state attribute set to "terminated" and the event attribute set to "rejected" or "deactivated"; or - the state attribute set to "active" and the state attribute within the <contact> element belonging to this UE set to "terminated", and associated event attribute element to "rejected" or "deactivated"; the UE shall remove all registration details relating to these public user identities. In case of a "deactivated" event attribute, the UE shall start the initial registration procedure as described in subclause F.2.1.2.2. In case of a "rejected" event attribute, the UE shall release all dialogs related to those public user identities. F.2.1.3 Subscription and notification The text in subclause 5.1.2 applies without changes. F.2.1.4 Generic procedures applicable to all methods excluding the REGISTER method F.2.1.4.1 UE originating case The procedures described in subclause 5.1.2A.1 apply with the additional procedures described in the present subclause. When the UE sends any request, the requirements in subclause 5.1.2A.1 are replaced by the following requirements. The UE shall include: - a Via header field set to include the public IP address of the UE or FQDN and the protected server port in the sent-by field. The UE shall only use a FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT; and if this is a request for a new dialog, and the request includes a Contact header field, then the UE should populate the Contact header field as follows: 1) if a public GRUU value ("pub-gruu" header field parameter) has been saved associated with the public user identity to be used for this request, and the UE does not indicate privacy of the P-Asserted-Identity, then insert the public GRUU ("pub-gruu" header field parameter) value in the Contact header field as specified in RFC 5627 [93]; or 2) if a temporary GRUU value ("temp-gruu" header field parameter) has been saved associated with the public user identity to be used for this request, and the UE does indicate privacy of the P-Asserted-Identity, then insert the temporary GRUU ("temp-gruu" header field parameter) value in the Contact header field as specified in RFC 5627 [93]. If this is a request within an existing dialog, and the request includes a Contact header field, and the contact address previously used in the dialog was a GRUU, then the UE should insert the previously used GRUU value in the Contact header field as specified in RFC 5627 [93]. If the UE did not insert a GRUU in the Contact header field, then the UE shall include the public IP address of the UE or FQDN and the protected server port in the hostport parameter in any Contact header field that is otherwise included. The UE shall only use a FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT. NOTE: The means to ensure that the FQDN resolves to the public IP address of the NAT are outside of the scope of this specification. One option for resolving this is local configuration. The UE shall discard any SIP response that is not integrity protected and is received from the P-CSCF outside of the registration and authentication procedures. The requirements on the UE within the registration and authentication procedures are defined in subclause F.2.1.2.4. When a SIP transaction times out, i.e. timer B, timer F or timer H expires at the UE, the UE may behave as if timer F expired, as described in subclause F.2.1.2.3. F.2.1.4.2 UE terminating case The procedures described in subclause 5.1.2A.2 apply with the additional procedures described in the present subclause. When the UE sends any response, the requirements in subclause 5.1.2A.1 are replaced by the following requirement. If the response includes a Contact header field, and the response is not sent within an existing dialog, then the UE should populate the Contact header field as follows: 1) if a public GRUU value ("pub-gruu" header field parameter) has been saved associated with the public user identity from the P-Called-Party-ID header field, and the UE does not indicate privacy of the P-Asserted-Identity, then insert the public GRUU ("pub-gruu" header field parameter) value in the Contact header field as specified in RFC 5627 [93]; and 2) if a temporary GRUU value ("temp-gruu" header field parameter) has been saved associated with the public user identity from the P-Called-Party-ID header field, and the UE does indicate privacy of the P-Asserted-Identity, then the UE should insert the temporary GRUU ("temp-gruu" header field parameter) value in the Contact header field as specified in RFC 5627 [93]. If the UE did not insert a GRUU in the Contact header field, then the UE shall: - include the public IP address of the UE or FQDN and the protected server port in the hostport parameter in any Contact header field that is otherwise included. The UE shall only use a FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT. NOTE: The means to ensure that the FQDN resolves to the public IP address of the NAT are outside of the scope of this specification. One option for resolving this is local configuration. The UE shall discard any SIP request that is not integrity protected and is received from the P-CSCF outside of the registration and authentication procedures. The requirements on the UE within the registration and authentication procedures are defined in subclause F.2.1.2. F.2.2 P-CSCF usage of SIP F.2.2.1 Introduction This subclause describes the SIP procedures for supporting hosted NAT scenarios. The description enhances the procedures specified in subclause 5.2. The P-CSCF shall support the symmetric response routeing mechanism according to RFC 3581 [56A]. NOTE: Symmetric response routeing is used to support hosted NAT and applicable only to initial, unprotected REGISTER requests and corresponding responses. F.2.2.2 Registration The procedures described in subclause 5.2.2 apply with the additional procedures described in the present subclause. When the P-CSCF receives a REGISTER request from the UE, the P-CSCF shall behave as of subclause 5.2.2.1. If IMS AKA is the security mechanism, when the P-CSCF receives a REGISTER request from the UE, the P-CSCF shall perform the procedures of subclause 5.2.2.2 with the following exception to items 2) and 3): 2) in case the REGISTER request was received without integrity protection, then: a) check the existence of the Security-Client header field. If the Security-Client header field is not present, then the P-CSCF shall return a suitable 4xx response. If the Security-Client header field is present the P-CSCF shall: - in case the UE indicated support for "UDP-enc-tun" then remove and store it. - in case the UE does not indicate support for "UDP-enc-tun" then: - if the host portion of the sent-by field in the topmost Via header field contains an IP address that differs from the source address of the IP packet, silently drop the REGISTER; - otherwise continue with procedures as of subclause 5.2.2. NOTE 1: If the UE does not indicate support for "UDP-enc-tun" and the P-CSCF detects that the UE is located behind a NAT device, then the P-CSCF can just drop the REGISTER to avoid unnecessary signalling traffic. b) if the host portion of the sent-by field in the topmost Via header field contains a FQDN, or if it contains an IP address that differs from the source address of the IP packet, the P-CSCF shall: - add a "received" header field parameter in accordance with the procedure defined in RFC 3581 [56A]. If the "rport" header field parameter is included in the Via header field, the P-CSCF shall also set the value of the "rport" header field parameter to the source port of the requestin accordance with the procedure defined in RFC 3581 [56A]; and - check that no any previously registered UE has either the same public IP address (allocated by the NAT and indicated in the Via header field) and the protected server port (specified in the Security-Client header field) or the same public IP address and the protected client port (specified in the Security-Client header field). If there is such UE, the P-CSCF shall return a 400 (Bad Request) response with 301 Warning header field indicating "incompatible network address format" to the unprotected REGISTER request. Otherwise, the P-CSCF shall forward the REGISTER request. NOTE 2: If two UEs are behind the same NAT, the NAT can assign to them the same public IP address (but different NAT's port). Hence, the two respective UE will have different protected server port numbers, and different protected client port numbers. 3) in case the REGISTER request was received integrity protected, then the P-CSCF shall: a) check the security association which protected the request. If the security association is a temporary one, the P-CSCF shall: - in case the host parameter in the Contact address is in the form of a FQDN, ensure that the given FQDN will resolve (e.g., by reverse DNS lookup) to the IP address bound to the security association; - in case the P-CSCF has detected earlier that the UE is located behind a NAT, retrieve port_Uenc from the encapsulating UDP header of the packet received and complete configuration of the temporary set of security associations by configuring port_Uenc in each of the temporary security associations; - check whether the request contains a Security-Verify header field in addition to a Security-Client header field. If there are no such header fields, then the P-CSCF shall return a suitable 4xx response. If there are such header fields, then the P-CSCF shall compare the content of the Security-Verify header field with the content of the Security-Server header field sent earlier and the content of the Security-Client header field with the content of the Security-Client header field received in the challenged REGISTER. If those do not match, then there is a potential man-in-the-middle attack. The request should be rejected by sending a suitable 4xx response. If the contents match, the P-CSCF shall remove the Security-Verify and the Security-Client header field; b) if the security association the REGISTER request was received on, is an already established one, then the P-CSCF shall: - remove the Security-Verify header field if it is present; - check if the Security-Client header field containing new parameter values is present, and: - if this header field or any required parameter is missing, then the P-CSCF shall return a suitable 4xx response. - if this header field and the required parameters are present, then the P-CSCF shall check that no any previously registered UE has the same public IP address and the protected client port (specified in the Security-Client header field). If there is such UE, the P-CSCF shall return a 400 (Bad Request) response with 301 Warning header field indicating "incompatible network address format" to the REGISTER request. Otherwise, the P-CSCF shall remove and store the Security-Client header field before forwarding the request to the S-CSCF; NOTE 3: When sending the protected REGISTER request to the P-CSCF, the UE will not modify the protected server port value, since the protected server port value stays fixed for a UE until all public user identities of the UE have been de-registered. When the P-CSCF receives a 401 (Unauthorized) response to an unprotected REGISTER request: 1) if this response contains a "received" header field parameter in the Via header field associated with the UE; 2) if the request associated with the response was received: A) using UDP and this response contains a "rport" header field parameter in the Via header field associated with the UE; or B) using TCP; and 3) the UE indicated support for "UDP-enc-tun" IPsec mode; the P-CSCF shall: 1) delete any temporary set of security associations established towards the UE; 2) remove the "ck" and "ik" WWW-Authenticate header field parameters contained in the 401 (Unauthorized) response and bind the values to the proper private user identity and to the temporary set of security associations which will be setup as a result of this challenge. The P-CSCF shall forward the 401 (Unauthorized) response to the UE if and only if the "ck" and "ik" header field parameters have been removed; 3) insert a Security-Server header field in the response, containing the P-CSCF security list and the parameters needed for the security association setup, as specified in Annex H of 3GPP TS 33.203 [19]. The P-CSCF shall support the "ipsec-3gpp" security mechanism, as specified in RFC 3329 [48]. The P-CSCF shall support the IPSec layer algorithms for integrity protection and for encryption as defined in 3GPP TS 33.203 [19]. The P-CSCF shall indicate "UDP-enc-tun" as the only IPsec mode; 4) set up the temporary set of security associations with a temporary SIP level lifetime between the UE and the P-CSCF for the user identified with the private user identity. The P-CSCF shall select UDP encapsulated tunnel mode and shall leave the value for port-Uenc unspecified in each of the temporary security associations. For further details see 3GPP TS 33.203 [19] and RFC 3329 [48]. The P-CSCF shall set the temporary SIP level lifetime for the temporary set of security associations to the value of reg-await-auth timer; and 5) send the 401 (Unauthorized) response unprotected to the UE using the mechanisms described in RFC 3261 [26] and RFC 3581 [56A], i.e. in case UDP is used as transport protocol the P-CSCF shall send the response to the IP address indicated in the "received" header field parameter and to the port indicated in the "rport" header field parameter of the Via header field associated with the UE. In case UDP is used as transport protocol, the P-CSCF shall use the IP address and the port on which the REGISTER request was received as source IP address and the source port when sending the response back to the UE. When the P-CSCF receives a 401 (Unauthorized) response to a protected REGISTER request and that REGISTER request was protected by an old set of security associations that use UDP encapsulated tunnel mode, the P-CSCF shall: 1) delete any temporary set of security associations established towards the UE; 2) remove the "ck" and "ik" WWW-Authenticate header field parameters contained in the 401 (Unauthorized) response and bind the values to the proper private user identity and to the temporary set of security associations which will be setup as a result of this challenge. The P-CSCF shall forward the 401 (Unauthorized) response to the UE if and only if the "ck" and "ik" header field parameters have been removed; 3) insert a Security-Server header field in the response, containing the P-CSCF security list and the parameters needed for the security association setup, as specified in Annex H of 3GPP TS 33.203 [19]. The P-CSCF shall support the "ipsec-3gpp" security mechanism, as specified in RFC 3329 [48]. The P-CSCF shall support the IPsec layer algorithms for integrity protection and encryption as defined in 3GPP TS 33.203 [19]. The P-CSCF shall indicate "UDP-enc-tun" as the IPsec mode; 4) set up the temporary set of security associations with a temporary SIP level lifetime between the UE and the P-CSCF for the user identified with the private user identity. The P-CSCF shall select UDP encapsulated tunnel mode and shall specify the same port_Uenc that was used in the old set of security associations. The P-CSCF shall set the temporary SIP level lifetime for the temporary set of security associations to the value of reg-await-auth timer; and 5) send the 401 (Unauthorized) response to the UE using the old set of security associations. Otherwise, when the P-CSCF receives a 401 (Unauthorized) response to an unprotected REGISTER request and: - this response does not contain a "received" header field parameter in the Via header field associated with the UE; - this response does not contain "rport" header field parameter in the Via header field associated with the UE and the request associated with the response was received using UDP; or - when the P-CSCF receives a 401 (Unauthorized) response to a protected REGISTER request and that REGISTER request was protected by an old set of security associations that do not use UDP encapsulated tunnel mode; the P-CSCF shall proceed as described in subclause 5.2.2.2. F.2.3 S-CSCF usage of SIP F.2.3.1 S-CSCF usage of SIP F.2.3.1.1 Protected REGISTER with IMS AKA as a security mechanism The procedures at the S-CSCF described in subclause 5.4.1.2.2 apply. NOTE: When two UEs that are behind the same NAT register their contact addresses, the NAT can assign to them the same public IP address (but different NAT's ports). If these two UEs select the same protected server port number, and register via different P-CSCFs, then they will have the same contact addresses (i.e. same IP address and protected server port). However, any request targeted to either UE will be sent to the respective P-CSCF, hence not causing any ambiguity at the P-CSCF when forwarding the request via NAT. F.3 Void F.4 P-CSCF usage of SIP in case UDP encapsulated IPsec is not employed F.4.1 Introduction The subclause F.4 describes the SIP procedures for supporting hosted NAT scenarios in case UDP encapsulated IPsec is not employed. In these scenarios the procedures for NAT traversal must take into account that all SIP requests and responses are not protected by an IPsec security association. This subclause also assumes that the UE transmits the SIP messages from the same IP address and port on which the UE expects to receive SIP messages. F.4.2 Registration The procedures described in subclause 5.2.2 apply with the additional procedures described in the present clause. When the P-CSCF receives a REGISTER request from the UE, the P-CSCF shall add the "received" header field parameter to the Via header field set to the source IP address of the packet header in accordance with the procedure defined in RFC 3261 [26] and RFC 3581 [56A]. If the "rport" header field parameter is included in the Via header field, the P-CSCF shall also set the value of the "rport" header field parameter to the source port of the request, in accordance with the procedure defined in RFC 3581 [56A]. When the P-CSCF detects that the UE is behind a NAT: - if the UE has indicated in the received REGISTER request support of the keep-alive mechanism defined in SIP outbound (RFC 5626 [92]) according to RFC 6223 [143], the P-CSCF shall indicate to the UE that it supports the keep-alive mechanism; and - if the UE has not indicated in the received REGISTER request support of the keep-alive mechanism defined in SIP outbound (RFC 5626 [92]) according to RFC 6223 [143]: a) if a P-CSCF registration timer is running, the P-CSCF should not forward the REGISTER request if received half of the time before expiry of the S-CSCF registration timer, unless the request is intended to update the UE's capabilities according to RFC 3840 [62] or to modify the ICSI values or IARI values that the UE intends to use in the g.ims.app-ref feature tag. If the P-CSCF decides to not forward the REGISTER request, the P-CSCF shall build a 200 (OK) response based on the contents of the 200 (OK) response to the previous REGISTER request and send this response to the UE. If the P-CSCF decides to forward the REGISTER request, the P-CSCF shall set the registration expiration interval to the registration expiration interval value indicated in the received 200 (OK) response to the previous REGISTER request; and b) when the P-CSCF receives a 200 (OK) response to the REGISTER request, the P-CSCF shall modify the value of the Expires header field and/or Expires parameter in the Contact header according to the transport protocol. In order to minimize the number of REGISTER requests to the S-CSCF, the P-CSCF may also start a P-CSCF registration timer with a value of 600 seconds if the value received from the S-CSCF was for greater than 1200 seconds, or to half of the time otherwise. If, upon receiving a REGISTER request from an unregistered user and the P-CSCF discovers that the UE is behind a NAT, the P-CSCF performs the following actions on the Contact header field depending on its content: - if the Contact header field contains a contact address in the form of an IP address (NOTE), the P-CSCF shall save (for the duration of the registration) this IP address (i.e. the private IP address of the UE) and associated port number (i.e. the private port of the UE) and bind them to the source IP address (i.e. the public IP address of the NAT) and the source port number (i.e. the port number of the NAT) of the IP packet that contained the REGISTER request and forward the REGISTER request; - if the Contact header field contains more than one contact addresses in the form of an IP address, the P-CSCF shall apply the above procedure to one of those contact addresses by choosing the one with the highest qvalue parameter) and delete any other contact addresses containing an IP address. If the P-CSCF was unable to choose a contact address based on the qvalue, the P-CSCF shall choose one based on local policy and delete any other contact addresses containing an IP address. NOTE: When the host parameter in the Contact address is in the form of a FQDN, the P-CSCF will resolve the given FQDN (by DNS lookup) to the IP address of the UE. When including the FQDN in the Contact header field the UE insures that the FQDN resolves to the IP address that the UE uses to send the REGISTER request. When the P-CSCF received a response to the above request, the P-CSCF shall forward the response to the UE using the mechanisms described in RFC 3581 [56A]. In case UDP is used, the P-CSCF shall send the response to the IP address indicated in the "received" header field parameter and to the port indicated in the "rport" header field parameter of the Via header field in the response. If the REGISTER request received from the UE was received over a TCP connection, the P-CSCF shall send the response to the UE over the same TCP connection over which the request was received. The P-CSCF shall transmit the IP packet (containing the response) from the same IP address and port on which the REGISTER request was received. F.4.3 General treatment for all dialogs and standalone transactions excluding the REGISTER method F.4.3.1 Introduction The procedures described in subclause 5.2.6 apply with the additional procedures described in subclause F.4.3. F.4.3.2 Request initiated by the UE When the P-CSCF receives, from the UE that is behind a NAT, an initial request for a dialog or a request for a standalone transaction, the P-CSCF shall: a) if the "rport" header field parameter is included in the Via header field, set the value of the "rport" header field parameter in the Via header field to the source port of the received IP packet that contained the request; aa) insert the "received" header field parameter in the Via header field containing the source IP address of the received IP packet (that contained the request), as defined in RFC-3581 [56A]; b) if the request is a dialog-forming request that was received over UDP, bind the source IP address (i.e. the public IP address of the NAT) and associated source port number (i.e. the port number of the NAT) of the received IP packet (that contained the initial dialog-forming request) to: - the IP address (i.e. the private IP address of the UE) and associated port number (i.e. the private port of the UE) contained in the Contact header field of the received dialog-forming request, if the Contact header field contained an IP address and associated port number, and save the binding; or - the saved IP address (i.e. the private IP address of the UE) and associated port number (i.e. the private port of the UE) contained in the Contact header field of the REGISTER request, if the Contact header field of the received dialog-forming request contained a GRUU, and save the binding; and c) if the dialog-forming request was received over TCP connection, keep this TCP connection up during the entire duration of the dialog; before forwarding the request, based on the topmost Route header field, in accordance with the procedures of RFC 3261 [26]. When the P-CSCF receives a response to the above request, the P-CSCF shall forward the response to the UE using the mechanisms described in RFC 3581 [56A]. In case UDP is used, the P-CSCF shall send the response to the IP address indicated in the "received" header field parameter and to the port indicated in the "rport" header field parameter of the Via header field of the response. If the dialog-forming request received from the UE was received over the TCP connection, the P-CSCF shall send the response to the UE over the same TCP connection over which the dialog-forming request was received. The P-CSCF shall transmit the IP packet (containing the response) from the same IP address and port on which the initial dialog-forming request was received. For all subsequent requests belonging to the dialog, received from the UE, the P-CSCF shall: - insert the "received" header field parameter in the Via header field as described in RFC 3261 [26]; - if the "rport" header field parameter is included in the Via header field, set the value of the "rport" header field parameter in the Via header field as defined in RFC 3581 [56A]; and - forward the request as described in RFC 3261 [26]. For all subsequent responses belonging to the dialog, destined for the UE, the P-CSCF shall forward the responses using the "received" header field parameter and if UDP is used, set the value of the "rport" header field parameter in the Via header field of the response as defined in RFC 3581 [56A]. For all subsequent requests belonging to the dialog and destined for the UE (that contains the private IP address and associated private port number in the Request-URI), the P-CSCF shall send the requests to the UE either: - over the TCP connection that was established when the initial INVITE request was received; or - use UDP. When sending the request using UDP, the P-CSCF shall insert the request in an IP packet, and send the IP packet to the saved IP address (i.e. the public IP address of the NAT) and associated port number (i.e. the port number of the NAT). The P-CSCF shall transmit the IP packet (containing the request) from the same IP address and port on which the REGISTER request was received. NOTE: When inserting its SIP URI in the Record-Route header field of the dialog-forming request received from the UE, the P-CSCF can include a pointer in the user part of its SIP URI that points to the saved binding used to route the in-dialog requests to the UE. The Route header field of the in-dialog requests will contain the respective pointer in the user part of the P-CSCF's SIP URI. F.4.3.3 Request terminated by the UE When the P-CSCF receives an initial request for a dialog or a request for a standalone transaction destined for the UE (it contains the private IP address and associated private port number in the Request-URI), the P-CSCF shall send the requests to the UE either: - over the TCP connection for the related registration or registration flow (if the multiple registrations mechanism is used), if available (e.g. TCP connection was established during the registration procedure); or - use UDP. When sending the request using UDP, the P-CSCF shall send the request to the saved IP address (i.e. the public IP address of the NAT) and associated port number (i.e. the port number of the NAT) for the related registration or registration flow (if the multiple registrations mechanism is used) that is bound to the private IP address and associated private port number indicated in the Request-URI and saved during the registration procedure. The P-CSCF shall transmit the IP packet (containing the request) from the same IP address and port on which the REGISTER request was received. NOTE 1: If the Contact bound to the terminating UE's registration state includes a transport=tcp URI parameter, for the terminating requests, the P-CSCF follows the procedures specified in RFC 3261 [26] subclause 7 and RFC 3263 [27A] subclause 4.1 for selection of the transport, which recommend to use the TCP connection. For all subsequent requests belonging to the dialog that are received from the UE, the P-CSCF shall: - insert the "received" header field parameter in the Via header field as defined in RFC 3261 [26]; - if the "rport" header field parameter is included in the Via header field, set the value of the "rport" header field parameter in the Via header field as defined in RFC 3581 [56A]; and - forward the request as described in RFC 3261 [26]. For all subsequent responses belonging to the dialog, destined or the UE, the P-CSCF shall forward the responses using the "received" header field parameter and if UDP is used, set the value of the "rport" header field parameter in the Via header field of the response as defined in RFC 3581 [56A]. For all subsequent requests belonging to the dialog and destined for the UE (that contains the private IP address and associated private port number in the Request-URI), the P-CSCF shall send the requests to the UE either: - over the TCP connection, if available; or - use UDP. When sending the request using UDP, the P-CSCF shall insert the request in an IP packet, and send the IP packet to the saved IP address (i.e. the public IP address of the NAT) and associated port number (i.e. the port number of the NAT). The P-CSCF shall transmit the IP packet (containing the request) from the same IP address and port on which the REGISTER request was received. NOTE 2: When inserting its SIP URI in the Record-Route header field in a response to the dialog-forming request received from the UE, the P-CSCF can include a pointer in the user part of its SIP URI that points to the saved binding used to route the in-dialog requests to the UE. The Route header field of the in-dialog requests will contain the respective pointer in the user part of the P-CSCF's SIP URI. F.5 NAT traversal for media flows To allow the IMS access gateway to perform address latching, for a given UDP-based media stream, the UE shall use the same port number for sending and receiving packets. To allow early media flows, the UE shall send keepalive messages for each UDP-based media stream as soon as an SDP offer or answer is received in order to allow the IMS access gateway to perform address latching before the call is established. To keep NAT bindings and firewall pinholes open for the UDP-based media streams, and enable the IMS access gateway to perform address latching, the UE shall send keepalive messages for each media stream as defined in subclause K.5.2.1. Annex G (informative): Void Annex H (normative): IP-Connectivity Access Network specific concepts when using DOCSIS to access IM CN subsystem H.1 Scope The present annex defines IP-CAN specific requirements for a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is a DOCSIS cable access network. DOCSIS (Data Over Cable Service Interface Specification) is a term referring to the Recommendation ITU-T J112 [87] Annex B standard for cable modem systems. H.2 DOCSIS aspects when connected to the IM CN subsystem H.2.1 Introduction A UE accessing the IM CN subsystem, and the IM CN subsystem itself, utilise the services provided by the DOCSIS cable access network to provide packet-mode communication between the UE and the IM CN subsystem. From the perspective of the UE, the necessary IP-CAN bearer for signalling is transparently available to the UE. The UE is not directly involved in requests for IP-CAN bearer(s) for media flow(s). The IM CN interacts with the PCRF in the DOCSIS IP-CAN to establish IP-CAN bearer(s) for media flow(s), on behalf of the UE. H.2.2 Procedures at the UE H.2.2.1 Activation and P-CSCF discovery Prior to communication with the IM CN subsystem, the UE shall perform a Network Attachment procedure as defined in the CableLabs PacketCable specifications PKT-TR-ARCH-FRM [88]. When using DOCSIS, both IPv4 and IPv6 UEs may access the IM CN subsystem. The procedures for P-CSCF discovery defined in subclause 9.2.1 of this document apply. H.2.2.1A Modification of IP-CAN used for SIP signalling Not applicable. H.2.2.1B Re-establishment of the IP-CAN used for SIP signalling Not applicable. H.2.2.1C P-CSCF restoration procedure A UE supporting the P-CSCF restoration procedure uses the keep-alive procedures described in RFC 6223 [143]. If the P-CSCF fails to respond to the keep-alive request the UE shall acquire a different P-CSCF address using any of the methods described in the subclause H.2.2.1 and perform an initial registration as specified in subclause 5.1. H.2.2.2 Void H.2.2.3 Void H.2.2.4 Void H.2.2.5 Handling of the IP-CAN for media H.2.2.5.1 General requirements The UE does not directly request resources for media flow(s). H.2.2.5.1A Activation or modification of IP-CAN for media by the UE Not applicable. H.2.2.5.1B Activation or modification of IP-CAN for media by the network Not applicable. H.2.2.5.1C Deactivation of IP-CAN for media Not applicable. H.2.2.5.2 Special requirements applying to forked responses The UE does not directly request resources for media flow(s). As a result there are no special UE requirements applying to forked responses. H.2.2.5.3 Unsuccessful situations Not applicable. H.2.2.6 Emergency service H.2.2.6.1 General If attached to network via DOCSIS access technology, the UE shall always consider being attached to its home operator's network for the purpose of emergency calls. NOTE: In DOCSIS the UE is unable to receive any indication from the network, that would allow the UE to determine, whether it is currently attached to its home operator's network or to a different network, so the UE assumes itself always attached to the home operator's network when connected via DOCSIS access technology. H.2.2.6.1A Type of emergency service derived from emergency service category value Not applicable. H.2.2.6.1B Type of emergency service derived from extended local emergency number list Not applicable. H.2.2.6.2 eCall type of emergency service The UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". H.2.2.6.3 Current location discovery during an emergency call Void. H.2A Usage of SDP H.2A.0 General Not applicable. H.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network Not applicable. H.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE Not applicable. H.2A.3 Emergency service No additional procedures defined. H.3 Application usage of SIP H.3.1 Procedures at the UE H.3.1.0 Void H.3.1.0a IMS_Registration_handling policy Not applicable. H.3.1.1 P-Access-Network-Info header field If the UE is aware of the access technology, the UE shall include the P-Access-Network-Info header field where indicated in subclause 5.1. H.3.1.1A Cellular-Network-Info header field Not applicable. H.3.1.2 Availability for calls Not applicable. H.3.1.2A Availability for SMS Void. H.3.1.3 Authorization header field When using SIP digest or SIP digest without TLS, the UE need not include an Authorization header field on sending a REGISTER request, as defined in subclause 5.1.1.2.1. NOTE: In case the Authorization header field is absent, the mechanism only supports that one public user identity is associated with only one private user identity. The public user identity is set so that it is possible to derive the private user identity from the public user identity by removing SIP URI scheme and the following parts of the SIP URI if present: port number, URI parameters, and To header field parameters. Therefore, the public user identity used for registration in this case cannot be shared across multiple UEs. Deployment scenarios that require public user identities to be shared across multiple UEs that don't include an private user identity in the initial REGISTER request can be supported as follows: - Assign each sharing UE a unique public user identity to be used for registration, - Assign the shared public user identitiess to the implicit registration set of the unique registering public user identities assigned to each sharing UE. H.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Not applicable. H.3.1.5 3GPP PS data off Not applicable. H.3.1.6 Transport mechanisms No additional requirements are defined. H.3.1.7 RLOS Not applicable. H.3.2 Procedures at the P-CSCF H.3.2.0 Registration and authentication Void. H.3.2.1 Determining network to which the originating user is attached If the access-type field in the P-Access-Network-Info header field indicated DOCSIS access the P-CSCF shall assume that the initial request for a dialog or standalone transaction or an unknown method destined for a PSAP is initiated in the same country. NOTE 1: If local policy does not require the insertion of P-Access-Network-Info header field in the P-CSCF even if it is missing in the received initial request, the P-CSCF can assume that the request is initiated by fixed broadband UE in the same country. NOTE 2: If the network provided and UE provided P-Access-Network-Info header fields indicate different access types the P-CSCF ignores the information in either the network provided or the UE provided P-Access-Network-Info header field according to operator policy. H.3.2.2 Location information handling Upon receipt of an initial request for a dialog or standalone transaction or an unknown method, the P-CSCF based on local policy may include a P-Access-Network-Info header field. NOTE: The way the P-CSCF deduces that the request comes from a UE connected through DOCSIS access is implementation dependent. H.3.2.3 Void H.3.2.4 Void H.3.2.5 Void H.3.2.6 Resource sharing Not applicable. H.3.2.7 RLOS Not applicable. H.3.3 Procedures at the S-CSCF H.3.3.1 Notification of AS about registration status Not applicable. H.3.3.2 RLOS Not applicable. H.4 3GPP specific encoding for SIP header field extensions H.4.1 Void H.5 Use of circuit-switched domain There is no CS domain in this access technology. Annex I (normative): Additional routeing capabilities in support of traffics in IM CN subsystem I.1 Scope Additional routeing functionality is necessary for support of: - transit traffic as operators may use the IM CN subsystem as a transit network to provide transit functionality for their own CS networks, enterprise networks, or other network operators; - other traffics such as roaming traffic and incoming traffic destined to CSI UEs (Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services) traffics; - traffic for the roaming architecture for voice over IMS with local breakout; and - originating traffic if required by local policy as specified in subclause 5.4.3.2. Depending on the additional routeing functionalities, the required specific functions may reside in a stand-alone entity or may be collocated with an MGCF, a BGCF, an I-CSCF, an S-CSCF, or an IBCF as appropriate for the specific scenario. When colocated with an I-CSCF, the additional routeing capabilities may be performed in advance of I-CSCF procedures as specified in subclause 5.3, or after I-CSCF procedures have failed to identify an S-CSCF supporting the user identified by the Request-URI. When colocated with an MGCF, the generated requests can be routed to an I-CSCF or to possible targets of the routeing procedures defined in subclause I.2. The BGCF procedures specified in subclause 5.6 are a subset of the more general routeing procedures provided in this annex. NOTE: Depending on the host entity for the additional routeing functions, the functionality can be accessed as: a) the last set of functions on the host before forwarding a request (e.g., on an MGCF, an S-CSCF or an IBCF); b) the first set of functions performed by the host entity when receiving a request at the host entity's entry point (e.g., on a BGCF, I-CSCF or IBCF); c) a specified point in the logic of the host (e.g., on the I-CSCF at failure to identify an S-CSCF for the Request-URI); or d) a set of functions associated with a separate entry point (e.g., at a separate entry point associated with a BGCF, I-CSCF, IBCF or stand-alone entity). I.1A General For all SIP transactions identified, if priority is supported, as containing an authorised Resource-Priority header field, or, if such an option is supported, relating to a dialog which previously contained an authorised Resource-Priority header field. The additional routeing functionality shall give priority over other transactions or dialogs. This allows special treatment of such transactions or dialogs. If priority is supported, the priority treatment of transactions or dialogs shall be adjusted according to the most recently received authorized Resource-Priority header field or backwards indication value. NOTE 1: The special treatment can include filtering, higher priority processing, routeing, call gapping. The exact meaning of priority is not defined further in this document, but is left to national regulation and network configuration. NOTE 2: These SIP transactions are exempt from network management controls. If logging is in progress for this dialog, check whether a trigger for stopping logging of SIP signalling has occurred, as described in RFC 8497 [140] and configured in the trace management object defined in 3GPP TS 24.323 [8K]. If a stop trigger event has occurred then stop logging of signalling, else determine, by checking its debug configuration, whether to log the response. With the exception of 305 (Use Proxy) responses, the additional routeing functionality shall not recurse on 3xx responses. If the additional routeing functionality inserts its own Record-Route header field, then the additional routeing functionality may require the periodic refreshment of the session to avoid hung states. If the network element requires the session to be refreshed, the additional routeing functionality shall apply the procedures described in RFC 4028 [58] clause 8. NOTE 3: Requesting the session to be refreshed requires support by at least one of the UEs. This functionality cannot automatically be granted, i.e. at least one of the involved UEs needs to support it. Based on local policy the additional routeing function shall add in requests and in responses in the P-Charging-Vector header field a "transit-ioi" header field parameter with an entry which identifies the operator network which the request or response is transitting or with a void entry. Based on local policy the additional routeing function shall delete or void in requests and in responses in the P-Charging-Vector header field any received "transit-ioi" header field parameter value. I.2 Originating, transit and interconnection routeing procedures The additional routeing functionality, or associated functional entity, performing these additional routeing procedures should analyse the destination address, and determine whether to route to another network, directly, or via the IBCF, or to the BGCF, the MGCF or the I-CSCF in its own network. This analysis may use public (e.g., DNS, ENUM) and/or private database lookups, and/or locally configured data and may, based on operator policy, modify the Request-URI (e.g. to remove number prefixes, to translate local numbers to global numbers, to update the Request-URI with the URI including an obtained ported-to routeing number, etc). In addition, and based upon local policy, the analysis may include the carrier identified by the "cic" tel-URI parameter of the Request-URI and other signalling information from the incoming request as part of the route determination. Examples of other signalling information are: the content of the P-Access-Network-Info header field, the value of the "cpc" tel URI parameter of the P-Asserted-Identity header field, the value of the "phone-context" Tel URI parameter of the Request-URI, the SDP content, the ICSI values in the Contact header field and the content of the P-Asserted-Service header field. If the additional routeing functionality decides that the request shall be routed via a specific entity (e.g. IBCF), it shall insert the URI of this entity in the Route header of the request. When provided as a stand-alone entity, the network element performing these functions need not Record-Route the INVITE request. When provided as a stand-alone entity, the network element performing these functions shall not apply the procedures of RFC 3323 [33] relating to privacy. If overlap signalling using the multiple-INVITE method is supported as a network option, several INVITE requests with the same Call ID and same From header field (including "tag" header field parameter) can be received outside of an existing dialog. Such INVITE requests relate to the same call and the additional routeing function shall route such INVITE request received during a certain period of timeto the same next hop. When colocated with a MGCF, based on local policy for calls originated from circuit-switched networks, if the circuit-switched is a transit network the additional routeing function shall add in requests in the P-Charging-Vector header field a "transit-ioi" header field parameter with an entry which identifies the PSTN network which the request was transitting or with a void entry. NOTE 1: Only one "transit-ioi" header field parameter entry is added per transit network. NOTE 2: The local policy can take bilateral agreements between operators into consideration. The entity implementing the additional routeing functionality shall remove the P-Served-User header field prior to forwarding the request. If a) the additional routeing functionality supports indicating the traffic leg as specified in RFC 7549 [225]; b) the Request-URI does not already include an "iotl" SIP URI parameter, and NOTE 3: If an "iotl" SIP URI parameter is included it contains the value "visitedA-homeB" inserted by the TRF in the roaming architecture for voice over IMS with local breakout scenario. c) required by local policy; then the additional routeing functionality shall: a) if the Request-URI contains a SIP URI, append the "iotl" SIP URI parameter set to "homeA-homeB" to the Request-URI; and b) if the Request-URI contains a tel URI: - convert the tel URI in the Request-URI to the form of a SIP URI with user=phone; and - append an "iotl" SIP URI parameter with a value set to "homeA-homeB" in the Request-URI. I.3 Providing IMS application services in support of transit & interconnection traffics I.3.1 Introduction When the IM CN subsystem provides transit functionality to other operator networks or enterprise networks, it may also provide IMS applications services to the operator network or enterprise network. The transit service invocation, performed by a transit function, is performed based on local configured transit invocation criteria that are provided for the specific transit scenario. NOTE: The transit invocation criteria for invocation is intended to be per served network basis, for which transit functionality is provided, and not per subscriber basis. Similar to the initial filter criteria for a user profile, the transit invocation criteria may have service point triggers, used to generate an ordered list of transit invocation criteria to be applied to a request, based on different information in the request, SIP method, SIP header field, and SIP body. The service invocation procedure shall support suppression/avoidance of conflicting services, multiple invocations of the same service and loopback scenarios. I.3.2 Procedures I.3.2.1 Treatment for dialog and standalone transactions When the transit function receives an initial request for a dialog, or a request for a standalone transaction, and the request is received either from a functional entity within the same trust domain or contains a valid original dialog identifier (see step 3) or the dialog identifier (From, To and Call-ID header fields) relates to an existing request processed by the transit function, then prior to forwarding the request, the transit function shall: 1) check if an original dialog identifier that the transit function previously placed in a Route header field is present in the topmost Route header field of the incoming request. - If not present, the transit function shall build an ordered list of transit invocation criteria. - If present, the request has been sent from an AS in response to a previously sent request, an ordered list of transit invocation criteria already exists and the transit function shall not change the ordered list of transit invocation criteria. 2) remove its own SIP URI from the topmost Route header field; 3) check whether the initial request matches any unexecuted transit invocation criteria. If there is a match, then the transit function shall select the first matching unexecuted transit invocation criteria from the ordered list of transit invocation criteria and the transit function shall insert the AS URI to be contacted into the Route header field as the topmost entry followed by its own URI populated; NOTE: Depending on the result of processing the transit invocation criteria the transit function can contact one or more AS(s) before processing the outgoing Request-URI. 4) if the request is not forwarded to an AS and if local policy requires the application of other additional routeing capabilities, handled by entities other than the transit function, the transit function shall apply the additional routeing capabilities if they are locally available or forward the request to an entity that implements the additional routeing capabilities; 5) determine the destination address (e.g. DNS access) using the URI placed in the topmost Route header field if present, otherwise based on the Request-URI. If the destination requires interconnect functionalities (e.g. the destination address is of an IP address type other than the IP address type used in the IM CN subsystem), the transit function shall forward the request to the destination address via an IBCF in the same network; 6) in case of an initial request for a dialog, based on local policy record-route; and 7) route the request based on SIP routeing procedures. When the transit function receives a target refresh request, or a a subsequent request other than target refresh request, for a dialog, prior to forwarding the request, the transit function shall: 1) remove its own URI from the topmost Route header field; and 2) forward the request based on the topmost Route header field. With the exception of 305 (Use Proxy) responses, the transit function shall not recurse on 3xx responses. I.3.2.1A Handling of header fields related to charging When the transit function receives a request from a functional entity that is not an AS and if the request is forwarded to an AS the transit function shall: - store the value of the "orig-ioi" header field parameter received in the P-Charging-Vector header field if present; NOTE 1: Any received "orig-ioi" header field parameter will be a type 2 IOI. The type 2 IOI identifies the service provider from which the request was sent. - remove the "orig-ioi" header field parameter from the P-Charging-Vector header field, if present; - store the value of the "transit-ioi" header field parameter and remove the "transit-ioi" header field parameter, if present; and - insert in the P-Charging-Vector header field an IOI type 3 value in an "orig-ioi" header field parameter identifying the network sending the request and based on operator option a Relayed-Charge header field with contents set to the value of the received "transit-ioi" header field parameter. When forwarding the request from an AS to a functional entity that is not an AS the transit function shall: - store the value of the "orig-ioi" header field parameter received in the P-Charging-Vector header field if present; NOTE 2: Any received "orig-ioi" header field parameter will be a type 3 IOI. The type 3 IOI identifies the service provider from which the request was sent. - remove the "orig-ioi" header field parameter from the P-Charging-Vector header field, if present; and - insert in the P-Charging-Vector header field the "orig-ioi" header field parameter with the IOI type 2 value stored when the initial request for a dialog or the request for a standalone transaction was received from an entity that was not an AS; - insert the "transit-ioi" header field parameter if previously stored; and - remove the Relayed-Charge header field, if present. When the transit function receives a 1xx or 2xx response to a request from a functional entity that is not an AS and if the response is forwarded to an AS the transit function shall: - store the values of the "orig-ioi", the "term-ioi" and the "transit-ioi" header field parameter received in the P-Charging-Vector header field if present; NOTE 3: Any received "term-ioi" header field parameter will be a type 2 IOI. The type 2 IOI identifies the service provider from which the response was sent. - remove the "orig-ioi", the "term-ioi", and the "transit-ioi" header field parameters from the P-Charging-Vector header field, if present; and - insert in the P-Charging-Vector header field an IOI type 3 value in a "term-ioi" header field parameter identifying the network sending the response, an IOI type 3 value in an "orig-ioi" header field parameter stored when the request was received from an AS, and based on operator option a Relayed-Charge header field with contents set to the value of the received "transit-ioi" header field parameter. When forwarding any response to a request from an AS to a functional entity that is not an AS the transit function shall remove the Relayed-Charge header field, if present. When forwarding the 1xx or 2xx response to a request from an AS to a functional entity that is not an AS the transit function shall: - remove the "orig-ioi" and the "term-ioi" header field parameter from the P-Charging-Vector header field, if present; and NOTE 4: Any received "term-ioi" and "orig-ioi" header field parameter will be a type 3 IOI. The type 3 IOI identifies the service provider from which the response was sent. - insert in the P-Charging-Vector header field an "orig-ioi" header field parameter with the IOI type 2 value, an "term-ioi" header field parameter with the IOI type 2 value received in the 1xx or 2xx response to the request from a functional entity that was not an AS, insert the "transit-ioi" header field parameter if previously stored. I.3.2.2 Original dialog identifier for transit function The original dialog identifier is an implementation specific token that the transit function encodes into the own transit function URI in a Route header field, prior to forwarding the request to an AS. This is possible because the transit function is the only entity that creates and consumes the value. The token may identify the original dialog of the request, so in case an AS acting as a B2BUA changes the dialog, the transit function is able to identify the original dialog when the request returns to the transit function. In a case of a standalone transaction, the token indicates that the request has been sent to the transit function from an AS in response to a previously sent request. The token can be encoded in different ways, such as e.g., a character string in the user-part of the transit function URI, a parameter in the transit function URI or port number in the transit function URI. The transit function shall ensure that the value chosen is unique, in order for the transit function to recognize the value when received in a subsequent message of one or more dialogs and make the proper association between related dialogs that pass through an AS. An original dialog identifier is sent to each AS invoked due to transit invocation criteria evaluation such that the transit function can associate requests as part of the same sequence that trigger transit invocation criteria evaluation in priority order (and not rely on SIP dialog information that may change due to B2BUA AS). NOTE: If the same original dialog identifier is included in more than one request from a particular AS (based on service logic in the AS), then the transit function will continue the transit invocation criteria evaluation sequence. If the AS wants transit invocation criteria evaluation to start from the beginning for a request, then AS does not include an original dialog identifier. I.4 Loopback routeing procedures I.4.1 Introduction In order to support traffics for the roaming architecture for voice over IMS with local breakout the additional routeing functionality will perform the procedures described in this subclause. An additional routeing functionality performing the procedures in this subclause is always located in the visited PLMN and is referred to as Transit and Roaming Function (TRF). The TRF performs local break out and routes the INVITE request via a specific entity e.g. IBCF or BGCF. Loopback routeing requires support in the visited network and the home network. If the visited network supports loopback routeing then the P-CSCF will, based on local policy, express this support by adding a g.3gpp.trf feature-capability indicator value to the URI of the desired TRF. The home network decides based on local operator policy if loopback routeing shall be applied. If loopback routeing is applied, the home network routes the INVITE request back to the TRF located in the visited network indicating that loopback routeing is used by including the g.3gpp.loopback feature-capability indicator in a Feature-Caps header field. In the loopback scenario OMR as specified in 3GPP TS 29.079 [11D] is used to determine the optimal media path between the visited network and the terminating network without passing through the home network. I.4.2 TRF procedure When the TRF receives an initial request for a dialog, the TRF shall: 1) retain the "icid-value" header field parameter in the P-Charging-Vector header field; 2) store the value of the "orig-ioi" header field parameter received in the P-Charging-Vector header field, if present, and remove the "orig-ioi" header field parameter from the P-Charging-Vector header field. Insert a type 2 "orig-ioi" header field parameter into the P-Charging-Vector header field. Set the type 2 "orig-ioi" header field parameter to a value that identifies the sending network in which the TRF resides. The TRF shall not include the "term-ioi" header field parameter. Store the value of a "transit-ioi" header field parameter received in the P-Charging-Vector header field, if present, and remove the "transit-ioi" header field parameter from the P-Charging-Vector header field before forwarding the request; 3) if required by local policy, perform number normalization and enum translation in the same way as performed by S-CSCF in subclause 5.4.3.2 step 10); 4) if the P-Access-Network header field is available, determine the entity for local break out (e.g. IBCF or BGCF) using: a) the location of the originating user; and b) the destination address, then include a Route header field set to the URI associated with the determined entity in the forwarded request; 5) create a Record-Route header field containing the TRF own SIP URI; 6) remove the "+g.3gpp.loopback" header field parameter from the Feature-Caps header field of the outgoing request; 6A) if the TRF supports indicating the traffic leg as specified in RFC 7549 [225] and required by local policy: a) if the Request-URI in the INVITE request contains a SIP URI, append an "iotl" SIP URI parameter set to "visitedA-homeB" to the Request-URI; and b) if the Request-URI in the INVITE request contains a tel URI: - convert the tel URI in the Request-URI to the form of a SIP URI with user=phone; and - append the "iotl" SIP URI parameter set to "visitedA-homeB" in the Request-URI; and 7) route the request based on SIP routeing procedures. When the TRF receives a 1xx or 2xx response to the INVITE request above, the TRF shall: - store the value of the "transit-ioi" header field parameter received in the P-Charging-Vector header field and remove the "transit-ioi" header field parameter from the P-Charging-Vector header field, if present; - remove the "orig-ioi" header field parameter and the "term-ioi" header field parameter from the P-Charging-Vector header field before forwarding the response; and NOTE: Any received "term-ioi" header field parameter will be a type 2 IOI identifying the sending network of the response. - insert in the P-Charging-Vector header field the "orig-ioi" header field parameter, if received in the request, and the type 1 "term-ioi" header field parameter in the response. The TRF shall set the type 1 "term-ioi" header field parameter to a value that identifies the network in which the TRF resides and the type 1 "orig-ioi" header field parameter is set to the previously received value of the type 1 "orig-ioi" header field parameter. When the TRF receives subsequent requests or responses to subsequent requests containing the "+g.3gpp.loopback" header field parameter from the Feature-Caps header field, the TRF shall remove the "+g.3gpp.loopback" header field parameter from the Feature-Caps header field of the outgoing request or the outgoing response. When the TRF receives responses to initial or subsequent requests from the terminating side, the TRF shall insert in the P-Charging-Vector header field, if present, the "loopback" header field parameter to the outgoing response. When the TRF receives subsequent requests from the terminating side, the TRF shall insert in the P-Charging-Vector header field, if present, the "loopback" header field parameter to the outgoing request. When the TRF receives a subsequent request, the TRF shall: 1) retain the "icid-value" header field parameter in the P-Charging-Vector header field; 2) store the value of the "orig-ioi" header field parameter received in the P-Charging-Vector header field, if present, and remove the "orig-ioi" header field parameter from the P-Charging-Vector header field; 3) if the subsequent request is: a) received from originating home network and forwarded to terminating home network, insert a type 2 "orig-ioi" header field parameter into the P-Charging-Vector header field, and set the type 2 "orig-ioi" header field parameter to a value that identifies the sending network in which the TRF resides. The TRF shall not include the "term-ioi" header field parameter; or b) received from terminating home network and forwarded to originating home network, insert a type 1 "orig-ioi" header field parameter into the P-Charging-Vector header field, and set the type 1 "orig-ioi" header field parameter to a value that identifies the sending network in which the TRF resides. The TRF shall not include the "term-ioi" header field parameter; and 4) store the value of a "transit-ioi" header field parameter received in the P-Charging-Vector header field, if present, and remove the "transit-ioi" header field parameter from the P-Charging-Vector header field before forwarding the request. When the TRF receives a response to a subsequent request, the TRF shall: 1) store the value of the "transit-ioi" header field parameter received in the P-Charging-Vector header field and remove the "transit-ioi" header field parameter from the P-Charging-Vector header field, if present; 2) remove the "orig-ioi" header field parameter and the "term-ioi" header field parameter from the P-Charging-Vector header field before forwarding the response; and 3) if the response to the subsequent request is: a) received from terminating home network and forwarded to originating home network, insert in the P-Charging-Vector header field the "orig-ioi" header field parameter, if received in the request, and the type 1 "term-ioi" header field parameter in the response. The TRF shall set the type 1 "term-ioi" header field parameter to a value that identifies the network in which the TRF resides and the type 1 "orig-ioi" header field parameter is set to the previously received value of the type 1 "orig-ioi" header field parameter; and b) received from originating home network and forwarded to terminating home network, insert in the P-Charging-Vector header field the "orig-ioi" header field parameter, if received in the request, and the type 2 "term-ioi" header field parameter in the response. The TRF shall set the type 2 "term-ioi" header field parameter to a value that identifies the network in which the TRF resides and the type 2 "orig-ioi" header field parameter is set to the previously received value of the type 2 "orig-ioi" header field parameter. I.5 Overload control I.5.1 Introduction The additional routeing functionality, or associated functional entity, performing additional routeing procedures described in I.3 may support the event-based overload control mechanism. I.5.2 Outgoing subscriptions to load-control event Based on operator policy, the additional routeing functionality may subscribe to the load-control event package with one ore more target SIP entities. The list of target SIP entities is provisioned. Subscription to the load-control event package is triggered by internal events (e.g. the physical device hosting the SIP entity is power-cycled) or through a management interface. The AS shall perform subscriptions to the load-control event package to a target entity in accordance with RFC 6665 [28] and with RFC 7200 [201]. When subscribing to the load-control event, additional routeing functionality shall: 1) Send a SUBSCRIBE request in accordance with RFC 6665 [28] and with RFC 7200 [201] to the target entity, with the following elements: - an Expires header field set to a network specific value; 2) If the target entity is located in a different network and local policy requires the application of IBCF capabilities, forward the request to an IBCF acting as an exit point. The additional routeing functionalit shall automatically refresh ongoing subscriptions to the load-control event package either 600 seconds before the expiration time if the initial subscription was for greater than 1200 seconds, or when half of the time has expired if the initial subscription was for 1200 seconds or less. The additional routeing functionality can terminate a subscription according to RFC 6665 [28]. Annex J (normative): Void Annex K (normative): Additional procedures in support of UE managed NAT traversal K.1 Scope This annex describes the UE, P-CSCF, and S-CSCF procedures in support of UE managed NAT traversal. For ICE, the IBCF procedures are also described. In this scenario, both the media flows and the SIP signalling both traverse a NA(P)T device located in the customer premises domain. The term "hosted NAT" is used to address this function. This annex does not consider the case where the NAT is behind the P-CSCF as different NAT traversal procedures are necessary for this architectural scenario. The procedures described in this subclause of this annex rely on the UE to manage the NAT traversal process. As part of the UE management process, the UE can learn whether it is behind a NAT or not, and choose whether the proceedures in this annex are applied or not. The protection of SIP messages is provided by applying either UDP encapsulation to IPSec packets in accordance with RFC 3948 [63A] and as defined in 3GPP TS 33.203 [19] or by utilizing TLS as defined in 3GPP TS 33.203 [19]. NOTE 1: This annex describes the mechanism for support of UE managed NAT traversal scenario defined in 3GPP TS 23.228 [7]. This does not preclude other mechanisms but they are out of the scope of this annex. NOTE 2: It is recognized that outbound can be useful for capabilities beyond NAT traversal (e.g. multiple registrations) however this annex does not consider such capabilities at this time. Such capabilites can require additional information elements in the REGISTER request so that the P-CSCF and S-CSCF can distinguish whether to apply procedures as of annex F or annex K. K.2 Application usage of SIP K.2.1 Procedures at the UE K.2.1.1 General This subclause describes the UE SIP procedures for supporting a UE managed hosted NAT traversal approach. The description enhances the procedures specified in subclause 5.1. K.2.1.2 Registration and authentication K.2.1.2.1 General The text in subclause 5.1.1.1 applies without changes. K.2.1.2.1A Parameters contained in the ISIM The text in subclause 5.1.1.1A applies without changes. K.2.1.2.1B Parameters provisioned to a UE without ISIM or USIM The text in subclause 5.1.1.1B applies without changes. K.2.1.2.2 Initial registration K.2.1.2.2.1 General The procedures described in subclause 5.1.1.2.1 apply with the additional procedures described in the present subclause. NOTE 1: In accordance with the definitions given in subclause 3.1 the IP address acquired initially by the UE in a hosted NAT scenario is the UE private IP address. On sending a REGISTER request, the UE shall populate the header fields as indicated in subitems a) through j) of subclause 5.1.1.2 with the exceptions of subitems c) and d) which are modified as follows. The UE shall populate: c) a Contact header field according to the following rules: the Contact header field shall be set to include SIP URI(s) containing the private IP address or FQDN of the UE in the hostport parameter. The UE shall also include an instance ID ("+sip.instance" header field parameter) and "reg-id" header field parameter as described in RFC 5626 [92]. The UE shall include all supported ICSI values (coded as specified in subclause 7.2A.8.2) in a g.3gpp.icsi-ref media feature tag as defined in subclause 7.9.2 and RFC 3840 [62] for the IMS communication services it intends to use, and IARI values (coded as specified in subclause 7.2A.9.2), for theIMS applications it intends to use in a g.3gpp.iari-ref media feature tag as defined in subclause 7.9.3 and RFC 3840 [62]; d) a Via header field set to include the private IP address or FQDN of the UE in the sent-by field. For TCP, the response is received on the TCP connection on which the request was sent. For UDP, the UE shall include the "rport" header field parameter as defined in RFC 3581 [56A]. NOTE 2: The UE will learn its public IP address from the "received" header field parameter in the topmost Via header field in the 401 (Unauthorized) response to the unprotected REGISTER request. NOTE 3: If the UE specifies a FQDN in the hostport parameter in the Contact header field and in the sent-by field in the Via header field of an unprotected REGISTER request, this FQDN will not be subject to any processing by the P-CSCF or other IMS entities. When a 401 (Unauthorized) response to a REGISTER request is received with integrity protection the UE shall behave as described in subclause K.2.1.2.5. When a 401 (Unauthorized) response to a REGISTER request is received and this response is received without integrity protection, the procedures described in subclause 5.1.1.2 apply with the following additions: The UE shall compare the IP address in the "received" header field parameter with the corresponding value in the sent-by parameter in the topmost Via header field to detect if the UE is behind a NAT. If the comparison indicates that the respective values are the same, the UE concludes that it is not behind a NAT. - if the UE is not behind a NAT the UE shall proceed with the procedures described in subclause 5.1; - if the UE is behind a NAT the UE shall verify using the Security-Server header field that either the mechanism-name "tls" or "ipsec-3gpp" and the mode "UDP-enc-tun" is selected. If the verification succeeds the UE shall behave as described in subclause K.2.1.2.5 and store the IP address contained in the "received" header field parameter as the UE's public IP address. If the verification does not succeed the UE shall abort the registration. On receiving the 200 (OK) response to the REGISTER request, the procedures described in subclause 5.1.1.2 apply with the following additions: The UE shall determine the P-CSCFs ability to support the keep-alive procedures as described in RFC 5626 [92] by checking whether the "outbound" option-tag is present in the Require header field: - if no "outbound" option-tag is present, the UE may use some other explicit indication in order to find out whether the P-CSCF supports the outbound edge proxy functionality. Such indication may be acomplished either through UE local configuration means or the UE can examine the 200 (OK) response to its REGISTER request for Path header fields, and if such are present check whether the bottommost Path header field contains the "ob" SIP URI parameter. If the UE determines that the P-CSCF supports the outbound edge proxy functionality, the UE can use the keep-alive techniques defined in subclause K.2.1.5 and RFC 5626 [92] towards the P-CSCF; or - if an "outbound" option-tag is present, the UE shall initiate keep-alive mechanisms as defined in subclause K.2.1.5 and RFC 5626 [92] towards the P-CSCF. NOTE 4: Presence of the "outbound" option-tag in the Require header field indicates that both the P-CSCF and S-CSCF fully support the outbound procedures. The number of subsequent outbound registrations for the same private user identity but with a different reg-id value is based on operator policy. K.2.1.2.2.2 Initial registration using IMS AKA The procedures described in subclause 5.1.1.2.2 apply with the additional procedures described in the present subclause. On sending a REGISTER request, the UE shall populate the header fields as indicated in subclause 5.1.1.2.2 with the exceptions of the subitems which are modified as follows: c) additionally for the Via header field, for UDP, if the REGISTER request is protected by a security association, include the public IP address or FQDN and the protected server port value in the sent-by field. For TCP, if the REGISTER request is protected by a security association, the UE shall include the public IP address or FQDN; d) the Security-Client header field set to specify the security mechanisms the UE supports, the IPsec layer algorithms the UE supports and the parameters needed for the security association setup. The UE shall support the setup of two pairs of security associations as defined in 3GPP TS 33.203 [19]. The syntax of the parameters needed for the security association setup is specified in annex H of 3GPP TS 33.203 [19]. The UE shall support the "ipsec-3gpp" security mechanism, as specified in RFC 3329 [48]. The UE shall support the IPsec layer algorithms for integrity and confidentiality protection as defined in 3GPP TS 33.203 [19], and shall announce support for them according to the procedures defined in RFC 3329 [48]. In addition to transport mode, the UE shall support UDP encapsulated tunnel mode as per RFC 3948 [73A] and shall announce support for both modes as described in 3GPP TS 33.203 [19]; K.2.1.2.2.3 Initial registration using SIP digest without TLS The procedures described in subclause 5.1.1.2.3 apply without modification. K.2.1.2.2.4 Initial registration using SIP digest with TLS The procedures described in subclause 5.1.1.2.4 apply without modification. K.2.1.2.2.5 Initial registration using NASS-IMS bundled authentication The procedures described in subclause 5.1.1.2.5 apply without modification. K.2.1.2.3 Initial subscription to the registration-state event package The procedures described in subclause 5.1.1.3 apply with the additional procedures described in subclause K.2.1.4.1. K.2.1.2.4 User-initiated reregistration K.2.1.2.4.1 General The procedures described in subclause 5.1.1.4 apply with the additional procedures described in the present subclause. On sending a REGISTER request that does not contain a challenge response, the UE shall populate the header fields as indicated in subclause 5.1.1.4.1 with the exception of subitems c) and d) which are modified as follows. The UE shall populate: c) a Contact header field set to include SIP URI(s) that contain(s) in the hostport parameter the private IP address of the UE or FQDN, its instance ID ("+sip.instance" header field parameter) along with the same "reg-id" header field parameter used for the initial, successful, registration for the given P-CSCF public identity combination as described in RFC 5626 [92]. The UE shall include all supported ICSI values (coded as specified in subclause 7.2A.8.2) in a g.3gpp.icsi-ref media feature tag as defined in subclause 7.9.2 and RFC 3840 [62] for the IMS communication services it intends to use, and IARI values (coded as specified in subclause 7.2A.9.2), for the IMS applications it intends to use in a g.3gpp.iari-ref media feature tag as defined in subclause 7.9.3 and RFC 3840 [62]; and d) a Via header field according to the following rules: - For UDP, the UE shall include the public IP address or FQDN in the sent-by field. The UE shall also include the "rport" header field parameter as defined in RFC 3581 [56A]. The UE shall only use an FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT; or - For TCP, the UE shall include the public IP address or FQDN of the UE in the sent-by field. The UE shall only use an FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT; When the timer F expires at the UE, the UE shall: 1) stop processing of all ongoing dialogs and transactions associated with that, if any (i.e. no further SIP signalling will be sent by the UE on behalf of these transactions or dialogs); and 2) after releasing all IP-CAN bearers used for the transport of media according to the procedures in subclause 9.2.2, the UE shall follow the procedures in RFC 5626 [92] to form a new flow to replace the failed one. When registering to create a new flow to replace the failed one, procedures in subclause 5.1.1.2 apply. NOTE: These actions can also be triggered as a result of the failure of a STUN keep-alive. It is an implementation option whether these actions are also triggered by other means than expiration of timer F, e.g., based on ICMP messages. If failed registration attempts occur in the process of creating a new flow, the flow recovery procedures defined in RFC 5626 [92] shall apply. K.2.1.2.4.2 IMS AKA as a security mechanism The procedures described in subclause 5.1.1.4.2 apply without modification. K.2.1.2.4.3 SIP Digest without TLS as a security mechanism The procedures described in subclause 5.1.1.4.3 apply without modification. K.2.1.2.4.4 SIP Digest with TLS as a security mechanism The procedures described in subclause 5.1.1.4.4 apply without modification. K.2.1.2.4.5 NASS-IMS bundled authentication as a security mechanism The procedures described in subclause 5.1.1.4.5 apply without modification. K.2.1.2.5 Authentication K.2.1.2.5.1 IMS AKA – general The procedures of subclause 5.1.1.5.1 apply with the additional procedures described in the present subclause. On receiving a 401 (Unauthorized) response to the REGISTER request and the response is deemed to be valid and signalling security is to be used, the UE shall behave as of subclause 5.1.1.5.1 with the exception of subitem 3) which is modified as follows. The UE shall: 3) send another REGISTER request using the temporary set of security associations to protect the message. The header fields are populated as defined for the initial registration (see subclause K.2.1.2.2), with the addition that the UE shall include an Authorization header field containing the private user identity and if the "algorithm" header field parameter is "AKAv1-MD5" or "AKAv2-SHA-256", the authentication challenge response shall be calculated by the UE using RES and other parameters, as described in RFC 3310 [49] when AKAv1 is used or as described in RFC 4169 [227] when AKAv2 is used. If the "algorithm" header field parameter is "MD5" or "SHA-256", the UE shall calculate SIP digest-response parameters as indicated in RFC 7616 [286] and RFC 8760 [287] and shall build an Authorization header field based on these parameters. The UE shall also insert the Security-Client header field that is identical to the Security-Client header field that was included in the previous REGISTER request (i.e. the REGISTER request that was challenged with the received 401 (Unauthorized) response). The UE shall also insert the Security-Verify header field into the request, by mirroring in it the content of the Security-Server header field received in the 401 (Unauthorized) response. The UE shall set the Call-ID of the integrity-protected REGISTER request which carries the authentication challenge response to the same value as the Call-ID of the 401 (Unauthorized) response which carried the challenge. NOTE: The "AKAv1-MD5" and "MD5" algorithms are only supported for backward compatibility. For IPsec, if the 200 (OK) response is not received before the temporary SIP level lifetime of the temporary set of security associations expires or a 403 (Forbidden) response is received, the UE shall consider the registration to have failed. The UE shall delete the temporary set of security associations it was trying to establish, and use the old set of security associations. The UE should send an unprotected REGISTER request according to the procedure specified in subclause K.2.1.2.2 if the UE considers the old set of security associations to be no longer active at the P-CSCF. K.2.1.2.5.2 Void K.2.1.2.5.3 IMS AKA abnormal cases The text in subclause 5.1.1.5.3 applies without changes. K.2.1.2.5.4 SIP digest without TLS – general The text in subclause 5.1.1.5.4 applies without changes. K.2.1.2.5.5 SIP digest without TLS – abnormal procedures The procedures of subclause 5.1.1.5.5 apply with the additional procedures described in the present subclause. On receiving a 403 (Forbidden) response, the UE shall consider the registration to have failed. If performing SIP digest with TLS, the UE should send an initial REGISTER according to the procedure specified in subclause K.2.1.2.2 if the UE considers the TLS session to be no longer active at the P-CSCF. K.2.1.2.5.6 SIP digest with TLS – general The text in subclause 5.1.1.5.6 applies without changes. K.2.1.2.5.7 SIP digest with TLS – abnormal procedures The text in subclause 5.1.1.5.7 applies without changes. K.2.1.2.5.8 NASS-IMS bundled authentication – general The text in subclause 5.1.1.5.8 applies without changes. K.2.1.2.5.9 NASS-IMS bundled authentication – abnormal procedures The text in subclause 5.1.1.5.9 applies without changes. K.2.1.2.5.10 Abnormal procedures for all security mechanisms The text in subclause 5.1.1.5.10 applies without changes. K.2.1.2.5A Network-initiated re-authentication The procedures of subclause 5.1.1.5A apply with the additional procedures described in the present subclause. On starting the re-authentication procedure sending a REGISTER request that does not contain a challenge response, the UE shall behave as of subclause 5.1.1.5A with the exception of subitem 2) which is modified as follows. The UE shall: 2) start the re-authentication procedures at the appropriate time (as a result of the S-CSCF procedure described in subclause 5.4.1.6) by initiating a reregistration as described in subclause K.2.1.2.4, if required. K.2.1.2.5B Change of IPv6 address due to privacy The text in subclause 5.1.1.5B applies without changes. K.2.1.2.6 User-initiated deregistration K.2.1.2.6.1 General The procedures of subclause 5.1.1.6.1 apply with the additional procedures described in the present subclause. On sending a REGISTER request, the UE shall populate the header fields as indicated in subclause 5.1.1.6.1 with the exception of subitems c) and d) which are modified as follows. The UE shall populate: c) a Contact header field set to either the value of "*" or SIP URI(s) that contain(s) in the hostport parameter the IP address of the UE or FQDN, its instance ID ("+sip.instance" header field parameter) along with the same "reg-id" header field parameter used for the initial, successful, registration for the given P-CSCF public identity combination as described in RFC 5626 [92];. The UE shall only use a FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT; d) a Via header field according to the following rules: - For UDP, the UE shall include the public IP address or FQDN. The UE shall also include the "rport" header field parameter as defined in RFC 3581 [56A]. The UE shall only use an FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT; or - For TCP, the UE shall include the public IP address or FQDN of the UE in the sent-by field. The UE shall only use an FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT; NOTE: In case of hosted NAT traversal only the UE public IP addresses are bound to security associations or TLS session. K.2.1.2.6.2 IMS AKA as a security mechanism The text in subclause 5.1.1.6.2 applies without changes. K.2.1.2.6.3 SIP digest as a security mechanism The text in subclause 5.1.1.6.3 applies without changes. K.2.1.2.6.4 SIP digest with TLS as a security mechanism The text in subclause 5.1.1.6.4 applies without changes. K.2.1.2.6.5 Initial registration using NASS-IMS bundled authentication The text in subclause 5.1.1.6.5 applies without changes. K.2.1.2.7 Network-initiated deregistration The procedures of subclause 5.1.1.7 apply with the additional procedures described in the present subclause. Upon receipt of a NOTIFY request on the dialog which was generated during subscription to the reg event package as described in subclause 5.1.1.3, including one or more <registration> element(s) which were registered by this UE with: - the state attribute set to "terminated" and the event attribute set to "rejected" or "deactivated"; or - the state attribute set to "active" and the state attribute within the <contact> element belonging to this UE set to "terminated", and associated event attribute element to "rejected" or "deactivated"; The UE shall remove all registration details relating to these public user identities. In case of a "deactivated" event attribute, the UE shall start the initial registration procedure as described in subclause K.2.1.2.2. In case of a "rejected" event attribute, the UE shall release all dialogs related to those public user identities. K.2.1.3 Subscription and notification The text in subclause 5.1.2 applies without changes. K.2.1.4 Generic procedures applicable to all methods excluding the REGISTER method K.2.1.4.1 UE-originating case The procedures described in subclause 5.1.2A.1 apply with the additional procedures described in the present subclause. When the UE sends any request, the requirements in subclause 5.1.2A.1 are extended by the following requirements. The UE shall include: - a Via header field according to the following rules: - For UDP, the UE shall include the public IP address or FQDN and the protected server port value in the sent-by field. The UE shall also include the "rport" header field parameter as defined in RFC 3581 [56A]. The UE shall only use an FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT; or - For TCP, the UE shall include the public IP address or FQDN of the UE in the sent-by field. The UE shall only use an FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT; and - if the request contains a Contact header field, include a Contact header field according to the following rules: - if this is a request for a new or existing dialog, and the UE did insert a GRUU in the Contact header field, then the UE shall also include its instance ID ("+sip.instance" header field parameter), and an "ob" SIP URI parameter as described in RFC 5626 [92]; or - if this is a request for a new or existing dialog, and the UE did not insert a GRUU in the Contact header field, then the UE shall include the public IP address of the UE or FQDN and the protected server port value bound to the security association or TLS session in the hostport parameter along with its instance ID ("+sip.instance" header field parameter), and an "ob" SIP URI parameter as described in RFC 5626 [92]. The UE shall only use a FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT. NOTE: The means to ensure that the FQDN resolves to the public IP address of the NAT are outside of the scope of this specification. One option for resolving this is local configuration. Where a security association or TLS session exists, the UE shall discard any SIP response that is not protected by the security association or TLS session and is received from the P-CSCF outside of the registration and authentication procedures. The requirements on the UE within the registration and authentication procedures are defined in subclause K.2.1.2. When a SIP transaction times out, i.e. timer B, timer F or timer H expires at the UE, the UE may behave as if timer F expired, as described in subclause K.2.1.2.4. K.2.1.4.2 UE-terminating case The procedures described in subclause 5.1.2A.2 apply with the additional procedures described in the present subclause. When the UE sends any response, the requirements in subclause 5.1.2A.2 are extended by the following requirement. If the UE did not include a GRUU in the Contact header field, then the UE shall: - include the public IP address of the UE or FQDN and the protected server port value bound to the security association or TLS session in the hostport parameter in any Contact header field that is otherwise included. The UE shall only use a FQDN, if it is ensured that the FQDN resolves to the public IP address of the NAT. The UE shall discard any SIP request that is not integrity protected and is received from the P-CSCF outside of the registration and authentication procedures. The requirements on the UE within the registration and authentication procedures are defined in subclause K.2.1.2. K.2.1.5 Maintaining flows and detecting flow failures STUN Binding Requests are used by the UE as a keep-alive mechanism to maintain NAT bindings for signalling flows over connectionless transport (for dialogs outside a registration as well as within a registration) as well as to determine whether a flow (as described in RFC 5626 [92]) is still valid (e.g. a NAT reboot could cause the transport parameters to change). As such, the UE acts as a STUN client and shall follow the requirements defined by RFC 8489 [291]. Further, when using UDP encapsulated IPsec, the keep-alive capabilities defined within should not be used. CRLF as defined in RFC 5626 [92] is used by the UE as a keep-alive mechanism to maintain NAT bindings for signalling flows over connection oriented transports (for dialogs outside a registration as well as within a registration) as well as to determine whether a flow (as described in RFC 5626 [92]) is still valid (e.g. a NAT reboot could cause the transport parameters to change). As such, the UE shall follow the requirements defined by RFC 5626 [92]. If the UE determines that the flow to a given P-CSCF is no longer valid (the UE does not receive a STUN reply (or CRLF) or the reply indicates a new public IP Address) the UE shall consider the flow and any associated security associations invalid and perform the initial registration procedures defined in subclause K.2.1.2.2. When a NAT is not present, it may not be desirable to send keep-alive requests (i.e. given battery considerations for wireless UEs). As such, if a UE can reliably determine that a NAT is not present (i.e. by comparing the "received" header field parameter in the Via header field in the response to the initial un-protected REGISTER request with the locally assigned IP address) then the UE may not perform the keep-alive procedures. K.2.1.6 Emergency services K.2.1.6.1 General In addition to the procedures in subclause 5.1.6.1, the following additional procedures apply. When receiving and sending requests unprotected, the UE shall transmit and receive all SIP messages using the same IP port. K.2.1.6.2 Initial emergency registration When a UE performs an initial emergency registration the UE shall perform the actions as specified in subclause K.2.1.2.2. The remaining procedures described in subclause 5.1.6.2 apply without modification. K.2.1.6.2A New initial emergency registration The text in subclause 5.1.6.2A applies without changes. K.2.1.6.3 Initial subscription to the registration-state event package The text in subclause 5.1.6.3 applies without changes. K.2.1.6.4 User-initiated emergency reregistration The UE shall perform user-initiated emergency reregistration as specified in subclause K.2.1.2.4. The remaining procedures described in subclause 5.1.6.4 apply without modification. K.2.1.6.5 Authentication The UE shall perform the authentication procedures as specified in subclause K.2.1.2.5. The remaining procedures described in subclause 5.1.6.5 apply without modification. K.2.1.6.6 User-initiated emergency deregistration The text in subclause 5.1.6.6 applies without changes. K.2.1.6.7 Network-initiated emergency deregistration The text in subclause 5.1.6.7 applies without changes. K.2.1.6.8 Emergency session setup K.2.1.6.8.1 General The text in subclause 5.1.6.8.1 applies without changes. K.2.1.6.8.2 Emergency session set-up in case of no registration The text in subclause 5.1.6.8.2 applies without changes. K.2.1.6.8.3 Emergency session set-up with an emergency registration After a successful initial emergency registration, the UE shall apply the procedures as specified in subclause K.2.1.4, subclause 5.1.3, and subclause 5.1.4. The remaining procedures described in subclause 5.1.6.8.3 apply without modification. K.2.1.6.8.4 Emergency session set-up within a non-emergency registration The UE shall apply the procedures as specified in subclause K.2.1.4, subclause 5.1.3, and subclause 5.1.4. The remaining procedures described in subclause 5.1.6.8.4 apply without modification. K.2.1.6.9 Emergency session release The text in subclause 5.1.6.9 applies without changes. K.2.2 Procedures at the P-CSCF K.2.2.1 Introduction This subclause describes the SIP procedures for supporting hosted NAT scenarios. The description enhances the procedures specified in subclause 5.2. K.2.2.2 Registration K.2.2.2.1 General The procedures described in subclause 5.2.2.1 apply without changes. K.2.2.2.2 IMS AKA as a security mechanism The procedures described in subclause 5.2.2.2 apply with the additional procedures described in the present subclause. When the P-CSCF receives a REGISTER request from the UE, the P-CSCF shall behave as in subclause 5.2.2.2 with the exception of subitems 2) and 3) which are modified as follows. 2) in case the REGISTER request was received without protection, then: a) check the existence of the Security-Client header field. If the Security-Client header field is not present and signalling security is used, then the P-CSCF shall return a suitable 4xx response. If the Security-Client header field is present the P-CSCF shall: - in case the UE indicated support for "UDP-enc-tun" then remove and store it; or - in case the UE does not indicate support for "UDP-enc-tun" then: - if the host portion of the sent-by field in the topmost Via header field contains an IP address that differs from the source address of the IP packet, silently drop the REGISTER request; - otherwise continue with procedures as of subclause 5.2.2.2; NOTE 2: If the UE does not indicate support for "UDP-enc-tun" and the P-CSCF detects that the UE is located behind a NAT device, then the P-CSCF can just drop the REGISTER request to avoid unnecessary signalling traffic. 3) in case the REGISTER request was received integrity protected, then the P-CSCF shall: a) check the security association which protected the request. If IPsec is used and the security association is a temporary one the P-CSCF shall: - in case the hostport parameter in the Contact address is in the form of a FQDN, ensure that the given FQDN will resolve (e.g., by reverse DNS lookup) to the IP address bound to the security association; - in case the P-CSCF has detected earlier that the UE is located behind a NAT and IPsec is being used, retrieve port_Uenc from the encapsulating UDP header of the packet received and complete configuration of the temporary set of security associations by configuring port_Uenc in each of the temporary security associations; - check whether the request contains a Security-Verify header field in addition to a Security-Client header field. If there are no such header fields, then the P-CSCF shall return a suitable 4xx response. If there are such header fields, then the P-CSCF shall compare the content of the Security-Verify header field with the content of the Security-Server header field sent earlier and the content of the Security-Client header field with the content of the Security-Client header field received in the challenged REGISTER request. If those do not match, then there is a potential man-in-the-middle attack. The request should be rejected by sending a suitable 4xx response. If the contents match, the P-CSCF shall remove the Security-Verify and the Security-Client header field; When the P-CSCF receives a 401 (Unauthorized) response to an unprotected REGISTER request and the P-CSCF previously determined that the UE is behind a NAT and the UE indicated support for "UDP-enc-tun" IPsec mode, the P-CSCF shall: 1) delete any temporary set of security associations established towards the UE; 2) for IPsec, remove the "ck" and "ik" WWW-Authenticate header field parameters contained in the 401 (Unauthorized) response and bind the values to the proper private user identity and to the temporary set of security associations which will be setup as a result of this challenge. The P-CSCF shall forward the 401 (Unauthorized) response to the UE if and only if the "ck" and "ik" header field parameters have been removed; 3) insert a Security-Server header field in the response, containing the P-CSCF security list and the parameters needed.The P-CSCF shall support the setup of two pairs of security associations, as defined in 3GPP TS 33.203 [19]. The syntax of the parameters needed of the IPsec security association setup is specified in annex H of 3GPP TS 33.203 [19]. The P-CSCF shall support the "ipsec-3gpp" security mechanism, as specified in RFC 3329 [48]. The P-CSCF shall support the IPSec layer algorithms for integrity protection and for encryption as defined in 3GPP TS 33.203 [19]. The P-CSCF shall indicate "UDP-enc-tun" as the only IPsec mode. 4) set up the temporary set of security associations with a temporary SIP level lifetime between the UE and the P-CSCF for the user identified with the private user identity. The P-CSCF shall select UDP encapsulated tunnel mode and shall leave the value for port-Uenc unspecified in each of the temporary security associations. For further details see 3GPP TS 33.203 [19] and RFC 3329 [48]. The P-CSCF shall set the temporary SIP level lifetime for the temporary set of security associations to the value of reg-await-auth timer; and 5) send the 401 (Unauthorized) response unprotected to the UE using the mechanisms described in RFC 3261 [26] and RFC 3581 [56A], i.e. the P-CSCF shall send the response to the IP address indicated in the "received" header field parameter and, in case UDP is used, to the port indicated in the "rport" header field parameter (if present) of the Via header field associated with the UE. In case TCP is used as transport protocol, the P-CSCF shall use the port on which the REGISTER request was received as client port for sending the response back to the UE. When the P-CSCF receives a 401 (Unauthorized) response to a protected REGISTER request and the P-CSCF previously determined that the UE is behind a NAT and that REGISTER request was protected by an old set of security associations that use UDP encapsulated tunnel mode, the P-CSCF shall: 1) delete any temporary set of security associations established towards the UE; 2) remove the "ck" and "ik" WWW-Authenticate header field parameters contained in the 401 (Unauthorized) response and bind the values to the proper private user identity and to the temporary set of security associations which will be setup as a result of this challenge. The P-CSCF shall forward the 401 (Unauthorized) response to the UE if and only if the "ck" and "ik" header field parameters have been removed; 3) insert a Security-Server header field in the response, containing the P-CSCF security list and the parameters needed for the security association setup, as specified in Annex H of 3GPP TS 33.203 [19]. The P-CSCF shall support the "ipsec-3gpp" security mechanism, as specified in RFC 3329 [48]. The P-CSCF shall support the IPsec layer algorithms for integrity protection and encryption as defined in 3GPP TS 33.203 [19]. The P-CSCF shall indicate "UDP-enc-tun" as the IPsec mode; 4) set up the temporary set of security associations with a temporary SIP level lifetime between the UE and the P-CSCF for the user identified with the private user identity. The P-CSCF shall select UDP encapsulated tunnel mode and shall specify the same port_Uenc that was used in the old set of security associations. The P-CSCF shall set the temporary SIP level lifetime for the temporary set of security associations to the value of reg-await-auth timer; and 5) send the 401 (Unauthorized) response to the UE using the old set of security associations and using the rules for sending responses as described in RFC 3261 [26] and RFC 3581 [56A], i.e. the P-CSCF shall send the response to the IP address indicated in the "received" header field parameter and if UDP is used, to the port indicated in the "rport" header field parameter (if present) of the Via header field associated with the UE. Otherwise, when the P-CSCF receives a 401 (Unauthorized) response to an unprotected REGISTER request and: - this response does not contain a "received" header field parameter in the Via header field associated with the UE; - this response does not contain "rport" header field parameter in the Via header field associated with the UE and the request associated with the response was received using UDP; or - when the P-CSCF receives a 401 (Unauthorized) response to a protected REGISTER request and that REGISTER request was protected by an old set of security associations that do not use UDP encapsulated tunnel mode; the P-CSCF shall proceed as described in subclause 5.2.2.2 of the main body of this specification. K.2.2.2.3 SIP digest without TLS as a security mechanism The text in subclause 5.2.2.3 applies without changes. K.2.2.2.4 SIP digest with TLS as a security mechanism The procedures described in subclause 5.2.2.4 apply without changes. K.2.2.2.5 NASS-IMS bundled authentication as a security mechanism The text in subclause 5.2.2.5 applies without changes. K.2.2.3 General treatment for all dialogs and standalone transactions excluding the REGISTER method K.2.2.3.1 Requests initiated by the UE K.2.2.3.1.1 General for all requests The procedures described in subclause 5.2.6.3.1 apply with the additional procedures described in the present subclause. When the P-CSCF receives from the UE an initial request for a dialog or a request for a standalone transaction, the requirements are extended by the following requirements. Before forwarding the request, based on the topmost Route header field, in accordance with the procedures of RFC 3261 [26], the P-CSCF shall ensure that all signalling during the lifetime of the dialogue is sent over the same IMS flow set as the dialogue initiating request. NOTE: The suggested way to ensure all signalling is sent over the same IMS flow set is to form an IMS flow token in the same way that a P-CSCF would form this for the Path header field and insert this IMS flow token in the user portion of the URI used in the record route header field value. K.2.2.3.1.2 General for all responses The procedures in subclause 5.2.6.3.2 apply without changes. K.2.2.3.1.2A Abnormal cases The text in subclause 5.2.6.3.2A applies without changes. K.2.2.3.1.3 Initial request for a dialog The text in subclause 5.2.6.3.3 applies without changes. K.2.2.3.1.4 Responses to an initial request for a dialog The text in subclause 5.2.6.3.4 applies without changes. K.2.2.3.1.5 Target refresh request for a dialog The text in subclause 5.2.6.3.5 applies without changes. K.2.2.3.1.6 Responses to a target refresh request for a dialog The text in subclause 5.2.6.3.6 applies without changes. K.2.2.3.1.7 Request for a standalone transaction The text in subclause 5.2.6.3.7 applies without changes. K.2.2.3.1.8 Responses to a request for a standalone transaction The text in subclause 5.2.6.3.8 applies without changes. K.2.2.3.1.9 Subsequent request other than a target refresh request The text in subclause 5.2.6.3.9 applies without changes. K.2.2.3.1.10 Responses to a subsequent request other than a target refresh request Void K.2.2.3.1.11 Request for an unkown method that does not relate to an existing dialog The text in subclause 5.2.6.3.11 applies without changes. K.2.2.3.1.12 Responses to a request for an unkown method that does not relate to an existing dialog Void K.2.2.3.2 Requests terminated by the UE K.2.2.3.2.1 General for all requests Void K.2.2.3.2.2 General for all responses Void K.2.2.3.2.3 Initial request for a dialog The procedures described in subclause 5.2.6.4.3 apply with the additional procedures described in the present subclause. When the P-CSCF receives, destined for the UE, a request, the requirements are extended by the following requirements. The P-CSCF shall: - forward the request to the terminating UE over the appropriate flow within the denoted IMS flow set. K.2.2.3.2.4 Responses to an initial request for a dialog The text in subclause 5.2.6.4.4 applies without changes. K.2.2.3.2.5 Target refresh request for a dialog The procedures described in subclause 5.2.6.4.5 apply with the additional procedures described in the present subclause. When the P-CSCF receives, destined for the UE, a request, the requirements are extended by the following requirements. The P-CSCF shall: - forward the request to the terminating UE over the appropriate flow within the denoted IMS flow set. K.2.2.3.2.6 Responses to a target refresh request for a dialog The text in subclause 5.2.6.4.6 applies without changes. K.2.2.3.2.7 Request for a standalone transaction The procedures described in subclause 5.2.6.4.7 apply with the additional procedures described in the present subclause. When the P-CSCF receives, destined for the UE, a request, the requirements are extended by the following requirements. The P-CSCF shall: - forward the request to the terminating UE over the appropriate flow within the denoted IMS flow set. K.2.2.3.2.8 Responses to a request for a standalone transaction The text in subclause 5.2.6.4.8 applies without changes. K.2.2.3.2.9 Subsequent request other than a target refresh request The procedures described in subclause 5.2.6.4.9 apply with the additional procedures described in the present subclause. When the P-CSCF receives, destined for the UE, a request, the requirements are extended by the following requirements. The P-CSCF shall: - forward the request to the terminating UE over the appropriate flow within the denoted IMS flow set. K.2.2.3.2.10 Responses to a subsequent request other than a target refresh request The text in subclause 5.2.6.4.10 applies without changes. K.2.2.3.2.11 Request for an unknown method that does not relate to an existing dialog Void K.2.2.3.2.12 Responses to a request for an unknown method that does not relate to an existing dialog Void K.2.2.4 Void K.2.2.5 Emergency services K.2.2.5.1 General The procedures described in subclause 5.2.10.1 apply without changes. K.2.2.5.2 General treatment for all dialogs and standalone transactions excluding the REGISTER method – from an unregistered user The procedures described in subclause 5.2.10.2 apply with the additional procedures described in the present subclause. When the P-CSCF receives from the UE an initial request for a dialog or a request for a standalone transaction, the requirements are extended by the following requirements. Before forwarding the request, based on the topmost Route header field, in accordance with the procedures of RFC 3261 [26], the P-CSCF shall ensure that all signalling during the lifetime of the dialogue is sent over the same IMS flow set as the dialogue initiating request. NOTE: The suggested way to ensure all signalling is sent over the same IMS flow set is to form an IMS flow token in the same way that a P-CSCF would form this for the Path header field and insert this IMS flow token in the user portion of the URI used in the Record-Route header field value. K.2.2.5.3 General treatment for all dialogs and standalone transactions excluding the REGISTER method after emergency registration The procedures described in subclause 5.2.10.3 apply with the additional procedures described in the present subclause. When the P-CSCF receives from the UE an initial request for a dialog, or a standalone transaction, or an unknown method, the following requirements: 1) include in the Request-URI an emergency service URN, i.e. a service URN with a top-level service type of "sos" as specified in RFC 5031 [69], if necessary, and execute the procedure described in step 4, 5, 6, and 7, in subclause 5.2.6.3.3, subclause 5.2.6.3.7, subclause 5.2.6.3.11, subclause 5.2.7.2 and subclause K.2.2.3.1, as appropriate. An additional sub-service type can be added if information on the type of emergency service is known. The entry in the Request-URI that the P-CSCF includes may either be: - as received from the UE in the Request-URI in accordance with RFC 5031 [69]; or - as deduced from the Request-URI received from the UE. K.2.2.5.4 General treatment for all dialogs and standalone transactions excluding the REGISTER method – non-emergency registration The procedures described in subclause 5.2.10.4 apply with the additional procedures described in the present subclause. When the P-CSCF receives from the UE an initial request for a dialog, or a standalone transaction, or an unknown method, the following requirements are extended: 1) include in the Request-URI an emergency service URN, i.e. a service URN with a top-level service type of "sos" as specified in RFC 5031 [69], if necessary, and execute the procedure described in step 3, 4, 5, 6, and 7, in subclause 5.2.6.3.3, subclause 5.2.6.3.7, subclause 5.2.6.3.11 subclause 5.2.7.2 and subclause K.2.2.3.1, as appropriate. An additional sub-service type can be added if information on the type of emergency service is known. The entry in the Request-URI that the P-CSCF includes may either be: - as received from the UE in the Request-URI in accordance with RFC 5031 [69]; or - as deduced from the Request-URI received from the UE; and K.2.2.5.5 Abnormal cases The text in subclause 5.2.10.5 applies without changes. K.2.3 Void K.2.4 Void K.3 Application usage of SDP K.3.1 UE usage of SDP The procedures as of subclause 6.1 apply. K.3.2 P-CSCF usage of SDP The procedures as of subclause 6.2 apply. K.4 Void K.5 Application usage of ICE K.5.1 Introduction The following subclauses describe the usage of the Interactive Connectivity Establishment (ICE) procedures as documented in RFC 8445 [289] and RFC 8839 [290]. K.5.2 UE usage of ICE K.5.2.1 General NAT bindings also need to be kept alive for media. RFC 8445 [289] provides requirements for STUN based keepalive mechanisms. UEs that do not implement the ICE procedures as defined in RFC 8445 [289] should implement the keepalive procedures defined in RFC 8445 [289]. In the case where keepalives are required and the other end does not support ICE (such that STUN cannot be used for a keepalive) or the UE can not discover STUN or TURN servers to gather candidates, the UE shall send an empty (no payload) RTP packet with a payload type of 20 as a keepalive as long as the other end has not negotiated the use of this value. If this value has already been negotiated, then some other unused static payload type from table 5 of RFC 3551 [55A] shall be used. When sending an empty RTP packet, the UE shall continue using the sequence number (SSRC) and timestamp as the negotiated RTP steam. K.5.2.2 Call initiation – UE-origination case The UE should support the agent requirements for ICE as defined by RFC 8445 [289] when sending the initial INVITE request. RFC 8445 [289] and RFC 8839 [290] provide procedures for: 1) Gathering candidate addresses for RTP and RTCP prior to sending the INVITE; 2) Encoding the candidate addresses in the SDP that is included with the INVITE; 3) Acting as a STUN server to receive binding requests from the remote client when it does connectivity checks; 4) Performing connectivity checks on received candidate addresses for RTP and RTCP; 5) Determining and possibly selecting a better active address based on the requirements in RFC 8445 [289] and RFC 8839 [290]; 6) Subsequent offer/answer exchanges; and 7) Sending media. When supporting the ICE procedures, the UE shall also support the STUN agent requirements as described in RFC 8489 [291] in order to gather STUN addresses, the TURN client requirements as described in RFC 8656 [292] in order to gather TURN Server addresses and the STUN Server requirements defined in RFC 8445 [289] as well as the requirements for STUN Servers defined in RFC 8489 [291] for responding to connectivity checks. RFC 8445 [289] provides an algorithm for determining the priority of a particular candidate. The following additional requirements are provided to the UE: 1) The type preference assigned for each type of candidate from least to highest should be: Relayed Transport Address, STUN address, local address; and 2) If the UE has a dual IPv4/IPv6 stack, IPv6 addresses may be assigned a higher local preference than IPv4 addresses based on the operator's policy. RFC 8445 [289] provides guidance on choosing the in-use candidate and recommends that a UE choose relayed candidates as the in-use address. The following additional requirements are provided to the UE: 1) If a TURN server is available, the Relayed Transport Address should be used as the initial active transport address (i.e. as advertised in the m/c lines of the SDP); and 2) If a TURN server is not available, an address obtained via STUN should be used as the initial active transport address. Regardless of whether the UE supports the above procedures, the UE shall, upon receipt of an SDP answer with candidate addresses, perform connectivity checks on the candidate addresses as described in RFC 8445 [289] and RFC 8839 [290]. In order to perform connectivity checks, the UE shall act as a STUN client as defined in RFC 8489 [291]. Further, the UE shall also follow the procedures in RFC 8445 [289] and RFC 8839 [290] when sending media. K.5.2.3 Call termination – UE-termination case The UE should support agent requirements for ICE as defined by RFC 8445 [289] when receiving an initial INVITE request. RFC 8445 [289] and RFC 8839 [290] provide procedures for: 1) Gathering candidate addresses for RTP and RTCP prior to sending the answer as described in RFC 8445 [289]; 2) Encoding the candidate addresses in the SDP answer as described in RFC 8839 [290]; 3) Acting as a STUN server to receive binding requests from the remote client when it does connectivity checks; 4) Performing connectivity checks on received candidate addresses for RTP and RTCP; 5) Determining and possibly selecting a better active address based on the requirements in RFC 8445 [289] and RFC 8839 [290]; 6) Subsequent offer/answer exchanges; and 7) Sending media. When supporting the ICE procedures, the UE shall also support the STUN agent requirements as described in RFC 8489 [291] in order to gather STUN addresses, the TURN client requirements as described in RFC 8656 [292] in order to gather TURN Server addresses and the STUN Server requirements defined in RFC 8445 [289] as well as the requirements for STUN Servers defined in RFC 8489 [291] for responding to connectivity checks. RFC 8445 [289] provides an algorithm for determining the priority of a given candidate. The additional requirements for the UE: 1) The priority of candidate addresses from least to highest should be: Relayed Transport Address, STUN address, local address; and 2) If the UE has a dual IPv4/IPv6 stack, IPv6 addresses MAY be placed at a higher priority than IPV4 addresses based on the operator's policy. RFC 8445 [289] provides guidance on choosing the in-use candidate and recommends that a UE choose relayed candidates as the in-use address. The following additional requirements are provided to the UE: 1) If a TURN server is available, the Relayed Transport Address should be used as the initial active transport address (i.e. as advertised in the m/c lines of the SDP); and 2) If a TURN server is not available, an address obtained via STUN should be used as the initial active transport address. Regardless of whether the UE supports the above procedures, the UE shall, upon receipt of an SDP offer with candidate addresses, perform connectivity checks on the candidate addresses as described in RFC 8445 [289] and RFC 8839 [290]. In order to perform connectivity checks, the UE shall act as a STUN client as defined in RFC 8489 [291]. Further, the UE shall also follow the procedures in RFC 8445 [289] and RFC 8839 [290] when sending media. When receiving an SDP offer which does not indicate support for ICE, the UE aborts the ICE procedures and reverts to RFC 3264 [27B] offer/answer procedures; per RFC 8445 [289] and RFC 8839 [290]. However, if the terminating UE is behind a NA(P)T device this may result in the inability to pass media for the session as the terminating UE will respond with its locally assigned IP address which is unreachable. In order to ensure successful media exchange, the terminating UE shall provide either a STUN derived IP address and port or a TURN provided IP address and port in the m/c lines of the SDP answer. If the provided address and port is a TURN address and port, the policy charging and control framework will be unable to establish proper filter criteria as the address is that of the TURN server and not that of the UE or NAT in front of the UE; see RFC 8445 [289] subclause B.3 for further details. To rectify this issue, the terminating UE shall also include a candidate attribute as described in RFC 8445 [289] and RFC 8839 [290] identifying the server reflexive IP address and port (i.e. the IP address and port on the public side of the NAT) used when a TURN provided address and port is provided in the m/c line of the SDP answer. K.5.3 P-CSCF support of ICE The P-CSCF procedures to support ICE as specified in RFC 8445 [289] and RFC 8839 [290] are defined in subclause 6.7.2.7. K.5.4 Void Annex L (normative): IP-Connectivity Access Network specific concepts when using EPS to access IM CN subsystem L.1 Scope The present annex defines IP-CAN specific requirements for a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is Evolved Packet System (EPS). The EPS IP-CAN has an EPS core network which can be supported by an E-UTRAN radio access network. L.2 EPS aspects when connected to the IM CN subsystem via E-UTRAN L.2.1 Introduction A UE accessing the IM CN subsystem, and the IM CN subsystem itself, utilise the services provided by EPS to provide packet-mode communication between the UE and the IM CN subsystem. Requirements for the UE on the use of these packet-mode services are specified in this clause. Requirements for the P-GW in support of this communication are specified in 3GPP TS 29.061 [11], and 3GPP TS 29.212 [13B]. When using the EPS, each IP-CAN bearer is provided by an EPS bearer. L.2.2 Procedures at the UE L.2.2.1 EPS bearer context activation and P-CSCF discovery The policy on the PDN connection established during the EPS attach procedure identifies parameters for composing the ESM messages sent during the EPS attach procedure as specified in 3GPP TS 24.301 [8J], when the UE performs the EPS attach procedure in order to communicate with IM CN subsystem. The UE may support the policy on the PDN connection established during the EPS attach procedure. If the UE supports the optional configuration parameter "Access_Point_Name_Parameter_Reading_Rule", as defined in 3GPP TS 24.167 [8G] and has been configured with this parameter, then the UE shall use it to retrieve the access point name to use in the EPS bearer context activation procedure. If the UE supports the policy on the PDN connection established during the EPS attach procedure, the UE may support being configured with the policy on the PDN connection established during the EPS attach procedure using one or more of the following methods: a) the EPS_initial_attach_ConRefs node of EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the EPS_initial_attach_ConRefs node of EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and c) the EPS_initial_attach_ConRefs node of 3GPP TS 24.167 [8G]. If the UE is configured with both the EPS_initial_attach_ConRefs node of 3GPP TS 24.167 [8G] and the EPS_initial_attach_ConRefs node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the EPS_initial_attach_ConRefs node of the EFIMSConfigData file shall take precedence. NOTE 1: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [15B]. Prior to communication with the IM CN subsystem, the UE shall: a) if not attached for EPS services yet, perform a EPS attach procedure as specified in 3GPP TS 24.301 [8J]. If the UE requests establishment of a PDN connection during the EPS attach procedure, and the UE supports and is configured with the policy on the PDN connection established during the EPS attach procedure, the UE shall compose the ESM messages sent during the EPS attach procedure, according to the policy on the PDN connection established during the EPS attach procedure; b) ensure that a EPS bearer context used for SIP signalling according to the APN and P-GW selection criteria described in 3GPP TS 23.401 [7B], is available. This EPS bearer context shall remain active throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the deregistration. As a result, the EPS bearer context provides the UE with information that makes the UE able to construct an IPv4 or an IPv6 address; NOTE 2: The default EPS bearer context can also be used for SIP signalling as well as any other EPS bearer context. When the EPS bearer context establishment procedure for the SIP signalling is initiated by the UE: I. if a default EPS bearer context is not available with the selected P-GW, the UE shall indicate to the network in the PDN CONNECTIVITY REQUEST that the request is for SIP signalling. If the request is authorized, the network establishes a bearer with the appropriate QCI as described in 3GPP TS 24.301 [8J]. The UE may also use this EPS bearer context for DNS and DHCP signalling; II. if the default EPS bearer context is available with the selected P-GW, and is to be used for SIP signalling no additional steps are needed; and III. if the default EPS bearer context is available with the selected P-GW and an EPS bearer for SIP signalling with the correct QCI and TFT is to be established, the UE shall indicate to the network, by setting the IM CN Subsystem Signalling Flag in the Protocol Configuration Options information element in the BEARER RESOURCE ALLOCATION REQUEST message, that the request is for SIP signalling. If the request is authorized, the network either establishes a new dedicated bearer or modifies an exisiting bearer with the appropriate QCI and TFT as described in 3GPP TS 24.301 [8J]. The general QoS negotiation mechanism is described in 3GPP TS 24.301 [8J]; and NOTE 3: An EPS bearer with a QCI value other than the one for signalling can carry both IM CN subsystem signalling and media, in case the media does not need to be authorized by Policy and Charging control mechanisms as defined in 3GPP TS 29.212 [13B] and the media stream is not mandated by the P-CSCF to be carried in a separate EPS bearer. c) acquire a P-CSCF address(es). The methods for P-CSCF discovery are: I. When using IPv4, employ the Dynamic Host Configuration Protocol (DHCP) RFC 2132 [20F], the DHCPv4 options for SIP servers RFC 3361 [35A], and RFC 3263 [27A] as described in subclause 9.2.1. When using IPv6, employ Dynamic Host Configuration Protocol for IPv6 (DHCPv6) RFC 3315 [40], the DHCPv6 options for SIP servers RFC 3319 [41] and DHCPv6 options for Domain Name Servers (DNS) RFC 3646 [56C] as described in subclause 9.2.1. II. Transfer P-CSCF address(es) within the EPS bearer context activation procedure. The UE shall indicate the request for a P-CSCF address to the network within the Protocol Configuration Options information element of the PDN CONNECTIVITY REQUEST message or BEARER RESOURCE ALLOCATION REQUEST message. If the network provides the UE with a list of P-CSCF IPv4 or IPv6 addresses in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message or ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall assume that the list is ordered top-down with the first P-CSCF address within the Protocol Configuration Options information element as the P-CSCF address having the highest preference and the last P-CSCF address within the Protocol Configuration Options information element as the P-CSCF address having the lowest preference. III. The UE selects a P-CSCF from the list (see 3GPP TS 31.103 [15B]) stored in the ISIM. IV. The UE selects a P-CSCF from the list in IMS management object. The UE shall use method IV to select a P-CSCF, if - a P-CSCF is to be discovered in the home network; - the UE is roaming; and - the IMS management object contains the P-CSCF list. The UE shall use method III to select the P-CSCF, if: - a P-CSCF is to be discovered in the home network; - the UE is roaming; - either the UE does not contain the IMS management object, or the UE contains the IMS management object but the IMS management object does not contain the P-CSCF list; and - the ISIM residing in the UICC supports the P-CSCF list. The UE can freely select method I or II for P-CSCF discovery, if: - the UE is in the home network; or - the UE is roaming and the P-CSCF is to be discovered in the visited network. The UE can select method IV, if: - the UE is in the home network; and - the IMS management object contains the P-CSCF list. In case method I is selected and several P-CSCF addresses or FQDNs are provided to the UE, the selection of P-CSCF address or FQDN shall be performed as indicated in RFC 3361 [35A] when using IPv4 or RFC 3319 [41] when using IPv6. If sufficient information for P-CSCF address selection is not available, selection of the P-CSCF address by the UE is implementation specific. NOTE 4: The UE decides whether the P-CSCF is to be discovered in the serving network or in the home network based on local configuration, e.g. whether the application on the UE is permitted to use local breakout. If the UE is designed to use I above, but receives P-CSCF address(es) according to II, then the UE shall either ignore the received address(es), or use the address(es) in accordance with II, and not proceed with the DHCP request according to I. If the UE is configured to use Option II above and detects that all P-CSCFs known by the UE have been used when the UE selects a different P-CSCF as a result of: - receiving 305 (Use Proxy) to the REGISTER request; - receiving 504 (Server Time-out); or - expiration of the timer F at the UE, then if there are more than one PDN connection that UE is connected to and unless the IP-CAN bearer is in use by other applications, the UE shall: 1) release IP-CAN bearer that is used only for the transport of SIP signalling and that are not used for other non-IMS applications, but shall not release emergency IP-CAN bearers; and 2) unless the UE decides the service is no longer needed, a) perform a new P-CSCF discovery procedure as described in subslause 9.2.1; and b) perform the procedures for initial registration as described in subclause 5.1.1.2. When using IPv4, the UE may request a DNS Server IPv4 address(es) via RFC 2132 [20F] or by the Protocol Configuration Options information element when activating a EPS bearer context according to 3GPP TS 24.301 [8J]. When using IPv6, the UE may request a DNS Server IPv6 address(es) via RFC 3315 [40] and RFC 3646 [56C] or by the Protocol Configuration Options information element when activating a EPS bearer context according to 3GPP TS 24.301 [8J]. The encoding of the request and response for IPv4 or IPv6 address(es) for DNS server(s) and list of P-CSCF address(es) within the Protocol Configuration Options information element is described in 3GPP TS 24.301 [8J]. When: - the UE obtains an EPS bearer context used for SIP signalling by performing handover of the connection from another IP-CAN; - IP address of the UE is not changed during the handover; and - the UE already communicates with the IM CN subsystem via the connection with the other IP-CAN, e.g. the UE determines that its contact with host portion set to the UE IP address (or FQDN of the UE) associated with the connection with the other IP-CAN has been bound to a public user identity; the UE shall continue using the P-CSCF address(es) acquired in the other IP-CAN. The UE may support the policy on when a UE roaming in a VPLMN is allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS. If the UE roams in the EPS IP-CAN, has a session and the policy indicates "roaming in a VPLMN and having an ongoing session, is not allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS", the UE shall not handover the PDN connection providing access to IMS from EPC via WLAN to EPS. If the UE roams in the EPS IP-CAN, has a session and the policy indicates "roaming in a VPLMN and having an ongoing session, is allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS", the UE shall, if not prevented by other rules or policies, handover the PDN connection providing access to IMS from EPC via WLAN to EPS. If the UE roams in the EPS IP-CAN and the policy indicates "roaming in a VPLMN is not allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS, irrespective of if the UE is in a session or not", the UE shall not handover the PDN connection providing access to IMS from EPC via WLAN to EPS. The UE can re-establish a new PDN connection to another IP-CAN type in idle mode, e.g. due to UE domain preference. If the UE supports the policy on whether a roaming UE when in a session is allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS, the UE may support being configured with the policy on whether a roaming UE when in a session is allowed to transfer the PDN connection providing access to IMS between EPC via WLAN EPS using one or more of the following methods: a) the Allow_Handover_PDN_connection_WLAN_And_EPS node of EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the Allow_Handover_PDN_connection_WLAN_And_EPS node of EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and c) the Allow_Handover_PDN_connection_WLAN_And_EPS node of 3GPP TS 24.167 [8G]. If the UE is configured with both the Allow_Handover_PDN_connection_WLAN_And_EPS node of 3GPP TS 24.167 [8G] and the Allow_Handover_PDN_connection_WLAN_And_EPS node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the Allow_Handover_PDN_connection_WLAN_And_EPS node of the EFIMSConfigData file shall take precedence. NOTE 5: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [15B]. L.2.2.1A Modification of a EPS bearer context used for SIP signalling The EPS bearer context shall not be modified from being used exclusively for SIP signalling to a general purpose EPS bearer. After the establishment of an EPS bearer context used for SIP signalling, the UE shall not set the IM CN Subsystem Signalling Flag in the Protocol Configuration Options information element of any subsequent BEARER RESOURCE MODIFICATION REQUEST message for that APN. The UE shall ignore the IM CN Subsystem Signalling Flag if received from the network in the Protocol Configuration Options information element. After the establishment of a EPS bearer context used for SIP signalling, the UE shall not indicate the request for a P-CSCF address to the network within the Protocol Configuration Options information element of any subsequent BEARER RESOURCE MODIFICATION REQUEST message for that APN. The UE shall ignore P-CSCF address(es) if received from the network in the Protocol Configuration Options information element. L.2.2.1B Re-establishment of the EPS bearer context for SIP signalling If the UE registered a public user identity with an IP address allocated for the APN of the EPS bearer context used for SIP signalling, the EPS bearer context used for SIP signalling is deactivated as result of signalling from the network and: i) if the UE is required to perform an initial registration according to subclause L.3.1.2; ii) if the signalling from the network results in requiring the UE to initiate activation of the PDN connection of the EPS bearer context used for SIP signalling; or iii) if the UE needs to continue having a public user identity registered with an IP address allocated for the APN; the UE shall: A) if the non-access stratum is performing the UE requested PDN connectivity procedure and the EPS bearer context activation procedure(s) for the APN triggered as result of the signalling from the network, wait until the UE requested PDN connectivity procedure and the EPS bearer context activation procedure(s) for the APN finish; and B) perform the procedures in subclause L.2.2.1, bullets a), b) and c). If none of the bullets i), ii) and iii) of this subclause evaluate to true, or the procedures in bullet B) of this subclause were unable to ensure that the EPS bearer context used for SIP signalling is available or were unable to acquire any P-CSCF address(es): 1) if the SIP signalling was carried over a dedicated EPS bearer context, the UE shall release all resources established as a result of SIP signalling by sending to the network either: a) a BEARER RESOURCE MODIFICATION REQUEST message, if there are EPS bearer contexts to this PDN that are not related SIP sessions; or b) a PDN DISCONNECT REQUEST message if all the EPS bearer contexts to this PDN are related to SIP sessions. NOTE: If the SIP signalling was carried over the default EPS bearer context, all the resources established as a result of SIP signalling are released without any explicit NAS signalling. If the default EPS bearer context of the PDN connection of the EPS bearer context used for SIP signalling was deactivated at the start of this subclause, and the procedures in bullet B) of this subclause ensured that the EPS bearer context used for SIP signalling is available and acquired the P-CSCF address(es), the UE shall perform a new initial registration according to subclause 5.1.1.2. L.2.2.1C P-CSCF restoration procedure A UE supporting the P-CSCF restoration procedure performs one of the following procedures: A if the UE used method II for P-CSCF discovery and if the UE receives one or more P-CSCF address(es) in the Protocol Configuration Options information element of a Modify EPS Bearer Context Request message the one or more P-CSCF addresse(s) do not include the address of the currently used P-CSCF, then the UE shall acquire a different P-CSCF address from the one or more P-CSCF addresse(s) in the Modify EPS Bearer Context Request message. If more than one P-CSCF address with the same container identifier (i.e. "P-CSCF IPv6 Address" or "P-CSCF IPv4 Address") are included, then the UE shall assume that the more than one P-CSCF addresses with the same container identifier are prioritised with the first P-CSCF address with the same container identifier within the Protocol Configuration Options information element as the P-CSCF address with the highest priority. If the UE used method II for P-CSCF discovery and if the UE has previously sent the "P-CSCF Re-selection support" PCO indicator at PDN creation and if the UE receives one or more P-CSCF address(es) in the Protocol Configuration Options information element of a Modify EPS Bearer Context Request message, then the UE shall acquire a P-CSCF address from the one or more P-CSCF addresse(s) in the Modify EPS Bearer Context Request message. If more than one P-CSCF address with the same container identifier (i.e. "P-CSCF IPv6 Address" or "P-CSCF IPv4 Address") are included, then the UE shall assume that the more than one P-CSCF addresses with the same container identifier are prioritised with the first P-CSCF address with the same container identifier within the Protocol Configuration Options information element as the P-CSCF address with the highest priority; B if the UE uses RFC 6223 [143] as part of P-CSCF restoration procedures, and if the P-CSCF fails to respond to a keep-alive request, then the UE shall acquire a different P-CSCF address using one of the methods I, III and IV for P-CSCF discovery described in the subclause L.2.2.1. If the UE has an ongoing session and acquired the new P-CSCF address by using procedure A described above, the UE may wait until the UE has detected that the ongoing session has ended before performing an initial registration as specified in subclause 5.1. In all other cases, when the UE has acquired the P-CSCF address, the UE not having an ongoing session shall perform an initial registration as specified in subclause 5.1. NOTE 1: For UEs using procedure A described above, the network ensures that P-CSCF address(es) in the Protocol Configuration Options information element of a Modify EPS Bearer Context Request message is sent only during P-CSCF restoration procedures as defined in subclause 5 of 3GPP TS 23.380 [7D]. NOTE 2: The P-CSCF can be completely unreachable, so it is up to UE implementation to detect the end of an ongoing session, e.g. using media plane inactivity detection. Services depending on signalling such as CW and MT calls will not work during this time. L.2.2.2 Session management procedures The existing procedures for session management as described in 3GPP TS 24.301 [8J] shall apply while the UE is connected to the IM CN subsystem. L.2.2.3 Mobility management procedures The existing procedures for mobility management as described in 3GPP TS 24.301 [8J] shall apply while the UE is connected to the IM CN subsystem. L.2.2.4 Cell selection and lack of coverage The existing mechanisms and criteria for cell selection as described in 3GPP TS 36.304 [19B] shall apply while the UE is connected to the IM CN subsystem. L.2.2.5 EPS bearer contexts for media L.2.2.5.1 General requirements NOTE 1: In EPS, the UE cannot control whether media streams belonging to different SIP sessions are established on the same EPS bearer context or not. During establishment of a session, the UE establishes data streams(s) for media related to the session. Such data stream(s) can result in activation of additional EPS bearer context(s). Either the UE or the network can request for resource allocations for media, but the establishment and modification of the EPS bearer is controlled by the network as described in 3GPP TS 24.301 [8J]. NOTE 2: When the UE wishes to allocate bandwidth for RTP and RTCP, the UE uses the rules as those outlined in 3GPP TS 29.213 [13C]. If the resource allocation is initiated by the UE, the UE starts reserving resources whenever it has sufficient information about the media streams, and used codecs available as specified in 3GPP TS 24.301 [8J]. NOTE 3: If the resource reservation requests are initiated by the EPS IP CAN, then the bearer establishment is initiated by the network after the P-CSCF has authorised the respective IP flows and provided the QoS requirements over the Rx interface to the PCRF as described in 3GPP TS 29.214 [13D]. L.2.2.5.1A Activation or modification of EPS bearer contexts for media by the UE If the UE is configured not to initiate resource allocation for media according to 3GPP TS 24.167 [8G], then the UE shall refrain from requesting additional EPS bearer context(s) for media until the UE considers that the network did not initiate resource allocation for the media. L.2.2.5.1B Activation or modification of EPS bearer contexts for media by the network If the UE receives an activation request from the network for a EPS bearer context which is associated with the EPS bearer context used for signalling, the UE shall, based on the information contained in the Traffic Flow Template information element, correlate the media EPS bearer context with a currently ongoing SIP session establishment or SIP session modification. If the UE receives a modification request from the network for a EPS bearer context that is used for one or more media streams in an ongoing SIP session, the UE shall: 1) modify the related EPS bearer context in accordance with the request received from the network. L.2.2.5.1C Deactivation of EPS bearer context for media When a data stream for media related to a session is released, if the EPS bearer resource transporting the data stream is no longer needed and allocation of the EPS bearer resource was requested by the UE, then the UE releases the EPS bearer resource. NOTE: The EPS bearer resource can be needed e.g. for other data streams of a session or for other applications in the UE. L.2.2.5.1D Default EPS bearer context usage restriction policy The default EPS bearer context usage restriction policy consists of zero or more default EPS bearer context usage restriction policy parts. The default EPS bearer context usage restriction policy part consists of a mandatory media type condition and an optional ICSI condition. The default EPS bearer context usage restriction policy does not apply to UE detected emergency calls. Sending media is restricted according to the default EPS bearer context usage restriction policy, if sending media is restricted according to at least one default EPS bearer context usage restriction policy part of the default EPS bearer context usage restriction policy or if the UE is roaming. Sending media is restricted according to the default EPS bearer context usage restriction policy part if: 1) the media is to be sent for a media stream negotiated in a session offered or established by SIP signalling; 2) the media stream is of a media type indicated in the media type condition of the EPS bearer context usage restriction policy part; 3) the following is true: a) the default EPS bearer context usage restriction policy part does not have the ICSI condition; or b) the session is offered or established by SIP signalling related to an IMS communication service identified in the ICSI condition of the default EPS bearer context usage restriction policy part; and 4) the media is to be sent via the default EPS bearer context of the PDN connection for SIP signalling. The UE may support the default EPS bearer context usage restriction policy. If the UE supports the default EPS bearer context usage restriction policy: 1) the UE shall not send media restricted according to the default EPS bearer context usage restriction policy; and 2) the UE may support being configured with the default EPS bearer context usage restriction policy using one or more of the following methods: a) the Default_EPS_bearer_context_usage_restriction_policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the Default_EPS_bearer_context_usage_restriction_policy node of the EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and c) Default_EPS_bearer_context_usage_restriction_policy node of 3GPP TS 24.167 [8G]. If the UE is configured with both the the Default_EPS_bearer_context_usage_restriction_policy node of Default_EPS_bearer_context_usage_restriction_policy node of 3GPP TS 24.167 [8G] and the Ethe Default_EPS_bearer_context_usage_restriction_policy node of FIMSConfigData file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the EFIMSConfigData file shall take precedence. NOTE: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [15B]. L.2.2.5.2 Special requirements applying to forked responses NOTE 1: The procedures in this subclause only apply when the UE requests activation and modification of media bearers. In the case where the network activates and modifies the media bearers the network takes care of the handling of media bearers in the case of forking. Since the UE does not know that forking has occurred until a second, provisional response arrives, the UE requests resource allocation as required by the initial response received. If a subsequent provisional response is received, different alternative actions may be performed depending on the requirements in the SDP answer: 1) the bearer requirements of the subsequent SDP can be accommodated by the existing resources requested. The UE performs no further resource requests. 2) the subsequent SDP introduces different QoS requirements or additional IP flows. The UE requests further resource allocation according to subclause L.2.2.5.1. 3) the subsequent SDP introduces one or more additional IP flows. The UE requests further resource allocation according to subclause L.2.2.5.1. NOTE 2: When several forked responses are received, the resources requested by the UE are the "logical OR" of the resources indicated in the multiple responses to avoid allocation of unnecessary resources. The UE does not request more resources than proposed in the original INVITE request. When a final answer is received for one of the early dialogs, the UE proceeds to set up the SIP session. The UE shall release all the unneeded IP-CAN resources. Therefore, upon the reception of the first final 200 (OK) response for the INVITE request (in addition to the procedures defined in RFC 3261 [26] subclause 13.2.2.4), the UE shall: 1) in case resources were established or modified as a consequence of the INVITE request and forked provisional responses that are not related to the accepted 200 (OK) response, send release request to release the unneeded resources. L.2.2.5.3 Unsuccessful situations One of the Rx and Gx interface related error codes can be received by the UE in either the PDN CONNECTIVITY REJECT message, the BEARER RESOURCE MODIFICATION REJECT message, or the BEARER RESOURCE ALLOCATION REJECT message. If the UE receives a Rx and Gx interface related error code, the UE shall either handle the resource reservation failure as described in subclause 6.1.1 or retransmit the message up to three times. The Rx and Gx interface related error codes are further specified in 3GPP TS 29.214 [13D] and 3GPP TS 29.212 [13B]. L.2.2.6 Emergency service L.2.2.6.1 General Emergency bearers are defined for use in emergency calls in EPS and core network support of these bearers is indicated to the UE in NAS signalling. Where the UE recognises that a call request is an emergency call and the core network supports emergency bearers, the UE shall use these EPS bearer contexts for both signalling and media for emergency calls made using the IM CN subsystem. Some jurisdictions allow emergency calls to be made when the UE does not contain an ISIM or USIM, or where the credentials are not accepted. Additionally, where the UE is in state EMM-REGISTERED.LIMITED-SERVICE and EMM-REGISTERED.PLMN-SEARCH, a normal ATTACH has been attempted but it can also be assumed that a registration in the IM CN subsystem will also fail. In such cases, subject to the lower layers indicating that the network does support emergency bearer services in limited service state (see 3GPP TS 36.331 [19F]), the procedures for emergency calls without registration can be applied, as defined in subclause 5.1.6.8.2. If the EPS authentication procedure has already succeeded during the latest normal or emergency ATTACH procedure, the UE shall perform an initial emergency registration, as described in subclause 5.1.6.2 before attempting an emergency call as described in subclause 5.1.6.8.3. NOTE 1: The UE can determine that EPS authentication procedure has succeeded during the emergency ATTACH procedure when a non-null integrity protection algorithm (i.e. other than EIA0 algorithm) is received in the NAS signalling SECURITY MODE COMMAND message. When activating an EPS bearer context to perform emergency registration, the UE shall request a PDN connection for emergency bearer services as described in 3GPP TS 24.301 [8J]. The procedures for EPS bearer context activation and P-CSCF discovery, as described in subclause L.2.2.1 of this specification apply accordingly. In order to find out whether the UE is attached to the home PLMN or to the visited PLMN, the UE shall compare the MCC and MNC values derived from its IMSI with the MCC and MNC of the PLMN the UE is attached to. If the MCC and MNC of the PLMN the UE is attached to do not match with the MCC and MNC derived from the IMSI, then for the purpose of emergency calls in the IM CN subsystem the UE shall consider to be attached to a VPLMN. NOTE 2: In this respect an equivalent HPLMN, as defined in 3GPP TS 23.122 [4C] will be considered as a visited network. NOTE 3: The UE verifies if a detected emergency number is still present in the Extended Local Emergency Number List after attach to a different PLMN. It is possible for the number to no longer be present in the Extended Local Emergency Number List if: - the PLMN attached to relies on the Local Emergency Number List for deriving a URN; or - the previously received Extended Emergency Number List Validity field indicated "Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received". If the UE detected an emergency number, the UE subsequently performs an attach procedure or an emergency attach procedure with a different PLMN than the PLMN from which the UE received the last Extended Local Emergency Number List, the dialled number is not stored in the ME, in the USIM and in the Local Emergency Number List; and - the ATTACH ACCEPT message received from the different PLMN contains the Extended Local Emergency Number List and the emergency number is present in the updated Extended Local Emergency Number List then the UE uses the updated Extended Local Emergency Number List when it performs the procedures in subclause L.2.2.6.1B; and - the ATTACH ACCEPT message received from the different PLMN contains no Extended Local Emergency Number List or the emergency number is no longer present in the updated Extended Local Emergency Number List then the UE shall attempt UE procedures for SIP that relate to emergency using emergency service URN "urn:service:sos". If the dialled number is equal to a local emergency number stored in the Extended Local Emergency Number List (as defined in 3GPP TS 24.301 [8J]), then the UE shall recognize such a number as for an emergency call and: - if the dialled number is equal to an emergency number stored in the ME, or in the USIM, then the UE shall perform either procedures in the subclause L.2.2.6.1B or the procedures in subclause L.2.2.6.1A; and - if the dialled number in not equal to an emergency number stored in the ME, or in the USIM, then the UE shall perform procedures in the subclause L.2.2.6.1B. If the dialled number is not equal to a local emergency number stored in the Extended Local Emergency Number List (as defined in 3GPP TS 24.301 [8J]) and: - if the dialled number is equal to an emergency number stored in the ME, in the USIM or in the Local Emergency Number List (as defined in 3GPP TS 24.008 [8]), then the UE shall recognize such a number as for an emergency call and performs the procedures in subclause L.2.2.6.1A. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.2A.1.1 and subclause 5.1.3.1, if: - the 380 (Alternate Service) response contains a Contact header field; - the value of the Contact header field is a service URN; and - the service URN has a top-level service type of "sos"; then the UE determines that "emergency service information is included" as described 3GPP TS 23.167 [4B]. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.3.1 if the 380 (Alternate Service) response does not contain a Contact header field with service URN that has a top-level service type of "sos", then the UE determines that "no emergency service information is included" as described 3GPP TS 23.167 [4B]. If the "emergency service information is included" as described 3GPP TS 23.167 [4B]: 1) if the URN in the Contact header field matches an emergency service URN in table L.2.2.6.1, then the type of emergency service is the value corresponding to the matching entry in table L.2.2.6.1; and 2) if the URN in the Contact header field does not match any emergency service URN in table L.2.2.6.1, then the type of emergency service is not identified. NOTE 4: In bullet 2), the URN in the Contact header field either contains "no emergency subservice type" as described in 3GPP TS 23.167 [4B] triggering an emergency call, or contains an "emergency subservice type that does not map into an emergency service category for the CS domain" as described in 3GPP TS 23.167 [4B] triggering a normal call when the dialled number is available or triggering an emergency call when the dialled number is not available. The country specific URN is an example of a "emergency subservice type that does not map into an emergency service category for the CS domain". When the emergency registration expires, the UE should disconnect the PDN connection for emergency bearer services as described in 3GPP TS 24.301 [8J]. Upon receiving a 3xx other than 380 (Alternative service), 4xx, 5xx or 6xx response to an INVITE request for a UE detectable emergency call, the UE shall perform domain selection as specified in 3GPP TS 23.167 [4B] annex H, to re-attempt the emergency call. L.2.2.6.1A Type of emergency service derived from emergency service category value The type of emergency service for an emergency number is derived from the settings of the emergency service category value (bits 1 to 5 of the emergency service category value as specified in subclause 10.5.4.33 of 3GPP TS 24.008 [8]). Table L.2.2.6.1 below specifies mappings between a type of emergency service and an emergency service URN. The UE shall use the mapping to match an emergency service URN and a type of emergency service. If a dialled number is an emergency number but does not map to a type of emergency service the service URN shall be "urn:service:sos". Table L.2.2.6.1: Mapping between type of emergency service and emergency service URN Type of emergency service Emergency service URN Police urn:service:sos.police Ambulance urn:service:sos.ambulance Fire Brigade urn:service:sos.fire Marine Guard urn:service:sos.marine Mountain Rescue urn:service:sos.mountain NOTE 1: It is not possible for a UE to indicate more than one type of emergency service in an emergency service URN. If an IP-CAN, capable of providing local emergency numbers, did not provide a local emergency number that matches the dialled number (see subclause 5.1.6.1) and multiple types of emergency service can be derived for a dialled number from the information configured on the USIM then: - if the UE is in the HPLMN, the UE shall map any one of these types of emergency service to an emergency service URN as specified in table L.2.2.6.1; and - if the UE is in the VPLMN, the UE shall select "urn:service:sos". NOTE 2: If the Non-3GPP emergency number indicator within the Non-3GPP NW provided policies IE (see 3GPP TS 24.008 [8]) provided through registration procedures over 3GPP access is set to "use of non-3GPP emergency numbers permitted", the UE also considers WLAN provided local emergency numbers (see 3GPP TS 24.302 [8U], subclause 4.7). If the Non-3GPP NW provided policies IE provided through registration procedures over 3GPP access is set to "use of non-3GPP emergency numbers not permitted", the UE does not consider WLAN provided local emergency numbers. If the Non-3GPP NW provided policies IE is not provided through registration procedures over 3GPP access, the UE does not consider WLAN provided local emergency numbers. If an IP-CAN, capable of providing local emergency numbers, provided a local emergency number that matches the dialled number (see subclause 5.1.6.1), and: - if the UE can derive one or more types of emergency service from the information received from the IP-CAN for the dialled number and the UE cannot derive types of emergency service from the information configured on the USIM for the dialled number; or - if the UE is able to derive identical types of emergency service from both the information received from the IP-CAN for the dialled number and from the information configured on the USIM for the dialled number, then the UE shall map any one of these emergency service types to an emergency service URN as specified in table L.2.2.6.1. NOTE 3: How the UE resolves clashes where an emergency number is associated with one or more different types of emergency service configured in the USIM and in information received from the access network, is implementation dependent. L.2.2.6.1B Type of emergency service derived from extended local emergency number list The Extended Local Emergency Number List (defined in 3GPP TS 24.301 [8J]) can contain sub-services of the associated emergency service URN for the detected emergency number. If: - the length of sub-services field is greater than "0", the UE shall construct the emergency service URN using "urn:service:sos" followed by adding a dot followed by the content of the sub-services field; and - the length of sub-services field is "0", the UE shall use the emergency service URN "urn:service:sos". EXAMPLE 1: For a detected number, if the sub-service is "gas", then the UE constructs "urn:service:sos.gas" as the associated emergency service URN. EXAMPLE 2: For a detected number, if no sub-service is provided, then the UE uses "urn:service:sos" as the associated emergency service URN. L.2.2.6.2 eCall type of emergency service If the IP-CAN indicates the eCall over IMS support defined in 3GPP TS 36.331 [19F] or in 3GPP TS 38.331 [19G], or the CS domain is not available to the UE, the UE can send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". If the IP-CAN does not indicates the eCall support indication and the CS domain is available to the UE, the UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". L.2.2.6.3 Current location discovery during an emergency call Void. L.2A Usage of SDP L.2A.0 General NOTE 1: When: - establishing a session which is not an emergency session; or - modifying a session which is not an emergency session; and if the IMSVoPS indicator is received in the EPS network feature support information element (see 3GPP TS 24.301 [8J]) and no persistent EPS bearer context exists at the UE, the UE constructs SDP based on the restrictions indicated in the IMSVoPS indicator. Regardless whether the IMSVoPS indicator indicating voice is supported or not, m-lines can be set to "audio" and exclude voice codecs from the SDP answer or SDP offer. When a persistent EPS bearer context exists, m-lines can be set to "audio" and include voice codecs in the SDP answer or SDP offer. NOTE 2: When the UE is accessing the IM CN subsystem via E-UTRAN, the appropriate specification for access domain selection is 3GPP TS 23.221 [6]. L.2A.1 Impact on SDP offer / answer of activation or modification of EPS bearer context for media by the network If, due to the activation of EPS bearer context from the network the related SDP media description needs to be changed, the UE shall update the related SDP information by sending, within a SIP request, a new SDP offer for each of the existing SIP dialogs, If the UE receives a modification request from the network for a EPS bearer context that is used for one or more media streams in an ongoing SIP session, the UE shall: 1) if, due to the modification of the EPS bearer context, the related SDP media description need to be changed, update the related SDP information by sending, within a SIP request, a new SDP offer for each of the existing SIP dialogs, and respond to the EPS bearer context modification request. NOTE: The UE can decide to indicate additional media streams as well as additional or different codecs in the SDP offer than those used in the already ongoing session. L.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE If the UE receives an SDP offer where the SDP offer includes all media streams for which the originating side indicated its local preconditions as met, if the precondition mechanism is supported by the terminating UE and the IP-CAN performs network-initiated resource reservation for the terminating UE and the available resources are not sufficient for the received offer, the terminating UE shall indicate its local preconditions and provide the SDP answer to the originating side without waiting for resource reservation. NOTE: If the resource reservation is controlled by the EPS IP-CAN, the resource reservation request is initiated by the network after the P-CSCF has authorised the respective IP flows and provided the QoS requirements over the Rx interface to the PCRF as described in 3GPP TS 29.214 [13D]. L.2A.3 Emergency service NOTE: When establishing an emergency session or when modifying an emergency session, the IMSVoPS indicator does not influence handling of SDP offer and SDP answer. L.3 Application usage of SIP L.3.1 Procedures at the UE L.3.1.0 Registration and authentication The UE shall perform reregistration of a previously registered public user identity bound to any one of its contact addresses when changing to an IP-CAN for which usage is specified in annex R or annex W. The reregistration is performed using the new IP-CAN. NOTE 1: This document does not specify how the UE detects that the used IP-CAN has changed. The information that is forcing the reregistration is also used to generate the content for the P-Access-Network-Info header field. NOTE 2: The UE will send the reregistration irrespective of whether it has a SIP dialog or not. If the UE supports the 3GPP PS data off, then the UE shall in all REGISTER requests include the "+g.3gpp.ps-data-off" header field parameter defined in subclause 7.9.8 set to a value indicating the 3GPP PS data off status. When the UE sends a REGISTER request, if the 3GPP PS data off status is "active", then the UE shall only include media feature tags associated with services that are 3GPP PS data off exempt services in the g.3gpp.icsi-ref media feature tag, as defined in subclause 7.9.2 and RFC 3840 [62], for the IMS communication services it intends to use. If the UE is registered, and the 3GPP PS data off status is changed or the UE is provided by the network with a new list of 3GPP PS data off exempt services while the 3GPP PS data off status is "active", then the UE shall perform a reregistration of the previously registered public user identity. A UE supporting ANBR as specified in 3GPP TS 26.114 [9B] shall also support RAN-assisted codec adaptation as specified in 3GPP TS 36.300 [268] and 3GPP TS 36.321 [269]. If the UE supports ANBR, upon receiving a 200 (OK) response to the REGISTER request and if the 200 (OK) response contains a Feature-Caps header field with the g.3gpp.anbr feature-capability indicator the UE shall assume that the network supports RAN-assisted codec adaptation as specified in 3GPP TS 36.300 [268] and 3GPP TS 36.321 [269]. The UE is allowed to include the SDP ‘anbr’ attribute during session establishment as specified in 3GPP TS 26.114 [9B]. L.3.1.0a IMS_Registration_handling policy The IMS_Registration_handling policy indicates whether the UE deregisters from IMS after a configured amount of time after receiving an indication that the IMS Voice over PS Session is not supported. The UE may support the IMS_Registration_handling policy. If the UE supports the IMS_Registration_handling policy, the UE may support being configured with the IMS_Registration_handling policy using one or more of the following methods: a) the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and c) the IMS_Registration_Policy node of 3GPP TS 24.167 [8G]. If the UE is configured with both the IMS_Registration_Policy node of 3GPP TS 24.167 [8G] and the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the IMS_Registration_Policy node of the EFIMSConfigData file shall take precedence. NOTE 1: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [15B]. If the UE is registered with IMS and the IMSVoPS indicator, provided by the lower layers (see 3GPP TS 24.301 [8J]), indicates voice is not supported, the UE shall: A) if the Stay_Registered_When_VoPS_Not_Supported leaf indicates requirement to stay registered, the UE needs not to deregister and maintains the registration as required for IMS services; or NOTE 2: The UE will periodically refresh the registration when needed. B) if the Stay_Registered_When_VoPS_Not_Supported leaf indicates requirement to deregister and the Deregistration_Timer leaf used to configure the NoVoPS-dereg timer defined in table 7.8.1 contains a timer value for the time to wait before deregistrerting from IMS, start a timer with the value indicated in the policy and: a) if the timer expires before the UE receives an indication from the lower layers that IMS voice is supported: 1) if there is no ongoing IMS session, the UE either performs reregistration as specified in subclause 5.1.1.4 and shall only include feature tags associated with services that are independent of IMSVoPS indicator or deregister from the IMS following the procedures specified in subclause 5.1.1.6; or 2) if there is ongoing IMS session, and i) if the UE does not receive indication from the lower layer that the IMS voice is supported before the ongoing IMS session is terminated, the UE either performs reregistration as specified in subclause 5.1.1.4 and shall only include feature tags associated with services that are independent of IMSVoPS indicator or deregister from the IMS following the procedures specified in subclause 5.1.1.6 as soon as the ongoing IMS based service is terminated; or ii) if the UE receives indication from the lower layer that the IMS voice is supported before the ongoing IMS session is terminated, cancel the timer; or NOTE 3: How the UE selects reregistration or deregistration is implementation dependent (e.g., SMS service) b) if the UE receives an indication from the lower layers that IMS voice is supported before the timer expires, cancel the timer. If the IMS_Registration_handling policy is not configured, the UE behaviour is implementation specific. L.3.1.1 P-Access-Network-Info header field The UE shall always include the P-Access-Network-Info header field where indicated in subclause 5.1. NOTE: If the P-Access-Network-Info header field includes radio cell identity, the P-Access-Network-Info header field populated by the UE that supports Multi-RAT Dual Connectivity with the EPC as described in 3GPP TS 37.340 [264] will contain the information about the radio cell identity of the Master RAN node that is serving the UE. L.3.1.1A Cellular-Network-Info header field Not applicable. L.3.1.2 Availability for calls This subclause documents the minimal requirements for being available for voice communication services when using EPS. A UE shall perform an initial registration as specified in subclause 5.1.1.2 using an EPS bearer context for SIP signalling (see annex L.2.2.1), if all the following conditions are met: 1) if the UE is operating in one of the following modes of operation (see 3GPP TS 24.301 [8J]): a) PS mode 1; b) CS/PS mode 1 and the UE is attached for EPS-Services only; 2) if the UE is capable of receiving any (but not necessarily all) of the media types which the CS domain supports, such that the media type can also be used when accessing the IM CN subsystem using the current IP-CAN; 3) if: a) the media type of item 2 is an "audio" media type b) the UE supports codecs suitable for (conversational) speech; and c) the "audio" media type is not restricted from inclusion in an SDP message according to the media type restriction policy as specified in subclause 6.1.1 and one of the following is true: a) 3GPP PS data off status is "inactive"; b) 3GPP PS data off status is "active", the UE is in the HPLMN or the EHPLMN, and MMTEL voice is a 3GPP PS data off exempt service; or c) 3GPP PS data off status is "active", the UE is in the VPLMN, the UE is configured with an indication that MMTEL voice is a 3GPP PS data off exempt service in a VPLMN, and MMTEL voice is a 3GPP PS data off roaming exempt service. 4) if the UE determines that its contact has not been bound to a public user identity using the IP-CAN, such that the contact is expected to be used for the delivery of incoming requests in the IM CN subsystem relating to the media of item 2 and item 3; 5) if the IMSVoPS indicator, provided by the lower layers (see 3GPP TS 24.301 [8J]), indicates voice is supported; 6) if the procedures to perform the initial registration are enabled (see 3GPP TS 24.305 [8T]); and 7) if the EPS bearer context used for SIP signalling is: a) available; or b) not available, and the UE: i. is allowed to send a PDN CONNECTIVITY REQUEST message to establish an EPS bearer context that is needed for performing the initial registration; or ii. is allowed to send a BEARER RESOURCE ALLOCATION REQUEST message, wishes to establish an EPS bearer with the correct QCI and TFT for performing the initial registration, and a default EPS bearer context for the APN exists. NOTE 1: 3GPP TS 24.301 [8J] specifies conditions that prevent the UE from sending a PDN CONNECTIVITY REQUEST message or a BEARER RESOURCE ALLOCATION REQUEST message. NOTE 2: Regardless of any of the above conditions, a UE might attempt to register with the IM CN subsystem at any time. EXAMPLE: As an example of the note, a UE configured to preferably attempt to use the EPS to access IM CN subsystem can perform an initial registration as specified in subclause 5.1.1.2, if the conditions in items 2, 3, 4, 5, 6 and 7 in this subclause, evaluate to true. The UE indicates to the non-access stratum the status of being available for voice over PS when: I) the UE is capable of receiving any (but not necessarily all) of the media types which the CS domain supports, such that the media type can also be used when accessing the IM CN subsystem using the current IP-CAN; II) if the media type of item I is an "audio" media type, the UE supports codecs suitable for (conversational) speech, the "audio" media type is not restricted from inclusion in an SDP message according to the media type restriction policy as specified in subclause 6.1.1, and: a) 3GPP PS data off status is "inactive"; b) 3GPP PS data off status is "active", the UE is in the HPLMN or the EHPLMN, and MMTEL voice is a 3GPP PS data off exempt service; or c) 3GPP PS data off status is "active", the UE is in the VPLMN, the UE is configured with an indication that MMTEL voice is a 3GPP PS data off exempt service in a VPLMN, and MMTEL voice is a 3GPP PS data off roaming exempt service; and III) the UE determines a contact has been bound to a public user identity using the IP-CAN, such that this contact is expected to be used for the delivery of incoming requests in the IM CN subsystem relating to such media. The UE indicates to the non-access stratum the status of being not available for voice over PS when: I) in response to receiving the IMSVoPS indicator indicating voice is supported, the UE: - initiated an initial registration as specified in subclause 5.1.1.2, received a final response to the REGISTER request sent, but the conditions for indicating the status of being available for voice over PS are not met; or - did not initiate an initial registration as specified in subclause 5.1.1.2 and, these conditions for indicating the status of being available for voice over PS are not met; or II) the conditions for indicating the status of being available for voice over PS are no longer met. NOTE 3: The status of being not available for voice over PS is used for domain selection for UE originating sessions / calls specified in 3GPP TS 23.221 [6] subclause 7.2a. L.3.1.2A Availability for SMS The UE determines that the UE is able to use SMS using IMS if the UE: I) is capable of using the MIME type "application/vnd.3gpp.sms" (see 3GPP TS 24.341 [8L]), such that the MIME type can also be used when accessing the IM CN subsystem using the current IP-CAN; II) supports the role of an SM-over-IP sender (see 3GPP TS 24.341 [8L]); IIA) determines the EPS bearer context used for SIP signalling exists; III) determines a contact has been bound to a public user identity using the IP-CAN, such that this contact is expected to be used for the delivery of incoming requests in the IM CN subsystem relating to such media; IV) the UE does not determine that SMS over IP is restricted in 3GPP TS 24.341 [8L] subclause 5.2.1.3; and V) the 3GPP PS data off status is: - "inactive"; - "active", the UE is in the HPLMN or the EHPLMN, and SMS over IMS is a 3GPP PS data off exempt service; or - "active", the UE is in the VPLMN, the UE is configured with an indication that SMS over IMS is a 3GPP PS data off exempt service in a VPLMN, and SMS over IMS is a 3GPP PS data off roaming exempt service. When above criteria are not matched, the UE determines that SMS using IMS is unavailable. NOTE: The status that SMS using IMS is unavailable is used for domain selection for UE originating SMS specified in 3GPP TS 23.221 [6] subclause 7.2c. L.3.1.3 Authorization header field Void. L.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Upon receiving an INVITE request not including the "precondition" option-tag in the Supported header field and not including the "precondition" option-tag in the Require header field, and the IP-CAN performs network-initiated resource reservation for the UE, the UE: 1) if the INVITE request contains an SDP offer and the local resources required at the terminating UE for the received SDP offer are not available: a) shall not alert the user; and b) shall send 183 (Session Progress) response to the INVITE request without waiting for resource reservation and without alerting the user. If the INVITE request includes a Supported header field indicating support of reliable provisional responses, the UE shall send the 183 (Session Progress) response reliably. In the 183 (Session Progres) response, the UE shall include an SDP answer; and 2) if the INVITE request does not contain an SDP offer and the INVITE request includes a Supported header field indicating support of reliable provisional responses: a) shall generate an SDP offer; b) if the local resources required at the terminating UE for the generated SDP offer are not available: A) shall not alert the user; and B) shall reliably send 183 (Session Progress) response to the INVITE request without waiting for resource reservation and without alerting the user. In the 183 (Session Progres) response, the UE shall include the generated SDP offer. Upon successful reservation of local resources, if the precondition mechanism is not used by the terminating UE, the UE can send 180 (Ringing) response to the INVITE request and can alert the user. L.3.1.5 3GPP PS data off If the 3GPP PS data off status is "active" the UE shall only send initial requests that: 1) are associated with a 3GPP IMS service which enforces 3GPP PS data off; NOTE: These services are specified in 3GPP TS 22.011 [1C], and enforcement of 3GPP PS data off is described in the respective service specifications. 2) are associated with an emergency service; 3) are associated with access to RLOS; or 4) are associated with 3GPP PS data off exempt services configured in the UE using one or more of the following methods: - the non_3GPP_ICSIs_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G] is not configured; - the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the VPLMN; - the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] is not configured; or - the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the VPLMN. If the UE is configured with both the non_3GPP_ICSIs_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. If the UE is configured with both the non_3GPP_ICSIs_roaming_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. If the 3GPP PS data off status changes from "inactive" to "active" the UE shall release all dialogs that 1) are not associated with a 3GPP IMS service which enforces 3GPP PS data off; NOTE: These services are specified in 3GPP TS 22.011 [1C], and enforcement of 3GPP PS data off is described in the respective service specifications. 2) are not associated with an emergency service; and 3) are not associated with 3GPP data off exempt services configured in the UE using one or more of the following methods: - the non_3GPP_ICSIs_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G] is not configured; - the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the VPLMN; - the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] is not configured; or - the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the VPLMN. If the UE is configured with both the non_3GPP_ICSIs_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. If the UE is configured with both the non_3GPP_ICSIs_roaming_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. L.3.1.6 Transport mechanisms No additional requirements are defined. L.3.1.7 RLOS L.3.1.7.1 General The support for RLOS as described in this subclause is optional for the UE. L.3.1.7.2 Registration A UE containing a UICC on sending an unprotected REGISTER request for RLOS, shall perform the actions as specified in subclause 5.1.1.2 wih the following additions: a) the UE shall in the REGISTER request include a "+g.3gpp.rlos" Contact header field parameter, as defined in subclause 7.9.9. NOTE: The UE can choose to use initial registration using IMS AKA or initial registration using GPRS-IMS bundled authentication. A UE not containing a UICC on sending an uprotected REGISTER request for RLOS shall perform the actions as specified in subclause 5.1.1.2 for registration using GPRS-IMS bundled authentication with the following additions: a) the UE shall generate a home network domain name according to the rules specified in 3GPP TS 23.003 [3] using the PLMN to which the UE is currently attached and set the Request-URI to the SIP URI of the so generated home network domain name; b) the UE shall include a To header field set to "sip:[email protected]" (specified in 3GPP TS 23.003 [3]); c) the UE shall include a From header field set to "sip:[email protected]" (specified in 3GPP TS 23.003 [3]); and d) the UE shall in the REGISTER request include a "+g.3gpp.rlos" Contact header field parameter, as defined in subclause 7.9.9 On reception of a 200 (OK) response to the REGISTER request for RLOS, the UE shall perform the actions as specified in subclause 5.1.1.2 and shall locally store an indication that RLOS session setup is possible. The indication is valid for an implementation specific time. On receiving a 403 (Forbidden) response containing a Response-Source header field with a "fe" header field parameter set to "<urn:3gpp:fe:s-cscf>" for an initial registration that included a "+g.3gpp.rlos" Contact header field parameter in the REGISTER request, then the UE shall locally store an indication that setup of a RLOS session is possible. The indication is stored for an implementation dependent time. L.3.1.7.3 Session Setup L.3.1.7.3.1 Void L.3.1.7.3.2 RLOS session set-up in case of unsuccessful registration The UE shall establish a RLOS session as described in this sub-clause only after it has initiated a RLOS registration and has received a 403 (Forbidden) response sent from an S-CSCF. When establishing a RLOS session in case of an unregistered user, the UE is allowed to receive responses to RLOS requests and requests inside an established RLOS session on the unprotected ports. The UE shall reject or silently discard all other messages. Additionally, the UE shall transmit signalling packets pertaining to the RLOS session from the same IP address and unprotected port on which it expects to receive signalling packets containing the responses to RLOS requests and the requests inside the established RLOS session. When establishing a RLOS session for an unregistered user, the UE shall use the local IP address and P-CSCF address as used when sending the RLOS registration. The UE shall send only the initial INVITE requests to the port advertised to the UE during the P-CSCF discovery procedure. If the UE does not receive any specific port information during the P-CSCF discovery procedure, the UE shall send the initial INVITE request to the SIP default port values as specified in RFC 3261 [26]. The UE shall apply the procedures as specified in subclause 5.1.2A.1 and subclause 5.1.3 with the following additions: 1) the UE shall set the From header field of the INVITE request to the public user identity as used in the RLOS registration; 2) the UE shall: a) if a dial string for a specific RLOS service is available in the UE, use the dial string to build the Request-URI as specified in subclause 5.1.2A.1.3; and b) if no dial string for a specific RLOS service is available in the UE use the dummy MSISDN value as defined in 3GPP TS 23.003 [3] to build the Request-URI as specified in subclause 5.1.2A.1.3; 3) the UE shall insert in the INVITE request, a To header field with the same value as in the Request-URI; 4) The UE shall insert a P-Preferred-Service header field according to RFC 6050 [121] set to "urn:urn-7:3gpp-service.ims.icsi.rlos"; 5) The UE shall insert an Accept-Contact header field field containing the "+g.3gpp.icsi-ref" header field parameter containing an ICSI value set to "urn:urn-7:3gpp-service.ims.icsi.rlos"; 6) the UE shall include in the P-Access-Network-Info header field in any request for a dialog, any subsequent request (except CANCEL requests) or response (except CANCEL responses) within a dialog or any request. Insertion of the P-Access-Network-Info header field into the ACK request is optional. The UE shall populate the P-Access-Network-Info header field with the current point of attachment to the IP-CAN as specified for the access network technology (see subclause 7.2A.4).; 7) The UE shall populate the P-Preferred-Identity header field in the INVITE request with an IMEI based identity in the form of a SIP URI as specified in 3GPP TS 23.003 [3] subclause 13.13; 8) a Contact header field set to include SIP URI that contains in the hostport parameter the IP address of the UE and an unprotected port where the UE will receive incoming requests belonging to this dialog. The UE shall also include a "sip.instance" media feature tag containing Instance ID as described in RFC 5626 [92]. The UE shall also include the "+g.3gpp. icsi-ref" header field parameter containing an ICSI value set to "urn:urn-7:3gpp-service.ims.icsi.rlos" . The UE shall not include either the public or temporary GRUU in the Contact header field; 9) a Via header field set to include the IP address of the UE in the sent-by field and for the UDP the unprotected server port value where the UE will receive responses, while for the TCP, the response is received on the TCP connection on which the RLOS request was sent. For the UDP, the UE shall also include "rport" header field parameter with no value in the top Via header field.; NOTE 1: The UE inserts the same IP address and port number into the Contact header field and the Via header field, and sends all IP packets to the P-CSCF from this IP address and port number. 10) if the UE has its location information available, or a URI that points to the location information, the UE shall include a Geolocation header field in the INVITE request in the following way: - if the UE is aware of the URI that points to where the UE's location is stored, include the URI as the Geolocation header field value, as described in RFC 6442 [89]; or - if the UE is aware of its location information, include the location information in a PIDF location object, in accordance with RFC 4119 [90], include the location object in a message body with the content type application/pidf+xml, and include a Content ID URL, referring to the message body, as the Geolocation header field value, as described RFC 6442 [89], and include a Content-Disposition header field with a disposition type "render" value and a "handling" header field parameter with an "optional" value, as described in RFC 3261 [26]; NOTE 2: If the location information is old or inaccurate, the UE does not consider location information to be available. 11) if the UE includes a Geolocation header field, the UE shall also include a Geolocation-Routing header field with a "yes" header field value, which indicates that the location of the UE can be used by other entities to make routing decisions, as described in RFC 6442 [89]; and 12) if the UE has neither geographical location information available, nor a URI that points to the location information, the UE shall not insert a Geolocation header field in the INVITE request. The UE shall build a proper preloaded Route header field value for all new dialogs. The UE shall build a Route header field value containing only the P-CSCF URI which was used in the RLOS registration. When a SIP transaction times out, i.e. timer B, timer F or timer H expires at the UE, the UE may behave as if timer F expired, as described in subclause 5.1.1.4. If the response for the initial INVITE request indicates that the UE is behind NAT, and the INVITE request was sent over TCP connection, the UE shall keep the TCP connection during the entire duration of the emergency session. In this case the UE will receive all responses to the emergency requests and the requests inside the established emergency session over this TCP connection. If the Via header field of any provisional response, or of the final 200 (OK) response, for the initial INVITE request contains a "keep" header field parameter with a value, unless the UE detects that it is not behind a NAT, the UE shall start to send keep-alives associated with the session towards the P-CSCF, as described in RFC 6223 [143]. L.3.1.7.3.3 RLOS session set-up in case of successful registration The UE shall apply the procedures as specified in subclauses 5.1.2A and 5.1.3 with the following additions: 1) the UE shall include in the Request-URI of the initial INVITE request the dummy MSISDN value as defined in 3GPP TS 23.003 [3]; 2) the UE shall insert in the INVITE request, a To header field with the same value as in the Request-URI; 3) The UE shall insert a P-Preferred-Service header field according to RFC 6050 [121] set to "urn:urn-7:3gpp-service.ims.icsi.rlos"; and 4) The UE shall insert an Accept-Contact header field field containing the "+g.3gpp.icsi-ref" header field parameter containing an ICSI value set to "urn:urn-7:3gpp-service.ims.icsi.rlos"; L.3.2 Procedures at the P-CSCF L.3.2.0 Registration and authentication Void. L.3.2.1 Determining network to which the originating user is attached If the P-CSCF is configured to handle emergency requests, in order to determine from which network the request was originated the P-CSCF shall check the MCC and MNC fields received: - during the registration procedure from the Rx interface as defined in 3GPP°TS°29.214 [13D] (e.g. used for deployments without IMS-level roaming interfaces where the P-CSCF is located in the home network); or - from the P-Access-Network-Info header field. NOTE: The above check can be against more than one MNC code stored in the P-CSCF. L.3.2.2 Location information handling Void. L.3.2.3 Prohibited usage of PDN connection for emergency bearer services If the P-CSCF detects that a UE uses a PDN connection for emergency bearer services for a non-emergency REGISTER request, the P-CSCF shall reject that request by a 403 (Forbidden) response. NOTE: By assigning specific IP address ranges for a PDN connection for emergency bearer services and configuring those ranges in P-CSCF, the P-CSCF can detect based on the registered Contact address if UE uses an emergency PDN connection for initial registration. L.3.2.4 Support for paging policy differentiation The P-CSCF may support paging policy differentiation by marking packet(s) to be sent towards the UE related to that IMS capability. A specific DSCP (IPv4) value and/or a specific Traffic Class (IPv6) value are assigned by local configuration in the P-CSCF. If local policy requires to provide such marking, the P-CSCF shall identify terminating requests which: a) contain SDP with an "audio" media line and which are related to a IMS multimedia telephony service session specified in TS 24.173 [8H]; or b) do not contain an SDP offer but some indication, e.g. a feature capability indicator, indicates that an "audio" media line that would meet network policy for such differentiation, could form part of the subsequent SDP offer. NOTE 1: Precise details of such indications, if any, are subject to operator policy. Alternatively the operator policy can be to not preferentially page requests without an SDP offer. For such identified requests: a) where an unreliable transport mechanism is used as the transport protocol for SIP, the P-CSCF shall mark packets containing an INVITE request; and b) if a reliable transport mechanism is used as the transport protocol for SIP: 1) if a new reliable transport connection needs to be established, the P-CSCF shall turn on the marking of packets within the reliable transport connection in advance of sending an INVITE request; and 2) if there is an existing reliable transport connection, the P-CSCF may turn on the marking of packets within the reliable transport connection in advance of sending an INVITE request. In both these cases for a reliable transport connection, the P-CSCF shall turn off the marking of packets within the reliable transport connection at an appropriate time. L.3.2.5 Void L.3.2.6 Resource sharing L.3.2.6.1 Registration If PCC is supported for this access technology a P-CSCF supporting resource sharing shall insert a Resource-Share header field with the value set to "supported" as described in subclause 7.2.13 and perform the actions in the following subclauses. L.3.2.6.2 UE-originating case Upon receiveing an initial INVITE request from a served UE, if the P-CSCF supports resource sharing and local policy requires that resources are reserved already on the SDP offer in the initial INVITE request, the P-CSCF can: 1) for each m-line in the SDP offer, internally generate a set of temporary resource sharing rules where: a) if the media line is not subject to resouce sharing according to local policies, each resource sharing rule contains a sharing key with a value that is unique and not used by any another media stream in any ongoing session involving the UE; b) directionality is included according to local policy; and c) if the media line is subject to resouce sharing according to local policies, each resource sharing rule contains a sharing key with the value as assigned to other ongoing media stream(s) of some ongoing session(s) involving the UE that also use the shared resources; and 2) apply resource-sharing as specified in 3GPP TS 29.214 [13D] using the temporary resource sharing rules. When the P-CSCF supporting resource receives a 18x response or a 2xx response containing the initial SDP answer, a Resource-Share header field with the value "media-sharing" and the "origin" header field parameter set to "session-initiator", the P-CSCF: 1) shall store resource sharing rules and the value of the corresponding sharing key as described in subclause 7.2.13.5 and use the stored sharing keys to identify resource sharing rules for the media streams in this session; and 2) will apply resource sharing as specified in 3GPP TS 29.214 [13D] using the stored sharing rules. NOTE 1: If a Resource-Share header field containing the same stored sharing key values and updated resource sharing rules are received in any other session involving the served UE, the updated resource sharing rules overrides the resource sharing rules received in this session. If P-CSCF supports resource sharing and when the first response to the initial INVITE request (with the exception of the 100 (Trying) response) contains a Resource-Share header field with the value "no-media-sharing" and the "origin" header field parameter set to the value "session-initiator", the P-CSCF shall not share media in this session. NOTE 2: When resource sharing is not possible, sharing keys identifying the temporary set of resource sharing rules used over the Rx interface if resources were reserved using the SDP offer can still be kept but can never be used in any other session involving this UE as long as this session is ongoing. If P-CSCF supports resource sharing and when the first response to the initial INVITE request (with the exception of the 100 (Trying) response) containing the initial SDP answer does not contain a Resource-Share header field, the P-CSCF may apply resource sharing using local configuration. L.3.2.6.3 UE-terminating case L.3.2.6.3.1 The initial INVITE request contains an initial SDP offer If P-CSCF supports resource sharing and when P-CSCF receives an initial INVITE request destined to the served user containg the Resource-Share header field parameter with the value "media-sharing" and the "origin" header field parameter set to the value "session-receiver" and if local policy requires resource reservation using the initial SDP offer the P-CSCF shall: 1) store resource sharing rules and corresponding sharing key values as described in subclause 7.2.13.5 and use each stored sharing key to identify resource sharing rules for media streams in this session; and 2) apply resource sharing as specified in 3GPP TS 29.214 [13D] using the stored resource sharing rules. NOTE: If a Resource-Share header field containing the stored sharing key are received in any other session involving the served UE, the updated resource sharing rules overrides the resource sharing rules received in this session. Upon receiving a response to the above INVITE request containing an initial SDP answer, if the initial INVITE request containging the initial SDP offer contained the Resource-Share header field set to the value "media-sharing" and the "origin" header field parameter set to "session-receiver" and if local policy requires resource reservation on the initial SDP answer, the P-CSCF shall: 1) store resource sharing rules and corresponding sharing key values as described in subclause 7.2.13.5 and use the stored sharing keys to identify resource sharing rules for media streams in this session; and 2) apply resource sharing as specified in 3GPP TS 29.214 [13D] using the stored resource sharing rules. If P-CSCF supports resource sharing and when P-CSCF receives an initial INVITE request containg the Resource-Share header field with the value "no-media-sharing" and the "origin" header field parameter set to the value "session-receiver", the P-CSCF shall not share media in this session. If P-CSCF supports resource sharing and when P-CSCF receives an initial INVITE request not containing a Resource-Share header field, the P-CSCF may apply resource sharing using local configuration. If the P-CSCF supporting resource sharing receives a request or response from the home network destined to the served user containing a Resource-Share header field with the "origin" header field parameter set to the value "session-initiator" or without the "origin header field parameter, the P-CSCF shall not use the content of the header field and remove the header field from the outgoing response or request. L.3.2.6.3.2 The 18x response or the 2xx responses contains an initial SDP offer When the P-CSCF supporting resource sharing receives an 18x response or a 2xx response from a served UE and the response contains an initial SDP offer and local policy requires resource reservation using the initial SDP offer, the P-CSCF shall : 1) for each m-line in the SDP offer, internally generate a set of temporary resource sharing rules where: - each resource sharing rule contains a sharing key with a value that is unique and not used by any another media stream in any ongoing session involving the UE; and - directionality is included according to local policy; and 2) apply resource-sharing as specified in 3GPP TS 29.214 [13D] using the temporary resource sharing rules. Upon receiving a PRACK request or an ACK request containing the initial SDP answer and a Resource-Share header field with the value "media-sharing" and the "origin" header field parameter set to "session-receiver", the P-CSCF shall: 1) store resource sharing rules and the value of the corresponding sharing key as described in subclause 7.2.13.5 and use stored sharing key to identify resource sharing rules for the media streams in this session; and 2) apply resource sharing rules as specified in 3GPP TS 29.214 [13D] using the stored sharing rules. Upon receiving a PRACK request or an ACK request containing the initial SDP answer and a Resource-Share header field with the value "no-media-sharing", the P-CSCF shall not share resources in this session. NOTE: If resources can't be shared the temporary set of resource sharing rules used over Rx interface when reserving resources using the initial SDP offer can still be kept but can never be used in any other session involving this UE as long as this dialog is ongoing. Upon receiving a PRACK request or an ACK request containing the initial SDP answer and the response does not contain a Resource-Share header field, the P-CSCF may apply resource sharing using local configuration. L.3.2.6.4 Abnormal cases If P-CSCF receives a request or response from the served UE and there is a conflict with the given instructions over Rx and the UE behaviour, the P-CSCF shall: - immediately stop resource sharing for all media streams in this session as described in 3GPP TS 29.214 [13D]; and - if resource sharing options is determined by an AS, include the Resource-Share header field set to the value "no-media-sharing" along with the "origin" header field set to "session-initiator" or "session-receiver" as appropriate in the outgoing request or response. NOTE 1: How P-CSCF detects that there is a conflict with the given instruction over Rx and the UE behaviour is implementation dependent and not further described. NOTE 2: A typical example of a conflict between a given instruction over Rx and the UE behaviour is if media sharing is allowed in both uplink and downlink direction and if in the communication waiting use case, the UE sends a 200 (OK) response to the INVITE request without putting the first call on hold. The UE's behaviour is then regarded as unpredictable and resource sharing cannot be used for any session using the stored sharing key value involving that UE. The P-CSCF shall remove the Resource-Share header field from the request or response received from a served user. L.3.2.6.5 Resource sharing options updated by AS At any point in an ongoing session the AS in the home network can include in an subsequent request or response a Resource-Share header field containing updated resource sharing options and when such an update is received the P-CSCF shall store the new sharing rules as described in subclause 7.2.13.8.4 and apply any change as described in 3GPP TS 29.214 [13D]. L.3.2.7 Priority sharing L.3.2.7.1 General If P-CSCF supports priority sharing, PCC is supported for this access technology and if according to operator policy, the P-CSCF shall apply the procedures in the following subclauses. If P-CSCF supports priority sharing, the P-CSCF shall remove the Priority-Share header field from outgoing requests or responses destined to the served UE. L.3.2.7.2 Registration procedure The P-CSCF supporting priority sharing and if according to operator policy shall include the g.3gpp.priority-share feature-capability indicator defined in subclause 7.9A.10 in a Feature-Caps header field in the SIP REGISTER request. L.3.2.7.3 Session establishment procedure When receiving the Priority-Share header field defined in subclause 7.2.16 in an initial INVITE request or in a 18x or a 2xx response to the initial INVITE request destined to the served UE and if according to operator policy, the P-CSCF shall apply priority sharing according to 3GPP TS 29.214 [13D] based on the value of the Priority-Share header field. L.3.2.7.4 Subsequent request procedure When receiving the Priority-Share header field in a re-INVITE request, in a18x or in a 2xx responses to the re-INVITE request destined to the served UE and if according to operator policy, the P-CSCF shall apply priority sharing according to 3GPP TS 29.214 [13D] based on the value of the Priority-Share header field. When receiving the Priority-Share header field in an subsequent request or in a 2xx responses to the subsequent request destined to the served UE and if according to operator policy, the P-CSCF shall apply priority sharing according to 3GPP TS 29.214 [13D], based on the value of the Priority-Share header field. L.3.2.8 RLOS L.3.2.8.1 General The support for RLOS as described in this subclause is optional for the P-CSCF. L.3.2.8.2 Registration A P-CSCF supporting RLOS shall perform the procedures as specified in subclause 5.2.2 and in addition shall perform the procedures specified in this sublclause. When the P-CSCF receives a REGISTER request from the UE and the REGISTER request contains a "+g.3gpp.rlos" Contact header field parameter, and: 1) if: a) the P-Access-Network-Info header field in REGISTER request indicates an IP-CAN for which procedures are defined in an Annex different than Annex L; or b) the IP address and APN check, as defined in section Z3.3 of 3GPP TS 23.228 [7] fail; then the P-CSCF shall reject the REGISTER request by sending a 403 response including a Response-Source header field with an "fe" header field parameter set to "<urn:3gpp:fe:p-cscf.orig>"; or 2) if the public user identity in the REGISTER request indicates a user for which the operator of the P-CSCF does not have a roaming agreement, then the P-CSCF shall select a preconfigured S-CSCF and insert a Route header field with the S-CSCF URI for originating requests and forward the request to the selected S-CSCF. When the P-CSCF receives a 403 (Forbidden) response to a REGISTER request that contained a "+g.3gpp.rlos" Contact header field parameter, the P-CSCF shall: 1) create a temporary unauthenticated subscriber record for the registered public user identity; 2) associate the S-CSCF with the registered public user identity and associated contact address; 3) store the registered public user identity as a default public user identity for use with procedures for the P-Asserted-Identity header field for requests received from the UE; 4) store the values received in the P-Charging-Function-Addresses header field; 5) if a "term-ioi" header field parameter is received in the P-Charging-Vector header field, store the value of the received "term-ioi" header field parameter; and NOTE: Any received "term-ioi" header field parameter will contain a type 1 IOI. The type 1 IOI identifies the home network of the registered user. 6) void. L.3.2.8.3 Session Setup L.3.2.8.3.1 General If the P-CSCF supports RLOS, the P‑CSCF shall accept unprotected requests on the IP address and the unprotected port advertised to the UE during the P-CSCF discovery or the SIP default port. When the P-CSCF sends unprotected responses to the UE, it shall use the same IP address and port where the corresponding request was received. L.3.2.8.3.2 General treatment for RLOS session setup – requests from an unregistered user If the P-CSCF receives an initial request for a dialog or standalone transaction, or an unknown method from an unregistered user on the IP address and the unprotected port advertised to the UE during the P-CSCF discovery or the SIP default port, The P-CSCF shall inspect the Request-URI independent of values of possible entries in the received Route header fields for the presence of the dummy MSISDN or a RLOS service specific dial string. The P-CSCF shall consider the Request URI of the initial request as indicating RLOS, if the Request-URI contains the dummy URI or a RLOS service specific dial string and if the request contains a P-Preferred-Service header field according to RFC 6050 [121] set to "urn:urn-7:3gpp-service.ims.icsi.rlos". If the P-CSCF detects that the initial request for a dialog or a standalone transaction, or an unknown method indicates RLOS, and the P-CSCF has previously stored a temporary unauthenticated subscriber record for the public user identity contained in the From header field of the request: 1) shall include a topmost Route header field set to the URI of the S-CSCF as stored in the unauthenticated subscriber record; NOTE 2: How the list of E-CSCF is obtained by the P-CSCF is implementation dependent. 2) shall execute the procedure described in subclause 5.2.6.3.3, subclause 5.2.6.3.7, subclause 5.2.6.3.11 and subclause 5.2.7.2, as appropriate except for: - verifying the preloaded route against the received Service-Route header field; - routing to IBCF; and - inserting a type 1 "orig-ioi" header field parameter in the P-Charging-Vector header field; 3) shall insert a P-Asserted-Identity header field set to the public user identity as stored in the unauthenticated subscriber record; and 4) if the P-CSCF detects that the UE is behind a NAT, and the UE's Via header field contains a "keep" header field parameter, shall add a value to the parameter, to indicate that it is willing to receive keep-alives associated with the dialog from the UE, as defined in RFC 6223 [143]. When the P-CSCF receives any 1xx or 2xx response to the above requests, the P-CSCF shall execute the appropriate procedure for the type of request described in subclause 5.2.6.3.4, subclause 5.2.6.3.8, and subclause 5.2.6.3.12, except that the P-CSCF may rewrite the port number of its own Record-Route entry to an unprotected port where the P-CSCF wants to receive the subsequent incoming requests from the UE belonging to this dialog. When the P-CSCF receives a target refresh request from the UE for a dialog, the P-CSCF shall execute the procedure described in subclause 5.2.6.3.5, except for inserting a type 1 "orig-ioi" header field parameter in the P-Charging-Vector header field. When the P-CSCF receives from the UE subsequent requests other than a target refresh request (including requests relating to an existing dialog where the method is unknown), the P-CSCF shall execute the procedure described in subclause 5.2.6.3.9, except for inserting a type 1 "orig-ioi" header field parameter in the P-Charging-Vector header field. When the P-CSCF receives any 1xx or 2xx response to the above requests, the P-CSCF shall execute the appropriate procedure for the type of request described in subclause 5.2.6.3.5 or subclause 5.2.6.3.9. L.3.2.8.3.3 General treatment for RLOS session setup – requests from a registered user The P-CSCF shall follow procedures specified subclause 5.2.6. L.3.2.9 Support of ANBR and RAN-assisted codec adaptation If the network supports ANBR as specified in 3GPP TS 26.114 [9B] and RAN-assisted codec adaptation as specified in 3GPP TS 36.300 [268] and 3GPP TS 36.321 [269], then the P-CSCF might be configured to indicate ANBR support. If the P-CSCF is configured to indicate ANBR support, when the P-CSCF receives the 200 (OK) response to the REGISTER request the P-CSCF shall include the "g.3gpp.anbr" feature-capability indicator in the Feature-Caps header field of the 200 (OK) response to the REGISTER request. L.3.3 Procedures at the S-CSCF L.3.3.1 Notification of AS about registration status Not applicable. L.3.3.2 RLOS L.3.3.2.1 General The support for RLOS as described in this subclause is optional. L.3.3.2.2 Registration A S-CSCF supporting RLOS shall perform the procedures as specified in subclause 5.4.1.2 and in addition shall perform the procedures specified in this subclause. Upon receipt of a REGISTER request that is part of an initial registration as described in subclause 5.4.1.2.1 1) if REGISTER request contains a "+g.3gpp.rlos" Contact header field parameter, the S-CSCF: a) if the S-CSCF supports GPRS-IMS-Bundled authentication and the public user identity in the REGISTER request indicates a user for which the operators of the S-CSCF does not have a roaming agreement with the home network operator, shall reject the request by returning a 420 (Bad Extension) response in which the Unsupported header field contains the value "sec-agree"; and b) if the S-CSCF does not support GPRS-IMS-Bundled authentication and the public user identity in the REGISTER request indicates a user for which the operators of the S-CSCF does not have a roaming agreement with the home network operator, shall reject the request by returning a 403 (Forbidden) response and include a Response-Source header field with a "fe" header field parameter set to "<urn:3gpp:fe:s-cscf>". The S-CSCF shall create a temporary record for the public user identity which is registered with a default service profile which is valid for an implementation specific time; and Upon receipt of a REGISTER request without an Authorization header field as described in subclause 5.4.1.2.1E and the REGISTER request contains a "+g.3gpp.rlos" Contact header field paramete, the S-CSCF shall skip the procedures in subclause 5.4.1.2.1E and shall 1) identify the user by the public user identity as received in the To header field of the REGISTER request. The S-CSCF shall derive the private user identity from the public user identity being registered by removing URI scheme and the following parts of the URI if present: port number, URI parameters, and To header field parameters; 2) check if the P-Visited-Network-ID header field is included in the REGISTER request, and if it is included identify the visited network by the value of this header field; 3) check whether a "received" header field parameter exists in the Via header field provided by the UE. If a "received" header field parameter exists, the S-CSCF shall compare the IP address recorded in the "received" header field parameter against the UE's IP address stored during registration. In case of IPv6 stateless autoconfiguration, the S-CSCF shall compare the prefix of the IP address recorded in the "received" header field parameter against the UE's IP address prefix stored during registration. If no "received" header field parameter exists in the Via header field provided by the UE, then the S-CSCF shall compare IP address recorded in the "sent-by" parameter against the stored UE IP address. In case of IPv6 stateless autoconfiguration, S-CSCF shall compare the prefix of the IP address recorded in the "sent-by" parameter against the UE's IP address prefix stored during registration. In any case, if the stored IP address (or prefix) and the (prefix of the) IP address recorded in the Via header field provided by the UE do not match, the S‑CSCF shall query the HSS as described in 3GPP TS 29.228 [14] with the derived private user identity and the public user identity as input and store the received IP address (or prefix) of the UE. If the stored IP address (or prefix) and the (prefix of the) IP address recorded in the Via header field provided by the UE still do not match the S-CSCF shall reject the registration with a 403 (Forbidden) response and skip the following steps; 4) determine the duration of the registration by checking the registration expiration interval value in the received REGISTER request and bind it either to the respective contact address of the UE or to the registration flow and the associated contact address (if the multiple registration mechanism is used). Based on local policy, the S-CSCF may reduce the duration of the registration or send back a 423 (Interval Too Brief) response specifying the minimum allowed time for registration; 5) update registration bindings; 6) create a temporary record for the public user identity being registered with a default service profile; 7) store the "icid-value" header field parameter received in the P-Charging-Vector header field; 8) if an "orig-ioi" header field parameter is received in the P-Charging-Vector header field, store the value of the received "orig-ioi" header field parameter; 9) check whether a Path header field was included in the REGISTER request and construct a list of preloaded Route header fields from the list of entries in the received Path header field. The S-CSCF shall preserve the order of the preloaded Route header fields and bind them either to the contact address of the UE and the contact information that was received in the REGISTER request; and 10) create and send a 200 (OK) response for the REGISTER request as specified in subclause 5.4.1.2.2F; In case the timer reg-await-auth is running for this user, S-CSCF supports RLOS as specified in TS 23.228 [7] and the REGISTER request contains a "+g.3gpp.rlos" Contact header field parameter, the S-CSCF shall: 1) check if the Call-ID of the request matches with the Call-ID of the 401 (Unauthorized) response which carried the last challenge. The S-CSCF shall only proceed further if the Call-IDs match; 2) stop timer reg-await-auth; 3) check whether an Authorization header field is included, containing: a) the private user identity of the user in the "username" header field parameter; b) if the "integrity-protected" header field parameter is set to "yes", the "algorithm" header field parameter set to "AKAv1-MD5" or "AKAv2-SHA-256"; NOTE: The "AKAv1-MD5" algorithm is only supported for backward compatibility. c) if the "integrity-protected" header field parameter is set to "tls-connected", the "algorithm" header field parameter set to "AKAv2-SHA-256" if the S-CSCF supports the IMS AKA using HTTP Digest AKAv2 without IPSec security association; and d) the authentication challenge response needed for the authentication procedure in the "response" header field parameter. The S-CSCF shall only proceed with the following steps in this paragraph if the authentication challenge response was included; 4) check whether the received authentication challenge response and the expected authentication challenge response (calculated by the S-CSCF using XRES and other parameters as described in RFC 3310 [49] when AKAv1 is used or as described in RFC 4169 [227] when AKAv2 is used) match. The XRES parameter was received from the HSS as part of the Authentication Vector. The S-CSCF shall only proceed with the following steps if the challenge response received from the UE and the expected response calculated by the S-CSCF do not match; 5) if there are public user identities (including the public user identity being registered, if previously registered) that belong to this user that have been previously registered with the same private user identity, and with an old contact address different from the one received in the REGISTER request and if the previous registrations have not expired: a) terminate all dialogs, associated with the previously registered public user identities (including the public user identity being registered, if previously registered), with a status code 480 (Temporarily Unavailable) in the Reason header field of the BYE request, as specified in subclause 5.4.5.1.2; b) send a NOTIFY request, to the subscribers to the registration event package of the previously registered public user identities, that indicates that all previously registered public user identities (excluding the public user identity being registered) belonging to this user identified with its private user identity, have been deregistered, as described in subclause 5.4.2.1.2. For the public user identity being registered, the NOTIFY request contains the new contact information; and c) delete all information associated with the previously registered public user identities; 6) store the following information in the local data: a) the public user identities due to the received REGISTER request which is set to the public user identity as received in the REGISTER request. The public user identity is identified as non-barred; b) a default service profile that indicates that the public user identity is registered for RLOS; c) if S-CSCF restoration procedures are supported, the restoration information if received as specified in 3GPP TS 29.228 [14]; and d) if PCRF based P-CSCF restoration procedures are supported, all the user profile(s) corresponding to the public user identities being registered (explicitly or implicitly), including the IMSI, if available; 7) update registration bindings and a) bind to each non-barred registered public user identity the registered contact information including all header field parameters contained in the Contact header field and all associated SIP URI parameters, and b) if the Contact header field of the REGISTER request contained a "+sip.instance" and a "reg-id" header field parameter, and the SIP URI in the Path header field inserted by the P-CSCF contained an "ob" SIP URI parameter header field, and: - if the public user identity has not previously been registered with the same "+sip.instance" and "reg-id" Contact header field parameter values, then create the registration flow in addition to any existing registration flow; or - if the public user identity has previously been registered with the same "+sip.instance" and "reg-id" header field parameter values, then determine whether the request refreshes or replaces an existing registration flow. If the request: i) refreshes an existing registration flow, then the S-CSCF shall leave the flow intact; or ii) replaces the existing registration flow with a new flow, then the S-CSCF shall: a) terminate any dialog, as specified in subclause 5.4.5.1.2, with a status code 480 (Temporarily Unavailable) in the Reason header field of the BYE request, associated with the registration flow being replaced; and b) send a NOTIFY request to the subscribers to the registration event package for the public user identity indicated in the REGISTER request, as described in subclause 5.4.2.1.2; 8) check whether a Path header field was included in the REGISTER request and construct a list of preloaded Route header fields from the list of entries in the received Path header field. The S-CSCF shall preserve the order of the preloaded Route header fields and bind them either to the contact address of the UE or the registration flow and the associated contact address (if the multiple registration mechanism is used) and the contact information that was received in the REGISTER request; 9) determine the duration of the registration by checking the value of the registration expiration interval value in the received REGISTER request and bind it either to the respective contact address of the UE or to the registration flow and the associated contact address (if the multiple registration mechanism is used). Based on local policy, the S-CSCF may reduce the duration of the registration or send back a 423 (Interval Too Brief) response specifying the minimum allowed time for registration.; 10) store the "icid-value" header field parameter received in the P-Charging-Vector header field; 11) if an "orig-ioi" header field parameter is received in the P-Charging-Vector header field, store the value of the received "orig-ioi" header field parameter; and 12) create a 403 (Forbidden) response for the REGISTER request including a Response-Source header field with a "fe" header field parameter set to "<urn:3gpp:fe:s-cscf >" and send the so generated response. L.3.3.2.3 Session Setup L.3.3.2.3.1 General A S-CSCF supporting RLOS shall perform the procedures as specified in subclause 5.4.3.2 and in addition shall perform the procedures specified in this subclause. When the S-CSCF receives from the served user from an initial request for a dialog or a request for a standalone transaction and performing the procedures in subclause 5.4.3.2 and: 1) if there is no original dialog identifier that the S-CSCF previously placed in a Route header field is present in the topmost Route header field of the incoming request; and 2) if the Request-URI contains the dummy MSISDN value as defined in 3GPP TS 23.003 [3] or a RLOS service specific dial string and a P-Preferred-Service header set to "urn:urn-7:3gpp-service.ims.icsi.rlos" is included in the request; the S-CSCF shall build an ordered list of initial filter criteria based on the temporary unauthenticated subscriber record for the public user identiy of the served user instead of building the ordered list of initial filter criteria as described in bullet 3). L.4 3GPP specific encoding for SIP header field extensions L.4.1 Void L.5 Use of circuit-switched domain There is no CS domain in this access technology. NOTE 1: If the UE sends an INVITE request including voice codecs which is not successful due to a failure from the lower layers indicating that access is barred for originating calls but not specific to CSFB (see 3GPP TS 24.301 [8J]) and if the CS domain is supported and available, the UE can attempt the voice call via the CS domain. NOTE 2: If the UE has sent an INVITE request including voice codecs, receives a 500 (Server Internal Error) response to this INVITE request containing no Retry-After header field, including a Reason header field with a protocol value set to "FAILURE_CAUSE" including a cause value header field parameter set to "1" as specified in subclause 7.2A.18.12.2, a Response-Source header field with a "fe" header field parameter set to "<urn:3gpp:fe:p-cscf.orig>", and the UE is attached to both PS and CS domains, the UE can attempt the voice call via the CS domain, e.g. by initiating a service request for CS fallback (see 3GPP TS 24.301 [8J]). Annex M (normative): IP-Connectivity Access Network specific concepts when using cdma2000® packet data subsystem to access IM CN subsystem M.1 Scope This annex defines IP-CAN specific requirements for call control protocol for use in the IM CN subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is the cdma2000® packet data subsystem. It also defines procedures for invoking CS domain services. M.2 cdma2000® packet data subsystem aspects when connected to the IM CN subsystem M.2.1 Introduction A UE accessing the IM CN subsystem, and the IM CN subsystem itself, utilise the services provided by the cdma2000® packet data subsystem to provide packet-mode communication between the UE and the IM CN subsystem. Requirements for the UE on the use of these packet-mode services are specified in this subclause. Requirements for the IP-CAN bearer control point (i.e. the point where the UE has attached itself to the cdma2000® packet data subsystem) support of this communication are specified in 3GPP2 X.S0011-E [127]. M.2.2 Procedures at the UE M.2.2.1 Establishment of IP-CAN bearer and P-CSCF discovery Prior to communication with the IM CN subsystem, the UE shall: a) establish a connection with the cdma2000® wireless IP network specified in 3GPP2 X.S0011-E [127]. Upon establishment a connection with the cdma2000® wireless IP network, the UE can have an IPv4 address only, an IPv6 address only, or both IPv4 and IPv6 addresses simultaneously; b) ensure that an IP-CAN bearer used for SIP signalling is available. This IP-CAN bearer shall remain active throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the last deregistration; The UE shall choose one of the following options when performing establishment of this IP-CAN bearer: I. A dedicated IP-CAN bearer for SIP signalling: The UE shall indicate to the IP-CAN bearer control point that this is an IP-CAN bearer intended to carry IM CN subsystem-related signalling only. The UE may also use this IP-CAN bearer for DNS and DHCP access. II. A general-purpose IP-CAN bearer: The UE may decide to use a general-purpose IP-CAN bearer to carry IM CN subsystem-related signalling. The UE may carry both signalling and media on the general-purpose IP-CAN bearer; and c) discover a P-CSCF. The methods for P-CSCF discovery are: I. Use DHCP mechanism II Retrieve the list of P-CSCF address(es) stored in the IMC III Obtain the list of P-CSCF address(es) from the IMS management object The UE can freely select method I, II, or III for P-CSCF discovery. If DHCP is used, the following procedures apply: Upon establishing an IP-CAN bearer, the UE may use the Dynamic Host Configuration Protocol (DHCP) specified in RFC 2131 [40A] or Dynamic Host Configuration Protocol for IPv6 (DHCPv6) specified in RFC 3315 [40] to discover the P-CSCF. Prior to accessing the DHCP server, the UE will have obtained an IP address via means other than DHCP and DHCPv6, see 3GPP2 X.S0011-E [127]. If the UE uses DHCP for P-CSCF discovery and the UE is unaware of the address of the DHCP server, the UE shall send the DHCPINFORM using the limited broadcast IP address (i.e., 255.255.255.255) and UDP port 67. If the UE knows the IP address of the DHCP server, the UE shall send the DHCPINFORM to the DHCP server's unicast IP address and UDP port 67. The DHCP server shall send the DHCPACK on the IP address specified in the Client IP Address field of the DHCPINFORM. The DHCP server may include, in the DHCPACK, the SIP Server DHCP Option specified in RFC 3361 [35A], which carries either a list of IPv4 address(es) of the P-CSCF(s) or a list of DNS fully qualified domain name(s) that can be mapped to one or more P-CSCF(s). If the UE uses DHCPv6 for P-CSCF discovery and the UE is unaware of the address of the DHCP Server, the UE shall send an Information Request using the IPv6 multicast address FF02::1:2 and the UDP port 547. If the UE knows the IP address of the DHCPv6 server, the UE shall send the Information Request message to the DHCPv6 server's IP address and UDP port 547. In the Information Request, the UE may request either one or both the SIP Servers Domain Name List option and the SIP Servers IPv6 Address List option specified in RFC 3319 [41]. The DHCP server shall send the Reply to the IP address specified in the Information Request. The DHCP server may include in the Reply either one or both the SIP Servers Domain Name List option and the SIP Servers IPv6 Address List option, as requested by the UE. In case several P-CSCF's IP addresses or domain names are provided to the UE, the UE shall perform P-CSCF selection according to RFC 3361 [35A] or RFC 3319 [41]. The UE shall perform the procedure for the resolution of domain name according to RFC 3263 [27A]. M.2.2.1A Modification of IP-CAN used for SIP signalling Not applicable. M.2.2.1B Re-establishment of the IP-CAN used for SIP signalling Not applicable. M.2.2.1C P-CSCF restoration procedure A UE supporting the P-CSCF restoration procedure uses the keep-alive procedures described in RFC 6223 [143]. If the P-CSCF fails to respond to the keep-alive request the UE shall acquire a different P-CSCF address using any of the methods described in the subclause M.2.2.1 and perform an initial registration as specified in subclause 5.1. M.2.2.2 Void M.2.2.3 IP-CAN bearer control point support of DHCP based P-CSCF discovery The IP-CAN bearer control point, or Home Agent in case of Mobile IP with reverse tunneling, may forward the packet to one or more local DHCP servers, or relay the packet to a specific DHCP server. The IP-CAN bearer control point, or Home Agent in case of Mobile IP with reverse tunnelling, shall not forward the DHCPINFORM (or Information-Request) to any UE. NOTE 1: For forwarding the DHCPINFORM or Information-Request, the IP-CAN bearer control point, or Home Agent in case of Mobile IP with reverse tunnelling, does not change the destination IP address of the packet. NOTE 2: For relaying the DHCPINFORM or Information-Request, the IP-CAN bearer control point, or Home Agent in case of Mobile IP with reverse tunnelling inserts a DHCP server's IP address in the destination IP address field of the packet. M.2.2.4 Void M.2.2.5 Handling of the IP-CAN for media M.2.2.5.1 General requirements Not applicable. M.2.2.5.1A Activation or modification of IP-CAN for media by the UE Not applicable. M.2.2.5.1B Activation or modification of IP-CAN for media by the network Not applicable. M.2.2.5.1C Deactivation of IP-CAN for media Not applicable. M.2.2.5.2 Special requirements applying to forked responses Not applicable. M.2.2.5.3 Unsuccessful situations Not applicable. M.2.2.6 Emergency service M.2.2.6.1 General When establishing an HRPD session to perform emergency registration, the UE shall follow the procedures defined in 3GPP2 X.S0060 [86B]. To determine whether the HRPD UE is attached to the home network or to the visited network, the UE shall compare the Carrier ID values obtained per 3GPP2 X.S0060 [86B]. If the Carrier ID of the network the UE is attached to does not match with the provisioned Carrier ID, then for the purpose of emergency calls in the IM CN subsystem the UE shall consider to be attached to a visited network. NOTE: For 3GPP2-1X and 3GPP2-UMB, no IP-CAN specific support is provided in the current release. No carrier identification is provided for 3GPP2-1X or 3GPP2-UMB in the P-Access-Network-Info header field, and thus there is no IMS specific procedure for identifying that the UE is in the home network. M.2.2.6.1A Type of emergency service derived from emergency service category value Not applicable. M.2.2.6.1B Type of emergency service derived from extended local emergency number list Not applicable. M.2.2.6.2 eCall type of emergency service The UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". M.2.2.6.3 Current location discovery during an emergency call Void. M.2A Usage of SDP M.2A.0 General Not applicable. M.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network Not applicable. M.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE Not applicable. M.2A.3 Emergency service No additional procedures defined. M.3 Application usage of SIP M.3.1 Procedures at the UE M.3.1.0 Void M.3.1.0a IMS_Registration_handling policy Not applicable. M.3.1.1 P-Access-Network-Info header field The UE shall always include the P-Access-Network-Info header field where indicated in subclause 5.1. M.3.1.1A Cellular-Network-Info header field Not applicable. M.3.1.2 Availability for calls Not applicable. M.3.1.2A Availability for SMS Void. M.3.1.3 Authorization header field When using SIP digest or SIP digest without TLS, the UE need not include an Authorization header field on sending a REGISTER request, as defined in subclause 5.1.1.2.1. NOTE: In case the Authorization header field is absent, the mechanism only supports that one public user identity is associated with only one private user identity. The public user identity is set so that it is possible to derive the private user identity from the public user identity by removing SIP URI scheme and the following parts of the SIP URI if present: port number, URI parameters, and To header field parameters. Therefore, the public user identity used for registration in this case cannot be shared across multiple UEs. Deployment scenarios that require public user identities to be shared across multiple UEs that don't include an private user identity in the initial REGISTER request can be supported as follows: - Assign each sharing UE a unique public user identity to be used for registration, - Assign the shared public user identitiess to the implicit registration set of the unique registering public user identities assigned to each sharing UE. M.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Not applicable. M.3.1.5 3GPP PS data off Not applicable. M.3.1.6 Transport mechanisms No additional requirements are defined. M.3.1.7 RLOS Not applicable. M.3.2 Procedures at the P-CSCF M.3.2.0 Registration and authentication Void. M.3.2.1 Determining network to which the originating user is attached For an HRPD UE, after the initial request for a dialog or standalone transaction or an unknown method is received the P-CSCF shall check the Carrier ID field received in the P-Access-Network-Info header field to determine from which network the request was originated. NOTE: For 3GPP2-1X and 3GPP2-UMB, no IP-CAN specific support is provided in the current release. No carrier identification is provided for 3GPP2-1X or 3GPP2-UMB in the P-Access-Network-Info header field, and thus there is no IMS specific procedure for identifying that the UE is in the home network. M.3.2.2 Location information handling Void M.3.2.3 Void M.3.2.4 Void M.3.2.5 Void M.3.2.6 Resource sharing Not applicable. M.3.2.7 Priority sharing Not applicable. M.3.2.8 RLOS Not applicable. M.3.3 Procedures at the S-CSCF M.3.3.1 Notification of AS about registration status The procedures described in subclause 5.4.1.7 apply with the additional procedures described in the present subclause: 1) in case the received REGISTER request contained a Timestamp header field, the S-CSCF shall insert a Timestamp header field with the value of the Timestamp header field from the received REGISTER request. M.3.3.2 RLOS Not applicable. M.4 3GPP specific encoding for SIP header field extensions M.4.1 Void M.5 Use of circuit switched domain When an emergency call is to be set up over the CS domain, the UE shall attempt it according to the procedures described in 3GPP2 C.S0005-D [85]. Annex N (Normative): Functions to support overlap signalling N.1 Scope This annex defines the procedures performed by network entities within the IM CN subsystem to support overlap signalling. The support of overlap signalling within the IM CN subsystem is optional, and is depended on the network policy. N.2 Digit collection function N.2.1 General The digit collection function is invoked if an entity requires additional digits for a decision where to route a INVITE request. NOTE 1: The digit collection function is only applicable for the in-dialog method of overlap signalling. Further information about digit collection is provided in subclause 4.9.3.3. The digit collection function may interact with a routeing database, to reach this decision. The digit collection function shall be performed by an entity acting as a B2BUA. The digit collection function requires the ability to recognise incomplete numbers. The digit collection function may be implemented in different network nodes depending on the operator's deployment strategy (e.g. AS, IBCF). NOTE 2: An HSS does not support the recognition of incomplete numbers. A routeing database being queried by ENUM also does not support the recognition of incomplete numbers. NOTE 3: A private routeing database to support the recognition of incomplete numbers e.g. for transit calls or ported numbers can be used. N.2.2 Collection of digits N.2.2.1 Initial INVITE request Upon receiving an initial INVITE request carrying an SDP offer, the digit collection function shall: 1) if the request contains enough digits to forward the request, forward the request towards it's destination; 2) if the digit collection function chooses to collect additional digits in INFO requests, in order to forward the request, and the sender of the INVITE request has indicated support of reliable responses, store the received digits and send a reliable 183 (Session Progress) provisional response in order to establish an early dialog with the sender of the INVITE request. The response shall not contain an SDP answer; or 3) if it is determined that the en-bloc will not be able to forward the request even if additional digits are received,, send a 404 (Not Found) response. Upon receiving an initial INVITE request without an SDP offer, the digit collection function shall: 1) if the request contains enough digits to forward the request, forward the request towards it's destination; or 2) send a 404 (Not Found) response. NOTE 1: If the initial INVITE request does not contain an SDP offer, a reliable 18x provisional response generated by the en-bloc conversion function would have to contain an SDP offer. In this case digit collection needs to be performed by the originating SIP entity (e.g. MGCF). When the digit collection function sends the reliable 183 (Session Progress) provisional response, in order to establish an early dialog with the sender of the INVITE request, the digit collection function shall start a digit collection timer. If the timer expires, the digit collection function shall terminate the call setup by sending a sending a 484 (Address Incomplete) response towards the sender of the INVITE request. NOTE 2: The digit collection timer is similar to the protection timer used in PSTN/ISDN. The timer value range is between 5 and 15 seconds, and the default value is 10 seconds. N.2.2.2 Collection of additional digits Upon receiving an INFO request carrying additional digits, and if an early dialog towards the destination of the initial INVITE request for the call does not exist, the digit collection function shall: 1) send a 200 (OK) response to the INFO request; 2) add the received digits to the previously stored digits for the call; 3) restart the digit collection timer; and 4) check if enough digits have been received in order to forward the initial INVITE request. When enough digits for the call have been received in order to forward the initial INVITE request, the digit collection function shall add all stored digits to the request URI and forward the request towards its destination and stop the digit collection timer. Upon receiving an INFO request carrying additional digits, and the initial INVITE request has been forwarded towards its destination, but an early dialog towards the destination of the initial INVITE request for the call does not exist, the digit collection function shall: 1) send a 200 (OK) response to the INFO request; and 2) add the received digits to the previously stored, but yet not forwarded, digits for the call; When the digit collection function receives a provisional response from the destination of the initial INVITE request, and the digit collection function has received additional digits in INFO requests, the digit collection shall generate and send an INFO request towards the destination of the initial INVITE request. The Request-URI shall contain all digits which have been received and stored since the initial INVITE request was forwarded. Upon receiving an INFO request carrying additional digits, and if an early dialog towards the destination of the initial INVITE request for the call does exist, the digit collection function shall forward the INFO request on the early dialog towards the destination of the initial SIP INVITE request. Upon receiving an INFO request carrying additional digits, and if a 180 (Ringing) or a 200 (OK) response to the initial INVITE request for the call has been received, or the digit collection function has received some other indication that enough digits have been forwarded in order for the INVITE request to reach the terminating SIP user, the digit collection function shall, based on operator policy: 1) send a 200 (OK) response to the INFO request and not forward the INFO request; or 2) forward the INFO request on the early dialog towards the destination of the initial SIP INVITE request. N.2.2.3 Handling of 404 (Not Found) / 484 (Address Incomplete) responses Upon receiving a 404/484 response to the initial INVITE request, the digit collection function shall acknowledge the response and shall start the digit collection timer. The digit collection function shall not forward the response towards the sender of the INVITE request. NOTE: If the digit collection function has received a 404/484 response, it will send a new initial INVITE request when it has received additional digits as described above, in order to establish an early dialog towards the destination of the INVITE request. The digit collection timer will re-start if an INFO request with additional digits is received. At timer expiry, the digit collection function will terminate the call as described above N.2.3 Forwarding of SIP messages by the digit collection function Apart from 404/484 responses to the initial INVITE request, and INFO requests carrying additional digits received after a 180 (Ringing) or a 200 (OK) response to the initial INVITE request has been received, the digit collection function shall forward all SIP messages. When forwarding SIP messages, the digit collection function shall modify the SIP messages to comply with SIP procedures on both call legs as specified below: 1) The digit collection function will receive a "tag" To header field parameter value from the receiver of the initial INVITE request, which is different from the "tag" To header field parameter value that the digit collection function inserted in the 183 (Session Progress) response that it sent when it received the initial INVITE request. The digit collection function shall modify the "tag" header field parameter value accordingly when forwarding mid-dialog SIP messages. 2) The digit collection function will return a Contact header field in the initial 183 (Session Progress) provisional response to the originating side, which contains a SIP-URI of the digit collection function. The contact information is used in the Request-URI of subsequent mid-dialog SIP requests sent by the originating side, until the digit collection function has received, and forwarded to the originating side, a 183 (Session Progress) provisional response from the destination of the INVITE request. If the Request-URI of the received mid-dialog SIP request contains the SIP-URI of the digit collection function, and the digit collection function forwards the request, the digit collection function shall modify the Request-URI before forwarding the SIP request. 3) The digit collection function will return the Record-Route header fields, which it received in the initial INVITE request, in the initial 183 (Session Progress) provisional response to the originating side. The information is used in the Route header fields of subsequent mid-dialog SIP requests sent by the originating side, until the digit collection function has received, and forwarded to the originating side, a 183 (Session Progress) provisional response from the destination of the INVITE request. If the Route header fields of the received mid-dialog SIP request are based on the Record-Route headers fields which the digit collection function returned in the initial 183 (Session Progress) provisional response, and the digit collection function forwards the request, the digit collection function shall modify the Route header fields before forwarding the SIP request. N.3 En-bloc conversion function N.3.1 General The en-bloc conversion function may be performed in an entity acting as B2BUA. The en-bloc conversion function may be implemented in different network nodes depending on the operator's deployment strategy (e.g. AS, IBCF). If the initial INVITE request is to be forwarded towards a network, or towards a network entity, that does not support overlap signalling, the en-bloc conversion function shall determine the end of address signalling. The following methods can be used to determine the end of the address signalling: 1) the maximum number of digits used in a national numbering plan has been received; 2) number analysis, e.g. using a provisioned dial plan, is used to determinte that the complete number of digits has been received; or 3) an inter digit timer expires, and the minimum number of digits required for routeing the call have been received. The timer is started when the initial INVITE request is received, and re-started every time new digit(s) are received. NOTE: The inter digit timer is similar to the protection timer used in PSTN/ISDN. The timer value range is between 5 and 15 seconds, and the default value is 10 seconds. The procedures for collecting additional digits are described in subclauses N.3.2 and N.3.3. When end of address signalling has been determined, the en-bloc conversion function shall generate an INVITE request, add all digits to the request and forwards the request towards its destination. N.3.2 Multiple-INVITE method Upon reception of an INVITE request, the en-bloc conversion function shall: 1) if an inter digit timer is running for a previously received INVITE request with the same Call-ID and From header, and a) if the number of digits within that previous INVITE request is below the number of digits received in the new INVITE request (or as an equivalent test if the CSeqID of the previous INVITE request is below the CSeqID of the new INVITE request), stop the inter-digit timer for that previous INVITE request and send a 484 (Address Incomplete) response for it; and b) if the number of digits with the previous INVITE request is above or equal to the number of digits received in the new INVITE request (or as an equivalent test if the CSeqID of the previous INVITE request is below the CSeqID of the new INVITE request), send a 484 (Address Incomplete) response for the new INVITE request; and 2) if the en-bloc conversion function determines that the number received in the INVITE request is complete, forward the INVITE request; and 3) if the en-bloc conversion function determines that it will not be able to forward the request even if additional digits are received, send a 404 (Not Found) response; and 4) if the en-bloc conversion function chooses to collect additional digits, store the INVITE request and start an inter-digit timer to wait for possible INVITE requests with the same Call ID and From header. When the inter-digit timer expires the en-bloc conversion function shall: 1) if it determines that the number received in the stored INVITE request is incomplete (e. g. by number analysis), terminate the call setup by sending a sending a 484 (Address Incomplete) response towards the sender of the INVITE request; and 2) if it does not determines that the number received in the last INVITE request is incomplete, forward the corresponding stored INVITE request to the next hop. After forwarding an INVITE request, the en-bloc conversion function shall apply SIP proxy procedures for all subsequent SIP messages within the corresponding dialogue, unless other functionality not related to en-bloc conversion allocated in the same physical norde requires a different behaviour. N.3.3 In-dialog method Upon receiving an initial INVITE request carrying an SDP offer, the en-bloc conversion function shall: 1) if it determines that the request contains a complete number, forward the request towards it's destination; 2) if the en-bloc conversion function chooses to collect additional digits in INFO requests before forwarding the request, and the sender of the INVITE request has indicated support of reliable responses, store the received digits, send a reliable 183 (Session Progress) provisional response without an SDP answer in order to establish an early dialog with the sender of the INVITE request, and start an inter digit timer; or 3) if the en-bloc conversion function determines that it will not be able to forward the request even if additional digits are received, send a 404 (Not Found) response. Upon receiving an initial INVITE request without an SDP offer, the en-bloc conversion function shall: 1) if it is determined that the request contains a complete number, forward the request towards it's destination; or 2) send a 404 (Not Found) response. NOTE: If the initial INVITE request does not contain an SDP offer, a reliable 18x provisional response generated by the en-bloc conversion function would have to contain an SDP offer. The en-bloc conversion function for the in-dialog method specified here does not support en-bloc conversion for calls with an initial INVITE request that does not contain an SDP offer in the present release. However, en-bloc conversion for an initial INVITE request that does not contain an SDP offer can be performed by the originating SIP entity (e.g. MGCF). Upon receiving an INFO request carrying additional digits, and an early dialog towards the destination of the initial SIP INVITE request for the call has not been created, the en-bloc conversion function shall: 1) send a 200 (OK) response to the INFO request; 2) add the received digits to the previously stored digits for the call; 3) re-start the inter digit timer; and 4) check if it can determine that a complete number for the call has been received. When the en-bloc conversion function determines that a complete number for the call has been received, it shall add all stored digits to the initial INVITE request and forward the request towards its destination and stop the inter digit timer. When the inter-digit timer expires the en-bloc conversion function shall 1) if it determines that the number so far is incomplete (e. g. by number analysis), terminate the call setup by sending a sending a 484 (Address Incomplete) response towards the sender of the INVITE request; or 2) if it does not determines that the number received in the last INVITE request is incomplete, forward the INVITE request to the next hop, including all received digits. Upon receiving an INFO request carrying additional digits, if the en-bloc conversion function has forwarded the initial INVITE request towards its destination, the en-bloc conversion function shall send a 200 (OK) response to the INFO request and not forward the INFO request. Apart from INFO requests carrying additional digits received after the initial INVITE request has been forwarded, the en-bloc conversion function shall forward all SIP messages. The en bloc conversion function will receive a "tag" To header field parameter value from the receiver of the initial INVITE request, which is different from the "tag" To header field parameter value that the digit collection function inserted in the 183 (Session Progress) response that it sent when it received the initial INVITE request. The digit collection function shall modify the "tag" To header field parameter value accordingly when forwarding in-dialog SIP messages. Annex O (normative): IP-Connectivity Access Network specific concepts when using the EPC via cdma2000® HRPD to access IM CN subsystem O.1 Scope The present annex defines IP-CAN specific requirements for a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is the Evolved Packet Core (EPC) via a cdma2000® HRPD access network. O.2 IP-CAN aspects when connected to the IM CN subsystem O.2.1 Introduction A UE accessing the IM CN subsystem, and the IM CN subsystem itself, utilise the services provided by the EPC and cdma2000® HRPD access network as specified by 3GPP2 X.P0057 [86C] to provide packet-mode communication between the UE and the IM CN subsystem. Requirements for the UE on the use of these packet-mode services are specified in this clause. Requirements for the P-GW in support of this communication are specified in 3GPP TS 29.061 [11] and 3GPP TS 29.212 [13B]. Requirements for the use of the EPC via packet cdma2000® HRPD as an IP-CAN are specified in 3GPP2 X.P0057 [86C]. O.2.2 Procedures at the UE O.2.2.1 IP-CAN bearer context activation and P-CSCF discovery Prior to communication with the IM CN subsystem, the UE shall: a) establish a connection with the IP-CAN via the cdma2000® HRPD wireless IP network specified in 3GPP2 X.P0057 [86C]. Upon establishing a connection with the cdma2000® eHRPD wireless IP network, the UE can have an IPv4 address only, an IPv6 address only, or both IPv4 and IPv6 addresses simultaneously; b) ensure that a IP-CAN bearer context used for SIP signalling is available, according to the APN and P-GW selection criteria described in 3GPP TS 23.402 [7E]. This IP-CAN bearer context shall remain active throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the deregistration; and NOTE 1: Any IP-CAN bearer can carry both IM CN subsystem signalling and media if the media does not need to be authorized by Policy and Charging control mechanisms as defined in 3GPP TS 29.212 [13B], and the media stream is not mandated by the P-CSCF to be carried in a separate IP-CAN bearer. NOTE 2: IP-CAN PDN connection and bearer management procedures are specified in 3GPP2 X.P0057 [86C]. c) acquire a P-CSCF address(es). The methods for P-CSCF discovery are: I. Use DHCP mechanism II Retrieve the list of P-CSCF address(es) stored in the IMC III Obtain the list of P-CSCFaddress(es) from the IMS management object IV. Transfer P-CSCF address(es) within the IP-CAN bearer context activation procedure. The UE shall indicate the request for a P-CSCF address to the network within the Protocol Configuration Options information element of the during PDN connectivity establishment as specified in 3GPP2 X.P0057 [86C]. If the network provides the UE with a list of P-CSCF IPv4 or IPv6 addresses, the UE shall assume that the list is prioritised with the first address within the Protocol Configuration Options information element as the P-CSCF address with the highest priority. The UE can freely select method I, II, III, or IV for P-CSCF discovery. If DHCP is used, the following procedures apply: Upon establishing an IP-CAN bearer, the UE may use the Dynamic Host Configuration Protocol (DHCP) specified in RFC 2131 [40A] or Dynamic Host Configuration Protocol for IPv6 (DHCPv6) specified in RFC 3315 [40] to discover the P-CSCF. Prior to accessing the DHCP server, the UE will have obtained an IP address via means other than DHCP and DHCPv6. If the UE uses DHCP for P-CSCF discovery and the UE is unaware of the address of the DHCP server, the UE shall send the DHCPINFORM using the limited broadcast IP address (i.e., 255.255.255.255) and UDP port 67. If the UE knows the IP address of the DHCP server, the UE shall send the DHCPINFORM to the DHCP server's unicast IP address and UDP port 67. The DHCP server shall send the DHCPACK on the IP address specified in the Client IP Address field of the DHCPINFORM. The DHCP server may include, in the DHCPACK, the SIP Server DHCP Option specified in RFC 3361 [35A], which carries either a list of IPv4 address(es) of the P-CSCF(s) or a list of DNS fully qualified domain name(s) that can be mapped to one or more P-CSCF(s). If the UE uses DHCPv6 for P-CSCF discovery and the UE is unaware of the address of the DHCP Server, the UE shall send an Information Request using the IPv6 multicast address FF02::1:2 and the UDP port 547. If the UE knows the IP address of the DHCPv6 server, the UE shall send the Information Request message to the DHCPv6 server's IP address and UDP port 547. In the Information Request, the UE may request either one or both the SIP Servers Domain Name List option and the SIP Servers IPv6 Address List option specified in RFC 3319 [41]. The DHCP server shall send the Reply to the IP address specified in the Information Request. The DHCP server may include in the Reply either one or both the SIP Servers Domain Name List option and the SIP Servers IPv6 Address List option, as requested by the UE. If the UE supports the optional configuration parameter "Access_Point_Name_Parameter_Reading_Rule", as defined in 3GPP TS 24.167 [8G] and has been configured with this parameter, then the UE shall use it to retrieve the access point name to use in the IP CAN bearer context activation procedure. In case several P-CSCF's IP addresses or domain names are provided to the UE, the UE shall perform P-CSCF selection according to RFC 3361 [35A] or RFC 3319 [41]. The UE shall perform the procedure for the resolution of domain name according to RFC 3263 [27A]. O.2.2.1A Modification of an IP-CAN bearer context used for SIP signalling The UE shall not modify the IP-CAN bearer from being used exclusively for SIP signalling to a general purpose IP-CAN bearer and vice versa. After the establishment of a SIP bearer context used for SIP signalling, the UE shall not indicate the request for a P-CSCF address to the network when requesting an IP-CAN bearer modification for that APN. The UE shall ignore P-CSCF address(es) if received from the network as part of the bearer modification procedure. O.2.2.1B Re-establishment of the IP-CAN bearer context for SIP signalling If the IP-CAN bearer context for SIP signalling is lost and cannot be re-established: a. if the SIP signalling was carried over a dedicated IP-CAN bearer, the UE shall release all resources established as a result of SIP signalling by either: - requesting an IP-CAN bearer modification if there are IP-CAN bearers to this PDN that are not related SIP sessions; or - initiating disconnection of the PDN connection if all the bearers to this PDN are related to SIP sessions. NOTE: If the SIP signalling was carried over the default IP-CAN bearer, all the resources established as a result of SIP signalling are released. O.2.2.1C P-CSCF restoration procedure A UE supporting the P-CSCF restoration procedure performs one of the following procedures: A if the UE used method II for P-CSCF discovery and if the UE receives one or more P-CSCF address(es) in an VSNCP Configure-Request message and the one or more P-CSCF addresse(s) do not include the address of the currently used P-CSCF, then the UE shall acquire a different P-CSCF address from the one or more P-CSCF addresse(s) in the VSNCP Configure-Request message. The UE shall assume that the more than one P-CSCF address are prioritised with the first P-CSCF address within the Protocol Configuration Options information element as the P-CSCF address with the highest priority; B if the UE uses RFC 6223 [143] as part of P-CSCF restoration procedures, and if the P-CSCF fails to respond to a keep-alive request, then the UE shall acquire a different P-CSCF address using one of the methods I, II and III for P-CSCF discovery described in the subclause O.2.2.1. When a different P-CSCF address is acquired the UE shall perform an initial registration as specified in subclause 5.1. O.2.2.2 Session management procedures The existing procedures for session management as described in 3GPP2 X.P0057 [86C] shall apply while the UE is connected to the IM CN subsystem. O.2.2.3 Mobility management procedures The existing procedures for mobility management as described in 3GPP2 X.P0057 [86C] shall apply while the UE is connected to the IM CN subsystem. O.2.2.4 Cell selection and lack of coverage The existing mechanisms and criteria for cell selection as described in 3GPP2 C.S0014-C [86D] shall apply while the UE is connected to the IM CN subsystem. O.2.2.5 IP-CAN bearer contexts for media O.2.2.5.1 General requirements NOTE 1: The UE cannot control whether media streams belonging to different SIP sessions are established on the same IP-CAN bearer context or not. During establishment of a session, the UE establishes data streams(s) for media related to the session. Such data stream(s) can result in activation of additional IP-CAN bearer context(s). Either the UE or the network can request for resource allocations for media, but the establishment and modification of the IP-CAN bearer is controlled by the network as described in 3GPP2 X.P0057 [86C]. NOTE 2: When the UE wishes to allocate bandwidth for RTP and RTCP, the rules as outlined in 3GPP TS 29.213 [13C] apply. Application of QoS to when using an EPC IP-CAN with cdma2000® HRPD is described in 3GPP2 X.P0057 [86C]. O.2.2.5.1A Activation or modification of IP-CAN bearer contexts for media by the UE No additional clarifications are needed for the use of the EPC via cdma2000® HRPD as an IP-CAN. O.2.2.5.1B Activation or modification of IP-CAN bearer contexts for media by the network If the UE receives an activation request from the network for an IP-CAN bearer context which is associated with the IP-CAN bearer context used for signalling, the UE shall, based on the information contained in the Traffic Flow Template provided by the network, correlate the media IP-CAN bearer context with a currently ongoing SIP session establishment or SIP session modification. If the UE receives a modification request from the network for an IP-CAN bearer context that is used for one or more media streams in an ongoing SIP session, the UE shall modify the related IP-CAN bearer context in accordance with the request received from the network. O.2.2.5.1C Deactivation of of IP-CAN bearer contexts for media Not applicable O.2.2.5.2 Special requirements applying to forked responses NOTE 1: The procedures in this subclause only apply when the UE requests activation and modification of media bearers. In the case where the network activates and modifies the media bearers the network takes care of the handling of media bearers in the case of forking. Since the UE does not know that forking has occurred until a second, provisional response arrives, the UE requests resource allocation as required by the initial response received. If a subsequent provisional response is received, different alternative actions may be performed depending on the requirements in the SDP answer: 1) the bearer requirements of the subsequent SDP can be accommodated by the existing resources requested. The UE performs no further resource requests. 2) the subsequent SDP introduces different QoS requirements or additional IP flows. The UE requests further resource allocation according to subclause O.2.2.5.1. 3) the subsequent SDP introduces one or more additional IP flows. The UE requests further resource allocation according to subclause O.2.2.5.1. NOTE 2: When several forked responses are received, the resources requested by the UE are the "logical OR" of the resources indicated in the multiple responses to avoid allocation of unnecessary resources. The UE does not request more resources than proposed in the original INVITE request. When a final answer is received for one of the early dialogs, the UE proceeds to set up the SIP session. The UE shall release all the unneeded IP-CAN resources. Therefore, upon the reception of the first final 200 (OK) response for the INVITE request (in addition to the procedures defined in RFC 3261 [26] subclause 13.2.2.4), the UE shall: 1) in case resources were established or modified as a consequence of the INVITE request and forked provisional responses that are not related to the accepted 200 (OK) response, send release request to release the unneeded resources. O.2.2.5.3 Unsuccessful situations Not applicable. O.2.2.6 Emergency service O.2.2.6.1 General Emergency services is not supported when the IP-CAN is the EPC via a cdma2000® HRPD access network. O.2.2.6.1A Type of emergency service derived from emergency service category value Not applicable. O.2.2.6.1B Type of emergency service derived from extended local emergency number list Not applicable. O.2.2.6.2 eCall type of emergency service The UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". O.2.2.6.3 Current location discovery during an emergency call Void. O.2A Usage of SDP O.2A.0 General Not applicable. O.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN bearer context for media by the network If, due to the activation of an IP-CAN bearer context from the network the related SDP media description needs to be changed the UE shall update the related SDP information by sending a new SDP offer within a SIP request, which is sent over the existing SIP dialog, If the UE receives a modification request from the network for an IP-CAN bearer context that is used for one or more media streams in an ongoing SIP session, the UE shall: 1) if, due to the modification of the IP-CAN bearer context, the related SDP media description need to be changed, update the related SDP information by sending a new SDP offer within a SIP request, that is sent over the existing SIP dialog, and respond to the IP-CAN bearer context modification request. NOTE: The UE can decide to indicate additional media streams as well as additional or different codecs in the SDP offer than those used in the already ongoing session. O.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE If the UE receives an SDP offer where the SDP offer includes all media streams for which the originating side indicated its local preconditions as met, if the precondition mechanism is supported by the terminating UE and the IP-CAN performs network-initiated resource reservation for the terminating UE and the available resources are not sufficient for the received offer the terminating UE shall indicate its local preconditions and provide the SDP answer to the originating side without waiting for resource reservation. NOTE: If the resource reservation is controlled by the network, the resource reservation request is initiated by the network after the P-CSCF has authorised the respective IP flows and provided the QoS requirements over the Rx interface to the PCRF as described in 3GPP TS 29.214 [13D]. O.2A.3 Emergency service No additional procedures defined. O.3 Application usage of SIP O.3.1 Procedures at the UE O.3.1.0 Void O.3.1.0a IMS_Registration_handling policy Not applicable. O.3.1.1 P-Access-Network-Info header field The UE shall always include the P-Access-Network-Info header field where indicated in subclause 5.1. O.3.1.1A Cellular-Network-Info header field Not applicable. O.3.1.2 Availability for calls Not applicable. O.3.1.2A Availability for SMS Void. O.3.1.3 Authorization header field When using SIP digest or SIP digest without TLS, the UE need not include an Authorization header field on sending a REGISTER request, as defined in subclause 5.1.1.2.1. NOTE: In case the Authorization header field is absent, the mechanism only supports that one public user identity is associated with only one private user identity. The public user identity is set so that it is possible to derive the private user identity from the public user identity by removing SIP URI scheme and the following parts of the SIP URI if present: port number, URI parameters, and To header field parameters. Therefore, the public user identity used for registration in this case cannot be shared across multiple UEs. Deployment scenarios that require public user identities to be shared across multiple UEs that don't include an private user identity in the initial REGISTER request can be supported as follows: - Assign each sharing UE a unique public user identity to be used for registration, - Assign the shared public user identitiess to the implicit registration set of the unique registering public user identities assigned to each sharing UE. O.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Not applicable. O.3.1.5 3GPP PS data off Not applicable. O.3.1.6 Transport mechanisms No additional requirements are defined. O.3.1.7 RLOS Not applicable. O.3.2 Procedures at the P-CSCF O.3.2.0 Registration and authentication Void. O.3.2.1 Determining network to which the originating user is attached The P-CSCF handling is as defined in subclause M.3.2. NOTE: Emergency call support for the EPC IP-CAN is not specified in this release. A common P-Access-Network-Info header field value is used for both cdma2000® HRPD based IP-CANs (i.e. HRPD access specified by 3GPP2 X.S0011‑E [127], and HRPD access as specified by 3GPP2 X.P0057 [86C]). The result of this is that in both cases the handling in the P-CSCF will be identical. If an operator deploys an IM CN subsystem with both cdma2000® HRPD based IP‑CANs, the P-CSCF has no means of distinguishing one from the other. The emergency call handling for the EPC IP‑CAN using cdma2000® HRPD access as specified by 3GPP2 X.P0057 [86C] is out of scope for this release of this specification, and therefore all identified emergency calls with a P-Access-Network-Info header field value of "3GPP2‑1X‑HRPD" will be handled with a 380 (Alternative Service) response when HRPD IP-CAN emergency support is not active. O.3.2.2 Location information handling Void. O.3.2.3 Void O.3.2.4 Void O.3.2.5 Void O.3.2.6 Resource sharing If the P-CSCF supports resource sharing, PCC is supported for this access technology and if according to local policy, the P-CSCF shall apply the procedures in subclause L.3.2.6. O.3.2.7 Priority sharing If the P-CSCF supports priority sharing, PCC is supported for this access technology and if according to operator policy, the P-CSCF shall apply the procedures in subclause L.3.2.7. O.3.2.8 RLOS Not applicable. O.3.3 Procedures at the S-CSCF O.3.3.1 Notification of AS about registration status The S-CSCF handling is as defined in subclause M.3.3.1. O.3.3.2 RLOS Not applicable. O.4 3GPP specific encoding for SIP header field extensions O.4.1 Void O.5 Use of circuit-switched domain There is no CS domain in this access technology. Annex P (informative): Void Annex Q (normative): IP-Connectivity Access Network specific concepts when using the cdma2000® 1x Femtocell Network to access IM CN subsystem Q.1 Scope The present annex defines IP-CAN specific requirements for a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is an IP network as incorporated into the cdma2000® 1x femtocell network subsystem [86E]. Q.2 cdma2000® 1x Femtocell Network aspects when connected to the IM CN subsystem Q.2.1 Introduction In the cdma2000® 1x femtocell network subsystem, the cdma2000® 1x Mobile Station (MS) accesses the IM CN subsystem by utilising the services provided by the cdma2000® 1x Femtocell Access Point (FAP) [86E]. NOTE: Protocol between the cdma2000® 1x MS and the cdma2000® 1x FAP is out of scope of this document. The cdma2000® 1x FAP 3GPP2 X.P0059-200 [86E] acts as a UE toward the IM CN subsystem. From the perspective of the FAP, it is assumed that one or more IP-CAN bearer(s) are provided, in the form of connection(s) managed by the layer 2. Q.2.2 Procedures at the UE Q.2.2.1 Activation and P-CSCF discovery Unless a static IP address is allocated to the cdma2000® 1x FAP, prior to communication with the IM CN subsystem, the cdma2000® 1x FAP shall perform a Network Attachment procedure depending on the used cdma2000® 1x FAP access type. When using a cdma2000® 1x FAP access, both IPv4 and IPv6 may be used to access the IM CN subsystem. The cdma2000® 1x FAP may request a DNS Server IPv4 address(es) via RFC 2132 [20F] or a DNS Server IPv6 address(es) via RFC 3315 [40]. When using IPv4, the cdma2000® 1x FAP may acquires a P-CSCF address(es) by using the DHCP (see RFC 2132 [20F]), the DHCPv4 options for SIP servers (see RFC 3361 [35A]), and RFC 3263 [27A]. In case the DHCP server provides several P-CSCF addresses or FQDNs to the cdma2000® 1x FAP, the cdma2000® 1x FAP shall select the P-CSCF address or FQDN as indicated in RFC 3361 [35A]. If sufficient information for P-CSCF address selection is not available, selection of the P-CSCF address by the cdma2000® 1x FAP is implementation specific. When using IPv6, the cdma2000® 1x FAP may acquires a P-CSCF address(es) by using the DHCPv6 (see RFC 3315 [40] and RFC 3646 [56C]), the DHCPv6 options for SIP servers (see RFC 3319 [41]), and RFC 3263 [27H]. In case the DHCP server provides several P-CSCF addresses or FQDNs to the cdma2000® 1x FAP, the cdma2000® 1x FAP shall select the P-CSCF address or FQDN as indicated in RFC 3319 [41]. If sufficient information for P-CSCF address selection is not available, selection of the P-CSCF address by the cdma2000® 1x FAP is implementation specific. Q.2.2.1A Modification of IP-CAN used for SIP signalling Not applicable. Q.2.2.1B Re-establishment of IP-CAN used for SIP signalling Not applicable. Q.2.2.2 Void Q.2.2.3 Void Q.2.2.4 Void Q.2.2.5 Handling of the IP-CAN for media Q.2.2.5.1 General requirements The cdma2000® 1x FAP uses the bearer used for signalling also for transmission of media. Q.2.2.5.1A Activation or modification of IP-CAN for media by the UE Not applicable. Q.2.2.5.1B Activation or modification of IP-CAN for media by the network Not applicable. Q.2.2.5.1C Deactivation of IP-CAN for media Not applicable Q.2.2.5.2 Special requirements applying to forked responses Not applicable. Q.2.2.5.3 Unsuccessful situations Not applicable. Q.2.2.6 Emergency service Q.2.2.6.1 General Emergency calls are perceived as regular calls from the perspective of the IM CN subsystem. Entities outside the IM CN subsystem identify and route such calls to PSAP. Q.2.2.6.1A Type of emergency service derived from emergency service category value Not applicable. Q.2.2.6.1B Type of emergency service derived from extended local emergency number list Not applicable. Q.2.2.6.2 eCall type of emergency service The UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". Q.2.2.6.3 Current location discovery during an emergency call Void. Q.2A Usage of SDP Q.2A.0 General Not applicable. Q.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network Not applicable. Q.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE Not applicable. Q.2A.3 Emergency service No additional procedures defined. Q.3 Application usage of SIP Q.3.1 Procedures at the UE Q.3.1.0 Void Q.3.1.0a IMS_Registration_handling policy Not applicable. Q.3.1.1 P-Access-Network-Info header field The cdma2000® 1x FAP shall include the P-Access-Network-Info header field where indicated in subclause 5.1. Q.3.1.1A Cellular-Network-Info header field Not applicable. Q.3.1.2 Availability for calls Not applicable. Q.3.1.2A Availability for SMS Void. Q.3.1.3 Authorization header field Void. Q.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Not applicable. Q.3.1.5 3GPP PS data off Not applicable. Q.3.1.6 Transport mechanisms No additional requirements are defined. Q.3.1.7 RLOS Not applicable. Q.3.2 Procedures at the P-CSCF Q.3.2.0 Registration and authentication Void. Q.3.2.1 Determining network to which the originating user is attached If access-type field in the P-Access-Network-Info header field indicated 3GPP2-1X-Femto access the P-CSCF shall assume that an initial request for a dialog or standalone transaction or an unknown method destined for a PSAP is initiated in the same country. Q.3.2.2 Location information handling Not applicable Q.3.2.3 Void Q.3.2.4 Void Q.3.2.5 Void Q.3.2.6 Resource sharing Not applicable. Q.3.2.7 Priority sharing Not applicable. Q.3.2.8 RLOS Not applicable. Q.3.3 Procedures at the S-CSCF Q.3.3.1 Notification of AS about registration status Not applicable Q.3.3.2 RLOS Not applicable. Q.4 3GPP specific encoding for SIP header field extensions Q.4.1 Void Q.5 Use of circuit-switched domain Not applicable Annex R (normative): IP-Connectivity Access Network specific concepts when using the EPC via WLAN to access IM CN subsystem R.1 Scope The present annex defines IP-CAN specific requirements for a call control protocol for use in the IM CN subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is the Evolved Packet Core (EPC) via Wireless Local Access Network (WLAN). R.2 IP-CAN aspects when connected to the IM CN subsystem R.2.1 Introduction A UE accessing the IM CN subsystem, and the IM CN subsystem itself, utilise the services provided by the EPC and the WLAN to provide packet-mode communication between the UE and the IM CN subsystem. Requirements for the UE on the use of these packet-mode services are specified in this clause. R.2.2 Procedures at the UE R.2.2.1 Establishment of IP-CAN bearer and P-CSCF discovery Prior to communication with the IM CN subsystem: NOTE 1: The UE performs access network discovery and selection procedures as specified in 3GPP TS 24.302 [8U] and executes access authentication signalling for access to the EPC between the UE and 3GPP AAA server, if applicable, as described in 3GPP TS 24.302 [8U] prior to perform the procedure to obtain a local IP address; a) the UE establishes an IP-CAN bearer for SIP signalling as follows: 1) if the UE attaches to the EPC via S2b using untrusted WLAN IP access: A) the UE shall obtain a local IP address using the WLAN IP access; B) if the UE does not support procedures for access to the EPC via restrictive non-3GPP access network or unless the UE determines that the WLAN used is a restrictive non-3GPP access network, then the UE shall establish an IKEv2 security association and an IPsec ESP security association with ePDG as described in 3GPP TS 24.302 [8U]. If the UE supports the Fixed Access Broadband interworking, the UE shall apply the establishment of tunnel specified in 3GPP TS 24.139 [8X]; NOTE 2: UE can determine that the WLAN used is a restrictive non-3GPP access network if no IKEv2 response is received for the IKEv2 IKE_SA_INIT request, or using means out of scope of this specification. C) if the UE supports procedures for access to the EPC via restrictive non-3GPP access network, and if the UE determines that the WLAN used is a restrictive non-3GPP access network, then the UE may perform procedures for access to the EPC via restrictive non-3GPP access network as described in 3GPP TS 24.302 [8U], and may establish an IKEv2 security association and an IPsec ESP security association with ePDG via the firewall traversal tunnel; D) the IKEv2 security association and the IPsec ESP security association (tunnel) shall remain active throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the deregistration; and E) the UE may carry both signalling and media on an IPsec ESP security association; 2) if the UE attaches to the EPC via S2c using the WLAN IP access: A) the UE shall obtain a local IP address; B) the UE shall establish an IKEv2 security association and an IPsec ESP security association as described in 3GPP TS 24.302 [8U] and 3GPP TS 24.303 [8V]. If the UE supports the Fixed Access Broadband interworking, the UE shall apply the establishment of tunnel specified in 3GPP TS 24.139 [8X]; C) the IKEv2 security association and the IPsec ESP security association (tunnel) shall remain active throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the deregistration; and D) the UE may carry both signalling and media on an IPsec ESP security association. 3) if the UE attaches to the EPC via S2a using a trusted WLAN IP access: A) the IPv4 address and/or IPv6 prefix is allocated as specified in 3GPP TS 24.302 [8U]; and B) the UE IP address shall remain valid throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the deregistration; The UE can determine trust relationship of a non-3GPP IP access network as specified in 3GPP TS 24.302 [8U]; and b) the UE shall aquire a P-CSCF address(es). The methods for P-CSCF discovery are: I. Use DHCP mechanism II. Use DNS When using IPv4, the UE may request a DNS Server IPv4 address(es) via RFC 2132 [20F]. When using IPv6, the UE may request a DNS Server IPv6 address(es) via RFC 3315 [40] and RFC 3646 [56C]. III. Obtain the list of P-CSCF address(es) from the IMS management object IV. Obtain P-CSCF address(es) using signalling for access to the EPC via WLAN. If the UE attaches to the EPC via S2b using untrusted WLAN IP access, the UE shall request P-CSCF IPv4 address(es), P-CSCF IPv6 address(es) or both using the P_CSCF_IP4_ADDRESS attribute, the P_CSCF_IP6_ADDRESS attribute or both in the CFG_REQUEST configuration payload as described in 3GPP TS 24.302 [8U]. The network can provide the UE with the P-CSCF IPv4 address(es), P-CSCF IPv6 address(es) or both using the P_CSCF_IP4_ADDRESS attribute, the P_CSCF_IP6_ADDRESS attribute or both in the CFG_REPLY configuration payload as described in 3GPP TS 24.302 [8U]. If the UE receives multiple P-CSCF IPv4 or IPv6 addresses, the UE shall assume that the list is ordered top-down with the first P-CSCF address within the CFG_REPLY configuration payload as the P-CSCF address having the highest preference and the last P-CSCF address within the CFG_REPLY configuration payload as the P-CSCF address having the lowest preference. If the UE attaches to the EPC via S2a using trusted WLAN IP access using single-connection mode, the UE shall indicate request for P-CSCF IPv4 address(es), P-CSCF IPv6 address(es) or both within the PROTOCOL_CONFIGURATION_OPTIONS item of the message with SCM_REQUEST message type as described in 3GPP TS 24.302 [8U]. The network can provide the UE with the P-CSCF IPv4 address(es), P-CSCF IPv6 address(es) or both within the PROTOCOL_CONFIGURATION_OPTIONS item of the message with SCM_RESPONSE message type as described in 3GPP TS 24.302 [8U]. If the UE receives multiple P-CSCF IPv4 or IPv6 addresses, the UE shall assume that the list is ordered top-down with the first P-CSCF address within the PROTOCOL_CONFIGURATION_OPTIONS item as the P-CSCF address having the highest preference and the last P-CSCF address within the PROTOCOL_CONFIGURATION_OPTIONS item as the P-CSCF address having the lowest preference. If the UE attaches to the EPC via S2a using trusted WLAN IP access using multi-connection mode, the UE shall indicate request for P-CSCF IPv4 address(es), P-CSCF IPv6 address(es) or both within the Protocol Configuration Options information element of the PDN CONNECTIVITY REQUEST message as described in 3GPP TS 24.244 [8ZB]. The network can provide the UE with the P-CSCF IPv4 address(es), P-CSCF IPv6 address(es) or both within the Protocol Configuration Options information element of the PDN CONNECTIVITY ACCEPT message as described in 3GPP TS 24.244 [8ZB]. If the UE receives multiple P-CSCF IPv4 or IPv6 addresses, the UE shall assume that the list is ordered top-down with the first P-CSCF address within the Protocol Configuration Options information element as the P-CSCF address having the highest preference and the last P-CSCF address within the Protocol Configuration Options information element as the P-CSCF address having the lowest preference. The UE shall use method III to select a P-CSCF, if a P-CSCF is to be discovered in the home network and the WLAN, to which the UE is attached, is connected to a visited network. The UE can freely select method I, II, III or IV for P-CSCF discovery if: - the UE is in the home network; or - the WLAN, to which the UE is attached, is connected to a visited network and the P-CSCF is to be discovered in the visited network. If DHCP is used, the following procedures apply: Upon establishing an IP-CAN, the UE may use the Dynamic Host Configuration Protocol (DHCP) specified in RFC 2131 [40A] or Dynamic Host Configuration Protocol for IPv6 (DHCPv6) specified in RFC 3315 [40] to discover the P-CSCF. Prior to accessing the DHCP server, the UE will have obtained an IP address via means other than DHCP and DHCPv6. If the UE uses DHCP for P-CSCF discovery and the UE is unaware of the address of the DHCP server, the UE sends the DHCPINFORM using the limited broadcast IP address (i.e., 255.255.255.255) and UDP port 67. If the UE knows the IP address of the DHCP server, the UE shall send the DHCPINFORM to the DHCP server's unicast IP address and UDP port 67. The DHCP server sends the DHCPACK on the IP address specified in the Client IP Address field of the DHCPINFORM. The DHCP server can include, in the DHCPACK, the SIP Server DHCP Option specified in RFC 3361 [35A], which carries either a list of IPv4 address(es) of the P-CSCF(s) or a list of DNS fully qualified domain name(s) that can be mapped to one or more P-CSCF(s). If the UE uses DHCPv6 for P-CSCF discovery and the UE is unaware of the address of the DHCP Server, the UE shall send an Information Request using the IPv6 multicast address FF02::1:2 and the UDP port 547. If the UE knows the IP address of the DHCPv6 server, the UE shall send the Information Request message to the DHCPv6 server's IP address and UDP port 547. In the Information Request, the UE can request either one or both the SIP Servers Domain Name List option and the SIP Servers IPv6 Address List option specified in RFC 3319 [41]. The DHCP server sends the Reply to the IP address specified in the Information Request. The DHCP server can include in the Reply either one or both the SIP Servers Domain Name List option and the SIP Servers IPv6 Address List option, as requested by the UE. If the UE supports the optional configuration parameter "Access_Point_Name_Parameter_Reading_Rule", as defined in 3GPP TS 24.167 [8G] and has been configured with this parameter, then the UE shall use it to retrieve the access point name to use in the establishment of IP-CAN bearer. In case several P-CSCF's IP addresses or domain names are provided to the UE, the UE shall perform P-CSCF selection according to RFC 3361 [35A] or RFC 3319 [41]. The UE shall perform the procedure for the resolution of domain name according to RFC 3263 [27A]. If sufficient information for P-CSCF address selection is not available, selection of the P-CSCF address by the UE is implementation specific. When: - the UE obtains an IP-CAN bearer for SIP signalling by performing handover of the connection from another IP-CAN; - IP address of the UE is not changed during the handover; and - the UE already communicates with the IM CN subsystem via the connection with the other IP-CAN, e.g. the UE determines that its contact with host portion set to the UE IP address (or FQDN of the UE) associated with the connection with the other IP-CAN has been bound to a public user identity; the UE shall continue using the P-CSCF address(es) acquired in the other IP-CAN. The UE may support the policy on when a UE roaming in a VPLMN is allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS as specified in subclause L.2.1.1. If the UE roams in the EPS IP-CAN, has a session and the policy indicates "roaming in a VPLMN and having an ongoing session, is not allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS", the UE shall not handover the PDN connection providing access to IMS from EPS to EPC via WLAN. If the UE roams in the EPS IP-CAN, has a session and the policy indicates "roaming in a VPLMN and having an ongoing session, is allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS", the UE shall, if not prevented by other rules or policies, handover the PDN connection providing access to IMS from EPS to EPC via WLAN. If the UE roams in the EPS IP-CAN and the policy indicates "roaming in a VPLMN is not allowed to transfer the PDN connection providing access to IMS between EPC via WLAN and EPS, irrespective of if the UE is in a session or not", the UE shall not handover the PDN connection providing access to IMS from EPS to EPC via WLAN. The UE can re-establish a new PDN connection to another IP-CAN type in idle mode, e.g. due to UE domain preference. The UE may support the policy on when a UE is allowed to transfer a PDN connection providing access to IMS between EPC via WLAN and 5GS as specified in subclause U.2.1.1. If the UE is in a session and the policy indicates "is not allowed to transfer the PDN connection providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RAN" or if the UE is roaming when in a session and the policy indicates "a UE roaming in a VPLMN and having an ongoing IMS session, is not allowed to transfer the PDN connection providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RAN" the UE shall not handover the PDN connection providing access to IMS from 5GS to EPC via WLAN. If the UE is in a seesion in the EPS IP-CAN and the policy indicates "a UE having an ongoing IMS session, is allowed to transfer the PDN connection providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RAN" or the UE is roaming in an EPS IP-CAN and the policy indicates "a UE roaming in a VPLMN and having an ongoing IMS session, is allowed to transfer the PDN connection providing access to IMS between EPC via non-3GPP access and 5GCN via NG-RAN" the UE shall, if not prevented by other rules or policies, handover the PDN connection providing access to IMS from 5GS to EPC via WLAN. If the UE is in a 5GS IP-CAN and the policy indicates "a UE is not allowed to transfer a PDN connection providing access to IMS, if any, between EPC via non-3GPP access and 5GCN via NG-RAN, irrespective of if the UE has an ongoing IMS session or not" or the UE is roaming in a 5GS IP-CAN and the policy indicates "a UE roaming in a VPLMN is not allowed to transfer a PDN connection providing access to IMS, if any, between EPC via non-3GPP access and 5GCN via NG-RAN, irrespective of if the UE has an ongoing IMS session or not" the UE shall not handover the PDU session providing access to IMS from 5GS to EPC via WLAN. R.2.2.1A Modification of an IP-CAN used for SIP signalling Not applicable. R.2.2.1B Re-establishment of the IP-CAN used for SIP signalling If the UE registered a public user identity with an IP address allocated for the APN of the IP-CAN bearer for SIP signalling, the IP-CAN bearer for SIP signalling is deactivated as result of signalling from the network, and: i) the signalling from the network results in requiring the UE to initiate activation of the IP-CAN bearer for SIP signalling; or ii) the UE needs to continue having a public user identity registered with an IP address allocated for the APN; and the UE is allowed to activate the IP-CAN bearer for SIP signalling, the UE shall: A) if the non-access stratum is performing activation of the IP-CAN bearer for SIP signalling for the APN triggered as result of the signalling from the network, wait until the activation of the IP-CAN bearer for SIP signalling for the APN finishes; B) if the non-access stratum is not performing activation of the IP-CAN bearer for SIP signalling for the APN, perform the procedures in subclause R.2.2.1, bullet a); and C) if the IP-CAN bearer for SIP signalling is available: - perform the procedures in subclause R.2.2.1, bullet b); and - if a P-CSCF address was acquired, perform a new initial registration according to subclause 5.1.1.2. R.2.2.1C P-CSCF restoration procedure A UE supporting the P-CSCF restoration procedure performs one of the following procedures: A) if the UE used method IV for P-CSCF discovery, the UE has previously sent the "P-CSCF Re-selection support" PCO indicator (in trusted non-3GPP access network) or the P-CSCF_RESELECTION_SUPPORT IKEv2 attribute (in untrusted non-3GPP access network) during the PDN connection establishment, and the UE receives one or more P-CSCF address(es) during the TWAG initiated PDN connectivity modification procedure (in trusted non-3GPP access network) or the ePDG initiated modification (in untrusted non-3GPP access network), then the UE shall acquire a P-CSCF address from the one or more P-CSCF addresse(s). If more than one P-CSCF addresses of the same IP address type are included, then the UE shall assume that the more than one P-CSCF addresses of the same IP address type are prioritised with the first P-CSCF address within the Protocol Configuration Options information element or within the IKEv2 configuration payload as the P-CSCF address having the highest priority; and B) if the UE uses RFC 6223 [143] as part of P-CSCF restoration procedures, and the P-CSCF fails to respond to keep-alive requests, then the UE shall acquire a different P-CSCF address using any of the methods described in the subclause R.2.2.1. When the UE has acquired the P-CSCF address, the UE shall perform an initial registration as specified in subclause 5.1. NOTE: For UEs using procedure A described above, the network ensures that P-CSCF address(es) received in the Protocol Configuration Options information element during TWAG initiated PDN connectivity modification procedure (in trusted non-3GPP access network), and P-CSCF address(es) received in the P-CSCF_IP6_ADDRESS attribute, the P-CSCF_IP4_ADDRESS attribute or both during ePDG initiated modification (in untrusted non-3GPP access network) are sent only during P-CSCF restoration procedures as defined in subclause 5 of 3GPP TS 23.380 [7D]. R.2.2.2 Void R.2.2.3 IP-CAN support of DHCP based P-CSCF discovery When using WLAN IP access via S2c to access the EPC, the Home Agent (HA) in case of Mobile IP with reverse tunneling, can forward the packet to one or more local DHCP servers, or relay the packet to a specific DHCP server. The HA in case of Mobile IP with reverse tunnelling, does not forward the DHCPINFORM (or Information-Request) to any UE. NOTE 1: For forwarding the DHCPINFORM or Information-Request, the HA in case of Mobile IP with reverse tunnelling, does not change the destination IP address of the packet. NOTE 2: For relaying the DHCPINFORM or Information-Request, the HA in case of Mobile IP with reverse tunnelling inserts a DHCP server's IP address in the destination IP address field of the packet. R.2.2.4 Void R.2.2.5 Tunnel procedures for media R.2.2.5.1 General requirements The UE can establish media streams that belong to different SIP sessions on the same tunnel when accessing the EPC via untrusted WLAN. During establishment of a session, the UE establishes data streams(s) for media related to the session. When using untrusted WLAN IP access via S2c to access the EPC, such data stream(s) may result in activation of additional IPsec ESP security associations (tunnels). If the capabilities of the originating UE, or operator policy at the ePDG prevents the originating UE from establishment of additional IPsec ESP security associations (tunnels) according to the media grouping attributes given by the P-CSCF in accordance with RFC 3524 [54], the UE will not establish such grouping of media streams. Instead, the originating UE shall negotiate media parameters for the session according to RFC 3264 [27B]. If the capabilities of the terminating UE or operator policy at the ePDG prevents the originating UE from establishment of additional IPsec ESP security associations (tunnels) according to the media grouping attributes given by the P-CSCF in accordance with RFC 3524 [54], the UE will not establish such grouping of media streams. Instead, the terminating UE shall handle such SDP offers in accordance with RFC 3388 [53]. The UE can receive a media authorization token in the P-Media-Authorization header field from the P-CSCF according to RFC 3313 [31]. If a media authorization token is received in the P-Media-Authorization header field when a SIP session is initiated, the UE shall reuse the existing tunnel and ignore the media authorization token. R.2.2.5.1A Modification of tunnel for media by the UE The tunnel modification procedure for the UE shall follow the procedures specified in 3GPP TS 24.302 [8U]. If the UE supports the Fixed Access Broadband interworking, the modification of tunnel specified in 3GPP TS 24.139 [8X] shall be applied. R.2.2.5.1B Modification of tunnel for media by the network The UE shall follow the procedure specified in 3GPP TS 24.302 [8U] for the modification of tunnel. If the UE supports the Fixed Access Broadband interworking, the modification of tunnel specified in 3GPP TS 24.139 [8X] shall be applied. If the UE attaches to the EPC via S2b using untrusted WLAN IP access, and IKEv2 multiple bearer PDN connectivity is used in the PDN connection according to 3GPP TS 24.302 [8U], then: 1) if: A) an additional IPSec ESP tunnel is established according to 3GPP TS 24.302 [8U]; or B) an IPSec ESP tunnel is modified according to 3GPP TS 24.302 [8U]; the UE shall, based on the information contained in the TFT Notify payload, correlate the media IPSec ESP tunnel with SDP media descriptions of a currently ongoing SIP session establishment or SIP session modification. R.2.2.5.1C Deactivation of tunnel for media Not applicable. R.2.2.5.2 Special requirements applying to forked responses Since the UE is unable to perform bearer modification, forked responses place no special requirements on the UE. R.2.2.5.3 Unsuccessful situations Not applicable. R.2.2.6 Emergency service R.2.2.6.1 General In this release of the specification, a WLAN, conforming to the requirements in this annex, defines emergency bearers. Emergency session is supported over the WLAN access if the UE has failed or has not been able to use 3GPP access to set up an emergency session as described in 3GPP TS 23.167 [4B] annex J. IMS emergency session is also supported for UEs with unavailable IMSI (i.e. a UE without USIM) or unauthenticated IMSI. Some jurisdictions allow emergency calls to be made when the UE does not contain an ISIM or USIM, or where the credentials are not accepted. When the UE is attached over a WLAN access and detects an emergency call attempt, if the UE supports the emerg-non3gpp timer defined in table 7.8.1, the UE shall start the emerg-non3gpp timer when starting a domain selection searching for a 3GPP access usable to establish an emergency call. The UE shall stop the timer when a 3GPP access supporting emergency call is found. When the emerg-non3gpp timer expires, the UE shall consider that it has failed to use 3GPP access to setup the emergency call and shall attempt to setup the emergency call over the available WLAN access. The UE may support being configured for the emerg-non3gpp timer using one or more of the following methods: a) the Timer_Emerg_non3gpp leaf of the EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the Timer_Emerg_non3gpp leaf of the EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and c) the Timer_Emerg_non3gpp leaf of 3GPP TS 24.167 [8G]. EPC procedures for emergency session using WLAN are defined for both trusted WLAN access via S2a, depending on the TWAN usage mode, and untrusted WLAN access via S2b to access EPC. When the IM CN subsystem is selected as the domain for the emergency call attempt, and the UE uses: - untrusted WLAN access via S2b, the UE determines that the EPC supports emergency bearer services by selecting or using an ePDG that has indicated its capability of support for emergency services, as specified in subclause 7.2.1A of 3GPP TS 24.302 [8U]; or - trusted WLAN access via S2a, the UE determines that the EPC, accessed in usage modes multi-connection mode or single-connection mode, supports emergency bearer services if the CONNECTION_MODE_CAPABILITY item in the EAP-Request/AKA'-Challenge message indicates support of emergency services, as specified in 3GPP TS 24.302 [8U]. When the IM CN subsystem is selected as the domain for the emergency call attempt, and the UE uses untrusted WLAN access via S2b, the UE determines whether it is currently attached to its home operator's network (e.g. HPLMN) or not (e.g. VPLMN) after it has determined that the core network supports emergency bearer services. When establishing an IMS emergency session using trusted WLAN access via S2a, the UE shall establish an IMS emergency session over trusted WLAN access depending on the usage mode used to access EPC. When using the usage mode single-connection mode, subclause 6.4.2.6.2A of 3GPP TS 24.302 [8U] applies. When using the usage mode multi-connection mode, subclause 6.4.2.6.3A of 3GPP TS 24.302 [8U] applies. The procedures for attaching to the EPC via S2a using a trusted WLAN IP access, as described in subclause R.2.2.1 of this specification apply accordingly. When establishing an IMS emergency session using untrusted WLAN access via S2b, the UE shall establish an IMS emergency session over untrusted non-3GPP access as specified in 3GPP TS 24.302 [8U]. The procedures for attaching to the EPC via S2b using untrusted WLAN IP access, as described in subclause R.2.2.1 of this specification apply accordingly. If the ME is equipped with a UICC, in order to find out whether the UE is attached to the home PLMN or to the visited PLMN, the UE shall compare the MCC and MNC values derived from its IMSI with the MCC and MNC of the PLMN the UE is attached to. If the MCC and MNC of the PLMN the UE is attached to do not match with the MCC and MNC derived from the IMSI, then for the purposes of emergency calls in the IM CN subsystem the UE shall consider to be attached to a VPLMN. If the ME is not equipped with a UICC, the procedure to find d out whether the UE is attached to the home PLMN or to the visited PLMN for the purpose of emergency calls in the IM CN subsystem, is implementation specific. NOTE 1: The UE verifies if a detected emergency number is still present in the Extended Local Emergency Number List applicable to the PLMN it is currently using. It is possible for the number to no longer be present in the Extended Local Emergency Number List if: - the PLMN attached to relies on the Local Emergency Number List for deriving a URN; or - the previously received Extended Emergency Number List Validity field indicated "Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received". If the UE detected an emergency number, the UE subsequently uses a different PLMN than the PLMN from which the UE received the last Extended Local Emergency Number List: NOTE 2: The UE has either attached to or authenticated (e.g. due to EAP-3GPP-LimitedService based access authentication, see 3GPP TS 24.302 [8U]) with a PLMN via WLAN prior to detecting the emergency number or because of detecting the emergency number. - the dialled number is not stored in the ME, in the USIM and in the Local Emergency Number List; then: a) if the UE supports provision and handling of local emergency numbers as defined in 3GPP TS 24.302 [8U], the UE has received the local emergency numbers using any of the methods defined in subclause 4.7 in 3GPP TS 24.302 [8U], the dialled number matches a received local emergency number, then the UE derives a URN as defined in 3GPP TS 24.302 [8U] or using the procedures in subclause R.2.2.6.1A, depending on the method used to provision the local emergency number; b) otherwise, the UE shall attempt UE procedures for SIP that relate to emergency using emergency service URN "urn:service:sos". If the dialled number is equal to a local emergency number stored in the Extended Local Emergency Number List (as defined in 3GPP TS 24.301 [8J]), then the UE shall recognize such a number as for an emergency call and: - if the dialled number is equal to an emergency number stored in the ME, or in the USIM, then the UE shall perform either procedures in the subclause R.2.2.6.1B or the procedures in subclause R.2.2.6.1A; and - if the dialled number in not equal to an emergency number stored in the ME, or in the USIM, then the UE shall perform procedures in the subclause R.2.2.6.1B. If the dialled number is not equal to a local emergency number stored in the Extended Local Emergency Number List (as defined in 3GPP TS 24.301 [8J]) and: - if the dialled number is equal to an emergency number stored in the ME, in the USIM or in the Local Emergency Number List (as defined in 3GPP TS 24.008 [8]), then the UE shall recognize such a number as for an emergency call and performs the procedures in subclause R.2.2.6.1A. Once IPsec tunnel setup is completed, the UE shall follow the procedures described in subclause R.2.2.1 of this specification for establishment of IP-CAN bearer and P-CSCF discovery accordingly. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.2A.1.1 and subclause 5.1.3.1, if: - the 380 (Alternate Service) response contains a Contact header field; - the value of the Contact header field is a service URN; and - the service URN has a top-level service type of "sos"; then the UE determines that "emergency service information is included" as described 3GPP TS 23.167 [4B]. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.3.1, if the 380 (Alternate Service) response does not contain a Contact header field with service URN that has a top-level service type of "sos", then the UE determines that "no emergency service information is included" as described 3GPP TS 23.167 [4B]. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.2A.1.1 and subclause 5.1.3.1, the UE shall proceed as follows: 1) if a 3GPP access network is available and the UE has not already attempted to use a 3GPP access network to set up an emergency session as described in 3GPP TS 23.167 [4B] annex J, when the UE selects a domain in accordance with the conventions and rules specified in 3GPP TS 22.101 [1A] and 3GPP TS 23.167 [4B], the UE shall attempt to select a domain of the 3GPP access network, and: - if the CS domain is selected, the UE behaviour is defined in subclause 7.1.2 of 3GPP TS 23.167 [4B] and in annex B, annex L or annex U; and - if the IM CN subsystem is selected, the UE shall apply the procedures in subclause 5.1.6 with the exception of selecting a domain for the emergency call attempt; In addition, when the UE determines that "it has not been able to use 3GPP access to set up an emergency session" in accordance with subclause J.1 of 3GPP TS 23.167 [4B], the UE shall apply the procedures in subclause 5.1.6 using WLAN, with the exception of selecting a domain for the emergency call attempt; and 2) if a 3GPP access network is not available, then the UE shall apply the procedures in subclause 5.1.6 using WLAN, with the exception of selecting a domain for the emergency call attempt. When the emergency session ends, the UE: 1) shall release the tunnel as described in 3GPP TS 24.302 [8U]; and 2) if EPC via WLAN is the preferred IP-CAN to access IM CN subsystem or if no 3GPP access is available: a) if the UE did not select the currently selected ePDG using procedures for selection of ePDG for non-emergency services, shall select an ePDG for non-emergency services as described in 3GPP TS 24.302 [8U]; b) if the UE does not have an IP-CAN bearer for non-emergency SIP signalling, shall follow the procedures described in subclause R.2.2.1 for establishment of an IP-CAN bearer for SIP signalling and P-CSCF discovery; and c) if the UE determines that its contact associated with the IP-CAN bearer for non-emergency SIP signalling is not bound to a public user identity, shall perform an initial registration as specified in subclause 5.1.1.2 using the IP-CAN bearer for SIP signalling. R.2.2.6.1A Type of emergency service derived from emergency service category value The type of emergency service for an emergency number is derived from the settings of the emergency service category value (bits 1 to 5 of the emergency service category value as specified in subclause 10.5.4.33 of 3GPP TS 24.008 [8]). Table R.2.2.6.1 below specifies mappings between a type of emergency service and an emergency service URN. The UE shall use the mapping to match an emergency service URN and a type of emergency service. If a dialled number is an emergency number but does not map to a type of emergency service the service URN shall be "urn:service:sos". Table R.2.2.6.1: Mapping between type of emergency service and emergency service URN Type of emergency service Emergency service URN Police urn:service:sos.police Ambulance urn:service:sos.ambulance Fire Brigade urn:service:sos.fire Marine Guard urn:service:sos.marine Mountain Rescue urn:service:sos.mountain NOTE 1: It is not possible for a UE to indicate more than one type of emergency service in an emergency service URN. If: - the UE considers itself in the country of the HPLMN; NOTE 2: It is out of scope of the present annex to define how the UE determines whether it considered itself in the country of the HPLMN. When the UE is in coverage of a 3GPP RAT, it can, for example, use the information derived from the available PLMN(s). In this case, the UE can match the MCC broadcasted on the BCCH of the 3GPP access against the UE's IMSI to determine if they belong to the same country, as defined in 3GPP TS 23.122 [4C]. If the UE is not in coverage of a 3GPP RAT, the UE can use other techniques, including user-provided location, for determining whether it is located in its home country or not. - multiple types of emergency services can be derived for a dialled number from the information configured on the USIM; and - no IP-CAN provided a local emergency number that matches the dialled number (see subclause 5.1.6.1); NOTE 3: If the Non-3GPP emergency number indicator within the Non-3GPP NW provided policies IE (see 3GPP TS 24.008 [8]) provided through registration procedures over 3GPP access is set to "use of non-3GPP emergency numbers permitted", the UE also considers WLAN provided local emergency numbers (see 3GPP TS 24.302 [8U], subclause 4.7). If the Non-3GPP NW provided policies IE provided through registration procedures over 3GPP access is set to "use of non-3GPP emergency numbers not permitted", the UE does not consider WLAN provided local emergency numbers. If the Non-3GPP NW provided policies IE is not provided through registration procedures over 3GPP access, the UE does not consider WLAN provided local emergency numbers. NOTE 4: A UE, only connected to a PLMN through non-3GPP access, considers the WLAN provided local emergency numbers if the applicable conditions in subclause 4.7 of 3GPP TS 24.302 [8U], are met. then the UE shall map any one of these types of emergency service to an emergency service URN as specified in table R.2.2.6.1. If the UE considers itself in the country of the HPLMN and an IP-CAN provided a local emergency number that matches the dialled number (see subclause 5.1.6.1), and if the UE: - can derive one or more types of emergency service from the information received from the IP-CAN for the dialled number and the UE cannot derive types of emergency service from the information configured on the USIM for the dialled number; or - derives identical types of emergency service from both the information received from the IP-CAN for the dialled number and from the information configured on the USIM for the dialled number; then the UE shall map any one of these emergency service types to an emergency service URN as specified in table R.2.2.6.1. NOTE 5: How the UE resolves clashes where an emergency number is associated with one or more different types of emergency service configured in the USIM and in information received from an IP-CAN, is implementation dependent. R.2.2.6.1B Type of emergency service derived from extended local emergency number list The Extended Local Emergency Number List (defined in 3GPP TS 24.301 [8J]) can contain sub-services of the associated emergency service URN for the detected emergency number. If: - the length of sub-services field is greater than "0", the UE shall construct the emergency service URN using "urn:service:sos" followed by adding a dot followed by the content of the sub-services field; and - the length of sub-services field is "0", the UE shall use the emergency service URN "urn:service:sos". EXAMPLE 1: For a detected number, if the sub-service is "gas", then the UE constructs "urn:service:sos.gas" as the associated emergency service URN. EXAMPLE 2: For a detected number, if no sub-service is provided, then the UE uses "urn:service:sos" as the associated emergency service URN. R.2.2.6.2 eCall type of emergency service The UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". R.2.2.6.3 Current location discovery during an emergency call The UE may support the current location discovery during an emergency call specified in subclause 5.1.6.8.2, subclause 5.1.6.8.3, subclause 5.1.6.8.4, and subclause 5.1.6.12. R.2A Usage of SDP R.2A.0 General Not applicable. R.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network If the UE is attached to the EPC via S2b using untrusted WLAN IP access, and IKEv2 multiple bearer PDN connectivity is used in the PDN connection according to 3GPP TS 24.302 [8U], then: 1) if an additional IPSec ESP tunnel is established according to 3GPP TS 24.302 [8U] and the related SDP media description needs to be changed, the UE shall update the related SDP information by sending a new SDP offer within a SIP request, which is sent over the existing SIP dialog; and 2) if an IPSec ESP tunnel is modified according to 3GPP TS 24.302 [8U] and the related SDP media description need to be changed, the UE shall update the related SDP information by sending a new SDP offer within a SIP request, that is sent over the existing SIP dialog. NOTE: The UE can decide to indicate additional media streams as well as additional or different codecs in the SDP offer than those used in the already ongoing session. R.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE Not applicable. R.2A.3 Emergency service No additional procedures defined. R.3 Application usage of SIP R.3.1 Procedures at the UE R.3.1.0 Registration and authentication Editor's note: [WID: TURAN-CT, CR#4993]: Best usage of this FTT-IMS establishment is when the UE does not establish the IKEv2 security association which is an option not specified in subclause R.2.2.1. This requires further study. In order to reach the IM CN subsystem in some untrusted access networks, the UE may support: - address and/or port number conversions provided by a NA(P)T or NA(P)T-PT as described in annex F and annex K; or - the IP UE requested FTT-IMS establishment procedure specified in 3GPP TS 24.322 [8Y], which is applicable to direct access to an external IP network and not applicable to access through a PLMN. If a UE supports one or both of these capabilities then a UE may progressively try them to overcome failure to reach the IPM CN subsystem. Use of these capabilities shall have the following priority order: 1) UE does not use capability because reaching the IMS without an intervening NA(P)T, NA(P)T-PT, or tunnel is preferred. 2) UE may use address and/or port number conversions provided by a NA(P)T or NA(P)T-PT as described in either annex F or annex K. 3) UE may use the UE requested FTT-IMS establishment procedure specified in 3GPP TS 24.322 [8Y]. If the UE uses the UE-requested FTT-IMS establishment procedure specified in 3GPP TS 24.322 [8Y], the UE considers itself to: - be configured to send keep-alives; - be directly connected to an IP-CAN for which usage of NAT is defined; and - be behind a NAT. Optional procedures apply when the UE is supporting traversal of restrictive non-3GPP access network using STUN/TURN/ICE, as follows: a) the protection of SIP messages is provided by utilizing TLS as defined in 3GPP TS 33.203 [19]; b) the mechanisms specified in this annex shall only be applicable when the IP traffic to the IMS core does not traverse through the Evolved Packet Core (EPC); c) the UE shall establish the TLS connection to the P-CSCF on port 443 as defined in 3GPP TS 33.203 [19]. The UE shall use SIP digest with TLS for registration as specified in subclause 5.1. If the TLS connection is established successfully, the UE sends SIP signalling over the TLS connection to the P-CSCF; d) the UE shall support the keep-alive procedures described in RFC 6223 [143]; NOTE 1: If the UE is configured to use an HTTP proxy, the UE use the HTTP CONNECT method specified in RFC 2817 [220] to request the HTTP proxy to establish the TCP connection with the P-CSCF. Once the UE has received a positive reply from the proxy that the TCP connection has been established, the UE initiates the TLS handshake with the P-CSCF and establishes the TLS connection. e) the procedures described in subclause K.5.2 apply with the additional procedures described in the present subclause; f) when using the ICE procedures for traversal of restrictive non-3GPP access network, the UE shall support the ICE TCP as specified in RFC 6544 [131] and TURN TCP as specified in RFC 6062 [221]. g) if the UE is configured to use TURN over TCP on port 80, the UE shall establish the TCP connection to TURN server on port 80. If the UE is configured to use TURN over TLS on port 443, the UE shall establish the TLS connection to the TURN server on port 443 as defined in 3GPP TS 33.203 [19]. If the UE is configured to use both, the UE should prefer to use TURN over TCP on port 80 to avoid TLS overhead; h) if the connection is established successfully, the UE sends TURN control messages and media packets over the connection as defined in RFC 5766 [101]. NOTE 2: If the UE is configured to use an HTTP proxy, the UE use the HTTP CONNECT method specified in RFC 2817 [220] to request the HTTP proxy to establish the TCP connection with the TURN server. Then, if the UE is configured to use TURN over TLS on port 443 and the UE has received a positive reply from the proxy that the TCP connection has been established, the UE initiates the TLS handshake with the TURN server and establishes the TLS connection. The UE shall perform reregistration of a previously registered public user identity bound to any one of its contact addresses when changing to an IP-CAN for which usage is specified in annex B, annex L or annex U. The reregistration is performed using the new IP-CAN. NOTE 3: This document does not specify how the UE detects that the used IP-CAN has changed. The information that is forcing the reregistration is also used to generate the content for the P-Access-Network-Info header field. NOTE 4: The UE will send the reregistration irrespective of whether it has a SIP dialog or not. R.3.1.0a IMS_Registration_handling policy Not applicable. R.3.1.1 P-Access-Network-Info header field The UE shall always include the P-Access-Network-Info header field where indicated in subclause 5.1. R.3.1.1A Cellular-Network-Info header field The UE: 1) using the Evolved Packet Core (EPC) via Untrusted Wireless Local Access Network (WLAN) as IP-CAN to access the IM CN subsystem; and 2) supporting one or more cellular radio access technology (e.g. E-UTRAN); shall always include the Cellular-Network-Info header field specified in subclause 7.2.15, if the information is available, in every request or response in which the P-Access-Network-Info header field is present. NOTE: If the Cellular-Network-Info header field includes radio cell identity, then the Cellular-Network-Info header field populated by the UE that supports Multi-RAT Dual Connectivity with the EPC as described in 3GPP TS 37.340 [264] will contain the information about the radio cell identity of the Master RAN node that is serving the UE. R.3.1.2 Availability for calls Not applicable. R.3.1.2A Availability for SMS Void. R.3.1.3 Authorization header field When using SIP digest or SIP digest without TLS, the UE need not include an Authorization header field on sending a REGISTER request, as defined in subclause 5.1.1.2.1. NOTE: In case the Authorization header field is absent, the mechanism only supports that one public user identity is associated with only one private user identity. The public user identity is set so that it is possible to derive the private user identity from the public user identity by removing SIP URI scheme and the following parts of the SIP URI if present: port number, URI parameters, and To header field parameters. Therefore, the public user identity used for registration in this case cannot be shared across multiple UEs. Deployment scenarios that require public user identities to be shared across multiple UEs that don't include an private user identity in the initial REGISTER request can be supported as follows: - Assign each sharing UE a unique public user identity to be used for registration, - Assign the shared public user identitiess to the implicit registration set of the unique registering public user identities assigned to each sharing UE. R.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Not applicable. R.3.1.5 3GPP PS data off Not applicable. R.3.1.6 Transport mechanisms The transport mechansims as defined in subclause 4.2A are used with an additional requirement: a) If the UE has attached to the EPC via untrusted non-3gpp access and uses IPSec tunnel mode, in order to reduce the risk of UDP fragmentation, the UE shall decrement the IPSec tunnel overhead from the path MTU between the UE and the ePDG prior applying the transport selection for SIP requests as defined in RFC 3261 [26] subclause 18.1.1. NOTE: The method for discovering the maximum transmission unit for non-3GPP is implementation dependent and out of scope of 3GPP. R.3.1.7 RLOS Not applicable. R.3.2 Procedures at the P-CSCF R.3.2.0 Registration and authentication The P-CSCF may support UEs connected via restrictive non-3GPP access network. If the P-CSCF supports UEs connected via restrictive non-3GPP access network, when the P-CSCF receives a 200 (OK) response to a REGISTER request, if the contact address of REGISTER request contains an IP address assigned by the EFTF, and the UE's Via header field contains a "keep" header field parameter, then the P-CSCF shall add a value to the "keep" header field parameter of the UE's Via header field of the 200 (OK) response as defined in RFC 6223 [143]. Optional procedures apply when the P-CSCF is supporting traversal of restrictive non-3GPP access network using STUN/TURN/ICE, as follows: NOTE: In this scenario, the restrictive non-3GPP access network coexists with NA(P)T device located in the customer premises domain: a) the protection of SIP messages is provided by utilizing TLS as defined in 3GPP TS 33.203 [19]; b) the P-CSCF supporting these additional procedures should use SIP digest with TLS as defined in subclause 5 and the P-CSCF should inserts an IMS-ALG on the media plane; c) the mechanisms specified in this annex shall only be applicable when the IP traffic to the IMS core does not traverse through the Evolved Packet Core (EPC); d) the P-CSCF shall support the procedures defined in subclause 5.2, with the exception that the P-CSCF shall use SIP over TLS on port 443 as defined in 3GPP TS 33.203 [19]; e) when the UE has indicated support of the keep-alive mechanism defined in RFC 6223 [143], the P-CSCF shall indicate to the UE that it supports the keep-alive mechanism; and f) the IMS-ALG in the P-CSCF shall support ICE procedures, as defined in subclause 6.7.2.7. R.3.2.1 Determining network to which the originating user is attached If the P-CSCF is configured to handle emergency requests, in order to determine from which network the request was originated the P-CSCF shall, - if PCRF is used for this UE and 3GPP-User-Location-Info as specified in 3GPP TS 29.214 [13D] is available (see subclause 5.2.1), check the MCC and MNC received in 3GPP-User-Location-Info; and - if PCRF is not used for this UE or 3GPP-User-Location-Info is not available, check the MCC and MNC fields received in the Cellular-Network-Info header field in the emergency request. NOTE 1: The Cellular-Network-Info header field includes the MCC and the MNC of the cellular radio access network on which the UE most recently camped. The UE is not necessarily attached to a network via that cell or still camped on that cell. NOTE 2: The above check can be against more than one MNC code stored in the P-CSCF. R.3.2.2 Location information handling Void. R.3.2.3 Prohibited usage of PDN connection for emergency bearer services If the P-CSCF detects that a UE uses a PDN connection for emergency bearer services for a non-emergency REGISTER request, the P-CSCF shall reject that request by a 403 (Forbidden) response. NOTE: By assigning specific IP address ranges for a PDN connection for emergency bearer services and configuring those ranges in P-CSCF, the P-CSCF can detect based on the registered Contact address if UE uses an emergency PDN connection for initial registration. R.3.2.4 Void R.3.2.5 Void R.3.2.6 Resource sharing If PCC is supported for this access technology a P-CSCF supporting resource sharing shall apply the procedures in subclause L.3.2.6. NOTE: Resource sharing has in this version of the specification no meaning in the WLAN IP CAN. However, since transfer to EPS IP CAN is seamless from P-CSCF point of view the resource sharing options used over the Rx interface when the UE is attached to the WLAN IP CAN could be used when the UE moves to EPS IP CAN and since Rx requires the resource sharing options to be included in the initial AAR the resource sharing options need to be included also when the UE attached to the WLAN IP CAN initiates or receives a INVITE request. R.3.2.7 Priority sharing If PCC is supported for this access technology a P-CSCF supporting priority sharing and if according to operator policy shall apply the procedures in subclause L.3.2.7. R.3.2.8 RLOS Not applicable. R.3.3 Procedures at the S-CSCF R.3.3.1 Notification of AS about registration status Not applicable. R.3.3.2 RLOS Not applicable. R.4 3GPP specific encoding for SIP header field extensions R.4.1 Void R.5 Use of circuit-switched domain Void. Annex S (normative): IP-Connectivity Access Network specific concepts when using DVB-RCS2 to access IM CN subsystem S.1 Scope The present annex defines IP-CAN specific requirements for a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is DVB-RCS2 satellite access network. DVB-RCS2 (Second Generation DVB Interactive Satellite System) is a term referring to the ETSI standard ETSI TS 101 454-1 [193], ETSI EN 301 545-2 [194], ETSI TS 101 545-3 [195] for 2nd generation DVB satellite based access network technology with a return channel for two-way communication. S.2 DVB-RCS2 aspects when connected to the IM CN subsystem S.2.1 Introduction A UE accessing the IM CN subsystem, and the IM CN subsystem itself, utilise the services provided by the DVB-RCS2 satellite access network to provide packet-mode communication between the UE and the IM CN subsystem. From the perspective of the UE, the necessary IP-CAN bearer for signalling is transparently available to the UE. The UE is not directly involved in requests for IP-CAN bearer(s) for media flow(s). The IM CN interacts with the PCRF in the DVB-RCS2 IP-CAN to establish IP-CAN bearer(s) for media flow(s), on behalf of the UE. S.2.2 Procedures at the UE S.2.2.1 Activation and P-CSCF discovery Prior to communication with the IM CN subsystem, the UE shall: a) establish a connection to a DVB-RCS2 RCST depending on local configuration; the RCST shall have completed the RCST commissioning and initialization procedures as described in ETSI TS 101 545-3 [195], and thus have achieved IP connectivity to the NCC of an SVN; b) obtain an IP address using the standard IETF protocols (e.g., DHCP or IPCP). The UE shall fix the obtained IP address throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the last deregistration; and c) acquire a P-CSCF address(es), according to one of the methods described in subclause 9.2.1; the method available to the UE is determined by the SVN to which the RCST is connected. S.2.2.1A Modification of IP-CAN bearer used for SIP signalling Not applicable. S.2.2.1B Re-establishment of IP-CAN bearer used for SIP signalling Not applicable. S.2.2.1C P-CSCF restoration procedure A UE supporting the P-CSCF restoration procedure uses the keep-alive procedures described in RFC 6223 [143]. If the P-CSCF fails to respond to keep-alive requests the UE shall acquire a different P-CSCF address using any of the methods described in the subclause S.2.2.1 and perform an initial registration as specified in subclause 5.1. S.2.2.2 Void S.2.2.3 Void S.2.2.4 Void S.2.2.5 Handling of the IP-CAN for media S.2.2.5.1 General requirements The UE does not directly request resources for media flow(s). S.2.2.5.1A Activation or modification of IP-CAN for media by the UE Not applicable. S.2.2.5.1B Activation or modification of IP-CAN for media by the network Not applicable. S.2.2.5.1C Deactivation of IP-CAN for media Not applicable. S.2.2.5.2 Special requirements applying to forked responses The UE does not directly request resources for media flow(s). As a result there are no special UE requirements applying to forked responses. S.2.2.5.3 Unsuccessful situations Not applicable. S.2.2.6 Emergency service S.2.2.6.1 General Emergency service is not supported when the IP-CAN is a DVB-RCS2 satellite access network. S.2.2.6.1A Type of emergency service derived from emergency service category value Not applicable. S.2.2.6.1B Type of emergency service derived from extended local emergency number list Not applicable. S.2.2.6.2 eCall type of emergency service The UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". S.2.2.6.3 Current location discovery during an emergency call Void. S.2A Usage of SDP S.2A.0 General Not applicable. S.2A.1 Impact on SDP offer / answer of activation or modification of satellite bearer for media by the network Not applicable. S.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE Not applicable. S.2A.3 Emergency service No additional procedures defined. S.3 Application usage of SIP S.3.1 Procedures at the UE S.3.1.0 Void S.3.1.0a IMS_Registration_handling policy Not applicable. S.3.1.1 P-Access-Network-Info header field The UE may, but need not, include the P-Access-Network-Info header field where indicated in subclause 5.1. S.3.1.1A Cellular-Network-Info header field Not applicable. S.3.1.2 Availability for calls Not applicable. S.3.1.2A Availability for SMS Void. S.3.1.3 Authorization header field Void S.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Not applicable. S.3.1.5 3GPP PS data off Not applicable. S.3.1.6 Transport mechanisms No additional requirements are defined. S.3.1.7 RLOS Not applicable. S.3.2 Procedures at the P-CSCF S.3.2.0 Registration and authentication Void. S.3.2.1 Determining network to which the originating user is attached In order to determine from which network the request was originated the P-CSCF shall check if the location information received in the network provided and/or UE provided "dvb-rcs2-node-id" parameter in the P-Access-Network-Info header field(s) indicates that the UE is connected to the same network as the P-CSCF or not. NOTE 1: If local policy does not require the insertion of P-Access-Network-Info header field in the P-CSCF even if it is missing in the received initial request, the P-CSCF can assume that the request is initiated by a UE in the same network as the P-CSCF. NOTE 2: If the location information in the network provided and UE provided "dvb-rcs2-node-id" parameters (in a request that includes two P-Access-Network-Info header fields) is contradictory, or the two P-Access-Network-Info header fields indicate different access types the P-CSCF ignores either the network provided or the UE provided information according to operator policy. S.3.2.2 Location information handling Upon receipt of an initial request for a dialog or standalone transaction or an unknown method, the P-CSCF based on local policy may include a P-Access-Network-Info header field. The value of the "dvb-rcs2-node-id" parameter shall be provided by the IP-CAN. S.3.2.3 Void S.3.2.4 Void S.3.2.5 Void S.3.2.6 Resource sharing Not applicable. S.3.2.7 Priority sharing Not applicable. S.3.2.8 RLOS Not applicable. S.3.3 Procedures at the S-CSCF S.3.3.1 Notification of AS about registration status Not applicable S.3.3.2 RLOS Not applicable. S.4 3GPP specific encoding for SIP header field extensions S.4.1 Void S.5 Use of circuit-switched domain There is no CS domain in this access technology. Annex T (Normative): Network policy requirements for the IM CN subsystem T.1 Scope This annex details areas where network policy is subject to additional requirements to those specified in the main part of this document. T.2 Application of network policy for the support of transcoding When providing transcoding functions at the P-CSCF, at the IBCF and at an AS, the set of codecs to be forwarded as the SDP offer to the remote user is subject to network policy. In order to give support to the codecs and media quality originally requested by the offerer, the network policy shall meet the following requirements. NOTE 1: RFC 3264 [27B] recommends to list codecs in priority order, so by adding network inserted codecs to the end of the codec list will give higher priority to previous codecs that might have been inserted by the originating UE. A) An intermediate entity should attempt to support the original request for codecs from the UE. B) An intermediate entity should only remove a codec from the codec list to meet policy requirements of the local access of the user. C) A modification (i.e. any combination of reordering, removal or addition) to the codec list should only be made, such that the resultant SDP offer / answer exchange results in media of equal or better end-to-end quality than if the modification had not been made, subject to policy restrictions of the access of the local user. NOTE 2: Transcoding between codecs of higher quality can provide better end-to-end quality than using a common codec of lower quality. D) A modification (i.e. any combination of reordering, removal or addition) to the codec list should only be made, such that the resultant SDP offer / answer exchange prefers solutions that do not use a transcoder rather than ones that do use transcoder, subject to meeting the policy restrictions in B) and meeting the best end-to-end media quality in C) above. E) Additions to the codec list that are provided by the network entity shall be supported by transcoding between at least one of the offered codecs contained in the SDP offer and the added codecs. F) An intermediate entity shall not insert a codec to the codec list if end-to-end media security mechanism is required for the related media. G) If an intermediate entity performs transcoding during an ongoing session and receives a SIP message containing a subsequent SDP offer including the codec that is currently in use on the incoming call leg, the entity should include the codec that is currently in use on the outgoing call leg when forwarding the SIP message. H) If an intermediate entity performs transcoding during an ongoing session and receives a SIP message containing a subsequent SDP offer not including the codec that is currently in use on the incoming call leg, the entity should include the codec that is currently in use on the outgoing call leg when forwarding the SIP message, subject to meeting the policy restrictions in E). I) If an intermediate entity does not perform transcoding during an ongoing session and receives a SIP message containing a subsequent SDP offer including the codec that is currently in use, the entity should not add any codecs in the subsequent SDP offer. Annex U (normative): IP-Connectivity Access Network specific concepts when using 5GS to access IM CN subsystem U.1 Scope The present annex defines IP-CAN specific requirements for a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is 5G System (5GS). The 5GS IP-CAN has a 5GS core network which can be supported by a NG-RAN. U.2 IP-CAN aspects when connected to the IM CN subsystem U.2.1 Introduction A UE accessing the IM CN subsystem, and the IM CN subsystem itself, utilise the services provided by 5GS to provide packet-mode communication between the UE and the IM CN subsystem. Requirements for the UE on the use of these packet-mode services are specified in this clause. When using the 5GS, each IP-CAN bearer is provided by a 5GS QoS flow. U.2.2 Procedures at the UE U.2.2.1 Establishment of IP-CAN bearer and P-CSCF discovery Prior to communication with the IM CN subsystem, the UE shall: a) if not registered for 5GS services, perform a registration procedure in 5GS as specified in 3GPP TS 24.501 [258]; b) ensure that a 5GS PDU session and a QoS flow used for SIP signalling of that PDU session is available. This 5GS QoS flow shall remain active throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the deregistration. As a result, the 5GS PDU session provides the UE with information that makes the UE able to construct an IPv4 or an IPv6 address; when establishing a 5GS PDU session, if a service which requires service continuity provided by SSC mode 1 as specified in 3GPP TS 23.501 [257], (e.g. IMS Multimedia Telephony Service as specified in 3GPP TS 24.173 [8H]), is to be used within that PDU session, the UE shall set SSC mode 1 for that PDU session; when establishing a 5GS PDU session with a QoS flow used for SIP signaling, the UE shall indicate to the network, by setting the IM CN Subsystem Signalling Flag in the extended Protocol Configuration Options information element specified in 3GPP TS 24.501 [258] in the PDU SESSION ESTABLISHMENT REQUEST message, that the request is for SIP signalling; c) use the QoS flow associated with the default QoS rule for SIP signalling. The UE may also use this 5GS QoS flow for Domain Name Server (DNS) and Dynamic Host Configuration Protocol (DHCP) signalling; and d) acquire a P-CSCF address(es). The methods for P-CSCF discovery are: I. When using IPv4, employ the DHCP RFC 2132 [20F], the DHCPv4 options for SIP servers RFC 3361 [35A], and RFC 3263 [27A] as described in subclause 9.2.1. When using IPv6, employ Dynamic Host Configuration Protocol for IPv6 (DHCPv6) RFC 3315 [40], the DHCPv6 options for SIP servers RFC 3319 [41] and DHCPv6 options for DNS RFC 3646 [56C] as described in subclause 9.2.1. II. Transfer P-CSCF address(es) within the 5GS PDU session establishement procedure. The UE shall indicate the request for a P-CSCF address to the network within the extended Protocol Configuration Options information element of the PDU SESSION ESTABLISHMENT REQUEST message. If the network provides the UE with a list of P-CSCF IPv4 or IPv6 addresses in the PDU SESSION ESTABLISHMENT ACCEPT message, the UE shall assume that the list is ordered top-down with the first P-CSCF address within the extended Protocol Configuration Options information element as the P-CSCF address having the highest preference and the last P-CSCF address within the extended Protocol Configuration Options information element as the P-CSCF address having the lowest preference. III. The UE selects a P-CSCF from the list (see 3GPP TS 31.103 [15B]) stored in the ISIM. IV. The UE selects a P-CSCF from the list in IMS management object. The UE shall use method IV to select a P-CSCF, if - a P-CSCF is to be discovered in the home network; - the UE is roaming; and - the IMS management object contains the P-CSCF list. The UE shall use method III to select the P-CSCF, if: - a P-CSCF is to be discovered in the home network; - the UE is roaming; - either the UE does not contain the IMS management object, or the UE contains the IMS management object but the IMS management object does not contain the P-CSCF list; and - the ISIM residing in the UICC supports the P-CSCF list. The UE can freely select method I or II for P-CSCF discovery, if: - the UE is in the home network; or - the UE is roaming and the P-CSCF is to be discovered in the visited network. The UE can select method IV, if: - the UE is in the home network; and - the IMS management object contains the P-CSCF list. In case method I is selected and several P-CSCF addresses or FQDNs are provided to the UE, the selection of P-CSCF address or FQDN shall be performed as indicated in RFC 3361 [35A] when using IPv4 or RFC 3319 [41] when using IPv6. If sufficient information for P-CSCF address selection is not available, selection of the P-CSCF address by the UE is implementation specific. NOTE: The UE decides whether the P-CSCF is to be discovered in the serving network or in the home network based on local configuration, e.g. whether the application on the UE is permitted to use local breakout. If the UE is designed to use I above, but receives P-CSCF address(es) according to II, then the UE shall either ignore the received address(es), or use the address(es) in accordance with II, and not proceed with the DHCP request according to I. If the UE is configured to use Option II above and detects that all P-CSCFs known by the UE have been used when the UE selects a different P-CSCF as a result of: - receiving 305 (Use Proxy) to the REGISTER request; - receiving 504 (Server Time-out); or - expiration of the timer F at the UE, then unless the PDU session is in use by other applications, the UE shall: 1) release the PDU session of the 5GS QoS flow that is used only for the transport of SIP signalling and that are not used for other non-IMS applications, but shall not release emergency PDU session; and 2) unless the UE decides the service is no longer needed, a) perform a new P-CSCF discovery procedure as described in subslause 9.2.1; and b) perform the procedures for initial registration as described in subclause 5.1.1.2. When using IPv4, the UE may request a DNS Server IPv4 address(es) via RFC 2132 [20F] or by the extended Protocol Configuration Options information element when establishing the PDU session according to 3GPP TS 24.501 [258]. When using IPv6, the UE may request a DNS Server IPv6 address(es) via RFC 3315 [40] and RFC 3646 [56C] or by the extended Protocol Configuration Options information element when establishing the PDU session according to 3GPP TS 24.501 [258]. When: - the UE obtains a 5GS QoS flow used for SIP signalling by performing handover of the connection from another IP-CAN; - IP address of the UE is not changed during the handover; and - the UE already communicates with the IM CN subsystem via the connection with the other IP-CAN, e.g. the UE determines that its contact with host portion set to the UE IP address (or FQDN of the UE) associated with the connection with the other IP-CAN has been bound to a public user identity; the UE shall continue using the P-CSCF address(es) acquired in the other IP-CAN. The UE may support the policy on whether a roaming UE when in a session is allowed to handover the PDN connection providing access to IMS between EPC via WLAN and 5GS, or is allowed to handover a PDU session providing access to IMS via non 3GPP access, the UE may support being configured with the policy on whether UE when in a session is allowed to transfer the PDN connection or PDU session providing access to IMS between EPC via WLAN using one or more of the following methods: a) the Allow_Handover_PDU_session_non-3GPP_and_NG-RAN node of EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the Allow_Handover_PDU_session_non-3GPP_and_NG-RANnode of EFIMSConfigData file described in 3GPP TS 31.103 [15B]; c) the Allow_Handover_PDU_session_non-3GPP_and_NG-RAN node of 3GPP TS 24.167 [8G]; d) the Allow_Handover_PDN_connection_non-3GPP_and_NG-RAN node of EFIMSConfigData file described in 3GPP TS 31.102 [15C]; e) the Allow_Handover_PDN_connection_non-3GPP_and_NG-RAN node of EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and f) the Allow_Handover_PDN_connection_non-3GPP_and_NG-RAN node of 3GPP TS 24.167 [8G]. If the UE is configured with both the Allow_Handover_PDU_session_non-3GPP_and_NG-RAN node of 3GPP TS 24.167 [8G] and the Allow_Handover_PDU_session_non-3GPP_and_NG-RAN node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the Allow_Handover_PDU_session_non-3GPP_and_NG-RAN node of the EFIMSConfigData file shall take precedence. If the UE is configured with both the Allow_Handover_PDN_connection_non-3GPP_and_NG-RAN node of 3GPP TS 24.167 [8G] and the Allow_Handover_PDN_connection_non-3GPP_and_NG-RAN node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the Allow_Handover_PDN_connection_non-3GPP_and_NG-RAN node of the EFIMSConfigData file shall take precedence. NOTE 5: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [15B]. U.2.2.1A Modification of the PDU session of the 5GS QoS flow used for SIP signalling The UE shall not modify the 5GS QoS flow from being used exclusively for SIP signalling. When a 5GS QoS flow used for SIP signalling is established, the UE shall not set the IM CN Subsystem Signalling Flag in the extended Protocol Configuration Options information element specified in 3GPP TS 24.501 [258] of any subsequent PDU SESSION MODIFICATION REQUEST message for that DNN. The UE shall ignore the IM CN Subsystem Signalling Flag if received from the network in the extended Protocol Configuration Options information element. After the establishment of a 5GS QoS flow used for SIP signalling, the UE shall not indicate the request for a P-CSCF address to the network within the extended Protocol Configuration Options information element of any subsequent PDU SESSION MODIFICATION REQUEST message for that DNN. The UE shall ignore P-CSCF address(es) if received from the network in the extended Protocol Configuration Options information element of a PDU SESSION MODIFICATION COMMAND message which is triggered by a PDU SESSION MODIFICATION REQUEST message. U.2.2.1B Re-establishment of the PDU session with the 5GS QoS flow used for SIP signalling If the UE registered a public user identity with an IP address allocated for the DNN of the PDU session with the 5GS QoS flow used for SIP signalling, the PDU session with the 5GS QoS flow used for SIP signalling is deactivated as result of signalling from the network and: i) if the UE is required to perform an initial registration according to subclause U.3.1.2; ii) if the signalling from the network results in requiring the UE to initiate activation of the PDU session of the 5GS QoS flow used for SIP signalling; or iii) if the UE needs to continue having a public user identity registered with an IP address allocated for the DNN; the UE shall: A) if the non-access stratum is performing the UE requested PDU session establishment procedure for the DNN triggered as result of the signalling from the network, wait until the UE requested PDU session establishment procedure for the DNN finish; and B) perform the procedures in subclause U.2.2.1, bullets a), b) and c). If none of the bullets i), ii) and iii) of this subclause evaluate to true, or the procedures in bullet B) of this subclause were unable to ensure that the 5GS QoS flow used for SIP signalling is available or were unable to acquire any P-CSCF address(es): 1) if the SIP signalling was carried over a 5GS QoS flow not associated with the default QoS rule, the UE shall release all resources established as a result of SIP signalling by sending to the network either: a) a PDU SESSION MODIFICATION REQUEST message, if there are 5GS QoS flows of this PDU session that are not related SIP sessions; or b) a PDU SESSION RELEASE REQUEST message if all the 5GS QoS flows of this PDU session are related to SIP sessions. If the 5GS QoS flow associated with default QoS rule used for SIP signalling was deactivated as described at the start of this subclause, and the procedures in bullet B) of this subclause ensured that the 5GS QoS flow used for SIP signalling is available and acquired the P-CSCF address(es), the UE shall perform a new initial registration according to subclause 5.1.1.2. U.2.2.1C P-CSCF restoration procedure A UE supporting the P-CSCF restoration procedure performs one of the following procedures: A if the UE used method II for P-CSCF discovery and if the UE receives one or more P-CSCF address(es) in the extended Protocol Configuration Options information element of a PDU SESSION MODIFICATION COMMAND message and the one or more P-CSCF addresse(s) do not include the address of the currently used P-CSCF, then the UE shall acquire a different P-CSCF address from the one or more P-CSCF addresse(s) in the PDU SESSION MODIFICATION COMMAND message. If more than one P-CSCF address with the same container identifier (i.e. "P-CSCF IPv6 Address" or "P-CSCF IPv4 Address") are included, then the UE shall assume that the more than one P-CSCF addresses with the same container identifier are prioritised with the first P-CSCF address with the same container identifier within the Protocol Configuration Options information element as the P-CSCF address with the highest priority. If the UE used method II for P-CSCF discovery and if the UE has previously sent the "P-CSCF Re-selection support" PCO indicator at PDU session creation and if the UE receives one or more P-CSCF address(es) in the extended Protocol Configuration Options information element of a PDU SESSION MODIFICATION COMMAND message, then the UE shall acquire a P-CSCF address from the one or more P-CSCF addresse(s) in the PDU SESSION MODIFICATION COMMAND message. If more than one P-CSCF address with the same container identifier (i.e. "P-CSCF IPv6 Address" or "P-CSCF IPv4 Address") are included, then the UE shall assume that the more than one P-CSCF addresses with the same container identifier are prioritised with the first P-CSCF address with the same container identifier within the Protocol Configuration Options information element as the P-CSCF address with the highest priority; B if the UE uses RFC 6223 [143] as part of P-CSCF restoration procedures, and if the P-CSCF fails to respond to a keep-alive request, then the UE shall acquire a different P-CSCF address using one of the methods I, III and IV for P-CSCF discovery described in the subclause U.2.2.1. If the UE has an ongoing session and acquired the new P-CSCF address by using procedure A described above, the UE may wait until the UE has detected that the ongoing session has ended before performing an initial registration as specified in subclause 5.1. In all other cases, when the UE has acquired the P-CSCF address, the UE not having an ongoing session shall perform an initial registration as specified in subclause 5.1. NOTE 1: For UEs using procedure A described above, the network ensures that P-CSCF address(es) in the extended Protocol Configuration Options information element of a PDU SESSION MODIFICATION COMMAND message is sent only during P-CSCF restoration procedures as defined in subclause 5 of 3GPP TS 23.380 [7D]. NOTE 2: The P-CSCF can be completely unreachable, so it is up to UE implementation to detect the end of an ongoing session, e.g. using media plane inactivity detection. Services depending on signalling such as CW and MT calls will not work during this time. U.2.2.2 Session management procedures The procedures for session management as described in 3GPP TS 24.501 [258] shall apply while the UE is connected to the IM CN subsystem. U.2.2.3 Mobility management procedures The procedures for mobility management as described in 3GPP TS 24.501 [258] shall apply while the UE is connected to the IM CN subsystem. U.2.2.4 Cell selection and lack of coverage The existing mechanisms and criteria for cell selection as described in 3GPP TS 38.304 [260] or 3GPP TS 36.304 [19B] shall apply while the UE is connected to the IM CN Subsystem. U.2.2.5 5GS QoS flow for media U.2.2.5.1 General requirements NOTE 1: During establishment of a session, the UE establishes data streams(s) for media related to the session. Either the UE or the network can request for resource allocations for media, but the establishment and modification of the 5GS QoS flow is controlled by the network as described in 3GPP TS 24.501 [258]. If the resource allocation is initiated by the UE, the UE starts reserving resources whenever it has sufficient information about the media streams, and used codecs available as specified in 3GPP TS 24.501 [258]. NOTE 2: If the resource reservation requests are initiated by the network, then the establishment of 5GS QoS flow for media is initiated by the network after the P-CSCF has authorised the respective 5GS QoS flows and provided the QoS requirements to the PCF. U.2.2.5.1A Activation or modification of QoS flows for media by the UE If the UE is configured not to initiate resource allocation for media according to 3GPP TS 24.167 [8G], then the UE shall refrain from requesting additional 5GS QoS flow(s) for media until the UE considers that the network did not initiate resource allocation for the media. U.2.2.5.1B Activation or modification of QoS flows for media by the network If the UE receives an activation request from the network for a 5GS QoS flow for media which is associated with the 5GS QoS flow used for signalling, the UE shall correlate the media 5GS QoS flow with a currently ongoing SIP session establishment or SIP session modification. If the UE receives a modification request from the network for a 5GS QoS flow that is used for one or more media streams in an ongoing SIP session, the UE shall: 1) modify the related PDU session context in accordance with the request received from the network. U.2.2.5.1C Deactivation of a QoS flow for media When a data stream for media related to a session is released, if the 5GS QoS flow transporting the data stream is no longer needed and allocation of the 5GS QoS flow was requested by the UE, then the UE releases the 5GS QoS flow. NOTE: The 5GS QoS flow can be needed e.g. for other data streams of a session or for other applications in the UE. U.2.2.5.1D Default QoS flow usage restriction policy The default QoS flow usage restriction policy consists of zero or more default QoS flow usage restriction policy parts. The default QoS flow usage restriction policy part consists of a mandatory media type condition and an optional ICSI condition. The default QoS flow usage restriction policy does not apply to UE detected emergency calls. Sending media is restricted according to the default QoS flow usage restriction policy, if sending media is restricted according to at least one default QoS flow usage restriction policy part of the default QoS flow usage restriction policy or if the UE is roaming. Sending media is restricted according to the default QoS flow usage restriction policy part if: 1) the media is to be sent for a media stream negotiated in a session offered or established by SIP signalling; 2) the media stream is of a media type indicated in the media type condition of the QoS flow usage restriction policy part; 3) the following is true: a) the default QoS flow usage restriction policy part does not have the ICSI condition; or b) the session is offered or established by SIP signalling related to an IMS communication service identified in the ICSI condition of the default QoS flow usage restriction policy part; and 4) the media is to be sent via the default QoS flow of the PDU session for SIP signalling. The UE may support the default QoS flow usage restriction policy. If the UE supports the default QoS flow usage restriction policy: 1) the UE shall not send media restricted according to the default QoS flow usage restriction policy; and 2) the UE may support being configured with the default QoS flow usage restriction policy using one or more of the following methods: a) the Default_QoS_Flow_usage_restriction_policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the Default_QoS_Flow_usage_restriction_policy node of the EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and c) the Default_QoS_Flow_usage_restriction_policy node of 3GPP TS 24.167 [8G]. If the UE is configured with both the Default_QoS_Flow_usage_restriction_policy node of 3GPP TS 24.167 [8G] and the Default_QoS_Flow_usage_restriction_policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the Default_QoS_Flow_usage_restriction_policy node of the EFIMSConfigData file shall take precedence. NOTE: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [15B]. U.2.2.5.2 Special requirements applying to forked responses NOTE 1: The procedures in this subclause only apply when the UE requests activation and modification of 5GS QoS flows for media . In the case where the network activates and modifies the 5GS QoS flows for media the network takes care of the handling of 5GS QoS flows in the case of forking. Since the UE does not know that forking has occurred until a second, provisional response arrives, the UE requests resource allocation as required by the initial response received. If a subsequent provisional response is received, different alternative actions may be performed depending on the requirements in the SDP answer: 1) The resource requirements of the subsequent SDP can be accommodated by the existing resources requested. The UE performs no further resource requests. 2) The subsequent SDP introduces different QoS requirements or additional IP flows. The UE requests further resource allocation according to subclause U.2.2.5.1. 3) The subsequent SDP introduces one or more additional IP flows. The UE requests further resource allocation according to subclause U.2.2.5.1. NOTE 2: When several forked responses are received, the resources requested by the UE are the "logical OR" of the resources indicated in the multiple responses to avoid allocation of unnecessary resources. The UE does not request more resources than proposed in the original INVITE request. When a final answer is received for one of the early dialogs, the UE proceeds to set up the SIP session. The UE shall release all the unneeded IP-CAN resources. Therefore, upon the reception of the first final 200 (OK) response for the INVITE request (in addition to the procedures defined in RFC 3261 [26] subclause 13.2.2.4), the UE shall: 1) in case resources were established or modified as a consequence of the INVITE request and forked provisional responses that are not related to the accepted 200 (OK) response, send release request to release the unneeded resources. U.2.2.5.3 Unsuccessful situations The UE can receive resource reservation related error codes in a PDU SESSION MODIFICATION REJECT as described in 3GPP TS 24.501 [258]. If the UE receives a resource reservation related error code, the UE shall either handle the resource reservation failure as described in subclause 6.1.1 or retransmit the message up to three times. U.2.2.6 Emergency service U.2.2.6.1 General For the purposes of this document, an emergency PDU session is the equivalent of emergency bearers; i.e. the 5GS defines emergency bearers for the support of emergency calls. Emergency PDU session is defined for use in emergency calls in 5GS and core network support of emergency PDU session is indicated to the UE in NAS signalling. Where the UE recognises that a call request is an emergency call and the core network supports emergency PDU session, the UE shall use emergency PDU session for both signalling and media for emergency calls made using the IM CN subsystem. Some jurisdictions allow emergency calls to be made when the UE does not contain an UICC, or where the credentials are not accepted. Additionally, where the UE is in state 5GMM-REGISTERED.LIMITED-SERVICE or 5GMM-REGISTERED.PLMN-SEARCH, a normal registration in 5GS has been attempted but it can also be assumed that a registration in the IM CN subsystem will also fail. In such cases, subject to the lower layers indicating that the network does support emergency bearer services in limited service state (see 3GPP TS 36.331 [19F] or 3GPP TS 38.331 [19G]), the procedures for emergency calls without registration can be applied, as defined in subclause 5.1.6.8.2. If the 5GS primary authentication procedure has already succeeded during the latest normal or emergency registration procedure in 5GS, the UE shall perform an initial emergency registration, as described in subclause 5.1.6.2 before attempting an emergency call as described in subclause 5.1.6.8.3. NOTE 1: The UE can determine that 5GS primary authentication procedure has succeeded during the emergency registration procedure in 5GS when a non-null integrity protection algorithm (i.e. other than 5G-IA0 algorithm) is received in the NAS signalling SECURITY MODE COMMAND message. To perform emergency registration, the UE shall request to establish an emergency PDU session as described in 3GPP TS 24.501 [258]. The procedures for PDU session establishment and P-CSCF discovery, as described in subclause U.2.2.1 of this specification apply accordingly. In the present document, "EMS is Y" as described in 3GPP TS 23.167 [4B] refers to one of the following conditions: a) if the UE is in an NR cell connected to 5GCN, the network indicates in the REGISTRATION ACCEPT message that EMC is set to either "Emergency services supported in NR connected to 5GCN only" or "Emergency services supported in NR connected to 5GCN and E-UTRA connected to 5GCN" as described in 3GPP TS 24.501 [258]; or b) if the UE is in an E-UTRA cell connected to 5GCN, the network indicates in the REGISTRATION ACCEPT message that EMC is set to either "Emergency services supported in E-UTRA connected to 5GCN only" or "Emergency services supported in NR connected to 5GCN and E-UTRA connected to 5GCN" as described in 3GPP TS 24.501 [258]. In the present document, "EMS is N" as described in 3GPP TS 23.167 [4B] refers to one of the following conditions: a) if the UE is in an NR cell connected to 5GCN, the network indicates in the REGISTRATION ACCEPT message that EMC is set to either "Emergency services not supported" or "Emergency services supported in E-UTRA connected to 5GCN only" as described in 3GPP TS 24.501 [258]; or b) if the UE is in an E-UTRA cell connected to 5GCN, the network indicates in the REGISTRATION ACCEPT message that EMC is set to either "Emergency services not supported" or "Emergency services supported in NR connected to 5GCN only" as described in 3GPP TS 24.501 [258]. In the present document, "ESFB is Y" as described in 3GPP TS 23.167 [4B] refers to one of the following conditions: a) if the UE is in an NR cell connected to 5GCN, the network indicates in the REGISTRATION ACCEPT message that EMF is set to either "Emergency service fallback supported in NR connected to 5GCN only" or "Emergency service fallback supported in NR connected to 5GCN and E-UTRA connected to 5GCN" as described in 3GPP TS 24.501 [258]; or b) if the UE is in an E-UTRA cell connected to 5GCN, the network indicates in the REGISTRATION ACCEPT message that EMF is set to either "Emergency service fallback supported in E-UTRA connected to 5GCN only" or "Emergency service fallback supported in NR connected to 5GCN and E-UTRA connected to 5GCN" as described in 3GPP TS 24.501 [258]. In the present document, "ESFB is N" as described in 3GPP TS 23.167 [4B] refers to one of the following conditions: a) if the UE is in an NR cell connected to 5GCN, the network indicates in the REGISTRATION ACCEPT message that EMF is set to either "Emergency service fallback not supported" or "Emergency service fallback supported in E-UTRA connected to 5GCN only" as described in 3GPP TS 24.501 [258]; or b) if the UE is in an E-UTRA cell connected to 5GCN, the network indicates in the REGISTRATION ACCEPT message that EMF is set to either "Emergency service fallback not supported" or "Emergency service fallback supported in NR connected to 5GCN only" as described in 3GPP TS 24.501 [258]. Emergency services fallback is defined to direct or redirect the UE towards either E-UTRA connected to 5GCN or EPS and support of emergency service fallback is indicated to the UE in NAS signalling. In order to find out whether the UE is attached to the home PLMN or to a visited PLMN, the UE shall compare the MCC and MNC values derived from its IMSI with the MCC and MNC of the PLMN the UE is attached to. If the MCC and MNC of the PLMN the UE is attached to do not match with the MCC and MNC derived from the IMSI, then for the purpose of emergency calls in the IM CN subsystem the UE shall consider to be attached to a VPLMN. NOTE 2: In this respect an equivalent HPLMN, as defined in 3GPP TS 23.122 [4C] will be considered as a visited network. If the UE selected an entry of the "list of subscriber data" in the SNPN access mode as specified in 3GPP TS 23.122 [4C], in order to find out whether the UE is attached to a subscribed SNPN or to a non-subscribed SNPN , the UE shall compare the SNPN identity of the selected entry of the "list of subscriber data" with the SNPN identity of the SNPN the UE is attached to. If the SNPN identity of the SNPN the UE is attached to does not match the SNPN identity of the selected entry of the "list of subscriber data", then for the purpose of emergency calls in the IM CN subsystem the UE shall consider to be attached to a non-subscribed SNPN. If the UE selected the PLMN subscription in the SNPN access mode as specified in 3GPP TS 23.122 [4C], then for the purpose of emergency calls in the IM CN subsystem the UE shall consider to be attached to a non-subscribed SNPN. If the dialled number is equal to a local emergency number stored in the Extended Local Emergency Number List (as defined in 3GPP TS 24.301 [8J]), then the UE shall recognize such a number as for an emergency call and: - if the dialled number is equal to an emergency number stored in the ME, or in the USIM, then the UE shall perform either procedures in the subclause U.2.2.6.1B or the procedures in subclause U.2.2.6.1A; and - if the dialled number in not equal to an emergency number stored in the ME, or in the USIM, then the UE shall perform procedures in the subclause U.2.2.6.1B. If the dialled number is not equal to a local emergency number stored in the Extended Local Emergency Number List (as defined in 3GPP TS 24.301 [8J]) and: - if the dialled number is equal to an emergency number stored in the ME, in the USIM or in the Local Emergency Number List (as defined in 3GPP TS24.008 [8]), then the UE shall recognize such a number as for an emergency call and performs the procedures in subclause U.2.2.6.1A. NOTE 3: The UE verifies if a detected emergency number is still present in the Extended Local Emergency Number List after registering to a different PLMN. It is possible for the number to no longer be present in the Extended Local Emergency Number List if: - the PLMN attached to relies on the Local Emergency Number List for deriving a URN; or - the previously received Extended Emergency Number List Validity field indicated "Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received". If the UE detected an emergency number, the UE subsequently performs a registration procedure or an emergency registration procedure with a different PLMN than the PLMN from which the UE received the last Extended Local Emergency Number List, the dialled number is not stored in the ME, in the USIM and in the Local Emergency Number List, and: - the REGISTRATION ACCEPT message received from the different PLMN contains the Extended Local Emergency Number List and the emergency number is present in the updated Extended Local Emergency Number List then the UE uses the updated Extended Local Emergency Number List when it performs the procedures in subclause U.2.2.6.1B; and - the REGISTRATION ACCEPT message received from the different PLMN contains no Extended Local Emergency Number List or the emergency number is no longer present in the updated Extended Local Emergency Number List then the UE shall attempt UE procedures for SIP that relate to emergency using emergency service URN "urn:service:sos". Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.2A.1.1 and subclause 5.1.3.1, if: - the 380 (Alternate Service) response contains a Contact header field; - the value of the Contact header field is a service URN; and - the service URN has a top-level service type of "sos"; then the UE determines that "emergency service information is included" as described 3GPP TS 23.167 [4B]. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.3.1 if the 380 (Alternate Service) response does not contain a Contact header field with service URN that has a top-level service type of "sos", then the UE determines that "no emergency service information is included" as described 3GPP TS 23.167 [4B]. If the "emergency service information is included" as described 3GPP TS 23.167 [4B]: 1) if the URN in the Contact header field matches an emergency service URN in table U.2.2.6.1, then the type of emergency service is the value corresponding to the matching entry in table U.2.2.6.1; and 2) if the URN in the Contact header field does not match any emergency service URN in table U.2.2.6.1, then the type of emergency service is not identified. NOTE 4: In bullet 2), the URN in the Contact header field either contains "no emergency subservice type" as described in 3GPP TS 23.167 [4B] triggering an emergency call, or contains an "emergency subservice type that does not map into an emergency service category for the CS domain" as described in 3GPP TS 23.167 [4B] triggering a normal call when the dialled number is available or triggering an emergency call when the dialled number is not available. The country specific URN is an example of a "emergency subservice type that does not map into an emergency service category for the CS domain". When the emergency registration expires, the UE should disconnect the emergency PDU session. Upon receiving a 3xx other than 380 (Alternative service), 4xx, 5xx or 6xx response to an INVITE request for a UE detectable emergency call, the UE shall perform domain selection as specified in 3GPP TS 23.167 [4B] annex H, to re-attempt the emergency call. U.2.2.6.1A Type of emergency service derived from emergency service category value The type of emergency service for an emergency number is derived from the settings of the emergency service category value (bits 1 to 5 of the emergency service category value as specified in subclause 10.5.4.33 of 3GPP TS 24.008 [8]). Table U.2.2.6.1 below specifies mappings between a type of emergency service and an emergency service URN. The UE shall use the mapping to match an emergency service URN and a type of emergency service. If a dialled number is an emergency number but does not map to a type of emergency service the service URN shall be "urn:service:sos". Table U.2.2.6.1: Mapping between type of emergency service and emergency service URN Type of emergency service Emergency service URN Police urn:service:sos.police Ambulance urn:service:sos.ambulance Fire Brigade urn:service:sos.fire Marine Guard urn:service:sos.marine Mountain Rescue urn:service:sos.mountain NOTE 1: It is not possible for a UE to indicate more than one type of emergency service in an emergency service URN. If an IP-CAN, capable of providing local emergency numbers, did not provide a local emergency number that matches the dialled number (see subclause 5.1.6.1) and multiple types of emergency service can be derived for a dialled number from the information configured on the UICC then: - if the UE is in the HPLMN or a subscribed SNPN, the UE shall map any one of these types of emergency service to an emergency service URN as specified in table U.2.2.6.1; and - if the UE is in a VPLMN or a non-subscribed SNPN, the UE shall select "urn:service:sos". If an IP-CAN, capable of providing local emergency numbers, provided a local emergency number that matches the dialled number (see subclause 5.1.6.1), and: - if the UE can derive one or more types of emergency service from the information received from the IP-CAN for the dialled number and the UE cannot derive types of emergency service from the information configured on the UICC for the dialled number; or - if the UE is able to derive identical types of emergency service from both the information received from the IP-CAN for the dialled number and from the information configured on the UICC for the dialled number, then the UE shall map any one of these emergency service types to an emergency service URN as specified in table U.2.2.6.1. NOTE 2: How the UE resolves clashes where an emergency number is associated with one or more different types of emergency service configured in the USIM and in information received from the core network, is implementation dependent. U.2.2.6.1B Type of emergency service derived from extended local emergency number list The Extended Local Emergency Number List (defined in 3GPP TS 24.301 [8J]) can contain sub-services of the associated emergency service URN for the detected emergency number. If: - the length of sub-services field is greater than "0", the UE shall construct the emergency service URN using "urn:service:sos" followed by adding a dot followed by the content of the sub-services field; and - the length of sub-services field is "0", the UE shall use the emergency service URN "urn:service:sos". EXAMPLE 1: For a detected number, if the sub-service is "gas", then the UE constructs "urn:service:sos.gas" as the associated emergency service URN. EXAMPLE 2: For a detected number, if no sub-service is provided, then the UE uses "urn:service:sos" as the associated emergency service URN. U.2.2.6.2 eCall type of emergency service If the IP-CAN indicates the eCall over IMS support defined in 3GPP TS 36.331 [19F] or in 3GPP TS 38.331 [19G], or the CS domain is not available to the UE, the UE can send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". If the IP-CAN does not indicate the eCall support indication and the CS domain is available to the UE, the UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". U.2.2.6.3 Current location discovery during an emergency call Void. U.2.2.6.4 Emergency services in single-registration mode NOTE: This subclause covers only the case where the UE selects the IM CN subsystem in accordance with the conventions and rules specified in 3GPP TS 23.167 [4B] and describes the IP-CAN specific procedure. It does not preclude the use of CS domain. When a CS system based on 3GPP TS 24.008 [8] is to be used, clause B.5 applies. When the UE operates in single-registration mode as described in 3GPP TS 24.501 [258] and the UE recognises that a call request is an emergency call, if: 1) the IM CN subsystem is selected in accordance with the conventions and rules specified in 3GPP TS 23.167 [4B]; and 2) the UE is currently registered to the 5GS services while the UE is in an NR cell connected to 5GCN; then the following treatment is applied: 1) if the EMC indicates "Emergency services not supported": a) if the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257] and the emergency services fallback is available (i.e., "ESFB is Y" as described in 3GPP TS 23.167 [4B]), the UE shall attempt emergency services fallback as specified in 3GPP TS 24.501 [258]. If the UE receives from the lower layers an indication that the emergency services fallback attempt failed, the UE may behave as described in bullet b) below assuming that the emergency services fallback is not available; b) if the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257] and the emergency services fallback is not available (i.e., "ESFB is N" as described in 3GPP TS 23.167 [4B]) and if: i) the EMF is set to "Emergency services fallback supported in E-UTRA connected to 5GCN only" and the UE is capable of accessing 5GCN via E-UTRA, the UE shall either: A) attempt to select an E-UTRA cell connected to 5GCN. If the UE finds a suitable E-UTRA cell connected to 5GCN, the UE shall attempt emergency services fallback as specified in 3GPP TS 24.501 [258] via E-UTRA connected to 5GCN. If the UE does not find a suitable E-UTRA cell connected to 5GCN or the UE receives from the lower layers an indication that the emergency services fallback attempt failed, the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; or B) attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; or ii) the EMF is set to "Emergency services fallback not supported" or the UE is not capable of accessing 5GCN via E-UTRA, the UE shall request the lower layers to disable the N1 mode capability for 3GPP access as specified in 3GPP TS 24.501 [257] and attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; and c) if the UE does not support emergency services fallback as specified in 3GPP TS 23.501 [257], the UE shall request the lower layers to disable the N1 mode capability for 3GPP access as specified in 3GPP TS 24.501 [257] and attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; 2) if the EMC indicates "Emergency services supported in E-UTRA connected to 5GCN only": a) if the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257] and the emergency services fallback is available (i.e., "ESFB is Y" as described in 3GPP TS 23.167 [4B]), the UE shall attempt emergency services fallback as specified in 3GPP TS 24.501 [258]. If the UE receives from the lower layers an indication that the emergency services fallback attempt failed, the UE may behave as described in bullet b) below assuming that the emergency services fallback is not available; and b) if the UE does not support emergency services fallback as specified in 3GPP TS 23.501 [257] or the emergency services fallback is not available (i.e., "ESFB is N" as described in 3GPP TS 23.167 [4B]) and if: i) the UE is capable of accessing 5GCN via E-UTRA, the UE shall attempt to select an E-UTRA cell connected to 5GCN. If the UE finds a suitable E-UTRA cell connected to 5GCN, the UE shall trigger establishment of an emergency PDU session as specified in 3GPP TS 24.501 [258] via E-UTRA connected to 5GCN. If the UE does not find a suitable E-UTRA cell connected to 5GCN, the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; or ii) the UE is not capable of accessing 5GCN via E-UTRA, the UE shall request the lower layers to disable the N1 mode capability for 3GPP access as specified in 3GPP TS 24.501 [257] and attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; and 3) if the EMC indicates "Emergency services supported in NR connected to 5GCN only" or "Emergency services supported in NR connected to 5GCN and E-UTRA connected to 5GCN", the UE shall trigger establishment of an emergency PDU session as specified in 3GPP TS 24.501 [258]. When the UE operates in single-registration mode as described in 3GPP TS 24.501 [258] and the UE recognises that a call request is an emergency call, if: 1) the IM CN subsystem is selected in accordance with the conventions and rules specified in 3GPP TS 23.167 [4B]; and 2) the UE is currently registered to the 5GS services while the UE is in an E-UTRA cell connected to 5GCN; then the following treatment is applied: 1) if the EMC indicates "Emergency services not supported": a) if the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257] and the emergency services fallback is available (i.e., "ESFB is Y" as described in 3GPP TS 23.167 [4B]), the UE shall attempt emergency services fallback as specified in 3GPP TS 24.501 [258]. If the UE receives from the lower layers an indication that the emergency services fallback attempt failed, the UE may behave as described in bullet b) below assuming that the emergency services fallback is not available; b) if the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257] and the emergency services fallback is not available (i.e., "ESFB is N" as described in 3GPP TS 23.167 [4B]) and if: i) the EMF is set to "Emergency services fallback supported in NR connected to 5GCN only" and the UE is capable of accessing 5GCN via NR, the UE shall either: A) attempt to select an NR cell connected to 5GCN. If the UE finds a suitable NR cell connected to 5GCN, the UE shall attempt emergency services fallback as specified in 3GPP TS 24.501 [258] via NR connected to 5GCN. If the UE does not find a suitable NR cell connected to 5GCN or the UE receives from the lower layers an indication that the emergency services fallback attempt failed, the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; or B) attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; or ii) the EMF is set to "Emergency services fallback not supported" or the UE is not capable of accessing 5GCN via NR, the UE shall request the lower layers to disable the N1 mode capability for 3GPP access as specified in 3GPP TS 24.501 [257] and attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; and c) if the UE does not support emergency services fallback as specified in 3GPP TS 23.501 [257], the UE shall request the lower layers to disable the N1 mode capability for 3GPP access as specified in 3GPP TS 24.501 [257] and attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; 2) if the EMC indicates "Emergency services supported in NR connected to 5GCN only": a) if the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257] and the emergency services fallback is available (i.e., "ESFB is Y" as described in 3GPP TS 23.167 [4B]), the UE shall attempt emergency services fallback as specified in 3GPP TS 24.501 [258]. If the UE receives from the lower layers an indication that the emergency services fallback attempt failed, the UE may behave as described in bullet b) below assuming that the emergency services fallback is not available; and b) if the UE does not support emergency services fallback as specified in 3GPP TS 23.501 [257] or the emergency services fallback is not available (i.e., "ESFB is N" as described in 3GPP TS 23.167 [4B]) and if: i) the UE is capable of accessing 5GCN via NR, the UE shall attempt to select an NR cell connected to 5GCN. If the UE finds a suitable NR cell connected to 5GCN, the UE shall trigger establishment of an emergency PDU session as specified in 3GPP TS 24.501 [258] via NR connected to 5GCN. If the UE does not find a suitable NR cell connected to 5GCN, the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; or ii) the UE is not capable of accessing 5GCN via NR, the UE shall request the lower layers to disable the N1 mode capability for 3GPP access as specified in 3GPP TS 24.501 [257] and attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; and 3) if the EMC indicates "Emergency services supported in E-UTRA connected to 5GCN only" or "Emergency services supported in NR connected to 5GCN and E-UTRA connected to 5GCN", the UE shall trigger establishment of an emergency PDU session as specified in 3GPP TS 24.501 [258]. U.2.2.6.5 Emergency services in dual registration mode NOTE 1: This subclause covers only the case where the UE selects the IM CN subsystem in accordance with the conventions and rules specified in 3GPP TS 23.167 [4B] and describes the IP-CAN specific procedure. It does not preclude the use of CS domain. When a CS system based on 3GPP TS 24.008 [8] is to be used, clause B.5 applies. When the UE operates in dual-registration mode as described in 3GPP TS 24.501 [258] and the UE recognises that a call request is an emergency call, if: 1) the IM CN subsystem is selected in accordance with the conventions and rules specified in 3GPP TS 23.167 [4B]; and 2) the UE currently camps on an NR cell connected to 5GCN; then the following treatment is applied: 1) if the EMC indicates "Emergency services not supported" and: a) if the UE is attached for EPS services and the network provided the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; or b) if the UE is not attached for EPS services, and: i) if emergency services fallback is available (i.e. "ESFB is Y" as described in 3GPP TS 23.167 [4B]) and the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257], the UE shall attempt emergency services fallback as specified in 3GPP TS 24.501 [258]. If the UE receives from the lower layers an indication that the emergency services fallback attempt failed, the UE may behave as described in bullet ii) below assuming that the emergency services fallback is not available; or ii) if emergency services fallback is not available (i.e. "ESFB is N" as described in 3GPP TS 23.167 [4B]) or the UE does not support emergency services fallback as specified in 3GPP TS 23.501 [257], the UE shall attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; 2) if the EMC indicates "Emergency services supported in E-UTRA connected to 5GCN only" and: a) if the UE is attached for EPS services and: i) if the network provided the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; or ii) if the network provided the UE with the EMC BS set to "emergency bearer services in S1 mode not supported" as described in 3GPP TS 24.301 [8J] and the UE is capable of accessing 5GCN via E-UTRA, the UE shall be locally detached for EPS services and the UE shall attempt to select an E-UTRA cell connected to 5GCN. If the UE finds a suitable E-UTRA cell connected to 5GCN, the UE shall trigger establishment of an emergency PDU session as specified in 3GPP TS 24.501 [258] via E-UTRA connected to 5GCN; or b) if the UE is not attached for EPS services and: i) if emergency services fallback is available (i.e., "ESFB is Y" as described in 3GPP TS 23.167 [4B]) and the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257], the UE shall attempt emergency services fallback as specified in 3GPP TS 24.501 [258]. If the UE receives from the lower layers an indication that the emergency services fallback attempt failed, the UE may behave as described in bullet ii) below assuming that the emergency services fallback is not available; or ii) if emergency services fallback is not available (i.e., "ESFB is N" as described in 3GPP TS 23.167 [4B]) or the UE does not support emergency services fallback as specified in 3GPP TS 23.501 [257], and: A) if the UE is capable of accessing 5GCN via E-UTRA, the UE shall attempt to select an E-UTRA cell connected to 5GCN. If the UE finds a suitable E-UTRA cell connected to 5GCN, the UE shall trigger establishment of an emergency PDU session as specified in 3GPP TS 24.501 [258] via E-UTRA connected to 5GCN. If the UE does not find a suitable E-UTRA cell connected to 5GCN, the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; or B) if the UE is not capable of accessing 5GCN via E-UTRA, the UE shall attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; and 3) if the EMC indicates "Emergency services supported in NR connected to 5GCN only" or "Emergency services supported in NR connected to 5GCN and E-UTRA connected to 5GCN", and: a) if the UE is not attached for EPS services or the UE is attached for EPS services but the network provided the UE with the EMC BS set to "emergency bearer services in S1 mode not supported" as described in 3GPP TS 24.301 [8J], the UE shall trigger establishment of an emergency PDU session as specified in 3GPP TS 24.501 [258]; or b) if the UE is attached for EPS services and the network provided the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall either: i) trigger establishment of an emergency PDU session as specified in 3GPP TS 24.501 [258]; or ii) perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration. NOTE 2: In the above case, the UE chooses between items i) and ii) based on UE implementation. When the UE operates in dual-registration mode as described in 3GPP TS 24.501 [258] and the UE recognises that a call request is an emergency call, if: 1) the IM CN subsystem is selected in accordance with the conventions and rules specified in 3GPP TS 23.167 [4B]; and 2) the UE currently camps on an E-UTRA cell connected to 5GCN and the UE is not attached for EPS services; then the following treatment is applied: 1) if the EMC indicates "Emergency services not supported" and: a) if emergency services fallback is available (i.e. "ESFB is Y" as described in 3GPP TS 23.167 [4B]) and the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257], the UE shall attempt emergency services fallback as specified in 3GPP TS 24.501 [258]. If the UE receives from the lower layers an indication that the emergency services fallback attempt failed, the UE may behave as described in bullet b) below assuming that the emergency services fallback is not available; or b) if emergency services fallback is not available (i.e. "ESFB is N" as described in 3GPP TS 23.167 [4B]) or the UE does not support emergency services fallback as specified in 3GPP TS 23.501 [257], the UE shall attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC, the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; and 2) if the EMC indicates "Emergency services supported in NR connected to 5GCN only" and: a) if emergency services fallback is available (i.e., "ESFB is Y" as described in 3GPP TS 23.167 [4B]) and the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257], the UE shall attempt emergency services fallback as specified in 3GPP TS 24.501 [258]. If the UE receives from the lower layers an indication that the emergency services fallback attempt failed, the UE may behave as described in bullet b) below assuming that the emergency services fallback is not available; or b) if emergency services fallback is not available (i.e., "ESFB is N" as described in 3GPP TS 23.167 [4B]) or the UE does not support emergency services fallback as specified in 3GPP TS 23.501 [257] and: i) if the UE is capable of accessing 5GCN via NR, the UE shall attempt to select an NR cell connected to 5GCN. If the UE finds a suitable NR cell connected to 5GCN, the UE shall trigger establishment of an emergency PDU session as specified in 3GPP TS 24.501 [258] via NR connected to 5GCN. If the UE cannot find a suitable NR cell connected to 5GCN, the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; and ii) if the UE is not capable of accessing 5GCN via NR, the UE shall attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to activate an EPS bearer context to perform emergency registration; and 3) if the EMC indicates "Emergency services supported in E-UTRA connected to 5GCN only" or "Emergency services supported in NR connected to 5GCN and E-UTRA connected to 5GCN", the UE shall trigger establishment of an emergency PDU session as specified in 3GPP TS 24.501 [258]. If the UE operating in dual-registration mode and camping on an E-UTRA cell connected to 5GCN, is also attached for EPS service, the domain selection is out of the scope of the specification. U.2A Usage of SDP U.2A.0 General No additional procedures defined. U.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network If, due to the activation of 5GS QoS flow from the network the related SDP media description needs to be changed, the UE shall update the related SDP information by sending a new SDP offer within a SIP request, which is sent over the existing SIP dialog. If the UE receives a modification request from the network for a 5GS QoS flow that is used for one or more media streams in an ongoing SIP session, the UE shall: 1) if, due to the modification of the 5GS QoS flow, the related SDP media description need to be changed, update the related SDP information by sending a new SDP offer within a SIP request, that is sent over the existing SIP dialog, and respond to the 5GS QoS flow modification request. NOTE: The UE can decide to indicate additional media streams as well as additional or different codecs in the SDP offer than those used in the already ongoing session. U.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE If the UE receives an SDP offer where the SDP offer includes all media streams for which the originating side indicated its local preconditions as met, if the precondition mechanism is supported by the terminating UE and the IP-CAN performs network-initiated resource reservation for the terminating UE and the available resources are not sufficient for the received offer, the terminating UE shall indicate its local preconditions and provide the SDP answer to the originating side without waiting for resource reservation. U.2A.3 Emergency service NOTE: When establishing an emergency session or when modifying an emergency session, the IMSVoPS indicator does not influence handling of SDP offer and SDP answer. U.3 Application usage of SIP U.3.1 Procedures at the UE U.3.1.0 Registration and authentication The UE shall perform reregistration of a previously registered public user identity bound to any one of its contact addresses when changing to an IP-CAN for which usage is specified in annex R or annex W. The reregistration is performed using the new IP-CAN. NOTE 1: This document does not specify how the UE detects that the used IP-CAN has changed. The information that is forcing the reregistration is also used to generate the content for the P-Access-Network-Info header field. NOTE 2: The UE will send the reregistration irrespective of whether it has a SIP dialog or not. If the UE supports the 3GPP PS data off, then the UE shall in all REGISTER requests include the "+g.3gpp.ps-data-off" header field parameter defined in subclause 7.9.8 set to a value indicating the 3GPP PS data off status. When the UE sends a REGISTER request, if the 3GPP PS data off status is "active", then the UE shall only include media feature tags associated with services that are 3GPP PS data off exempt services in the g.3gpp.icsi-ref media feature tag, as defined in subclause 7.9.2 and RFC 3840 [62], for the IMS communication services it intends to use. If the UE is registered, and the 3GPP PS data off status is changed, then the UE shall perform a reregistration of the previously registered public user identity. A UE supporting ANBR as specified in 3GPP TS 26.114 [9B] shall also support RAN-assisted codec adaptation as specified in 3GPP TS 38.300 [270] and 3GPP TS 38.321 [271]. If the UE supports ANBR, upon receiving a 200 (OK) response to the REGISTER request and if the 200 (OK) response contains a Feature-Caps header field with the g.3gpp.anbr feature-capability indicator the UE shall assume that the Network supports RAN-assisted codec adaptation as specified in 3GPP TS 38.300 [270] and 3GPP TS 38.321 [271]. The UE is allowed to include the SDP ‘anbr’ attribute during session establishment as specified in 3GPP TS 26.114 [9B]. U.3.1.0A IMS_Registration_handling policy The IMS_Registration_handling policy indicates whether the UE deregisters from IMS after a configured amount of time after receiving an indication that the IMS Voice over PS Session is not supported. The UE may support the IMS_Registration_handling policy. If the UE supports the IMS_Registration_handling policy, the UE may support being configured with the IMS_Registration_handling policy using one or more of the following methods: a) the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and c) the IMS_Registration_Policy node of 3GPP TS 24.167 [8G]. If the UE is configured with both the IMS_Registration_Policy node of 3GPP TS 24.167 [8G] and the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the IMS_Registration_Policy node of the EFIMSConfigData file shall take precedence. NOTE 1: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [15B]. If the UE is registered with IMS and the IMSVoPS indicator, provided by the lower layers (see 3GPP TS 24.501 [258]), indicates voice is not supported, the UE shall: A) if the Stay_Registered_When_VoPS_Not_Supported leaf indicates requirement to stay registered, the UE needs not to deregister and maintains the registration as required for IMS services; or NOTE 2: The UE will periodically refresh the registration when needed. B) if the Stay_Registered_When_VoPS_Not_Supported leaf indicates requirement to deregister and the Deregistration_Timer leaf used to configure the NoVoPS-dereg timer defined in table 7.8.1 contains a timer value for the time to wait before deregistrerting from IMS, start a timer with the value indicated in the policy and: a) if the timer expires before the UE receives an indication from the lower layers that IMS voice is supported: 1) if there is no ongoing IMS session, the UE either performs reregistration as specified in subclause 5.1.1.4 and shall only include feature tags associated with services that are independent of IMSVoPS indicator or deregister from the IMS following the procedures specified in subclause 5.1.1.6; or 2) if there is ongoing IMS session, and i) if the UE does not receive indication from the lower layer that the IMS voice is supported before the ongoing IMS session is terminated, the UE either performs reregistration as specified in subclause 5.1.1.4 and shall only include feature tags associated with services that are independent of IMSVoPS indicator or deregister from the IMS following the procedures specified in subclause 5.1.1.6 as soon as the ongoing IMS based service is terminated; or ii) if the UE receives indication from the lower layer that the IMS voice is supported before the ongoing IMS session is terminated, cancel the timer; or NOTE 3: How the UE selects reregistration or deregistration is implementation dependent (e.g., SMS service) b) if the UE receives an indication from the lower layers that IMS voice is supported before the timer expires, cancel the timer. If the IMS_Registration_handling policy is not configured, the UE behaviour is implementation specific. U.3.1.1 P-Access-Network-Info header field The UE shall always include the P-Access-Network-Info header field where indicated in subclause 5.1. NOTE: If the P-Access-Network-Info header field includes radio cell identity, the P-Access-Network-Info header field populated by the UE that supports Multi-RAT Dual Connectivity with the 5GCN as described in 3GPP TS 37.340 [264] will contain the information about the radio cell identity of the Master RAN node that is serving the UE. U.3.1.1A Cellular-Network-Info header field Not applicable. U.3.1.2 Availability for calls This subclause documents the minimal requirements for being available for voice communication services when using 5GS. A UE shall perform an initial registration as specified in subclause 5.1.1.2 using a QoS flow for SIP signalling (see annex U.2.2.1), if all the following conditions are met: 1) if the UE is operating in the "voice centric" way; 2) if the UE is capable of receiving any (but not necessarily all) of the media types which the CS domain supports, such that the media type can also be used when accessing the IM CN subsystem using: a) the 5GS IP-CAN via NR; b) the 5GS IP-CAN via E-UTRA; or NOTE 1: The use of 5GS IP-CAN via E-UTRA can also be the result of an inter-RAT fallback during setup of the IMS voice call. This can occur, for example, when a UE not supporting the media type in 5GS IP-CAN via NR initiates an IMS voice call in 5GS IP-CAN via NR. c) the EPS IP-CAN; NOTE 2: EPS can be used as IP-CAN as the result of an EPS fallback during setup of the IMS voice call. This can occur, for example, when a UE not supporting the media type in 5GS IP-CAN via NR initiates an IMS voice call in 5GS IP-CAN via NR, or when a UE not supporting the media type in 5GS IP-CAN via E-UTRA initiates an IMS voice call in 5GS IP-CAN via E-UTRA. 3) if: a) the media type of item 2 is an "audio" media type; b) the UE supports codecs suitable for (conversational) speech; and c) the "audio" media type is not restricted from inclusion in an SDP message according to the media type restriction policy as specified in subclause 6.1.1; and one of the following is true: a) 3GPP PS data off status is "inactive"; b) 3GPP PS data off status is "active", the UE is in the HPLMN or EHPLMN or a subscribed SNPN, and MMTEL voice is a 3GPP PS data off exempt service; or c) 3GPP PS data off status is "active", the UE is in a VPLMN or a non-subscribed SNPN, the UE is configured with an indication that MMTEL voice is a 3GPP PS data off roaming exempt service in the VPLMN or MMTEL voice is a 3GPP data off non-subscribed exempt service in the non-subscribed SNPN; 4) if the UE determines that its contact has not been bound to a public user identity using the IP-CAN, such that the contact is expected to be used for the delivery of incoming requests in the IM CN subsystem relating to the media of item 2 and item 3; 5) if the IMSVoPS indicator, provided by the lower layers indicates voice is supported; 6) if the procedures to perform the initial registration are enabled (see 3GPP TS 24.305 [8T]); and 7) if the PDU session used for IMS is: a) available; or b) not available, and the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message to establish a PDU session with 5GS QoS flow that is needed for performing the initial registration as described in U.2.2.1. NOTE 3: Regardless of any of the above conditions, a UE might attempt to register with the IM CN subsystem at any time. EXAMPLE: As an example of the note, a UE configured to preferably attempt to use the 5GS to access IM CN subsystem can perform an initial registration as specified in subclause 5.1.1.2, if the conditions in items 2, 3, 4, 5, 6 and 7 in this subclause, evaluate to true. The UE indicates to the non-access stratum the status of being available for voice over PS when: I) the UE is capable of receiving any (but not necessarily all) of the media types which the CS domain supports, such that the media type can also be used when accessing the IM CN subsystem using: a) the 5GS IP-CAN via NR; b) the 5GS IP-CAN via E-UTRA; or NOTE 4: The use of 5GS IP-CAN via E-UTRA can also be the result of an inter-RAT fallback during setup of the IMS voice call. This can occur, for example, when a UE not supporting the media type in 5GS IP-CAN via NR initiates an IMS voice call in 5GS IP-CAN via NR. c) the EPS IP-CAN; NOTE 5: EPS can be used as IP-CAN as the result of an EPS fallback during setup of the IMS voice call. This can occur, for example, when a UE not supporting the media type in 5GS IP-CAN via NR initiates an IMS voice call in 5GS IP-CAN via NR, or when a UE not supporting the media type in 5GS IP-CAN via E-UTRA initiates an IMS voice call in 5GS IP-CAN via E-UTRA. II) if the media type of item I is an "audio" media type, the UE supports codecs suitable for (conversational) speech, the "audio" media type is not restricted from inclusion in an SDP message according to the media type restriction policy as specified in subclause 6.1.1; and: a) 3GPP PS data off status is "inactive"; b) 3GPP PS data off status is "active", the UE is in the HPLMN, the EHPLMN or a subscribed SNPN, and MMTEL voice is a 3GPP PS data off exempt service; or c) 3GPP PS data off status is "active", the UE is in a VPLMN or a non-subscribed SNPN, the UE is configured with an indication that MMTEL voice is a 3GPP PS data off roaming exempt service in the VPLMN or MMTEL voice is a 3GPP PS data off non-subscribed exempt service in the non-subscribed SNPN; and III) the UE determines a contact has been bound to a public user identity using the IP-CAN, such that this contact is expected to be used for the delivery of incoming requests in the IM CN subsystem relating to such media. The UE indicates to the non-access stratum the status of being not available for voice over PS when: I) in response to receiving the IMSVoPS indicator indicating voice is supported, the UE: - initiated an initial registration as specified in subclause 5.1.1.2, received a final response to the REGISTER request sent, but the conditions for indicating the status of being available for voice over PS are not met; or - did not initiate an initial registration as specified in subclause 5.1.1.2 and, these conditions for indicating the status of being available for voice over PS are not met; or II) the conditions for indicating the status of being available for voice over PS are no longer met. NOTE 6: The status of being not available for voice over PS is used for domain selection for UE originating sessions / calls specified in 3GPP TS 23.501 [257] subclause 5.16.3.5. U.3.1.2A Availability for SMS The UE determines that the UE is able to use SMS using IMS if the UE: I) is capable of using the MIME type "application/vnd.3gpp.sms" (see 3GPP TS 24.341 [8L]), such that the MIME type can also be used when accessing the IM CN subsystem using the current IP-CAN; II) supports the role of an SM-over-IP sender (see 3GPP TS 24.341 [8L]); IIA) determines the PDU session used for IMS exists; III) determines a contact has been bound to a public user identity using the IP-CAN, such that this contact is expected to be used for the delivery of incoming requests in the IM CN subsystem relating to such media; and IV) the UE does not determine that SMS over IP is restricted in 3GPP TS 24.341 [8L] subclause 5.2.1.3; and V) the 3GPP PS data off status is: - "inactive"; - "active", the UE is in the HPLMN, the EHPLMN or a subscribed SNPN, and SMS over IMS is a 3GPP PS data off exempt service; or - "active", the UE is in a VPLMN or a non-subscribed SNPN, the UE is configured with an indication that SMS over IMS is a 3GPP PS data off roaming exempt service in the VPLMN or SMS over IMS is a 3GPP PS data off non-subscribed exempt service in the non-subscribed SNPN. When above criteria are not met, the UE determines that SMS using IMS is unavailable. NOTE: The status that SMS using IMS is unavailable is used for domain selection for UE originating SMS specified in 3GPP TS 23.501 [257] subclause 5.16.3.8. U.3.1.3 Authorization header field Void. U.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Upon receiving an INVITE request not including the "precondition" option-tag in the Supported header field and not including the "precondition" option-tag in the Require header field, and the IP-CAN performs network-initiated resource reservation for the UE, the UE: 1) if the INVITE request contains an SDP offer and the local resources required at the terminating UE for the received SDP offer are not available: a) shall not alert the user; and b) shall send 183 (Session Progress) response to the INVITE request without waiting for resource reservation and without alerting the user. If the INVITE request includes a Supported header field indicating support of reliable provisional responses, the UE shall send the 183 (Session Progress) response reliably. In the 183 (Session Progres) response, the UE shall include an SDP answer; and 2) if the INVITE request does not contain an SDP offer and the INVITE request includes a Supported header field indicating support of reliable provisional responses: a) shall generate an SDP offer; b) if the local resources required at the terminating UE for the generated SDP offer are not available: A) shall not alert the user; and B) shall reliably send 183 (Session Progress) response to the INVITE request without waiting for resource reservation and without alerting the user. In the 183 (Session Progres) response, the UE shall include the generated SDP offer. Upon successful reservation of local resources, if the precondition mechanism is not used by the terminating UE, the UE can send 180 (Ringing) response to the INVITE request and can alert the user. U.3.1.5 3GPP PS data off If the 3GPP PS data off status is "active" the UE shall only send initial requests that: 1) are associated with a 3GPP IMS service which enforces 3GPP PS data off; NOTE 1: These services are specified in 3GPP TS 22.011 [1C], and enforcement of 3GPP PS data off is described in the respective service specifications. 2) are associated with an emergency service; or 3) are associated with 3GPP PS data off exempt services configured in the UE using one or more of the following methods: - the non_3GPP_ICSIs_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G] is not configured; - the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the VPLMN; - the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] is not configured; - the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the VPLMN; - the /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/non_3GPP_ICSIs_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the subscribed SNPN, or if the UE is in a non-subscribed SNPN and the non_3GPP_ICSIs_non-subscribed_exempt node specified in 3GPP TS 24.167 [8G] is not configured; or - the non_3GPP_ICSIs_non-subscribed_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in a non-subscribed SNPN. If the UE is configured with both the non_3GPP_ICSIs_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. If the UE is configured with both the non_3GPP_ICSIs_roaming_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. If the 3GPP PS data off status changes from "inactive" to "active" the UE shall release all dialogs that 1) are not associated with a 3GPP IMS service which enforces 3GPP PS data off; NOTE 2: These services are specified in 3GPP TS 22.011 [1C], and enforcement of 3GPP PS data off is described in the respective service specifications. 2) are not associated with an emergency service; and 3) are not associated with 3GPP data off exempt services configured in the UE using one or more of the following methods: - the non_3GPP_ICSIs_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G] is not configured; - the non_3GPP_ICSIs_roaming_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in a VPLMN; - the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the VPLMN; - the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the HPLMN or the EHPLMN, or if the UE is in the VPLMN and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] is not configured; or - the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], if the UE is in the VPLMN. - the /<X>/SNPN_Configuration/<X>/3GPP_PS_data_off/non_3GPP_ICSIs_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in the subscribed SNPN, or if the UE is in a non-subscribed SNPN and the non_3GPP_ICSIs_non-subscribed_exempt node specified in 3GPP TS 24.167 [8G] is not configured; - the non_3GPP_ICSIs_non-subscribed_exempt node specified in 3GPP TS 24.167 [8G], if the UE is in a non-subscribed SNPN. If the UE is configured with both the non_3GPP_ICSIs_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. If the UE is configured with both the non_3GPP_ICSIs_roaming_exempt node of 3GPP TS 24.167 [8G] and the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C], then the non_3GPP_ICSIs_roaming_exempt node in the EF3GPPPSDATAOFFservicelist file described in 3GPP TS 31.102 [15C] shall take precedence. U.3.1.6 RLOS Not applicable. U.3.1.7 SIP handling at the originating UE when redirecting the UE from NG-RAN to E-UTRAN fails When a failure occurs in the process of redirecting the UE from NG-RAN to E-UTRAN and the UE is aware of the failure, the UE shall send out a CANCEL request to cancel the INVITE request that includes a Reason header field with a protocol value set to "RELEASE_CAUSE" and a "cause" header field parameter with the value of "7" as specified in subclause 7.2A.18.11.2. U.3.1.8 Unified Access Control The following information is provided to the non-access stratum: - MO-IMS-registration-related-signalling-started; and - MO-IMS-registration-related-signalling-ended; Prior to sending a REGISTER request which is not for emergency registration, the UE sends the MO-IMS-registration-related-signalling-started to the non-access stratum and a) if the barring result is "not-barred", continues with registration procedure as described in subclause 5.1.1; and b) if the barring result is "barred", aborts the registration procedure. In this case, upon receiving an indication from the lower layers that the barring is alleviated, the registration procedure may be initiated, if still needed. When the UE needs to send SUBSCRIBE request for the reg event package, then the UE sends the MO-IMS-registration-related-signalling-started to the non-access stratum before sending SUBSCRIBE request and a) if the barring result is "not-barred", continues with subscribe procedure as described in subclause 5.1.1.3; and b) if the barring result is "barred", aborts the subscribe procedure. In this case, upon receiving an indication from the lower layers that the barring is alleviated, the subscribe procedure may be initiated, if still needed. When a procedure for MO IMS registration related signalling ends, i.e. - a final response to the REGISTER request which is not for emergency registration is received; - a final response to the SUBSCRIBE request for the reg event package is received; - timer F expires at the UE; or - a fatal transport error for sending the REGISTER request or the SUBSCRIBE request is reported by the transport layer, as desribed in IETF RFC 3261 [26]; the UE sends the MO-IMS-registration-related-signalling-ended to the non-access stratum. U.3.1.9 Abnormal cases Upon sending MO-IMS-registration-related-signalling-started indication to the non-access stratum as described in subclause U.3.1.8, if: a) the UE receives, from the lower layers, a notification that the service request 1) was not accepted due to congestion; or 2) resulted in starting timer T3525 (see 3GPP TS 24.501 [258]); and b) a procedure for MO IMS registration related signalling has not ended; then: a) the UE shall abort the procedure for MO-IMS-registration-related-signalling and send MO-IMS-registration-related-signalling-ended indication to the non-access stratum; and b) if an alternative radio access network is available, the UE may attempt the procedure for MO-IMS-registration-related signalling on the alternative radio access network. U.3.2 Procedures at the P-CSCF U.3.2.0 Registration and authentication Void. U.3.2.1 Determining network to which the originating user is attached If the P-CSCF is configured to handle emergency requests, in order to determine from which network the request was originated the P-CSCF shall check the MCC and MNC fields received: - during the registration procedure from the Rx interface as defined in 3GPP TS 29.214 [13D] (e.g. used for deployments without IMS-level roaming interfaces where the P-CSCF is located in the home network); or - from the P-Access-Network-Info header field. NOTE: The above check can be against more than one MNC code stored in the P-CSCF. U.3.2.2 Location information handling Void. U.3.2.3 Prohibited usage of PDU session for emergency services If the P-CSCF detects that a UE uses a PDU session for emergency services for a non-emergency REGISTER request, the P-CSCF shall reject that request by a 403 (Forbidden) response. NOTE: By assigning specific IP address ranges for a PDU session for emergency bearer services and configuring those ranges in P-CSCF, the P-CSCF can detect based on the registered Contact address if UE uses an emergency PDU session for initial registration. U.3.2.4 Support for paging policy differentiation The P-CSCF may support paging policy differentiation by marking packet(s) to be sent towards the UE related to that IMS capability. A specific DSCP (IPv4) value and/or a specific Traffic Class (IPv6) value are assigned by local configuration in the P-CSCF. If local policy requires to provide such marking, the P-CSCF shall identify terminating requests which: a) contain SDP with an "audio" media line and which are related to a IMS multimedia telephony service session specified in 3GPP TS 24.173 [8H]; or b) do not contain an SDP offer but some indication, e.g. a feature capability indicator, indicates that an "audio" media line that would meet network policy for such differentiation, could form part of the subsequent SDP offer. NOTE 1: Precise details of such indications, if any, are subject to operator policy. Alternatively the operator policy can be to not preferentially page requests without an SDP offer. For such identified requests: a) where an unreliable transport mechanism is used as the transport protocol for SIP, the P-CSCF shall mark packets containing an INVITE request; and b) if a reliable transport mechanism is used as the transport protocol for SIP: 1) if a new reliable transport connection needs to be established, the P-CSCF shall turn on the marking of packets within the reliable transport connection in advance of sending an INVITE request; and 2) if there is an existing reliable transport connection, the P-CSCF may turn on the marking of packets within the reliable transport connection in advance of sending an INVITE request. In both these cases for a reliable transport connection, the P-CSCF shall turn off the marking of packets within the reliable transport connection at an appropriate time. U.3.2.5 Void U.3.2.6 Resource sharing This feature is not supported in this release. U.3.2.7 Priority sharing This feature is not supported in this release. U.3.2.8 RLOS Not applicable. U.3.2.9 Support of ANBR and RAN-assisted codec adaptation If the network supports ANBR as specified in 3GPP TS 26.114 [9B] and RAN-assisted codec adaptation as specified in 3GPP TS 38.300 [270] and 3GPP TS 38.321 [271], then the P-CSCF might be configured to indicate ANBR support. If the P-CSCF is configured to indicate ANBR support, when the P-CSCF receives the 200 (OK) response to the REGISTER request the P-CSCF shall include the "g.3gpp.anbr" feature-capability indicator in the Feature-Caps header field of the 200 (OK) response to the REGISTER request. U.3.3 Procedures at the S-CSCF U.3.3.1 Notification of AS about registration status Not applicable. U.3.3.2 RLOS Not applicable. U.4 3GPP specific encoding for SIP header field extensions U.4.1 Void U.5 Use of circuit-switched domain There is no CS domain in this access technology. Annex V (normative): HTTP Profiling V.1 Scope The present annex defines the HTTP messages and data types sent over reference points specified in the present document. V.2 Ms reference point V.2.1 General The Ms reference point is used to request signing of an Identity header field or request verification of a signed assertion in an Identity header field. HTTP POST method is used for the verification request. HTTP 200 (OK) is used when the AS for verification has successfully processed the verification request. HTTP POST method is used for the signing request. HTTP 200 (OK) is used when the AS for signing has successfully processed the signing request. NOTE 1: If the RCD verification using assertion of RCD info functionality is implemented within the Calling number verification using signature verification and attestation information feature, as specified in subclause 3.1, the HTTP POST signing request can contain RCD info (i.e. a PASSporT SHAKEN JSON Web Token specified in RFC 8588 [261] can contain rcd PASSporT claims in accordance with draft-ietf-stir-passport-rcd [302]). HTTP POST method is used for the diversion signing request. HTTP 200 (OK) is used when the AS for signing has successfully processed the diversion signing request. HTTP POST method is used for the Resource-Priority header field signing request. HTTP 200 (OK) is used when the AS for signing has successfully processed the Resource-Priority header field signing request. HTTP POST method is used for the Resource-Priority and Priority header fields signing request. HTTP 200 (OK) is used when the AS for signing has successfully processed the Resource-Priority and Priority header field signing request. HTTP POST method is used for the RCD info signing request. HTTP 200 (OK) is used when the AS for signing has successfully processed the RCD info signing request. NOTE 2: If the Calling number verification using signature verification and attestation information feature is not supported and the RCD verification using assertion of RCD info functionality is implemented as a standalone feature, as specified in subclause 3.1, the HTTP POST RCD info signing request is used (i.e. a PASSporT rcd JSON Web Token is used in accordance with draft-ietf-stir-passport-rcd [302]). Figure V.2.1-1: Usage of the Ms reference point V.2.2 Resource structure Editor's note: [WI: NG_RTC_Ph2, CR#6714] Update of the resource structure to support signing of RCD info and verification of the signed RCD info is FFS. API resources are defined with respect to a "server root". The server root is a URI: - {hostname}:{port}/{RoutingPath}, The resource URI structure is: Figure V.2.2-1: Resource structure for the resource exposed over the Ms reference point NOTE: v1 is the version number of the API. Table V.2.2-1: Variables for the server root Variable Description Presence hostname Host name used to reach the resource. M port Port where the resource is reached M RoutingPath Path identifying the resource M V.2.3 Request requirements V.2.3.1 General V.2.3.2 Request header requirements Table V.2.3.2-1 lists request header field requirements. Table V.2.3.2-1: Header fields included in the requests Header field name Description Presence Content-Type Describes the format of the request body. Shall be set to "application/json" M Accept Describes the supported format of the response body. Shall be set to "application/json" if present O The JSON object in a request starts with the name of the request. For the signingRequest, the JSON object starts with: { "signingRequest": { For the verificationRequest, the JSON object starts with: { "verificationRequest": { V.2.4 Response requirements V.2.4.1 General V.2.4.2 Response header requirements Table V.2.4.2-1: Header fields included in the responses Header field name Description Presence Content-Type Describes the format of the response body. Shall be set to "application/json" M The JSON object in a response starts with the name of the response. For the signingResponse, the JSON object starts with: { "signingResponse": { For the verificationResponse, the JSON object starts with: { "verificationResponse": { V.2.4.3 Error response requirements V.2.4.3.1 General If the server cannot process the request, the server provides an HTTP error response. The error response contains a JSON object specifying the error type. The server provides a service error when the server is unable to process the request. The server provides a policy error when the server is able to process the request, but not able to complete the service execution due to a policy restriction. V.2.4.3.2 Service errors Table V.2.4.3.2-1: Service failure descriptions Exception ID Exception text HTTP status code Exception variables Description - Error: Missing request body. 400 - The request could not be processed due to missing request body. - Error: Missing mandatory parameter. 400 - The request could not be processed due to missing parameters. - Error: Requested response body type is not supported. 406 - The request could not be processed due to a not supported message body format. - Error: Requested resource not found. 404 - The request could not be processed due to no resource available related to the Request-URI - Error: Unsupported request body type. 415 - The request could not be processed due to not supported message body. - Error: Invalid parameter value. 400 - The request could not be processed due to invalid parameter value. - Error: Failed to parse message body. 400 - The request could not be processed due to failure to parse the message body. - Error: Missing mandatory Content-Length headers 411 - The request could not be processed due to a missing Content-Length header. V.2.4.3.3 Policy errors Table V.2.4.3.3-1: Policy failure descriptions Exception ID Exception text HTTP status code Exception variables Description - Method not allowed 405 - The resource was invoked with unsupported operation - Internal server error. 500 - The request failed due to internal error V.2.5 signing V.2.5.1 General To construct a PASSporT SHAKEN object specified in RFC 8588 [261], a PASSporT rph object specified in RFC 8443 [279] and RFC 9027 [278], or a PASSporT div object, specified in RFC 8946 [265], the client sends an HTTP POST request to the AS for signing containing the SIP request information plus any additional claim information to be signed by the target PASSporT type. If the request was successfully processed, then the received signingResponse contains an Identity header field value populated with a signed PASSporT of the requested type along with the appropriate Identity header field parameters. Unsuccessful requests are responded with an HTTP 4xx or 5xx response. V.2.5.2 Data types Table V.2.5.2-1 specifies the data types included in the signing request. The signing request contains the claims included in: - a PASSporT SHAKEN JSON Web Token, specified in RFC 8588 [261]; - a PASSporT div JSON Web Token specified in RFC 8946 [265]; or - a PASSporT rph JSON Web Token specified in RFC 8443 [279] and RFC 9027 [278]. Table V.2.5.2-1: Data types for the signingRequest Parameter Type; Value Presence Description ppt string; set to the value of the "ppt" parameter in the protected header of the PASSporT to be created O This parameter is included to inform the AS for signing the type of PASSporT that is to be constructed and signed. attest string; "A", "B" or "C" O Identifying the relation between the service provider attesting the identity and the subscriber. Specified in RFC 8588 [261]. dest array of identity claim JSON objects representing destination identities; tn or uri M Identifying the called user taken from the To header field for a "shaken" or "rph" PASSporT as specified in RFC 8224 [252], and from the Request-URI after retargeting for a "div" PASSporT as specified in RFC 8946 [265]. div identity claim JSON object, tn or uri. A hi element should be included. O Identifying the diverting user; i.e., the user identified in the Request-URI before retargeting, taken from the History-Info header field as pecified in RFC 8946 [265]. iat integer; time and date of issuance of the PASSporT token M Time since 1 January 1970 in Numeric Date format as specified in RFC 7519 [235]. orig identity claim JSON object; tn or uri M Identifying the calling user. Specified in RFC 8225 [262]. origid String; UUID O Specified in RFC 8588 [261] rph array of strings that correspond to the r-values indicated in the SIP Resource-Priority header field O Contains assertion of the priority level of the user to be used for a given communication session as specified in RFC 8443 [279] and RFC 9027 [278]. sph string "psap-callback" O Contains header field value "psap-callback" of the SIP Priority header field as specified in RFC 9027 [278]. The signing request provides the following two options for identifying the PASSporT type to be constructed: - the PASSporT type is indicated by invoking the signing resource associated with that PASSporT type, as defined in subclause V.2.2; or - the PASSporT type is identified by including a ppt parameter when invoking the /signing resource defined in subclause V.2.2. Table V.2.5.2-1a indicates representative signingRequest parameter inclusion rules per PASSporT type. Table V.2.5.2-1a: signingRequest parameters per PASSporT Type PASSporT Type Parameter attest dest div iat orig origid rph sph shaken M M X M M M X X div X M M M M X X X rph X M X M M X M O NOTE: "M" means "mandatory", "O" means "optional", and "X" means "not applicable". Table V.2.5.2-2 further specifies the data types contained in the signing request parameters. Table V.2.5.2-2: Data types for the signingRequest parameters Parameter Type; Value Presence Description hi string. An "index" header field parameter as specified in RFC 7044 [66] O The "index" header field parameter is included in the entry identifying the diverting user in the History-Info header field. tn string; allowed characters as for local-number-digits and global-number-digits defined in RFC 3966 [22] M The number needs to be in canonical form according to RFC 8224 [252] section 8.3 (see NOTE). uri string; A SIP URI as specified in RFC 3261 [26] following the generic guidelines in RFC [3986]. O Used if the "orig" or "dest" is given in a SIP URI. NOTE: The TAS is expected to provide a valid globally routable number. Table V.2.5.2-3 specifies the data types included in the signing response. Table V.2.5.2-3: Data types for the signingResponse Parameter Type; Value Presence Description identityHeader string; Identity header field value as specified in RFC 8224 [252] M This string cannot be NULL V.2.6 verification V.2.6.1 General To verify one or more received PASSporTs, the client sends a verification request in the form of an HTTP POST request to the AS for verification containing the Identity header field(s) populated with the PASSporT object(s) to be verified. The verification request also contains the following information: - the originating identity and optionally all the diverting identities; and/or - the Resource-Priority header field value and optionally the header field value "psap-callback" of the Priority header field. The verificationResponse contains the outcome of the verification in a verstat claim with values as specified for the verstat tel URI parameter in subclause 7.2A.20 and in a verstatPriority claim with values as specified for the Priority-Verstat header field in subclause 7.2.21. The verificationResponse can optionally contain the claims of PASSporT(s) that passed verification. The verificationResponse can also contain verification results information for each verified PASSporT, as follows: - if verification passed, then verificationResponse contains the validated claims of the PASSporT; - if verification failed, then verificationResponse contains information describing the reason for the failure. Unsuccessful requests are responded with an HTTP 4xx or 5xx response. V.2.6.2 Data types Table V.2.6.2-1 specifies the data types included in the verification request. Table V.2.6.2-1: Data types for the verificationRequest Parameter Type; Value Presence Description identityHeader string; Identity header field value for the originating identity as specified in RFC 8224 [252] and RFC 8588 [261]. M This parameter contains the "shaken" Identity header field value to be verified (see NOTE 1). identityHeaders array of string; Identity header field values as specified in RFC 8224 [252] , RFC 8443 [279], RFC 8946 [265], RFC 9027 [278]. One identityHeader claim per received Identity header field is sent. O This array contains the "div" and "rph" Identity header field values to be verified (see NOTE 2). to string; identity claim JSON object; tn or uri M The destination identity taken from the To header field. Used when no div claim is included. dest string; identity claim JSON object; tn or uri O The destination identity taken from the Request-URI in the incoming request. time integer; Numeric date format defined in RFC 7519 [235] M Time based on the Date header field in the incoming request. from string; identity claim JSON object; tn or uri M The asserted identity, taken from the P-Asserted-Identity or the From header field of the incoming request protectedHeaders array of string; header field(s) O Contains the SIP header field(s) protected by claims in the PASSporT(s) of the identityHeaders array. NOTE 1) For "shaken" PASSporT verification, an identityHeader parameter containing a "shaken" Identity header field shall be included in the verification request. NOTE 2) For "rph" PASSporT verification, an identityHeaders parameter containing an "rph" Identity header field shall be included in the verification request. If the identityHeader parameter contains a "shaken" Identity header field, and/or the identityHeaders parameter contains an "rph" Identity header field, then all "div" Identity header field(s) received in an INVITE request shall be included in the identityHeaders parameter of the verification request. If "rph" PASSporT verification is not to be performed, and if the INVITE request does not contain any "div" Identity header fields, then the identityHeaders parameter shall not be included in the verification request. Invocation of the verification request results in the verification of the Identity header fields in the identityHeader and identityHeaders parameters. In addition, a verification request invocation can verify the integrity of SIP header fields protected by the "div" and "rph" PASSporTs. When verification of SIP header field integrity is required, the protected SIP header field(s) information shall be conveyed in the protectedHeaders parameter. The dest parameter is included when the verification request includes a div claim, and when the verification service is required to distinguish between a legitimately retargeted request and a maliciously replayed request. Table V.2.6.2-1a indicates representative inclusion rules for the verification request identityHeader and identityHeaders parameters for the different combinations of PASSporT types to be verified. Table V.2.6.2-1a: Verification request identityHeader and identityHeaders parameter inclusion rules PASSporT type(s) to be verified Parameter identityHeader identityHeaders shaken M X shaken, div M M rph X M rph, div X M shaken, rph M M shaken, rph, div M M NOTE: "M" means "mandatory" and "X" means "not applicable". Table V.2.6.2-2 specifies the data types included in the verification response. Table V.2.6.2-2: Data types for the verificationResponse Parameter Type; Value Presence Description divResult array of one or more [div, verstatValue] tuples O Parameter informing of the result of the verification of diverting identities. For each verified identity the verstat parameter is added to the verified identity. verstatValue string; set to a value defined in table 7.2A.20.3-1 O Parameter informing of the result of the verification of originating identity. To be used in the verstat parameter added to the verified identity. The parameter is mandatory if the request contained a PASSporT SHAKEN JSON Web Token. verstatPriority string; set to a value defined in table 7.2.21-1 O Parameter informing of the result of the verification of the Resource-Priority header field and optionally the header field value "psap-callback" of the Priority header field. verifyResults array of one or more verifyResult, as defined in table V.2.6.2-3 O Each array entry contains the verification results of a PASSporT contained in the request. Table V.2.6.2-3 specifies the mandatory data types of the verifyResult parameter included in the verification response. Table V.2.6.2-3: Data types for mandatory verifyResult parameters Parameter Type; Value Presence Description verifyResult structured data type containing [ppt, status, validClaims, reasonCode, reasonText, passport] tuple M Contains the verification results of a single Identity header field contained in the identityHeader parameter or an entry of the identityHeaders array of the verification request.The ppt and status parameters are always present. The inclusion of the other parameters in the tuple depends on the value of the status parameter. ppt string, set to the value of the ppt parameter in the protected header of the PASSporT. M Identifies the type of PASSporT associated with this array entry. status String, set to the value pass, fail or none. M Identifies the verification result of the PASSporT associated with this array entry. Each verifyResult entry of the verifyResults array conveys the verification results of an Identity header field contained in the identityHeader parameter or contained in an entry of the identityHeaders array of the verification request. Additional verifyResult parameters are returned based on the value of the status parameter as follows: - a status parameter with a value of "fail" returns the parameters shown in table V.2.6.2-4; - a status parameter with a value of "pass" returns the parameter shown in table V.2.6.2-5; and - a status parameter with a value of "none" returns no additional parameters. A status parameter with a value of "none" indicates that the PASSporT type is not supported. Table V.2.6.2-4 specifies the optional data types of the verifyResult parameter included in the verification response. Table V.2.6.2-4: Data types of optional verifyResult parameters Parameter Type; Value Presence Description reasonCode integer O Identifies the 4xx failure reason code of the failing PASSporT, as defined in RFC 8224 [252]. reasonText string O Identifies the failure text associated with the 4xx failure reason code, as specified in RFC 8224 [252]. passport string O Contains the failing PASSporT NOTE: These parameters are optional since they are included only when the verifyResult "status" parameter has a value of "fail". Table V.2.6.2-5 specifies the additional data types included in the verification response when the status parameter contains a value of "pass". Table V.2.6.2-5: Data types of additional verifyResults parameter for status of "pass" Parameter Type; Value Presence Description validClaims JSON object O The validClaims parameter contains the payload of the verified PASSporT. The validClaims parameter can be used: - to verify the integrity of SIP header field information associated with the validated claims, where a mismatch results in a verification failure; or - to ensure that SIP header field contents contain the information authorized by the validated claims, where a mismatch is resolved by updating the SIP header field to match the validated claims. Annex W (normative): IP-Connectivity Access Network specific concepts when using the 5GCN via WLAN to access IM CN subsystem W.1 Scope The present annex defines IP-CAN specific requirements for a call control protocol for use in the IM CN subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP), where the IP-CAN is the 5GCN via Wireless Local Access Network (WLAN). W.2 IP-CAN aspects when connected to the IM CN subsystem W.2.1 Introduction A UE accessing the IM CN subsystem, and the IM CN subsystem itself, utilise the services provided by the 5GCN and the WLAN to provide packet-mode communication between the UE and the IM CN subsystem. Requirements for the UE on the use of these packet-mode services are specified in this clause. W.2.2 Procedures at the UE W.2.2.1 Establishment of IP-CAN bearer and P-CSCF discovery NOTE: The UE performs access network discovery and selection procedures as specified in 3GPP TS 24.502 [263] and executes access authentication signalling as described in 3GPP TS 24.502 [263] prior to perform the procedure to obtain a local IP address; The UE handles an IP-CAN bearer for SIP signalling as follows: 1) the UE shall obtain a local IP address; 2) the UE shall establish an IKEv2 security association and an IPsec ESP security association as described in 3GPP TS 24.502 [263]; and 3) the IKEv2 security association and the IPsec ESP security association (tunnel) shall remain active throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the deregistration; and In addition the procedures specified in Annex U.2.2.1 apply The UE may support the policy on when a UE is allowed to transfer a PDU session providing access to IMS between 5GC via non-3GPP access and 5GS as specified in subclause U.2.1.1. If the UE is in a session and the policy indicates "a UE having an ongoing IMS session, is not allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RAN" or if the UE is roaming when in a session and the policy indicates "a UE roaming in a VPLMN and having an ongoing IMS session, is not allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RAN" the UE shall not handover the PDU session providing access to IMS from 5GC via non-3GPP access to 5GS. If the UE is in a seesion in the EPS IP-CAN and the policy indicates "a UE is not allowed to transfer a PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN" or the UE is roaming in an EPS IP-CAN and the policy indicates "a UE roaming in a VPLMN and having an ongoing IMS session, is allowed to transfer the PDU session providing access to IMS between 5GCN via non-3GPP access and 5GCN via NG-RAN" the UE shall, if not prevented by other rules or policies, handover the PDU session providing access to IMS from 5GC via non-3GPP access to 5GS. If the UE is in a 5GS IP-CAN and the policy indicates "a UE is not allowed to transfer a PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN, irrespective of if the UE has an ongoing IMS session or not" or the UE is roaming in a 5GS IP-CAN and the policy indicates "a UE roaming in a VPLMN is not allowed to transfer a PDU session providing access to IMS, if any, between 5GCN via non-3GPP access and 5GCN via NG-RAN, irrespective of if the UE has an ongoing IMS session or not" the UE shall not handover the PDU session providing access to IMS from 5GC via non-3GPP access to 5GS. W.2.2.1A Modification of an IP-CAN used for SIP signalling The procedures specified in Annex U.2.2.1A apply. W.2.2.1B Re-establishment of the IP-CAN used for SIP signalling The procedures specified in Annex U.2.2.1B apply. W.2.2.1C P-CSCF restoration procedure The procedures specified in Annex U.2.2.1C apply. W.2.2.2 Session management procedures The procedures specified in Annex U.2.2.2 apply. W.2.2.3 Mobility management procedures The procedures specified in Annex U.2.2.3 apply. W.2.2.4 Cell selection and lack of coverage Not applicable. W.2.2.5 5GS QoS flow for media W.2.2.5.1 General requirements NOTE 1: During establishment of a session, the UE establishes data streams(s) for media related to the session. Either the UE or the network can request for resource allocations for media, but the establishment and modification of the 5GS QoS flow is controlled by the network as described in 3GPP TS 24.501 [258]. If the resource allocation is initiated by the UE, the UE starts reserving resources whenever it has sufficient information about the media streams, and used codecs available as specified in 3GPP TS 24.501 [258] and 3GPP TS 24.502 [263]. NOTE 2: If the resource reservation requests are initiated by the network, then the establishment of 5GS QoS flow for media is initiated by the network after the P-CSCF has authorised the respective 5GS QoS flows and provided the QoS requirements to the PCF. W.2.2.5.1A Activation or modification of QoS flows for media by the UE If the UE is configured not to initiate resource allocation for media according to 3GPP TS 24.167 [8G], then the UE shall refrain from requesting additional 5GS QoS flow(s) for media until the UE considers that the network did not initiate resource allocation for the media. W.2.2.5.1B Activation or modification of QoS flows for media by the network If the UE receives an activation request from the network for a 5GS QoS flow for media which is associated with the 5GS QoS flow used for signalling, the UE shall correlate the media 5GS QoS flow with a currently ongoing SIP session establishment or SIP session modification. If the UE receives a modification request from the network for a 5GS QoS flow that is used for one or more media streams in an ongoing SIP session, the UE shall: 1) modify the related PDU session context in accordance with the request received from the network. W.2.2.5.1C Deactivation of a QoS flow for media When a data stream for media related to a session is released, if the 5GS QoS flow transporting the data stream is no longer needed and allocation of the 5GS QoS flow was requested by the UE, then the UE releases the 5GS QoS flow. NOTE: The 5GS QoS flow can be needed e.g. for other data streams of a session or for other applications in the UE. W.2.2.5.2 Special requirements applying to forked responses The procedures specified in Annex U.2.2.5.2 apply. W.2.2.5.3 Unsuccessful situations Not applicable. W.2.2.6 Emergency service W.2.2.6.1 General Emergency session is supported over the WLAN access if the UE has failed or has not been able to use 3GPP access to set up an emergency session as described in 3GPP TS 23.167 [4B] annex L. IMS emergency session is also supported for UEs with unavailable IMSI (i.e. a UE without USIM) or unauthenticated IMSI. Some jurisdictions allow emergency calls to be made when the UE does not contain an ISIM or USIM, or where the credentials are not accepted. The UE determines that the 5GCN supports emergency services via WLAN when the Emergency service support for non-3GPP (EMCN3) access indicator in the REGISTRATION ACCEPT message indicates emergency services are supported over non-3GPP access as defined in subclause 9.11.3.5 of 3GPP TS 24.501 [258]. When the UE is registered over a WLAN access and detects an emergency call attempt, if the UE supports the emerg-non3gpp timer defined in table 7.8.1 and has determined that 5GCN supports emergency services via WLAN the UE shall start the emerg-non3gpp timer when starting a domain selection searching for a 3GPP access usable to establish an emergency call. The UE shall stop the timer when a 3GPP access supporting emergency call is found. When the emerg-non3gpp timer expires the UE shall consider that it has failed to use 3GPP access to setup the emergency call and shall attempt to setup the emergency call over the available WLAN access. The UE may support being configured for the emerg-non3gpp timer using one or more of the following methods: a) the Timer_Emerg_non3gpp leaf of the EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the Timer_Emerg_non3gpp leaf of the EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and c) the Timer_Emerg_non3gpp leaf of 3GPP TS 24.167 [8G]. When the IM CN subsystem is selected as the domain for the emergency call attempt, the UE determines whether it is currently attached to its home operator's network (e.g. HPLMN) or not (e.g. VPLMN) after it has determined that the 5GCN supports emergency services via WLAN. To perform emergency registration, the UE shall request to establish an emergency PDU session as described in 3GPP TS 24.501 [258]. The procedures for PDU session establishment and P-CSCF discovery, as described in subclause W.2.2.1 of this specification apply accordingly. If the ME is equipped with a UICC, in order to find out whether the UE is attached to the home PLMN or to the visited PLMN, the UE shall compare the MCC and MNC values derived from its IMSI with the MCC and MNC of the PLMN the UE is attached to. If the MCC and MNC of the PLMN the UE is attached to do not match with the MCC and MNC derived from the IMSI, then for the purposes of emergency calls in the IM CN subsystem the UE shall consider to be attached to a VPLMN. If the ME is not equipped with a UICC, the procedure to find d out whether the UE is attached to the home PLMN or to the visited PLMN for the purpose of emergency calls in the IM CN subsystem, is implementation specific. NOTE: The UE verifies if a detected emergency number is still present in the Extended Local Emergency Number List applicable to the PLMN it is currently using. It is possible for the number to no longer be present in the Extended Local Emergency Number List if: - the PLMN attached to relies on the Local Emergency Number List for deriving a URN; or - the previously received Extended Emergency Number List Validity field indicated "Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received". If the UE detected an emergency number, the UE subsequently uses a different PLMN than the PLMN from which the UE received the last Extended Local Emergency Number List, the dialled number is not stored in the ME, in the USIM and in the Local Emergency Number List, and: - the REGISTRATION ACCEPT message received from the different PLMN contains the Extended Local Emergency Number List and the emergency number is present in the updated Extended Local Emergency Number List then the UE uses the updated Extended Local Emergency Number List when it performs the procedures in subclause W.2.2.6.1B; and - the REGISTRATION ACCEPT message received from the different PLMN contains no Extended Local Emergency Number List or the emergency number is no longer present in the updated Extended Local Emergency Number List then the UE shall attempt UE procedures for SIP that relate to emergency using emergency service URN "urn:service:sos". If the dialled number is equal to a local emergency number stored in the Extended Local Emergency Number List (as defined in 3GPP TS 24.301 [8J]), then the UE shall recognize such a number as for an emergency call and: - if the dialled number is equal to an emergency number stored in the ME, or in the USIM, then the UE shall perform either procedures in the subclause W.2.2.6.1B or the procedures in subclause W.2.2.6.1A; and - if the dialled number in not equal to an emergency number stored in the ME, or in the USIM, then the UE shall perform procedures in the subclause W.2.2.6.1B. If the dialled number is not equal to a local emergency number stored in the Extended Local Emergency Number List (as defined in 3GPP TS 24.301 [8J]) and: - if the dialled number is equal to an emergency number stored in the ME, in the USIM or in the Local Emergency Number List (as defined in 3GPP TS 24.008 [8]), then the UE shall recognize such a number as for an emergency call and performs the procedures in subclause W.2.2.6.1A. Once IPsec tunnel setup is completed, the UE shall follow the procedures described in subclause W.2.2.1 of this specification for establishment of IP-CAN bearer and P-CSCF discovery accordingly. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.2A.1.1 and subclause 5.1.3.1, if: - the 380 (Alternate Service) response contains a Contact header field; - the value of the Contact header field is a service URN; and - the service URN has a top-level service type of "sos"; then the UE determines that "emergency service information is included" as described 3GPP TS 23.167 [4B]. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.3.1, if the 380 (Alternate Service) response does not contain a Contact header field with service URN that has a top-level service type of "sos", then the UE determines that "no emergency service information is included" as described 3GPP TS 23.167 [4B]. Upon reception of a 380 (Alternative Service) response to an INVITE request as defined in subclause 5.1.2A.1.1 and subclause 5.1.3.1, the UE shall proceed as follows: 1) if a 3GPP access network is available and the UE has not already attempted to use a 3GPP access network to set up an emergency session as described in 3GPP TS 23.167 [4B] annex L, when the UE selects a domain in accordance with the conventions and rules specified in 3GPP TS 22.101 [1A] and 3GPP TS 23.167 [4B], the UE shall attempt to select a domain of the 3GPP access network, and: - if the CS domain is selected, the UE behaviour is defined in subclause 7.1.2 of 3GPP TS 23.167 [4B] and in annex B; and - if the IM CN subsystem is selected, the UE shall apply the procedures in subclause 5.1.6 with the exception of selecting a domain for the emergency call attempt; In addition, when the UE determines that "it has not been able to use 3GPP access to set up an emergency session" in accordance with subclause L.1 of 3GPP TS 23.167 [4B], the UE shall apply the procedures in subclause 5.1.6 using WLAN, with the exception of selecting a domain for the emergency call attempt; and 2) if a 3GPP access network is not available, then the UE shall apply the procedures in subclause 5.1.6 using WLAN, with the exception of selecting a domain for the emergency call attempt. When the emergency registration expires, the UE should disconnect the emergency PDU session. W.2.2.6.1A Type of emergency service derived from emergency service category value Annex U.2.2.6.1A applies. W.2.2.6.1B Type of emergency service derived from extended local emergency number list Annex U.2.2.6.1B applies. W.2.2.6.2 eCall type of emergency service The UE shall not send an INVITE request with Request-URI set to "urn:service:sos.ecall.manual" or "urn:service:sos.ecall.automatic". W.2.2.6.3 Current location discovery during an emergency call The UE may support the current location discovery during an emergency call specified in subclause 5.1.6.8.2, subclause 5.1.6.8.3, subclause 5.1.6.8.4, and subclause 5.1.6.12. W.2A Usage of SDP W.2A.0 General Not applicable. W.2A.1 Impact on SDP offer / answer of activation or modification of IP-CAN for media by the network The procedures specified in Annex U.2A.1 apply. W.2A.2 Handling of SDP at the terminating UE when originating UE has resources available and IP-CAN performs network-initiated resource reservation for terminating UE Not applicable. W.2A.3 Emergency service No additional procedures defined. W.3 Application usage of SIP W.3.1 Procedures at the UE W.3.1.0 Registration and authentication The procedures specified in Annex U.3.1.0 apply with the following clarification: - the UE shall perform reregistration of a previously registered public user identity bound to any one of its contact addresses when changing to an IP-CAN for which usage is specified in annex U or annex L. W.3.1.0a IMS_Registration_handling policy The IMS_Registration_handling policy indicates whether the UE deregisters from IMS after a configured amount of time after receiving an indication that the IMS Voice over PS Session is not supported. The UE may support the IMS_Registration_handling policy. If the UE supports the IMS_Registration_handling policy, the UE may support being configured with the IMS_Registration_handling policy using one or more of the following methods: a) the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C]; b) the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.103 [15B]; and c) the IMS_Registration_Policy node of 3GPP TS 24.167 [8G]. If the UE is configured with both the IMS_Registration_Policy node of 3GPP TS 24.167 [8G] and the IMS_Registration_Policy node of the EFIMSConfigData file described in 3GPP TS 31.102 [15C] or 3GPP TS 31.103 [15B], then the IMS_Registration_Policy node of the EFIMSConfigData file shall take precedence. NOTE 1: Precedence for files configured on both the USIM and ISIM is defined in 3GPP TS 31.103 [15B]. If the UE is registered with IMS and the IMSVoPS indicator, provided by the lower layers (see 3GPP TS 24.501 [258]), indicates voice is not supported, the UE shall: A) if the Stay_Registered_When_VoPS_Not_Supported leaf indicates requirement to stay registered, the UE needs not to deregister and maintains the registration as required for IMS services; or NOTE 2: The UE will periodically refresh the registration when needed. B) if the Stay_Registered_When_VoPS_Not_Supported leaf indicates requirement to deregister and the Deregistration_Timer leaf used to configure the NoVoPS-dereg timer defined in table 7.8.1 contains a timer value for the time to wait before deregistrerting from IMS, start a timer with the value indicated in the policy and: a) if the timer expires before the UE receives an indication from the lower layers that IMS voice is supported: 1) if there is no ongoing IMS session, the UE either performs reregistration as specified in subclause 5.1.1.4 and shall only include feature tags associated with services that are independent of IMSVoPS indicator or deregister from the IMS following the procedures specified in subclause 5.1.1.6; or 2) if there is ongoing IMS session, and i) if the UE does not receive indication from the lower layer that the IMS voice is supported before the ongoing IMS session is terminated, the UE either performs reregistration as specified in subclause 5.1.1.4 and shall only include feature tags associated with services that are independent of IMSVoPS indicator or deregister from the IMS following the procedures specified in subclause 5.1.1.6 as soon as the ongoing IMS based service is terminated; or ii) if the UE receives indication from the lower layer that the IMS voice is supported before the ongoing IMS session is terminated, cancel the timer; or NOTE 3: How the UE selects reregistration or deregistration is implementation dependent (e.g., SMS service) b) if the UE receives an indication from the lower layers that IMS voice is supported before the timer expires, cancel the timer. If the IMS_Registration_handling policy is not configured, the UE behaviour is implementation specific. W.3.1.1 P-Access-Network-Info header field The UE shall always include the P-Access-Network-Info header field where indicated in subclause 5.1. W.3.1.1A Cellular-Network-Info header field The UE: 1) using the 5GCN via Wireless Local Access Network (WLAN) as IP-CAN to access the IM CN subsystem; and 2) supporting one or more cellular radio access technology (e.g. NR); shall always include the Cellular-Network-Info header field specified in subclause 7.2.15, if the information is available, in every request or response in which the P-Access-Network-Info header field is present. W.3.1.2 Availability for calls Not applicable. W.3.1.2A Availability for SMS Void. W.3.1.3 Authorization header field Void. W.3.1.4 SIP handling at the terminating UE when precondition is not supported in the received INVITE request, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE Not applicable. W.3.1.5 3GPP PS data off Not applicable. W.3.1.6 Transport mechanisms Void. W.3.1.7 RLOS Not applicable. W.3.2 Procedures at the P-CSCF W.3.2.0 Registration and authentication Void. W.3.2.1 Determining network to which the originating user is attached The procedures specified in Annex U.3.2.1 apply. W.3.2.2 Location information handling Void. W.3.2.3 Prohibited usage of PDU session for emergency bearer services The procedures specified in Annex U.3.2.3 apply. W.3.2.4 Support for paging policy differentiation Void. W.3.2.5 Void W.3.2.6 Resource sharing The feature is not supported in this release of the specification. W.3.2.7 Priority sharing The feature is not supported in this release of the specificaiton W.3.2.8 RLOS Not applicable. W.3.3 Procedures at the S-CSCF W.3.3.1 Notification of AS about registration status Not applicable. W.3.3.2 RLOS Not applicable. W.4 3GPP specific encoding for SIP header field extensions W.4.1 Void W.5 Use of circuit-switched domain Void. Annex X (informative): Support of SBA in IMS X.1 Scope This annex describes support for SBA for IMS nodes. IMS nodes can use the SBA interfaces described in the present Annex as an alternative to the Diameter Rx and Cx and Sh reference points and Mr'/Cr reference points based on configuration. To support co-existence of IMS nodes supporting SBA services and IMS nodes not supporting SBA services SBI, enabled IMS nodes can support both SBI and non-SBI interfaces. While the main body of the present document only describes usage of Diameter Rx and Cx and Sh reference points and Mr'/Cr reference points, the usage of the equivalent SBA services is a valid option. NOTE 1: This version of the specification does not specify the details for usage of SBIs by P-CSCF, S-CSCF, I-CSCF and AS in the main body of the specification. NOTE 2: This annex is intended to be used in conjunction with 5GC, see Annex U and Annex W. X.2 Reference points to support SBA in IMS The following IMS related reference points are realized by service-based interfaces: - N5: Reference point between the PCF and an AF. NOTE 1: The P-CSCF acts as an AF from the PCF point of view. The N5 Reference point is defined in 3GPP TS 23.501 [257] and the related protocol specification is in 3GPP TS 29.514 [273]. It provides equivalent functionality to the Diameter-based Rx reference point. - N70: Reference point between an SBI capable I/S-CSCF and an SBI capable HSS. NOTE 2: The N70 Reference point is defined in 3GPP TS 23.228 [7] and the related protocol specification is in 3GPP TS 29.562 [274]. It provides equivalent functionality to the Diameter-based Cx reference point. - N71: Reference point between an SBI capable IMS AS and an SBI capable HSS. NOTE 3: The N71 Reference point is defined in 3GPP TS 23.228 [7] and the related protocol specification is in 3GPP TS 29.562 [274]. It provides equivalent functionality to the Diameter-based Sh reference point. - DC2: Reference point between an SBI capable IMS AS and MF. NOTE 4: The DC2 Reference point is defined in 3GPP TS 23.228 [7] and the related protocol specification is in 3GPP TS 29.176 [298]. X.3 Services to support SBA in IMS If a P-CSCF uses the Npcf_PolicyAuthorization service, it will apply Npcf_PolicyAuthorization service operations (defined in 3GPP TS 29.514[273]) instead of Rx procedures (defined in 3GPP TS 29.214[13D]) and will interact with the PCF instead of the PCRF. - Npcf_PolicyAuthorization: This service is provided by the PCF. This service is to authorise an AF request and to create policies as requested by the authorized AF for the PDU Session to which the AF session is bound. This service also allows the NF service consumer to subscribe/unsubscribe the notification of events. NOTE 1: The P-CSCF acts as an AF from the PCF point of view. The Npcf_PolicyAuthorization service is defined in 3GPP TS 23.502 [275] and the related protocol specification is in 3GPP TS 29.514 [273]. It provides equivalent functionality to the Diameter-based Rx reference point. If an I-CSCF or an S-CSCF uses the Nhss_ims services, it will apply Nhss_ims service operations instead of Cx procedures mentioned throughout the present document and will interact with an SBI capable HSS. - Nhss_imsUEContextManagement: This service is provided by an SBI capable HSS. It enables service operations related to the management of a UE context. - Nhss_imsSubscriberDataManagement: This service is provided by an SBI capable HSS. It enables service operations related to subscriber data management. - Nhss_imsUEAuthentication: This service is provided by an SBI capable HSS. It enables a service operation related to the authentication between the end user and the home IMS network. NOTE 2: The Nhss_imsUEContextManagement, Nhss_imsSubscriberDataManagement, and Nhss_imsUEAuthentication services are defined in annex AA of 3GPP TS 23.228 [7] and the related protocol specification is in 3GPP TS 29.562 [274]. They provide equivalent functionality to the Diameter-based Cx and Sh reference point. NOTE 3: The Nhss_imsUEAuthentication service is not consumed by I-CSCF. NOTE 4: The Nhss_imsUEAuthentication and Nhss_imsUEContextManagement services are not consumed by AS. If an I-CSCF or an S-CSCF uses the Nnrf_NFDiscovery service, it will apply Nnrf_NFDiscovery service operations instead of Cx procedures mentioned throughout the present document and will interact with an SBI capable NRF. NOTE 5: The Nnrf_NFDiscovery service is defined in 3GPP TS 23.502 [275] and the related protocol specification is in 3GPP TS 29.510 [288]. If an IMS AS uses MF services, it will apply Nmf service operations (defined in 3GPP TS 29.176 [298]). - Nmf_MediaResourceManagement (MRM): This service is provided by an MF. It enables an IMS AS to create, update and delete media resources related to IMS Data Channel. Annex AX (normative): Support of UE-Satellite-UE communication in IMS AX.1 Scope The present annex defines UE-Satellite-UE communication specific requirements for use in IMS, i.e., optimized media routing via IMS user plane on-board satellite as described in 3GPP TS 23.228 [7] and TS 23.501 [257]. NOTE: UE-Satellite-UE communication is only applicable for LEO and MEO satellites in this Release of the specification. AX.2 Optimized media routing AX.2.1 Introduction The optimized media routing via IMS described in this annex refers to a routing of media between UEs under the coverage of the same or of different serving satellites, using IMS satellite media plane optimization and with the user plane traffic not transiting through any network elements on the ground as described in 3GPP TS 23.228 [7]. NOTE 1: In this Release of the specification, this feature is supported only for IMS voice/video service and for UEs belonging to the same PLMN and in the non-roaming scenario. Subject to operator policy, the network may support UE-Satellite-UE communication in IMS, i.e. optimized media routing via IMS. If the network supports optimized media routing via IMS, then at call set-up, the P-CSCF determines if the activation of optimized media routing via IMS is possible. This is performed by the P-CSCF on the UE originating side determines the network support of the optimized media routing via IMS and negotiate with the P-CSCF on the terminating side if it supports optimized media routing via IMS. Determination of the support of optimized media routing via IMS is based on the reception of the identifier of the satellite by the originating P-CSCF. When the P-CSCF activates optimized media routing via IMS, then the P-CSCF selects an IMS-AGW onboard the satellite. During handover, if the P-CSCF determines, based on the identifier of the satellite, that optimized media routing via IMS cannot continue between a satellite that is about to serve the local UE and the satellite serving the remote UE, the P-CSCF activates ground fallback routing by selecting an IMS-AGW on the ground. NOTE 2: In this Release of the specification, how the P-CSCF uses the satellite identifier to derive whether optimized media routing over IMS can continue is not covered. The lack of the satellite identifier means optimized media routing is no longer possible. NOTE 3: The ground fallback routing refers to the case with the media transiting through the ground segment. AX.2.2 Procedures at the P-CSCF AX.2.2.1 Determining the activation of optimized media routing If the P-CSCF supports optimized media routing via IMS, the P-CSCF determines that the UE is to be in its home country, the UE indicates in the SIP INVITE request message that P-Access-Network-Info header field value is set to indicate an IP-CAN associated with satellite NG-RAN, and the identifier of the satellite serving the UE is received by the P-CSCF, then the P-CSCF may initiate the procedure for optimized media routing via IMS. NOTE 1: In order to determine the UE is in its home country, the P-CSCF checks the MCC fields received in the P-Access-Network-Info header field against the MCC code(s) stored in the P-CSCF. NOTE 2: The P-CSCF receives from the PCF, in the Access Network Information, the identifier of the satellite serving the UE. The PCF receives the information from the SMF. NOTE 3: For the purpose of optimized media routing via IMS, in this Release of the specification, in the P-Access-Network-Info header field, the access-class field set to "3GPP-NR-SAT", "3GPP-NR(LEO)", "3GPP-NR(MEO)", or "3GPP-NR(OTHERSAT)" are considered associated with satellite NG-RAN. NOTE 4: In this Release of the specification, how the P-CSCF uses the satellite identifier to derive whether optimized media routing over IMS is possible is not specified. Upon receiving the SIP INVITE message, the P-CSCF shall allocate an IMS-AGW on ground and send the identifier of the satellite serving the UE received together with an SDP offer to the terminating side to trigger media negotiation. The terminating P-CSCF shall return the 18X response together with the identifier of the satellite serving the remote UE, if any, and the SDP answer. If the identifier of the satellite serving the remote UE is not present, the originating P-CSCF shall not activate optimized media routing via IMS. If the terminating P-CSCF indicates its activation of the optimized media routing via IMS, the P-CSCF re-selects an IMS-AGW on satellite and releases the IMS-AGW on ground. The P-CSCF shall send the modified SDP offer containing the IMS-AGW transport address to the terminating P-CSCF. Upon receiving the SDP offer, the terminating P-CSCF shall update the IMS-AGW on satellite for the terminating UE with the transport address received in the SDP offer. Editor's Note: [CT1#153 – CR6707] The required IEs for how the identifier of the satellite is transferred from the terminating P-CSCF to the originating P-CSCF is FFS. AX.2.2.2 Call initiation with early media During the call setup via satellite NG-RAN access, if the originating P-CSCF has requested the IMS-AGW on ground to reserve early media resources, receives the P-Early-Media header field in the SDP answer and the identifier of the satellite serving terminating UE, the originating P-CSCF shall allocate an IMS-AGW on satellite and shall not request the IMS-AGW on ground to release the early media resources if the originating P-CSCF decides to activate the optimized media routing. The originating P-CSCF shall release the IMS-AGW on ground and interact with the IMS-AGW on satellite when the SDP answer triggered by the early media re-negotiation is received. Annex Y (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New WG doc Version 0.0.0 Editor's internal draft Version 0.0.1 Editor's internal draft Version 0.0.2 Editor's internal draft N1-001060 Version 0.0.3 Submitted to CN1 SIP adhoc #1 19/10/00 N1-001109 Version 0.0.4 Reflecting results of initial CN1 discussion 19/10/00 N1-001115 Version 0.0.5 Reflecting output of CN1 SIP adhoc#1 discussion 09/11/00 Version 0.0.6 Revision to include latest template and styles N1-010092 Version 0.0.7 Reflecting updates of some IETF drafts 14/02/01 N1-010269 Version 0.0.8 Revision to include temporary annex B incorporating valuable source material 18/03/01 N1-010378 rev Version 0.1.0 incorporating results of CN1 discussion at CN1 #16 12/04/01 N1-010737 Version 0.2.0 incorporating results of CN1 discussions at SIP adhoc #4 11/06/01 N1-010935 Version 0.3.0 incorporating results of CN1 discussions at CN1 #16 23/07/01 N1-011103 Version 0.4.0 incorporating results of CN1 discussions at CN1 #18 (agreed documents N1-011028, N1-011050, N1-011055, N1-011056) 12/09/01 N1-011385 Version 0.5.0 incorporating results of CN1 discussions at CN1 #19 (agreed documents N1-011109, N1-011152, N1-011195, N1-011312, N1-011319, N1-011343) 04/10/01 N1-011470 Version 0.6.0 incorporating results of CN1 discussions at CN1 #19bis (agreed documents N1-011346, N1-011373, N1-011389, N1-011390, N1-011392, N1-011393, N1-011394, N1-011408, N1-011410, N1-011426) 19/10/01 N1-011643 Version 0.7.0 incorporating results of CN1 discussions at CN1 #20 (agreed documents N1-011477, N1-011479, N1-011498, N1-011523, N1-011548, N1-011585, N1-011586, N1-011592, N1-011611, N1-011629) 16/11/01 N1-011821 Version 0.8.0 incorporating results of CN1 discussions at CN1 #20bis (agreed documents N1-011685, N1-011690, N1-011741, N1-011743, N1-011759, N1-011760, N1-011761, N1-011765c, N1-011767, N1-011769, N1-011770, N1-011771, N1-011774, N1-011777, N1-011779, N1-011780) N1-011712 was agreed but determined to have no impact on the specification at this time. 30/11/01 N1-020010 Version 1.0.0 incorporating results of CN1 discussions at CN1 #21 (agreed documents N1-011828, N1-011829, N1-011836, N1-011899 [revision marks not used on moved text - additional change from chairman's report incorporated], implementation of subclause 3.1 editor's note based on discussion of N1-011900 [chairman's report], N1-011905, N1-011984, N1-011985, N1-011986, N1-011988, N1-011989, N1-012012 [excluding points 2 and 16], N1-012013, N1-012014 [excluding point 1], N1-012015, N1-012021, N1-012022, N1-012025, N1-012031, N1-012045, N1-012056, N1-012057) CN1 agreed for presentation for information to CN plenary. 18/01/02 N1-020189 Version 1.1.0 incorporating results of CN1 discussions at CN1 SIP ad-hoc (agreed documents N1-020015, N1-020053, N1-020064, N1-020101, N1-020123, N1-020124, N1-020142, N1-020146, N1-020147, N1-020148, N1-020151, N1-020157, N1-020159, N1-020165). Also N1-012000 (agreed at previous meeting) required, subclause 5.2.6 to be deleted and this change has been enacted 01/02/02 N1-020459 Version 1.2.0 incorporating results of CN1 discussions at CN1 #22 (agreed documents N1-020198, N1-020396, N1-020398, N1-020399, N1-020408, N1-020417, N1-020418, N1-020419, N1-020421, N1-020422, N1-020436, N1-020437, N1-020449) 01/02/02 N1-020569 Version 1.2.1 issues to correct cut and paste error in incorporation of Annex B into main document. Affected subclause 5.1.1.3. Change to clause 7 title that was incorrectly applied to subclause 7.2 also corrected. 22/02/02 Advanced to version 2.0.0 based on agreement of N1-020515. Version 2.0.0 incorporating results of CN1 discussions at CN1 #22bis (agreed documents N1-020466, N1-020468, N1-020469, N1-020472, N1-020473, N1-020500, N1-020504, N1-020507, N1-020511, N1-020512, N1-020521, N1-020583, N1-020584, N1-020602, N1-020603, N1-020604, N1-020611, N1-020612, N1-020613, N1-020614, N1-020615, N1-020617, N1-020623, N1-020624, N1-020625, N1-020626, N1-020627, N1-020642, N1-020643, N1-020646, N1-020649, N1-020656, N1-020659, N1-020668, N1-020669, N1-020670, N1-020671). In addition N1-020409, agreed at CN1#22 but missed from the previous version, was also implemented. References have been resequenced. 02/03/02 Editorial clean-up by ETSI/MCC. 2.0.0 2.0.1 11/03/02 TSG CN#15 NP-020049 The draft was approved, and 3GPP TS 24.229 was then to be issued in Rel-5 under formal change control. 2.0.1 5.0.0 2002-06 NP-16 NP-020230 004 1 S-CSCF Actions on Authentication Failure 5.0.0 5.1.0 N1-020903 2002-06 NP-16 NP-020230 005 2 Disallow Parallel Registrations 5.0.0 5.1.0 N1-020959 2002-06 NP-16 NP-020230 007 1 Hiding 5.0.0 5.1.0 N1-020910 2002-06 NP-16 NP-020312 008 8 Support for services for unregistered users 5.0.0 5.1.0 2002-06 009 1 Not implemented nor implementable. In the meeting report CN1#24 under doc N1-021513 it is shown that CR095r2 supercedes 009r1 if 095r2 was to be approved in CN#16 (but unfortunately 009r1 was also approved in the the CN#16 draft minutes). N1-020921 2002-06 NP-16 NP-020231 019 MGCF procedure clarification 5.0.0 5.1.0 N1-020788 2002-06 NP-16 NP-020231 020 2 MGCF procedure error cases 5.0.0 5.1.0 N1-020960 2002-06 NP-16 NP-020231 022 1 Abbreviations clean up 5.0.0 5.1.0 N1-020949 2002-06 NP-16 NP-020231 023 Clarification of SIP usage outside IM CN subsystem 5.0.0 5.1.0 N1-020792 2002-06 NP-16 NP-020314 024 3 Replacement of COMET by UPDATE 5.0.0 5.1.0 2002-06 NP-16 NP-020231 025 3 Incorporation of current RFC numbers 5.0.0 5.1.0 N1-021091 2002-06 NP-16 NP-020231 026 1 Clarification of B2BUA usage in roles 5.0.0 5.1.0 N1-020941 2002-06 NP-16 NP-020231 028 4 Determination of MO / MT requests in I-CSCF(THIG) 5.0.0 5.1.0 N1-021248 2002-06 NP-16 NP-020231 030 2 P-CSCF release of an existing session 5.0.0 5.1.0 N1-021006 2002-06 NP-16 NP-020232 031 1 S-CSCF release of an existing session 5.0.0 5.1.0 N1-020939 2002-06 NP-16 NP-020232 033 3 SDP procedure at the UE 5.0.0 5.1.0 N1-020971 2002-06 NP-16 NP-020232 035 1 AS Procedures corrections 5.0.0 5.1.0 N1-020934 2002-06 NP-16 NP-020232 036 8 Corrections to SIP Compression 5.0.0 5.1.0 N1-021499 2002-06 NP-16 NP-020232 037 1 Enhancement of S-CSCF and I-CSCF Routing Procedures for interworking with external networks 5.0.0 5.1.0 N1-020928 2002-06 NP-16 NP-020232 041 2 Delivery of IMS security parameters from S-CSCF to the P-CSCF by using proprietary auth-param 5.0.0 5.1.0 N1-021003 2002-06 NP-16 NP-020232 045 Cleanup of request / response terminology - clause 5 5.0.0 5.1.0 N1-020835 2002-06 NP-16 NP-020232 046 Cleanup of request / response terminology - clause 6 5.0.0 5.1.0 N1-020836 2002-06 NP-16 NP-020232 047 2 Simplification of profile tables 5.0.0 5.1.0 N1-021059 2002-06 NP-16 NP-020232 049 Forking options 5.0.0 5.1.0 N1-020839 2002-06 NP-16 NP-020315 050 1 Media-Authorization header corrections 5.0.0 5.1.0 2002-06 NP-16 NP-020233 051 1 Clause 5.4 editorials (S-CSCF) 5.0.0 5.1.0 N1-020950 2002-06 NP-16 NP-020233 053 2 Integrity protection signalling from the P-CSCF to the S-CSCF 5.0.0 5.1.0 N1-021007 2002-06 NP-16 NP-020233 054 Representing IM CN subsystem functional entities in profile table roles 5.0.0 5.1.0 N1-020847 2002-06 NP-16 NP-020233 055 Clause 4 editorials 5.0.0 5.1.0 N1-020848 2002-06 NP-16 NP-020233 056 Clause 5.8 editorials (MRFC) 5.0.0 5.1.0 N1-020849 2002-06 NP-16 NP-020233 057 1 Annex A editorials, including precondition additions 5.0.0 5.1.0 N1-021001 2002-06 NP-16 NP-020233 058 2 Representing the registrar as a UA 5.0.0 5.1.0 N1-021054 2002-06 NP-16 NP-020233 059 Additional definitions 5.0.0 5.1.0 N1-020852 2002-06 NP-16 NP-020312 060 11 Restructuring of S-CSCF Registration Sections 5.0.0 5.1.0 2002-06 NP-16 NP-020234 061 2 Determination of MOC / MTC at P-CSCF and S-CSCF 5.0.0 5.1.0 N1-021060 2002-06 NP-16 NP-020234 062 Correction to the terminating procedures 5.0.0 5.1.0 N1-020927 2002-06 NP-16 NP-020234 063 Loose Routing for Network Initiated Call Release Procedures 5.0.0 5.1.0 N1-020940 2002-06 NP-16 NP-020234 064 Incorporation of previously agreed corrections to clause 5.2.5.2 (N1-020416) 5.0.0 5.1.0 N1-021004 2002-06 NP-16 NP-020234 065 Clause 7.2 editorial corrections 5.0.0 5.1.0 N1-021005 2002-06 NP-16 NP-020234 067 2 S-CSCF routing of MO calls 5.0.0 5.1.0 N1-021097 2002-06 NP-16 NP-020234 068 1 I-CSCF routeing of dialog requests 5.0.0 5.1.0 N1-021078 2002-06 NP-16 NP-020234 069 2 Definition of the Tokanised-by parameter 5.0.0 5.1.0 N1-021096 2002-06 NP-16 NP-020235 070 3 SDP procedures at UE 5.0.0 5.1.0 N1-021453 2002-06 NP-16 NP-020235 073 2 Updates to the procedures involving the iFCs, following the Oulu iFC changes 5.0.0 5.1.0 N1-021440 2002-06 NP-16 NP-020235 074 1 Addition of DHCPv6 references to 24.229 5.0.0 5.1.0 N1-021086 2002-06 NP-16 NP-020235 075 1 Clarification to URL and address assignments 5.0.0 5.1.0 N1-021083 2002-06 NP-16 NP-020235 079 3 Downloading the implicitely registered public user identities from the S-CSCF to P-CSCF 5.0.0 5.1.0 N1-021510 2002-06 NP-16 NP-020235 080 3 Clarification of GPRS aspects 5.0.0 5.1.0 N1-021486 2002-06 NP-16 NP-020235 081 2 Introduction of Subscription Locator Function Interrogation at I-CSCF in 24.229 5.0.0 5.1.0 N1-021469 2002-06 NP-16 NP-020235 082 1 Introduction of Visited_Network_ID p-header 5.0.0 5.1.0 N1-021433 2002-06 NP-16 NP-020236 084 1 MRFC register addresses 5.0.0 5.1.0 N1-021434 2002-06 NP-16 NP-020236 085 1 MRFC INVITE interface editor's notes 5.0.0 5.1.0 N1-021470 2002-06 NP-16 NP-020236 086 1 MRFC OPTIONS interface editor's notes 5.0.0 5.1.0 N1-021471 2002-06 NP-16 NP-020236 087 MRFC PRACK & INFO editor's notes 5.0.0 5.1.0 N1-021159 2002-06 NP-16 NP-020236 088 1 MGCF OPTIONS interface editor's notes 5.0.0 5.1.0 N1-021472 2002-06 NP-16 NP-020236 089 MGCF reINVITE editor's notes 5.0.0 5.1.0 N1-021161 2002-06 NP-16 NP-020237 090 3PCC AS editor's notes 5.0.0 5.1.0 N1-021162 2002-06 NP-16 NP-020237 091 AS acting as terminating UA editor's notes 5.0.0 5.1.0 N1-021163 2002-06 NP-16 NP-020237 092 1 AS acting as originating UA editor's notes 5.0.0 5.1.0 N1-021466 2002-06 NP-16 NP-020237 093 2 Charging overview clause 5.0.0 5.1.0 N1-021512 2002-06 NP-16 NP-020237 094 1 Procedures for original-dialog-id P-header 5.0.0 5.1.0 N1-021456 2002-06 NP-16 NP-020237 095 2 Procedures for charging-vector P-header 5.0.0 5.1.0 N1-021513 2002-06 NP-16 NP-020237 096 1 Procedures for charging-function-addresses P-header 5.0.0 5.1.0 N1-021458 2002-06 NP-16 NP-020237 097 1 SDP types 5.0.0 5.1.0 N1-021467 2002-06 NP-16 NP-020237 100 Removal of State from profile tables 5.0.0 5.1.0 N1-021173 2002-06 NP-16 NP-020238 101 Editor's note cleanup - clause 3 5.0.0 5.1.0 N1-021174 2002-06 NP-16 NP-020238 102 Editor's note cleanup - clause 4 5.0.0 5.1.0 N1-021175 2002-06 NP-16 NP-020238 103 Editor's note cleanup - clause 5.1 and deletion of void subclauses 5.0.0 5.1.0 N1-021176 2002-06 NP-16 NP-020238 104 1 Editor's note cleanup - clause 5.2 and deletion of void subclauses 5.0.0 5.1.0 N1-021487 2002-06 NP-16 NP-020238 105 Editor's note cleanup - clause 5.3 5.0.0 5.1.0 N1-021178 2002-06 NP-16 NP-020238 106 Editor's note cleanup - clause 5.4 and deletion of void subclauses 5.0.0 5.1.0 N1-021179 2002-06 NP-16 NP-020238 107 Editor's note cleanup - clause 5.5 and deletion of void subclauses 5.0.0 5.1.0 N1-021180 2002-06 NP-16 NP-020238 110 Editor's note cleanup - clause 6 5.0.0 5.1.0 N1-021183 2002-06 NP-16 NP-020238 111 Editor's note cleanup - clause 9 5.0.0 5.1.0 N1-021184 2002-06 NP-16 NP-020239 113 1 SIP Default Timers 5.0.0 5.1.0 N1-021465 2002-06 NP-16 NP-020239 114 1 Correction of the subscription to the registration event package 5.0.0 5.1.0 N1-021436 2002-06 NP-16 NP-020239 115 1 Support for ISIMless UICC 5.0.0 5.1.0 N1-021441 2002-06 NP-16 NP-020239 119 1 SIP procedures at UE 5.0.0 5.1.0 N1-021452 2002-06 NP-16 NP-020239 121 2 New requirements in the P-CSCF 5.0.0 5.1.0 N1-021509 2002-06 NP-16 NP-020239 122 SDP procedures at MGCF 5.0.0 5.1.0 N1-021264 2002-06 NP-16 NP-020239 124 1 S-CSCF allocation 5.0.0 5.1.0 N1-021443 2002-06 NP-16 NP-020240 129 1 Introduction of P-Access-Network-Info header 5.0.0 5.1.0 N1-021498 2002-06 NP-16 NP-020240 130 2 Usage of Path and P-Service Route 5.0.0 5.1.0 N1-021508 2002-06 NP-16 NP-020240 133 Removal of Referred-By header from specification 5.0.0 5.1.0 N1-021354 2002-06 NP-16 NP-020240 134 Handling of Record-Route header in profile tables 5.0.0 5.1.0 N1-021357 2002-06 NP-16 NP-020312 135 1 Asserted identities and privacy 5.0.0 5.1.0 2002-06 NP-16 NP-020240 136 Removal of caller preferences from specification 5.0.0 5.1.0 N1-021359 2002-06 NP-16 NP-020240 137 Substitution of REFER references 5.0.0 5.1.0 N1-021360 2002-06 NP-16 NP-020240 138 Removal of session timer from specification 5.0.0 5.1.0 N1-021361 2002-09 NP-17 NP-020489 141 2 Adding MESSAGE to 24.229 5.1.0 5.2.0 2002-09 NP-17 NP-020375 142 Public user identity to use for third party register 5.1.0 5.2.0 N1-021563 2002-09 NP-17 NP-020375 143 1 Replace P-Original-Dialog-ID header with unique data in Route header 5.1.0 5.2.0 N1-021797 2002-09 NP-17 NP-020375 145 Synchronize text with latest I-D for P-headers for charging 5.1.0 5.2.0 N1-021569 2002-09 NP-17 NP-020488 146 2 Service profiles and implicitly registered public user identities 5.1.0 5.2.0 2002-09 NP-17 NP-020376 147 S-CSCF decides when to include 5.1.0 5.2.0 N1-021571 2002-09 NP-17 NP-020376 148 Clean up XML in clause 7.6 5.1.0 5.2.0 N1-021572 2002-09 NP-17 NP-020376 149 Fix clause 5.2.7.4 header 5.1.0 5.2.0 N1-021573 2002-09 NP-17 NP-020376 150 Removal of forward reference to non P-CSCF procedures 5.1.0 5.2.0 N1-021589 2002-09 NP-17 NP-020376 151 Deregistration of public user identities 5.1.0 5.2.0 N1-021590 2002-09 NP-17 NP-020376 152 Reauthentication trigger via other means 5.1.0 5.2.0 N1-021591 2002-09 NP-17 NP-020487 153 3 Registration with integrity protection 5.1.0 5.2.0 2002-09 NP-17 NP-020485 154 2 Explicit listing of need to route response messages 5.1.0 5.2.0 2002-09 NP-17 NP-020377 157 1 Include IP address in ICID 5.1.0 5.2.0 N1-021816 2002-09 NP-17 NP-020377 158 Reference updates 5.1.0 5.2.0 N1-021604 2002-09 NP-17 NP-020377 159 Abbreviation updates 5.1.0 5.2.0 N1-021605 2002-09 NP-17 NP-020377 163 1 Clarifications of allocation of IP address 5.1.0 5.2.0 N1-021817 2002-09 NP-17 NP-020377 171 1 Verifications at the P-CSCF for subsequent request 5.1.0 5.2.0 N1-021802 2002-09 NP-17 NP-020377 174 1 Clarification of IMS signalling flag 5.1.0 5.2.0 N1-021781 2002-09 NP-17 NP-020377 176 1 Definition of a general-purpose PDP context for IMS 5.1.0 5.2.0 N1-021783 2002-09 NP-17 NP-020372 177 2 Request for DNS IPv6 server address 5.1.0 5.2.0 N1-021833 2002-09 NP-17 NP-020378 178 Error cases for PDP context modification 5.1.0 5.2.0 N1-021679 2002-09 NP-17 NP-020378 183 1 Incorporation of draft-ietf-sip-sec-agree-04.txt 5.1.0 5.2.0 N1-021791 2002-09 NP-17 NP-020378 185 1 User Initiated De-registration 5.1.0 5.2.0 N1-021787 2002-09 NP-17 NP-020378 186 1 Mobile initiated de-registration 5.1.0 5.2.0 N1-021788 2002-09 NP-17 NP-020378 187 1 CallID of REGISTER requests 5.1.0 5.2.0 N1-021786 2002-09 NP-17 NP-020378 188 1 Correction to the I-CSCF routing procedures 5.1.0 5.2.0 N1-021803 2002-09 NP-17 NP-020378 189 1 Registration procedures at P-CSCF 5.1.0 5.2.0 N1-021793 2002-09 NP-17 NP-020378 192 1 Corrections related to the P-Access-Network-Info header 5.1.0 5.2.0 N1-021827 2002-09 NP-17 NP-020378 194 1 Chapter to decribe the registration event 5.1.0 5.2.0 N1-021794 2002-09 NP-17 NP-020484 196 Definition of abbreviation IMS 5.1.0 5.2.0 2002-12 NP-18 NP-020558 140 4 Support of non-IMS forking 5.2.0 5.3.0 N1-022446 2002-12 NP-18 NP-020565 144 2 Identification of supported IETF drafts within this release 5.2.0 5.3.0 N1-022114 2002-12 NP-18 NP-020558 161 3 Clarifications and editorials to SIP profile 5.2.0 5.3.0 N1-022412 2002-12 NP-18 NP-020558 175 5 Clarifications of the binding and media grouping 5.2.0 5.3.0 N1-022494 2002-12 NP-18 NP-020558 179 2 Support of originating requests from Application Servers 5.2.0 5.3.0 N1-022106 2002-12 NP-18 NP-020558 197 Wrong references in 4.1 5.2.0 5.3.0 N1-021902 2002-12 NP-18 NP-020558 198 Alignment of the MGCF procedures to RFC 3312 5.2.0 5.3.0 N1-021903 2002-12 NP-18 NP-020558 199 1 Service Route Header and Path Header interactions 5.2.0 5.3.0 N1-022080 2002-12 NP-18 NP-020558 202 Addition of clause 6 though clause 9 references to conformance clause 5.2.0 5.3.0 N1-021919 2002-12 NP-18 NP-020558 203 1 URL and address assignments 5.2.0 5.3.0 N1-022115 2002-12 NP-18 NP-020559 204 3 Fix gprs-charging-info definition and descriptions 5.2.0 5.3.0 N1-022426 2002-12 NP-18 NP-020559 206 Alignment of the SDP attributes related to QoS integration with IETF 5.2.0 5.3.0 N1-021930 2002-12 NP-18 NP-020559 207 1 Update of the 3GPP-generated SIP P- headers document references 5.2.0 5.3.0 N1-022116 2002-12 NP-18 NP-020559 208 1 Handling of INVITE requests that do not contain SDP 5.2.0 5.3.0 N1-022098 2002-12 NP-18 NP-020559 209 2 UE Registration 5.2.0 5.3.0 N1-022471 2002-12 NP-18 NP-020559 211 1 Usage of private user identity during registration 5.2.0 5.3.0 N1-022083 2002-12 NP-18 NP-020559 212 1 P-CSCF subscription to the users registration-state event 5.2.0 5.3.0 N1-022084 2002-12 NP-18 NP-020559 213 2 Handling of MT call by the P-CSCF 5.2.0 5.3.0 N1-022154 2002-12 NP-18 NP-020559 215 P-CSCF acting as a UA 5.2.0 5.3.0 N1-021939 2002-12 NP-18 NP-020559 216 1 S-CSCF handling of protected registrations 5.2.0 5.3.0 N1-022085 2002-12 NP-18 NP-020560 217 1 S-CSCF handling of subscription to the users registration-state event 5.2.0 5.3.0 N1-022086 2002-12 NP-18 NP-020560 218 1 Determination of MO or MT in I-CSCF 5.2.0 5.3.0 N1-022102 2002-12 NP-18 NP-020560 220 Definition of the NAI and RTCP abbreviations 5.2.0 5.3.0 N1-021944 2002-12 NP-18 NP-020560 222 4 Go related error codes in the UE 5.2.0 5.3.0 N1-022495 2002-12 NP-18 NP-020560 223 1 Clarifications on CCF/ECF addresses 5.2.0 5.3.0 N1-022120 2002-12 NP-18 NP-020560 225 2 Clarifications on dedicated PDP Context for IMS signalling 5.2.0 5.3.0 N1-022156 2002-12 NP-18 NP-020560 228 3 Clarifications on the use of charging correlation information 5.2.0 5.3.0 N1-022425 2002-12 NP-18 NP-020560 232 1 Expires information in REGISTER response 5.2.0 5.3.0 N1-022095 2002-12 NP-18 NP-020560 235 2 Indication of successful establishment of Dedicated Signalling PDP context to the UE 5.2.0 5.3.0 N1-022129 2002-12 NP-18 NP-020560 237 P-CSCF sending 100 (Trying) Response for reINVITE 5.2.0 5.3.0 N1-021998 2002-12 NP-18 NP-020561 239 1 Correction on P-Asserted-Id, P-Preferred-Id, Remote-Party-ID 5.2.0 5.3.0 N1-022100 2002-12 NP-18 NP-020561 240 1 Clarifications to subclause 9.2.5 5.2.0 5.3.0 N1-022137 2002-12 NP-18 NP-020561 242 ENUM translation 5.2.0 5.3.0 N1-022020 2002-12 NP-18 NP-020561 243 1 AS routing 5.2.0 5.3.0 N1-022107 2002-12 NP-18 NP-020561 245 1 Warning header 5.2.0 5.3.0 N1-022108 2002-12 NP-18 NP-020561 246 3 S-CSCF procedure tidyup 5.2.0 5.3.0 N1-022497 2002-12 NP-18 NP-020561 247 1 P-CSCF procedure tidyup 5.2.0 5.3.0 N1-022125 2002-12 NP-18 NP-020561 248 2 UE procedure tidyup 5.2.0 5.3.0 N1-022472 2002-12 NP-18 NP-020561 249 3 MESSAGE corrections part 1 5.2.0 5.3.0 N1-022455 2002-12 NP-18 NP-020561 250 2 MESSAGE corrections part 2 5.2.0 5.3.0 N1-022456 2002-12 NP-18 NP-020562 251 2 Security association clarifications 5.2.0 5.3.0 N1-022440 2002-12 NP-18 NP-020562 252 1 The use of security association by the UE 5.2.0 5.3.0 N1-022433 2002-12 NP-18 NP-020562 253 1 UE integrity protected re-registration 5.2.0 5.3.0 N1-022434 2002-12 NP-18 NP-020562 255 3 Handling of default public user identities by the P-CSCF 5.2.0 5.3.0 N1-022496 2002-12 NP-18 NP-020562 263 Fixing ioi descriptions 5.2.0 5.3.0 N1-022266 2002-12 NP-18 NP-020562 264 1 Fix descriptions for ECF/CCF addresses 5.2.0 5.3.0 N1-022447 2002-12 NP-18 NP-020562 266 2 Alignment with draft-ietf-sipping-reg-event-00 and clarification on network initiated deregistration 5.2.0 5.3.0 N1-022493 2002-12 NP-18 NP-020563 267 1 Correction to network initiated re-authentication procedure 5.2.0 5.3.0 N1-022449 2002-12 NP-18 NP-020563 268 1 Registration Expires Timer Default Setting 5.2.0 5.3.0 N1-022439 2002-12 NP-18 NP-020563 269 1 Clarification on Sh interface for charging purposes 5.2.0 5.3.0 N1-022465 2002-12 NP-18 NP-020563 270 2 Clarifications on the scope 5.2.0 5.3.0 N1-022500 2002-12 NP-18 NP-020563 273 1 Add charging info for SUBSCRIBE 5.2.0 5.3.0 N1-022467 2002-12 NP-18 NP-020563 274 1 Profile revisions for RFC 3261 headers 5.2.0 5.3.0 N1-022413 2002-12 NP-18 NP-020563 275 Consistency changes for SDP procedures at MGCF 5.2.0 5.3.0 N1-022345 2002-12 NP-18 NP-020563 276 Proxy support of PRACK 5.2.0 5.3.0 N1-022350 2002-12 NP-18 NP-020563 277 Clarification of transparent handling of parameters in profile 5.2.0 5.3.0 N1-022351 2002-12 NP-18 NP-020564 279 1 Meaning of refresh request 5.2.0 5.3.0 N1-022444 2002-12 NP-18 NP-020564 280 Removal of Caller Preferences dependency 5.2.0 5.3.0 N1-022362 2002-12 NP-18 NP-020564 281 1 P-Access-Network-Info clarifications 5.2.0 5.3.0 N1-022445 2002-12 NP-18 NP-020564 282 Clarification on use of the From header by the UE 5.2.0 5.3.0 N1-022370 2002-12 NP-18 NP-020634 283 2 Support of comp=sigcomp parameter 5.2.0 5.3.0 2002-12 NP-18 NP-020668 284 4 SDP media policy rejection 5.2.0 5.3.0 2002-12 NP-18 NP-020567 285 1 Fallback for compression failure 5.2.0 5.3.0 N1-022481 2002-12 NP-18 NP-020564 287 1 SA related procedures 5.2.0 5.3.0 N1-022459 2002-12 NP-18 NP-020568 290 1 Emergency Service correction 5.2.0 5.3.0 N1-022461 2002-12 NP-18 NP-020663 278 4 P-CSCF does not strip away headers 5.2.0 5.3.0 N1-022499 2002-12 NP-18 NP-020557 289 PCF to PDF 5.2.0 5.3.0 N1-022387 2003-03 NP-19 NP-030049 291 Minor correction and consistency changes to general part of profile 5.3.0 5.4.0 N1-030012 2003-03 NP-19 NP-030049 292 SIP profile minor correction and consistency changes 5.3.0 5.4.0 N1-030013 2003-03 NP-19 NP-030049 293 1 Network asserted identity procedure corrections for the UE 5.3.0 5.4.0 N1-030261 2003-03 NP-19 NP-030049 294 1 Asserted identity inclusion in SIP profile 5.3.0 5.4.0 N1-030300 2003-03 NP-19 NP-030049 296 Profile references relating to registration 5.3.0 5.4.0 N1-030023 2003-03 NP-19 NP-030049 297 2 Reference corrections 5.3.0 5.4.0 N1-030301 2003-03 NP-19 NP-030050 300 1 488 message with a subset of allowed media parameters 5.3.0 5.4.0 N1-030245 2003-03 NP-19 NP-030050 301 1 Handling of Emergency Numbers in P-CSCF 5.3.0 5.4.0 N1-030239 2003-03 NP-19 NP-030050 302 2 Correction of the registration state event package 5.3.0 5.4.0 N1-030268 2003-03 NP-19 NP-030050 305 2 User initiated de-registration at P-CSCF 5.3.0 5.4.0 N1-030295 2003-03 NP-19 NP-030050 306 2 Network-initiated deregistration at UE, P-CSCF, and S-CSCF 5.3.0 5.4.0 N1-030296 2003-03 NP-19 NP-030050 307 2 UE deregistration during established dialogs 5.3.0 5.4.0 N1-030297 2003-03 NP-19 NP-030050 308 2 S-CSCF handling of deregistration during established dialogs 5.3.0 5.4.0 N1-030298 2003-03 NP-19 NP-030050 309 1 S-CSCF handling of established dialogs upon deregistration 5.3.0 5.4.0 N1-030233 2003-03 NP-19 NP-030050 310 2 S-CSCF handling of established dialogs upon registration-lifetime expiration 5.3.0 5.4.0 N1-030299 2003-03 NP-19 NP-030051 311 1 P-CSCF handling of established dialogs upon registration-lifetime expiration 5.3.0 5.4.0 N1-030235 2003-03 NP-19 NP-030051 312 1 Correction of Authentication procedure 5.3.0 5.4.0 N1-030240 2003-03 NP-19 NP-030051 313 Mixed Path header and Service-Route operation 5.3.0 5.4.0 N1-030127 2003-03 NP-19 NP-030051 315 2 Clarifications on updating the authorization token 5.3.0 5.4.0 N1-030255 2003-03 NP-19 NP-030051 318 2 Consideration of P-CSCF/PDF 5.3.0 5.4.0 N1-030307 2003-03 NP-19 NP-030051 319 2 Clarification on GPRS charging information 5.3.0 5.4.0 N1-030308 2003-03 NP-19 NP-030051 323 1 P-Access-Network-Info procedure corrections for the UE 5.3.0 5.4.0 N1-030250 2003-03 NP-19 NP-030051 324 1 P-Access-Network-Info procedure corrections for the S-CSCF 5.3.0 5.4.0 N1-030251 2003-03 NP-19 NP-030051 326 1 Updating user agent related profile tables 5.3.0 5.4.0 N1-030260 2003-03 NP-19 NP-030052 327 2 Cleanup and clarification to the registration and authentication procedure 5.3.0 5.4.0 N1-030282 2003-03 NP-19 NP-030052 328 1 Corrections to the reg event package 5.3.0 5.4.0 N1-030230 2003-03 NP-19 NP-030052 330 2 Clarifications for setting up separate PDP contexts in case of SBLP 5.3.0 5.4.0 N1-030288 2003-03 NP-19 NP-030052 331 2 Handling of the P-Media-Autohorization header 5.3.0 5.4.0 N1-030289 2003-03 NP-19 NP-030052 333 3 Removal of P-Asserted-Identity from clause 7 of 24.229 5.3.0 5.4.0 N1-030310 2003-03 NP-19 NP-030052 334 P-CSCF general procedure corrections 5.3.0 5.4.0 N1-030182 2003-03 NP-19 NP-030052 335 2 Usage of Contact in UE's registration procedure 5.3.0 5.4.0 N1-030281 2003-03 NP-19 NP-030052 337 Usage of P-Asserted-Identity for responses 5.3.0 5.4.0 N1-030193 2003-03 NP-19 NP-030052 339 2 Authorization for registration event package 5.3.0 5.4.0 N1-030285 2003-03 NP-19 NP-030052 341 1 P-CSCF subscription to reg event 5.3.0 5.4.0 N1-030284 2003-06 NP-20 NP-030275 295 4 Security agreement inclusion in SIP profile 5.4.0 5.5.0 N1-030939 2003-06 NP-20 NP-030275 322 5 3GPP P-header inclusion in SIP profile 5.4.0 5.5.0 N1-030938 2003-06 NP-20 NP-030275 332 5 Change of IP address for the UE 5.4.0 5.5.0 N1-030923 2003-06 NP-20 NP-030275 342 Removal of the requirement for UE re-authentication initiated by HSS 5.4.0 5.5.0 N1-030349 2003-06 NP-20 NP-030275 343 2 UE behaviour on reception of 420 (Bad Extension) message 5.4.0 5.5.0 N1-030552 2003-06 NP-20 NP-030275 347 2 Handling of DTMF 5.4.0 5.5.0 N1-030551 2003-06 NP-20 NP-030276 348 1 Format of Tel URL in P-Asserted-Id 5.4.0 5.5.0 N1-030510 2003-06 NP-20 NP-030276 349 Delete Note on header stripping/SDP manipulation 5.4.0 5.5.0 N1-030387 2003-06 NP-20 NP-030276 354 1 Clarifications on using DNS procedures 5.4.0 5.5.0 N1-030520 2003-06 NP-20 NP-030276 356 4 Addition of procedures at the AS for SDP 5.4.0 5.5.0 N1-030942 2003-06 NP-20 NP-030276 357 1 Usage of P-Associated-URI 5.4.0 5.5.0 N1-030499 2003-06 NP-20 NP-030276 359 1 Network-initiated deregistration at UE and P-CSCF 5.4.0 5.5.0 N1-030501 2003-06 NP-20 NP-030276 360 2 Barred identities 5.4.0 5.5.0 N1-030550 2003-06 NP-20 NP-030276 365 1 PDP contex subject to SBLP cannot be reused by other IMS sessions 5.4.0 5.5.0 N1-030513 2003-06 NP-20 NP-030276 368 1 User authentication failure cleanups 5.4.0 5.5.0 N1-030506 2003-06 NP-20 NP-030277 369 3 S-CSCF behavior correction to enable call forwarding 5.4.0 5.5.0 N1-030931 2003-06 NP-20 NP-030277 370 1 SUBSCRIBE request information stored at the P-CSCF and S-CSCF 5.4.0 5.5.0 N1-030521 2003-06 NP-20 NP-030277 371 1 Profile Tables - Transparency 5.4.0 5.5.0 N1-030858 2003-06 NP-20 NP-030277 375 1 Profile Tables - Major Capability Corrections 5.4.0 5.5.0 N1-030860 2003-06 NP-20 NP-030277 376 2 Profile Tables - Deletion of Elements not used in 24.229 5.4.0 5.5.0 N1-030921 2003-06 NP-20 NP-030277 377 1 Use of the QoS parameter 'signalling information' for a signalling PDP context 5.4.0 5.5.0 N1-030840 2003-06 NP-20 NP-030277 378 2 Deregistration of a PUID (not the last one) 5.4.0 5.5.0 N1-030919 2003-06 NP-20 NP-030277 379 2 'Last registered public user identity' terminology change 5.4.0 5.5.0 N1-030920 2003-06 NP-20 NP-030277 380 1 Check Integrity Protection for P-Access-Network-Info header 5.4.0 5.5.0 N1-030881 2003-06 NP-20 NP-030278 381 1 PCSCF setting of Integrity protection indicator and checking of Security Verify header 5.4.0 5.5.0 N1-030882 2003-06 NP-20 NP-030278 383 1 Consistent treatment of register and de-register 5.4.0 5.5.0 N1-030884 2003-06 NP-20 NP-030278 384 1 Optionality of sending CK is removed 5.4.0 5.5.0 N1-030885 2003-06 NP-20 NP-030278 385 1 Addition of note and Correction of References regarding security associations and registration 5.4.0 5.5.0 N1-030886 2003-06 NP-20 NP-030278 387 1 Subscription/Registration refresh time 5.4.0 5.5.0 N1-030887 2003-06 NP-20 NP-030278 388 1 Corrections to use of IK 5.4.0 5.5.0 N1-030863 2003-06 NP-20 NP-030278 390 Mobile-originating case at UE 5.4.0 5.5.0 N1-030647 2003-06 NP-20 NP-030278 394 2 Re-authentication procedure. 5.4.0 5.5.0 N1-030917 2003-06 NP-20 NP-030278 395 Replacement of SIP URL with SIP URI 5.4.0 5.5.0 N1-030652 2003-06 NP-20 NP-030279 397 2 Notification about registration state 5.4.0 5.5.0 N1-030926 2003-06 NP-20 NP-030279 402 1 Handling of P-Asserted ID in MGCF 5.4.0 5.5.0 N1-030848 2003-06 NP-20 NP-030279 404 1 S-CSCF initiated release of calls to circiut switched network 5.4.0 5.5.0 N1-030873 2003-06 NP-20 NP-030279 405 2 Supported Integrity algorithms 5.4.0 5.5.0 N1-030927 2003-06 NP-20 NP-030279 407 1 RFC 3524, Single Reservation Flows 5.4.0 5.5.0 N1-030851 2003-06 NP-20 NP-030279 410 1 Clarification of the S-CSCF's handling of the P-access-network-info header 5.4.0 5.5.0 N1-030868 2003-06 NP-20 NP-030279 411 2 Port numbers in the RR header entries 5.4.0 5.5.0 N1-030941 2003-06 NP-20 NP-030279 412 2 Registration abnormal cases 5.4.0 5.5.0 N1-030928 2003-06 NP-20 NP-030280 415 Minor correction to section 5.4.5.1.2 5.4.0 5.5.0 N1-030720 2003-06 NP-20 NP-030280 417 1 Introduction of RTCP bandwidth 5.4.0 5.5.0 N1-030872 2003-06 NP-20 NP-030280 418 1 Registratin Event - Shortend 5.4.0 5.5.0 N1-030844 2003-06 NP-20 NP-030280 419 1 HSS / S-CSCF text relating to user deregistration 5.4.0 5.5.0 N1-030845 2003-06 NP-20 NP-030280 421 Handling of unknown methods at the P-CSCF 5.4.0 5.5.0 N1-030743 2003-06 NP-20 NP-030280 422 1 Definitions and abbreviations update 5.4.0 5.5.0 N1-030870 2003-06 NP-20 NP-030280 423 Removal of hanging paragraph 5.4.0 5.5.0 N1-030752 2003-06 NP-20 NP-030280 424 Access network charging information 5.4.0 5.5.0 N1-030753 2003-06 NP-20 NP-030280 425 1 UE procedure tidyup 5.4.0 5.5.0 N1-030871 2003-06 NP-20 NP-030281 426 P-CSCF procedure tidyup 5.4.0 5.5.0 N1-030755 2003-06 NP-20 NP-030281 427 I-CSCF procedure tidyup 5.4.0 5.5.0 N1-030756 2003-06 NP-20 NP-030281 428 S-CSCF procedure tidyup 5.4.0 5.5.0 N1-030757 2003-06 NP-20 NP-030281 429 BGCF procedure tidyup 5.4.0 5.5.0 N1-030758 2003-06 NP-20 NP-030281 430 AS procedure tidyup 5.4.0 5.5.0 N1-030759 2003-06 NP-20 NP-030281 431 MRFC procedure tidyup 5.4.0 5.5.0 N1-030760 2003-06 NP-20 NP-030281 434 1 SDP procedure tidyup 5.4.0 5.5.0 N1-030852 2003-06 NP-20 NP-030281 438 2 Profile Tables – Further Corrections 5.4.0 5.5.0 N1-030935 2003-06 NP-20 NP-030281 439 3 AS's subscription for the registration state event package 5.4.0 5.5.0 N1-030940 2003-06 NP-20 NP-030281 440 Temporary Public User Identity in re- and de-REGISTER requests 5.4.0 5.5.0 N1-030792 2003-09 NP-21 NP-030412 444 2 All non-REGISTER requests must be integrity protected 5.5.0 5.6.0 N1-031328 2003-09 NP-21 NP-030412 445 Download of all service profiles linked to PUID being registered and implicitly registered 5.5.0 5.6.0 N1-031010 2003-09 NP-21 NP-030412 448 3 Authentication at UE 5.5.0 5.6.0 N1-031326 2003-09 NP-21 NP-030412 449 1 Nework authentication failure at the UE 5.5.0 5.6.0 N1-031242 2003-09 NP-21 NP-030412 451 3 Handling of security association 5.5.0 5.6.0 N1-031327 2003-09 NP-21 NP-030412 452 1 Re-authentication timer at S-CSCF 5.5.0 5.6.0 N1-031274 2003-09 NP-21 NP-030412 455 2 Authentication failure at S-CSCF 5.5.0 5.6.0 N1-031285 2003-09 NP-21 NP-030413 456 2 Subscription termination sent by the S-CSCF 5.5.0 5.6.0 N1-031276 2003-09 NP-21 NP-030413 457 Subscription termination at the P-CSCF 5.5.0 5.6.0 N1-031032 2003-09 NP-21 NP-030413 458 Network -initiated deregistration at P-CSCF 5.5.0 5.6.0 N1-031033 2003-09 NP-21 NP-030349 459 2 Notification about registration status at AS 5.5.0 5.6.0 2003-09 NP-21 NP-030413 461 1 Service profile 5.5.0 5.6.0 N1-031233 2003-09 NP-21 NP-030413 466 1 Requirements on Preconditions 5.5.0 5.6.0 N1-031246 2003-09 NP-21 NP-030413 467 1 Call forwarding cleanup 5.5.0 5.6.0 N1-031238 2003-09 NP-21 NP-030413 468 Update of references 5.5.0 5.6.0 N1-031094 2003-09 NP-21 NP-030414 470 1 Adding P-Asserted-Identity headers to NE initiated subscriptions 5.5.0 5.6.0 N1-031314 2003-09 NP-21 NP-030414 479 1 Replace USIM by ISIM for user identity storage 5.5.0 5.6.0 N1-031247 2003-09 NP-21 NP-030414 481 1 24.229 R5 CR: Corrections to Profile Tables 5.5.0 5.6.0 N1-031248 2003-09 NP-21 NP-030414 482 24.229 R5 CR: Setting of SUBSCRIBE exipiration time 5.5.0 5.6.0 N1-031140 2003-09 NP-21 NP-030414 483 3 24.229 R5 CR: Alignment of IMS Compression with RFC 3486 5.5.0 5.6.0 N1-031335 2003-09 NP-21 NP-030418 465 1 Alignment with TS for policy control over Gq interface 5.6.0 6.0.0 N1-031267 2003-09 NP-21 NP-030418 472 1 I-CSCF procedures for openness 5.6.0 6.0.0 N1-031304 2003-09 NP-21 NP-030433 473 3 Registration from multiple terminals and forking 5.6.0 6.0.0 2003-09 NP-21 NP-030419 480 3 Access Independent IMS 5.6.0 6.0.0 N1-031333 2003-12 NP-22 NP-030482 487 1 Registration amendments in profile 6.0.0 6.1.0 N1-031627 2003-12 NP-22 NP-030482 489 Privacy considerations for the UE 6.0.0 6.1.0 N1-031351 2003-12 NP-22 NP-030476 493 INVITE dialog amendments in profile 6.0.0 6.1.0 N1-031359 2003-12 NP-22 NP-030482 494 Correction of I-CSCF handling of multiple private user identities with same public user identity 6.0.0 6.1.0 N1-031375 2003-12 NP-22 NP-030476 496 1 P-Asserted-Identity in SUBSCRIBE requests 6.0.0 6.1.0 N1-031632 2003-12 NP-22 NP-030482 497 Addition of reference to Gq interface 6.0.0 6.1.0 N1-031378 2003-12 NP-22 NP-030476 503 2 Update of HSS information at deregistration 6.0.0 6.1.0 N1-031720 2003-12 NP-22 NP-030482 507 Unavailable definitions 6.0.0 6.1.0 N1-031392 2003-12 NP-22 NP-030476 509 Reference corrections 6.0.0 6.1.0 N1-031394 2003-12 NP-22 NP-030484 510 1 UICC related changes for IMS commonality and interoperability 6.0.0 6.1.0 N1-031682 2003-12 NP-22 NP-030484 511 Interoperability and commonality; definition of scope 6.0.0 6.1.0 N1-031427 2003-12 NP-22 NP-030484 512 Interoperability and commonality; addition of terminology 6.0.0 6.1.0 N1-031428 2003-12 NP-22 NP-030484 513 Interoperability and commonality; media grouping 6.0.0 6.1.0 N1-031429 2003-12 NP-22 NP-030484 515 Interoperability and commonality; charging information 6.0.0 6.1.0 N1-031431 2003-12 NP-22 NP-030482 518 1 Profile support of RFC 3326: The Reason Header Field for the Session Initiation Protocol 6.0.0 6.1.0 N1-031681 2003-12 NP-22 NP-030482 519 Profile support of RFC 3581: An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing 6.0.0 6.1.0 N1-031439 2003-12 NP-22 NP-030484 522 1 Clause 9 restructuring 6.0.0 6.1.0 N1-031684 2003-12 NP-22 NP-030477 524 2 Correct use of RAND during re-synchronisation failures 6.0.0 6.1.0 N1-031712 2003-12 NP-22 NP-030478 526 1 Correction to description or RES/XRES usage 6.0.0 6.1.0 N1-031617 2003-12 NP-22 NP-030483 529 Corrections on charging specification number 6.0.0 6.1.0 N1-031469 2003-12 NP-22 NP-030581 531 3 Corrections on ICID for REGISTER 6.0.0 6.1.0 2003-12 NP-22 NP-030478 543 1 Correction of user initiated re-registration 6.0.0 6.1.0 N1-031619 2003-12 NP-22 NP-030483 551 1 IMS trust domain in Rel 6 6.0.0 6.1.0 N1-031622 2003-12 NP-22 NP-030478 556 1 P-CSCF and UE handling of Security Associations 6.0.0 6.1.0 N1-031624 2003-12 NP-22 NP-030483 560 2 SDP offer handling in SIP responses in S-CSCF and P-CSCF 6.0.0 6.1.0 N1-031727 2003-12 NP-22 NP-030483 564 1 SIP compression 6.0.0 6.1.0 N1-031705 2003-12 NP-22 NP-030478 566 Sending challenge 6.0.0 6.1.0 N1-031580 2003-12 NP-22 NP-030480 568 2 Reg-await-auth timer value 6.0.0 6.1.0 N1-031716 2003-12 NP-22 NP-030480 571 1 Network initiated deregistration 6.0.0 6.1.0 N1-031707 2003-12 NP-22 NP-030483 572 Text harmonisation with 3GPP2 6.0.0 6.1.0 N1-031589 2003-12 NP-22 NP-030483 573 1 Procedures in the absence of UICC 6.0.0 6.1.0 N1-031680 2003-12 NP-22 NP-030483 575 1 P-Access-Network-Info changes 6.0.0 6.1.0 N1-031683 2004-03 NP-23 NP-040027 488 3 Completion of major capabilities table in respect of privacy 6.1.0 6.2.0 N1-040406 2004-03 NP-23 NP-040027 499 5 P-CSCF integrity protection 6.1.0 6.2.0 N1-040500 2004-03 NP-23 NP-040032 578 1 UE requesting no-fork 6.1.0 6.2.0 N1-040184 2004-03 NP-23 NP-040032 579 1 Inclusion of caller preferences into profile 6.1.0 6.2.0 N1-040284 2004-03 NP-23 NP-040027 586 1 Network-initiated re-authentication 6.1.0 6.2.0 N1-040391 2004-03 NP-23 NP-040032 588 1 Re-authentication - Abnormal cases 6.1.0 6.2.0 N1-040393 2004-03 NP-23 NP-040027 592 1 Integrity protected correction 6.1.0 6.2.0 N1-040398 2004-03 NP-23 NP-040032 596 1 Sec-agree parameter in "Proxy-Require" header 6.1.0 6.2.0 N1-040400 2004-03 NP-23 NP-040027 600 2 Handling of record-route in target refresh and subsequent request 6.1.0 6.2.0 N1-040481 2004-03 NP-23 NP-040035 603 Cleanup for IP-CAN and GPRS 6.1.0 6.2.0 N1-040304 2004-03 NP-23 NP-040032 604 Forking in S-CSCF 6.1.0 6.2.0 N1-040325 2004-03 NP-23 NP-040108 605 3 Determination of S-CSCF role 6.1.0 6.2.0 2004-03 NP-23 NP-040134 608 3 Unprotected deregistration 6.1.0 6.2.0 2004-03 NP-23 NP-040029 610 Sending authentication challenge 6.1.0 6.2.0 N1-040331 2004-03 NP-23 NP-040033 613 Reference to PDF operation 6.1.0 6.2.0 N1-040334 2004-03 NP-23 NP-040029 615 1 Support of MESSAGE (Profile Tables) 6.1.0 6.2.0 N1-040466 2004-03 NP-23 NP-040033 616 2 Introduction of PSI Routing to 24.229 6.1.0 6.2.0 N1-040487 2004-03 NP-23 NP-040033 617 1 P-CSCF Re-selection 6.1.0 6.2.0 N1-040463 2004-03 NP-23 NP-040033 618 I-CSCF does not re-select S-CSCF during re-registration 6.1.0 6.2.0 N1-040344 2004-03 NP-23 NP-040033 620 1 Handling of media authorization token due to messaging 6.1.0 6.2.0 N1-040430 2004-06 NP-24 NP-040191 621 2 Forking requests terminating at the served user 6.2.0 6.3.0 N1-040739 2004-06 NP-24 NP-040191 624 1 Abbreviations 6.2.0 6.3.0 N1-040691 2004-06 NP-24 NP-040191 625 5 Removal of restriction for multiple SIP sessions on a single PDP context 6.2.0 6.3.0 N1-041053 2004-06 NP-24 NP-040191 626 3 Record route in S-CSCF 6.2.0 6.3.0 N1-041061 2004-06 NP-24 NP-040189 627 3 Correction of reception of media authorization token 6.2.0 6.3.0 N1-040994 2004-06 NP-24 NP-040191 628 3 Introduction of PSI Routing to 24.229 6.2.0 6.3.0 N1-041059 2004-06 NP-24 NP-040198 629 2 Addition of PRESNC material 6.2.0 6.3.0 N1-040996 2004-06 NP-24 NP-040189 631 1 Missing statements regarding P-Charging-Function-Addresses header 6.2.0 6.3.0 N1-040987 2004-06 NP-24 NP-040191 634 1 Multiple registrations 6.2.0 6.3.0 N1-041054 2004-06 NP-24 NP-040192 635 1 Network-initiated deregistration 6.2.0 6.3.0 N1-041055 2004-06 NP-24 NP-040192 636 Network-initiated re-authentication 6.2.0 6.3.0 N1-040778 2004-06 NP-24 NP-040192 637 1 Mobile-initiated deregistration 6.2.0 6.3.0 N1-041056 2004-06 NP-24 NP-040192 638 1 Notification about registration state 6.2.0 6.3.0 N1-041057 2004-06 NP-24 NP-040189 642 3 Syntax of the extension to the P-Charging-Vector header field 6.2.0 6.3.0 N1-041100 2004-06 NP-24 NP-040192 643 2 Session Timer 6.2.0 6.3.0 N1-041095 2004-06 NP-24 NP-040193 644 3 Session initiation without preconditions 6.2.0 6.3.0 N1-041096 2004-06 NP-24 NP-040192 645 1 IMS Conferencing: Inclusion of Profile Tables to TS 24.229 6.2.0 6.3.0 N1-041015 2004-06 NP-24 NP-040189 649 1 Revisions due to published version of draft-ietf-sipping-reg-event 6.2.0 6.3.0 N1-040992 2004-06 NP-24 NP-040198 652 Creation of separate event package table for UA role 6.2.0 6.3.0 N1-041066 2004-09 NP-25 NP-040380 658 Correction of User identity verification at the AS 6.3.0 6.4.0 N1-041344 2004-09 NP-25 NP-040381 666 1 NOTIFY requests 6.3.0 6.4.0 N1-041586 2004-09 NP-25 NP-040381 654 4 Callee capabilities and Registration 6.3.0 6.4.0 N1-041315 2004-09 NP-25 NP-040381 668 2 Network deregistration 6.3.0 6.4.0 N1-041614 2004-09 NP-25 NP-040381 682 1 SDP parameters received by the S-CSCF and the P-CSCF in the 200 OK message 6.3.0 6.4.0 N1-041592 2004-09 NP-25 NP-040381 661 1 Call Release 6.3.0 6.4.0 N1-041589 2004-09 NP-25 NP-040381 659 Multiple public ID registration 6.3.0 6.4.0 N1-041350 2004-09 NP-25 NP-040381 660 Standalone transactions 6.3.0 6.4.0 N1-041351 2004-09 NP-25 NP-040381 663 Unprotected REGISTER 6.3.0 6.4.0 N1-041354 2004-09 NP-25 NP-040381 662 1 Session timer 6.3.0 6.4.0 N1-041590 2004-09 NP-25 NP-040381 665 Contact in SUBSCRIBE request 6.3.0 6.4.0 N1-041372 2004-09 NP-25 NP-040381 650 2 Support of draft-ietf-sip-replaces 6.3.0 6.4.0 N1-041391 2004-09 NP-25 NP-040381 657 1 Support of draft-ietf-sip-join 6.3.0 6.4.0 N1-041393 2004-09 NP-25 NP-040381 656 1 Support of draft-ietf-sip-referredby 6.3.0 6.4.0 N1-041263 2004-09 NP-25 NP-040381 678 Support of TLS 6.3.0 6.4.0 N1-041462 2004-09 NP-25 NP-040381 688 2 Filtering of the P-Access-Network-Info header by the S-CSCF and privacy rules 6.3.0 6.4.0 N1-041641 2004-09 NP-25 NP-040382 692 2 Ipv6 IPv4 interworking 6.3.0 6.4.0 N1-041630 2004-09 NP-25 NP-040383 689 2 Addition of session set-up not requiring preconditions and reliable transport of provisional responses. 6.3.0 6.4.0 N1-041632 2004-09 NP-25 NP-040385 697 Missing value for the event attribute within the <contact> element of NOTIFY body 6.3.0 6.4.0 N1-041540 2004-09 NP-25 NP-040385 698 HSS initiated deregistration 6.3.0 6.4.0 N1-041549 2004-09 NP-25 NP-040385 673 Syntax correction for the P-Charging-Vector header 6.3.0 6.4.0 N1-041434 2004-09 NP-25 NP-040385 699 1 Network initiated deregistration upon UE roaming and registration to a new network 6.3.0 6.4.0 N1-041629 2004-12 NP-26 NP-040506 651 4 Downloading the user profile based on User-Data-Request-Type 6.4.0 6.5.0 N1-042031 2004-12 NP-26 NP-040506 703 2 SDP Encryption 6.4.0 6.5.0 N1-042095 2004-12 NP-26 NP-040506 704 1 RTCP streams 6.4.0 6.5.0 N1-042019 2004-12 NP-26 NP-040506 709 Contact in 200(OK) response 6.4.0 6.5.0 N1-041725 2004-12 NP-26 NP-040506 710 1 P-Access-Network-Info header 6.4.0 6.5.0 N1-042020 2004-12 NP-26 NP-040506 711 1 P-Called-Party-ID header 6.4.0 6.5.0 N1-041954 2004-12 NP-26 NP-040506 713 1 IMS-ALG routing 6.4.0 6.5.0 N1-042021 2004-12 NP-26 NP-040506 714 1 Public User Identity 6.4.0 6.5.0 N1-042022 2004-12 NP-26 NP-040506 715 1 "Pres" and "im" URIs 6.4.0 6.5.0 N1-042023 2004-12 NP-26 NP-040502 723 1 Correction Term IOI handling 6.4.0 6.5.0 N1-041956 2004-12 NP-26 NP-040502 725 1 Request handling in S-CSCF originating case 6.4.0 6.5.0 N1-041958 2004-12 NP-26 NP-040502 727 1 Request handling in S-CSCF - terminating case 6.4.0 6.5.0 N1-041960 2004-12 NP-26 NP-040506 728 SBLP and non-realtime PDP contexts 6.4.0 6.5.0 N1-041797 2004-12 NP-26 NP-040590 730 2 Reference updates 6.4.0 6.5.0 N1-042085 2004-12 NP-26 NP-040590 733 3 Support for extended SigComp 6.4.0 6.5.0 N1-042117 2004-12 NP-26 NP-040590 734 2 Correction to subclause 5.1.3 of TS 24,229 6.4.0 6.5.0 N1-042120 2004-12 NP-26 NP-040590 735 1 Correction to subclause 5.1.4.1.2.3 of TS 24,.229 6.4.0 6.5.0 N1-042084 2004-12 NP-26 NP-040502 738 1 Population of Via header when using REGISTER method 6.4.0 6.5.0 N1-041962 2004-12 NP-26 NP-040590 739 Tel-URI related reference updates 6.4.0 6.5.0 N1-041869 2004-12 NP-26 NP-040590 741 1 Throttling 6.4.0 6.5.0 N1-042086 2004-12 NP-26 NP-040590 742 Editorial correction resulting from CR665 6.4.0 6.5.0 N1-041881 2004-12 NP-26 NP-040590 743 Unprotected REGISTER corrections 6.4.0 6.5.0 N1-041882 2004-12 NP-26 NP-040590 744 1 Corrections to receiving SDP offer in 200 (OK) response 6.4.0 6.5.0 N1-042087 2004-12 NP-26 NP-040590 745 1 Privacy corrections 6.4.0 6.5.0 N1-042085 2004-12 NP-26 NP-040590 747 2 Syntax of the P-Charging-Vector 6.4.0 6.5.0 N1-042105 2004-12 NP-26 NP-040590 752 2 Unavailability of the access-network-charging-info when the session is established without SBLP 6.4.0 6.5.0 N1-042106 2004-12 NP-26 NP-040590 753 1 SIP messages carrying the access-network-charging-info for sessions without preconditions 6.4.0 6.5.0 N1-042089 2004-12 NP-26 NP-040590 755 1 Network-initiated deregistration for multiple UEs sharing the same user public identity and for the old contact information of a roaming UE registered in a new network 6.4.0 6.5.0 N1-042090 2004-12 NP-26 NP-040502 765 1 Interaction between S-CSCF and HSS in Network initiated deregistration procedure 6.4.0 6.5.0 N1-041966 2004-12 NP-26 NP-040502 768 1 Downloading of user profile 6.4.0 6.5.0 N1-042103 2005-01 Fix Word problem 6.5.0 6.5.1 2005-03 NP-27 NP-050069 839 Filter criteria matching and generation of third-party REGISTER request for network-initiated deregistration 5.11.1 5.12.0 N1-050220 2005-03 NP-27 NP-050069 785 Deregistration effect on active sessions 6.5.1 6.6.0 N1-050052 2005-03 NP-27 NP-050069 784 Deregistration effect on active sessions 5.11.1 5.12.0 N1-050051 2005-03 NP-27 NP-050069 809 1 IOI storage at MGCF 5.11.1 5.12.0 N1-050295 2005-03 NP-27 NP-050069 840 Filter criteria matching and generation of third-party REGISTER request for network-initiated deregistration 6.5.1 6.6.0 N1-050221 2005-03 NP-27 NP-050069 806 1 Use of original dialog identifier at AS 6.5.1 6.6.0 N1-050292 2005-03 NP-27 NP-050069 807 2 Checking Request-URI for terminating requests at the S-CSCF 5.11.1 5.12.0 N1-050401 2005-03 NP-27 NP-050069 805 1 Use of original dialog identifier at AS 5.11.1 5.12.0 N1-050291 2005-03 NP-27 NP-050069 808 2 Checking Request-URI for terminating requests at the S-CSCF 6.5.1 6.6.0 N1-050402 2005-03 NP-27 NP-050069 810 1 IOI storage at MGCF 6.5.1 6.6.0 N1-050296 2005-03 NP-27 NP-050073 794 RFC 3966 6.5.1 6.6.0 N1-050080 2005-03 NP-27 NP-050073 848 1 Removal of I-CSCF normative requirement on Cx interface 6.5.1 6.6.0 N1-050299 2005-03 NP-27 NP-050073 841 Filtering of the P-Access-Network-Info header by the S-CSCF and privacy rules 6.5.1 6.6.0 N1-050225 2005-03 NP-27 NP-050073 817 Editorial corrections 6.5.1 6.6.0 N1-050129 2005-03 NP-27 NP-050073 786 1 Cleanups resulting from CR changes for last version 6.5.1 6.6.0 N1-050324 2005-03 NP-27 NP-050073 821 1 Handling topmost Route header at the P-CSCF 6.5.1 6.6.0 N1-050297 2005-03 NP-27 NP-050073 790 Registration - Abnormal Case 6.5.1 6.6.0 N1-050076 2005-03 NP-27 NP-050074 832 1 Corrections to the tables for 'PUBLISH' 6.5.1 6.6.0 N1-050341 2005-03 NP-27 NP-050074 822 1 Corrections to the UE tables for 'major capabilities' 6.5.1 6.6.0 N1-050332 2005-03 NP-27 NP-050074 825 1 Corrections to the UE tables for 'ACK' 6.5.1 6.6.0 N1-050334 2005-03 NP-27 NP-050074 826 1 Corrections to the tables for 'CANCEL' 6.5.1 6.6.0 N1-050335 2005-03 NP-27 NP-050074 827 1 Corrections to the tables for 'INVITE' 6.5.1 6.6.0 N1-050336 2005-03 NP-27 NP-050074 828 1 Corrections to the tables for 'MESSAGE' 6.5.1 6.6.0 N1-050337 2005-03 NP-27 NP-050074 829 1 Corrections to the tables for 'NOTIFY' 6.5.1 6.6.0 N1-050338 2005-03 NP-27 NP-050074 830 1 Corrections to the tables for 'OPTIONS' 6.5.1 6.6.0 N1-050339 2005-03 NP-27 NP-050074 834 1 Corrections to the tables for 'REGISTER' 6.5.1 6.6.0 N1-050343 2005-03 NP-27 NP-050074 831 1 Corrections to the tables for 'PRACK' 6.5.1 6.6.0 N1-050340 2005-03 NP-27 NP-050074 833 1 Corrections to the tables for 'REFER' 6.5.1 6.6.0 N1-050342 2005-03 NP-27 NP-050074 835 1 Corrections to the tables for 'SUBSCRIBE' 6.5.1 6.6.0 N1-050344 2005-03 NP-27 NP-050074 836 1 Corrections to the tables for 'UPDATE' 6.5.1 6.6.0 N1-050345 2005-03 NP-27 NP-050074 837 1 Corrections to the tables for SDP 6.5.1 6.6.0 N1-050346 2005-03 NP-27 NP-050074 824 1 Removal of the UE table for 'status codes' 6.5.1 6.6.0 N1-050351 2005-03 NP-27 NP-050074 823 1 Corrections to the tables for 'BYE' 6.5.1 6.6.0 N1-050333 2005-03 NP-27 NP-050075 846 2 Correction to the Registration procedure 6.5.1 6.6.0 N1-050413 2005-03 NP-27 NP-050075 850 1 Addition of IMS-ALF to profile tables 6.5.1 6.6.0 N1-050348 2005-03 NP-27 NP-050075 851 2 Press and im URIs in incoming requests 6.5.1 6.6.0 N1-050395 2005-03 NP-27 NP-050075 788 1 MO - Calls to IPv4 SIP terminals 6.5.1 6.6.0 N1-050387 2005-03 NP-27 NP-050075 818 3 Corrections to subclause 5.5 in TS 24.229 6.5.1 6.6.0 N1-050414 2005-03 NP-27 NP-050075 801 3 Default handling associated with the trigger at the S-CSCF 6.5.1 6.6.0 N1-050418 2005-03 NP-27 NP-050075 803 4 Default handling associated with the trigger for third party registration 6.5.1 6.6.0 N1-050421 2005-03 NP-27 NP-050078 795 1 Sip-profile package in major capabilities 6.5.1 6.6.0 N1-050306 2005-03 NP-27 NP-050127 849 2 Corrections to addition of session set-up not requiring preconditions and reliable transport of provisional responses 6.5.1 6.6.0 2005-06 CP-28 CP-050059 879 Correction Reg-Await-Auth Timer 6.6.0 6.7.0 C1-050522 2005-06 CP-28 CP-050059 881 Security Association in P-CSCF 6.6.0 6.7.0 C1-050524 2005-06 CP-28 CP-050059 871 1 Port 5060 6.6.0 6.7.0 C1-050674 2005-06 CP-28 CP-050059 891 2 SIP headers storage for P-CSCF initiated session release 6.6.0 6.7.0 C1-050777 2005-06 CP-28 CP-050059 921 1 Correction of error in the specification of the extension to Authorization header 6.6.0 6.7.0 C1-050689 2005-06 CP-28 CP-050059 886 2 Handling of P-Associated URI header 6.6.0 6.7.0 C1-050783 2005-06 CP-28 CP-050059 907 2 Clarification to the procedures at the I-CSCF 6.6.0 6.7.0 C1-050785 2005-06 CP-28 CP-050061 894 1 Re-registration failure 6.6.0 6.7.0 C1-050709 2005-06 CP-28 CP-050061 892 Completion of status-code tables in SIP profile 6.6.0 6.7.0 C1-050571 2005-06 CP-28 CP-050061 865 1 Unsubscribe by P-CSCF 6.6.0 6.7.0 C1-050671 2005-06 CP-28 CP-050061 866 1 Protected initial registration 6.6.0 6.7.0 C1-050708 2005-06 CP-28 CP-050061 916 1 Clarify that S-CSCF shall support Supported and Require headers 6.6.0 6.7.0 C1-050684 2005-06 CP-28 CP-050061 862 Shared public user identities 6.6.0 6.7.0 C1-050599 2005-06 CP-28 CP-050061 860 1 P-CSCF - routing of REGISTER requests 6.6.0 6.7.0 C1-050701 2005-06 CP-28 CP-050061 870 1 Correction of table A.104A 6.6.0 6.7.0 C1-050711 2005-06 CP-28 CP-050061 887 1 Contact address in REGISTER response 6.6.0 6.7.0 C1-050716 2005-06 CP-28 CP-050061 890 1 P-CSCF Record-Route processing for target refresh requests/responses 6.6.0 6.7.0 C1-050717 2005-06 CP-28 CP-050061 893 1 AS originated requests on behalf of PSI 6.6.0 6.7.0 C1-050719 2005-06 CP-28 CP-050061 896 1 Routing PSI at terminating side 6.6.0 6.7.0 C1-050720 2005-06 CP-28 CP-050061 856 2 Notification about registration state 6.6.0 6.7.0 C1-050789 2005-06 CP-28 CP-050061 861 3 Registration failure at UE 6.6.0 6.7.0 C1-050790 2005-06 CP-28 CP-050061 899 2 Correction of the references for the integration of resource management procedures 6.6.0 6.7.0 C1-050791 2005-06 CP-28 CP-050061 902 2 Clarification on P-CSCF-intiated call release 6.6.0 6.7.0 C1-050792 2005-06 CP-28 CP-050061 863 3 Error handling in UE in case of RFC 3524 6.6.0 6.7.0 C1-050793 2005-06 CP-28 CP-050061 895 3 UE registration failure because the selected S-CSCF is unreachable 6.6.0 6.7.0 C1-050802 2005-06 CP-28 CP-050061 787 6 MT- SDP offer with IPv4 address. 6.6.0 6.7.0 C1-050794 2005-06 CP-28 CP-050061 858 1 S-CSCF redirecting 6.6.0 6.7.0 C1-050700 2005-06 CP-28 CP-050064 872 2 I-WLAN information for IMS 6.6.0 6.7.0 C1-050729 2005-06 CP-28 CP-050074 901 MWI RFC3842 6.6.0 7.0.0 C1-050600 2005-06 CP-28 CP-050075 905 1 3xx response and non-SDP bodies handking by proxies 6.6.0 7.0.0 C1-050775 2005-09 CP-29 CP-050346 986 Modifications to 24.229 to allow multiple IPsec security association per IKE_Security association 7.0.0 7.1.0 2005-09 CP-29 CP-050355 930 1 Correction Profile Table A.119 7.0.0 7.1.0 C1-051061 2005-09 CP-29 CP-050355 946 Public User identity in 3rd party REG 7.0.0 7.1.0 C1-050906 2005-09 CP-29 CP-050355 957 1 Removal of Access Network Charging Information by the S-CSCF 7.0.0 7.1.0 C1-051081 2005-09 CP-29 CP-050355 965 Optional ccf 7.0.0 7.1.0 C1-050986 2005-09 CP-29 CP-050355 969 1 Contact header in REGISTER requests 7.0.0 7.1.0 C1-051177 2005-09 CP-29 CP-050359 932 SigComp-Corrections 7.0.0 7.1.0 C1-050877 2005-09 CP-29 CP-050359 962 1 IETF reference corrections 7.0.0 7.1.0 C1-051074 2005-09 CP-29 CP-050359 968 1 AS procedure correction 7.0.0 7.1.0 C1-051085 2005-09 CP-29 CP-050367 924 Incorporation of draft-ietf-sip-history 7.0.0 7.1.0 C1-050838 2005-09 CP-29 CP-050367 938 Contact header 7.0.0 7.1.0 C1-050887 2005-09 CP-29 CP-050367 939 1 Reason header - loss of radio coverage 7.0.0 7.1.0 C1-051158 2005-09 CP-29 CP-050367 947 3 Changes to TS 24.229 to ease interworking with non precondition terminals 7.0.0 7.1.0 C1-051213 2005-09 CP-29 CP-050367 958 2 Contents of P-Associated-URI header in 200 (OK) response to REGISTER 7.0.0 7.1.0 C1-051206 2005-09 CP-29 CP-050367 960 3 Consideration on 3rd Party Service Provider in Trust Domain 7.0.0 7.1.0 C1-051208 2005-09 CP-29 CP-050367 971 1 Correction of requirement to insert P-Asserted-Identity header 7.0.0 7.1.0 C1-051166 2005-09 CP-29 CP-050368 950 3 privacy and trust rules for History header 7.0.0 7.1.0 C1-051199 2005-10 missing word in subclause 5.4.1.2.2, bullet 10b) is added by MCC 7.1.0 7.1.1 2005-12 CP-30 CP-050538 1049 Replace "originated" with "terminated" 7.1.1 7.2.0 C1-051479 2005-12 CP-30 CP-050538 1046 2 Mobile originating call related requests 7.1.1 7.2.0 C1-051668 2005-12 CP-30 CP-050538 1012 1 Correction to section 5.4.3.2 t of TS 24.229 7.1.1 7.2.0 C1-051563 2005-12 CP-30 CP-050538 1026 Handling of P-Charging-Function-Adress 7.1.1 7.2.0 C1-051424 2005-12 CP-30 CP-050538 1071 Correction Syntax P-Charging Vector 7.1.1 7.2.0 C1-051508 2005-12 CP-30 CP-050541 1002 1 Modification to the definition of Security Association 7.1.1 7.2.0 C1-051576 2005-12 CP-30 CP-050542 0982 3 Access Type of P-Access-Network-Info header 7.1.1 7.2.0 C1-051675 2005-12 CP-30 CP-050542 1059 Replace "served" by "Originating" UE 7.1.1 7.2.0 C1-051489 2005-12 CP-30 CP-050542 1017 Correction to subclause 5.7.5.1. of TS 24229 7.1.1 7.2.0 C1-051382 2005-12 CP-30 CP-050542 1073 2 Short Session Setup in IMS 7.1.1 7.2.0 C1-051656 2005-12 CP-30 CP-050542 1054 Adjusting section reference in section 6.3 7.1.1 7.2.0 C1-051484 2005-12 CP-30 CP-050542 1029 1 B2B UA AS handling 7.1.1 7.2.0 C1-041597 2005-12 CP-30 CP-050542 1062 2 Correction to 3rd party registration procedures for SESSION_TERMINATED default handling 7.1.1 7.2.0 C1-051672 2005-12 CP-30 CP-050542 0994 cdma2000 7.1.1 7.2.0 C1-051336 2005-12 CP-30 CP-050542 1043 Correction of a reference in some tables in Appendix A 7.1.1 7.2.0 C1-051473 2005-12 CP-30 CP-050542 1005 2 Refreshes of SUBSCRIBE to reg-event (Fix for Rel 7) 7.1.1 7.2.0 C1-051670 2005-12 CP-30 CP-050542 1065 1 Charging terms correction 7.1.1 7.2.0 C1-051618 2005-12 CP-30 CP-050548 1081 Change of originating and terminating terminal terminology 7.1.1 7.2.0 C1-051535 2005-12 CP-30 CP-050548 1069 2 IBCF 7.1.1 7.2.0 C1-051587 2005-12 CP-30 CP-050550 1055 Editorial Changes 7.1.1 7.2.0 C1-051485 2005-12 CP-30 CP-050550 0996 1 UE initiated deregistration 7.1.1 7.2.0 C1-051649 2005-12 CP-30 CP-050550 1027 1 Mobile originated Request for unregistered user 7.1.1 7.2.0 C1-051653 2005-12 CP-30 CP-050550 0990 1 Authentication related Clarification 7.1.1 7.2.0 C1-051560 2005-12 CP-30 CP-050550 1019 2 Receipt of SIP URI with user equal phone at I-CSCF 7.1.1 7.2.0 C1-051671 2005-12 CP-30 CP-050550 0995 2 Default public user ID 7.1.1 7.2.0 C1-051691 2005-12 CP-30 CP-050550 0997 1 P-Preferred-Identity header 7.1.1 7.2.0 C1-051650 2005-12 CP-30 CP-050550 1082 1 P-CSCF discovery 7.1.1 7.2.0 C1-051681 2005-12 CP-30 CP-050677 1085 2 Incorporating of TR 24.819 fixed broadband access impacts into TS 24.229 7.1.1 7.2.0 2006-03 CP-31 CP-060106 1187 - Removal of Warning header non-compliance with RFC 3261 7.2.0 7.3.0 C1-060328 2006-03 CP-31 CP-060106 1117 1 IMS AKA - SQN resync clarifications 7.2.0 7.3.0 C1-060453 2006-03 CP-31 CP-060106 1114 1 IMS AKA - content of initial authentication header 7.2.0 7.3.0 C1-060450 2006-03 CP-31 CP-060106 1204 - Syntax and operation for Security-Client, Security-Server and Security-Verify headers 7.2.0 7.3.0 C1-060387 2006-03 CP-31 CP-060107 1148 1 UE processing 305 (Use Proxy) 7.2.0 7.3.0 C1-060507 2006-03 CP-31 CP-060107 1164 1 Clarifications on P-CSCF discovery 7.2.0 7.3.0 C1-060459 2006-03 CP-31 CP-060107 1161 1 DHCPv6 options for Domain Name Servers 7.2.0 7.3.0 C1-060456 2006-03 CP-31 CP-060110 1136 1 SDP answer 7.2.0 7.3.0 C1-060472 2006-03 CP-31 CP-060110 1206 - Inclusion of Ma reference point 7.2.0 7.3.0 C1-060392 2006-03 CP-31 CP-060110 1134 - Preconditions required 7.2.0 7.3.0 C1-060192 2006-03 CP-31 CP-060110 1156 1 Tables Change in Appendix A 7.2.0 7.3.0 C1-060478 2006-03 CP-31 CP-060110 1132 1 P-Asserted-Identity 7.2.0 7.3.0 C1-060476 2006-03 CP-31 CP-060111 1219 - Reference Update of TS24.229, Rel7 7.2.0 7.3.0 C1-060483 2006-03 CP-31 CP-060111 1119 2 IMS Short Session Setup - Clarifications 7.2.0 7.3.0 C1-060595 2006-03 CP-31 CP-060111 1189 3 Definition of principles for IOI exchange and storage 7.2.0 7.3.0 C1-060610 2006-03 CP-31 CP-060111 1129 2 Tel URI 7.2.0 7.3.0 C1-060593 2006-03 CP-31 CP-060117 1210 1 Coding of P-Access-Network-Info header for 3GPP2 IMS 7.2.0 7.3.0 C1-060494 2006-03 CP-31 CP-060118 1103 1 Editor's Note on xDSL bearer 7.2.0 7.3.0 C1-060119 2006-03 CP-31 CP-060118 1095 1 Reference to new annexes on NAT 7.2.0 7.3.0 C1-060116 2006-03 CP-31 CP-060118 1101 - Replaces header in Profile Tables 7.2.0 7.3.0 C1-060051 2006-03 CP-31 CP-060118 1093 2 P-Access-Network-Info header absence for emergency call detection 7.2.0 7.3.0 C1-060339 2006-03 CP-31 CP-060118 1196 1 correction for the procedure of changing media data 7.2.0 7.3.0 C1-060518 2006-03 CP-31 CP-060118 1197 1 Editorial Changes 7.2.0 7.3.0 C1-060519 2006-03 CP-31 CP-060118 1092 3 Optionality of P-Access-Network-Info header 7.2.0 7.3.0 C1-060338 2006-03 CP-31 CP-060118 1086 1 Addition of TISPAN supported internet-drafts 7.2.0 7.3.0 C1-060337 2006-03 CP-31 CP-060118 1089 1 IBCF corrections 7.2.0 7.3.0 C1-060110 2006-03 CP-31 CP-060118 1106 4 Completion of IBCF routing procedures 7.2.0 7.3.0 C1-060498 2006-03 CP-31 CP-060118 1088 4 IBCF enhancements 7.2.0 7.3.0 C1-060603 2006-03 CP-31 CP-060119 1177 1 PacketCable Extensions to P-Charging-Vector header 7.2.0 7.3.0 C1-060512 2006-03 CP-31 CP-060120 1098 4 Emergency service S-CSCF impact 7.2.0 7.3.0 C1-060601 2006-03 CP-31 CP-060120 1097 5 Emergency service - P-CSCF impact 7.2.0 7.3.0 C1-060600 2006-03 CP-31 CP-060120 1099 5 Emergency service - E-CSCF impact 7.2.0 7.3.0 C1-060599 2006-03 CP-31 CP-060120 1096 5 Emergency service - UE impact 7.2.0 7.3.0 C1-060602 2006-03 CP-31 CP-060121 1183 - Transfer of Text from the Combinational Services TR 24.879 to TS 24.229 7.2.0 7.3.0 C1-060311 2006-03 CP-31 CP-060124 1138 2 Session termination by P-CSCF 7.2.0 7.3.0 C1-060605 2006-03 CP-31 CP-060124 1157 3 Support for RFC 4145 7.2.0 7.3.0 C1-060621 2006-03 CP-31 CP-060124 1184 3 Registration of multiple PUIs - CR 7.2.0 7.3.0 C1-060608 2006-03 CP-31 CP-060124 1137 1 Session termination by S-CSCF 7.2.0 7.3.0 C1-060533 2006-03 CP-31 CP-060124 1152 1 Editorial Changes 7.2.0 7.3.0 C1-060539 2006-03 CP-31 CP-060124 1107 1 Reference Update of TS24.229 7.2.0 7.3.0 C1-060123 2006-03 CP-31 CP-060124 1125 - Pre-loaded Route header 7.2.0 7.3.0 C1-060183 2006-03 CP-31 CP-060142 1226 1 Transport of HSS address from I-CSCF to S-CSCF 7.2.0 7.3.0 - 2006-03 CP-31 CP-060153 1222 2 Mandationof RFC 4320 fixes for issues found with the Session Initiation Protocol's (SIP) Non-INVITE Transactions 7.2.0 7.3.0 - 2006-03 CP-31 CP-060176 1225 2 Support of call forwarding at the S-CSCF 7.2.0 7.3.0 - 2006-06 CP-32 CP-060232 1290 2 Realm Parameter Handling 7.3.0 7.4.0 2006-06 CP-32 CP-060249 1242 3 SDP answer 7.3.0 7.4.0 2006-06 CP-32 CP-060262 1309 2 Hiding correction 7.3.0 7.4.0 C1-061115 2006-06 CP-32 CP-060262 1306 2 3rd-party registration 7.3.0 7.4.0 C1-061098 2006-06 CP-32 CP-060262 1303 1 One private identity one contact 7.3.0 7.4.0 C1-061095 2006-06 CP-32 CP-060264 1274 2 Re-authentication during deregistration 7.3.0 7.4.0 C1-061113 2006-06 CP-32 CP-060265 1312 I-CSCF registration procedure correction 7.3.0 7.4.0 C1-060829 2006-06 CP-32 CP-060266 1265 1 IOI overview 7.3.0 7.4.0 C1-060997 2006-06 CP-32 CP-060266 1271 1 Introduction of signalling encryption 7.3.0 7.4.0 C1-060999 2006-06 CP-32 CP-060266 1348 UE behavior after timer F expiry 7.3.0 7.4.0 C1-060897 2006-06 CP-32 CP-060266 1236 2 P-Asserted-ID 7.3.0 7.4.0 C1-061119 2006-06 CP-32 CP-060266 1238 1 Via header in the initial registration 7.3.0 7.4.0 C1-060975 2006-06 CP-32 CP-060266 1327 1 Incorrect requirement on I-CSCF 7.3.0 7.4.0 C1-061079 2006-06 CP-32 CP-060270 1247 1 Emergency PUID 7.3.0 7.4.0 C1-061054 2006-06 CP-32 CP-060270 1266 1 Inclusion of draft-ietf-ecrit-service-urn 7.3.0 7.4.0 C1-061009 2006-06 CP-32 CP-060270 1229 Emergency service S-CSCF impact 7.3.0 7.4.0 C1-060642 2006-06 CP-32 CP-060270 1360 Inclusion of E-CSCF in subclause 3.1 and subclause 4.1 7.3.0 7.4.0 C1-060923 2006-06 CP-32 CP-060270 1249 2 Emergency call release 7.3.0 7.4.0 C1-061121 2006-06 CP-32 CP-060270 1338 1 Adding RDF in E-CSCF procedure 7.3.0 7.4.0 C1-061060 2006-06 CP-32 CP-060270 1358 1 Priority handling for emergency calls at the E-CSCF 7.3.0 7.4.0 C1-061017 2006-06 CP-32 CP-060270 1357 1 Priority handling for emergency calls at the S-CSCF 7.3.0 7.4.0 C1-061015 2006-06 CP-32 CP-060270 1356 1 Priority handling for emergency calls at the P-CSCF 7.3.0 7.4.0 C1-061013 2006-06 CP-32 CP-060270 1354 Inclusion of session timer procedures at the E-CSCF 7.3.0 7.4.0 C1-060917 2006-06 CP-32 CP-060270 1340 2 TEL URI associated with emergency IMPU 7.3.0 7.4.0 C1-061120 2006-06 CP-32 CP-060270 1337 1 Getting local emergency numbers 7.3.0 7.4.0 C1-061010 2006-06 CP-32 CP-060270 1336 1 Some corrections in IMS emergency calls 7.3.0 7.4.0 C1-061059 2006-06 CP-32 CP-060271 1258 1 UDP encapsulation of IPSec 7.3.0 7.4.0 C1-061019 2006-06 CP-32 CP-060271 1318 1 Extensions to P-Access-Network-Info header for DOCSIS Access 7.3.0 7.4.0 C1-061025 2006-06 CP-32 CP-060271 1317 2 PRACK 7.3.0 7.4.0 C1-061026 2006-06 CP-32 CP-060271 1267 1 IBCF corrections 7.3.0 7.4.0 C1-061022 2006-06 CP-32 CP-060271 1259 1 IBCF initiated call release 7.3.0 7.4.0 C1-061021 2006-06 CP-32 CP-060271 1345 1 Correction of the reference document 7.3.0 7.4.0 C1-061082 2006-06 CP-32 CP-060274 1234 1 Final NOTIFY 7.3.0 7.4.0 C1-060989 2006-06 CP-32 CP-060274 1255 Full notification 7.3.0 7.4.0 C1-060686 2006-06 CP-32 CP-060274 1260 Reg event package parameters in notification 7.3.0 7.4.0 C1-060704 2006-06 CP-32 CP-060274 1261 Subscription refreshing 7.3.0 7.4.0 C1-060705 2006-06 CP-32 CP-060274 1217 2 Definition of B2BUA 7.3.0 7.4.0 C1-061074 2006-06 CP-32 CP-060274 1277 1 Usage of associated public user identities 7.3.0 7.4.0 C1-060964 2006-06 CP-32 CP-060274 1321 Verification by I-CSCF of trust domain origin for incoming requests 7.3.0 7.4.0 C1-060844 2006-06 CP-32 CP-060274 1322 Miscellaneous Correction 7.3.0 7.4.0 C1-060845 2006-06 CP-32 CP-060274 1328 1 Resilience to registration and authentication errors 7.3.0 7.4.0 C1-061080 2006-06 CP-32 CP-060274 1335 1 The Correction on the description for the information of registration status 7.3.0 7.4.0 C1-060986 2006-06 CP-32 CP-060274 1361 Reference updates 7.3.0 7.4.0 C1-060924 2006-06 CP-32 CP-060283 1366 Emergency service – UE impact 7.3.0 7.4.0 2006-06 CP-32 CP-060284 1367 Emergency service- E-CSCF impact 7.3.0 7.4.0 2006-06 CP-32 CP-060335 1232 3 Handling of P-Charging-Addresses 7.3.0 7.4.0 2006-06 CP-32 CP-060345 1365 1 Registration of several unrelated public user identities 7.3.0 7.4.0 2006-06 CP-32 CP-060352 1228 4 Emergency service P-CSCF-impact 7.3.0 7.4.0 C1-061134 2006-09 CP-33 CP-060452 1461 1 Correction of Realm Parameter Handling for S-CSCF procedures 7.4.0 7.5.0 C1-061732 2006-09 CP-33 CP-060452 1467 SDP reference revision 7.4.0 7.5.0 C1-061657 2006-09 CP-33 CP-060452 1475 2 "Response" value in unprotected Register requests 7.4.0 7.5.0 C1-061845 2006-09 CP-33 CP-060463 1351 3 Treatment of emergency requests other than INVITE requests at the P-CSCF 7.4.0 7.5.0 C1-061357 2006-09 CP-33 CP-060463 1352 3 Treatment of emergency requests other than INVITE requests at the E-CSCF 7.4.0 7.5.0 C1-061358 2006-09 CP-33 CP-060463 1369 1 UE emergency deregistration 7.4.0 7.5.0 C1-061304 2006-09 CP-33 CP-060463 1370 1 Emergency subscription 7.4.0 7.5.0 C1-061305 2006-09 CP-33 CP-060463 1371 1 P-CSCF emergency subscription 7.4.0 7.5.0 C1-061306 2006-09 CP-33 CP-060463 1373 2 S-CSCF emergency registration 7.4.0 7.5.0 C1-061350 2006-09 CP-33 CP-060463 1374 2 Handling of Emergency registration in S-CSCF 7.4.0 7.5.0 C1-061349 2006-09 CP-33 CP-060463 1375 2 Handling of emergency registration at the UE 7.4.0 7.5.0 C1-061351 2006-09 CP-33 CP-060463 1379 4 Location handling E-CSCF 7.4.0 7.5.0 C1-061913 2006-09 CP-33 CP-060463 1380 1 Clarification of Emergency Session Setup without prior IMS Registration 7.4.0 7.5.0 C1-061311 2006-09 CP-33 CP-060463 1381 1 Clarifications to subclause 5.1.6.1 7.4.0 7.5.0 C1-061313 2006-09 CP-33 CP-060463 1383 1 Non-INVITE requests 7.4.0 7.5.0 C1-061314 2006-09 CP-33 CP-060463 1384 2 IP-CAN for emergency calls 7.4.0 7.5.0 C1-061355 2006-09 CP-33 CP-060463 1390 1 Adoption of terminology from draft-ietf-ecrit-requirements 7.4.0 7.5.0 C1-061315 2006-09 CP-33 CP-060463 1391 3 Minor corrections to EMC1 text from previous CRs 7.4.0 7.5.0 C1-061367 2006-09 CP-33 CP-060463 1414 2 Handling of loacation information at E-CSCF 7.4.0 7.5.0 C1-061860 2006-09 CP-33 CP-060463 1440 2 P-Asserted-Identity in P-CSCF handling 7.4.0 7.5.0 C1-061861 2006-09 CP-33 CP-060463 1443 4 Handling of PSAP address mapping result at E-CSCF 7.4.0 7.5.0 C1-061919 2006-09 CP-33 CP-060465 1413 1 Miscellaneous Corrections in Annex F 7.4.0 7.5.0 C1-061826 2006-09 CP-33 CP-060465 1420 1 Transit IMS 7.4.0 7.5.0 C1-061827 2006-09 CP-33 CP-060465 1425 1 P-CSCF procedures for session release when QoS resources are unavailable 7.4.0 7.5.0 C1-061830 2006-09 CP-33 CP-060465 1427 1 Make SDP bandwidth modifiers optional for standard RTCP usage 7.4.0 7.5.0 C1-061832 2006-09 CP-33 CP-060465 1430 3 Addition of the cpc parameter to TS24.229 7.4.0 7.5.0 C1-061882 2006-09 CP-33 CP-060466 1385 4 Introduction of GRUU in 24.229 7.4.0 7.5.0 C1-061858 2006-09 CP-33 CP-060466 1386 5 S-SCSF procedures to support GRUU 7.4.0 7.5.0 C1-061915 2006-09 CP-33 CP-060468 1405 Original dialog identifier 7.4.0 7.5.0 C1-061408 2006-09 CP-33 CP-060468 1406 No-fork 7.4.0 7.5.0 C1-061409 2006-09 CP-33 CP-060468 1409 Connection addres - zero 7.4.0 7.5.0 C1-061412 2006-09 CP-33 CP-060468 1415 Reference for populating the "Anonymous" From header 7.4.0 7.5.0 C1-061439 2006-09 CP-33 CP-060468 1439 1 Usage of P-Associated-URI 7.4.0 7.5.0 C1-061759 2006-09 CP-33 CP-060468 1450 Clarification of network initiated deregistration to match reginfo format 7.4.0 7.5.0 C1-061585 2006-09 CP-33 CP-060468 1456 2 Authentication between UA and UA 7.4.0 7.5.0 C1-061851 2006-09 CP-33 CP-060468 1457 2 Treatment by S-CSCF of profile changes for registered PUIs 7.4.0 7.5.0 C1-061853 2006-09 CP-33 CP-060468 1458 1 Completionof RFC 4320 fixes for 100 Trying responses Non-INVITE Transactions RFC 4320 fixes for 100 Trying responses Non-INVITE Transactions tration 7.4.0 7.5.0 C1-061765 2006-09 CP-33 CP-060468 1463 Correction to S-CSCF procedures for UE-originated requests 7.4.0 7.5.0 C1-061646 2006-09 CP-33 CP-060468 1464 1 SCTP transport 7.4.0 7.5.0 C1-061766 2006-09 CP-33 CP-060504 1257 4 SDP usage at MGCF 7.4.0 7.5.0 C1-061847 2006-09 CP-33 CP-060504 1417 1 Type 3 orig-ioi in I-CSCF 7.4.0 7.5.0 C1-061744 2006-09 CP-33 CP-060504 1469 SDP corrections 7.4.0 7.5.0 C1-061659 2006-09 CP-33 CP-060504 1471 SDP completion 7.4.0 7.5.0 C1-061661 2006-09 CP-33 CP-060504 1478 1 Updates to Profile Tables UE Major Capabilities 7.4.0 7.5.0 C1-061754 2006-09 CP-33 CP-060504 1481 Removal of Editor's notes in 24.229, rel-6 7.4.0 7.5.0 C1-061745 2006-09 CP-33 CP-060504 1483 Final codec selection 7.4.0 7.5.0 C1-061850 2006-09 CP-33 CP-060526 1418 3 Originating requests on behalf of an unregistered user 7.4.0 7.5.0 C1-061758 2006-09 Version 7.5.1 created by MCC to correct styles 7.5.0 7.5.1 2006-12 CP-34 CP-060655 1502 - RFC reference update 7.5.1 7.6.0 C1-061977 2006-12 CP-34 CP-060655 1506 - SDP group attribute correction 7.5.1 7.6.0 C1-061981 2006-12 CP-34 CP-060655 1504 1 Addressing editor's notes relating to trust domains 7.5.1 7.6.0 C1-062304 2006-12 CP-34 CP-060655 1546 - Join header correction 7.5.1 7.6.0 C1-062205 2006-12 CP-34 CP-060655 1508 2 Processing the successful response at S-CSCF 7.5.1 7.6.0 C1-062434 2006-12 CP-34 CP-060655 1449 2 Correction of S-CSCF construction and UE interpretation of registration event notification 7.5.1 7.6.0 C1-062317 2006-12 CP-34 CP-060655 1514 1 Removal of more Editor's notes in 24.229, rel-6 7.5.1 7.6.0 C1-062310 2006-12 CP-34 CP-060659 1491 2 Location handling for emergency 7.5.1 7.6.0 C1-062437 2006-12 CP-34 CP-060659 1521 1 Location information for IMS emergency 7.5.1 7.6.0 C1-062293 2006-12 CP-34 CP-060659 1529 2 Emergency re-registration due to mobility 7.5.1 7.6.0 C1-062436 2006-12 CP-34 CP-060659 1515 1 Removal of Editor's notes on emergency call in clause 4 7.5.1 7.6.0 C1-062292 2006-12 CP-34 CP-060659 1484 1 Corrections to emergency call procedures for P-Asserted-Identity header 7.5.1 7.6.0 C1-062289 2006-12 CP-34 CP-060659 1543 - Next hop is the BGCF 7.5.1 7.6.0 C1-062181 2006-12 CP-34 CP-060659 1536 - Editorial corrections to emergency call text 7.5.1 7.6.0 C1-062142 2006-12 CP-34 CP-060659 1542 1 minor correction to EMC of UE and PCSCF 7.5.1 7.6.0 C1-062299 2006-12 CP-34 CP-060659 1490 2 Emergency call on existing registration 7.5.1 7.6.0 C1-062435 2006-12 CP-34 CP-060660 1486 2 Introduction of communication service concept in TS 24229 7.5.1 7.6.0 C1-062451 2006-12 CP-34 CP-060662 1494 1 Tel URI translation 7.5.1 7.6.0 C1-062325 2006-12 CP-34 CP-060662 1523 1 I-CSCF procedure 7.5.1 7.6.0 C1-062333 2006-12 CP-34 CP-060662 1544 - Clarification of UEs initial SDP offer 7.5.1 7.6.0 C1-062189 2006-12 CP-34 CP-060662 1493 1 Alias URI 7.5.1 7.6.0 C1-062324 2006-12 CP-34 CP-060662 1525 1 Clarification of iFC execution for UE-terminated requests at S-CSCF 7.5.1 7.6.0 C1-062334 2006-12 CP-34 CP-060662 1533 1 SIP response code to unknown method 7.5.1 7.6.0 C1-062336 2006-12 CP-34 CP-060662 1537 - Originating requests on behalf of an unregistered user 7.5.1 7.6.0 C1-062143 2006-12 CP-34 CP-060662 1538 - Treatment by S-CSCF of profile changes for registered PUIs 7.5.1 7.6.0 C1-062144 2006-12 CP-34 CP-060662 1547 - Corrections to Profile table for RFC 4320 compliance 7.5.1 7.6.0 C1-062210 2006-12 CP-34 CP-060662 1539 - Miscellaneous editorial corrections 7.5.1 7.6.0 C1-062145 2006-12 CP-34 CP-060662 1509 1 No-forking at AS 7.5.1 7.6.0 C1-062329 2006-12 CP-34 CP-060662 1528 2 P-Visited-Network-ID on ISC interface 7.5.1 7.6.0 C1-062442 2006-12 CP-34 CP-060662 1487 1 Introduction of P-Profile Key in TS 24.229 7.5.1 7.6.0 C1-062322 2006-12 CP-34 CP-060662 1522 1 Local numbering 7.5.1 7.6.0 C1-062338 2006-12 CP-34 CP-060662 1495 2 BGCF procedures 7.5.1 7.6.0 C1-062440 2006-12 CP-34 CP-060662 1498 2 AS acting as PSI 7.5.1 7.6.0 C1-062441 2006-12 CP-34 CP-060662 1524 - Clarification of the URI in UE-terminating requests at the P-CSCF 7.5.1 7.6.0 C1-062061 2006-12 CP-34 CP-060662 1549 1 Core Network Service Authorizatrion 7.5.1 7.6.0 C1-062339 2006-12 CP-34 CP-060663 1527 3 Align with GRUU IETF draft 11 7.5.1 7.6.0 C1-062512 2006-12 CP-34 CP-060663 1496 1 I-CSCF processing GRUU 7.5.1 7.6.0 C1-062340 2006-12 CP-34 CP-060663 1497 1 S-CSCF processing GRUU 7.5.1 7.6.0 C1-062341 2006-12 CP-34 CP-060663 1422 3 GRUU processing by non-UE User Agents 7.5.1 7.6.0 C1-062343 2006-12 CP-34 CP-060667 1426 3 Allowing an asserted display name to be conveyed with a Public Identity 7.5.1 7.6.0 C1-062427 2006-12 CP-34 CP-060667 1429 4 Update to NAT Traversal procedures in support of Outbound and ICE 7.5.1 7.6.0 C1-062515 2006-12 CP-34 CP-060667 1540 2 Annex I (Transit IMS) improvements 7.5.1 7.6.0 C1-062516 2007-03 CP-35 CP-070130 1566 - Session Establishment Interworking with Rel-5 UEs 7.6.0 7.7.0 C1-070052 2007-03 CP-35 CP-070130 1638 - Inclusion of draft-ietf-sip-uri-list-message in SIP profile 7.6.0 7.7.0 C1-070266 2007-03 CP-35 CP-070130 1619 - Clarifications on resource reservation 7.6.0 7.7.0 C1-070180 2007-03 CP-35 CP-070130 1621 1 Routeing B2BUA handling of Replaces header 7.6.0 7.7.0 C1-070439 2007-03 CP-35 CP-070132 1609 - Establishing an emergency session 7.6.0 7.7.0 C1-070147 2007-03 CP-35 CP-070132 1575 - Deletion of editors note in subclause 5.1.6.5 7.6.0 7.7.0 C1-070068 2007-03 CP-35 CP-070132 1639 - Identification of emergency calls 7.6.0 7.7.0 C1-070276 2007-03 CP-35 CP-070132 1593 1 Limitation on Emergency Registration 7.6.0 7.7.0 C1-070424 2007-03 CP-35 CP-070132 1586 1 Tidyup UE clause 7.6.0 7.7.0 C1-070418 2007-03 CP-35 CP-070132 1654 1 Double reference removal 7.6.0 7.7.0 C1-070381 2007-03 CP-35 CP-070132 1605 1 Emergency PUID 7.6.0 7.7.0 C1-070419 2007-03 CP-35 CP-070132 1569 1 Handling of parallel emergency registration 7.6.0 7.7.0 C1-070413 2007-03 CP-35 CP-070132 1574 1 Deletion of editors note in subclause 5.1.6.2 7.6.0 7.7.0 C1-070414 2007-03 CP-35 CP-070132 1568 1 Connecting to an Emergency APN 7.6.0 7.7.0 C1-070409 2007-03 CP-35 CP-070132 1581 1 Deletion of Editor' s notes in 5.2.10 7.6.0 7.7.0 C1-070416 2007-03 CP-35 CP-070132 1641 - Correction of service-urn 7.6.0 7.7.0 C1-070278 2007-03 CP-35 CP-070132 1589 - Correction of CR#1484r1 implementation error (subclause 5.1.6.8.3) 7.6.0 7.7.0 C1-070111 2007-03 CP-35 CP-070132 1610 - Emergency session-no registration 7.6.0 7.7.0 C1-070148 2007-03 CP-35 CP-070134 1612 2 Emergency treatment at P-CSCF 7.6.0 7.7.0 C1-070563 2007-03 CP-35 CP-070134 1635 1 Remove the term ESRP 7.6.0 7.7.0 C1-070430 2007-03 CP-35 CP-070134 1607 2 Emergency call at P-CSCF 7.6.0 7.7.0 C1-070443 2007-03 CP-35 CP-070134 1632 1 Backward compatibility for using 380 response 7.6.0 7.7.0 C1-070429 2007-03 CP-35 CP-070134 1653 3 Location for emergency 7.6.0 7.7.0 C1-070618 2007-03 CP-35 CP-070134 1626 1 Handling of re-registration when user redial emergency number 7.6.0 7.7.0 C1-070426 2007-03 CP-35 CP-070134 1582 2 Deletion of editors notes in 5.11 and 5.4.8 7.6.0 7.7.0 C1-070615 2007-03 CP-35 CP-070134 1567 3 Home Network Indication for Emergency Calls 7.6.0 7.7.0 C1-070640 2007-03 CP-35 CP-070134 1631 2 Correction to emergency call procedure with non-emergency registration for P-Asserted-Identity header 7.6.0 7.7.0 C1-070617 2007-03 CP-35 CP-070137 1634 1 Profile definition for CSI application server 7.6.0 7.7.0 C1-070469 2007-03 CP-35 CP-070138 1660 1 Format of dsl-location 7.6.0 7.7.0 C1-070552 2007-03 CP-35 CP-070138 1595 1 Deletion of EN's in clause 5.10 7.6.0 7.7.0 C1-070547 2007-03 CP-35 CP-070138 1594 - Deletion of EN's in Annex G 7.6.0 7.7.0 C1-070132 2007-03 CP-35 CP-070139 1613 2 Annex K NAT Traversal Procedural and References Updates 7.6.0 7.7.0 C1-070626 2007-03 CP-35 CP-070139 1617 1 Routing of SIP URI "user=phone" when domain doesn't own target user 7.6.0 7.7.0 C1-070551 2007-03 CP-35 CP-070139 1614 1 Annex A updates for Annex K NAT Traversal Procedurals 7.6.0 7.7.0 C1-070550 2007-03 CP-35 CP-070140 1598 1 Forked MESSAGE request 7.6.0 7.7.0 C1-070451 2007-03 CP-35 CP-070140 1558 1 Removal of notes for screening functionality 7.6.0 7.7.0 C1-070441 2007-03 CP-35 CP-070140 1556 1 Handling of special characters in the local service number 7.6.0 7.7.0 C1-070458 2007-03 CP-35 CP-070140 1655 2 Forwarding a request by transit functions in the S-CSCF 7.6.0 7.7.0 C1-070586 2007-03 CP-35 CP-070140 1587 1 Terminating case in S-CSCF 7.6.0 7.7.0 C1-070449 2007-03 CP-35 CP-070140 1559 - Completion of SIP timers functionality 7.6.0 7.7.0 C1-070039 2007-03 CP-35 CP-070140 1588 1 P-User-Database 7.6.0 7.7.0 C1-070450 2007-03 CP-35 CP-070140 1560 1 Removal of notes for SIGCOMP functionality 7.6.0 7.7.0 C1-070442 2007-03 CP-35 CP-070140 1557 - Removal of normative statements in NOTEs 7.6.0 7.7.0 C1-070037 2007-03 CP-35 CP-070140 1604 1 Forwarding P-Charging-Vector outside the home network 7.6.0 7.7.0 C1-070453 2007-03 CP-35 CP-070140 1555 1 Removal of Editor's notes for message bodies 7.6.0 7.7.0 C1-070440 2007-03 CP-35 CP-070140 1652 - Correction for local numbers 7.6.0 7.7.0 C1-070341 2007-03 CP-35 CP-070140 1601 - Tel URI translation 7.6.0 7.7.0 C1-070139 2007-03 CP-35 CP-070140 1646 1 Align definition of Alias URI with the description in 23.228 7.6.0 7.7.0 C1-070455 2007-03 CP-35 CP-070140 1600 2 Dual IP addresses 7.6.0 7.7.0 C1-070584 2007-03 CP-35 CP-070142 1642 - SIP extensions covering URI-lists 7.6.0 7.7.0 C1-070279 2007-03 CP-35 CP-070148 1564 1 Network Initiated / Modified Media PDP Contexts 7.6.0 7.7.0 C1-070447 2007-03 CP-35 CP-070149 1643 - SDP usage in association with BFCP (additions to SDP profile) 7.6.0 7.7.0 C1-070282 2007-03 CP-35 CP-070151 1648 2 S-CSCF inserts P-Called-Party-ID before forwarding request towards served user 7.6.0 7.7.0 C1-070588 2007-03 CP-35 CP-070151 1597 1 Instance ID 7.6.0 7.7.0 C1-070461 2007-03 CP-35 CP-070151 1615 1 Signalling Public User Identity to AS when request URI is Temp-GRUU 7.6.0 7.7.0 C1-070463 2007-03 CP-35 CP-070214 1640 3 Location conveyance revisions 7.6.0 7.7.0 2007-03 CP-35 CP-070242 1576 3 Deletion of editors notes in subclauses 5.1.6.8.2, 5.1.6.8.3, 5.1.6.8.4 7.6.0 7.7.0 2007-03 CP-35 CP-070252 1658 4 Profile for IBCF 7.6.0 7.7.0 2007-03 CP-35 CP-070254 1580 3 PCC introduction to TS 24.229 7.6.0 7.7.0 2007-03 CP-35 CP-070255 1630 3 Corrections for the handling of target refresh requests at the S-CSCF 7.6.0 7.7.0 2007-03 CP-35 CP-070271 1623 5 Further alignment with phonebcp draft 7.6.0 7.7.0 2007-06 CP-36 CP-070370 1749 1 Correction of coding rules of P-Access-Network-Info header 7.7.0 7.8.0 C1-071435 2007-06 CP-36 CP-070370 1689 2 Inclusion of "addressing an amplification vulnerability in session initiation protocol forking proxies" (draft-ietf-sip-fork-loop-fix) in the SIP profile 7.7.0 7.8.0 C1-071409 2007-06 CP-36 CP-070373 1666 2 Protocol between E-CSCF and LRF 7.7.0 7.8.0 C1-071040 2007-06 CP-36 CP-070373 1690 - Further alignment with phonebcp draft 7.7.0 7.8.0 C1-070779 2007-06 CP-36 CP-070373 1763 1 Emergency registration clarification 7.7.0 7.8.0 C1-071441 2007-06 CP-36 CP-070373 1665 1 Definition of identities used for emergency call 7.7.0 7.8.0 C1-070957 2007-06 CP-36 CP-070374 1714 1 Alignment of layout of access technology specific annexes 7.7.0 7.8.0 C1-071032 2007-06 CP-36 CP-070374 1715 1 GPRS IP-CAN change of normative requirement out of scope to informative 7.7.0 7.8.0 C1-071033 2007-06 CP-36 CP-070374 1732 2 Clarification on iFC execution 7.7.0 7.8.0 C1-071460 2007-06 CP-36 CP-070374 1721 1 UE un-subscribing to reg-event 7.7.0 7.8.0 C1-071419 2007-06 CP-36 CP-070374 1722 - MO Record-Route at P-CSCF 7.7.0 7.8.0 C1-071051 2007-06 CP-36 CP-070374 1723 1 MT Record-Route at P-CSCF 7.7.0 7.8.0 C1-071420 2007-06 CP-36 CP-070374 1727 1 Double registration 7.7.0 7.8.0 C1-071422 2007-06 CP-36 CP-070374 1730 1 Inclusion of new mandatory elements of SigComp 7.7.0 7.8.0 C1-071423 2007-06 CP-36 CP-070374 1731 1 Use of a presence specific dictionary in SigComp 7.7.0 7.8.0 C1-071424 2007-06 CP-36 CP-070374 1720 1 Registration and deregistration 7.7.0 7.8.0 C1-071418 2007-06 CP-36 CP-070374 1746 1 Correction to P-CSCF procedures for cancellation of a session currently being established 7.7.0 7.8.0 C1-071431 2007-06 CP-36 CP-070374 1762 1 Originating a terminating request in an AS 7.7.0 7.8.0 C1-071433 2007-06 CP-36 CP-070374 1769 2 Clarification to Original Dialog Identifier 7.7.0 7.8.0 C1-071463 2007-06 CP-36 CP-070374 1761 - Local numbering clarification 7.7.0 7.8.0 C1-071196 2007-06 CP-36 CP-070374 1760 1 PANI related corrections 7.7.0 7.8.0 C1-071437 2007-06 CP-36 CP-070374 1743 1 The precondition mechanism may be required in subsequent SDP offer/answer exchanges 7.7.0 7.8.0 C1-071430 2007-06 CP-36 CP-070374 1772 - Minor miscellaneous clean-up 7.7.0 7.8.0 C1-071231 2007-06 CP-36 CP-070374 1739 1 P-CSCF processing of P-Early-Media 7.7.0 7.8.0 C1-071428 2007-06 CP-36 CP-070374 1738 3 Originating UE sending of P-Early-Media 7.7.0 7.8.0 C1-071462 2007-06 CP-36 CP-070374 1737 2 Originating UE processing of P-Early-Media 7.7.0 7.8.0 C1-071461 2007-06 CP-36 CP-070375 1692 - Profile support for a session initiation protocol event package and data format for various settings in support for the push-to-talk over cellular service (RFC4354) 7.7.0 7.8.0 C1-070781 2007-06 CP-36 CP-070375 1562 4 Completion of Phone-context parameter in rel-7 7.7.0 7.8.0 C1-071009 2007-06 CP-36 CP-070375 1700 - Translation of non-international format numbers 7.7.0 7.8.0 C1-070810 2007-06 CP-36 CP-070375 1680 - Outgoing Request URI=pres or IM URI processing clarification and misc clean-up 7.7.0 7.8.0 C1-070705 2007-06 CP-36 CP-070375 1691 1 Profile support for the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular (draft-allen-sipping-poc-p-answer-state-header) 7.7.0 7.8.0 C1-070987 2007-06 CP-36 CP-070375 1678 1 Qvalue 7.7.0 7.8.0 C1-070984 2007-06 CP-36 CP-070375 1704 - Minor miscellaneous clean-up 7.7.0 7.8.0 C1-070824 2007-06 CP-36 CP-070375 1703 - Filter criteria evaluation when the AS changes the P-Asserted-Identity 7.7.0 7.8.0 C1-070823 2007-06 CP-36 CP-070378 1718 1 Addition to network initiated PDP context 7.7.0 7.8.0 C1-071346 2007-06 CP-36 CP-070380 1679 - Cleanup of Signalling Public GRUU to AS 7.7.0 7.8.0 C1-070704 2007-06 CP-36 CP-070380 1663 - Provide GRUU functionality in case of hosted NAT 7.7.0 7.8.0 C1-070663 2007-06 CP-36 CP-070380 1756 1 GRUU Alignment with stage 2 7.7.0 7.8.0 C1-071456 2007-06 CP-36 CP-070380 1686 2 Alternate GRUU for AS acting on behalf of Public User Identity 7.7.0 7.8.0 C1-071010 2007-06 CP-36 CP-070380 1713 2 Cleanup of GRUU 7.7.0 7.8.0 C1-071238 2007-06 CP-36 CP-070380 1766 1 Management of GRUU 7.7.0 7.8.0 C1-071457 2007-06 CP-36 CP-070380 1711 2 Use of GRUU for Emergency Sessions 7.7.0 7.8.0 C1-071458 2007-06 CP-36 CP-070383 1773 - IMS Communication Service ID registration 7.7.0 7.8.0 C1-071234 2007-06 CP-36 CP-070383 1645 6 IMS Communication Service ID 24.229 7.7.0 7.8.0 C1-071475 2007-06 CP-36 CP-070388 1735 2 Correction on the handlng of CPC parameter regarding trust domain 7.7.0 7.8.0 C1-071464 2007-06 CP-36 CP-070388 1662 - Tidyup open issues from FBI work item 7.7.0 7.8.0 C1-070662 2007-06 CP-36 CP-070388 1596 5 Update to NAT Traversal procedures in support of Outbound and ICE 7.7.0 7.8.0 C1-071400 2007-06 CP-36 CP-070388 1740 1 IBCF processing of P-Early-Media 7.7.0 7.8.0 C1-071404 2007-06 CP-36 CP-070388 1742 1 IBCF Path header 7.7.0 7.8.0 C1-071405 2007-06 CP-36 CP-070436 1696 3 Endorsement of P-Early-Media header draft 7.7.0 7.8.0 2007-06 CP-36 CP-070447 1698 3 Report of new transit scenario documented in stage 2 7.7.0 7.8.0 - 2007-06 CP-36 CP-070450 1771 3 THIG processing correction to ensure conformity to RFC 3261 7.7.0 7.8.0 - 2007-06 CP-36 CP-070496 1717 4 PCC impact 7.7.0 7.8.0 - 2007-06 CP-36 CP-070393 1751 1 Resource-Priority header and trust domains 7.7.0 8.0.0 C1-071446 2007-06 CP-36 CP-070393 1695 2 Inclusion policy for Resource-Priority header in support of multimedia priority service 7.7.0 8.0.0 C1-071443 2007-06 CP-36 CP-070393 1694 2 Inclusion of "communications resource priority for the session initiation protocol" (RFC4412) in the SIP profile 7.7.0 8.0.0 C1-071444 2007-06 CP-36 CP-070393 1693 1 Inclusion of "extending the session initiation protocol Reason header for preemption events" (RFC4411) in the SIP profile 7.7.0 8.0.0 C1-070918 2007-06 CP-36 CP-070396 1682 2 IMS Enhancements to Support Number Portability (NP) for Cable Networks 7.7.0 8.0.0 C1-070994 2007-06 CP-36 CP-070396 1681 4 Enhancements to Support Preferred Circuit Carrier Access and Dial-Around for Cable Networks 7.7.0 8.0.0 C1-071294 2007-09 CP-37 CP-070578 1945 Correction of the Authorization Header in the Profile Table 8.0.0 8.1.0 C1-072085 2007-09 CP-37 CP-070578 1811 Integrity param in De- and ReREGISTER 8.0.0 8.1.0 C1-071573 2007-09 CP-37 CP-070579 1905 2 Clarification of DTD 8.0.0 8.1.0 C1-072150 2007-09 CP-37 CP-070580 1795 2 Unprotected registration at UE 8.0.0 8.1.0 C1-072153 2007-09 CP-37 CP-070580 1876 IETF reference updates 8.0.0 8.1.0 C1-071772 2007-09 CP-37 CP-070580 1924 1 P-Access-Network-Info header clarification 8.0.0 8.1.0 C1-072042 2007-09 CP-37 CP-070580 1922 1 Optional rport parameter in UE 8.0.0 8.1.0 C1-072039 2007-09 CP-37 CP-070580 1797 1 Unprotected registration at S-CSCF 8.0.0 8.1.0 C1-072052 2007-09 CP-37 CP-070584 1866 Emergency Registration without eAPN 8.0.0 8.1.0 C1-071728 2007-09 CP-37 CP-070585 1878 IETF reference updates relating to emergency call feature 8.0.0 8.1.0 C1-071776 2007-09 CP-37 CP-070585 1892 1 Correction of emergency procedures unregistered user case 8.0.0 8.1.0 C1-072018 2007-09 CP-37 CP-070585 1894 Emergency registration timer in visited network 8.0.0 8.1.0 C1-071808 2007-09 CP-37 CP-070585 1927 Contents of From header when initiating an emergency session within a emergency registration 8.0.0 8.1.0 C1-071874 2007-09 CP-37 CP-070586 1861 1 Correction for the URNs of IMS Communication Service Identifier and IMS Application Reference Identifier 8.0.0 8.1.0 C1-071956 2007-09 CP-37 CP-070586 1909 2 Completing UE ICSI/IARI procedures 8.0.0 8.1.0 C1-072162 2007-09 CP-37 CP-070586 1842 1 S-CSCF option to add P-Asserted-Service in UE-originated case 8.0.0 8.1.0 C1-071952 2007-09 CP-37 CP-070586 1911 2 Completing S-CSCF ICSI/IARI procedures 8.0.0 8.1.0 C1-072164 2007-09 CP-37 CP-070586 1826 1 Cleanup of text related to contact header dealing with ICSI 8.0.0 8.1.0 C1-071942 2007-09 CP-37 CP-070586 1838 2 Description of the ICSI as an assigned identifier 8.0.0 8.1.0 C1-072159 2007-09 CP-37 CP-070586 1929 1 ICSI Alignments with reqs 2, 3 and 11 8.0.0 8.1.0 C1-071947 2007-09 CP-37 CP-070586 1942 1 UE usage of ServideID received from the network 8.0.0 8.1.0 C1-072181 2007-09 CP-37 CP-070586 1840 Correction of application server handling of ICSI and IARI values 8.0.0 8.1.0 C1-071676 2007-09 CP-37 CP-070590 1807 3 Trust Domain in IMS 8.0.0 8.1.0 C1-072185 2007-09 CP-37 CP-070590 1799 1 Unprotected registration at P-CSCF 8.0.0 8.1.0 C1-072054 2007-09 CP-37 CP-070590 1793 1 Protected registration 8.0.0 8.1.0 C1-072046 2007-09 CP-37 CP-070590 1804 1 No multiple simultanous Registration 8.0.0 8.1.0 C1-072056 2007-09 CP-37 CP-070590 1864 1 Corrections of tables in Annex A 8.0.0 8.1.0 C1-072065 2007-09 CP-37 CP-070590 1879 1 Essential corrections to P-Early-Media header procedures 8.0.0 8.1.0 C1-072062 2007-09 CP-37 CP-070590 1881 IETF SigComp reference updates 8.0.0 8.1.0 C1-071779 2007-09 CP-37 CP-070590 1934 SIP related reference update 8.0.0 8.1.0 C1-071888 2007-09 CP-37 CP-070590 1913 1 Removal of IBCF Route Headers Editors Note 8.0.0 8.1.0 C1-072073 2007-09 CP-37 CP-070590 1854 1 Clarification on P-Profile-Key 8.0.0 8.1.0 C1-072063 2007-09 CP-37 CP-070592 1817 Resolve FFS for AS-GRUU 8.0.0 8.1.0 C1-071581 2007-09 CP-37 CP-070596 1885 2 Update Emergency NAT Traversal Procedures Annex K 8.0.0 8.1.0 C1-072078 2007-09 CP-37 CP-070596 1883 1 Update GRUU NAT Traversal Procedures Annex-K 8.0.0 8.1.0 C1-071926 2007-09 CP-37 CP-070600 1750 3 Resource-Priority and priority 7.8.0 8.1.0 C1-072132 2007-09 CP-37 CP-070600 1919 2 Addition of MGCF for optional support of Resource-Priority 8.0.0 8.1.0 C1-072184 2007-09 CP-37 CP-070601 1815 2 Updates to Annex K in support of SIP Digest and TLS procedures 8.0.0 8.1.0 C1-072137 2007-09 CP-37 CP-070601 1812 4 UE Digest and TLS Procedures 8.0.0 8.1.0 C1-072172 2007-09 CP-37 CP-070601 1814 4 S-CSCF Digest and TLS Procedures 8.0.0 8.1.0 C1-072174 2007-09 CP-37 CP-070601 1813 4 P-CSCF Digest and TLS Procedures 8.0.0 8.1.0 C1-072173 2007-09 CP-37 CP-070603 1847 1 Cleanup of SigComp dictionary support 8.0.0 8.1.0 C1-072144 2007-09 CP-37 CP-070603 1896 1 S-CSCF procedure corrections 8.0.0 8.1.0 C1-072089 2007-09 CP-37 CP-070603 1935 Restructuring of subclause 5.2.6 (General treatment for all dialogs and standalone transactions excluding the REGISTER method) of the P-CSCF 8.0.0 8.1.0 C1-071891 2007-09 CP-37 CP-070603 1788 2 Request-URI in registration 8.0.0 8.1.0 C1-072154 2007-09 CP-37 CP-070670 1907 3 Definition of feature tag for IARI/ICSI 8.0.0 8.1.0 C1-072006 2007-09 CP-37 CP-070674 1791 2 Emergency registration 8.0.0 8.1.0 C1-072016 2007-09 CP-37 CP-070676 1851 4 P-CSCF behaviour upon loss of SIP signalling transport 8.0.0 8.1.0 C1-072178 2007-09 CP-37 CP-070691 1926 5 UE setting of IARI 8.0.0 8.1.0 C1-072166 2007-12 CP-38 CP-070735 2077 1 Update P-Early-Media Reference 8.1.0 8.2.0 C1-072750 2007-12 CP-38 CP-070785 2065 Authenticating with AKAv1-MD5 8.1.0 8.2.0 C1-072533 2007-12 CP-38 CP-070785 2115 Proxy profile corrections 8.1.0 8.2.0 C1-072922 2007-12 CP-38 CP-070785 2111 Corrections to RFC 3329 entries in profile 8.1.0 8.2.0 C1-072918 2007-12 CP-38 CP-070785 2041 1 Corrections for re-authenticating user 8.1.0 8.2.0 C1-072553 2007-12 CP-38 CP-070785 2049 3 Introduction of versioning and conventions 8.1.0 8.2.0 C1-072989 2007-12 CP-38 CP-070788 2028 1 Coverage of access technology specific text 8.1.0 8.2.0 C1-072746 2007-12 CP-38 CP-070788 2017 2 Action on missing "integrity-protected" parameter 8.1.0 8.2.0 C1-073179 2007-12 CP-38 CP-070788 2035 1 MGCF does not act as a proxy 8.1.0 8.2.0 C1-072565 2007-12 CP-38 CP-070788 2070 1 Correction to subclause 7.2A.5.2.2 8.1.0 8.2.0 C1-073052 2007-12 CP-38 CP-070791 1999 1 380 at normal call setup 8.1.0 8.2.0 C1-072670 2007-12 CP-38 CP-070791 2062 2 Miscellaneous EMC1 corrections 8.1.0 8.2.0 C1-072748 2007-12 CP-38 CP-070791 2120 Introductory text for emergency service 8.1.0 8.2.0 C1-072930 2007-12 CP-38 CP-070794 1990 Correct sub-section references in Annex-K 8.1.0 8.2.0 C1-072295 2007-12 CP-38 CP-070794 2023 Correction of outbound and ice option tag support in profile tables 8.1.0 8.2.0 C1-072383 2007-12 CP-38 CP-070795 1986 1 Align with draft-gruu-reg-ev-09 8.1.0 8.2.0 C1-072752 2007-12 CP-38 CP-070795 2043 1 Addition of GRUU to emergency set-up when registration exists 8.1.0 8.2.0 C1-072599 2007-12 CP-38 CP-070799 2067 1 P-CSCF Releases/Rejects session due to PCRF responses 8.1.0 8.2.0 C1-073067 2007-12 CP-38 CP-070805 2053 2 Terminating UE ICSI procedures 8.1.0 8.2.0 C1-072708 2007-12 CP-38 CP-070805 2021 1 Correction to digest and TLS Procedures for Annex K 8.1.0 8.2.0 C1-072508 2007-12 CP-38 CP-070805 1951 1 Correction to the examples for ICSI and IARI values 8.1.0 8.2.0 C1-072490 2007-12 CP-38 CP-070805 2014 2 Encoding of ICSI and IARI within the g.ims.app_ref feature tag 8.1.0 8.2.0 C1-072704 2007-12 CP-38 CP-070805 2051 1 Multiple IARI/ICSI values in g.ims.app_ref feature tag 8.1.0 8.2.0 C1-072512 2007-12 CP-38 CP-070805 1969 1 One ICSI value per P-Preferred-Service header 8.0.0 8.2.0 C1-072496 2007-12 CP-38 CP-070805 1963 1 Change of name for feature tag g.ims.app_ref 8.0.0 8.2.0 C1-072492 2007-12 CP-38 CP-070806 2008 2 Handling of invalid and unauthorized media based on Communication Service Identifiers 8.1.0 8.2.0 C1-072702 2007-12 CP-38 CP-070806 2092 2 S-CSCF Processing of P-Preferred-Service and P-Asserted-Service 8.1.0 8.2.0 C1-073204 2007-12 CP-38 CP-070806 2107 2 The received list of ICSIs from the Network 8.1.0 8.2.0 C1-073206 2007-12 CP-38 CP-070806 2088 ICSI in Annex F 8.1.0 8.2.0 C1-072841 2007-12 CP-38 CP-070806 2019 2 Miscellaneous service identifier corrections 8.1.0 8.2.0 C1-073106 2007-12 CP-38 CP-070806 1965 3 Minor corrections to P-Preferred and P-Asserted Service headers 8.1.0 8.2.0 C1-073102 2007-12 CP-38 CP-070806 1976 2 Correction to S-CSCF handling of IMS communication service 8.1.0 8.2.0 C1-072700 2007-12 CP-38 CP-070807 2005 1 No SIPS 8.1.0 8.2.0 C1-072593 2007-12 CP-38 CP-070807 1961 1 Route header verification at P-CSCF 8.1.0 8.2.0 C1-072587 2007-12 CP-38 CP-070807 1955 1 Update of the reference for P-Profile-Key Private Header (P-Header) 8.1.0 8.2.0 C1-072487 2007-12 CP-38 CP-070807 2012 Reference alignment 8.1.0 8.2.0 C1-072364 2007-12 CP-38 CP-070807 2037 1 AS does not subscribe to reg-event package when user is unregistered 8.1.0 8.2.0 C1-072597 2007-12 CP-38 CP-070807 2045 2 Correction of mutually exclusive ICSI and GRUU 8.1.0 8.2.0 C1-072706 2007-12 CP-38 CP-070807 2055 Update of P-Answer-State header draft Reference 8.1.0 8.2.0 C1-072446 2007-12 CP-38 CP-070808 2057 2 Clarification of UE handling of the P-Early-Media header. 8.1.0 8.2.0 C1-072723 2007-12 CP-38 CP-070808 2100 1 Access Network Info for I-WLAN 8.1.0 8.2.0 C1-073075 2007-12 CP-38 CP-070808 2003 2 Service Profile Change 8.1.0 8.2.0 C1-072718 2007-12 CP-38 CP-070808 1957 4 Correction to the IBCF subsection in relation with trusted domain 8.1.0 8.2.0 C1-072687 2007-12 CP-38 CP-070808 2072 2 Correction to procedure when registration timer times out 8.1.0 8.2.0 C1-073173 2007-12 CP-38 CP-070808 2103 1 Access Network Info for 3GPP2/UMB 8.1.0 8.2.0 C1-073057 2007-12 CP-38 CP-070810 2081 3 Correction of multiple Contact headers in abnormal case 8.1.0 8.2.0 C1-073226 2007-12 CP-38 CP-070810 2117 1 Miscellaneous editorial corrections (part 3) 8.1.0 8.2.0 C1-073165 2007-12 CP-38 CP-070810 1932 4 Incorporation of draft-ietf-consent-framework 8.1.0 8.2.0 C1-073166 2007-12 CP-38 CP-070810 2098 1 Superfluous requirements for removing charging information at terminating P-CSCF 8.1.0 8.2.0 C1-073164 2007-12 CP-38 CP-070810 1974 1 Synchronization When Service Profile Being Modified 8.1.0 8.2.0 C1-072661 2007-12 CP-38 CP-070810 2029 3 Miscellaneous editorial corrections 8.1.0 8.2.0 C1-072764 2007-12 CP-38 CP-070810 2059 3 Miscellaneous editorial corrections (part 2) 8.1.0 8.2.0 C1-073162 2007-12 CP-38 CP-070811 2078 1 Clarification on interconnect functionalities 8.1.0 8.2.0 C1-073163 2007-12 CP-38 CP-070812 2086 1 Semantics for values in "integrity-protected" field 8.1.0 8.2.0 C1-073112 2007-12 CP-38 CP-070812 2060 3 Public user identity and private user identity derivation in UEs without UICC 8.1.0 8.2.0 C1-073201 2007-12 CP-38 CP-070812 2006 1 Digest Support in Profile Tables 8.1.0 8.2.0 C1-072623 2007-12 CP-38 CP-070812 2026 1 Security-related references and definitions 8.1.0 8.2.0 C1-072761 2007-12 CP-38 CP-070812 2025 3 Introduction to security mechanisms 8.1.0 8.2.0 C1-073175 2007-12 CP-38 CP-070812 1982 6 Updates to integrity protection for digest and TLS 8.1.0 8.2.0 C1-073202 2007-12 CP-38 CP-070814 2085 4 Addition of SIP header to support UUS1 8.1.0 8.2.0 C1-073208 2007-12 CP-38 CP-070816 2024 5 Integration of text for digest and TLS plus digest into the main body of the specification 8.1.0 8.2.0 C1-073200 2007-12 CP-38 CP-070864 1953 5 Clarifications on NW-init and resource reservation 8.1.0 8.2.0 C1-073069 2007-12 CP-38 CP-070875 1997 4 Corrections for emergency procedures 8.1.0 8.2.0 C1-072991 2008-03 CP-39 CP-080120 2174 Reference correction for RFC 4244 8.2.0 8.3.0 C1-080147 2008-03 CP-39 CP-080120 2149 Handling of the reason header in requests at the MGCF 8.2.0 8.3.0 C1-080045 2008-03 CP-39 CP-080120 2162 1 Correction on handling of P-Charging-Vector at IBCF 8.2.0 8.3.0 C1-080515 2008-03 CP-39 CP-080120 2181 1 Correction of Alias 8.2.0 8.3.0 C1-080517 2008-03 CP-39 CP-080120 2176 SDP with precondition 8.2.0 8.3.0 C1-080149 2008-03 CP-39 CP-080126 2201 2 Handling of Service ID in interworking cases 8.2.0 8.3.0 C1-080630 2008-03 CP-39 CP-080126 2155 2 Clarification on the use of IARI in the contact header 8.2.0 8.3.0 C1-080635 2008-03 CP-39 CP-080126 2183 2 UE behaviour when no ICSI is contained in the Accept-Contact header 8.2.0 8.3.0 C1-080531 2008-03 CP-39 CP-080130 2143 1 Procedure at S-CSCF 8.2.0 8.3.0 C1-080600 2008-03 CP-39 CP-080130 2144 Empty RES 8.2.0 8.3.0 C1-080009 2008-03 CP-39 CP-080130 2145 1 Alias URI 8.2.0 8.3.0 C1-080601 2008-03 CP-39 CP-080130 2146 2 Notification at S-CSCF 8.2.0 8.3.0 C1-080631 2008-03 CP-39 CP-080130 2156 1 Correction of example of IARI coding 8.2.0 8.3.0 C1-080526 2008-03 CP-39 CP-080130 2160 1 Correction on the value used for P-Preferred-Identity header at UE 8.2.0 8.3.0 C1-080513 2008-03 CP-39 CP-080130 2170 1 Correction to user initiated mergency re-registration 8.2.0 8.3.0 C1-080405 2008-03 CP-39 CP-080130 2187 1 IPv4 and IPv6 support 8.2.0 8.3.0 C1-080609 2008-03 CP-39 CP-080130 2188 4 P-CSCF awareness for 3GPP accesses 8.2.0 8.3.0 C1-080658 2008-03 CP-39 CP-080130 2196 2 Annex K: ICE procedures for the IBCF 8.2.0 8.3.0 C1-080643 2008-03 CP-39 CP-080131 2192 1 Completion of CIC and DAI requirements for MGCF 8.2.0 8.3.0 C1-080472 2008-03 CP-39 CP-080132 2163 1 Miscelanous Corrections on SIP Digest 8.2.0 8.3.0 C1-080473 2008-03 CP-39 CP-080132 2189 1 Enhancements to security introduction text 8.2.0 8.3.0 C1-080474 2008-03 CP-39 CP-080134 2190 1 Inclusion of NASS bundled authentication 8.2.0 8.3.0 C1-080518 2008-03 CP-39 CP-080139 2164 1 SIP XML addition for support of transit specific content 8.2.0 8.3.0 C1-080533 2008-03 CP-39 CP-080140 2138 2 IP-CAN procedure for cdma2000 8.2.0 8.3.0 C1-080411 2008-03 CP-39 CP-080140 2141 2 P-CSCF interface to IP-CAN 8.2.0 8.3.0 C1-080413 2008-03 CP-39 CP-080140 2140 2 Access-network-charging-info for cdma2000 access 8.2.0 8.3.0 C1-080412 2008-03 CP-39 CP-080141 2197 1 Wildcarded Public User Identity: P-CSCF impact 8.2.0 8.3.0 C1-080612 2008-03 CP-39 CP-080141 2198 2 Wildcarded Public User Identity: S-CSCF impact 8.2.0 8.3.0 C1-080644 2008-03 CP-39 CP-080199 2147 4 NAT traversal 8.2.0 8.3.0 2008-03 CP-39 CP-080201 2151 5 Handling of the reason header in responses 8.2.0 8.3.0 2008-06 CP-40 CP-080338 2288 1 Correction to de-registration procedure when registration expirated 8.3.0 8.4.0 C1-081936 2008-06 CP-40 CP-080340 2215 - Revision of references to documents from IETF ECRIT working group 8.3.0 8.4.0 C1-080854 2008-06 CP-40 CP-080341 2243 1 Correction to P-CSCF session release procedures 8.3.0 8.4.0 C1-081336 2008-06 CP-40 CP-080341 2275 2 Addition of AVPF support 8.3.0 8.4.0 C1-082022 2008-06 CP-40 CP-080341 2258 1 Correction on identifiers distinguishing the dialog 8.3.0 8.4.0 C1-081338 2008-06 CP-40 CP-080341 2238 1 Removal of reason header annex 8.3.0 8.4.0 C1-081334 2008-06 CP-40 CP-080341 2217 - Revision of references to documents from IETF 8.3.0 8.4.0 C1-080858 2008-06 CP-40 CP-080341 2277 1 Addition of the SDP Capability Negotiaion mechanism 8.3.0 8.4.0 C1-081932 2008-06 CP-40 CP-080343 2158 6 Handling of SDP at the terminating UE 8.3.0 8.4.0 C1-082050 2008-06 CP-40 CP-080344 2290 - Correction of GRUU references 8.3.0 8.4.0 C1-081799 2008-06 CP-40 CP-080349 2236 - Revision of references to documents from IETF SIP working group 8.3.0 8.4.0 C1-080860 2008-06 CP-40 CP-080353 2203 1 Emergency calls - NAT traversal at UE 8.3.0 8.4.0 C1-081228 2008-06 CP-40 CP-080353 2204 1 NAT traversal for emergency calls at P-CSCF 8.3.0 8.4.0 C1-081229 2008-06 CP-40 CP-080353 2220 1 PANI header text revision 8.3.0 8.4.0 C1-081346 2008-06 CP-40 CP-080353 2225 1 Addition of 802.11n to P-Access-Network-Info header 8.3.0 8.4.0 C1-081348 2008-06 CP-40 CP-080353 2205 3 "im" URI 8.3.0 8.4.0 C1-081411 2008-06 CP-40 CP-080353 2254 2 Annex K: Moving of IBCF ICE procedures 8.3.0 8.4.0 C1-081469 2008-06 CP-40 CP-080353 2168 9 Correction of 3GPP IM CN subsystem XML handling 8.3.0 8.4.0 C1-081481 2008-06 CP-40 CP-080353 2221 1 Media transcoding control functionality in IBCF 8.3.0 8.4.0 C1-081347 2008-06 CP-40 CP-080353 2219 1 PANI header coding 8.3.0 8.4.0 C1-081345 2008-06 CP-40 CP-080353 2209 1 Alias URI 8.3.0 8.4.0 C1-081343 2008-06 CP-40 CP-080353 2136 7 3GPP IM CN subsystem XML Schema version 8.3.0 8.4.0 C1-081480 2008-06 CP-40 CP-080353 2255 3 Annex K: ICE procedures for the P-CSCF 8.3.0 8.4.0 C1-081470 2008-06 CP-40 CP-080354 2284 2 SDP Enhancements to support resource allocation 8.3.0 8.4.0 C1-082045 2008-06 CP-40 CP-080354 2218 2 B2BUA AS influence of filter criteria evaluation 8.3.0 8.4.0 C1-082033 2008-06 CP-40 CP-080354 2263 1 Multiple contact addresses 8.3.0 8.4.0 C1-082041 2008-06 CP-40 CP-080354 2280 - Annex A : SIP Record-Route header table correction 8.3.0 8.4.0 C1-081605 2008-06 CP-40 CP-080354 2206 2 "rport" and "received" parameters at P-CSCF 8.3.0 8.4.0 C1-081871 2008-06 CP-40 CP-080354 2282 1 Display Name in Reg Event 8.3.0 8.4.0 C1-082027 2008-06 CP-40 CP-080354 2285 - Update IETF draft reference 8.3.0 8.4.0 C1-081701 2008-06 CP-40 CP-080354 2207 2 UE handling the "rport" parameter 8.3.0 8.4.0 C1-081872 2008-06 CP-40 CP-080355 2234 4 Annex K alignment with main body and cleanup 8.3.0 8.4.0 C1-082043 2008-06 CP-40 CP-080355 2291 1 Determining when to invoke SIP Digest procedures in S-CSCF 8.3.0 8.4.0 C1-081944 2008-06 CP-40 CP-080355 2269 1 Cleanup of SIP Digest/TLS procedures 8.3.0 8.4.0 C1-081942 2008-06 CP-40 CP-080359 2260 2 P-CSCF: Aligning P-Profile-Key behaviour for Wildcarded public user identities with Wildcarded PSI 8.3.0 8.4.0 C1-081476 2008-06 CP-40 CP-080359 2212 4 Dial string handling 8.3.0 8.4.0 C1-082110 2008-06 CP-40 CP-080359 2261 2 Trustdomain: Adding P-Profile-Key header to the trustdomain 8.3.0 8.4.0 C1-081477 2008-06 CP-40 CP-080359 2239 1 Trust domain changes for identity headers for business communication 8.3.0 8.4.0 C1-081206 2008-06 CP-40 CP-080359 2259 2 I-CSCF: Aligning P-Profile-Key behaviour for Wildcarded public user identities with Wildcarded PSI procedures 8.3.0 8.4.0 C1-081475 2008-06 CP-40 CP-080359 2232 2 Delivering Request-URI to UE managing several terminals 8.3.0 8.4.0 C1-081474 2008-06 CP-40 CP-080359 2262 - Private network indication annex A changes 8.3.0 8.4.0 C1-081210 2008-06 CP-40 CP-080359 2240 3 Handling of private network indication 8.3.0 8.4.0 C1-081953 2008-06 CP-40 CP-080360 2273 1 Event package usage for Message Waiting Indication (MWI) service 8.3.0 8.4.0 C1-081901 2008-06 CP-40 CP-080360 2226 3 XML-support of transit specific content Tables 8.3.0 8.4.0 C1-081905 2008-06 CP-40 CP-080364 2222 3 Depth of IMS service level trace 8.3.0 8.4.0 C1-081955 2008-06 CP-40 CP-080366 2252 1 Emergency CS call set up procedures for non-3GPP systems 8.3.0 8.4.0 C1-081465 2008-06 CP-40 CP-080366 2268 1 Different IP addresses 8.3.0 8.4.0 C1-081945 2008-06 CP-40 CP-080366 2251 1 Remove specific codec requirement 8.3.0 8.4.0 C1-081464 2008-06 CP-40 CP-080400 2208 2 "rport" parameter 8.3.0 8.4.0 - 2008-06 CP-40 CP-080402 2296 - IARI and ICSI in different feature tags 8.3.0 8.4.0 - 2008-06 CP-40 CP-080417 2211 5 Call forwarding in IMS 8.3.0 8.4.0 - 2008-06 Editorial change done by MCC 8.4.0 8.4.1 2008-09 CP-41 CP-080643 2177 7 Allow Multiple Registrations in Rel 8 by using Outbound 8.4.1 8.5.0 2008-09 CP-41 CP-080539 2178 6 Add Timestamp in Register Request 8.4.1 8.5.0 C1-082810 2008-09 CP-41 CP-080527 2297 1 Cleanup of P-CSCF procedures for inclusion of "tls-yes" and "tls-pending" 8.4.1 8.5.0 C1-082623 2008-09 CP-41 CP-080538 2298 1 Introduction of GIBA (Early IMS) procedures 8.4.1 8.5.0 C1-082657 2008-09 CP-41 CP-080527 2299 1 Add reference to draft-dotson-sip-mutual-auth 8.4.1 8.5.0 C1-082621 2008-09 CP-41 CP-080523 2301 1 Correction of DHCP reference 8.4.1 8.5.0 C1-082620 2008-09 CP-41 CP-080523 2302 Reference correction 8.4.1 8.5.0 C1-082142 2008-09 CP-41 CP-080515 2306 1 Annex A: Correction of SDP connection information 8.4.1 8.5.0 C1-082611 2008-09 CP-41 CP-080523 2308 1 Backward compability issue with P-Access-Network-Info ABNF extension 8.4.1 8.5.0 C1-082625 2008-09 CP-41 CP-080517 2314 Addition of AVPF support and SDP capability negotiation mechanism 8.4.1 8.5.0 C1-082268 2008-09 CP-41 CP-080520 2316 Profile corrections for outbound 8.4.1 8.5.0 C1-082270 2008-09 CP-41 CP-080531 2319 Support of Direct Ethernet access as IP-CAN 8.4.1 8.5.0 C1-082324 2008-09 CP-41 CP-080520 2323 1 Update Outbound Reference 8.4.1 8.5.0 C1-082626 2008-09 CP-41 CP-080523 2325 2 Error Response for Different S-CSCF Assignment 8.4.1 8.5.0 C1-082770 2008-09 CP-41 CP-080527 2328 1 Annex K Technical Corrections 8.4.1 8.5.0 C1-082622 2008-09 CP-41 CP-080528 2329 1 Adding P-Debug-ID to SIP Profile Tables 8.4.1 8.5.0 C1-082752 2008-09 CP-41 CP-080528 2330 2 Subscribing to the debug event package 8.4.1 8.5.0 C1-082781 2008-09 CP-41 CP-080522 2331 4 EPS as IP-CAN 8.4.1 8.5.0 C1-083637 2008-09 CP-41 CP-080523 2333 2 Alignment of IP-CAN specific annexes 8.4.1 8.5.0 C1-082778 2008-09 CP-41 CP-080516 2336 Emergency PUID 8.4.1 8.5.0 C1-082864 2008-09 CP-41 CP-080667 2340 3 Initial emergency registration 8.4.1 8.5.0 2008-09 CP-41 CP-080516 2342 2 Emergency session set-up 8.4.1 8.5.0 C1-083532 2008-09 CP-41 CP-080516 2344 1 P-CSCF handling of emergency sessions 8.4.1 8.5.0 C1-083391 2008-09 CP-41 CP-080516 2346 3 S-CSCF handling of emergency registration 8.4.1 8.5.0 C1-083534 2008-09 CP-41 CP-080523 2347 1 Informative Explanation and Corrections of Profile Tables 8.4.1 8.5.0 C1-083353 2008-09 CP-41 CP-080523 2350 1 More than one contact address per UE 8.4.1 8.5.0 C1-083351 2008-09 CP-41 CP-080528 2351 1 IMS Trace for entities not on the path of the register request 8.4.1 8.5.0 C1-083383 2008-09 CP-41 CP-080528 2352 1 Start and stop procedures for IMS trace 8.4.1 8.5.0 C1-083384 2008-09 CP-41 CP-080636 2353 1 Align emergency session handling outside a security association or TLS session 8.4.1 8.5.0 2008-09 CP-41 CP-080637 2354 3 Addressing privacy requirement 8.4.1 8.5.0 2008-09 CP-41 CP-080523 2359 2 SDP Offer 8.4.1 8.5.0 C1-083398 2008-09 CP-41 CP-080515 2362 SDP referencing error for IBCF (IMS-ALG) 8.4.1 8.5.0 C1-082927 2008-09 CP-41 CP-080523 2363 2 Addition of draft-ietf-sip-199-00 8.4.1 8.5.0 C1-083399 2008-09 CP-41 CP-080523 2365 1 Usage of draft-holmberg-sip-keep-01 for emergency session 8.4.1 8.5.0 C1-083395 2008-09 CP-41 CP-080537 2366 1 Mediactrl and netann specifications 8.4.1 8.5.0 C1-083363 2008-09 CP-41 CP-080536 2369 1 S-CSCF and AS procedures with Enhanced Filter Criteria 8.4.1 8.5.0 C1-083501 2008-09 CP-41 CP-080617 2371 2 Correct handling for <reason> element 8.4.1 8.5.0 2008-09 CP-41 CP-080539 2375 Modification of ci-3gpp2 parameter 8.4.1 8.5.0 C1-083200 2008-09 CP-41 CP-080668 2377 3 Alignment of usage of terms ISIM and ISIM Application 8.4.1 8.5.0 2008-09 CP-41 CP-080524 2378 1 Introduction additional methods of P-CSCF discovery to support IMS Local Breakout 8.4.1 8.5.0 C1-083400 2008-09 CP-41 CP-080515 2381 Alignment with current version of draft-ietf-sip-fork-loop-fix 8.4.1 8.5.0 C1-083246 2008-09 CP-41 CP-080522 2386 1 Relationship to IP-CAN 8.4.1 8.5.0 C1-083424 2008-09 Editorial change done by MCC 8.5.0 8.5.1 2008-12 CP-42 CP-080942 2324 9 Introduction of IMC in support of common IMS 8.5.1 8.6.0 - 2008-12 CP-42 CP-080847 2327 5 SDP Enhancements to support resource allocation 8.5.1 8.6.0 C1-084937 2008-12 CP-42 CP-080840 2332 3 Additional changes for private network indication 8.5.1 8.6.0 C1-084441 2008-12 CP-42 CP-080847 2358 7 Prevent DDOS attack on PSAP 8.5.1 8.6.0 C1-085454 2008-12 CP-42 CP-080840 2383 1 Modifications to private network indication in profile 8.5.1 8.6.0 C1-084080 2008-12 CP-42 CP-080847 2388 3 Annex A fixes regarding draft-ietf-sip-199 8.5.1 8.6.0 C1-085202 2008-12 CP-42 CP-080847 2389 1 Annex A fixes regarding draft-holmberg-sip-keep 8.5.1 8.6.0 C1-084278 2008-12 CP-42 CP-080847 2394 - Correction on setting P-Served-User 8.5.1 8.6.0 C1-083694 2008-12 CP-42 CP-080847 2396 1 Clarification on ICSI and IARI 8.5.1 8.6.0 C1-084203 2008-12 CP-42 CP-080847 2402 2 Interface identifier 8.5.1 8.6.0 C1-085204 2008-12 CP-42 CP-080844 2403 2 UE subscription to reg-evet 8.5.1 8.6.0 C1-084420 2008-12 CP-42 CP-080844 2405 3 UE - multiple contacts registration 8.5.1 8.6.0 C1-085205 2008-12 CP-42 CP-080844 2406 1 UE - multiple contacts authentication and deregistration 8.5.1 8.6.0 C1-084282 2008-12 CP-42 CP-080844 2407 1 UE using multiple contacts 8.5.1 8.6.0 C1-084283 2008-12 CP-42 CP-080845 2408 4 Introduction of additional methods of P-CSCF discovery for EPS to support IMS Local Breakout 8.5.1 8.6.0 C1-085206 2008-12 CP-42 CP-080956 2409 5 UE procedures when multiple P-CSCF discovery procedures are supported 8.5.1 8.6.0 - 2008-12 CP-42 CP-080854 2411 1 Cr addition to section 4 8.5.1 8.6.0 C1-084230 2008-12 CP-42 CP-080854 2412 2 Netann, mediactrl text improvements 8.5.1 8.6.0 C1-084434 2008-12 CP-42 CP-080854 2413 2 Media control for charging, delegation 8.5.1 8.6.0 C1-085256 2008-12 CP-42 CP-080847 2421 - Trademark CDMA terminology 8.5.1 8.6.0 C1-083983 2008-12 CP-42 CP-080843 2423 2 Aligning initial INVITE request usage of Accept header field and profile tables 8.5.1 8.6.0 C1-084438 2008-12 CP-42 CP-080858 2424 1 Clarification of security-verify for TLS 8.5.1 8.6.0 C1-084234 2008-12 CP-42 CP-080840 2425 2 Setting of the Phone-contex paramater when IP-CAN is Ethernet 8.5.1 8.6.0 C1-085201 2008-12 CP-42 CP-080847 2427 - P-CSCF call release upon reception of indication that no ressource is available. 8.5.1 8.6.0 C1-084024 2008-12 CP-42 CP-080847 2428 2 Removing of the cpc parameter by the terminating S-CSCF removes CPC 8.5.1 8.6.0 C1-084435 2008-12 CP-42 CP-080844 2430 2 Clarification of abnormal case for deregistration 8.5.1 8.6.0 C1-085158 2008-12 CP-42 CP-080847 2431 - P-CSCF handling of "integrity-protected" 8.5.1 8.6.0 C1-084048 2008-12 CP-42 CP-080839 2432 2 Registration Procedure for ICS 8.5.1 8.6.0 C1-085200 2008-12 CP-42 CP-080870 2434 1 SMSIP related changes for the profile tables 8.5.1 8.6.0 C1-084202 2008-12 CP-42 CP-080853 2435 1 Adding roles defined for service level interworking for messaging to the profile table 8.5.1 8.6.0 C1-084270 2008-12 CP-42 CP-080840 2436 - Downloading of information to the P-CSCF 8.5.1 8.6.0 C1-084082 2008-12 CP-42 CP-080835 2440 2 Adding reference to Internet Draft on sos URI parameter for emergency calls 8.5.1 8.6.0 C1-085260 2008-12 CP-42 CP-080857 2441 - Update reference for DAI Parameter for the "tel" URI 8.5.1 8.6.0 C1-084120 2008-12 CP-42 CP-080847 2442 3 Inclusion of draft-ietf-sip-body-handling in the profile tables 8.5.1 8.6.0 C1-085209 2008-12 CP-42 CP-080856 2443 3 Deterministic Routeing for overlap signalling 8.5.1 8.6.0 C1-085239 2008-12 CP-42 CP-080840 2444 1 Allowing P-Asserted Identity from an UE 8.5.1 8.6.0 C1-085254 2008-12 CP-42 CP-080835 2446 - Emergency call 8.5.1 8.6.0 C1-084649 2008-12 CP-42 CP-080843 2448 1 Deregistration in 200 (OK) 8.5.1 8.6.0 C1-085435 2008-12 CP-42 CP-080939 2449 2 Revision of 24.229-2449r1 (C1-085416) 8.5.1 8.6.0 - 2008-12 CP-42 CP-080844 2450 2 Usage of outbound in call setup 8.5.1 8.6.0 C1-085450 2008-12 CP-42 CP-080844 2451 - Multiple registrations at P-CSCF 8.5.1 8.6.0 C1-084655 2008-12 CP-42 CP-080940 2452 2 Revision of 24.229-2452r1 (C1-085418) 8.5.1 8.6.0 - 2008-12 CP-42 CP-080844 2454 1 Multiple registrations at S-CSCF 8.5.1 8.6.0 C1-085419 2008-12 CP-42 CP-080869 2456 - Correction of ICSI and IARI feature tag name 8.5.1 8.6.0 C1-084689 2008-12 CP-42 CP-080862 2457 2 Inclusion and Modification of Resource-Priority header at P-CSCF 8.5.1 8.6.0 C1-085451 2008-12 CP-42 CP-080854 2458 1 Media control related profile table updates 8.5.1 8.6.0 C1-085255 2008-12 CP-42 CP-080854 2459 1 Mediactrl reference updates 8.5.1 8.6.0 C1-085257 2008-12 CP-42 CP-080839 2460 2 Instance ID definition 8.5.1 8.6.0 C1-085459 2008-12 CP-42 CP-080844 2462 2 GRUU and Multilple registration 8.5.1 8.6.0 C1-085468 2008-12 CP-42 CP-080959 2464 4 Overlap signalling procedures 8.5.1 8.6.0 - 2008-12 CP-42 CP-080841 2469 - Reference updates (release 6 ietf dependencies) 8.5.1 8.6.0 C1-084898 2008-12 CP-42 CP-080843 2471 - Reference updates (release 7 ietf dependencies) 8.5.1 8.6.0 C1-084903 2008-12 CP-42 CP-080858 2472 1 No domain field for SIP digest 8.5.1 8.6.0 C1-085261 2008-12 CP-42 CP-080858 2473 1 Digest Authentication of Non-Register requests 8.5.1 8.6.0 C1-085262 2008-12 CP-42 CP-080855 2477 1 Minor corrections to configuration of entities for trace 8.5.1 8.6.0 C1-085128 2008-12 CP-42 CP-080843 2479 - Inclusion of missing RFC 3351 reference 8.5.1 8.6.0 C1-085011 2008-12 CP-42 CP-080847 2480 2 Documentation of INFO within the IM CN subsystem 8.5.1 8.6.0 C1-085424 2008-12 CP-42 CP-080847 2481 - Removal of TrGw normative requirements from IBCF 8.5.1 8.6.0 C1-085015 2008-12 CP-42 CP-080847 2482 - Editiorial consistency and best practice 8.5.1 8.6.0 C1-085016 2008-12 CP-42 CP-080965 2483 3 Updates to profile tables to include ICS additions 8.5.1 8.6.0 - 2008-12 CP-42 CP-080849 2484 - Cleanup of various GIBA Editor's notes 8.5.1 8.6.0 C1-085025 2008-12 CP-42 CP-080853 2485 1 Addition of cpim/message and message/imdn+xml 8.5.1 8.6.0 C1-085291 2008-12 CP-42 CP-080847 2494 3 Documenting RFC 5373 8.5.1 8.6.0 C1-085483 2008-12 CP-42 CP-080873 2495 1 S-CSCF and AS procedures with Enhanced Filter Criteria 8.5.1 8.6.0 C1-085292 2008-12 CP-42 CP-080847 2498 2 Call release by the P-CSCF upon resource reservation faillure 8.5.1 8.6.0 C1-085467 2008-12 CP-42 CP-080847 2499 1 Hosted NAT traversal for media flows 8.5.1 8.6.0 C1-085430 2008-12 CP-42 CP-080846 2501 1 Reference updates (release 8 ietf dependencies) 8.5.1 8.6.0 C1-085426 2008-12 CP-42 CP-080847 2502 - Corrections to security overview 8.5.1 8.6.0 C1-085093 2008-12 CP-42 CP-080847 2505 - Identification of public user identity in absence of Authorization header 8.5.1 8.6.0 C1-085131 2008-12 CP-42 Editorial cleanup by ETSI EditHelp! and MCC 8.5.1 8.6.0 2009-03 CP-43 CP-090134 2438 7 Correction of non UE detectable emergency call procedures 8.6.0 8.7.0 C1-091088 2009-03 CP-43 CP-090121 2507 Correction of URN-value for Service Identifiers 8.6.0 8.7.0 C1-090012 2009-03 CP-43 CP-090134 2508 1 Re-selection of S-CSCF during Terminating and Originating Procedures 8.6.0 8.7.0 C1-090991 2009-03 CP-43 CP-090146 2509 2 Re-selection of S-CSCF during Terminating and Originating Procedures when restoration is supported. 8.6.0 8.7.0 C1-091066 2009-03 CP-43 CP-090245 2510 4 Returning an error to trigger a new registration when IMS restoration is supported 8.6.0 8.7.0 - 2009-03 CP-43 CP-090225 2511 4 Re-selection of S-CSCF during Re-registration when IMS restoration is supported 8.6.0 8.7.0 - 2009-03 CP-43 CP-090134 2514 1 Outbound with IMS AKA 8.6.0 8.7.0 C1-090992 2009-03 CP-43 CP-090134 2515 2 Registration procedure at the S-CSCF 8.6.0 8.7.0 C1-091041 2009-03 CP-43 CP-090134 2516 3 P-CSCFprocessing 200 (OK) 8.6.0 8.7.0 C1-091085 2009-03 CP-43 CP-090134 2517 4 Multiple de-registrations 8.6.0 8.7.0 C1-091111 2009-03 CP-43 CP-090134 2519 1 Instance-ID in INVITE 8.6.0 8.7.0 C1-090997 2009-03 CP-43 CP-090134 2520 Multiple contact addresses 8.6.0 8.7.0 C1-090042 2009-03 CP-43 CP-090130 2524 3 Support for eHRPD 8.6.0 8.7.0 C1-091381 2009-03 CP-43 CP-090155 2525 1 Adding the role of The Early Session Disposition Type 8.6.0 8.7.0 C1-090950 2009-03 CP-43 CP-090134 2527 Cleanup inclusion of draft-ietf-sip-body-handling in the profile tables 8.6.0 8.7.0 C1-090201 2009-03 CP-43 CP-090116 2529 2 Aligning with draft-ietf-sip-location-conveyance-12 8.6.0 8.7.0 C1-091040 2009-03 CP-43 CP-090134 2530 1 Addressing privacy requirement for emergency calls 8.6.0 8.7.0 C1-090999 2009-03 CP-43 CP-090116 2532 1 Correcting condition for using indicating use of emergency registration 8.6.0 8.7.0 C1-090959 2009-03 CP-43 CP-090224 2534 3 Overlap signalling en-bloc conversion procedures 8.6.0 8.7.0 - 2009-03 CP-43 CP-090209 2535 3 Overlap signalling digit collection procedures 8.6.0 8.7.0 - 2009-03 CP-43 CP-090134 2537 1 Correction of registration duration value 8.6.0 8.7.0 C1-091024 2009-03 CP-43 CP-090127 2540 1 Corrections to E-UTRAN specific aspects 8.6.0 8.7.0 C1-090850 2009-03 CP-43 CP-090134 2541 Miscellaneous corrections to annex B 8.6.0 8.7.0 C1-090377 2009-03 CP-43 CP-090142 2543 1 Miscellaneous corrections to Annex M 8.6.0 8.7.0 C1-090985 2009-03 CP-43 CP-090142 2544 1 Phone-context parameter value for cdma2000® 8.6.0 8.7.0 C1-090986 2009-03 CP-43 CP-090142 2545 1 Common IMS for MGW and MRF 8.6.0 8.7.0 C1-090987 2009-03 CP-43 CP-090134 2546 4 Deterministic behaviour for Call Forwarding 8.6.0 8.7.0 C1-091122 2009-03 CP-43 CP-090136 2547 1 Overlap Corrections 8.6.0 8.7.0 C1-090962 2009-03 CP-43 CP-090116 2550 1 Alignment of emergency indication with draft-patel-ecrit-sos-parameter-03 8.6.0 8.7.0 C1-090968 2009-03 CP-43 CP-090272 2553 3 Use of multiple access technologies in IMS 8.6.0 8.7.0 - 2009-03 CP-43 CP-090134 2555 Alignment of authentication parameter terminology 8.6.0 8.7.0 C1-090534 2009-03 CP-43 CP-090134 2556 Use of access-class and access-type constructs in the P-Access-Network-Info header field 8.6.0 8.7.0 C1-090535 2009-03 CP-43 CP-090134 2558 P-Served-User header field corrections (profile) 8.6.0 8.7.0 C1-090537 2009-03 CP-43 CP-090134 2560 Editorial consistency and best practice 8.6.0 8.7.0 C1-090539 2009-03 CP-43 CP-090141 2561 1 Removal of redundant NASS bundled authentication text for S-CSCF 8.6.0 8.7.0 C1-090969 2009-03 CP-43 CP-090150 2564 1 Emergency call handling for CS media 8.6.0 8.7.0 C1-090908 2009-03 CP-43 CP-090118 2574 2 Correction to Annex A / SIP extensions for media authorization 8.6.0 8.7.0 C1-091120 2009-03 CP-43 CP-090275 2578 4 Correction to Annex A /P-Access-Network-Info 8.6.0 8.7.0 - 2009-03 CP-43 CP-090134 2579 2 Correction to Annex A /P-User-Database header 8.6.0 8.7.0 C1-091084 2009-03 CP-43 CP-090134 2582 2 Routeing B2BUA transparency 8.6.0 8.7.0 C1-091078 2009-03 CP-43 CP-090134 2583 1 Call release by P-CSCF- Editorial correction 8.6.0 8.7.0 C1-091013 2009-03 CP-43 CP-090118 2584 1 References correction 8.6.0 8.7.0 C1-091014 2009-03 CP-43 CP-090142 2595 1 Corrections for cdma2000® HRPD Emergency Services 8.6.0 8.7.0 C1-090988 2009-03 CP-43 CP-090127 2596 Corrections to EPS as IMS access technology Annex 8.6.0 8.7.0 C1-090685 2009-03 CP-43 CP-090135 2597 1 Update of references to SIP debug internet drafts 8.6.0 8.7.0 C1-090970 2009-03 CP-43 CP-090159 2598 1 Handling of provisioned mode of the resource allocation used for IMS media 8.6.0 8.7.0 C1-091069 2009-03 CP-43 CP-090237 2601 2 Reference correction 8.6.0 8.7.0 C1-091115 2009-06 CP-44 CP-090428 2518 5 Flow- token in the Record-Route 8.7.0 8.8.0 C1-091475 2009-06 CP-44 CP-090398 2539 8 Mechanism for UE to identify a SIP URI that has an associated tel URI 8.7.0 8.8.0 C1-092241 2009-06 CP-44 CP-090428 2557 3 Application server usage of P-Served-User header field 8.7.0 8.8.0 C1-092077 2009-06 CP-44 CP-090399 2605 2 P-CSCF releasing a dialog 8.7.0 8.8.0 C1-092084 2009-06 CP-44 CP-090399 2607 2 S-CSCF releasing a dialog 8.7.0 8.8.0 C1-092086 2009-06 CP-44 CP-090428 2608 2 GRUU translation 8.7.0 8.8.0 C1-092087 2009-06 CP-44 CP-090428 2610 1 Correct backwards emergency notification procedure 8.7.0 8.8.0 C1-092072 2009-06 CP-44 CP-090428 2611 Correction of implementation error of CR2537r1 8.7.0 8.8.0 C1-091494 2009-06 CP-44 CP-090428 2612 1 BGCF routing 8.7.0 8.8.0 C1-092074 2009-06 CP-44 CP-090403 2614 Correction of 3GPP URN link 8.7.0 8.8.0 C1-091504 2009-06 CP-44 CP-090428 2616 2 RFC 2833 substituted by RFC 4733 8.7.0 8.8.0 C1-092050 2009-06 CP-44 CP-090428 2617 Call Forwarding Leftover 8.7.0 8.8.0 C1-091510 2009-06 CP-44 CP-090415 2618 1 Correction Identity handling for NGCN 8.7.0 8.8.0 C1-091974 2009-06 CP-44 CP-090419 2619 Reference Update draft-ietf-mmusic-sdp-cs 8.7.0 8.8.0 C1-091513 2009-06 CP-44 CP-090428 2620 1 RFC reference fix 8.7.0 8.8.0 C1-092075 2009-06 CP-44 CP-090428 2625 1 Deterministic XML schema 8.7.0 8.8.0 C1-092204 2009-06 CP-44 CP-090398 2634 Emergency call treatment of P-Preferred-Identity header field in profile 8.7.0 8.8.0 C1-091649 2009-06 CP-44 CP-090405 2635 1 Subdivision of digit collection text 8.7.0 8.8.0 C1-091967 2009-06 CP-44 CP-090428 2636 Editorial changes 8.7.0 8.8.0 C1-091655 2009-06 CP-44 CP-090398 2639 1 Correcting emergency registration support and access type 8.7.0 8.8.0 C1-092003 2009-06 CP-44 CP-090397 2645 1 Correction to Annex A /Caller preferences directives 8.7.0 8.8.0 C1-092079 2009-06 CP-44 CP-090428 2657 2 Alignment of Cx reference point procedures withTS 29.228 procedures 8.7.0 8.8.0 C1-092211 2009-06 CP-44 CP-090415 2658 2 Correction to GRUU procedures to ensure that sessions using UE assigned Public GRUUs don't fail 8.7.0 8.8.0 C1-092219 2009-06 CP-44 CP-090428 2659 Removing obsolete Editor's Note 8.7.0 8.8.0 C1-091854 2009-06 CP-44 CP-090428 2660 1 Correction of instance ID related Editor's Note and text 8.7.0 8.8.0 C1-092076 2009-06 CP-44 CP-090398 2662 Version update for "sos" URI parameter Internet Draft 8.7.0 8.8.0 C1-091857 2009-06 CP-44 CP-090428 2663 Contact Header in PUBLISH method 8.7.0 8.8.0 C1-091879 2009-06 CP-44 CP-090428 2666 Removing non-essential and incorrect statement regarding ordering of codec formats in the SDP offer 8.7.0 8.8.0 C1-092114 2009-06 CP-44 CP-090400 2667 1 Correction to Annex A /P-User-Database 8.7.0 8.8.0 C1-092209 2009-06 CP-44 CP-090430 2644 2 Addition of capability for delivering the original Request-URI 8.8.0 9.0.0 C1-092227 2009-09 CP-45 CP-090696 2671 2 Service-Route/Path header handling for fetching bindings 9.0.0 9.1.0 C1-093049 2009-09 CP-45 CP-090644 2674 2 Inconsistency between text and XML schema 9.0.0 9.1.0 C1-093709 2009-09 CP-45 CP-090650 2675 Confusing text in L.2.2.5.1A 9.0.0 9.1.0 C1-092401 2009-09 CP-45 CP-090658 2676 3 Emergency call handling in P-CSCF and UE 9.0.0 9.1.0 C1-093070 2009-09 CP-45 CP-090649 2679 1 TISPAN IBCF review comment fixes 9.0.0 9.1.0 C1-092903 2009-09 CP-45 CP-090696 2680 TISPAN review comments - minor fixes 9.0.0 9.1.0 C1-092407 2009-09 CP-45 CP-090657 2682 1 Contact port in non REGISTER request with AKA 9.0.0 9.1.0 C1-092409 2009-09 CP-45 CP-090696 2684 1 reg/debug event package subscription headers 9.0.0 9.1.0 C1-092987 2009-09 CP-45 CP-090664 2686 2 Connection of complex UEs to IMS 9.0.0 9.1.0 C1-093739 2009-09 CP-45 CP-090737 2689 2 Calling party category (cpc) 9.0.0 9.1.0 - 2009-09 CP-45 CP-090696 2691 1 UE procedure on registration failure 9.0.0 9.1.0 C1-093015 2009-09 CP-45 CP-090658 2693 1 Correction of BGCF procedures 9.0.0 9.1.0 C1-092989 2009-09 CP-45 CP-090696 2694 2 Topology hiding on Path header 9.0.0 9.1.0 C1-093016 2009-09 CP-45 CP-090682 2695 1 Create XML source files 9.0.0 9.1.0 C1-093029 2009-09 CP-45 CP-090667 2697 1 Correcting preventing of DDOS attack on registrar 9.0.0 9.1.0 C1-092952 2009-09 CP-45 CP-090657 2700 Correcting mismatch in conditions for non-UE detectable emergency call 9.0.0 9.1.0 C1-092494 2009-09 CP-45 CP-090659 2702 1 The "comp" parameter 9.0.0 9.1.0 C1-093702 2009-09 CP-45 CP-090659 2704 Routing procedure 9.0.0 9.1.0 C1-092501 2009-09 CP-45 CP-090664 2706 UE as an externally attached network 9.0.0 9.1.0 C1-092503 2009-09 CP-45 CP-090725 2710 2 Require with the option-tag "outbound" 9.0.0 9.1.0 - 2009-09 CP-45 CP-090658 2712 1 Outbound support 9.0.0 9.1.0 C1-092994 2009-09 CP-45 CP-090657 2718 2 Contact header in registration 9.0.0 9.1.0 C1-093704 2009-09 CP-45 CP-090659 2720 1 S-CSCF not supporting Outbound registration 9.0.0 9.1.0 C1-093002 2009-09 CP-45 CP-090648 2722 2 NAT traversal without outbound 9.0.0 9.1.0 C1-093041 2009-09 CP-45 CP-090651 2724 Duplicate subclauses in Annex O 9.0.0 9.1.0 C1-092530 2009-09 CP-45 CP-090664 2727 2 P-CSCF handling alignments for priviledged senders 9.0.0 9.1.0 C1-093486 2009-09 CP-45 CP-090664 2729 1 P-CSCF handling for NCGN as regular UE 9.0.0 9.1.0 C1-092932 2009-09 CP-45 CP-090664 2731 5 S-CSCF handling alignments for NGCN 9.0.0 9.1.0 C1-093910 2009-09 CP-45 CP-090664 2741 2 Use of GRUU by UEs that perform the functions of an external attached network 9.0.0 9.1.0 C1-093905 2009-09 CP-45 CP-090658 2743 Correction of alignment of Cx reference point procedures withTS 29.228 procedures 9.0.0 9.1.0 C1-092658 2009-09 CP-45 CP-090659 2745 Reference update for draft-montemurro-gsma-imei-urn 9.0.0 9.1.0 C1-092660 2009-09 CP-45 CP-090696 2746 1 Annex K: P-CSCF alignment 9.0.0 9.1.0 C1-093017 2009-09 CP-45 CP-090696 2747 1 Annex K: S-CSCF alignment 9.0.0 9.1.0 C1-093018 2009-09 CP-45 CP-090696 2748 Annex K: Removal of IBCF modifications 9.0.0 9.1.0 C1-092664 2009-09 CP-45 CP-090658 2752 2 Keep-alives for emergency calls 9.0.0 9.1.0 C1-093043 2009-09 CP-45 CP-090649 2755 1 P-CSCF forwarding request towards entry point 9.0.0 9.1.0 C1-092910 2009-09 CP-45 CP-090659 2759 1 Re-INVITE for precondition status indication 9.0.0 9.1.0 C1-093011 2009-09 CP-45 CP-090658 2761 1 Digest URI verification fix 9.0.0 9.1.0 C1-093034 2009-09 CP-45 CP-090696 2762 SDP in session modification messages 9.0.0 9.1.0 C1-092678 2009-09 CP-45 CP-090658 2764 Correction of table condition: AoC roles 9.0.0 9.1.0 C1-092680 2009-09 CP-45 CP-090732 2766 5 Aligning IANA registration of MIME type "application/3gpp-ims+xml" 9.0.0 9.1.0 - 2009-09 CP-45 CP-090690 2767 4 Emergency call introduction 9.0.0 9.1.0 C1-093946 2009-09 CP-45 CP-090690 2768 1 Emergency call changes to Annex B (GPRS) 9.0.0 9.1.0 C1-092825 2009-09 CP-45 CP-090690 2769 1 Emergency call changes to Annex L (EPS) 9.0.0 9.1.0 C1-092826 2009-09 CP-45 CP-090667 2778 1 How the P-CSCF forwards the request to the next hop excluding the REGISTER method. 9.0.0 9.1.0 C1-093006 2009-09 CP-45 CP-090696 2779 1 Clarification of a target refresh request. 9.0.0 9.1.0 C1-093007 2009-09 CP-45 CP-090660 2780 1 No Proxy-Authentication-Info header 9.0.0 9.1.0 C1-093721 2009-09 CP-45 CP-090664 2781 2 No P-P-I from NGCN 9.0.0 9.1.0 C1-093790 2009-09 CP-45 CP-090696 2784 1 Trust domain clarification 9.0.0 9.1.0 C1-093753 2009-09 CP-45 CP-090696 2785 1 Clarification of Handling of geo-local numbers 9.0.0 9.1.0 C1-093754 2009-09 CP-45 CP-090645 2789 IOI Handling 9.0.0 9.1.0 C1-093266 2009-09 CP-45 CP-090671 2791 1 Invalid Registration 9.0.0 9.1.0 C1-093745 2009-09 CP-45 CP-090665 2793 1 IBCF and P-Asserted-Identity 9.0.0 9.1.0 C1-093783 2009-09 CP-45 CP-090657 2797 1 Correct the preconditions for NBA mechanism 9.0.0 9.1.0 C1-093760 2009-09 CP-45 CP-090682 2800 4 Correction of dialog correlation 9.0.0 9.1.0 C1-093985 2009-09 CP-45 CP-090696 2801 Corrections to SDP profile table entries 9.0.0 9.1.0 C1-093449 2009-09 CP-45 CP-090657 2803 1 Adding RFC 3890 and maximum packet rate to SDP profile tables 9.0.0 9.1.0 C1-093762 2009-09 CP-45 CP-090679 2806 2 Correcting duplicate mentioning of 802.3y 9.0.0 9.1.0 C1-093913 2009-09 CP-45 CP-090647 2813 Update of reference to I-D for sos URI parameter and miscellaneous reference corrections 9.0.0 9.1.0 C1-093574 2009-09 CP-45 CP-090659 2815 2 Use of ports for SIP between UE and P-CSCF 9.0.0 9.1.0 C1-093908 2009-09 CP-45 CP-090659 2817 1 Profile table correction on the support of security mechanism 9.0.0 9.1.0 C1-093578 2009-09 CP-45 CP-090696 2819 1 Correction on the summary of security mechanism 9.0.0 9.1.0 C1-093767 2009-09 CP-45 CP-090657 2827 1 Clarification on identity usage for NBA 9.0.0 9.1.0 C1-093769 2009-09 CP-45 CP-090664 2829 Describe the right behaviour of the IBCF 9.0.0 9.1.0 C1-093609 2009-12 CP-46 CP-090923 2834 3 Correction to introduce support for IMSVoPS 9.1.0 9.2.0 C1-095602 2009-12 CP-46 CP-090923 2835 2 Transcoding Control at MRF using RFC 4117 9.1.0 9.2.0 C1-094737 2009-12 CP-46 CP-090890 2839 Inclusion of draft-ietf-sipcore-invfix 9.1.0 9.2.0 C1-094120 2009-12 CP-46 CP-090890 2843 1 Inclusion of draft-ietf-sip-ipv6-abnf-fix 9.1.0 9.2.0 C1-094531 2009-12 CP-46 CP-090891 2847 Change of ua-profile package to xcap-diff package 9.1.0 9.2.0 C1-094131 2009-12 CP-46 CP-090892 2850 Release 7 IETF reference updates for emergency call 9.1.0 9.2.0 C1-094134 2009-12 CP-46 CP-090940 2854 Inclusion of draft-ietf-sip-record-route-fix 9.1.0 9.2.0 C1-094152 2009-12 CP-46 CP-090940 2855 1 Correction of support of trust domain boundaries for identity 9.1.0 9.2.0 C1-094566 2009-12 CP-46 CP-090923 2856 1 Inclusion of roles for XCAP client / server at the Ut reference point for supplementary services 9.1.0 9.2.0 C1-094538 2009-12 CP-46 CP-090920 2858 Update of draft-ietf-sip-body-handling reference to RFC 5621 9.1.0 9.2.0 C1-094215 2009-12 CP-46 CP-090940 2860 xsd file alignment with main document 9.1.0 9.2.0 C1-094316 2009-12 CP-46 CP-090940 2861 1 Textual layout errors in Annex A 9.1.0 9.2.0 C1-094568 2009-12 CP-46 CP-090936 2863 2 Media plane security 9.1.0 9.2.0 C1-094729 2009-12 CP-46 CP-090940 2866 1 3rd party registration failure 9.1.0 9.2.0 C1-094336 2009-12 CP-46 CP-090923 2689 4 Detecting requests destined for a PSAP 9.1.0 9.2.0 C1-095704 2009-12 CP-46 CP-091016 2875 5 Alignment of 24.229 with draft-ietf-sipcore-info-events 9.1.0 9.2.0 - 2009-12 CP-46 CP-090940 2877 1 Correction of indication to the user that an emergency call was made 9.1.0 9.2.0 C1-094582 2009-12 CP-46 CP-090940 2881 2 Annex A /183 (Session Progress) response 9.1.0 9.2.0 C1-094733 2009-12 CP-46 CP-090890 2885 Annex A / c and m paramters in media description in SDP 9.1.0 9.2.0 C1-094382 2009-12 CP-46 CP-090890 2889 Annex A / User-Agent in PUBLISH responses 9.1.0 9.2.0 C1-094387 2009-12 CP-46 CP-091049 2891 3 Annex A / Allow events 9.1.0 9.2.0 - 2009-12 CP-46 CP-090940 2892 1 Annex A /MIME-Version header 9.1.0 9.2.0 C1-094571 2009-12 CP-46 CP-090940 2893 2 Annex A / Require header 9.1.0 9.2.0 C1-094734 2009-12 CP-46 CP-090940 2894 1 Application of trust domains to the P-Early-media header field 9.1.0 9.2.0 C1-094573 2009-12 CP-46 CP-090923 2895 2 Allowing direct routing between AS and MRFC 9.1.0 9.2.0 C1-094736 2009-12 CP-46 CP-090936 2900 3 Registration of IMS media plane security capabilities 9.1.0 9.2.0 C1-094730 2009-12 CP-46 CP-090893 2905 Updating of outbound and related references 9.1.0 9.2.0 C1-094826 2009-12 CP-46 CP-090894 2908 Updating of GRUU references 9.1.0 9.2.0 C1-094832 2009-12 CP-46 CP-090940 2909 Miscellaneous editorial corrections 9.1.0 9.2.0 C1-094850 2009-12 CP-46 CP-090892 2912 1 Removal of outstanding Editor's notes for EMC1 9.1.0 9.2.0 C1-095486 2009-12 CP-46 CP-090896 2914 Removal of outstanding Editor's note for ServID 9.1.0 9.2.0 C1-094855 2009-12 CP-46 CP-090903 2916 Removal of outstanding Editor's note for Overlap 9.1.0 9.2.0 C1-094857 2009-12 CP-46 CP-090940 2924 2 Definition of globally Globally Routeable SIP URI. 9.1.0 9.2.0 C1-095676 2009-12 CP-46 CP-090940 2925 1 Handling of Request-URI with tel URI and sip URI containing user=phone by the BGCF 9.1.0 9.2.0 C1-095438 2009-12 CP-46 CP-090940 2926 2 Additional routeing capabilities 9.1.0 9.2.0 C1-095677 2009-12 CP-46 CP-090902 2932 1 Handling of Route by the I-CSCF 9.1.0 9.2.0 C1-095607 2009-12 CP-46 CP-090902 2934 1 Annex A/ P-Charging-Vector 9.1.0 9.2.0 C1-095606 2009-12 CP-46 CP-090902 2936 2 REGISTERs for Keeping NAT binding /Annex F 9.1.0 9.2.0 C1-095703 2009-12 CP-46 CP-090938 2940 1 Ml reference point additions – general aspects 9.1.0 9.2.0 C1-095467 2009-12 CP-46 CP-090938 2941 1 Ml reference point additions – location determination summary 9.1.0 9.2.0 C1-095468 2009-12 CP-46 CP-090938 2942 3 Ml reference point additions – E-CSCF changes 9.1.0 9.2.0 C1-095726 2009-12 CP-46 CP-090938 2943 3 Ml reference point additions – new LRF functionality 9.1.0 9.2.0 C1-095727 2009-12 CP-46 CP-090938 2944 Ml reference point additions – profile changes 9.1.0 9.2.0 C1-094995 2009-12 CP-46 CP-090902 2946 Correction of profile table on the role for UE 9.1.0 9.2.0 C1-094997 2009-12 CP-46 CP-090936 2951 2 Indicating End-to-Access Edge Media Plane Security in session set-up 9.1.0 9.2.0 C1-095700 2009-12 CP-46 CP-090895 2954 2 Correct Phone-Context parameter coding 9.1.0 9.2.0 C1-095688 2009-12 CP-46 CP-090940 2955 2 Human readable UE name 9.1.0 9.2.0 C1-095648 2009-12 CP-46 CP-090927 2959 2 E-CSCF invoking EATF 9.1.0 9.2.0 C1-095718 2009-12 CP-46 CP-090930 2960 2 IMEI in unauthenticated emergency call in EPS and GPRS 9.1.0 9.2.0 C1-095714 2009-12 CP-46 CP-090930 2961 1 Emergency bearer activation in EPS and GPRS 9.1.0 9.2.0 C1-095309 2009-12 CP-46 CP-090892 2964 Alignment of 24.229 with draft-patel-ecrit-sos-parameter-07 9.1.0 9.2.0 C1-095069 2009-12 CP-46 CP-090892 2967 1 Removal of editor's note in 5.4.8.2 – use of "sos" in GRUU 9.1.0 9.2.0 C1-095489 2009-12 CP-46 CP-090923 2971 1 Reason header in provisional responses 9.1.0 9.2.0 C1-095472 2009-12 CP-46 CP-090940 2976 Correcting SIP interface to VoiceXML media services 9.1.0 9.2.0 C1-095187 2009-12 CP-46 CP-090940 2980 1 Annex A: Support of INFO for CAT and CRS 9.1.0 9.2.0 C1-095445 2009-12 CP-46 CP-090940 2981 2 Removal of editor's note on 199 provisional response 9.1.0 9.2.0 C1-095649 2009-12 CP-46 CP-090983 2970 2 Update to annex J based on draft-patel-dispatch-cpc-oli-parameter 9.1.0 9.2.0 - 2010-03 CP-47 CP-100131 2810 3 Correcting handling of emergency session requests made by unregistered users 9.2.0 9.3.0 C1-101129 2010-03 CP-47 CP-100110 2930 4 Handling of Request-URI with tel URI and sip URI containing user=phone by the S-CSCF 9.2.0 9.3.0 C1-100993 2010-03 CP-47 CP-100104 2958 4 Emergency session with P-CSCF in visited network 9.2.0 9.3.0 C1-100720 2010-03 CP-47 CP-100110 2990 1 IETF reference updates (IMSProtoc2 related) 9.2.0 9.3.0 C1-100210 2010-03 CP-47 CP-100124 2992 3 Support of draft-ietf-mmusic-sdp-media-capabilities 9.2.0 9.3.0 C1-101151 2010-03 CP-47 CP-100153 2994 5 Adding 1XRTT Femto support for the 3GPP2-1X access type 9.2.0 9.3.0 C1-101180 2010-03 CP-47 CP-100149 2996 1 Correction for e2ae syntax 9.2.0 9.3.0 C1-100200 2010-03 CP-47 CP-100153 2997 2 Implications of resource reservation failure 9.2.0 9.3.0 C1-100704 2010-03 CP-47 CP-100143 2998 1 RFC 4488 in Annex A 9.2.0 9.3.0 C1-100176 2010-03 CP-47 CP-100153 3000 1 Removing an Editor's note in the reference section 9.2.0 9.3.0 C1-100135 2010-03 CP-47 CP-100153 3001 4 Handling of Subscription context information by intermediary entities 9.2.0 9.3.0 C1-101116 2010-03 CP-47 CP-100151 3002 1 Editorial update: adding missing defenitions, correcting typos and inconsistencies 9.2.0 9.3.0 C1-100198 2010-03 CP-47 CP-100151 3003 3 Correcting providing of additional location information to LRF 9.2.0 9.3.0 C1-101117 2010-03 CP-47 CP-100149 3004 1 Editorial amendments for end to access edge media security 9.2.0 9.3.0 C1-100233 2010-03 CP-47 CP-100149 3005 2 Improvements to end to access edge security text 9.2.0 9.3.0 C1-100780 2010-03 CP-47 CP-100149 3006 1 MGCF is not involved in e2ae security 9.2.0 9.3.0 C1-100234 2010-03 CP-47 CP-100149 3007 1 UE requirements in the absence of P-CSCF support of end to access edge security 9.2.0 9.3.0 C1-100202 2010-03 CP-47 CP-100149 3008 1 Profile additions for end to access edge security 9.2.0 9.3.0 C1-100203 2010-03 CP-47 CP-100149 3009 1 Coverage of media security in the security introduction 9.2.0 9.3.0 C1-100204 2010-03 CP-47 CP-100151 3010 1 Making the E-CSCF responsible for the domain of incoming Request-URI 9.2.0 9.3.0 C1-100230 2010-03 CP-47 CP-100151 3011 1 Usage of P-Charging-Vector header within the emergency call architecture 9.2.0 9.3.0 C1-100199 2010-03 CP-47 CP-100151 3013 1 Delivery of location by the E-CSCF 9.2.0 9.3.0 C1-100159 2010-03 CP-47 CP-100151 3014 2 Structure of reference identifier 9.2.0 9.3.0 C1-100941 2010-03 CP-47 CP-100151 3015 1 Handling of editor's note on subscribing to all dialogs 9.2.0 9.3.0 C1-100160 2010-03 CP-47 CP-100109 3017 Resolution of editor's notes related to PRIOR 9.2.0 9.3.0 C1-100208 2010-03 CP-47 CP-100230 3019 1 Removal of editor's notes relating to learning of trust domain boundaries and information saved during registration 9.2.0 9.3.0 - 2010-03 CP-47 CP-100135 3020 1 Correcting IP-CAN documentation 9.2.0 9.3.0 C1-100944 2010-03 CP-47 CP-100153 3024 P-CSCF Note correction 9.2.0 9.3.0 C1-100339 2010-03 CP-47 CP-100153 3025 Authentication-Info header field 9.2.0 9.3.0 C1-100340 2010-03 CP-47 CP-100153 3026 4 DTMF Info Package definition 9.2.0 9.3.0 C1-101119 2010-03 CP-47 CP-100110 3028 Removal of editor's note: 199 (Early Dialog Terminated) option-tag 9.2.0 9.3.0 C1-100366 2010-03 CP-47 CP-100111 3031 Removal of editor's note: Annex K NAT traversal 9.2.0 9.3.0 C1-100369 2010-03 CP-47 CP-100107 3035 Closure of SAES related editor's notes 9.2.0 9.3.0 C1-100419 2010-03 CP-47 CP-100117 3037 Addressing editor's notes relating to NASS bundled authentication 9.2.0 9.3.0 C1-100421 2010-03 CP-47 CP-100110 3039 Removal of editor's notes relating to emergency call 9.2.0 9.3.0 C1-100423 2010-03 CP-47 CP-100110 3043 Removal of outstanding Editor's note on IOI 9.2.0 9.3.0 C1-100436 2010-03 CP-47 CP-100107 3045 Incorrect NAS message in Annex L 9.2.0 9.3.0 C1-100454 2010-03 CP-47 CP-100135 3048 2 Delete EN pertaining to RFC 4117 9.2.0 9.3.0 C1-101156 2010-03 CP-47 CP-100122 3053 Incorrect trigger in I-CSCF for restoration procedures 9.2.0 9.3.0 C1-100462 2010-03 CP-47 CP-100112 3054 1 Clean up editor's notes on subscription to debug event package 9.2.0 9.3.0 C1-100983 2010-03 CP-47 CP-100149 3055 1 Exchanging media plane security capabilities at registration 9.2.0 9.3.0 C1-100971 2010-03 CP-47 CP-100218 3056 2 Profile table changes for exchanging media plane security capabilities at registration 9.2.0 9.3.0 - 2010-03 CP-47 CP-100153 3057 1 Corrections to profile table entries related to security agreement 9.2.0 9.3.0 C1-100973 2010-03 CP-47 CP-100110 3059 1 Inclusion of draft alert-urns for INVITE Responses 9.2.0 9.3.0 C1-100954 2010-03 CP-47 CP-100119 3063 Reference update of draft-ietf-mediactrl-vxml 9.2.0 9.3.0 C1-100518 2010-03 CP-47 CP-100118 3065 1 Address the UUS related Editor's Note 9.2.0 9.3.0 C1-100986 2010-03 CP-47 CP-100110 3069 1 Correcting missing reference 9.2.0 9.3.0 C1-100991 2010-03 CP-47 CP-100153 3072 4 Session ID profile table alignment 9.2.0 9.3.0 C1-101176 2010-03 CP-47 CP-100105 3075 1 Annex A/ Fixing of missing status support in Tables 9.2.0 9.3.0 C1-100982 2010-03 CP-47 CP-100105 3078 Annex A/ P-Media-Authorization support 9.2.0 9.3.0 C1-100666 2010-03 CP-47 CP-100105 3081 Annex A / integration of resource management and SIP 9.2.0 9.3.0 C1-100670 2010-03 CP-47 CP-100247 3082 2 Additional routeing capabilities 9.2.0 9.3.0 - 2010-03 CP-47 CP-100138 3083 3 P-CSCF Restoration Procedures 9.2.0 9.3.0 C1-101262 2010-03 CP-47 CP-100110 3086 New version of IETF draft-yu-tel-dai 9.2.0 9.3.0 C1-100684 2010-03 CP-47 CP-100110 3092 Abnormal Digest procedures fix 9.2.0 9.3.0 C1-100692 2010-03 CP-47 CP-100128 3094 IMDN reference update 9.2.0 9.3.0 C1-100694 2010-03 CP-47 CP-100140 3095 1 I4 applicability and EATF functionality 9.2.0 9.3.0 C1-100940 2010-03 CP-47 CP-100153 3096 Failure of GPRS and EPS resource reservation 9.2.0 9.3.0 C1-100703 2010-03 CP-47 CP-100142 3097 3 Addition of Dialog Event package to profile tables in support of Inter-UE transfer 9.2.0 9.3.0 C1-101162 2010-03 CP-47 CP-100151 3098 Correction of reference to RFC 4235 9.2.0 9.3.0 C1-100966 2010-03 CP-47 CP-100144 3099 Emergency call clarifications in the absence of registration 9.2.0 9.3.0 C1-100774 2010-03 CP-47 CP-100110 3101 Correct authentication and registration referencing for emergency registration 9.2.0 9.3.0 C1-100805 2010-03 CP-47 CP-100107 3103 P-Access-Network-Info correction for LTE 9.2.0 9.3.0 C1-100808 2010-03 CP-47 CP-100104 3106 Update reference for draft-patel-ecrit-sos-parameter 9.2.0 9.3.0 C1-100811 2010-03 CP-47 CP-100216 3033 2 Updating of SAES related references 9.2.0 9.3.0 - 2010-03 CP-47 Editorial correction 9.3.0 9.3.1 - 2010-06 CP-48 CP-100364 3012 3 Completion of dialog event package usage 9.3.1 9.4.0 C1-101860 2010-06 CP-48 CP-100363 3118 1 Profile table changes for SDES media plane security role 9.3.1 9.4.0 C1-101889 2010-06 CP-48 CP-100363 3119 Using SDES cryptro attribute 9.3.1 9.4.0 C1-101395 2010-06 CP-48 CP-100346 3121 Wrong requirements for ICS MSC in profile tables 9.3.1 9.4.0 C1-101399 2010-06 CP-48 CP-100337 3129 Reference updates 9.3.1 9.4.0 C1-101472 2010-06 CP-48 CP-100359 3130 1 norefersub corrections 9.3.1 9.4.0 C1-101859 2010-06 CP-48 CP-100364 3131 Charging tidyup 9.3.1 9.4.0 C1-101487 2010-06 CP-48 CP-100359 3136 1 MSC Server assisted mid-call feature - conferencing 9.3.1 9.4.0 C1-102032 2010-06 CP-48 CP-100340 3142 1 RFC4694 for IBCF 9.3.1 9.4.0 C1-101814 2010-06 CP-48 CP-100364 3148 3xx response replaced by response 9.3.1 9.4.0 C1-101584 2010-06 CP-48 CP-100340 3151 1 Use of P-Served-User header field in user location procedure 9.3.1 9.4.0 C1-101812 2010-06 CP-48 CP-100340 3155 2 IBCF and Content-Disposition 9.3.1 9.4.0 C1-102031 2010-06 CP-48 CP-100351 3158 1 Addition of MSRP SDP a=path attribute 9.3.1 9.4.0 C1-101820 2010-06 CP-48 CP-100363 3161 1 Roles relating to media plane security 9.3.1 9.4.0 C1-101890 2010-06 CP-48 CP-100354 3162 2 IMS available 9.3.1 9.4.0 C1-102103 2010-06 CP-48 CP-100367 3040 1 Identifying an emergency call at the P-CSCF 9.4.0 10.0.0 C1-101504 2010-06 CP-48 CP-100367 3110 Handling of Privacy header 9.4.0 10.0.0 C1-101838 2010-06 CP-48 CP-100367 3113 2 S-CSCF triggering of Additional Routeing capability 9.4.0 10.0.0 C1-102042 2010-06 CP-48 CP-100367 3114 2 xPON access type values in P-Access-Network-Info 9.4.0 10.0.0 C1-102043 2010-06 CP-48 CP-100367 3116 1 Digit manipulation 9.4.0 10.0.0 C1-101843 2010-06 CP-48 CP-100371 3124 1 Digest authentication without Authorization header 9.4.0 10.0.0 C1-102012 2010-06 CP-48 CP-100367 3126 1 Corrections for NASS-Bundled authentication 9.4.0 10.0.0 C1-101844 2010-06 CP-48 CP-100367 3134 Miscellaneous editorial issues 9.4.0 10.0.0 C1-101503 2010-06 CP-48 CP-100371 3137 Usage of "trusted node authentication" 9.4.0 10.0.0 C1-101509 2010-06 CP-48 CP-100367 3146 1 Annex A, Table A.4, item 2C, reference update 9.4.0 10.0.0 C1-101845 2010-09 CP-49 CP-100510 3168 3 Outbound reregistration at P-CSCF 10.0.0 10.1.0 C1-102822 2010-09 CP-49 CP-100500 3171 3 Initial registration for GPRS-IMS at S-CSCF 10.0.0 10.1.0 C1-102848 2010-09 CP-49 CP-100511 3172 5 Privacy protection in IBCF 10.0.0 10.1.0 C1-103526 2010-09 CP-49 CP-100639 3176 3 Alignment with RFC 5552 10.0.0 10.1.0 - 2010-09 CP-49 CP-100511 3178 6 User-related policy data enforcement by the P-CSCF 10.0.0 10.1.0 C1-103517 2010-09 CP-49 CP-100640 3180 3 Handling of aliases URIs 10.0.0 10.1.0 - 2010-09 CP-49 CP-100641 3181 3 Structure of the Request URI sent by a UE 10.0.0 10.1.0 - 2010-09 CP-49 CP-100481 3188 2 Home network check for (E)UTRAN access 10.0.0 10.1.0 C1-103041 2010-09 CP-49 CP-100482 3196 1 Updates to references pertaining to Internet Drafts for tel URI parameters 10.0.0 10.1.0 C1-102676 2010-09 CP-49 CP-100519 3197 1 Usage of alternative P-CSCF address during registration 10.0.0 10.1.0 C1-102631 2010-09 CP-49 CP-100496 3198 8 Mandate registeration with IMS in order to receive audio/voice services 10.0.0 10.1.0 C1-103536 2010-09 CP-49 CP-100510 3200 Annex A, Reason header 10.0.0 10.1.0 C1-102448 2010-09 CP-49 CP-100652 3205 3 Emergency registration in HPLMN 10.0.0 10.1.0 - 2010-09 CP-49 CP-100486 3209 1 Keep-alive corrections 10.0.0 10.1.0 C1-102624 2010-09 CP-49 CP-100511 3211 4 Passing policy with subscription information to UE and P-CSCF 10.0.0 10.1.0 C1-103504 2010-09 CP-49 CP-100486 3214 1 Wildcarded identity AVP correction 10.0.0 10.1.0 C1-102685 2010-09 CP-49 CP-100486 3217 Subclause reference correction 10.0.0 10.1.0 C1-102492 2010-09 CP-49 CP-100483 3221 Update of draft-rosenberg-sip-app-media-tag reference 10.0.0 10.1.0 C1-102532 2010-09 CP-49 CP-100511 3222 3 Location number 10.0.0 10.1.0 C1-103543 2010-09 CP-49 CP-100487 3226 Updates to references pertaining to Internet Drafts for tel URI parameters 10.0.0 10.1.0 C1-102679 2010-09 CP-49 CP-100511 3236 2 Insertion of IMS access gateway by P-CSCF 10.0.0 10.1.0 C1-103518 2010-09 CP-49 CP-100511 3237 4 Enforcement of P-Early-Media indication by P-CSCF 10.0.0 10.1.0 C1-103544 2010-09 CP-49 CP-100508 3239 EN pertaining to Media Plane Securtiy 10.0.0 10.1.0 C1-103039 2010-09 CP-49 CP-100481 3243 2 Detecting valid emergency identifiers 10.0.0 10.1.0 C1-103542 2010-09 CP-49 CP-100501 3245 2 Emergency PDN connection usage control in P-CSCF 10.0.0 10.1.0 C1-103513 2010-09 CP-49 CP-100510 3249 1 IBCF procedures for SIP message 10.0.0 10.1.0 C1-103382 2010-09 CP-49 CP-100519 3250 2 Indicating wildcarded IMPU in reg-event 10.0.0 10.1.0 C1-103528 2010-09 CP-49 CP-100501 3252 1 Wildcarded Identities handling 10.0.0 10.1.0 C1-103354 2010-09 CP-49 CP-100481 3256 2 Correction of Stage 3 misalignment with Stage 1 and Stage 2 on use of SIP 380 response. 10.0.0 10.1.0 C1-103389 2010-09 CP-49 CP-100519 3257 3 SigComp disabling 10.0.0 10.1.0 C1-103530 2010-09 CP-49 CP-100486 3258 2 Ensuring PSAP receives correctly formatted request 10.0.0 10.1.0 C1-103568 2010-09 CP-49 CP-100486 3261 1 Mandate registeration with IMS in order to receive audio/voice services 10.0.0 10.1.0 C1-103508 2010-12 CP-50 CP-100843 3305 2 SRVCC enhancements - ATCF invocation 10.1.0 10.2.0 C1-104362 2010-12 CP-50 CP-100728 3267 1 Protected AKA registration at S-CSCF 10.1.0 10.2.0 C1-104197 2010-12 CP-50 CP-100728 3270 1 Protected Digest registration at S-CSCF 10.1.0 10.2.0 C1-104300 2010-12 CP-50 CP-100728 3273 2 Unprotected registration at S-CSCF 10.1.0 10.2.0 C1-104370 2010-12 CP-50 CP-100750 3278 Supported header field corrected 10.1.0 10.2.0 C1-103619 2010-12 CP-50 CP-100728 3281 1 Update reference 10.1.0 10.2.0 C1-104310 2010-12 CP-50 CP-100725 3285 Correcting mixed references in IBCF 10.1.0 10.2.0 C1-103761 2010-12 CP-50 CP-100728 3288 3 Conference and IBCF IMS_ALG and removal of an Editor's note. 10.1.0 10.2.0 C1-105071 2010-12 CP-50 CP-100735 3291 Correcting errors in S-CSCF restoration procedures 10.1.0 10.2.0 C1-103773 2010-12 CP-50 CP-100728 3301 Incorrect sequence of steps in P-CSCF 10.1.0 10.2.0 C1-104316 2010-12 CP-50 CP-100723 3304 Emergency registration and normal registration 10.1.0 10.2.0 C1-104183 2010-12 CP-50 CP-100738 3314 1 Updating IMEI URN draft reference 10.1.0 10.2.0 C1-104328 2010-12 CP-50 CP-100721 3319 IETF reference updates 10.1.0 10.2.0 C1-103921 2010-12 CP-50 CP-100722 3324 IETF reference updates 10.1.0 10.2.0 C1-103926 2010-12 CP-50 CP-100726 3328 IETF reference updates 10.1.0 10.2.0 C1-103936 2010-12 CP-50 CP-100728 3331 IETF reference updates 10.1.0 10.2.0 C1-104337 2010-12 CP-50 CP-100728 3334 EN removal: Retry-After Header field value in 503 response 10.1.0 10.2.0 C1-103955 2010-12 CP-50 CP-100728 3340 EN removal: Network inserted codecs 10.1.0 10.2.0 C1-103961 2010-12 CP-50 CP-100723 3344 1 Further modifications required to SIP 380 response to remove new requirements. 10.1.0 10.2.0 C1-104187 2010-12 CP-50 CP-100864 3345 4 Inclusion of IMEI in the sip.instance of the initial SIP-Register request 10.1.0 10.2.0 C1-105086 2010-12 CP-50 CP-100733 3348 Handling of editor's note relating to private network traffic breakout and breakin 10.1.0 10.2.0 C1-103984 2010-12 CP-50 CP-100726 3354 2 Inclusion of file transfer attributes 10.1.0 10.2.0 C1-104986 2010-12 CP-50 CP-100752 3355 2 IBCF and 3xx responses 10.1.0 10.2.0 C1-104595 2010-12 CP-50 CP-100752 3356 Non E.164 Tel URI conversion failure 10.1.0 10.2.0 C1-104464 2010-12 CP-50 CP-100750 3357 2 max-time and base-time parameters provision 10.1.0 10.2.0 C1-105207 2010-12 CP-50 CP-100752 3358 reference correction 10.1.0 10.2.0 C1-104466 2010-12 CP-50 CP-100728 3361 1 AKA registration at S-CSCF 10.1.0 10.2.0 C1-104991 2010-12 CP-50 CP-100728 3364 2 Autentication already performed 10.1.0 10.2.0 C1-105203 2010-12 CP-50 CP-100728 3367 1 Digest registration at S-CSCF 10.1.0 10.2.0 C1-104997 2010-12 CP-50 CP-100728 3370 1 Bundle registration 10.1.0 10.2.0 C1-105000 2010-12 CP-50 CP-100720 3377 1 Codec and DTMF correction 10.1.0 10.2.0 C1-104980 2010-12 CP-50 CP-100728 3380 Definition: multiple registrations 10.1.0 10.2.0 C1-104535 2010-12 CP-50 CP-100871 3383 1 Reference update: draft-ietf-sipcore-199 10.1.0 10.2.0 - 2010-12 CP-50 CP-100724 3387 Reference update: draft-ietf-sipcore-keep 10.1.0 10.2.0 C1-104547 2010-12 CP-50 CP-100864 3388 2 Modifications to priority handling in support of MPS 10.1.0 10.2.0 C1-105095 2010-12 CP-50 CP-100885 3389 3 Updating the restoration procedure definition 10.1.0 10.2.0 - 2010-12 CP-50 CP-100752 3390 Adding RFC 5318 to major capabilities tables 10.1.0 10.2.0 C1-105226 2010-12 CP-50 CP-100728 3393 1 Handling of the isfocus media feature tag in P-CSCF 10.1.0 10.2.0 C1-105003 2010-12 CP-50 CP-100752 3394 Annex A, Table A.4, item 29+72 and Table A.4A, prerequisite 10.1.0 10.2.0 C1-104618 2010-12 CP-50 CP-100728 3397 "ob" parameter in case of no registration 10.1.0 10.2.0 C1-105006 2010-12 CP-50 CP-100728 3401 2 Addition of Target-Dialog header and capability in Annex A 10.1.0 10.2.0 C1-105074 2010-12 CP-50 CP-100766 3405 2 Alternative emergency session handling in non-roaming cases (P-CSCF) 10.1.0 10.2.0 C1-105052 2010-12 CP-50 CP-100766 3406 2 Alternative emergency session handling in non-roaming cases (S-CSCF) 10.1.0 10.2.0 C1-105053 2010-12 CP-50 CP-100766 3407 Alternative emergency session handling in non-roaming cases (E-CSCF) 10.1.0 10.2.0 C1-104682 2010-12 CP-50 CP-100749 3409 Removal of erroneous passing on of IOI value to PSAP 10.1.0 10.2.0 C1-104718 2010-12 CP-50 CP-100766 3411 Additions to E-CSCF functionality for IESE 10.1.0 10.2.0 C1-104721 2010-12 CP-50 CP-100766 3412 IBCF detection and routeing of emergency call 10.1.0 10.2.0 C1-104722 2010-12 CP-50 CP-100864 3413 3 Introduction to priority schemes in the IM CN subsystem 10.1.0 10.2.0 C1-105221 2010-12 CP-50 CP-100766 3414 1 Addition to introductory clauses in support of IESE 10.1.0 10.2.0 C1-104974 2010-12 CP-50 CP-100725 3415 1 Correction of the usage for type 3 IOI 10.1.0 10.2.0 C1-105051 2010-12 CP-50 CP-100864 3425 2 P-CSCF behaviour for insufficient bandwidth 10.1.0 10.2.0 C1-105058 2010-12 CP-50 CP-100752 3416 1 Text corrections 10.1.0 10.2.0 C1-104969 2010-12 CP-50 CP-100727 3420 Update of IETF reference 10.1.0 10.2.0 C1-104842 2011-03 CP-51 CP-110181 3371 4 Sending of location information from LRF to E-CSCF 10.2.0 10.3.0 C1-110671 2011-03 CP-51 CP-110181 3429 2 Response code in Reason header field 10.2.0 10.3.0 C1-110659 2011-03 CP-51 CP-110164 3432 1 UE initiated deregistration 10.2.0 10.3.0 C1-110581 2011-03 CP-51 CP-110181 3433 Other databases 10.2.0 10.3.0 C1-110010 2011-03 CP-51 CP-110181 3434 1 Clarification of possible triggers for network-initiated reauthentication 10.2.0 10.3.0 C1-110560 2011-03 CP-51 CP-110161 3435 6 Update to IMS registration procedures due to USAT initiated Refresh for ISIM/USIM EFs 10.2.0 10.3.0 C1-111511 2011-03 CP-51 CP-110184 3436 1 Optimal Media Routeing – SDP attribute syntax definition 10.2.0 10.3.0 C1-110558 2011-03 CP-51 CP-110184 3437 1 Update SDP profile table for Optimal Media Routeing 10.2.0 10.3.0 C1-110559 2011-03 CP-51 CP-110196 3439 1 Modifications to S-CSCF procedures in support of MPS 10.2.0 10.3.0 C1-110562 2011-03 CP-51 CP-110196 3440 1 Modifications to P-CSCF and IBCF procedures in support of MPS 10.2.0 10.3.0 C1-110563 2011-03 CP-51 CP-110201 3441 1 Select E-CSCF upon S-SCSF failure 10.2.0 10.3.0 C1-110557 2011-03 CP-51 CP-110158 3445 1 Correct P-CSCF handling of requests for emergency services with Route header fields 10.2.0 10.3.0 C1-110567 2011-03 CP-51 CP-110196 3450 Clarification on P-CSCF behaviour in case of insufficient bandwidth 10.2.0 10.3.0 C1-110180 2011-03 CP-51 CP-110166 3453 2 New Reference for Alert-URN 10.2.0 10.3.0 C1-111349 2011-03 CP-51 CP-110187 3457 5 Explicit Congestion Notification (ECN) for RTP over UDP 10.2.0 10.3.0 C1-111360 2011-03 CP-51 CP-110196 3458 4 Clarify the P-CSCF restoration procedure 10.2.0 10.3.0 C1-111271 2011-03 CP-51 CP-110164 3461 1 Reference update: draft-ietf-mmusic-ice-tcp 10.2.0 10.3.0 C1-110578 2011-03 CP-51 CP-110164 3464 1 Reference update: RFC 6086 10.2.0 10.3.0 C1-110589 2011-03 CP-51 CP-110159 3468 Reference update: draft-ietf-sipcore-keep 10.2.0 10.3.0 C1-110267 2011-03 CP-51 CP-110164 3471 3 P-CSCF Path SIP URI and IMS flow token correction 10.2.0 10.3.0 C1-111283 2011-03 CP-51 CP-110196 3474 1 Encoding of PANI for E-UTRAN 10.2.0 10.3.0 C1-110442 2011-03 CP-51 CP-110196 3475 3 Insertion of "orig" parameter by IBCF 10.2.0 10.3.0 C1-110665 2011-03 CP-51 CP-110196 3479 5 Removal of reference CPC and OLI Internet Draft 10.2.0 10.3.0 C1-111329 2011-03 CP-51 CP-110158 3483 2 Specifying "sos" URI parameter in 24.229 10.2.0 10.3.0 C1-111087 2011-03 CP-51 CP-110196 3484 7 Example of IMS Registration conditions, taking into account the network operator's preference for selection of the voice domain 10.2.0 10.3.0 C1-111270 2011-03 CP-51 CP-110181 3486 2 Removal of Sigcomp disabling 10.2.0 10.3.0 C1-111266 2011-03 CP-51 CP-110164 3489 New registration 10.2.0 10.3.0 C1-110842 2011-03 CP-51 CP-110309 3490 6 Inclusion of MEID in the sip.instance of the SIP-Register request 10.2.0 10.3.0 - 2011-03 CP-51 CP-110181 3491 1 Disabling SigComp by default in E-UTRAN 10.2.0 10.3.0 C1-111221 2011-03 CP-51 CP-110164 3495 1 S-CSCF Service-Route SIP URI 10.2.0 10.3.0 C1-111274 2011-03 CP-51 CP-110184 3496 4 Introduction of OMR procedures in AS, MGCF and P-CSCF 10.2.0 10.3.0 C1-111359 2011-03 CP-51 CP-110181 3497 Removal of editor's note: different sets of policies for a user 10.2.0 10.3.0 C1-111235 2011-03 CP-51 CP-110181 3498 Removal of editor's note: additional policy elements 10.2.0 10.3.0 C1-110939 2011-03 CP-51 CP-110164 3501 Reference update and procedure correction: 199 10.2.0 10.3.0 C1-111277 2011-03 CP-51 CP-110162 3502 1 Contact header clarification 10.2.0 10.3.0 C1-111240 2011-03 CP-51 CP-110160 3507 1 MGCF procedure corrections related to SIP preconditions 10.2.0 10.3.0 C1-111259 2011-03 CP-51 CP-110164 3510 Erroneous row reference in Table A.50A 10.2.0 10.3.0 C1-111000 2011-03 CP-51 CP-110164 3514 1 Correction reference 10.2.0 10.3.0 C1-111280 2011-03 CP-51 CP-110176 3517 2 Correction to the header field indicating where the request comes from in E-CSCF procedures 10.2.0 10.3.0 C1-111325 2011-03 CP-51 CP-110181 3519 1 Editiorial corrections to S-CSCF registration subclauses 10.2.0 10.3.0 C1-111241 2011-03 CP-51 CP-110181 3520 3 Clarification of authentication of 380 and 504 responses with multiple registration 10.2.0 10.3.0 C1-111337 2011-03 CP-51 CP-110181 3521 1 Provision of phone-context parameter value via MO 10.2.0 10.3.0 C1-111245 2011-03 CP-51 CP-110010 3522 3 P-CSCF graceful shutdown 10.2.0 10.3.0 - 2011-06 CP-52 CP-110450 3532 1 Reference update: 199 10.3.0 10.4.0 C1-112024 2011-06 CP-52 CP-110445 3536 1 Reference update: RFC 6223 10.3.0 10.4.0 C1-112013 2011-06 CP-52 CP-110450 3539 Annex A: RFC 6086 reference corrections 10.3.0 10.4.0 C1-111556 2011-06 CP-52 CP-110468 3540 1 Removal of Annex F.3 10.3.0 10.4.0 C1-112015 2011-06 CP-52 CP-110468 3541 1 Moving of P-CSCF ICE procedures (Annex K.3.2 and K.5.3) 10.3.0 10.4.0 C1-112016 2011-06 CP-52 CP-110468 3542 1 Removal of Annex G 10.3.0 10.4.0 C1-112014 2011-06 CP-52 CP-110468 3545 1 S-CSCF-initiated session release 10.3.0 10.4.0 C1-112025 2011-06 CP-52 CP-110450 3548 1 Service-Route at the UE 10.3.0 10.4.0 C1-112040 2011-06 CP-52 CP-110450 3551 1 Service-Route at the P-CSCF 10.3.0 10.4.0 C1-112043 2011-06 CP-52 CP-110450 3554 2 Service-Route at the S-CSCF 10.3.0 10.4.0 C1-112227 2011-06 CP-52 CP-110450 3557 1 Path header field at the S-CSCF 10.3.0 10.4.0 C1-112049 2011-06 CP-52 CP-110450 3560 1 S-CSCF releasing the dialogs 10.3.0 10.4.0 C1-112052 2011-06 CP-52 CP-110450 3563 1 NOTIFY request 10.3.0 10.4.0 C1-112028 2011-06 CP-52 CP-110450 3566 1 Network Initiated deregistration at S-CSCF 10.3.0 10.4.0 C1-112031 2011-06 CP-52 CP-110450 3569 2 Network Initiated deregistration at P-CSCF 10.3.0 10.4.0 C1-112223 2011-06 CP-52 CP-110450 3572 1 Network Initiated deregistration at UE 10.3.0 10.4.0 C1-112037 2011-06 CP-52 CP-110468 3573 UE initiated deregistration 10.3.0 10.4.0 C1-111590 2011-06 CP-52 CP-110448 3578 1 P-Access-Network-Info : ABNF correction 10.3.0 10.4.0 C1-112004 2011-06 CP-52 CP-110468 3579 1 Moving of IBCF ICE procedures (Annex K.5.4) 10.3.0 10.4.0 C1-112017 2011-06 CP-52 CP-110531 3583 1 SRVCC enhancements in Annex A 10.3.0 10.4.0 - 2011-06 CP-52 CP-110469 3584 ENs on P-CSCF invoking ATCF 10.3.0 10.4.0 C1-111614 2011-06 CP-52 CP-110465 3585 1 Inclusion of MEID in the sip.instance of the SIP-Register request 10.3.0 10.4.0 C1-112201 2011-06 CP-52 CP-110465 3586 1 Clarification of scope of section 5.1.6 on Emergency Call 10.3.0 10.4.0 C1-112089 2011-06 CP-52 CP-110447 3591 1 Fraud prevention for deregistration for ICS 10.3.0 10.4.0 C1-112061 2011-06 CP-52 CP-110474 3596 2 UICC Access to IMS 10.3.0 10.4.0 C1-112249 2011-06 CP-52 CP-110447 3599 1 Updating IMEI URN draft reference 10.3.0 10.4.0 C1-112058 2011-06 CP-52 CP-110468 3602 2 Insertion of "gated" parameter by the P-CSCF 10.3.0 10.4.0 C1-112231 2011-06 CP-52 CP-110451 3605 1 Removal of dial around indicator 10.3.0 10.4.0 C1-112235 2011-06 CP-52 CP-110477 3606 1 OMR designation as media level attributes in profile 10.3.0 10.4.0 C1-112096 2011-06 CP-52 CP-110472 3612 2 Application server detection and routeing of emergency call 10.3.0 10.4.0 C1-112232 2011-06 CP-52 CP-110468 3613 1 Removal of duplicate material in P-CSCF emergency call handling 10.3.0 10.4.0 C1-112094 2011-06 CP-52 CP-110468 3622 Miscellaneous 24.229 corrections 10.3.0 10.4.0 C1-111949 2011-06 CP-52 CP-110521 3611 3 Removal of repetition of IOI header field parameters 10.3.0 10.4.0 - 2011-06 CP-52 CP-110535 3518 4 Reference Location for Emergency Service 10.4.0 11.0.0 - 2011-09 CP-53 CP-110686 3624 1 Reference update 11.0.0 11.1.0 C1-112731 2011-09 CP-53 CP-110654 3633 3 Correcting errors in S-CSCF restoration procedure 11.0.0 11.1.0 C1-113584 2011-09 CP-53 CP-110656 3641 2 P-Profile-Key header field corrections in I-CSCF 11.0.0 11.1.0 C1-112915 2011-09 CP-53 CP-110693 3648 3 Emergency session when IMS voice over PS is not supported 11.0.0 11.1.0 C1-113170 2011-09 CP-53 CP-110666 3651 EATF in Annex A 11.0.0 11.1.0 C1-112512 2011-09 CP-53 CP-110695 3657 2 Correction on call initiation procedure at the MGCF 11.0.0 11.1.0 C1-112945 2011-09 CP-53 CP-110686 3658 Editorial corrections on SIP header field name 11.0.0 11.1.0 C1-112519 2011-09 CP-53 CP-110689 3659 1 Address the Editor's Note in RLI 11.0.0 11.1.0 C1-112725 2011-09 CP-53 CP-110704 3665 3 Additional IOI correction for SIP responses 11.0.0 11.1.0 - 2011-09 CP-53 CP-110653 3669 1 Replacement of draft-garcia-mmusic-sdp-misc-cap with draft-garcia-mmusic-sdp-miscellaneous-caps 11.0.0 11.1.0 C1-113294 2011-09 CP-53 CP-110686 3670 4 Filtering of P-Associated-URI at P-CSCF 11.0.0 11.1.0 C1-113440 2011-09 CP-53 CP-110674 3676 2 Modification on roles of ATCF 11.0.0 11.1.0 C1-112928 2011-09 CP-53 CP-110651 3683 1 Emergency call – correction of requests covered at the P-CSCF 11.0.0 11.1.0 C1-112832 2011-09 CP-53 CP-110658 3687 IETF reference update 11.0.0 11.1.0 C1-112647 2011-09 CP-53 CP-110681 3689 1 Removal of "select an E-CSCF" 11.0.0 11.1.0 C1-112754 2011-09 CP-53 CP-110686 3691 2 Release of Media Bearers 11.0.0 11.1.0 C1-112937 2011-09 CP-53 CP-110686 3693 2 Network identified by IOI header field parameter 11.0.0 11.1.0 C1-112960 2011-09 CP-53 CP-110648 3700 "P-Visited-Network-ID" correction 11.0.0 11.1.0 C1-113004 2011-09 CP-53 C1-110715 3701 2 Emergency session handling correction 11.0.0 11.1.0 - 2011-09 CP-53 CP-110681 3703 Deletion of Editor's Note Concerning P-CSCF Dialstring Recognition 11.0.0 11.1.0 C1-113087 2011-09 CP-53 CP-110693 3707 1 Emergency Session Setup – Incorrect Reference 11.0.0 11.1.0 C1-113445 2011-09 CP-53 CP-110677 3713 2 Policy passing when different policies are related to different IMPIs sharing an IMPU 11.0.0 11.1.0 C1-113698 2011-09 CP-53 CP-110681 3715 ENs on XML namespace registration 11.0.0 11.1.0 C1-113176 2011-09 CP-53 CP-110656 3719 1 Adding Call-Info to SUBSCRIBE in annex A 11.0.0 11.1.0 C1-113529 2011-09 CP-53 CP-110653 3730 Updating IMEI URN draft reference 11.0.0 11.1.0 C1-113287 2011-09 CP-53 CP-110653 3732 2 Including draft-holmberg-sipcore-proxy-feature 11.0.0 11.1.0 C1-113594 2011-09 CP-53 CP-110687 3740 Transit IOI principles 11.0.0 11.1.0 C1-113595 2011-09 CP-53 CP-110681 3744 Deletion of Editor's Note in 24.229 on authentication mechanism (Rel-10) 11.0.0 11.1.0 C1-113374 2011-09 CP-53 CP-110681 3746 1 Deletion of Editor's Note in 24.229 on aor attribute (Rel-10) 11.0.0 11.1.0 C1-113476 2011-09 CP-53 CP-110661 3758 Deletion of Editor's Note in 24.229 on NASS error message (Rel-8) 11.0.0 11.1.0 C1-113388 2011-09 CP-53 CP-110686 3759 Inter-operator identifier corrections 11.0.0 11.1.0 C1-113392 2011-09 CP-53 CP-110736 3762 2 Correction on EMC handling of S-CSCF 11.0.0 11.1.0 - 2011-09 CP-53 CP-110690 3763 3GPP2 reference corrections 11.0.0 11.1.0 C1-113396 2011-12 CP-54 CP-110887 3673 9 "Default handling" triggering correction 11.1.0 11.2.0 C1-115232 2011-12 CP-54 CP-110887 3766 3 AS determination of the served user identity 11.1.0 11.2.0 C1-114942 2011-12 CP-54 CP-110887 3771 Editorial correction of the P-CSCF behavior for TCP connection 11.1.0 11.2.0 C1-113821 2011-12 CP-54 CP-110873 3773 1 Update draft-atarius-dispatch-meid-urn 11.1.0 11.2.0 C1-114376 2011-12 CP-54 CP-110887 3786 1 Correction on conditional expression of Major Capabilities 11.1.0 11.2.0 C1-114384 2011-12 CP-54 CP-110852 3790 4 P-CSCF behaviour for emergency calls when failure occurs 11.1.0 11.2.0 C1-115362 2011-12 CP-54 CP-110887 3794 3 Adding missing handling in NOTIFY body for a registration event 11.1.0 11.2.0 C1-114462 2011-12 CP-54 CP-110887 3803 1 P-Profile-Key header field corrections in AS 11.1.0 11.2.0 C1-114214 2011-12 CP-54 CP-110887 3807 1 P-Profile-Key header field corrections in S-CSCF 11.1.0 11.2.0 C1-114215 2011-12 CP-54 CP-110887 3809 S-CSCF flow selection correction 11.1.0 11.2.0 C1-114106 2011-12 CP-54 CP-110887 3810 S-CSCF determing supported IP version by UE for media 11.1.0 11.2.0 C1-114107 2011-12 CP-54 CP-110881 3812 3 ICSI to visited network 11.1.0 11.2.0 C1-115170 2011-12 CP-54 CP-110868 3819 1 Removal of editor's notes relating to insertion of P-Access-Network-Info header field by a proxy 11.1.0 11.2.0 C1-114206 2011-12 CP-54 CP-110887 3820 Editorial corrections on SIP header field name 11.1.0 11.2.0 C1-114534 2011-12 CP-54 CP-110887 3821 1 Addition of IEEE802.3ah to P-Access-Network-Info header 11.1.0 11.2.0 C1-115154 2011-12 CP-54 CP-110887 3822 Editorial correction on de-registration of emergency service 11.1.0 11.2.0 C1-114536 2011-12 CP-54 CP-110856 3827 1 Incorrect reference to RFC 5261 11.1.0 11.2.0 C1-115009 2011-12 CP-54 CP-110873 3834 2 proxy-feature I-D reference update 11.1.0 11.2.0 C1-115288 2011-12 CP-54 CP-110861 3840 Inclusion of media feature tag ASN.1 identifiers 11.1.0 11.2.0 C1-114594 2011-12 CP-54 CP-110887 3845 Record-Route reference correction 11.1.0 11.2.0 C1-114600 2011-12 CP-54 CP-110887 3846 1 Number of emergency registrations 11.1.0 11.2.0 C1-115167 2011-12 CP-54 CP-110850 3850 2 Reference update: Reason header in SIP responses 11.1.0 11.2.0 C1-115274 2011-12 CP-54 CP-110887 3855 4 Additional granularity for IMS Communication Service Identifier 11.1.0 11.2.0 C1-115348 2011-12 CP-54 CP-110869 3857 Correction UE handling compression 11.1.0 11.2.0 C1-114687 2011-12 CP-54 CP-110880 3859 1 Routing of emergency requests via S-CSCF 11.1.0 11.2.0 C1-115178 2011-12 CP-54 CP-110887 3860 1 S-CSCF terminating procedures 11.1.0 11.2.0 C1-115155 2011-12 CP-54 CP-110873 3862 2 Transcoding Control at the IMS-ALG in the P-CSCF and related ECN corrections. 11.1.0 11.2.0 C1-115340 2011-12 CP-54 CP-110887 3863 1 T1 Timer value for MRFC 11.1.0 11.2.0 C1-115158 2011-12 CP-54 CP-110881 3868 1 Adding availability for SMS over IMS determination 11.1.0 11.2.0 C1-114971 2011-12 CP-54 CP-110881 3869 1 ICSI included by AS in Feature-Caps header field in terminating requests 11.1.0 11.2.0 C1-115171 2011-12 CP-54 CP-110881 3870 Indicating Multimedia Telephony Application Server in Feature-Caps header field 11.1.0 11.2.0 C1-114779 2011-12 CP-54 CP-110865 3874 1 3GPP2 reference corrections 11.1.0 11.2.0 C1-115192 2011-12 CP-54 CP-110887 3879 2 Correction on MRFC handling when receiving an INVITE message 11.1.0 11.2.0 C1-115235 2011-12 CP-54 CP-110885 3891 2 Additional routeing function behaviour for transit ioi 11.1.0 11.2.0 C1-115231 2011-12 CP-54 CP-110887 3892 2 Clarification on I-CSCF routeing procedure for incoming call with Request-URI in SIP URI format 11.1.0 11.2.0 C1-115252 2012-01 Correction of formatting in tables of annex A 11.2.0 11.2.1 2012-03 CP-55 CP-120118 3835 4 IPXS: Application invocation procedures 11.2.1 11.3.0 C1-120849 2012-03 CP-55 CP-120165 3844 3 Updating of UUS references 11.2.1 11.3.0 - 2012-03 CP-55 CP-120096 3900 Corrections on the conditions of MSRP SDP a=path attribute 11.2.1 11.3.0 C1-120114 2012-03 CP-55 CP-120117 3901 Addition of procedures in case of Fiber access network 11.2.1 11.3.0 C1-120148 2012-03 CP-55 CP-120117 3902 Removal of Editor's Note about access-info of P-Access-Network-Info header 11.2.1 11.3.0 C1-120149 2012-03 CP-55 CP-120124 3903 1 ICSI to visited network - ENs 11.2.1 11.3.0 C1-120778 2012-03 CP-55 CP-120117 3905 2 S-CSCF behavior when the number of simultaneous registrations for the same UE is reached. 11.2.1 11.3.0 C1-120880 2012-03 CP-55 CP-120117 3906 3 P-CSCF address provided by OMA DM for fixed access (Annex E). 11.2.1 11.3.0 C1-120906 2012-03 CP-55 CP-120124 3909 3 Use of Contact Parameters in a 3XX Response from an LRF 11.2.1 11.3.0 C1-120898 2012-03 CP-55 CP-120093 3916 1 Geo-Redundancy Registration 11.2.1 11.3.0 C1-120556 2012-03 CP-55 CP-120107 3918 2 P-CSCF forwarding REGISTER when ATCF is used 11.2.1 11.3.0 C1-120869 2012-03 CP-55 CP-120112 3920 IMS-ALG in the P-CSCF is invoked for Transcoding Control 11.2.1 11.3.0 C1-120212 2012-03 CP-55 CP-120117 3921 2 P-Served-User to BGCF 11.2.1 11.3.0 C1-120854 2012-03 CP-55 CP-120090 3928 1 Location Conveyance: Reference update 11.2.1 11.3.0 C1-120562 2012-03 CP-55 CP-120117 3933 1 Location Conveyance: Location Forwarding to MGCF and PSAP 11.2.1 11.3.0 C1-120563 2012-03 CP-55 CP-120112 3940 1 Reference update: draft-holmberg-sipcore-proxy-feature 11.2.1 11.3.0 C1-120619 2012-03 CP-55 CP-120112 3942 1 UE usage of Feature-Caps 11.2.1 11.3.0 C1-120617 2012-03 CP-55 CP-120124 3945 1 GRUU: UE self-assigned GRUU 11.2.1 11.3.0 C1-120766 2012-03 CP-55 CP-120116 3947 2 IMS_IOI_CH input on IBCF behaviour 11.2.1 11.3.0 C1-120848 2012-03 CP-55 CP-120115 3948 1 GINI input on profile tables 11.2.1 11.3.0 C1-120696 2012-03 CP-55 CP-120092 3957 1 Updating references to IMEI URN and XML body handling drafts 11.2.1 11.3.0 C1-120583 2012-03 CP-55 CP-120112 3960 1 Removing contradictory statement from User initiated deregstration procedure 11.2.1 11.3.0 C1-120621 2012-03 CP-55 CP-120117 3961 Editorial corrections 11.2.1 11.3.0 C1-120321 2012-03 CP-55 CP-120124 3962 1 Clarification on forking related issues 11.2.1 11.3.0 C1-120768 2012-03 CP-55 CP-120115 3967 2 Add general support for RFC 6140 11.2.1 11.3.0 C1-120850 2012-03 CP-55 CP-120115 3968 2 Add complex UE support for RFC 6140 mainline GIN registration functionality 11.2.1 11.3.0 C1-120851 2012-03 CP-55 CP-120115 3969 2 Add S-CSCF support for RFC 6140 mainline GIN registration functionality 11.2.1 11.3.0 C1-120852 2012-03 CP-55 CP-120119 3970 3 Introduction of MRB functional entity 11.2.1 11.3.0 C1-120896 2012-06 CP-56 CP-120299 3896 2 Reference update for MIKEY_TICKET RFC 11.3.0 11.4.0 C1-121104 2012-06 CP-56 CP-120314 3904 6 P-Served-User and session case 11.3.0 11.4.0 C1-122360 2012-06 CP-56 CP-120307 3946 2 P-CSCF releasing the session when resource is lost 11.3.0 11.4.0 C1-121545 2012-06 CP-56 CP-120307 3952 8 Correcting procedure for propagating service profile update to the UE 11.3.0 11.4.0 C1-122450 2012-06 CP-56 CP-120324 3971 6 Addition of the transit and roaming function 11.3.0 11.4.0 C1-122413 2012-06 CP-56 CP-120323 3975 4 PANI header support of network provided location information 11.3.0 11.4.0 C1-122508 2012-06 CP-56 CP-120323 3976 4 Distribution of location information- AS procedures 11.3.0 11.4.0 C1-122509 2012-06 CP-56 CP-120289 3983 Correction on SDP Profile Status 11.3.0 11.4.0 C1-121042 2012-06 CP-56 CP-120314 3984 1 Editorial correction on SDP Profile Status 11.3.0 11.4.0 C1-121540 2012-06 CP-56 CP-120286 3989 GRUU: S-CSCF URI matching 11.3.0 11.4.0 C1-121054 2012-06 CP-56 CP-120284 3993 1 Reference update: draft-salud-alert-info-urns 11.3.0 11.4.0 C1-121416 2012-06 CP-56 CP-120307 3997 2 Restoration procedures missing in entry IBCF 11.3.0 11.4.0 C1-122250 2012-06 CP-56 CP-120306 3998 2 Missing emergency call procedure in S-CSCF 11.3.0 11.4.0 C1-121658 2012-06 CP-56 CP-120324 4000 6 Loopback routeing 11.3.0 11.4.0 C1-122412 2012-06 CP-56 CP-120322 4005 1 Removal of EN regarding PUI format 11.3.0 11.4.0 C1-121529 2012-06 CP-56 CP-120303 4011 Correcting implementation error, dai parameter 11.3.0 11.4.0 C1-121178 2012-06 CP-56 CP-120307 4012 E-CSCF handling of PAI in responses 11.3.0 11.4.0 C1-121179 2012-06 CP-56 CP-120307 4013 Editorial corrections to 24.229 11.3.0 11.4.0 C1-121190 2012-06 CP-56 CP-120314 4018 1 Correcting incorrect references in P-CSCF procedures when emergency call failure occurs 11.3.0 11.4.0 C1-121406 2012-06 CP-56 CP-120314 4019 7 Correcting IBCF and profile tables for use of 3GPP IM CN subsystem XML body in restoration procedures 11.3.0 11.4.0 C1-122415 2012-06 CP-56 CP-120322 4020 7 Addition of GRUU procedures for RFC6140 procedures 11.3.0 11.4.0 C1-122480 2012-06 CP-56 CP-120286 4025 1 Correcting contradictory statements regarding GRUU handling by IBCF 11.3.0 11.4.0 C1-121411 2012-06 CP-56 CP-120314 4026 2 Transparent passing of contact feature tags by B2BUA AS 11.3.0 11.4.0 C1-121719 2012-06 CP-56 CP-120307 4027 1 Use of Contact Parameters in a 3XX Response from an LRF 11.3.0 11.4.0 C1-121546 2012-06 CP-56 CP-120301 4030 1 Reference update: draft-ietf-avtcore-ecn-for-rtp 11.3.0 11.4.0 C1-122285 2012-06 CP-56 CP-120427 4031 2 Update to reference titles in TS 24.229 11.3.0 11.4.0 - 2012-06 CP-56 CP-120314 4032 1 Transparency to GRUU of B2BUA AS 11.3.0 11.4.0 C1-122369 2012-06 CP-56 CP-120314 4033 2 Addressing potential abuse of 3xx responses 11.3.0 11.4.0 C1-122414 2012-06 CP-56 CP-120303 4038 2 Correcting ambiguity in restoration procedures definitions 11.3.0 11.4.0 C1-122445 2012-06 CP-56 CP-120307 4041 1 Adding the related-icid in charging overview 11.3.0 11.4.0 C1-122365 2012-06 CP-56 CP-120295 4045 Updating of UUS references 11.3.0 11.4.0 C1-121944 2012-06 CP-56 CP-120292 4049 IETF reference update (mixer-control) 11.3.0 11.4.0 C1-121948 2012-06 CP-56 CP-120290 4058 1 Correction on profile of REFER request 11.3.0 11.4.0 C1-122268 2012-06 CP-56 CP-120314 4059 Contact header field parameter values 11.3.0 11.4.0 C1-121970 2012-06 CP-56 CP-120314 4064 1 Adding 3gpp body xml schema to archive 11.3.0 11.4.0 C1-122372 2012-06 CP-56 CP-120314 4069 3 New technology annex when using the EPC via WLAN to access IM CN subsystem 11.3.0 11.4.0 C1-122513 2012-06 CP-56 CP-120290 4074 Handling of EN relating to granularity of access class 11.3.0 11.4.0 C1-122089 2012-06 CP-56 CP-120314 4075 2 Provision of access-type values in the P-CSCF, and Support of network location reporting for IMS functionality over GxGxx interfaces 11.3.0 11.4.0 C1-122491 2012-06 CP-56 CP-120314 4076 2 Correction to the technology annex when using I- WLAN to access IM CN subsystem 11.3.0 11.4.0 C1-122486 2012-06 CP-56 CP-120314 4077 P-CSCF handling UE port along with IP address during registration 11.3.0 11.4.0 C1-122116 2012-06 CP-56 CP-120307 4079 2 Use of Contact Parameters in a 3XX Response from an LRF 11.3.0 11.4.0 C1-122499 2012-09 CP-57 CP-120583 4039 5 SMS domain selection 11.4.0 11.5.0 C1-123296 2012-09 CP-57 CP-120566 4068 5 Emergency sub-service type handling 11.4.0 11.5.0 C1-123416 2012-09 CP-57 CP-120597 4078 1 Support of MRB Query mode in 3GPP TS 24.229 11.4.0 11.5.0 C1-122938 2012-09 CP-57 CP-120603 4082 2 Application servers and RAVEL 11.4.0 11.5.0 C1-123288 2012-09 CP-57 CP-120586 4083 1 Annex A updates for USSI 11.4.0 11.5.0 C1-123264 2012-09 CP-57 CP-120588 4084 1 Correction of correction to profile tables for use of 3GPP IM CN subsystem XML body in restoration procedures 11.4.0 11.5.0 C1-123172 2012-09 CP-57 CP-120588 4085 1 Correcting profile tables for use of 3GPP IM CN subsystem XML body in response to request for emergency services 11.4.0 11.5.0 C1-123168 2012-09 CP-57 CP-120582 4088 2 Reference update and technical changes: draft-ietf-sipcore-proxy-feature 11.4.0 11.5.0 C1-123348 2012-09 CP-57 CP-120601 4089 1 Annex A: P-Access-Network-Info in ACK 11.4.0 11.5.0 C1-123256 2012-09 CP-57 CP-120569 4094 1 Correction of SDP Profile about RFC 4145 11.4.0 11.5.0 C1-123104 2012-09 CP-57 CP-120582 4097 1 Feature-Caps header field part of trust domain 11.4.0 11.5.0 C1-123158 2012-09 CP-57 CP-120599 4098 Removing an EN regarding missing charging related headers 11.4.0 11.5.0 C1-122680 2012-09 CP-57 CP-120603 4099 Removing an EN regarding preservation of parameters in AS 11.4.0 11.5.0 C1-122686 2012-09 CP-57 CP-120603 4100 Removing EN regarding number normalization and enum translation 11.4.0 11.5.0 C1-122687 2012-09 CP-57 CP-120603 4107 1 IOI usage between TRF and terminating side 11.4.0 11.5.0 C1-123284 2012-09 CP-57 CP-120603 4108 1 Co-location of TRF 11.4.0 11.5.0 C1-123285 2012-09 CP-57 CP-120569 4114 1 Correct handling of PPR in S-CSCF 11.4.0 11.5.0 C1-123109 2012-09 CP-57 CP-120583 4115 1 Correction ue initiated deregistration 11.4.0 11.5.0 C1-123295 2012-09 CP-57 CP-120577 4118 1 Condition for usage of Session-ID header filed within MESSAGE response 11.4.0 11.5.0 C1-123134 2012-09 CP-57 CP-120597 4119 Reference update: draft-ietf-mediactrl-mrb 11.4.0 11.5.0 C1-122765 2012-09 CP-57 CP-120597 4120 3 Visited network MRB information 11.4.0 11.5.0 C1-123396 2012-09 CP-57 CP-120583 4121 3 PCSCF discovery clarification 11.4.0 11.5.0 C1-123440 2012-09 CP-57 CP-120600 4122 2 Clarifications of used identities for registration procedures 11.4.0 11.5.0 C1-123355 2012-09 CP-57 CP-120588 4123 3 DVB-RCS2 satellite access network as IP-CAN for IMS 11.4.0 11.5.0 C1-123428 2012-09 CP-57 CP-120600 4124 3 Add reg-event changes for RFC 6140 11.4.0 11.5.0 C1-123378 2012-09 CP-57 CP-120583 4126 1 P-CSCF registration context lost 11.4.0 11.5.0 C1-123297 2012-09 CP-57 CP-120588 4131 1 Correction DHCP mechanism for P-CSCF discovery in Annex M 11.4.0 11.5.0 C1-123293 2012-09 CP-57 CP-120588 4132 1 Correction to DHCP mechanism for P-CSCF discovery in Annex O 11.4.0 11.5.0 C1-123294 2012-09 CP-57 CP-120588 4133 Correction to Annex 9.2 11.4.0 11.5.0 C1-122849 2012-09 CP-57 CP-120570 4137 1 Reference update: draft-ietf-mmusic-ice-tcp 11.4.0 11.5.0 C1-123130 2012-09 CP-57 CP-120601 4140 1 Network provided location information inserted by the MSC server enhanced for ICS 11.4.0 11.5.0 C1-123259 2012-09 CP-57 CP-120591 4146 Specification of ISC gateway function – general clauses 11.4.0 11.5.0 C1-122928 2012-09 CP-57 CP-120591 4147 1 Specification of ISC gateway function – SIP procedures 11.4.0 11.5.0 C1-123271 2012-09 CP-57 CP-120591 4148 1 Specification of application gateway function – SDP procedures 11.4.0 11.5.0 C1-123272 2012-09 CP-57 CP-120588 4151 Reversal of terminology change in annex D 11.4.0 11.5.0 C1-122939 2012-09 CP-57 CP-120588 4152 1 Emergency priority using the Resource-Priority header field 11.4.0 11.5.0 C1-123173 2012-09 CP-57 CP-120641 4153 3 Description of overload control 11.4.0 11.5.0 - 2012-09 CP-57 CP-120642 4154 3 Support of overload control 11.4.0 11.5.0 - 2012-09 CP-57 CP-120664 4156 5 Media plane security 11.4.0 11.5.0 - 2012-09 CP-57 CP-120576 4159 1 mediasec ref deletions 11.4.0 11.5.0 C1-123141 2012-09 CP-57 CP-120603 4162 Updates to charging introduction for RAVEL 11.4.0 11.5.0 C1-122968 2012-09 CP-57 CP-120588 4163 1 Condition for restoration procedures causing UE reregistration 11.4.0 11.5.0 C1-123174 2012-09 CP-57 CP-120588 4164 1 Missing procedure for NASS-IMS bundled authentication at S-CSCF 11.4.0 11.5.0 C1-123171 2012-09 CP-57 CP-120574 4180 2 Emergency and normal registration independence 11.4.0 11.5.0 C1-123374 2012-09 CP-57 CP-120606 4185 2 Support of T.38 related SDP attributes 11.4.0 11.5.0 C1-123400 2012-09 CP-57 CP-120578 4188 Correcting incorrect references in P-CSCF procedures when emergency call failure occurs 11.4.0 11.5.0 C1-123164 2012-09 CP-57 CP-120656 4189 1 Reference list correction to align with the corrected TS 29.212 title 11.4.0 11.5.0 - 2012-12 CP-58 CP-120802 4106 5 Additional guidance on use of 3xx responses 11.5.0 11.6.0 C1-124983 2012-12 CP-58 CP-120802 4127 2 Update the general requirements for tunnel procedures 11.5.0 11.6.0 C1-123886 2012-12 CP-58 CP-120802 4128 4 IP address obtained on S2a interface 11.5.0 11.6.0 C1-124274 2012-12 CP-58 CP-120802 4129 4 Tunnel modification by the UE 11.5.0 11.6.0 C1-124275 2012-12 CP-58 CP-120802 4130 5 Tunnel modification by the network 11.5.0 11.6.0 C1-124276 2012-12 CP-58 CP-120804 4149 3 Specification of ISC gateway function – SIP profile 11.5.0 11.6.0 C1-124261 2012-12 CP-58 CP-120804 4150 2 Specification of application gateway function – SDP profile 11.5.0 11.6.0 C1-124100 2012-12 CP-58 CP-120787 4187 1 IANA registration of OMR parameters 11.5.0 11.6.0 C1-123575 2012-12 CP-58 CP-120783 4196 Delete IETF mediasec draft reference 11.5.0 11.6.0 C1-123520 2012-12 CP-58 CP-120783 4197 IMS media security profile table cleanup 11.5.0 11.6.0 C1-123521 2012-12 CP-58 CP-120793 4201 4 Contents of From and To header fields in SUBSCRIBE message 11.5.0 11.6.0 C1-124950 2012-12 CP-58 CP-120802 4202 4 Correction on handling of rn parameter and npdi parameter at S-CSCF. 11.5.0 11.6.0 C1-125015 2012-12 CP-58 CP-120821 4203 2 Support of T.38 SDP attributes in IMS 11.5.0 11.6.0 C1-124158 2012-12 CP-58 CP-120801 4204 1 Transit-ioi is removed from fowarded message to visited network 11.5.0 11.6.0 C1-124092 2012-12 CP-58 CP-120815 4205 5 Overload control clarifications 11.5.0 11.6.0 C1-125010 2012-12 CP-58 CP-120812 4206 3 Removing ENs about IBCF and OMR 11.5.0 11.6.0 C1-124262 2012-12 CP-58 CP-120812 4207 Removing an EN regarding PSI 11.5.0 11.6.0 C1-123620 2012-12 CP-58 CP-120812 4212 Correcting the UE-originating case indication 11.5.0 11.6.0 C1-123630 2012-12 CP-58 CP-120793 4214 6 Correcting procedures for re-establishment a context for SIP signalling 11.5.0 11.6.0 C1-124952 2012-12 CP-58 CP-120773 4219 4 Correction of emergency sub-service type handling 11.5.0 11.6.0 C1-124284 2012-12 CP-58 CP-120793 4220 2 Remaining corrections to emergency sub-service type handling 11.5.0 11.6.0 C1-124181 2012-12 CP-58 CP-120782 4223 2 Corrections to E-CSCF and LRF handling for emergency calls 11.5.0 11.6.0 C1-124764 2012-12 CP-58 CP-120812 4224 Application servers and RAVEL 11.5.0 11.6.0 C1-123577 2012-12 CP-58 CP-120777 4228 1 Correction of 3GPP IM CN subsystem XML handling 11.5.0 11.6.0 C1-123972 2012-12 CP-58 CP-120793 4229 3 PCSCF discovery Annex L editorial 11.5.0 11.6.0 C1-124989 2012-12 CP-58 CP-120776 4234 Table A.162, item 61 referencing incorrect document 11.5.0 11.6.0 C1-123669 2012-12 CP-58 CP-120802 4235 1 SDP impacts due to IP-CAN bearer release 11.5.0 11.6.0 C1-124006 2012-12 CP-58 CP-120802 4236 1 Precondition and INVITE without SDP offer 11.5.0 11.6.0 C1-124007 2012-12 CP-58 CP-120802 4237 1 User rejecting media stream during set up of multimedia session 11.5.0 11.6.0 C1-124008 2012-12 CP-58 CP-120812 4239 1 Decission on loop back routing in S-CSCF 11.5.0 11.6.0 C1-124102 2012-12 CP-58 CP-120793 4241 1 Correct Defintion of Temporarily Authorized Resource-Priority 11.5.0 11.6.0 C1-124003 2012-12 CP-58 CP-120791 4243 2 Reference update: draft-ietf-sipcore-proxy-feature 11.5.0 11.6.0 C1-124766 2012-12 CP-58 CP-120791 4244 1 Feature-Caps header field in target refresh requests and responses 11.5.0 11.6.0 C1-124122 2012-12 CP-58 CP-120804 4247 1 Specification of application gateway function – SDP procedures 11.5.0 11.6.0 C1-124098 2012-12 CP-58 CP-120810 4248 1 Profiles change for P-Access-Network-Info header 11.5.0 11.6.0 C1-124111 2012-12 CP-58 CP-120810 4249 3 Correction to the coding of UE-time-zone 11.5.0 11.6.0 C1-124273 2012-12 CP-58 CP-120810 4250 2 Removal of Editor's Note on NPLI inserted by both P-CSCF and AS 11.5.0 11.6.0 C1-124223 2012-12 CP-58 CP-120793 4251 1 Correct emergency call description when roaming 11.5.0 11.6.0 C1-124116 2012-12 CP-58 CP-120782 4254 Dialog state notification clarification 11.5.0 11.6.0 C1-123752 2012-12 CP-58 CP-120785 4257 1 Emergency and normal registration independence 11.5.0 11.6.0 C1-123994 2012-12 CP-58 CP-120815 4258 5 Overload control -Inconstancies correction 11.5.0 11.6.0 C1-125009 2012-12 CP-58 CP-120815 4262 3 Event-based overload control procedures 11.5.0 11.6.0 C1-124856 2012-12 CP-58 CP-120780 4263 2 Correction to integrity-protected usage in S-CSCF 11.5.0 11.6.0 C1-124150 2012-12 CP-58 CP-120809 4273 Mz Reference Point – ISC alternative 11.5.0 11.6.0 C1-124301 2012-12 CP-58 CP-120812 4275 1 Removing the g.3gpp.loopback in TRF 11.5.0 11.6.0 C1-124850 2012-12 CP-58 CP-120788 4281 Reference update: RFC 6679 11.5.0 11.6.0 C1-124369 2012-12 CP-58 CP-120775 4285 3 Updating IMEI URN draft reference 11.5.0 11.6.0 C1-125006 2012-12 CP-58 CP-120793 4286 2 Default ICSI value selected by S-CSCF 11.5.0 11.6.0 C1-124951 2012-12 CP-58 CP-120810 4287 Correction of "UE-time-zone" to "local-time-zone" in TS 24.229 11.5.0 11.6.0 C1-124433 2012-12 CP-58 CP-120801 4288 Transit IOI general description 11.5.0 11.6.0 C1-124439 2012-12 CP-58 CP-120801 4289 1 Including transit-IOI in SIP responses 11.5.0 11.6.0 C1-124843 2012-12 CP-58 CP-120802 4294 1 Removal of internal references from IBCF procedures 11.5.0 11.6.0 C1-124772 2012-12 CP-58 CP-120815 4296 2 Closure of open issues in IOC work item 11.5.0 11.6.0 C1-125008 2012-12 CP-58 CP-120793 4299 1 P-CSCF registration context lost – text correction 11.5.0 11.6.0 C1-124896 2012-12 CP-58 CP-120793 4300 NAT detection by the UE- text correction 11.5.0 11.6.0 C1-124521 2012-12 CP-58 CP-120780 4305 Correction on integrity-protected handling in S-CSCF 11.5.0 11.6.0 C1-124528 2012-12 CP-58 CP-120793 4311 1 Correction to challenge response examination in P-CSCF 11.5.0 11.6.0 C1-124903 2013-03 CP-59 CP-130093 4139 6 IBCF don't change the dialog-ID 11.6.0 11.7.0 C1-130555 2013-03 CP-59 CP-130117 4238 3 Network provided cell identity for UTRAN 11.6.0 11.7.0 C1-130501 2013-03 CP-59 CP-130110 4246 4 Specification of ISC gateway function – SIP procedures 11.6.0 11.7.0 C1-130336 2013-03 CP-59 CP-130117 4301 5 Network provided Geographical Identifier 11.6.0 11.7.0 C1-130915 2013-03 CP-59 CP-130099 4314 4 Correct determination of the status of being available for voice over PS 11.6.0 11.7.0 C1-130892 2013-03 CP-59 CP-130116 4315 3 Correcting availability for calls when dedicated bearer suitable for SIP signalling is used 11.6.0 11.7.0 C1-130897 2013-03 CP-59 CP-130117 4324 1 P-CSCF handling of PANI in case PCRF is used 11.6.0 11.7.0 C1-130502 2013-03 CP-59 CP-130098 4327 1 Security Client header in case of Media Sec 11.6.0 11.7.0 C1-130536 2013-03 CP-59 CP-130107 4331 1 Support for P-Charging-Vector in SIP ACK 11.6.0 11.7.0 C1-130512 2013-03 CP-59 CP-130107 4332 1 Replacement of RFC3455 by draft-drage-sipping-rfc3455bis-06 11.6.0 11.7.0 C1-130564 2013-03 CP-59 CP-130107 4333 1 Clarification of handling IOI parameter at S-CSCF 11.6.0 11.7.0 C1-130565 2013-03 CP-59 CP-130107 4334 3 Clarification of handling IOI parameters at transit function 11.6.0 11.7.0 C1-130895 2013-03 CP-59 CP-130102 4337 Reference update: RFC 6809 11.6.0 11.7.0 C1-130143 2013-03 CP-59 CP-130116 4440 Correcting reference to PSU extension 11.6.0 11.7.0 C1-130164 2013-03 CP-59 CP-130116 4441 1 ICSIs in Contact and Accept-Contact header fields 11.6.0 11.7.0 C1-130746 2013-03 CP-59 CP-130101 4447 2 Annex A updates for RFC5506 11.6.0 11.7.0 C1-130797 2013-03 CP-59 CP-130101 4450 2 Annex A updates for RFC3611 11.6.0 11.7.0 C1-130814 2013-03 CP-59 CP-130116 4451 2 Annex A updates for 3gpp_MaxRecvSDUSize SDP attributes 11.6.0 11.7.0 C1-130827 2013-03 CP-59 CP-130094 4462 1 Correction of subclause reference in dialstring related procedures 11.6.0 11.7.0 C1-130739 2013-03 CP-59 CP-130098 4469 Delete IETF mediasec draft reference 11.6.0 11.7.0 C1-130328 2013-03 CP-59 CP-130101 4471 Correction of references to annex G and annex F 11.6.0 11.7.0 C1-130334 2013-03 CP-59 CP-130121 4472 Interaction between overload control mechanisms 11.6.0 11.7.0 C1-130337 2013-03 CP-59 CP-130098 4480 1 IANA registration issues for a=3ge2ae 11.6.0 11.7.0 C1-130539 2013-03 CP-59 CP-130096 4483 1 Profile changes relating to CRS 11.6.0 11.7.0 C1-130542 2013-03 CP-59 CP-130135 4456 2 Improvements to the UE Keepalive Procedure for UE managed NAT Traversal 11.7.0 12.0.0 C1-130901 2013-03 CP-59 CP-130135 4461 Correction of header styles 11.7.0 12.0.0 C1-130269 2013-03 CP-59 CP-130188 4477 3 Emergency service URN for country specific types of emergency service 11.7.0 12.0.0 - 2013-06 CP-60 CP-130261 4448 2 Annex A updates for RFC5285 12.0.0 12.1.0 C1-132481 2013-06 CP-60 CP-130262 4449 3 Annex A updates for RFC6236 12.0.0 12.1.0 C1-132315 2013-06 CP-60 CP-130268 4476 4 PSAP Callback Indicator 12.0.0 12.1.0 C1-131784 2013-06 CP-60 CP-130222 4499 1 Updating MMUSIC draft references for ICS User Agent and SCC Application Server 12.0.0 12.1.0 C1-132292 2013-06 CP-60 CP-130240 4502 1 Reference update of draft-atarius-dispatch-meid-urn 12.0.0 12.1.0 C1-131543 2013-06 CP-60 CP-130257 4503 Missplaced release procedure 12.0.0 12.1.0 C1-131038 2013-06 CP-60 CP-130257 4504 4 P-Visited-Network-ID clarifications 12.0.0 12.1.0 C1-131775 2013-06 CP-60 CP-130227 4505 1 Not reachable for SIP signalling due to unclear requirement on re-establishment of the SIP signalling bearer 12.0.0 12.1.0 C1-131410 2013-06 CP-60 CP-130231 4506 3 UE indicating type of emergency service when 380 response is received 12.0.0 12.1.0 C1-131924 2013-06 CP-60 CP-130257 4507 5 EN correction on IANA registration 12.0.0 12.1.0 C1-131851 2013-06 CP-60 CP-130387 4508 2 Adjacent Network Indicator 12.0.0 12.1.0 - 2013-06 CP-60 CP-130257 4509 2 IANA registered URN for emergency service offered in one country only 12.0.0 12.1.0 C1-131741 2013-06 CP-60 CP-130252 4516 Syntax for "local-time-zone" incorrect 12.0.0 12.1.0 C1-131084 2013-06 CP-60 CP-130257 4517 2 Adding the procedure of the "icid-value" header field parameter in SIP response 12.0.0 12.1.0 C1-131714 2013-06 CP-60 CP-130242 4529 1 "transit-ioi" header field parameter correction 12.0.0 12.1.0 C1-131633 2013-06 CP-60 CP-130253 4531 Removing RAVEL EN related to charging indicators 12.0.0 12.1.0 C1-131151 2013-06 CP-60 CP-130253 4533 1 IOI exchange when loopback routeing occurs 12.0.0 12.1.0 C1-131621 2013-06 CP-60 CP-130253 4535 1 Handling of transit IOI when loopback routeing occurs 12.0.0 12.1.0 C1-131623 2013-06 CP-60 CP-130265 4537 1 Type 1 IOI for originating leg P-CSCF to S-CSCF 12.0.0 12.1.0 C1-131614 2013-06 CP-60 CP-130265 4539 1 Type 1 IOI for terminating leg P-CSCF to S-CSCF 12.0.0 12.1.0 C1-131615 2013-06 CP-60 CP-130265 4541 3 Type 1 IOI P-CSCF to S-CSCF for SUBSCRIBE 12.0.0 12.1.0 C1-132480 2013-06 CP-60 CP-130265 4547 5 Resolving IMS dangling session issue 12.0.0 12.1.0 C1-132658 2013-06 CP-60 CP-130230 4548 1 Emergency bearer support and IMS Emergency correction 12.0.0 12.1.0 C1-131414 2013-06 CP-60 CP-130233 4557 3 Removal of dialled digits option from emergency call generation 12.0.0 12.1.0 C1-132564 2013-06 CP-60 CP-130251 4569 2 Removal of Editor's Note on maximum number of registration flows 12.0.0 12.1.0 C1-131635 2013-06 CP-60 CP-130257 4576 2 Phone-context : text clarification 12.0.0 12.1.0 C1-132668 2013-06 CP-60 CP-130220 4585 3 Prevent receipt of normal call at the UE while it is attached for emergency services only 12.0.0 12.1.0 C1-132627 2013-06 CP-60 CP-130257 4586 1 S-CSCF procedures for inserting the P-Acces-Network-Info header 12.0.0 12.1.0 C1-132322 2013-06 CP-60 CP-130265 4587 Correcting the list of header fields parameters in 4.5.1 12.0.0 12.1.0 C1-131908 2013-06 CP-60 CP-130265 4588 1 Reason header field in CANCEL 12.0.0 12.1.0 C1-132478 2013-06 CP-60 CP-130388 4589 4 PSAP Callback Indicator: Annex A 12.0.0 12.1.0 - 2013-06 CP-60 CP-130257 4590 Correction on title of IETF RFC 5031 12.0.0 12.1.0 C1-131945 2013-06 CP-60 CP-130257 4591 1 Encoding for "integrity-protected" parameter 12.0.0 12.1.0 C1-132323 2013-06 CP-60 CP-130265 4604 1 Editorial CR against UE procedures for emergency services 12.0.0 12.1.0 C1-132483 2013-06 CP-60 CP-130225 4609 2 Consolidation of DTMF info package definition in 3GPP TS 24.229 12.0.0 12.1.0 C1-132580 2013-06 CP-60 CP-130265 4611 Rport for UDP only 12.0.0 12.1.0 C1-132126 2013-09 CP-61 CP-130504 4574 1 Indication of network supported services to the UE in Feature-Caps header 12.1.0 12.2.0 C1-133633 2013-09 CP-61 CP-130504 4575 6 Nonce caching handling to optimize authentication procedures 12.1.0 12.2.0 C1-133661 2013-09 CP-61 CP-130507 4602 3 Ignore a PSAP callback indicator defined in draft-ietf-ecrit-psap-callback at the UE 12.1.0 12.2.0 C1-133522 2013-09 CP-61 CP-130481 4616 1 Updating IMEI URN draft reference 12.1.0 12.2.0 C1-133252 2013-09 CP-61 CP-130513 4617 1 Updating TS 24.229 to RFC 6665 12.1.0 12.2.0 C1-133236 2013-09 CP-61 CP-130511 4620 Clarification of Service-Route header usage 12.1.0 12.2.0 C1-132718 2013-09 CP-61 CP-130504 4621 3 Clarifying that ISO 3166-1 alpha-2 codes are not neccesarily country codes 12.1.0 12.2.0 C1-133631 2013-09 CP-61 CP-130512 4622 2 Access via WLAN connected to EPC when WLAN is a restrictive non-3GPP access network 12.1.0 12.2.0 C1-133575 2013-09 CP-61 CP-130504 4623 2 Fixing issues in RTP media security 12.1.0 12.2.0 C1-133524 2013-09 CP-61 CP-130504 4626 2 Correct "otherwise" condition, causing emergency call failure or delay 12.1.0 12.2.0 C1-133525 2013-09 CP-61 CP-130493 4629 Via header field handling on Privacy protection at IBCF 12.1.0 12.2.0 C1-132756 2013-09 CP-61 CP-130483 4634 1 Reference update of draft-vanelburg-dispatch-private-network-ind 12.1.0 12.2.0 C1-133265 2013-09 CP-61 CP-130511 4635 2 P-CSCF discovery 12.1.0 12.2.0 C1-133579 2013-09 CP-61 CP-130511 4638 2 S-CSCF matching between ICSIs and SIP request content 12.1.0 12.2.0 C1-133636 2013-09 CP-61 CP-130504 4639 1 Overload control application 12.1.0 12.2.0 C1-133476 2013-09 CP-61 CP-130504 4640 Correction on the supported SIP status codes profile 12.1.0 12.2.0 C1-132824 2013-09 CP-61 CP-130511 4642 1 Priority Consideration for SIP Overload Control 12.1.0 12.2.0 C1-133310 2013-09 CP-61 CP-130511 4643 3 Switching to CS domain when the PS voice call initiation is failed due to access class barring (24.229) alternative2 12.1.0 12.2.0 C1-133638 2013-09 CP-61 CP-130501 4648 3 Identifying the home network to TRF 12.1.0 12.2.0 C1-133611 2013-09 CP-61 CP-130511 4652 3 Clarification on UE reaction to IP-CAN bearer changes during a VoLTE/VT call 12.1.0 12.2.0 C1-133639 2013-09 CP-61 CP-130512 4653 2 Tunnelling over restrictive access networks IMS case 12.1.0 12.2.0 C1-133580 2013-09 CP-61 CP-130504 4654 draft-ietf-ecrit-psap-callback reference update 12.1.0 12.2.0 C1-133024 2013-09 CP-61 CP-130507 4655 draft-ietf-ecrit-psap-callback reference update 12.1.0 12.2.0 C1-133025 2013-09 CP-61 CP-130507 4656 Addition of AS to profile tables 12.1.0 12.2.0 C1-133031 2013-09 CP-61 CP-130488 4666 1 Fixing essential issues in RTP media security 12.1.0 12.2.0 C1-133505 2013-12 CP-62 CP-130749 4624 3 End-to-access-edge media security for MSRP, BFCP and UDPTL 12.2.0 12.3.0 C1-134612 2013-12 CP-62 CP-130753 4660 5 Include DST adjustment in local time zone 12.2.0 12.3.0 C1-135174 2013-12 CP-62 CP-130753 4667 3 Adding country-specific URN to configurable lists 12.2.0 12.3.0 C1-134510 2013-12 CP-62 CP-130758 4669 2 Improve requirement to ignore the PSAP callback indicator 12.2.0 12.3.0 C1-134330 2013-12 CP-62 CP-130722 4677 1 Reference update of draft-vanelburg-dispatch-private-network-ind 12.2.0 12.3.0 C1-134200 2013-12 CP-62 CP-130728 4681 Reference update: draft-kaplan-insipid-session-id 12.2.0 12.3.0 C1-133695 2013-12 CP-62 CP-130748 4683 1 Reference update: draft-ietf-soc-overload-control, draft-ietf-soc-overload-rate-control and draft-ietf-soc-load-control-event-package 12.2.0 12.3.0 C1-134439 2013-12 CP-62 CP-130743 4685 1 Reference update: RFC 6917 (draft-ietf-mediactrl-mrb) 12.2.0 12.3.0 C1-134189 2013-12 CP-62 CP-130764 4686 1 Editor's note in access via WLAN connected to EPC when WLAN is a restrictive non-3GPP access network 12.2.0 12.3.0 C1-134102 2013-12 CP-62 CP-130804 4687 2 Solution for tunnelling of IMS services over restrictive non-3GPP access networks - keep-alive using RFC 6223 12.2.0 12.3.0 - 2013-12 CP-62 CP-130721 4692 1 Reference update: RFC 7006 (draft-ietf-mmusic-sdp-miscellaneous-caps) 12.2.0 12.3.0 C1-134210 2013-12 CP-62 CP-130766 4694 2 Addition of Definitions for Business Trunking 12.2.0 12.3.0 C1-134447 2013-12 CP-62 CP-130766 4695 2 Addition of Business Trunking Features for Signalling Security 12.2.0 12.3.0 C1-134448 2013-12 CP-62 CP-130766 4696 3 Addition of Business Trunking Features at UE 12.2.0 12.3.0 C1-134478 2013-12 CP-62 CP-130767 4697 3 Addition of Business Trunking Features at P-CSCF 12.2.0 12.3.0 C1-134975 2013-12 CP-62 CP-130753 4701 3 Nonce caching and digest authentication- corrections 12.2.0 12.3.0 C1-134525 2013-12 CP-62 CP-130805 4712 4 Tunnelling over restrictive access networks IMS case 12.2.0 12.3.0 - 2013-12 CP-62 CP-130733 4716 3 Use of ECN in Multimedia Priority Service 12.2.0 12.3.0 C1-134374 2013-12 CP-62 CP-130814 4717 5 Updating the depiction of the creation of subscription dialog 12.2.0 12.3.0 - 2013-12 CP-62 CP-130729 4722 Fixing remaining errors in media security 12.2.0 12.3.0 C1-133921 2013-12 CP-62 CP-130753 4723 3 Correction to formatting of text in Abnormal cases related to mobile originated sessions 12.2.0 12.3.0 C1-135173 2013-12 CP-62 CP-130753 4724 1 Correcting table number for IM CN Subsystem XML body schema 12.2.0 12.3.0 C1-135172 2013-12 CP-62 CP-130731 4730 4 Correction when receiving a 380 (Alternative Service) response indicating "emergency" to UE non-detectable IMS emergency call 12.2.0 12.3.0 C1-134906 2013-12 CP-62 CP-130753 4731 3 Time zone in Pacific/Kiritimati 12.2.0 12.3.0 C1-135175 2013-12 CP-62 CP-130753 4736 1 Reversal of change relating to digest authentication 12.2.0 12.3.0 C1-134233 2013-12 CP-62 CP-130720 4741 Reference Update: draft-ietf-salud-alert-info-urns 12.2.0 12.3.0 C1-134537 2013-12 CP-62 CP-130753 4745 1 Number of retry attempts when receiving invalid challenges in IMS AKA procedure 12.2.0 12.3.0 C1-135109 2013-12 CP-62 CP-130736 4746 1 Incorrect preconditions for inclusion of P-Refused-URI-List and Retry-After header fields in INVITE 12.2.0 12.3.0 C1-135119 2013-12 CP-62 CP-130753 4747 1 Inclusion of b=RR and b=RS at session-level in SDP 12.2.0 12.3.0 C1-135111 2013-12 CP-62 CP-130744 4751 Correct Annex A due to 3xx response containing a Contact header field 12.2.0 12.3.0 C1-134571 2013-12 CP-62 CP-130753 4753 1 P-ANI encoding correction 12.2.0 12.3.0 C1-135009 2013-12 CP-62 CP-130753 4754 1 Proxy-Authentication-Info header field not defined for SIP 12.2.0 12.3.0 C1-135106 2013-12 CP-62 CP-130746 4756 utran-sai-id-3gpp and utran-sai-3gpp 12.2.0 12.3.0 C1-134610 2013-12 CP-62 CP-130749 4757 End-to-end media security for MSRP using TLS and KMS 12.2.0 12.3.0 C1-134613 2013-12 CP-62 CP-130758 4760 2 EN Removal: Support of the PSAP callback indicator in non-INVITE requests 12.2.0 12.3.0 C1-135149 2013-12 CP-62 CP-130747 4762 1 Home network bypassing of E.164 translation 12.2.0 12.3.0 C1-135008 2013-12 CP-62 CP-130721 4767 1 Updating IMEI URN draft reference 12.2.0 12.3.0 C1-134988 2013-12 CP-62 CP-130753 4769 2 Nodes that set the access-class parameter 12.2.0 12.3.0 C1-135180 2013-12 CP-62 CP-130753 4770 1 Correction term-ioi handling 12.2.0 12.3.0 C1-135176 2013-12 CP-62 CP-130770 4776 2 Mapping of Target-Dialog identifiers 12.2.0 12.3.0 C1-135151 2013-12 CP-62 CP-130758 4713 2 Reference update: draft-ietf-ecrit-psap-callback 12.2.0 12.3.0 C1-134650 2014-03 CP-63 CP-140153 4748 5 Usage of b=AS 12.3.0 12.4.0 C1-140636 2014-03 CP-63 CP-140126 4785 2 Clarify that SDP for sessions with voice media can be updated in a TA indicating voice over PS is not supported 12.3.0 12.4.0 C1-140401 2014-03 CP-63 CP-140150 4786 1 Reference update of draft-ietf-mmusic-udptl-dtls 12.3.0 12.4.0 C1-140593 2014-03 CP-63 CP-140146 4787 Solution for tunnelling of IMS services over restrictive non-3GPP access networks - keep-alive using RFC 6223 in Annex D 12.3.0 12.4.0 C1-140018 2014-03 CP-63 CP-140133 4789 Re-adding 3gpp body xml schema to archive 12.3.0 12.4.0 C1-140032 2014-03 CP-63 CP-140128 4791 2 Correction on syntax of values of feature capability indicators 12.3.0 12.4.0 C1-140661 2014-03 CP-63 CP-140115 4796 Reference update of draft-vanelburg-dispatch-private-network-ind 12.3.0 12.4.0 C1-140052 2014-03 CP-63 CP-140153 4797 1 Collection of transit-ioi example 12.3.0 12.4.0 C1-140611 2014-03 CP-63 CP-140115 4802 1 Correcting P-Private-Network-Indication descriptions in response 12.3.0 12.4.0 C1-140471 2014-03 CP-63 CP-140153 4804 1 Alignment between Annex I and the core specification 12.3.0 12.4.0 C1-140614 2014-03 CP-63 CP-140149 4805 Correction of P-CSCF procedures for Business Trunking 12.3.0 12.4.0 C1-140138 2014-03 CP-63 CP-140121 4809 3 Non UE detected emergency call correction for retry in CS domain 12.3.0 12.4.0 C1-140778 2014-03 CP-63 CP-140119 4815 1 Lost procedures for handling Retry-After in failure response to REGISTER request 12.3.0 12.4.0 C1-140478 2014-03 CP-63 CP-140149 4816 1 Business trunking in IBCF 12.3.0 12.4.0 C1-140587 2014-03 CP-63 CP-140128 4818 Correcting g.3gpp.home visited feature-capability indicator name 12.3.0 12.4.0 C1-140190 2014-03 CP-63 CP-140114 4823 1 Updating IMEI URN draft reference 12.3.0 12.4.0 C1-140500 2014-03 CP-63 CP-140113 4830 2 Allocating a GRUU when the explictly registered IMPU is barred 12.3.0 12.4.0 C1-140693 2014-03 CP-63 CP-140153 4842 2 daylight-saving-time definition clarifications 12.3.0 12.4.0 C1-140675 2014-03 CP-63 CP-140153 4843 1 Use of "daylight-saving-time" parameter 12.3.0 12.4.0 C1-140624 2014-03 CP-63 CP-140113 4845 2 Generation of Public GRUU 12.3.0 12.4.0 C1-140699 2014-03 CP-63 CP-140153 4846 1 P-CSCF and GRUU 12.3.0 12.4.0 C1-140610 2014-06 CP-64 CP-140332 4771 6 Firewall traversal for IMS services based on ICE 12.4.0 12.5.0 C1-141589 2014-06 CP-64 CP-140322 4855 3 Non UE detected emergency call correction: additional cases for retry attempt using EMERGENCY SETUP in CS domain 12.4.0 12.5.0 C1-142524 2014-06 CP-64 CP-140320 4856 1 IMS based telepresence: 24.229 SDP impacts 12.4.0 12.5.0 C1-141464 2014-06 CP-64 CP-140296 4858 3 Clarification of payload type usage for telephony-events 12.4.0 12.5.0 C1-141629 2014-06 CP-64 CP-140317 4860 2 Reference update: RFC 7090 (draft-ietf-ecrit-psap-callback) 12.4.0 12.5.0 C1-142349 2014-06 CP-64 CP-140296 4865 3 Corrections for voice centric UE to continue being reachable for IMS voice when P-CSCF serving the UE stops being available 12.4.0 12.5.0 C1-141555 2014-06 CP-64 CP-140318 4866 1 Reference update of draft-ietf-mmusic-udptl-dtls 12.4.0 12.5.0 C1-141481 2014-06 CP-64 CP-140322 4867 SIP timer table update due to RFC 6026 12.4.0 12.5.0 C1-140907 2014-06 CP-64 CP-140330 4868 1 Routeing to MSC server in S-CSCF 12.4.0 12.5.0 C1-141497 2014-06 CP-64 CP-140302 4871 1 IOI exchange between the SCC AS and ATCF 12.4.0 12.5.0 C1-141500 2014-06 CP-64 CP-140322 4888 5 Proactive media transcoding in IMS 12.4.0 12.5.0 C1-142533 2014-06 CP-64 CP-140324 4889 2 Indicating traffic leg in dialog creating and stand-alone requests 12.4.0 12.5.0 C1-142410 2014-06 CP-64 CP-140295 4894 1 Reference update of draft-vanelburg-dispatch-private-network-ind 12.4.0 12.5.0 C1-141806 2014-06 CP-64 CP-140322 4902 2 Support of RFC 3263 for P-CSCF discovery procedure 12.4.0 12.5.0 C1-141592 2014-06 CP-64 CP-140291 4908 Syntax for OLI is incorrect 12.4.0 12.5.0 C1-141035 2014-06 CP-64 CP-140294 4913 1 GRUU validation 12.4.0 12.5.0 C1-141367 2014-06 CP-64 CP-140322 4914 1 Issue with "Tokenized-by" 12.4.0 12.5.0 C1-141482 2014-06 CP-64 CP-140300 4922 Profile table changes for SDES media plane security role 12.4.0 12.5.0 C1-141057 2014-06 CP-64 CP-140318 4923 Profile tables changes for e2e media security for MSRP using TLS and KMS 12.4.0 12.5.0 C1-141058 2014-06 CP-64 CP-140318 4924 Profile tables changes for mediasec header field 12.4.0 12.5.0 C1-141059 2014-06 CP-64 CP-140322 4930 3 Remote strength tag value in subsequent SDP offers 12.4.0 12.5.0 C1-141658 2014-06 CP-64 CP-140322 4934 Correction of I-CSCF IOI Note 12.4.0 12.5.0 C1-141141 2014-06 CP-64 CP-140322 4935 IOI in NOTIFY response 12.4.0 12.5.0 C1-141142 2014-06 CP-64 CP-140316 4936 4 Barring premium rate number 12.4.0 12.5.0 C1-142407 2014-06 CP-64 CP-140322 4938 2 Fail-safe emergency PDN connection release 12.4.0 12.5.0 C1-142504 2014-06 CP-64 CP-140307 4940 1 EN removal: Feature-capability indicator IANA registration status 12.4.0 12.5.0 C1-142256 2014-06 CP-64 CP-140311 4942 1 Correction of g.3gpp.icsi-ref feature-capability indicator definition 12.4.0 12.5.0 C1-142258 2014-06 CP-64 CP-140321 4943 1 Web Real Time Communication (WebRTC) Access to IMS: Annex A impacts 12.4.0 12.5.0 C1-142336 2014-06 CP-64 CP-140322 4944 3 Applicability of i-wlan-node-id parameter in P-Access-Network-Info 12.4.0 12.5.0 C1-142529 2014-06 CP-64 CP-140299 4961 2 Solution for editor's note related to draft-ietf-sipcore-rfc4244bis-00 12.4.0 12.5.0 C1-142451 2014-06 CP-64 CP-140292 4967 2 URI matching for terminating requests 12.4.0 12.5.0 C1-142441 2014-06 CP-64 CP-140324 4968 2 Traffic leg URI parameter in SUBSCRIBE from P-CSCF 12.4.0 12.5.0 C1-142413 2014-06 CP-64 CP-140324 4969 1 Trust domain for traffic leg URI parameter 12.4.0 12.5.0 C1-142362 2014-06 CP-64 CP-140324 4970 2 Traffic leg URI parameter – Annex A 12.4.0 12.5.0 C1-142414 2014-06 CP-64 CP-140294 4975 1 Updating CS-SDP draft reference to RFC 7195 12.4.0 12.5.0 C1-142241 2014-06 CP-64 CP-140322 4979 2 Session refresh request retry 12.4.0 12.5.0 C1-142525 2014-06 CP-64 CP-140304 4982 1 Update draft-atarius-dispatch-meid-urn 12.4.0 12.5.0 C1-142254 2014-06 CP-64 CP-140322 4984 2 Reference mismatch between Rel-11 and Rel-12 12.4.0 12.5.0 C1-142505 2014-06 CP-64 CP-140322 4985 1 Race case for subscription to reg-event 12.4.0 12.5.0 C1-142367 2014-06 CP-64 CP-140321 4988 3 WebRTC access to IMS general part 12.4.0 12.5.0 C1-142514 2014-06 CP-64 CP-140305 4992 1 Reference update for overload control 12.4.0 12.5.0 C1-142263 2014-06 CP-64 CP-140332 4993 1 Removal of TURAN material from non-supported access technology I-WLAN 12.4.0 12.5.0 C1-142140 2014-06 CP-64 CP-140315 4994 2 Reconstruction of identity text 12.4.0 12.5.0 C1-142512 2014-06 CP-64 CP-140321 4995 1 Support of webrtc functional entities 12.4.0 12.5.0 C1-142333 2014-06 CP-64 CP-140322 4996 2 Clarification on description of Loose-Route indication 12.4.0 12.5.0 C1-142460 2014-06 CP-64 CP-140324 4997 2 Indicating II-NNI traversal scenario - REGISTER 12.4.0 12.5.0 C1-142412 2014-06 CP-64 CP-140322 4998 1 Correction on the value of transit-ioi parameter. 12.4.0 12.5.0 C1-142337 2014-06 CP-64 CP-140324 4999 1 Indicating the use case towards TRF 12.4.0 12.5.0 C1-142358 2014-06 CP-64 CP-140306 5002 EN removal: Feature-capability indicator IANA registration status 12.4.0 12.5.0 C1-142476 2014-09 CP-65 CP-140649 4844 2 SDP renegotiation not impacting TLS for BFCP 12.5.0 12.6.0 C1-143235 2014-09 CP-65 CP-140656 4895 6 Capability indication by P-CSCF 12.5.0 12.6.0 C1-143287 2014-09 CP-65 CP-140634 4949 3 Resolving interoperability problems caused by insufficiently documented UE precondition handling - alternative A 12.5.0 12.6.0 C1-143296 2014-09 CP-65 CP-140656 4956 3 Annex F : selection of the transport protocol by the P-CSCF 12.5.0 12.6.0 C1-143120 2014-09 CP-65 CP-140633 5012 1 Updating IMEI URN draft reference to RFC 7254 12.5.0 12.6.0 C1-143085 2014-09 CP-65 CP-140649 5013 Reference update: draft-ietf-mmusic-udptl-dtls 12.5.0 12.6.0 C1-142589 2014-09 CP-65 CP-140644 5015 EN removal: g.3gpp.icsi-ref feature-capability indicator IANA registration status 12.5.0 12.6.0 C1-142591 2014-09 CP-65 CP-140652 5016 2 History-Info anonymized in case of privacy 12.5.0 12.6.0 C1-143284 2014-09 CP-65 CP-140652 5017 1 History-Info optional header field parameters 12.5.0 12.6.0 C1-143232 2014-09 CP-65 CP-140652 5018 1 Updating references from RFC 4244 to RFC 7044 12.5.0 12.6.0 C1-143285 2014-09 CP-65 CP-140655 5019 WebRTC support of SCTP over DTLS 12.5.0 12.6.0 C1-142638 2014-09 CP-65 CP-140665 5020 3 Correction of P-CSCF 380 response message to triggering CS emergency calls 12.5.0 12.6.0 C1-143406 2014-09 CP-65 CP-140656 5021 1 Sync Failure during initial IMS registration 12.5.0 12.6.0 C1-143116 2014-09 CP-65 CP-140656 5022 1 Blocked Subsriber in S-CSCF 12.5.0 12.6.0 C1-143117 2014-09 CP-65 CP-140641 5025 1 ICE in IBCF 12.5.0 12.6.0 C1-143102 2014-09 CP-65 CP-140648 5026 1 IANA registration for permium rate tel URI parameter 12.5.0 12.6.0 C1-143204 2014-09 CP-65 CP-140658 5027 Reference update: draft-holmberg-dispatch-iotl 12.5.0 12.6.0 C1-142705 2014-09 CP-65 CP-140660 5028 4 Including IMSI in terminating INVITE for P-CSCF restoration 12.5.0 12.6.0 C1-143393 2014-09 CP-65 CP-140656 5029 2 Replacing tel URI after ENUM lookup clarification 12.5.0 12.6.0 C1-143288 2014-09 CP-65 CP-140658 5030 2 Identifying roaming architecture for voice over IMS with local breakout 12.5.0 12.6.0 C1-143282 2014-09 CP-65 CP-140658 5031 2 II-NNI traversal scenario - General 12.5.0 12.6.0 C1-143283 2014-09 CP-65 CP-140658 5032 1 Adding II-NNI traversal scenario by BGCF 12.5.0 12.6.0 C1-143227 2014-09 CP-65 CP-140658 5033 1 Indicatiing II-NNI traversal scenario in transit cases 12.5.0 12.6.0 C1-143228 2014-09 CP-65 CP-140658 5034 1 Using the "iotl" parameter in IBCF 12.5.0 12.6.0 C1-143229 2014-09 CP-65 CP-140655 5036 1 Reference update: draft-ietf-mmusic-sctp-sdp 12.5.0 12.6.0 C1-143215 2014-09 CP-65 CP-140646 5037 P-Preferred Identity reference correction 12.5.0 12.6.0 C1-142822 2014-09 CP-65 CP-140648 5038 2 Identifying when to translate a premium number in IBCF 12.5.0 12.6.0 C1-143278 2014-09 CP-65 CP-140660 5039 3 HSS based P-CSCF restoration procedures 12.5.0 12.6.0 C1-143391 2014-09 CP-65 CP-140660 5040 2 IBCF detecting a non-working P-CSCF for HSS based solution 12.5.0 12.6.0 C1-143381 2014-09 CP-65 CP-140656 5041 1 Correction of C1-142367, SUBSCRIBE race case 12.5.0 12.6.0 C1-143124 2014-09 CP-65 CP-140656 5042 4 Transit IOI handling towards an AS 12.5.0 12.6.0 C1-143394 2014-09 CP-65 CP-140658 5043 Trust domain for iotl parameter 12.5.0 12.6.0 C1-142871 2014-09 CP-65 CP-140665 5044 2 Support of additional Reason header field containing information about bearer loss 12.5.0 12.6.0 C1-143335 2014-09 CP-65 CP-140665 5045 1 Creation of new protocol values within the Reason header field 12.5.0 12.6.0 C1-143017 2014-09 CP-65 CP-140665 5046 2 Adjustment of I-WLAN support from release 12 12.5.0 12.6.0 C1-143401 2014-09 CP-65 CP-140656 5047 Correction of transit-ioi handling at S-CSCF 12.5.0 12.6.0 C1-142881 2014-09 CP-65 CP-140654 5050 Telepresence annex A corrections 12.5.0 12.6.0 C1-142944 2014-09 CP-65 CP-140656 5052 1 Annex A – Correction of 380 response major capability 12.5.0 12.6.0 C1-143126 2014-09 CP-65 CP-140681 4932 7 AS determination of used registration 12.5.0 12.6.0 - 2014-12 CP-66 CP-140839 4698 7 Major Capabilities for Business Trunking 12.6.0 12.7.0 C1-144967 2014-12 CP-66 CP-140831 4955 12 Adding an option enabling P-CSCF to send 380 response triggering CS EMERGENCY SETUP to default PSAP 12.6.0 12.7.0 C1-145053 2014-12 CP-66 CP-140831 4983 5 Inclusion of "precondition" option-tag in messages sent by MT UE 12.6.0 12.7.0 C1-144006 2014-12 CP-66 CP-140829 5055 Reference update: RFC 7345 (draft-ietf-mmusic-udptl-dtls) 12.6.0 12.7.0 C1-143413 2014-12 CP-66 CP-140823 5057 1 Reference Update: RFC7315 12.6.0 12.7.0 C1-143983 2014-12 CP-66 CP-140831 5061 3 Replacing draft-kaplan-insipid-session-id with draft-ietf-insipid-session-id 12.6.0 12.7.0 C1-144331 2014-12 CP-66 CP-140831 5063 1 Correcting for termination of received-transit-ioi 12.6.0 12.7.0 C1-143995 2014-12 CP-66 CP-140831 5065 2 Including Transit IOI exchange cases for visited network 12.6.0 12.7.0 C1-144244 2014-12 CP-66 CP-140831 5066 4 Corrections of handling P-Charging-Vector for NOTIFY method 12.6.0 12.7.0 C1-144973 2014-12 CP-66 CP-140831 5068 1 Clarification of handling icid-value of P-Charging-Vector header 12.6.0 12.7.0 C1-143999 2014-12 CP-66 CP-140831 5069 1 Correction about handling icid-value at TRF 12.6.0 12.7.0 C1-144000 2014-12 CP-66 CP-140816 5074 1 Reference update from draft-vanelburg-dispatch-private-network-ind to RFC 7316 12.6.0 12.7.0 C1-143965 2014-12 CP-66 CP-140849 5075 5 Support of altc 12.6.0 12.7.0 C1-144373 2014-12 CP-66 CP-140826 5078 2 Editor's note on ICSI usage 12.6.0 12.7.0 C1-144772 2014-12 CP-66 CP-140841 5080 3 Alt2 Including IMSI in terminating INVITE for P-CSCF restoration 12.6.0 12.7.0 C1-144238 2014-12 CP-66 CP-140831 5082 1 Response of terminating UE to SDP offer including incapable media streams 12.6.0 12.7.0 C1-144005 2014-12 CP-66 CP-140865 5088 1 ICE for TCP in P-CSCF 12.6.0 12.7.0 C1-144096 2014-12 CP-66 CP-140839 5089 Clarifying how to identify a private network 12.6.0 12.7.0 C1-143663 2014-12 CP-66 CP-140852 5090 5 The "iotl" SIP URI parameter included in the destination used for charging 12.6.0 12.7.0 C1-144995 2014-12 CP-66 CP-140852 5091 2 Aligning the list of conditions 12.6.0 12.7.0 C1-144194 2014-12 CP-66 CP-140852 5093 2 Removing an editor's note in BGCF 12.6.0 12.7.0 C1-144241 2014-12 CP-66 CP-140852 5094 Identifying further II-NNI traversal scenarios 12.6.0 12.7.0 C1-143681 2014-12 CP-66 CP-140837 5095 5 S-CSCF action when timer reg-await-auth is still running 12.6.0 12.7.0 C1-145001 2014-12 CP-66 CP-140831 5100 2 Correcting match conditions in 5.4.3.3 12.6.0 12.7.0 C1-144757 2014-12 CP-66 CP-140826 5104 1 EN: combination of emergency call types 12.6.0 12.7.0 C1-143993 2014-12 CP-66 CP-140837 5105 1 P-Charging-Function-Addresses only to P-CSCF in own network 12.6.0 12.7.0 C1-144141 2014-12 CP-66 CP-140865 5106 5 procedures using AKAv2 for WebRTC 12.6.0 12.7.0 C1-145047 2014-12 CP-66 CP-140841 5109 1 PCO list handling in P-CSCF restoration 12.6.0 12.7.0 C1-144121 2014-12 CP-66 CP-140845 5110 1 Correction of definitions 12.6.0 12.7.0 C1-144086 2014-12 CP-66 CP-140831 5112 Reference to tables from text 12.6.0 12.7.0 C1-143822 2014-12 CP-66 CP-140831 5113 2 Description of relaying charging parameters in subclause 4.5 12.6.0 12.7.0 C1-144282 2014-12 CP-66 CP-140831 5114 5 Definition of relayed charging parameters 12.6.0 12.7.0 C1-145056 2014-12 CP-66 CP-140841 5115 8 HSS-based P-CSCF restoration: S-CSCF procedures 12.6.0 12.7.0 C1-144997 2014-12 CP-66 CP-140841 5116 4 P-CSCF restoration: Annex A additions 12.6.0 12.7.0 C1-144375 2014-12 CP-66 CP-140841 5117 2 HSS based P-CSCF restoration: IBCF detecting non-working P-CSCF 12.6.0 12.7.0 C1-144199 2014-12 CP-66 CP-140841 5118 1 HSS based P-CSCF restoration; P-CSCF has restarted 12.6.0 12.7.0 C1-144130 2014-12 CP-66 CP-140831 5119 1 Clarifications for AS determines used registration 12.6.0 12.7.0 C1-144142 2014-12 CP-66 CP-140865 5120 5 The definition of WAF id and the related procedures 12.6.0 12.7.0 C1-144888 2014-12 CP-66 CP-140848 5121 3 NAT traversal for ETSI E2NA 12.6.0 12.7.0 C1-144878 2014-12 CP-66 CP-140852 5122 Reference update: draft-holmberg-dispatch-iotl 12.6.0 12.7.0 C1-144296 2014-12 CP-66 CP-140828 5128 Reference update: SIP overload control 12.6.0 12.7.0 C1-144304 2014-12 CP-66 CP-140831 5129 1 Minor corrections for phone-context 12.6.0 12.7.0 C1-144776 2014-12 CP-66 CP-140831 5130 RFC7044 reference correction 12.6.0 12.7.0 C1-144318 2014-12 CP-66 CP-140831 5132 1 Definition of type of emergency service 12.6.0 12.7.0 C1-144777 2014-12 CP-66 CP-140852 5133 1 Correction of confusing note 12.6.0 12.7.0 C1-144969 2014-12 CP-66 CP-140841 5134 3 Adding Restoration text to clause 4. 12.6.0 12.7.0 C1-144996 2014-12 CP-66 CP-140837 5135 Clarification of text on determination of originating or terminating case. 12.6.0 12.7.0 C1-144376 2014-12 CP-66 CP-140831 5138 1 Correcting E-CSCF P-Charging-Vector handling for SUBSCRIBE from LRF 12.6.0 12.7.0 C1-144794 2014-12 CP-66 CP-140831 5139 1 Clarification on IOI between a P-CSCF and an E-CSCF 12.6.0 12.7.0 C1-144795 2014-12 CP-66 CP-140852 5140 1 Updated proxy capability to include also I-CSCF 12.6.0 12.7.0 C1-144882 2014-12 CP-66 CP-140837 5141 1 Clarification of the use of transit-ioi 12.6.0 12.7.0 C1-144784 2014-12 CP-66 CP-140838 5152 2 Movement of material in annex U to an access specific annex 12.6.0 12.7.0 C1-145048 2014-12 CP-66 CP-140856 5153 Support of network-initiated USSD operations in profile tables 12.6.0 12.7.0 C1-144554 2014-12 CP-66 CP-140837 5154 Removal of I-WLAN as IP-CAN 12.6.0 12.7.0 C1-144557 2014-12 CP-66 CP-140866 5157 1 3gpp_mtsi_app_adapt SDP attribute 12.6.0 12.7.0 C1-144899 2014-12 CP-66 CP-140837 5162 Make the "utran-sai-3gpp" parameter optional 12.6.0 12.7.0 C1-144951 2014-12 CP-66 CP-140860 5062 2 Reducing likelihood of ghost calls when precondition is not used, the terminating UE does not have resources available and IP-CAN performs network-initiated resource reservation for the terminating UE 12.7.0 13.0.0 C1-144898 2014-12 CP-66 CP-140857 5076 P-CSCF discovery using signalling for access to EPC via WLAN connected using S2a and S2b 12.7.0 13.0.0 C1-143589 2014-12 CP-66 CP-140861 5131 1 new cause-param value for service number translation 12.7.0 13.0.0 C1-144896 2014-12 CP-66 CP-140860 5136 1 No bandwidth information when port is zero 12.7.0 13.0.0 C1-144793 2014-12 CP-66 CP-140859 5148 1 Paging policy differentiation 12.7.0 13.0.0 C1-144897 2015-03 CP-67 CP-150082 4125 3 Hosted NAT traversal for MSRP media flows 13.0.0 13.1.0 C1-150791 2015-03 CP-67 CP-150079 4466 12 Determination of host part of SIP URI used in Request-URI when representing telephone numbers as SIP URIs 13.0.0 13.1.0 C1-150584 2015-03 CP-67 CP-150079 5035 6 Insertion of "operator-specific-GI" in PANI by the AS 13.0.0 13.1.0 C1-150785 2015-03 CP-67 CP-150082 5108 6 Reference to FQDN 13.0.0 13.1.0 C1-150342 2015-03 CP-67 CP-150079 5164 3 phone-context setting 13.0.0 13.1.0 C1-150897 2015-03 CP-67 CP-150176 5165 3 P-Early-Media & Preconditions interaction clarification 13.0.0 13.1.0 - 2015-03 CP-67 CP-150079 5167 2 Mapping between cell-id and Geolocation Identifier 13.0.0 13.1.0 C1-150789 2015-03 CP-67 CP-150082 5168 3 Not acquiring P-CSCF addresses when UE communicates with IM CN subsystem and handover between IP-CANs occurs 13.0.0 13.1.0 C1-150793 2015-03 CP-67 CP-150060 5178 3 Correction to attribute "a=inactive" in initial INVITE 13.0.0 13.1.0 C1-150740 2015-03 CP-67 CP-150050 5184 Reference update for UUSIW 13.0.0 13.1.0 C1-150110 2015-03 CP-67 CP-150058 5186 Abbreviations for eMEDIASEC-CT requirements 13.0.0 13.1.0 C1-150112 2015-03 CP-67 CP-150079 5187 Correction of reference identifier for RFC 6026 13.0.0 13.1.0 C1-150113 2015-03 CP-67 CP-150082 5188 1 TWAN Release Cause 13.0.0 13.1.0 C1-150591 2015-03 CP-67 CP-150074 5190 Reference update: draft-holmberg-dispatch-iotl 13.0.0 13.1.0 C1-150119 2015-03 CP-67 CP-150060 5192 Reference update: draft-holmberg-sipcore-received-realm 13.0.0 13.1.0 C1-150123 2015-03 CP-67 CP-150053 5195 Reference update: RFC 7135 (was draft-polk-local-emergency-rph-namespace 13.0.0 13.1.0 C1-150126 2015-03 CP-67 CP-150060 5197 1 Reference update: draft-ietf-insipid-session-id 13.0.0 13.1.0 C1-150554 2015-03 CP-67 CP-150072 5199 IMS WebRTC reference updates 13.0.0 13.1.0 C1-150133 2015-03 CP-67 CP-150074 5201 Correction of syntax and description with regards to the iotl SIP URI parameter 13.0.0 13.1.0 C1-150171 2015-03 CP-67 CP-150060 5203 1 Correcting P-Charging-Vector for target refresh request on P-CSCF 13.0.0 13.1.0 C1-150556 2015-03 CP-67 CP-150175 5215 3 Correction of P-Charging-Vector access-network-charging-info syntax – Alt 2 13.0.0 13.1.0 - 2015-03 CP-67 CP-150044 5221 1 Handling of P-Charging-Function-Addresses 13.0.0 13.1.0 C1-150540 2015-03 CP-67 CP-150060 5223 1 "utran-sai-id-3gpp" vs ""utran-sai- 3gpp" 13.0.0 13.1.0 C1-150550 2015-03 CP-67 CP-150063 5225 2 PS_TO_CS_HANDOVER AVP in P-CSCF 13.0.0 13.1.0 C1-150778 2015-03 CP-67 CP-150084 5226 Resource sharing – Definitions 13.0.0 13.1.0 C1-150234 2015-03 CP-67 CP-150084 5227 2 Resource sharing – General part 13.0.0 13.1.0 C1-150725 2015-03 CP-67 CP-150084 5228 2 Resource sharing – Resource-Share header field 13.0.0 13.1.0 C1-150782 2015-03 CP-67 CP-150084 5229 1 Resource sharing – P-CSCF procedures 13.0.0 13.1.0 C1-150688 2015-03 CP-67 CP-150084 5231 1 Resource sharing – AS procedure 13.0.0 13.1.0 C1-150689 2015-03 CP-67 CP-150067 5233 3 Update REFER to reflect RFC 6665 13.0.0 13.1.0 C1-150875 2015-03 CP-67 CP-150066 5241 2 Clause 4 improvements: restoration procedures. 13.0.0 13.1.0 C1-150824 2015-03 CP-67 CP-150066 5243 2 Applicability statement improvement for the Restoration-Info 13.0.0 13.1.0 C1-150774 2015-03 CP-67 CP-150066 5245 2 P-CSCF restoration: Restoration-Info Annex A corrections 13.0.0 13.1.0 C1-150776 2015-03 CP-67 CP-150060 5247 1 Relayed-Charge header field in Annex A 13.0.0 13.1.0 C1-150558 2015-03 CP-67 CP-150060 5249 1 Addition of transit function to profile tables 13.0.0 13.1.0 C1-150560 2015-03 CP-67 CP-150082 5250 1 P-CSCF restoration name alignment 13.0.0 13.1.0 C1-150596 2015-03 CP-67 CP-150060 5252 2 Revisions to definition of Relayed-Charge header field 13.0.0 13.1.0 C1-150708 2015-03 CP-67 CP-150079 5255 Chargiong related definitions 13.0.0 13.1.0 C1-150316 2015-03 CP-67 CP-150082 5256 1 Addition of missing word SIP parameters in general description of trust domain 13.0.0 13.1.0 C1-150599 2015-03 CP-67 CP-150079 5258 1 Clarification of IOI between a P-CSCF and an E-CSCF on request from a user with/without emergency registration 13.0.0 13.1.0 C1-150574 2015-03 CP-67 CP-150080 5260 Reference update: draft-mohali-dispatch-cause-for-service-number 13.0.0 13.1.0 C1-150393 2015-06 CP-68 CP-150324 5163 6 Closure of TCP connections 13.1.0 13.2.0 C1-151649 2015-06 CP-68 CP-150328 5166 7 Determination of the registration duration by the S-CSCF 13.1.0 13.2.0 C1-152280 2015-06 CP-68 CP-150324 5169 3 Precondition and swap of 200 for UPDATE and 180/200 for INVITE 13.1.0 13.2.0 C1-151445 2015-06 CP-68 CP-150324 5175 5 Correcting undesired consequences of 503 response in P-CSCF terminating call handling 13.1.0 13.2.0 C1-151595 2015-06 CP-68 CP-150324 5176 8 Correcting IBCF hiding of the Service Route procedure 13.1.0 13.2.0 C1-151795 2015-06 CP-68 CP-150324 5264 4 New header field for dynamic service interaction 13.1.0 13.2.0 C1-151651 2015-06 CP-68 CP-150287 5270 1 Reference Update: RFC7462 (alert-info urns) 13.1.0 13.2.0 C1-151400 2015-06 CP-68 CP-150297 5276 1 Clarifying condition for not routeing via S-CSCF for an emergency call 13.1.0 13.2.0 C1-151439 2015-06 CP-68 CP-150322 5277 2 Moving P-CSCF procedures to annex L 13.1.0 13.2.0 C1-151583 2015-06 CP-68 CP-150322 5278 1 Including resource sharing in annex A 13.1.0 13.2.0 C1-152150 2015-06 CP-68 CP-150322 5279 Removing S-CSCF impact 13.1.0 13.2.0 C1-150999 2015-06 CP-68 CP-150322 5280 2 Solving editor's note about INVITE without SDP offer 13.1.0 13.2.0 C1-151584 2015-06 CP-68 CP-150322 5281 1 Resource sharing per media stream in the AS 13.1.0 13.2.0 C1-151520 2015-06 CP-68 CP-150321 5282 4 P-CSCF priority order 13.1.0 13.2.0 C1-152149 2015-06 CP-68 CP-150322 5283 5 Resource sharing procedures and updated ABNF 13.1.0 13.2.0 C1-152269 2015-06 CP-68 CP-150324 5284 Removing MSC server enhanced for ICS from proxy major capabilities 13.1.0 13.2.0 C1-151008 2015-06 CP-68 CP-150324 5285 Defining an MSC server enhanced for SRVCC role in annex A 13.1.0 13.2.0 C1-151009 2015-06 CP-68 CP-150293 5290 1 Corrections to media plane security 13.1.0 13.2.0 C1-151428 2015-06 CP-68 CP-150324 5291 2 Correcting P-Charging-Vector for response to subsequent request on P-CSCF 13.1.0 13.2.0 C1-151590 2015-06 CP-68 CP-150324 5294 5 Correcting undesired consequences of 503 response in P-CSCF originating call handling 13.1.0 13.2.0 C1-152272 2015-06 CP-68 CP-150311 5302 Correction to Annex A table for p-cscf restoration 13.1.0 13.2.0 C1-151054 2015-06 CP-68 CP-150306 5305 1 IETF Update on IMS Telepresence 13.1.0 13.2.0 C1-151509 2015-06 CP-68 CP-150324 5313 Applying THIG on Path header field, using new Feature-capability indicator 13.1.0 13.2.0 C1-151165 2015-06 CP-68 CP-150294 5321 3 Update 3GPP2 referrence to reflect the correct published version 13.1.0 13.2.0 C1-151603 2015-06 CP-68 CP-150324 5322 1 Editorial change to eliminate confusion on UE supporting multiple registrations 13.1.0 13.2.0 C1-151449 2015-06 CP-68 CP-150324 5323 6 Expires in 3rd party REGISTER 13.1.0 13.2.0 C1-152496 2015-06 CP-68 CP-150324 5324 1 Correction Restoration-Info in Annex A 13.1.0 13.2.0 C1-151452 2015-06 CP-68 CP-150307 5326 Moving misplaced subclause 5.7.1.3B 13.1.0 13.2.0 C1-151230 2015-06 CP-68 CP-150300 5329 4 Translation of geo-local numbers 13.1.0 13.2.0 C1-152211 2015-06 CP-68 CP-150324 5330 2 Anonymous User Identity in the From header field 13.1.0 13.2.0 C1-151592 2015-06 CP-68 CP-150300 5334 3 Loopback indication in responses 13.1.0 13.2.0 C1-152263 2015-06 CP-68 CP-150321 5335 P-CSCF priority order text alignment 13.1.0 13.2.0 C1-151669 2015-06 CP-68 CP-150324 5336 Removal of redundant Via header from INVITE response table. 13.1.0 13.2.0 C1-151765 2015-06 CP-68 CP-150324 5338 1 Removal of redundant Require header from SUBSCRIBE 2xx response table. 13.1.0 13.2.0 C1-152225 2015-06 CP-68 CP-150292 5344 1 Modification of missing Allow-Events header field status in annex A 13.1.0 13.2.0 C1-152172 2015-06 CP-68 CP-150324 5345 1 Support of Expires header field in responses to PUBLISH request in annex A 13.1.0 13.2.0 C1-152226 2015-06 CP-68 CP-150328 5347 1 Aligning TLS profiles used by CT1 specifications with SA3 agreed TLS profile 13.1.0 13.2.0 C1-152230 2015-06 CP-68 CP-150324 5349 1 Correction of profile status of Contact header field in annex A 13.1.0 13.2.0 C1-152227 2015-06 CP-68 CP-150324 5350 Correcting profile status of WWW-Authenticate and Proxy-Authenticate header field in annex A 13.1.0 13.2.0 C1-151790 2015-06 CP-68 CP-150324 5351 1 Modification of prerequisites for CANCEL response in annex A 13.1.0 13.2.0 C1-152228 2015-06 CP-68 CP-150324 5352 2 Correction of status code for the PUBLISH response in annex A 13.1.0 13.2.0 C1-152285 2015-06 CP-68 CP-150328 5353 1 UE accessing IM CN subsystem using PDP context provided by SGSN connected to S-GW and P-GW 13.1.0 13.2.0 C1-152060 2015-06 CP-68 CP-150328 5354 Not acquiring P-CSCF addresses when UE communicates with IM CN subsystem and handover to GPRS IP-CANs occurs 13.1.0 13.2.0 C1-151806 2015-06 CP-68 CP-150324 5355 2 Correcting undesired consequences of 503 response in MGCF handling 13.1.0 13.2.0 C1-152273 2015-06 CP-68 CP-150324 5364 2 Annex A status correction of Record-Route 13.1.0 13.2.0 C1-152274 2015-06 CP-68 CP-150324 5365 Annex A status correction of Supported header field 13.1.0 13.2.0 C1-151824 2015-06 CP-68 CP-150324 5366 1 Annex A status correction of Server header field 13.1.0 13.2.0 C1-152235 2015-06 CP-68 CP-150307 5368 Correction to P-Access-Network-Info 13.1.0 13.2.0 C1-151872 2015-06 CP-68 CP-150328 5369 Improvement of reference to S-CSCF restoration procedures 13.1.0 13.2.0 C1-151877 2015-06 CP-68 CP-150324 5370 1 Clarification on BSSID usage 13.1.0 13.2.0 C1-152240 2015-06 CP-68 CP-150318 5372 Reference update: RFC 7549 (draft-holmberg-dispatch-iotl) 13.1.0 13.2.0 C1-151906 2015-06 CP-68 CP-150324 5373 1 P-CSCF public user identity matching 13.1.0 13.2.0 C1-152246 2015-06 CP-68 CP-150289 5379 1 Content-Disposition for pidf+xml message bodies 13.1.0 13.2.0 C1-152161 2015-06 CP-68 CP-150324 5380 3 P-Early Media; Annex A corrections 13.1.0 13.2.0 C1-152295 2015-06 CP-68 CP-150307 5382 1 Corrections Relayed-Charge Annex A 13.1.0 13.2.0 C1-152221 2015-06 CP-68 CP-150307 5384 3 Relayed-charge clarifications 13.1.0 13.2.0 C1-152289 2015-06 CP-68 CP-150324 5385 1 Geographical Identifier insertion when TWAN is used 13.1.0 13.2.0 C1-152241 2015-06 CP-68 CP-150325 5386 3 Reference update: draft-mohali-dispatch-cause-for-service-number 13.1.0 13.2.0 C1-152497 2015-06 CP-68 CP-150325 5387 Service access number translation by an AS 13.1.0 13.2.0 C1-152006 2015-06 Post CT-68 Deletion of superfluous empty rows in tables of annex A 13.2.0 13.2.1 2015-09 CP-69 CP-150520 5303 5 S-CSCF stores AS IP address 13.2.1 13.3.0 C1-153039 2015-09 CP-69 CP-150520 5363 3 Annex A status correction of Record-Route for MESSAGE method 13.2.1 13.3.0 C1-152680 2015-09 CP-69 CP-150521 5388 Updated Reference: draft-mohali-dispatch-cause-for-service-number 13.2.1 13.3.0 C1-152519 2015-09 CP-69 CP-150521 5389 3 Service Access Number at terminating UE 13.2.1 13.3.0 C1-153271 2015-09 CP-69 CP-150530 5392 Incorrect reference to S-CSCF restoration procedures 13.2.1 13.3.0 C1-152569 2015-09 CP-69 CP-150535 5393 Resource sharing in CDMA2000 access 13.2.1 13.3.0 C1-152570 2015-09 CP-69 CP-150535 5394 Resolving the editor's notes about UE involvement 13.2.1 13.3.0 C1-152571 2015-09 CP-69 CP-150535 5395 Aligning the general description with the actual procedures 13.2.1 13.3.0 C1-152573 2015-09 CP-69 CP-150535 5396 Minor improvement of the P-CSCF resource sharing procedures 13.2.1 13.3.0 C1-152574 2015-09 CP-69 CP-150535 5397 Stop resource sharing when receiving a conflicting SDP offer 13.2.1 13.3.0 C1-152575 2015-09 CP-69 CP-150535 5398 P-CSCF indicating that resource sharing is no longer possible 13.2.1 13.3.0 C1-152576 2015-09 CP-69 CP-150535 5399 Updating resource sharing options 13.2.1 13.3.0 C1-152577 2015-09 CP-69 CP-150530 5400 1 Remove sending of 403 due to MAC address error 13.2.1 13.3.0 C1-153045 2015-09 CP-69 CP-150514 5402 1 SIP timer table update due to RFC 6665 – missing timer N added 13.2.1 13.3.0 C1-153024 2015-09 CP-69 CP-150533 5403 2 Support of Emergency services over WLAN access to EPC 13.2.1 13.3.0 C1-153217 2015-09 CP-69 CP-150530 5405 1 Domain selection for UE originating voice and SMS 13.2.1 13.3.0 C1-153046 2015-09 CP-69 CP-150530 5406 Correction for Route Header in REGISTER request 13.2.1 13.3.0 C1-152619 2015-09 CP-69 CP-150530 5410 1 Annex A: support of PANI in INVITE request by MGCF 13.2.1 13.3.0 C1-153035 2015-09 CP-69 CP-150504 5413 Reference update: RFC 7415 13.2.1 13.3.0 C1-152660 2015-09 CP-69 CP-150510 5415 1 Defining an "MSC server enhanced for DRVCC" role in annex A 13.2.1 13.3.0 C1-152735 2015-09 CP-69 CP-150530 5416 1 General principle of ICID and IOI 13.2.1 13.3.0 C1-153048 2015-09 CP-69 CP-150530 5417 1 Apply general principle of ICID and IOI to P-CSCF 13.2.1 13.3.0 C1-153049 2015-09 CP-69 CP-150530 5418 2 Apply general principle of ICID and IOI to S-CSCF 13.2.1 13.3.0 C1-153065 2015-09 CP-69 CP-150530 5419 2 Apply general principle of ICID and IOI to AS 13.2.1 13.3.0 C1-153066 2015-09 CP-69 CP-150530 5420 Apply general principle of ICID and IOI to I-CSCF. 13.2.1 13.3.0 C1-152670 2015-09 CP-69 CP-150530 5421 1 Apply general principle of ICID and IOI to MGCF 13.2.1 13.3.0 C1-153052 2015-09 CP-69 CP-150530 5422 Apply general principle of ICID and IOI to BGCF 13.2.1 13.3.0 C1-152672 2015-09 CP-69 CP-150530 5423 1 Apply general principle of ICID and IOI to IBCF 13.2.1 13.3.0 C1-153053 2015-09 CP-69 CP-150530 5424 Apply general principle of ICID and IOI to E-CSCF 13.2.1 13.3.0 C1-152674 2015-09 CP-69 CP-150530 5425 2 Apply general principle of ICID and IOI to ISC gateway function 13.2.1 13.3.0 C1-153067 2015-09 CP-69 CP-150530 5426 4 Apply general principle of ICID and IOI to TF and TRF 13.2.1 13.3.0 C1-153079 2015-09 CP-69 CP-150520 5427 Correction of profile status on Allow header field 13.2.1 13.3.0 C1-152677 2015-09 CP-69 CP-150520 5428 Profile status modification for P-Charging-Vector and Relayed-Charge in Annex A 13.2.1 13.3.0 C1-152679 2015-09 CP-69 CP-150586 5448 2 Support for Video Region-of-Interest (ROI) Signaling 13.2.1 13.3.0 - 2015-09 CP-69 CP-150513 5431 No-response value for Restoration-Info header field 13.2.1 13.3.0 C1-152716 2015-09 CP-69 CP-150520 5432 1 UE to perform reregistration on change of IPCAN 13.2.1 13.3.0 C1-153041 2015-09 CP-69 CP-150512 5434 Non-dialable callback number in PAI before LRF is invoked 13.2.1 13.3.0 C1-152720 2015-09 CP-69 CP-150520 5436 Correcting the spelling of "privilege" 13.2.1 13.3.0 C1-152795 2015-09 CP-69 CP-150520 5437 Correcting the Contact header field entry of PUBLISH in profile tables 13.2.1 13.3.0 C1-152796 2015-09 CP-69 CP-150520 5438 1 Corrections related to reg event XML 13.2.1 13.3.0 C1-153042 2015-09 CP-69 CP-150520 5439 1 Delete duplicated SHALL 13.2.1 13.3.0 C1-153043 2015-09 CP-69 CP-150520 5440 3 Missing Content-Type in Supported header field of CANCEL method 13.2.1 13.3.0 C1-153081 2015-09 CP-69 CP-150520 5441 EPC via WLAN - not reachable for SIP signalling upon loss of IP-CAN bearer for SIP signalling 13.2.1 13.3.0 C1-152847 2015-09 CP-69 CP-150530 5442 2 Supported Media Types 13.2.1 13.3.0 C1-153069 2015-09 CP-69 CP-150513 5444 IANA registration for Restoration-Info header field 13.2.1 13.3.0 C1-152877 2015-09 CP-69 CP-150508 5446 IANA registration for Relayed-Charge header field 13.2.1 13.3.0 C1-152879 2015-09 CP-69 CP-150520 5447 AS handling of expires=0 13.2.1 13.3.0 C1-152880 2015-09 CP-69 Correction of table numbering 13.3.0 13.3.1 2015-12 CP-70 CP-150699 5449 1 Updated Reference: draft-mohali-dispatch-cause-for-service-number 13.3.1 13.4.0 C1-153702 2015-12 CP-70 CP-150699 5450 1 service access number terminology definition 13.3.1 13.4.0 C1-153703 2015-12 CP-70 CP-150705 5452 1 Support for Video Region-of-Interest (ROI) Signaling 13.3.1 13.4.0 C1-153718 2015-12 CP-70 CP-150709 5453 1 Various editorial corrections 13.3.1 13.4.0 C1-153720 2015-12 CP-70 CP-150701 5454 1 P-CSCF restoration in Annex R 13.3.1 13.4.0 C1-154591 2015-12 CP-70 CP-150698 5457 Annex A - incorrect linkage to INFO request and INFO response 13.3.1 13.4.0 C1-153339 2015-12 CP-70 CP-150720 5458 Resource sharing in CDMA2000 access using EPC 13.3.1 13.4.0 C1-153366 2015-12 CP-70 CP-150709 5459 Cleanup of duplicate words 13.3.1 13.4.0 C1-153371 2015-12 CP-70 CP-150709 5460 Cleanup of table numbers in clause 4 13.3.1 13.4.0 C1-153372 2015-12 CP-70 CP-150872 5461 1 draft-gundavelli-ipsecme-3gpp-ims-options became RFC7651 13.3.1 13.4.0 - 2015-12 CP-70 CP-150698 5463 3 Missing Content-Type in Supported header field of CANCEL method in Table A.181 13.3.1 13.4.0 C1-154505 2015-12 CP-70 CP-150714 5464 2 Remove non-access technology specific requirement from access technology annex 13.3.1 13.4.0 C1-153979 2015-12 CP-70 CP-150714 5466 1 WLAN Location Information in support of emergency session 13.3.1 13.4.0 C1-153695 2015-12 CP-70 CP-150698 5468 MSC server roles 13.3.1 13.4.0 C1-153579 2015-12 CP-70 CP-150698 5470 3 Protocol values for SIP reason header field 13.3.1 13.4.0 C1-154502 2015-12 CP-70 CP-150685 5472 1 Protocol value for S1 protocol errors missing 13.3.1 13.4.0 C1-153726 2015-12 CP-70 CP-150698 5473 3 Updates on UE to perform reregistration on change of IPCAN 13.3.1 13.4.0 C1-153767 2015-12 CP-70 CP-150712 5474 3 Media Optimization for WebRTC – SDP syntax 13.3.1 13.4.0 C1-154516 2015-12 CP-70 CP-150689 5476 Removal of the IANA specific subclauses for headers 13.3.1 13.4.0 C1-153613 2015-12 CP-70 CP-150698 5477 Correct name of "network-provided" 13.3.1 13.4.0 C1-153615 2015-12 CP-70 CP-150689 5479 2 P-CSCF restoration corrections 13.3.1 13.4.0 C1-154534 2015-12 CP-70 CP-150698 5480 Removing confusing inactive statement 13.3.1 13.4.0 C1-153620 2015-12 CP-70 CP-150690 5482 1 Update RFC 6665 related references to RFC 7614, RFC 7621 and RFC 7647 13.3.1 13.4.0 C1-153747 2015-12 CP-70 CP-150680 5485 2 P-Access-Network-Info ABNF Update 13.3.1 13.4.0 C1-154597 2015-12 CP-70 CP-150693 5487 1 JSON Web Token Claims for transport of WAF and WWSF identities 13.3.1 13.4.0 C1-154530 2015-12 CP-70 CP-150880 5493 2 Call modification: removing mandatory usage of the preconditions mechanism 13.3.1 13.4.0 - 2015-12 CP-70 CP-150693 5495 Reference update: RFC 7675 (draft-ietf-rtcweb-stun-consent-freshness) 13.3.1 13.4.0 C1-154030 2015-12 CP-70 CP-150684 5497 Reference update: draft-ietf-mmusic-sctp-sdp 13.3.1 13.4.0 C1-154048 2015-12 CP-70 CP-150715 5498 MCPTT: SDP Considerations 13.3.1 13.4.0 C1-154051 2015-12 CP-70 CP-150718 5499 1 Support of RTP / RTCP transport multiplexing in IMS call control signalling 13.3.1 13.4.0 C1-154581 2015-12 CP-70 CP-150720 5500 1 Correct AS and S-CSCF for resource sharing 13.3.1 13.4.0 C1-154500 2015-12 CP-70 CP-150717 5501 Paging Policy Differentiation, complete TCP cases 13.3.1 13.4.0 C1-154127 2015-12 CP-70 CP-150712 5502 1 Negotiation of contents of data channels (MSRP) – Annex A 13.3.1 13.4.0 C1-154515 2015-12 CP-70 CP-150698 5503 1 Determination of used registration – standalone request 13.3.1 13.4.0 C1-154501 2015-12 CP-70 CP-150681 5506 1 Adding the loopback-indication in subsequent requests 13.3.1 13.4.0 C1-154570 2015-12 CP-70 CP-150681 5511 1 Loopback indication in Responses 13.3.1 13.4.0 C1-154567 2015-12 CP-70 CP-150712 5512 1 Media Optimization for WebRTC – Optional Procedures for intermediate nodes 13.3.1 13.4.0 C1-154518 2015-12 CP-70 CP-150709 5513 Cleanup of duplicate words-2 13.3.1 13.4.0 C1-154168 2015-12 CP-70 CP-150709 5514 Reference correction in Table A.3 13.3.1 13.4.0 C1-154172 2015-12 CP-70 CP-150709 5515 1 Reference correction for IBCF performing media transcoding control 13.3.1 13.4.0 C1-154519 2015-12 CP-70 CP-150709 5516 Normative word in normal notes 13.3.1 13.4.0 C1-154174 2015-12 CP-70 CP-150677 5522 Call modification: UE shall not indicate the requirement for the precondition mechanism by using the Require header field mechanism. 13.3.1 13.4.0 C1-154234 2015-12 CP-70 CP-150708 5524 2 New access type value for ProSe UE-to-Network Relay 13.3.1 13.4.0 C1-154457 2015-12 CP-70 CP-150699 5526 1 Service access number scope 13.3.1 13.4.0 C1-154506 2015-12 CP-70 CP-150709 5527 3 Handling of failure responses by the UE during call setup 13.3.1 13.4.0 C1-154881 2015-12 CP-70 CP-150698 5528 2 Correcting ambiguity when a list of UE actions are specified 13.3.1 13.4.0 C1-154720 2015-12 CP-70 CP-150698 5529 1 Update condition c22 of Content-Type in Supported header field of CANCEL method in Table A.23 13.3.1 13.4.0 C1-154504 2015-12 CP-70 CP-150698 5530 Correct description of P-CSCF restoration 13.3.1 13.4.0 C1-154395 2016-03 CP-71 CP-160136 5361 10 Coding of Type 1 IOIs and of Type 3 IOIs 13.4.0 13.5.0 C1-161541 2016-03 CP-71 CP-160083 5467 6 Addition of UE Provided Location Information for Untrusted WLAN access 13.4.0 13.5.0 C1-160941 2016-03 CP-71 CP-160082 5523 5 Align terms with definitions in TS 24.302 and reword untestable conditions when accessing IM CN subsystem via WLAN IP access 13.4.0 13.5.0 C1-161539 2016-03 CP-71 CP-160136 5532 2 Usage of the contact address previously registered 13.4.0 13.5.0 C1-160494 2016-03 CP-71 CP-160136 5536 2 JSON Web Token Claims for transport of WAF and WWSF identities: missing note 13.4.0 13.5.0 C1-160495 2016-03 CP-71 CP-160136 5537 1 P-Access-Network-Info ABNF Update 13.4.0 13.5.0 C1-160444 2016-03 CP-71 CP-160136 5538 4 MGCF call modification: removing mandatory usage of the preconditions mechanism 13.4.0 13.5.0 C1-161354 2016-03 CP-71 CP-160076 5539 MCPTT: Removal of SDP considerations 13.4.0 13.5.0 C1-160078 2016-03 CP-71 CP-160066 5542 Correction of the incorrect referenced subclause number. 13.4.0 13.5.0 C1-160155 2016-03 CP-71 CP-160064 5548 2 MGCF call initiation: removing posibility for using require header field in preconditions 13.4.0 13.5.0 C1-160487 2016-03 CP-71 CP-160136 5549 1 UE session modification clarification 13.4.0 13.5.0 C1-160447 2016-03 CP-71 CP-160074 5550 1 Profile table for media plane optimization webrtc attributes 13.4.0 13.5.0 C1-160450 2016-03 CP-71 CP-160136 5551 1 Reg-token in case of no registration 13.4.0 13.5.0 C1-160448 2016-03 CP-71 CP-160136 5552 IANA registration part for Service Interact-Info 13.4.0 13.5.0 C1-160224 2016-03 CP-71 CP-160074 5553 Update reference for draft-ietf-mmusic-data-channel-sdpneg 13.4.0 13.5.0 C1-160229 2016-03 CP-71 CP-160136 5562 4 Clarification of emergency registration handling 13.4.0 13.5.0 C1-160618 2016-03 CP-71 CP-160081 5563 Support for Video Region-of-Interest (ROI) Signaling 13.4.0 13.5.0 C1-160336 2016-03 CP-71 CP-160080 5564 1 Support of enhanced bandwidth negotiation mechanism for MTSI sessions 13.4.0 13.5.0 C1-161333 2016-03 CP-71 CP-160080 5565 Support of enhanced bandwidth negotiation mechanism by MTSI UE 13.4.0 13.5.0 C1-160819 2016-03 CP-71 CP-160083 5568 Network-provided PANI when a UE accesses IMS from general Internet using S2b 13.4.0 13.5.0 C1-160855 2016-03 CP-71 CP-160138 5569 2 P-Access-Network-Info header field in retransmitted SIP messages 13.4.0 13.5.0 - 2016-03 CP-71 CP-160136 5570 1 Precondition option tag in responses within a dialog other than INVITE responses 13.4.0 13.5.0 C1-161383 2016-03 CP-71 CP-160136 5571 1 Clarification of base-time description 13.4.0 13.5.0 C1-161502 2016-03 CP-71 CP-160136 5577 2 Restriction on requesting early media authorization from UE 13.4.0 13.5.0 C1-161506 2016-03 CP-71 Editorial corrections 13.5.0 13.5.1 2016-06 CP-72 CP-160317 5561 8 Handling of 380 in Annex R 13.5.1 13.6.0 C1-161953 2016-06 CP-72 CP-160317 5580 2 Corrections for PSAP callback after emergency session via untrusted WLAN 13.5.1 13.6.0 C1-162307 2016-06 CP-72 CP-160317 5581 3 Corrections for the "VIRTUAL" access type 13.5.1 13.6.0 C1-162982 2016-06 CP-72 CP-160298 5584 1 orig-cdiv session case definition from draft-mohali-dispatch-originating-cdiv-parameter-01 13.5.1 13.6.0 C1-162093 2016-06 CP-72 CP-160317 5591 2 Corrections to Cellular-Network-Info handling 13.5.1 13.6.0 C1-162507 2016-06 CP-72 CP-160298 5596 2 Updates to RFC 7315 P-header extensions usage in SIP requests/responses 13.5.1 13.6.0 C1-162471 2016-06 CP-72 CP-160314 5597 Enhanced bandwidth negotiation clarification 13.5.1 13.6.0 C1-161769 2016-06 CP-72 CP-160320 5598 Correct name of "np" header field parameter 13.5.1 13.6.0 C1-161770 2016-06 CP-72 CP-160320 5601 P-Charging-Vector header in CANCEL request and responses 13.5.1 13.6.0 C1-161773 2016-06 CP-72 CP-160322 5613 1 Uppdating annex A with MIME bodies 13.5.1 13.6.0 C1-162779 2016-06 CP-72 CP-160320 5617 2 SDP offer/answer for TLS and DTLS protected media 13.5.1 13.6.0 C1-163122 2016-06 CP-72 CP-160322 5623 1 Adding draft-holmberg-dispatch-mcptt-rp-namespace to annex A 13.5.1 13.6.0 C1-163008 2016-06 CP-72 CP-160298 5626 1 Reference update: draft-holmberg-dispatch-pani-abnf 13.5.1 13.6.0 C1-162864 2016-06 CP-72 CP-160311 5636 Corrections of errors in PANI and CNI 13.5.1 13.6.0 C1-162584 2016-06 CP-72 CP-160321 5585 Service access number draft update 13.5.1 13.6.0 C1-161619 2016-06 CP-72 CP-160328 5566 4 Coding of the user part in the contact address 13.6.0 14.0.0 C1-162075 2016-06 CP-72 CP-160332 5567 3 Correcting statements on early media conflicting with TS 24.628 13.6.0 14.0.0 C1-162076 2016-06 CP-72 CP-160328 5599 2 P-Access-Network-Info header in ACK request 13.6.0 14.0.0 C1-162281 2016-06 CP-72 CP-160328 5600 2 P-Charging-Vector header in ACK request 13.6.0 14.0.0 C1-162282 2016-06 CP-72 CP-160328 5607 5 Clarifications of call setup and session modifications using preconditions 13.6.0 14.0.0 C1-163038 2016-06 CP-72 CP-160328 5608 1 Resource-Priority description minor correction 13.6.0 14.0.0 C1-162074 2016-06 CP-72 CP-160326 5609 6 Addition of eCall URNs 13.6.0 14.0.0 C1-163032 2016-06 CP-72 CP-160328 5612 2 Indication of release cause 13.6.0 14.0.0 C1-163036 2016-06 CP-72 CP-160332 5615 1 Mandatory support of RTP/RTCP multiplexing 13.6.0 14.0.0 C1-162876 2016-06 CP-72 CP-160328 5630 1 Request forwarding in IBCF 13.6.0 14.0.0 C1-162881 2016-06 CP-72 CP-160326 5631 4 MSD transfer for eCall over IMS 13.6.0 14.0.0 C1-163060 2016-06 CP-72 CP-160328 5632 3 Handling of 488 response with 301 warn-code in network 13.6.0 14.0.0 C1-163150 2016-06 CP-72 CP-160328 5639 1 Clarifications of QoS attributes during session modifications 13.6.0 14.0.0 C1-162886 2016-06 CP-72 CP-160329 5634 1 Media type restriction policy enforcement 13.6.0 14.0.0 C1-162941 2016-06 Editorial fixes 14.0.0 14.0.1 Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2016-09 CT#73 CP-160495 5641 4 A Introducing priority sharing 14.1.0 2016-09 CT#73 CP-160515 5642 4 B Default EPS bearer context usage restriction policy 14.1.0 2016-09 CT#73 CP-160509 5644 A Missing parameters for lawful interception of calls established over untrusted non-3GPP access connected to EPC 14.1.0 2016-09 CT#73 CP-160514 5645 F Handling re-INVITE request collisions in application servers 14.1.0 2016-09 CT#73 CP-160518 5648 1 F Correction of reference to Ix interface 14.1.0 2016-09 CT#73 CP-160518 5649 F Correction of referenced specification for Ix interface 14.1.0 2016-09 CT#73 CP-160508 5652 A Updated ref to draft-mohali-dispatch-cause-for-service-number-07 14.1.0 2016-09 CT#73 CP-160483 5662 1 A P-CSCF includes access-network-charging-info in reliable response 14.1.0 2016-09 CT#73 CP-160517 5663 3 B Phase 2 support of Emergency services over WLAN 14.1.0 2016-09 CT#73 CP-160514 5665 F Trust Domain issues 14.1.0 2016-09 CT#73 CP-160490 5667 1 A Registration-token in 3rd party REGISTER 14.1.0 2016-09 CT#73 CP-160515 5668 2 C Support of Media_type_restirction_policy only conditional 14.1.0 2016-09 CT#73 CP-160514 5669 1 F Error in Table A.4 for Resource-Priority 14.1.0 2016-09 CT#73 CP-160514 5670 F Reference for CNI header 14.1.0 2016-09 CT#73 CP-160518 5671 F Related ICID also for DRVCC 14.1.0 2016-09 CT#73 CP-160512 5672 1 C Update of eCall over IMS procedures 14.1.0 2016-09 CT#73 CP-160514 5673 F Correct terminology access-type access-class fields 14.1.0 2016-09 CT#73 CP-160514 5674 1 F Corrections to resource sharing 14.1.0 2016-09 CT#73 CP-160514 5678 F Correct reference for codec insertion 14.1.0 2016-09 CT#73 CP-160483 5685 1 A Correction on support of P-Asserted-Identity header 14.1.0 2016-09 CT#73 CP-160484 5696 A Reference update: RFC 7913 14.1.0 2016-09 CT#73 CP-160509 5698 1 A Correction on support of Cellular-Network-Info header 14.1.0 2016-09 CT#73 CP-160514 5699 1 F Correcting reference for DTLS-SRTP in annex A 14.1.0 2016-09 CT#73 CP-160518 5701 1 F Reference update draft-ietf-mmusic-mux-exclusive 24.229 14.1.0 2016-09 CT#73 CP-160521 5702 1 B Enable usage P-Visited-Network-ID header for S8HR 14.1.0 2016-12 CT#74 CP-160752 5650 3 B Clarification on SDP offer answer for transcoding 14.2.0 2016-12 CT#74 CP-160752 5653 4 B Registration timeout for emergency call 14.2.0 2016-12 CT#74 CP-160752 5655 6 F Emergency call retry in CS domain 14.2.0 2016-12 CT#74 CP-160708 5692 2 A Correction on support of P-Asserted-Service header 14.2.0 2016-12 CT#74 CP-160742 5704 6 B Send Reliable 18x 14.2.0 2016-12 CT#74 CP-160741 5705 F Incomplete sentence 14.2.0 2016-12 CT#74 CP-160742 5706 1 B Enforcement of policy on PDN connection established during EPS attach procedure 14.2.0 2016-12 CT#74 CP-160798 5707 5 B Providing the current UE location during emergency call 14.2.0 2016-12 CT#74 CP-160739 5709 F MGW rejecting eCall over IMS 14.2.0 2016-12 CT#74 CP-160742 5710 4 B Enforcement of precondition usage policy 14.2.0 2016-12 CT#74 CP-160752 5711 2 B Network provided location information for UE accessing P-CSCF from Internet without usage of EPC (or other PS core network) 14.2.0 2016-12 CT#74 CP-160798 5712 F PSAP callback after emergency call via ePDG compliant to Rel-14 14.2.0 2016-12 CT#74 CP-160755 5713 1 F Providing subscriber's ID in case of anonymous emergency calls 14.2.0 2016-12 CT#74 CP-160730 5715 A Updated ref to draft-mohali-dispatch-cause-for-service-number-09 14.2.0 2016-12 CT#74 CP-160752 5716 1 F Modification of the duplicated SIP-ISUP interworking procedure at MGCF 14.2.0 2016-12 CT#74 CP-160752 5719 1 F Clarification of the support of the additional routeing fuctionality at IBCFs 14.2.0 2016-12 CT#74 CP-160741 5720 1 B Fallback procedure for 488 response with 301 warning code 14.2.0 2016-12 CT#74 CP-160711 5724 A Updated ref to draft-mohali-dispatch-originating-cdiv-parameter-02 14.2.0 2016-12 CT#74 CP-160747 5726 5 B Reason header extension mechanism in failure responses 14.2.0 2016-12 CT#74 CP-160711 5730 A Reference update: RFC 7976 14.2.0 2016-12 CT#74 CP-160729 5736 A Reference update: draft-ietf-mmusic-4572-update 14.2.0 2016-12 CT#74 CP-160729 5738 1 A Missing updates from support of draft-ietf-mmusic-dtls-sdp 14.2.0 2016-12 CT#74 CP-160744 5739 2 B SDP profile update to support simulcast and RTP-level pause and resume 14.2.0 2016-12 CT#74 CP-160744 5740 1 B Support of multiple codecs and codec configurations per media line in SDP answer 14.2.0 2016-12 CT#74 CP-160755 5741 1 C P-Visited-Network-ID header for S8HR 14.2.0 2016-12 CT#74 CP-160755 5742 1 C Support of non-UE detected emergency calls for S8 roaming 14.2.0 2016-12 CT#74 CP-160752 5743 1 F Add in BYE and CANCEL an SDP body indicating which desired status triggered the failure 14.2.0 2016-12 CT#74 CP-160739 5744 3 F Update to eCall over IMS procedures 14.2.0 2016-12 CT#74 CP-160751 5746 2 B Indication of calling number verification 14.2.0 2016-12 CT#74 CP-160821 5747 5 B Emergency number determination for call over WLAN 14.2.0 2016-12 CT#74 CP-160741 5748 1 F Clarifications that 5.1.3.1 is for initial INVITE 14.2.0 2016-12 CT#74 CP-160714 5751 A IANA form premium-rate tel URI parameter 14.2.0 2016-12 CT#74 CP-160755 5752 B Terminology 14.2.0 2016-12 CT#74 CP-160755 5753 B Emergency registration for roaming users in deployments without IMS-level roaming interfaces 14.2.0 2016-12 CT#74 CP-160755 5754 4 B Emergency registration triggered by 420 (Bad Extension) for roaming users in deployments without IMS-level roaming interfaces 14.2.0 2016-12 CT#74 CP-160715 5757 1 A AKAv2 usage for WebRTC 14.2.0 2016-12 CT#74 CP-160752 5764 1 F Clarification on handling of Route header field at the IBCF 14.2.0 2016-12 CT#74 CP-160716 5768 A Reference update: RFC 7989 14.2.0 2016-12 CT#74 CP-160742 5771 2 B Definition and configuration of emergency registration timer 14.2.0 2016-12 CT#74 CP-160819 5772 6 B Removal of editors notes for parameters configured on UICC 14.2.0 2016-12 CT#74 CP-160815 5774 5 A Emergency URN determination for call over WLAN 14.2.0 2016-12 CT#74 CP-160748 5776 3 B New Protocol value for Reason Header for P-CSCF initiated call release 14.2.0 2016-12 CT#74 CP-160752 5777 2 B anonymous IMS emergency session support indication 14.2.0 2016-12 CT#74 CP-160713 5780 2 A EN related to reg-event for static PBX 14.2.0 2016-12 CT#74 CP-160717 5783 1 A Correction of IANA form Restoration-Info 14.2.0 2016-12 CT#74 CP-160716 5786 1 A Correction of IANA form Restoration-Info 14.2.0 2016-12 CT#74 CP-160724 5788 1 A Correction of IANA form Resource-Share 14.2.0 2017-03 CT#75 CP-170124 5789 1 B Policy on local numbers 14.3.0 2017-03 CT#75 CP-170118 5791 2 A Updated ref to draft-mohali-dispatch-cause-for-service-number 14.3.0 2017-03 CT#75 CP-170123 5793 5 B New Response-Source header field in error responses– Alt2-urn 14.3.0 2017-03 CT#75 CP-170137 5794 2 F Removing misplaced statement 14.3.0 2017-03 CT#75 CP-170105 5798 A Updated ref to draft-mohali-dispatch-originating-cdiv-parameter-03 14.3.0 2017-03 CT#75 CP-170137 5799 1 F Clarification on SDP offer answer for transcoding 14.3.0 2017-03 CT#75 CP-170134 5800 1 C Unsolicited transfer of UPLI during emergency call over WLAN 14.3.0 2017-03 CT#75 CP-170120 5801 5 B Stage 3 for CT Aspects of Determination of Completeness of Charging Information in IMS 14.3.0 2017-03 CT#75 CP-170113 5806 1 A RFC 4572 obsoleted by draft-ietf-mmusic-4572-update 14.3.0 2017-03 CT#75 CP-170123 5807 F SDP offer/answer clarifications for RTP/RTCP multiplexing 14.3.0 2017-03 CT#75 CP-170135 5808 3 B Identity verification using the Identity header procedures 14.3.0 2017-03 CT#75 CP-170107 5811 A IANA registration, clarifications to registration token 14.3.0 2017-03 CT#75 CP-170123 5813 5 B S-CSCF storing authentication parameters 14.3.0 2017-03 CT#75 CP-170135 5814 1 B Addition of the Unwanted response 14.3.0 2017-03 CT#75 CP-170130 5815 4 B Data off IMS procedures 14.3.0 2017-03 CT#75 CP-170106 5822 1 A IANA registration for "premium-rate" complete 14.3.0 2017-03 CT#75 CP-170103 5828 1 A Update IANA registration template for infoDtmf 14.3.0 2017-03 CT#75 CP-170104 5835 A IANA registration for e2ae complete 14.3.0 2017-03 CT#75 CP-170134 5838 F 200 (OK) response for INFO request requesting current location information 14.3.0 2017-03 CT#75 CP-170124 5840 2 B Removal of editors notes for parameters configured on UICC 14.3.0 2017-03 CT#75 CP-170124 5841 1 F Clarification of which nodes should be used on the USIM/ISIM file 14.3.0 2017-03 CT#75 CP-170137 5842 1 F Access-types for the PANI Header Field 14.3.0 2017-03 CT#75 CP-170107 5845 A Reference update: RFC 8055 14.3.0 2017-03 CT#75 CP-170117 5847 1 A Correcting errors in Priority Sharing procedures 14.3.0 2017-03 CT#75 CP-170137 5848 F Incorrect reference for RFC 4457 14.3.0 2017-03 CT#75 CP-170137 5849 F Incorrect reference for RFC 7549 14.3.0 2017-03 CT#75 CP-170128 5850 B Support of "Compact Concurrent Codec Negotiation and Capabilities" 14.3.0 2017-03 CT#75 CP-170135 5851 1 F Presence of a "verstat" tel URI parameter in the From header field 14.3.0 2017-03 CT#75 CP-170123 5852 1 F Addition of AOC Info body to annex A 14.3.0 2017-03 CT#75 CP-170132 5859 2 F P-CSCF cancels a session currently being established - conditions and 500 response cause values 14.3.0 2017-03 CT#75 CP-170112 5861 1 A Reference update for draft-ietf-mmusic-data-channel-sdpneg 14.3.0 2017-03 CT#75 CP-170112 5863 A Correction of name of SDP dtls-id attribute 14.3.0 2017-03 CT#75 CP-170124 5864 B SMSoIP usage policy 14.3.0 2017-03 CT#75 CP-170113 5867 A S-CSCF storing AS IP address 14.3.0 2017-03 CT#75 CP-170123 5871 3 B Adding optionality to use PVNI header field to P-CSCF procedures 14.3.0 2017-03 CT#75 Removal of revision marks 14.3.1 2017-06 CT#76 CP-171089 5804 6 B Enabling emergency over WLAN when roaming 14.4.0 2017-06 CT#76 CP-171076 5865 5 C Not remove P-CSCF address 14.4.0 2017-06 CT#76 CP-171072 5873 2 B Charging Completeness: Procedures at the P-CSCF 14.4.0 2017-06 CT#76 CP-171072 5874 1 B Charging Completeness: Procedures at the I-CSCF 14.4.0 2017-06 CT#76 CP-171072 5875 1 B Charging Completeness: Procedures at the S-CSCF 14.4.0 2017-06 CT#76 CP-171072 5876 2 B Charging Completeness: Procedures at the MGCF 14.4.0 2017-06 CT#76 CP-171072 5877 1 B Charging Completeness: Procedures at the BGCF 14.4.0 2017-06 CT#76 CP-171072 5878 2 B Charging Completeness: Procedures at the AS 14.4.0 2017-06 CT#76 CP-171072 5879 3 B Charging Completeness: Procedures at the MRFC 14.4.0 2017-06 CT#76 CP-171072 5880 2 B Charging Completeness: Procedures at the IBCF 14.4.0 2017-06 CT#76 CP-171072 5881 1 B Charging Completeness: Procedures at the E-CSCF 14.4.0 2017-06 CT#76 CP-171072 5882 4 B Charging Completeness: Procedures at the ISC Gateway Function 14.4.0 2017-06 CT#76 CP-171087 5883 1 B Addition of the location parameter 14.4.0 2017-06 CT#76 CP-171064 5885 A Reference update: RFC 8122 14.4.0 2017-06 CT#76 CP-171093 5886 F Reference update: draft-ietf-mmusic-mux-exclusive 14.4.0 2017-06 CT#76 CP-171093 5887 2 F E-CSCF/IBCF procedrues for interconnection of IMS emergency session 14.4.0 2017-06 CT#76 CP-171090 5888 F Addition of missing 4xx response codes for SPECTRE to profile tables 14.4.0 2017-06 CT#76 CP-171065 5890 1 A Reference Update RFC8119 14.4.0 2017-06 CT#76 CP-171093 5891 1 F Correcting text for Response-Source 14.4.0 2017-06 CT#76 CP-171056 5895 1 A Updated reference to draft-mohali-sipcore-originating-cdiv-parameter 14.4.0 2017-06 CT#76 CP-171089 5897 1 F Annex A updates for current UE location discovery 14.4.0 2017-06 CT#76 CP-171093 5898 F Annex A updates for access classes in PANI 14.4.0 2017-06 CT#76 CP-171075 5899 1 F Update of reference to IETF draft for eCall over IMS 14.4.0 2017-06 CT#76 CP-171085 5900 2 F Correction data off IMS procedures 14.4.0 2017-06 CT#76 CP-171090 5902 2 F Usage of sip.666 14.4.0 2017-06 CT#76 CP-171090 5903 2 F Profile Table Correction for 666 14.4.0 2017-06 CT#76 CP-171093 5905 3 F Correction of misleading note, Resource-Share WLAN 14.4.0 2017-06 CT#76 CP-171093 5906 F Resource share corrections and clarifications 14.4.0 2017-06 CT#76 CP-171076 5907 5 F Add possibility to use PVNI header field in 200 OK 14.4.0 2017-06 CT#76 CP-171083 5911 F Reference update: MMCMH related IETF drafts 14.4.0 2017-06 CT#76 CP-171090 5912 F Reference update: draft-ietf-stir-rfc4474bis 14.4.0 2017-06 CT#76 CP-171093 5913 3 F Emergency calls via S-CSCF to E-CSCF 14.4.0 2017-06 CT#76 CP-171093 5914 2 F Clarification procedure of deducing an emergency service URN for P-CSCF 14.4.0 2017-06 CT#76 CP-171059 5917 A Reference update: draft-ietf-mmusic-sctp-sdp 14.4.0 2017-06 CT#76 CP-171064 5919 A Reference update: draft-ietf-mmusic-dtls-sdp 14.4.0 2017-06 CT#76 CP-171093 5921 2 F Correction of e2ae media security procedures when SDP capneg is applied 14.4.0 2017-06 CT#76 CP-171093 5923 2 B Response-Source header field handling completion 14.4.0 2017-06 CT#76 CP-171093 5924 1 F Clean up unspecified home domain name 14.4.0 2017-06 CT#76 CP-171076 5925 1 F Reshuffling P-CSCF response handling 14.4.0 2017-06 CT#76 CP-171087 5926 2 F Editor's notes on Reason extensions 14.4.0 2017-06 CT#76 CP-171078 5927 2 F IMS Trace (ISAT) Reference and Syntax Updates 14.4.0 2017-06 CT#76 CP-171093 5928 1 F Corrections to Resource-Shared defintion and profile table entry 14.4.0 2017-06 CT#76 CP-171093 5929 1 F Correct Annex A for Response-Source 14.4.0 2017-06 CT#76 CP-171076 5930 1 C PVNI header field usage in P-CSCF procedures - update 14.4.0 2017-06 CT#76 CP-171077 5932 2 F Definition and configuration of emergency request timer 14.4.0 2017-06 CT#76 CP-171054 5939 A Update draft-atarius-dispatch-meid-urn reference 14.4.0 2017-06 CT#76 CP-171060 5943 A IANA registration completed: registration-token 14.4.0 2017-09 CT#77 CP-172084 5952 A IANA registratin for DTMF info package complete 14.5.0 2017-09 CT#77 CP-172086 5956 A IANA registration for rel-12 reason protocols complete 14.5.0 2017-09 CT#77 CP-172092 5958 A IANA registration for rel-13 reason protocols complete 14.5.0 2017-09 CT#77 CP-172089 5961 A IANA registration for Relayed-Charge 14.5.0 2017-09 CT#77 CP-172111 5963 2 F Clarify use of Non-3GPP NW provided policies IE and WLAN provided emergency numbers 14.5.0 2017-09 CT#77 CP-172112 5965 F RFC 8197 available 14.5.0 2017-09 CT#77 CP-172100 5967 1 F ISAT add MGCF, MSC Server roles and clean-ups 14.5.0 2017-09 CT#77 CP-172109 5972 1 F Reference Update for the ISUP location parameter 14.5.0 2017-09 CT#77 CP-172113 5973 F Correction for INVITE to UPDATE in Non-UE detectable emergency session 14.5.0 2017-09 CT#77 CP-172090 5975 A IANA registration for Resource-Share complete 14.5.0 2017-09 CT#77 CP-172088 5978 A IANA registration for Restoration-Info complete 14.5.0 2017-09 CT#77 CP-172089 5982 2 A Remove IANA registration template for sos.country-specific 14.5.0 2017-09 CT#77 CP-172107 5983 1 F Aligning the availability for calls procedures 14.5.0 2017-09 CT#77 CP-172121 5872 4 C Procedure improvement of P-CSCF routing the SUBSCRIBE 15.0.0 2017-09 CT#77 CP-172115 5962 1 B Annex for 5G IP-CAN 15.0.0 2017-09 CT#77 CP-172117 5964 F Correction on S-CSCF orig-ioi handling for call forwarding 15.0.0 2017-09 CT#77 CP-172117 5966 2 B SDP offer/answer negotiation for media transcoding 15.0.0 2017-09 CT#77 CP-172117 5968 F Correction handling of Relayed-Charge header field 15.0.0 2017-09 CT#77 CP-172117 5969 B Support of IETF draft-ietf-sipcore-content-id 15.0.0 2017-09 CT#77 CP-172121 5970 1 F Clarification for emergency registration 15.0.0 2017-09 CT#77 CP-172117 5979 1 F Reference to a new IETF draft regarding using PVNI header field in responses 15.0.0 2017-12 CT#78 CP-173080 5920 9 B Registration handling when VoPS not supported 15.1.0 2017-12 CT#78 CP-173074 5985 4 B Conditions for sending 488 response 15.1.0 2017-12 CT#78 CP-173059 5987 A Reference Update for the ISUP location parameter 15.1.0 2017-12 CT#78 CP-173046 5992 1 A Update draft ref for Originating-CDIV param in P-Served-User 15.1.0 2017-12 CT#78 CP-173059 5994 A Removing Editor's Notes after IANA reg 15.1.0 2017-12 CT#78 CP-173061 5996 3 A sos-URN restriction for test eCalls 15.1.0 2017-12 CT#78 CP-173080 5998 F Making "Emergency session set-up in case of no registration" dependent on a network's indication of support for emergency bearer services in limited service state 15.1.0 2017-12 CT#78 CP-173080 6001 1 F Prohibiting usage of PDN connection for emergency bearer services for non-emergencies 15.1.0 2017-12 CT#78 CP-173048 6004 1 A Defining access technology specific procedures for attempting emergency call via WLAN 15.1.0 2017-12 CT#78 CP-173080 6005 1 F Editorials e.g. related to sub-clause headings 15.1.0 2017-12 CT#78 CP-173062 6007 A Missing update reference to RFC8119 15.1.0 2017-12 CT#78 CP-173074 6008 4 F Clarification on 403 response to REGISTER handling 15.1.0 2017-12 CT#78 CP-173051 6011 A Resource-Share handling in AppServer terminating side 15.1.0 2017-12 CT#78 CP-173051 6014 1 A Resource Sharing in P-CSCF orig side 15.1.0 2017-12 CT#78 CP-173059 6016 A Correcting reference to draft-ietf-sipcore-reason-q850-loc 15.1.0 2017-12 CT#78 CP-173061 6018 A Support of eCall MIME bodies in profile tables 15.1.0 2017-12 CT#78 CP-173082 6019 1 B Support for e2e QoS over untrusted WLAN 15.1.0 2017-12 CT#78 CP-173070 6020 2 B Annex U SIP procedure at the UE 15.1.0 2017-12 CT#78 CP-173070 6021 1 B Annex U SIP procedure at the S-CSCF 15.1.0 2017-12 CT#78 CP-173070 6022 1 B Annex U SIP procedure at the P-CSCF 15.1.0 2017-12 CT#78 CP-173070 6024 2 B Annex U emergency service procedure on UE 15.1.0 2017-12 CT#78 CP-173052 6027 A Reference update: draft-ietf-mmusic-dtls-sdp 15.1.0 2017-12 CT#78 CP-173074 6028 F Reference update: RFC 8262 15.1.0 2017-12 CT#78 CP-173057 6030 1 A Resolve EN "It is FFS if the UE can still use these numbers when connected only to non-3GPP access" 15.1.0 2017-12 CT#78 CP-173074 6034 3 C Proposed enhancements to avoid IP fragmentation for non-3GPP access 15.1.0 2017-12 CT#78 CP-173074 6036 D Editorial changes of dialogues to dialogs 15.1.0 2017-12 CT#78 CP-173074 6037 1 F Clarification on sending updated SDP offer on all SIP dialogs 15.1.0 2017-12 CT#78 CP-173080 6038 2 F Clarification for authentication during emergency attach 15.1.0 2017-12 CT#78 CP-173070 6039 2 B Enabling NR CGI reporting in the P-Access-Network-Info header field 15.1.0 2017-12 CT#78 CP-173048 6042 A Cellular-Network-Info IANA registered. 15.1.0 2017-12 CT#78 CP-173070 6043 2 B SSC mode 1 for mmtel services 15.1.0 2017-12 CT#78 CP-173070 6044 2 B Transfer P-CSCF address from 5GS 15.1.0 2017-12 CT#78 CP-173058 6046 A IANA registratin for "verstat" complete 15.1.0 2017-12 CT#78 CP-173062 6049 1 A Removal of editor's note IPv4/IPv6 support. 15.1.0 2018-03 CT#79 CP-180085 5940 7 B Identifying the registration token from "reg" event 15.2.0 2018-03 CT#79 CP-180059 6053 1 A Specifying the length of the third sub service label of the country-specific URN 15.2.0 2018-03 CT#79 CP-180067 6055 A Reregistration upon provisioning of a new list of PS data off exempt services 15.2.0 2018-03 CT#79 CP-180085 6056 1 B Definition of user-specified encoding type of subadress 15.2.0 2018-03 CT#79 CP-180071 6060 4 A Inconsistent UE behaviour when 503 to REGISTER 15.2.0 2018-03 CT#79 CP-180078 6061 6 B Adding subclauses in annexes for deriving an emergency service URN 15.2.0 2018-03 CT#79 CP-180070 6063 1 A Support for "fe-identifier" header field parameter only optional 15.2.0 2018-03 CT#79 CP-180059 6067 A Update reference to draft-allen-sipcore-sip-tree-cap-indicators 15.2.0 2018-03 CT#79 CP-180068 6070 A Reference Update for the ISUP location parameter 15.2.0 2018-03 CT#79 CP-180078 6071 2 B 5GS QoS flow for media 15.2.0 2018-03 CT#79 CP-180078 6072 1 B Session and Mobility Management 5GS 15.2.0 2018-03 CT#79 CP-180078 6073 1 B 5GS cell selection 15.2.0 2018-03 CT#79 CP-180064 6076 A Reference update: RFC 8224 15.2.0 2018-03 CT#79 CP-180085 6078 2 C SSID usage in phonecontext teluri parameter 15.2.0 2018-03 CT#79 CP-180138 6079 4 B Policy for handover of PDN connection between WLAN and EPS 15.2.0 2018-03 CT#79 CP-180078 6080 B Clarifying that 5GS defines emergency bearers by means of emergency PDU session 15.2.0 2018-03 CT#79 CP-180078 6081 1 F Adding annex U in interoperability of IP-CAN section 15.2.0 2018-03 CT#79 CP-180084 6084 3 B Definition of the Ms reference point 15.2.0 2018-06 CT#80 CP-181060 6085 2 B Establishment of IP-CAN bearer Annex U 15.3.0 2018-06 CT#80 CP-181060 6086 2 B Modification of PDU session with QoS flow for SIP signalling 15.3.0 2018-06 CT#80 CP-181067 6090 5 B Gateway attestation procedure for the IBCF 15.3.0 2018-06 CT#80 CP-181067 6091 5 B S-CSCF performing attestation 15.3.0 2018-06 CT#80 CP-181067 6092 4 B AS procedures for attestation and verification 15.3.0 2018-06 CT#80 CP-181067 6093 4 B IBCF procedures over the Ms reference point 15.3.0 2018-06 CT#80 CP-181067 6094 4 B AS procedures over the Ms reference point 15.3.0 2018-06 CT#80 CP-181060 6096 1 B Adding 5GS IP-CAN where needed 15.3.0 2018-06 CT#80 CP-181053 6098 1 A Redefinition of the emerg-reg timer 15.3.0 2018-06 CT#80 CP-181060 6099 7 B Emergency call in single registration mode 15.3.0 2018-06 CT#80 CP-181060 6101 B Addressing EN on IP address assignment 15.3.0 2018-06 CT#80 CP-181060 6102 1 B Re-establishment of QoS Flow used for SIP signalling 15.3.0 2018-06 CT#80 CP-181060 6104 1 B Addressing the ENs on PS data off 15.3.0 2018-06 CT#80 CP-181060 6105 B Resource sharing in 5G 15.3.0 2018-06 CT#80 CP-181060 6106 B Priority sharing in 5G 15.3.0 2018-06 CT#80 CP-181060 6107 3 B Emergency service URN derival from Extended Emergency List IE 15.3.0 2018-06 CT#80 CP-181068 6108 F Syntax correction for the P-Charging-Vector header field 15.3.0 2018-06 CT#80 CP-181060 6109 1 B Clarification for emergency registration for 5G IMS 15.3.0 2018-06 CT#80 CP-181052 6111 A IANA registration complete: g.3gpp.verstat Feature-capability indicator 15.3.0 2018-06 CT#80 CP-181067 6113 1 B "Calling number verification using signature verification and attestation": feature definition 15.3.0 2018-06 CT#80 CP-181067 6114 2 B Definition of Attestation-Info header field 15.3.0 2018-06 CT#80 CP-181067 6115 2 B Definition of Origination-Id header field 15.3.0 2018-06 CT#80 CP-181060 6117 B Restricting eCall over IMS in 5GS to E-UTRA connected to 5GCN 15.3.0 2018-06 CT#80 CP-181060 6118 1 F Adding references to Annex U 15.3.0 2018-06 CT#80 CP-181060 6120 1 B Emergency call upon 380 15.3.0 2018-06 CT#80 CP-181060 6121 2 B PDU session affecting services availability 15.3.0 2018-06 CT#80 CP-181074 6123 2 B 3GPP PS Data off2 IMS procedures 15.3.0 2018-06 CT#80 CP-181067 6124 1 B Annex for HTTP usage in 24.229 15.3.0 2018-06 CT#80 CP-181060 6087 1 B P-CSCF restoration in Annex U 15.3.0 2018-09 CT#81 CP-182145 6119 6 B Emergency call in dual registration mode 15.4.0 2018-09 CT#81 CP-182105 6127 3 F Correct procedures due to receiving URN information 15.4.0 2018-09 CT#81 CP-182145 6128 2 F Correct annexes due to receiving URN information 15.4.0 2018-09 CT#81 CP-182128 6133 2 B Enable replacing emergency service URN if unknown 15.4.0 2018-09 CT#81 CP-182145 6137 2 F 3 Octet TAC in PANI 15.4.0 2018-09 CT#81 CP-182158 6139 F deletion of superfluous "void" in H.5 15.4.0 2018-09 CT#81 CP-182145 6140 1 F TS 23.221 does not apply to 5GS 15.4.0 2018-09 CT#81 CP-182114 6146 A Reference update for the Feature-Capability Indicators 15.4.0 2018-09 CT#81 CP-182118 6149 A Support of Identity header field 15.4.0 2018-09 CT#81 CP-182150 6150 B Attestation information in SIP profile tables 15.4.0 2018-09 CT#81 CP-182113 6155 1 A Update draft ref for Originating-CDIV param in P-Served-User 15.4.0 2018-09 CT#81 CP-182150 6159 F Correct terminating AS procedure 15.4.0 2018-09 CT#81 CP-182150 6160 6 B Ms reference point specification 15.4.0 2018-09 CT#81 CP-182145 6161 2 F Emergency service in single registration mode 15.4.0 2018-09 CT#81 CP-182145 6163 1 F Term Voice Centric in Annex U 15.4.0 2018-09 CT#81 CP-182145 6165 2 B Annex for n3g access to 5GC 15.4.0 2018-09 CT#81 CP-182158 6166 F Correction to statement in Annex E.5 and Annex H.5 15.4.0 2018-09 CT#81 CP-182123 6171 1 A Modification on the procedures for determination of completeness of charging Information 15.4.0 2018-09 CT#81 CP-182158 6172 1 F Correction to policy for handover of PDN connection between WLAN and EPS 15.4.0 2018-09 CT#81 CP-182145 6174 1 F Too many 5GS IP-CANs 15.4.0 2018-09 CT#81 CP-182145 6175 2 C Location information in Dual Connectivity 15.4.0 2018-09 CT#81 CP-182150 6185 4 B Signing and verification at diversion 15.4.0 2018-09 CT#81 CP-182119 6187 A Reference Update for the ISUP Q.850 location parameter 15.4.0 2018-12 CT#82 CP-183044 6134 12 B Prevent use of EENL URNs provided by another PLMN 15.5.0 2018-12 CT#82 CP-183055 6158 7 F Clarification on PLMN-Id in P-Access-Network-Info header 15.5.0 2018-12 CT#82 CP-183044 6164 5 B P-Charging-Vector header for 5GS 15.5.0 2018-12 CT#82 CP-183072 6193 1 A Change reference from IETF draft to RFC 15.5.0 2018-12 CT#82 CP-183044 6194 8 B Prevent use of EENL URNs provided by another PLMN involving WLAN connected to EPC 15.5.0 2018-12 CT#82 CP-183074 6197 1 A Hosted NAT traversal for TCP based streams 15.5.0 2018-12 CT#82 CP-183050 6205 1 A P-CSCF handling DTLS-SRTP 15.5.0 2018-12 CT#82 CP-183056 6207 1 A Removal of the EN on "Default EPS bearer context usage restriction policy" 15.5.0 2018-12 CT#82 CP-183052 6212 2 A Update draft ref for Originating-CDIV param in P-Served-User 15.5.0 2018-12 CT#82 CP-183054 6222 A Removing EN for Response_Source header registrationt 15.5.0 2018-12 CT#82 CP-183055 6231 1 F Removing SIP COMET method 15.5.0 2018-12 CT#82 CP-183044 6232 F Correcting 3 Octets TAC in Cellular-Network-Info and PANI 15.5.0 2018-12 CT#82 CP-183055 6233 3 B New timer for EC attempt via non-3GPP access 15.5.0 2018-12 CT#82 CP-183044 6235 F Correcting 5GC to 5GCN 15.5.0 2018-12 CT#82 CP-183052 6240 1 A Delete EN in R.3.2.1 15.5.0 2018-12 CT#82 CP-183044 6241 F Correct conditions for applying procedure for emergency calls without registrationt 15.5.0 2018-12 CT#82 CP-183055 6250 2 F Privacy protection of user location information 15.5.0 2018-12 CT#82 CP-183044 6251 3 F Clarification of choosing the right emergency service URN in case of conflict 15.5.0 2018-12 CT#82 CP-183049 6253 3 F div verification modifications 15.5.0 2018-12 CT#82 CP-183044 6254 3 F Correct procedures specific to 3GPP accesses; add 5G applicability 15.5.0 2018-12 CT#82 CP-183044 6255 1 F Correct ambigious 5G procedure names 15.5.0 2018-12 CT#82 CP-183044 6256 7 F Prevent use of EENL URNs provided by another PLMN involving WLAN connected to 5GC 15.5.0 2018-12 CT#82 CP-183044 6257 4 F Correct prohibiting usage of PDN connection for emergency bearer services 15.5.0 2018-12 CT#82 CP-183044 6260 F Corrections on emergency services in single-registration mode 15.5.0 2018-12 CT#82 CP-183044 6261 F Corrections on emergency services in dual-registration mode 15.5.0 2018-12 CT#82 CP-183044 6262 1 B PCF Based P-CSCF Restoration 15.5.0 2018-12 CT#82 CP-183044 6263 3 B Handling of default QoS flow usage restriction policy in annex U 15.5.0 2018-12 CT#82 CP-183049 6264 3 F Resolution of eSPECTRE editor's notest 15.5.0 2018-12 CT#82 CP-183044 6265 1 F Clarification for emergency calls without registration 15.5.0 2018-12 CT#82 CP-183044 6266 1 F Removal of NOTE for emergency call upon 380 15.5.0 2018-12 CT#82 CP-183044 6267 F Availability for calls in 5GS 15.5.0 2018-12 CT#82 CP-183053 6270 1 A Dynamic Service Interaction missing in annex A 15.5.0 2018-12 CT#82 CP-183044 6272 F Applicability of IMS registration policy- “Stay_Registered_When_VoPS_Not_Supported" for 5GS 15.5.0 2018-12 CT#82 CP-183044 6273 1 F Correct usage of DNS to obtain emergency numbers 15.5.0 2018-12 CT#82 CP-183066 6275 A PS-Data-Off IANA registration complete 15.5.0 2018-12 CT#82 CP-183077 6147 3 B Support of the Location Source Parameter for the SIP Geolocation Header Field 16.0.0 2018-12 CT#82 CP-183077 6277 1 F Default CPC value 16.0.0 2019-03 CT#83 CP-190108 6278 1 C Addition of 802.11ac to P-Access-Network-Info header 16.1.0 2019-03 CT#83 CP-190102 6279 1 C Inclusion of PIDF-LO as per RFC 5491 16.1.0 2019-03 CT#83 CP-190077 6284 3 A EN on ETSI 283 035 16.1.0 2019-03 CT#83 CP-190093 6286 1 A Unsuccessful resource reservation in Annex U 16.1.0 2019-03 CT#83 CP-190102 6291 1 F Correct restoration procedures 16.1.0 2019-03 CT#83 CP-190093 6294 1 A T3517 expiry after ESFB attempt 16.1.0 2019-03 CT#83 CP-190108 6295 F Subscriptions to dialog and presence states for emergency calls 16.1.0 2019-03 CT#83 CP-190079 6299 1 A Update reference from IETF logme-marking draft to RFC 8497 16.1.0 2019-03 CT#83 CP-190081 6303 1 A Reference Update for the ISUP Cause Location Parameter Draft 16.1.0 2019-03 CT#83 CP-190102 6304 1 F Reference Update for Location-Source Parameter 16.1.0 2019-03 CT#83 CP-190076 6309 A Terminating INVITE when only IMS emergency registered 16.1.0 2019-03 CT#83 CP-190075 6315 1 A P-Served-User case orig-cdiv is now RFC 8498 16.1.0 2019-03 CT#83 CP-190093 6317 1 A Addition of 5GS IP-CAN as "phone-context" tel URI parameter 16.1.0 2019-03 CT#83 CP-190102 6318 1 F Restricting the use of "urn:service:sos" in some jurisdictions 16.1.0 2019-06 CT#84 CP-191141 6320 2 B Handling of Session Timer 16.2.0 2019-06 CT#84 CP-191141 6323 F Deletion of a Note related to "urn:service:sos" 16.2.0 2019-06 CT#84 CP-191139 6324 3 B Update SDP Profile definition for DBI support 16.2.0 2019-06 CT#84 CP-191144 6325 1 B RLOS definitions 16.2.0 2019-06 CT#84 CP-191144 6326 2 B RLOS registration 16.2.0 2019-06 CT#84 CP-191144 6327 1 B RLOS session setup 16.2.0 2019-06 CT#84 16.2.0 2019-06 CT#84 CP-191120 6332 A Reference Update for the ISUP Cause Location Parameter Draft 16.2.0 2019-06 CT#84 CP-191126 6334 A Correct “urn:services:sos" into “urn:service:sos" 16.2.0 2019-06 CT#84 CP-191121 6336 1 A QoS flow for SIP signalling in 5GS 16.2.0 2019-06 CT#84 CP-191147 6338 1 F 802.11 references update in TS 24.229 16.2.0 2019-09 CT#85 CP-192039 6342 1 A IANA registration of Priority-Share header field 16.3.0 2019-09 CT#85 CP-192046 6344 1 A Address EN on emergency service type conflict 16.3.0 2019-09 CT#85 CP-192046 6346 1 A Editor’s Note in U.2A.3 16.3.0 2019-09 CT#85 CP-192068 6347 D Correction for structure in Annex O 16.3.0 2019-09 CT#85 CP-192068 6348 1 B RLOS for UICC less case 16.3.0 2019-09 CT#85 CP-192068 6349 1 B R-URI of RLOS INVITE 16.3.0 2019-09 CT#85 CP-192046 6351 A Correct cell selection and lack of coverage requirements when NG-RAN is used 16.3.0 2019-09 CT#85 CP-192071 6352 F Correction for the definition of "HSS based P-CSCF restoration procedures" 16.3.0 2019-09 CT#85 CP-192046 6354 1 A Correct IM CN subsystem interworking with 5GCN via WLAN interoperability 16.3.0 2019-09 CT#85 CP-192064 6356 1 F Correcting emergency call handling for UEs 16.3.0 2019-09 CT#85 CP-192046 6357 2 A Resolving EN on UE and AMF in different PLMNs 16.3.0 2019-09 CT#85 CP-192049 6361 1 A Update to the reference on P header 16.3.0 2019-09 CT#85 CP-192041 6364 1 A Update to the reference on RTP/RTCP Multiplexing 16.3.0 2019-09 CT#85 CP-192064 6365 1 F Reference Update draft-ietf-sipcore-locparam 16.3.0 2019-09 CT#85 CP-192044 6368 1 A Reference Update RFC8606 16.3.0 2019-09 CT#85 CP-192048 6370 A Reference update: RFC 8588 16.3.0 2019-09 CT#85 CP-192067 6371 B Definition of Additional-Identity header field 16.3.0 2019-09 CT#85 CP-192050 6373 1 A Correction in detecting a successful authentication procedure during emergency ATTACH 16.3.0 2019-09 CT#85 CP-192048 6375 A Reference update of draft-ietf-stir-passport-divert 16.3.0 2019-09 CT#85 CP-192064 6376 1 F ASN.1 corrections 24.229 16.3.0 2019-09 CT#85 CP-192071 6378 2 F SIP handling at the originating UE when redirection fails from NG-RAN to E-UTRAN 16.3.0 2019-09 CT#85 CP-192064 6381 1 F Incorrect cause for FAILURE_CAUSE 16.3.0 2019-12 CT#86 CP-193116 6322 7 C Correction to P-CSCF restoration procedures 16.4.0 2019-12 CT#86 CP-193107 6383 1 F Reference Update draft-ietf-sipcore-locparam 16.4.0 2019-12 CT#86 CP-193120 6384 2 B Service Based Architecture in IMS 16.4.0 2019-12 CT#86 CP-193112 6385 1 B RLOS and PS data off 16.4.0 2019-12 CT#86 CP-193112 6386 1 B RLOS Profile definition 16.4.0 2019-12 CT#86 CP-193112 6387 C Usage of IMEI based identity in RLOS INVITE request 16.4.0 2019-12 CT#86 CP-193112 6388 C Handling of messages not related to RLOS 16.4.0 2019-12 CT#86 CP-193112 6389 1 F RLOS Request-URI supporting dial strings 16.4.0 2019-12 CT#86 CP-193116 6390 2 B Enabling NR-U access-type reporting in P-Access-Network-Info header and Cellular-Network-Info header field 16.4.0 2019-12 CT#86 CP-193116 6392 F Ensure correct Reason for SRVCC 16.4.0 2019-12 CT#86 CP-193116 6393 1 B Reregistration between 3GPP and non-3GPP access, missing cases 16.4.0 2019-12 CT#86 CP-193092 6394 3 F Procedure for MO IMS related signalling started indication for UAC 16.4.0 2019-12 CT#86 CP-193111 6397 B Additional-Identity header in REFER request 16.4.0 2019-12 CT#86 CP-193085 6399 1 A P-CSCF restoration in 5GS 16.4.0 2019-12 CT#86 CP-193116 6400 D Editorial correction of E-UTRAN 16.4.0 2020-03 CT#87e CP-200128 6409 B SDP profile update to support FLUS 16.5.0 2020-03 CT#87e CP-200128 6410 1 B Correct reference 16.5.0 2020-03 CT#87e CP-200120 6412 F Correction of P-Associated-URI handling 16.5.0 2020-06 CT#88e CP-201133 6404 8 F Correction in IMS_Registration_handling policy about how UE should deregister. 16.6.0 2020-06 CT#88e CP-201110 6408 1 F No impact from SBA on main body 16.6.0 2020-06 CT#88e CP-201100 6413 1 F UAC for MO-IMS signalling EN resolution 16.6.0 2020-06 CT#88e CP-201133 6414 1 C NG eCall support over NR connected to the 5GC 16.6.0 2020-06 CT#88e CP-201093 6417 A Reference update for PASSporT Extension for Diverted Calls 16.6.0 2020-06 CT#88e CP-201133 6418 B Support of "a=3gpp-qos-hint" SDP attribute for MTSI data channels 16.6.0 2020-06 CT#88e CP-201135 6420 1 B Adding NID to PANI 16.6.0 2020-06 CT#88e CP-201100 6421 1 F Abnormal case handling for MO IMS registration related signalling 16.6.0 2020-06 CT#88e CP-201133 6423 F Correction of data type for verification signing 16.6.0 2020-09 CT#89e CP-202160 6424 F Reference Update RFC8787 16.7.0 2020-09 CT#89e CP-202129 6429 2 A Removal of Capability indication by P-CSCF feature 16.7.0 2020-09 CT#89e CP-202181 6430 2 C 24.229 P-CSCF and UE MPS priority upgrade 17.0.0 2020-09 CT#89e CP-202181 6431 2 C 24.229 Subsequent MPS priority upgrade 17.0.0 2020-09 CT#89e CP-202184 6432 F 5GS terminology: PDU session 17.0.0 2020-09 CT#89e CP-202179 6433 1 F Usage of RFC 5688. 17.0.0 2020-09 CT#89e CP-202179 6434 1 B EPS fallback indication in SIP 17.0.0 2020-09 CT#89e CP-202184 6437 F Fix reference for uniform resource identifier 17.0.0 2020-09 CT#89e CP-202184 6438 2 B New SDP a=content value for video announcement 17.0.0 2020-12 CT#90e CP-203214 6439 4 F Correction to anonymous emergency calls 17.1.0 2020-12 CT#90e CP-203206 6441 A Resolve ENs for RLOS session setup 17.1.0 2020-12 CT#90e CP-203214 6442 F Correction in the P-CSCF operation upon recipt of REGISTER request for RLOS 17.1.0 2020-12 CT#90e CP-203193 6446 1 A IANA registration for Response-Source 17.1.0 2020-12 CT#90e CP-203194 6449 A Correction of isub-encoding field name 17.1.0 2020-12 CT#90e CP-203203 6450 2 F 24.229 MPS Editors notes removal 17.1.0 2020-12 CT#90e CP-203203 6451 1 F 24.229 MPS P-CSCF Editors notes removal 17.1.0 2020-12 CT#90e CP-203214 6454 1 F Correction on TCP connection reuse 17.1.0 2020-12 CT#90e CP-203214 6455 F Clarification on number of retry attempts when receiving invalid challenges 17.1.0 2020-12 CT#90e CP-203204 6457 A Additional-Identity header field, IANA registered 17.1.0 2020-12 CT#90e CP-203192 6462 A Editor's Notes for the Service-Interact-Info header field 17.1.0 2020-12 CT#90e CP-203187 6465 1 A Header fields IANA registered 17.1.0 2020-12 CT#90e CP-203190 6470 A Reference update: draft-ietf-mmusic-data-channel-sdpneg 17.1.0 2020-12 CT#90e CP-203200 6474 A Reference update: MMCMH related IETF drafts 17.1.0 2020-12 CT#90e CP-203214 6476 1 B Adding handling of the UE configuration parameter “Access_Point_Name_Parameter_Reading_Rule“ for the UE to read the APN name parameter from correct input source. 17.1.0 2020-12 CT#90e CP-203214 6478 F Addition of missing abbreviations. 17.1.0 2020-12 CT#90e CP-203214 6480 1 F Improve readability of section L.3.2.8.2 for P-CSCF handling of REGISTER request for RLOS 17.1.0 2020-12 CT#90e CP-203256 6481 2 B Policy for handover between WLAN and 5GS 17.1.0 2021-03 CT#91e CP-210134 6482 1 F Clarification on receiving a 4xx, 5xx (except 503) or 6xx response without Retry-After header field to the REGISTER request 17.2.0 2021-03 CT#91e CP-210129 6483 1 F correction of implementation error of CR6450 17.2.0 2021-03 CT#91e CP-210096 6489 A Reference update: RFC 8841 17.2.0 2021-03 CT#91e CP-210098 6494 A Reference update: RFC 8842 17.2.0 2021-03 CT#91e CP-210099 6499 A Reference update: RFC 8864 17.2.0 2021-03 CT#91e CP-210101 6503 A Reference update: RFC 8851 and RFC 8853 17.2.0 2021-03 CT#91e CP-210102 6507 A Reference update: RFC 8858 17.2.0 2021-03 CT#91e CP-210134 6508 1 F UE behavior clarification when IMS voice not available 17.2.0 2021-03 CT#91e CP-210134 6509 F Error in reference to 23.167 17.2.0 2021-03 CT#91e CP-210103 6513 A Reference update: RFC 8946 17.2.0 2021-03 CT#91e CP-210116 6514 F N1 mode disabling done by NAS 17.2.0 2021-03 CT#91e CP-210134 6516 1 F Clarification on UE procedure for sharing location information in emergency call INVITE 17.2.0 2021-06 CT#92e CP-211134 6527 1 A S-CSCF reselection in eIMS 17.3.0 2021-06 CT#92e CP-211137 6520 1 B Coding of phone-context for SNPN 17.3.0 2021-06 CT#92e CP-211155 6518 3 B Support for signed attestation for priority and emergency sessions 17.3.0 2021-06 CT#92e CP-211156 6411 3 B Location information; mid-call access change 17.3.0 2021-06 CT#92e CP-211156 6524 1 B User-Equipment-Info-Extension applicability over Rx reference point 17.3.0 2021-06 CT#92e CP-211156 6522 2 F Removal of unnecessary statement in Note when preconditions are not used 17.3.0 2021-06 CT#92e CP-211159 6521 1 D Correction of implementation errors of CR6450 and CR6451 17.3.0 2021-06 CT#92e CP-211323 6523 3 B Correction on UE SDP handling for EPS Fallback 17.3.0 2021-06 CT#92e Editorial correction in the title of the specification 17.3.1 2021-09 CT#93e CP-212146 6528 1 F 24.229 RPH signing for MPS 17.4.0 2021-09 CT#93e CP-212146 6529 Reference update: RFC 9027 17.4.0 2021-09 CT#93e CP-212142 6530 2 B New code points for access type and access class for satellite access in the SIP headers 17.4.0 2021-09 CT#93e CP-212147 6532 1 F Clarification on cell-info-age 17.4.0 2021-12 CT#94e CP-213264 6535 5 B UE with SNPN determines serving network 17.5.0 2021-12 CT#94e CP-213057 6534 1 F Correction to CR#6530 17.5.0 2021-12 CT#94e CP-213036 6536 1 B Dialog event package extension for UE information 17.5.0 2021-12 CT#94e CP-213058 6537 - F P-CSCF to provide eps-fallback parameter 17.5.0 2021-12 CT#94e CP-213030 6539 - F Usage of alternate P-CSCF for emergency registration 17.5.0 2022-03 CT#95e CP-220273 6538 1 B Update of SIP Digest Access Authentication and reference update for HTTP/1.1 protocol 17.6.0 2022-03 CT#95e CP-220274 6541 1 B Transport of HSS-GID in the HPLMN 17.6.0 2022-03 CT#95e CP-220236 6542 1 B Support for emergency services in SNPN 17.6.0 2022-03 CT#95e CP-220270 6543 F Clarification of Priority-Verstat values 17.6.0 2022-03 CT#95e CP-220273 6544 B Update of IETF references for ICE, STUN, TURN and IPv6 privacy 17.6.0 2022-03 CT#95e CP-220278 6545 1 F 24.229 MPS priority upgrade at entry points 17.6.0 2022-03 CT#95e CP-220275 6548 1 F Condition for P-CSCF retry for emergency registration 17.6.0 2022-03 CT#95e CP-220275 6552 1 F Confirmation of resource reservation 17.6.0 2022-03 CT#95e CP-220275 6553 1 F Clarification of in-call access update 17.6.0 2022-03 CT#95e 3gpp-ims+xml.xsd file attached 17.6.1 2022-06 CT#96 CP-221220 6561 1 F IMS registration related signalling in SOR-CMCI 17.7.0 2022-06 CT#96 CP-221228 6554 1 B Support of e2ae security using DTLS-SRTP for non WebRTC sessions 17.7.0 2022-06 CT#96 CP-221228 6557 - B IMS authentication using AKAv2-SHA-256 digest AKA algorithm 17.7.0 2022-06 CT#96 CP-221232 6560 2 C Add IBCF Ms procedures to support verification failures 17.7.0 2022-06 CT#96 CP-221314 6558 2 F Reason header values for 5GS 17.7.0 2022-06 CT#96 CP-221348 6556 7 F Annex-V - Verify integrity of SIP header fields based on validated PASSporT claims 17.7.0 2022-06 CT#96 CP-221349 6555 6 C Annex-V Signing and Verification Modifications 17.7.0 2022-06 CT#96 CP-221352 6559 5 F Annex V Corrections 17.7.0 2022-09 CT#97 CP-222161 6564 1 F Reference update: draft-ietf-stir-identity-header-errors-handling 17.8.0 2022-09 Editorial correction 17.8.1 2022-12 CT#98e CP-223141 6565 2 F Annex A update: support of Reason header with "STIR" protocol value 17.9.0 2022-12 CT#98e CP-223141 6566 2 F Reason header field: only one reason value per protocol value allowed 17.9.0 2022-12 CT#98e CP-223122 6568 1 F SNPN: PS Data Off and SMS 17.9.0 2022-12 CT#98e CP-223140 6572 1 A Corrections to current location discovery schema 17.9.0 2022-12 CT#98e CP-223148 6573 1 F Enabling NR-ProSe-L2UNR/L3UNR access-type reporting in P-Access-Network-Info header and Cellular-Network-Info header field 17.9.0 2022-12 CT#98e CP-223141 6574 1 F Reference update: draft-ietf-stir-identity-header-errors-handling 17.9.0 2012-12 CT#98e CP-223128 6567 1 B Support of IETF draft-ietf-sipcore-multiple-reasons 18.0.0 2023-03 CT#99 CP-230259 6584 - A EN on bulk registration 18.1.0 2023-03 CT#99 CP-230237 6576 1 A No procedures for Service-Interact-Info defined 18.1.0 2023-03 CT#99 CP-230220 6585 3 C IMS cross border mobility with Home routed IMS calls 18.1.0 2023-03 CT#99 Section 7.2.22 moved from 7.14 to 7.2 18.1.1 2023-06 CT#100 CP-231244 6605 - A IANA registration for eWebRTCi SDP attributes complete 18.2.0 2023-06 CT#100 CP-231248 6618 1 A IANA registration g.3gpp.thig-path complete 18.2.0 2023-06 CT#100 CP-231253 6599 - A IANA registration of user-specified value completed 18.2.0 2023-06 CT#100 CP-231263 6608 1 A IANA registration for g.3gpp.rlos complete 18.2.0 2023-06 CT#100 CP-231331 6612 - A IANA registration for g.3gpp.announcement-no-confirmation complete 18.2.0 2023-06 CT#100 CP-231274 6610 - A IANA registration for Priority-Verstat complete 18.2.0 2023-06 CT#100 CP-231217 6589 2 F Clarification of the UE behavior at Unified Access Control alleviation 18.2.0 2023-06 CT#100 CP-231232 6620 1 F Correct default bearer/QoS flow restriction policy 18.2.0 2023-06 CT#100 CP-231238 6594 1 B Extension of Cellular-Network-Info 18.2.0 2023-06 CT#100 CP-231247 6592 2 F Clarification of annex V messages 18.2.0 2023-06 CT#100 CP-231247 6593 1 D Editorial alignments and corrections 18.2.0 2023-06 CT#100 CP-231247 6619 1 F Correction to the reference in Annex X 18.2.0 2023-06 CT#100 CP-231247 6621 - F Reference update: RFC 9366 18.2.0 2023-06 CT#100 Fixing errors 18.2.1 2023-09 CT#101 CP-232226 6637 - A Reference update: RFC 9410 18.3.0 2023-09 CT#101 CP-232208 6635 1 A IANA registration related to SEW2-CT complete 18.3.0 2023-09 CT#101 CP-232193 6642 1 B Not performing UE identity verification for the remote UE during IMS emergency registration and session establishment 18.3.0 2023-09 CT#101 CP-232207 6625 1 A IANA registration for g.3gpp.anbr is complete 18.3.0 2023-09 CT#101 CP-232207 6630 1 A IANA registration for Release Cause value 7 redirection is complete 18.3.0 2023-09 CT#101 CP-232235 6638 1 F Clarification of the UE behavior on receiving Retry-After header 18.3.0 2023-09 CT#101 CP-232225 6627 1 A IANA registration for g.3gpp.in-call-access-update complete 18.3.0 2023-09 CT#101 CP-232211 6622 1 B Adding reference to TS 24.186 for IMS data channel 18.3.0 2023-09 CT#101 CP-232211 6641 2 B Update the Procedure Description for IMS DC Capability Negotiation 18.3.0 2023-09 CT#101 CP-232211 6588 6 B Update SBA in IMS for NG_RTC 18.3.0 2023-12 CT#102 CP-233188 6646 - A Reason header field values 18.4.0 2023-12 CT#102 CP-233168 6648 - F Reference to obsoleted IETF HTTP/1.1 RFCs 18.4.0 2023-12 CT#102 CP-233168 6590 9 F Emerg-reg timer change in TS 24.229 18.4.0 2024-03 CT#103 CP-240117 6652 - F Removal of EN related to IMS data channel support 18.5.0 2024-03 CT#103 CP-240117 6651 1 B Support of a=3gpp-bdc-used-by SDP attribute for IMS data channels 18.5.0 2024-03 CT#103 CP-240098 6656 1 A Support of NR RedCap within P-Access-Network-Info header field 18.5.0 2024-03 CT#103 CP-240110 6660 1 F Emerg-reg-retry timer configuration and handling in TS 24.229 18.5.0 2024-03 CT#103 CP-240125 6644 4 B Priority IMS Registration 18.5.0 2024-03 CT#103 CP-240117 6658 1 B Support of a=3gpp-req-app SDP attribute for IMS data channels 18.5.0 2024-03 CT#103 CP-240090 6657 1 B Location validation for L3 remote UE during emergency service 18.5.0 2024-09 CT#105 CP-242176 6666 1 A Change SHA2-256 and SHA2-512/256 algorithm parameter 18.6.0 2024-09 CT#105 CP-242207 6664 2 A Reference Update for draft-sipcore-rfc7976bis 18.6.0 2024-09 CT#105 CP-242218 6670 2 C Alignment of abnormal MSD transfer for eCall with CEN 19.0.0 2024-09 CT#105 CP-242255 6667 7 C Alignment of eCall over IMS with CEN 19.0.0 2024-09 CT#105 CP-242256 6669 7 C Alignment of test eCall with CEN 19.0.0 2024-12 CT#106 CP-243189 6679 - C Correcting the reference for eCall MSD definition 19.1.0 2024-12 CT#106 CP-243184 6681 - F Update of test eCall 19.1.0 2024-12 CT#106 CP-243223 6675 1 B The standalone DC in R19 TS 19.1.0 2024-12 CT#106 CP-243198 6684 1 A Support for satellite access RAT types to align with SA2 19.1.0 2024-12 CT#106 CP-243217 6701 1 A Reference update on the IETF draft 19.1.0 2024-12 CT#106 CP-243192 6686 1 A Priority IMS Registration 19.1.0 2024-12 CT#106 CP-243184 6687 1 B Support of a Priority header field value psap-callback by the UE 19.1.0 2024-12 CT#106 CP-243222 6688 1 B MPS for Messaging P-CSCF changes 19.1.0 2024-12 CT#106 CP-243189 6692 1 F Clarification on the emergency reregistration 19.1.0 2024-12 CT#106 CP-243223 6691 2 B Update the description of PS Data off feature 19.1.0 2024-12 CT#106 CP-243208 6702 2 B Introducing the structure of the new Annex for UE-satellite-UE communicaiton 19.1.0 2024-12 CT#106 CP-243184 6685 2 C Correcting Updated MSD Transfer for PSAP Callback for an eCall 19.1.0 2024-12 CT#106 CP-243239 6680 7 C Alignment of test eCall with CR0377 to TS 23.167 19.1.0 2025-03 CT#107 CP-250154 6705 1 B Providing introduction for the UE-Satellite-UE communication in IMS 19.2.0 2025-03 CT#107 CP-250145 6706 1 F Priority IMS Registration 19.2.0 2025-03 CT#107 CP-250154 6707 1 B Determining the activation of optimized media routing 19.2.0 2025-03 CT#107 CP-250184 6708 2 F Clarfication and corrections to CEN eCall 19.2.0 2025-03 CT#107 CP-250154 6710 2 B Support of UE-Satellite-UE communication with early media in IMS 19.2.0 2025-03 CT#107 CP-250159 6712 - F Name of the "MPS for messaging" indicator 19.2.0 2025-03 CT#107 CP-250159 6713 1 B P-CSCF handling of MPS for Messaging indication 19.2.0 2025-03 CT#107 CP-250150 6714 1 B RCD verification using assertion of rich call data, introduction 19.2.0 |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 1 Scope | The present document specifies the service requirements for Multimedia Priority Service (MPS).
The scope of this document is to specify those requirements of MPS necessary to provide an end-to-end service and to interwork with external networks where needed. Service interactions with external networks are considered within the scope of this document although these interactions may be specified in other standards. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TR 22.952: "Priority Service Guide".
[3] 3GPP TS 22.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 1".
[4] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2".
[5] 3GPP TS 24.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3".
[6] 3GPP TS 22.011: "Service accessibility".
[7] 3GPP TS 22.261: "Service requirements for next generation new services and markets". |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 3 Definitions and abbreviations | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
MPS session: A session for which priority treatment is applied for allocating and maintaining radio and network resources.
MPS-subscribed UE: A UE having MPS subscription.
Priority Treatment: Refers to mechanisms and features that increase the success rate for MPS session invocation, establishment and maintenance until release.
Service User: An individual authorized to use MPS and who has been granted a user priority level assignment by a regional/national authority (i.e., an agency authorised to issue priority assignments), and has a subscription to a mobile network operator that supports the MPS feature.
NOTE A Service User is not always restricted to a human user of the service (e.g., in the case of IoT, it could be a specialized application using MPS through machine interactions that may not directly involve a human Service User). |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
DTS Data Transport Service
MMTEL Multimedia Telephony
MPS Multimedia Priority Service
OTT Over-The-Top
PIN Personal Identification Number
VPN Virtual Private Network |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 4 General description | MPS is applicable in EPS and 5GS systems.
MPS provides priority treatment to increase the probability of an authorized Service User’s Voice, Video, Data and Messaging communication being successful. Some form of priority treatment is applied to the MPS invocation and session establishment, and continues to be applied until the MPS session is released. The priority treatment may be applied before the invocation if a greater probability of success in receiving, recognizing, and processing the invocation is needed.
MPS allows qualified and authorized users to obtain priority access to the next available radio channel on a priority basis before other PLMN users, during situations when PLMN congestion is blocking session establishment attempts. In addition, MPS supports priority sessions on an "end-to-end" priority basis.
MPS is intended to be utilised for Voice, Video, Messaging and Data bearer services, including the Data Transport Service, in the Packet-switched (PS) domain and the IP Multimedia Subsystem (IMS). It also involves priority transitioning of MPS service (e.g., Voice) to the CS domain when the network does not support the requested service in the PS domain. MPS sessions for Voice, Video, Data, and Messaging are based on providing priority treatment to the corresponding commercial services offered to the public.
MPS is also intended to be utilized for IoT communications through machine interactions that may not directly involve a human Service User.
MPS includes network functions that fall into the following broad categories:
Service Invocation: The process to recognize and identify a request for an MPS session. An MPS Service Provider network recognizes an MPS invocation based on the presence of an MPS-unique identifier entered by the originating Service User in the service request received by the network from the UE, or based on the subscription profile of the originating UE, or as a regional/operator option the subscription profile of the terminating UE.
NOTE: The option related to “subscription profile of the terminating UE” may not involve end-to-end priority because this option is based on providing priority only in the terminating network based on the terminating UE subscription profile.
Authorization: The process to verify that a Service User is authorized for MPS. This includes capabilities to verify authorization to receive priority treatment in the radio access network and to access the MPS application service (MPS Voice, Video, Data, and Messaging).
End-to-End Priority Treatment: The process of providing priority treatment in all parts of the path, from one endpoint to the other endpoint(s). End-to-end priority treatment includes priority treatment by all MPS capable networks involved in the MPS session path, the origination network and the termination network as well as any transit networks in between.
Invocation-to-Release Priority Treatment: The process of providing priority treatment to all phases of a session, from invocation until release, including all steps in between.
The combination of End-to-End Priority Treatment and Invocation-to-Release Priority Treatment includes both pre- and post-authorization treatment and includes the following aspects:
1) Priority processing of the Service User’s MPS invocation,
2) Admission control and allocation of network resources (including bearer resources) in origination, termination, and transit networks, including handovers,
3) Transport of signaling and media packets,
4) Priority processing within EPS, 5GS and CN, and
5) Processing of the Service Users release of an MPS service session.
Network Interconnection and Protocol Interworking: A Service User’s MPS invocation and session establishment will involve transport and processing, and the end-to-end signaling and media path may traverse multiple MPS Service Provider networks. These end-to-end cases include, but are not limited to:
1) Voice, video, data and messaging services over EPS or 5GS, including signaling for call/session establishment and media;
2) EPS/5GS interworking with the CS domain, including a) calls originated in the CS domain and terminated in EPS/5GS, and b) calls from EPS/5GS to the CS domain;
3) CS Fallback from EPS, for one or both ends of call, with maintenance of existing PS domain MPS services, either in EPS or in a legacy system, e.g., the GPRS Core; and
4) Access to MPS data, video, and messaging services not under IMS control. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5 High level requirements | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.1 General | The system shall provide preferential treatment based on the subscription for MPS for:
- An authorized Service User using a UE with an MPS subscription,
NOTE 1: The MPS subscription related information is associated with the UE’s HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE, the UE’s membership in a special access class as per TS 22.011 [6] is used for E-UTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5GS (NR and E-UTRA access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
- An authorized Service User using a UE that does not have an MPS subscription, and
NOTE 2: In this case, the Service User’s MPS subscription information (e.g., credentials) is not associated with the UE’s HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription. .
- An authorized IoT device with an MPS subscription.
NOTE 3: The MPS subscription related information is associated with the IoT device’s HPLMN subscription and is either stored in the IoT device and the HPLMN, or only in the HPLMN to allow invocation/revocation of MPS through machine interactions possibly without involving a human. .
Upon invocation of MPS, the system shall provide preferential treatment for access and core network resources associated with the session (i.e., signalling and media bearer related resources within a domain and across domains), including, when applicable, priority treatment towards an enterprise network supporting MPS.
NOTE 4: ‘enterprise network’ (mentioned above, and in other following sections) may be a 3GPP or non-3GPP network.
A Service User is assigned a priority level by a regional/national authority i.e., agency authorised to issue priority levels. Upon MPS invocation the calling Service User's priority level is used to identify the priority to be used for the session being established.
Pre-emption of active sessions shall be subject to regional/national regulatory requirements.
Subject to regional/national regulatory policy, a PLMN should have the capability to retain public access as a fundamental function. Therefore, MPS traffic volumes should be limited (e.g. not to exceed a regional/national specified percentage of any concentrated network resource, such as eNodeB capacity), so as not to compromise this function. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.2 Priority session treatment in originating network | When an MPS session is originated by a Service User, the session shall receive priority treatment (priority access to signalling and media bearer resources for voice, video, data, and messaging service) in the originating PLMN based on the originating Service User priority information (i.e., priority indication and priority level).
When an MPS session is requested by a Service User and the originating network supporting session establishment cannot assign the necessary resources to the MPS session, the MPS session request shall be:
- Queued,
- Processed for the next available resource in accordance with the calling Service User's priority level and session initiation time.
The network shall support the capability to inform the calling Service User about the status of the MPS session (e.g., tones or signalling messages can be used to indicate that the session request has been queued).
If the queued MPS session times out, then normal session processing applies. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.3 Priority session progression | For an MPS session, a Service User shall receive priority session treatment/progression through the PLMN(s). In case the MPS session traverses or terminates in other networks (e.g., the PSTN), the network providing priority session treatment/progression shall support the capability to indicate to the other network that this is an MPS session.
NOTE: If there is no agreement on priority handling between networks, the priority does not carry across network boundaries. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.4 Priority session treatment in terminating network | When a terminating network receives an incoming MPS session establishment attempt, the MPS session shall receive priority treatment (priority access to signalling and media bearer resources for voice, video, data, and messaging service) in the terminating PLMN, based on the originating Service User priority information. When requested, this includes MPS treatment towards an enterprise network supporting MPS.
As an operator option, the terminating network may invoke priority treatment for an incoming session from a non-MPS subscriber to an MPS subscriber (see clause 4).
When the terminating network supporting session establishment cannot assign the necessary resources to the MPS session, the MPS session request shall be:
- Queued,
- Processed for the next available resource in accordance with the Service User's priority level and session arrival time.
The network shall support the capability to inform the calling Service User about the status of the MPS session (e.g., tones or signalling messages can be used to indicate that the session request has been queued).
If the queued MPS session times out, then normal session processing applies.
5.4a Priority Data Bearer Service
The Priority Data Bearer Service provides MPS priority for data and video services not under IMS control.
When a Service User invokes Priority Data Bearer Service for transport of any data packets to and from that Service User, the network should give priority in admission/upgrade of the Priority Data Bearer(s) and in packet data scheduling in the event of congestion (for new sessions and upgrade to existing sessions), subject to regional/national regulatory policy. Specifically:
- A Priority Data Bearer service session shall be given priority for admission/upgrade over non-Priority Data Bearer sessions during times of congestion;
- Data packets belonging to a Priority Data Bearer service shall not be dropped before data packets belonging to a non-Priority Data Bearer service session, when the network is experiencing congestion, subject to the limitation imposed by public access. Priority Data Bearer session QoS, as required for the type of service invoked (e.g., packet delay), should be maintained throughout the activity of the data session.
MPS for Data Transport Service (DTS) is a generic priority packet transport service that applies independently of the specific data application being used. In the case of EPS, MPS for DTS enables the prioritization of all traffic on the default bearer upon request. It may also apply to other bearers based on operator policy and regulatory rules. In the case of 5GS, MPS for DTS enables the prioritization of all traffic on the QoS Flow associated with the default QoS rule upon request. It may also apply to other QoS flows based on operator policy and regulatory rules. MPS for DTS is a specific example of Priority Data Bearer Service. MPS for DTS service specific requirements are described in clause 9.3.
NOTE: MPS for streaming video can be provided as an Over The Top (OTT) service using the MPS for DTS service. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.5 Priority levels | The Service User shall be assigned one of "n" user priority levels. The priority levels are defined with 1 being the highest priority level and "n" being the lowest priority level.
The 3GPP network shall be able to support at least 5 user priority levels.
Assignment of priority levels is a matter of regional/national and operator policy.
In case of interconnecting networks that have different priority levels, mappings between priority levels should be established. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.6 Invocation on demand | MPS priority shall be invoked only when requested by the Service User. However, certain priority treatments are provided prior to invocation as specified in Section 5.13.
MPS is applied when idle resources required for an origination session request are not available.
If idle resources are available when MPS is requested, the request shall be allowed to proceed as normal, but marked as an MPS request.
An indication of an MPS session should be propagated towards the terminating network regardless of the availability of resources in the originating network. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.7 Multimedia priority service code/identifier | MPS shall be requested by including an MPS code/identifier in the session origination request, or optionally, by using an MPS input string (e.g., an MPS public user identity). |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.8 Roaming | MPS shall be supported when the Service User is roaming and the visited network and home network support MPS, and roaming agreements are in place for MPS. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.8.1 Roaming within the home country | The system shall support MPS when a UE with an MPS subscription is roaming within the home country and the visited and home network support MPS, and roaming agreements are in place for MPS.
NOTE 1: Roaming within a home country is subject to national/regional rules and operator policy.
NOTE 2: The MPS subscription related information associated with the UE’s HPLMN subscriptionis used for roaming within the home country. Membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] clause 6.22.2.2 is used for 5G (NR and E-UTRAN access to the 5GC). |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.8.2 Roaming outside the home country | The system shall support MPS when a UE with an MPS subscription is roaming outside of the home country and the visited and home network support MPS, and roaming agreements are in place for MPS.
NOTE 1: Roaming outside a home country is subject to national/regional rules and operator policy.
NOTE 2: The UE subscription in the home PLMN is configured for MPS with the visited PLMN outside the home country as specified in TS 22.261 [7] clause 6.22.2.2, for 5GS (E-UTRA and NR access to the 5GC).
NOTE 3: The home PLMN can configure the UE to discover and select a network supporting MPS when roaming outside of the home country (e.g., the UE is configured to select a specific MPS capable visited PLMN when roaming in a country that may have multiple PLMNs where some are MPS capable and some are not MPS capable). |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.9 Handover | MPS shall be supported during and after the handover (i.e., sessions shall continue to get priority treatment in the network during and after the handover). Resource allocation for the session during handover shall receive priority treatment (priority access to signalling and media bearer resources for voice, video, and data) in the target cell based on the Service User priority information (i.e., priority indication and priority level).
For handover of an MPS voice call to CS, only the active, or if all calls are on hold, only the most recently active voice call shall be transferred and receive the priority treatment in CS. Any remaining non-MPS voice sessions in PS may be released. Any remaining MPS sessions, e.g., MPS data, in PS shall not be released. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.10 Interworking with CS domain | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.10.1 Mobile origination in the CS domain -> MPS mobile termination | For a Priority Service voice call, as described in [2] and as specified in [3, 4, 5], originated by a Service User in the CS Domain, MPS shall support priority Mobile Termination of the session in the IMS. The priority information received from the CS domain shall be mapped and used in the IMS accordingly. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.10.2 MPS mobile origination -> mobile termination to the CS domain | For an MPS voice session originated by a Service User in the IMS, MPS shall support priority delivery of the voice session to the serving CS Domain. The calling Service User priority level shall be sent to the CS Domain. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.10.3 CS Fallback from LTE | Circuit Switched (CS) fallback from LTE needs to be given priority in the LTE system to support MPS voice in cells where voice is not supported in the PS domain. Priority treatment applies to both mobile originated calls and mobile terminated calls.
When an MPS Service User in LTE originates a voice call intended to be supported in the CS domain, and when configured by the operator, the LTE system shall provide priority treatment in the signalling and resource allocations needed to support priority CS fallback.
When a terminating LTE network receives indication of an incoming call to the CS domain, the LTE system shall provide priority treatment in the signalling and resource allocations needed to support priority CS fallback.
5.10a Fallback in 5GS
MPS voice calls need to be provided priority treatment following a voice fallback in 5GS when configured by the operator to fallback to another RAN type and/or core network type to support voice. The priority treatment applies to both mobile originated calls and mobile terminated calls. Non-voice PDU sessions that have priority in the 5GS prior to a voice fallback need to be given priority after the voice fallback. The priority treatment applies when the MPS non-voice PDU sessions move with the MPS voice PDU session and when MPS non-voice PDU sessions do not move with the MPS voice PDU session.
When an MPS Service User in a 5GS originates an MPS voice call and when configured by the operator for voice fallback to another RAN type and/or core network type, the system shall provide priority treatment in the signalling and resource allocations to support the priority voice fallback.
When a 5GS receives indication of a terminating MPS voice call and when configured by the operator for voice fallback to another RAN type and/or core network type, the system shall provide priority treatment in the signalling and resource allocations to support the priority voice fallback.
When the 5GS initiates a voice fallback for an MPS call, the system shall provide priority treatment in the signalling and resource allocations needed to support non-voice priority PDU sessions, if any exist at the time of the voice fallback. The priority treatment shall apply whether the MPS non-voice PDU session moves with the MPS voice PDU session or not. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.11 Network Management Functions | Based on regional/national requirements and network operator policy, an MPS session shall be exempted from network management controls up to the point where further exemption would cause network instability. Congestion controls, overload controls, load balancing, and load re-balancing shall not adversely impact MPS. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.12 Policy Control | The 3GPP network shall be able to make and enforce policy decisions regarding relative treatment of MPS application services (Voice, Video, Data, and Messaging) for admission control subject to regional/national regulatory requirements and operator policy.
The 3GPP network shall be able to make and enforce policy decisions regarding relative treatment of MPS application services traffic depending on the media type subject to regional/national regulatory requirements and operator policy (e.g., based on operator policy or regulation, Voice may have higher priority than Video or Data). |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.13 Priority before service invocation | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.13.1 Overview of priority before service invocation | Providing priority treatment to MPS-subscribed UEs during attachment/registration for radio access and network connectivity before the MPS application service session invocation requests improves the probability of an MPS session request being successful. This involves providing priority treatment for the signalling during the UE attachment for radio access and network connectivity based on a subscription profile. Prior to accessing subscription related information in the network, subscription related information stored in the UE is used, e.g., membership in the special access class required to be reserved for MPS use as per 3GPP TS 22.011 [6], or the special Access Identity used for MPS as per 3GPP TS 22.261 [7]. Without such priority treatment, a Service User’s UE might fail to gain radio access network and CN connectivity which in turn means that there is no access to the MPS application services (Voice, Video, and Data). Priority treatment before MPS session request increases the probability of successful MPS session establishment and any associated process for the Service User authorization (e.g., credential collection). |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.13.2 Requirement for priority before service invocation | The 3GPP network shall be able to provide priority treatment to an MPS-subscribed UE before the MPS application service invocation (e.g., priority treatment for the default and IMS signalling bearers establishment based on a subscription profile).
The 3GPP network shall be able to provide priority requests for access and attachment to the 3GPP network from an MPS-subscribed UE, including those procedures applied prior to and during the access of subscription related information (e.g., based on the UE membership in a special access class for MPS, or when allowed to operate with Access Identity 1 as per 3GPP TS 22.261 [7]). |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.14 Recovery/Restoration | The 3GPP system shall allow operational measures to expedite service recovery and restoration (i.e., service restoration after failure/unavailability). Should a disruption occur, MPS shall be re-provisioned, repaired, or restored to required service levels on a priority basis subject to regional/national regulatory requirements and operator policy. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.15 Quality of Service (QoS) | In certain cases, the QoS characteristics (e.g., packet delay and packet loss) for an MPS session may be the same as the underlying communication service (e.g., voice, video, data or messaging) used to support the MPS session, with the MPS session being provided priority treatment subject to regional/national regulatory and operator policies. In other cases, there may be a need to request specific QoS characteristics for the MPS session (e.g., specific data communications as described in clause 5.4a, 9.3).
The 3GPP network shall allow selection and/or configuration of QoS rule(s) appropriate for MPS Voice, Video, Data and Messaging.
The 3GPP network shall allow enforcement of QoS rule(s) for MPS Voice, Video, Data, and Messaging.
The system shall support means to retain MPS sessions invoked for Voice, Video, Data and Messaging during transient network degradation conditions and recovery (e.g., during short radio link interruption), and re-verify any recovered MPS session afterwards. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.16 Inter-network aspects | The system shall allow MPS priorities to be signalled across interconnected networks.
NOTE 1: Support of MPS services across networks is based on policy and agreements between the network operators.
NOTE 2: Intermediate 3GPP networks not supporting MPS (e.g., transit networks between an originating network and terminating network) should allow MPS priorities to be signalled transparently, based on operator policy and agreements for MPS.
The system shall support means to identify that an incoming voice, video, data or messaging service session from another network is an MPS session and to handle it with priority.
The system shall support measures to verify policy and admit an incoming MPS session for Voice, Video, Data, or Messaging service received from another network with priority. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.17 Interactions with supplementary services | Interactions with a supplementary service might occur during set-up or after establishment of an MPS call or session. A supplementary service is a service which modifies or supplements a basic telecommunication service (see definition in 3GPP TR 21.905 [1]).
The system shall provide MPS priority for a supplementary service associated with an MPS call or session in progress when the supplementary service is associated with the Service User authorized for MPS.
When a supplementary service (e.g., Communication Diversion) results in an established authorized MPS call or session being redirected or extended, MPS priority shall be provided for the redirected or extended call or session.
When a supplementary service (e.g., Conference/Three-Party) is used to join an MPS priority call or session (e.g., to add parties to the established MPS call/session), MPS priority shall be retained on that leg when joined to the supplementary service. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 5.18 3GPP and non-3GPP accesses | When a UE is using 3GPP RAT(s) as well as non-3GPP WLAN access technology, the 3GPP system will select the most appropriate 3GPP RAT or non-3GPP WLAN access technology for one or more services active on theUE. This subclause covers MPS handling when 3GPP RAT(s) and non-3GPP WLAN access technology are being used for one or more services active on a UE.
The system shall support MPS based on operator policy when the UE is using E-UTRA and non-3GPP WLAN and connected to the same EPC.
The system shall support MPS based on operator policy when the UE is using 3GPP RAT(s) and non-3GPP WLAN and connected to the same 5GC. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 6 MMI aspects | In the case when MPS invocation is based on the presence of an MPS-specific service code entered by the originating Service User, this specific service code must be defined for the 3GPP network to recognize such an invocation.
The 3GPP network supporting on-demand invocation of MPS shall recognize a service code indicating a request for MPS.
NOTE: A Service User roaming within or outside the home country must use an MPS-specific service code recognized by the visited PLMN, to indicate a request for MPS based on the agreements between the home and visited PLMNs for MPS.
The choice of an MPS-specific service code is a regional/national and operator matter. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 7 Security and privacy | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 7.1 General | Operators support and use a wide range of security tools and capabilities to protect the 3GPP system and all supported application services. It is important that appropriate measures be taken to ensure that the use of these security capabilities does not negatively impact MPS.
Use of security mechanisms (e.g., intrusion detection / prevention systems, deep packet inspection, and encryption) shall not interfere with priority treatment mechanisms supporting authorized MPS usage. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 7.2 Access Control | Access to MPS shall be determined based on the subscriber's profile. A level of authorisation in addition to authorisation to use the IMS is required.
Unauthorized access to MPS shall be prevented. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 7.3 Integrity | The 3GPP system shall be capable of providing integrity protection to MPS signalling and media bearers for voice, video, data, and messaging service. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 7.4 Confidentiality/Privacy | The 3GPP system shall be capable of providing confidentiality protection to MPS signalling and media bearers for voice, video, and data as appropriate.
The 3GPP system shall be capable of maintaining anonymity of the originating Service User to the terminating party, if requested by the originating Service User. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 7.5 Use of Encryption | If encryption is used on MPS communication, priority information shall be accessible to all network elements which have to understand and process that priority information. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 7.6 Attestation of Authorized MPS Priority | A 3GPP system receiving a session with MPS priority from another network needs to verify that the session is authorized for MPS priority.
The originating 3GPP system shall provide a means to securely attest to MPS authorization for the session.
The 3GPP system shall provide a means to securely verify the attestation of MPS authorization received from the originating network for the session. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 8 Charging aspects | A network supporting MPS shall be capable of recording the following charging information, in addition to non-MPS information:
- MPS invocation attempt and successful session set-up,
- Session bearers (originations and/or terminations) on which MPS was used to gain access to resources,
- Recording of MPS information, e.g., priority level.
The system shall associate MPS related charging events with the MPS subscription. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9 Service specific aspects | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.1 MPS for MMTEL voice | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.1.1 General | MPS for MMTEL voice provides the Service User with priority voice communication sessions in periods of severe network congestion during which normal commercial voice service is degraded.
The system shall support:
- MPS for MMTEL voice and voice conference calls for an authorized Service User using a UE with a subscription for MPS,
NOTE 1: The MPS subscription related information is associated with the UE’s HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE,the UE’s membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
- MPS for MMTEL voice and voice conference calls for an authorized Service User using a UE that does not have an MPS subscription, and
NOTE 2: In this case, the Service User’s MPS subscription information (e.g., credentials) is not associated with the UE’s HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription. .
- MPS for all participants of an authorized MMTEL voice conference call.
NOTE 3: MPS for all participants of an MMTEL voice conference call allows a Service User (i.e., the host) to establish an MMTEL voice conference with MPS for all participants, or upgrade on ongoing MMTEL voice conference to MPS for all participants regardless of their subscription to MPS. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.1.2 Invocation and revocation | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.1.2.1 Invocation | A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL voice/conference call, e.g., when the normal MMTEL call cannot be established, or to upgrade an already established normal MMTEL call to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to:
- initiate MPS for an MMTEL voice call or an MPS MMTEL voice conference call, or
- request upgrade of an established MMTEL voice call, or an established MMTEL voice conference call to MPS.
NOTE 1: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL voice call).
A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL voice call or conference call during roaming, e.g., when the normal MMTEL voice/conference call cannot be established, or to upgrade an already established normal MMTEL call to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to:
- initiate MPS for an MMTEL voice call, or an MPS MMTEL voice conference call when roaming within the home country and outside the home country, or
- requests upgrade of an established MMTEL voice call, or an established MMTEL voice conference call to MPS when roaming within the home country and outside the home country.
NOTE 2: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL voice call) that is recognized by the visited PLMN.
A Service User using a UE that does not have an MPS subscription can invoke MPS to request priority for an MMTEL voice call or MMTEL voice conference call, e.g., when the normal MMTEL voice call or MMTEL voice conference call cannot be established.
The system shall support means for a Service User using a UE that does not have a subscription for MPS to initiate MPS for an MMTEL voice call or MMTEL voice conference call.
NOTE 3: MPS invocation using a UE that does not have an MPS subscription is done using a predetermined method that is outside the scope of 3GPP (e.g., by the Service User use of a predetermined access number, such as a special telephone number).
A Service User who is the host of a MMTEL voice conference can invoke MPS to upgrade the entire MMTEL voice conference call to obtain priority treatment for all participants on the MMTEL voice conference call, e.g., when the normal MMTEL voice conference call cannot be established, or to upgrade an already established normal MMTEL conference call to MPS.
The system shall support means for a Service User to:
- initiate MPS for all participants of an MMTEL voice conference call, or
- request upgrade of all participants of an ongoing MMTEL voice conference call to MPS.
The system shall provide MPS for a late participant joining an MPS for MMTEL voice conference after MPS was activated for all participants.
NOTE 4: When MPS is invoked for all participants of a MMTEL voice conference, the user priority level is based on the host MPS Service User, except in cases where an individual participant used MPS to join the conference with a higher user priority level, the higher user priority level is kept.
NOTE 5: The invocation of MPS for all participants may be done using a customized feature of a voice conference service (available only to the host) that indicates a request for priority to the system. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.1.2.2 Revocation | The 3GPP system shall revoke MPS for the following cases:
• upon end of an MPS MMTEL voice call, or an MPS MMTEL voice conference call from a UE with an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal MMTEL voice service),
• upon end of an MPS MMTEL voice call, or an MPS MMTEL voice conference call from a UE that does not have an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal voice service), and
• upon end of an MPS MMTEL voice conference call where MPS was provided to all participants on the voice conference call, and the UEs shall return to normal conditions (i.e., use of normal MMTEL voice service).
The 3GPP system shall revoke MPS for an individual participant leaving an ongoing MPS for MMTEL voice conference where MPS is activated for all participants.
When an MPS MMTEL voice call or an MPS MMTEL voice conference call is not explicitly ended, upon UE detachment/deregistration (e.g., orderly power down), the system in the RPLMN shall automatically revoke MPS such that MPS priority treatment shall not automatically apply to subsequent calls upon subsequent registration. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.1.3 Authentication and authorization | The system shall support means to authenticate and authorize an MPS MMTEL voice or voice conference call request from a UE with an MPS subscription.
The system shall support means to authenticate and authorize a Service User request for an MPS MMTEL voice or voice conference call from a UE that does not have an MPS subscription.
NOTE 1: The method for authenticating and authorizing the Service User using a UE that does not have an MPS subscription is predetermined. As part of the authentication and authorization process, the Service User provides MPS credentials (e.g., a calling card number, PIN or security token) specifically assigned for the purpose of obtaining MPS from a UE that does not have an MPS subscription.
The system shall support means for a visited PLMN, including a visited PLMN within or outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize an MPS for MMTEL voice or voice conference call.
NOTE 2: The method for authenticating and authorizing UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
The system shall support means to authenticate and authorize a Service User request to establish or upgrade all participants of an MMTEL voice conference call to MPS priority. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.1.4 Signalling | The system shall provide priority treatment to the invocation signalling in the network once the request by the Service User for MPS for an MMTEL voice or MMTEL voice conference call is identified by the system.
The system shall support a means for MPS activation when normal MMTEL voice service is congested at the request of the Service User.
The system shall provide priority treatment to the affected signalling when MPS is activated for an MMTEL voice call, or MMTEL voice conference call. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.1.5 Media | The system shall provide priority treatment to the audio media flows, when MPS is activated for an MMTEL voice call or MMTEL voice conference call. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.2 MPS for MMTEL video | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.2.1 General | The primary purpose of MPS for MMTEL video is to provide the Service User with priority video communication sessions in periods of severe network congestion during which normal commercial video service is degraded.
The system shall support:
- MPS for MMTEL video and video conference calls for an authorized Service User using a UE with a subscription for MPS,
NOTE 1: The MPS subscription related information is associated with the UE’s HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE,the UE’s membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
- MPS for MMTEL video and video conference calls for an authorized Service User using a UE that does not have an MPS subscription, and
NOTE 2: In this case, the Service User’s MPS subscription information (e.g., credentials) is not associated with the UE’s HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription..
- MPS for all participants of an authorized MMTEL video conference call.
NOTE 3: MPS for all participants of an MMTEL video conference call allows a Service User (i.e., the host) to establish an MMTEL video conference with MPS for all participants, or upgrade on ongoing MMTEL video conference to MPS for all participants regardless of their subscription to MPS. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.2.2 Invocation and revocation | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.2.2.1 Invocation | A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL video call or MMTEL video conference call, e.g., when the normal MMTEL video call cannot be established, or to upgrade an already established normal MMTEL call to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to:
- initiate MPS for an MMTEL video call or an MPS MMTEL video conference call, or
- request upgrade of an established MMTEL video call, or an established MMTEL video conference call to MPS.
NOTE 1: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL video call).
NOTE 2: In the case where the MMTEL video call is already established but becomes unacceptable, the invocation by the Service User to upgrade the MMTEL video call to MPS may be done using a using a specialized MPS application on the UE (i.e., as an alternative to releasing and retrying the call which may fail).
A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL video call or MMTEL video conference call during roaming, e.g., when the normal MMTEL video call cannot be established, or to upgrade an already established normal MMTEL video/conference call to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to:
- initiate MPS for an MMTEL video call, or an MPS MMTEL video conference call when roaming within the home country and outside the home country, or
- request upgrade of an established MMTEL video call, or an established MMTEL video conference call to MPS when roaming within the home country and outside the home country.
NOTE 3: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL video call) that is recognized by the visited PLMN.
NOTE 4: In the case where the MMTel video call is already established but becomes unacceptable, the invocation by the Service User to upgrade the MMTel video call to MPS may be done using a using a specialized MPS application on the UE (i.e., as an alternative to releasing and retrying the call which may fail) that is recognized by the visited PLMN.
A Service User, using a UE that does not have an MPS subscription, can invoke MPS to request priority for an MMTEL video call or MMTEL video conference call, e.g., when the normal MMTEL video call, or MMTEL video conference call cannot be established
The system shall support means for a Service User using a UE that does not have a subscription for MPS to initiate MPS for an MMTEL video call or MMTEL video conference call.
NOTE 5: MPS invocation using a UE that does not have an MPS subscription is done using a predetermined method (e.g., by the Service User use of a predetermine access number, such as a special telephone number) and is outside the scope of 3GPP.
A Service User who is the host of a MMTEL video conference can invoke MPS to upgrade the entire MMTEL video conference call to obtain priority treatment for all participants on the MMTEL video conference call, e.g., when the normal MMTEL video call cannot be established, or to upgrade an already established normal MMTEL video conference call to MPS.
The system shall support means for a Service User to:
- initiate MPS for all participants of an MMTEL video conference call, or
- request upgrade of all participants of an ongoing MMTEL video conference call to MPS.
The system shall provide MPS for a late participant joining an MPS for MMTEL video conference after MPS was activated for all participants.
NOTE 6: When MPS is invoked for all participants of a MMTEL video conference, the user priority level is based on the host MPS Service User, except in cases where an individual participant used MPS to join the conference with a higher user priority level, the higher user priority level is kept.
NOTE 7: The invocation of MPS for all participants may be done using a customized feature of a video conference service (available only to the host) that indicates a request for priority to the system. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.2.2.2 Revocation | The 3GPP system shall revoke MPS for the following cases:
• upon end of an MPS MMTEL video call, or an MPS MMTEL video conference call from a UE with an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal MMTEL video service),
• upon end of an MPS MMTEL video call, or an MPS MMTEL video conference call from a UE that does not have an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal video service), and
• upon end of an MPS MMTEL video conference call where MPS was provided to all participants on the video conference call, and the UEs shall return to normal conditions (i.e., use of normal MMTEL video service).
The 3GPP system shall revoke MPS for an individual participant leaving an ongoing MPS for MMTEL video conference where MPS is activated for all participants.
When an MPS MMTEL video call or an MPS MMTEL video conference call is not explicitly ended, upon UE detachment/deregistration (e.g., orderly power down), the 3GPP system in the RPLMN shall automatically revoke MPS such that MPS priority treatment shall not automatically apply to subsequent calls upon subsequent registration. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.2.3 Authentication and authorization | The system shall support means to authenticate and authorize an MPS MMTEL video or video conference call request from a UE with an MPS subscription.
The system shall support means to authenticate and authorize a Service User request for an MPS MMTEL video or video conference call from a UE that does not have an MPS subscription.
NOTE 1: The method for authenticating and authorizing the Service User using a UE that does not have an MPS subscription is predetermined. As part of the authentication and authorization process, the Service User provides MPS credentials (e.g., a calling card number, PIN or security token) specifically assigned for the purpose of obtaining MPS from a UE that does not have an MPS subscription.
The system shall support means for a visited PLMN, including a visited PLMN outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize an MPS for MMTEL video or video conference call.
NOTE 2: The method for authenticating and authorizing UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
The system shall support means to authenticate and authorize a Service User request to establish or upgrade all participants of an MMTEL video conference call to MPS priority. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.2.4 Signalling | The system shall provide priority treatment to the invocation signalling in the network once the request by the Service User for MPS for an MMTEL video or MMTEL video conference call is identified by the system.
The system shall support a means for MPS activation when normal MMTEL video service is congested at the request of the Service User.
The system shall provide priority treatment to the affected signalling when MPS is activated for an MMTEL video call, or MMTEL video conference call. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.2.5 Media | The system shall provide priority treatment to the audio and video media flows, when MPS is activated for an MMTEL video call or MMTEL video conference call.
The system shall support a means to differentiate the priority between the audio and video streams of a given MPS MMTEL video call.
The system shall support a means to differentiate the priority between the audio and video streams of MPS participants (Service Users) on an MMTEL video conference call.
The system shall retain the audio of an MPS for MMTEL video call or MMTEL video conference call when both the audio and video cannot be supported but the audio can be supported.
The system shall support priority re-establishment of the video media when an MPS MMTEL video call, or an MPS MMTEL video conference call, is in progress with only audio media and the conditions which previously blocked the video media are no longer applicable.
NOTE: This requirement does not imply the need to introduce a new IMS feature. It adds the need for priority treatment using the existing IMS feature for re-establishment of the video media. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.3 MPS for DTS | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.3.1 General | MPS for Data Transport Service (DTS) is a generic priority packet transport service that applies independently of the specific data application being used. It is a specific example of Priority Data Bearer Service described in clause 5.4a. MPS for DTS provides the Service User with priority for applications using the default bearer upon request (in the case of EPS), or QoS flow associated with the default QoS rule upon request (in the case of 5GS), to one or more selected active Packet Data Networks (PDNs)/Data Networks (DNs), in periods of severe network congestion during which normal commercial data service is degraded. MPS for DTS may also apply to other bearers (in the case of EPS) and other QoS Flows (in the case of 5GS) based on operator policy and regulatory rules.
NOTE 1: Service Data Flows (SDFs) previously mapped to the default bearer (in case of EPS) / QoS flow associated with the default QoS rule (in case of 5GS), are upgraded to MPS priority.
The system shall support:
- MPS for DTS for an authorized Service User using a UE with a subscription for MPS, and
NOTE 2: The MPS subscription related information is associated with the UE’s HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE, the UE’s membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
- MPS for DTS for an authorized Service User using a UE that does not have an MPS subscription.
NOTE 3: In this case, the Service User’s MPS subscription information (e.g., credentials) is not associated with the UE’s HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription..
MPS for DTS may be used to by a Service User to obtain priority access (e.g., Virtual Private Network (VPN) access) to an enterprise network (e.g., a private corporate network or private Government Agency network to download data and/or access enterprise applications such as email, text/chat/presence, voice and video).
The system shall support for an authorised Service User, an end-to-end MPS for DTS connection between the MPS subscribed UE and an associated enterprise network supporting MPS on demand based on operator policy and when agreements are in place for MPS.
NOTE 4: The end-to-end MPS for DTS connection between the UE and an associated enterprise network is supported either using a web browser (e.g., use of a predetermined address (i.e., URL) in a web browser) or using a user-selectable option provided as part of the VPN client in the UE with an MPS subscription.
MPS for DTS provides an IoT device with subscription to MPS with priority for applications using a specific default bearer (in the case of EPS), or default QoS flow (in the case of 5GS), towards a single specified PDN/DN;in the case of IoT connectivity to an enterprise, MPS also provides priority for the terminating access network (connected to the enterprise).
The system shall support:
- MPS for DTS for an authorized IoT device with a subscription for MPS, and
- an end-to-end MPS for DTS connection between the MPS subscribed IoT device and an associated enterprise network supporting MPS on demand based on operator policy when agreements are in place for MPS.
NOTE 5: An MPS specialized application on the MPS subscribed IoT device is used to support MPS for DTS through machine interactions that may not directly involve a human Service User.
An authorized enterprise network supporting MPS uses MPS for DTS to activate priority for remote MPS subscribed UEs and MPS subscribed IoT devices associated with the enterprise network based on operator policy when agreements are in place for MPS.
The system shall support:
- for an authorized enterprise network supporting MPS, activation of MPS for DTS for remote MPS subscribed UEs associated with the enterprise network on demand based on operator policy when agreements are in place for MPS, and
- for an authorized enterprise network supporting MPS, activation of MPS for DTS for remote MPS subscribed IoT devices associated with the enterprise network on demand based on operator policy when agreements are in place for MPS.
NOTE 6: MPS for DTS activation by an authorized enterprise network supporting MPS involves prearrangement and configuration (i.e., subscription arrangement identifying the enterprise network authorization for remote activation of DTS in IoT devices) within the MPS Service Provider PLMN. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.3.2 Invocation and revocation | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.3.2.1 Invocation | A Service User, using a UE with an MPS subscription, can invoke MPS for DTS to request priority, e.g., when the normal data session cannot be established, or to upgrade an already established normal data session to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to initiate MPS for a DTS session.
NOTE 1: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User using a web browser to enter a predetermined address such as an URL).
A Service User, using a UE with an MPS subscription, can invoke MPS to request priority during roaming, e.g., when the normal data sessions cannot be established, or to upgrade an already established normal data session to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to initiate MPS for DTS session when roaming within the home country and outside the home country.
NOTE 2: MPS for DTS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User using a web browser to enter a predetermined address such as an URL) recognized by the visited PLMN.
A Service User, using a UE that does not have an MPS subscription, can invoke MPS for DTS to request priority, e.g., when the normal data session cannot be established, or to upgrade an already established normal data session to MPS.
The system shall support means for a Service User using a UE that does not have a subscription for MPS to initiate MPS for DTS.
NOTE 3: MPS for DTS invocation using a UE that does not have an MPS subscription is done using a predetermined method (e.g., by the Service User use of a predetermine URL address) and is outside the scope of 3GPP.
A Service User, using a UE with an MPS subscription, can invoke MPS for DTS to obtain priority for Virtual Private Network (VPN) access to an enterprise network (e.g., a Government Agency private enterprise network), e.g., when normal data session cannot be established or is degraded.
The system shall support means for a Service User using a UE with an MPS subscription to initiate an MPS for DTS session to an associated enterprise network supporting MPS on demand based on operator policy and when agreements are in place for MPS.
NOTE 4: Invocation of MPS for DTS is done either using a web browser (e.g., use of a predetermined address (i.e., URL) in a web browser) or using a user-selectable option provided as part of the VPN client in the UE with an MPS subscription.
An IoT device with an MPS subscription can invoke MPS for DTS to request priority when normal data service is degraded.
The system shall support means for an IoT device with an MPS subscription to initiate an MPS for DTS session to an enterprise network supporting MPS.
NOTE 5: An MPS specialized application on the MPS subscribed IoT device is responsible for determining whether or not to invoke MPS for DTS in support of the data communication needs. The MPS specialized application allows invocation/revocation of the DTS through machine interactions that may not directly involve a human Service User.
An authorized enterprise network supporting MPS activates MPS for DTS to request priority for MPS subscribed UEs and MPS subscribed IoT devices associated with the enterprise network when normal data service is unacceptable.
The 3GPP system shall support means for an authorized enterprise network supporting MPS to request activation of MPS for DTS for the following cases:
- a specific MPS subscribed UE or IoT device, and
- a group of MPS subscribed UEs or IoT devices.
NOTE 6: MPS for DTS invocation done by the enterprise network supporting MPS involves prearrangement and configuration (i.e., subscription arrangement identifying the enterprise network authorization for remote activation of DTS in IoT devices) within the MPS Service Provider PLMN. For example, an MPS specialized application hosted in the enterprise network (e.g., IoT application server) may be responsible for determining whether or not to invoke MPS for DTS. The MPS specialized application allows invocation/revocation of the DTS through machine interactions that may not directly involve a human Service User.
The system shall support receiving and authenticating MPS for DTS invocation requests from authorized MPS Service Users via public non-3GPP networks.
NOTE 7: The intent of the above requirement is to allow an authorized MPS Service User to send a request via the Internet to establish an MPS for DTS session for one or more active PDNs/DNs of a UE.
The system shall support discovery and selection of active data connections upon receipt of an MPS for DTS invocation request by an authorized MPS Service User. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.3.2.2 Revocation | The system shall support means to release an MPS for DTS session for the cases:
- an MPS Service User using a UE with an MPS subscription,
- an MPS Service User using a UE that does not have an MPS subscription, and
- an IoT device with an MPS subscription.
The system shall support means for an authorized enterprise network supporting MPS to explicitly request to release an MPS for DTS session or group of MPS for DTS sessions while maintaining basic connectivity to the MPS subscribed UE(s) or IoT device(s).
The system shall support means for an MPS Service User to explicitly release an MPS for DTS session from a UE with an MPS subscription when roaming, including outside the home country.
If MPS for DTS is not explicitly revoked by the Service User or an IoT device, the system in the RPLMN shall automatically revoke MPS:
- upon UE detachment/deregistration (e.g., power down), or
- when all the connections pertaining to the MPS for DTS session are released (without explicit release of the MPS for DTS session).
The system shall automatically revoke MPS when the maximum allowed duration for an MPS for DTS session is reached. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.3.3 Authentication and authorization | The system shall support means to authenticate and authorize an MPS for DTS session request from a UE with an MPS subscription.
The system shall support means to authenticate and authorize a Service User request for an MPS for DTS session from a UE that does not have an MPS subscription.
NOTE 1: The method for authenticating and authorizing the Service User using a UE that does not have an MPS subscription is predetermined. As part of the authentication and authorization process, the Service User provides MPS credentials (e.g., PIN or security token) specifically assigned for the purpose of obtaining MPS from a UE that does not have an MPS subscription.
The system shall support means for a visited PLMN, including a visited PLMN outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize an MPS for DTS session.
NOTE 2: The method for authenticating and authorizing UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
The system shall support means to authenticate and authorize an MPS for DTS session request from an IoT device with an MPS subscription.
The system shall support means to authenticate and authorise an enterprise network supporting MPS requesting activation of MPS for DTS for the following cases:
- a specific MPS subscribed UE or IoT device, and
- a group of MPS subscribed UEs or IoT devices. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.3.4 Signalling | The system shall provide priority treatment to the invocation signalling in the network once the MPS for DTS request is identified by the system.
The system shall support a means for MPS for DTS activation when normal data service is congested. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.3.5 Media | The system shall provide priority treatment to the affected media flows when an MPS for DTS session is activated.
The system shall provide priority treatment to the affected media flows when MPS for DTS is activated for the connection between an MPS subscribed UE or IoT device and an associated enterprise network supporting MPS.
NOTE: Both the MPS subscribed UE or IoT device and the enterprise network must be served by the same PLMN. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.3.6 QoS | The system shall be capable of supporting a set of default QoS characteristics for an active MPS for DTS session.
The system shall be capable of verifying authorization for a requested QoS modification to an active MPS for DTS session.
The system shall be capable of making authorized QoS modifications in support of MPS for DTS for all media traffic supported via the default bearer (in the case of EPS), or the default QoS flow (in the case of 5GS).
The system shall support means to allow a Service User to request QoS modifications for an active MPS for DTS session.
The system shall support means to provide a Service User with an indication that a requested QoS modification of an active MPS for DTS session was successful. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.3.7 Security | The system shall support security capabilities to verify an enterprise network's authorization to request MPS for DTS activation. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.4 MPS for Messaging Services | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.4.1 General | MPS for Messaging provides priority for messaging services in periods of network congestion during which normal commercial messaging services are degraded.
The system shall support MPS priority for messaging services supported using IMS Messaging, SMS and/or MMS, or MSGin5G for an authorized Service User using a UE with a subscription for MPS.
NOTE 1: MPS for Messaging may make use of commercial messaging service offerings provided by the operator. However, the messaging service applications are not in scope.
NOTE 2: The MPS Service User might not know whether the messaging service is supported using IMS Messaging, SMS and/or MMS, or MSGin5G.
NOTE 3: SMS options in scope are SMS via NAS and SMS over IP (i.e., SMS over MAP and SMS over SGs are not in scope).
The system shall support MPS priority for messaging using SMS and/or MMS or MSGin5G for an authorized IoT device with a subscription for MPS.
NOTE 4: An MPS specialized application on the MPS subscribed IoT device is used to support MPS for Messaging through machine interactions that might not directly involve a human Service User. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.4.2 Invocation and revocation | |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.4.2.1 Invocation | A Service User using a UE with an MPS subscription can activate MPS for Messaging to request priority, e.g., when the normal messaging service is degraded.
The system shall support means for a Service User using a UE with an MPS subscription to activate MPS for Messaging.
NOTE 1: MPS for Messaging invocation is done using a predetermined method (e.g., by the Service User using a web browser to enter a predetermined address such as an URL or sending a message to the MPS operator to activate MPS for Messaging).
A Service User using a UE with an MPS subscription can invoke MPS for Messaging to request priority during roaming, e.g., when the normal messaging service is degraded.
The system shall support means for a Service User using a UE with an MPS subscription to activate MPS for Messaging when roaming within the home country and outside the home country.
NOTE 2: MPS for Messaging invocation is done using a predetermined method recognized by the visited PLMN.
An IoT device with an MPS subscription can invoke MPS for Messaging to request priority when normal messaging service is degraded.
The system shall support means for an authorized IoT device with an MPS subscription to activate MPS for Messaging.
NOTE 3: An MPS specialized application on the MPS subscribed IoT device is responsible for determining whether or not to invoke MPS for Messaging in support of the text communication needs. The MPS specialized application allows invocation/revocation of MPS for Messaging through machine interactions that might not directly involve a human Service User.
An authorized enterprise network supporting MPS activates MPS for Messaging to request priority for MPS subscribed UEs and MPS subscribed IoT devices associated with the enterprise network when normal messaging service is degraded.
The system shall support means for an authorized enterprise network supporting MPS to request activation of MPS for Messaging for the following cases:
- a specific MPS subscribed UE or MPS subscribed IoT device, and
- a group of MPS subscribed UEs or MPS subscribed IoT devices.
NOTE 4: MPS for Messaging invocation done by the enterprise network supporting MPS involves prearrangement and configuration (i.e., subscription arrangement identifying the enterprise network authorization for remote activation of MPS for Messaging) within the MPS Service Provider PLMN. For example, an MPS specialized application hosted in the enterprise network (e.g., IoT application server) might be responsible for determining whether or not to invoke MPS for Messaging. The MPS specialized application allows invocation/revocation of MPS for Messaging through machine interactions that might not directly involve a human Service User.
The system shall support receiving and authenticating MPS for Messaging invocation requests from authorized MPS Service Users using UEs with an MPS subscription and authorized IoT devices with an MPS subscription via public non-3GPP networks.
NOTE 4: The intent of the above requirement is to allow an authorized MPS Service User or authorized IoT device to send a request via the Internet to activate or enable MPS for Messaging.
Based on national/regional regulatory rules and operator policy, the system shall support means to activate:
- MPS for Messaging separately from MPS for DTS described in clause 9.2, or
- MPS for Messaging and MPS for DTS together.
NOTE 5: The intent of the above requirement is to allow the MPS Service Provider flexibility to activate/revoke MPS for Messaging and MPS for DTS separately or in combination. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.4.2.2 Revocation | The system shall support means to revoke MPS for Messaging for the cases:
- a Service User using a UE with an MPS subscription, and
- an IoT device with an MPS subscription.
The system shall support means for an authorized enterprise network supporting MPS to explicitly request to revoke MPS for Messaging for a individual or group of MPS subscribed UEs or MPS subscribed IoT devices while maintaining basic connectivity to the MPS subscribed UE(s) or MPS subscribed IoT device(s).
The system shall support means for a Service User to explicitly revoke MPS for Messaging from a UE with an MPS subscription when roaming, including outside the home country.
If MPS for Messaging is not explicitly revoked by the Service User or IoT device, the system in the RPLMN shall automatically revoke MPS upon UE detachment/deregistration (e.g., power down).
The system shall support means for an authorized IoT device with an MPS subscription to revoke MPS for Messaging.
The system shall automatically revoke MPS when the maximum allowed duration for MPS for Messaging is reached.
Based on national/regional regulatory rules and operator policy, the system shall support means to revoke:
- MPS for Messaging separately from MPS for DTS described in clause 9.2, or
- MPS for Messaging and MPS for DTS together.
NOTE 5: The intent of the above requirement is to allow the MPS Service Provider flexibility to activate/revoke MPS for Messaging and MPS for DTS separately or in combination. |
89ea20b01c703949b0169bf5d5287c1e | 22.153 | 9.4.3 Authentication and authorization | The system shall support means to authenticate and authorize an MPS for Messaging activation request from a UE with an MPS subscription.
The system shall support means for a visited PLMN, including a visited PLMN outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize MPS for Messaging.
NOTE 1: The MPS subscription related information is associated with the UE’s HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE, the UE’s membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
NOTE 2: The method for authenticating and authorizing a UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
The system shall support means to authenticate and authorize an MPS for Messaging activation request from an IoT device with an MPS subscription.
The system shall support means to authenticate and authorise an enterprise network that supports MPS when it requests activation of MPS for Messaging for the following cases:
- a specific MPS subscribed UE or MPS subscribed IoT device, and
- a group of MPS subscribed UEs or MPS subscribed IoT devices. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.