From: Mark Friedenbach <mark@monetize•io>
To: Jay F <jayf@outlook•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] A bitcoin UDP P2P protocol extension
Date: Sat, 23 Mar 2013 19:27:31 -0700 [thread overview]
Message-ID: <CACh7GpFVcXt+k52PBZLpdt=VTmH7dbQoC+2Z4ZenYPBjDZKY3g@mail.gmail.com> (raw)
In-Reply-To: <BLU0-SMTP30A4EFEB3349A94802E930C8D60@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
Nearly all of these new(er) user-mode transports run over UDP, so you can
hole-punch and port forward just the same. Some which don't can
nevertheless be tunneled, to the same effect.
Ultimately I don't have any skin in this game though. Just trying to save
someone from reinventing a perfectly good wheel ;)
On Sat, Mar 23, 2013 at 5:57 PM, Jay F <jayf@outlook•com> wrote:
> My first concern was that I and about everyone else only has TCP/UDP
> port forwarding, but at least for the first:
>
> UDT uses UDP to transfer bulk data with its own reliability control and
> congestion control mechanisms. Multiple UDT flows can share a single UDP
> port, thus a firewall can open only one UDP port for all UDT connections.
>
> The latter appears not so friendly to NAT.
>
>
> On 3/23/2013 3:30 PM, Mark Friedenbach wrote:
> > If you're considering a datagram protocol, you might be interested in
> > some more modern alternatives to UDP:
> >
> > UDT: Breaking the Data Transfer Bottleneck
> > http://udt.sourceforge.net/
> >
> > Stream Control Transmission Protocol
> > http://en.wikipedia.org/wiki/Stream_Control_Transmission_Protocol
> >
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 2531 bytes --]
prev parent reply other threads:[~2013-03-24 2:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 7:17 Jeff Garzik
2013-03-23 10:42 ` Randy Willis
2013-03-23 14:52 ` Luke-Jr
2013-03-23 15:24 ` Jeff Garzik
2013-03-23 22:01 ` Caleb James DeLisle
2013-03-23 22:30 ` Mark Friedenbach
2013-03-24 0:57 ` Jay F
2013-03-24 1:22 ` Gregory Maxwell
2013-03-24 2:08 ` Jeff Garzik
2013-03-24 9:11 ` Ralph J.Mayer
2013-03-24 2:27 ` Mark Friedenbach [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACh7GpFVcXt+k52PBZLpdt=VTmH7dbQoC+2Z4ZenYPBjDZKY3g@mail.gmail.com' \
--to=mark@monetize$(echo .)io \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jayf@outlook$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox