From: Mike Hearn <mike@plan99•net>
To: Andreas Schildbach <andreas@schildbach•de>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP70 extension to allow for identity delegation
Date: Sun, 2 Mar 2014 17:14:43 +0100 [thread overview]
Message-ID: <CANEZrP3i05=_xLbS1VDYkXfW0XVOyN9LBHhaf--TEGCryN0Ppg@mail.gmail.com> (raw)
In-Reply-To: <levi7k$pkt$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
On Sun, Mar 2, 2014 at 4:20 PM, Andreas Schildbach <andreas@schildbach•de>wrote:
> I somehow think that it is too early for this heavy kind of extension,
> given that the first version of BIP70 isn't even deployed widely let
> alone *used*.
>
Definitely agree - like I said, I publish this only because I keep getting
asked about it.
> By reading your proposal I get the idea that the current spec doesn't
> allow two (or three) different PKIs at once
That's right. There's little point in having multiple PKI's simultaneously,
that's why it doesn't allow it.
This one is a special case because it doesn't replace but rather
specialises and extends the existing PKI. Old clients that don't understand
it would still show something useful and by upgrading you get better
output. Actually you get closer to the output you're supposed to get.
That's going to be rare though, I think. Generally you wouldn't want to
have multiple PKIs in use simultaneously for the same payment request.
> I would prefer if your fix would stay local to X.509 (and thus only
> change X.509 specific structs rather than the top-level PaymentRequest).
>
It can be done but only by sacrificing backwards compatibility, which
doesn't seem worth it to me. It's hardly a big deal to have two signature
fields. The rest is all localised to the X509 parts.
[-- Attachment #2: Type: text/html, Size: 2090 bytes --]
prev parent reply other threads:[~2014-03-02 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 11:46 Mike Hearn
2014-03-02 10:38 ` Jeremy Spilman
2014-03-02 10:44 ` Mike Hearn
[not found] ` <1393704464.6290.118.camel@mimiz>
2014-03-01 20:42 ` Kevin Greene
2014-03-02 10:57 ` Mike Hearn
2014-03-02 15:20 ` Andreas Schildbach
2014-03-02 16:14 ` Mike Hearn [this message]
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='CANEZrP3i05=_xLbS1VDYkXfW0XVOyN9LBHhaf--TEGCryN0Ppg@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=andreas@schildbach$(echo .)de \
--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