Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YVpzv-0002oy-Mk for bitcoin-development@lists.sourceforge.net; Wed, 11 Mar 2015 23:25:07 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.172 as permitted sender) client-ip=209.85.212.172; envelope-from=pindar.wong@gmail.com; helo=mail-wi0-f172.google.com; Received: from mail-wi0-f172.google.com ([209.85.212.172]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YVpzu-0002dZ-39 for bitcoin-development@lists.sourceforge.net; Wed, 11 Mar 2015 23:25:07 +0000 Received: by wivr20 with SMTP id r20so15884596wiv.3 for ; Wed, 11 Mar 2015 16:25:00 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.10.67 with SMTP id g3mr12588391wib.78.1426116300080; Wed, 11 Mar 2015 16:25:00 -0700 (PDT) Received: by 10.194.156.166 with HTTP; Wed, 11 Mar 2015 16:24:59 -0700 (PDT) In-Reply-To: References: <55002AD9.2060006@thomaskerin.io> Date: Thu, 12 Mar 2015 07:24:59 +0800 Message-ID: From: Pindar Wong To: Gregory Maxwell Content-Type: multipart/alternative; boundary=001a11c25a76798cb505110b93ab 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: 1YVpzu-0002dZ-39 Cc: Bitcoin Development 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 23:25:07 -0000 --001a11c25a76798cb505110b93ab Content-Type: text/plain; charset=UTF-8 Hi, 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. m2c. p. On Thu, Mar 12, 2015 at 4:16 AM, Gregory Maxwell wrote: > On Wed, Mar 11, 2015 at 11:45 AM, Thomas Kerin wrote: > > I used BIP0090 as a place-holder, but I would like to request a BIP > number > > for this now. > > We have had repeated problems in the past with people working on and > circulating prior draft proposals squatting on each others numbers, > and each demanding access to the same numbers. As a matter of > procedure I will not assign squatted numbers, but also discussion > should come in advance of number assignment; general subject here > seems reasonable but many proposals are withdrawn by the party > tendering them after further discussion shows the effort to be without > public interest or actually subsumed by other functionality. :) > > Proposals should not be called "BIP[nn]" until they're actually a BIP. > Feel free to call it bip-kerin-multisignature or any other > placeholder name that won't be confused with a finished BIP for > drafting. > > If there is any public documentation on the process which caused you > specific confusion, please feel free to point me at it and I'll be > sure to fix it! Sorry for any confusion there. > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for > all > things parallel software development, from weekly thought leadership blogs > to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --001a11c25a76798cb505110b93ab Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

Perhaps at some point consider introducing= something akin to a 'Bitcoin-Draft' (BD) status with some autoexpi= ry period?

I understand that the Internet Engineering Task Force (IETF)=C2=A0 has the concept of= 'Internet = Drafts" (ID) and this looks like it has worked for them so far.
m2c.

p.


On Thu, Mar 12, 2015 at 4:16 A= M, Gregory Maxwell <gmaxwell@gmail.com> wrote:
On Wed, Mar 11, 2015 at 11:45 AM, Th= omas Kerin <me@thomaskerin.io&g= t; wrote:
> I used BIP0090 as a place-holder, but I would like to request a BIP nu= mber
> for this now.

We have had repeated problems in the past with people working on and=
circulating prior draft proposals squatting on each others numbers,
and each demanding access to the same numbers. As a matter of
procedure I will not assign squatted numbers, but also discussion
should come in advance of number assignment; general subject here
seems reasonable but many proposals are withdrawn by the party
tendering them after further discussion shows the effort to be without
public interest or actually subsumed by other functionality. :)

Proposals should not be called "BIP[nn]" until they're actual= ly a BIP.
=C2=A0 Feel free to call it bip-kerin-multisignature or any other
placeholder name that won't be confused with a finished BIP for
drafting.

If there is any public documentation on the process which caused you
specific confusion, please feel free to point me at it and I'll be
sure to fix it! Sorry for any confusion there.

---------------------------------------------------------------------------= ---
Dive into the World of Parallel Programming The Go Parallel Website, sponso= red
by Intel and developed in partnership with Slashdot Media, is your hub for = all
things parallel software development, from weekly thought leadership blogs = to
news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--001a11c25a76798cb505110b93ab--