[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: IETF Country Codes
"copyright on the use" is a funny phrase. Aren't copyrights supposed to be
on copying and patents on "use"? :-)
Anyway, the country code list is all over the Internet on a zillion web
pages and has been for many years. The correspondence
that has been posted with ISO indicates they have no problem with this
or any non-profit use. They are saying they may impose royalties
on incorporation of the standard, which right now seems to mean more than
just the codes, into for-profit products. For example, there
is this message saying that the royalty would apply if the vendor
incorporated the standard into their product but not if they instructed
uses to download and insert it! (See for example
http://www.ncits.org/archive/2003/in030463/in030463.htm)
My draft would certainly be improved by the insertion of the usual IETF
IPR disclaimer boilerplate. If my draft is a derivative work, it is
non-profit and seems to be in an area where ISO has given permission for
copying and said it would not apply royalties, assuming it is legally
entitled to.
Part of the idea of the draft is to freeze things so they can't get worse.
I don't think ISO could get away with revoking the permissions it has
issued so far on the standard to date but could impose arbitrary restrictions
on versions with future changes in them. (Just like the random people that own
the Dewey Decimal system succeed in extracting royalties to use the up-to-date
augmented version even though copyright long ago expired on earlier versions.)
Since future changes to the IETF Country Codes would be through IETF
mechanisms, they would not be affected by ISO restrictions on its future
changes to its two-letter country code list.
Donald
-----Original Message-----
From: Michael StJohns [mailto:mstjohns@mindspring.com]
Sent: Monday, 22 September, 2003 4:51 PM
To: Eastlake III Donald-LDE008; iab@iab.org; iesg@ietf.org
Cc: Eastlake III Donald-LDE008; dee3@torque.pothole.com
Subject: Re: IETF Country Codes
I hate to say this but... copyright? I'm not sure.... scratch that.. I'm
pretty sure that ISO holds a copyright on the use of the codes and
including them in a list as you have with the express purpose of making
their list valueless in the context of the internet will probably land
you/we in copyright hot water.
I think there are ways around it - but this is probably one for the ICANN
lawyers...
*sigh*
Mike
At 15:13 9/22/2003, Donald E Eastlake 3rd wrote:
>So I wrote the attached draft. I was originally going to
>include Language Codes but there are significantly more
>complex and would probably best be handled in a separate
>document.
>
>Any thoughts on whether I should submit this (keeping in
>mind that anyone could submit a similar draft at any time...)
>
>Thanks,
>Donald
>
>PS: My office is moving this Thursday so it may be hard to
>contact me at "work" that day. After Friday I believe my
>work phone will be 1-508-786-7554.
>
>============================================================
> Donald E. Eastlake 3rd Donald.Eastlake@motorola.com
> 155 Beaver Street +1 588-851-8280(w) +1 508-634-2066(h)
> Milford, MA 01757 USA dee3@torque.pothole.com
>INTERNET-DRAFT Donald E. Eastlake 3rd
> Motorola Laboratories
>Expires: February 2004 September 2003
>
>
>
> IETF Country Codes
> ---- ------- -----
> <draft-eastlake-ietf-codes-00.txt>
>
>
>
>Status of This Document
>
> Distribution of this draft is unlimited. Comments should be sent to
> the author. It is intended to become a special Best Current Practice
> amending all existing IETF Standards and Best Current Practices to
> which it applies.
>
> This document is an Internet Draft and is in full conformance with
> all provisions of Section 10 of RFC 2026. Internet Drafts are
> working documents of the Internet Engineering Task Force (IETF), its
> areas, and its working groups. Note that other groups may also
> distribute working documents as Internet Drafts.
>
> 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 list of current Internet-Drafts can be accessed at
> http://www.ietf.org/ietf/1id-abstracts.txt
>
> The list of Internet-Draft Shadow Directories can be accessed at
> http://www.ietf.org/shadow.html.
>
>
>
>Copyright Notice
>
> Copyright (C) The Internet Society (2003). All Rights Reserved.
>
>
>
>Abstract
>
> To protect IETF protocols that use codes similar to ISO Country Codes
> from the potential burden of royalties and the burdensome
> uncertainties of the possible arbitrary imposition of and changes in
> such royalties, IETF Country Codes are hereby adopted.
>
>
>
>
>
>D. Eastlake 3rd [Page 1]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
>Table of Contents
>
> [Table of Contents gets moved here from the end]
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>D. Eastlake 3rd [Page 2]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
>1. Introduction and Effect
>
> The International Standards Organization has threatened to enforce
> unspecified royalties for the use of ISO Country Codes. Even if they
> do not take this step, their action has imposed enormous uncertainty
> on the users of any protocol based on these codes because such
> royalties could be imposed at any time. IETF Standards that are
> currently defined with reference to these codes include the global
> DNS [RFC 1034, 1035, 1591] and IETF language tags [RFC 3066] and any
> Standards, IETF or otherwise, that depend on these such as URIs [RFC
> 2396], HTTP [RFC 2616], and XML [XML].
>
> The approval of this special Best Current Practice document by the
> IESG shall direct that, in all existing IETF Standards and Best
> Current Practices, including those approved by the IESG but not yet
> published, all references to ISO Country Codes shall hereby be
> interpreted to refer only to IETF Country Codes unless the reference
> is in the nature of historic or commentary without normative effect.
>
> The IETF warrants that it will never charge royalties for the use of
> IETF Country Codes and invites other oranizations to make reference
> to them.
>
>
>
>2. Country Codes
>
> The initial table of IETF County Codes is as follows. (It is
> different from the ISO table of two letter country codes in that it
> contains additional allocated codes (ac, gg, im, and je) and, because
> of the IETF dedication to stability and interoperability, it
> maintains the country code of the United Kingdom as "uk" and that of
> Serbia and Montenegro (Yugloslavia) as "yu", the codes currently in
> use.)
>
> ac Ascension Island
> ad Andorra
> ae United Arab Emirates
> af Afghanistan
> ag Antigua and Barbuda
> ai Anguilla
> al Albania
> am Armenia
> an Netherlands Antilles
> ao Angola
> aq Antarctica
> ar Argentina
> as American Samoa
> at Austria
> au Australia
>
>
>D. Eastlake 3rd [Page 3]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
> aw Aruba
> az Azerbaijan
> ba Bosnia and Herzegovina
> bb Barbados
> bd Bangladesh
> be Belgium
> bf Burkina Faso
> bg Bulgaria
> bh Bahrain
> bi Burundi
> bj Benin
> bm Bermuda
> bn Brunei Darussalam
> bo Bolivia
> br Brazil
> bs Bahamas
> bt Bhutan
> bv Bouvet Island
> bw Botswana
> by Belarus
> bz Belize
> ca Canada
> cc Cocos (Keeling) Islands
> cd Democratic Republic of the Congo
> cf Central African Republic
> cg Republic of Congo
> ch Switzerland
> ci Cote D'Ivoire
> ck Cook Islands
> cl Chile
> cm Cameroon
> cn China
> co Colombia
> cr Costa Rica
> cs Checkoslovakia
> cu Cuba
> cv Cape Verde
> cx Christmas Island
> cy Cyprus
> cz Czech Republic
> de Germany
> dj Djibouti
> dk Denmark
> dm Dominica
> do Dominican Republic
> dz Algeria
> ec Ecuador
> ee Estonia
> eg Egypt
> eh Western Sahara
>
>
>D. Eastlake 3rd [Page 4]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
> er Eritrea
> es Spain
> et Ethiopia
> fi Finland
> fj Fiji
> fk Falkland Islands (Malvinas)
> fm Federated States of Micronesia
> fo Faroe Islands
> fr France
> ga Gabon
> gd Grenada
> ge Georgia
> gf French Guiana
> gg Guernsey
> gh Ghana
> gi Gibraltar
> gl Greenland
> gm Gambia
> gn Guinea
> gp Guadeloupe
> gq Equatorial Guinea
> gr Greece
> gs South Georgia and The South Sandwich Islands
> gt Guatemala
> gu Guam
> gw Guinea-Bissau
> gy Guyana
> hk Hong Kong
> hm Heard Island and Mcdonald Islands
> hn Honduras
> hr Croatia
> ht Haiti
> hu Hungary
> id Indonesia
> ie Ireland
> il Israel
> im Isle of Man
> in India
> io British Indian Ocean Territory
> iq Iraq
> ir Islamic Republic of Iran
> is Iceland
> it Italy
> je Jersey
> jm Jamaica
> jo Jordan
> jp Japan
> ke Kenya
> kg Kyrgyzstan
> kh Cambodia
>
>
>D. Eastlake 3rd [Page 5]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
> ki Kiribati
> km Comoros
> kn Saint Kitts and Nevis
> kp Democratic People's Republic of Korea
> kr Republic of Korea
> kw Kuwait
> ky Cayman Islands
> kz Kazakhstan
> la Lao People's Democratic Republic
> lb Lebanon
> lc Saint Lucia
> li Liechtenstein
> lk Sri Lanka
> lr Liberia
> ls Lesotho
> lt Lithuania
> lu Luxembourg
> lv Latvia
> ly Libyan Arab Jamahiriya
> ma Morocco
> mc Monaco
> md Republic of Moldova
> mg Madagascar
> mh Marshall Islands
> mk Former Yugoslav Republic of Macedonia
> ml Mali
> mm Myanmar
> mn Mongolia
> mo Macau
> mp Northern Mariana Islands
> mq Martinique
> mr Mauritania
> ms Montserrat
> mt Malta
> mu Mauritius
> mv Maldives
> mw Malawi
> mx Mexico
> my Malaysia
> mz Mozambique
> na Namibia
> nc New Caledonia
> ne Niger
> nf Norfolk Island
> ng Nigeria
> ni Nicaragua
> nl Netherlands
> no Norway
> np Nepal
> nr Nauru
>
>
>D. Eastlake 3rd [Page 6]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
> nu Niue
> nz New Zealand
> om Oman
> pa Panama
> pe Peru
> pf French Polynesia
> pg Papua New Guinea
> ph Philippines
> pk Pakistan
> pl Poland
> pm Saint Pierre and Miquelon
> pn Pitcairn
> pr Puerto Rico
> ps Occupied Palestinian Territory
> pt Portugal
> pw Palau
> py Paraguay
> qa Qatar
> re Reunion Island
> ro Romania
> ru Russian Federation
> rw Rwanda
> sa Saudi Arabia
> sb Solomon Islands
> sc Seychelles
> sd Sudan
> se Sweden
> sg Singapore
> sh Saint Helena
> si Slovenia
> sj Svalbard and Jan Mayen Islands
> sk Slovak Republic
> sl Sierra Leone
> sm San Marino
> sn Senegal
> so Somalia
> sr Suriname
> st Sao Tome and Principe
> sv El Salvador
> sy Syrian Arab Republic
> sz Swaziland
> tc Turks and Caicos Islands
> td Chad
> tf French Southern Territories
> tg Togo
> th Thailand
> tj Tajikistan
> tk Tokelau
> tl Timor-Leste
> tm Turkmenistan
>
>
>D. Eastlake 3rd [Page 7]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
> tn Tunisia
> to Tonga
> tr Turkey
> tt Trinidad and Tobago
> tv Tuvalu
> tw Taiwan
> tz Tanzania
> ua Ukraine
> ug Uganda
> uk United Kingdom
> um USA Minor Outlying Islands
> us United States of America
> uy Uruguay
> uz Uzbekistan
> va Vatican City
> vc Saint Vincent and The Grenadines
> ve Venezuela
> vg British Virgin Islands
> vi USA Virgin Islands
> vn Viet Nam
> vu Vanuatu
> wf Wallis and Futuna Islands
> ws Western Samoa
> ye Yemen
> yt Mayotte
> yu Serbia and Montenegro (Yugloslavia)
> za South Africa
> zm Zambia
> zw Zimbabwe
>
>
>
>3. IANA Considerations
>
> IANA will maintain the IETF Country Codes registry consisting of two
> case insenstitive [ASCII] letters the first of which is not "X". All
> IETF Country Codes starting with "X" are reserved for local use.
>
> (Note: should all available two letter pairs be allocated, it may
> become necessary to allow ASCII digits in IETF Country Codes. Code
> which processes IETF Country Codes should allow for this
> possibility.)
>
> New two letter codes will be allocated based on either (1) a decision
> of the IESG or (2) the issuance by the United Nations of a new United
> Nations Country Number. In the first case, the IESG will specify the
> code. In the second case, the code desired by the apparent UN
> recognized authority in the area for which the UN Country Number was
> issued will normally choose the code; however, if they fail to
> designate an unsed code within a reasonable length of time, IANA will
>
>
>D. Eastlake 3rd [Page 8]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
> select a code at random for the available two letter codes using a
> procedure such as that described in [RFC 2777].
>
> IETF Country Codes will be de-allocated only by a decision of the
> IESG.
>
>
>
>4. Security Considerations
>
> There are not believed to be any substantial security effects from
> this document. It may improve security by increasing the stability
> of country codes used in IETF protocols and it may reduce security
> due to any confusion caused by divergence between IETF Country Codes,
> ISO Country Codes, and other Country Codes; however, such confusion
> may already exist in, for example, DNS top level country code domains
> which have not changed despite ISO Country Code changes.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>D. Eastlake 3rd [Page 9]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
>Normative References
>
> [ASCII] - "USA Standard Code for Information Interchange", X3.4
> American National Standards institute: New York, 1968.
>
> [RFC 2777] - "Publicly Verifiable Nomcom Random Selection", D.
> Eastlake 3rd, February 2000.
>
>
>
>Informative References
>
> [ISO 3166-1] - "Codes for the Representation of Names of Countries
> and Their Subdivisions - Part 1: Country Codes", ISO, 1997.
>
> [RFC 1034] - "Domain Names - Concepts and Facilities", P.
> Mockapetris, STD 13, November 1987.
>
> [RFC 1035] - "Domain Names - Implementation and Specifications", P.
> Mockapetris, STD 13, November 1987.
>
> [RFC 1591] - "Domain Name System Structure and Delegation", J.
> Postel, March 1994.
>
> [RFC 2396] - "Uniform Resource Identifiers (URI): Generic Syntax", T.
> Berners-Lee, R. Fielding, and L. Masinter, August 1998.
>
> [RFC 2616] - "Hypertext Transfer Protocol -- HTTP/1.1", R. Fielding,
> J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-
> Lee, June 1999.
>
> [RFC 3066] - "Tags for the Identification of Languages", H.
> Alvestrand, January 2001.
>
> [XML] - "Extensible Mark Up Language (XML) 1.0 (Second Edition)", T.
> Bray, J. Paoli, C. M Sperberg-McQueen, E. Maler, February 1998.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>D. Eastlake 3rd [Page 10]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
>Author's Address
>
> Donald E. Eastlake 3rd
> 155 Beaver Street
> Milford, MA 01757 USA
>
> Telephone: +1-508-634-2066 (h)
> EMail: Donald.Eastlake@motorola.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>D. Eastlake 3rd [Page 11]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
>Full Copyright Statement
>
> Copyright (C) The Internet Society (2003). All Rights Reserved.
>
> This document and translations of it may be copied and furnished to
> others, and derivative works that comment on or otherwise explain it
> or assist in its implementation may be prepared, copied, published
> and distributed, in whole or in part, without restriction of any
> kind, provided that the above copyright notice and this paragraph are
> included on all such copies and derivative works. However, this
> document itself may not be modified in any way, such as by removing
> the copyright notice or references to the Internet Society or other
> Internet organizations, except as needed for the purpose of
> developing Internet standards in which case the procedures for
> copyrights defined in the Internet Standards process must be
> followed, or as required to translate it into languages other than
> English.
>
> The limited permissions granted above are perpetual and will not be
> revoked by the Internet Society or its successors or assigns.
>
> This document and the information contained herein is provided on an
> "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
> TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
> BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
> HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
> MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>
>
>
>Expiration and File Name
>
> This draft expires February 2004.
>
> Its file name is draft-eastlake-ietf-codes-00.txt.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>D. Eastlake 3rd [Page 12]
>*
>
>INTERNET-DRAFT IETF Country Codes September 2003
>
>
> Status of This Document....................................1
> Copyright Notice...........................................1
> Abstract...................................................1
>
> Table of Contents..........................................2
>
> 1. Introduction and Effect.................................3 2.
> Country Codes...........................................3 3. IANA
> Considerations.....................................8 4. Security
> Considerations.................................9
>
> Normative References......................................10
> Informative References....................................10
>
> Author's Address..........................................11
>
> Full Copyright Statement..................................12
> Expiration and File Name..................................12
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>D. Eastlake 3rd [Page 13]
>*