draft-ietf-dnsop-default-local-zones-06.txt   draft-ietf-dnsop-default-local-zones-07.txt 
Network Working Group M. Andrews Network Working Group M. Andrews
Internet-Draft ISC Internet-Draft ISC
Intended status: BCP July 11, 2008 Intended status: BCP February 25, 2009
Expires: January 12, 2009 Expires: August 29, 2009
Locally-served DNS Zones Locally-served DNS Zones
draft-ietf-dnsop-default-local-zones-06 draft-ietf-dnsop-default-local-zones-07
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79. This document may contain material
have been or will be disclosed, and any of which he or she becomes from IETF Documents or IETF Contributions published or made publicly
aware will be disclosed, in accordance with Section 6 of BCP 79. available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 12, 2009. This Internet-Draft will expire on August 29, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract Abstract
Experience has shown that there are a number of DNS zones all Experience has shown that there are a number of DNS zones all
iterative resolvers and recursive nameservers should, unless iterative resolvers and recursive nameservers should, unless
configured otherwise, automatically serve. RFC 4193 specifies that configured otherwise, automatically serve. RFC 4193 specifies that
this should occur for D.F.IP6.ARPA. This document extends the this should occur for D.F.IP6.ARPA. This document extends the
practice to cover the IN-ADDR.ARPA zones for RFC 1918 address space practice to cover the IN-ADDR.ARPA zones for RFC 1918 address space
and other well known zones with similar characteristics. and other well known zones with similar characteristics.
skipping to change at page 2, line 26 skipping to change at page 2, line 39
4.5. IPv6 Link Local Addresses . . . . . . . . . . . . . . . . 7 4.5. IPv6 Link Local Addresses . . . . . . . . . . . . . . . . 7
4.6. IPv6 Example Prefix . . . . . . . . . . . . . . . . . . . 7 4.6. IPv6 Example Prefix . . . . . . . . . . . . . . . . . . . 7
5. Zones that are Out-Of-Scope . . . . . . . . . . . . . . . . . 7 5. Zones that are Out-Of-Scope . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . . 9 9.1. Normative References . . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . . 10
Appendix A. Change History [To Be Removed on Publication] . . . . 10 Appendix A. Change History [To Be Removed on Publication] . . . . 10
A.1. draft-ietf-dnsop-default-local-zones-06.txt . . . . . . . 10 A.1. draft-ietf-dnsop-default-local-zones-07.txt . . . . . . . 10
A.2. draft-ietf-dnsop-default-local-zones-05.txt . . . . . . . 11 A.2. draft-ietf-dnsop-default-local-zones-06.txt . . . . . . . 11
A.3. draft-ietf-dnsop-default-local-zones-04.txt . . . . . . . 11 A.3. draft-ietf-dnsop-default-local-zones-05.txt . . . . . . . 11
A.4. draft-ietf-dnsop-default-local-zones-03.txt . . . . . . . 11 A.4. draft-ietf-dnsop-default-local-zones-04.txt . . . . . . . 11
A.5. draft-ietf-dnsop-default-local-zones-02.txt . . . . . . . 11 A.5. draft-ietf-dnsop-default-local-zones-03.txt . . . . . . . 11
A.6. draft-ietf-dnsop-default-local-zones-01.txt . . . . . . . 11 A.6. draft-ietf-dnsop-default-local-zones-02.txt . . . . . . . 11
A.7. draft-ietf-dnsop-default-local-zones-00.txt . . . . . . . 11 A.7. draft-ietf-dnsop-default-local-zones-01.txt . . . . . . . 11
A.8. draft-andrews-full-service-resolvers-03.txt . . . . . . . 11 A.8. draft-ietf-dnsop-default-local-zones-00.txt . . . . . . . 11
A.9. draft-andrews-full-service-resolvers-02.txt . . . . . . . 12 A.9. draft-andrews-full-service-resolvers-03.txt . . . . . . . 12
A.10. draft-andrews-full-service-resolvers-02.txt . . . . . . . 12
Appendix B. Proposed Status [To Be Removed on Publication] . . . 12 Appendix B. Proposed Status [To Be Removed on Publication] . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12
Intellectual Property and Copyright Statements . . . . . . . . . . 13
1. Introduction 1. Introduction
Experience has shown that there are a number of DNS [RFC 1034] [RFC Experience has shown that there are a number of DNS [RFC 1034] [RFC
1035] zones that all iterative resolvers and recursive nameservers 1035] zones that all iterative resolvers and recursive nameservers
SHOULD, unless intentionally configured otherwise, automatically SHOULD, unless intentionally configured otherwise, automatically
serve. These zones include, but are not limited to, the IN-ADDR.ARPA serve. These zones include, but are not limited to, the IN-ADDR.ARPA
zones for the address space allocated by [RFC 1918] and the IP6.ARPA zones for the address space allocated by [RFC 1918] and the IP6.ARPA
zones for locally assigned unique local IPv6 addresses, [RFC 4193]. zones for locally assigned unique local IPv6 addresses, [RFC 4193].
skipping to change at page 10, line 46 skipping to change at page 10, line 46
[RFC 3330] [RFC 3330]
"Special-Use IPv4 Addresses", RFC 3330, September 2002. "Special-Use IPv4 Addresses", RFC 3330, September 2002.
[RFC 3849] [RFC 3849]
Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix
Reserved for Documentation", RFC 3849, July 2004. Reserved for Documentation", RFC 3849, July 2004.
Appendix A. Change History [To Be Removed on Publication] Appendix A. Change History [To Be Removed on Publication]
A.1. draft-ietf-dnsop-default-local-zones-06.txt A.1. draft-ietf-dnsop-default-local-zones-07.txt
none, expiry prevention
A.2. draft-ietf-dnsop-default-local-zones-06.txt
add IPv6 example prefix add IPv6 example prefix
A.2. draft-ietf-dnsop-default-local-zones-05.txt A.3. draft-ietf-dnsop-default-local-zones-05.txt
none, expiry prevention none, expiry prevention
A.3. draft-ietf-dnsop-default-local-zones-04.txt A.4. draft-ietf-dnsop-default-local-zones-04.txt
Centrally Assigned Local addresses -> Non-Locally Assigned Local Centrally Assigned Local addresses -> Non-Locally Assigned Local
address address
A.4. draft-ietf-dnsop-default-local-zones-03.txt A.5. draft-ietf-dnsop-default-local-zones-03.txt
expanded section 4 descriptions expanded section 4 descriptions
Added references [RFC 2136], [RFC 3596], Added references [RFC 2136], [RFC 3596],
[I-D.draft-ietf-dnsop-as112-ops] and [I-D.draft-ietf-dnsop-as112-ops] and
[I-D.draft-ietf-dnsop-as112-under-attack-help-help]. [I-D.draft-ietf-dnsop-as112-under-attack-help-help].
Revised language. Revised language.
A.5. draft-ietf-dnsop-default-local-zones-02.txt A.6. draft-ietf-dnsop-default-local-zones-02.txt
RNAME now "nobody.invalid." RNAME now "nobody.invalid."
Revised language. Revised language.
A.6. draft-ietf-dnsop-default-local-zones-01.txt A.7. draft-ietf-dnsop-default-local-zones-01.txt
Revised impact description. Revised impact description.
Updated to reflect change in IP6.INT status. Updated to reflect change in IP6.INT status.
A.7. draft-ietf-dnsop-default-local-zones-00.txt A.8. draft-ietf-dnsop-default-local-zones-00.txt
Adopted by DNSOP. Adopted by DNSOP.
"Author's Note" re-titled "Zones that are Out-Of-Scope" "Author's Note" re-titled "Zones that are Out-Of-Scope"
Add note that these zone are expected to seed the IANA registry. Add note that these zone are expected to seed the IANA registry.
Title changed. Title changed.
A.8. draft-andrews-full-service-resolvers-03.txt A.9. draft-andrews-full-service-resolvers-03.txt
Added "Proposed Status". Added "Proposed Status".
A.9. draft-andrews-full-service-resolvers-02.txt A.10. draft-andrews-full-service-resolvers-02.txt
Added 0.IN-ADDR.ARPA. Added 0.IN-ADDR.ARPA.
Appendix B. Proposed Status [To Be Removed on Publication] Appendix B. Proposed Status [To Be Removed on Publication]
This Internet-Draft is being submitted for eventual publication as an This Internet-Draft is being submitted for eventual publication as an
RFC with a proposed status of Best Current Practice. RFC with a proposed status of Best Current Practice.
Author's Address Author's Address
Mark P. Andrews Mark P. Andrews
Internet Systems Consortium Internet Systems Consortium
950 Charter Street 950 Charter Street
Redwood City, CA 94063 Redwood City, CA 94063
US US
Email: Mark_Andrews@isc.org Email: Mark_Andrews@isc.org
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
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.
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, THE IETF TRUST 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.
Intellectual Property
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
ietf-ipr@ietf.org.
 End of changes. 16 change blocks. 
27 lines changed or deleted 50 lines changed or added

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