idnits 2.17.1 draft-ietf-dnsext-rsa-03.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 3110 5 Title: RSA/SHA-1 SIGs and RSA KEYs in the Domain Name 6 System (DNS) 7 Author(s): D. Eastlake 3rd 8 Status: Standards Track 9 Date: May 2001 10 Mailbox: Donald.Eastlake@motorola.com 11 Pages: 7 12 Characters: 14587 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-dnsext-rsa-03.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3110.txt 19 This document describes how to produce RSA/SHA1 SIG resource records 20 (RRs) in Section 3 and, so as to completely replace RFC 2537, 21 describes how to produce RSA KEY RRs in Section 2. 23 Since the adoption of a Proposed Standard for RSA signatures in the 24 DNS (Domain Name Space), advances in hashing have been made. A new 25 DNS signature algorithm is defined to make these advances available in 26 SIG RRs. The use of the previously specified weaker mechanism is 27 deprecated. The algorithm number of the RSA KEY RR is changed to 28 correspond to this new SIG algorithm. No other changes are made to 29 DNS security. 31 This document is a product of the DNS Extensions Working Group of the 32 IETF. 34 This is now a Proposed Standard Protocol. 36 This document specifies an Internet standards track protocol for 37 the Internet community, and requests discussion and suggestions 38 for improvements. Please refer to the current edition of the 39 "Internet Official Protocol Standards" (STD 1) for the 40 standardization state and status of this protocol. Distribution 41 of this memo is unlimited. 43 This announcement is sent to the IETF list and the RFC-DIST list. 44 Requests to be added to or deleted from the IETF distribution list 45 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 46 added to or deleted from the RFC-DIST distribution list should 47 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 49 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 50 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 51 help: ways_to_get_rfcs. For example: 53 To: rfc-info@RFC-EDITOR.ORG 54 Subject: getting rfcs 56 help: ways_to_get_rfcs 58 Requests for special distribution should be addressed to either the 59 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 60 specifically noted otherwise on the RFC itself, all RFCs are for 61 unlimited distribution.echo 62 Submissions for Requests for Comments should be sent to 63 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 64 Authors, for further information.