Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1S7W7W-0006nl-G9
	for bitcoin-development@lists.sourceforge.net;
	Tue, 13 Mar 2012 18:06:50 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.175 as permitted sender)
	client-ip=209.85.212.175; envelope-from=mh.in.england@gmail.com;
	helo=mail-wi0-f175.google.com; 
Received: from mail-wi0-f175.google.com ([209.85.212.175])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1S7W7R-0005Vj-1n
	for bitcoin-development@lists.sourceforge.net;
	Tue, 13 Mar 2012 18:06:50 +0000
Received: by wibhn6 with SMTP id hn6so5307775wib.10
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 13 Mar 2012 11:06:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.139.129 with SMTP id c1mr10135011wej.48.1331661998711;
	Tue, 13 Mar 2012 11:06:38 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.216.162.66 with HTTP; Tue, 13 Mar 2012 11:06:38 -0700 (PDT)
Date: Tue, 13 Mar 2012 19:06:38 +0100
X-Google-Sender-Auth: 7vwdDQKOIb-6-Xq0RLQV7MNfaf4
Message-ID: <CANEZrP17mwsmhShUKDOrZFsotLD+PHt6omNpL3-r21RtmHRX4Q@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.5 (-)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	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: 1S7W7R-0005Vj-1n
Subject: [Bitcoin-development] Adding a pong message
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: Tue, 13 Mar 2012 18:06:50 -0000

https://github.com/bitcoin/bitcoin/pull/932 adds a "pong" message that
echoes back a 64 bit nonce contained in the ping, if the protocol
version is new enough.

The goal of this is to make it easier for clients, especially mobile
clients, to quickly check if a connection is stale, and also to see if
a remote node is overloaded so we can avoid talking to it. A common
case where this happens is if the remote node is itself downloading
the block chain or doing something equally intensive.

Any objections?