draft-ietf-kitten-rfc5653bis-05.txt   draft-ietf-kitten-rfc5653bis-06.txt 
Network Working Group M. Upadhyay Network Working Group M. Upadhyay
Internet-Draft Google Internet-Draft Google
Obsoletes: 5653 (if approved) S. Malkani Obsoletes: 5653 (if approved) S. Malkani
Intended status: Standards Track ActivIdentity Intended status: Standards Track ActivIdentity
Expires: February 5, 2018 W. Wang Expires: May 16, 2018 W. Wang
Oracle Oracle
August 4, 2017 November 12, 2017
Generic Security Service API Version 2: Java Bindings Update Generic Security Service API Version 2: Java Bindings Update
draft-ietf-kitten-rfc5653bis-05 draft-ietf-kitten-rfc5653bis-06
Abstract Abstract
The Generic Security Services Application Program Interface (GSS-API) The Generic Security Services Application Program Interface (GSS-API)
offers application programmers uniform access to security services offers application programmers uniform access to security services
atop a variety of underlying cryptographic mechanisms. This document atop a variety of underlying cryptographic mechanisms. This document
updates the Java bindings for the GSS-API that are specified in updates the Java bindings for the GSS-API that are specified in
"Generic Security Service API Version 2 : Java Bindings Update" (RFC "Generic Security Service API Version 2 : Java Bindings Update" (RFC
5653). This document obsoletes RFC 5653 by adding a new output token 5653). This document obsoletes RFC 5653 by adding a new output token
field to the GSSException class so that when the initSecContext or field to the GSSException class so that when the initSecContext or
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Interface (GSS-API) Mechanism: Version 2" (RFC 4121). Interface (GSS-API) Mechanism: Version 2" (RFC 4121).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://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 February 5, 2018. This Internet-Draft will expire on May 16, 2018.
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 (https://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.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
skipping to change at page 91, line 30 skipping to change at page 91, line 30
While a Java method can never return a value and throw an While a Java method can never return a value and throw an
exception at the same time, we can embed the error token inside exception at the same time, we can embed the error token inside
the exception so that the caller has a chance to retrieve it. the exception so that the caller has a chance to retrieve it.
This update adds a new GSSException constructor to include this This update adds a new GSSException constructor to include this
token inside a GSSException object, and a getOutputToken() method token inside a GSSException object, and a getOutputToken() method
to retrieve the token. The specification for the initSecContext to retrieve the token. The specification for the initSecContext
and acceptSecContext methods are updated to describe the new and acceptSecContext methods are updated to describe the new
behavior. Various examples are also updated. behavior. Various examples are also updated.
This is a compatible change. New JGSS programs should make use of New JGSS programs should make use of this new feature but it is
this new feature but it is not mandatory. not mandatory. A program that intends to run with both old and
new GSS Java bindings can use reflection to check the availability
of this new method and call it accordingly.
2) Removing stream-based GSSContext methods 2) Removing stream-based GSSContext methods
The overloaded methods of GSSContext that use input and output The overloaded methods of GSSContext that use input and output
streams as the means to convey authentication and per-message GSS- streams as the means to convey authentication and per-message GSS-
API tokens as described in Section 5.15 of RFC 5653 [RFC5653] are API tokens as described in Section 5.15 of RFC 5653 [RFC5653] are
removed in this update as the wire protocol should be defined by removed in this update as the wire protocol should be defined by
an application and not a library. It's also impossible to an application and not a library. It's also impossible to
implement these methods correctly when the token has no self- implement these methods correctly when the token has no self-
framing (where the end cannot be determined) or the library has no framing (where the end cannot be determined) or the library has no
skipping to change at page 92, line 51 skipping to change at page 92, line 51
This document updates the NT_HOSTBASED_SERVICE OID value in This document updates the NT_HOSTBASED_SERVICE OID value in
section 6.2.1 to be consistent with the C-bindings in RFC 2744 section 6.2.1 to be consistent with the C-bindings in RFC 2744
[RFC2744]. [RFC2744].
13. References 13. References
13.1. Normative References 13.1. Normative References
[RFC2025] Adams, C., "The Simple Public-Key GSS-API Mechanism [RFC2025] Adams, C., "The Simple Public-Key GSS-API Mechanism
(SPKM)", RFC 2025, DOI 10.17487/RFC2025, October 1996, (SPKM)", RFC 2025, DOI 10.17487/RFC2025, October 1996,
<http://www.rfc-editor.org/info/rfc2025>. <https://www.rfc-editor.org/info/rfc2025>.
[RFC2743] Linn, J., "Generic Security Service Application Program [RFC2743] Linn, J., "Generic Security Service Application Program
Interface Version 2, Update 1", RFC 2743, Interface Version 2, Update 1", RFC 2743,
DOI 10.17487/RFC2743, January 2000, DOI 10.17487/RFC2743, January 2000,
<http://www.rfc-editor.org/info/rfc2743>. <https://www.rfc-editor.org/info/rfc2743>.
[RFC2744] Wray, J., "Generic Security Service API Version 2 : [RFC2744] Wray, J., "Generic Security Service API Version 2 :
C-bindings", RFC 2744, DOI 10.17487/RFC2744, January 2000, C-bindings", RFC 2744, DOI 10.17487/RFC2744, January 2000,
<http://www.rfc-editor.org/info/rfc2744>. <https://www.rfc-editor.org/info/rfc2744>.
[RFC2853] Kabat, J. and M. Upadhyay, "Generic Security Service API [RFC2853] Kabat, J. and M. Upadhyay, "Generic Security Service API
Version 2 : Java Bindings", RFC 2853, Version 2 : Java Bindings", RFC 2853,
DOI 10.17487/RFC2853, June 2000, DOI 10.17487/RFC2853, June 2000,
<http://www.rfc-editor.org/info/rfc2853>. <https://www.rfc-editor.org/info/rfc2853>.
[RFC4121] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos [RFC4121] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos
Version 5 Generic Security Service Application Program Version 5 Generic Security Service Application Program
Interface (GSS-API) Mechanism: Version 2", RFC 4121, Interface (GSS-API) Mechanism: Version 2", RFC 4121,
DOI 10.17487/RFC4121, July 2005, DOI 10.17487/RFC4121, July 2005,
<http://www.rfc-editor.org/info/rfc4121>. <https://www.rfc-editor.org/info/rfc4121>.
[RFC4178] Zhu, L., Leach, P., Jaganathan, K., and W. Ingersoll, "The [RFC4178] Zhu, L., Leach, P., Jaganathan, K., and W. Ingersoll, "The
Simple and Protected Generic Security Service Application Simple and Protected Generic Security Service Application
Program Interface (GSS-API) Negotiation Mechanism", Program Interface (GSS-API) Negotiation Mechanism",
RFC 4178, DOI 10.17487/RFC4178, October 2005, RFC 4178, DOI 10.17487/RFC4178, October 2005,
<http://www.rfc-editor.org/info/rfc4178>. <https://www.rfc-editor.org/info/rfc4178>.
[RFC5653] Upadhyay, M. and S. Malkani, "Generic Security Service API [RFC5653] Upadhyay, M. and S. Malkani, "Generic Security Service API
Version 2: Java Bindings Update", RFC 5653, Version 2: Java Bindings Update", RFC 5653,
DOI 10.17487/RFC5653, August 2009, DOI 10.17487/RFC5653, August 2009,
<http://www.rfc-editor.org/info/rfc5653>. <https://www.rfc-editor.org/info/rfc5653>.
13.2. Informative References 13.2. Informative References
[JLS] Gosling, J., Joy, B., Steele, G., and G. Bracha, "The Java [JLS] Gosling, J., Joy, B., Steele, G., and G. Bracha, "The Java
Language Specification", Third Edition, 2005, Language Specification", Third Edition, 2005,
<http://java.sun.com/docs/books/jls/>. <http://java.sun.com/docs/books/jls/>.
Authors' Addresses Authors' Addresses
Mayank D. Upadhyay Mayank D. Upadhyay
 End of changes. 14 change blocks. 
15 lines changed or deleted 17 lines changed or added

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