[governance] Re: Fully Internationalized-Canonical-Order IDNs

[yehudakatz at mailinator.com]

Hello Subbiah,

1.
Could you please tell me if you are aware of an RFC or Other Proposal for the
Conical Name Order ‘EXTENTIONS” for iDNS or Other Formats?  [m17n, i18n, L10n
or other basis/ e.g.: Internationalization Tag Set (ITS)]. 

I am looking for a List similar to:
  Country Codes from ISO 3166
    http://www.freesoft.org/CIE/RFC/1700/39.htm

Only my list would have the ‘Conical Internationalized Extension’
Like this :( A list of transliterations of: .Com/.Net/.Org - equivalents)

Expl.: Big5, CJK, English, etc.  Iterations
Conical Internationalized Extension’ Language/Country			       
	      
Country 					A 2	A 3	Number
----------------------------------------------------------------------
.COM = 
CHINA						造字   
造字?    156
HONG KONG				    ??	    ???     344
JAPAN						日本    
日本?   392
KOREA, DEM PEOPLE'S Rep OF	  ??	  ???	  408
KOREA, REPUBLIC OF		       ??      ???     410
SINGAPORE				    ??	    ???     702
UNITED STATES				  N/A	  COM	  840

--

.NET = 
CHINA						造字   
造字?    156
HONG KONG				   ??	   ???	   344
JAPAN						日本   
日本?    392
KOREA, DEM PEOPLE'S Rep OF	  ??	  ???	  408
KOREA, REPUBLIC OF		       ??      ???     410
SINGAPORE				    ??	    ???     702
UNITED STATES				  N/A	  NET	  840

--

.ORG = 
CHINA						造字    
造字?   156
HONG KONG				   ??	   ???	   344
JAPAN						日本   
日本?    392
KOREA, DEM PEOPLE'S Rep OF	  ??	  ???	  408
KOREA, REPUBLIC OF		       ??      ???     410
SINGAPORE				    ??	    ???     702
UNITED STATES				  N/A	  ORG	  840

----------------------------------------------------------------------
--

2.

Is a fundamental-problem, getting a fully internationalized-canonical-order IDN
to work with DNSSEC ?
--
Ref.: http://www.faqs.org/rfcs/rfc2535.html
RFC 2535		DNS Security Extensions 	      March 1999
…
8.2 Canonical DNS Name Order

   For purposes of DNS security, the canonical ordering of owner names
   is to sort individual labels as unsigned left justified octet strings
   where the absence of a octet sorts before a zero value octet and
   upper case letters are treated as lower case letters.  Names in a
   zone are sorted by sorting on the highest level label and then,
   within those names with the same highest level label by the next
   lower label, etc. down to leaf node labels.	Within a zone, the zone
   name itself always exists and all other names are the zone name with
   some prefix of lower level labels.  Thus the zone name itself always
   sorts first.

   Example:
	  foo.example
	  a.foo.example
	  yljkjljk.a.foo.example
	  Z.a.foo.example
	  zABC.a.FOO.EXAMPLE
	  z.foo.example
	  *.z.foo.example
	  \200.z.foo.example

8.3 Canonical RR Ordering Within An RRset

   Within any particular owner name and type, RRs are sorted by RDATA as
   a left justified unsigned octet sequence where the absence of an   octet
sorts before the zero octet.

8.4 Canonical Ordering of RR Types

   When RRs of the same name but different types must be ordered, they
   are ordered by type, considering the type to be an unsigned integer,
   except that SIG RRs are placed immediately after the type they cover.
   Thus, for example, an A record would be put before an MX record
   because A is type 1 and MX is type 15 but if both were signed, the
   order would be A < SIG(A) < MX < SIG(MX).

--
End
____________________________________________________________
You received this message as a subscriber on the list:
     governance at lists.cpsr.org
To be removed from the list, send any message to:
     governance-unsubscribe at lists.cpsr.org

For all list information and functions, see:
     http://lists.cpsr.org/lists/info/governance