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
118
119
120
121
122
123
124
125
126
127
128
129
130
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pindar.wong@gmail.com>) id 1YVqOG-0000jT-1R
for bitcoin-development@lists.sourceforge.net;
Wed, 11 Mar 2015 23:50:16 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.180 as permitted sender)
client-ip=74.125.82.180; envelope-from=pindar.wong@gmail.com;
helo=mail-we0-f180.google.com;
Received: from mail-we0-f180.google.com ([74.125.82.180])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YVqOE-0006xl-MB
for bitcoin-development@lists.sourceforge.net;
Wed, 11 Mar 2015 23:50:16 +0000
Received: by wesk11 with SMTP id k11so12687450wes.13
for <bitcoin-development@lists.sourceforge.net>;
Wed, 11 Mar 2015 16:50:08 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.109.9 with SMTP id ho9mr80675368wjb.29.1426117808251;
Wed, 11 Mar 2015 16:50:08 -0700 (PDT)
Received: by 10.194.156.166 with HTTP; Wed, 11 Mar 2015 16:50:08 -0700 (PDT)
In-Reply-To: <CAAS2fgTvqTmkujVKLryH+iX7JFd=jJp89p7bggrdmRHAbWiNxQ@mail.gmail.com>
References: <55002AD9.2060006@thomaskerin.io>
<CAAS2fgR_nA5p+6+wgJGLddxjswxdqqzOsPg5=s0GNEiEAYFxnQ@mail.gmail.com>
<CAM7BtUqE4cq3EMHitL-ms3YaDE79=RF09f1eiLc023t8u=GySA@mail.gmail.com>
<CAAS2fgTvqTmkujVKLryH+iX7JFd=jJp89p7bggrdmRHAbWiNxQ@mail.gmail.com>
Date: Thu, 12 Mar 2015 07:50:08 +0800
Message-ID: <CAM7BtUrMzCa_MhMgqW_JVGy4Dia3DYvC_yetjW+zqH8wOuZyMQ@mail.gmail.com>
From: Pindar Wong <pindar.wong@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bf10a125e67b205110bed08
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
(pindar.wong[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: 1YVqOE-0006xl-MB
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP for standard multi-signature P2SH
addresses
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, 11 Mar 2015 23:50:16 -0000
--047d7bf10a125e67b205110bed08
Content-Type: text/plain; charset=UTF-8
Understood... perhaps just add something like:
'After copy-editing and acceptance,* a BIP number is assigned* and it will
be published here.'?
https://en.bitcoin.it/wiki/Bitcoin_Improvement_Proposals
p.
On Thu, Mar 12, 2015 at 7:34 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> On Wed, Mar 11, 2015 at 11:24 PM, Pindar Wong <pindar.wong@gmail.com>
> wrote:
> > Perhaps at some point consider introducing something akin to a
> > 'Bitcoin-Draft' (BD) status with some autoexpiry period?
> >
> > I understand that the Internet Engineering Task Force (IETF) has the
> > concept of 'Internet Drafts" (ID) and this looks like it has worked for
> them
> > so far.
>
> Thats more or less what posting to the list is supposed to be.
> Creating a draft document requires no approval, beyond filling out the
> right form.
>
> Perhaps calling out that as a distinct step would be better, indeed.
>
--047d7bf10a125e67b205110bed08
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Understood... perhaps just add something like:<br><br=
>'After copy-editing and acceptance,<b> <i>a BIP number is assigned</i>=
</b> and it will be published here.'?<br><br><a href=3D"https://en.bitc=
oin.it/wiki/Bitcoin_Improvement_Proposals">https://en.bitcoin.it/wiki/Bitco=
in_Improvement_Proposals</a><br><br></div>p.<br><div><br></div></div><div c=
lass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Mar 12, 2015 at=
7:34 AM, Gregory Maxwell <span dir=3D"ltr"><<a href=3D"mailto:gmaxwell@=
gmail.com" target=3D"_blank">gmaxwell@gmail.com</a>></span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><span class=3D"">On Wed, Mar 11, 2015 at 11:24=
PM, Pindar Wong <<a href=3D"mailto:pindar.wong@gmail.com">pindar.wong@g=
mail.com</a>> wrote:<br>
> Perhaps at some point consider introducing something akin to a<br>
> 'Bitcoin-Draft' (BD) status with some autoexpiry period?<br>
><br>
> I understand that the Internet Engineering Task Force (IETF)=C2=A0 has=
the<br>
> concept of 'Internet Drafts" (ID) and this looks like it has =
worked for them<br>
> so far.<br>
<br>
</span>Thats more or less what posting to the list is supposed to be.<br>
Creating a draft document requires no approval, beyond filling out the<br>
right form.<br>
<br>
Perhaps calling out that as a distinct step would be better, indeed.<br>
</blockquote></div><br></div>
--047d7bf10a125e67b205110bed08--
|
