1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <willis.randy@ymail.com>) id 1UJLuD-0006wi-8B
for bitcoin-development@lists.sourceforge.net;
Sat, 23 Mar 2013 10:42:33 +0000
X-ACL-Warn:
Received: from nm21.bullet.mail.bf1.yahoo.com ([98.139.212.180])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1UJLuC-0002QU-1Q
for bitcoin-development@lists.sourceforge.net;
Sat, 23 Mar 2013 10:42:33 +0000
Received: from [98.139.212.150] by nm21.bullet.mail.bf1.yahoo.com with NNFMP;
23 Mar 2013 10:42:26 -0000
Received: from [98.139.212.209] by tm7.bullet.mail.bf1.yahoo.com with NNFMP;
23 Mar 2013 10:42:26 -0000
Received: from [127.0.0.1] by omp1018.mail.bf1.yahoo.com with NNFMP;
23 Mar 2013 10:42:26 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 560021.31951.bm@omp1018.mail.bf1.yahoo.com
Received: (qmail 31306 invoked by uid 60001); 23 Mar 2013 10:42:26 -0000
X-YMail-OSG: QIxf.w4VM1lxwdu44VFTr5OvytMiOU24tf7Gny8zZL3ksXv
1jCRdIh5DA0G7CiOjxkYbrHyAkWqC94xUvH8LF0nmOuEy6LjWM1IgkPdBrFC
fMLGy3a14Vjki3VGnVXCd9UqSdRuV37VtT4tUzFNdjZbzO8ME.jqm4Fdeqt6
WlWS0Ragrgoa90V8x6E4usGXbFaZ3dOUS3_fnRHVwBofEVZy.nWsD4zVNCnf
LFpWnf6D8zDrItQ.gtKRYZZNInv3agzTwNsNplSgMcN7Q1k1YU7G_AVKjScc
ruX9HHh6RtEXe5G2vmptBeA9jROCpi60ow.l9QRoQMI3Q02dg_OfLUXGhaWS
V0Xvsr2Dvrl1vmOFpqYAsoHaSYDCbJZi57iDli5hRBNzhwfYYtLcluWyVjAZ
VCJ2wL2myPWfOy28SKWPMVHjdagu_fE3t7pKbFJ1pBmaVxBPbD8.lQr2GP5i
mTI3FqUCHJ6gdmRN3Azcq7TqThaFMxngsJxHAksO830jPftleJF.jptjA.rv
HwoZA_UOVS2byjSfqQenWawWI.Ia1tOvPaly8uKqqLGZp24P4rwp3tNVyE_4
x.9xf7mKgobxUzvfDVDF.m2aLOEOE_2TVHJII5Erm8S30vPUdRcA5NOZNLz4
ShAVA4_CQr3gijJ4RreQvh0_AdcsBaTqb4E5D32hKtMapEbQ_iXJrxjii0EA
v7b1FigrdNAPqQ.Ha
Received: from [213.144.148.243] by web161601.mail.bf1.yahoo.com via HTTP;
Sat, 23 Mar 2013 03:42:26 PDT
X-Rocket-MIMEInfo: 002.001,
Tm90IGxvb2tlZCBhdCBjb2RlIHlldCwgc29tZSB0aG91Z2h0czoKCjEpIEluIElQdjQgbWF4IFVEUCBkYXRhIHNpemUgaXMgNjU1MDcgYnl0ZXMuCjIpIFdoYXQgYWJvdXQgYmlnIG1lc3NhZ2VzIChibG9jayk_CjMpIEkgdGhpbmsgcmVsYXkgc3BlZWQgY2FuIGJlIGluY3JlYXNlZCBvbmx5IGJ5IHJlZHVjaW5nIG5ldHdvcmsgZGlhbWV0ZXIuIAoKSW50cm9kdWNpbmcgc3VwZXItbm9kZXMgd2l0aCB0aG91c2FuZHMgb2YgY29ubmVjdGVkIHBlZXJzIGNhbiBncmVhdGx5IGhlbHAgaGVyZS4KNCkgVGhlIG9ubHkBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.138.524
References: <CA+8xBpe9D=poPyJ=soGdN3sovqdmvyGGij6FM8PHYGUB5aUkzQ@mail.gmail.com>
Message-ID: <1364035346.19716.YahooMailNeo@web161601.mail.bf1.yahoo.com>
Date: Sat, 23 Mar 2013 03:42:26 -0700 (PDT)
From: Randy Willis <willis.randy@ymail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CA+8xBpe9D=poPyJ=soGdN3sovqdmvyGGij6FM8PHYGUB5aUkzQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.1 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(willis.randy[at]ymail.com)
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.139.212.180 listed in list.dnswl.org]
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UJLuC-0002QU-1Q
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
Reply-To: Randy Willis <willis.randy@ymail.com>
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 10:42:33 -0000
Not looked at code yet, some thoughts:=0A=0A1) In IPv4 max UDP data size is=
65507 bytes.=0A2) What about big messages (block)?=0A3) I think relay spee=
d can be increased only by reducing network diameter. =0A=0AIntroducing sup=
er-nodes with thousands of connected peers can greatly help here.=0A4) The =
only (IMO) UDP advantage: hole punching. But requirement of active =0A=0ATC=
P connection defies it. And hole punching will need protocol extension.=0A5=
) unsolicited tx broadcast will increase traffic of nodes (especially well-=
connected)=0Aand less people will run them.=0A=0A=0A---- Original Message -=
----=0A=0AFrom: Jeff Garzik <jgarzik@exmulti.com>=0ATo: Bitcoin Development=
<bitcoin-development@lists.sourceforge.net>=0ACc: =0ASent: Saturday, March=
23, 2013 7:17 AM=0ASubject: [Bitcoin-development] A bitcoin UDP P2P protoc=
ol extension=0A=0AHere is a rough draft implementation of a UDP P2P protoco=
l extension=0Afor bitcoin:=0A=0A=A0 =A0 https://github.com/jgarzik/bitcoin/=
tree/udp=0A=A0 =A0 http://yyz.us/bitcoin/udp-v0.patch=0A=0AProtocol specif=
ication (such that it is):=0A=0A- UDP, bound to same port as TCP P2P (norma=
lly 8333)=0A- Active, simultaneous TCP P2P connection required (useful agai=
nst DoS=0Aand other attacks)=0A- Same message format as TCP P2P, same pchMe=
ssageStart conventions,=0Aetc. (my CNetMessage pull req would be helpful he=
re)=0A- Multiple P2P messages per UDP packet permitted=0A- Max UDP packet s=
ize 100*1024 bytes=0A- Advertises NODE_UDP in nServices=0A- New "getudpcook=
" TCP P2P command returns a "udpcook" message,=0Acontaining a yummy cookie=
=0A- UDP P2P commands "inv", "tx" and "addr" are handled as if received via=
TCP=0A- UDP P2P command "udpsub" sets a mask, that subscribes to one or mo=
re=0Adata broadcasts.=0A- When USM_INV_BCAST mask bit is set, receive "inv"=
messages via UDP=0Arather than TCP.=0A=0AProject and design goals (or, why=
do this?):=0A=0A- It is theorized that UDP may be useful for some messages=
we=0Abroadcast throughout the network=0A- A productive discussion STARTS w=
ith code, otherwise discussion=0Acontinues forever.=0A- Investigate improvi=
ng "inv" relay speed=0A- Investigate unconditional "tx" broadcasting via UD=
P, as "inv"=0Aalternative, for small tx's.=0A- Investigate improving block =
relay speed (or perhaps block header relay speed)=0A- Open up new design av=
enues, for P2P patterns more suited to UDP than=0ATCP in general.=0A=0A-- =
=0AJeff Garzik=0AexMULTI, Inc.=0Ajgarzik@exmulti.com=0A=0A-----------------=
-------------------------------------------------------------=0AEveryone ha=
tes slow websites. So do we.=0AMake your web apps faster with AppDynamics=
=0ADownload AppDynamics Lite for free today:=0Ahttp://p.sf.net/sfu/appdyn_d=
2d_mar=0A_______________________________________________=0ABitcoin-developm=
ent mailing list=0ABitcoin-development@lists.sourceforge.net=0Ahttps://list=
s.sourceforge.net/lists/listinfo/bitcoin-development=0A
|
