wip clarify DeclareMiningJob.Success + DeclaraMiningJob.Error

06-Job-Declaration-Protocol.md

@@ -100,13 +100,23 @@ More specifically, the `SipHash 2-4` variant is used. Aside from the preimage (w
 
 ### 6.3.5 `DeclareMiningJob.Success` (Server -> Client)
 
+A response sent by JDS acknowledging some Custom Job declaration.
+
+xxx todo xxx clarify `new_mining_job_token` with regards to:
+- async mining (`SetCustomMiningJob`)
+- potential JDS signature
+
 | Field Name           | Data Type | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | -------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | request_id           | U32       | Identifier of the original request                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | new_mining_job_token | B0_255    | Unique identifier provided by the pool of the job that the Job Declarator has declared with the pool. It MAY be the same token as DeclareMiningJob::mining_job_token if the pool allows to start mining on not yet declared job. If the token is different from the one in the corresponding DeclareMiningJob message (irrespective of if the client is already mining using the original token), the client MUST send a SetCustomMiningJob message on each Mining Protocol client which wishes to mine using the declared job. |
 
 ### 6.3.6 `DeclareMiningJob.Error` (Server->Client)
 
+A response sent by JDS rejecting some Custom Job declaration.
+
+This should be a trigger for fallback into some other Pool+JDS or solo mining.
+
 | Field Name    | Data Type | Description                                            |
 | ------------- | --------- | ------------------------------------------------------ |
 | request_id    | U32       | Identifier of the original request                     |