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 <mh.in.england@gmail.com>) id 1XFgjl-0005ol-A9
	for bitcoin-development@lists.sourceforge.net;
	Fri, 08 Aug 2014 09:45:25 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.218.51 as permitted sender)
	client-ip=209.85.218.51; envelope-from=mh.in.england@gmail.com;
	helo=mail-oi0-f51.google.com; 
Received: from mail-oi0-f51.google.com ([209.85.218.51])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XFgjk-0006Fv-KR
	for bitcoin-development@lists.sourceforge.net;
	Fri, 08 Aug 2014 09:45:25 +0000
Received: by mail-oi0-f51.google.com with SMTP id g201so3512189oib.24
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 08 Aug 2014 02:45:19 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.158.8 with SMTP id wq8mr29012308oeb.40.1407491119202;
	Fri, 08 Aug 2014 02:45:19 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Fri, 8 Aug 2014 02:45:19 -0700 (PDT)
In-Reply-To: <CAJHLa0Ok6s5xQcMSeLa69adLBXEaicuXqcg45eZrwYtVFbx-dA@mail.gmail.com>
References: <CAJHLa0Ok6s5xQcMSeLa69adLBXEaicuXqcg45eZrwYtVFbx-dA@mail.gmail.com>
Date: Fri, 8 Aug 2014 11:45:19 +0200
X-Google-Sender-Auth: J9kFW2C9ZXbzIiLzv19DqYV3ygM
Message-ID: <CANEZrP2wYcxJhxRRa86Nm9ENtK2SA5VNG-L7f5pHb_W=Ajcj5Q@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=047d7bd6ac482f490005001b1006
X-Spam-Score: -0.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
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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: 1XFgjk-0006Fv-KR
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related
	services
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: Fri, 08 Aug 2014 09:45:25 -0000

--047d7bd6ac482f490005001b1006
Content-Type: text/plain; charset=UTF-8

Given that we're not running out of service bits and service bits mean you
don't have to try connecting to every node to find out what services it
supports, why not keep using the existing extension mechanism until we
start running out of bits?

--047d7bd6ac482f490005001b1006
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Given that we&#39;re not running out of service bits and s=
ervice bits mean you don&#39;t have to try connecting to every node to find=
 out what services it supports, why not keep using the existing extension m=
echanism until we start running out of bits?</div>

--047d7bd6ac482f490005001b1006--