diff --git a/docs/protocol/v2/draft/overview.mdx b/docs/protocol/v2/draft/overview.mdx index 032f478a3..5812abec4 100644 --- a/docs/protocol/v2/draft/overview.mdx +++ b/docs/protocol/v2/draft/overview.mdx @@ -15,6 +15,7 @@ The protocol follows the [JSON-RPC 2.0](https://www.jsonrpc.org/specification) s Unlike base JSON-RPC, request IDs **MUST** be a string or an integer, never `null`. An error response has `id: null` only when the request ID could not be determined. +A receiver rejects a message that has a `method` and an `id` of `null` with `-32600` (Invalid request) and `id: null`. It does not treat the message as a notification. Both sides send requests, and each side chooses IDs for its own requests independently, so the same ID can be in use in both directions. A sender **MUST NOT** reuse an ID while a request with that ID is still awaiting a response. diff --git a/docs/protocol/v2/overview.mdx b/docs/protocol/v2/overview.mdx index adb43721e..e8274f7b5 100644 --- a/docs/protocol/v2/overview.mdx +++ b/docs/protocol/v2/overview.mdx @@ -15,6 +15,7 @@ The protocol follows the [JSON-RPC 2.0](https://www.jsonrpc.org/specification) s Unlike base JSON-RPC, request IDs **MUST** be a string or an integer, never `null`. An error response has `id: null` only when the request ID could not be determined. +A receiver rejects a message that has a `method` and an `id` of `null` with `-32600` (Invalid request) and `id: null`. It does not treat the message as a notification. Both sides send requests, and each side chooses IDs for its own requests independently, so the same ID can be in use in both directions. A sender **MUST NOT** reuse an ID while a request with that ID is still awaiting a response.