draft-ietf-idn-aceid-00.txt   draft-ietf-idn-aceid-01.txt 
Internet Draft Naomasa Maruyama Internet Draft Naomasa Maruyama
draft-ietf-idn-aceid-00.txt Yoshiro Yoneya draft-ietf-idn-aceid-01.txt Yoshiro Yoneya
November 17, 2000 JPNIC Dec 11, 2000 JPNIC
Expires May 17, 2001 Expires June 11, 2001
Proposal for a determining process of ACE identifier Proposal for a determining process of ACE identifier
Status of this memo Status of this memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other Force (IETF), its areas, and its working groups. Note that other
skipping to change at line 75 skipping to change at line 75
In order to maintain a smooth standardization process for ACE, In order to maintain a smooth standardization process for ACE,
this document proposes a strategy for selecting and reserving of ACE this document proposes a strategy for selecting and reserving of ACE
identifiers and a method for assigning them. identifiers and a method for assigning them.
2.1 The ACE identifier candidates and tentative suspension of 2.1 The ACE identifier candidates and tentative suspension of
registering relevant domain names registering relevant domain names
All strings starting with a combination of two alpha-numericals, All strings starting with a combination of two alpha-numericals,
followed by two hyphens, are defined to be ACE prefix identifier followed by two hyphens, are defined to be ACE prefix identifier
candidates. All strings starting with one hyphen followed by three candidates. All strings starting with two hyphens followed by two
alpha-numericals, and strings starting with two hyphens followed by alpha-numericals are defined as ACE suffix identifier candidates. ACE
two alpha-numericals are defined as ACE suffix identifier candidates. prefix identifier candidates and ACE suffix identifier candidates are
ACE prefix identifier candidates and ACE suffix identifier candidates collectively called ACE identifier candidates.
are collectively called ACE identifier candidates.
All the domain name registries recognized by ICANN SHOULD All the domain name registries recognized by ICANN SHOULD
tentatively suspend registration of domain names which have an ACE tentatively suspend registration of domain names which have an ACE
prefix identifier candidate at the heads of one of the labels of the prefix identifier candidate at the head of at least one label of the
domain name and those which have an ACE suffix identifier candidate at domain name and those which have an ACE suffix identifier candidate at
the tail of one of the labels of the name. These domain names are the tail of at least one label of the name. These domain names are
collectively called "relevant domain names". collectively called "relevant domain names".
This suspension should be continued until March 1, 2001 00:00:00 UTC. This suspension should be continued until March 1, 2001 00:00:00 UTC.
2.2 Survey of relevant domain name registration 2.2 Survey of relevant domain name registration
All registries recognized by ICANN SHOULD conduct a survey about All registries recognized by ICANN SHOULD conduct a survey about
relevant domain names registered in their zone, and report, no later relevant domain names registered in their zone, and report, no later
than February 10, 2001 00:00:00 UTC, all of the ACE identifier than February 10, 2001 00:00:00 UTC, all of the ACE identifier
candidates which are used by relevant domain names. candidates which are used by relevant domain names.
2.3 Selection of ACE identifiers and permanent blocking of 2.3 Selection of ACE identifiers and permanent blocking of
relevant domain names relevant domain names
The IDN WG MUST summarize the reports and list ACE identifier The IDN WG or other organ of IETF or ICANN MUST summarize the
candidates that are not reported to be used in registered domain names reports and list ACE identifier candidates that are not reported to be
by February 17, 2001 00:00:00 UTC, and select ten to twenty ACE prefix used in registered domain names by February 17, 2001 00:00:00 UTC, and
identifier candidates and ten to twenty ACE suffix identifier select ten to twenty ACE prefix identifier candidates and ten to
candidates for ACE identifiers. Among these twenty to forty ACE twenty ACE suffix identifier candidates for ACE identifiers. Among
identifiers, one prefix identifier and one suffix identifier will be these twenty to forty ACE identifiers, one prefix identifier and one
used for experiments. Others will be used, one by one as ACE standard suffix identifier will be used for experiments. Others will be used,
evolves. one by one as ACE standard evolves.
The list of ACE identifiers will be sent to IANA, and will be The list of ACE identifiers will be sent to IANA, and will be
maintained by IANA from February 24, 2001 00:00:00 UTC. Domain names maintained by IANA from February 24, 2001 00:00:00 UTC. Domain names
relevant to these identifiers SHOULD NOT be registered in any DNS relevant to these identifiers SHOULD NOT be registered in any DNS
zone, except for registration of multilingual domain names compliant zone, except for registration of multilingual domain names compliant
to one of future IDN standards. This new restriction about the domain to one of future IDN standards. This new restriction about the domain
name space will be notified to all ICANN recognized registries by IANA name space will be notified to all ICANN recognized registries by IANA
immediately after it receives the list. immediately after it receives the list.
2.4 Blocking of registration for relevant domain names 2.4 Blocking of registration for relevant domain names
skipping to change at line 156 skipping to change at line 155
When an Internet Draft relating to ACE is accepted as an Internet When an Internet Draft relating to ACE is accepted as an Internet
standard and becomes an RFC, IDN WG or other organ of IETF or ICANN standard and becomes an RFC, IDN WG or other organ of IETF or ICANN
MUST replace the experimental ACE identifier, augmented by the version MUST replace the experimental ACE identifier, augmented by the version
number, with one of the ACE identifiers. number, with one of the ACE identifiers.
5. Security considerations 5. Security considerations
None in particular. None in particular.
6. References 6. Changes from the previous version
We excluded suffixes of one hyphen followed by three alpha-
numericals from the candidates. This is because we found that, as of
Nov. 29, 2000, there were 23,921 domain names registered in the .JP
space relevant to these suffixes. This was more than 10% of 227,852
total registrations in the JPNIC database at the moment, and hence we
felt these suffixes are not good candidates.
In addition to this and some minor linguistic corrections, we
changed "The IDN WG" in section 2.3 to "The IDN WG or other organ of
IETF or ICANN".
7. References
[IDNREQ] Z Wenzel, J Seng, "Requirements of Internationalized Domain [IDNREQ] Z Wenzel, J Seng, "Requirements of Internationalized Domain
Names", draft-ietf-idn-requirements-03.txt, Jun 2000. Names", draft-ietf-idn-requirements-03.txt, Jun 2000.
[RACE] P Hoffman, "RACE: Row-based ASCII Compatible Encoding for [RACE] P Hoffman, "RACE: Row-based ASCII Compatible Encoding for
IDN", draft-ietf-idn-race-02.txt, Oct 2000. IDN", draft-ietf-idn-race-02.txt, Oct 2000.
[BRACE] A Costello, "BRACE: Bi-mode Row-based ASCII-Compatible [BRACE] A Costello, "BRACE: Bi-mode Row-based ASCII-Compatible
Encoding for IDN", draft-ietf-idn-brace-00.txt, Sep 2000. Encoding for IDN", draft-ietf-idn-brace-00.txt, Sep 2000.
[LACE] P Hoffman, "LACE: Length-based ASCII Compatible Encoding for [LACE] P Hoffman, "LACE: Length-based ASCII Compatible Encoding for
IDN", draft-ietf-idn-lace-00.txt, Nov 2000. IDN", draft-ietf-idn-lace-00.txt, Nov 2000.
[VERSION] M Blanchet, "Handling versions of internationalized domain [VERSION] M Blanchet, "Handling versions of internationalized domain
names protocols", draft-ietf-idn-version-00.txt, Nov 2000. names protocols", draft-ietf-idn-version-00.txt, Nov 2000.
7. Acknowledgements 8. Acknowledgements
JPNIC IDN-TF members, We would like to express our hearty thanks to members of JPNIC IDN
Dave Crocker. Task Force for valuable discussions about this issue. We also would
like to express our appreciation to Mr. Dave Crocker for checking and
correcting the preliminary version of this draft.
8. Author's Address 9. Author's Address
Naomasa Maruyama Naomasa Maruyama
Japan Network Information Center Japan Network Information Center
Fuundo Bldg 1F, 1-2 Kanda-ogawamachi Fuundo Bldg 1F, 1-2 Kanda-ogawamachi
Chiyoda-ku Tokyo 101-0052, Japan Chiyoda-ku Tokyo 101-0052, Japan
maruyama@nic.ad.jp maruyama@nic.ad.jp
Yoshiro Yoneya Yoshiro Yoneya
Japan Network Information Center Japan Network Information Center
Fuundo Bldg 1F, 1-2 Kanda-ogawamachi Fuundo Bldg 1F, 1-2 Kanda-ogawamachi
 End of changes. 9 change blocks. 
23 lines changed or deleted 37 lines changed or added

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