rfc8905v2.txt   rfc8905.txt 
skipping to change at line 437 skipping to change at line 437
handled by the application and are not in scope of this document. handled by the application and are not in scope of this document.
To avoid unnecessary data collection, payment target types SHOULD NOT To avoid unnecessary data collection, payment target types SHOULD NOT
include personally identifying information about the sender of a include personally identifying information about the sender of a
payment that is not essential for an application to conduct a payment that is not essential for an application to conduct a
payment. payment.
9. IANA Considerations 9. IANA Considerations
IANA maintains the "Uniform Resource Identifier (URI) Schemes" IANA maintains the "Uniform Resource Identifier (URI) Schemes"
registry, which contains an entry for the 'payto' URI scheme. IANA registry, which contains an entry for the 'payto' URI scheme as
has updated that entry to reference this document. follows. IANA has updated that entry to reference this document.
Scheme name: payto
Status: provisional
URI scheme syntax: See Section 2 of RFC 8905.
URI scheme semantics: See Section 3 of RFC 8905.
Applications/protocols that use this scheme name: payto URIs are
mainly used by financial software.
Contact: Christian Grothoff <grothoff@gnu.org>
Change controller: Christian Grothoff <grothoff@gnu.org>
References: See Section 11 of RFC 8905.
10. Payto Payment Target Types 10. Payto Payment Target Types
This document specifies a list of payment target types. It is This document specifies a list of payment target types. It is
possible that future work will need to specify additional payment possible that future work will need to specify additional payment
target types. The GNUnet Assigned Numbers Authority (GANA) [GANA] target types. The GNUnet Assigned Numbers Authority (GANA) [GANA]
operates the "Payto Payment Target Types" registry to track the operates the "Payto Payment Target Types" registry to track the
following information for each payment target type: following information for each payment target type:
Name: The name of the payment target type (case-insensitive ASCII Name: The name of the payment target type (case-insensitive ASCII
skipping to change at line 520 skipping to change at line 537
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[unicode-tr36] [unicode-tr36]
Davis, M., Ed. and M. Suignard, "Unicode Technical Report Davis, M., Ed. and M. Suignard, Ed., "Unicode Technical
#36: Unicode Security Considerations", September 2014. Report #36: Unicode Security Considerations", September
2014.
11.2. Informative References 11.2. Informative References
[BIC] International Organization for Standardization, "Banking [BIC] International Organization for Standardization, "Banking
-- Banking telecommunication messages -- Business -- Banking telecommunication messages -- Business
identifier code (BIC)", ISO 9362, December 2014, identifier code (BIC)", ISO 9362, December 2014,
<https://www.iso.org>. <https://www.iso.org>.
[BIP0021] Schneider, N. and M. Corallo, "Bitcoin Improvement [BIP0021] Schneider, N. and M. Corallo, "Bitcoin Improvement
Proposal 21", September 2019, <https://en.bitcoin.it/w/ Proposal 21", September 2019, <https://en.bitcoin.it/w/
 End of changes. 2 change blocks. 
4 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/