[idn] SC/TC equivalence

[David Hopwood <david.hopwood@zetnet.co.uk>]

-----BEGIN PGP SIGNED MESSAGE-----

Edmon wrote:
> From: "Eric Brunner-Williams in Portland Maine" <brunner@nic-naa.net>
> > What is the key value for users "opting out" of SC/TC equivalences?
> 
> There are two main scenarios that I could think of that I would like to see
> SC/TC opted out.
> Say I wanted to have different online identities in the PRC, HongKong and
> Taiwan with two Chinese charcters.  And I want to use:
> <SC><SC> in PRC
> <SC><TC> in HK and
> <TC><TC> in Taiwan

Unless I'm missing something, SC/TC equivalence doesn't affect the protocol;
it's purely a local issue for administrators of zones that include names
with Chinese characters. They could configure the authoritative servers for
those zones to use any of the following approaches:

1. have zone entries for each combination.
2. have zone entries only for folded names, and do folding in the server.
3. have the server try to match the unfolded name first, and if not found,
   try to match the folded name.

Intermediate servers will cache the variants that are actually used (which
is probably only a small subset of the possible variants).

So the WG doesn't need to decide this, apart from pointing out the options.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO3EfjDkCAxeYt5gVAQEiwwf/ZD4a7sFKXRaePXRImGOlZM8NRu32CCty
X8D2uEtyo1ZATDjUXK71Um92wiOLHOp6m2DwZbXzT8YT6mt/8pnDdfQs5iug218D
Byi137qwBXDrwPKv1mKqAXsC9dSHBGZly1w7Mmwg+ugJ7vuv0pqwmSHIy+UoCTnP
vU010nVfqj5c/kt7cH6Gkt2Tan5uoii1WpZRRj0tXYezuqsTKC/f5D4GFWtvdzAN
iTyMlI4lM3znZOCI1vwfxOPgBU4ONHugvrrjv72pTrDbt3qrivpgndvcFI4Mo4El
bsHGqumZhRq5qMC8vSF9tJDKtJJMOoTY831yQJprdyASVKNvEKItkw==
=u31z
-----END PGP SIGNATURE-----