-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09/26/2014 01:53 AM, Gregory Maxwell wrote: > On Tue, Aug 19, 2014 at 10:11 AM, Justus Ranvier > <jus...@monetas.net> wrote: >> Two draft information BIPs are attached. > > I've pinged some people privately but also pinging the list… no > commentary on this proposal? >
Regarding the BIP process itself, I rather think it's broken in the case of informational BIPs. Proposals that require explicit action on the part of others do not logically belong in the same process as purely information proposals that do not require any explicit action by others are going to be carried out regardless. The only reason we proposed these as BIPs at all was to support the intent of BIP43. - -- Justus Ranvier | Monetas <http://monetas.net/> <mailto:jus...@monetas.net> | Public key ID : C3F7BB2638450DB5 | BM-2cTepVtZ6AyJAs2Y8LpcvZB8KbdaWLwKqc -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJUJMrzAAoJEMP3uyY4RQ217DMH/1oGHayVo4smLM/OKeu1qqXC Xex4NNh6g7Jsu2ulfJ5ow3g7jHEDzTBp33THhUv6cnV7CpDvTC+Y24LDRrYwOBQo YuQ9u0NNtrcgoi+6vs8NuGO+yZyTyBYs1emOipsICsg42H8yhEHlrMyfOTJsO6r/ nAiqR+QH6isNOjQerd9Fs0nYQ6VANs8IksL41L8ch9YAvgKx7C8WxdcQrk/S2pNL JwD7Q729J34x34HPnOb5j5Rfm1gvQInYELBu0YBaCy7D05PZd5nPSYqUC3n35hUA AMvVf65jdQVBjvjlcqDPAPdBTQ3qjhQ+7EAWKJrwlrzhGXaWA3HpipRDUSyqzBg= =OhH8 -----END PGP SIGNATURE-----
0x38450DB5.asc
Description: application/pgp-keys
------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
