[dnsext] RFC 6840 on Clarifications and Implementation Notes for DNS Security (DNSSEC)

rfc-editor@rfc-editor.org Thu, 21 February 2013 17:33 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ADAF21F8EA5; Thu, 21 Feb 2013 09:33:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.043
X-Spam-Level:
X-Spam-Status: No, score=-102.043 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MRV1nUkzQUX4; Thu, 21 Feb 2013 09:33:47 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 02D1621F8E71; Thu, 21 Feb 2013 09:33:47 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id CD87972F4B8; Thu, 21 Feb 2013 09:32:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130221173252.CD87972F4B8@rfc-editor.org>
Date: Thu, 21 Feb 2013 09:32:52 -0800
Cc: dnsext@ietf.org, rfc-editor@rfc-editor.org
Subject: [dnsext] RFC 6840 on Clarifications and Implementation Notes for DNS Security (DNSSEC)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Feb 2013 17:33:47 -0000

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

        
        RFC 6840

        Title:      Clarifications and Implementation Notes 
                    for DNS Security (DNSSEC)
        Author:     S. Weiler, Ed.,
                    D. Blacka, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2012
        Mailbox:    weiler@tislabs.com, 
                    davidb@verisign.com
        Pages:      21
        Characters: 47283
        Updates:    RFC4033, RFC4034, RFC4035, RFC5155

        I-D Tag:    draft-ietf-dnsext-dnssec-bis-updates-20.txt

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

This document is a collection of technical clarifications to the DNS
Security (DNSSEC) document set.  It is meant to serve as a resource
to implementors as well as a collection of DNSSEC errata that existed
at the time of writing.

This document updates the core DNSSEC documents (RFC 4033, RFC 4034,
and RFC 4035) as well as the NSEC3 specification (RFC 5155).  It also
defines NSEC3 and SHA-2 (RFC 4509 and RFC 5702) as core parts of the
DNSSEC specification.

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

This is now a Proposed Standard.

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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC