[{"name":"SP-210003","title":"LS from ATIS IoT Group: Request that a standardised SST value for this S-NEST new Slice Service Type (SST) be added to TS 23.501","source":"ATIS IoT Group","contact":"Farrokh Khatibi","contact-id":79662,"tdoctype":"LS in","for":"Action","abstract":"As requested by 3GPP, the ATIS IoT Group worked with GSMA 5GJA to define a new Standardised Network Slice Type (S-NEST) in PRD NG.116. ATIS would like to inform TSG SA and SA WG2 that the new Slice Service Type (SST) for High-Performance Machine-Type Communications (HMTC) has been added in NG.116 Generic Network Slice Template v4. Interested member companies plan to submit a CR to SA WG2 requesting that a standardised SST value for this S-NEST new Slice Service Type (SST) be added to TS 23.501 in order to meet the described IoT characteristics matrix. Action: SA WG2 to take the above information into account and, if there is no further feedback, document the new defined SST in TS 23.501.","secretary_remarks":"Proposed Action: Noted. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10280,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"","lsoriginalls":"IoT_CAT_Liaison_Letter_to_SA_and_SA2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210003.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210006","title":"LS from IEEE 802.1 Working Group: Liaison response to LS SP-201142 on Use of Inclusive Language in 3GPP specifications","source":"IEEE 802.1 Working Group","contact":"Glenn Parsons","contact-id":17960,"tdoctype":"LS in","for":"Action","abstract":"Dear Colleagues, The IEEE 802.1 Working Group would like to thank TSG SA for the information provided in liaison statement LS SP-201142 on use of inclusive language in 3GPP specifications. We would like to inform you that efforts are being made in our organization to use more inclusive and neutral language in our standards. An IEEE SA resolution indicates that: 'IEEE standards should be written in such a way as to avoid noninclusive and insensitive terminology (see IEEE Policy 9.27) and other deprecated terminology (see clause 10 of the IEEE SA Style Manual) except when required by safety, legal, regulatory, and other similar considerations. Terms such as master\/slave, blacklist, and whitelist should be avoided.', see the December 2020 entry in https:\/\/standards.ieee.org\/about\/sasb\/resolutions.html. IEEE Std 802.1AS is a profile of IEEE Std 1588; therefore, IEEE Std 802.1AS is based on IEEE Std 1588 to a large extent, including terminology. The IEEE 802.1 WG prefers to maintain consistency with IEEE Std 1588 and to align to the terms of IEEE Std 1588, which is being amended by IEEE P1588g to define suitable and inclusive terminology. The IEEE 802.1 WG is developing a Project Authorization Request (PAR) on inclusive language for IEEE Std 802.1AS in alignment with IEEE P1588g and an anticipated update to clause 10 of the IEEE SA Style Manual. We recommend that 3GPP also waits for the finalization of the IEEE 1588 alternative terminology to allow industry standards alignment. We look forward to receiving an update from you. Note that the IEEE 802 work is open and contribution driven. Participation is on an individual basis and technical discussion can be conducted based on individual contributions. The TSN Task Group holds regular electronic meetings: details are available at https:\/\/1.ieee802.org\/wg-calendar. Respectfully submitted, Glenn Parsons Chair, IEEE 802.1 Working Group","secretary_remarks":"CC#3: Left open. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10290,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2","Cc":"IEEE, IETF, GSMA, ETSI, OMA, ISO, OneM2M, ITU-T, TIA, ATIS, SAE, 5GAA, IEC, TSG RAN, TSG CT","lsoriginalls":"Liaison-response-inclusive-language-0221","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210006.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210010","title":"LS from RAN WG2: Reply LS on Use of Inclusive Language in 3GPP","source":"RAN WG2","contact":"Richard Burbidge","contact-id":14160,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has undertaken the work relating to the use of inclusive language in 3GPP and the following replacement terminology has been agreed: blacklist -> exclude-list blacklisted -> exclude-listed whitelist -> allow-list whitelisted -> allow-listed CSG whitelist -> Permitted CSG list In addition, RAN WG2 made corresponding changes to related field and IE names in 36.331 and 38.331. RAN WG2 is aware that RAN WG4 and CT WG1 specifications (at least in 36.133 and 23.122) also refer to the CSG whitelist and requests RAN WG4 and CT WG1 to use the same replacement terminology in their specifications. RAN WG2 have prepared technically endorsed Rel-17 CRs for the following specifications: 36.300, 36.304, 36.306, 36.331, 37.320, 38.300, 38.304, 38.306 and 38.331. The attached technically endorsed CRs are provided to RAN for information. Each CR will be updated and agreed by RAN WG2 and submitted to RAN plenary for approval when the first Rel-17 version of the corresponding specification is expected to be created. Action: Take note of the attached technically endorsed CRs.","secretary_remarks":"CC#3: Left open. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10300,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-01 11:22:13","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA, RAN WG4, CT WG1","Cc":"TSG CT","lsoriginalls":"R2-2101986","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210010.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210016","title":"LS from MulteFire Alliance: LS on MulteFire PLMN-ID","source":"MulteFire Alliance","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"MulteFire Alliance (MFA) has developed the MulteFire standards release 1.0 and release 1.1 which address the use of the LTE in the unlicensed bands in a stand-alone fashion (no need for licensed anchor). Moving towards 5G, MFA will adopt 3GPP NR technology for Private Networks. MFA has recently been allocated a PLMN-ID from ITU-T. This PLMN-ID is planned to be used for private networks. The ITU-T stipulates this following condition for the use of the PLMN-ID for technologies that are based on standards or specifications developed by another ROIO\/SDO T-REC-E.212. Clause H.4.3: 'If the requested resources will be used in networks that are based on technical standards or specifications developed by another ROIO\/SDO, the applicant shall affirm and provide evidence that there exists mutual consent between the applicant and the other ROIO\/SDO regarding the usage of the requested resources for the ROIO\/SDO-specified networks.' MFA would like to ask for 3GPP to confirm the potential use of the MFA PLMN-ID on 3GPP NR Private Networks. Action: MFA would like to ask for 3GPP to confirm the potential use of the MFA PLMN-ID on 3GPP NR Private Networks","secretary_remarks":"Response drafted in SP-210130. Final response in SP-210264.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10200,"status":"replied to","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-16 12:44:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG RAN, TSG CT","lsoriginalls":"MF LS to 3GPP 12-MAR-2021.pdf","lsreply":"SP-210264","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210016.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210017","title":"LS from CT WG4: LS on migration from ETSI forge to 3GPP forge","source":"CT WG4","contact":"Peter Schmitt","contact-id":13753,"tdoctype":"LS in","for":"Action","abstract":"In Q3 2020 the GitLab project '3GPP\/5G_APIs' (hosted in ETSI Forge collaboration platform) was moved to a similar platform hosted in 3GPP (under 3gpp.org domain). So, starting from plenary #89, 3GPP Forge was used as endorsed by plenary. This needs to be reflected in TR 21.900. The reference in clause 5B to 'https:\/\/forge.etsi.org\/rep\/3GPP\/5G_APIs' has to be replaced by 'https:\/\/forge.3gpp.org\/rep\/all\/5G_APIs'. Action: CT WG4 kindly asks TSG SA group to update TR 21.900.","secretary_remarks":"Proposed Action: Noted. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10310,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-16 12:44:24","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG5, CT WG3, SA WG4, SA WG6","Cc":"TSG CT","lsoriginalls":"C4-211513","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210017.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210019","title":"LS from SA WG1: LS on support of PWS over SNPN","source":"SA WG1","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 has discussed for some time about the lack of service requirements, and stage-2\/3 support, for PWS over SNPN, so far missing in Rel-16 and Rel-17 specs. SA WG1 has identified and discussed impacts of certain PWS regulatory requirements for mobile network deployments in venues or areas with large numbers of users (e.g. football stadiums or campus areas), affecting both PLMN and NPNs. In fact, some regulations (e.g. related to EU\/NL-Alert PWS systems in Europe) indicate that SNPNs with more than e.g. 25000 users will not be exempt from PWS regulations pertaining to public mobile networks. Thus, the lack of SNPN support for PWS would prevent the possibility to deploy a SNPN network in those type of scenarios. Therefore, SA WG1 sees the need to introduce support of PWS over SNPN in Rel-17. Action: SA WG1 would like to inform TSG groups that SA WG1 sees the need to introduce support of PWS over SNPN in Rel-17, and kindly ask to provide any feedback in case proper stage-2\/3 work is deemed not feasible to complete within the Rel-17 timeframe.","secretary_remarks":"Response drafted in SP-210125 (Postponed). This was postponed.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10230,"status":"postponed","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-16 12:44:24","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, RAN WG2, RAN WG3, TSG SA, TSG CT, TSG RAN","Cc":"SA WG3","lsoriginalls":"S1-210368","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210019.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210021","title":"LS from SA WG2: Reply LS from ATIS IoT Group: Request that a standardised SST value for this S-NEST new Slice Service Type (SST)","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 would like to thank ATIS IoT Group for the request to add a new SST for High-Performance Machine-Type Communications (HMTC). SA WG2 approved the attached TS 23.501 CR 2571 for rel.17 that adds this new SST in TS 23.501. The CR if approved by SA#91 will be implemented in the latest rel.17 version of TS 23.501.","secretary_remarks":"Related to discussion paper SP-210237. A response LS was drafted in SP-210254. This LS was postponed.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10250,"status":"postponed","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-16 12:44:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ATIS IoT Group","Cc":"TSG SA, GSMA 5GJA","lsoriginalls":"S2-2101051","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210021.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210024","title":"LS from ITU-R WP5D: LIASION STATEMENT TO RELEVANT EXTERNAL ORGANIZATIONS ON TIMING OF UPDATES TO IMT-2020 RECOMMENDATION ITU-R M.2150 AND IMT-ADVANCED RECOMMENDATION ITU-R M.2012 AFTER YEAR 2021","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Action","abstract":"WP 5D has proposed internally to adopt the indicated way forward on the general revision of M.2150 to complete in 2023 and associated with that, a way forward on Revision 6 on M.2012 leading to a dual revision occurring in mid-year 2023. WP 5D seeks the views of the relevant External Organisations towards obtaining alignment for these ways forward and the indicated methods of work. In summary, WP 5D plans the following for the anticipated timing in ITU-R related to the next revisions of these two Recommendations after year 2021, to both complete in year 2023: - For IMT-2020: - the first general revision of M.2150 would complete at WP 5D Meeting #44 (13 22 June 2023). - the revision would be formally initiated by WP 5D from WP 5D Meeting #38 (7-18 June 2021), and a suitable announcement would be dispatched with the finalized detailed schedule. - A preliminary working scheduled is provided in Attachment 3 for advance planning purposes. - For IMT-Advanced: - the revision 6 of M.2012 would complete at WP 5D Meeting #44 (13 22 June 2023). - the revision would be formally initiated by WP 5D from WP 5D Meeting #38 (7-18 June 2021), and a suitable announcement would be dispatched with the finalized detailed schedule. - The preliminary working scheduled provided in Attachment 3 would also be applicable to this update of M.2012 for advance planning purposes. WP 5D has completed the update process to be used for future updates of IMT 2020 in Rec. M.2150. It is available as published Document IMT-2020\/57. Request for Action: In accordance with the above, and considering Document IMT-2020\/57, and the preliminary advance planning schedule view enclosed in Attachment 3, WP 5D kindly requests the GCS Proponent and Transposing Organizations of IMT-2020 (Rec. ITU-R M.2150) and IMT-Advanced (Rec. ITU-R M.2012) to take into account this advance and preliminary view of the revisions schedules in their planning and work. WP 5D looks forward to the continued cooperation with the External Organizations. WP 5D kindly seeks the views of the External Organisations towards these matters, as the overall timing and detailed schedules for these Revisions are planned to be finalized in WP 5D in Meeting #38 (7 18 June 2021). The submission deadline for Meeting #38 is 31 May 2021 at 1600 hours UTC. The follow-on step would be for WP 5D, from Meeting #38 in June 2021to dispatch the formal announcement of the relevant revisions and the associated release of the final detailed schedules in Documents IMT-2020\/AAA 'Schedule for General Revision of Recommendation ITU-R M.2150' and IMT-Adv\/BBB, Schedule for Revision 6 of Recommendation ITU-R M.2012' which would initiate the revisions.","secretary_remarks":"Proposed Action: Noted. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-17 09:56:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"R19-WP5D-210301-TD-0313!!MSW-E","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210024.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210025","title":"LS from SA WG5: LS on OpenAPI guidelines","source":"SA WG5","contact":"Thomas Tovinger","contact-id":3654,"tdoctype":"LS in","for":"Action","abstract":"At SA#90, SA WG5 received an official request from TSG CT (in the CT report to SA) to align with the OpenAPI guidelines developed by CT in 29.501. SA WG5 has analysed and discussed these comments extensively, also in a conf. call with CT, and a contribution summarising the request from CT was submitted to SA WG5#136e by the CT chair as S5-212235 (attached). SA WG5 has discussed the document and would like to provide the following feedback regarding the requests provided (main bullets in slides 3-5 of S5-212235): 1. 'As described in TR 21.900 clause 5B, All OpenAPI specification files documented by TS have to be stored by the MCC officer in the following locations.' SA WG5 reply: SA WG5 has some concerns to put all OpenAPI files into one repository. SA WG5 is actively cooperating with open source projects and the SA WG5 forge repository is already referred by external groups in their implementation. Changing the repository may cause problems and impact SA WG5 external influence. In addition, we would like some clarification on the rationale behind using one repository. One reason presented was simplification of referencing other OpenAPI files. We think this target may also be achieved by other means (please see bullet point 3). SA WG5 supports any endeavour to make 3GPP OpenAPI definitions easily accessible for the worldwide development community. We suggest working on a simplified branching strategy for outside exposure shielding external readers from 3GPP internals. We welcome a continued discussion with CT on this point. It is not an issue however for our MCC officer to store the files in the zip file containing the Word file of the new version of the TS; this can be done from the SA#91 CR implementation. 2. 'Align YAML file naming with TS 29.501 clause 5.3.6' SA WG5 reply: SA WG5 specifications contain an OpenAPI definition file name. SA WG5's understanding is that this approach is consistent with CT guidelines. 3. 'Align $refs in normative OpenAPI in TS's' SA WG5 reply: SA WG5 acknowledges that references need to be carefully designed. For example, 3GPP should ensure that the external development community can use the 3GPP definitions without the need to change them. References containing just the file name and no relative or absolute path components can help in that. SA WG5 proposes to enhance the 3GPP Forge environment with the possibility to specify locations where the tool shall search for referenced files. This would allow for using simple references with the file name only, also for the case that CT and SA WG5 use different repositories. 4. 'Align to 3GPP Common API Versioning Mechanism' SA WG5 reply: SA WG5 currently uses a versioning concept where the OpenAPI definition version number is identical to the TS version number containing the OpenAPI definition. We acknowledge that the CT concept which decouples the OpenAPI definition version number from the TS version number has advantages. We will study if it is possible to adopt the CT concept. 5. 'Align with IE naming convention' SA WG5 reply: SA WG5 guidelines and best practices are aligned with CT naming conventions in many cases: - Attribute names follow lowerCamel convention - Values of enumerations use UPPER_WITH_UNDERSCORE - Data type names follow UpperCamel convention - Array names are either plural ('users') or are appending 'List' ('userList'). Plural only can be used in future. - Query parameter names follow the same naming convention as attributes when they refer to attributes of the resource. CT uses lower-with-hyphen. SA WG5 believes readability is improved when attribute names and query names are identical when they refer to the same information. - URI path segment names follow lower-with-hyphen for standalone Management Services (MnS). For an MnS combined from an NRM and CRUD operations, the naming convention for managed object classes used in stage 2 (e.g. to align with RAN specifications) is also used for stage 3: normally UpperCamel is followed (e.g","secretary_remarks":"Proposed Action: Noted. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-17 09:56:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG CT","Cc":"CT WG4, CT WG3","lsoriginalls":"S5-212312","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210025.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210028","title":"LS from TSG RAN: Draft Letter to ITU in reply to RP-210731 = ITU_R_WP5D_TEMP_313 on timing of updates to IMT-2020 Recommendation ITU-R M.2150 and IMT-Advanced Recommendation ITU-R M.2012 after year 2021","source":"TSG RAN","contact":"Giovanni Romano","contact-id":10718,"tdoctype":"LS in","for":"Endorsement","abstract":"For 3GPP review: in: TSG SA feedback LS before: March 26, 2021 to: PCG","secretary_remarks":"For review and forwarding to PCG. This was endorsed and will be forwarded to the PCG.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10340,"status":"endorsed","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-25 06:10:23","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"","lsoriginalls":"RP-210783","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210028.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210029","title":"LS from TSG RAN: DRAFT Letter to ITU on the completion of the submission of LTE-Advanced toward Revision 5 of Rec. ITU-R M.2012","source":"TSG RAN","contact":"Giovanni Romano","contact-id":10718,"tdoctype":"LS in","for":"Endorsement","abstract":"For 3GPP review: in: TSG SA feedback LS before: March 26, 2021 to: PCG","secretary_remarks":"For review and forwarding to PCG. This was endorsed and will be forwarded to the PCG.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10350,"status":"endorsed","reservation_date":"2021-02-27 15:44:51","uploaded":"2021-03-25 06:10:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"","lsoriginalls":"RP-210787","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210029.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210125","title":"[DRAFT] Reply LS on support of PWS over SNPN","source":"Qualcomm Finland RFFE Oy","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1, SA WG2, CT WG1, RAN WG2, RAN WG3, TSG CT, TSG RAN. CC: SA WG3. Attachments: [TBD: agreed CR, and WID]","secretary_remarks":"Response to SP-210019. This was postponed.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10240,"status":"postponed","reservation_date":"2021-03-15 05:22:04","uploaded":"2021-03-17 22:35:47","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, CT WG1, RAN WG2, RAN WG3, TSG CT, TSG RAN","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210125.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210130","title":"[DRAFT] Reply LS on MulteFire PLMN-ID","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Responds to MFA re the use of PLMN-ID for SNPNs","secretary_remarks":"Response to SP-210016. Rev8 was approved (to be revised to a new TD number by MCC). Revised to SP-210264.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10210,"status":"revised","reservation_date":"2021-03-15 11:55:49","uploaded":"2021-03-17 21:22:02","revisionof":"","revisedto":"SP-210264","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"MulteFire Alliance","Cc":"TSG RAN, TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210130.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210237","title":"Discussion on the missing context to the newly introduced HMTC SST","source":"Deutsche Telekom","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"discussion","for":"Decision","abstract":"This contribution discusses missing context of newly introduced Slice Service Type High-Performance Machine-Type Communications (HMTC) in 3GPP specification and proposes some way forward.","secretary_remarks":"This was noted.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2021-03-17 23:09:08","uploaded":"2021-03-17 23:10:47","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210237.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210254","title":"[DRAFT] LS on SST Values","source":"Deutsche Telekom","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"LS out","for":"Approval","abstract":"-","secretary_remarks":"Created at CC#3. Response to SP-210021. This LS OUT was noted and the incoming LS in SP-210021 was postponed.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2021-03-23 16:34:36","uploaded":"2021-03-28 07:57:47","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, GSMA","Cc":"SA WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210254.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210264","title":"Reply LS on MulteFire PLMN-ID","source":"TSG SA","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"To: MulteFire Alliance. CC: TSG RAN, TSG CT","secretary_remarks":"Revision of SP-210130_Rev8. This LS OUT was approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10220,"status":"approved","reservation_date":"2021-03-28 07:27:45","uploaded":"2021-03-28 07:28:55","revisionof":"SP-210130","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-210016","lsto":"MulteFire Alliance","Cc":"TSG RAN, TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_91E_Electronic\/Docs\/SP-210264.zip","group":"SP","meeting":"SP-91-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]