RFC 3658 Delegation Signer (DS) Resource Record (RR)
rfc-editor@rfc-editor.org Fri, 19 December 2003 00:41 UTC
Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02102 for <dnsext-archive@lists.ietf.org>; Thu, 18 Dec 2003 19:41:50 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD) id 1AX8bi-000N9m-Cl for namedroppers-data@psg.com; Fri, 19 Dec 2003 00:35:06 +0000
Received: from [128.9.144.145] (helo=gamma.isi.edu) by psg.com with esmtp (Exim 4.24; FreeBSD) id 1AX8bV-000N7g-0B for namedroppers@ops.ietf.org; Fri, 19 Dec 2003 00:34:53 +0000
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hBJ0Yfs23165; Thu, 18 Dec 2003 16:34:41 -0800 (PST)
Message-Id: <200312190034.hBJ0Yfs23165@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3658 Delegation Signer (DS) Resource Record (RR)
Cc: rfc-editor@rfc-editor.org, namedroppers@ops.ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 18 Dec 2003 16:34:41 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-19.2 required=5.0 tests=BAYES_00, MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3658 Title: Delegation Signer (DS) Resource Record (RR) Author(s): O. Gudmundsson Status: Standards Track Date: December 2003 Mailbox: ds-rfc@ogud.com Pages: 19 Characters: 42120 Updates: 3090, 3008, 2535, 1035 I-D Tag: draft-ietf-dnsext-delegation-signer-15.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3658.txt The delegation signer (DS) resource record (RR) is inserted at a zone cut (i.e., a delegation point) to indicate that the delegated zone is digitally signed and that the delegated zone recognizes the indicated key as a valid zone key for the delegated zone. The DS RR is a modification to the DNS Security Extensions definition, motivated by operational considerations. The intent is to use this resource record as an explicit statement about the delegation, rather than relying on inference. This document defines the DS RR, gives examples of how it is used and describes the implications on resolvers. This change is not backwards compatible with RFC 2535. This document updates RFC 1035, RFC 2535, RFC 3008 and RFC 3090. This document is a product of the DNS Extensions Working Group of the IETF. This is now a Proposed Standard Protocol. 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. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.