summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeff Garzik <jgarzik@exmulti.com>2013-03-23 11:24:41 -0400
committerbitcoindev <bitcoindev@gnusha.org>2013-03-23 15:24:48 +0000
commitb8712f153f448614ff6c91b0a23426e452ae9509 (patch)
tree888a14e81bb67f73165b8597d5f6a21abcc0221e
parent0b908ed5ed6ce4cef02087f5a571115c4e8eebde (diff)
downloadpi-bitcoindev-b8712f153f448614ff6c91b0a23426e452ae9509.tar.gz
pi-bitcoindev-b8712f153f448614ff6c91b0a23426e452ae9509.zip
Re: [Bitcoin-development] A bitcoin UDP P2P protocol extension
-rw-r--r--88/301716d89aabb56a689b1185b1f7f44ea4fd7b91
1 files changed, 91 insertions, 0 deletions
diff --git a/88/301716d89aabb56a689b1185b1f7f44ea4fd7b b/88/301716d89aabb56a689b1185b1f7f44ea4fd7b
new file mode 100644
index 000000000..1d14257dd
--- /dev/null
+++ b/88/301716d89aabb56a689b1185b1f7f44ea4fd7b
@@ -0,0 +1,91 @@
+Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
+ helo=mx.sourceforge.net)
+ by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <jgarzik@exmulti.com>) id 1UJQJM-0005nH-UO
+ for bitcoin-development@lists.sourceforge.net;
+ Sat, 23 Mar 2013 15:24:48 +0000
+X-ACL-Warn:
+Received: from mail-pa0-f43.google.com ([209.85.220.43])
+ by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1UJQJL-0001Qm-OD
+ for bitcoin-development@lists.sourceforge.net;
+ Sat, 23 Mar 2013 15:24:48 +0000
+Received: by mail-pa0-f43.google.com with SMTP id rl6so376361pac.2
+ for <bitcoin-development@lists.sourceforge.net>;
+ Sat, 23 Mar 2013 08:24:41 -0700 (PDT)
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+ d=google.com; s=20120113;
+ h=mime-version:x-received:x-originating-ip:in-reply-to:references
+ :date:message-id:subject:from:to:cc:content-type:x-gm-message-state;
+ bh=tbhXH7zmp3Mh62c3D4Jm/U5aFjQ+hw5WFytUIUlfa44=;
+ b=W7+NVjKd0LMQc+CCiJya9i+Q4YkD5X6msHc5KCL1TPMh2IHeFnJfTtuaOm4rcD65KI
+ Hb1pEShCZr1+Bj3b/5mAqMwx9WddPcWWS1p0mkGIAcBXxrCWQPYVGzhYEZB0OZLmTQRe
+ +gHSuduHNRtCiGPn9FE9/lgcFrlgYrp4OsfnegubowG41AiHkNGwFc1a+rG/ZvYKnA7w
+ nGnM/H5kKyr4Ivz5GZn4743mG6h044auhiJinF8gWiQqom6LZ3ja8YwZbabC2So7rPCa
+ R14khBphA+zdgOfH9Zs2KCFwQBT8/DdGgoPRF0AreNoJxQltAqMSGUmZt/EKqYkgnB4Y
+ Yyow==
+MIME-Version: 1.0
+X-Received: by 10.68.238.163 with SMTP id vl3mr8255309pbc.177.1364052281847;
+ Sat, 23 Mar 2013 08:24:41 -0700 (PDT)
+Received: by 10.68.146.133 with HTTP; Sat, 23 Mar 2013 08:24:41 -0700 (PDT)
+X-Originating-IP: [99.43.178.25]
+In-Reply-To: <201303231452.23042.luke@dashjr.org>
+References: <CA+8xBpe9D=poPyJ=soGdN3sovqdmvyGGij6FM8PHYGUB5aUkzQ@mail.gmail.com>
+ <1364035346.19716.YahooMailNeo@web161601.mail.bf1.yahoo.com>
+ <201303231452.23042.luke@dashjr.org>
+Date: Sat, 23 Mar 2013 11:24:41 -0400
+Message-ID: <CA+8xBpfvTQ9pEygPmeSf0guOsECu6uecOG-KB=GVXtPKNo23ZQ@mail.gmail.com>
+From: Jeff Garzik <jgarzik@exmulti.com>
+To: Luke-Jr <luke@dashjr.org>
+Content-Type: text/plain; charset=ISO-8859-1
+X-Gm-Message-State: ALoCoQka3aGDDUauPHm0ObzjEAtxLdf9ZCqLoX8cGivBfoVyT8cMEkqVnYaLBCsHr4poVR2eLugh
+X-Spam-Score: 0.0 (/)
+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
+ See http://spamassassin.org/tag/ for more details.
+X-Headers-End: 1UJQJL-0001Qm-OD
+Cc: bitcoin-development@lists.sourceforge.net
+Subject: Re: [Bitcoin-development] A bitcoin UDP P2P protocol extension
+X-BeenThere: bitcoin-development@lists.sourceforge.net
+X-Mailman-Version: 2.1.9
+Precedence: list
+List-Id: <bitcoin-development.lists.sourceforge.net>
+List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
+List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
+List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
+List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
+List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
+X-List-Received-Date: Sat, 23 Mar 2013 15:24:49 -0000
+
+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
+
+