Sanjeev mentioned: From: [email protected] Sent: Thursday, July 25, 2013 10:31 AM [...] 5. REGISTRATION_REQ, and SPECTRUM_USE_NOTIFY transctions; can it have repsonses like accepted/denied by database? [...]
The JSONRPC spec defines a "notification" as a type of request that needs no response; in fact a response is not even allowed. Since the PAWS SPECTRUM_USE_NOTIFY is "this kind of message" semantically (note that SPECTRUM_USE_RESP is empty), I propose we: * State that the SPECTRUM_USE_NOTIFY uses the JSONRPC "Notification" Request object (see: http://www.jsonrpc.org/specification#notification), and * That we eliminate the SPECTRUM_USE_RESP from the PAWS spec. This is consistent with Vince's characterization that SPECTRUM_USE_NOTIFY is an "async notify, fire-and-forget, from the perspective of the device". Thoughts? Dan Harasty
_______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
