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 <pindar.wong@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>; 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: <CAAS2fgR_nA5p+6+wgJGLddxjswxdqqzOsPg5=s0GNEiEAYFxnQ@mail.gmail.com> References: <55002AD9.2060006@thomaskerin.io> <CAAS2fgR_nA5p+6+wgJGLddxjswxdqqzOsPg5=s0GNEiEAYFxnQ@mail.gmail.com> Date: Thu, 12 Mar 2015 07:24:59 +0800 Message-ID: <CAM7BtUqE4cq3EMHitL-ms3YaDE79=RF09f1eiLc023t8u=GySA@mail.gmail.com> From: Pindar Wong <pindar.wong@gmail.com> To: Gregory Maxwell <gmaxwell@gmail.com> 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 <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: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) <http://www.ietf.org> has the concept of 'Internet Drafts" (ID) <http://www.ietf.org/ietf-ftp/1id-guidelines.txt> and this looks like it has worked for them so far. m2c. p. On Thu, Mar 12, 2015 at 4:16 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote: > On Wed, Mar 11, 2015 at 11:45 AM, Thomas Kerin <me@thomaskerin.io> 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 <div dir=3D"ltr">Hi,<br><div><br>Perhaps at some point consider introducing= something akin to a 'Bitcoin-Draft' (BD) status with some autoexpi= ry period?<br><br></div><div>I understand that the <a href=3D"http://www.ie= tf.org">Internet Engineering Task Force (IETF)</a>=C2=A0 has the concept of= <a href=3D"http://www.ietf.org/ietf-ftp/1id-guidelines.txt">'Internet = Drafts" (ID)</a> and this looks like it has worked for them so far. <b= r><br></div><div>m2c.<br><br></div><div>p.<br><br></div></div><div class=3D= "gmail_extra"><br><div class=3D"gmail_quote">On Thu, Mar 12, 2015 at 4:16 A= M, Gregory Maxwell <span dir=3D"ltr"><<a href=3D"mailto:gmaxwell@gmail.c= om" target=3D"_blank">gmaxwell@gmail.com</a>></span> wrote:<br><blockquo= te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so= lid;padding-left:1ex"><span class=3D"">On Wed, Mar 11, 2015 at 11:45 AM, Th= omas Kerin <<a href=3D"mailto:me@thomaskerin.io">me@thomaskerin.io</a>&g= t; wrote:<br> > I used BIP0090 as a place-holder, but I would like to request a BIP nu= mber<br> > for this now.<br> <br> </span>We have had repeated problems in the past with people working on and= <br> circulating prior draft proposals squatting on each others numbers,<br> and each demanding access to the same numbers. As a matter of<br> procedure I will not assign squatted numbers, but also discussion<br> should come in advance of number assignment; general subject here<br> seems reasonable but many proposals are withdrawn by the party<br> tendering them after further discussion shows the effort to be without<br> public interest or actually subsumed by other functionality. :)<br> <br> Proposals should not be called "BIP[nn]" until they're actual= ly a BIP.<br> =C2=A0 Feel free to call it bip-kerin-multisignature or any other<br> placeholder name that won't be confused with a finished BIP for<br> drafting.<br> <br> If there is any public documentation on the process which caused you<br> specific confusion, please feel free to point me at it and I'll be<br> sure to fix it! Sorry for any confusion there.<br> <br> ---------------------------------------------------------------------------= ---<br> Dive into the World of Parallel Programming The Go Parallel Website, sponso= red<br> by Intel and developed in partnership with Slashdot Media, is your hub for = all<br> things parallel software development, from weekly thought leadership blogs = to<br> news, videos, case studies, tutorials and more. Take a look and join the<br= > conversation now. <a href=3D"http://goparallel.sourceforge.net/" target=3D"= _blank">http://goparallel.sourceforge.net/</a><br> _______________________________________________<br> Bitcoin-development mailing list<br> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo= pment@lists.sourceforge.net</a><br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development= " target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment</a><br> </blockquote></div><br></div> --001a11c25a76798cb505110b93ab--