[standards-jig] RETRACTED: DTCP (JEP-0046)
justin-jdev at affinix.com
Sat Apr 12 00:19:32 UTC 2003
JEP-0065 supercedes JEP-0046.
- 65 uses the SOCKS5 protocol for handshaking, which means existing libraries
and code can be reused, while 46 has a custom protocol.
- 65 has the ability to relay over a specialized proxy component.
- 65 is almost council approved, just one vote shy.
There is no sense in having two competing standards that do nearly the same
On Friday 11 April 2003 04:23 pm, Tom Waters wrote:
> It sure would be nice if JEP authors would summarize in a standard way
> the REASONING behind the retraction... kind of an epitaph, not the be
> confused with an epithet, which is what opponents of the JEP would have
> scrawled on it before its demise.
> -----Original Message-----
> From: standards-jig-admin at jabber.org
> [mailto:standards-jig-admin at jabber.org] On Behalf Of Peter Saint-Andre
> Sent: Friday, April 11, 2003 4:18 PM
> To: standards-jig at jabber.org
> Subject: [standards-jig] RETRACTED: DTCP (JEP-0046)
> At the request of the JEP author, I have changed the status of JEP-0046
> (DTCP) to Retracted. This JEP will not be considered further by the
> Jabber Software Foundation and should not be used as a basis for
More information about the Standards