public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@exmulti.com>
To: Luke-Jr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] A bitcoin UDP P2P protocol extension
Date: Sat, 23 Mar 2013 11:24:41 -0400	[thread overview]
Message-ID: <CA+8xBpfvTQ9pEygPmeSf0guOsECu6uecOG-KB=GVXtPKNo23ZQ@mail.gmail.com> (raw)
In-Reply-To: <201303231452.23042.luke@dashjr.org>

On Sat, Mar 23, 2013 at 10:52 AM, Luke-Jr <luke@dashjr.org> wrote:
> On Saturday, March 23, 2013 10:42:26 AM Randy Willis wrote:
>> Introducing super-nodes with thousands of connected peers can greatly help
>> here.
>
> UDP is connectionless.
> I would hope any UDP bitcoin protocol doesn't try to emulate a connection. :/

It depends on the usage.  Simply broadcasting a TX or INV to a remote
peer does not require a connection, clearly...  but you probably want
to signal acceptance of those messages somehow.

But other uses, like subscribing to a broadcast, does require some
notion of an association.

In the rough draft, a parallel TCP connection with version/verack
sequence is required, and you may make use of it if a connection is
needed.

But that is just one approach.  A more robust, heavyweight UDP P2P
might be a hole-punching TCP alternative.  It's up to the community
and results of experimentation.

Bittorrent has evolved a full transfer protocol over UDP, to get
around firewalls and the like.
-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com



  reply	other threads:[~2013-03-23 15:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-23  7:17 [Bitcoin-development] A bitcoin UDP P2P protocol extension Jeff Garzik
2013-03-23 10:42 ` Randy Willis
2013-03-23 14:52   ` Luke-Jr
2013-03-23 15:24     ` Jeff Garzik [this message]
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

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='CA+8xBpfvTQ9pEygPmeSf0guOsECu6uecOG-KB=GVXtPKNo23ZQ@mail.gmail.com' \
    --to=jgarzik@exmulti.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=luke@dashjr.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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