From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VvPWP-0006im-JV for bitcoin-development@lists.sourceforge.net; Tue, 24 Dec 2013 10:47:33 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.67 as permitted sender) client-ip=209.85.220.67; envelope-from=tier.nolan@gmail.com; helo=mail-pa0-f67.google.com; Received: from mail-pa0-f67.google.com ([209.85.220.67]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VvPWO-0004dD-CR for bitcoin-development@lists.sourceforge.net; Tue, 24 Dec 2013 10:47:33 +0000 Received: by mail-pa0-f67.google.com with SMTP id rd3so4004754pab.10 for ; Tue, 24 Dec 2013 02:47:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.68.178.197 with SMTP id da5mr31696701pbc.28.1387882046491; Tue, 24 Dec 2013 02:47:26 -0800 (PST) Received: by 10.70.70.196 with HTTP; Tue, 24 Dec 2013 02:47:26 -0800 (PST) In-Reply-To: References: Date: Tue, 24 Dec 2013 10:47:26 +0000 Message-ID: From: Tier Nolan To: "bitcoin-development@lists.sourceforge.net" Content-Type: multipart/alternative; boundary=047d7b86f8365f135704ee4578b9 X-Spam-Score: 2.1 (++) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: github.com] -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 (tier.nolan[at]gmail.com) 1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see ] -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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 1.5 SF_NO_SPF_SPAM SF_NO_SPF_SPAM X-Headers-End: 1VvPWO-0004dD-CR Subject: Re: [Bitcoin-development] Peer Discovery and Overlay X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Dec 2013 10:47:33 -0000 --047d7b86f8365f135704ee4578b9 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Dec 24, 2013 at 8:52 AM, Jeremy Spilman wrote: > Are there any past instances of applications hijacking or interfacing with > the exiting p2p messages, or abusing 'getaddr' functionality? Are there > any guidelines on this, or should there be? > > There was a BIP by Stefan Thomas for adding custom services to the protocol. Discovery would be helpful here too. If this was added, it wouldn't be intended for use in a hostile way though. This one was the custom services BIP. It defines a change to the version message and also custom sub-commands. https://github.com/bitcoin/bips/blob/master/bip-0036.mediawiki This one discusses how network discovery should be handles. https://en.bitcoin.it/wiki/User:Justmoon/BIP_Draft:_Custom_Service_Discovery --047d7b86f8365f135704ee4578b9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable --047d7b86f8365f135704ee4578b9--