Am Mittwoch, den 11.12.2019, 17:10 +0000 schrieb Kevin Smith: > > On 9 Sep 2019, at 20:37, Florian Schmaus <f...@geekplace.eu> wrote: > > Furthermore, xep359 makes it very clear > > that xep359-IDs are just unique and stable within the scope of the > > id-assigning-entity (this allows implementations to use simple > > mechanisms to generate the ID without considering collisions with > > other > > id-assigning-entities). > > Good point, thanks Flo. Although I’m not sure that 359 does make it > clear that it’s not globally unique, actually the opposite - I > believe it’s a SHOULD on using UUID, and my understanding has always > been that these are intended to be globally unique (I realise you > have authority on claims of the original intention) from reading it. > This isn’t the only XEP that’s written on the basis of the unique IDs > being unique :) > > We probably need to clear this up - was I the only one with this > misconception? (i.e. do we update 422 (and others) or 359?) > Yes this was also my understanding all the way through. It is the reason all my MAM indices are composite including id and assigning entity. If we go for UUID we'd probably need to mention which version it should be and what to consider a namespace and name (if v5) or MAC (if v1) to make sure there won't be other assumptions (like reproducible UUIDs - for duplication/collision detection)
--RR _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
