TKEY Secret Key Renewal Mode
draft-kamite-dnsext-tkey-secret-renewal-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Dr. Masaya Nakayama | ||
Last updated | 2001-07-09 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
TKEY [RFC2930] provides methods of setting up shared secret keys for TSIG [RFC2845] other than manual exchange. But TKEY itself cannot control timing of key renewal very well though it can add or delete shared keys. Since continuing to sign messages with old keys permanently is not safe, hosts which make use of TSIG should pay attention to the time limit of secret usage.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)