metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3597: Handling of Unknown DNS Resource Record (RR) Types

Still current, but amended. Parts of this document are changed or extended by RFC 4033, RFC 4034, RFC 4035, RFC 5395, RFC 6195, RFC 6895. Read both.

In plain English — editorial summary, not part of the RFC

Extending the Domain Name System (DNS) with new Resource Record (RR) types currently requires changes to name server software. This document specifies the changes necessary to allow future DNS implementations to handle new RR types transparently. [STANDARDS-TRACK]

Document record

Document ID
RFC3597
Published
September 2003
Authors
A. Gustafsson
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
8
Also known as
—
Updates:
RFC 2163, RFC 2535
Updated by:
RFC 4033, RFC 4034, RFC 4035, RFC 5395, RFC 6195, RFC 6895

Topics

Referenced by

6 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3597-handling-of-unknown-dns-resource-record-rr-types