[{"name":"S2-2108290","title":"LS from BBF: Reply to your liaison S2-2106577","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, The following hopefully will bring some clarity to the questions raised in your liaison S2-2106577. Q1: The scenario we envision is that for a combined AGF-UPF, the combined AGF\/UPF will have local means of determining the MTU of the access link, and the 5G-RG will have the same information as a result of RFC 4638 procedures which we are documenting in issue 2 of TR-456. An FN-RG will typically default on the basis of protocol suite. In which case: - The N3 MTU is irrelevant in the downstream direction. So the combined AGF\/UPF can simply assume the locally determined access MTU is the value to use for downstream traffic. - The SMF advertised value in PCO to the 5G-RG is compared with the locally determined MTU of the access link, and the 5G-RG can use the lower of the two values as the actual constraint for upstream traffic without needing to know the serving AGF\/UPF deployment configuration. It can also use existing procedures to advertise this value to non-3GPP devices attached to the home network. This avoids the scenario where the N3 MTU imposes an unacceptable constraint when it is smaller than the access MTU and will be irrelevant for locally anchored PDU sessions. Local processing at the FN-RG or 5G-RG and combined AGF\/UPF can address the case where the N3 MTU is greater than the access MTU. This does require the SMF to have knowledge that the given PDU session will only ever be single access, and is served by a combined AGF\/UPF such that it may be locally configured to provide an appropriate MTU value. We suspect this could be achieved on the basis of selected DNN, or potentially by other means. We had anticipated the answer to Q2 and saw this as the most painless way forward in the near term to address the sensibilities of our operator community. Q2: We appreciated being advised of any developments in this area. Q3: The BBF desire to use an optional modifier to the GLI for specific FN-RG support cases will meet our needs and be transparent to 3GPP within the constraints outlined in your liaison reply. Q4: SA WG2's understanding that an FN-RG PPPoE session can only access a single DNN\/Slice is correct. We cannot envision a scenario whereby other than a 1:1 cardinality of PPPoE sessions to PDU sessions could be supported. Therefore a unique session per DNN\/Slice is required. We have documented procedures to extend FN-RG support to permit more than one IP session to be supported (corresponding to the same number of PDU sessions). Our use case would treat the realm portion of the NAI as the selected DNN, which we believe is aligned with TS23.003 clause 9. The username portion of the NAI is not used for this purpose. With this clarification, we reiterate our support for removing restrictions with respect to the simultaneous use of a DNN in both a URSP match descriptor and route selection descriptor. We understand this restriction has been removed, can you please confirm. Q5 & Q6: Noted. We look forward to continuing our fruitful relationship. Thanks, Lincoln Lavoie Broadband Forum Technical Committee Chair","secretary_remarks":"Response drafted in S2-2108362. Final response in S2-2109041","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11480,"status":"replied to","reservation_date":"2021-10-29 06:41:20","uploaded":"2021-10-29 07:49:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4","Cc":"CableLabs","lsoriginalls":"LIAISE-474","lsreply":"S2-2109041","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108290.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108299","title":"LS from BBF: EAP-5G changes","source":"BBF","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, During the course of our deliberations, we have come to realize that the use of EAP-5G over PPP for W-CP initiation is an unsuitable choice for 5G-RG support over wireline. The issue we have identified is that EAP over PPP does not provide a fragmentation mechanism, and previous liaisons have advised us that the wireline MTU will be inadequate to communicate some SUCI encodings without fragmentation and reassembly support. As such we have modified our call flows to initiate the VSNP procedures to establish reliable NAS transport with fragmentation and reassembly support earlier in the call flow sequence, and communicate the key elements of the EAP-5G exchange as part of W-CP initiation dialog within our framework of VSNP messaging. We note the above change will have a number of impacts on TS23.316. We will document the updated procedures in issue 2 of TR-456, which is currently in straw ballot. We look forward to continuing our fruitful relationship. Thanks, Lincoln Lavoie Broadband Forum Technical Committee Chair","secretary_remarks":"Response drafted in S2-2108363. Final response in S2-2109043","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11530,"status":"replied to","reservation_date":"2021-10-29 06:41:20","uploaded":"2021-11-09 13:10:37","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG4","Cc":"","lsoriginalls":"LIAISE-477","lsreply":"S2-2109043","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108299.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108361","title":"MTU value for wireline access","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that existing procedures for assigning MTU value applies also for wireline access, and that a suitable MTU value may be configured e.g. for a DNN used for only wireline access.","secretary_remarks":"r01 agreed. Revised to S2-2109042.","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11510,"status":"revised","reservation_date":"2021-11-06 15:37:01","uploaded":"2021-11-08 19:33:53","revisionof":"","revisedto":"S2-2109042","release":"Rel-17","crspec":23.316,"crspecversion":"17.1.0","workitem":[{"winame":"5WWC"}],"crnumber":2061.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108361.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108362","title":"[DRAFT] Reply LS on MTU and other topics","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This is a proposed reply to the BBF LS in (LIAISE-474 \/ S2-2108290)","secretary_remarks":"Response to S2-2108290. r00 agreed. Revised to S2-2109041.","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11490,"status":"revised","reservation_date":"2021-11-06 15:37:02","uploaded":"2021-11-08 19:33:53","revisionof":"","revisedto":"S2-2109041","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"CT WG4, Cablelabs","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108362.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108363","title":"[DRAFT] Reply LS on EAP-5G changes","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This is a proposed reply to the BBF LS in (LIAISE-477 \/ S2-2108299)","secretary_remarks":"Response to S2-2108299. r00 agreed. Revised to S2-2109043.","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11540,"status":"revised","reservation_date":"2021-11-06 15:37:02","uploaded":"2021-11-08 19:33:53","revisionof":"","revisedto":"S2-2109043","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"CT WG4, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108363.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108833","title":"Providing UE's address to AMF during registration via trusted Non-3GPP access","source":"Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Broadcom","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the N2 message sent in step 6b, the TNGF includes a 'null' IP address (e.g., 0.0.0.0). After the UE is assigned an IP address, the TNGF may include this address in a subsequent N2 message, e.g., in step 14.","secretary_remarks":"r01 agreed. Revised to S2-2109044.","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11560,"status":"revised","reservation_date":"2021-11-08 13:44:01","uploaded":"2021-11-08 15:02:31","revisionof":"","revisedto":"S2-2109044","release":"Rel-16","crspec":23.502,"crspecversion":"16.10.0","workitem":[{"winame":"5WWC"}],"crnumber":3294.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108833.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108848","title":"Providing UE's address to AMF during registration via trusted Non-3GPP access","source":"Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Broadcom","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: In the N2 message sent in step 6b, the TNGF includes a 'null' IP address (e.g., 0.0.0.0). After the UE is assigned an IP address, the TNGF may include this address in a subsequent N2 message, e.g., in step 14.","secretary_remarks":"r00 agreed. Revised to S2-2109045.","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11580,"status":"revised","reservation_date":"2021-11-08 14:01:57","uploaded":"2021-11-08 15:02:31","revisionof":"","revisedto":"S2-2109045","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"TEI17"},{"winame":" 5WWC"}],"crnumber":3295.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108848.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108929","title":"Applicability of ATSSS to 5G-RG in Rel-17","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Restrict the support of ATSSS by 5G-RG to Rel-16 version of specifications","secretary_remarks":"r01 agreed. Revised to S2-2109046.","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11600,"status":"revised","reservation_date":"2021-11-08 16:48:24","uploaded":"2021-11-08 17:14:19","revisionof":"","revisedto":"S2-2109046","release":"Rel-17","crspec":23.316,"crspecversion":"17.1.0","workitem":[{"winame":"5WWC"},{"winame":" ATSSS_Ph2"}],"crnumber":2062.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108929.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109041","title":"Reply LS on MTU and other topics","source":"SA WG2","contact":"Stefan Rommer","contact-id":25950,"tdoctype":"LS out","for":"Approval","abstract":"To: BBF. CC: CT WG4, Cablelabs. Attachment: TS 23.316 CR2061 (S2-2109042)","secretary_remarks":"Revision of S2-2108362r00. Approved","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11500,"status":"approved","reservation_date":"2021-11-22 09:35:15","uploaded":"2021-11-23 15:21:13","revisionof":"S2-2108362","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2108290","lsto":"BBF","Cc":"CT WG4, Cablelabs","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109041.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109042","title":"MTU value for wireline access","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that existing procedures for assigning MTU value applies also for wireline access, and that a suitable MTU value may be configured e.g. for a DNN used for only wireline access.","secretary_remarks":"Revision of S2-2108361r01. Approved","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11520,"status":"agreed","reservation_date":"2021-11-22 09:35:15","uploaded":"2021-11-23 15:21:13","revisionof":"S2-2108361","revisedto":"","release":"Rel-17","crspec":23.316,"crspecversion":"17.1.0","workitem":[{"winame":"5WWC"},{"winame":" TEI17"}],"crnumber":2061.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211304","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109042.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109043","title":"Reply LS on EAP-5G changes","source":"SA WG2","contact":"Stefan Rommer","contact-id":25950,"tdoctype":"LS out","for":"Approval","abstract":"To: BBF. CC: CT WG4, CT WG1","secretary_remarks":"Revision of S2-2108363r00. Approved","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11550,"status":"approved","reservation_date":"2021-11-22 09:35:16","uploaded":"2021-11-23 15:21:13","revisionof":"S2-2108363","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2108299","lsto":"BBF","Cc":"CT WG4, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109043.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109044","title":"Providing UE's address to AMF during registration via trusted Non-3GPP access","source":"Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Broadcom, Ericsson","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In the N2 message sent in step 6b, the TNGF includes a 'null' IP address (e.g., 0.0.0.0). After the UE is assigned an IP address, the TNGF may include this address in a subsequent N2 message, e.g., in step 14.","secretary_remarks":"Revision of S2-2108833r01. Approved","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11570,"status":"agreed","reservation_date":"2021-11-22 09:35:16","uploaded":"2021-11-23 15:21:13","revisionof":"S2-2108833","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.10.0","workitem":[{"winame":"5WWC"}],"crnumber":3294.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211274","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109044.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109045","title":"Providing UE's address to AMF during registration via trusted Non-3GPP access","source":"Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Broadcom, Ericsson","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Rel-17 mirror CR: Summary of change: In the N2 message sent in step 6b, the TNGF includes a 'null' IP address (e.g., 0.0.0.0). After the UE is assigned an IP address, the TNGF may include this address in a subsequent N2 message, e.g., in step 14.","secretary_remarks":"Revision of S2-2108848r00. Approved","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11590,"status":"agreed","reservation_date":"2021-11-22 09:35:18","uploaded":"2021-11-23 15:21:13","revisionof":"S2-2108848","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"5WWC"}],"crnumber":3295.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-211274","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109045.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109046","title":"Applicability of ATSSS to 5G-RG in Rel-17","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Restrict the support of ATSSS by 5G-RG to Rel-16 version of specifications when connect to NG RAN and to Rel-17 when conenct to EPC","secretary_remarks":"Revision of S2-2108929r01. Approved","agenda_item_sort_order":27,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11610,"status":"agreed","reservation_date":"2021-11-22 09:35:19","uploaded":"2021-11-23 15:21:13","revisionof":"S2-2108929","revisedto":"","release":"Rel-17","crspec":23.316,"crspecversion":"17.1.0","workitem":[{"winame":"5WWC"},{"winame":" ATSSS_Ph2"}],"crnumber":2062.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211288","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109046.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]