From: Jeff Garzik <jgarzik@bitpay•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] PSA: Extending BIP 70 / payment protocol
Date: Wed, 21 May 2014 10:32:54 -0400 [thread overview]
Message-ID: <CAJHLa0P_HWm-qqKJxandJfNeN-KoBVwsW14biyNdnu4JESbKew@mail.gmail.com> (raw)
Please put any payment protocol extensions into a new draft BIP. BIP
70 should not be updated continuously.
Mimic the IETF, where new RFCs are produced as protocols are extended.
Once published, an IETF RFC is considered static.
That said, I think it is OK to be smart, and break the "static" rule a
bit for significant BIP bugs, or harmless maintenance of
links-to-resources.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
reply other threads:[~2014-05-21 14:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJHLa0P_HWm-qqKJxandJfNeN-KoBVwsW14biyNdnu4JESbKew@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--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