[{"name":"S3i160032","title":"TPKT \u2013 Connection Establishment Simplification","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"This contribution proposes simplification to the TPKT Connection Establishment Procedures to minimize LEMF and CSP impacts.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"9.1","ainame":"Release 12 33.108 v12.11.0 and earlier","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-19 14:37:18","uploaded":"2016-01-19 16:53:49","revisionof":"","revisedto":"S3i160051","release":"Rel-12","crspec":33.108,"crspecversion":"12.11.0","workitem":"","crnumber":297.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160032.zip","group":"S3","meeting":"S3-ah-31834","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S3i160035","title":"Correction of GLIC to ULIC","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"The term \u201cGLIC\u201d is used in several places where the term ULIC should be used.  This is a historic leftover and needs to be corrected. All instances of \u201cGLIC\u201d are changed to \u201cULIC\u201d. There will be incorrect references to GLIC which is not defined in the standard and certain features will not be implementable which can lead a CSP to not be able to meet its regulatory obligations.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"9.1","ainame":"Release 12 33.108 v12.11.0 and earlier","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-19 15:54:14","uploaded":"2016-01-19 16:54:25","revisionof":"","revisedto":"S3i160097","release":"Rel-12","crspec":33.108,"crspecversion":"12.11.0","workitem":"","crnumber":298.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160035.zip","group":"S3","meeting":"S3-ah-31834","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S3i160051","title":"TPKT \u2013 Connection Establishment Simplification","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"Annex G on use of TPKT indicates that the TCP Connection may be established by the LEMF, however, normally this should be established by the MF.  There are no procedures for the LEMF to initiate such procedures.  In addition, there TPKT establishment procedures include many capability negotiation mechanisms, many of which are not needed for a simple implementation. Thus, simplification is proposed to not require the TPKT connection establishment negotiation mechanism.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"9.1","ainame":"Release 12 33.108 v12.11.0 and earlier","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-20 16:54:53","uploaded":"2016-01-20 17:09:50","revisionof":"S3i160032","revisedto":"S3i160084","release":"Rel-12","crspec":33.108,"crspecversion":"12.11.0","workitem":"","crnumber":297.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160051.zip","group":"S3","meeting":"S3-ah-31834","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S3i160097","title":"Correction of GLIC to ULIC","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"The term \u201cGLIC\u201d is used in several places where the term ULIC should be used.  This is a historic leftover and needs to be corrected.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"9.1","ainame":"Release 12 33.108 v12.11.0 and earlier","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-28 14:22:55","uploaded":"2016-01-28 14:25:51","revisionof":"S3i160035","revisedto":"","release":"Rel-12","crspec":33.108,"crspecversion":"12.11.0","workitem":[{"winame":"LI12"}],"crnumber":298.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-160049","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160097.zip","group":"S3","meeting":"S3-ah-31834","year":2016,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]