payto

1 files changed, 34 insertions, 25 deletions

diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
index 2f322a8..a7a4b90 100644
--- a/standards/draft-dold-payto.xml
+++ b/standards/draft-dold-payto.xml
@@ -4,7 +4,6 @@
 <!ENTITY RFC3629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3629.xml">
 <!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
 <!ENTITY RFC5234 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5234.xml">
-<!ENTITY RFC7595 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7595.xml">
 <!ENTITY RFC8174 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml">
 <!ENTITY RFC8126 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8126.xml">
 ]>
@@ -53,7 +52,7 @@
       </address>
     </author>
 
-    <date day="04" month="November" year="2019" />
+    <date day="17" month="December" year="2019" />
 
     <!-- Meta-data Declarations -->
     <area>General</area>
@@ -186,23 +185,23 @@
   The following options SHOULD be understood by every payment target type.
 </t>
 <t>
-
-  amount:  The amount to transfer, including currency information if applicable.
-  The format MUST be:
+  amount: The amount to transfer.  The format MUST be:
 <figure>
   <artwork><![CDATA[
-  amount = [ currency ":" ] unit [ "." fraction ]
+  amount = currency ":" unit [ "." fraction ]
   currency = 1*ALPHA
   unit = 1*(DIGIT / ",")
   fraction = 1*(DIGIT / ",")
  ]]>
   </artwork>
 </figure>
-If a 3-letter 'currency' is used, it must be an
-<xref target="ISO4217" /> alphabetic code.
-The 'unit' value MUST be smaller than 2^53.
-If present, the 'fraction' MUST consist of no more than 8 decimal digits.
-The use of commas is optional for readability and they MUST be ignored.
+  If a 3-letter 'currency' is used, it MUST be an
+  <xref target="ISO4217" />
+  alphabetic code. A payment target type MAY define semantics beyond ISO 4217
+  for currency codes that are not 3 characters. The 'unit' value MUST be smaller
+  than 2^53. If present, the 'fraction' MUST consist of no more than 8 decimal
+  digits.
+  The use of commas is optional for readability and they MUST be ignored.
 </t>
 
 <t>
@@ -365,6 +364,22 @@ options are mandatory for this payment target.</t>
 </t>
 </section>
 
+<section anchor="registry-entry-void" title="Void Payment Target">
+<t>
+<list style="symbols">
+<t>Name: void</t>
+<t>
+  Description: The "void" payment target type allows specifying the parameters
+  of an out-of-band payment (such as cash or other types of in-person
+  transactions).  The path is optional and interpreted as a comment.
+</t>
+<t>Example: payto://void/?amount=EUR:10.5</t>
+<t>Contact: N/A</t>
+<t>References: [this.I-D]</t>
+</list>
+</t>
+</section>
+
 </section><!-- tracking -->
 
 <section anchor="security" title="Security Considerations">
@@ -397,23 +412,18 @@ IANA maintains a registry called the "Uniform Resource Identifier
 
 <section anchor="payto-uri" title="URI Scheme Registration">
 <t>
-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"
-<xref target="RFC7595" />.
-
-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.
+  IANA maintains the "Uniform Resource Identifier (URI) Schemes"
+  registry that contains an entry for the 'payto' URI scheme.  IANA is
+  requested to update that entry to reference this document when
+  published as an RFC.
 </t>
 </section>
 
 <section anchor="payto-registry" title="Payment Target Type Registry">
 <t>
-IANA is requested to create a new subregistry of the "Uniform
-Resource Identifier (URI) Schemes" registry called the "Payment
-Target Types" registry with this document as the reference.
+  IANA maintains the "Uniform Resource Identifier (URI) Schemes"
+  registry.  IANA is requested to create a new subregistry for
+  payment methods called the "Payment Target Types" registry.
 </t>
 <t>The subregistry shall record for each entry:
 <list style="symbols">
@@ -438,6 +448,7 @@ dots and dashes)</t>
     upi       | N/A                     | [This.I-D]
     bitcoin   | N/A                     | [This.I-D]
     ilp       | N/A                     | [This.I-D]
+    void      | N/A                     | [This.I-D]
   </artwork>
 </figure>
 
@@ -464,8 +475,6 @@ dots and dashes)</t>
 
     &RFC5234;
 
-    &RFC7595;
-
     &RFC8126;
 
     &RFC8174;