[{"name":"S2-2004775","title":"LS from BBF: Issue with FN-RG IPv6 support","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Action","abstract":"Dear colleagues, We have identified issues with IPv6 support for FN-RGs with respect to the currently specified behaviors of the 5G system. 1) Support for FN-RGs using IPv6oE procedures The current specification has the interface identifier used by a UE for construction of the IPv6 Link Local addresses (LLA) assigned by the SMF. FN-RGs that use the IPoE protocol suite for IPv6 support currently conform to IETF RFC 2464 for LLA assignment. A 2464 compliant FN-RG will self-assign an interface identifier expressed as an EUI-64 using the FN-RG's WAN interface MAC address as input. There is no means to explicitly override this with a network assigned value. We believe a potential (and perhaps the only possible) solution exists in the form of adding an optional field to the PDU Session Establishment Request that the W-AGF may or may not send. The field would be the 'suggested interface identifier' and carry an 8 byte EUI-64 as an argument. The W-AGF would encode the FN-RG MAC address as an EUI-64 in the request. If the SMF receives the 'suggested interface identifier' field, it will use that information in the construction of the LLA to use for the FN-RG for that PDU session. The SMF would have the opportunity to verify it was not a duplicate (and if so it was take local measures to circumvent the issue), and will echo that value back in the PDU Session Establishment Accept Message as per existing practice. Therefore, a means would exist to synchronize the LLA expected by the FN-RG and the LLA sent by the SMF. 2) Support for FN-RGs using PPPoE and IPv6CP procedures IETF RFC 5072 NCP negotiation procedures performed between the FN-RG and W-AGF require the AGF to know the SMF's link local address. Again, we believe a potential (and only possible solution) is that an information element be added to the PDU Session Establishment Accept message that provides this information to the W-AGF for use in RFC 5072 negotiation procedures. This would ensure reliable knowledge of the SMF LLA when the AGF performed IPv6CP negotiation procedures with the FN-RG. We assume the SMF LLA is invariant for the duration of the PDU session. Member companies will be submitting CRs more completely documenting this proposal. We would request they be given consideration. The impact of the lack of this solution would require that the W-AGF would have to be specified as a layer 3 node and perform extensive interworking between the SMF and an FN-RG for IPv6 procedures. We also would advise that with respect to DHCP support in the SMF, DHCPv4 and DHCPv6 messages will not be directly received from the FN-RGs or 5G-RGs, but will have transited one or more DHCP relays that will exist in the path taken by the PDU session traffic. We would like to understand what an SMF would accept from the point of view of addressing for a DHCPv4 DISCOVER or DHCPv6 SOLICIT message. For example whether the request is unicast or broadcast, and will it accept requests with relay options. We look forward to continuing our fruitful relationship. Thanks, Lincoln Lavoie, Broadband Forum Technical Committee Chair","secretary_remarks":"Revision of postponed S2-2003627 from S2#139E. Response drafted in S2-2004927. Final response in S2-2006205","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11590,"status":"replied to","reservation_date":"2020-08-04 05:43:45","uploaded":"2020-08-04 06:30:51","revisionof":"S2-2003627","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, CT WG3","Cc":"","lsoriginalls":"LIAISE-394","lsreply":"S2-2006205","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004775.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004815","title":"LS from BBF: Completion of WT-456 and WT-470","source":"BBF","contact":"Lincoln Lavoie","contact-id":39231,"tdoctype":"LS in","for":"Information","abstract":"Dear colleagues, We are pleased to attach the finalized versions of WT-456 'AGF Requirements' and WT-470 '5G WWC Architecture'. To be clear on our process, this is upon completion of comment resolution and editorial review by the WWC work area, but prior to final membership balloting, formal approval and publication. Review and comments are welcome, although any modifications to the document will not appear until the next revision. These two documents are part of the phase 1 of BBF WWC work, which is also expected to include updates to TR-124 (Functional Requirements for Broadband Residential Gateway Devices) and TR-181 (Device Data Model for TR-069) - these two specifications have started finalization process with comment resolution to take place at our Q3 meeting. We have a number of functional extensions and refinements to the WWC work planned for the remainder of the year and beyond, including some FFS items present in the attached WT documents. We look forward to continuing our fruitful relationship. Thanks, Lincoln Lavoie Broadband Forum Technical Committee Chair","secretary_remarks":"Postponed","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11580,"status":"postponed","reservation_date":"2020-08-04 05:43:46","uploaded":"2020-08-11 06:04:47","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, SA WG5, CT WG1, CT WG13, CT WG14, RAN WG3","Cc":"","lsoriginalls":"LIAISE-411","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004815.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004843","title":"5G-RG indicating over 5G NAS whether it supports ATSSS over EPC","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A 5G RG establishing a PDU Session over 5G NAS indicates whether it supports a PDN Connection acting as user-plane resource associated with this MA PDU Session.","secretary_remarks":"CC#2: This CR was postponed.","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11630,"status":"postponed","reservation_date":"2020-08-08 16:19:25","uploaded":"2020-08-13 08:04:47","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2047.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004843.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004926","title":"Handling of IPv6 addresses for FN-RG","source":"Ericsson, Telecom Italia, Nokia, Charter, Cablelabs","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - W-AGF can provide FN-RGs IPv6 LLA at PDU session establishment request message. - SMF can provide SMF IPv6 LLA in PDU session establishment accept message in case of Wireline access.","secretary_remarks":"Revision of (postponed) S2-2003685 from S2#139E. Approved","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11600,"status":"agreed","reservation_date":"2020-08-10 20:30:46","uploaded":"2020-08-13 19:26:42","revisionof":"S2-2003685","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2046.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200676","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004926.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004927","title":"[DRAFT] Reply LS on Issue with FN-RG IPv6 support","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This paper proposes a reply to the BBF LS on FN-RG IPv6 support","secretary_remarks":"Response to S2-2004775. Agreed. Revised to S2-2006205.","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11610,"status":"revised","reservation_date":"2020-08-10 20:30:48","uploaded":"2020-08-13 19:26:42","revisionof":"","revisedto":"S2-2006205","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"Cablelabs","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004927.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2004928","title":"Correction to the description of FN-RG Session Modification Procedure","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update text in 23.316.","secretary_remarks":"Approved","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11640,"status":"agreed","reservation_date":"2020-08-10 20:30:49","uploaded":"2020-08-13 19:26:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2048.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200676","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2004928.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005424","title":"Correcting UE Id in the Access Network parameters","source":"Lenovo, Motorola Mobility","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In step 5 of figure 4.12a.2.2-1, the '5G GUTI or SUCI' is deleted from the AN parameters. As the text mentions, the UE Id can be a 5G-GUTI or SUCI.","secretary_remarks":"Approved","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11650,"status":"agreed","reservation_date":"2020-08-13 08:33:38","uploaded":"2020-08-13 20:23:41","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5WWC"}],"crnumber":2364.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200676","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005424.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005426","title":"Selecting the authentication method for devices that do not support 5GC NAS over WLAN access","source":"Lenovo, Motorola Mobility, Broadcom","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During the initial registration for a N5CW device, the UDM receives an Authentication Method element, which indicates a preferred EAP authentication method. This Authentication Method element is provided from TWIF to AMF, then from AMF","secretary_remarks":"Noted","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11660,"status":"noted","reservation_date":"2020-08-13 08:36:19","uploaded":"2020-08-13 20:23:41","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5WWC"}],"crnumber":2365.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005426.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005525","title":"Adding emergency registration procedure for trusted non-3GPP access","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the UE has no SUPI and no valid 5G-GUTI, PEI shall be included instead of its encrypted Permanent User ID (SUCI) in the NAS message. step 21b instead of step 22b of figure 4.2.2.2.2-1 shall not be performed. The emergency registratio","secretary_remarks":"Approved","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11670,"status":"agreed","reservation_date":"2020-08-13 10:39:11","uploaded":"2020-08-13 12:18:33","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5WWC"}],"crnumber":2374.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200676","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005525.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005526","title":"Adding handover procedure between EPS and 5GC-TNGF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a clause to describe the handover procedures between EPS and 5GC-TNGF which includes the handover from EPS to 5GC-TNGF and the handover from 5GC-TNGF to EPS. The handover procedures can refer to the handover procedures between EP","secretary_remarks":"r04 agreed. Revised to S2-2006206","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11680,"status":"revised","reservation_date":"2020-08-13 10:39:13","uploaded":"2020-08-13 12:18:33","revisionof":"","revisedto":"S2-2006206","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5WWC"}],"crnumber":2375.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005526.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005527","title":"Clarification on Identifiers of N5CW devices","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the N5CW device has not registered to 5GC over 3GPP access when it registers to the 5GC via trusted WLAN, the NAI shall include the SUCI. The SUCI shall be constructed as specified in TS 33.501 [15] clause 6.12.2.","secretary_remarks":"r02 agreed. Revised to S2-2006207","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11700,"status":"revised","reservation_date":"2020-08-13 10:39:14","uploaded":"2020-08-13 12:18:33","revisionof":"","revisedto":"S2-2006207","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5WWC"}],"crnumber":2376.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005527.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2005528","title":"Correction on figure in 5WWC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the figure where the AN parameters contain GUAMI and Establishment Cause instead.","secretary_remarks":"r01 agreed. Revised to S2-2006208","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11720,"status":"revised","reservation_date":"2020-08-13 10:39:15","uploaded":"2020-08-13 12:18:33","revisionof":"","revisedto":"S2-2006208","release":"Rel-16","crspec":"23.316","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2049.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2005528.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006205","title":"Reply LS on Issue with FN-RG IPv6 support","source":"SA WG2","contact":"Stefan Rommer","contact-id":25950,"tdoctype":"LS out","for":"Approval","abstract":"To: BBF. CC: Cablelabs. Attachments: TS 23.316 CR2046","secretary_remarks":"Revision of S2-2004927. Approved","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11620,"status":"approved","reservation_date":"2020-08-31 14:28:37","uploaded":"2020-08-31 14:29:39","revisionof":"S2-2004927","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5WWC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2004775","lsto":"BBF","Cc":"Cablelabs","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006205.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006206","title":"Adding handover procedure between EPS and 5GC-TNGF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a clause to describe the handover procedures between EPS and 5GC-TNGF which includes the handover from EPS to 5GC-TNGF and the handover from 5GC-TNGF to EPS. The handover procedures can refer to the handover procedures between EP","secretary_remarks":"Revision r04 of S2-2005526. Approved","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11690,"status":"agreed","reservation_date":"2020-09-03 04:32:07","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2005526","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5WWC"}],"crnumber":2375.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200676","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006206.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006207","title":"Clarification on Identifiers of N5CW devices","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the N5CW device has not registered to 5GC over 3GPP access when it registers to the 5GC via trusted WLAN, the NAI shall include the SUCI. The SUCI shall be constructed as specified in TS 33.501 [15] clause 6.12.2.","secretary_remarks":"Revision r02 of S2-2005527. Approved","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11710,"status":"agreed","reservation_date":"2020-09-03 04:32:08","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2005527","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.5.1","workitem":[{"winame":"5WWC"}],"crnumber":2376.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200676","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006207.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2006208","title":"Correction on figure in 5WWC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the figure where the AN parameters contain GUAMI and Establishment Cause instead.","secretary_remarks":"Revision r01 of S2-2005528. Approved","agenda_item_sort_order":13,"ainumber":"7.2","ainame":"Wireless and Wireline Convergence for the 5G system architecture (5WWC)","tdoc_agenda_sort_order":11730,"status":"agreed","reservation_date":"2020-09-03 04:32:10","uploaded":"2020-09-03 15:01:14","revisionof":"S2-2005528","revisedto":"","release":"Rel-16","crspec":"23.316","crspecversion":"16.4.0","workitem":[{"winame":"5WWC"}],"crnumber":2049.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200676","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_140e_Electronic\/Docs\/S2-2006208.zip","group":"S2","meeting":"S2-140-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]