From: Jonas Schnelli <dev@jonasschnelli•ch>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP151 protocol incompatibility
Date: Mon, 13 Feb 2017 11:07:12 +0100 [thread overview]
Message-ID: <ff7c24ba-7c70-efaf-a319-b1aebfd8a3bd@jonasschnelli.ch> (raw)
In-Reply-To: <dde5349d-c430-ad57-30c7-77954ff1a94d@voskuil.org>
[-- Attachment #1.1: Type: text/plain, Size: 1225 bytes --]
> All adopted BIPs to date have followed this
> pattern. This is not the same and it is not helpful to imply that it is
> just following that pattern.
Look at feefilter BIP 133
(https://github.com/bitcoin/bips/blob/master/bip-0133.mediawiki#backward-compatibility)
or sendheaders BIP130
(https://github.com/bitcoin/bips/blob/master/bip-0130.mediawiki#backward-compatibility)
Isn't it the same there?
Once BIP151 is implemented, it would make sense to bump the protocol
version, but this needs to be done once this has been
implemented/deployed. Or do I make a mistake somewhere?
>
> As for DOS, waste of bandwidth is not something to be ignored. If a peer
> is flooding a node with addr message the node can manage it because it
> understands the semantics of addr messages. If a node is required to
> allow any message that it cannot understand it has no recourse. It
> cannot determine whether it is under attack or if the behavior is
> correct and for proper continued operation must be ignored.
How do you threat any other not known message types? Any peer can send
you any type of message anytime. Why would your implementation how you
threat unknown messages be different for messages specified in BIP151?
</jonas>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-02-13 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 5:18 Eric Voskuil
2017-02-13 8:47 ` Pieter Wuille
2017-02-13 9:36 ` Eric Voskuil
2017-02-13 10:07 ` Jonas Schnelli [this message]
2017-02-13 10:30 ` Eric Voskuil
2017-02-13 11:14 ` Jonas Schnelli
2017-02-14 19:54 ` Eric Voskuil
2017-02-14 20:58 ` Jonas Schnelli
2017-02-13 10:16 ` Matt Corallo
2017-02-13 10:54 ` Eric Voskuil
2017-02-13 11:11 ` Matt Corallo
2017-02-13 11:17 ` Eric Voskuil
2017-02-13 13:04 ` Matt Corallo
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=ff7c24ba-7c70-efaf-a319-b1aebfd8a3bd@jonasschnelli.ch \
--to=dev@jonasschnelli$(echo .)ch \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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