draft-ietf-dnsop-serverid-06.txt

来自「非常好的dns解析软件」· 文本 代码 · 共 619 行 · 第 1/2 页

       should lend itself to access controls on who can query for it.

   4.  It should be possible to return a unique identifier for a server
       without requiring the exposure of information that may be non-
       public and considered sensitive by the operator, such as a
       hostname or unicast IP address maintained for administrative
       purposes.

   5.  It should be possible to authenticate the received data by some
       mechanism analogous to those provided by DNSSEC.  In this
       context, the need could be met by including encryption options in
       the specification of a new mechanism.

   6.  The identification mechanism should not be implementation-
       specific.










Woolf & Conrad          Expires September 6, 2006               [Page 6]

Internet-Draft                  Serverid                      March 2006


3.  IANA Considerations

   This document proposes no specific IANA action.  Protocol extensions,
   if any, to meet the requirements described are out of scope for this
   document.  A proposed extension, specified and adopted by normal IETF
   process, is described in [NSID], including relevant IANA action.













































Woolf & Conrad          Expires September 6, 2006               [Page 7]

Internet-Draft                  Serverid                      March 2006


4.  Security Considerations

   Providing identifying information as to which server is responding to
   a particular query from a particular location in the Internet can be
   seen as information leakage and thus a security risk.  This motivates
   the suggestion above that a new mechanism for server identification
   allow the administrator to disable the functionality altogether or
   partially restrict availability of the data.  It also suggests that
   the serverid data should not be readily correlated with a hostname or
   unicast IP address that may be considered private to the nameserver
   operator's management infrastructure.

   Propagation of protocol or service meta-data can sometimes expose the
   application to denial of service or other attack.  As DNS is a
   critically important infrastructure service for the production
   Internet, extra care needs to be taken against this risk for
   designers, implementors, and operators of a new mechanism for server
   identification.

   Both authentication and confidentiality of serverid data are
   potentially of interest to administrators-- that is, operators may
   wish to make serverid data available and reliable to themselves and
   their chosen associates only.  This would imply both an ability to
   authenticate it to themselves and keep it private from arbitrary
   other parties.  This led to Characteristics 4 and 5 of an improved
   solution.

























Woolf & Conrad          Expires September 6, 2006               [Page 8]

Internet-Draft                  Serverid                      March 2006


5.  Acknowledgements

   The technique for host identification documented here was initially
   implemented by Paul Vixie of the Internet Software Consortium in the
   Berkeley Internet Name Daemon package.  Comments and questions on
   earlier drafts were provided by Bob Halley, Brian Wellington, Andreas
   Gustafsson, Ted Hardie, Chris Yarnell, Randy Bush, and members of the
   ICANN Root Server System Advisory Committee.  The newest version
   takes a significantly different direction from previous versions,
   owing to discussion among contributors to the DNSOP working group and
   others, particularly Olafur Gudmundsson, Ed Lewis, Bill Manning, Sam
   Weiler, and Rob Austein.

6.  References

   [1]  Mockapetris, P., "Domain Names - Concepts and Facilities",
        RFC 1034, STD 0013, November 1987.

   [2]  Mockapetris, P., "Domain Names - Implementation and
        Specification", RFC 1035, STD 0013, November 1987.

   [3]  Hardie, T., "Distributing Authoritative Name Servers via Shared
        Unicast Addresses", RFC 3258, April 2002.

   [4]  ISC, "BIND 9 Configuration Reference".

   [5]  Austein, S., "DNS Name Server Identifier Option (NSID)",
        Internet Drafts http://www.ietf.org/internet-drafts/
        draft-ietf-dnsext-nsid-01.txt, January 2006.

   [6]  Arends, R., Austein, S., Larson, M., Massey, D., and S. Rose,
        "DNS Security Introduction and Requirements", RFC 4033,
        March 2005.


















Woolf & Conrad          Expires September 6, 2006               [Page 9]

Internet-Draft                  Serverid                      March 2006


Authors' Addresses

   Suzanne Woolf
   Internet Systems Consortium, Inc.
   950 Charter Street
   Redwood City, CA  94063
   US

   Phone: [phone]
   Email: [e-mail]
   URI:   http://www.isc.org/


   David Conrad
   Nominum, Inc.
   2385 Bay Road
   Redwood City, CA  94063
   US

   Phone: [phone]
   Email: [e-mail]
   URI:   http://www.nominum.com/





























Woolf & Conrad          Expires September 6, 2006              [Page 10]

Internet-Draft                  Serverid                      March 2006


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights 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; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   [e-mail].


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2006).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

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




Woolf & Conrad          Expires September 6, 2006              [Page 11]