Peter Saint-Andre wrote:
> 1. We modify XEP-0174 so it just defines _presence._tcp as a discovery
> mechanism, as a result of which you have an IP address and port that you
> can use for a direct TCP connection that functions as a transport for an
> e2e XML stream.
>
> 2. We split the e2e XML streams stuff out from XEP-0174 into a new
> "e2e-streams" spec, which defines how you use whatever reliable
> transport is close to hand (direct TCP connection, IBB, SOCKS5, ice-tcp,
> etc.) as the transport for an e2e XML stream (this can be unencrypted as
> all XEP-0174 implementations do now, or upgraded to encrypted using
> STARTTLS, which is what we'd recommend -- but this way it is
> backwards-compatible and enables code reuse).
It should get a note about clientCert requests.
> 3. The current XTLS spec morphs into a new "Jingle-xmpp" spec that
> defines a Jingle application type for an XMPP session (as defined in
> XEP-streams), where that application type can use IBB, SOCKS5, ice-tcp,
> or any other reliable transport.
Sounds ok to me. Funny thing is that XTLS gets closer again to my
first idea (except that I did not used jingle). If you need some help
writing 2. or 3. give me a call. I will be away for the weekend but
could help you out on sunday evening (which will be the whole sunday
in your timezone).
Dirk
P.S.: Too bad I implemented the current XTLS today for testing
--
[X] <-- nail here for new monitor
