From d65d11702d7c96228f2d07149809c4d414bc5698 Mon Sep 17 00:00:00 2001 From: Christian Grothoff Date: Fri, 27 Sep 2019 12:34:57 +0200 Subject: address comments by Adrian Farrel (ISE) --- standards/draft-dold-payto.xml | 44 ++++++++++++++++++++++++++++-------------- 1 file changed, 30 insertions(+), 14 deletions(-) (limited to 'standards/draft-dold-payto.xml') diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml index dc06793..8ed4f11 100644 --- a/standards/draft-dold-payto.xml +++ b/standards/draft-dold-payto.xml @@ -110,7 +110,7 @@
The authority component of a payment URI identifies the payment target type. The - payment target types are defined in the "Payment Target Types" registry, see . The path component of the URI identifies the target for a payment as interpreted @@ -127,7 +127,7 @@ banking application) to choose which account to pay with. An application SHOULD allow dereferencing a payto URI even - if the payment target type of that URI is not registered in the "Payment Target Types" registry. + if the payment target type of that URI is not registered in the "Payment Target Types" sub-registry. Details of the payment MUST be taken from the path and options given in the URI. The user SHOULD be allowed to @@ -233,20 +233,32 @@ essential for an application to conduct a payment.
+IANA maintains a registry called the "Uniform Resource Identifier +(URI) Schemes" registry. +
- The "payto" URI scheme is already registered in the "Provisional URI Schemes" registry . +IANA maintains a sub-registry of the "Uniform Resource Identifier +(URI) Schemes" registry also called the "Uniform Resource Identifier +(URI) Schemes" registry. The "payto" URI scheme is already +registered in this sub-registry with status set to "provisional" +. + +IANA is requested to update the reference for the "payto" URI scheme +to reference the RFC number of this document when it is published as +an RFC.
-
+
-This document defines a registry for payment methods. The name of the registry -is "Payment Target Types". +IANA is requested to create a new sub-registry of the "Uniform +Resource Identifier (URI) Schemes" registry called the "Payment +Target Types" registry with this document as the reference. -The registry shall record for each entry: +The sub-registry shall record for each entry: Name: The name of the payment target type (case insensitive ASCII string, restricted to alphanumeric characters, dots and dashes) @@ -256,7 +268,7 @@ dots and dashes) References: Optionally, references describing the payment method (such as an RFC) and method-specific options, or references describing the payment system underlying the payment target type. - The registration policy for this registry is "First Come First Served", as described in . + The registration policy for this sub-registry is "First Come First Served", as described in . When requesting new entries, careful consideration of the following criteria is strongly advised: @@ -273,6 +285,9 @@ When requesting new entries, careful consideration of the following criteria is payment processor or bank beyond a simple payment. The payment target and the options do not contain the payment sender's account details. + +IANA is requested to populate the new sub-registry with the entries +documented in the following sub-sections.
@@ -282,7 +297,7 @@ When requesting new entries, careful consideration of the following criteria is Description: Automated Clearing House. The path consist of two components, the routing number and the account number. Example: payto://ach/122000661/1234 Contact: N/A -References: +References: , [this.I-D]
@@ -294,7 +309,7 @@ When requesting new entries, careful consideration of the following criteria is Description: Business Identifier Code. The path consist of just a BIC. This is used for wire transfers between banks. The registry for BICs is provided by SWIFT. The path does not allow specifying a bank account number. Example: payto://bic/SOGEDEFFXXX Contact: N/A -References: +References: , [this.I-D]
@@ -315,7 +330,7 @@ When requesting new entries, careful consideration of the following criteria is payto://iban/SOGEDEFFXXX/DE75512108001245126199 Contact: N/A -References: +References: , [this.I-D]
@@ -328,7 +343,7 @@ When requesting new entries, careful consideration of the following criteria is options are mandatory for this payment target. Example: payto://upi/alice@example.com?receiver-name=Alice&amount=INR:200 Contact: N/A -References: +References: , [this.I-D]
@@ -340,7 +355,7 @@ options are mandatory for this payment target. Description: Bitcoin protocol. The path is a "bitcoinaddress" as per . Example: payto://bitcoin/12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu Contact: N/A -References: +References: , [this.I-D]
@@ -352,7 +367,7 @@ options are mandatory for this payment target. Description: Interledger protocol. The path is an ILP address as per . Example: payto://ilp/g.acme.bob Contact: N/A -References: +References: , [this.I-D] @@ -566,6 +581,7 @@ options are mandatory for this payment target.