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

In plain English — editorial summary, not part of the RFC

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. [STANDARDS-TRACK]

Document record

Document ID

RFC4025

Published

March 2005

Authors

M. Richardson

Status

PROPOSED STANDARD

Stream

IETF

Area

sec

Pages

12

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC4025
• Reported errata exist →

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 4013SASLprep: Stringprep Profile for User Names and PasswordsObsoleted

  March 2005

• RFC 4010Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS)Current

  February 2005

• RFC 4043Internet X.509 Public Key Infrastructure Permanent IdentifierCurrent

  May 2005

• RFC 4046Multicast Security (MSEC) Group Key Management ArchitectureCurrent

  May 2005

• RFC 4055Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileUpdated

  June 2005

• RFC 4056Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax (CMS)Current

  June 2005

• RFC 4059Internet X.509 Public Key Infrastructure Warranty Certificate ExtensionCurrent

  May 2005

• RFC 4082Timed Efficient Stream Loss-Tolerant Authentication (TESLA): Multicast Source Authentication Transform IntroductionCurrent

  June 2005

Also filed under

• PROPOSED STANDARD
• 2005
• IETF stream
• sec area