Authentication Indicator in Kerberos Tickets
draft-ietf-kitten-krb-auth-indicator-04

The information below is for an old version of the document
Document Type Active Internet-Draft (kitten WG)
Last updated 2016-12-29 (latest revision 2016-12-15)
Replaces draft-jain-kitten-krb-auth-indicator
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Benjamin Kaduk
Shepherd write-up Show (last changed 2016-11-17)
IESG IESG state In Last Call (ends 2017-01-06)
Consensus Boilerplate Yes
Telechat date
Responsible AD Stephen Farrell
Send notices to "Benjamin Kaduk" <kaduk@mit.edu>
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Internet Engineering Task Force                                  A. Jain
Internet-Draft                                              Georgia Tech
Updates: 4120 (if approved)                                    N. Kinder
Intended status: Standards Track                             N. McCallum
Expires: June 18, 2017                                     Red Hat, Inc.
                                                       December 15, 2016

              Authentication Indicator in Kerberos Tickets
                draft-ietf-kitten-krb-auth-indicator-04

Abstract

   This document updates RFC 4120 in order to specify an extension in
   the Kerberos protocol.  It defines a new authorization data type AD-
   AUTHENTICATION-INDICATOR.  The purpose of introducing this data type
   is to include an indicator of the strength of a client's
   authentication in service tickets so that application services can
   use it as an input into policy decisions.

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 June 18, 2017.

Copyright Notice

   Copyright (c) 2016 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
   to this document.  Code Components extracted from this document must

Jain, et al.              Expires June 18, 2017                 [Page 1]
Internet-Draft          Authentication Indicator           December 2016

   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  . . . . . . . . . . . . . . . . . . . .   2
   3.  AD Type Specification . . . . . . . . . . . . . . . . . . . .   2
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Appendix A.  ASN.1 Module . . . . . . . . . . . . . . . . . . . .   5
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Kerberos [RFC4120] allows secure interaction among users and services
   over a network.  It supports a variety of authentication mechanisms
   using its pre-authentication framework [RFC6113].  The Kerberos
   authentication service has been architected to support password-based
   authentication as well as multi-factor authentication using one-time
   password devices, public-key cryptography and other pre-
   authentication schemes.  Implementations that offer pre-
   authentication mechanisms supporting significantly different
   strengths of client authentication may choose to keep track of the
   strength of the authentication that was used, for use as an input
   into policy decisions.

   This document specifies a new authorization data type to convey
   authentication strength information to application services.
   Elements of this type MUST appear within an AD-CAMMAC [RFC7751]
   container.

2.  Document Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

3.  AD Type Specification

   The KDC MAY include authorization data of ad-type 97, wrapped in AD-
   CAMMAC, in initial credentials.  The KDC MAY copy it from a ticket-
   granting ticket into service tickets.

Jain, et al.              Expires June 18, 2017                 [Page 2]
Internet-Draft          Authentication Indicator           December 2016

   The corresponding ad-data field contains the DER encoding of the
   following ASN.1 type:

   AD-AUTHENTICATION-INDICATOR ::= SEQUENCE OF UTF8String
Show full document text