RFC - 3445
Limiting the Scope of the KEY Resource Record (RR)
| Obsoleted by: |
| RFC-4035prop |
Protocol Modifications for the DNS Security Extensions (Updated by RFC-4470prop)
|
| RFC-4034prop |
Resource Records for the DNS Security Extensions (Updated by RFC-4470prop)
|
| RFC-4033prop |
DNS Security Introduction and Requirements |
| Updates: |
| RFC-2535 |
Domain Name System Security Extensions (Obsoleted by RFC-4033prop, RFC-4035prop, RFC-4034prop) (Updated by RFC-3755, RFC-3757, RFC-3226prop, RFC-3658, RFC-3655, RFC-3007prop, RFC-3008, RFC-3845, RFC-3597prop, RFC-3445, RFC-3090, RFC-2931prop)
|
| Referred by: |
9 RFC |
| Refers to: |
5 RFC |
Status
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.
Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract
This document limits the Domain Name System (DNS) KEY Resource Record
(RR) to only keys used by the Domain Name System Security Extensions
(DNSSEC). The original KEY RR used sub-typing to store both DNSSEC
keys and arbitrary application keys. Storing both DNSSEC and
application keys with the same record type is a mistake. This
document removes application keys from the KEY record by redefining
the Protocol Octet field in the KEY RR Data. As a result of removing
application keys, all but one of the flags in the KEY record become
unnecessary and are redefined. Three existing application key sub-
types are changed to reserved, but the format of the KEY record is
not changed. This document updates RFC 2535(-> 4035prop | 4034prop | 4033prop).
