[rfc-dist] RFC 3757 on Domain Name System KEY (DNSKEY) Resource Record (RR) Secure Entry Point (SEP) Flag

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Thu May 27 16:04:31 PDT 2004

A new Request for Comments is now available in online RFC libraries.

        RFC 3757

        Title:      Domain Name System KEY (DNSKEY) Resource Record
                    (RR) Secure Entry Point (SEP) Flag
        Author(s):  O. Kolkman, J. Schlyter, E. Lewis
        Status:     Standards Track
        Date:       May 2004
        Mailbox:    olaf at ripe.net, jakob at nic.se, edlewis at arin.net
        Pages:      8
        Characters: 16868
        Updates:    3755, 2535

        I-D Tag:    draft-ietf-dnsext-keyrr-key-signing-flag-12.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3757.txt

With the Delegation Signer (DS) resource record (RR), the concept of a
public key acting as a secure entry point (SEP) has been introduced.
During exchanges of public keys with the parent there is a need to
differentiate SEP keys from other public keys in the Domain Name
System KEY (DNSKEY) resource record set.  A flag bit in the
DNSKEY RR is defined to indicate that DNSKEY is to be used as a SEP.
The flag bit is intended to assist in operational procedures to
correctly generate DS resource records, or to indicate what DNSKEYs
are intended for static configuration.  The flag bit is not to be used
in the DNS verification protocol.  This document updates RFC 2535 and
RFC 3755.

This document is a product of the DNS Extensions Working Group of the

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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at 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 at 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 at 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.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list