RFC 4033 on DNS Security Introduction and Requirements
rfc-editor@rfc-editor.org Wed, 30 March 2005 04:00 UTC
Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02283 for <dnsext-archive@lists.ietf.org>; Tue, 29 Mar 2005 23:00:25 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1DGUIp-000GNd-VU for namedroppers-data@psg.com; Wed, 30 Mar 2005 03:55:35 +0000
Received: from [128.9.160.161] (helo=boreas.isi.edu) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1DGUIm-000GLk-Nf for namedroppers@ops.ietf.org; Wed, 30 Mar 2005 03:55:32 +0000
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j2U3sUq18035; Tue, 29 Mar 2005 19:54:30 -0800 (PST)
Message-Id: <200503300354.j2U3sUq18035@boreas.isi.edu>
To: ietf-announce@ietf.org
Subject: RFC 4033 on DNS Security Introduction and Requirements
Cc: rfc-editor@rfc-editor.org, namedroppers@ops.ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 29 Mar 2005 19:54:30 -0800
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com
X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00, MIME_BOUND_NEXTPART,NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=3.0.1
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 4033 Title: DNS Security Introduction and Requirements 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: 21 Characters: 52445 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-intro-13.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4033.txt The Domain Name System Security Extensions (DNSSEC) add data origin authentication and data integrity to the Domain Name System. This document introduces these extensions and describes their capabilities and limitations. This document also discusses the services that the DNS security extensions do and do not provide. Last, this document describes the interrelationships between the documents that collectively describe DNSSEC. 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.