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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1Wn7a5-0006Pz-OL
for bitcoin-development@lists.sourceforge.net;
Wed, 21 May 2014 14:33:21 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.51 as permitted sender)
client-ip=74.125.82.51; envelope-from=jgarzik@bitpay.com;
helo=mail-wg0-f51.google.com;
Received: from mail-wg0-f51.google.com ([74.125.82.51])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wn7a4-000655-UD
for bitcoin-development@lists.sourceforge.net;
Wed, 21 May 2014 14:33:21 +0000
Received: by mail-wg0-f51.google.com with SMTP id x13so2061246wgg.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 21 May 2014 07:33:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to
:content-type;
bh=LRXSvPj5Xbx5Mm4UUS0SuvEhCPkDm8Xqy8iDpLl5dj8=;
b=aQC8UYkrJwM7l4QiEHzGG9NC9Fpc0b4XEOwbewVkYbNJoSMbYCxDElRtVQU/fCD/8N
wMLZOO8jzo5R+zO1fEZdAD24C3+TrT4CNqnKFSWbqR6BduoGTwDc/kwBOOBK5c5FYNpw
nto2zYx7pkHfstDMzFr0b+3NLwkS5GOlyWW/H4cNWP9SQqwWd0p1lwVywEyNSVsTorOE
iBPwX+Isi/VMdNXQlORP3mD6zVsF2klmOPONYzcGGST5FfeSR6ne3UXGEsV0vz29jOwX
/pbuJndP9Secn0XsiHQlw/UQvqAMJa+2/ZEkmvmmu9X27nU7EaTfOQDNIA6kaXQmdroq
7F2A==
X-Gm-Message-State: ALoCoQmwwKrY3VJvfAFPM/vkMs0utyaoWbBLmMKIvcQBThjr+GEQjl66YMSC63m17xZKUPBjSq8H
X-Received: by 10.194.246.234 with SMTP id xz10mr2596848wjc.77.1400682794635;
Wed, 21 May 2014 07:33:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.240.166 with HTTP; Wed, 21 May 2014 07:32:54 -0700 (PDT)
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Wed, 21 May 2014 10:32:54 -0400
Message-ID: <CAJHLa0P_HWm-qqKJxandJfNeN-KoBVwsW14biyNdnu4JESbKew@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
-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: 1Wn7a4-000655-UD
Subject: [Bitcoin-development] PSA: Extending BIP 70 / payment protocol
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: Wed, 21 May 2014 14:33:22 -0000
Please put any payment protocol extensions into a new draft BIP. BIP
70 should not be updated continuously.
Mimic the IETF, where new RFCs are produced as protocols are extended.
Once published, an IETF RFC is considered static.
That said, I think it is OK to be smart, and break the "static" rule a
bit for significant BIP bugs, or harmless maintenance of
links-to-resources.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
