RFC 4035 on Protocol Modifications for the DNS Security Extensions

A new Request for Comments is now available in online RFC libraries.

        RFC 4035

        Title:      Protocol Modifications for the
                    DNS Security Extensions
        Author(s):  R. Arends, R. Austein, M. Larson, D. Massey,
                    S. Rose
        Status:     Standards Track
        Date:       March 2005
        Mailbox:    roy.arends@telin.nl, sra@isc.org,
                    mlarson@verisign.com, massey@cs.colostate.edu,
                    scott.rose@nist.gov
        Pages:      53
        Characters: 130589
        Updates:    1034, 1035, 2136, 2181, 2308, 3225, 3007, 3597,
                    3226
        Obsoletes:  2535, 3008, 3090, 3445, 3655, 3658, 3755, 3757,
                    3845

        I-D Tag:    draft-ietf-dnsext-dnssec-protocol-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4035.txt

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
add data origin authentication and data integrity to the DNS.  This
document describes the DNSSEC protocol modifications.  This document
defines the concept of a signed zone, along with the requirements for
serving and resolving by using DNSSEC.  These techniques allow a
security-aware resolver to authenticate both DNS resource records
and authoritative DNS error indications.

This document obsoletes RFC 2535 and incorporates changes from all
updates to RFC 2535.

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.

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.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.