[{"name":"C4-260015","title":"Addition of 422 error Status code for PATCH operation","source":"Oracle Corporation, Nokia","contact":"John Mohanraj","contact-id":95823,"tdoctype":"CR","for":"Agreement","abstract":"CR C4-253096 introduced the use of HTTP status code 422: Unprocessable Entity for PATCH requests that are syntactically correct and understood by the producer, but cannot be processed. In TS 29.531, section 5.3 describes the NSSF_NSSAIAvailability service, and the current error response for both PUT and PATCH \"Replace\" operations is set to 400: Bad Request. However, this status code does not precisely indicate the nature of the error.\n\nIt is therefore advisable to use the 422 status code should be used in such scenarios, to help consumer NFs differentiate between non-processable and syntactically incorrect requests.","secretary_remarks":"","agenda_item_sort_order":83,"ainumber":"19.","ainame":"Service Based Interface Protocol Improvements Release 19 [SBIProtoc19]","tdoc_agenda_sort_order":0,"status":"withdrawn","reservation_date":"2026-01-22 02:50:27","uploaded":"2026-01-30 09:19:41","revisionof":"","revisedto":"","release":"Rel-19","crspec":29.531,"crspecversion":"19.5.0","workitem":[{"winame":"SBIProtoc19"}],"crnumber":255.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_ct\/WG4_protocollars_ex-CN4\/CT4_133_Goa-2026-02\/Docs\/C4-260015.zip","group":"C4","meeting":"C4-133","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]