[{"name":"S2-2300033","title":"LS from CT WG4: LS on Enabling operators to deploy N32 purpose specific SEPPs","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 has agreed the attached CR enabling operators to deploy N32 purpose specific SEPPs in their networks, i.e. not requiring all SEPPs deployed in a PLMN (or SNPN) to support the same N32 purposes (e.g. roaming, SMS interconnect, disaster roaming, inter-PLMN mobility, SNPN interconnect). Note: N32 purposes are defined in clause 6.1.5.3.9 of TS 29.573. The N32 purpose of a request is signalled from NF\/SCP to a SEPP in the 3gpp-Sbi-Interplmn-Purpose header (see TS 29.500). SCPs (or NFs) of PLMNs deploying N32 purpose specific SEPPs would route their requests towards a local SEPP that supports the N32 purpose of the request and, as per existing requirements, that enables to reach the target PLMN. SCPs (or NFs) of PLMNs not deploying N32 purpose specific SEPPs would route their requests towards a local SEPP as per existing requirements, i.e. that enables to reach the target PLMN. The local SEPP would then send the request to a remote SEPP that supports the N32 purpose of the request, if the remote PLMN deploys N32 purpose specific SEPPs. CT WG4 noted that DNS procedures specified in GSMA IR.67 to discover a remote SEPP uses a well-known SEPP FQDN (sepp.5gc.mnc345.mcc012.3gppnetwork.org) 'unless specified and agreed otherwise', and that GSMA also considered the possibility to support discovering different SEPPs for different N32 purposes: 'Note: Multiple NAPTR record lines may be foreseen in the future. For example: one NAPTR record for roaming and one NAPTR record for (SMS) interworking.' CT WG4 kindly ask GSMA NG to confirm the need for enabling operators to deploy N32 purpose specific SEPPs. If so, CT WG4 kindly asks GSMA NG to provide feedback on the proposed solution if any, and to consider possibly defining DNS procedure extensions to enable the discovery of a remote SEPP supporting a specific N32 purpose, if appropriate.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10640,"status":"noted","reservation_date":"2022-12-19 08:34:55","uploaded":"2022-12-19 12:42:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG","Cc":"SA WG2","lsoriginalls":"C4-225493","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300033.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]