RFC 4025 on A Method for Storing IPsec Keying Material in DNS

[rfc-editor at rfc-editor.org]

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


        RFC 4025

        Title:      A Method for Storing IPsec Keying Material in DNS
        Author(s):  M. Richardson
        Status:     Standards Track
        Date:       March 2005
        Mailbox:    mcr at sandelman.ottawa.on.ca
        Pages:      12
        Characters: 25408
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipseckey-rr-11.txt

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


This document describes a new resource record for the Domain Name
System (DNS).  This record may be used to store public keys for use
in IP security (IPsec) systems.  The record also includes provisions
for indicating what system should be contacted when an
IPsec tunnel is established with the entity in question.

This record replaces the functionality of the sub-type #4 of the
KEY Resource Record, which has been obsoleted by RFC 3445.

This document is a product of the IPSEC KEYing information resource
record 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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.

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.

<ftp://ftp.isi.edu/in-notes/rfc4025.txt>

_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce