[{"name":"S2-2100187","title":"Support for Attestation for IMS priority sessions","source":"Ericsson, AT&T, T-Mobile USA, Perspecta Labs, CISA ECD, Nokia, Nokia Shanghai-Bell, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In addition to caller identity authentication\/verification that are to be now applied to priority calls, priority calls may also be subject to 'Resource-Priority' Header (RPH) signing and verifying as defined in RFC 8443. In these cases, the attestation is applied to the Resource-Priority information by the IMS entity responsible for authorizing and handling the IMS session. This enables the inclusion of cryptographically signed assertions for the values populated in the Session Initiation Protocol (SIP) 'Resource-Priority' header field, which is used for prioritization of communications resources. In the context of priority sessions, the S-CSCF, TAS, or another IMS AS should be capable of interacting with an Application Server (AS) that supports calling number and\/or Resource-Priority information authentication\/signing and may do so based on operator policy.","secretary_remarks":"Approved","agenda_item_sort_order":71,"ainumber":"8.17","ainame":"Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES)","tdoc_agenda_sort_order":23760,"status":"agreed","reservation_date":"2021-02-11 17:35:35","uploaded":"2021-02-18 16:35:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.228","crspecversion":"16.6.0","workitem":[{"winame":"TEI17_SAPES"}],"crnumber":1241.0,"crrevision":"","crcategory":"B","tsg_crp":"SP-210088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100187.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100188","title":"Support for Caller Identity Attestation and Assertion of Emergency sessions","source":"Ericsson, Nokia, Nokia Shanghai-Bell, AT&T, T-Mobile USA, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the case of emergency calls, it is proposed that the P-CSCF performs attestation for the calling identity. In addition, emergency calls may also be subject to Resource-Priority information signing as defined in RFC 8443. In this case, the attestation is applied to the Resource-Priority information by the IMS entity responsible for authorizing and handling the IMS session. This enables the inclusion of cryptographically signed assertions for the values populated in the Session Initiation Protocol (SIP) 'Resource-Priority' header field, which is used for prioritization of communications resources. When an emergency session is delivered to an emergency network outside the domain of the operator, the IBCF should be capable of interacting with an Application Server (AS) that supports calling number and\/or Resource-Priority information authentication\/signing, and may do so based on configured operator policy, once it determines that an emergency call is destined for a Next Generation Emergency Services Network. By the same token the IBCF should be able to invoke an AS for verification of signed Resource-Priority information if available in the incoming request.","secretary_remarks":"Approved","agenda_item_sort_order":71,"ainumber":"8.17","ainame":"Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES)","tdoc_agenda_sort_order":23770,"status":"agreed","reservation_date":"2021-02-11 17:35:36","uploaded":"2021-02-18 16:35:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.167","crspecversion":"16.3.0","workitem":[{"winame":"TEI17_SAPES"}],"crnumber":359.0,"crrevision":"","crcategory":"B","tsg_crp":"SP-210088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100188.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]