draft-iab-2870bis-00.txt   draft-iab-2870bis-01.txt 
Network Working Group M. Blanchet Network Working Group M. Blanchet
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 2870 (if approved) L-J. Liman Obsoletes: 2870 (if approved) L-J. Liman
Intended status: Best Current Practice Netnod Intended status: Best Current Practice Netnod
Expires: January 11, 2014 July 10, 2013 Expires: August 15, 2014 February 11, 2014
DNS Root Name Service Protocol and Deployment Requirements DNS Root Name Service Protocol and Deployment Requirements
draft-iab-2870bis-00.txt draft-iab-2870bis-01.txt
Abstract Abstract
The DNS Root Name service are a critical part of the Internet The DNS Root Name service is a critical part of the Internet
architecture. The protocol and deployment requirements expected to architecture. The protocol and deployment requirements expected to
be implemented for the DNS root name services are defined in this be implemented for the DNS root name service are defined in this
document. Operational requirements are out of scope. This document document. Operational requirements are out of scope.
obsoletes and reclassifies RFC2870 as Historic.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 11, 2014. This Internet-Draft will expire on August 15, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. RFC 2870 as Historic . . . . . . . . . . . . . . . . . . 2 1.1. RFC 2870 as Historic . . . . . . . . . . . . . . . . . . 2
2. Protocol Requirements . . . . . . . . . . . . . . . . . . . . 3 2. Protocol Requirements . . . . . . . . . . . . . . . . . . . . 2
3. Deployment Requirements . . . . . . . . . . . . . . . . . . . 3 3. Deployment Requirements . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
7. Informative References . . . . . . . . . . . . . . . . . . . 4 7. Informative References . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
[RFC2870] discusses protocol and operational requirements for root [RFC2870] discusses protocol and operational requirements for root
name servers for Internet's domain name system(DNS) protocol name servers for Internet's domain name system(DNS) protocol
[RFC1035]. Since its publication, both protocol and operational [RFC1035]. Since its publication, both protocol and operational
requirements have evolved. The concensus of the community is to requirements have evolved. In the modern Internet it makes more
separate the two sets of requirements into two documents. The sense to separate the two sets of requirements into two documents.
operational requirements are defined in [RSSAC-001]. This document The operational requirements are defined in [RSSAC-001]. This
defines the protocol requirements and some deployment requirements. document defines the protocol requirements and some deployment
requirements.
The root servers are authoritative servers of the unique [RFC2826] The root servers are authoritative servers of the unique [RFC2826]
root zone (".")[ROOTZONE], the root-servers.net zone, and the zone root zone (".")[ROOTZONE]. They currently also serve the root-
for the .arpa top-level domain[ARPAZONE]. This document describes servers.net zone and the zone for the .arpa top-level
the external interface of the root name servers from a protocol domain[ARPAZONE]. This document describes the external interface of
viewpoint of the service. It specifies basic requirements for the the root name servers from a protocol viewpoint of the service. It
Internet that DNS clients meet when interacting with a root name specifies basic requirements for the Internet that DNS clients meet
service over the public Internet. when interacting with a root name service over the public Internet.
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
document, are to be interpreted as described in BCP 14, [RFC2119]. document, are to be interpreted as described in BCP 14, [RFC2119].
1.1. RFC 2870 as Historic 1.1. RFC 2870 as Historic
This document obsoletes and reclassifies [RFC2870] as Historic. This document obsoletes and reclassifies [RFC2870] as Historic.
This document and [RSSAC-001] together functionally replace
[RFC2870].
2. Protocol Requirements 2. Protocol Requirements
This section describes the high-level protocol requirements. This section describes the minimum high-level protocol requirements.
Operative details are not discussed and are left to the operators of Operative details are documented in [RSSAC-001] and implementation is
the root name service. left to the operators of the root name service.
The root name service: The root name service:
MUST implement [RFC1035] and [RFC2181]. MUST implement core DNS [RFC1035] and clarifications to the DNS
[RFC2181].
MUST support IPv4[RFC0791] and IPv6[RFC2460] transport of DNS MUST support IPv4[RFC0791] and IPv6[RFC2460] transport of DNS
queries and responses. queries and responses.
MUST support UDP[RFC0768] and TCP[RFC0793] transport of DNS MUST support UDP[RFC0768] and TCP[RFC0793] transport of DNS
queries and responses. queries and responses.
MUST generate checksums when sending UDP datagrams and MUST verify MUST generate checksums when sending UDP datagrams and MUST verify
checksums when receiving UDP datagrams containing a non-zero checksums when receiving UDP datagrams containing a non-zero
checksum. checksum.
MUST implement DNSSEC[RFC4035], as an authoritative name service MUST implement DNSSEC[RFC4035], as an authoritative name service.
serving signed zones accodingly.
3. Deployment Requirements 3. Deployment Requirements
The root name service: The root name service:
MUST answer queries from any Internet host MUST answer queries from any entity conforming to [RFC1122] with a
valid IP address.
MUST serve the unique [RFC2826] root zone[ROOTZONE], the root- MUST serve the unique [RFC2826] root zone[ROOTZONE].
servers.net zone, and the zone for the .arpa top-level domain
[ARPAZONE],[RFC3172]. MAY also serve the root-servers.net zone, and the zone for the
.arpa top-level domain [ARPAZONE],[RFC3172].
4. Security Considerations 4. Security Considerations
This document does not specify a new protocol. However, the root This document does not specify a new protocol. However, the root
name servers are a key component of the Internet architecture and name service is a key component of the Internet architecture and play
play a key role into the overall security of the Internet[RFC2826]. a key role into the overall security of the Internet[RFC2826].
Specific security considerations on the DNS protocols are discussed Specific security considerations on the DNS protocols are discussed
in their respective specifications. The security considerations on in their respective specifications. The security considerations on
the operational side of the root name servers are discussed in the operational side of the root name servers are discussed in
[RSSAC-001]. [RSSAC-001].
5. IANA Considerations 5. IANA Considerations
This document has no action for IANA. This document has no action for IANA.
6. Acknowledgements 6. Acknowledgements
Some text was taken from [RFC2870]. Andrew Sullivan, Simon Some text was taken from [RFC2870]. The editors of this document
Perreault, Jean-Philippe Dionne, Dave Thaler, Russ Housley, Alissa would like to sincerely thank the following individuals for valuable
Cooper, Joe Abley, Joao Damas, Daniel Karrenberg, Jacques Latour, contributions to the text: Andrew Sullivan, Simon Perreault, Jean-
Eliot Lear, provided comments or text. Philippe Dionne, Dave Thaler, Russ Housley, Alissa Cooper, Joe Abley,
Joao Damas, Daniel Karrenberg, Jacques Latour, Eliot Lear and Bill
Manning.
7. Informative References 7. Informative References
[ARPAZONE] [ARPAZONE]
Internet Assigned Numbers Authority (IANA), ., ".ARPA Zone Internet Assigned Numbers Authority (IANA), , ".ARPA Zone
Management", , <http://www.iana.org/domains/arpa>. Management", <http://www.iana.org/domains/arpa>.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September
1981. 1981.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC [RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC
793, September 1981. 793, September 1981.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[RFC1122] Braden, R., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS [RFC2181] Elz, R. and R. Bush, "Clarifications to the DNS
Specification", RFC 2181, July 1997. Specification", RFC 2181, July 1997.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC2826] Internet Architecture Board, "IAB Technical Comment on the [RFC2826] Internet Architecture Board, "IAB Technical Comment on the
skipping to change at page 5, line 10 skipping to change at page 5, line 6
[RFC3172] Huston, G., "Management Guidelines & Operational [RFC3172] Huston, G., "Management Guidelines & Operational
Requirements for the Address and Routing Parameter Area Requirements for the Address and Routing Parameter Area
Domain ("arpa")", BCP 52, RFC 3172, September 2001. Domain ("arpa")", BCP 52, RFC 3172, September 2001.
[RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Protocol Modifications for the DNS Security Rose, "Protocol Modifications for the DNS Security
Extensions", RFC 4035, March 2005. Extensions", RFC 4035, March 2005.
[ROOTZONE] [ROOTZONE]
, "Root Zone", , <ftp://rs.internic.net/domain/root.zone>. "Root Zone", <ftp://rs.internic.net/domain/root.zone>.
[RSSAC-001] [RSSAC-001]
Abley, J., Damas, J., Larson, M., Liman, L-J., Manderson, Abley, J., Damas, J., Larson, M., Liman, L-J., Manderson,
T., and B. Verd, "Service Expectations of Root Servers", , T., and B. Verd, "Service Expectations of Root Servers",
<http://www.icann.org/en/groups/rssac>. <http://www.icann.org/en/groups/rssac>.
Authors' Addresses Authors' Addresses
Marc Blanchet Marc Blanchet
Viagenie Viagenie
246 Aberdeen 246 Aberdeen
Quebec, QC G1R 2E1 Quebec, QC G1R 2E1
Canada Canada
 End of changes. 22 change blocks. 
41 lines changed or deleted 51 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/