[GNUnet-SVN] [taler-marketing] branch master updated: add default operation and security

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository marketing.

The following commit(s) were added to refs/heads/master by this push:
     new 6218065  add default operation and security
6218065 is described below

commit 6218065a9ec8736858843b1908dc1e3bf3753a93
Author: Florian Dold <address@hidden>
AuthorDate: Sat Apr 7 03:48:00 2018 +0200

    add default operation and security
---
 standards/draft-dold-payto.xml | 26 +++++++++++++++++---------
 1 file changed, 17 insertions(+), 9 deletions(-)

diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
index e0e55d3..7621975 100644
--- a/standards/draft-dold-payto.xml
+++ b/standards/draft-dold-payto.xml
@@ -109,14 +109,21 @@ Questions:
 
 <section anchor="semantics" title="Semantics">
 <t>
-  The authority component of a payment URI identifies the payment method.  The 
registry
-  for payment methods is defined in <xref target="payment-methods" /> of this 
document.
+  The authority component of a payment URI identifies the payment method.  The
+  payment methods are defined in the Payto Payment Method Registry, see <xref
+  target="payto-registry" />.
 
   The path component of the URI identifies the target account for a payment as 
interpreted
   by the respective payment method.
 
   The query component of the URI can provide additional parameters for a 
payment.
   Every payment method SHOULD accept the options defined in generic-opt.
+
+  The default operation of applications that invoke a URI with the payto scheme
+  SHOULD be to launch an application (if available) associated with the payment
+  method that can initiate a payment.  Details of the payment MUST be taken
+  from the path and options given in the URI.  The user SHOULD be allowed to
+  modify these details before confirming a payment.
 </t>
 </section>
 
@@ -132,11 +139,6 @@ Questions:
 
 </section>
 
-<section anchor="payment-methods" title="Payment Methods">
-
-<t>The payment methods are defined in the Payto Payment Method Registry, see 
<xref target="payto-registry" />.</t>
-</section>
-
 <section anchor="generic-options" title="Generic Options">
 <t>
   The following options SHOULD be understood by every payment method.
@@ -189,6 +191,11 @@ Questions:
 </t>
 </section>
 
+<section anchor="security" title="Security Considerations">
+<t>Applications handling the payto URI scheme MUST NOT initiate any
+transactions without prior review and confirmation from the user.</t>
+</section>
+
 <section anchor="iana" title="IANA Considerations">
 
 <section anchor="payto-uri" title="URI Scheme Registration">
@@ -203,11 +210,13 @@ The "payto" URI scheme is to be registered in the 
"Permanent URI Schemes" regist
 <t>Contact: address@hidden</t>
 <t>Change controller: address@hidden</t>
 <!-- There does not seem to be a way to link to the references section! -->
-<t>References: See References section of this document>.</t>
+<t>References: See References section of this document.</t>
 </list>
 </t>
 </section>
 
+</section>
+
 <section anchor="payto-registry" title="Payto Payment Method Registry">
 <t>
 This document defines a registry for payment methods.  The name of the registry
@@ -234,7 +243,6 @@ The registration policy for this registry is "First Come 
First Served", as descr
 
 </section>
 
-</section>
 
 <!-- section anchor="checksums" title="Checksums">
 <t>

-- 
To stop receiving notification emails like this one, please contact
address@hidden