From: Wladimir <laanwj@gmail•com>
To: Matt Whitlock <bip@mattwhitlock•name>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: allocate 8 service bits for experimental use
Date: Tue, 17 Jun 2014 10:16:01 +0200 [thread overview]
Message-ID: <CA+s+GJB_zpgth4=7O2vAOH2RPTz=9xZtbWH=dr6hYzDm8osNyw@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJBJ5aXNEv+8zARXHPL1+fg1Etd3-EhF2TeW+gS-_r+s3g@mail.gmail.com>
On Tue, Jun 17, 2014 at 10:08 AM, Wladimir <laanwj@gmail•com> wrote:
> On Tue, Jun 17, 2014 at 10:02 AM, Matt Whitlock <bip@mattwhitlock•name> wrote:
>> On Tuesday, 17 June 2014, at 9:57 am, Wladimir wrote:
>>> Yes, as I said in the github topic
>>> (https://github.com/bitcoin/bitcoin/pull/4351) I suggest we adapt a
>>> string-based name space for extensions.
>>
>> Why use textual strings? These fields are not for human consumption. Why not use UUIDs, which are fixed length and will not waste as much bandwidth in the protocol? Or if you'd prefer a hierarchical namespace, you could use OIDs, a la ASN.1.
Also it IS useful for these fields to be human readable for
statistics, peer list views and such. When encountering a new, unknown
extension when connecting to a node it's much more useful to get a
google-able string to find out what it is about, than some long
hexadecimal or dotted-number identifier.
Wladimir
next prev parent reply other threads:[~2014-06-17 8:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 7:23 Peter Todd
2014-06-17 7:57 ` Wladimir
2014-06-17 8:02 ` Matt Whitlock
2014-06-17 8:08 ` Wladimir
2014-06-17 8:16 ` Wladimir [this message]
2014-06-17 21:29 ` Jeff Garzik
2014-06-18 6:20 ` Wladimir
2014-06-18 10:23 ` Wladimir
2014-06-18 11:48 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+s+GJB_zpgth4=7O2vAOH2RPTz=9xZtbWH=dr6hYzDm8osNyw@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bip@mattwhitlock$(echo .)name \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox