[{"name":"C4-181180","title":"LS on a potential USIM solution for PLMN and RAT selection policies for roaming","source":"CT6","contact":"Tim P. Evans","contact-id":24416,"tdoctype":"LS in","for":"Discussion","abstract":"CT6 would like to indicate that the existing mechanism for USIM OTA (defined in TS 31.115 and TS 31.116) and that provides integrity protection, cyphering and replay protection, is a generic protocol that can be adapted to many transports.The USIM OTA also allows the operator to immediately send a REFRESH command for steering of roaming (see TS 31.111) to trigger the steering of roaming procedure. CT6 would be happy to work with the relevant groups to extend the OTA transport to the control plane, if this becomes a requirement.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-15 11:45:16","uploaded":"2018-01-15 12:31:20","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, SA3, CT1, CT4","Cc":"SA1","lsoriginalls":"C6-170696","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181180.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181181","title":"LS on interworking between networks with different 5G deployments options in a roaming scenario","source":"GSMA NG SIGNAL","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"LS was discussed as C4-176230, noted and reply LS was sent in Reno meeting.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"withdrawn","reservation_date":"2018-01-15 11:49:10","uploaded":"2018-01-15 12:31:20","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, CT4","Cc":"","lsoriginalls":"LS on Interworking between networks with different 5G deployments options in a roaming scenario","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181181.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181182","title":"LS on a new GTP-U extension header","source":"RAN3","contact":"Nianshan Shi","contact-id":45408,"tdoctype":"LS in","for":"Discussion","abstract":"RAN3 would like to inform CT4 that RAN3 has agreed to specify one new NR RAN container for the unified NR user plane (including X2 for EN-DC, Xn and F1).\nThe new NR RAN container, carried in the GTP-U header extension shall contain the NR user plane protocols for flow control.\nThis requires the addition of a new NR RAN Container in GTP-U Definition of Extension Header Type","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-15 11:51:23","uploaded":"2018-01-15 12:31:20","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"NR_newRAT-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"R3-175029","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181182.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181183","title":"LS on the number of data bearers","source":"RAN","contact":"Alexander Sayenko","contact-id":47308,"tdoctype":"LS in","for":"Information","abstract":"TSG RAN received several LS documents \u2013 from RAN WG2, CT WG1, CT WG4 and SA WG2 \u2013 regarding the feasibility of having extended number of data bearers for LTE. Following the preference from SA WG2, TSG RAN will initiate the normative work to support 15 data bearers in LTE with the target completion date of June 2018.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-15 11:54:10","uploaded":"2018-01-15 12:31:20","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"RP-172149 (from RAN WG2), RP-172154 (from CT WG1), RP-172164 (from CT WG4), RP-172163 (from SA WG2)","lsto":"SA, CT","Cc":"RAN2, RAN3, SA2, CT1, CT4","lsoriginalls":"RP-172836","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181183.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181184","title":"LS on Removal of 'over LTE' limitation from Mission Critical Specifications","source":"SA1","contact":"Kees Verweij","contact-id":12756,"tdoctype":"LS in","for":"Discussion","abstract":"3GPP SA1 would like to inform SA2, SA3, SA4, SA5, SA6, CT1, CT3, CT4, CT6, RAN1, RAN2, RAN3, RAN4, RAN5 and RAN6 that SA1 has agreed on the attached CRs that \n-\tchange the titles of the stage 1 specifications for Mission Critical Services, removing \"over LTE\"; and\n-\tapply related updates to the wording in the specifications to clarify that the requirements are applicable from LTE onwards.\nThe background of the changes is that Mission Critical user organisations intend to take advantage of the continuous evolution of 3GPP systems while enhancing MC Services, i.e. MCPTT, MCVideo and MCData, and adding new mission critical services over such continuously evolving 3GPP systems. The changes in the attached CRs should make it clear that the requirements specified in 3GPP stage 1 Technical Specifications of MC Services are not restricted to LTE.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-15 11:56:45","uploaded":"2018-01-15 12:31:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"MCOver"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, SA3, SA4, SA5, SA6, CT1, CT3, CT4, CT6, RAN1, RAN2, RAN3, RAN4, RAN5, RAN6","Cc":"SA, CT, RAN","lsoriginalls":"S1-174542","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181184.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181187","title":"Response to LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast","source":"SA2","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 kindly asks RAN2, CT1, CT4, SA3 to take the LS information into account and provide feedback to help SA2 make the decision on the two options for ciphering keys distribution.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2018-01-15 12:04:36","uploaded":"2018-01-15 12:31:21","revisionof":"","revisedto":"C4-182008","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"LCS_LTE_acc_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"R2-1712030, R2-1712031","lsto":"RAN2, CT1, CT4, SA3","Cc":"RAN3","lsoriginalls":"S2-179617","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181187.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181191","title":"LS on security across inter-operator interconnect","source":"SA3","contact":"Hans Christian Rudolph","contact-id":72672,"tdoctype":"LS in","for":"Discussion","abstract":"SA3 would like to inform CT4 that it is working on securing inter-operator interconnect for 5G. GSMA FSAG DESS has provided guideline requirements in the attached LS to SA3. SA3 is still discussing which of the requirements can be met.\n\nThe essence of the GSMA guideline requirements is that various information elements within the same message require different levels of protection. SA3 has concluded that protection has to take place at the application layer.\n\nSA3 kindly asks CT4 to involve SA3 in definition of the IEs and protocols across inter-operator interconnect and their transport.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-15 12:14:50","uploaded":"2018-01-15 12:31:22","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-SEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"S3-173527","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181191.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181193","title":"LS on TR for Overload Control for Diameter Charging completion","source":"SA5 Charging","contact":"Robert T\u00f6rnkvist","contact-id":35172,"tdoctype":"LS in","for":"Discussion","abstract":"SA5 would like to inform that the study TR 32.869 on Overload Control for Diameter Charging has been completed and will be sent for approval to the next plenary SA#78.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-15 12:20:33","uploaded":"2018-01-15 12:31:22","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"FS_DOCME_CH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"S5-176307","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181193.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181194","title":"LS to CT4 LS to CT4 on AVPs range numbers for Rel-15","source":"SA5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Discussion","abstract":"SA5 would like to request for a new range of AVP codes to be reserved for TS 32.299 Rel-15, in the CT4 TS 29.230.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-15 12:22:47","uploaded":"2018-01-15 12:31:23","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"CT3","lsoriginalls":"S5-176313","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181194.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181196","title":"LS to CT4 on the \"Study on forward compatibility for 3GPP Diameter Charging Applications\" completion","source":"SA5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Discussion","abstract":"SA5 would like to inform CT4, about the completion of their \"Study on forward compatibility for 3GPP Diameter Charging Applications (FS_FWDCA)\", which main objective was to address the CT4 TR 29.819 \"Study on Impacts of the Diameter Base Protocol Specification Update\" conclusion on Diameter extensibility rules, per subclause 5.3.1.4:\n\n\"For 3GPP Diameter Accounting application using the Diameter Base Protocol Accounting (application Id =3), such as specified in the 3GPP TS 32.299 [16], further studies are required to evaluate how AVPs can be added to existing commands with the M-bit cleared to avoid backward compatible issues\"\n\nThe TR 32.870 has been completed and will be sent to the next SA#78 for information and approval.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-15 12:28:01","uploaded":"2018-01-15 12:31:23","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"FS_FWDCA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"CT3","lsoriginalls":"S5-176467","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181196.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181197","title":"LS on IPv6 work items","source":"ITU-T SG20","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Information","abstract":"ITU-T Study Group 20 has a work item pertaining to Draft Recommendation Y.IPv6RefModel \"Reference Model of IPv6 Addressing Plan for Internet of Things Deployment\" which underscores an optional reference model of an IPv6 subnet addressing plan for Internet of things (IoT) deployment by end-users such as smart cities, public administrations and companies. \nITU-T SG20 would like to invite your experts to share and submit any relevant information and documents on the above-mentioned work items, including more specifically:\n-\tAny examples, models and use cases of IPv6 subnet addressing plans encompassing Internet of Things;\n-\tAny recommendations on IPv6 subnet addressing plan design.\nWe would appreciate very much receiving such inputs by 28 January 2018. \nITU-T SG20 looks forward to cooperating with the experts and to benefit from expertise in this domain.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-15 12:30:33","uploaded":"2018-01-15 12:31:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"sp16-sg20-oLS-00060","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181197.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181201","title":"LS on a new requirement on \u201cUnpredictable GTP TEID\u201d.","source":"SA3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"SA3 would like to inform CT4 that a new requirement on GTP TEID assignment has been agreed for inclusion in the (Rel15) draft TS33.250:\nThe GTP TEID shall be unpredictable","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2018-01-16 09:23:19","uploaded":"2018-01-16 09:32:12","revisionof":"C4-176151","revisedto":"C4-182011","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"SCAS_PGW"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"S3-171536","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181201.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181202","title":"LS on defining GTP extension header for 5GS Container","source":"RAN3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"RAN3 has decided to specify a 5GS container which includes the Radio Network Layer user plane information elements which need to be exchanged over NG-U e.g. QFI (QoS Flow ID).","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-16 09:23:48","uploaded":"2018-01-16 09:32:12","revisionof":"C4-176161","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"R3-174196","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181202.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181209","title":"NGMN White Paper on Service-based Architecture in 5G","source":"NGMN Alliance Project \u201cService-Based Architecture in 5G\u201d","contact":"Dan Wang","contact-id":72661,"tdoctype":"LS in","for":"Information","abstract":"NGMN is pleased to inform the recipients of this liaison statement that the White Paper of the NGMN Service-based Architecture in 5G has been published. \nThe deliverable has been created by NGMN Mobile Network Operator-Partners.\n\nThe document describes a service framework including service registration, service authorization, and service discovery. Service-based Architecture for 5G is designed in a forward-looking manner, such that the functionalities in 5G Core Network (CN) consist of services, the interface between Control Plane (CP) and User Plane (UP) should be Service Based Interface (SBI) and the Data Service should be used. The deployment aspects of SBA are explored along with the gap analysis and recommendations for related SDOs. \n\nNGMN kindly requests the recipients of this liaison to take the content of this White Paper and the recommendations into account for their ongoing work on the industry-wide 5G architecture.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2018-01-22 07:23:17","uploaded":"2018-01-22 07:25:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA2, 3GPP SA5, ETSI ISG NFV, GSMA","Cc":"3GPP SA, 3GPP SA3, 3GPP CT, 3GPP CT4","lsoriginalls":"180105 Liaison NGMN Service Based Architecture","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181209.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181211","title":"Reply LS to CT4 LS to CT4 on AVPs range numbers for Rel-15","source":"CT4","contact":"Ulrich Wiehe","contact-id":73600,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"approved","reservation_date":"2018-01-22 08:44:37","uploaded":"2018-01-29 14:47:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"TEI15"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA5","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181211.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-181325","title":"LS on SBI Design and its Security Implications","source":"SA3","contact":"Hans Christian Rudolph","contact-id":72672,"tdoctype":"LS in","for":"Discussion","abstract":"ACTION: \tSA3 asks CT3\/CT4 group to consider the design criteria described in section 1.2 above when designing SBI for 5G. SA3 security solutions depend on CT3\u2019s and CT4\u2019s design decisions and SA3 would therefore ask CT3\/CT4 to closely work with SA3 on the matter. \n\tSA3 further asks CT3\/CT4 to inform SA3 if CT3\/CT4 identify any problems or concerns in following the guidelines in section 1.2.\nSA3 also asks CT3\/CT4 to kindly respond to the questions in section 1.3. SA3 asks CT3\/CT4 to respond by SA3#90Bis to allow SA3 to define a 5GS security solution for SBA for phase 1 before stage 2 documents are to be closed.","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2018-01-25 08:51:01","uploaded":"2018-01-29 14:47:53","revisionof":"","revisedto":"C4-182012","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-SEC"},{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3, CT4","Cc":"SA2","lsoriginalls":"S3-180389","lsreply":"C4-182199, C4-182244","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_82_Gothenburg\/Docs\/C4-181325.zip","group":"C4","meeting":"C4-82","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]