Kerberos Principal Name Canonicalization and KDC-Generated Cross-Realm Referrals
draft-ietf-krb-wg-kerberos-referrals-14

The information below is for an old version of the document
Document Type Active Internet-Draft (krb-wg WG)
Last updated 2012-09-12 (latest revision 2012-03-12)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Jeffrey Hutzelman
Shepherd write-up Show (last changed 2012-03-09)
IESG IESG state In Last Call
Telechat date
Responsible AD Stephen Farrell
IESG note The Document Shepherd for this document is Jeffrey Hutzelman (jhutz@cmu.edu).
Send notices to krb-wg-chairs@tools.ietf.org, draft-ietf-krb-wg-kerberos-referrals@tools.ietf.org
Kerberos WORKING GROUP                                   S. Hartman, Ed.
Internet-Draft                                         Painless Security
Updates: 4120 (if approved)                                   K. Raeburn
Intended status: Standards Track                                     MIT
Expires: September 13, 2012                                       L. Zhu
                                                   Microsoft Corporation
                                                          March 12, 2012

 Kerberos Principal Name Canonicalization and KDC-Generated Cross-Realm
                               Referrals
                draft-ietf-krb-wg-kerberos-referrals-14

Abstract

   The memo documents a method for a Kerberos Key Distribution Center
   (KDC) to respond to client requests for Kerberos tickets when the
   client does not have detailed configuration information on the realms
   of users or services.  The KDC will handle requests for principals in
   other realms by returning either a referral error or a cross-realm
   TGT to another realm on the referral path.  The clients will use this
   referral information to reach the realm of the target principal and
   then receive the ticket.  This memo also provides a mechanism for
   verifying that a request has not been tampered with in transit.  This
   memo updates RFC 4120.

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 September 13, 2012.

Copyright Notice

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

Hartman, et al.        Expires September 13, 2012               [Page 1]
Internet-Draft                KDC Referrals                   March 2012

   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
   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Hartman, et al.        Expires September 13, 2012               [Page 2]
Internet-Draft                KDC Referrals                   March 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Conventions Used in This Document  . . . . . . . . . . . . . .  5
   3.  Requesting a Referral  . . . . . . . . . . . . . . . . . . . .  5
   4.  Realm Organization Model . . . . . . . . . . . . . . . . . . .  6
     4.1.  Trust Assumptions  . . . . . . . . . . . . . . . . . . . .  6
   5.  Enterprise Principal Name Type . . . . . . . . . . . . . . . .  7
   6.  Name Canonicalization  . . . . . . . . . . . . . . . . . . . .  8
   7.  Client Referrals . . . . . . . . . . . . . . . . . . . . . . . 10
   8.  Server Referrals . . . . . . . . . . . . . . . . . . . . . . . 11
   9.  Cross Realm Routing  . . . . . . . . . . . . . . . . . . . . . 12
   10. Caching Information  . . . . . . . . . . . . . . . . . . . . . 12
   11. Negotiation of FAST and Detecting Modified Requests  . . . . . 12
   12. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   13. Security Considerations  . . . . . . . . . . . . . . . . . . . 14
Show full document text