idnits 2.17.1 draft-ietf-dnsext-restrict-key-for-dnssec-04.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 3445 5 Title: Limiting the Scope of the KEY Resource Record (RR) 6 Author(s): D. Massey, S. Rose 7 Status: Standards Track 8 Date: December 2002 9 Mailbox: masseyd@isi.edu, scott.rose@nist.gov 10 Pages: 10 11 Characters: 20947 12 Updates: 2535 14 I-D Tag: draft-ietf-dnsext-restrict-key-for-dnssec-04.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3445.txt 18 This document limits the Domain Name System (DNS) KEY Resource Record 19 (RR) to only keys used by the Domain Name System Security Extensions 20 (DNSSEC). The original KEY RR used sub-typing to store both DNSSEC 21 keys and arbitrary application keys. Storing both DNSSEC and 22 application keys with the same record type is a mistake. This 23 document removes application keys from the KEY record by redefining 24 the Protocol Octet field in the KEY RR Data. As a result of removing 25 application keys, all but one of the flags in the KEY record become 26 unnecessary and are redefined. Three existing application key 27 sub-types are changed to reserved, but the format of the KEY record is 28 not changed. This document updates RFC 2535. 30 This document is a product of the DNS Extensions Working Group of the 31 IETF. 33 This is now a Proposed Standard Protocol. 35 This document specifies an Internet standards track protocol for 36 the Internet community, and requests discussion and suggestions 37 for improvements. Please refer to the current edition of the 38 "Internet Official Protocol Standards" (STD 1) for the 39 standardization state and status of this protocol. Distribution 40 of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.