[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (RFC 2853) 00 01 02 03 04 05 RFC 5653

NETWORK WORKING GROUP                                         S. Malkani
Internet-Draft                                          Sun Microsystems
Expires: July 28, 2005                                  January 27, 2005


            Corrections and Updates of GSS-API Java Bindings
                  draft-ietf-kitten-rfc2853bis-00.txt

Status of this Memo

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   and any of which I become aware will be disclosed, in accordance with
   RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on July 28, 2005.

Copyright Notice

   Copyright (C) The Internet Society (2005).  All Rights Reserved.

Abstract

   This document corrects and updates the specification of the Java
   programming language bindings of the Generic Security Services
   Application Programming Interface (GSS-API).  Specifically, the error
   code values used for GSS exceptions were incorrect in the original;
   additionally, missing numeric values of the credential usage
   constants are specified.







Malkani                  Expires July 28, 2005                  [Page 1]

Internet-Draft           GSS J-Bindings Update              January 2005


Table of Contents

   1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2. Credential Usage Constant Values . . . . . . . . . . . . . . . . 4
   3. Major Status Code Constant Values  . . . . . . . . . . . . . . . 5
   4. Security Considerations  . . . . . . . . . . . . . . . . . . . . 7
   5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 8
   6. Normative  . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
      Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
      Intellectual Property and Copyright Statements . . . . . . . . . 9









































Malkani                  Expires July 28, 2005                  [Page 2]

Internet-Draft           GSS J-Bindings Update              January 2005


1.  Introduction

   This document corrects or updates two sections of the original
   [RFC2853], section 6.3.2 for GSSCredential usage flags, and section
   6.8.1 for GSS status code values.

   The original Java bindings of the GSS-API left out the specification
   of the values of the credential usage constants.

   Additionally a transcription error resulted in misalignment of the
   major GSS status codes in sections 6.8.1 and 4.12.1.








































Malkani                  Expires July 28, 2005                  [Page 3]

Internet-Draft           GSS J-Bindings Update              January 2005


2.  Credential Usage Constant Values

   GSS-API credentials are represented by the GSSCredential interface.
   Credentials provide the prerequisites which permit GSS-API peers to
   establish security contexts with each other.  A caller may designate
   that the credential elements which are to be applied for context
   initiation or acceptance be selected by default.

   RFC 2853 section 6.3.2 defines static constants for the GSSCredential
   usage flags used to determine how the credentials may be used to
   initiate or accept security contexts.

   The values for the INITIATE_AND_ACCEPT, INITIATE_ONLY and ACCEPT_ONLY
   constants are 0, 1 and 2, respectively:
   o  public static final int INITIATE_AND_ACCEPT = 0
         Credential usage flag requesting that it be able to be used for
         both context initiation and acceptance.
   o  public static final int INITIATE_ONLY = 1
         Credential usage flag requesting that it be able to be used for
         context initiation only.
   o  public static final int ACCEPT_ONLY = 2
         Credential usage flag requesting that it be able to be used for
         context acceptance only.




























Malkani                  Expires July 28, 2005                  [Page 4]

Internet-Draft           GSS J-Bindings Update              January 2005


3.  Major Status Code Constant Values

   All the GSS-API routines return two distinct values to report status
   information to the caller: GSS status codes and mechanism status
   codes.  The errors indicated via a GSS status code are generic API
   routine errors as defined in the GSS-API specification, and indicate
   errors that are independent of the underlying mechanism(s) used to
   provide the security service.

   The Java Bindings of GSS-API as specified in RFC 2853, use the Java
   exception mechanism for reporting GSS errors.  A GSSException is
   thrown whenever a fatal GSS-API error occurs including mechanism
   specific errors.  It may contain both the major and minor GSS-API
   status codes.  All Java GSS-API methods are declared as throwing this
   exception.  All the valid GSS-API status code values are declared as
   constants in the GSSException class.

   RFC 2853 section 6.8.1 specifies static constants for GSS status
   codes used to define all the major valid GSS-API error codes.

   This draft updates RFC 2853 section 6.8.1 to define the correct GSS
   status code values, and obsoletes the GSS status code values defined
   in section 4.12.1.

   The updated GSS Status code values are:
   o  public static final int BAD_BINDINGS = 1
         Incorrect channel bindings were supplied.
   o  public static final int BAD_MECH = 2
         An unsupported mechanism was requested.
   o  public static final int BAD_NAME = 3
         An invalid name was supplied.
   o  public static final int BAD_NAMETYPE = 4
         A supplied name was of an unsupported type.
   o  public static final int BAD_STATUS = 5
         An invalid status code was supplied.
   o  public static final int BAD_MIC = 6
         A token had an invalid MIC.
   o  public static final int CONTEXT_EXPIRED = 7
         The context has expired.
   o  public static final int CREDENTIALS_EXPIRED = 8
         The referenced credentials have expired.
   o  public static final int DEFECTIVE_CREDENTIAL = 9
         A supplied credential was invalid.
   o  public static final int DEFECTIVE_TOKEN = 10
         A supplied token was invalid.
   o  public static final int FAILURE = 11
         Miscellaneous failure, unspecified at the GSS-API level.
   o  public static final int NO_CONTEXT = 12



Malkani                  Expires July 28, 2005                  [Page 5]

Internet-Draft           GSS J-Bindings Update              January 2005


         Invalid context has been supplied.
   o  public static final int NO_CRED = 13
         No credentials were supplied, or the credentials were
         unavailable or inaccessible.
   o  public static final int BAD_QOP = 14
         The quality-of-protection requested could not be provided.
   o  public static final int UNAUTHORIZED = 15
         The operation is forbidden by local security policy.
   o  public static final int UNAVAILABLE = 16
         The operation or option is unavailable.
   o  public static final int DUPLICATE_ELEMENT = 17
         The requested credential element already exists.
   o  public static final int NAME_NOT_MN = 18
         The provided name was not a mechanism name.
   o  public static final int DUPLICATE_TOKEN = 19
         The token was a duplicate of an earlier version.
   o  public static final int OLD_TOKEN = 20
         The token's validity period has expired.
   o  public static final int UNSEQ_TOKEN = 21
         A latter token has already been processed.
   o  public static final int GAP_TOKEN = 22
         An expected per-message token was not received.





























Malkani                  Expires July 28, 2005                  [Page 6]

Internet-Draft           GSS J-Bindings Update              January 2005


4.  Security Considerations

   This document has no security considerations.
















































Malkani                  Expires July 28, 2005                  [Page 7]

Internet-Draft           GSS J-Bindings Update              January 2005


5.  Acknowledgements

   The author would like to thank Jeff Nisewanger, Sean Mullan and
   Nicolas Williams for their helpful input, comments and suggestions.

6  Normative

   [RFC2743]  Linn, J., "Generic Security Service Application Program
              Interface Version 2, Update 1", RFC 2743, January 2000.

   [RFC2853]  Kabat, J. and M. Upadhyay, "Generic Security Service API
              Version 2 : Java Bindings", RFC 2853, June 2000.


Author's Address

   Seema Malkani
   Sun Microsystems, Inc.
   4140 Network Circle
   Santa Clara, CA  95054
   US

   EMail: Seema.Malkani@sun.com




























Malkani                  Expires July 28, 2005                  [Page 8]

Internet-Draft           GSS J-Bindings Update              January 2005


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Malkani                  Expires July 28, 2005                  [Page 9]


Html markup produced by rfcmarkup 1.108, available from http://tools.ietf.org/tools/rfcmarkup/