[standards-jig] DTCP/JOBS/etc Madness -- Part Deux

Dave Smith dizzyd at jabber.org
Tue Dec 17 01:46:02 UTC 2002


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Justin,

I've drafted an initial version of my proposal into a JEP: 
http://www.jabber.org/jeps/jep-0065.html

Perhaps this will help clarify the use of SOCKS5 in this setup.  As for 
comparing this to DTCP, I guess I don't follow.

Diz

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 
> here)
> 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 
> the
> 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 
> jabber.
> 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?
>
> -Justin
>
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> http://mailman.jabber.org/listinfo/standards-jig
>

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 (Build 349) Beta

iQA/AwUBPf6B5GDRN3IVRx7DEQJKugCgtM6y+fg+on+i2bY8K7gUEx6fnz4Anj/+
ndvGlTYd7CuG5U2nyFXOjFoK
=JPyt
-----END PGP SIGNATURE-----




More information about the Standards mailing list