Published RFCs never change. Although every published RFC has been
submitted to careful proofreading by the RFC Editor and the author
(s), errors do sometimes go undetected. As a service to the readers
of RFCs, this page contains a list of technical and editorial errors
that have been reported to the RFC Editor and verified by the authors
or the IESG.
In general, we cannot guarantee the correctness of these errata; the
reader must make his/her own judgment.
Erratum for RFC 2308
RFC 2308,
"Negative Caching of DNS Queries (DNS NCACHE)", March 1998
Reported By: Hideshi Enokihara <Hideshi.Enokihara@jp.yokogawa.com>
Date: Thu, 2 Feb 2006 16:07:04 +0900
UNVERIFIED Section 7.2 says: 7.2 Dead / Unreachable Server (OPTIONAL) Dead / Unreachable servers are servers that fail to respond in any way to a query or where the transport layer has provided an indication that the server does not exist or is unreachable. A server may be deemed to be dead or unreachable if it has not responded to an outstanding query within 120 seconds. Examples of transport layer indications are: ICMP error messages indicating host, net or port unreachable. TCP resets IP stack error messages providing similar indications to those above. A server MAY cache a dead server indication. If it does so it MUST NOT be deemed dead for longer than five (5) minutes. The indication MUST be stored against query tuple <query name, type, class, server IP address> unless there was a transport layer indication that the server does not exist, in which case it applies to all queries to that specific IP address. It should say: 7.2 Dead / Unreachable Server (OPTIONAL) Dead / Unreachable servers are servers that fail to respond in any way to a query or where the transport layer has provided an indication that the server does not exist or is unreachable. A server may be deemed to be dead or unreachable if it has not responded to an outstanding query within 120 seconds. Examples of transport layer indications are: ICMP error messages indicating host, net or port unreachable. TCP resets IP stack error messages providing similar indications to those above. A resolver MAY cache a dead server indication. If it does so it MUST NOT be deemed dead for longer than five (5) minutes. The indication MUST be stored against query tuple <query name, type, class, server IP address> unless there was a transport layer indication that the server does not exist, in which case it applies to all queries to that specific IP address. Rationale: Last sentence says, "A server MAY cache a dead server indication.". But, this "server" is typo, I think. This "server" should be "resolver" because section 7.1's last sentence uses "resolver".
|