[rfc-dist] RFC 4956 on DNS Security (DNSSEC) Opt-In

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Jul 27 13:31:04 PDT 2007

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

        RFC 4956

        Title:      DNS Security (DNSSEC) Opt-In 
        Author:     R. Arends, M. Kosters,
                    D. Blacka
        Status:     Experimental
        Date:       July 2007
        Mailbox:    roy at nominet.org.uk, 
                    markk at verisign.com, 
                    davidb at verisign.com
        Pages:      17
        Characters: 32033
        Updates/Obsoletes/SeeAlso:   None

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

        URL:        http://www.rfc-editor.org/rfc/rfc4956.txt

In the DNS security (DNSSEC) extensions, delegations to unsigned
subzones are cryptographically secured.  Maintaining this
cryptography is not always practical or necessary.  This document
describes an experimental "Opt-In" model that allows administrators
to omit this cryptography and manage the cost of adopting DNSSEC with
large zones.  This memo defines an Experimental Protocol for the Internet

This document is a product of the DNS Extensions
Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet 
community. It does not specify an Internet standard of any kind. Discussion
and suggestions for improvement are requested.  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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list