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? [...]
As for possible responses to REGISTRATION_REQ, I have been planning to suggest this: I think we need a new generic error code "REGISTRATION_FAILED". Perhaps a value -203, or the next available -200-block code. This should be used by the Database in response to a REGISTRATION_REQ if no other more specific code is applicable. (For example: if a registration failed due to a missing field in REGISTRATION_REQ, the Database should still send the REQUIRED error; if a REGISTRATION_REQ failed due to the Device being unauthorized, the Database should still send the UNAUTHORIZED error.) Sanjeev: does that address your need sentiment for "a denied registration"? Dan (I have a separate comment about SPECTRUM_USE_NOTIFY, to follow.)
_______________________________________________ paws mailing list [email protected] https://www.ietf.org/mailman/listinfo/paws
