Kerberos Service Discovery using DNS
draft-ietf-kitten-krb-service-discovery-00

Document Type Active Internet-Draft (kitten WG)
Last updated 2017-03-01 (latest revision 2017-02-09)
Replaces draft-mccallum-kitten-krb-service-discovery
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                              N. McCallum
Internet-Draft                                                 M. Rogers
Updates: 4120 (if approved)                                Red Hat, Inc.
Intended status: Standards Track                        February 9, 2017
Expires: August 13, 2017

                  Kerberos Service Discovery using DNS
               draft-ietf-kitten-krb-service-discovery-00

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 13, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

McCallum & Rogers        Expires August 13, 2017                [Page 1]
Internet-Draft              Service Discovery              February 2017

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Document Conventions  . . . . . . . . . . . . . . . . . . . .   3
   3.  Realm to Domain Translation . . . . . . . . . . . . . . . . .   3
   4.  Required URI Format . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Scheme  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  Flags . . . . . . . . . . . . . . . . . . . . . . . . . .   3
       4.2.1.  Master Flag . . . . . . . . . . . . . . . . . . . . .   4
     4.3.  Transport . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.4.  Residual  . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Kerberos V5 KDC Service Discovery . . . . . . . . . . . . . .   4
   6.  Kerberos Password Service Discovery . . . . . . . . . . . . .   4
   7.  Kerberos Admin Service Discovery  . . . . . . . . . . . . . .   5
   8.  Relationship to Existing Mechanism  . . . . . . . . . . . . .   5
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Kerberos Server Discovery Flags . . . . . . . . . . . . .   5
       9.1.1.  Registration Template . . . . . . . . . . . . . . . .   5
       9.1.2.  Initial Registry Contents . . . . . . . . . . . . . .   6
     9.2.  Kerberos Server Discovery Transport Types . . . . . . . .   6
       9.2.1.  Registration Template . . . . . . . . . . . . . . . .   6
       9.2.2.  Initial Registry Contents . . . . . . . . . . . . . .   6
   10. Appendix  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  URI Format Examples  . . . . . . . . . . . . . . . . . .   7
   11. Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Section 7.2.3 of Kerberos V5 [RFC4120] defines a procedure for
   discovering a KDC based on DNS SRV records.  This method has three
   drawbacks.  First, two DNS queries are required to locate a single
   service (one for UDP and one for TCP).  Second, specifying UDP and
   TCP in separate records means that the DNS administrator has no
   control over client preferences for TCP or UDP.  Third, any new
   transports for reaching the KDC (such as MS-KKDCP) will require new
Show full document text