draft-dold-payto.xml (25390B)
1 <?xml version="1.0" encoding="US-ASCII"?> 2 <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ 3 <!ENTITY RFC3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml"> 4 <!ENTITY RFC3629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3629.xml"> 5 <!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"> 6 <!ENTITY RFC5234 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5234.xml"> 7 <!ENTITY RFC8174 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml"> 8 <!ENTITY RFC8126 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8126.xml"> 9 ]> 10 <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> 11 12 <?rfc strict="yes" ?> 13 <?rfc toc="yes" ?> 14 <?rfc symrefs="yes"?> 15 <?rfc sortrefs="yes" ?> 16 <?rfc compact="yes" ?> 17 <?rfc subcompact="no" ?> 18 19 <rfc category="info" 20 docName="draft-dold-payto-14" 21 ipr="trust200902"> 22 23 <front> 24 <title abbrev="The 'payto' URI scheme"> 25 The 'payto' URI scheme for payments 26 </title> 27 28 <author fullname="Florian Dold" initials="F.D." surname="Dold"> 29 <organization>Taler Systems SA</organization> 30 <address> 31 <postal> 32 <street>7, rue de Mondorf</street> 33 <city>Erpeldange</city> 34 <code>L-5421</code> 35 <country>LU</country> 36 </postal> 37 <email>dold@taler.net</email> 38 </address> 39 </author> 40 41 <author fullname="Christian Grothoff" initials="C.G." surname="Grothoff"> 42 <organization>BFH</organization> 43 <address> 44 <postal> 45 <street>Höheweg 80</street> 46 <street></street> 47 <city>Biel/Bienne</city> 48 <code>CH-2501</code> 49 <country>CH</country> 50 </postal> 51 <email>christian.grothoff@bfh.ch</email> 52 </address> 53 </author> 54 55 <date day="01" month="May" year="2020" /> 56 57 <!-- Meta-data Declarations --> 58 <area>General</area> 59 <workgroup>Independent Stream</workgroup> 60 <keyword>payments</keyword> 61 62 <abstract> 63 64 <t> 65 This document defines the 'payto' Uniform Resource Identifier (URI) scheme 66 for designating targets for payments. 67 </t> 68 69 <t> 70 A unified URI scheme for all payment target types 71 allows applications to offer user interactions with URIs that represent payment targets, 72 simplifying the introduction of new payment systems and applications. 73 </t> 74 75 </abstract> 76 77 </front> 78 79 <middle> 80 81 <section anchor="introduction" title="Introduction"> 82 <t> 83 This document defines the 'payto' Uniform Resource Identifier (URI) <xref target="RFC3986" /> scheme 84 for designating transfer form data for payments. 85 </t> 86 87 <section title="Objective"> 88 <t> 89 A 'payto' URI always identifies the target of a payment. 90 A 'payto' URI consists of a payment target type, a target identifier and optional parameters 91 such as an amount or a payment reference. 92 </t> 93 <t> 94 The interpretation of the target identifier is defined by the payment target type, and typically 95 represents either a bank account or an (unsettled) transaction. 96 </t> 97 <t> 98 A unified URI scheme for all payment target types 99 allows applications to offer user interactions with URIs that represent payment targets, 100 simplifying the introduction of new payment systems and applications. 101 </t> 102 </section> 103 <section title="Requirements Language"> 104 <t> 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 107 "OPTIONAL" in this document are to be interpreted as described in BCP 14 108 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, 109 they appear in all capitals, as shown here. 110 </t> 111 </section> 112 113 </section> 114 115 <section anchor="syntax" 116 title="Syntax of a 'payto' URI"> 117 <t> 118 This document uses the Augmented Backus-Naur Form (ABNF) of <xref target="RFC5234"/>. 119 </t> 120 <figure> 121 <artwork type="abnf"><![CDATA[ 122 payto-URI = "payto://" authority path-abempty [ "?" opts ] 123 opts = opt *( "&" opt ) 124 opt-name = generic-opt / authority-specific-opt 125 opt-value = *pchar 126 opt = opt-name "=" opt-value 127 generic-opt = "amount" / "receiver-name" / "sender-name" / 128 "message" / "instruction" 129 authority-specific-opt = ALPHA *( ALPHA / DIGIT / "-" / "." ) 130 authority = ALPHA *( ALPHA / DIGIT / "-" / "." ) 131 ]]> 132 </artwork> 133 </figure> 134 <t> 135 'path-abempty' is defined in <xref target="RFC3986" /> in Section 3.3. 136 'pchar' is defined in <xref target="RFC3986" />, Appendix A. 137 </t> 138 </section> 139 140 <section anchor="semantics" title="Semantics"> 141 <t> 142 The authority component of a payment URI identifies the payment target type. The 143 payment target types are defined in the "Payment Target Types" sub-registry, see <xref 144 target="payto-registry" />. 145 146 The path component of the URI identifies the target for a payment as interpreted 147 by the respective payment target type. 148 149 The query component of the URI can provide additional parameters for a payment. 150 Every payment target type SHOULD accept the options defined in generic-opt. 151 152 The default operation of applications that invoke a URI with the payto scheme 153 MUST be to launch an application (if available) associated with the payment 154 target type that can initiate a payment. If multiple handlers are registered for the same 155 payment target type, the user SHOULD be able to choose which application to launch. 156 This allows users with multiple bank accounts (each accessed the respective bank's 157 banking application) to choose which account to pay with. 158 159 An application SHOULD allow dereferencing a payto URI even 160 if the payment target type of that URI is not registered in the "Payment Target Types" sub-registry. 161 162 Details of the payment MUST be taken 163 from the path and options given in the URI. The user SHOULD be allowed to 164 modify these details before confirming a payment. 165 </t> 166 </section> 167 168 <section anchor="examples" title="Examples"> 169 <figure> 170 <artwork><![CDATA[ 171 payto://iban/DE75512108001245126199?amount=EUR:200.0&message=hello 172 173 INVALID (authority missing): payto:iban/12345 174 ]]> 175 </artwork> 176 </figure> 177 178 </section> 179 180 <section anchor="generic-options" title="Generic Options"> 181 <t> 182 Applications MUST accept URIs with options in any order. The 183 "amount" option MUST NOT occur more than once. Other options MAY be 184 allowed multiple times, with further restrictions depending on the 185 payment target type. 186 187 The following options SHOULD be understood by every payment target type. 188 </t> 189 <t> 190 amount: The amount to transfer. The format MUST be: 191 <figure> 192 <artwork><![CDATA[ 193 amount = currency ":" unit [ "." fraction ] 194 currency = 1*ALPHA 195 unit = 1*(DIGIT / ",") 196 fraction = 1*(DIGIT / ",") 197 ]]> 198 </artwork> 199 </figure> 200 If a 3-letter 'currency' is used, it MUST be an 201 <xref target="ISO4217" /> 202 alphabetic code. A payment target type MAY define semantics beyond ISO 4217 203 for currency codes that are not 3 characters. The 'unit' value MUST be smaller 204 than 2^53. If present, the 'fraction' MUST consist of no more than 8 decimal 205 digits. 206 The use of commas is optional for readability and they MUST be ignored. 207 </t> 208 209 <t> 210 receiver-name: Name of the entity that receives the payment (creditor). 211 The value of this option MAY 212 be subject to lossy conversion, modification and truncation (for example, due to 213 line wrapping or character set conversion). 214 </t> 215 216 <t> 217 sender-name: Name of the entity that makes the payment (debtor). 218 The value of this option MAY 219 be subject to lossy conversion, modification and truncation (for example, due to 220 line wrapping or character set conversion). 221 </t> 222 223 <t> 224 message: A short message to identify the purpose of the payment. 225 The value of this option MAY 226 be subject to lossy conversion, modification and truncation (for example, due to 227 line wrapping or character set conversion). 228 </t> 229 230 <t> 231 instruction: A short message giving payment reconciliation instructions to 232 the recipient. 233 An instruction that follows the character set and length limitation defined by the 234 respective payment target type SHOULD NOT be subject to lossy conversion. 235 </t> 236 </section> 237 238 <section anchor="encoding" title="Internationalization and Character Encoding"> 239 <t> 240 Various payment systems use restricted character sets. 241 An application that processes 'payto' URIs MUST convert 242 characters that are not allowed by the respective payment systems 243 into allowable character using either an encoding or a replacement table. 244 This conversion process MAY be lossy, except for the instruction field. 245 If the value of the instruction field would be subject to lossy conversion, 246 modification or truncation, 247 the application SHOULD refuse further processing of the payment until a 248 different value for the instruction is provided. 249 </t> 250 <t> 251 To avoid special encoding rules for the payment target identifier, the userinfo component 252 <xref target="RFC3986" /> is disallowed in payto URIs. Instead, the payment target identifier is 253 given as an option, where encoding rules are uniform for all options. 254 </t> 255 <t> 256 Defining a generic way of tagging the language of option fields containing natural 257 language text (such as "receiver-name", "sender-name" and "message) 258 is out of the scope of this document, as internationalization must accomodate the restrictions 259 and requirements of the underlying banking system of the payment target type. 260 261 The internationalization concerns SHOULD be individually defined by each payment target type. 262 </t> 263 </section> 264 <section anchor="tracking" title="Tracking Payment Target Types"> 265 <t> 266 A registry of Payment Target Types is described in <xref target="payto-registry" />. 267 268 The registration policy for this registry is "First Come First Served", 269 as described in <xref target="RFC8126" />. 270 When requesting new entries, careful consideration of the following criteria is strongly advised: 271 <list style="numbers"> 272 <t>The description clearly defines the syntax and semantics of the payment target and optional parameters if applicable.</t> 273 <t>Relevant references are provided if they are available.</t> 274 <t>The chosen name is appropriate for the payment target type, does not conflict 275 with well-known payment systems, and avoids potential to confuse users.</t> 276 <t>The payment system underlying the payment target type is not fundamentally 277 incompatible with the general options (such as positive decimal amounts) in this specification.</t> 278 <t>The payment target type is not a vendor-specific version of a payment target type that 279 could be described more generally by a vendor-neutral payment target type.</t> 280 <t>The specification of the new payment target type remains within the scope of payment transfer form data. 281 In particular specifying complete invoices is not in scope. Neither are processing instructions to the 282 payment processor or bank beyond a simple payment.</t> 283 <t>The payment target and the options do not contain the payment sender's account details.</t> 284 </list> 285 </t> 286 <t> 287 Documents that support requests for new registry entries should 288 provide the following information for each entry: 289 <list style="symbols"> 290 <t>Name: The name of the payment target type (case insensitive ASCII string, restricted to alphanumeric characters, 291 dots and dashes)</t> 292 <t>Description: A description of the payment target type, including 293 the semantics of the path in the URI if applicable.</t> 294 <t>Example: At least one example URI to illustrate the payment target type.</t> 295 <t>Contact: The contact information of a person to contact for further information</t> 296 <t>References: Optionally, references describing the payment target type (such as an RFC) and target-specific options, 297 or references describing the payment system underlying the payment target type.</t> 298 </list> 299 </t> 300 <t> 301 This document populates the registry with six entries as follows (see 302 also <xref target="payto-registry" />). 303 </t> 304 305 <section anchor="registry-entry-ach" title="ACH Bank Account"> 306 <t> 307 <list style="symbols"> 308 <t>Name: ach</t> 309 <t>Description: Automated Clearing House. The path consist of two components, the routing number and the account number. 310 Limitations on the length and character set of option values are defined by the implementation 311 of the handler. 312 Language tagging and internationalization of options is not supported. 313 </t> 314 <t>Example: payto://ach/122000661/1234</t> 315 <t>Contact: N/A</t> 316 <t>References: <xref target="NACHA" />, [this.I-D]</t> 317 </list> 318 </t> 319 </section> 320 321 <section anchor="registry-entry-bic" title="Business Identifier Code"> 322 <t> 323 <list style="symbols"> 324 <t>Name: bic</t> 325 <t>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. 326 Limitations on the length and character set of option values are defined by the implementation 327 of the handler. 328 Language tagging and internationalization of options is not supported. 329 </t> 330 <t>Example: payto://bic/SOGEDEFFXXX</t> 331 <t>Contact: N/A</t> 332 <t>References: <xref target="BIC" />, [this.I-D]</t> 333 </list> 334 </t> 335 </section> 336 337 <section anchor="registry-entry-iban" title="International Bank Account Number"> 338 <t> 339 <list style="symbols"> 340 <t>Name: iban</t> 341 <t>Description: International Bank Account Number (IBAN). Generally the IBAN allows to unambiguously derive 342 the the associated Business Identifier Code (BIC). However, some legacy applications process payments to the same IBAN differently based on the 343 specified BIC. Thus the path can either consist of a single component (the IBAN) or two components 344 (BIC followed by IBAN). The "message" option of the payto URI corresponds to the "unstructured remittance information" 345 of SEPA credit transfers and is thus limited to 140 characters with character set limitations that 346 differ according to the countries of banks and payment processors involved in the payment. 347 The "instruction" option of the payto URI corresponds to the "end to end identifier" of SEPA credit transfers 348 and is thus limited to at most 35 characters that can be alphanumeric or from the allowed set 349 of special characters "+?/-:().,'". 350 Language tagging and internationalization of options is not supported. 351 </t> 352 <t>Example: 353 354 payto://iban/DE75512108001245126199 355 356 payto://iban/SOGEDEFFXXX/DE75512108001245126199 357 </t> 358 <t>Contact: N/A</t> 359 <t>References: <xref target="ISO20022" />, [this.I-D]</t> 360 </list> 361 </t> 362 </section> 363 364 <section anchor="registry-entry-upi" title="Unified Payments Interface"> 365 <t> 366 <list style="symbols"> 367 <t>Name: upi</t> 368 <t>Description: Unified Payment Interface. The path is an account alias. The amount and receiver-name 369 options are mandatory for this payment target. 370 Limitations on the length and character set of option values are defined by the implementation 371 of the handler. 372 Language tags and internationalization of options are not supported. 373 </t> 374 <t>Example: payto://upi/alice@example.com?receiver-name=Alice&amount=INR:200</t> 375 <t>Contact: N/A</t> 376 <t>References: <xref target="UPILinking" />, [this.I-D]</t> 377 </list> 378 </t> 379 </section> 380 381 <section anchor="registry-entry-bitcoin" title="Bitcoin Address"> 382 <t> 383 <list style="symbols"> 384 <t>Name: bitcoin</t> 385 <t>Description: Bitcoin protocol. The path is a "bitcoinaddress" as per <xref target="BIP0021" />. 386 Limitations on the length and character set of option values are defined by the implementation 387 of the handler. 388 Language tags and internationalization of options are not supported. 389 </t> 390 <t>Example: payto://bitcoin/12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu</t> 391 <t>Contact: N/A</t> 392 <t>References: <xref target="BIP0021" />, [this.I-D]</t> 393 </list> 394 </t> 395 </section> 396 397 <section anchor="registry-entry-ilp" title="Interledger Protocol Address"> 398 <t> 399 <list style="symbols"> 400 <t>Name: ilp</t> 401 <t>Description: Interledger protocol. The path is an ILP address as per <xref target="ILP-ADDR" />. 402 Limitations on the length and character set of option values are defined by the implementation 403 of the handler. 404 Language tagging and internationalization of options is not supported. 405 </t> 406 <t>Example: payto://ilp/g.acme.bob</t> 407 <t>Contact: N/A</t> 408 <t>References: <xref target="ILP-ADDR" />, [this.I-D]</t> 409 </list> 410 </t> 411 </section> 412 413 <section anchor="registry-entry-void" title="Void Payment Target"> 414 <t> 415 <list style="symbols"> 416 <t>Name: void</t> 417 <t> 418 Description: The "void" payment target type allows specifying the parameters 419 of an out-of-band payment (such as cash or other types of in-person 420 transactions). The path is optional and interpreted as a comment. 421 Limitations on the length and character set of option values are defined by the implementation 422 of the handler. 423 Language tags and internationalization of options are not supported. 424 </t> 425 <t>Example: payto://void/?amount=EUR:10.5</t> 426 <t>Contact: N/A</t> 427 <t>References: [this.I-D]</t> 428 </list> 429 </t> 430 </section> 431 432 </section><!-- tracking --> 433 434 <section anchor="security" title="Security Considerations"> 435 <t> 436 Interactive applications handling the payto URI scheme MUST NOT initiate any 437 financial transactions without prior review and confirmation from the user, 438 and MUST take measures to prevent clickjacking <xref target="HMW12"/>. 439 </t> 440 <t> 441 Unless a payto URI is received over a trusted, authenticated channel, 442 a user might not be able to identify the target of a payment. In particular 443 due to homographs <xref target="unicode-tr36" />, a payment target type SHOULD NOT 444 use human-readable names in combination with unicode in the target 445 account specification, as it could give the user the illusion of being able 446 to identify the target account from the URI. 447 </t> 448 <t> 449 The authentication/authorization mechanisms and transport security services 450 used to process a payment encoded in a payto URI 451 are handled by the application and are not in scope of this document. 452 </t> 453 <t> 454 To avoid unnecessary data collection, payment target types SHOULD NOT 455 include personally identifying information about the sender of a payment that is not 456 essential for an application to conduct a payment. 457 </t> 458 </section> 459 460 <section anchor="iana" title="IANA Considerations"> 461 462 <t> 463 IANA maintains a registry called the "Uniform Resource Identifier 464 (URI) Schemes" registry. 465 </t> 466 467 <section anchor="payto-uri" title="URI Scheme Registration"> 468 <t> 469 IANA maintains the "Uniform Resource Identifier (URI) Schemes" 470 registry that contains an entry for the 'payto' URI scheme. IANA is 471 requested to update that entry to reference this document when 472 published as an RFC. 473 </t> 474 </section> 475 </section> 476 477 <section anchor="payto-registry" title="Payment Target Types"> 478 <t> 479 This document specifies a list of Payment Target Types. It is 480 possible that future work will need to specify additional payment 481 target types. The GNUnet Assigned Numbers Authority (GANA) <xref target="GANA" /> 482 operates the "payto-payment-target-types" registry to track 483 the following information for each payment target type: 484 <list style="symbols"> 485 <t>Name: The name of the payment target type (case insensitive ASCII string, restricted to alphanumeric characters, 486 dots and dashes)</t> 487 <t>Contact: The contact information of a person to contact for further information</t> 488 <t>References: Optionally, references describing the payment target type (such as an RFC) and target-specific options, 489 or references describing the payment system underlying the payment target type.</t> 490 </list> 491 </t> 492 <t> 493 The entries that have been made for the "payto-payment-target-types" 494 defined in this document are as follows: 495 </t> 496 <figure> 497 <artwork> 498 Name | Contact | Reference 499 ----------+-------------------------+------------ 500 ach | N/A | [This.I-D] 501 bic | N/A | [This.I-D] 502 iban | N/A | [This.I-D] 503 upi | N/A | [This.I-D] 504 bitcoin | N/A | [This.I-D] 505 ilp | N/A | [This.I-D] 506 void | N/A | [This.I-D] 507 </artwork> 508 </figure> 509 510 </section><!-- payto-registry --> 511 512 </middle> 513 514 <back> 515 516 <references title="Normative References"> 517 518 &RFC2119; 519 520 &RFC3986; 521 522 &RFC5234; 523 524 &RFC8126; 525 526 &RFC8174; 527 528 529 <reference anchor="ISO4217"> 530 <front> 531 <title>ISO 4217 Currency Codes</title> 532 <author> 533 <organization>International Organization for Standardization</organization> 534 <address> 535 <uri>http://www.iso.ch</uri> 536 </address> 537 </author> 538 <date month="August" year="2018"/> 539 </front> 540 </reference> 541 542 <reference anchor="ISO20022"> 543 <front> 544 <title>ISO 20022 Financial Services - Universal financial industry message scheme</title> 545 <author> 546 <organization>International Organization for Standardization</organization> 547 <address> 548 <uri>http://www.iso.ch</uri> 549 </address> 550 </author> 551 <date month="May" year="2013"/> 552 </front> 553 </reference> 554 555 <reference anchor="NACHA"> 556 <front> 557 <title>NACHA Operating Rules & Guidelines</title> 558 <author> 559 <organization>NACHA</organization> 560 <address> 561 <uri>https://www.nacha.org/</uri> 562 </address> 563 </author> 564 <date month="January" year="2017"/> 565 </front> 566 </reference> 567 568 <reference anchor="unicode-tr36"> 569 <front> 570 <title abbrev="Unicode Security Considerations">Unicode Technical Report #36: Unicode Security Considerations</title> 571 <author initials="M." surname="Davis" fullname="Mark Davis" role="editor"> 572 <address> 573 <email>markdavis@google.com</email> 574 </address> 575 </author> 576 <author initials="M." surname="Suignard" fullname="Michael Suignard"> 577 <address> 578 <email>michel@suignard.com</email> 579 </address> 580 </author> 581 <date month="September" year="2014"/> 582 </front> 583 </reference> 584 585 586 </references> 587 588 <references title="Informational References"> 589 590 <reference anchor="BIP0021" target="https://en.bitcoin.it/wiki/BIP_0021"> 591 <front> 592 <title>Bitcoin Improvement Proposal 21</title> 593 <author initials="N." surname="Schneider" 594 fullname="Nils Schneider"> 595 </author> 596 <author initials="M." surname="Corallo" 597 fullname="Matt Corallo"> 598 </author> 599 600 <date month="January" year="2012" /> 601 </front> 602 </reference> 603 604 <reference anchor="HMW12" target="https://www.usenix.org/system/files/conference/usenixsecurity12/sec12-final39.pdf"> 605 <front> 606 <title>Clickjacking: Attacks and Defenses</title> 607 <author initials="L.S." surname="Huang" 608 fullname="Lin-Shung Huang"> 609 </author> 610 <author initials="A." surname="Moshchuk" 611 fullname="Alexander, Moshchuk"> 612 </author> 613 <author initials="H.J." surname="Wang" 614 fullname="Helen J. Wang"> 615 </author> 616 <author initials="S." surname="Schecter" 617 fullname="Stuart Schecter"> 618 </author> 619 <author initials="C." surname="Jackson" 620 fullname="Collin Jackson"> 621 </author> 622 623 <date month="January" year="2012" /> 624 </front> 625 </reference> 626 627 <reference anchor="UPILinking" target="https://www.npci.org.in/sites/default/files/UPI%20Linking%20Specs_ver%201.6.pdf"> 628 <front> 629 <title>Unified Payment Interface - Common URL Specifications For Deep 630 Linking And Proximity Integration</title> 631 <author><organization>National Payment Corporation of India</organization> 632 </author> 633 <date month="November" year="2017" /> 634 </front> 635 </reference> 636 637 <reference anchor="ILP-ADDR" target="https://interledger.org/rfcs/0015-ilp-addresses/"> 638 <front> 639 <title>ILP Addresses - v2.0.0</title> 640 <author><organization>Interledger Team</organization> 641 </author> 642 <date month="September" year="2018" /> 643 </front> 644 </reference> 645 646 <reference anchor="BIC" target="https://www.iso.org/standard/60390.html"> 647 <front> 648 <title>ISO 9362:2014 Business Identifier Code (BIC)</title> 649 <author><organization>International Organization for Standardization</organization> 650 </author> 651 <date month="March" year="2019" /> 652 </front> 653 </reference> 654 655 <reference anchor="GANA" target="https://gana.gnunet.org/"> 656 <front> 657 <title>GNUnet Assigned Numbers Authority (GANA)</title> 658 <author><organization>GNUnet e.V.</organization> 659 </author> 660 <date month="April" year="2020" /> 661 </front> 662 </reference> 663 664 </references> 665 666 <!-- Change Log 667 v11 2020-03-23 CG Workaround IESG/IAB/IANA/ISE discussion on who gets to create IANA registries as suggested by Adrian Farrel 668 v10 2019-11-14 CG Address comments from Adrian Farrel 669 v09 2019-11-04 CG Reference ISO 4217 for currency codes, clean up ENBF syntax and language (based on feedback from Matthias Heckmann) 670 v08 2019-09-27 CG Clarify use of sub-registry as per draft-ise-iana-policy 671 v05 2019-05-20 CG Addressing coments, preparing for independent stream submission, adding BIC 672 v01 2017-02-15 CG References and formatting 673 v01 2017-02-13 CG Minimal clarifications 674 v00 2017-01-17 FD Initial version 675 --> 676 </back> 677 </rfc>