Re: [Standards] Message-IDs

On 28 Feb 2018, at 14:47, Denver Gingerich wrote: > > On Wed, Feb 28, 2018 at 08:59:01AM +, Kevin Smith wrote: >> On 13 Feb 2018, at 16:57, Simon Friedberger wrote: >>>E3. Simply make the ID: FROM-TIMESTAMP. >>>Here FROM needs to be

Re: [Standards] Message-IDs

On Wed, Feb 28, 2018 at 08:59:01AM +, Kevin Smith wrote: > On 13 Feb 2018, at 16:57, Simon Friedberger wrote: > > E3. Simply make the ID: FROM-TIMESTAMP. > > Here FROM needs to be the eventual FROM after possible > > rewriting. Can > > that be

Re: [Standards] Message-IDs

On Mittwoch, 28. Februar 2018 10:28:01 CET Kevin Smith wrote: > On 26 Feb 2018, at 15:59, Simon Friedberger wrote: > > So, lest this discussion just die. Here is a proposal: > Thanks for the proposal. Bashing follows. > > >Client-A generates message-ID based on

Re: [Standards] Message-IDs

On 26 Feb 2018, at 15:59, Simon Friedberger wrote: > So, lest this discussion just die. Here is a proposal: Thanks for the proposal. Bashing follows. >Client-A generates message-ID based on HASH(connection_counter, >server_salt). The connection_counter needs to

Re: [Standards] Message-IDs

On 13 Feb 2018, at 16:57, Simon Friedberger wrote: > During the discussion on the different ID types at the summit I had an > idea for > a possible solution to the problem but not a sufficient understanding of the > problem to even discuss it. I tried to find somebody to

Re: [Standards] Message-IDs

On Montag, 26. Februar 2018 16:59:46 CET Simon Friedberger wrote: > So, lest this discussion just die. Here is a proposal: > > * > > Client-A generates message-ID based on HASH(connection_counter, > server_salt). The connection_counter needs to be maintained only for > one

Re: [Standards] Message-IDs

So, lest this discussion just die. Here is a proposal: * Client-A generates message-ID based on HASH(connection_counter, server_salt). The connection_counter needs to be maintained only for one connection. The server salt is server generated, anew for each connection and is

Re: [Standards] Message-IDs

On Dienstag, 13. Februar 2018 21:42:56 CET Simon Friedberger wrote: > >> ... > > You are mixing multiple problems with multiple solutions, which was > > probably in an effort to get the whole picture, but also leads to > > confusion. I personally would like to concentrate on solving C4, where > >

Re: [Standards] Message-IDs

Hi Michal, thank you for your comments. I will address them inline. > I'm really tempted to say that the new message routing (in next gen > XMPP as discussed during summit) > must require the message stanza to have "id" attribute. I personally > think that uuid v4 would enough here. > This, to

Re: [Standards] Message-IDs

Hi Simon Thanks for refreshing the topic. Few things from me below (perspective of XMPP server developer, MongooseIM). Best regards Michal Piotrowski michal.piotrow...@erlang-solutions.com On 13 February 2018 at 17:57, Simon Friedberger wrote: > Hello List! > > >

Re: [Standards] Message-IDs

On 13.02.2018 21:42, Simon Friedberger wrote: > On 13.02.2018 17:57, Simon Friedberger wrote: >>>     C2. According to Daniel it is not clear which ID should be used when >>>     referencing things. In other words if he gets a delivery receipt >>> for an >>>     ID the client might have

Re: [Standards] Message-IDs

Hi Florian, thanks for chiming in! On 13.02.2018 17:57, Simon Friedberger wrote: >>     C2. According to Daniel it is not clear which ID should be used when >>     referencing things. In other words if he gets a delivery receipt >> for an >>     ID the client might have based that on the