Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@exmulti.com>) id 1Sfgdt-0008TN-Pl
	for bitcoin-development@lists.sourceforge.net;
	Sat, 16 Jun 2012 00:13:29 +0000
X-ACL-Warn: 
Received: from mail-lpp01m010-f47.google.com ([209.85.215.47])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Sfgds-0002gb-G1
	for bitcoin-development@lists.sourceforge.net;
	Sat, 16 Jun 2012 00:13:29 +0000
Received: by lags15 with SMTP id s15so2715513lag.34
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 15 Jun 2012 17:13:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:date:message-id:subject:from:to
	:content-type:x-gm-message-state;
	bh=K1RKgAC1gjEIuEsYGaFMXOPaxi0hymyeD+lxFnMxsTs=;
	b=pS0208luDREYIIgnUo72a0C1bHg2sJffZ/cukcIP1uwy11cmQEKpek8U7hlYN9Iqle
	I3BEcNlEdxmDlbWRxeuLhea0oKzk1e4a+bF3sXXTIMlntzetklimavvc73kU0ppSKEj8
	x+M12vdJTf69qPrfHscO4Vbwjt/d1R2nr7uXvvRLhh6+G0TA47Q5cYyEjEfOE18KKP9q
	b2WEltUOq2fCv5xcAY3qHifHyOI/v0Hoo/xueGrMCOEgY8wrcgJ2B5nFiunjHAg0IFbf
	ZGH+4exDo/GNbXGxFQKKeERTD3Yib/iX0gYBzQhZ79xlGigrD4HW2F+54rbJ8oRiYvCz
	qsgA==
MIME-Version: 1.0
Received: by 10.152.148.169 with SMTP id tt9mr7063833lab.49.1339805601883;
	Fri, 15 Jun 2012 17:13:21 -0700 (PDT)
Received: by 10.114.19.70 with HTTP; Fri, 15 Jun 2012 17:13:21 -0700 (PDT)
X-Originating-IP: [2001:4830:1603:2:21c:c0ff:fe79:c8c2]
Date: Fri, 15 Jun 2012 20:13:21 -0400
Message-ID: <CA+8xBpdD31koaVBh1RuDZKH1sygr8z10K=bPz8DepqYOa8i6yg@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmvwUnGLiqZVAmu32T03ioz9vrrbaNhTpMCRu1oGJwkPl3wVUNouF6edofa5NyG+c7vFfm4
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1Sfgds-0002gb-G1
Subject: [Bitcoin-development] Proposed new P2P command and response:
	getcmds, cmdlist
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: Sat, 16 Jun 2012 00:13:29 -0000

Outside of major features advertised network-wide in nService bits,
P2P protocol lacks a good method of enumerating minor features or
extensions.  The version number increment is coarse-grained, and is
not self-documenting.  A simple extension which lists supported
commands is added, as demonstrated in this pull request:

     https://github.com/bitcoin/bitcoin/pull/1471

Another option is for verack to return this information at login,
eliminating the need for a separate command/response.

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com