Re: [Standards] XMPP Council Minutes 2018-06-20

2018-06-23 Thread Goffi
Hi,

Le samedi 23 juin 2018, 13:24:22 CEST Tedd Sterr a écrit :

> 3) Advance XEP-0363: HTTP File Upload
> Kev: [on-list] (without the agenda in advance, failed to look at this
> again) Sam: [on-list] (still nervous about the http headers stuff being
> too restrictive) Daniel: +1
> Dave: [pending]
> Georg: [pending]

Did you read my feedback about this? In particular what about my remarks on 
expiration date? I would like to have an answer on that, it's particularly 
important in my opinion. Thanks!

Cheers
Goffi


___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [Standards] XMPP Council Minutes 2018-06-20

2018-06-23 Thread Kim Alvefur
On Sat, Jun 23, 2018 at 11:28:54AM +, Tedd Sterr wrote:
> On Stream Compression: as TLS is pretty much a requirement now and it
> already does compression (unless explicitly disabled), wouldn't that
> make Stream Compression surplus to requirements at this point?

It is explicitly disabled and it should be.

You do not want the SASL exchange to go through compression.

-- 
Kim "Zash" Alvefur


signature.asc
Description: PGP signature
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [Standards] XMPP Council Minutes 2018-06-20

2018-06-23 Thread Tedd Sterr
Contrary to vicious rumours floating around, I have no interest in supplanting 
Dave's position as Chair.
With only a few hours remaining and no agenda forthcoming, I thought a meeting 
with some agenda would be better than with none - and the agenda is largely 
straightforward.

Why was "Deprecate XEP-0229" there? That's entirely my 'fault.'
There was a vote on advancing Stream Compression in April [1], and as result of 
that not passing there was the suggestion of adding 0318 to the next agenda.
The next agenda [2] was, coincidentally, my previous attempt to oust Dave 
written by myself and so I added it. However, it was subsequently skipped in 
the meeting for lack of time (XEP-0050 took almost the whole meeting) [3], but 
was never revisited.
So, with an otherwise bare agenda and nothing else obvious to add, I 
surreptitiously added it again. ...and I would've gotten away with it too, if 
it weren't for those meddling kids!

[1] https://mail.jabber.org/pipermail/standards/2018-April/034768.html
[2] https://mail.jabber.org/pipermail/standards/2018-April/034789.html
[3] https://mail.jabber.org/pipermail/standards/2018-April/034790.html


On Stream Compression: as TLS is pretty much a requirement now and it already 
does compression (unless explicitly disabled), wouldn't that make Stream 
Compression surplus to requirements at this point?

___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


[Standards] XMPP Council Minutes 2018-06-20

2018-06-23 Thread Tedd Sterr
http://logs.xmpp.org/council/2018-06-20/#15:00:27

1) Roll Call and Sandwich Orders
Present: Kev, Sam, Daniel
Stuck in endless meetings: Dave
Deep under-cover behind enemy lines: Georg

2) Isn't it nice that Tedd Sterr does the agenda?
[It's a dirty job, but somebody should do it.]

3) Advance XEP-0363: HTTP File Upload
Kev: [on-list] (without the agenda in advance, failed to look at this again)
Sam: [on-list] (still nervous about the http headers stuff being too 
restrictive)
Daniel: +1
Dave: [pending]
Georg: [pending]

4) Deprecate XEP-0229: Stream Compression with LZW (and XEP-0138: Stream 
Compression)
Kev doesn't know why this appeared on the agenda - Daniel thinks it was voted 
on 6 months ago - Kev agrees that it did come up before.
Daniel thinks it's probably due to perceived insecurity; Kev sees that there 
was a vote in April not to advance it.

Sam: +0
Kev: -0
Daniel: -0
Dave: [pending]
Gerg: [pending]

Daniel thinks compression is generally nice to have, and maybe this could be 
made secure with proper business rules.
Sam agrees that compression is nice to have, but isn't against getting rid of 
it.
Kev says that some sort of compression is desirable, as XMPP is heavily 
compressible and sometimes used on poor links.
Daniel thinks this issue should be revisited soon. Kev agrees - it could be 
Stream Compression, or EXI (XEP-0322), or something else - but deprecating 
isn't the Right Thing™ at the moment; Sam agrees.

5) Outsanding Votes et les Vol-au-vents
[Georg had two -- now done: 
https://mail.jabber.org/pipermail/standards/2018-June/035191.html]

6) Next Meeting, Next Meal
2018-06-27 1500 UTC

7) Bier und AOB
Nobody shouts imminently.

8) Close and Take Your Rubbish Home with You
Thanks all; show's over!


Discussion of EXI continues...
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___