[Standards] Proposed XMPP Extension: Roster Versioning

[Peter Saint-Andre]

Peter Saint-Andre wrote:

> If we change it to a SHOULD will that make people happier? We do
> something similar in server dialback (recommend an algorithm for key
> generation using HMAC-SHA256, but say you can use something else).

Here is revised text:

   The value of the 'version' attribute SHOULD be a non-negative
   integer representing a strictly increasing sequence number that
   is increased with any change to the roster (whether or not the
   client supports this extension) but MAY be a unique identifer that
   is opaque to the client but understood by the server. In any case,
   the 'version' attribute contained in roster pushes MUST be unique.

Can we stop painting this bike shed and move on? :)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mail.jabber.org/pipermail/standards/attachments/20080305/911ecd03/attachment.bin