One document matched: draft-ietf-dnsext-dns-protocol-profile-01.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY I-D.ietf-dnsext-rfc2671bis-edns0 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-dnsext-rfc2671bis-edns0.xml">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC4307 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4307.xml">
<!ENTITY RFC0805 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0805.xml">
<!ENTITY RFC0811 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0811.xml">
<!ENTITY RFC0819 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0819.xml">
<!ENTITY RFC0881 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0881.xml">
<!ENTITY RFC0882 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0882.xml">
<!ENTITY RFC0883 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0883.xml">
<!ENTITY RFC0897 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0897.xml">
<!ENTITY RFC0920 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0920.xml">
<!ENTITY RFC0921 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0921.xml">
<!ENTITY RFC0973 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0973.xml">
<!ENTITY RFC0974 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.0974.xml">
<!ENTITY RFC1032 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1032.xml">
<!ENTITY RFC1033 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1033.xml">
<!ENTITY RFC1034 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1034.xml">
<!ENTITY RFC1035 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1035.xml">
<!ENTITY RFC1101 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1101.xml">
<!ENTITY RFC1122 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1122.xml">
<!ENTITY RFC1123 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1123.xml">
<!ENTITY RFC1178 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1178.xml">
<!ENTITY RFC1183 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1183.xml">
<!ENTITY RFC1348 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1348.xml">
<!ENTITY RFC1386 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1386.xml">
<!ENTITY RFC1464 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1464.xml">
<!ENTITY RFC1480 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1480.xml">
<!ENTITY RFC1535 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1535.xml">
<!ENTITY RFC1536 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1536.xml">
<!ENTITY RFC1537 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1537.xml">
<!ENTITY RFC1591 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1591.xml">
<!ENTITY RFC1611 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1611.xml">
<!ENTITY RFC1612 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1612.xml">
<!ENTITY RFC1637 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1637.xml">
<!ENTITY RFC1664 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1664.xml">
<!ENTITY RFC1706 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1706.xml">
<!ENTITY RFC1712 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1712.xml">
<!ENTITY RFC1713 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1713.xml">
<!ENTITY RFC1794 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1794.xml">
<!ENTITY RFC1811 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1811.xml">
<!ENTITY RFC1816 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1816.xml">
<!ENTITY RFC1876 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1876.xml">
<!ENTITY RFC1886 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1886.xml">
<!ENTITY RFC1912 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1912.xml">
<!ENTITY RFC1956 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1956.xml">
<!ENTITY RFC1982 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1982.xml">
<!ENTITY RFC1995 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1995.xml">
<!ENTITY RFC1996 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1996.xml">
<!ENTITY RFC2010 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2010.xml">
<!ENTITY RFC2052 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2052.xml">
<!ENTITY RFC2053 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2053.xml">
<!ENTITY RFC2065 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2065.xml">
<!ENTITY RFC2100 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2100.xml">
<!ENTITY RFC2136 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2136.xml">
<!ENTITY RFC2137 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2137.xml">
<!ENTITY RFC2142 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2142.xml">
<!ENTITY RFC2146 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2146.xml">
<!ENTITY RFC2163 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2163.xml">
<!ENTITY RFC2168 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2168.xml">
<!ENTITY RFC2181 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2181.xml">
<!ENTITY RFC2182 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2182.xml">
<!ENTITY RFC2219 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2219.xml">
<!ENTITY RFC2230 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2230.xml">
<!ENTITY RFC2240 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2240.xml">
<!ENTITY RFC2247 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2247.xml">
<!ENTITY RFC2276 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2276.xml">
<!ENTITY RFC2307 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2307.xml">
<!ENTITY RFC2308 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2308.xml">
<!ENTITY RFC2317 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2317.xml">
<!ENTITY RFC2345 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2345.xml">
<!ENTITY RFC2352 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2352.xml">
<!ENTITY RFC2377 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2377.xml">
<!ENTITY RFC2517 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2517.xml">
<!ENTITY RFC2535 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2535.xml">
<!ENTITY RFC2536 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2536.xml">
<!ENTITY RFC2537 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2537.xml">
<!ENTITY RFC2538 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2538.xml">
<!ENTITY RFC2539 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2539.xml">
<!ENTITY RFC2540 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2540.xml">
<!ENTITY RFC2541 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2541.xml">
<!ENTITY RFC2606 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2606.xml">
<!ENTITY RFC2671 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2671.xml">
<!ENTITY RFC2672 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2672.xml">
<!ENTITY RFC2673 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2673.xml">
<!ENTITY RFC2694 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2694.xml">
<!ENTITY RFC2782 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2782.xml">
<!ENTITY RFC2825 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2825.xml">
<!ENTITY RFC2826 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2826.xml">
<!ENTITY RFC2832 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2832.xml">
<!ENTITY RFC2845 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2845.xml">
<!ENTITY RFC2870 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2870.xml">
<!ENTITY RFC2874 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2874.xml">
<!ENTITY RFC2915 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2915.xml">
<!ENTITY RFC2916 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2916.xml">
<!ENTITY RFC2929 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2929.xml">
<!ENTITY RFC2930 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2930.xml">
<!ENTITY RFC2931 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2931.xml">
<!ENTITY RFC2937 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2937.xml">
<!ENTITY RFC2972 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2972.xml">
<!ENTITY RFC3007 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3007.xml">
<!ENTITY RFC3008 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3008.xml">
<!ENTITY RFC3071 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3071.xml">
<!ENTITY RFC3090 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3090.xml">
<!ENTITY RFC3110 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3110.xml">
<!ENTITY RFC3123 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3123.xml">
<!ENTITY RFC3152 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3152.xml">
<!ENTITY RFC3197 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3197.xml">
<!ENTITY RFC3225 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3225.xml">
<!ENTITY RFC3226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3226.xml">
<!ENTITY RFC3245 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3245.xml">
<!ENTITY RFC3254 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3254.xml">
<!ENTITY RFC3258 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3258.xml">
<!ENTITY RFC3263 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3263.xml">
<!ENTITY RFC3352 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3352.xml">
<!ENTITY RFC3363 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3363.xml">
<!ENTITY RFC3364 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3364.xml">
<!ENTITY RFC3367 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3367.xml">
<!ENTITY RFC3368 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3368.xml">
<!ENTITY RFC3401 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3401.xml">
<!ENTITY RFC3402 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3402.xml">
<!ENTITY RFC3403 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3403.xml">
<!ENTITY RFC3404 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3404.xml">
<!ENTITY RFC3405 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3405.xml">
<!ENTITY RFC3425 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3425.xml">
<!ENTITY RFC3445 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3445.xml">
<!ENTITY RFC3467 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3467.xml">
<!ENTITY RFC3490 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3490.xml">
<!ENTITY RFC3491 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3491.xml">
<!ENTITY RFC3492 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3492.xml">
<!ENTITY RFC3596 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3596.xml">
<!ENTITY RFC3597 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3597.xml">
<!ENTITY RFC3645 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3645.xml">
<!ENTITY RFC3646 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3646.xml">
<!ENTITY RFC3655 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3655.xml">
<!ENTITY RFC3658 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3658.xml">
<!ENTITY RFC3675 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3675.xml">
<!ENTITY RFC3696 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3696.xml">
<!ENTITY RFC3755 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3755.xml">
<!ENTITY RFC3757 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3757.xml">
<!ENTITY RFC4025 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4025.xml">
<!ENTITY RFC4033 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4033.xml">
<!ENTITY RFC4034 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4034.xml">
<!ENTITY RFC4035 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4035.xml">
<!ENTITY RFC4255 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4255.xml">
<!ENTITY RFC4343 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4343.xml">
<!ENTITY RFC4408 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4408.xml">
<!ENTITY RFC4431 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4431.xml">
<!ENTITY RFC4701 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4701.xml">
<!ENTITY RFC5001 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5001.xml">
]>
<rfc ipr='full3978' docName='draft-ietf-dnsext-dns-protocol-profile-01'>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc toc="yes" ?>
<front>
<title abbrev="The Modern DNS Implementation Guide">
The Modern DNS Implementation Guide
</title>
<author initials="G.G."
surname="Michaelson"
fullname="George Michaelson">
<organization abbrev="APNIC">
Asia Pacific Network Information Centre
</organization>
<address>
<postal>
<street>Level 1, 33 Park Road</street>
<city>Milton</city>
<region>Queensland</region>
<code>4064</code>
<country>AU</country>
</postal>
<phone>+61 7 3858 3100</phone>
<email>ggm@apnic.net</email>
</address>
</author>
<date month='January' year='2008' />
<keyword>I-D</keyword>
<abstract>
<t>A structured catalogue of relevant DNS RFCs is presented
with references to the specific normative sections which should be
followed in a modern DNS implementation.
This document is to be used as guide for DNS implementors,
for testing and compliance of DNS software, and to
help guide DNS standards' advancement.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>As of the time of writing, the Domain Name Service (DNS)
is almost 25 years old.
In that time a significant amount
of change has occurred in the collection of RFCs which document
how DNS systems should be implemented and operated.</t>
<list style="symbols">
<t>Developers of DNS systems need a single reference which can be
used consistently to review interoperability between implementations
and to guide implementation of DNS systems.</t>
<t>Operators of DNS systems need a reference which can be
used to understand existing DNS systems conformance
and to guide acquisition and management of new DNS systems.</t>
</list>
<t>Accordingly, the DNS Extensions (DNSEXT) working group has been asked
by the Real-time Applications and Infrastructure (RAI)
Area Directors (AD) and others
to document what the basic requirements for
'modern' DNS implementations are.</t>
<t>By reviewing the normative sections of the 'head' documents
(i.e. the documents which are current, have not been superseded
by another document, explicitly deprecated or fallen
into disrepair) the DNSEXT working group identified the set
of references into those documents which specify all
of the 'directives' which define how the 'modern' DNS system should work.</t>
<t>In the process of review, areas of attention were identified.
These represent normative directing text(s) in the RFCs, or
the entire RFCs themselves, which required change, to reflect the
current state of the DNS.</t>
<t>During this documents development, areas of standardisation which required
attention were noted, and were addressed in one of the following four ways.</t>
<list style="symbols">
<t>Firstly, if the revisions were simple enough, a -bis process
(where the document is lightly edited to achive the specific desired
changes, and is then published as a complete replacement for the
original) was
used to define the smallest set of changes to the RFC, and a new
version rolled, with the old one deprecated.</t>
<t>Secondly, if the revisions were complex, or so many exist that
a complete re-write would be more effective, a more lengthy process was
used to re-define the complete set of behaviors as a working group
activity. The outcome is the same: A new RFC was created, and the
old RFC can be deprecated.</t>
<t>Thirdly, if the RFC is no longer held to be relevant, it was
deprecated without replacement.</t>
<t>Lastly, if the change was too small to justify revision of the head document
then the inclusion of normative language was appropriate in this document. For instance, allowed
interpretations of pre-RFC2119 non-normative texts.</t>
</list>
<t>This document is not intended to be used to guide operation of DNS systems, nor to guide
creation and maintenance of DNS zones, or the DNS namespace. In particular, normative directions
on features which must be implemented may still be, (in many cases) disabled under operational control.</t>
<section title="Key Approach">
<t>Normally in an RFC or draft, a section of boilerplate directs
the meaning of normative language and how it relates to the
standard usages. In that respect, this document is no different.
</t>
<t>However, as a general principle, this document seeks to avoid
directly creating new normative text. Instead, it is
a collation of references to the normative text of other documents.
</t>
<t>As far as possible, no new normative language should have been created
in this document. Where it is seen, it needs to be clearly understood
to be either derived from a prior document (and referenced accordingly)
or else clearly marked as being originated in this document. </t>
<t>As far as possible, the document should be structured and
maintained in an overall manner which allows it to be subject
to future revision. For example, the likelihood of subsequent
changes to Hash function lifetimes means that it is foreseeable the
documents normative language references to cryptographic algorithms
will require future revision. New developments in DNS will require
consideration for their normative language and should be reviewed
against each section of this document.
</t>
<t>Therefore, this document should be actively maintained, and updated
when a significant body of new DNS developments have occurred,
e.g. to reflect changes in DNS standardisation.</t>
</section>
<section title="Normative Language Usage">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in
<xref format="none" target="RFC2119">RFC 2119</xref>.
</t>
<t>Because of the new normative language review, introduced in
<xref format="none" target='RFC4307'>RFC 4307</xref>
it was also possible to refine normative language in this document, as a "step
along the road" to final resolution. Therefore some instances of
normative language in this document revise the reference by changing a
MUST into a MUST-, or a SHOULD into a SHOULD+ reference. This provides a
signal that implementors need to be aware of change in the compliance status
of the behaviour under consideration, and therefore need to be working towards
a future goal of a stronger (or weaker) normative binding in that area.</t>
<t>Since the normative language includes SHOULD
and MAY directives, DNS Implementors are strongly encouraged to
identify completely all optional elements of their systems, including
both positive (MAY and SHOULD directives which have been followed)
as well as negative (MAY and SHOULD directives which have been ignored).</t>
</section>
</section>
<section title="General Considerations">
<t>{new normative language}
This document catalogs the compliance
issues for an implementation of any component of the DNS. Implementors
MUST adhere to the collected state of these directives to be considered
fully standards compliant.</t>
<t>{not normative}
Because important DNS RFCs pre-date
<xref format="none" target="RFC2119">RFC 2119</xref>
this document explicitly shows
where their text is to be re-interpreted in line with RFC2119 normative language</t>
<t>The document is organized into five major
sections, addressing Common Requirements, Authoritative Servers, Stub Resolvers, Recursive
Resolvers and Middle-boxes. DNS Implementors should read all sections
carefully since subsequent sections refer back to prior sections and
catalog variances as well as new requirements. </t>
<t>Application specific considerations are not normatively addressed
by this document. Where mentioned, the text should be interpreted as
guidance only.</t>
</section>
<section title="Common Requirements">
<t>{new normative language. the -bis document needs its reference confirmed.}
EDNS0 MUST be implemented by all DNS systems. Its use is an operational decision.
This is is line with [<xref format="none" target="RFC2671">RFC 2671</xref>] and its -bis document.</t>
<t>{new normative language}
Unknown RRtypes MUST be preserved.
This is in line with [<xref format="none" target="RFC3597">RFC 3597 (Section 3)</xref>].
which states:
<list>
<t>To enable new RR types to be deployed without server changes, name
servers and resolvers MUST handle RRs of unknown type
transparently. That is, they must treat the RDATA section of
such RRs as unstructured binary data, storing and transmitting
it without change.</t>
</list></t>
<t>{new normative language}
The DNS Database consistency MUST be maintained. Data MUST NOT leak between zones.
{needs normative reference}</t>
<t>{non normative}
The following documents define registries of DNS RR types. All new record types can be treated as unknown RRs as above.
{list of RR-types refs. Just the IANA registry, rather than all RFCs has been suggested by Olafur}</t>
<t>{new normative language}
Processing of DNS names in US-ASCII range MUST be case-insensitive.
[<xref format="none" target="RFC4343">RFC 4343</xref>].
also see [<xref format="none" target="RFC1035">RFC 1035 (2.3.3)</xref>]
and [<xref format="none" target="RFC1034">RFC 1034 (3.1)</xref>].</t>
</section>
<section title="Authoritative Servers">
<t>{Much of this text comes from <xref target='NLNet-1'/>. These requirements are in order of importance: }</t>
<section title="Zones">
<section title="Zone Contents">
<t>{non normative}
The zone file format as specified in
[<xref format="none" target="RFC1035">RFC 1035 (5.1)</xref>] is optional.
It is used as a common presentation format only. </t>
<t>{new normative language: needs RFC reference}
A served zone SHOULD not contain errors, or produce unpredictable results when
RRs that are obsolete, or not implemented are encountered. </t>
<t>Zones MUST follow the rules as defined in
[<xref format="none" target="RFC1035">RFC 1035 (5.2)</xref>]
and subsequent revisions by the following RFCs:
<list>
<t>[<xref format="none" target="RFC1101">RFC 1101</xref>]</t>
<t>[<xref format="none" target="RFC1122">RFC 1122</xref>]</t>
<t>[<xref format="none" target="RFC1183">RFC 1183</xref>]</t>
<t>[<xref format="none" target="RFC1706">RFC 1706</xref>]</t>
<t>[<xref format="none" target="RFC1876">RFC 1876</xref>]</t>
<t>[<xref format="none" target="RFC1982">RFC 1982</xref>]</t>
<t>[<xref format="none" target="RFC1995">RFC 1995</xref>]</t>
<t>[<xref format="none" target="RFC1996">RFC 1996</xref>]</t>
<t>[<xref format="none" target="RFC2136">RFC 2136</xref>]</t>
<t>[<xref format="none" target="RFC2137">RFC 2137</xref>]</t>
<t>[<xref format="none" target="RFC2181">RFC 2181</xref>]</t>
<t>[<xref format="none" target="RFC2308">RFC 2308</xref>]</t>
<t>[<xref format="none" target="RFC2535">RFC 2535</xref>] {this needs to be reviewed, and probably updated to a new RFC}</t>
<t>[<xref format="none" target="RFC2782">RFC 2782</xref>]</t>
<t>[<xref format="none" target="RFC2845">RFC 2845</xref>]</t>
<t>[<xref format="none" target="RFC3425">RFC 3425</xref>]</t>
<t>[<xref format="none" target="RFC3658">RFC 3658</xref>]</t>
<t>[<xref format="none" target="RFC4034">RFC 4034</xref>]</t>
<t>[<xref format="none" target="RFC4035">RFC 4035</xref>]</t>
</list>
</t>
<t>The following text has been extracted from
[<xref format="none" target="RFC1035">RFC 1035 (section 5.2)</xref>]
and
[<xref format="none" target="RFC2181">RFC 2181 (section 5.2)</xref>]
and re-written using normative language specified in
<xref format="none" target="RFC2119">RFC 2119</xref></t>
<t>[<xref format="none" target="RFC1035">RFC 1035 (Section 5.2)</xref>] Rules governing zone content</t>
<t>{new normative text}</t>
<list style="numbers">
<t>All RRs in the zone MUST have the same class.
[<xref format="none" target="RFC1035">RFC 1035 (Section 5.2 rule 1)</xref>] </t>
<t>Exactly one SOA RR MUST be present at the top of the zone (meaning the delegation point).
[<xref format="none" target="RFC1035">RFC 1035 (Section 5.2 rule 2)</xref>].</t>
<t>If delegations are present and glue information is required, it SHOULD be present.
[<xref format="none" target="RFC2181">RFC 2181 (Section 5.2 para 2)</xref>].</t>
<t>The TTLs of all RRs in an RRset MUST be the same.
[<xref format="none" target="RFC2181">RFC 2181 (Section 5.2)</xref>].</t>
<t>You must adhere to
[<xref format="none" target="RFC2672">RFC 2672 (Section 3)</xref>]
and
{reference will need updating to published RFC}
<xref target="I-D.ietf-dnsext-rfc2671bis-edns0"/>
in respect of data conflicting with DNAME.</t>
<t>There MUST be no data at the same name as a CNAME,
and only DNSSEC records with a CNAME.
[<xref format="none" target="RFC4034">RFC 4034</xref>]
[<xref format="none" target="RFC4035">RFC 4035</xref>].</t>
<t>{new non-normative informational text}
Information present outside of the authoritative nodes in the zone is glue information,
rather than the result of an origin or similar error.
</t>
</list>
</section>
<section title="Zone synchronisation">
<section title="Timeout management">.
<t>{referencing RFC details needed} Timeouts on the SOAs for secondary zones according to [RFC...].</t>
</section>
</section>
</section>
<section title="Server and connection management">
<t>DNS servers MUST comply with [<xref format="none" target="RFC2181">RFC 2181 (4)</xref>].</t>
<section title="UDP">
<t>The server MUST listen to UDP on port 53 [<xref format="none" target="RFC2181">RFC 2181 (4)</xref>].</t>
<t> { new normative language, but implied from EDNS0 is a MUST. should have an RFC reference}
Large packet sizes SHOULD be supported. </t>
</section>
<section title="TCP">
<t> {new normative language, maybe.. }
The server MAY accept TCP connections. {? what is the correct wording and reference?} </t>
<t> Note that there may be one or more DNS messages in the stream.
Each message is prefixed with a two byte length field which gives the
message length, excluding the two byte length field.
[<xref format="none" target="RFC1035">RFC 1035 (4.2.2)</xref>].</t>
</section>
<section title="TCP Connection Management">
<t>The following text has been extracted from
[<xref format="none" target="RFC1035">RFC 1035 (section 4.2.2)</xref>]
and re-written using normative language specified in
[<xref format="none" target="RFC2119">RFC 2119</xref>].</t>
<t> [<xref format="none" target="RFC1035">RFC 1035 (4.2.2.)</xref>] TCP Usage</t>
<t>{new normative text}</t>
<t>
<list style="symbols">
<t> the server SHOULD not block other activities waiting for TCP data</t>
<t> The server SHOULD assume that the client will initiate
connection closing and SHOULD delay closing its end of the
connection until all outstanding client requests have been
satisfied.</t>
<t>{ this is 25 year old advice. is this still relevant or what should it be? }
For closing dormant connections the timeout should be in the order of 2 minutes.</t>
</list>
</t>
</section>
</section>
<section title="DNS Message processing">
<t>DNS messages should be processed in line with the precepts of
[<xref format="none" target="RFC1034">RFC 1034 (Section 4.3.1)</xref>].</t>
<t>{ new normative language. there is no explicit reference in existing RFCs to the following}
Non parsable messages SHOULD be replied to with a FORMERR.</t>
<t>When UDP transport is used, each UDP datagram MUST contain exactly
one DNS Message.
UDP datagrams SHOULD be constructed such that they contain no data
following the DNS Message.
If present, any additional data present following the DNS Message
MUST be ignored.</t>
<list style="symbols">
<t> Incoming DNS messages with the QR bit set to 1 (response) are discarded.
[<xref format="none" target="RFC1035">RFC 1035 (sect 7.3)</xref>].</t>
<t> RD is copied into the response [<xref format="none" target="RFC1035">RFC 1035 (4.1.1)</xref>]
the RA bit is set to 0 and the QUERYID is copied into the response message as follows:
<list style="symbols">
<t>OPCODE 0 (QUERY) MUST be supported [<xref format="none" target="RFC1035">RFC 1035</xref>].</t>
<t>OPCODE 1 (IQUERY) MUST result in RCODE=4 NOTIMPL [<xref format="none" target="RFC3425">RFC 3425</xref>].
{has this actually been deprecated?}</t>
<t>OPCODE 2 (STATUS) MUST result in RCODE=4 NOTIMPL [<xref format="none" target="RFC1035">RFC 1035</xref>].
{new normative language, not explicitly brought out}</t>
<t>OPCODE 3 (RESERVED) MUST result in RCODE=4 NOTIMPL {requires an RFC reference}</t>
<t>{new normative language} The following are optional but recommended techologies,
which SHOULD be implemented, rather than through use of NOTIMPL</t>
<list style="symbols">
<t>OPCODE 4 (NOTIFY) SHOULD+ be supported [<xref format="none" target="RFC1995">RFC 1995</xref>].</t>
<t>OPCODE 5 (UPDATE) SHOULD+ be supported [<xref format="none" target="RFC2136">RFC 2136 (sect 3)</xref>].</t>
</list>
</list>
</t>
<t>{no RFC/normatives found, need guidance}
<list style="symbols">
<t> AA bit in query packet SHOULD be ignored.</t>
<t> TC bit set in a query packet SHOULD+ be answered with FORMERR.</t>
<t> The TC bit answer FORMERR MUST not have the TC bit set.</t>
<t> RCODES SHOULD ignored.</t>
<t> QDCOUNT!=1 SHOULD result in RCODE=1 FORMERR</t>
</list>
</t>
<t> Presence of OPT RR in the ADDITIONAL Section indicates support of EDNS
[<xref format="none" target="RFC2671">RFC 2671 (Sections 4, 5.1)</xref>].
If the VERSION > 0 then the server will respond with an OPT with
RCODE=BADVERSION and VERSION=0 (The server supports EDNS0)
[<xref format="none" target="RFC2671">RFC 2671 (Section 4.6)</xref>].
In further processing ENDS0 support is taken into account.</t>
</list>
</section>
<section title="Further Query processing">.
<section title="Actions based on QTYPE of incoming Query">.
<t>Further processing of the packet is based on the algorithm from
[<xref format="none" target="RFC1034">RFC 1034</xref>]
as modified by [<xref format="none" target="RFC2672">RFC 2672 (4)</xref>].</t>
<t>DNSSEC Considerations follow [<xref format="none" target="RFC4035">RFC 4035</xref>].</t>
</section>
</section>
<section title="Additional Data processing">.
<t>{could be a normative MAY}</t>
<t>Additional data may be added as long as there is space in the packet. {need reference} </t>
<t>When processing the additional section priority is as specified in
[<xref format="none" target="RFC2874">RFC 2874 (4)</xref>]
<list style="symbols">
<t> A </t>
<t> AAAA </t>
</list>
</t>
<t>For truncation see section [<xref format="none" target="trnc">Truncation handling</xref>]
</t>
</section>
<section title="Label compression in RDATA">
<t>[<xref format="none" target="RFC1035">RFC 1035 (section 3.3. and 4.4.1)</xref>]
("Pointers can only be used for occurrences of a domain name where the format is not
class specific.")</t>
<t> Do label compression for labels in rdata
for which this is specifically mentioned in the RFC defining the RR.</t>
<list style="symbols">
<t>NS, SOA, CNAME, and PTR [<xref format="none" target="RFC1035">RFC 1035 (3.3) </xref>].</t>
<t>Others defined in [<xref format="none" target="RFC1035">RFC 1035 (3.3)</xref>]are not compressed. </t>
<t>MB, MG, MR, MINFO, MX also have compressed dnames.
These RRs and their compression are described in [<xref format="none" target="RFC1035">RFC 1035</xref>]. </t>
<t>AFSDB, RP, RT [<xref format="none" target="RFC1183">RFC 1183, (Section 1,2 & 3.3.3)</xref>].</t>
<t>You MUST follow the rules in [<xref format="none" target="RFC3597">RFC 3597</xref>]. </t>
</list>
</section>
<section anchor="trnc" title="Truncation handling">
<t> Truncation handling is as specified in [<xref format="none" target="RFC2181">RFC 2181 (9)</xref>].</t>
<t>{TBD normative text for this section. RFC references required.}
If inclusion of a RR set that is REQUIRED in either the answer or
authority section leads to message truncation. The section is left
empty and the truncation (TC) bit is set. If the DO bit is set RRSIG
RRs are required in the answer and authority section.</t>
<t>If inclusion of an RRset in the Additional section is not possible
RRs are omitted one by one. This may lead to incomplete RRsets.
Omission of RRs from the Additional section because of message size
constraints will NOT lead to setting of the TC bit.
[<xref format="none" target="RFC2181">RFC 2181 (9)</xref>].</t>
<t>{RFC references required.} Implementations need to allow for incomplete RRsets in the additional section.</t>
</section>
<section title="NSEC processing">
<t>{section reference required.}
The NSEC record is required to be in the authority section if a QNAME
or a QTYPE cannot be matched [<xref format="none" target="RFC4035">RFC 4035 (section ?)</xref>]. </t>
</section>
<section title="NSID support">
<t>{new non-normative language. This could be normative, in which
case it needs to be decided if its a MAY/SHOULD/SHOULD+/MUST}</t>
<t>An authoritative server may implement DNS Name Server Identifier
(NSID) Option processing. This should be implemented in line with
[<xref format="none" target="RFC5001">RFC 5001 (Section 2.2)</xref>].
</t>
</section>
</section>
<t>{this text needs to be moved out of authoritative servers. Not clear which section its in yet.}
Note that on a QNAME match the NS records are not copied into the AUTH
section (This is a requirement from step 4 'matching down the cache'
from [<xref format="none" target="RFC1034">RFC 1034 (Section 4.3.2)</xref>].
This is a requirement only for caching servers.</t>
<section title="Stub Resolvers">
<t>TBD
</t>
</section>
<section title="Recursive Resolvers">
<t>TBD
</t>
<section title="NSID support">
<t>{new non-normative language. This could be normative, in which
case it needs to be decided if its a MAY/SHOULD/SHOULD+/MUST}</t>
<t>A recursive server may implement DNS Name Server Identifier
(NSID) Option processing. This should be implemented in line with
[<xref format="none" target="RFC5001">RFC 5001 (Section 2.1)</xref>].
</t>
<t>NSID option processing is non-transitive.</t>
</section>
</section>
<section title="Middle-Boxes">
<t>TBD
</t>
</section>
<section title="IANA Considerations">
<t>None at this time. The goal of the document is to have no IANA actions.
</t>
</section>
<section title="Acknowledgments">
<t>Much of the initial ideas, and structure of the text reflect
ideas taken from a design document developed by
NLNet Labs, in the process of developing NSD. This was
written by Dr Wouter C.A. Wijngaards and Jaap Akkerhuis.
<xref target='NLNet-1'/>.</t>
<t>A list of RRtypes, included in the above document is maintained
by Jelte Jansen, and was also used as input to this document.
<xref target='Jelte-1'/>.</t>
<t>A list of DNS standards was developed in 2004 by András Salamon
and was used as input to this document.
<xref target='Salaman-1'/>.</t>
<t>The editor thanks Joe Abley and Wouter Wijngaards
for feedback and extensive comments on this document.</t>
</section>
<section title="Concordance of references">
<t>To assist in compiling automated checkers, this
document includes as an appendix a
concordance of normative references.
This provides a handy reference to the sections of this
document which depend on each cited RFC, and vice-versa.</t>
<t>To add new dependencies into the modern DNS Implementation Guide
this concordance should be used to identify related documents
and review if any have been superseded, and also to check where else
in this document a related dependency may exist.</t>
</section>
<section title="Changes since the -01 draft">
<t>[Note: This section is not for publication.]</t>
</section>
<section title="Changes since the -00 draft">
<t>Spelling, improved language and other
editorial changes (which did not alter the substance of
normative language)
from the namedroppers list were
incorporated wholesale. (jabley) </t>
<t>incorrect normative reference to 1997 removed. (jabley).</t>
<t>text from 3597 on Transparancy for unknown RRtypes included
(jabley).</t>
<t>Better normative language for 4.1.1 (TCP Connection Management)
adopted (jabley).</t>
<t>Better normative language for 4.2.2 (TCP) adopted (jabley).</t>
<t>Better normative language for 4.3 (UDP DNS Message Processing)
adopted (jabley).</t>
<t>References for OPT processing clarified (jabley).</t>
<t>A section addressing [RFC 5001] in respect of NSID was added
to the Server section and the Recursive Resolver section. (jabley)
incorporated.</t>
<t>Editorial from ml adopted for key approach section (wijngaards)</t>
<t>incorrect normative reference to 1997 corrected to 2671 (wijngaards)</t>
<t>added normative reference to 4343 (wijngaards)</t>
<t>added normative reference to RRset TTL (wijngaards)</t>
<t>editoral text in respect of NOTIFY/UPDATE (wijngaards)</t>
<t>normative editorial text in respect of FORMERR TC bit (wijngaards)</t>
</section>
</middle>
<back>
<references title="Normative References">
&I-D.ietf-dnsext-rfc2671bis-edns0;
&RFC1033;
&RFC1034;
&RFC1035;
&RFC1122;
&RFC1123;
&RFC1183;
&RFC1464;
&RFC1535;
&RFC1536;
&RFC1706;
&RFC1713;
&RFC1794;
&RFC1876;
&RFC1912;
&RFC1982;
&RFC1995;
&RFC1996;
&RFC2010;
&RFC2119;
&RFC2136;
&RFC2163;
&RFC2181;
&RFC2219;
&RFC2230;
&RFC2247;
&RFC2276;
&RFC2308;
&RFC2535;
&RFC2536;
&RFC2538;
&RFC2539;
&RFC2540;
&RFC2541;
&RFC2671;
&RFC2672;
&RFC2673;
&RFC2694;
&RFC2782;
&RFC2825;
&RFC2845;
&RFC2874;
&RFC2916;
&RFC2929;
&RFC2930;
&RFC2931;
&RFC2937;
&RFC2972;
&RFC3007;
&RFC3008;
&RFC3090;
&RFC3110;
&RFC3123;
&RFC3197;
&RFC3225;
&RFC3226;
&RFC3258;
&RFC3263;
&RFC3363;
&RFC3364;
&RFC3401;
&RFC3402;
&RFC3403;
&RFC3404;
&RFC3405;
&RFC3425;
&RFC3445;
&RFC3490;
&RFC3491;
&RFC3492;
&RFC3596;
&RFC3597;
&RFC3645;
&RFC3646;
&RFC3655;
&RFC3658;
&RFC3696;
&RFC3755;
&RFC3757;
&RFC4025;
&RFC4033;
&RFC4034;
&RFC4035;
&RFC4255;
&RFC4307;
&RFC4343;
&RFC4408;
&RFC4431;
&RFC4701;
&RFC5001;
</references>
<references title="Informational, Formerly Normative References, now obsolete">
&RFC0882;
&RFC0883;
&RFC0973;
&RFC1348;
&RFC1386;
&RFC1537;
&RFC1637;
&RFC1664;
&RFC1712;
&RFC1811;
&RFC1816;
&RFC1886;
&RFC2052;
&RFC2065;
&RFC2137;
&RFC2168;
&RFC2240;
&RFC2537;
&RFC2915;
&RFC3152;
</references>
<references title="Non-Normative, DNS related, but not relevant to Implementors References">
&RFC0805;
&RFC0811;
&RFC0819;
&RFC0881;
&RFC0897;
&RFC0920;
&RFC0921;
&RFC0974;
&RFC1032;
&RFC1101;
&RFC1178;
&RFC1480;
&RFC1591;
&RFC1611;
&RFC1612;
&RFC1956;
&RFC2053;
&RFC2100;
&RFC2142;
&RFC2146;
&RFC2182;
&RFC2307;
&RFC2317;
&RFC2345;
&RFC2352;
&RFC2377;
&RFC2517;
&RFC2606;
&RFC2826;
&RFC2832;
&RFC2870;
&RFC3071;
&RFC3245;
&RFC3254;
&RFC3352;
&RFC3367;
&RFC3368;
&RFC3467;
&RFC3675;
</references>
<references title="Informative References Non RFC's">
<reference anchor='NLNet-1' target='/dev/null'>
<front>
<title>NSD Requirements and Specifications</title>
<author initials="W.C.A."
surname="Wijngaards"
fullname="Wouter Wijngaards">
</author>
<date month='July' year='2006' />
</front>
</reference>
<reference anchor='Jelte-1' target='http://tjeb.nl/Projects/RRTypes'>
<front>
<title>RRtypes</title>
<author initials="J."
surname="Jansen"
fullname="Jelte Jansen">
</author>
<date month='August' year='2007' />
</front>
</reference>
<reference anchor='Salaman-1' target='http://www.dns.net/dnsrd/rfc/'>
<front>
<title>DNS related RFCs</title>
<author initials="A."
surname="Salaman"
fullname="András Salaman">
</author>
<date month='June' year='2004' />
</front>
</reference>
</references>
<section anchor="app-additional-1" title="Formerly Normative, now Obsolete References">
<list>
<t><xref format="none" target="RFC0882">RFC 882</xref></t>
<t><xref format="none" target="RFC0883">RFC 883</xref></t>
<t><xref format="none" target="RFC0973">RFC 973</xref></t>
<t>These RFCs were all obsoleted by
<xref format="none" target="RFC1034">RFC 1034</xref>
and
<xref format="none" target="RFC1035">RFC 1035</xref>
</t>
</list>
<list><t> <xref format="none" target="RFC1348">RFC 1348</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC1706">RFC 1706</xref></t>
</list>
<list><t> <xref format="none" target="RFC1386">RFC 1386</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC1480">RFC 1480</xref></t>
</list>
<list><t> <xref format="none" target="RFC1537">RFC 1537</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC1912">RFC 1912</xref></t>
</list>
<list><t> <xref format="none" target="RFC1637">RFC 1637</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC1706">RFC 1706</xref></t>
</list>
<list><t> <xref format="none" target="RFC1664">RFC 1664</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC2163">RFC 2163</xref></t>
</list>
<list><t> <xref format="none" target="RFC1712">RFC 1712</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC1876">RFC 1876</xref></t>
</list>
<list><t> <xref format="none" target="RFC1811">RFC 1811</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC1816">RFC 1816</xref></t>
<t>and subsequently <xref format="none" target="RFC2146">RFC 2146</xref></t>
</list>
<list><t> <xref format="none" target="RFC1816">RFC 1816</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC2146">RFC 2146</xref></t>
</list>
<list><t> <xref format="none" target="RFC1886">RFC 1886</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC3596">RFC 3596</xref></t>
</list>
<list><t> <xref format="none" target="RFC2052">RFC 2052</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC2782">RFC 2782</xref></t>
</list>
<list><t> <xref format="none" target="RFC2065">RFC 2065</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC2535">RFC 2535</xref></t>
</list>
<list><t> <xref format="none" target="RFC2137">RFC 2137</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC3007">RFC 3007</xref></t>
</list>
<list><t> <xref format="none" target="RFC2168">RFC 2168</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC3401">RFC 3401</xref>
<xref format="none" target="RFC3402">RFC 3402</xref>
<xref format="none" target="RFC3403">RFC 3403</xref>
and
<xref format="none" target="RFC3404">RFC 3404</xref></t>
</list>
<list><t> <xref format="none" target="RFC2240">RFC 2240</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC2352">RFC 2352</xref></t>
</list>
<list><t> <xref format="none" target="RFC2537">RFC 2537</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC3110">RFC 3110</xref></t>
</list>
<list><t> <xref format="none" target="RFC2915">RFC 2915</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC3401">RFC 3401</xref>
<xref format="none" target="RFC3402">RFC 3402</xref>
<xref format="none" target="RFC3403">RFC 3403</xref>
and
<xref format="none" target="RFC3404">RFC 3404</xref></t>
</list>
<list><t> <xref format="none" target="RFC3152">RFC 3152</xref></t>
<t>This RFC was obsoleted by <xref format="none" target="RFC3596">RFC 3596</xref></t>
</list>
</section>
<!-- supressed for now, as per Olafurs email of 2008/01/10
<section anchor="app-additional-2" title="DNS related, but not relevant to Implementors References">
<list><t> <xref format="none" target="RFC0805">RFC 805</xref></t></list>
<list><t> <xref format="none" target="RFC0811">RFC 811</xref></t></list>
<list><t> <xref format="none" target="RFC0819">RFC 819</xref></t></list>
<list><t> <xref format="none" target="RFC0881">RFC 881</xref></t></list>
<list><t> <xref format="none" target="RFC0897">RFC 897</xref></t></list>
<list><t> <xref format="none" target="RFC0920">RFC 920</xref></t></list>
<list><t> <xref format="none" target="RFC0921">RFC 921</xref></t></list>
<list><t> <xref format="none" target="RFC0974">RFC 974</xref></t></list>
<list><t> <xref format="none" target="RFC1032">RFC 1032</xref></t></list>
<list><t> <xref format="none" target="RFC1101">RFC 1101</xref></t></list>
<list><t> <xref format="none" target="RFC1178">RFC 1178</xref></t></list>
<list><t> <xref format="none" target="RFC1480">RFC 1480</xref></t></list>
<list><t> <xref format="none" target="RFC1591">RFC 1591</xref></t></list>
<list><t> <xref format="none" target="RFC1611">RFC 1611</xref></t></list>
<list><t> <xref format="none" target="RFC1612">RFC 1612</xref></t></list>
<list><t> <xref format="none" target="RFC1956">RFC 1956</xref></t></list>
<list><t> <xref format="none" target="RFC2053">RFC 2053</xref></t></list>
<list><t> <xref format="none" target="RFC2100">RFC 2100</xref></t></list>
<list><t> <xref format="none" target="RFC2142">RFC 2142</xref></t></list>
<list><t> <xref format="none" target="RFC2146">RFC 2146</xref></t></list>
<list><t> <xref format="none" target="RFC2182">RFC 2182</xref></t></list>
<list><t> <xref format="none" target="RFC2307">RFC 2307</xref></t></list>
<list><t> <xref format="none" target="RFC2317">RFC 2317</xref></t></list>
<list><t> <xref format="none" target="RFC2345">RFC 2345</xref></t></list>
<list><t> <xref format="none" target="RFC2352">RFC 2352</xref></t></list>
<list><t> <xref format="none" target="RFC2377">RFC 2377</xref></t></list>
<list><t> <xref format="none" target="RFC2517">RFC 2517</xref></t></list>
<list><t> <xref format="none" target="RFC2606">RFC 2606</xref></t></list>
<list><t> <xref format="none" target="RFC2826">RFC 2826</xref></t></list>
<list><t> <xref format="none" target="RFC2832">RFC 2832</xref></t></list>
<list><t> <xref format="none" target="RFC2870">RFC 2870</xref></t></list>
<list><t> <xref format="none" target="RFC3071">RFC 3071</xref></t></list>
<list><t> <xref format="none" target="RFC3245">RFC 3245</xref></t></list>
<list><t> <xref format="none" target="RFC3254">RFC 3254</xref></t></list>
<list><t> <xref format="none" target="RFC3352">RFC 3352</xref></t></list>
<list><t> <xref format="none" target="RFC3367">RFC 3367</xref></t></list>
<list><t> <xref format="none" target="RFC3368">RFC 3368</xref></t></list>
<list><t> <xref format="none" target="RFC3467">RFC 3467</xref></t></list>
<list><t> <xref format="none" target="RFC3675">RFC 3675</xref></t></list>
</section>
-->
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 02:55:46 |