draft-ietf-kitten-extended-mech-inquiry-00.txt   draft-ietf-kitten-extended-mech-inquiry-01.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: August 12, 2005 February 11, 2005 Expires: April 19, 2006 October 16, 2005
Extended Generic Security Service Mechanism Inquiry APIs Extended Generic Security Service Mechanism Inquiry APIs
draft-ietf-kitten-extended-mech-inquiry-00.txt draft-ietf-kitten-extended-mech-inquiry-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 August 12, 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
This document introduces new application programming interfaces This document introduces new application programming interfaces
(APIs) to the Generic Security Services API (GSS-API) for extended (APIs) to the Generic Security Services API (GSS-API) for extended
mechanism attribute inquiry. These interfaces are primarily intended mechanism attribute inquiry. These interfaces are primarily intended
for use in mechanism composition, but also to reduce instances of for use in mechanism composition, but also to reduce instances of
hardcoding of mechanism identifiers in GSS applications. hardcoding of mechanism identifiers in GSS applications.
These interfaces include: mechanism attributes and attribute sets, a These interfaces include: mechanism attributes and attribute sets, a
function for inquiring the attributes of a mechanism, a function for function for inquiring the attributes of a mechanism, a function for
indicating mechanisms that posses given attributes, and a function indicating mechanisms that posses given attributes, and a function
for displaying mechanism attributes. for displaying mechanism attributes.
Table of Contents Table of Contents
1. Conventions used in this document . . . . . . . . . . . . . 3 1. Conventions used in this document . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3
3. New GSS-API Interfaces . . . . . . . . . . . . . . . . . . . 3 3. New GSS-API Interfaces . . . . . . . . . . . . . . . . . . 3
3.1 Mechanism Attributes and Attribute Sets . . . . . . . . . . 3 3.1. Mechanism Attributes and Attribute Sets . . . . . . . . . 3
3.2 Determination of Attribute Sets of Composite Mechs . . . . . 4 3.2. Determination of Attribute Sets of Composite Mechs . . . . 4
3.3 List of Known Mechanism Attributes . . . . . . . . . . . . . 4 3.3. List of Known Mechanism Attributes . . . . . . . . . . . . 4
3.4 Mechanism Attribute Sets of Existing Mechs . . . . . . . . . 7 3.4. Mechanism Attribute Sets of Existing Mechs . . . . . . . . 6
3.5 New GSS-API Function Interfaces . . . . . . . . . . . . . . 8 3.5. New GSS-API Function Interfaces . . . . . . . . . . . . . 8
3.5.1 GSS_Indicate_mechs_by_attr() . . . . . . . . . . . . . . . . 9 3.5.1. GSS_Indicate_mechs_by_attr() . . . . . . . . . . . . . . . 8
3.5.2 GSS_Inquire_attrs_for_mech() . . . . . . . . . . . . . . . . 9 3.5.2. GSS_Inquire_attrs_for_mech() . . . . . . . . . . . . . . . 9
3.5.3 GSS_Display_mech_attr() . . . . . . . . . . . . . . . . . . 10 3.5.3. GSS_Display_mech_attr() . . . . . . . . . . . . . . . . . 10
3.5.4 New Major Status Values . . . . . . . . . . . . . . . . . . 10 3.5.4. New Major Status Values . . . . . . . . . . . . . . . . . 10
3.5.5 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.5.5. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 10
4. Requirements for Mechanism Designers . . . . . . . . . . . . 11 4. Requirements for Mechanism Designers . . . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . 11
6. Security considerations . . . . . . . . . . . . . . . . . . 12 6. Security considerations . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 7. References . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1 Normative . . . . . . . . . . . . . . . . . . . . . . . . . 12 7.1. Normative . . . . . . . . . . . . . . . . . . . . . . . . 12
7.2 Normative . . . . . . . . . . . . . . . . . . . . . . . . . 12 7.2. Normative . . . . . . . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . 13 Intellectual Property and Copyright Statements . . . . . . 14
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
3. New GSS-API Interfaces 3. New GSS-API Interfaces
skipping to change at page 3, line 41 skipping to change at page 3, line 41
hardcode mechanism OIDs. hardcode mechanism OIDs.
Section 3.1 describes the mechanism attributes concept. Sections Section 3.1 describes the mechanism attributes concept. Sections
3.5.1, 3.5.2 and 3.5.3 describe three new interfaces that deal in 3.5.1, 3.5.2 and 3.5.3 describe three new interfaces that deal in
mechanisms and attribute sets: mechanisms and attribute sets:
o GSS_Indicate_mechs_by_attrs() o GSS_Indicate_mechs_by_attrs()
o GSS_Inquire_attrs_for_mech() o GSS_Inquire_attrs_for_mech()
o GSS_Display_mech_attr() o GSS_Display_mech_attr()
3.1 Mechanism Attributes and Attribute Sets 3.1. Mechanism Attributes and Attribute Sets
An abstraction for the features provided by pseudo-mechanisms is An abstraction for the features provided by pseudo-mechanisms is
needed in order to facilitate the programmatic selection of needed in order to facilitate the programmatic selection of
mechanisms as well as for the programmatic composition of mechanisms. mechanisms as well as for the programmatic composition of mechanisms.
Two data types are needed: one for individual mechanism attributes Two data types are needed: one for individual mechanism attributes
and one for mechanism attribute sets. To simplify the mechanism and one for mechanism attribute sets. To simplify the mechanism
attributes interfaces we reuse the 'OID' and 'OID set' data types and attributes interfaces we reuse the 'OID' and 'OID set' data types and
model individual mechanism attribute types as OIDs. model individual mechanism attribute types as OIDs.
To this end we define an open namespace of mechanism attributes and To this end we define an open namespace of mechanism attributes and
assign them arcs off of this OID: assign them arcs off of this OID:
<TBD> [1.3.6.1.5.5.12 appears to be available, registration w/ IANA <TBD> [1.3.6.1.5.5.12 appears to be available, registration w/ IANA
TBD] TBD]
3.2 Determination of Attribute Sets of Composite Mechs 3.2. Determination of Attribute Sets of Composite Mechs
Each mechanism, composite or otherwise, has a set of mechanism Each mechanism, composite or otherwise, has a set of mechanism
attributes that it supports as specified. attributes that it supports as specified.
The mechanism attribute set of a composite mechanism is to be The mechanism attribute set of a composite mechanism is to be
determined by the top-most stackable pseudo-mechanism of the determined by the top-most stackable pseudo-mechanism of the
composite according to its own attribute set and that of the composite according to its own attribute set and that of the
remainder of the composite mechanism stack below it. remainder of the composite mechanism stack below it.
It may well be that some composite mechanisms' attribute sets consist It may well be that some composite mechanisms' attribute sets consist
of the union of those of their every component, however this need not of the union of those of their every component, however this need not
be the case and MUST NOT be assumed. be the case and MUST NOT be assumed.
Every stackable pseudo-mechanism's specification MUST specify the Every stackable pseudo-mechanism's specification MUST specify the
rules for determining the mechanism attribute set of mechanisms rules for determining the mechanism attribute set of mechanisms
composed by it. composed by it.
3.3 List of Known Mechanism Attributes 3.3. List of Known Mechanism Attributes
+-------------------------+---------+--------------------------------+ +-------------------------+--------+--------------------------------+
| Mech Attr Name | OID Arc | Arc Name | | Mech Attr Name | OID | Arc Name |
+-------------------------+---------+--------------------------------+ | | Arc | |
+-------------------------+--------+--------------------------------+
| GSS_C_MA_MECH_CONCRETE | (1) | concrete-mech | | GSS_C_MA_MECH_CONCRETE | (1) | concrete-mech |
| GSS_C_MA_MECH_STACKABLE | (2) | pseudo-mech | | GSS_C_MA_MECH_STACKABLE | (2) | pseudo-mech |
| GSS_C_MA_MECH_COMPOSITE | (3) | composite-mech | | GSS_C_MA_MECH_COMPOSITE | (3) | composite-mech |
| GSS_C_MA_MECH_NEGO | (4) | mech-negotiation-mech | | GSS_C_MA_MECH_NEGO | (4) | mech-negotiation-mech |
| GSS_C_MA_MECH_GLUE | (5) | mech-glue | | GSS_C_MA_MECH_GLUE | (5) | mech-glue |
| GSS_C_MA_NOT_MECH | (6) | not-mech | | GSS_C_MA_NOT_MECH | (6) | not-mech |
| GSS_C_MA_DEPRECATED | (7) | mech-deprecated | | GSS_C_MA_DEPRECATED | (7) | mech-deprecated |
| GSS_C_MA_NOT_DFLT_MECH | (8) | mech-not-default | | GSS_C_MA_NOT_DFLT_MECH | (8) | mech-not-default |
| GSS_C_MA_ITOK_FRAMED | (9) | initial-is-framed | | GSS_C_MA_ITOK_FRAMED | (9) | initial-is-framed |
| GSS_C_MA_AUTH_INIT | (10) | auth-init-princ | | GSS_C_MA_AUTH_INIT | (10) | auth-init-princ |
skipping to change at page 5, line 15 skipping to change at page 5, line 16
| GSS_C_MA_PROT_READY | (21) | prot-ready | | GSS_C_MA_PROT_READY | (21) | prot-ready |
| GSS_C_MA_REPLAY_DET | (22) | replay-detection | | GSS_C_MA_REPLAY_DET | (22) | replay-detection |
| GSS_C_MA_OOS_DET | (23) | oos-detection | | GSS_C_MA_OOS_DET | (23) | oos-detection |
| GSS_C_MA_CBINDINGS | (24) | channel-bindings | | GSS_C_MA_CBINDINGS | (24) | channel-bindings |
| GSS_C_MA_CBINDINGS_BIDI | (25) | channel-bindings-bidirectional | | GSS_C_MA_CBINDINGS_BIDI | (25) | channel-bindings-bidirectional |
| GSS_C_MA_CBINDINGS_NEGO | (26) | channel-bindings-negotiate | | GSS_C_MA_CBINDINGS_NEGO | (26) | channel-bindings-negotiate |
| GSS_C_MA_PFS | (27) | pfs | | GSS_C_MA_PFS | (27) | pfs |
| GSS_C_MA_COMPRESS | (28) | compress | | GSS_C_MA_COMPRESS | (28) | compress |
| GSS_C_MA_CTX_TRANS | (29) | context-transfer | | GSS_C_MA_CTX_TRANS | (29) | context-transfer |
| <reserved> | (30..) | | | <reserved> | (30..) | |
+-------------------------+---------+--------------------------------+ +-------------------------+--------+--------------------------------+
Table 1 Table 1
+---------------------------------+---------------------------------+ +-------------------------+-----------------------------------------+
| Mech Attr Name | Purpose | | Mech Attr Name | Purpose |
+---------------------------------+---------------------------------+ +-------------------------+-----------------------------------------+
| GSS_C_MA_MECH_CONCRETE | Indicates that a mech is | | GSS_C_MA_MECH_CONCRETE | Indicates that a mech is neither a |
| | neither a pseudo- mechanism nor | | | pseudo- mechanism nor a composite |
| | a composite mechanism. | | | mechanism. |
| GSS_C_MA_MECH_STACKABLE | Indicates that a mech is a | | GSS_C_MA_MECH_STACKABLE | Indicates that a mech is a |
| | pseudo-mechanism. | | | pseudo-mechanism. |
| GSS_C_MA_MECH_COMPOSITE | Indicates that a mech is a | | GSS_C_MA_MECH_COMPOSITE | Indicates that a mech is a composite |
| | composite mechanism. | | | mechanism. |
| GSS_C_MA_MECH_NEGO | Indicates that a mech | | GSS_C_MA_MECH_NEGO | Indicates that a mech negotiates other |
| | negotiates other mechs (e.g., | | | mechs (e.g., SPNEGO has this |
| | SPNEGO has this attribute). | | | attribute). |
| GSS_C_MA_MECH_GLUE | Indicates that the OID is not | | GSS_C_MA_MECH_GLUE | Indicates that the OID is not for a |
| | for a mechanism but for the | | | mechanism but for the GSS-API itself. |
| | GSS-API itself. | | GSS_C_MA_NOT_MECH | Indicates that the OID is known, yet |
| GSS_C_MA_NOT_MECH | Indicates that the OID is | | | also known not to be the OID of any |
| | known, yet also known not to be | | | GSS-API mechanism (or the GSS-API |
| | the OID of any GSS-API |
| | mechanism (or the GSS-API |
| | itself). | | | itself). |
| GSS_C_MA_DEPRECATED | Indicates that a mech (or its | | GSS_C_MA_DEPRECATED | Indicates that a mech (or its OID) is |
| | OID) is deprecated and MUST NOT | | | deprecated and MUST NOT be used as a |
| | be used as a default mechanism. |
| GSS_C_MA_NOT_DFLT_MECH | Indicates that a mech (or its |
| | OID) MUST NOT be used as a |
| | default mechanism. | | | default mechanism. |
| GSS_C_MA_ITOK_FRAMED | Indicates that the given | | GSS_C_MA_NOT_DFLT_MECH | Indicates that a mech (or its OID) MUST |
| | mechanism's initial context | | | NOT be used as a default mechanism. |
| | tokens are properly framed as | | GSS_C_MA_ITOK_FRAMED | Indicates that the given mechanism's |
| | per-section 3.1 of rfc2743. | | | initial context tokens are properly |
| GSS_C_MA_AUTH_INIT | Indicates support for | | | framed as per-section 3.1 of rfc2743. |
| | authentication of initiator to | | GSS_C_MA_AUTH_INIT | Indicates support for authentication of |
| | acceptor. | | | initiator to acceptor. |
| GSS_C_MA_AUTH_TARG | Indicates support for | | GSS_C_MA_AUTH_TARG | Indicates support for authentication of |
| | authentication of acceptor to | | | acceptor to initiator. |
| | initiator. |
| GSS_C_MA_AUTH_INIT_INIT | Indicates support for initial | | GSS_C_MA_AUTH_INIT_INIT | Indicates support for initial |
| | authentication of initiator to | | | authentication of initiator to |
| | acceptor. | | | acceptor. |
| GSS_C_MA_AUTH_TARG_INIT | Indicates support for initial | | GSS_C_MA_AUTH_TARG_INIT | Indicates support for initial |
| | authentication of acceptor to | | | authentication of acceptor to |
| | initiator. | | | initiator. |
| GSS_C_MA_AUTH_INIT_ANON | Indicates support for initiator | | GSS_C_MA_AUTH_INIT_ANON | Indicates support for initiator |
| | anonymity. | | | anonymity. |
| GSS_C_MA_AUTH_TARG_ANON | Indicates support for acceptor | | GSS_C_MA_AUTH_TARG_ANON | Indicates support for acceptor |
| | anonymity. | | | anonymity. |
| GSS_C_MA_DELEG_CRED | Indicates support for | | GSS_C_MA_DELEG_CRED | Indicates support for credential |
| | credential delegation. | | | delegation. |
| GSS_C_MA_INTEG_PROT | Indicates support for | | GSS_C_MA_INTEG_PROT | Indicates support for per-message |
| | per-message integrity | | | integrity protection. |
| | protection. | | GSS_C_MA_CONF_PROT | Indicates support for per-message |
| GSS_C_MA_CONF_PROT | Indicates support for | | | confidentiality protection. |
| | per-message confidentiality | | GSS_C_MA_MIC | Indicates support for MIC tokens. |
| | protection. | | GSS_C_MA_WRAP | Indicates support for WRAP tokens. |
| GSS_C_MA_MIC | Indicates support for MIC | | GSS_C_MA_PROT_READY | Indicates support for per-message |
| | tokens. | | | protection prior to full context |
| GSS_C_MA_WRAP | Indicates support for WRAP | | | establishment. |
| | tokens. | | GSS_C_MA_REPLAY_DET | Indicates support for replay detection. |
| GSS_C_MA_PROT_READY | Indicates support for | | GSS_C_MA_OOS_DET | Indicates support for out-of-sequence |
| | per-message protection prior to |
| | full context establishment. |
| GSS_C_MA_REPLAY_DET | Indicates support for replay |
| | detection. | | | detection. |
| GSS_C_MA_OOS_DET | Indicates support for | | GSS_C_MA_CBINDINGS | Indicates support for channel bindings. |
| | out-of-sequence detection. |
| GSS_C_MA_CBINDINGS | Indicates support for channel |
| | bindings. |
| GSS_C_MA_CBINDINGS_BIDI | Indicates that acceptors | | GSS_C_MA_CBINDINGS_BIDI | Indicates that acceptors |
| | unconditionally indicate to | | | unconditionally indicate to initiators |
| | initiators whether their | | | whether their channel bindings were |
| | channel bindings were matched | | | matched the acceptors', even when the |
| | the acceptors', even when the |
| | acceptor applications use | | | acceptor applications use |
| | GSS_C_NO_CHANNEL_BINDINGS.. | | | GSS_C_NO_CHANNEL_BINDINGS.. |
| GSS_C_MA_CBINDINGS_NEGO | Indicates that the mech acts as | | GSS_C_MA_CBINDINGS_NEGO | Indicates that the mech acts as a |
| | a signal for application | | | signal for application support for and |
| | support for and willingness to | | | willingness to use channel bindings. |
| | use channel bindings. | | GSS_C_MA_PFS | Indicates support for Perfect Forward |
| GSS_C_MA_PFS | Indicates support for Perfect | | | Security. |
| | Forward Security. | | GSS_C_MA_COMPRESS | Indicates support for compression of |
| GSS_C_MA_COMPRESS | Indicates support for | | | data inputs to GSS_Wrap(). |
| | compression of data inputs to | | GSS_C_MA_CTX_TRANS | Indicates support for security context |
| | GSS_Wrap(). | | | export/import. |
| GSS_C_MA_CTX_TRANS | Indicates support for security | +-------------------------+-----------------------------------------+
| | context export/import. |
+---------------------------------+---------------------------------+
Table 2 Table 2
3.4 Mechanism Attribute Sets of Existing Mechs 3.4. Mechanism Attribute Sets of Existing Mechs
The Kerberos V mechanism [RFC1964] [CFX] provides the following The Kerberos V mechanism [RFC1964] [CFX] provides the following
mechanism attributes: mechanism attributes:
o GSS_C_MA_MECH_CONCRETE o GSS_C_MA_MECH_CONCRETE
o GSS_C_MA_ITOK_FRAMED o GSS_C_MA_ITOK_FRAMED
o GSS_C_MA_AUTH_INIT o GSS_C_MA_AUTH_INIT
o GSS_C_MA_AUTH_TARG o GSS_C_MA_AUTH_TARG
o GSS_C_MA_DELEG_CRED o GSS_C_MA_DELEG_CRED
o GSS_C_MA_INTEG_PROT o GSS_C_MA_INTEG_PROT
o GSS_C_MA_CONF_PROT o GSS_C_MA_CONF_PROT
o GSS_C_MA_MIC o GSS_C_MA_MIC
o GSS_C_MA_WRAP o GSS_C_MA_WRAP
o GSS_C_MA_PROT_READY o GSS_C_MA_PROT_READY
o GSS_C_MA_REPLAY_DET o GSS_C_MA_REPLAY_DET
o GSS_C_MA_OOS_DET o GSS_C_MA_OOS_DET
o GSS_C_MA_CBINDINGS o GSS_C_MA_CBINDINGS
o GSS_C_MA_CTX_TRANS (some implementations, using o GSS_C_MA_CTX_TRANS (some implementations, using implementation-
implementation-specific exported context token formats) specific exported context token formats)
The Kerberos V mechanism also has a deprecated OID which has the same The Kerberos V mechanism also has a deprecated OID which has the same
mechanism attributes as above, and GSS_C_MA_DEPRECATED. mechanism attributes as above, and GSS_C_MA_DEPRECATED.
[The mechanism attributes of the SPKM family of mechanisms will be [The mechanism attributes of the SPKM family of mechanisms will be
provided in a separate document as SPKM is current being reviewed for provided in a separate document as SPKM is current being reviewed for
possibly significant changes due to problems in its specifications.] possibly significant changes due to problems in its specifications.]
The LIPKEY mechanism offers the following attributes: The LIPKEY mechanism offers the following attributes:
o GSS_C_MA_MECH_CONCRETE (should be stackable, but does not compose) o GSS_C_MA_MECH_CONCRETE (should be stackable, but does not compose)
o GSS_C_MA_ITOK_FRAMED o GSS_C_MA_ITOK_FRAMED
o GSS_C_MA_AUTH_INIT_INIT o GSS_C_MA_AUTH_INIT_INIT
o GSS_C_MA_AUTH_TARG (from SPKM-3) o GSS_C_MA_AUTH_TARG (from SPKM-3)
o GSS_C_MA_AUTH_TARG_ANON (from SPKM-3) o GSS_C_MA_AUTH_TARG_ANON (from SPKM-3)
o GSS_C_MA_INTEG_PROT o GSS_C_MA_INTEG_PROT
o GSS_C_MA_CONF_PROT o GSS_C_MA_CONF_PROT
o GSS_C_MA_REPLAY_DET o GSS_C_MA_REPLAY_DET
o GSS_C_MA_OOS_DET o GSS_C_MA_OOS_DET
o GSS_C_MA_CTX_TRANS (some implementations, using o GSS_C_MA_CTX_TRANS (some implementations, using implementation-
implementation-specific exported context token formats) specific exported context token formats)
(LIPKEY should also provide GSS_C_MA_CBINDINGS, but SPKM-3 (LIPKEY should also provide GSS_C_MA_CBINDINGS, but SPKM-3
requires clarifications on this point.) requires clarifications on this point.)
The SPNEGO mechanism [SPNEGO] provides the following attributes: The SPNEGO mechanism [SPNEGO] provides the following attributes:
o GSS_C_MA_MECH_NEGO o GSS_C_MA_MECH_NEGO
o GSS_C_MA_ITOK_FRAMED o GSS_C_MA_ITOK_FRAMED
The attributes of mechanisms negotiated by SPNEGO are not modified by The attributes of mechanisms negotiated by SPNEGO are not modified by
the use of SPNEGO. the use of SPNEGO.
All other mechanisms' attributes will be described elsewhere. All other mechanisms' attributes will be described elsewhere.
3.5 New GSS-API Function Interfaces 3.5. New GSS-API Function Interfaces
Several new interfaces are given by which, for example, GSS-API Several new interfaces are given by which, for example, GSS-API
applications may determine what features are provided by a given applications may determine what features are provided by a given
mechanism, what mechanisms provide what features and what mechanism, what mechanisms provide what features and what
compositions are legal. compositions are legal.
These new interfaces are all OPTIONAL. These new interfaces are all OPTIONAL.
In order to preserve backwards compatibility with applications that In order to preserve backwards compatibility with applications that
do not use the new interfaces GSS_Indicate_mechs() MUST NOT indicate do not use the new interfaces GSS_Indicate_mechs() MUST NOT indicate
skipping to change at page 8, line 48 skipping to change at page 8, line 33
GSS_Indicate_mechs(). GSS_Indicate_mechs().
Applications SHOULD use GSS_Indicate_mechs_by_attr() instead of Applications SHOULD use GSS_Indicate_mechs_by_attr() instead of
GSS_Indicate_mechs() wherever possible. GSS_Indicate_mechs() wherever possible.
Applications can use GSS_Indicate_mechs_by_attr() to determine what, Applications can use GSS_Indicate_mechs_by_attr() to determine what,
if any, mechanisms provide a given set of features. if any, mechanisms provide a given set of features.
GSS_Indicate_mechs_by_attr() can also be used to indicate (as in GSS_Indicate_mechs_by_attr() can also be used to indicate (as in
GSS_Indicate_mechs()) the set of available mechanisms of each type GSS_Indicate_mechs()) the set of available mechanisms of each type
(concrete, mechanism negotiation pseudo-mechanism, stackable (concrete, mechanism negotiation pseudo-mechanism, stackable pseudo-
pseudo-mechanism and composite mechanisms). mechanism and composite mechanisms).
Applications may use GSS_Inquire_attrs_for_mech() to test whether a Applications may use GSS_Inquire_attrs_for_mech() to test whether a
given composite mechanism is available and the set of features that given composite mechanism is available and the set of features that
it offers. it offers.
3.5.1 GSS_Indicate_mechs_by_attr() 3.5.1. GSS_Indicate_mechs_by_attr()
Inputs: Inputs:
o desired_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* o desired_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_*
OIDs that the mechanisms indicated in the mechs output parameter OIDs that the mechanisms indicated in the mechs output parameter
MUST offer. MUST offer.
o except_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* o except_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_*
OIDs that the mechanisms indicated in the mechs output parameter OIDs that the mechanisms indicated in the mechs output parameter
MUST NOT offer. MUST NOT offer.
Outputs: Outputs:
skipping to change at page 9, line 43 skipping to change at page 9, line 27
that offer at least the desired_mech_attrs but none of the that offer at least the desired_mech_attrs but none of the
except_mech_attrs. except_mech_attrs.
When desired_mech_attrs and except_mech_attrs are the empty set this When desired_mech_attrs and except_mech_attrs are the empty set this
function acts as a version of GSS_indicate_mechs() that outputs the function acts as a version of GSS_indicate_mechs() that outputs the
set of all supported mechanisms of all types. By setting the set of all supported mechanisms of all types. By setting the
desired_mechs input parameter to a set of a single GSS_C_MA_MECH* desired_mechs input parameter to a set of a single GSS_C_MA_MECH*
feature applications can obtain the list of all supported mechanisms feature applications can obtain the list of all supported mechanisms
of a given type (concrete, stackable, etc...). of a given type (concrete, stackable, etc...).
3.5.2 GSS_Inquire_attrs_for_mech() 3.5.2. GSS_Inquire_attrs_for_mech()
Inputs: Inputs:
o mech OBJECT IDENTIFIER -- mechanism OID o mech OBJECT IDENTIFIER -- mechanism OID
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
o mech_attrs SET OF OBJECT IDENTIFIER -- set of mech_attrs OIDs o mech_attrs SET OF OBJECT IDENTIFIER -- set of mech_attrs OIDs
(GSS_C_MA_*) (GSS_C_MA_*)
skipping to change at page 10, line 24 skipping to change at page 10, line 8
GSS_Inquire_mech_attrs_for_mech() indicates the set of mechanism GSS_Inquire_mech_attrs_for_mech() indicates the set of mechanism
attributes supported by a given mechanism. attributes supported by a given mechanism.
Because the mechanism attribute sets of composite mechanisms need not Because the mechanism attribute sets of composite mechanisms need not
be the union of their components', when called to obtain the feature be the union of their components', when called to obtain the feature
set of a composite mechanism GSS_Inquire_mech_attrs_for_mech() set of a composite mechanism GSS_Inquire_mech_attrs_for_mech()
obtains it by querying the mechanism at the top of the stack. See obtains it by querying the mechanism at the top of the stack. See
Section 3.1. Section 3.1.
3.5.3 GSS_Display_mech_attr() 3.5.3. GSS_Display_mech_attr()
Inputs: Inputs:
o mech_attr OBJECT IDENTIFIER -- mechanism attribute OID o mech_attr OBJECT IDENTIFIER -- mechanism attribute OID
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
o name OCTET STRING, -- name of mechanism attribute (e.g., o name OCTET STRING, -- name of mechanism attribute (e.g.,
GSS_C_MA_*) GSS_C_MA_*)
o short_desc OCTET STRING, -- a short description of the mechanism o short_desc OCTET STRING, -- a short description of the mechanism
skipping to change at page 10, line 50 skipping to change at page 10, line 34
o GSS_S_COMPLETE indicates success. o GSS_S_COMPLETE indicates success.
o GSS_S_BAD_MECH_ATTR indicates that the mechanism attribute o GSS_S_BAD_MECH_ATTR indicates that the mechanism attribute
referenced by the mech_attr parameter is unknown to the referenced by the mech_attr parameter is unknown to the
implementation. implementation.
o GSS_S_FAILURE indicates that the request failed for some other o GSS_S_FAILURE indicates that the request failed for some other
reason. reason.
This function can be used to obtain human-readable descriptions of This function can be used to obtain human-readable descriptions of
GSS-API mechanism attributes. GSS-API mechanism attributes.
3.5.4 New Major Status Values 3.5.4. New Major Status Values
A single new major status code is added for GSS_Display_mech_attr(): A single new major status code is added for GSS_Display_mech_attr():
o GSS_S_BAD_MECH_ATTR o GSS_S_BAD_MECH_ATTR
roughly corresponding to GSS_S_BAD_MECH, but applicable to mechanism roughly corresponding to GSS_S_BAD_MECH, but applicable to mechanism
attribute OIDs, rather than to mechanism OIDs. attribute OIDs, rather than to mechanism OIDs.
For the C-bindings GSS_S_BAD_MECH_ATTR shall have a routine error For the C-bindings GSS_S_BAD_MECH_ATTR shall have a routine error
number of 19 (this is shifted to the left by number of 19 (this is shifted to the left by
GSS_C_ROUTINE_ERROR_OFFSET). GSS_C_ROUTINE_ERROR_OFFSET).
3.5.5 C-Bindings 3.5.5. C-Bindings
#define GSS_S_BAD_MECH_ATTR (19ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_MECH_ATTR (19ul << GSS_C_ROUTINE_ERROR_OFFSET)
OM_uint32 gss_inquire_mechs_for_mech_attrs( OM_uint32 gss_inquire_mechs_for_mech_attrs(
OM_uint32 *minor_status, OM_uint32 *minor_status,
const gss_OID_set desired_mech_attrs, const gss_OID_set desired_mech_attrs,
gss_OID_set *mechs); gss_OID_set *mechs);
OM_uint32 gss_inquire_mech_attrs_for_mech( OM_uint32 gss_inquire_mech_attrs_for_mech(
OM_uint32 *minor_status, OM_uint32 *minor_status,
skipping to change at page 12, line 16 skipping to change at page 11, line 46
Allocation of arcs in the namespace of OIDs relative to the base Allocation of arcs in the namespace of OIDs relative to the base
mechanism attribute OID specified in Section 3.1 is reserved to the mechanism attribute OID specified in Section 3.1 is reserved to the
IANA. IANA.
6. Security considerations 6. Security considerations
... ...
7. References 7. References
7.1 Normative 7.1. 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.
7.2 Normative 7.2. Normative
[RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", RFC [RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism",
1964, June 1996. RFC 1964, June 1996.
[RFC2478] Baize, E. and D. Pinkas, "The Simple and Protected GSS-API [RFC2478] Baize, E. and D. Pinkas, "The Simple and Protected GSS-API
Negotiation Mechanism", RFC 2478, December 1998. Negotiation Mechanism", RFC 2478, December 1998.
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. 35 change blocks. 
125 lines changed or deleted 111 lines changed or added

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