RFC 3008 on DNSSEC Signing Authority
RFC Editor <rfc-ed@ISI.EDU> Wed, 29 November 2000 01:08 UTC
Received: from psg.com (psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA22260 for <dnsext-archive@lists.ietf.org>; Tue, 28 Nov 2000 20:08:49 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.16 #1) id 140v5C-000EH2-00 for namedroppers-data@psg.com; Tue, 28 Nov 2000 16:26:46 -0800
Received: from fwgw.boaw.cust.55cc.tor.boaw.net ([216.94.86.34] helo=roam.psg.com) by psg.com with esmtp (Exim 3.16 #1) id 140v5B-000EGA-00 for namedroppers@ops.ietf.org; Tue, 28 Nov 2000 16:26:45 -0800
Received: from randy by roam.psg.com with local (Exim 3.12 #1) id 140v5y-0003Do-00 for namedroppers@ops.ietf.org; Tue, 28 Nov 2000 16:27:34 -0800
Received: from boreas.isi.edu ([128.9.160.161]) by psg.com with esmtp (Exim 3.16 #1) id 140uME-000DS0-00 for namedroppers@ops.ietf.org; Tue, 28 Nov 2000 15:40:18 -0800
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA08029; Tue, 28 Nov 2000 15:40:13 -0800 (PST)
Message-Id: <200011282340.PAA08029@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3008 on DNSSEC Signing Authority
Cc: rfc-ed@ISI.EDU, namedroppers@ops.ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 28 Nov 2000 15:40:12 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3008 Title: Domain Name System Security (DNSSEC) Signing Authority Author(s): B. Wellington Status: Standards Track Date: November 2000 Mailbox: Brian.Wellington@nominum.com Pages: 7 Characters: 13484 Updates: 2535 I-D Tag: draft-ietf-dnsext-signing-auth-02.txt URL: ftp://ftp.isi.edu/in-notes/rfc3008.txt This document proposes a revised model of Domain Name System Security (DNSSEC) Signing Authority. The revised model is designed to clarify earlier documents and add additional restrictions to simplify the secure resolution process. Specifically, this affects the authorization of keys to sign sets of records. 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.echo 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.
- RFC 3008 on DNSSEC Signing Authority RFC Editor