Re: [Standards] Advancing XEP-0387: XMPP Compliance Suites 2017

2017-09-27 Thread Matthew Wild
On 27 September 2017 at 18:05, Sam Whited wrote: > Hi all, > > It's time for another round of reviews of the 2017 Compliance Suites > [1]. I think all the changes that people suggested last time have been > addressed. Anything else before we move it to the official >

[Standards] Advancing XEP-0387: XMPP Compliance Suites 2017

2017-09-27 Thread Sam Whited
Hi all, It's time for another round of reviews of the 2017 Compliance Suites [1]. I think all the changes that people suggested last time have been addressed. Anything else before we move it to the official recommendation? —Sam [1]: https://xmpp.org/extensions/xep-0387.html -- Sam Whited

Re: [Standards] Call for Experience for XEP-0368: SRV records for XMPP over TLS

2017-09-27 Thread Dave Cridland
On 27 September 2017 at 16:37, Jonas Wielicki wrote: > aioxmpp as client library supports this XEP minus ALPN. If ALPN support in a > second client implementation is all it needs, I can probably fix that in a > week or so (I took a quick look, the TLS library supports it). I

[Standards] 2017-09-27 XSF Council Minutes

2017-09-27 Thread JC Brand
2017-09-27 XSF Council Minutes == Present: Tobias, SamWhited, daniel, dwd Minute taker: jcbrand 1) Vote on "XEP-0060: Add pubsub#multi-items in Publish-Subscribe features #500" The URL: https://github.com/xsf/xeps/pull/500 Tobias, daniel and SamWhited will all

Re: [Standards] Call for Experience for XEP-0368: SRV records for XMPP over TLS

2017-09-27 Thread Jonas Wielicki
On Mittwoch, 27. September 2017 08:51:48 CEST Dave Cridland wrote: > The rules on "two implementations" are, I believe, aimed to correspond > to RFC 2026's Section 4.1.2, with the addition of licensing > requirements. > > I'd note, in particular, the second paragraph: > >The requirement for

Re: [Standards] 2017-09-20 XSF Council Minutes

2017-09-27 Thread Tobias Markmann
Hi, my missing votes are inline. On Wed, Sep 20, 2017 at 5:46 PM, JC Brand wrote: > 2017-09-20 XSF Council Minutes > == > > Present: Tobias, Link Mauve, SamWhited, jonasw, daniel > Minute taker: jcbrand > > 1) Vote on accepting "Consistent Color

Re: [Standards] Rename XEP status identifiers

2017-09-27 Thread Kevin Smith
On 27 Sep 2017, at 15:08, Sam Whited wrote: > > On Wed, Sep 27, 2017, at 02:08, Kevin Smith wrote: >> Are they not then going to be upset if there are backwards-incompatible >> changes in a new namespace? We try not to do that in Draft XEPs, but >> that’s the reason they’re

Re: [Standards] Rename XEP status identifiers

2017-09-27 Thread Sam Whited
On Wed, Sep 27, 2017, at 02:08, Kevin Smith wrote: > Are they not then going to be upset if there are backwards-incompatible > changes in a new namespace? We try not to do that in Draft XEPs, but > that’s the reason they’re Draft rather than Final, to give us that > option. "Stableish"? —Sam

Re: [Standards] Call for Experience for XEP-0368: SRV records for XMPP over TLS

2017-09-27 Thread Evgeny Khramtsov
Wed, 27 Sep 2017 14:33:07 +0100 Dave Cridland wrote: > But in any case, I think we can declare victory. Neat. ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe:

Re: [Standards] Call for Experience for XEP-0368: SRV records for XMPP over TLS

2017-09-27 Thread Dave Cridland
On 27 September 2017 at 11:34, Evgeny Khramtsov wrote: > Wed, 27 Sep 2017 13:10:58 +0300 > Evgeny Khramtsov wrote: > >> Wed, 27 Sep 2017 10:17:14 +0100 >> Dave Cridland wrote: >> >> > I believe I have the right records and code running

Re: [Standards] Call for Experience for XEP-0368: SRV records for XMPP over TLS

2017-09-27 Thread Evgeny Khramtsov
Wed, 27 Sep 2017 13:10:58 +0300 Evgeny Khramtsov wrote: > Wed, 27 Sep 2017 10:17:14 +0100 > Dave Cridland wrote: > > > I believe I have the right records and code running at > > dave.cridland.net if you'd like to try. > > Yes, it works (connected to

Re: [Standards] Call for Experience for XEP-0368: SRV records for XMPP over TLS

2017-09-27 Thread Evgeny Khramtsov
Wed, 27 Sep 2017 10:17:14 +0100 Dave Cridland wrote: > I believe I have the right records and code running at > dave.cridland.net if you'd like to try. Yes, it works (connected to 5270 port and TLS auth is accepted), but your server then connected on my _xmpp-server port,

Re: [Standards] Call for Experience for XEP-0368: SRV records for XMPP over TLS

2017-09-27 Thread Dave Cridland
On 27 September 2017 at 10:09, Evgeny Khramtsov wrote: > Wed, 27 Sep 2017 08:51:48 +0100 > Dave Cridland wrote: > >> * We have one S2S implementation, supporting SNI. >> >> On that basis, I don't *think* we can include S2S in Final, which is >> frustrating.

Re: [Standards] Call for Experience for XEP-0368: SRV records for XMPP over TLS

2017-09-27 Thread Dave Cridland
On 27 September 2017 at 02:37, Travis Burtrum wrote: > On 09/25/2017 06:57 AM, Dave Cridland wrote: >> On 25 September 2017 at 06:06, Travis Burtrum wrote: >>> >>> Conversations has had support since before this became a XEP actually. >>> >>> Everyone I

Re: [Standards] Rename XEP status identifiers

2017-09-27 Thread Kevin Smith
On 26 Sep 2017, at 20:35, Sam Whited wrote: > > On Tue, Sep 26, 2017, at 14:19, Ivan Vučica wrote: >> And now, to bikeshed a bit on the proposed naming: To a casual reader, >> stable has similar implications as final. Especially if said reader is >> used to Debian's use of

Re: [Standards] Rename XEP status identifiers

2017-09-27 Thread Dave Cridland
On 26 September 2017 at 20:19, Ivan Vučica wrote: > And now, to bikeshed a bit on the proposed naming: To a casual reader, > stable has similar implications as final. Especially if said reader is used > to Debian's use of the word. I think to developers, the two *do* have