draft-ietf-kitten-gssapi-v3-guide-to-00.txt   draft-ietf-kitten-gssapi-v3-guide-to-01.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: July 26, 2005 January 25, 2005 Expires: April 19, 2006 October 16, 2005
Guide to the GSS-APIv3 Guide to the GSS-APIv3
draft-ietf-kitten-gssapi-v3-guide-to-00.txt draft-ietf-kitten-gssapi-v3-guide-to-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
and any of which I become aware will be disclosed, in accordance with have been or will be disclosed, and any of which he or she becomes
RFC 3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 26, 2005. This Internet-Draft will expire on April 19, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005).
Abstract Abstract
Extensions to the GSS-APIv2 are needed for a number of reasons. This Extensions to the GSS-APIv2 are needed for a number of reasons. This
documents describes the extensions being proposed, the resons, documents describes the extensions being proposed, the resons,
possible future directions, and portability, IANA and security possible future directions, and portability, IANA and security
considerations. This document does not define any protocol or considerations. This document does not define any protocol or
interface and is purely informational. interface and is purely informational.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . . 3 1. Conventions used in this document . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. A Pseudo-Mechanism OID for the GSS-API Itself . . . . . . . . 5 3. A Pseudo-Mechanism OID for the GSS-API Itself . . . . . . . . 6
4. Mechanism Attribute Inquiry Facilities . . . . . . . . . . . . 6 4. Mechanism Attribute Inquiry Facilities . . . . . . . . . . . . 7
5. Security Context Extensibility Extensions . . . . . . . . . . 7 5. Security Context Extensibility Extensions . . . . . . . . . . 8
6. Credential Extensibility Extensions . . . . . . . . . . . . . 8 6. Credential Extensibility Extensions . . . . . . . . . . . . . 9
7. Credential Export/Import . . . . . . . . . . . . . . . . . . . 9 7. Credential Export/Import . . . . . . . . . . . . . . . . . . . 10
8. GSS_Store_cred() . . . . . . . . . . . . . . . . . . . . . . . 10 8. GSS_Store_cred() . . . . . . . . . . . . . . . . . . . . . . . 11
9. Pseudo-Mechanism Stacking . . . . . . . . . . . . . . . . . . 11 9. Pseudo-Mechanism Stacking . . . . . . . . . . . . . . . . . . 12
10. Naming Extensions . . . . . . . . . . . . . . . . . . . . . . 12 10. Naming Extensions . . . . . . . . . . . . . . . . . . . . . . 13
11. Additional Name Types . . . . . . . . . . . . . . . . . . . . 13 11. Additional Name Types . . . . . . . . . . . . . . . . . . . . 14
12. GSS_Pseudo_random() . . . . . . . . . . . . . . . . . . . . . 14 12. GSS_Pseudo_random() . . . . . . . . . . . . . . . . . . . . . 15
13. Channel Bindings Specifications . . . . . . . . . . . . . . . 15 13. Channel Bindings Specifications . . . . . . . . . . . . . . . 16
14. Semantic and Miscallaneous Extensions . . . . . . . . . . . . 16 14. Semantic and Miscallaneous Extensions . . . . . . . . . . . . 17
15. Portability Considerations . . . . . . . . . . . . . . . . . . 17 15. Portability Considerations . . . . . . . . . . . . . . . . . . 18
16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
17. Security Considerations . . . . . . . . . . . . . . . . . . . 19 17. Security Considerations . . . . . . . . . . . . . . . . . . . 20
18. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . 19 18. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 19 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 21
Intellectual Property and Copyright Statements . . . . . . . . 20 Intellectual Property and Copyright Statements . . . . . . . . 22
1. Conventions used in this document 1. Conventions used in this document
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
[NOTE: the references section is current fairly empty; the various [NOTE: the references section is current fairly empty; the various
skipping to change at page 11, line 15 skipping to change at page 12, line 15
9. Pseudo-Mechanism Stacking 9. Pseudo-Mechanism Stacking
A number of pseudo-mechanisms are being proposed which are designed A number of pseudo-mechanisms are being proposed which are designed
to "stack" atop other mechanisms. The possiblities are many, to "stack" atop other mechanisms. The possiblities are many,
including: a compression mechanism, a perfect forward security including: a compression mechanism, a perfect forward security
mechanism, an many others. mechanism, an many others.
The GSS-APIv2 only had concrete mechanisms and one pseudo-mechanism The GSS-APIv2 only had concrete mechanisms and one pseudo-mechanism
(SPNEGO) available. With this proposal the mechanism taxonomy is (SPNEGO) available. With this proposal the mechanism taxonomy is
quite expanded: quite expanded:
Concrete mechanisms (e.g., the Kerberos V mechanism) Concrete mechanisms (e.g., the Kerberos V mechanism)
Composite mechanisms (a concrete mechanism composed with one or Composite mechanisms (a concrete mechanism composed with one or
more stackable pseudo-mechanisms) more stackable pseudo-mechanisms)
Stackable pseudo-mechanisms Stackable pseudo-mechanisms
Other pseudo-mechanisms (e.g., SPNEGO, the GSS-API itself) Other pseudo-mechanisms (e.g., SPNEGO, the GSS-API itself)
Although composed mechanisms may be made available for use by Although composed mechanisms may be made available for use by GSS-
GSS-APIv2 applications without any further extensions, use of APIv2 applications without any further extensions, use of stackable
stackable pseudo-mechanisms can complicate mechanism negotiation; pseudo-mechanisms can complicate mechanism negotiation; additionally,
additionally, discovery of mechanisms appropriate for use in one or discovery of mechanisms appropriate for use in one or another context
another context would require hard-coding information about them in would require hard-coding information about them in GSS-APIv2
GSS-APIv2 applications. Extensions to the GSS-APIv2 could facilitate applications. Extensions to the GSS-APIv2 could facilitate use of
use of composite. composite.
The mechanism attribute inquiry facilities, together with the The mechanism attribute inquiry facilities, together with the
forllowing additional interfaces, provide for a complete interface to forllowing additional interfaces, provide for a complete interface to
mechanism composition and for managing the complexity of mechanism mechanism composition and for managing the complexity of mechanism
negotiation: negotiation:
GSS_Compose_oid() GSS_Compose_oid()
GSS_Decompose_oid() GSS_Decompose_oid()
GSS_Release_oid() GSS_Release_oid()
GSS_Indicate_negotiable_mechs() GSS_Indicate_negotiable_mechs()
GSS_Negotiate_mechs() GSS_Negotiate_mechs()
10. Naming Extensions 10. Naming Extensions
Some applications make use of exported names, as produced by Some applications make use of exported names, as produced by
GSS_Export_name(), to create/manage/evaluate access control lists; we GSS_Export_name(), to create/manage/evaluate access control lists; we
call this name-based authorization. call this name-based authorization.
Exported names typically encode names that are meant for display to Exported names typically encode names that are meant for display to
humans, not internal identifiers. humans, not internal identifiers.
skipping to change at page 16, line 8 skipping to change at page 17, line 8
12. GSS_Pseudo_random() 12. GSS_Pseudo_random()
<Decribe GSS_Pseudo_random() and the need for it.> <Decribe GSS_Pseudo_random() and the need for it.>
13. Channel Bindings Specifications 13. Channel Bindings Specifications
14. Semantic and Miscallaneous Extensions 14. Semantic and Miscallaneous Extensions
The GSS-APIv2 specifications say nothing about the thread-safety, The GSS-APIv2 specifications say nothing about the thread-safety,
much less the fork-safety, of the GSS-API. Thread-safety and much less the fork-safety, of the GSS-API. Thread-safety and fork-
fork-safety are, after all, platform- and/or language-specific safety are, after all, platform- and/or language-specific matters.
matters. But as support for multi-threading spreads the matter of But as support for multi-threading spreads the matter of thread-
thread-safety cannot be avoided. The matter of fork-safety is safety cannot be avoided. The matter of fork-safety is specific to
specific to platforms that provide a "fork()" function, or similar. platforms that provide a "fork()" function, or similar.
<describe the GSS-APIv3's thread-safety requirements> <describe the GSS-APIv3's thread-safety requirements>
<reference the portability considerations section> <reference the portability considerations section>
15. Portability Considerations 15. Portability Considerations
The potential for additional generic, mechanism-specific, language The potential for additional generic, mechanism-specific, language
binding-specific and, most importantly, semantic extensions to the binding-specific and, most importantly, semantic extensions to the
GSS-APIv3 may create application portability problems. The mechanism GSS-APIv3 may create application portability problems. The mechanism
attribute inquiry facilities of the GSS-APIv3 and the attribute inquiry facilities of the GSS-APIv3 and the pseudo-
pseudo-mechanism OID for the GSS-API itself double as a run-time mechanism OID for the GSS-API itself double as a run-time facility
facility for discovery of feature availability. Run-time feature for discovery of feature availability. Run-time feature discovery
discovery facilities, in turn, can be used at application build-time facilities, in turn, can be used at application build-time as well by
as well by building small applications to display the available building small applications to display the available features.
features.
<...> <...>
16. IANA Considerations 16. IANA Considerations
<Describe the namespace issues associated with future minor <Describe the namespace issues associated with future minor
extensions to the GSS-APIv3 and the IANA registries to be created to extensions to the GSS-APIv3 and the IANA registries to be created to
cope with them.> cope with them.>
17. Security Considerations 17. Security Considerations
<...> <...>
18 Normative 18. Normative
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2743] Linn, J., "Generic Security Service Application Program [RFC2743] Linn, J., "Generic Security Service Application Program
Interface Version 2, Update 1", RFC 2743, January 2000. Interface Version 2, Update 1", RFC 2743, January 2000.
[RFC2744] Wray, J., "Generic Security Service API Version 2 : [RFC2744] Wray, J., "Generic Security Service API Version 2 :
C-bindings", RFC 2744, January 2000. C-bindings", RFC 2744, January 2000.
Author's Address Author's Address
Nicolas Williams Nicolas Williams
Sun Microsystems Sun Microsystems
5300 Riata Trace Ct 5300 Riata Trace Ct
Austin, TX 78727 Austin, TX 78727
US US
EMail: Nicolas.Williams@sun.com Email: Nicolas.Williams@sun.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
 End of changes. 21 change blocks. 
48 lines changed or deleted 56 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/