On Mittwoch, 27. September 2017 17:25:02 CEST Dave Cridland wrote:
> On 27 September 2017 at 16:37, Jonas Wielicki <jo...@wielicki.name> 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
> > don’t have a server to test against though, and thus it hasn’t been on my
> > short list until now.
> 
> I'm not actually convinced ALPN is an interoperability requirement of
> this protocol anyway.
> 
> It's nice to have it, probably, but lacking it would not mean that the
> essential notion of Direct TLS broke.

Indeed, but if the choice is to remove ALPN from the XEP or not to advance it 
to Final, I would personally prefer this XEP to stay in Draft for now. ALPN 
*is* a useful tool in this context when multiplexing is needed or desired.

If you’re only talking about removing ALPN for S2S, I have no strong opinion 
about that.


> >> On that basis, I don't *think* we can include S2S in Final,
> > 
> > We’re talking about Draft here, not Final. But I assume this is a typo?
> 
> The CFE is for Final, isn't it? The XEP is Draft now.

Ha, you’re right. Got something confused in my mind, sorry for carrying on 
that confusion to the list.


kind regards,
Jonas

Attachment: signature.asc
Description: This is a digitally signed message part.

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

Reply via email to