[{"name":"S2-2203642","title":"LS from CT WG3: LS on handling of FQDN ranges in AF influence on traffic routing procedures","source":"CT WG3","contact":"Susana Fernandez","contact-id":42321,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is discussing the support of FQDN ranges as defined in TS 23.501 for AF influence on traffic routing procedures. According to that TS the FQDN range is considered one example of traffic filtering information and when provided, 'it may be used by SMF as one of the triggers for retrieving EAS Deployment Information from NEF. Retrieval of EAS Deployment Information is defined in TS 23.548 [130]'. CT WG3 has the following questions: Question 1: Is the FQDN range only used as a trigger to initiate the retrieval of EAS Deployment Information from NEF or is it also used to identify the traffic for influencing SMF routing decisions? Question 2: If it is used to identify the traffic for influencing SMF routing decisions, can SA WG2 clarify how it works? Is the FQDN range(s) used to identify the sessions\/users for which the EDIs apply, and if yes, how is this applicability exactly determined? Question 3: If it is only used as a trigger for the retrieval of EAS Deployment Information, why an FQDN range is required? Could a specific indicator or the application identifier included to identify the traffic satisfy the same purpose?. Action: CT WG3 kindly requests SA WG2 to answer the questions above and update their Specifications if considered necessary.","secretary_remarks":"Responses drafted in S2-2203880, S2-2204407. Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11760,"status":"postponed","reservation_date":"2022-04-21 14:48:20","uploaded":"2022-04-22 05:13:38","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-222419","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_151E_Electronic_2022-05\/Docs\/S2-2203642.zip","group":"S2","meeting":"S2-151-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]