Re: [Standards] Should we split XEP-0300 (Use of Cryptographic Hash Functions in XMPP) up?

2019-01-02 Thread Kevin Smith
On 16 Dec 2018, at 09:37, Jonas Schäfer wrote: > > This may sound ridiculous at first, given that the text easily fits on less > than 10 pages in font size, but bear with me. > > I was proposing an LC for it to Kevin, because the protocol IMO is rather > mature, but then I realized that we

Re: [Standards] Should we split XEP-0300 (Use of Cryptographic Hash Functions in XMPP) up?

2018-12-17 Thread Jonas Schäfer
On Montag, 17. Dezember 2018 17:24:10 CET Peter Saint-Andre wrote: > +1, although the hash function *recommendations* don't exactly feel > informational to me. XEP-0001 states: > An Informational XEP typically defines best practices for implementation or > deployment of an existing protocol

Re: [Standards] Should we split XEP-0300 (Use of Cryptographic Hash Functions in XMPP) up?

2018-12-17 Thread Peter Saint-Andre
On 12/16/18 2:37 AM, Jonas Schäfer wrote: > This may sound ridiculous at first, given that the text easily fits on less > than 10 pages in font size, but bear with me. > > I was proposing an LC for it to Kevin, because the protocol IMO is rather > mature, but then I realized that we have a

[Standards] Should we split XEP-0300 (Use of Cryptographic Hash Functions in XMPP) up?

2018-12-16 Thread Jonas Schäfer
This may sound ridiculous at first, given that the text easily fits on less than 10 pages in font size, but bear with me. I was proposing an LC for it to Kevin, because the protocol IMO is rather mature, but then I realized that we have a slight issue here: - The protocol could probably even