draft-ietf-dnsop-misbehavior-against-aaaa-00.txt

bind 9.3结合mysql数据库

   MORISHITA Orange Yasuhiro
   Research and Development Department, Japan Registry Service Co.,Ltd.
   Fuundo Bldg 3F, 1-2 Kanda-Ogawamachi
   Chiyoda-ku, Tokyo  101-0052
   Japan

   EMail: [e-mail]


   JINMEI Tatuya
   Corporate Research & Development Center, Toshiba Corporation
   1 Komukai Toshiba-cho, Saiwai-ku
   Kawasaki-shi, Kanagawa  212-8582
   Japan

   EMail: [e-mail]

Appendix A. Live Examples

   In this appendix, we show concrete implementations and domain names
   that may cause problematic cases so that the behavior can be
   reproduced in a practical environment. The examples are for



Morishita & Jinmei       Expires July 11, 2004                  [Page 5]

Internet-Draft    Common Misbehavior against AAAA Queries   January 2004


   informational purposes only, and the authors do not intend to accuse
   any implementations or zone administrators.

   The behavior described in Section 4.2 (return NOTIMP) can be found by
   looking for a AAAA RR of www.css.vtext.com at 66.174.3.4.

   The behavior described in Section 4.3 (broken responses) can be seen
   by querying for a AAAA RR of "www.gslb.mainichi.co.jp," which is an
   alias of "www.mainichi.co.jp," at 210.173.172.2. The same behavior
   can be found with the name "vip.alt.ihp.sony.co.jp," an alias of
   "www.sony.co.jp," at 210.139.255.204.

   The behavior described in Section 4.4 (lame delegation) can be found
   by querying for a AAAA RR of "www.ual.com" at 209.87.113.4.

   The behavior described in Section 4.5 (ignore queries) can be seen by
   trying to ask for a AAAA RR of "ad.3jp.doubleclick.net," which is an
   alias of "ad.jp.doubleclick.net," at 210.153.90.9.

   Many authoritative server implementations show the expected behavior
   described in Section 3. Some DNS load balancers reportedly have a
   problematic behavior shown in Section 4, but the authors do not have
   a concrete example. The CERT/CC provides a list of implementations
   that behave as described in Section 4.1 [2].

   The BIND9 caching server implementation is an example of the latter
   cases described in Section 4.3 and Section 4.4, respectively. The
   BIND8 caching server implementation is an example of the former case
   described in Section 4.3. As for the issue shown in Section 4.4,
   BIND8 caching servers prior to 8.3.5 show the behavior described as
   the former case in this section. The versions 8.3.5 and later of
   BIND8 caching server behave like the BIND9 caching server
   implementation with this matter.

   Regarding resolver implementations, the authors are only familiar
   with the ones derived from the BIND implementation. These
   implementations always fall back regardless of the RCODE; NXDOMAIN,
   NOTIMP, or SERVFAIL. It even falls back when getting a broken
   response. However, the behavior does not help the situation in the
   NXDOMAIN case (see Section 4.1). Lame delegation (Section 4.4) also
   causes a fatal error at the resolver side if the resolver is using
   some older versions of BIND8 caching server.

   The authors hear that a stub resolver routine implemented in some web
   browsers interprets the broken response described in Section 4.3 as a
   fatal error and does not fall back to A queries. However, we have not
   confirmed this information.




Morishita & Jinmei       Expires July 11, 2004                  [Page 6]

Internet-Draft    Common Misbehavior against AAAA Queries   January 2004


Appendix B. Change History

   Changes since draft-morishita-dnsop-misbehavior-against-aaaa-00 are:

   o  Made a separate appendix and moved live examples to appendix so
      that we can remove them when this document is (ever) officially
      published.

   o  Revised some live examples based on the recent status.

   o  Noted in introduction that the misbehavior is not specific to AAAA
      and that this document still concentrates on the AAAA case.

   o  Changed the section title of "delegation loop" to "lame
      delegation" in order to reflect the essential point of the issue.
      Wording on this matter was updated accordingly.

   o  Updated the Acknowledgements list.

   o  Changed the reference category from normative to informative (this
      is an informational document after all).

   o  Changed the draft name to an IETF dnsop working group document (as
      agreed).

   o  Applied several editorial fixes.

























Morishita & Jinmei       Expires July 11, 2004                  [Page 7]

Internet-Draft    Common Misbehavior against AAAA Queries   January 2004


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights. Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11. Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard. Please address the information to the IETF Executive
   Director.


Full Copyright Statement

   Copyright (C) The Internet Society (2004). 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 assignees.

   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



Morishita & Jinmei       Expires July 11, 2004                  [Page 8]

Internet-Draft    Common Misbehavior against AAAA Queries   January 2004


   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.











































Morishita & Jinmei       Expires July 11, 2004                  [Page 9]