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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <dscvlt@gmail.com>) id 1Wo4FT-0004Zj-I9
for bitcoin-development@lists.sourceforge.net;
Sat, 24 May 2014 05:11:59 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.54 as permitted sender)
client-ip=209.85.219.54; envelope-from=dscvlt@gmail.com;
helo=mail-oa0-f54.google.com;
Received: from mail-oa0-f54.google.com ([209.85.219.54])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wo4FS-0004f5-Lq
for bitcoin-development@lists.sourceforge.net;
Sat, 24 May 2014 05:11:59 +0000
Received: by mail-oa0-f54.google.com with SMTP id j17so6504725oag.41
for <bitcoin-development@lists.sourceforge.net>;
Fri, 23 May 2014 22:11:53 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.146.210 with SMTP id te18mr10037920oeb.44.1400908313111;
Fri, 23 May 2014 22:11:53 -0700 (PDT)
Received: by 10.182.225.66 with HTTP; Fri, 23 May 2014 22:11:53 -0700 (PDT)
In-Reply-To: <CAOXABZohe93SSRm1FN5ai2H97eBJV2j+LAjA-39YAaNmX=ep0Q@mail.gmail.com>
References: <CAOXABZohe93SSRm1FN5ai2H97eBJV2j+LAjA-39YAaNmX=ep0Q@mail.gmail.com>
Date: Sat, 24 May 2014 14:41:53 +0930
Message-ID: <CAOXABZrSbG+98m9SBKdft5DOfZV5jF9Zj2LCFVaEsUDouRLGeg@mail.gmail.com>
From: Ashley Holman <dscvlt@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7b5d42f85db1f304fa1e627e
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(dscvlt[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1Wo4FS-0004f5-Lq
Subject: Re: [Bitcoin-development] Cut-through propagation of blocks
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, 24 May 2014 05:11:59 -0000
--047d7b5d42f85db1f304fa1e627e
Content-Type: text/plain; charset=UTF-8
On Sat, May 24, 2014 at 1:27 PM, Ashley Holman <dscvlt@gmail.com> wrote:
>
> * Skip the inv/getdata sequence for new blocks - just push them out
> directly to save 1 roundtrip per hop
>
Upon further reflection, I remove this from my proposal. It's an unrelated
optimisation that probably distracts from the main point which is the
cut-through forwarding. The rest of the proposal still works if the
inv/getdata sequence is retained.
--047d7b5d42f85db1f304fa1e627e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Sat, May 24, 2014 at 1:27 PM, Ashley Holman <span dir=3D"ltr"><<a hre=
f=3D"mailto:dscvlt@gmail.com" target=3D"_blank">dscvlt@gmail.com</a>></s=
pan> wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-st=
yle:solid;padding-left:1ex">
<div dir=3D"ltr"><div>* Skip the inv/getdata sequence for new blocks - just=
push them out directly to save 1 roundtrip per hop</div><div></div></div><=
/blockquote><div><br></div><div>Upon further reflection, I remove this from=
my proposal. =C2=A0It's an unrelated optimisation that probably distra=
cts from the main point which is the cut-through forwarding. =C2=A0The rest=
of the proposal still works if the inv/getdata sequence is retained.<br>
</div></div></div></div>
--047d7b5d42f85db1f304fa1e627e--
|
