[{"name":"S5-187036","title":"Resubmitted Reply LS from CT to SA5 on API specification and API version number maintenance","source":"TSG CT","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"LS in","for":"","abstract":"CT thanks CT4 for the LS on API specification and API version number maintenance (CP-182196\/C4-186602). CT has discussed the recommendations listed in the LS and has reached the following conclusions:\n\nOn the recommendation 1:\nCT welcomes the proposal to submit a single CR per API to update the API version number. It is up to SA to agree on an update of CR template to include a specific check-box (e.g. \"API impacts\") on CR cover page.\n\nOn the recommendation 2:\nCT agrees on a principle to define a specific freezing date for API specifications, as for ASN.1, three months after the deep freeze of the stage 3.\n\nOn the recommendation 3:\nThe need for a separate OpenAPI file containing a copy of the normative annex of the specification has been discussed. CT considers as useful to create separate OpenAPI files, validated by 3GPP, and to store these OpenAPI files in a centralized way. These separate files would be for information and the Annex of each specification containing the OpenAPI description will remain normative. CT kindly asks CT4 to define the details of the associated process.\n\nOn the recommendation 4:\nCT believes that this recommendation is tightly linked to the recommendation 3. If there is a central storage of OpenAPI files independent of the TS, it seems relevant to include the ExternalDoc field in the OpenAPI.\n\nOn the recommendation 5:\nCT believes that the proposed process is good and should be applied by WG developing API in 3GPP.\n\nIt has to be noted that the current API version number pattern was questioned and there was a proposal to remove the Release indication (\"Rn\") from the API version number. It would be good to clarify why the current format has been defined as such in the TS 29.501. And this would help to clarify the maintenance of this API version number.\n\nMoreover, it was commented that the recommendations listed in this LS not only apply to the API designed for 5G SBI but also to any API defined by 3GPP. It would be good to have homogeneous handling of the API version number and API specification, especially when some of the APIs are exposed to non-3GPP external networks. It should be considered if some of the recommendations given for API for 5GC can be captured in a document that would be valid for other types of API.","secretary_remarks":"","agenda_item_sort_order":11,"ainumber":"5.3","ainame":"Liaison statements at SA5 level","tdoc_agenda_sort_order":70360,"status":"replied to","reservation_date":"2018-10-26 14:47:52","uploaded":"2018-10-30 10:34:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT4, CT3, SA, SA5, SA6","Cc":"","lsoriginalls":"CP-182239","lsreply":"S5-187336, S5-187336","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187036.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S5-187336","title":"Reply to: Resubmitted Reply LS from CT to SA5 on API specification and API version number maintenance","source":"SA5 (Ericsson et al)","contact":"John M Meredith","contact-id":637,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":11,"ainumber":"5.3","ainame":"Liaison statements at SA5 level","tdoc_agenda_sort_order":70361,"status":"approved","reservation_date":"2018-11-15 17:01:25","uploaded":"2018-11-15 17:01:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S5-187036","lsto":"TSG CT, TSG SA","Cc":"CT4, CT3, SA, SA6","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/TSG_SA\/WG5_TM\/TSGS5_122\/Docs\/S5-187336.zip","group":"S5","meeting":"S5-122","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]