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; 
MIME-Version: 1.0
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
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP for standard multi-signature P2SH
	addresses
Precedence: list

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.