Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <laanwj@gmail.com>) id 1XFguU-0002sE-LP for bitcoin-development@lists.sourceforge.net; Fri, 08 Aug 2014 09:56:30 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.170 as permitted sender) client-ip=209.85.223.170; envelope-from=laanwj@gmail.com; helo=mail-ie0-f170.google.com; Received: from mail-ie0-f170.google.com ([209.85.223.170]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XFguU-0006eG-08 for bitcoin-development@lists.sourceforge.net; Fri, 08 Aug 2014 09:56:30 +0000 Received: by mail-ie0-f170.google.com with SMTP id rl12so6180082iec.1 for <bitcoin-development@lists.sourceforge.net>; Fri, 08 Aug 2014 02:56:24 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.42.38.137 with SMTP id c9mr1536538ice.94.1407491784661; Fri, 08 Aug 2014 02:56:24 -0700 (PDT) Received: by 10.64.27.228 with HTTP; Fri, 8 Aug 2014 02:56:24 -0700 (PDT) In-Reply-To: <CANEZrP2wYcxJhxRRa86Nm9ENtK2SA5VNG-L7f5pHb_W=Ajcj5Q@mail.gmail.com> References: <CAJHLa0Ok6s5xQcMSeLa69adLBXEaicuXqcg45eZrwYtVFbx-dA@mail.gmail.com> <CANEZrP2wYcxJhxRRa86Nm9ENtK2SA5VNG-L7f5pHb_W=Ajcj5Q@mail.gmail.com> Date: Fri, 8 Aug 2014 11:56:24 +0200 Message-ID: <CA+s+GJD+9qpwFcVfHOCCsFYjmk7A0V=65vG-7jJ6D7jj4Pi_7g@mail.gmail.com> From: Wladimir <laanwj@gmail.com> To: Mike Hearn <mike@plan99.net> Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) 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 (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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 X-Headers-End: 1XFguU-0006eG-08 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:56:30 -0000 On Fri, Aug 8, 2014 at 11:45 AM, Mike Hearn <mike@plan99.net> wrote: > 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? He wants to use it to advertise services that are not part of the P2P protocol itself, but run on a different port. Reserving services bits for those is not acceptable. All the NODE_EXT_SERVICES bit does is advertise the P2P "getextsrv" command to get information, such as the port to connect on, for the auxilary service. Wladimir