Generic Security Service API Version 2: Java Bindings Update
draft-ietf-kitten-rfc5653bis-05

Document Type Active Internet-Draft (kitten WG)
Last updated 2017-08-04
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Matt Rogers
Shepherd write-up Show (last changed 2017-04-11)
IESG IESG state Publication Requested::AD Followup
Consensus Boilerplate Yes
Telechat date
Responsible AD Eric Rescorla
Send notices to mrogers@redhat.com
Network Working Group                                        M. Upadhyay
Internet-Draft                                                    Google
Obsoletes: 5653 (if approved)                                 S. Malkani
Intended status: Standards Track                           ActivIdentity
Expires: February 5, 2018                                        W. Wang
                                                                  Oracle
                                                          August 4, 2017

      Generic Security Service API Version 2: Java Bindings Update
                    draft-ietf-kitten-rfc5653bis-05

Abstract

   The Generic Security Services Application Program Interface (GSS-API)
   offers application programmers uniform access to security services
   atop a variety of underlying cryptographic mechanisms.  This document
   updates the Java bindings for the GSS-API that are specified in
   "Generic Security Service API Version 2 : Java Bindings Update" (RFC
   5653).  This document obsoletes RFC 5653 by adding a new output token
   field to the GSSException class so that when the initSecContext or
   acceptSecContext methods of the GSSContext class fails it has a
   chance to emit an error token which can be sent to the peer for
   debugging or informational purpose.  The stream-based GSSContext
   methods are also removed in this version.

   The GSS-API is described at a language-independent conceptual level
   in "Generic Security Service Application Program Interface Version 2,
   Update 1" (RFC 2743).  The GSS-API allows a caller application to
   authenticate a principal identity, to delegate rights to a peer, and
   to apply security services such as confidentiality and integrity on a
   per-message basis.  Examples of security mechanisms defined for GSS-
   API are "The Simple Public-Key GSS-API Mechanism" (RFC 2025) and "The
   Kerberos Version 5 Generic Security Service Application Program
   Interface (GSS-API) Mechanism: Version 2" (RFC 4121).

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

Upadhyay, et al.        Expires February 5, 2018                [Page 1]
Internet-Draft       draft-ietf-kitten-rfc5653bis-05         August 2017

   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 February 5, 2018.

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   6
   2.  GSS-API Operational Paradigm  . . . . . . . . . . . . . . . .   7
   3.  Additional Controls . . . . . . . . . . . . . . . . . . . . .   8
     3.1.  Delegation  . . . . . . . . . . . . . . . . . . . . . . .   9
     3.2.  Mutual Authentication . . . . . . . . . . . . . . . . . .  10
     3.3.  Replay and Out-of-Sequence Detection  . . . . . . . . . .  11
     3.4.  Anonymous Authentication  . . . . . . . . . . . . . . . .  11
Show full document text