[{"name":"C4-151956","title":"LS on Proposed extension to GUSS to include AS address","source":"3GPP TSG CT WG1","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"3GPP TSG-CT1 discussed a proposal how the Authentication Proxy (AP) is configured by HSS to route an HTTP request to an Application Server (AS) instance.\n\nThe proposal was:\n- the \"ASName\" field in GUSS of a user contains an AS instance address; and\n- when an AP receives an HTTP request from a user, and there are several AS instances providing the service (identified by the Host header field and the Request-URI) requested in the received HTTP request, then the AP routes the HTTP request to the AS instance address in the \"ASName\" field in user's GUSS.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-02 17:45:25","uploaded":"2015-11-02 19:40:06","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"TEI13"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG SA WG2, TSG SA WG3","Cc":"3GPP TSG CT WG4","lsoriginalls":"C1-153909","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-151956.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151958","title":"Reply LS to LS on 3GPP Work on Explicit Congestion Notification for Lower Layer Protocols.","source":"3GPP TSG CT WG1","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-02 17:52:51","uploaded":"2015-11-02 19:40:06","revisionof":"","revisedto":"","release":"Rel-10","crspec":"","crspecversion":"","workitem":[{"winame":"ECSRA_LAA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"CT, RAN, SA2, SA4, RAN2, CT3, CT4","lsoriginalls":"C1-153966","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-151958.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151960","title":"Reply LS on 3GPP Work on Explicit Congestion Notification for Lower Layer Protocols","source":"CT3","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"TSG SA had requested the following:\nSA requests that RAN2, SA2, SA4, CT1, CT3 and CT4 check whether the list of 3GPP Working Groups affected by IETF activities on ECN  (those who receive this action) is comprehensive.  SA further requests that a list of Technical Specifications that could be affected by the work is sent to SA. Finally, SA requests that if the recipient of this LS has comments for IETF tsvwg, that those comments please be sent to SA instead of IETF directly. SA will provide a coordinated response to the IETF\n\nCT3 is not aware of any additional affected WGs.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-02 17:59:11","uploaded":"2015-11-02 19:40:07","revisionof":"","revisedto":"","release":"Rel-10","crspec":"","crspecversion":"","workitem":[{"winame":"ECSRA_LAA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA2, SA4, RAN2, CT1, CT3, CT4, CT, RAN","lsoriginalls":"C3-154252","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-151960.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151962","title":"LS on extension to field length of PDCP Sequence Number","source":"TSG-RAN WG2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"RAN2 would like to inform RAN3, CT4 and SA3 that RAN2 has taken as a baseline to extend the field length of PDCP SN [TS 36.323] for AM DRB for both UL and DL to 23 bits in Rel-13, in addition to the previous maximum value of 15 bits (which is per DRB configurable). The FMS field in PDCP STATUS PDU is also extended to 23 bits and the size of BITMAP is increased accordingly.\n\nIn the related discussion this was recognized to have impact also to RAN3 and CT4 specifications.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2015-11-02 18:05:20","uploaded":"2015-11-02 19:40:07","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"LTE_CA_enh_b5C-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG-RAN WG3, TSG-CT WG4","Cc":"TSG-SA WG3","lsoriginalls":"R2-153873","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-151962.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151963","title":"Reply LS on S8HR roaming architecture handling of E9-1-1 calls in the US and Canada","source":"3GPP SA WG2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"3GPP SA WG2 would like to thank ATIS WTSC for their liaison regarding the potential impacts of S8HR roaming on the US and Canada\u2019s deployment of emergency services.\n\nFor the following question from ATIS WTSC:\n\n\u201cATIS WTSC kindly requests 3GPP SA2 to provide a description how, given the US and Canadian E9-1-1 requirements described above, the two included scenarios would function between the VPLMN and HPLMN when S8HR is employed.\u201d\n\nWhile SA2 cannot provide further clarification on the text of another organization\u2019s document (GSMA in this case), SA2 would like to inform WTSC that at the behest of GSMA, SA2 has begun a study (FS_V8) on the required architectural enhancements necessary to support the S8HR roaming model in 3GPP networks.  Currently SA2 has identified key issues relating to the support of emergency service within the S8HR roaming model, and may identify further issues as the study progresses.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-02 18:12:38","uploaded":"2015-11-02 19:40:07","revisionof":"","revisedto":"","release":"Rel-14","crspec":"","crspecversion":"","workitem":[{"winame":"FS_V8"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ATIS WTSC","Cc":"GSMA NG, GSMA WAS, 3GPP TSG-SA, 3GPP TSG-CT, 3GPP SA WG1, 3GPP SA WG3, 3GPP CT WG1, 3GPP CT WG3, 3GPP CT WG4, GSMA PSMC","lsoriginalls":"S2-153684","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-151963.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151964","title":"LS on Agreements on CIoT architecture for NB-IOT","source":"SA2","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 would like to inform that SA2 has reached agreements on CIoT architecture for NB-IOT as shown in S2-153636.\n\nSA2 has agreed, for normative work, to progress Solution 2 from TR 23.720 v1.1.0 as a mandatory feature for the UE and the Network and Solution 18 as an optional feature.\n\nSA2 plans to start normative work at SA2#112 meeting.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-02 18:15:48","uploaded":"2015-11-02 19:40:04","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"FS_AE_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN1, RAN2, RAN3, SA3, CT1, CT3, CT4","Cc":"","lsoriginalls":"S2-153695","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-151964.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151968","title":"LS on 3GPP Work on Explicit Congestion Notification for Lower Layer Protocols","source":"3GPP TSG SA WG4","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"SA4 thanks TSG SA for their LS on ECN for lower layer protocols. After checking the specifications under SA4 control, we would like to provide the following comments. \n-\tAmong specifications under SA4 control, the Rel-10 and later versions of 3GPP TS 26.114 include references to IETF RFC 3168 and RFC 6679.\n\n-\tIn addition, 3GPP TS 26.223 uses the media transport procedures specified in 3GPP TS 26.114.\n\n-\t3GPP TS 26.247 makes use of TCP and the performance of the service could be impacted by the way the ECN markings are affected by the lower layers.\n\n-\tSA4 would appreciate to be kept up to date on any possible changes that may affect the usability of the mentioned IETF RFC 3168, RFC 6679, and TCP in the aforementioned 3GPP specifications.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-02 18:59:06","uploaded":"2015-11-02 19:40:04","revisionof":"","revisedto":"","release":"Rel-9","crspec":"","crspecversion":"","workitem":[{"winame":"LTEimp-Vocoder"},{"winame":"HTTP_SDS"},{"winame":"IMS_TELEP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG SA","Cc":"3GPP SA WG2, 3GPP TSG CT WG1, 3GPP TSG CT WG3, 3GPP TSG CT WG4, 3GPP RAN WG2","lsoriginalls":"S4-151476","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-151968.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151971","title":"LS on Multi-stream Multiparty Conferencing Media Handling","source":"3GPP TSG SA WG4","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"SA4 would like to inform CT1, CT3 and CT4 that an extension is being added to MTSI for Multi-stream Multiparty Conferencing Media Handling (MMCMH). The attached CR describes the proposed updates to TS 26.114 in order to add this extension.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-02 19:09:19","uploaded":"2015-11-02 19:40:05","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"MMCMH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG CT WG1, 3GPP TSG CT WG3, 3GPP TSG CT WG4","Cc":"","lsoriginalls":"S4-151543","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-151971.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151972","title":"LS on Packet switched conversational multimedia applications TS 26.235 and TS 26.236","source":"3GPP TSG SA WG4","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"3GPP TS 26.235 Packet switched conversational multimedia applications; Default codecs and 3GPP TS 26.236 Packet switched conversational multimedia applications; Transport protocols are both under SA4 responsibility. Those 2 TSs haven\u2019t been updated since Rel-7 and SA4 considers them as being superseded by 3GPP TS 26.114 IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction, when it comes to specifying default codecs and media transport for multimedia conversational applications.\nSA4 therefore agreed to no longer maintain 3GPP TS 26.235 and 3GPP TS 26.236. The intention is that Rel-13 and subsequent releases of these specifications will not be created.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2015-11-02 19:12:25","uploaded":"2015-11-02 19:40:05","revisionof":"","revisedto":"","release":"Rel-13","crspec":"","crspecversion":"","workitem":[{"winame":"IMS-CODEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG CT WG3, 3GPP TSG CT WG4, 3GPP TSG RAN WG5, 3GPP TSG RAN WG2","Cc":"3GPP TSG SA","lsoriginalls":"S4-151562","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-151972.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-151975","title":"LS repy to ETSI TC INT LS on Validation project for the Conformance Test Specifications for Rf and Ro.","source":"3GPP SA5","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"3GPP SA5 thanks TC INT to have informed us about the start of the validation project for the Conformance Test Specifications for the Diameter Protocol over the Rf and the Ro reference points based on the 3GPP specifications TS 132 260 and 132 299 Release 10. \n\nThe received TC INT document on Conformance Test Specifications for the Diameter Protocol over the Rf and the Ro reference points TS 103 374-2 (DTS\/INT-00121-2), as attachment is now available so that interested companies in 3GPP SA5 may provide further feedback.","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-02 19:23:27","uploaded":"2015-11-02 19:40:05","revisionof":"","revisedto":"","release":"Rel-10","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI TC INT","Cc":"3GPP SA, 3GPP CT4","lsoriginalls":"S5-155250","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-151975.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-152139","title":"Proposed requirements for carrier Wi-Fi\u00ae networks","source":"Wi-Fi Alliance","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-11 10:00:53","uploaded":"2015-11-11 10:01:54","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"20150818 3GPP communication on carrier Wi-Fi requirements.","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-152139.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-152156","title":"LS reply to 3GPP CT4 UE Usage Type for Dedicated Core Networks","source":"GSMA PACKET","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-16 15:32:06","uploaded":"2015-11-16 15:37:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4","Cc":"","lsoriginalls":"PACKET#82 Doc 123 Rev 2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-152156.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-152157","title":"NG PACKET LS to Standardization groups on PMIP removal","source":"GSMA PACKET","contact":"Kimmo Kymalainen","contact-id":19464,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2015-11-16 15:34:40","uploaded":"2015-11-16 15:37:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA2, 3GPP CT4","Cc":"","lsoriginalls":"PACKET#83 Doc 107","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-152157.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"C4-152159","title":"ERP for Fast Re-Authentication","source":"ORANGE","contact":"Lionel Morand","contact-id":25150,"tdoctype":"discussion","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4","ainame":"Input liaison statements: allocation to agenda items as appropriate","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-11-16 17:21:39","uploaded":"2015-11-16 17:25:41","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/TSGCT4_71_Anaheim\/Docs\/C4-152159.zip","group":"C4","meeting":"C4-71","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]