Hi,
Few comments on the protocol spec:
1. Use of term 'device' in the doc confuses in many places whether it is master
or slave? Term 'master' while refering master device looks better, leaving
device for slave. As I understand master perhaps will be an equipment than
device.
2. Can DB initiate any kind of mesage exchanges with master, an active db
scenario? For example polling whether a registered master is alive, or any
failure scenarios etc?
3. Is there a de-registration or destroy message flow, when master shuts down
or go inoperative?
4. Is it sensible to have all protocol messages having a common prefix like
PAWS or similar? Eg:- PAWS-REG-REQ, PAWS-INT-REQ, etc.
6. Section 6.1: Data element optional/mandatory description can follow the
standard conventions described in section 1 of the spec
Best Regards,
Sajeev Manikkoth
Mobile: +918792292002
Email: [email protected]
http://www.linkedin.com/in/mksajeev
_______________________________________________
paws mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/paws
