Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id E388E1071 for ; Fri, 4 Sep 2015 03:50:50 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail148102.authsmtp.net (outmail148102.authsmtp.net [62.13.148.102]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 3B836154 for ; Fri, 4 Sep 2015 03:50:50 +0000 (UTC) Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt16.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t843om19048341; Fri, 4 Sep 2015 04:50:48 +0100 (BST) Received: from muck (030-098.web.ny.np1.net [64.61.30.98] (may be forged)) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t843oirK010303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 4 Sep 2015 04:50:47 +0100 (BST) Date: Thu, 3 Sep 2015 23:50:45 -0400 From: Peter Todd To: Dave Scotese Message-ID: <20150904035045.GA9821@muck> References: <55E8A246.7030102@bitcartel.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline In-Reply-To: X-Server-Quench: 208a7d9f-52b8-11e5-b399-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aAdMdgYUC1AEAgsB AmMbW1BeVV17XWQ7 bQ5PawRDYUpQVg11 VUBOXVMcUA1sAkNY RGUeUxlxdwYIfHh3 ZwhgXngKWxBzI1t4 QBxcCGwHMGJ9OmMW WV1YdwFReQMbfxoR O1cxNiYHcQ5VPz4z GA41ejw8IwAXAgVt ClhVdRoJWUsAHzA9 TBkeHDIpdQAA X-Authentic-SMTP: 61633532353630.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 64.61.30.98/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] BIP 100 specification X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Sep 2015 03:50:51 -0000 --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 03, 2015 at 01:34:54PM -0700, Dave Scotese via bitcoin-dev wrot= e: > I have seen "1M" mean 1,000,000 bytes as well as 1,048,576bytes and > 1,024,000 bytes. I believe the best policy is to use "megabyte" to mean > 2^20 (1,048,576) bytes. Kb always means 1024 bytes, even when a lot peop= le > round it, so I like the K spec best. I also see value in having human > readable data. The spec should nail down these details. The IEC standard is to use the prefix MiB for 2^20 bytes: https://en.wikipedia.org/wiki/Binary_prefix --=20 'peter'[:-1]@petertodd.org 000000000000000010f9e95aff6454fedb9d0a4b92a4108e9449c507936f9f18 --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQGrBAEBCACVBQJV6RURXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw MDAwMDAwMDAwMDAwMDAxMGY5ZTk1YWZmNjQ1NGZlZGI5ZDBhNGI5MmE0MTA4ZTk0 NDljNTA3OTM2ZjlmMTgvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udzp7Af/etizdLVR57SFo6VH0bPUC+H1 R/l6930A4a1sdK8i2uBUC+/zAr6WT0nEc6dSr6+9AU8ftbzgC8JghkXaiHIft3QC 8k0qpDek4tH5gC8+7tpK/AReX/4s0jMCo4D8K0Cy8wwT1J4HX20mAJHcR2sfNWbI Aa/deRf2PsrCKHZJtHYjLdrSKE4XjS7agBBBootjNiAHnQMsG89lE3bQUzJ+LhDu DBU5Vmr34vZemXRhXHc2OLK4SudWiNEq7z2U7+4VyXZghg9r8lFw9bcgx3aPTy5N DD2Pl29a4GqAfxNNI9umyJYeukl4gb5aqfErY6dKSEG4WPFbzLiCYVnJztWq8w== =MD+x -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn--