draft-iab-2870bis-02.txt   draft-iab-2870bis-03.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: August 18, 2015 February 14, 2015 Expires: March 27, 2016 September 24, 2015
DNS Root Name Service Protocol and Deployment Requirements DNS Root Name Service Protocol and Deployment Requirements
draft-iab-2870bis-02.txt draft-iab-2870bis-03.txt
Abstract Abstract
The DNS Root Name service is 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 service are defined in this be implemented for the DNS root name service are defined in this
document. Operational requirements are out of scope. document. Operational requirements are out of scope.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 August 18, 2015. This Internet-Draft will expire on March 27, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
skipping to change at page 3, line 20 skipping to change at page 3, line 20
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.
MUST implement EDNS(0)[RFC6891].
3. Deployment Requirements 3. Deployment Requirements
The root name service: The root name service:
MUST answer queries from any entity conforming to [RFC1122] with a MUST answer queries from any entity conforming to [RFC1122] with a
valid IP address. valid IP address.
MUST serve the unique [RFC2826] root zone[ROOTZONE]. MUST serve the unique [RFC2826] root zone[ROOTZONE].
4. Security Considerations 4. Security Considerations
skipping to change at page 3, line 50 skipping to change at page 4, line 4
This document has no action for IANA. This document has no action for IANA.
6. Acknowledgements 6. Acknowledgements
Some text was taken from [RFC2870]. The editors of this document Some text was taken from [RFC2870]. The editors of this document
would like to sincerely thank the following individuals for valuable would like to sincerely thank the following individuals for valuable
contributions to the text: Andrew Sullivan, Simon Perreault, Jean- contributions to the text: Andrew Sullivan, Simon Perreault, Jean-
Philippe Dionne, Dave Thaler, Russ Housley, Alissa Cooper, Joe Abley, Philippe Dionne, Dave Thaler, Russ Housley, Alissa Cooper, Joe Abley,
Joao Damas, Daniel Karrenberg, Jacques Latour, Eliot Lear, Bill Joao Damas, Daniel Karrenberg, Jacques Latour, Eliot Lear, Bill
Manning, David Conrad, Paul Hoffman. Manning, David Conrad, Paul Hoffman, Terry Manderson, Jari Arkko,
Mark Andrews.
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. DOI 10.17487/RFC0768, August 1980,
<http://www.rfc-editor.org/info/rfc768>.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
1981. DOI 10.17487/RFC0791, September 1981,
<http://www.rfc-editor.org/info/rfc791>.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC [RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
793, September 1981. RFC 793, DOI 10.17487/RFC0793, September 1981,
<http://www.rfc-editor.org/info/rfc793>.
[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, DOI 10.17487/RFC1035,
November 1987, <http://www.rfc-editor.org/info/rfc1035>.
[RFC1122] Braden, R., "Requirements for Internet Hosts - [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, October 1989. Communication Layers", STD 3, RFC 1122,
DOI 10.17487/RFC1122, October 1989,
<http://www.rfc-editor.org/info/rfc1122>.
[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,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[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, DOI 10.17487/RFC2181, July 1997,
<http://www.rfc-editor.org/info/rfc2181>.
[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, DOI 10.17487/RFC2460,
December 1998, <http://www.rfc-editor.org/info/rfc2460>.
[RFC2826] Internet Architecture Board, "IAB Technical Comment on the [RFC2826] Internet Architecture Board, "IAB Technical Comment on the
Unique DNS Root", RFC 2826, May 2000. Unique DNS Root", RFC 2826, DOI 10.17487/RFC2826, May
2000, <http://www.rfc-editor.org/info/rfc2826>.
[RFC2870] Bush, R., Karrenberg, D., Kosters, M., and R. Plzak, "Root [RFC2870] Bush, R., Karrenberg, D., Kosters, M., and R. Plzak, "Root
Name Server Operational Requirements", BCP 40, RFC 2870, Name Server Operational Requirements", BCP 40, RFC 2870,
June 2000. DOI 10.17487/RFC2870, June 2000,
<http://www.rfc-editor.org/info/rfc2870>.
[RFC3172] Huston, G., "Management Guidelines & Operational [RFC3172] Huston, G., Ed., "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, DOI 10.17487/RFC3172,
September 2001, <http://www.rfc-editor.org/info/rfc3172>.
[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, DOI 10.17487/RFC4035, March 2005,
<http://www.rfc-editor.org/info/rfc4035>.
[RFC6891] Damas, J., Graff, M., and P. Vixie, "Extension Mechanisms
for DNS (EDNS(0))", STD 75, RFC 6891,
DOI 10.17487/RFC6891, April 2013,
<http://www.rfc-editor.org/info/rfc6891>.
[ROOTZONE] [ROOTZONE]
"Root Zone", <ftp://rs.internic.net/domain/root.zone>. "Root Zone", <ftp://rs.internic.net/domain/root.zone>.
[RSSAC-001] [RSSAC-001]
Root Server System Advisory Committee (RSSAC), , "Service Root Server System Advisory Committee (RSSAC), , "Service
Expectations of Root Servers", November 2014, Expectations of Root Servers", November 2014,
<https://www.icann.org/en/system/files/files/rssac-001- <https://www.icann.org/en/system/files/files/rssac-001-
draft-20nov14-en.pdf>. draft-20nov14-en.pdf>.
 End of changes. 18 change blocks. 
20 lines changed or deleted 42 lines changed or added

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