From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1YVq9H-00005D-DF
	for bitcoin-development@lists.sourceforge.net;
	Wed, 11 Mar 2015 23:34:47 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.172 as permitted sender)
	client-ip=209.85.223.172; envelope-from=gmaxwell@gmail.com;
	helo=mail-ie0-f172.google.com; 
Received: from mail-ie0-f172.google.com ([209.85.223.172])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YVq9G-0007vA-Kx
	for bitcoin-development@lists.sourceforge.net;
	Wed, 11 Mar 2015 23:34:47 +0000
Received: by ieclw3 with SMTP id lw3so2002674iec.2
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 11 Mar 2015 16:34:41 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.31.14 with SMTP id f14mr31478099iof.28.1426116881092;
	Wed, 11 Mar 2015 16:34:41 -0700 (PDT)
Received: by 10.107.6.133 with HTTP; Wed, 11 Mar 2015 16:34:41 -0700 (PDT)
In-Reply-To: <CAM7BtUqE4cq3EMHitL-ms3YaDE79=RF09f1eiLc023t8u=GySA@mail.gmail.com>
References: <55002AD9.2060006@thomaskerin.io>
	<CAAS2fgR_nA5p+6+wgJGLddxjswxdqqzOsPg5=s0GNEiEAYFxnQ@mail.gmail.com>
	<CAM7BtUqE4cq3EMHitL-ms3YaDE79=RF09f1eiLc023t8u=GySA@mail.gmail.com>
Date: Wed, 11 Mar 2015 23:34:41 +0000
Message-ID: <CAAS2fgTvqTmkujVKLryH+iX7JFd=jJp89p7bggrdmRHAbWiNxQ@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Pindar Wong <pindar.wong@gmail.com>
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gmaxwell[at]gmail.com)
	-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: 1YVq9G-0007vA-Kx
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:34:47 -0000

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.