draft-ietf-dnsop-default-local-zones-01.txt   draft-ietf-dnsop-default-local-zones-02.txt 
Network Working Group M. Andrews Network Working Group M. Andrews
Internet-Draft ISC Internet-Draft ISC
Intended status: Best Current March 2, 2007 Intended status: Best Current June 8, 2007
Practice Practice
Expires: September 3, 2007 Expires: December 10, 2007
Locally-served DNS Zones Locally-served DNS Zones
draft-ietf-dnsop-default-local-zones-01 draft-ietf-dnsop-default-local-zones-02
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 September 3, 2007. This Internet-Draft will expire on December 10, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
Practice has shown that there are a number of DNS zones all iterative Experience has shown that there are a number of DNS zones all
resolvers and recursive nameservers should, unless configured iterative resolvers and recursive nameservers should, unless
otherwise, automatically serve. RFC 4193 already specifies that this configured otherwise, automatically serve. RFC 4193 specifies that
should occur for D.F.IP6.ARPA. This document extends the practice to this should occur for D.F.IP6.ARPA. This document extends the
cover the IN-ADDR.ARPA zones for RFC 1918 address space and other practice to cover the IN-ADDR.ARPA zones for RFC 1918 address space
well known zones with similar usage constraints. and other well known zones with similar characteristics.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Reserved Words . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Reserved Words . . . . . . . . . . . . . . . . . . . . . . 3
2. Effects on sites using RFC 1918 addresses. . . . . . . . . . . 3 2. Effects on sites using RFC 1918 addresses. . . . . . . . . . . 4
3. Changes to Iterative Resolver Behaviour. . . . . . . . . . . . 4 3. Changes to Iterative Resolver Behaviour. . . . . . . . . . . . 4
4. Lists Of Zones Covered . . . . . . . . . . . . . . . . . . . . 5 4. Lists Of Zones Covered . . . . . . . . . . . . . . . . . . . . 5
4.1. RFC 1918 Zones . . . . . . . . . . . . . . . . . . . . . . 5 4.1. RFC 1918 Zones . . . . . . . . . . . . . . . . . . . . . . 5
4.2. RFC 3330 Zones . . . . . . . . . . . . . . . . . . . . . . 5 4.2. RFC 3330 Zones . . . . . . . . . . . . . . . . . . . . . . 5
4.3. Local IPv6 Unicast Addresses . . . . . . . . . . . . . . . 6 4.3. Local IPv6 Unicast Addresses . . . . . . . . . . . . . . . 6
4.4. IPv6 Locally Assigned Local Addresses . . . . . . . . . . 6 4.4. IPv6 Locally Assigned Local Addresses . . . . . . . . . . 6
4.5. IPv6 Link Local Addresses . . . . . . . . . . . . . . . . 6 4.5. IPv6 Link Local Addresses . . . . . . . . . . . . . . . . 6
5. Zones that are Out-Of-Scope . . . . . . . . . . . . . . . . . 6 5. Zones that are Out-Of-Scope . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . . 9
Appendix A. Change History [To Be Removed on Publication] . . . . 9 Appendix A. Change History [To Be Removed on Publication] . . . . 9
A.1. draft-ietf-dnsop-default-local-zones-01.txt . . . . . . . 9 A.1. draft-ietf-dnsop-default-local-zones-02.txt . . . . . . . 9
A.2. draft-ietf-dnsop-default-local-zones-00.txt . . . . . . . 9 A.2. draft-ietf-dnsop-default-local-zones-01.txt . . . . . . . 9
A.3. draft-andrews-full-service-resolvers-03.txt . . . . . . . 9 A.3. draft-ietf-dnsop-default-local-zones-00.txt . . . . . . . 9
A.4. draft-andrews-full-service-resolvers-02.txt . . . . . . . 9 A.4. draft-andrews-full-service-resolvers-03.txt . . . . . . . 9
A.5. draft-andrews-full-service-resolvers-02.txt . . . . . . . 9
Appendix B. Proposed Status [To Be Removed on Publication] . . . 9 Appendix B. Proposed Status [To Be Removed on Publication] . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . . . . 10 Intellectual Property and Copyright Statements . . . . . . . . . . 11
1. Introduction 1. Introduction
Practice 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 all iterative resolvers and recursive nameservers should, 1035] zones that all iterative resolvers and recursive nameservers
unless configured otherwise, automatically serve. These zones SHOULD, unless intentionally configured otherwise, automatically
include, but are not limited to, the IN-ADDR.ARPA zones for the serve. These zones include, but are not limited to, the IN-ADDR.ARPA
address space allocated by [RFC 1918] and the IP6.ARPA zones for zones for the address space allocated by [RFC 1918] and the IP6.ARPA
locally assigned local IPv6 addresses, [RFC 4193]. zones for locally assigned unique local IPv6 addresses, [RFC 4193].
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 sacrificial name servers instructions to restrict them, and because it has therefore become
have been deployed to protect the immediate parent name servers for necessary to deploy sacrificial name servers to to protect the
these zones from excessive, unintentional, query load [AS112]. There immediate parent name servers for these zones from excessive,
is every expectation that the query load will continue to increase unintentional, query load [AS112]. There is every expectation that
unless steps are taken as outlined here. the query load will continue to increase unless steps are taken as
outlined here.
Additionally, queries from clients behind badly configured firewalls Additionally, queries from clients behind badly configured firewalls
that allow outgoing queries but drop responses for these name spaces that allow outgoing queries for these name spaces but drop the
also puts a significant load on the root servers. They also cause responses put a significant load on the root servers. They also
operational load for the root server operators as they have to reply cause operational load for the root server operators as they have to
to queries about why the root servers are "attacking" these clients. reply to queries about why the root servers are "attacking" these
Changing the default configuration will address all these issues for clients. Changing the default configuration will address all these
the zones listed below in Section 4. issues for the zones listed in Section 4.
[RFC 4193] already recommends that queries for D.F.IP6.ARPA be [RFC 4193] recommends that queries for D.F.IP6.ARPA be handled
handled locally. This document extends the recommendation to cover locally. This document extends the recommendation to cover the IN-
the IN-ADDR.ARPA zones for [RFC 1918] and other well known IN- ADDR.ARPA zones for [RFC 1918] and other well known IN-ADDR.ARPA and
ADDR.ARPA and IP6.ARPA zones for which queries should not appear on IP6.ARPA zones for which queries should not appear on the public
the public Internet. Internet.
It is hoped that by doing this the number of sacrificial servers It is hoped that by doing this the number of sacrificial servers
[AS112] will not have to be increased and may in time be reduced. [AS112] will not have to be increased, and may in time be reduced.
It should also help DNS responsiveness for sites which are using [RFC This recommendation should also help DNS responsiveness for sites
1918] addresses but do not follow the last paragraph in section 3 of which are using [RFC 1918] addresses but do not follow the last
[RFC 1918]. paragraph in Section 3 of [RFC 1918].
1.1. Reserved Words 1.1. Reserved Words
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].
2. Effects on sites using RFC 1918 addresses. 2. Effects on sites using RFC 1918 addresses.
For most sites using [RFC 1918] addresses, the changes here will have For most sites using [RFC 1918] addresses, the changes here will have
little or no detrimental effect. If the site does not already have little or no detrimental effect. If the site does not already have
the reverse tree populated the only effect will be that the answers the reverse tree populated the only effect will be that the name
are generated locally rather than remotely. error responses will be generated locally rather than remotely.
For sites that do have the reverse tree populated, most will either For sites that do have the reverse tree populated, most will either
have a local copy of the zones or will be forwarding the queries to have a local copy of the zones or will be forwarding the queries to
servers which have local copies of the zone. In either case the servers which have local copies of the zone. Therefore this
local resolver has a pre-existing configuration for the namespace and recommendation will not be relevant.
won't add the automatic zone.
The main impact will be felt at sites that make use of delegation for The most significant impact will be felt at sites that make use of
reverse lookups for [RFC 1918] addresses and have populated these delegations for [RFC 1918] addresses and have populated these zones.
zones. Typically, such sites will be fully disconnected from the These sites will need to override the default configuration expressed
Internet and have their own root servers for their own non-Internet in this document to allow resolution to continue. Typically, such
DNS tree. These sites will need to override the default sites will be fully disconnected from the Internet and have their own
configuration expressed in this document to allow resolution to root servers for their own non-Internet DNS tree.
continue.
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
name errors (RCODE=3) for queries within the lists of zones covered name errors (RCODE=3) for queries within the zones in Section 4, with
below, with the obvious exception of queries for the zone name itself the obvious exception of queries for the zone name itself where SOA,
where SOA, NS and "no data" responses will be returned as appropriate NS and "no data" responses will be returned as appropriate to the
to the query type. One common way to do this is to serve empty (SOA query type. One common way to do this is to serve empty (SOA and NS
and NS only) zones. only) zones.
A implementation doing this MUST provide a mechanism to disable this An implementation of this recommendation MUST provide a mechanism to
new behaviour, preferably on a zone by zone basis. disable this new behaviour, and SHOULD do so on a zone 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 leakage to the public Internet servers. This document detect leakage to the public Internet servers. This document
recommends that the NS record defaults to the name of the zone and recommends that the NS record defaults to the name of the zone and
the SOA MNAME defaults to the name of the only NS RR's target. The the SOA MNAME defaults to the name of the only NS RR's target. The
SOA RNAME should default to ".". Implementations SHOULD provide a SOA RNAME should default to "nobody.invalid." [RFC 2606].
mechanism to set these values. No address records need to be Implementations SHOULD provide a mechanism to set these values. No
provided for the name server. address records need to be provided for the name server.
Below is a example of a generic empty zone in master file format. It Below is an example of a generic empty zone in master file format.
will produce a negative cache ttl of 3 hours. It will produce a negative cache TTL of 3 hours.
@ 10800 IN SOA @ . 1 3600 1200 604800 10800 @ 10800 IN SOA @ nobody.invalid. 1 3600 1200 604800 10800
@ 10800 IN NS @ @ 10800 IN NS @
The SOA RR is needed to support negative caching [RFC 2308] of name The SOA RR is needed to support negative caching [RFC 2308] of name
error responses and to point clients to the primary master for DNS error responses and to point clients to the primary master for DNS
dynamic updates. dynamic updates.
SOA values of particular importance are the MNAME, the SOA RR's TTL SOA values of particular importance are the MNAME, the SOA RR's TTL
and the negTTL value. Both TTL values SHOULD match. The rest of the and the negTTL value. Both TTL values SHOULD match. The rest of the
SOA timer values may be chosen arbitrarily since it they are not SOA timer values MAY be chosen arbitrarily since it they are not
intended to control any zone transfer activity. intended to control any zone transfer activity.
The NS RR is needed as some UPDATE clients use NS queries to discover The NS RR is needed as some UPDATE clients use NS queries to discover
they zone to be updated. Having no address records for the name the zone to be updated. Having no address records for the name
server should abort UPDATE processing in the client server should abort UPDATE processing in the client.
4. Lists Of Zones Covered 4. Lists Of Zones Covered
The lists below are expected to seed a IANA registry.
4.1. RFC 1918 Zones 4.1. RFC 1918 Zones
10.IN-ADDR.ARPA 10.IN-ADDR.ARPA
16.172.IN-ADDR.ARPA 16.172.IN-ADDR.ARPA
17.172.IN-ADDR.ARPA 17.172.IN-ADDR.ARPA
18.172.IN-ADDR.ARPA 18.172.IN-ADDR.ARPA
19.172.IN-ADDR.ARPA 19.172.IN-ADDR.ARPA
20.172.IN-ADDR.ARPA 20.172.IN-ADDR.ARPA
21.172.IN-ADDR.ARPA 21.172.IN-ADDR.ARPA
22.172.IN-ADDR.ARPA 22.172.IN-ADDR.ARPA
skipping to change at page 5, line 44 skipping to change at page 5, line 43
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
See [RFC 3330]. See [RFC 3330].
0.IN-ADDR.ARPA /* IPv4 "THIS" NETWORK */ +------------------------------+------------------------------+
127.IN-ADDR.ARPA /* IPv4 LOOP-BACK NETWORK */ | Zone | Description |
254.169.IN-ADDR.ARPA /* IPv4 LINK LOCAL */ +------------------------------+------------------------------+
2.0.192.IN-ADDR.ARPA /* IPv4 TEST NET */ | 0.IN-ADDR.ARPA | /* IPv4 "THIS" NETWORK */ |
255.255.255.255.IN-ADDR.ARPA /* IPv4 BROADCAST */ | 127.IN-ADDR.ARPA | /* IPv4 LOOP-BACK NETWORK */ |
| 254.169.IN-ADDR.ARPA | /* IPv4 LINK LOCAL */ |
| 2.0.192.IN-ADDR.ARPA | /* IPv4 TEST NET */ |
| 255.255.255.255.IN-ADDR.ARPA | /* IPv4 BROADCAST */ |
+------------------------------+------------------------------+
4.3. Local IPv6 Unicast Addresses 4.3. Local IPv6 Unicast Addresses
See [RFC 4291], sections 2.4, 2.5.2 and 2.5.3. See [RFC 4291], Sections 2.4, 2.5.2 and 2.5.3.
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.IP 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.IP
6.ARPA 6.ARPA
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.IP 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.IP
6.ARPA 6.ARPA
4.4. IPv6 Locally Assigned Local Addresses 4.4. IPv6 Locally Assigned Local Addresses
See [RFC 4193]. See [RFC 4193].
D.F.IP6.ARPA D.F.IP6.ARPA
4.5. IPv6 Link Local Addresses 4.5. IPv6 Link Local Addresses
See [RFC 4291], sections 2.4 and 2.5.6. See [RFC 4291], Sections 2.4 and 2.5.6.
8.E.F.IP6.ARPA 8.E.F.IP6.ARPA
9.E.F.IP6.ARPA 9.E.F.IP6.ARPA
A.E.F.IP6.ARPA A.E.F.IP6.ARPA
B.E.F.IP6.ARPA B.E.F.IP6.ARPA
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.57, and IPv6 IPv6 site-local addresses, [RFC 4291] Sections 2.4 and 2.57, and IPv6
Globally Assigned Local [RFC 4193] addresses are not covered here. Centrally Assigned Local [RFC 4193] addresses are not covered here.
It is expected that IPv6 site-local addresses will be self correcting It is expected that IPv6 site-local addresses will be self correcting
as IPv6 implementations remove support for site-local addresses. as IPv6 implementations remove support for site-local addresses.
However, sacrificial servers for C.E.F.IP6.ARPA to F.E.F.IP6.ARPA may However, sacrificial servers for C.E.F.IP6.ARPA through
still need to be deployed in the short term if the traffic becomes F.E.F.IP6.ARPA may still need to be deployed in the short term if the
excessive. traffic becomes excessive.
For IPv6 Globally Assigned Local addresses [RFC 4291] there has been For IPv6 Centrally Assigned Local addresses (L = 0) [RFC 4193], there
no decision made about whether the registries will provide has been no decision made about whether the registries will provide
delegations in this space or not. If they don't, then C.F.IP6.ARPA delegations in this space or not. If they don't, then C.F.IP6.ARPA
will need to be added to the list above. If they do, then registries will need to be added to the list in Section 4.4. If they do, then
will need to take steps to ensure that name servers are provided for registries will need to take steps to ensure that name servers are
these addresses. provided for these addresses.
This document is also ignoring IP6.INT. IP6.INT has been wound up This document also ignores IP6.INT. IP6.INT has been wound up with
with only legacy resolvers now generating reverse queries under only legacy resolvers now generating reverse queries under IP6.INT.
IP6.INT.
This document has also deliberately ignored names immediately under This document has also deliberately ignored names immediately under
the root. While there is a subset of queries to the roots which the root. While there is a subset of queries to the roots which
could be addressed using the techniques described here (e.g. .local could be addressed using the techniques described here (e.g. .local,
and IPv4 addresses) there is also a vast amount of traffic that .workgroup and IPv4 addresses), there is also a vast amount of
requires a different strategy (e.g. lookups for unqualied hostnames, traffic that requires a different strategy (e.g. lookups for
IPv6 addresses). unqualified hostnames, IPv6 addresses).
6. IANA Considerations 6. IANA Considerations
This document recommends that IANA establish a registry of zones This document requests that IANA establish a registry of zones which
which require this default behaviour, the initial contents of which require this default behaviour. The initial contents of which are in
are in Section 4. More zones are expected to be added, and possibly Section 4. Implementors are encouraged to check this registry and
deleted from this registry over time. Name server implementors are adjust their implementations to reflect changes therein.
encouraged to 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 Consensus" as per [RFC
2434] or IETF Review in 2434bis. 2434] or IETF Review in 2434bis.
IANA should co-ordinate with the RIRs and ICANN to ensure the DNSSEC ICANN should co-ordinate with the RIRs to ensure that DNSSEC
deployment in the reverse trees that these zone are delegated in a deployment in the reverse trees that these zone are delegated from
unsecure manner as per Security Considerations. happens in 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
service disruption until full service resolvers have been re- service disruption until full service resolvers have been re-
configured. configured.
When DNSSEC is deployed within the IN-ADDR.ARPA and IP6.ARPA As DNSSEC is deployed within the IN-ADDR.ARPA and IP6.ARPA
namespaces, the zones listed above will need to be delegated as namespaces, the zones listed above will need to be delegated as
insecure delegations. This will allow DNSSEC validation to succeed insecure delegations. This will allow DNSSEC validation to succeed
for queries in these spaces despite not being answered from the for queries in these spaces despite not being answered from the
delegated servers. delegated servers.
It is recommended that sites actively using these namespaces secure It is recommended that sites actively using these namespaces secure
them using DNSSEC [RFC 4035] by publishing and using DNSSEC trust them using DNSSEC [RFC 4035] by publishing and using DNSSEC trust
anchors. This will protect the clients from accidental leakage of anchors. This will protect the clients from accidental leakage of
unsigned answers from the Internet. unsigned answers from the Internet.
skipping to change at page 8, line 35 skipping to change at page 8, line 35
[RFC 2308] [RFC 2308]
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] [RFC 2434]
Narten, T. and H. Alvestrand, "Guidelines for Writing an Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[RFC 3330] [RFC 2606]
"Special-Use IPv4 Addresses", RFC 3330, September 2002. Eastlake, D. and A. Panitz, "Reserved Top Level DNS
Names", BCP 32, RFC 2606, June 1999.
[RFC 4035] [RFC 4035]
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 4193]
Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
Addresses", RFC 4193, October 2005.
[RFC 4291] [RFC 4291]
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.
9.2. Informative References 9.2. Informative References
[AS112] "AS112 Project", <http://as112.net/>. [AS112] "AS112 Project", <http://as112.net/>.
[RFC 4193] [RFC 3330]
Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast "Special-Use IPv4 Addresses", RFC 3330, September 2002.
Addresses", RFC 4193, October 2005.
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-01.txt A.1. draft-ietf-dnsop-default-local-zones-02.txt
RNAME now "nobody.invalid."
Revised language.
A.2. 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.2. draft-ietf-dnsop-default-local-zones-00.txt A.3. 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.3. draft-andrews-full-service-resolvers-03.txt A.4. draft-andrews-full-service-resolvers-03.txt
Added "Proposed Status". Added "Proposed Status".
A.4. draft-andrews-full-service-resolvers-02.txt A.5. 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. 45 change blocks. 
117 lines changed or deleted 126 lines changed or added

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