On 22.01.2018 09:57, Dave Cridland wrote:
> On 19 January 2018 at 18:00, Florian Schmaus wrote:
>> On 30.11.2017 21:10, Florian Schmaus wrote:
>>> I also like to ask Council to consider this ProtoXEP for acceptance.
>> It's been 7 weeks. What is the status of this?
>
> According yo the XMPP Counc
On 19 January 2018 at 18:00, Florian Schmaus wrote:
> On 30.11.2017 21:10, Florian Schmaus wrote:
>> I also like to ask Council to consider this ProtoXEP for acceptance.
>
> It's been 7 weeks. What the status of this?
According yo the XMPP Council Spreadsheet Of Unofficial Doom, that was
voted on
On 30.11.2017 21:10, Florian Schmaus wrote:
> I also like to ask Council to consider this ProtoXEP for acceptance.
It's been 7 weeks. What the status of this?
- Florian
signature.asc
Description: OpenPGP digital signature
___
Standards mailing list
I
* Florian Schmaus [2017-11-30 21:13]:
> I've just submitted version 0.0.5 of the Instant Stream Resumption (ISR)
> ProtoXEP [1].
§5.2 Performing Instant Stream Resumption
| The initiating entity must also provide a element
| qualified by the 'https://xmpp.org/extensions/isr/0' namespace, which
Offlist: looking at diff I spotted another small typo: ommited :)
On Fri, Dec 1, 2017, 16:23 Florian Schmaus wrote:
> On 01.12.2017 13:44, Ivan Vučica wrote:
> > Some typos:
> >
> > - example 1, mechaisms
> > - section 4, “which is send as” (should be sent)
> > - section 5.1 and 5.2 and elsewher
On 01.12.2017 13:44, Ivan Vučica wrote:
> Some typos:
>
> - example 1, mechaisms
> - section 4, “which is send as” (should be sent)
> - section 5.1 and 5.2 and elsewhere, “htpps”
Thanks for your feedback. Much appreciated. I've incorporated it in
0.0.6-SNAPSHOT.
> In “If the with-isr-token' attr
Some typos:
- example 1, mechaisms
- section 4, “which is send as” (should be sent)
- section 5.1 and 5.2 and elsewhere, “htpps”
In “If the with-isr-token' attribute is set to 'false',”, it’s unclear to
me what that attribute is attached to. What if the attribute is omitted?
Thanks for your work
BTW: Are there any servers/clients supporting Multipath TCP? That would
reduce the number of instant stream switches.
On Fri, 2017-12-01 at 11:55 +0100, Daniel Gultsch wrote:
> I'm afraid I can't say much about the SASL2/multi-step integration
> but
> everything else looks good.
> If you want to re
I'm afraid I can't say much about the SASL2/multi-step integration but
everything else looks good.
If you want to resubmit this as a proto xep you have me vote.
Looking forward to implementing this into Conversations. (Hopefully at
least one of the major servers will provide a server side
implemen
I've just submitted version 0.0.5 of the Instant Stream Resumption (ISR)
ProtoXEP [1]. The mechanism performing the instant stream resumption is
now decoupled from the Hashed Token (HT) SASL mechanism, which was one
blockers in the past. The HT SASL mechanism is now being developed at
IETF [2]. I r
10 matches
Mail list logo
