[{"name":"S3i160017","title":"ASN.1 Correction to have PacketDataSummaryReport in clause B.9","source":"Nokia Networks","contact":"Nagaraja Rao","contact-id":41611,"tdoctype":"CR","for":"Approval","abstract":"Two errors are corrected: one in clause B.3a (adding a \u201c,\u201d after the \u201c\u2026\u201d) and another one in clause B.9 to have the correct name PacketDataSummaryReport. \nThe error was discovered and correction was provided by Jean-Pascal Chavanne (OFCOM).","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-18 19:18:44","uploaded":"2016-01-18 19:21:31","revisionof":"","revisedto":"S3i160034","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":294.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\/S3i160017.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":"S3i160018","title":"Correction in comment-part of ASN.1 for VoIP HI3 to refer to IMS-VoIP-Correlation","source":"Nokia Networks","contact":"Nagaraja Rao","contact-id":41611,"tdoctype":"CR","for":"Approval","abstract":"VoIP HI3 ASN.1 module has a reference pointing to a field \u201cCorrelationValues\u201d in HI2 that is not used for VoIP based on the recent changes. Even though the reference is in the comment-part of the ASN.1, it can still become the cause of a confusion. \n\nThe reference in the comment-part is changed from \u201cCorrelationValues\u201d to \u201cIMS-VoIP-Correlation\u201d.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"not pursued","reservation_date":"2016-01-18 21:02:06","uploaded":"2016-01-18 21:04:17","revisionof":"","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":295.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\/S3i160018.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":"S3i160025","title":"Dynamic Codecs and VoLTE HI3 RTP interpretation","source":"THALES","contact":"Eric Meilleray","contact-id":24419,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2016-01-19 09:10:38","uploaded":"2016-01-19 13:29:11","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160025.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":"S3i160031","title":"User Location Information reporting extensions over s2b","source":"Ericsson LM","contact":"Maurizio Iovieno","contact-id":23687,"tdoctype":"CR","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-19 12:35:52","uploaded":"2016-01-19 15:48:55","revisionof":"","revisedto":"S3i160072","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":"","crnumber":296.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160031.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":"S3i160034","title":"ASN.1 Correction to have PacketDataSummaryReport in clause B.9","source":"Nokia Networks","contact":"Nagaraja Rao","contact-id":41611,"tdoctype":"CR","for":"Approval","abstract":"Two errors are corrected: one in clause B.3a (adding a \u201c,\u201d after the \u201c\u2026\u201d) and another one in clause B.9 to have the correct name PacketDataSummaryReport. \nThe error was discovered and correction was provided by Jean-Pascal Chavanne (OFCOM). \n\nA few additional errors were discovered in the submitted CR and this revision takes care of them.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-19 15:50:22","uploaded":"2016-01-19 15:52:39","revisionof":"S3i160017","revisedto":"S3i160055","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":294.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\/S3i160034.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":"S3i160036","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. Currently this mechanism is restricted to the U.S. which does not allow other regions to make use of it if so desired.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-19 16:00:44","uploaded":"2016-01-19 16:54:25","revisionof":"","revisedto":"S3i160052","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":"","crnumber":299.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160036.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":"S3i160037","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":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-19 16:04:32","uploaded":"2016-01-19 16:54:25","revisionof":"","revisedto":"S3i160076","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":"","crnumber":300.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160037.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":"S3i160038","title":"Inclusion Conditions for the Stage 2 in Clause 6","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"The inclusion conditions for parameters defined in the Stage 2, Clause 6 are not clear. For example, mandatory parameters are listed incorrectly as conditional with no inclusion condition specified. Many conditional parameters have unstated inclusion conditions. All tables in Clause 6 are updated to clear indicate that parameters are mandatory with a straight shall requirement or for actual conditional parameters and inclusion condition is included. The standard can be implemented to leave out mandatory parameters that are incorrectly labeled as conditional which will then not allow an operator to meet their regulatory obligations of reporting all IRI and CC that they should be reporting.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-19 16:09:24","uploaded":"2016-01-19 16:54:25","revisionof":"","revisedto":"S3i160079","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":"","crnumber":301.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\/S3i160038.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":"S3i160042","title":"Alignment of HI2 and HI3 ASN.1 Correlation parameters for for VoIP","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"VoIP HI3 ASN.1 module has a reference pointing to a field \u201cCorrelationValues\u201d in HI2 that is not used for VoIP based on the recent changes. In fact, the this parameter is not aligned with that used for IRI for VoIP. This is a compatibility issue which can cause confusion at the LEMF and needs to be corrected. The ASN.1 type \u201cCorrelationValues\u201d is changed to to \u201cIMS-VoIP-Correlation\u201d and the \u201cIMS-VoIP-Correlation\u201d type is imported from the HI2 for EPS. Can lead to incompatibility, mis-interpretation and possible wrong implementation and consequently hinder a CSP from meeting its regluatory obligations of providing correlated IRI and CC to the LE.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-20 12:16:41","uploaded":"2016-01-20 13:22:43","revisionof":"","revisedto":"S3i160083","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":"","crnumber":302.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\/S3i160042.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":"S3i160047","title":"Location of the target 2G\/3G CS clarifications","source":"AQSACOM S.A.S.","contact":"Jerome GOUY","contact-id":37768,"tdoctype":"CR","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-20 13:42:19","uploaded":"2016-01-20 15:44:09","revisionof":"","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":303.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-160050","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160047.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":"S3i160049","title":"User Location Information clarification","source":"AQSACOM S.A.S.","contact":"Jerome GOUY","contact-id":37768,"tdoctype":"CR","for":"Approval","abstract":"Clarification of the information to be provided in the userLocationInfo parameter.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-20 13:53:03","uploaded":"2016-01-20 15:44:30","revisionof":"","revisedto":"S3i160059","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":"","crnumber":304.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\/S3i160049.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":"S3i160050","title":"Editorial correction and clarifications for serviceCenterAddress and XmlCivicAddress","source":"AQSACOM S.A.S.","contact":"Jerome GOUY","contact-id":37768,"tdoctype":"CR","for":"Approval","abstract":"Clarification of the information to be provided for serviceCenterAddress parameter, the Calling or\/and Called are not defined in partyinformation.\nEditorial correction for XmlCivicAddress information, reference to RFC 5139 is corrected from [yy] to [72].","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-20 15:55:57","uploaded":"2016-01-20 16:00:02","revisionof":"","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":305.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-160050","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160050.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":"S3i160052","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":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-20 16:59:03","uploaded":"2016-01-20 17:09:50","revisionof":"S3i160036","revisedto":"S3i160085","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":"","crnumber":299.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160052.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":"S3i160053","title":"TPKT \u2013 Application Beyond the U.S.","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"Annex G describes the use of TPKT for delivery of IRI and CC to the LEMF. Currently this mechanism is restricted to the U.S. which does not allow other regions to make use of it if so desired. Annex G is changed from a U.S. Annex to a more global Annex and is no longer informative.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"not pursued","reservation_date":"2016-01-20 17:06:06","uploaded":"2016-01-20 17:09:50","revisionof":"","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":"","crnumber":306.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\/S3i160053.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":"S3i160055","title":"ASN.1 Correction to have PacketDataSummaryReport in clause B.9","source":"Nokia Networks","contact":"Nagaraja Rao","contact-id":41611,"tdoctype":"CR","for":"Approval","abstract":"Two errors are corrected: one in clause B.3a (adding a \u201c,\u201d after the \u201c\u2026\u201d) and another one in clause B.9 to have the correct name PacketDataSummaryReport. \nThe error was discovered and correction was provided by Jean-Pascal Chavanne (OFCOM). \n\nA few additional errors were discovered in the submitted CR and this revision takes care of them. The zip file S3i160034 accidentally had a blank file. So, whatever was supposed to be S3i160034.zip is in this TDoc.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-22 15:58:27","uploaded":"2016-01-22 16:01:04","revisionof":"S3i160034","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":294.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-160050","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160055.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":"S3i160059","title":"User Location Information clarification","source":"AQSACOM S.A.S.","contact":"Jerome GOUY","contact-id":37768,"tdoctype":"CR","for":"Approval","abstract":"Clarification of the information to be provided in the userLocationInfo parameter.\n\nAfter few exchange with several participants, the change affects also APN-AMBR parameter.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-22 16:37:52","uploaded":"2016-01-22 16:44:48","revisionof":"S3i160049","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":304.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-160050","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160059.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":"S3i160072","title":"User Location Information reporting extensions over s2b","source":"Ericsson LM","contact":"Maurizio Iovieno","contact-id":23687,"tdoctype":"CR","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-27 07:51:09","uploaded":"2016-01-27 17:15:13","revisionof":"S3i160031","revisedto":"S3i160082","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":"","crnumber":296.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160072.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":"S3i160076","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":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-27 16:04:31","uploaded":"2016-01-27 16:09:10","revisionof":"S3i160037","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI12"}],"crnumber":300.0,"crrevision":1.0,"crcategory":"A","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\/S3i160076.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":"S3i160078","title":"Editorial clean up of SGN","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"Unclear abbriviation used, SGN instead of SGSN. Change SGN to SGSN","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-27 16:31:22","uploaded":"2016-01-27 16:33:38","revisionof":"","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":307.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-160050","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160078.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":"S3i160079","title":"Inclusion Conditions for the Stage 2 in Clause 6","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"The inclusion conditions for parameters defined in the Stage 2, Clause 6 are not clear. For example, mandatory parameters are listed incorrectly as conditional with no inclusion condition specified. Many conditional parameters have unstated inclusion conditions. All tables in Clause 6 are updated to clearly indicate that parameters are mandatory with a straight shall requirement or for actual conditional parameters an inclusion condition is included.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-27 16:41:15","uploaded":"2016-01-27 16:44:57","revisionof":"S3i160038","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":301.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-160050","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160079.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":"S3i160082","title":"User Location Information reporting extensions over s2b","source":"Ericsson LM","contact":"Maurizio Iovieno","contact-id":23687,"tdoctype":"CR","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-27 21:37:22","uploaded":"2016-01-28 07:37:58","revisionof":"S3i160072","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":296.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-160050","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160082.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":"S3i160083","title":"Alignment of HI2 and HI3 ASN.1 Correlation parameters for VoIP","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"VoIP HI3 ASN.1 module has a reference pointing to a field \u201cCorrelationValues\u201d in HI2 that is not used for VoIP based on the recent changes. In fact, this parameter is not aligned with that used for IRI for VoIP. This is a compatibility issue which can cause confusion at the LEMF and needs to be corrected.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2016-01-28 08:17:47","uploaded":"2016-01-28 08:20:12","revisionof":"S3i160042","revisedto":"S3i160086","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":"","crnumber":302.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\/S3i160083.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":"S3i160085","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\/DF. There are no procedures for the LEMF to initiate such procedures. In addition, the TPKT establishment procedures include many capability negotiation mechanisms, many of which are not needed for a simple implementation. In fact, the current specification allows the CSP and LEMF to implement different incompatible options. Thus this CR proposes changes to simplify the delivery interface in such a way that assures compatibility.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-28 08:41:08","uploaded":"2016-01-28 08:43:00","revisionof":"S3i160052","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI12"}],"crnumber":299.0,"crrevision":2.0,"crcategory":"A","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\/S3i160085.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":"S3i160086","title":"Alignment of HI2 and HI3 ASN.1 Correlation parameters for VoIP","source":"OTD","contact":"Selvam Rengasami","contact-id":31626,"tdoctype":"CR","for":"Approval","abstract":"VoIP HI3 ASN.1 module has a reference pointing to a field \u201cCorrelationValues\u201d in HI2 that is not used for VoIP based on the recent changes. In fact, this parameter is not aligned with that used for IRI for VoIP. This is a compatibility issue which can cause confusion at the LEMF and needs to be corrected.","secretary_remarks":"","agenda_item_sort_order":10,"ainumber":"9.2","ainame":"Release 13 33.108 v13.0.0","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2016-01-28 08:58:22","uploaded":"2016-01-28 09:00:34","revisionof":"S3i160083","revisedto":"","release":"Rel-13","crspec":33.108,"crspecversion":"13.0.0","workitem":[{"winame":"LI13"}],"crnumber":302.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-160050","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG3_Security\/TSGS3_LI\/2015_60_Dubrovnik\/Docs\/S3i160086.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}]