[standards-jig] NEW JEP: Direct TCP (JEP-0046)

[Justin Karneges]

Peter,

Whoops, I should have joined in on the discussion.  I have read the conference 
log, and Jer's comments sum up my opinion.

DTCP is for simple direct connections between two clients.  There are 
active/passive modes to decide the direction of the TCP connection, which is 
useful when trying to get around NAT.  The idea is that as long as one peer 
is either not firewalled or has an appropriate port-forward setup, either 
peer can request a successful DTCP.

JOBS is much more complex, and allows you to combine multiple connections 
together (similar to JEP-0037).  It also has a much more complicated iq 
protocol, for various types of connection attributes and admin control.  JOBS 
is expected to be implemented as a server module.  It is also possible that a 
client could implement its own "JOBS server", but this would strip JOBS down 
to the same capability as DTCP, just more complicated.  Actually, it would be 
less capable, since it doesn't support passive connections.

DTCP was designed for direct client-to-client connecting, and nothing more.  
This makes it "good for what it does".  If we want more than this, like 
server routing or multicast, then I say we do that as separate protocols.  It 
might even be possible to reduce the size of JOBS by having it use DTCP as a 
foundation.

Lastly, I want to say that simple specifications are more likely to be 
implemented.  I have already made an implementation of DTCP, and it is over 
1000 lines of code.  I'd imagine that implementing JOBS would be much harder, 
for very little payoff at this time.

-Justin

On Wednesday 18 September 2002 11:50, Peter Saint-Andre wrote:
> Justin,
>
> Perhaps you could explain the ways in which your DTCP is different from
> the Jabber OOB Broadcast Service (JOBS) spec defined in JEP-0042
> (http://www.jabber.org/jeps/jep-0042.html). There were some questions
> about that in today's JSF discussion.
>
> Also, some use cases and requirements would be a helpful addition to your
> DTCP JEP. I may start requiring those sections in order for a JEP to be
> published.
>
> Peter
>
> --
> Peter Saint-Andre
> Jabber Software Foundation
> http://www.jabber.org/people/stpeter.html
>
> On Wed, 18 Sep 2002, Justin Karneges wrote:
> > Dave,
> >
> > I'm not aware of the iChat protocol, but DTCP is not in any way
> > Jabber-ish by itself.  It is just an arbitrary TCP connection.  Sending
> > client-to-client XML over the line might be one application of it, but
> > that is outside the scope of the spec.
> >
> > What the connection will be used for needs to be specified in the
> > <comment> tag, just like DSPS.  What actually goes in here will need to
> > be discussed further (and standardized), I'm guessing.
> >
> > -Justin
> >
> > On Wednesday 18 September 2002 06:56, Dave Smith wrote:
> > > Justin,
> > >
> > > How does this differ from the "Jabber-ish" protocol that iChat uses on
> > > a local network?
> > >
> > > Diz
> > >
> > > On Tuesday, Sep 17, 2002, at 15:00 America/Denver, Peter Saint-Andre
> > >
> > > wrote:
> > > > I've received a new JEP from Justin Karneges on Direct TCP
> > > > connections between clients. You can review it here:
> > > >
> > > > http://www.jabber.org/jeps/jep-0046.html
> > > >
> > > > Peter
> > > >
> > > > --
> > > > Peter Saint-Andre
> > > > Jabber Software Foundation
> > > > http://www.jabber.org/people/stpeter.html
> > > >
> > > > _______________________________________________
> > > > Standards-JIG mailing list
> > > > Standards-JIG at jabber.org
> > > > http://mailman.jabber.org/listinfo/standards-jig
> > >
> > > _______________________________________________
> > > Standards-JIG mailing list
> > > Standards-JIG at jabber.org
> > > http://mailman.jabber.org/listinfo/standards-jig
> >
> > _______________________________________________
> > Standards-JIG mailing list
> > Standards-JIG at jabber.org
> > http://mailman.jabber.org/listinfo/standards-jig
>
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> http://mailman.jabber.org/listinfo/standards-jig