[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DNS Extensions Working Group of the IETF.
Title : Protocol Modifications for the DNS Security Extensions
Author(s) : R. Arends et al.
Filename : draft-ietf-dnsext-dnssec-protocol-00.txt
Pages : 32
Date : 2002-10-29
This document is part of a family of documents that describe the
DNS Security Extensions (DNSSEC). The DNS Security Extensions are
a collection of new resource records and protocol modifications
that provide source authentication for the DNS. This document
describes the DNSSEC protocol modifications. The concept of zone
signing is introduced and the zone format is modified to include
KEY, SIG, NXT, and DS resource records. If a resolver indicates
support for DNSSEC, the response process is modified to include
the appropriate KEY, SIG, NXT, and DS resource records. These
resource records are used by the resolver to authenticate the
This document obsoletes RFC 2535 and incorporates changes from all
updates to RFC 2535.
A URL for this Internet-Draft is:
To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.
Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
A list of Internet-Drafts directories can be found in
Internet-Drafts can also be obtained by e-mail.
Send a message to:
In the body type:
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the