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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1VaZCD-0004c5-Cf
for bitcoin-development@lists.sourceforge.net;
Sun, 27 Oct 2013 22:52:33 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.176 as permitted sender)
client-ip=209.85.212.176; envelope-from=gavinandresen@gmail.com;
helo=mail-wi0-f176.google.com;
Received: from mail-wi0-f176.google.com ([209.85.212.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VaZCB-0000MM-I6
for bitcoin-development@lists.sourceforge.net;
Sun, 27 Oct 2013 22:52:33 +0000
Received: by mail-wi0-f176.google.com with SMTP id ex4so714984wid.15
for <bitcoin-development@lists.sourceforge.net>;
Sun, 27 Oct 2013 15:52:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.188.164 with SMTP id gb4mr6556165wic.52.1382914345322;
Sun, 27 Oct 2013 15:52:25 -0700 (PDT)
Received: by 10.194.156.163 with HTTP; Sun, 27 Oct 2013 15:52:25 -0700 (PDT)
In-Reply-To: <526B45DB.2030200@jerviss.org>
References: <274a1888-276c-4aa6-a818-68f548fbe0fa@me.com>
<9DCDB8F6-E3B2-426B-A41E-087E66B3821A@gmail.com>
<526B45DB.2030200@jerviss.org>
Date: Mon, 28 Oct 2013 08:52:25 +1000
Message-ID: <CABsx9T2OMA_u=S9yUh2j78QDuCDUorYctktuixjwAjqc6neW=Q@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: kjj <bitcoin-devel@jerviss.org>
Content-Type: multipart/alternative; boundary=001a11c25c9e4ecf4004e9c0d649
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
(gavinandresen[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: 1VaZCB-0000MM-I6
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Feedback requested: "reject" p2p message
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: Sun, 27 Oct 2013 22:52:33 -0000
--001a11c25c9e4ecf4004e9c0d649
Content-Type: text/plain; charset=ISO-8859-1
RE: use HTTP-like status codes:
Okey dokey, I'll add a one-byte machine-readable HTTP-like status code.
Unless y'all want a 32-bit status code. Or maybe a varint. Or a
three-character numeric string. I really and truly don't care, but I am
writing this code right now so whatever you want, decide quickly.
If anybody has strong feelings about what the reject categories should be,
then please take the time to write a specific list, I can't read your
mind....
--
--
Gavin Andresen
--001a11c25c9e4ecf4004e9c0d649
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">RE: use HTTP-like status codes:<div><br></div><div>Okey do=
key, I'll add a one-byte machine-readable HTTP-like status code. Unless=
y'all want a 32-bit status code. =A0Or maybe a varint. Or a three-char=
acter numeric string. I really and truly don't care, but I am writing t=
his code right now so whatever you want, decide quickly.</div>
<div><br></div><div>If anybody has strong feelings about what the reject ca=
tegories should be, then please take the time to write a specific list, I c=
an't read your mind....</div><div class=3D"gmail_extra"><br><br>-- <br>
--<br>Gavin Andresen<br>
</div></div>
--001a11c25c9e4ecf4004e9c0d649--
|
