draft-ietf-dnsop-default-local-zones-07.txt   draft-ietf-dnsop-default-local-zones-08.txt 
Network Working Group M. Andrews Network Working Group M. Andrews
Internet-Draft ISC Internet-Draft ISC
Intended status: BCP February 25, 2009 Intended status: BCP February 27, 2009
Expires: August 29, 2009 Expires: August 31, 2009
Locally-served DNS Zones Locally-served DNS Zones
draft-ietf-dnsop-default-local-zones-07 draft-ietf-dnsop-default-local-zones-08
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 August 29, 2009. This Internet-Draft will expire on August 31, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
Abstract Abstract
Experience has shown that there are a number of DNS zones all Experience with the Domain Name System (DNS) has shown that there are
iterative resolvers and recursive nameservers should, unless a number of DNS zones all iterative resolvers and recursive
configured otherwise, automatically serve. RFC 4193 specifies that nameservers should automatically serve, unless configured otherwise.
this should occur for D.F.IP6.ARPA. This document extends the RFC 4193 specifies that this should occur for D.F.IP6.ARPA. This
practice to cover the IN-ADDR.ARPA zones for RFC 1918 address space document extends the practice to cover the IN-ADDR.ARPA zones for RFC
and other well known zones with similar characteristics. 1918 address space and other well known zones with similar
characteristics.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Reserved Words . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Reserved Words . . . . . . . . . . . . . . . . . . . . . . 4
2. Effects on sites using RFC 1918 addresses. . . . . . . . . . . 4 2. Effects on sites using RFC 1918 addresses. . . . . . . . . . . 5
3. Changes to Iterative Resolver Behaviour. . . . . . . . . . . . 4 3. Changes to Iterative Resolver Behaviour. . . . . . . . . . . . 5
4. Lists Of Zones Covered . . . . . . . . . . . . . . . . . . . . 5 4. Lists Of Zones Covered . . . . . . . . . . . . . . . . . . . . 6
4.1. RFC 1918 Zones . . . . . . . . . . . . . . . . . . . . . . 5 4.1. RFC1918 Zones . . . . . . . . . . . . . . . . . . . . . . 6
4.2. RFC 3330 Zones . . . . . . . . . . . . . . . . . . . . . . 6 4.2. RFC3330 Zones . . . . . . . . . . . . . . . . . . . . . . 7
4.3. Local IPv6 Unicast Addresses . . . . . . . . . . . . . . . 6 4.3. Local IPv6 Unicast Addresses . . . . . . . . . . . . . . . 7
4.4. IPv6 Locally Assigned Local Addresses . . . . . . . . . . 6 4.4. IPv6 Locally Assigned Local Addresses . . . . . . . . . . 7
4.5. IPv6 Link Local Addresses . . . . . . . . . . . . . . . . 7 4.5. IPv6 Link Local Addresses . . . . . . . . . . . . . . . . 8
4.6. IPv6 Example Prefix . . . . . . . . . . . . . . . . . . . 7 4.6. IPv6 Example Prefix . . . . . . . . . . . . . . . . . . . 8
5. Zones that are Out-Of-Scope . . . . . . . . . . . . . . . . . 7 5. Zones that are Out-Of-Scope . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . . 9 9.1. Normative References . . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . . 11
Appendix A. Change History [To Be Removed on Publication] . . . . 10 Appendix A. Change History [To Be Removed on Publication] . . . . 11
A.1. draft-ietf-dnsop-default-local-zones-07.txt . . . . . . . 10 A.1. draft-ietf-dnsop-default-local-zones-08.txt . . . . . . . 11
A.2. draft-ietf-dnsop-default-local-zones-06.txt . . . . . . . 11 A.2. draft-ietf-dnsop-default-local-zones-07.txt . . . . . . . 11
A.3. draft-ietf-dnsop-default-local-zones-05.txt . . . . . . . 11 A.3. draft-ietf-dnsop-default-local-zones-06.txt . . . . . . . 11
A.4. draft-ietf-dnsop-default-local-zones-04.txt . . . . . . . 11 A.4. draft-ietf-dnsop-default-local-zones-05.txt . . . . . . . 11
A.5. draft-ietf-dnsop-default-local-zones-03.txt . . . . . . . 11 A.5. draft-ietf-dnsop-default-local-zones-04.txt . . . . . . . 12
A.6. draft-ietf-dnsop-default-local-zones-02.txt . . . . . . . 11 A.6. draft-ietf-dnsop-default-local-zones-03.txt . . . . . . . 12
A.7. draft-ietf-dnsop-default-local-zones-01.txt . . . . . . . 11 A.7. draft-ietf-dnsop-default-local-zones-02.txt . . . . . . . 12
A.8. draft-ietf-dnsop-default-local-zones-00.txt . . . . . . . 11 A.8. draft-ietf-dnsop-default-local-zones-01.txt . . . . . . . 12
A.9. draft-andrews-full-service-resolvers-03.txt . . . . . . . 12 A.9. draft-ietf-dnsop-default-local-zones-00.txt . . . . . . . 12
A.10. draft-andrews-full-service-resolvers-02.txt . . . . . . . 12 A.10. draft-andrews-full-service-resolvers-03.txt . . . . . . . 12
Appendix B. Proposed Status [To Be Removed on Publication] . . . 12 A.11. draft-andrews-full-service-resolvers-02.txt . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 Appendix B. Proposed Status [To Be Removed on Publication] . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
Experience has shown that there are a number of DNS [RFC 1034] [RFC Experience with the Domain Name System (DNS, [RFC1034] and [RFC1035])
1035] zones that all iterative resolvers and recursive nameservers has shown that there are a number of DNS zones that all iterative
SHOULD, unless intentionally configured otherwise, automatically resolvers and recursive nameservers SHOULD automatically serve,
serve. These zones include, but are not limited to, the IN-ADDR.ARPA unless intentionally configured otherwise. These zones include, but
zones for the address space allocated by [RFC 1918] and the IP6.ARPA are not limited to, the IN-ADDR.ARPA zones for the address space
zones for locally assigned unique local IPv6 addresses, [RFC 4193]. allocated by [RFC1918] and the IP6.ARPA zones for locally assigned
unique local IPv6 addresses defined in [RFC4193].
This recommendation is made because data has shown that significant This recommendation is made because data has shown that significant
leakage of queries for these name spaces is occurring, despite leakage of queries for these name spaces is occurring, despite
instructions to restrict them, and because it has therefore become instructions to restrict them, and because it has therefore become
necessary to deploy sacrificial name servers to protect the immediate necessary to deploy sacrificial name servers to protect the immediate
parent name servers for these zones from excessive, unintentional, parent name servers for these zones from excessive, unintentional,
query load [AS112] [I-D.draft-ietf-dnsop-as112-ops] query load [AS112] [I-D.draft-ietf-dnsop-as112-ops]
[I-D.draft-ietf-dnsop-as112-under-attack-help-help]. There is every [I-D.draft-ietf-dnsop-as112-under-attack-help-help]. There is every
expectation that the query load will continue to increase unless expectation that the query load will continue to increase unless
steps are taken as outlined here. steps are taken as outlined here.
skipping to change at page 4, line 31 skipping to change at page 5, line 31
sites will be fully disconnected from the Internet and have their own sites will be fully disconnected from the Internet and have their own
root servers for their own non-Internet DNS tree. root servers for their own non-Internet DNS tree.
3. Changes to Iterative Resolver Behaviour. 3. Changes to Iterative Resolver Behaviour.
Unless configured otherwise, an iterative resolver will now return Unless configured otherwise, an iterative resolver will now return
authoritatively (aa=1) name errors (RCODE=3) for queries within the authoritatively (aa=1) name errors (RCODE=3) for queries within the
zones in Section 4, with the obvious exception of queries for the zones in Section 4, with the obvious exception of queries for the
zone name itself where SOA, NS and "no data" responses will be zone name itself where SOA, NS and "no data" responses will be
returned as appropriate to the query type. One common way to do this returned as appropriate to the query type. One common way to do this
is to serve empty (SOA and NS only) zones. all at once is to serve empty (SOA and NS only) zones.
An implementation of this recommendation MUST provide a mechanism to An implementation of this recommendation MUST provide a mechanism to
disable this new behaviour, and SHOULD allow this decision on a zone disable this new behaviour, and SHOULD allow this decision on a zone
by zone basis. by zone basis.
If using empty zones one SHOULD NOT use the same NS and SOA records If using empty zones one SHOULD NOT use the same NS and SOA records
as used on the public Internet servers as that will make it harder to as used on the public Internet servers as that will make it harder to
detect the origin of the responses and thus any leakage to the public detect the origin of the responses and thus any leakage to the public
Internet servers. This document recommends that the NS record Internet servers. This document recommends that the NS record
defaults to the name of the zone and the SOA MNAME defaults to the defaults to the name of the zone and the SOA MNAME defaults to the
skipping to change at page 6, line 7 skipping to change at page 7, line 7
| 27.172.IN-ADDR.ARPA | | 27.172.IN-ADDR.ARPA |
| 28.172.IN-ADDR.ARPA | | 28.172.IN-ADDR.ARPA |
| 29.172.IN-ADDR.ARPA | | 29.172.IN-ADDR.ARPA |
| 30.172.IN-ADDR.ARPA | | 30.172.IN-ADDR.ARPA |
| 31.172.IN-ADDR.ARPA | | 31.172.IN-ADDR.ARPA |
| 168.192.IN-ADDR.ARPA | | 168.192.IN-ADDR.ARPA |
+----------------------+ +----------------------+
4.2. RFC 3330 Zones 4.2. RFC 3330 Zones
The following zones correspond to those address ranges from [RFC The following zones correspond to those address ranges from [RFC3330]
3330] that are not expected to appear as source or destination that are not expected to appear as source or destination addresses on
addresses on the public Internet and to not have a unique name to the public Internet and to not have a unique name to associate with.
associate with.
The recommendation to serve an empty zone 127.IN-ADDR.ARPA is not a The recommendation to serve an empty zone 127.IN-ADDR.ARPA is not a
attempt to discourage any practice to provide a PTR RR for attempt to discourage any practice to provide a PTR RR for
1.0.0.127.IN-ADDR.ARPA locally. In fact, a meaningful reverse 1.0.0.127.IN-ADDR.ARPA locally. In fact, a meaningful reverse
mapping should exist, but the exact setup is out of the scope of this mapping should exist, but the exact setup is out of the scope of this
document. Similar logic applies to the reverse mapping for ::1 document. Similar logic applies to the reverse mapping for ::1
(Section 4.3). The recommendations made here simply assume no other (Section 4.3). The recommendations made here simply assume no other
coverage for these domains exists. coverage for these domains exists.
+------------------------------+------------------------+ +------------------------------+------------------------+
skipping to change at page 6, line 32 skipping to change at page 7, line 31
+------------------------------+------------------------+ +------------------------------+------------------------+
| 0.IN-ADDR.ARPA | IPv4 "THIS" NETWORK | | 0.IN-ADDR.ARPA | IPv4 "THIS" NETWORK |
| 127.IN-ADDR.ARPA | IPv4 LOOP-BACK NETWORK | | 127.IN-ADDR.ARPA | IPv4 LOOP-BACK NETWORK |
| 254.169.IN-ADDR.ARPA | IPv4 LINK LOCAL | | 254.169.IN-ADDR.ARPA | IPv4 LINK LOCAL |
| 2.0.192.IN-ADDR.ARPA | IPv4 TEST NET | | 2.0.192.IN-ADDR.ARPA | IPv4 TEST NET |
| 255.255.255.255.IN-ADDR.ARPA | IPv4 BROADCAST | | 255.255.255.255.IN-ADDR.ARPA | IPv4 BROADCAST |
+------------------------------+------------------------+ +------------------------------+------------------------+
4.3. Local IPv6 Unicast Addresses 4.3. Local IPv6 Unicast Addresses
The reverse mappings ([RFC 3596], Section 2.5 IP6.ARPA Domain) for The reverse mappings ([RFC3596], Section 2.5 IP6.ARPA Domain) for the
the IPv6 Unspecified (::) and Loopback (::1) addresses ([RFC 4291], IPv6 Unspecified (::) and Loopback (::1) addresses ([RFC4291],
Sections 2.4, 2.5.2 and 2.5.3) are covered by these two zones: Sections 2.4, 2.5.2 and 2.5.3) are covered by these two zones:
+-------------------------------------------+ +-------------------------------------------+
| Zone | | Zone |
+-------------------------------------------+ +-------------------------------------------+
| 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.\ | | 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.\ |
| 0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA | | 0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA |
| 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.\ | | 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.\ |
| 0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA | | 0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA |
+-------------------------------------------+ +-------------------------------------------+
skipping to change at page 7, line 39 skipping to change at page 8, line 39
+--------------------------+ +--------------------------+
| Zone | | Zone |
+--------------------------+ +--------------------------+
| 8.B.D.0.1.0.0.2.IP6.ARPA | | 8.B.D.0.1.0.0.2.IP6.ARPA |
+--------------------------+ +--------------------------+
Note: 8.B.D.0.1.0.0.2.IP6.ARPA is not being used as a example here. Note: 8.B.D.0.1.0.0.2.IP6.ARPA is not being used as a example here.
5. Zones that are Out-Of-Scope 5. Zones that are Out-Of-Scope
IPv6 site-local addresses, [RFC 4291] Sections 2.4 and 2.5.7, and IPv6 site-local addresses (deprecated, see [RFC4291] Sections 2.4 and
IPv6 Non-Locally Assigned Local addresses [RFC 4193] are not covered 2.5.7), and IPv6 Non-Locally Assigned Local addresses ([RFC4193]) are
here. It is expected that IPv6 site-local addresses will be self not covered here.
correcting as IPv6 implementations remove support for site-local
addresses. However, sacrificial servers for C.E.F.IP6.ARPA through It is expected that IPv6 site-local addresses will be self correcting
as IPv6 implementations remove support for site-local addresses.
However, sacrificial servers for the zones C.E.F.IP6.ARPA through
F.E.F.IP6.ARPA may still need to be deployed in the short term if the F.E.F.IP6.ARPA may still need to be deployed in the short term if the
traffic becomes excessive. traffic becomes excessive.
For IPv6 Non-Locally Assigned Local addresses (L = 0) [RFC 4193], For IPv6 Non-Locally Assigned Local addresses (L = 0) [RFC 4193],
there has been no decision made about whether the Regional Internet there has been no decision made about whether the Regional Internet
Registries (RIRs) will provide delegations in this space or not. If Registries (RIRs) will provide delegations in this space or not. If
they don't, then C.F.IP6.ARPA will need to be added to the list in they don't, then C.F.IP6.ARPA will need to be added to the list in
Section 4.4. If they do, then registries will need to take steps to Section 4.4. If they do, then registries will need to take steps to
ensure that name servers are provided for these addresses. ensure that name servers are provided for these addresses.
skipping to change at page 8, line 20 skipping to change at page 9, line 22
This document has also deliberately ignored names immediately under This document has also deliberately ignored names immediately under
the root domain. While there is a subset of queries to the root name the root domain. While there is a subset of queries to the root name
servers which could be addressed using the techniques described here servers which could be addressed using the techniques described here
(e.g. .local, .workgroup and IPv4 addresses), there is also a vast (e.g. .local, .workgroup and IPv4 addresses), there is also a vast
amount of traffic that requires a different strategy (e.g. lookups amount of traffic that requires a different strategy (e.g. lookups
for unqualified hostnames, IPv6 addresses). for unqualified hostnames, IPv6 addresses).
6. IANA Considerations 6. IANA Considerations
This document requests that IANA establish a registry of zones which This document requests that IANA establish a registry of zones which
require this default behaviour. The initial contents of which are in require this default behaviour. The initial contents of this
Section 4. Implementors are encouraged to check this registry and registry are defined in Section 4. Implementors are encouraged to
adjust their implementations to reflect changes therein. periodically check this registry and adjust their implementations to
reflect changes therein.
This registry can be amended through "IETF Consensus" as per [RFC This registry can be amended through "IETF Review" as per [RFC5226].
2434].
IANA should co-ordinate with the RIRs to ensure that, as DNSSEC is IANA should co-ordinate with the RIRs to ensure that, as DNSSEC is
deployed in the reverse tree, delegations for these zones are made in deployed in the reverse tree, delegations for these zones are made in
the manner described in Section 7. the manner described in Section 7.
7. Security Considerations 7. Security Considerations
During the initial deployment phase, particularly where [RFC 1918] During the initial deployment phase, particularly where [RFC 1918]
addresses are in use, there may be some clients that unexpectedly addresses are in use, there may be some clients that unexpectedly
receive a name error rather than a PTR record. This may cause some receive a name error rather than a PTR record. This may cause some
skipping to change at page 9, line 14 skipping to change at page 10, line 15
8. Acknowledgements 8. Acknowledgements
This work was supported by the US National Science Foundation This work was supported by the US National Science Foundation
(research grant SCI-0427144) and DNS-OARC. (research grant SCI-0427144) and DNS-OARC.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC 1034] [RFC1034] Mockapetris, P., "DOMAIN NAMES - CONCEPTS AND FACILITIES",
Mockapetris, P., "DOMAIN NAMES - CONCEPTS AND FACILITIES",
STD 13, RFC 1034, November 1987. STD 13, RFC 1034, November 1987.
[RFC 1035] [RFC1035] Mockapetris, P., "DOMAIN NAMES - IMPLEMENTATION AND
Mockapetris, P., "DOMAIN NAMES - IMPLEMENTATION AND
SPECIFICATION", STD 13, RFC 1035, November 1987. SPECIFICATION", STD 13, RFC 1035, November 1987.
[RFC 1918] [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
and E. Lear, "Address Allocation for Private Internets", and E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, February 1996. BCP 5, RFC 1918, February 1996.
[RFC 2119] [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
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.
[RFC 2136] [RFC2136] Vixie, P., Thomson, A., Rekhter, Y., and J. Bound,
Vixie, P., Thomson, A., Rekhter, Y., and J. Bound,
"Dynamic Updates in the Domain Name System (DNS UPDATE)", "Dynamic Updates in the Domain Name System (DNS UPDATE)",
RFC 2136, April 1997. RFC 2136, April 1997.
[RFC 2308] [RFC2308] Andrews, M., "Negative Caching of DNS Queries (DNS
Andrews, M., "Negative Caching of DNS Queries (DNS
NCACHE)", RFC 2398, March 1998. NCACHE)", RFC 2398, March 1998.
[RFC 2434] [RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS
Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC 2606]
Eastlake, D. and A. Panitz, "Reserved Top Level DNS
Names", BCP 32, RFC 2606, June 1999. Names", BCP 32, RFC 2606, June 1999.
[RFC 3596] [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi,
Thomson, S., Huitema, C., Ksinant, V., and M. Souissi,
"DNS Extensions to Support IPv6", RFC 3596, October 2003. "DNS Extensions to Support IPv6", RFC 3596, October 2003.
[RFC 4035] [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S.
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.
[RFC 4159] [RFC4159] Huston, G., "Deprecation of "ip6.int"", BCP 109, RFC 4159,
Huston, G., "Deprecation of "ip6.int"", BCP 109, RFC 4159,
August 2005. August 2005.
[RFC 4193] [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
Addresses", RFC 4193, October 2005. Addresses", RFC 4193, October 2005.
[RFC 4291] [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
October 2008.
9.2. Informative References 9.2. Informative References
[AS112] "AS112 Project", <http://www.as112.net/>. [AS112] "AS112 Project", <http://www.as112.net/>.
[I-D.draft-ietf-dnsop-as112-ops] [I-D.draft-ietf-dnsop-as112-ops]
Abley, J. and W. Maton, "AS112 Nameserver Operations", Abley, J. and W. Maton, "AS112 Nameserver Operations",
draft-ietf-dnsop-as112-ops-00 (work in progress), draft-ietf-dnsop-as112-ops-01 (work in progress),
February 2007. November 2007.
[I-D.draft-ietf-dnsop-as112-under-attack-help-help] [I-D.draft-ietf-dnsop-as112-under-attack-help-help]
Abley, J. and W. Maton, "I'm Being Attacked by Abley, J. and W. Maton, "I'm Being Attacked by
PRISONER.IANA.ORG!", PRISONER.IANA.ORG!",
draft-ietf-dnsop-as112-under-attack-help-help-00 (work in draft-ietf-dnsop-as112-under-attack-help-help-01 (work in
progress), February 2007. progress), November 2007.
[RFC 3330] [RFC3330] "Special-Use IPv4 Addresses", RFC 3330, September 2002.
"Special-Use IPv4 Addresses", RFC 3330, September 2002.
[RFC 3849] [RFC3849] 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-07.txt A.1. draft-ietf-dnsop-default-local-zones-08.txt
editorial, reference updates
A.2. draft-ietf-dnsop-default-local-zones-07.txt
none, expiry prevention none, expiry prevention
A.2. draft-ietf-dnsop-default-local-zones-06.txt A.3. draft-ietf-dnsop-default-local-zones-06.txt
add IPv6 example prefix add IPv6 example prefix
A.3. draft-ietf-dnsop-default-local-zones-05.txt A.4. draft-ietf-dnsop-default-local-zones-05.txt
none, expiry prevention none, expiry prevention
A.4. draft-ietf-dnsop-default-local-zones-04.txt A.5. 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.5. draft-ietf-dnsop-default-local-zones-03.txt A.6. 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.6. draft-ietf-dnsop-default-local-zones-02.txt A.7. draft-ietf-dnsop-default-local-zones-02.txt
RNAME now "nobody.invalid." RNAME now "nobody.invalid."
Revised language. Revised language.
A.7. draft-ietf-dnsop-default-local-zones-01.txt A.8. 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.8. draft-ietf-dnsop-default-local-zones-00.txt A.9. 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.9. draft-andrews-full-service-resolvers-03.txt A.10. draft-andrews-full-service-resolvers-03.txt
Added "Proposed Status". Added "Proposed Status".
A.10. draft-andrews-full-service-resolvers-02.txt A.11. 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
 End of changes. 39 change blocks. 
111 lines changed or deleted 104 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/