In looking at the ABNF in the latest draft (nice job Doug) I noticed something I consider to be a problem w/the ABNF in the draft. See:
10.1. CAP Commands (CMD)
...
Description: All of the command to the CS are supplied in this property. The "OPTIONS" parameter is overloaded and its meaning is dependent on the CMD value supplied.
Formal Definition: The property is defined by the following notation: ...
The concern I have is that there is no room for any future commands. That is, there is no iana-token (or x-token??) in the CMD value. As such there is no possibility to allow new commands so that older CSs will react consistantly to them.
Doug Royer | http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@xxxxxxxxx | Office: (208)612-INET
http://Royer.com/People/Doug | Fax: (866)594-8574
| Cell: (208)520-4044Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature