idnits 2.17.1 draft-stanish-x-iso4217-a3-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 2012) is 4152 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Walter Stanish 2 Intended status: Informational The IFEX Project 3 Expires: May 25, 2013 ifex-project.org 4 November 2012 6 Registry of Unofficial Extensions to the ISO 4217 Alpha Three Currency 7 Identification Namespace (X-ISO4217-A3) 8 draft-stanish-x-iso4217-a3-01 10 Abstract 12 This document defines a new IANA registry to keep track of 13 identifiers for currencies or currency-like commodities lying outside 14 the traditional scope of the International Organization for 15 Standardization (ISO) 4217 alpha-3 standard, such as digital 16 currencies and commodities, currencies issued by countries (nation- 17 states) with limited international recognition, emerging commodities 18 such as emissions reduction credits, private or commercial 19 currencies, and accounting units for local exchange and trading 20 systems (LETS). Such codes are already in use; the registry simply 21 codifies their existence. This document obsoletes draft-stanish-x- 22 iso4217-a3-00. 24 Status of this Memo 26 This memo defines an Experimental Protocol for the Internet 27 community. This memo does not specify an Internet standard of any 28 kind. Discussion and suggestions for improvement are requested. 29 Distribution of this memo is unlimited. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 40 This document is an individual submission. Comments are solicited 41 and should be addressed to the author(s). 43 This Internet-Draft is submitted in full conformance with the 44 provisions of BCP 78 and BCP 79. 46 This Internet-Draft will expire on May 25, 2013. 48 Copyright Notice 50 Copyright (c) 2012 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 1. Introduction 65 The vast majority of multicurrency financial systems today use the 66 International Organization for Standardization (ISO) 4217 standard 67 for currency identification, which provides three digit numeric and 68 three letter ("alpha-3") codepoints for the identification of each 69 currency. The latter, letter-based codes are in far greater use. 71 ISO4217 codepoints are registered by the International Organization 72 for Standardization through the maintenance agency for the registry, 73 SIX Interbank Clearing [SIX], a Swiss financial body. 75 The specific terms of SIX or the ISO's mandate within the currency 76 sphere do not appear to be publicly available. However, given that 77 geographically defined nation-states with some international 78 recognition and physically circulating currency (such as Transnistria 79 [PRB]) have not been issued currency codes, and leaving aside the 80 relatively large scope for raising conflict of interest questions 81 with regards to SIX's SWIFT links, it is reasonable to assume that 82 SIX and the ISO's mandate and/or sphere of interest in the currency 83 domain is highly unlikely to suddenly extend to emerging currency- 84 like commodities lacking some or all of the political qualities 85 exhibited by conventional currencies. 87 At present, issued codepoints are almost exclusively linked to 88 national or supra-national entities (eg. 'EUR' for the Euro, the 89 currency of the European Union) that have achieved political 90 recognition from the United Nations, with some exceptions for the 91 more popular traditional commodities, such as gold, and various 92 regional instruments backed by similar political entities. 94 This is understandable, given that conventional definitions of the 95 term 'currency' are often inextricably linked to the notion of 96 national issue by 'countries' or nation-states: 98 "a system of money in general use in a particular country" 99 -- The Oxford Dictionary [OXFORD] 101 Therefore currencies and currency-like commodities with far smaller 102 circulation not adopting a traditional national paradigm of issue are 103 unlikely to be granted a codepoint. Indeed, there is some evidence 104 that SIX Interbank Clearing has rejected proposals for such 105 registrations in the recent past, citing lack of a national entity 106 backing a particular currency. [ISO-REJECTION] 108 This situation has left both end users and system developers and 109 integrators in a quandry; in response they have apparently near 110 uniformly opted to respond by issuing unofficial ISO4217 alpha-3 111 codes for private use. 113 The present problem is that, given the recent growth of such 114 unofficial codes, and the increasing exchange of such assets across 115 disparate systems, no registry of unofficial codepoints exists. 116 Therefore no unambiguous, internet-wide, shared vocabulary can be 117 adopted by internet systems to identify this emerging class of 118 assets. 120 This document proposes the establishment of a registry to be 121 maintained by the Internet Assigned Numbers Authority (IANA) in order 122 to resolve this issue by creating an unofficial, parallel namespace 123 codifying such unofficial extensions to the ISO4217 alpha-3 official 124 standard, tracking present and future unofficial assignments. 126 Examples of currencies or currency-like commodities for which systems 127 may benefit from such registration include decentralized digital 128 currencies such as Bitcoin [BITCOIN], the upcoming Ripple Credit 129 [XRP], private currency systems [SLL], and regional currencies of 130 limited political recognition [PRB] [TEM]. 132 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 133 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 134 document are to be interpreted as described in BCP 14, RFC 2119 135 [RFC2119]. 137 Table of Contents 139 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 140 2. X-ISO4217-A3 . . . . . . . . . . . . . . . . . . . . . . . . . 6 141 2.1. Examples. . . . . . . . . . . . . . . . . . . . . . . . . . 6 142 2.2. Source Registry Identification. . . . . . . . . . . . . . . 6 143 2.3. Codepoint Identification. . . . . . . . . . . . . . . . . . 6 144 3. Implementation Considerations. . . . . . . . . . . . . . . . . 7 145 3.1. Input . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 146 3.1.1. Formats. . . . . . . . . . . . . . . . . . . . . . . . . 7 147 3.1.2. End User Input . . . . . . . . . . . . . . . . . . . . . 8 148 3.1.2.1. a3code Input. . . . . . . . . . . . . . . . . . . . . 8 149 3.1.3. Case Sensitivity . . . . . . . . . . . . . . . . . . . . 8 150 3.2. Output. . . . . . . . . . . . . . . . . . . . . . . . . . . 8 151 3.2.1. Machine Presentation . . . . . . . . . . . . . . . . . . 9 152 3.2.2. End User Presentation. . . . . . . . . . . . . . . . . . 9 153 3.3. Internationalization. . . . . . . . . . . . . . . . . . . . 9 154 4. Security Considerations. . . . . . . . . . . . . . . . . . . . 9 155 4.1. Input . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 156 4.1.1. Input Confirmation . . . . . . . . . . . . . . . . . . . 10 157 4.1.2. Case Normalization . . . . . . . . . . . . . . . . . . . 10 158 4.2. IANA Processes. . . . . . . . . . . . . . . . . . . . . . . 10 159 5. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 10 160 5.1. Name Space Exhaustion . . . . . . . . . . . . . . . . . . . 10 161 5.2. Registration. . . . . . . . . . . . . . . . . . . . . . . . 11 162 5.3. Modification / Cancellation . . . . . . . . . . . . . . . . 11 163 5.4. Publication . . . . . . . . . . . . . . . . . . . . . . . . 11 164 5.5. ISO Liason. . . . . . . . . . . . . . . . . . . . . . . . . 12 165 5.5.1. Resolving Duplicate Assignment . . . . . . . . . . . . . 12 166 5.6. Security. . . . . . . . . . . . . . . . . . . . . . . . . . 12 167 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 168 6.1. Normative References. . . . . . . . . . . . . . . . . . . . 13 169 6.2. Informative References. . . . . . . . . . . . . . . . . . . 14 170 7. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 15 171 8. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 15 172 9. Appendix A: Initial Registry Contents. . . . . . . . . . . . . 16 173 10. Appendix B: ISO4217 Registry Issues . . . . . . . . . . . . . 24 174 11. Appendix C: Document History. . . . . . . . . . . . . . . . . 25 176 2. X-ISO4217-A3 178 Official [ISO4217] codepoints shall be considered a subset of a 179 larger namespace, based upon a longer machine-format codepoint, 180 providing unambiguous identification of currencies and currency-like 181 commodities both within and beyond conventional ISO4217 assignment. 182 However, existing end user expectations regarding three-character 183 ('a3code') format and presentation are respected. 185 Systems implementers providing X-ISO4217-A3 support remain safe in 186 the knowledge that they will have the capacity to support all ISO4217 187 alpha-3 codepoints in addition to arbitrary currencies and currency- 188 like commodities. 190 2.1. Examples 192 The Euro is encoded as 'ZEUR'. 194 The digital currency or currency-like commodity known as Bitcoin is 195 encoded as 'XBTC'. 197 2.2. Source Registry Identification 199 In order to issue superset-compatible currency and currency-like 200 commodity identifiers within the [ISO4217] scheme, a prefix character 201 is introduced denominating the source registry, being either this 202 IANA-managed and unofficial registry (denoted with 'X') or the 203 official ISO-managed registry (denoted with 'Z'). 205 The 'X' notation is chosen as is the standard semantic for unofficial 206 extensions within internet drafts. The 'Z' notation is chosen as a 207 less frequently used opening consonant in Roman languages, thus 208 reducing the likelihood of unfortunate four-letter linguistic 209 connotations. 211 2.3. Codepoint Identification 213 The X-ISO4217-A3 format may be expressed in ABNF [RFC5234] as 214 follows: 216 codepoint = registry a3code ; eg: 'XBTC', 'ZEUR' 218 registry = reg-x / reg-z ; ie: capital 'X', capital 'Z' 219 reg-x = %d88 ; X-ISO4217-A3 (IANA managed) 220 reg-z = %d90 ; ISO4217-A3 (ISO managed) 222 a3code = 3caps-letter ; eg: 'EUR', 'BTC' 224 caps-letter = %d65 / %d66 / %d67 / %d68 / %d69 / %d70 / %d71 / 225 %d72 / %d73 / %d74 / %d75 / %d76 / %d77 / %d78 / 226 %d79 / %d80 / %d81 / %d82 / %d83 / %d84 / %d85 / 227 %d86 / %d87 / %d88 / %d89 / %d90 ; ie. capital A-Z 229 An explanation of the major elements follows. 231 codepoint: 232 A structurally valid X-ISO4217-A3 codepoint in machine format, ie. 233 including the registry identifier. 235 registry: 236 A character identifying the source registry of the subsequent 237 'a3code' being either 'X' (denoting this registry, managed by IANA) 238 or 'Z' (denoting the official ISO4217 registry, managed by SIX on 239 behalf of the ISO). 241 a3code: 242 Alpha-three code. A three letter alphanumeric string identifying a 243 specific currency or currency-like commodity within the prior 244 'registry', as presently used within ISO4217 and unofficial 245 extensions to the ISO4217 system, for example: 'EUR' (official ISO 246 code denoting the Euro) or 'BTC' (widely used code denoting 247 Bitcoin [BITCOIN]). 249 3. Implementation Considerations 251 3.1. Input 253 3.1.1. Formats 255 For legacy reasons, input MAY be accepted in either of two formats: 257 Three character (X-ISO4217-A3 'a3code') format: 258 This is the format most familiar to end users, ie. codes such as 259 'MYR' (Malaysian Ringgit) or 'SLL' (Second Life Linden Dollar). 260 This code format excludes an explicit registry identifier. This 261 format MAY be supported. 263 Four character (X-ISO4217-A3) format: 264 The full X-ISO4217-A3 four character format, including an explicit 265 registry identifier. For example, 'ZMYR' (Malaysian Ringgit) or 266 'XSLL' (Second Life Linden Dollar). This format MUST be supported 267 in all cases. 269 3.1.2. End User Input 271 Systems accepting input from end users MUST accept codepoints from 272 each registry in an equal fashion, such that end users are NOT aware 273 of any difference between individual registries. 275 3.1.2.1. a3code Input 277 Implementations MAY allow 'a3code' input. In this case, 278 implementations MUST normalize input to a complete an unambiguous X- 279 ISO4217-A3 codepoint immediately, using the following algorithm: 281 - If the 'a3code' exists within a single registry, normalize to that 282 X-ISO4217-A3 code. The implementation SHOULD confirm or report on 283 the result of normalization. 285 - If the 'a3code' exists within multiple registries, NOT marked 286 as an historic allocation ('is_historic' field), the 287 implementation 288 MUST NOT normalize the value. The implementation MUST return an 289 error. The implementation MAY provide the appropriate subset of 290 normalization options to the end user or peer system to assist 291 with 292 building an additional query using properly normalized input. 294 3.1.3. Case Sensitivity 296 Implementations MAY accept mixed or lower case input, but MUST 297 normalize this input to (structurally valid) upper case prior to 298 processing or storage. For relevant security considerations, see 299 Case Normalization. 301 3.2. Output 302 3.2.1. Machine Presentation 304 Implementations MUST present upper case only, normalized 305 (structurally valid), four character X-ISO4217-A3 identifiers to peer 306 systems. 308 For example, 'XVER' (Non Kyoto Protocol Verified Emissions Reduction 309 CO2 Tonne). 311 3.2.2. End User Presentation 313 For user presentation purposes, systems MAY present the 'a3code' 314 element to end users rather than the full X-ISO4217-A3 codepoint (eg: 315 'BTC' instead of 'XBTC'). In such cases, adequate context SHOULD be 316 given in order to prevent ambiguity. Adequate context MAY include 317 the option to view the full X-ISO4217-A3 codepoint, the human 318 language currency name, and the source registry, AND/OR the 319 reconfirmation of any initiated operation with such clarifying 320 contextual information added prior to its actual execution. 322 3.3. Internationalization 324 The registry MAY include currency and entity names as arbitrary UTF8 325 strings. 327 To aid the international recognition of individual codepoints, 328 implementations MUST present only upper case normalized (structurally 329 valid) identifiers to both peer systems and end users. (See Case 330 Sensitivity). 332 4. Security Considerations 334 X-ISO4217-A3 only provides a currency or currency-like commodity 335 identification scheme and DOES NOT approach problems of 336 communications security, which are purposefully left to other 337 protocols. Even so, some security considerations are are pertinent. 339 4.1. Input 340 4.1.1. Input Confirmation 342 Because there is always some scope for error in systems requiring end 343 user input (see Case Normalization), unambiguous confirmation of 344 input SHOULD be provided. Such confirmation MAY include the full X- 345 ISO4217-A3 codepoint, the human language currency name, and the 346 source registry. 348 4.1.2. Case Normalization 350 It should be noted with regards to case normalization that some 351 frequency of manual recognition (or transposition) errors is likely 352 to occur whenever input is sought. This frequency increases in 353 situations where an end user does not have linguistic or other types 354 of clues regarding a source document's probable vocabulary or 355 semantics, or is simply unfamiliar with the material. Machine-style 356 codes, such as X-ISO4217-A3, therefore fall in to a relatively high 357 risk area, albiet one that conventional ISO4217 systems are also 358 vulnerable to. 360 When considering the implementation of X-ISO4217-A3 systems that 361 accept lower or mixed-case input, implementers SHOULD consider 362 carefully whether case normalization is an appropriate choice for 363 their systems, given that the scope for such errors is nominally 364 (though not hugely) increased. (For example, an input of 'Z' could 365 come from a user misunderstanding a lowercase 'r', or an input of 'U' 366 could come from a user misunderstanding a lowercase 'a'.) To some 367 extent this issue SHOULD be mitigated by the requirement that 368 implementations MUST present only upper case (structurally valid) 369 codepoints both to peer systems and end users. 371 4.2. IANA Processes 373 IANA MUST provide adequate authentication of registrant institution 374 communications in order to prevent the subversion of established 375 institutions' registration information via IANA's registrar 376 functions. 378 5. IANA Considerations 380 5.1. Name Space Exhaustion 382 Should the entire IANA-managed portion of the X-ISO4217-A3 namespace 383 approach registration, IANA MUST immediately select an additional 384 registry prefix. 386 5.2. Registration 388 Codepoints MUST be assigned by IANA on a first come first served 389 basis [RFC5226]. To support innovation, in contrast to conventional 390 financial registries, codepoints MUST be issued to ANY registrant 391 supplying a valid domain name and reasonable information. 393 Registrants MUST provide the domain name with which their service is 394 primarily associated AND the name of the registrant (either a person 395 or an organizational entity), as well as the appropriate contents for 396 the registry fields. 398 Registrants MAY request a specific codepoint, or IANA MAY assign them 399 one. 401 5.3. Modification / Cancellation 403 Due to the nature of currency and currency-like commodity 404 identification between disparate financial systems, codepoint 405 allocations are permanent and binding. However, modifications to 406 metadata are possible and SHOULD be effected by IANA within a few 407 working days. IANA should update the 'modified' field of the 408 registry entry in question to reflect the fact that modification has 409 taken place. 411 5.4. Publication 413 IANA SHALL publish revisions to the global registry of X-ISO4217-A3 414 codes as changes are made. 416 IANA SHALL, where possible, attempt to include any and all changes to 417 the ISO4217 official codepoints within the registry. Whilst the 418 copyright status of the codepoints remains unclear, they are 419 distributed freely to the public and have been widely republished in 420 open sources such as Wikipedia for an extended period, so should not 421 be of legal concern. IANA MAY contact the author for the code that 422 was used to compile the ISO distributed code lists in to the registry 423 format in order to assist with ongoing maintenance. 425 IANA SHALL provide GPG-compatible cryptographic signatures along with 426 each version of the registry. IANA MAY provide additional 427 cryptographic signatures and/or checksums at their sole discretion. 429 The registry SHALL utilize UTF8 encoding in order to meet 430 internationalization requirements for institution names. 432 The format and initial contents of this registry document are 433 specified in Appendix A. 435 5.5. ISO Liason 437 IANA SHOULD formally notify [SIX] (as the maintenance agency of the 438 ISO4217 registry) of the existence of this registry. IANA SHOULD 439 make [SIX] feel welcome to forward parties unsuccessful in their 440 applications for ISO4217 codepoints to IANA, in order to acquire 441 alternate codepoint registrations within the IANA-managed X- 442 ISO4217-A3 registry. 444 5.5.1. Resolving Duplicate Assignment 446 In addition, the ISO MAY wish to inform IANA of any upcoming 447 codepoint additions that will effect duplicate allocation between the 448 X-ISO4217-A3 and ISO4217 registries. In the event of such a 449 duplicate assignment, which is perceived as unlikely to occur outside 450 of exceptional cases, IANA SHOULD add a new, optional field 451 indicating external registry codepoint equivalence to X-ISO4217-A3 452 registry records. 454 5.6. Security 456 IANA MUST provide adequate authentication of registrant institution 457 communications in order to prevent the subversion of established 458 codepoints' metadata via IANA's registrar functions. 460 As IANA is likely to have superior experience in this domain, 461 specific procedures are left to IANA's judgement. 463 6. References 465 6.1. Normative References 467 [ISO4217] ISO. "ISO 4217 - Currency Codes", 468 http://www.iso.org/iso/home/standards/ 469 currency_codes.htm 471 [RFC2119] Bradner, S., "Key words for use in RFCs to 472 Indicate Requirement Levels", BCP 14, RFC 2119, 473 March 1997. 475 [RFC5226] Narten, T., and H. Alvestrand, "Guidelines for 476 Writing an IANA Considerations Section in RFCs", 477 BCP 26, RFC 5226, May 2008. 479 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for 480 Syntax Specifications: ABNF", STD 68, RFC 5234, 481 January 2008. 483 6.2. Informative References 485 [BITCOIN] Nakamoto, S., "Bitcoin: A Peer-to-Peer Electronic 486 Cash System", 2009-05-24. 487 http://www.bitcoin.org/bitcoin.pdf 489 [ISO-REJECTION] grossdigitalproduct, "getting BTC into ISO 4217 490 currency list", 10 November 2012. 491 https://bitcointalk.org/index.php?topic=123600 492 Relevant excerpt: 493 "I also understand you have previously denied 494 such requests with the following statements: 495 1. The currency code is not linked to any 496 country code. 497 2. The currency code is considered a 498 'private currency' and not used for 499 tender in any country. 500 3. There will be no international payments 501 denominated in Bitcoin therefore an ISO 502 currency code for the Bitcoin is not 503 applicable. 504 4. The Institution responsible for the 505 Bitcoin does not appear to be recognized 506 internationally or have any official 507 status. Neither Reuters or Bloomberg 508 provides market data related to its use." 510 [OXFORD] Oxford University Press, "Definition of currency" 511 http://oxforddictionaries.com/definition/english/ 512 currency 514 [PRB] Trans-Dniester Republican Bank, "History of coins 515 and banknotes". Retrieved November, 2012. 516 http://www.cbpmr.net/?id=33&lang=en 518 [SIX] SIX Interbank Clearing 519 http://www.six-interbank-clearing.com/ 521 [SLL] "Economy of Second Life" 522 http://en.wikipedia.org/wiki/Economy_of_Second_Life 524 [TEM] Exchange and Solidarity Network of Magnesia, 525 "Alternate Monetary Unit" 526 http://www.tem-magnisia.gr/ 528 [XRP] OpenCoin, Inc. "Ripple open source payment system" 529 http://ripple.com/ 531 7. Acknowledgments 533 * Payward, Inc. funded the research and development of this 534 document. 535 * The (completely OMC unaffiliated) OpenSimulator project staff were 536 helpful in clarifiying the origin and status of OMC. 537 * Valued feedback was provided by the following parties: 538 Bill McQuillan, OpenCoin Inc. 540 8. Authors' Addresses 542 Walter Stanish Payward, Inc. 544 On behalf of The Internet Financial EXchange (IFEX) Project: 545 http://www.ifex-project.org/ 547 9. Appendix A: Initial Registry Contents 549 Prior to IANA handover, parties wishing to acquire an identifier may do 550 so by contacting the IFEX Project via ifex-project.org 552 # X-ISO4217-A3: Unofficial ISO4217 Alpha-3 Extensions Registry. 553 # 554 # Version: 20121125-0 555 # (Format is
-, where x is a digit from 0-9) 556 # 557 # To be cryptographically signed by IANA and replicated freely. 558 # 559 # Format: 560 # - Lines beginning with '#' are comments. 561 # - Whitespace should be ignored. 562 # - Fields at the end of a record may be absent. 563 # 564 # Fields: 565 # registry Registry of origin. 566 # 567 # Code Registry Maintenance Agency 568 # ------------------------------------------- 569 # X X-ISO4217-A3 IANA 570 # Z ISO4217-A3 SIX Interbank Clearing 571 # 572 # a3code Three character code identifying the currency or 573 # currency-like commodity within a registry. 574 # 575 # is_meta Denotes a meta-assignment (not a normal currency). 576 # 577 # is_historic Denotes a historic codepoint (obsolete). 578 # 579 # name-singular Singular form name of the currency (or primary unit) 580 # 581 # e Number of post-decimal digits in normal use. 582 # 583 # created Date of registration (YYYY-MM-DD), or blank for 584 # external registries. 585 # 586 # modified Date last modified (YYYY-MM-DD, YYYY-MM or YYYY as 587 # reflecting accuracy known), or blank for codes 588 # not yet modified or codes in external registries, 589 # except in the case of historic codepoints for which 590 # the field indicates date of withdrawl (if known). 591 # 592 # domain Primary domain name associated with the record, or 593 # blank for external registries. 595 # 596 # registrant Native language name of the registrant (UTF8), or 597 # blank for external registries. 598 X|ACD|0|0|Avination Care Dollar|2|2012-11-13||avination.com|Avination 599 Virtual Limited 600 X|BTC|0|0|Bitcoin|8|2012-11-13||bitcoin.org|Bitcoin Community 601 X|CER|0|0|Kyoto Protocol Certified Emissions Reduction CO2 602 Tonne|4|2012-11-13|||United Nations Framework Convention on Climate 603 Change 604 X|OMC|0|0|Open Metaverse Currency|2|2012-11-13||Open Metaverse Currency 605 Community 606 X|PRB|0|0|Transistrian Ruble|0|2012-11-13||cbpmr.net|Trans-Dniester 607 Republican Bank 608 X|SLL|0|0|Second Life Linden Dollar|0|2012-11-13||secondlife.com|Linden 609 Research, Inc. 610 X|TEM|0|0|Volos Alternative Monetary Unit|0|2012-11-13||tem- 611 magnesia.gr|Volos Alternative Monetary Unit Community 612 X|VER|0|0|Non Kyoto Protocol Verified Emissions Reduction CO2 613 Tonne|4|2012-11-13|||Non Kyoto Protocol Verified Emissions Reduction 614 Community 615 X|XRP|0|0|Ripple Credit|6|2012-11-13||ripple.com|OpenCoin Inc. 616 Z|ADP|0|1|Andorran Peseta|||2003-07 617 Z|AED|0|0|UAE Dirham|2 618 Z|AFA|0|1|Afghani|||2003-01 619 Z|AFN|0|0|Afghani|2 620 Z|ALK|0|1|Old Lek|||1989-12 621 Z|ALL|0|0|Lek|2 622 Z|AMD|0|0|Armenian Dram|2 623 Z|ANG|0|1|Netherlands Antillean Guilder|||2010-10 624 Z|AOA|0|0|Kwanza|2 625 Z|AOK|0|1|Kwanza|||1991-03 626 Z|AON|0|1|New Kwanza|||2000-02 627 Z|AOR|0|1|Kwanza Reajustado|||2000-02 628 Z|ARA|0|1|Austral|||1992-01 629 Z|ARP|0|1|Peso Argentino|||1985-07 630 Z|ARS|0|0|Argentine Peso|2 631 Z|ARY|0|1|Peso|||1990 632 Z|ATS|0|1|Schilling|||2002-03 633 Z|AUD|0|0|Australian Dollar|2 634 Z|AWG|0|0|Aruban Florin|2 635 Z|AYM|0|1|Azerbaijan Manat|||2005-10 636 Z|AZM|0|1|Azerbaijanian Manat|||2005-12 637 Z|AZN|0|0|Azerbaijanian Manat|2 638 Z|BAD|0|1|Dinar|||1997-07 639 Z|BAM|0|0|Convertible Mark|2 640 Z|BBD|0|0|Barbados Dollar|2 641 Z|BDT|0|0|Taka|2 642 Z|BEC|0|1|Convertible Franc|||1990-03 643 Z|BEF|0|1|Belgian Franc|||2002-03 644 Z|BEL|0|1|Financial Franc|||1990-03 645 Z|BGJ|0|1|Lev A/52|||1990 646 Z|BGK|0|1|Lev A/62|||1990 647 Z|BGL|0|1|Lev|||2003-11 648 Z|BGN|0|0|Bulgarian Lev|2 649 Z|BHD|0|0|Bahraini Dinar|3 650 Z|BIF|0|0|Burundi Franc|0 651 Z|BMD|0|0|Bermudian Dollar|2 652 Z|BND|0|0|Brunei Dollar|2 653 Z|BOB|0|0|Boliviano|2 654 Z|BOP|0|1|Peso boliviano|||1987-02 655 Z|BOV|0|0|Mvdol|2 656 Z|BRB|0|1|Cruzeiro|||1986-03 657 Z|BRC|0|1|Cruzado|||1989-02 658 Z|BRE|0|1|Cruzeiro|||1993-03 659 Z|BRL|0|0|Brazilian Real|2 660 Z|BRN|0|1|New Cruzado|||1990-03 661 Z|BRR|0|1|Cruzeiro Real|||1994-07 662 Z|BSD|0|0|Bahamian Dollar|2 663 Z|BTN|0|0|Ngultrum|2 664 Z|BUK|0|1|N.A.|||1990-02 665 Z|BWP|0|0|Pula|2 666 Z|BYB|0|1|Belarussian Ruble|||2001-01 667 Z|BYR|0|0|Belarussian Ruble|0 668 Z|BZD|0|0|Belize Dollar|2 669 Z|CAD|0|0|Canadian Dollar|2 670 Z|CDF|0|0|Congolese Franc|2 671 Z|CHC|0|1|WIR Franc (for electronic)|||2004-11 672 Z|CHE|0|0|WIR Euro|2 673 Z|CHF|0|0|Swiss Franc|2 674 Z|CHW|0|0|WIR Franc|2 675 Z|CLF|0|0|Unidades de fomento|0 676 Z|CLP|0|0|Chilean Peso|0 677 Z|CNX|0|1|Peoples Bank Dollar|||1989-12 678 Z|CNY|0|0|Yuan Renminbi|2 679 Z|COP|0|0|Colombian Peso|2 680 Z|COU|0|0|Unidad de Valor Real|2 681 Z|CRC|0|0|Costa Rican Colon|2 682 Z|CSD|0|1|Serbian Dinar|||2006-10 683 Z|CSJ|0|1|Krona A/53|||1990 684 Z|CSK|0|1|Koruna|||1993-03 685 Z|CUC|0|0|Peso Convertible|2 686 Z|CUP|0|0|Cuban Peso|2 687 Z|CVE|0|0|Cape Verde Escudo|2 688 Z|CYP|0|1|Cyprus Pound|||2008-01 689 Z|CZK|0|0|Czech Koruna|2 690 Z|DDM|0|1|Mark der DDR|||1990-09 691 Z|DEM|0|1|Deutsche Mark|||2002-03 692 Z|DJF|0|0|Djibouti Franc|0 693 Z|DKK|0|0|Danish Krone|2 694 Z|DOP|0|0|Dominican Peso|2 695 Z|DZD|0|0|Algerian Dinar|2 696 Z|ECS|0|1|Sucre|||2000-09 697 Z|ECV|0|1|Unidad de Valor Constante (UVC)|||2000-09 698 Z|EEK|0|1|Kroon|||2011-01 699 Z|EGP|0|0|Egyptian Pound|2 700 Z|EQE|0|1|Ekwele|||1989-12 701 Z|ERN|0|0|Nakfa|2 702 Z|ESA|0|1|Spanish Peseta|||1981 703 Z|ESB|0|1|"A" Account (convertible Peseta Account)|||1994-12 704 Z|ESP|0|1|Spanish Peseta|||2002-03 705 Z|ETB|0|0|Ethiopian Birr|2 706 Z|EUR|0|1|Euro|||2006-10 707 Z|FIM|0|1|Markka|||2002-03 708 Z|FJD|0|0|Fiji Dollar|2 709 Z|FKP|0|0|Falkland Islands Pound|2 710 Z|FRF|0|1|French Franc|||1999-01 711 Z|GBP|0|0|Pound Sterling|2 712 Z|GEK|0|1|Georgian Coupon|||1995-10 713 Z|GEL|0|0|Lari|2 714 Z|GHC|0|1|Cedi|||2008-01 715 Z|GHP|0|1|Ghana Cedi|||2007-06 716 Z|GHS|0|0|Ghana Cedi|2 717 Z|GIP|0|0|Gibraltar Pound|2 718 Z|GMD|0|0|Dalasi|2 719 Z|GNE|0|1|Syli|||1989-12 720 Z|GNF|0|0|Guinea Franc|0 721 Z|GNS|0|1|Syli|||1986-02 722 Z|GQE|0|1|Ekwele|||1986-06 723 Z|GRD|0|1|Drachma|||2002-03 724 Z|GTQ|0|0|Quetzal|2 725 Z|GWE|0|1|Guinea Escudo|||1981 726 Z|GWP|0|1|Guinea-Bissau Peso|||1997-05 727 Z|GYD|0|0|Guyana Dollar|2 728 Z|HKD|0|0|Hong Kong Dollar|2 729 Z|HNL|0|0|Lempira|2 730 Z|HRD|0|1|Croatian Dinar|||1995-01 731 Z|HRK|0|0|Croatian Kuna|2 732 Z|HTG|0|0|Gourde|2 733 Z|HUF|0|0|Forint|2 734 Z|IDR|0|1|Rupiah|||2002-07 735 Z|IEP|0|1|Irish Pound|||2002-03 736 Z|ILP|0|1|Pound|||1981 737 Z|ILR|0|1|Old Shekel|||1990 738 Z|ILS|0|0|New Israeli Sheqel|2 739 Z|INR|0|0|Indian Rupee|2 740 Z|IQD|0|0|Iraqi Dinar|3 741 Z|IRR|0|0|Iranian Rial|2 742 Z|ISJ|0|1|Old Krona|||1990 743 Z|ISK|0|0|Iceland Krona|0 744 Z|ITL|0|1|Italian Lira|||2002-03 745 Z|JMD|0|0|Jamaican Dollar|2 746 Z|JOD|0|0|Jordanian Dinar|3 747 Z|JPY|0|0|Yen|0 748 Z|KES|0|0|Kenyan Shilling|2 749 Z|KGS|0|0|Som|2 750 Z|KHR|0|0|Riel|2 751 Z|KMF|0|0|Comoro Franc|0 752 Z|KPW|0|0|North Korean Won|2 753 Z|KRW|0|0|Won|0 754 Z|KWD|0|0|Kuwaiti Dinar|3 755 Z|KYD|0|0|Cayman Islands Dollar|2 756 Z|KZT|0|0|Tenge|2 757 Z|LAJ|0|1|Kip Pot Pol|||1989-12 758 Z|LAK|0|0|Kip|2 759 Z|LBP|0|0|Lebanese Pound|2 760 Z|LKR|0|0|Sri Lanka Rupee|2 761 Z|LRD|0|0|Liberian Dollar|2 762 Z|LSL|0|0|Loti|2 763 Z|LSM|0|1|Maloti|||1985-05 764 Z|LTL|0|0|Lithuanian Litas|2 765 Z|LTT|0|1|Talonas|||1993-07 766 Z|LUC|0|1|Luxembourg Convertible Franc|||1990-03 767 Z|LUF|0|1|Luxembourg Franc|||2002-03 768 Z|LUL|0|1|Luxembourg Financial Franc|||1990-03 769 Z|LVL|0|0|Latvian Lats|2 770 Z|LVR|0|1|Latvian Ruble|||1994-12 771 Z|LYD|0|0|Libyan Dinar|3 772 Z|MAD|0|0|Moroccan Dirham|2 773 Z|MAF|0|1|Mali Franc|||1989-12 774 Z|MDL|0|0|Moldovan Leu|2 775 Z|MGA|0|0|Malagasy Ariary|2 776 Z|MGF|0|1|Malagasy Franc|||2004-12 777 Z|MKD|0|0|Denar|2 778 Z|MLF|0|1|Mali Franc|||1984-11 779 Z|MMK|0|0|Kyat|2 780 Z|MNT|0|0|Tugrik|2 781 Z|MOP|0|0|Pataca|2 782 Z|MRO|0|0|Ouguiya|2 783 Z|MTL|0|1|Maltese Lira|||2008-01 784 Z|MTP|0|1|Maltese Pound|||1983-06 785 Z|MUR|0|0|Mauritius Rupee|2 786 Z|MVQ|0|1|Maldive Rupee|||1989-12 787 Z|MVR|0|0|Rufiyaa|2 788 Z|MWK|0|0|Kwacha|2 789 Z|MXN|0|0|Mexican Peso|2 790 Z|MXP|0|1|Mexican Peso|||1993-01 791 Z|MXV|0|0|Mexican Unidad de Inversion (UDI)|2 792 Z|MYR|0|0|Malaysian Ringgit|2 793 Z|MZE|0|1|Mozambique Escudo|||1981 794 Z|MZM|0|1|Mozambique Metical|||2006-06 795 Z|MZN|0|0|Mozambique Metical|2 796 Z|NAD|0|0|Namibia Dollar|2 797 Z|NGN|0|0|Naira|2 798 Z|NIC|0|1|Cordoba|||1990-10 799 Z|NIO|0|0|Cordoba Oro|2 800 Z|NLG|0|1|Netherlands Guilder|||2002-03 801 Z|NOK|0|0|Norwegian Krone|2 802 Z|NPR|0|0|Nepalese Rupee|2 803 Z|NZD|0|0|New Zealand Dollar|2 804 Z|OMR|0|0|Rial Omani|3 805 Z|PAB|0|0|Balboa|2 806 Z|PEH|0|1|Sol|||1990 807 Z|PEI|0|1|Inti|||1991-07 808 Z|PEN|0|0|Nuevo Sol|2 809 Z|PES|0|1|Sol|||1986-02 810 Z|PGK|0|0|Kina|2 811 Z|PHP|0|0|Philippine Peso|2 812 Z|PKR|0|0|Pakistan Rupee|2 813 Z|PLN|0|0|Zloty|2 814 Z|PLZ|0|1|Zloty|||1997-01 815 Z|PTE|0|1|Portuguese Escudo|||2002-03 816 Z|PYG|0|0|Guarani|0 817 Z|QAR|0|0|Qatari Rial|2 818 Z|RHD|0|1|Rhodesian Dollar|||1981 819 Z|ROK|0|1|Leu A/52|||1990 820 Z|ROL|0|1|Old Leu|||2005-06 821 Z|RON|0|0|New Romanian Leu|2 822 Z|RSD|0|0|Serbian Dinar|2 823 Z|RUB|0|0|Russian Ruble|2 824 Z|RUR|0|1|Russian Ruble|||1994-07 825 Z|RWF|0|0|Rwanda Franc|0 826 Z|SAR|0|0|Saudi Riyal|2 827 Z|SBD|0|0|Solomon Islands Dollar|2 828 Z|SCR|0|0|Seychelles Rupee|2 829 Z|SDD|0|1|Sudanese Dinar|||2007-07 830 Z|SDG|0|1|Sudanese Pound|||2012-09 831 Z|SDP|0|1|Sudanese Pound|||1998-06 832 Z|SEK|0|0|Swedish Krona|2 833 Z|SGD|0|0|Singapore Dollar|2 834 Z|SHP|0|0|Saint Helena Pound|2 835 Z|SIT|0|1|Tolar|||2007-01 836 Z|SKK|0|1|Slovak Koruna|||2009-01 837 Z|SLL|0|0|Leone|2 838 Z|SOS|0|0|Somali Shilling|2 839 Z|SRD|0|0|Surinam Dollar|2 840 Z|SRG|0|1|Surinam Guilder|||2003-12 841 Z|SSP|0|0|South Sudanese Pound|2 842 Z|STD|0|0|Dobra|2 843 Z|SUR|0|1|Rouble|||1990-12 844 Z|SVC|0|0|El Salvador Colon|2 845 Z|SYP|0|0|Syrian Pound|2 846 Z|SZL|0|0|Lilangeni|2 847 Z|THB|0|0|Baht|2 848 Z|TJR|0|1|Tajik Ruble|||2001-04 849 Z|TJS|0|0|Somoni|2 850 Z|TMM|0|1|Turkmenistan Manat|||2009-01 851 Z|TMT|0|0|Turkmenistan New Manat|2 852 Z|TND|0|0|Tunisian Dinar|3 853 Z|TOP|0|0|Pa'anga|2 854 Z|TPE|0|1|Timor Escudo|||2002-11 855 Z|TRL|0|1|Old Turkish Lira|||2005-12 856 Z|TRY|0|1|New Turkish Lira|||2009-01 857 Z|TTD|0|0|Trinidad and Tobago Dollar|2 858 Z|TWD|0|0|New Taiwan Dollar|2 859 Z|TZS|0|0|Tanzanian Shilling|2 860 Z|UAH|0|0|Hryvnia|2 861 Z|UAK|0|1|Karbovanet|||1996-09 862 Z|UGS|0|1|Uganda Shilling|||1987-05 863 Z|UGW|0|1|Old Shilling|||1990 864 Z|UGX|0|0|Uganda Shilling|0 865 Z|USD|0|0|US Dollar|2 866 Z|USN|0|0|US Dollar (Next day)|2 867 Z|USS|0|0|US Dollar (Same day)|2 868 Z|UYI|0|0|Uruguay Peso en Unidades Indexadas (URUIURUI)|0 869 Z|UYN|0|1|Old Uruguay Peso|||1989-12 870 Z|UYP|0|1|Uruguayan Peso|||1993-03 871 Z|UYU|0|0|Peso Uruguayo|2 872 Z|UZS|0|0|Uzbekistan Sum|2 873 Z|VEB|0|1|Bolivar|||2008-01 874 Z|VEF|0|1|Bolivar Fuerte|||2011-12 875 Z|VNC|0|1|Old Dong|||1989-1990 876 Z|VND|0|0|Dong|0 877 Z|VUV|0|0|Vatu|0 878 Z|WST|0|0|Tala|2 879 Z|XAF|0|0|CFA Franc BEAC|0 880 Z|XAG|0|0|Silver 881 Z|XAU|0|0|Gold 882 Z|XBA|0|0|Bond Markets Unit European Composite Unit (EURCO) 883 Z|XBB|0|0|Bond Markets Unit European Monetary Unit (E.M.U.-6) 884 Z|XBC|0|0|Bond Markets Unit European Unit of Account 9 (E.U.A.-9) 885 Z|XBD|0|0|Bond Markets Unit European Unit of Account 17 (E.U.A.-17) 886 Z|XCD|0|0|East Caribbean Dollar|2 887 Z|XDR|1|0|SDR (Special Drawing Right) 888 Z|XEU|0|1|European Currency Unit (E.C.U)|||1999-01 889 Z|XFO|0|1|Gold-Franc|||2006-10 890 Z|XFU|0|0|UIC-Franc 891 Z|XOF|0|0|CFA Franc BCEAO|0 892 Z|XPD|0|0|Palladium 893 Z|XPF|0|0|CFP Franc|0 894 Z|XPT|0|0|Platinum 895 Z|XRE|0|1|RINET Funds Code|||1999-11 896 Z|XSU|0|0|Sucre 897 Z|XTS|1|0|Codes specifically reserved for testing purposes 898 Z|XUA|0|0|ADB Unit of Account 899 Z|XXX|1|0|The codes assigned for transactions where no currency is 900 involved 901 Z|YDD|0|1|Yemeni Dinar|||1991-09 902 Z|YER|0|0|Yemeni Rial|2 903 Z|YUD|0|1|New Yugoslavian Dinar|||1990-01 904 Z|YUM|0|1|New Dinar|||2003-07 905 Z|YUN|0|1|Yugoslavian Dinar|||1995-11 906 Z|ZAL|0|1|Financial Rand|||1995-03 907 Z|ZAR|0|0|Rand|2 908 Z|ZMK|0|1|Zambian Kwacha|||2012-12 909 Z|ZRN|0|1|New Zaire|||1999-06 910 Z|ZRZ|0|1|Zaire|||1994-02 911 Z|ZWC|0|1|Rhodesian Dollar|||1989-12 912 Z|ZWD|0|1|Zimbabwe Dollar|||2008-08 913 Z|ZWL|0|0|Zimbabwe Dollar|2 914 Z|ZWN|0|1|Zimbabwe Dollar (new)|||2006-09 915 Z|ZWR|0|1|Zimbabwe Dollar|||2009-06 917 10. Appendix B: ISO4217 Registry Issues 919 In researching this document the following issues were observed within 920 the ISO4217 registry publications provided at http://www.currency- 921 iso.org/: 923 Indistinct Requirements for Issue: 924 As discussed earlier in this document, there does not 925 appear to be any publicly available definition of the 926 requirements for codepoint registration within the 927 traditional ISO 4217 registry. Combined with observed 928 behaviors in denying registration requests, this fact 929 highlights the need for alternate registries. 931 Possible Conflict of Interest: 932 The present registry maintenance agency for ISO 4217 is 933 SIX Interbank Clearing, a Swiss entity that is strongly 934 affiliated with the existing SWIFT interbank clearing 935 network. Due to the innovative privision of alternate 936 international settlement paradigms provided by some 937 emerging electronic currencies and currency-like 938 commodities ([BITCOIN], etc.) this raises the question 939 of conflict of interest. 941 Historical Codepoint Division: 942 The lack of a unified distribution of current and historic 943 codepoints (properties, single publication source, etc.) 944 requires manual coordination and processing that is 945 problematic for implementors. 947 Lack of Codepoint Divisions: 948 There is no division within the ISO 4217 registry 949 publications regarding meta-assignments (such as test 950 codes and codes for organization-internal use) and normal 951 codepoints, nor between currency-like commodities and 952 conventional nationally linked currencies, nor between 953 currencies or currency-like commodities of decentralized 954 (non-consolidated) issue vs. conventional, national 955 currencies. This means that the majority of implementors 956 who do not wish to handle certain codepoint types (for 957 instance, the Swiss WIR mutual credit clearing system, 958 special drawing rights or accounting units used in 959 specific organizations such as the African Development 960 Bank) face a requirement for the definition of ad-hoc 961 codepoint subsets for display purposes. 963 11. Appendix C: Document History 965 draft-stanish-x-iso4217-a3-01 (2012-11-25) 966 - Complete section on input treatment. 967 - Expand treatment of formatting and add section on prefix 968 selection in response to feedback from Bill McQuillan. 969 - Change ISO identifier to 'Z' in response to feedback 970 from Bill McQuillan. 971 - Add IANA notes on handling ISO duplicate assignments. 972 - Modify IANA considerations regarding code maintenance. 973 - Correct formatting and typographic errors. 975 draft-stanish-x-iso4217-a3-00 (2012-11-13) 976 Initial release.