draft-ietf-idn-iptr-02.txt

bind-3.2.

       53(decimal). This behavior is consistent with the current DNS
       specification [RFC1035].


     - In future, EDNS0 is REQUIRED to send large packets.

       Then, before a client send a query to ask for IPTR record, it
       MUST query the server whether it knows the EDNS0 first. If the
       server knows EDNS0, then the client MAY send the IPTR query.
       Else, unfortunally, the client MUST change the QTYPE to PTR.

       Hence, the size of the UDP payload is no longer limited to 512
       octets any more.

6.2 Standard sample

     A resolver who wants to find the IDNs corresponding to an IP
     address 1.2.3.4 whould pursue a query of the form QTYPE=IPTR,
     QCLASS=IN, QNAME=4.3.2.1.IN-ADDR.ARPA, and would receive:







Shi, Jiang                                                      [Page 5]





INTERNET-DRAFT   Internationalized PTR Resource Record       17 May 2001



                 +------------------------------------------------------+
      Header     | OPCODE=SQUERY, RESPONSE, AA                          |
                 +------------------------------------------------------+
      Question   | QNAME=4.3.2.1.IN-ADDR.ARPA.,QCLASS=IN,QTYPE=IPTR     |
                 +------------------------------------------------------+
      Answer     | 4.3.2.1.IN-ADDR.ARPA. IPTR  "zh-CN" "name1-in-utf8"  |
                 | 4.3.2.1.IN-ADDR.ARPA. IPTR  "zh-TW" "name2-in-utf8"  |
                 | 4.3.2.1.IN-ADDR.ARPA. IPTR  "zh-JP" "name3-in-utf8"  |
                 | 4.3.2.1.IN-ADDR.ARPA. IPTR  "ko-KR" "name4-in-utf8"  |
                 +------------------------------------------------------+
      Authority  | ...                                                  |
                 +------------------------------------------------------+
      Additional | ...                                                  |
                 +------------------------------------------------------+


7. IPTR Usage

     The "foo1.example" in following samples MAY or MAY NOT be
     represented in the same characters.

     4.3.2.1.IN-ADDR.ARPA  IPTR  "zh-TW" "[foo1.example] in utf8"
                           IPTR  "zh-CN" "[foo1.example] in utf8"
                           IPTR  "ja-JP" "[foo1.example] in utf8"
                           IPTR  "ko-KR" "[foo1.example] in utf8"

     Moreover,

     4.3.2.1.IN-ADDR.ARPA  IPTR  "zh-TW" "[foo1.example] in utf8"
                           IPTR  "zh-TW" "[foo2.example] in utf8"
                           ...
                           IPTR  "zh-CN" "[foo1.example] in utf8"
                           IPTR  "zh-CN" "[foo2.example] in utf8"
                           ...
                           IPTR  "ja-JP" "[foo1.example] in utf8"
                           IPTR  "ja-JP" "[foo2.example] in utf8"
                           ...
                           IPTR  "ko-KR" "[foo1.example] in utf8"
                           IPTR  "ko-KR" "[foo2.example] in utf8"
                           ...

     will exist also. And "foo2.example" MUST be different from
     "foo1.example", if they are in signed with same LANGUAGE. Or a
     "Syntax Error" SHOULD be sent back, when an administrator config-
     ures the zone files. Furthermore "foo2.example" in the samples
     above MAY or MAY NOT be represented in the same characters.




Shi, Jiang                                                      [Page 6]





INTERNET-DRAFT   Internationalized PTR Resource Record       17 May 2001


     Thus,

     4.3.2.1.IN-ADDR.ARPA  IPTR "zh-TW" "[samefoo.sample] in utf8"
                           IPTR "zh-TW" "[samefoo.sample] in utf8"

     occurs a "Syntax Error".

     And,

     4.3.2.1.IN-ADDR.ARPA  IPTR "zh-TW" "[samefoo.sample] in utf8"
                           IPTR "zh-TW" "[difffoo.sample] in utf8"
                           IPTR "zh-CN" "[samefoo.sample] in utf8"
                           IPTR "ja-JP" "[samefoo.sample] in utf8"
                           IPTR "ko-KR" "[samefoo.sample] in utf8"

     is allowed.

8. Changes

     Through the discussion on the IETF49 meeting in San Diego, we
     deleted the chapter "Open Issues" of our previous draft (version
     01).

     And,

     4.3.2.1.IN-ADDR.ARPA  IPTR "zh-TW" "[samefoo.sample] in utf8"
                           IPTR "zh-TW" "[difffoo.sample] in utf8"
                           IPTR "zh-CN" "[samefoo.sample] in utf8"
                           IPTR "ja-JP" "[samefoo.sample] in utf8"
                           IPTR "ko-KR" "[samefoo.sample] in utf8"

     is allowed.

8. Changes

     Through the discussion on the IETF49 meeting in San Diego, we
     deleted the chapter "Open Issues" of our previous draft (version
     01).

References

     [IDNREQ] Zita Wenzel & James Seng, "Requirements of International-
     ized Domain Names", draft-ietf-idn-requirements.

     [IDNE] Marc Blanchet & Paul Hoffman, "Internationalized domain
     names using EDNS", draft-ietf-idn-idne.

     [NAMEPREP] Paul Hoffman & Marc Blanchet, "Preparation of



Shi, Jiang                                                      [Page 7]





INTERNET-DRAFT   Internationalized PTR Resource Record       17 May 2001


     Internationalized Host Names", draft-ietf-idn-nameprep.

     [RFC1034] P. Mockapetris, "DOMAIN NAMES - CONCEPTS AND FACILITIES",
     November 1987, RFC1034

     [RFC1035] P. Mockapetris, "DOMAIN NAMES - IMPLEMENTATION AND
     SPECIFICATION", November 1987, RFC1035

     [RFC1766] H. Alvestrand, "Tags for the Identification of
     Languages", March 1999, RFC 1766

     [RFC1886] S. Thomson, C. Huitema, "DNS Extensions to support IP
     version 6", December 1995, RFC1886

     [RFC2181] R. Elz, R. Bush, "Clarifications to the DNS Specifica-
     tion", July 1997, RFC2181

     [RFC2279] Francois Yergeau, "UTF-8, a transformation format of ISO
     10646", January 1998, RFC 2279.

     [RFC2671] Paul Vixie, "Extension Mechanisms for DNS (EDNS0)",
     August 1999, RFC 2671.

     [ISO 639] ISO 639:1988 (E/F) - Code for the representation of names
     of languages - The International Organization for Standardization,
     1st edition, 1988 17 pages Prepared by ISO/TC 37 - Terminology
     (principles and coordination).

     [ISO 3166] ISO 3166:1988 (E/F) - Codes for the representation of
     names of countries - The International Organization for Standardi-
     zation, 3rd edition, 1988-08-15.

Acknowledgements

     James Seng and Yoshiro Yoneya have given many comments in our e-
     mail discussions. Harald Alvestrand, Mark Davis have given many
     suggestions in the idn-wg mailing list discussions. And there are
     also a lot of people who have given us their comments in the idn-wg
     and BIND-user mailing list discussions.

Authors' Information

     Hongbo Shi
     Waseda University
     3-4-1 Okubo, Shinjyuku-ku
     Tokyo, 169-8555 Japan
     [e-mail]




Shi, Jiang                                                      [Page 8]





INTERNET-DRAFT   Internationalized PTR Resource Record       17 May 2001


     Jiang Ming Liang
     i-DNS.net
     8 Temasek Boulevard
     #24-02 Suntec Tower Three
     Singapore 038988
     [e-mail]













































Shi, Jiang                                                      [Page 9]