DNS Request and Transaction Signatures ( SIG(0)s )
draft-srose-rfc2931bis-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Scott Rose | ||
| Last updated | 2003-08-07 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-srose-rfc2931bis-00.txt
Abstract
Extensions to the Domain Name System (DNS) can provide data origin and transaction integrity and authentication to security aware resolvers and applications through the use of cryptographic digital signatures. However, these security extensions do not provide authentication at the transaction or message level. This document describes a message authentication scheme (called SIG(0)) that provides message level authentication and integrity checking by means of a meta-RR in the additional section of a DNS message.
Authors
Scott Rose (srose@verisignlabs.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)