metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 4635: HMAC SHA (Hashed Message Authentication Code, Secure Hash Algorithm) TSIG Algorithm Identifiers

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8945.

Current document in this lineage: RFC 8945 — Secret Key Transaction Authentication for DNS (TSIG)

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

Use of the Domain Name System TSIG resource record requires specification of a cryptographic message authentication code. Currently, identifiers have been specified only for HMAC MD5 (Hashed Message Authentication Code, Message Digest 5) and GSS (Generic Security Service) TSIG algorithms. This document standardizes identifiers and implementation requirements for additional HMAC SHA (Secure Hash Algorithm) TSIG algorithms and standardizes how to specify and handle the truncation of HMAC values in TSIG. [STANDARDS-TRACK]

Document record

Document ID
RFC4635
Published
August 2006
Authors
D. Eastlake 3rd
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
8
Also known as
—
Obsoleted by:
RFC 8945
Updates:
RFC 2845

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 2845 (2000)
  2. RFC 4635 (2006)
  3. RFC 8945 (2020) ✓

Read the full history of Secret Key Transaction Authentication for DNS (TSIG) →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

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

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/4635-hmac-sha-hashed-message-authentication-code-secure-hash-algorithm-tsig-algorithm