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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W3ZoI-00032Z-I6 for bitcoin-development@lists.sourceforge.net; Wed, 15 Jan 2014 23:23:46 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of midnightdesign.ws designates 50.87.144.70 as permitted sender) client-ip=50.87.144.70; envelope-from=boydb@midnightdesign.ws; helo=gator3054.hostgator.com; Received: from gator3054.hostgator.com ([50.87.144.70]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1W3ZoH-0006G1-QX for bitcoin-development@lists.sourceforge.net; Wed, 15 Jan 2014 23:23:46 +0000 Received: from [209.85.212.173] (port=60215 helo=mail-wi0-f173.google.com) by gator3054.hostgator.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80) (envelope-from ) id 1W3ZYE-0001Au-21 for bitcoin-development@lists.sourceforge.net; Wed, 15 Jan 2014 17:07:10 -0600 Received: by mail-wi0-f173.google.com with SMTP id d13so4484718wiw.12 for ; Wed, 15 Jan 2014 15:07:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=OT/6IxgE+a1+H/GfiHD1zdNThURyrFVlmg0XYFX90HE=; b=OEvaSHKPZSyJMurHdxJSMTya6copadVYpwKofzkXKlye50bEYnhd6b37mvRK1eZIMJ M6gAJEudEMoy9Uf99GFsxPRFZ8J7CCzRTyyQw7/ZCIBSeDDHOYff4ZL3Nidfp1QyHa0D LEVmF42Bqky+Xwgq43Y3dPdVsKel55bgyM4UfWKDkbKxfOm086/pTL9XiyswzldIRaeh 9Uxksyz4BcgoHnfyu7whAZgbfk41T7Pxorzpv3q92pBCaIsN/Dm6nUe3IZvNmZoLZ5At HRplVe1xImmITaUnSulVZ4417qDjL37Y+iiDhZArWZh05yD6Lm7yCav65zT5pHW2iGsu R8kQ== X-Gm-Message-State: ALoCoQnei7lM1Wg9wXCdXHmOLz8yO6TmXd1n727fPSGo9LAyjIIOPddsnYzuNBoKPyrEdqbY8PUy MIME-Version: 1.0 X-Received: by 10.194.187.101 with SMTP id fr5mr207923wjc.76.1389827228014; Wed, 15 Jan 2014 15:07:08 -0800 (PST) Received: by 10.227.12.193 with HTTP; Wed, 15 Jan 2014 15:07:07 -0800 (PST) In-Reply-To: <5747D5DF-879B-4A60-8BD6-18251E7D5F47@plan99.net> References: <5747D5DF-879B-4A60-8BD6-18251E7D5F47@plan99.net> Date: Wed, 15 Jan 2014 17:07:07 -0600 Message-ID: From: Brooks Boyd To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=047d7bd6b9ac39ae7a04f00a5e2a X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator3054.hostgator.com X-AntiAbuse: Original Domain - lists.sourceforge.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - midnightdesign.ws X-BWhitelist: no X-Source-IP: 209.85.212.173 X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: (mail-wi0-f173.google.com) [209.85.212.173]:60215 X-Source-Auth: midnight X-Email-Count: 1 X-Source-Cap: bWlkbmlnaHQ7bWlkbmlnaHQ7Z2F0b3IzMDU0Lmhvc3RnYXRvci5jb20= 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 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1W3ZoH-0006G1-QX Subject: Re: [Bitcoin-development] Tor / SPV 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: Wed, 15 Jan 2014 23:23:46 -0000 --047d7bd6b9ac39ae7a04f00a5e2a Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable > > 2) Secondly, we bump the protocol version, add a service flag and > introduce a new P2P protocol command =93tor?=94. If a client sends a tor? > message to a node that has the new service flag set, it will respond with= a > new =93tor=94 message that contains a regular addr packet, with a single > address, the IPv6-ified version of its hidden service name. > Rather than a separate message type that implies binding a clearnet IP to a hidden service ID, why not add the service flag that the peer would like Tor addresses, and the remote peer can then add IPv6-ified hidden service addresses to "addr" messages? May need to modify the network address format to include the ability to differentiate IPv6 clearnet vs. Tor addresses, but then you remove the implication that a node has to give both public and private IPs to a peer. If it's part of a batch of "addr"s, it could be my own hidden service ID, but it could also be one that I learned from someone else and is now propagating, for anyone to bootstrap with Tor hidden service peers if they'd like. Brooks --047d7bd6b9ac39ae7a04f00a5e2a Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
2) Secondly, we bump the protocol version, add a service flag and introduce= a new P2P protocol command =93tor?=94. If a client sends a tor? message to= a node that has the new service flag set, it will respond with a new =93to= r=94 message that contains a regular addr packet, with a single address, th= e IPv6-ified version of its hidden service name.


Rather than a separate message type that implies bi= nding a clearnet IP to a hidden service ID, why not add the service flag th= at the peer would like Tor addresses, and the remote peer can then add IPv6= -ified hidden service addresses to "addr" messages? May need to m= odify the network address format to include the ability to differentiate IP= v6 clearnet vs. Tor addresses, but then you remove the implication that a n= ode has to give both public and private IPs to a peer. If it's part of = a batch of "addr"s, it could be my own hidden service ID, but it = could also be one that I learned from someone else and is now propagating, = for anyone to bootstrap with Tor hidden service peers if they'd like.

Brooks
--047d7bd6b9ac39ae7a04f00a5e2a--