[standards-jig] DTCP/JOBS/etc Madness -- Part Deux
dizzyd at jabber.org
Tue Dec 17 01:46:02 UTC 2002
-----BEGIN PGP SIGNED MESSAGE-----
I've drafted an initial version of my proposal into a JEP:
Perhaps this will help clarify the use of SOCKS5 in this setup. As for
comparing this to DTCP, I guess I don't follow.
On Monday, Dec 16, 2002, at 17:26 America/Denver, Justin Karneges wrote:
> On Monday 16 December 2002 07:37 am, Dave Smith wrote:
>> I'm going to investigate this further and amend my proposal to use
>> SOCKS5 as wire protocol.
> After reading RFC 1928, I'm trying to see how this would work, yet stay
> transparent when involving a proxy.
> In terms of DTCP:
> 1) Serving client generates a DTCP key for the session (nothing new
> 2) Serving client would request a session with the proxy via Jabber,
> using the
> DTCP key.
> 3) DTCP jabber handshake
> 4) Connecting client connects to a host, and SOCKS authenticates using
> serving client's JID and key as username and password respectively.
> 5) If the host is the serving client itself (ie, not a proxy), then the
> serving client finishes the SOCKS handshake. END.
> 6) If the host is a proxy, then the proxy generates a 'ticket key',
> and sends
> this (along with the DTCP key it received) to the serving client via
> 7) The serving client then SOCKS authenticates with the proxy, using
> its JID
> and 'ticket key' as the username and password respectively.
> 8) The proxy then finishes the SOCKS handshake to both the serving and
> connecting clients (or sends errors to each, as necessary). END.
> What do others think?
> Standards-JIG mailing list
> Standards-JIG at jabber.org
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 (Build 349) Beta
-----END PGP SIGNATURE-----
More information about the Standards