diff options
| author | Christian Grothoff <christian@grothoff.org> | 2020-03-23 14:04:26 +0100 |
|---|---|---|
| committer | Christian Grothoff <christian@grothoff.org> | 2020-03-23 14:04:26 +0100 |
| commit | 95ea037b61ae2cdc9d32a9add49a7636fb62cb4e (patch) | |
| tree | e2ab5ceeabc82e49291e0b9fb7e7630850f7c9e5 | |
| parent | ec2cbda4474ca52728800564253702e5c2440078 (diff) | |
| download | marketing-95ea037b61ae2cdc9d32a9add49a7636fb62cb4e.tar.gz marketing-95ea037b61ae2cdc9d32a9add49a7636fb62cb4e.tar.bz2 marketing-95ea037b61ae2cdc9d32a9add49a7636fb62cb4e.zip | |
update payto draft based on ISE feedback
| -rw-r--r-- | standards/draft-dold-payto.xml | 28 |
1 files changed, 11 insertions, 17 deletions
diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml index a7a4b90..f6425ca 100644 --- a/standards/draft-dold-payto.xml +++ b/standards/draft-dold-payto.xml @@ -418,14 +418,16 @@ IANA maintains a registry called the "Uniform Resource Identifier published as an RFC. </t> </section> +</section> -<section anchor="payto-registry" title="Payment Target Type Registry"> +<section anchor="payto-registry" title="Payment Target Types"> <t> - 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: + This document specifies a list of Payment Target Types. It is + possible that future work will need to specify additional payment + target types. In that case, IANA may be asked to create a registry + to track "Payment Target Types" associated with the "Uniform Resource + Identifier (URI) Schemes" registry, and tracking the following + information for each entry: <list style="symbols"> <t>Name: The name of the payment target type (case insensitive ASCII string, restricted to alphanumeric characters, dots and dashes)</t> @@ -433,10 +435,10 @@ dots and dashes)</t> <t>References: Optionally, references describing the payment target type (such as an RFC) and target-specific options, or references describing the payment system underlying the payment target type.</t> </list> - The registration policy for this sub-registry is "First Come First Served", as described in <xref target="RFC8126" />. </t> <t> - IANA is requested to populate this registry as follows: + The entries that would be made for the payment target types defined + in this document are as follows: </t> <figure> <artwork> @@ -454,15 +456,6 @@ dots and dashes)</t> </section><!-- payto-registry --> -</section><!-- iana --> - - -<!-- section anchor="checksums" title="Checksums"> - <t>- - (how should fields be sorted? does order ever matter?) -</t> -</section --> - </middle> <back> @@ -609,6 +602,7 @@ dots and dashes)</t> </references> <!-- Change Log +v11 2020-03-23 CG Workaround IESG/IAB/IANA/ISE discussion on who gets to create IANA registries as suggested by Adrian Farrel v10 2019-11-14 CG Address comments from Adrian Farrel v09 2019-11-04 CG Reference ISO 4217 for currency codes, clean up ENBF syntax and language (based on feedback from Matthias Heckmann) v08 2019-09-27 CG Clarify use of sub-registry as per draft-ise-iana-policy |