XRPC: should unknown parameters be ignored? Or fail validation?

[snarfed]

Hi all! For records and other lexicon objects, the lexicon spec makes it pretty clear that undefined field are allowed, and code should ignore them and not fail validation. Anyone know if that also applies to unknown parameters, and I guess input fields, in XRPC queries, methods, and subscriptions? I don't see anything in the XRPC spec.

Concretely, I recently saw an XRPC request to /xrpc/com.atproto.server.describeServer?repo=did:plc:aopj66ocaplk5hx4qfeqc4sx. describeServer doesn't have a repo parameter, so my server failed validation on the request and returned a 400, but I suspect it should have ignored repo and served the request normally. nelind on #lexicon on the Discord agreed. Thoughts?