[rfc-dist] RFC 4509 on Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)

[rfc-editor@rfc-editor.org]

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

        
        RFC 4509

        Title:      Use of SHA-256 in DNSSEC 
                    Delegation Signer (DS) Resource Records (RRs) 
        Author:     W. Hardaker
        Status:     Standards Track
        Date:       May 2006
        Mailbox:    hardaker at tislabs.com
        Pages:      7
        Characters: 14155
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsext-ds-sha256-05.txt

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

This document specifies how to use the SHA-256 digest type in DNS
Delegation Signer (DS) Resource Records (RRs).  DS records, when
stored in a parent zone, point to DNSKEYs in a child zone.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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.


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

...