From 820736896ec0ee34c4a7b2432e0164ace75745b9 Mon Sep 17 00:00:00 2001
From: William Swanson <swansontec@gmail.com>
Date: Thu, 6 Mar 2014 17:16:03 -0800
Subject: BIP 72: Reduce the amount of escaping needed

RFC 3986 obsoletes RFC 1738, which this BIP was wrongly referencing.
The new RFC requires far less escaping for query parameters.
---
 bip-0072.mediawiki | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

(limited to 'bip-0072.mediawiki')

diff --git a/bip-0072.mediawiki b/bip-0072.mediawiki
index 4edd749..246a40c 100644
--- a/bip-0072.mediawiki
+++ b/bip-0072.mediawiki
@@ -22,8 +22,9 @@ bitcoin wallets.
 
 The bitcoin: URI scheme is extended with an additional, optional
 "r" parameter, whose value is a URL from which a PaymentRequest
-message should be fetched (unsafe and reserved octets in the URL value
-must be encoded as described in RFC 1738).
+message should be fetched (characters not allowed within the scope
+of a query parameter must be percent-encoded as described in RFC 3986
+and bip-0021).
 
 If the "r" parameter is provided and backwards compatibility
 is not required, then the bitcoin address portion of the URI may be
@@ -52,9 +53,9 @@ r parameter and will initiate a payment to bitcoin address.
 ==Examples==
 A backwards-compatible request:
 <pre>
-bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&r=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
+bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
 </pre>
 Non-backwards-compatible equivalent:
 <pre>
-bitcoin:?r=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
+bitcoin:?r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
 </pre>
-- 
cgit v1.2.3

