Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1WjtU6-0005Pk-UI
	for bitcoin-development@lists.sourceforge.net;
	Mon, 12 May 2014 16:53:50 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.41 as permitted sender)
	client-ip=209.85.215.41; envelope-from=gmaxwell@gmail.com;
	helo=mail-la0-f41.google.com; 
Received: from mail-la0-f41.google.com ([209.85.215.41])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WjtU6-0006Dc-5T
	for bitcoin-development@lists.sourceforge.net;
	Mon, 12 May 2014 16:53:50 +0000
Received: by mail-la0-f41.google.com with SMTP id e16so2139237lan.14
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 12 May 2014 09:53:43 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.165.40 with SMTP id yv8mr749130lbb.83.1399913622901;
	Mon, 12 May 2014 09:53:42 -0700 (PDT)
Received: by 10.112.89.68 with HTTP; Mon, 12 May 2014 09:53:42 -0700 (PDT)
Date: Mon, 12 May 2014 09:53:42 -0700
Message-ID: <CAAS2fgRWKWMkzqpQDXJGJYZPyb+vTnaRs3jOrzQ-zG5JJyqr1Q@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
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: 1WjtU6-0006Dc-5T
Subject: [Bitcoin-development] Prenumbered BIP naming
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: Mon, 12 May 2014 16:53:51 -0000

I've noticed some folks struggling to attach labels to their yet to be
numbered BIPs.

I'd recommend people call them "draft-<main author name>-<what it
does>" like draft-maxwell-coinburning in the style of pre-WG IETF
drafts.