-
Notifications
You must be signed in to change notification settings - Fork 36
/
draft-stanish-x-iso4217-a3-02.txt
1392 lines (899 loc) · 42.4 KB
/
draft-stanish-x-iso4217-a3-02.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
INTERNET-DRAFT Walter Stanish
Intended status: Informational The IFEX Project
Expires: May 26, 2013 ifex-project.org
November 2012
Registry of Unofficial Extensions to the ISO 4217 Alpha Three Currency
Identification Namespace (X-ISO4217-A3)
draft-stanish-x-iso4217-a3-02
Abstract
This document defines a new IANA registry to keep track of
identifiers for currencies or currency-like commodities lying outside
the traditional scope of the International Organization for
Standardization (ISO) 4217 alpha-3 standard, such as digital
currencies and commodities, currencies issued by countries (nation-
states) with limited international recognition, emerging commodities
such as emissions reduction credits, private or commercial
currencies, and accounting units for local exchange and trading
systems (LETS). Such codes are already in use; the registry simply
codifies their existence. This document obsoletes draft-stanish-x-
iso4217-a3-01.
Status of this Memo
This memo defines an Experimental Protocol for the Internet
community. This memo does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The IFEX Project / ifex-project.org [Page 1]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
This document is an individual submission. Comments are solicited
and should be addressed to the author(s).
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
This Internet-Draft will expire on May 26, 2013.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
The IFEX Project / ifex-project.org Section 1. [Page 2]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
1. Introduction
The vast majority of multicurrency financial systems today use the
International Organization for Standardization (ISO) 4217 standard
for currency identification, which provides three digit numeric and
three letter ("alpha-3") codepoints for the identification of each
currency. The latter, letter-based codes are in far greater use.
ISO4217 codepoints are registered by the International Organization
for Standardization through the maintenance agency for the registry,
SIX Interbank Clearing [SIX], a Swiss financial body.
The specific terms of SIX or the ISO's mandate within the currency
sphere do not appear to be publicly available. However, given that
geographically defined nation-states with some international
recognition and physically circulating currency (such as Transnistria
[PRB]) have not been issued currency codes, and leaving aside the
relatively large scope for raising conflict of interest questions
with regards to SIX's SWIFT links, it is reasonable to assume that
SIX and the ISO's mandate and/or sphere of interest in the currency
domain is highly unlikely to suddenly extend to emerging currency-
like commodities lacking some or all of the political qualities
exhibited by conventional currencies.
At present, issued codepoints are almost exclusively linked to
national or supra-national entities (eg. 'EUR' for the Euro, the
currency of the European Union) that have achieved political
recognition from the United Nations, with some exceptions for the
more popular traditional commodities, such as gold, and various
regional instruments backed by similar political entities.
This is understandable, given that conventional definitions of the
term 'currency' are often inextricably linked to the notion of
national issue by 'countries' or nation-states:
"a system of money in general use in a particular country"
-- The Oxford Dictionary [OXFORD]
Therefore currencies and currency-like commodities with far smaller
circulation not adopting a traditional national paradigm of issue are
unlikely to be granted a codepoint. Indeed, there is some evidence
that SIX Interbank Clearing has rejected proposals for such
registrations in the recent past, citing lack of a national entity
backing a particular currency. [ISO-REJECTION]
This situation has left both end users and system developers and
integrators in a quandry; in response they have apparently near
The IFEX Project / ifex-project.org Section 1. [Page 3]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
uniformly opted to respond by issuing unofficial ISO4217 alpha-3
codes for private use.
The present problem is that, given the recent growth of such
unofficial codes, and the increasing exchange of such assets across
disparate systems, no registry of unofficial codepoints exists.
Therefore no unambiguous, internet-wide, shared vocabulary can be
adopted by internet systems to identify this emerging class of
assets.
This document proposes the establishment of a registry to be
maintained by the Internet Assigned Numbers Authority (IANA) in order
to resolve this issue by creating an unofficial, parallel namespace
codifying such unofficial extensions to the ISO4217 alpha-3 official
standard, tracking present and future unofficial assignments.
Examples of currencies or currency-like commodities for which systems
may benefit from such registration include decentralized digital
currencies such as Bitcoin [BITCOIN], the upcoming Ripple Credit
[XRP], private currency systems [SLL], and regional currencies of
limited political recognition [PRB] [TEM].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119].
The IFEX Project / ifex-project.org Section 1. [Page 4]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. X-ISO4217-A3 . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1. Examples. . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2. Source Registry Identification. . . . . . . . . . . . . . . 6
2.3. Codepoint Identification. . . . . . . . . . . . . . . . . . 6
3. Implementation Considerations. . . . . . . . . . . . . . . . . 7
3.1. Input . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.1. Formats. . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.2. End User Input . . . . . . . . . . . . . . . . . . . . . 8
3.1.2.1. a3code Input. . . . . . . . . . . . . . . . . . . . . 8
3.1.3. Case Sensitivity . . . . . . . . . . . . . . . . . . . . 8
3.2. Output. . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.1. Machine Presentation . . . . . . . . . . . . . . . . . . 9
3.2.2. End User Presentation. . . . . . . . . . . . . . . . . . 9
3.3. Internationalization. . . . . . . . . . . . . . . . . . . . 9
4. Security Considerations. . . . . . . . . . . . . . . . . . . . 9
4.1. Input . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.1. Input Confirmation . . . . . . . . . . . . . . . . . . . 10
4.1.2. Case Normalization . . . . . . . . . . . . . . . . . . . 10
4.2. IANA Processes. . . . . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 10
5.1. Name Space Exhaustion . . . . . . . . . . . . . . . . . . . 10
5.2. Registration. . . . . . . . . . . . . . . . . . . . . . . . 11
5.3. Modification / Cancellation . . . . . . . . . . . . . . . . 11
5.4. Publication . . . . . . . . . . . . . . . . . . . . . . . . 11
5.5. ISO Liason. . . . . . . . . . . . . . . . . . . . . . . . . 12
5.5.1. Resolving Duplicate Assignment . . . . . . . . . . . . . 12
5.6. Security. . . . . . . . . . . . . . . . . . . . . . . . . . 12
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Normative References. . . . . . . . . . . . . . . . . . . . 13
6.2. Informative References. . . . . . . . . . . . . . . . . . . 14
7. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 15
8. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 15
9. Appendix A: Initial Registry Contents. . . . . . . . . . . . . 16
10. Appendix B: ISO4217 Registry Issues . . . . . . . . . . . . . 24
11. Appendix C: Document History. . . . . . . . . . . . . . . . . 25
The IFEX Project / ifex-project.org Section 1. [Page 5]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
2. X-ISO4217-A3
Official [ISO4217] codepoints shall be considered a subset of a
larger namespace, based upon a longer machine-format codepoint,
providing unambiguous identification of currencies and currency-like
commodities both within and beyond conventional ISO4217 assignment.
However, existing end user expectations regarding three-character
('a3code') format and presentation are respected.
Systems implementers providing X-ISO4217-A3 support remain safe in
the knowledge that they will have the capacity to support all ISO4217
alpha-3 codepoints in addition to arbitrary currencies and currency-
like commodities.
2.1. Examples
The Euro is encoded as 'ZEUR'.
The digital currency or currency-like commodity known as Bitcoin is
encoded as 'XBTC'.
2.2. Source Registry Identification
In order to issue superset-compatible currency and currency-like
commodity identifiers within the [ISO4217] scheme, a prefix character
is introduced denominating the source registry, being either this
IANA-managed and unofficial registry (denoted with 'X') or the
official ISO-managed registry (denoted with 'Z').
The 'X' notation is chosen as is the standard semantic for unofficial
extensions within internet drafts. The 'Z' notation is chosen as a
less frequently used opening consonant in Roman languages, thus
reducing the likelihood of unfortunate four-letter linguistic
connotations.
2.3. Codepoint Identification
The X-ISO4217-A3 format may be expressed in ABNF [RFC5234] as
follows:
codepoint = registry a3code ; eg: 'XBTC', 'ZEUR'
registry = reg-x / reg-z ; ie: capital 'X', capital 'Z'
The IFEX Project / ifex-project.org Section 2.3. [Page 6]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
reg-x = %d88 ; X-ISO4217-A3 (IANA managed)
reg-z = %d90 ; ISO4217-A3 (ISO managed)
a3code = 3caps-letter ; eg: 'EUR', 'BTC'
caps-letter = %d65 / %d66 / %d67 / %d68 / %d69 / %d70 / %d71 /
%d72 / %d73 / %d74 / %d75 / %d76 / %d77 / %d78 /
%d79 / %d80 / %d81 / %d82 / %d83 / %d84 / %d85 /
%d86 / %d87 / %d88 / %d89 / %d90 ; ie. capital A-Z
An explanation of the major elements follows.
codepoint:
A structurally valid X-ISO4217-A3 codepoint in machine format, ie.
including the registry identifier.
registry:
A character identifying the source registry of the subsequent
'a3code' being either 'X' (denoting this registry, managed by IANA)
or 'Z' (denoting the official ISO4217 registry, managed by SIX on
behalf of the ISO).
a3code:
Alpha-three code. A three letter alphanumeric string identifying a
specific currency or currency-like commodity within the prior
'registry', as presently used within ISO4217 and unofficial
extensions to the ISO4217 system, for example: 'EUR' (official ISO
code denoting the Euro) or 'BTC' (widely used code denoting
Bitcoin [BITCOIN]).
3. Implementation Considerations
3.1. Input
3.1.1. Formats
For legacy reasons, input MAY be accepted in either of two formats:
Three character (X-ISO4217-A3 'a3code') format:
This is the format most familiar to end users, ie. codes such as
'MYR' (Malaysian Ringgit) or 'SLL' (Second Life Linden Dollar).
This code format excludes an explicit registry identifier. This
format MAY be supported.
The IFEX Project / ifex-project.org Section 3.1.1. [Page 7]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
Four character (X-ISO4217-A3) format:
The full X-ISO4217-A3 four character format, including an explicit
registry identifier. For example, 'ZMYR' (Malaysian Ringgit) or
'XSLL' (Second Life Linden Dollar). This format MUST be supported
in all cases.
3.1.2. End User Input
Systems accepting input from end users MUST accept codepoints from
each registry in an equal fashion, such that end users are NOT aware
of any difference between individual registries.
3.1.2.1. a3code Input
Implementations MAY allow 'a3code' input. In this case,
implementations MUST normalize input to a complete an unambiguous X-
ISO4217-A3 codepoint immediately, using the following algorithm:
- If the 'a3code' exists within a single registry, normalize to that
X-ISO4217-A3 code. The implementation SHOULD confirm or report on
the result of normalization.
- If the 'a3code' exists within multiple registries, NOT marked
as an historic allocation ('is_historic' field), the
implementation
MUST NOT normalize the value. The implementation MUST return an
error. The implementation MAY provide the appropriate subset of
normalization options to the end user or peer system to assist
with
building an additional query using properly normalized input.
3.1.3. Case Sensitivity
Implementations MAY accept mixed or lower case input, but MUST
normalize this input to (structurally valid) upper case prior to
processing or storage. For relevant security considerations, see
Case Normalization.
3.2. Output
The IFEX Project / ifex-project.org Section 3.2. [Page 8]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
3.2.1. Machine Presentation
Implementations MUST present upper case only, normalized
(structurally valid), four character X-ISO4217-A3 identifiers to peer
systems.
For example, 'XVER' (Non Kyoto Protocol Verified Emissions Reduction
CO2 Tonne).
3.2.2. End User Presentation
For user presentation purposes, systems MAY present the 'a3code'
element to end users rather than the full X-ISO4217-A3 codepoint (eg:
'BTC' instead of 'XBTC'). In such cases, adequate context SHOULD be
given in order to prevent ambiguity. Adequate context MAY include
the option to view the full X-ISO4217-A3 codepoint, the human
language currency name, and the source registry, AND/OR the
reconfirmation of any initiated operation with such clarifying
contextual information added prior to its actual execution.
3.3. Internationalization
The registry MAY include currency and entity names as arbitrary UTF8
strings.
To aid the international recognition of individual codepoints,
implementations MUST present only upper case normalized (structurally
valid) identifiers to both peer systems and end users. (See Case
Sensitivity).
4. Security Considerations
X-ISO4217-A3 only provides a currency or currency-like commodity
identification scheme and DOES NOT approach problems of
communications security, which are purposefully left to other
protocols. Even so, some security considerations are are pertinent.
4.1. Input
The IFEX Project / ifex-project.org Section 4.1. [Page 9]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
4.1.1. Input Confirmation
Because there is always some scope for error in systems requiring end
user input (see Case Normalization), unambiguous confirmation of
input SHOULD be provided. Such confirmation MAY include the full X-
ISO4217-A3 codepoint, the human language currency name, and the
source registry.
4.1.2. Case Normalization
It should be noted with regards to case normalization that some
frequency of manual recognition (or transposition) errors is likely
to occur whenever input is sought. This frequency increases in
situations where an end user does not have linguistic or other types
of clues regarding a source document's probable vocabulary or
semantics, or is simply unfamiliar with the material. Machine-style
codes, such as X-ISO4217-A3, therefore fall in to a relatively high
risk area, albiet one that conventional ISO4217 systems are also
vulnerable to.
When considering the implementation of X-ISO4217-A3 systems that
accept lower or mixed-case input, implementers SHOULD consider
carefully whether case normalization is an appropriate choice for
their systems, given that the scope for such errors is nominally
(though not hugely) increased. (For example, an input of 'Z' could
come from a user misunderstanding a lowercase 'r', or an input of 'U'
could come from a user misunderstanding a lowercase 'a'.) To some
extent this issue SHOULD be mitigated by the requirement that
implementations MUST present only upper case (structurally valid)
codepoints both to peer systems and end users.
4.2. IANA Processes
IANA MUST provide adequate authentication of registrant institution
communications in order to prevent the subversion of established
institutions' registration information via IANA's registrar
functions.
5. IANA Considerations
5.1. Name Space Exhaustion
Should the entire IANA-managed portion of the X-ISO4217-A3 namespace
approach registration, IANA MUST immediately select an additional
The IFEX Project / ifex-project.org Section 5.1. [Page 10]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
registry prefix.
5.2. Registration
Codepoints MUST be assigned by IANA on a first come first served
basis [RFC5226]. To support innovation, in contrast to conventional
financial registries, codepoints MUST be issued to ANY registrant
supplying a valid domain name and reasonable information.
Registrants MUST provide the domain name with which their service is
primarily associated AND the name of the registrant (either a person
or an organizational entity), as well as the appropriate contents for
the registry fields.
Registrants MAY request a specific codepoint, or IANA MAY assign them
one.
5.3. Modification / Cancellation
Due to the nature of currency and currency-like commodity
identification between disparate financial systems, codepoint
allocations are permanent and binding. However, modifications to
metadata are possible and SHOULD be effected by IANA within a few
working days. IANA should update the 'modified' field of the
registry entry in question to reflect the fact that modification has
taken place.
5.4. Publication
IANA SHALL publish revisions to the global registry of X-ISO4217-A3
codes as changes are made.
IANA SHALL, where possible, attempt to include any and all changes to
the ISO4217 official codepoints within the registry. Whilst the
copyright status of the codepoints remains unclear, they are
distributed freely to the public and have been widely republished in
open sources such as Wikipedia for an extended period, so should not
be of legal concern. IANA MAY contact the author for the code that
was used to compile the ISO distributed code lists in to the registry
format in order to assist with ongoing maintenance.
IANA SHALL provide GPG-compatible cryptographic signatures along with
each version of the registry. IANA MAY provide additional
cryptographic signatures and/or checksums at their sole discretion.
The IFEX Project / ifex-project.org Section 5.4. [Page 11]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
The registry SHALL utilize UTF8 encoding in order to meet
internationalization requirements for institution names.
The format and initial contents of this registry document are
specified in Appendix A.
5.5. ISO Liason
IANA SHOULD formally notify [SIX] (as the maintenance agency of the
ISO4217 registry) of the existence of this registry. IANA SHOULD
make [SIX] feel welcome to forward parties unsuccessful in their
applications for ISO4217 codepoints to IANA, in order to acquire
alternate codepoint registrations within the IANA-managed X-
ISO4217-A3 registry.
5.5.1. Resolving Duplicate Assignment
In addition, the ISO MAY wish to inform IANA of any upcoming
codepoint additions that will effect duplicate allocation between the
X-ISO4217-A3 and ISO4217 registries. In the event of such a
duplicate assignment, which is perceived as unlikely to occur outside
of exceptional cases, IANA SHOULD add a new, optional field
indicating external registry codepoint equivalence to X-ISO4217-A3
registry records.
5.6. Security
IANA MUST provide adequate authentication of registrant institution
communications in order to prevent the subversion of established
codepoints' metadata via IANA's registrar functions.
As IANA is likely to have superior experience in this domain,
specific procedures are left to IANA's judgement.
The IFEX Project / ifex-project.org Section 5.6. [Page 12]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
6. References
6.1. Normative References
[ISO4217] ISO. "ISO 4217 - Currency Codes",
http://www.iso.org/iso/home/standards/
currency_codes.htm
[RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14, RFC 2119,
March 1997.
[RFC5226] Narten, T., and H. Alvestrand, "Guidelines for
Writing an IANA Considerations Section in RFCs",
BCP 26, RFC 5226, May 2008.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for
Syntax Specifications: ABNF", STD 68, RFC 5234,
January 2008.
The IFEX Project / ifex-project.org Section 6.1. [Page 13]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
6.2. Informative References
[BITCOIN] Nakamoto, S., "Bitcoin: A Peer-to-Peer Electronic
Cash System", 2009-05-24.
http://www.bitcoin.org/bitcoin.pdf
[ISO-REJECTION] grossdigitalproduct, "getting BTC into ISO 4217
currency list", 10 November 2012.
https://bitcointalk.org/index.php?topic=123600
Relevant excerpt:
"I also understand you have previously denied
such requests with the following statements:
1. The currency code is not linked to any
country code.
2. The currency code is considered a
'private currency' and not used for
tender in any country.
3. There will be no international payments
denominated in Bitcoin therefore an ISO
currency code for the Bitcoin is not
applicable.
4. The Institution responsible for the
Bitcoin does not appear to be recognized
internationally or have any official
status. Neither Reuters or Bloomberg
provides market data related to its use."
[OXFORD] Oxford University Press, "Definition of currency"
http://oxforddictionaries.com/definition/english/
currency
[PRB] Trans-Dniester Republican Bank, "History of coins
and banknotes". Retrieved November, 2012.
http://www.cbpmr.net/?id=33&lang=en
[SIX] SIX Interbank Clearing
http://www.six-interbank-clearing.com/
[SLL] "Economy of Second Life"
http://en.wikipedia.org/wiki/Economy_of_Second_Life
[TEM] Exchange and Solidarity Network of Magnesia,
"Alternate Monetary Unit"
http://www.tem-magnisia.gr/
[XRP] OpenCoin, Inc. "Ripple open source payment system"
http://ripple.com/
The IFEX Project / ifex-project.org Section 6.2. [Page 14]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
7. Acknowledgments
* Payward, Inc. funded the research and development of this
document.
* The (completely OMC unaffiliated) OpenSimulator project staff were
helpful in clarifiying the origin and status of OMC.
* Valued feedback was provided by the following parties:
Bill McQuillan, OpenCoin Inc.
8. Authors' Addresses
Walter Stanish <walter@stani.sh> Payward, Inc.
On behalf of The Internet Financial EXchange (IFEX) Project:
http://www.ifex-project.org/
The IFEX Project / ifex-project.org Section 8. [Page 15]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
9. Appendix A: Initial Registry Contents
Prior to IANA handover, parties wishing to acquire an identifier may do
so by contacting the IFEX Project via group.ifex-project.org
# X-ISO4217-A3: Unofficial ISO4217 Alpha-3 Extensions Registry.
#
# Version: 20121126-0
# (Format is <yyyy><mm><dd>-<x>, where x is a digit from 0-9)
#
# To be cryptographically signed by IANA and replicated freely.
#
# Format:
# - Lines beginning with '#' are comments.
# - Whitespace should be ignored.
# - Fields at the end of a record may be absent.
#
# Fields:
# registry Registry of origin.
#
# Code Registry Maintenance Agency
# -------------------------------------------
# X X-ISO4217-A3 IANA
# Z ISO4217-A3 SIX Interbank Clearing
#
# a3code Three character code identifying the currency or
# currency-like commodity within a registry.
#
# is_meta Denotes a meta-assignment (not a normal currency).
#
# is_historic Denotes a historic codepoint (obsolete).
#
# name-singular Singular form name of the currency (or primary unit)
#
# e Number of post-decimal digits in normal use.
#
# created Date of registration (YYYY-MM-DD), or blank for
# external registries.
#
# modified Date last modified (YYYY-MM-DD, YYYY-MM or YYYY as
# reflecting accuracy known), or blank for codes
# not yet modified or codes in external registries,
# except in the case of historic codepoints for which
# the field indicates date of withdrawl (if known).
#
# domain Primary domain name associated with the record, or
# blank for no domain or external registries.
The IFEX Project / ifex-project.org Section 9. [Page 16]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
#
# registrant Native language name of the registrant (UTF8), or
# blank for external registries.
X|ACD|0|0|Avination Care Dollar|2|2012-11-13||avination.com|Avination
Virtual Limited
X|BTC|0|0|Bitcoin|8|2012-11-13||bitcoin.org|Bitcoin Community
X|CER|0|0|Kyoto Protocol Certified Emissions Reduction CO2
Tonne|4|2012-11-13|||United Nations Framework Convention on Climate
Change
X|OMC|0|0|Open Metaverse Currency|2|2012-11-13||Open Metaverse Currency
Community
X|PRB|0|0|Transistrian Ruble|0|2012-11-13||cbpmr.net|Trans-Dniester
Republican Bank
X|SLL|0|0|Second Life Linden Dollar|0|2012-11-13||secondlife.com|Linden
Research, Inc.
X|TBC|0|0|Tonal Bitcoin|16|2012-11-26
X|TEM|0|0|Volos Alternative Monetary Unit|0|2012-11-13||tem-
magnesia.gr|Volos Alternative Monetary Unit Community
X|VER|0|0|Non Kyoto Protocol Verified Emissions Reduction CO2
Tonne|4|2012-11-13|||Non Kyoto Protocol Verified Emissions Reduction
Community
X|XRP|0|0|Ripple Credit|6|2012-11-13||ripple.com|OpenCoin Inc.
Z|ADP|0|1|Andorran Peseta|||2003-07
Z|AED|0|0|UAE Dirham|2
Z|AFA|0|1|Afghani|||2003-01
Z|AFN|0|0|Afghani|2
Z|ALK|0|1|Old Lek|||1989-12
Z|ALL|0|0|Lek|2
Z|AMD|0|0|Armenian Dram|2
Z|ANG|0|1|Netherlands Antillean Guilder|||2010-10
Z|AOA|0|0|Kwanza|2
Z|AOK|0|1|Kwanza|||1991-03
Z|AON|0|1|New Kwanza|||2000-02
Z|AOR|0|1|Kwanza Reajustado|||2000-02
Z|ARA|0|1|Austral|||1992-01
Z|ARP|0|1|Peso Argentino|||1985-07
Z|ARS|0|0|Argentine Peso|2
Z|ARY|0|1|Peso|||1990
Z|ATS|0|1|Schilling|||2002-03
Z|AUD|0|0|Australian Dollar|2
Z|AWG|0|0|Aruban Florin|2
Z|AYM|0|1|Azerbaijan Manat|||2005-10
Z|AZM|0|1|Azerbaijanian Manat|||2005-12
Z|AZN|0|0|Azerbaijanian Manat|2
Z|BAD|0|1|Dinar|||1997-07
Z|BAM|0|0|Convertible Mark|2
Z|BBD|0|0|Barbados Dollar|2
Z|BDT|0|0|Taka|2
The IFEX Project / ifex-project.org Section 9. [Page 17]
INTERNET-DRAFT Expires: May 26, 2013 November 2012
Z|BEC|0|1|Convertible Franc|||1990-03
Z|BEF|0|1|Belgian Franc|||2002-03
Z|BEL|0|1|Financial Franc|||1990-03
Z|BGJ|0|1|Lev A/52|||1990
Z|BGK|0|1|Lev A/62|||1990
Z|BGL|0|1|Lev|||2003-11
Z|BGN|0|0|Bulgarian Lev|2
Z|BHD|0|0|Bahraini Dinar|3
Z|BIF|0|0|Burundi Franc|0
Z|BMD|0|0|Bermudian Dollar|2
Z|BND|0|0|Brunei Dollar|2
Z|BOB|0|0|Boliviano|2
Z|BOP|0|1|Peso boliviano|||1987-02
Z|BOV|0|0|Mvdol|2
Z|BRB|0|1|Cruzeiro|||1986-03
Z|BRC|0|1|Cruzado|||1989-02
Z|BRE|0|1|Cruzeiro|||1993-03
Z|BRL|0|0|Brazilian Real|2
Z|BRN|0|1|New Cruzado|||1990-03
Z|BRR|0|1|Cruzeiro Real|||1994-07
Z|BSD|0|0|Bahamian Dollar|2
Z|BTN|0|0|Ngultrum|2
Z|BUK|0|1|N.A.|||1990-02
Z|BWP|0|0|Pula|2
Z|BYB|0|1|Belarussian Ruble|||2001-01
Z|BYR|0|0|Belarussian Ruble|0
Z|BZD|0|0|Belize Dollar|2
Z|CAD|0|0|Canadian Dollar|2
Z|CDF|0|0|Congolese Franc|2
Z|CHC|0|1|WIR Franc (for electronic)|||2004-11
Z|CHE|0|0|WIR Euro|2
Z|CHF|0|0|Swiss Franc|2
Z|CHW|0|0|WIR Franc|2
Z|CLF|0|0|Unidades de fomento|0
Z|CLP|0|0|Chilean Peso|0
Z|CNX|0|1|Peoples Bank Dollar|||1989-12
Z|CNY|0|0|Yuan Renminbi|2
Z|COP|0|0|Colombian Peso|2
Z|COU|0|0|Unidad de Valor Real|2
Z|CRC|0|0|Costa Rican Colon|2
Z|CSD|0|1|Serbian Dinar|||2006-10
Z|CSJ|0|1|Krona A/53|||1990
Z|CSK|0|1|Koruna|||1993-03
Z|CUC|0|0|Peso Convertible|2
Z|CUP|0|0|Cuban Peso|2
Z|CVE|0|0|Cape Verde Escudo|2
Z|CYP|0|1|Cyprus Pound|||2008-01
Z|CZK|0|0|Czech Koruna|2
The IFEX Project / ifex-project.org Section 9. [Page 18]