Handling of Unknown DNS Resource Record (RR) Types
draft-ietf-dnsext-unknown-rrs-06
The information below is for an old version of the document that is already published as an RFC.
| Document | Type | RFC Internet-Draft (dnsext WG) | |
|---|---|---|---|
| Author | Andreas Gustafsson | ||
| Last updated | 2020-01-21 (Latest revision 2003-06-30) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats | plain text htmlized pdfized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| This information refers to IESG processing after the RFC was initially published: | |||
| IESG | IESG state | RFC 3597 (Proposed Standard) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Ralph Droms | ||
| IESG note | Found error in RFC 3597, new document necessary and will no longer have downref problem. RFC 2163 should be moved to historic, though this can be decoupled from RFC 3597 advancing. | ||
| Send notices to | jakob@rfc.se, olaf@ripe.net | ||
draft-ietf-dnsext-unknown-rrs-06
A new Request for Comments is now available in online RFC libraries.
RFC 3597
Title: Handling of Unknown DNS Resource Record (RR) Types
Author(s): A. Gustafsson
Status: Standards Track
Date: September 2003
Mailbox: gson@nominum.com
Pages: 8
Characters: 17559
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dnsext-unknown-rrs-06.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3597.txt
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.
This document is a product of the DNS Extensions Working Group of the
IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.