draft-ietf-dnsop-root-opreq-00.txt   draft-ietf-dnsop-root-opreq-01.txt 
dnsop Randy Bush dnsop Randy Bush
INTERNET-DRAFT Verio INTERNET-DRAFT Verio
draft-ietf-dnsop-root-opreq-00.txt Daniel Karrenberg draft-ietf-dnsop-root-opreq-01.txt Daniel Karrenberg
June 1999 RIPE/NCC October 1999 RIPE/NCC
Mark Kosters Mark Kosters
Network Solutions Network Solutions
Raymond Plzak Raymond Plzak
SAIC SAIC
Root Name Server Operational Requirements Root Name Server Operational Requirements
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
skipping to change at page 3, line 42 skipping to change at page 3, line 42
any zones other than the root and root-servers.net zones. These any zones other than the root and root-servers.net zones. These
restrictions help prevent undue load on the root servers and restrictions help prevent undue load on the root servers and
reduce the chance of their caching incorrect data. reduce the chance of their caching incorrect data.
2.6 Root servers MUST answer queries from any internet host, i.e. may 2.6 Root servers MUST answer queries from any internet host, i.e. may
not block root name resolution from any valid IP address, except not block root name resolution from any valid IP address, except
in the case of queries causing operational problems, in which in the case of queries causing operational problems, in which
case the blocking SHOULD last only as long as the problem, and be case the blocking SHOULD last only as long as the problem, and be
as specific as reasonably possible. as specific as reasonably possible.
2.7 Root servers MUST NOT answer AXFR, or other zone transfer, 2.7 Root servers SHOULD NOT answer AXFR, or other zone transfer,
queries from clients other than other root servers. This queries from clients other than other root servers. This
restriction is intended to, among other things, prevent restriction is intended to, among other things, prevent
unnecessary load on the root servers. unnecessary load on the root servers as advice has been heard
such as "To avoid having a corruptable cache, make your server a
stealth secondary for the root zone." The root servers MAY put
the root zone up for ftp or other access on one or more less
critical servers.
2.8 Servers MUST generate checksums when sending UDP datagrams and 2.8 Servers MUST generate checksums when sending UDP datagrams and
MUST verify checksums when receiving UDP datagrams. MUST verify checksums when receiving UDP datagrams.
3. Security Considerations 3. Security Considerations
The servers need both physical and protocol security as well as The servers need both physical and protocol security as well as
unambiguous authentication of their responses. unambiguous authentication of their responses.
3.1 Physical security MUST be ensured in a manner expected of data 3.1 Physical security MUST be ensured in a manner expected of data
skipping to change at page 8, line 20 skipping to change at page 8, line 20
Clarifications to the DNS Specification. R. Elz, R. Bush. Jul Clarifications to the DNS Specification. R. Elz, R. Bush. Jul
1997. 1997.
[RFC2535] [RFC2535]
Domain Name System Security Extensions. D. Eastlake, 3rd, C. Kauf- Domain Name System Security Extensions. D. Eastlake, 3rd, C. Kauf-
man. Mar 1999. man. Mar 1999.
7. Authors' Addresses 7. Authors' Addresses
Randy Bush Randy Bush
Verio, Inc.
5147 Crystal Springs 5147 Crystal Springs
Bainbridge Island, WA US-98110 Bainbridge Island, WA US-98110
+1 206 780 0431 +1 206 780 0431
randy@psg.com randy@psg.com
Daniel Karrenberg Daniel Karrenberg
RIPE Network Coordination Centre (NCC) RIPE Network Coordination Centre (NCC)
Singel 258 Singel 258
NL-1016-AB Amsterdam NL-1016-AB Amsterdam
Netherlands Netherlands
skipping to change at page 9, line 9 skipping to change at page 9, line 9
8. Specification of Requirements 8. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. document are to be interpreted as described in RFC 2119.
9. Full Copyright Statement 9. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to others, 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 and derivative works that comment on or otherwise explain it or assist in
its implementation may be prepared, copied, published and distributed, in its implementation may be prepared, copied, published and distributed, in
whole or in part, without restriction of any kind, provided that the above 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 copyright notice and this paragraph are included on all such copies and
derivative works. However, this document itself may not be modified in any derivative works. However, this document itself may not be modified in
way, such as by removing the copyright notice or references to the Internet any
Society or other Internet organizations, except as needed for the purpose of 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 developing Internet standards in which case the procedures for copyrights
defined in the Internet Standards process must be followed, or as required defined in the Internet Standards process must be followed, or as
required
to translate it into languages other than English. to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked The limited permissions granted above are perpetual and will not be
revoked
by the Internet Society or its successors or assigns. by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" This document and the information contained herein is provided on an "AS
IS"
basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE
DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
TO
ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. PARTICULAR PURPOSE.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/