[{"name":"S2-150706","title":"LS from CT WG1: Reply LS on provision of WLAN identifiers for RAN rule","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks for RAN WG2 LS pointing on the conflict between RAN WG2 and CT WG1 specification regarding WLAN identifiers provided for RAN rule from E-UTRAN to the UE.  CT WG1 has discussed this issue but did not agree the related CRs to align with RAN WG","secretary_remarks":"","agenda_item_sort_order":17,"ainumber":"5.3","ainame":"Non-3GPP Access Maintenance","tdoc_agenda_sort_order":11160,"status":"noted","reservation_date":"2015-03-18 08:02:35","uploaded":"2015-03-18 08:13:47","revisionof":"","revisedto":"","release":"Rel-12","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2","lsoriginalls":"C1-150841","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_108_Los_Cabos\/Docs\/S2-150706.zip","group":"S2","meeting":"S2-108","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-150722","title":"LS from RAN WG2: Reply LS on provision of WLAN identifiers for RAN rule","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks for CT WG1 LS on CT WG1's understanding with regard to WLAN identifiers provided for RAN rule from (E-)UTRAN to the UE.  RAN WG2 has discussed the issue again and agreed that for each entry in the list of WLAN identities for RAN rule, the n","secretary_remarks":"","agenda_item_sort_order":17,"ainumber":"5.3","ainame":"Non-3GPP Access Maintenance","tdoc_agenda_sort_order":11150,"status":"noted","reservation_date":"2015-03-18 08:02:35","uploaded":"2015-03-18 08:14:47","revisionof":"","revisedto":"","release":"Rel-12","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"R2-150684","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_108_Los_Cabos\/Docs\/S2-150722.zip","group":"S2","meeting":"S2-108","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-150744","title":"LS from TSG SA: LS on I-WLAN specification maintenance","source":"TSG SA","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"In the context of promoting 3GPP specifications to Rel-12, TSG SA discussed the maintenance of I-WLAN feature and the related specifications. The earlier decision from TSG SA #64 to discontinue the maintenance of the I-WLAN feature was documented in SP-14","secretary_remarks":"","agenda_item_sort_order":17,"ainumber":"5.3","ainame":"Non-3GPP Access Maintenance","tdoc_agenda_sort_order":11140,"status":"noted","reservation_date":"2015-03-18 08:02:35","uploaded":"2015-03-18 08:15:37","revisionof":"","revisedto":"","release":"Rel-12","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3, SA WG3LI, SA WG5, CT WG1, CT WG4, CT WG6","Cc":"TSG CT","lsoriginalls":"SP-150158","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_108_Los_Cabos\/Docs\/S2-150744.zip","group":"S2","meeting":"S2-108","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-150819","title":"Adding Architecture alternative for S2a","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add architecture in 16.1.1 to cover the above scenario. Add a note in 4.2.3 that the above scenarios are possible but they are not shown for simplicity.","secretary_remarks":"","agenda_item_sort_order":17,"ainumber":"5.3","ainame":"Non-3GPP Access Maintenance","tdoc_agenda_sort_order":11170,"status":"noted","reservation_date":"2015-04-03 00:54:02","uploaded":"2015-04-07 12:29:54","revisionof":"","revisedto":"","release":"Rel-12","crspec":23.402,"crspecversion":"12.8.0","workitem":[{"winame":"TEI12"},{"winame":"WLAN_NS"}],"crnumber":1357.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_108_Los_Cabos\/Docs\/S2-150819.zip","group":"S2","meeting":"S2-108","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-150820","title":"Adding Architecture alternative for S2a","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Rel-13 mirror CR: Summary of change: Add architecture in 16.1.1 to cover the above scenario. Add a note in 4.2.3 that the above scenarios are possible but they are not shown for simplicity.","secretary_remarks":"","agenda_item_sort_order":17,"ainumber":"5.3","ainame":"Non-3GPP Access Maintenance","tdoc_agenda_sort_order":11180,"status":"noted","reservation_date":"2015-04-03 00:54:02","uploaded":"2015-04-07 12:29:54","revisionof":"","revisedto":"","release":"Rel-13","crspec":23.402,"crspecversion":"13.1.0","workitem":[{"winame":"TEI12"},{"winame":"WLAN_NS"}],"crnumber":1358.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_108_Los_Cabos\/Docs\/S2-150820.zip","group":"S2","meeting":"S2-108","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]