draft-ietf-kitten-krb-auth-indicator-06.txt   draft-ietf-kitten-krb-auth-indicator-07.txt 
Internet Engineering Task Force A. Jain Internet Engineering Task Force A. Jain
Internet-Draft Georgia Tech Internet-Draft Georgia Tech
Updates: 4120 (if approved) N. Kinder Updates: 4120 (if approved) N. Kinder
Intended status: Standards Track N. McCallum Intended status: Standards Track N. McCallum
Expires: July 8, 2017 Red Hat, Inc. Expires: August 13, 2017 Red Hat, Inc.
January 4, 2017 February 9, 2017
Authentication Indicator in Kerberos Tickets Authentication Indicator in Kerberos Tickets
draft-ietf-kitten-krb-auth-indicator-06 draft-ietf-kitten-krb-auth-indicator-07
Abstract Abstract
This document updates RFC 4120 in order to specify an extension in This document updates RFC 4120 in order to specify an extension in
the Kerberos protocol. It defines a new authorization data type AD- the Kerberos protocol. It defines a new authorization data type AD-
AUTHENTICATION-INDICATOR. The purpose of introducing this data type AUTHENTICATION-INDICATOR. The purpose of introducing this data type
is to include an indicator of the strength of a client's is to include an indicator of the strength of a client's
authentication in service tickets so that application services can authentication in service tickets so that application services can
use it as an input into policy decisions. use it as an input into policy decisions.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 8, 2017. This Internet-Draft will expire on August 13, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Document Conventions . . . . . . . . . . . . . . . . . . . . 2 2. Document Conventions . . . . . . . . . . . . . . . . . . . . 2
3. AD Type Specification . . . . . . . . . . . . . . . . . . . . 2 3. AD Type Specification . . . . . . . . . . . . . . . . . . . . 3
4. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . . 3 4. Assigned Numbers . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . 4 7.1. Normative References . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . 5
Appendix A. ASN.1 Module . . . . . . . . . . . . . . . . . . . . 6 Appendix A. ASN.1 Module . . . . . . . . . . . . . . . . . . . . 6
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 6 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
skipping to change at page 2, line 39 skipping to change at page 2, line 39
authentication as well as multi-factor authentication using one-time authentication as well as multi-factor authentication using one-time
password devices, public-key cryptography and other pre- password devices, public-key cryptography and other pre-
authentication schemes. Implementations that offer pre- authentication schemes. Implementations that offer pre-
authentication mechanisms supporting significantly different authentication mechanisms supporting significantly different
strengths of client authentication may choose to keep track of the strengths of client authentication may choose to keep track of the
strength of the authentication that was used, for use as an input strength of the authentication that was used, for use as an input
into policy decisions. into policy decisions.
This document specifies a new authorization data type to convey This document specifies a new authorization data type to convey
authentication strength information to application services. authentication strength information to application services.
Elements of this type appear within an AD-CAMMAC [RFC7751] container. Elements of this type appear within an AD-CAMMAC (authorization data
type Container Authenticated by Multiple Message Authentication
Codes) [RFC7751] container.
2. Document Conventions 2. Document Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. AD Type Specification 3. AD Type Specification
The KDC MAY include authorization data of ad-type 97, wrapped in AD- The Key Distribution Center (KDC) MAY include authorization data of
CAMMAC, in initial credentials. The KDC MAY copy it from a ticket- ad-type 97, wrapped in AD-CAMMAC, in initial credentials. The KDC
granting ticket into service tickets. MAY copy it from a ticket-granting ticket into service tickets.
The corresponding ad-data field contains the DER encoding of the The corresponding ad-data field contains the DER encoding [X.690] of
following ASN.1 type: the following ASN.1 [X.680] type:
AD-AUTHENTICATION-INDICATOR ::= SEQUENCE OF UTF8String AD-AUTHENTICATION-INDICATOR ::= SEQUENCE OF UTF8String
Each UTF8String value is a short string that indicates that a Each UTF8String value is a short string that indicates that a
particular set of requirements was met during the initial particular set of requirements was met during the initial
authentication. These strings are intended to be compared against authentication. These strings are intended to be compared against
known values. They are not intended to store structured data. Each known values. They are not intended to store structured data. Each
string MUST be either: string MUST be either:
* A URI which references a Level of Assurance Profile [RFC6711] * A URI which references a Level of Assurance Profile [RFC6711]
skipping to change at page 5, line 5 skipping to change at page 5, line 10
[RFC6113] Hartman, S. and L. Zhu, "A Generalized Framework for [RFC6113] Hartman, S. and L. Zhu, "A Generalized Framework for
Kerberos Pre-Authentication", RFC 6113, Kerberos Pre-Authentication", RFC 6113,
DOI 10.17487/RFC6113, April 2011, DOI 10.17487/RFC6113, April 2011,
<http://www.rfc-editor.org/info/rfc6113>. <http://www.rfc-editor.org/info/rfc6113>.
[RFC7751] Sorce, S. and T. Yu, "Kerberos Authorization Data [RFC7751] Sorce, S. and T. Yu, "Kerberos Authorization Data
Container Authenticated by Multiple Message Authentication Container Authenticated by Multiple Message Authentication
Codes (MACs)", RFC 7751, DOI 10.17487/RFC7751, March 2016, Codes (MACs)", RFC 7751, DOI 10.17487/RFC7751, March 2016,
<http://www.rfc-editor.org/info/rfc7751>. <http://www.rfc-editor.org/info/rfc7751>.
[X.680] ITU-T, "Information technology -- Abstract Syntax Notation
One (ASN.1): Specification of basic notation -- ITU-T
Recommendation X.680 (ISO/IEC International Standard
8824-1:2008)", 2008.
[X.690] ITU-T, "Information technology -- ASN.1 encoding rules:
Specification of Basic Encoding Rules (BER), Canonical
Encoding Rules (CER) and Distinguished Encoding Rules
(DER) -- ITU-T Recommendation X.690 (ISO/IEC International
Standard 8825-1:2008)", 2008.
7.2. Informative References 7.2. Informative References
[RFC6711] Johansson, L., "An IANA Registry for Level of Assurance [RFC6711] Johansson, L., "An IANA Registry for Level of Assurance
(LoA) Profiles", RFC 6711, DOI 10.17487/RFC6711, August (LoA) Profiles", RFC 6711, DOI 10.17487/RFC6711, August
2012, <http://www.rfc-editor.org/info/rfc6711>. 2012, <http://www.rfc-editor.org/info/rfc6711>.
Appendix A. ASN.1 Module Appendix A. ASN.1 Module
KerberosV5AuthenticationIndicators { KerberosV5AuthenticationIndicators {
iso(1) identified-organization(3) dod(6) internet(1) iso(1) identified-organization(3) dod(6) internet(1)
 End of changes. 8 change blocks. 
11 lines changed or deleted 24 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/