idnits 2.17.1 draft-ietf-dnsext-zone-status-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3090 5 Title: DNS Security Extension Clarification on Zone 6 Status 7 Author(s): E. Lewis 8 Status: Standards Track 9 Date: March 2001 10 Mailbox: lewis@tislabs.com 11 Pages: 11 12 Characters: 24166 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-dnsext-zone-status-05.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3090.txt 19 The definition of a secured zone is presented, clarifying and updating 20 sections of RFC 2535. RFC 2535 defines a zone to be secured based on 21 a per algorithm basis, e.g., a zone can be secured with RSA keys, and 22 not secured with DSA keys. This document changes this to define a 23 zone to be secured or not secured regardless of the key algorithm used 24 (or not used). To further simplify the determination of a zone's 25 status, "experimentally secure" status is deprecated. 27 This document is a product of the DNS Extensions Working Group of the 28 IETF. 30 This is now a Proposed Standard Protocol. 32 This document specifies an Internet standards track protocol for 33 the Internet community, and requests discussion and suggestions 34 for improvements. Please refer to the current edition of the 35 "Internet Official Protocol Standards" (STD 1) for the 36 standardization state and status of this protocol. Distribution 37 of this memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.