RFC 3090:DNS Security Extension Clarification on Z...
RFC-Ref

RFC - 3090

DNS Security Extension Clarification on Zone Status

Original: ftp://ftp.isi.edu/in-notes/rfc3090.txt
Authors: E. Lewis [NAI Labs]
Date: March 2001
Category: Informational
 
This specification has been !!! obsoleted !!!



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)

Updated by:
RFC-3658 Delegation Signer (DS) Resource Record (RR) (Obsoleted by RFC-4033prop, RFC-4035prop, RFC-4034prop) (Updated by RFC-3755)

Referred by: 10 RFC
Refers to: 7 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 (2001). All Rights Reserved.

Abstract

The definition of a secured zone is presented, clarifying and updating sections of RFC 2535(-> 4035prop | 4034prop | 4033prop). RFC 2535(-> 4035prop | 4034prop | 4033prop) defines a zone to be secured based on a per algorithm basis, e.g., a zone can be secured with RSA keys, and not secured with DSA keys. This document changes this to define a zone to be secured or not secured regardless of the key algorithm used (or not used). To further simplify the determination of a zone's status, "experimentally secure" status is deprecated.


About Resource

Google
Web
RFC-Ref