The short version is that it's perfectly fine. This doesn't modify the HTTP spec, and it uses established extension mechanisms. The long version: RFC 7231 def

The short version is that it's perfectly fine. This doesn't modify the HTTP spec, and it uses established extension mechanisms. The long version: RFC 7231 defines the standard HTTP methods in section 4.1. [1] Looking at it, the only methods that are required are GET and HEAD. All others are optional, and the spec explicitly calls out that additional methods may be created and registered with the IANA. Looking closely at this RFC reveals two things: 1. It doesn't modify any of the HTTP RFCs. (There's no "Obsoletes" or "Updates" header.) 2. In section 6 of the QUERY RFC, it requests that the IANA add the new method to its registry. That follows the guidelines in RFC 7231 section 4.1. [1] https://datatracker.ietf.org/doc/html/rfc7231#section-4.1 https://datatracker.ietf.org/doc/html/rfc7231#section-4.1