Kerberos Service Discovery using DNS
draft-mccallum-kitten-krb-service-discovery-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Nathaniel McCallum | ||
| Last updated | 2015-09-06 (Latest revision 2015-03-05) | ||
| Replaced by | draft-ietf-kitten-krb-service-discovery | ||
| RFC stream | (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
This document proposes defines a new mechanism for discovering Kerberos services using DNS. This new mechanism extends the mechanism already defined in Kerberos V5 [RFC4120] and has four goals. First, reduce the number of DNS queries required to discover a Kerberos KDC. Second, provide DNS administrators more control over client behavior. Third, provide support for discovery of the MS- KKDCP transport. Fourth, define a discovery procedure for Kerberos password services.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)