hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.4 Procedures at the UA | An application server acting as a UA that supports this extension and receives a request or response destined for the served user containing an SDP offer or answer may insert a Resource-Share header field prior to forwarding the request or response. The value of the header field set to "media-sharing" or "no-media-shar... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.5 Procedures at the proxy | When a P-CSCF supporting this extension receives a REGISTER request from a served UE, the P-CSCF may insert a Resource-Share header field prior to forwarding the REGISTER request. The value of the header field is then set to "supported".
When the P-CSCF receives an SDP offer or answer from the served UE in a subsequent... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.6 Security considerations | The Resource-Share header field does not contain any information that can disclose user information or the topology of nodes within an operator network. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.7 Syntax | The syntax for Resource-Share header field is specified in table 7.2.13.1
Table 7.2.13.1: Syntax of Resource-Share
resource-share = "Resource-Share" HCOLON r-s-param
r-s-param = r-s-supported / r-s-no-media-sharing / r-s-media-sharing / r-s-other
r-s-supported = "supported" [SEMI origin] *(SEMI generic-param)
r-s-no-me... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.8 Operation | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.8.1 General | The values in the "resource-share" header field field are defined as follows:
"supported" indicates that the sender would like to receive information about resource sharing options for sessions involving the UE identified by the "+sip.instance" header field parameter in the Contact header field.
"media-sharing" indicat... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.8.2 The "origin" header field parameter | The "origin" header field parameter is used to identify the source of the resource sharing information. The values in the "origin" header field field are defined as follows:
"session-initiator" indicates that the application server or the P-CSCF that included the Resource-Share header field is serving the UE sending th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.8.3 The "rules" header field parameter | The "rules" header field parameter carries one or more rules for resource sharing. Each rule is included in the same order as the corresponding m-line in the SDP offer/answer and consists of the following parts:
"new-sharing-key" this part is mandatory and identifies a media stream in an exisiting ongoing session or is... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.8.4 The "timestamp" header field parameter | The "timestamp" header field parameter indicates when the application server determined the resource sharing rules and is used to determine the most applicable resource sharing option.
NOTE: Since the media streams in several sessions can be shared race conditions can occur due to retransimissions of requests or respon... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.9 Examples of usage | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.9.1 Example overview | The following subclauses describe examples on how:
- the P-CSCF indicates in the REGISTER request that P-CSCF supports receiving information about resource sharing;
- the application server sends information about potential resource sharing to the P-CSCF; and
- the P-CSCF extracts resource sharing information for media... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.9.2 The P-CSCF indicates in the REGISTER request that P-CSCF supports receiving information about resource sharing | When P-CSCF receives a REGISTER request from a UE served by the P-CSCF, the P-CSCF can include a Resource-Share header field indicating that the P-CSCF supports receiving information about resource sharing.
The example 1 shows the coding when the P-CSCF indicates that the P-CSCF is interested in receiving information a... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.9.3 The application server sends information about potential resource sharing to the P-CSCF | When the application server receives a request or response containing an initial SDP offer/answer with media streams subject for resource sharing, the application server includes the Resource-Share header field with the value "media-sharing" and includes a "origin" header field parameter set to "session-initiator" or "... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.13.9.4 The P-CSCF extracts resource sharing information for media-streams | When the P-CSCF receives an initial SDP answer destined for the served UE in a request or response containing the Resource-Share header field, the P-CSCF extracts the resource sharing rules for each media stream from the "rules" header field parameter in the same order that the corresponding m-line appear in the SDP. T... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.14 Definition of Service-Interact-Info header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.14.1 Introduction | IANA registry: Header Field Parameter Registry for the Session Initiation Protocol (SIP)
Header field name: Service-Interact-Info
Usage: The Service Interact-Infor header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.14.2 Applicability statement for the Service-Interact-Info header field | The Service-Interact-Info header field is applicable within a trust domain. The Service-Interact-Info header field can be included in initial SIP requests and responses to initial SIP requests.
AS can include the service identity which has been executed into the Service-Interact-Info header field and also insert servic... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.14.3 Usage of the Service-Interact-Info header field | Upon receiving a SIP message and executing service logic, the AS should take the information contained in the Service-Interact-Info header field into account. If
1) the executed services indicated in the Service-Interact-Info header field is in conflict with the local service logic; or
2) the local service logic indica... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.14.4 Procedures at the UA | There are no specific procedures specified for a UA. A UAC in a B2BUA can add a Service-Interact-Info header field into the SIP message, or insert a service identity into the Service-Interact-Info header field, or remove the Service-Interact-Info header field when sending a SIP message |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.14.5 Procedures at the proxy | A SIP proxy that supports this extension can add a Service-Interact-Info header field into a SIP message, insert a service identity into the Service-Interact-Info header field, or remove the Service-Interact-Info header field when forwarding the SIP message. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.14.6 Security considerations | The Service-Interact-Info header field can contain sensitive information. The Service-Interact-Info header field should be removed when sent outside the trust domain.
A UE is not expected to receive the Service-Interact-Info header field. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.14.7 Syntax | The syntax for Service-Interact-Info header field is specified in table 7.2.14-1.
Table 7.2.14-1: Syntax of Service-Interact-Info
Service-Interact-Info = "Service-Interact-Info" HCOLON executed-service-params*(COMMA executed-service-params)
executed-service-params = executed-service / avoid-service
executed-service = "... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.15 Definition of Cellular-Network-Info header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.15.1 Introduction | A User Agent (UA) supporting one or more cellular radio access technology (e.g. E-UTRAN) but using a non-cellular IP-CAN to access the IM CN subsystem can use this header field to relay information to its service provider about the radio cell identity of the cellular radio access network the UE most recently camped on.... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.15.2 Applicability statement for the Cellular-Network-Info header field | The Cellular-Network-Info field is applicable within a trust domain. The Cellular-Network-Info header field can be included in any SIP requests and responses in which the P-Access-Network-Info header field is present. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.15.3 Usage of the Cellular-Network-Info header field | The Cellular-Network-Info header field is populated with the following contents:
1) the access-type field is set to one of "3GPP-GERAN","3GPP-UTRAN-FDD", "3GPP-UTRAN-TDD", "3GPP-E-UTRAN-FDD", "3GPP-E-UTRAN-TDD", "3GPP-E-UTRAN-ProSe-UNR", "3GPP-NR-FDD", "3GPP-NR-TDD", "3GPP-NR-U-FDD", "3GPP-NR-U-TDD", "3GPP-NR-ProSe-L2U... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.15.4 Procedures at the UA | A UA that supports this extension and is willing to disclose the related parameters may insert the Cellular-Network-Info header field in any SIP request or response in which the P-Access-Network-Info header field is allowed to be present. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.15.5 Procedures at the proxy | A SIP proxy shall not modify the value of the Cellular-Network-Info header field.
A SIP proxy shall remove the Cellular-Network-Info header field when the SIP signaling is forwarded to a SIP server located in an untrusted administrative network domain.
A SIP proxy that is providing services to the UA, can act upon the ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.15.6 Security considerations | The Cellular-Network-Info header field contains sensitive information. The Cellular-Network-Info header field should be removed when sent outside the trust domain.
A UE is not expected to receive the Cellular-Network-Info header field. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.15.7 Syntax | The syntax for Cellular-Network-Info header field is specified in table 7.2.15-1.
Table 7.2.15-1: Syntax of Cellular-Network-Info
Cellular-Network-Info = "Cellular-Network-Info" HCOLON cellular-net-spec
cellular-net-spec = access-type *(SEMI cellular-access-info)
access-type = "3GPP-GERAN" / "3GPP-UTRAN-FDD" / "3GPP-UT... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.16 Priority-Share header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.16.1 Introduction | IANA registry: Header Field Parameter Registry for the Session Initiation Protocol (SIP)
Header field name: Priority-Share
Usage: The Priority-Share header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/
The Prior... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.16.2 Applicability statement for the Priority-Share header field | The Priority-Share header field is applicable within a single private administrative domain or between different administrative domains where there is a trust relationship between the domains.
The Priority-Share header field is not included in a SIP message sent to another network if there is no trust relationship.
The... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.16.3 Usage of the Priority-Share header field | A SIP UA or SIP proxy that receives a SIP request or response that contains a Priority-Share header field can use the values as appropriate.
A SIP proxy may remove the Priority-Share header field according to local policy. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.16.4 Procedures at the UA | An application server acting as a UA that supports this extension and receives a request or response without the Priority-Share header field may insert a Priority-Share header field prior to forwarding the message. The header is populated as described in subclause 7.2.16.7.
If an application server acting as a UA that ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.16.5 Procedures at the proxy | A SIP proxy that supports this extension and receives a request or response without the Priority-Share header field may insert a Priority-Share header field prior to forwarding the message. The header is populated as described in subclause 7.2.16.7.
If a proxy that supports this extension receives a request or response... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.16.6 Security considerations | The Priority-Share header field does not contain any information that can disclose user information or the topology of nodes within an operator network. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.16.7 Syntax | The syntax for Priority-Share header field is specified in table 7.2.16.1
Table 7.2.16.1: Syntax of Priority-Share
priority-share = "Priority-Share" HCOLON priority-share-options *( SEMI generic-param)
priority-share-options = "allowed" / "not-allowed" / other-options
other-options = token |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.16.8 Examples of usage | The Priority-Share header field is included by an application server in the home network to inform about the possibility to share resources between session regardless of the priority of a session. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.17 Definition of Response-Source header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.17.1 Introduction | IANA registry: Header Fields registry for the Session Initiation Protocol (SIP)
Header field name: Response-Source
Usage: the Response-Source header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/
The Response-Sou... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.17.2 Applicability statement for the Response-Source header field | The Response-Source header field is applicable within a single private administrative domain or between different administrative domains where there is a trust relationship between the domains. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.17.3 Usage of the Response-Source header field | A SIP UA or SIP proxy may include the Response-Source header field when responding to a SIP request with an error response to provide the information on who is the sender of the error response using the appropriate URN value as defined in subclause 7.2.17.7.
A SIP UA or SIP proxy that receives a SIP response that conta... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.17.4 Procedures at the UA | A UA that supports this extension and rejects a request with an error response may insert a Response-Source header field within the response message. The header is populated as described in subclause 7.2.17.7.
If a UA that supports this extension receives a response with the Response-Source header field, it may take th... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.17.5 Procedures at the proxy | A proxy that supports this extension and receives a request for which its internal logic leads to reject the request with an error response may insert a Response-Source header field within the response message. The header is populated as described in subclause 7.2.17.7.
If a proxy that supports this extension receives ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.17.6 Security considerations | The Response-Source header field will contain a URN identifying the sender that may be considered as sensitive information. The Response-Source header field may be removed when received from outside the trust domain depending on the network policy. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.17.7 Syntax | The ABNF syntax for Response-Source header field is specified in table 7.2.17.7-1.
Table 7.2.17.7-1: Syntax of Response-Source header field
Response-Source = "Response-Source" HCOLON source-info
source-info = source-params *(SEMI source-params)
source-params = source-urn / token
source-urn = "fe" EQUAL LAQUOT source-ur... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.18 Definition of Attestation-Info header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.18.1 Introduction | IANA registry: Header Fields registry for the Session Initiation Protocol (SIP)
Header field name: Attestation-Info
Usage: The Attestation-Info header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/
When a node ha... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.18.2 Applicability statement for the Attestation-Info header field | The Attestation-Info header field is applicable within a single private administrative domain or between different administrative domains.
The Attestation-Info header field is applicable when:
1) a node has performed attestation of an identity in an incoming request; or
2) has performed gateway attestation of the reque... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.18.3 Usage of the Attestation-Info header field | A node in the originating network attesting the identity of the originating user can add an Attestation-Info header field to inform what relation the network has with the originating user. A node at a border of a network can add an identifier identifying from where the request was received. The Attestation-Info header ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.18.4 Procedures at the UA | There are no specific procedures specified for a UA. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.18.5 Procedures at the proxy | A SIP proxy that supports this extension and receives a request may as part of its procedures insert an Attestation-Info header field prior to forwarding the request. The header field is populated with a value as specified in Table 7.2.18-1. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.18.6 Security considerations | The Attestation-Info header field does not contain any sensitive information.
A UE is not expected to receive this information. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.18.7 Syntax | The syntax for Attestation-Info header field is specified in table 7.2.18-1.
Table 7.2.18-1: Syntax of Attestation-Info
Attestation-Info = "Attestation-Info" HCOLON attestation-level / generic-param
attestation-level = ("A" / "B" / "C")
The meaning of the values "A", "B" and "C" is as defined in RFC 8588 [261] and refe... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.18.8 Examples of usage | A node in the originating network, such as a 3GPP S-CSCF or an application server, can when attesting the identity of an originating user insert an Attestation-Info header field to provide information on the relation the network has to the originating user. This information can be used when inserting an Identity header... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.19 Definition of Origination-Id header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.19.1 Introduction | IANA registry: Header Fields registry for the Session Initiation Protocol (SIP)
Header field name: Origination-Id
Usage: The Origination-Id header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/
When a node has pe... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.19.2 Applicability statement for the Origination-Id header field | The Origination-Id header field is applicable within a single private administrative domain or between different administrative domains.
The Origination-Id header field is applicable when:
1) a node has performed attestation of an identity in an incoming request; or
2) has performed gateway attestation of the request i... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.19.3 Usage of the Origination-Id header field | A node in the originating network attesting the identity of the originating user can add an Origination-Id header field to identify the node that performed the identity attestation. This value is based on local configuration and regulation. A node at a border of a network can add an Origination-Id header field with a u... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.19.4 Procedures at the UA | There are no specific procedures specified for a UA. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.19.5 Procedures at the proxy | A SIP proxy that supports this extension and receives a request may as part of its procedures insert an Origination-ID header field prior to forwarding the request. The header field is populated with a value as specified in Table 7.2.19-1. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.19.6 Security considerations | The Origination-Id header field can contain a unique value identifying a specific node in the network. A network operator may want to remove this information before transporting to an utrusted entity.
A UE is not expected to receive this information. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.19.7 Syntax | The syntax for Origination-Id header field is specified in table 7.2.19-1.
Table 7.2.19-1: Syntax of Origination-Id
Origination-Id = "Origination-Id" HCOLON originator / token
originator = UUID
The format of the UUID is as defined as in RFC 4122. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.19.8 Examples of usage | A node in the originating network, such as a 3GPP S-CSCF or an application server, can when attesting the identity of an originating user insert an Origination-Id header field to provide information on who attested the identity of the originating user. This information can be used when inserting an Identity header fiel... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.20 Definition of Additional-Identity header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.20.1 Introduction | IANA registry: Header Fields registry for the Session Initiation Protocol (SIP)
Header field name: Additional-Identity
Usage: The Additional-Identity header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/
The Addi... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.20.2 Applicability statement for the Additional-Identity header field | The Additional-Identity header field is applicable within a single private administrative domain or between different administrative domains.
The Additional-Identity header field is applicable when:
- an originating UA wants to indicate the identity to be used as an originating identity in a multi-identity service;
- a... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.20.3 Usage of the Additional-Identity header field | A SIP UA or SIP proxy may include the Additional-Identity header field to indicate:
- in the originating network, the identity to be used for originating requests when the originating user is subscribed to the multi-identity service; and
- in the terminating network, the identity to which the terminating user is contac... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.20.4 Procedures at the UA | A SIP UA that supports this extension may as part of its procedures insert the Additional-Identity header field prior to sending the request. The header field is populated with a value as specified in table 7.2.20.7-1. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.20.5 Procedures at the proxy | A SIP proxy that supports this extension and receives a request may as part of its procedures insert an Additional-Identity header field prior to forwarding the request. The header field is populated with a value as specified in table 7.2.20.7-1. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.20.6 Security considerations | Within a 3GPP environment, the Additional-Identity header field is exchanged between a SIP UA and a SIP proxy in the same network. The Additional-Identity header field may also be exchanged between networks when there is a trust relationship for the Additional-Identity header field.
A functional entity at the boundary ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.20.7 Syntax | The syntax for Additional-Identity header field is specified in table 7.2.20.7-1.
Table 7.2.20.7-1: Syntax of the Additional-Identity Header Field
Additional-Identity = "Additional-Identity" HCOLON id-spec / token
id-spec = name-addr *(SEMI (id-param))
id-param = generic-param |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.20.8 Examples of usage | A node in the originating network, such as a UA, can use the Additional-Identity header field to provide to a multi-identity service the information about which identity of the originating user is to be used for this originating request.
A node in the terminating network, such as an application server, when performing ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.21 Definition of Priority-Verstat header field | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.21.1 Introduction | IANA registry: Header Fields registry for the Session Initiation Protocol (SIP)
Header field name: Priority-Verstat
Usage: The Priority-Verstat header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/
When a node ha... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.21.2 Applicability statement for the Priority-Verstat header field | The Priority-Verstat header field is applicable within a single private administrative domain or between different administrative domains.
The Priority-Verstat header field is applicable when a node has performed authentication of a Resource-Priority header field and a header field value "psap-callback" of a Priority h... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.21.3 Usage of the Priority-Verstat header field | The Priority-Verstat header field is used to indicate the verification status of the Resource-Priority header field and optionally the header field value "psap-callback" of the Priority header field. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.21.4 Procedures at the UA | There are no specific procedures specified for a UA. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.21.5 Procedures at the proxy | A SIP proxy that supports this extension and receives a request may as part of its procedures insert a Priority-Verstat header field prior to forwarding the request. The header field is populated as specified in table 7.2.21-1. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.21.6 Security considerations | A UE is not expected to receive this information. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.21.7 Syntax | The syntax for Priority-Verstat header field is specified in table 7.2.21-1.
Table 7.2.21-1: Syntax of Priority-Verstat
Priority-Verstat = "Priority-Verstat" HCOLON verstat-value
verstat-value = "RPH-Validation-Passed" / "RPH-Validation-Failed" / "No-RPH-Validation" /
"ECB-RPH-Validation-Passed" / "ECB-RPH-Validation-F... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.21.8 Examples of usage | The Priority-Verstat header field is used in networks which have requirements on authentication of a Resource-Priority header field and a header field value "psap-callback" of a Priority header field to authenticate content of the Resource-Priority header field and the header field value "psap-callback" of the Priority... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.22 Definition of Handover-Info header field | Editor's note: [WI: TEI18, CR 6585] as per RFC 5727 an IETF expert review is needed in order to obtain the IANA registration of this header field. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.22.1 Introduction | IANA registry: Header Fields registry for the Session Initiation Protocol (SIP)
Header field name: Handover-Info
Usage: The Handover-Info header field is used only for informative purposes.
Header field specification reference: 3GPP TS 24.229, http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/
The Handover-Info he... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.22.2 Applicability statement for the Handover-Info header field | The Handover-Info header field is applicable within a single private administrative domain. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.22.3 Usage of the Handover-Info header field | The Handover-Info header field is used to indicate that the UE needs to be re-authenticated using mechanisms defined in 3GPP TS 24.229, and to inform when a re-authentication of a UE entering the mobile network has been completed. The Handover-Info header field can be used to inform the UE of the role in a call, fulfil... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.22.4 Procedures at the UA | There are no specific procedures specified for a UA. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.22.5 Procedures at the proxy | A SIP proxy that supports this extension and receives a request may as part of its procedures insert a Handover-Info header field prior to forwarding the request. The header field is populated as specified in table 7.2.22-1. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.22.6 Security considerations | The header field when reaching a UE only contains information of whether the UE initiated or terminated the call which does not have any security or privacy impacts. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.22.7 Syntax | The syntax for Handover-Info header field is specified in table 7.2.22-1.
Table 7.2.22-1: Syntax of Handover-Info
Handover-Info = "Handover-Info" HCOLON info-element / role
info-element = "authentication-needed" / "handover-completed" /
other-value
role = "Role" EQUAL "session-initiator" / "session-receiver"
other-valu... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.2.22.8 Examples of usage | The Handover-Info header field is used in networks where UEs can roam into other networks but where the SIP core nodes are located in the home network. The header field is used to inform the core nodes in the home network that a re-authentication of the UE is needed. The home network can further use the header field to... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.3 Option-tags defined within the present document | There are no option-tags defined within the present document over and above those defined in the referenced IETF specifications. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.4 Status-codes defined within the present document | There are no status-codes defined within the present document over and above those defined in the referenced IETF specifications. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.5 Session description types defined within the present document | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.5.1 General | This subclause contains definitions for SDP parameters that are specific to SDP usage in the 3GPP IM CN Subsystem and therefore are not described in an RFC. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.5.2 End-to-access-edge media plane security | |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.5.2.1 General | The end-to-access-edge media security-indicator is used to indicate that a UE requests a P-CSCF to apply media plane security or to indicate that a P-CSCF has applied end-to-access-edge media security as defined in 3GPP TS 33.328 [19C]. |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.5.2.2 Syntax | 3GPP end-to-access-edge media security indicator is a value attribute which is encoded as a media-level SDP attribute with the ABNF syntax defined in table 7.5.1. ABNF is defined in RFC 2234 [20G].
Table 7.5.1: ABNF syntax of 3ge2ae attribute
3ge2ae-attribute = "a=3ge2ae:" indicator
indicator = "requested" / "applied" ... |
d3a3ac3f64ab68e4fcef5ea9a665f70a | 24.229 | 7.5.2.3 IANA registration | NOTE: This subclause contains information to be provided to IANA for the registration of the end-to-access-edge security indicator SDP attribute.
Contact name, email address, and telephone number:
3GPP Specifications Manager
3gppContact@etsi.org
+33 (0)492944200
Attribute Name (as it will appear in SDP)
3ge2ae
Long-for... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.