draft-ietf-kitten-extended-mech-inquiry-03.txt   draft-ietf-kitten-extended-mech-inquiry-04.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: August 28, 2008 February 25, 2008 Expires: September 22, 2008 March 21, 2008
Extended Generic Security Service Mechanism Inquiry APIs Extended Generic Security Service Mechanism Inquiry APIs
draft-ietf-kitten-extended-mech-inquiry-03.txt draft-ietf-kitten-extended-mech-inquiry-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. 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
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 28, 2008. This Internet-Draft will expire on September 22, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
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
skipping to change at page 2, line 15 skipping to change at page 2, line 15
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. List of Known Mechanism Attributes . . . . . . . . . . . . 4 3.2. List of Known Mechanism Attributes . . . . . . . . . . . . 4
3.3. Mechanism Attribute Sets of Existing Mechs . . . . . . . . 6 3.3. Mechanism Attribute Sets of Existing Mechs . . . . . . . . 6
3.4. New GSS-API Function Interfaces . . . . . . . . . . . . . 7 3.4. New GSS-API Function Interfaces . . . . . . . . . . . . . 7
3.4.1. GSS_Indicate_mechs_by_attr() . . . . . . . . . . . . . . . 8 3.4.1. Mechanism Attribute Criticality . . . . . . . . . . . . . 8
3.4.2. GSS_Inquire_attrs_for_mech() . . . . . . . . . . . . . . . 8 3.4.2. GSS_Indicate_mechs_by_attr() . . . . . . . . . . . . . . . 8
3.4.3. GSS_Display_mech_attr() . . . . . . . . . . . . . . . . . 9 3.4.3. GSS_Inquire_attrs_for_mech() . . . . . . . . . . . . . . . 9
3.4.4. New Major Status Values . . . . . . . . . . . . . . . . . 9 3.4.4. GSS_Display_mech_attr() . . . . . . . . . . . . . . . . . 9
3.4.5. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 9 3.4.5. New Major Status Values . . . . . . . . . . . . . . . . . 10
4. Requirements for Mechanism Designers . . . . . . . . . . . 10 3.4.6. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . 10 4. Requirements for Mechanism Designers . . . . . . . . . . . 11
6. Security considerations . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . 11 6. Security considerations . . . . . . . . . . . . . . . . . 11
7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . 12
7.2. Informative References . . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . 11 7.2. Informative References . . . . . . . . . . . . . . . . . . 12
Intellectual Property and Copyright Statements . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . 12
Intellectual Property and Copyright Statements . . . . . . 13
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
GSS-API [RFC2743] mechanisms have a number of properties that may be GSS-API [RFC2743] mechanisms have a number of properties that may be
skipping to change at page 3, line 37 skipping to change at page 3, line 37
3. New GSS-API Interfaces 3. New GSS-API Interfaces
We introduce a new concept: that of mechanism attributes. By We introduce a new concept: that of mechanism attributes. By
allowing applications to query the set of attributes associated with allowing applications to query the set of attributes associated with
individual mechanisms and to find out which mechanisms support a individual mechanisms and to find out which mechanisms support a
given set of attributes we allow applications to select mechanisms given set of attributes we allow applications to select mechanisms
based on their attributes yet without having to hardcode mechanism based on their attributes yet without having to hardcode mechanism
OIDs. OIDs.
Section 3.1 describes the mechanism attributes concept. Sections Section 3.1 describes the mechanism attributes concept. Sections
3.4.1, 3.4.2 and 3.4.3 describe three new interfaces that deal in 3.4.2, 3.4.3 and 3.4.4 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 mechanisms and pseudo-
needed in order to facilitate the programmatic selection of mechanisms is needed in order to facilitate the programmatic
mechanisms. selection of mechanisms. Pseudo-mechanisms are mechanisms which make
reference to other mechanisms in order to provide their services.
For example, SPNEGO is a pseudo-mechanism, for without other
mechanisms SPNEGO is useless.
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] <TBA by IANA> [1.3.6.1.5.5.13 appears to be available; see
http://www.iana.org/assignments/smi-numbers]
Each mechanism has a set of mechanism attributes that it supports as Each mechanism has a set of mechanism attributes that it supports as
described in its specification. described in its specification.
3.2. List of Known Mechanism Attributes 3.2. List of Known Mechanism Attributes
+-------------------------+---------+-------------------------+ +-------------------------+---------+-------------------------+
| Mech Attr Name | OID Arc | Arc Name | | Mech Attr Name | OID Arc | Arc Name |
+-------------------------+---------+-------------------------+ +-------------------------+---------+-------------------------+
| GSS_C_MA_MECH_CONCRETE | (1) | concrete-mech | | GSS_C_MA_MECH_CONCRETE | (1) | concrete-mech |
skipping to change at page 4, line 40 skipping to change at page 4, line 44
| GSS_C_MA_AUTH_INIT | (10) | auth-init-princ | | GSS_C_MA_AUTH_INIT | (10) | auth-init-princ |
| GSS_C_MA_AUTH_TARG | (11) | auth-targ-princ | | GSS_C_MA_AUTH_TARG | (11) | auth-targ-princ |
| GSS_C_MA_AUTH_INIT_INIT | (12) | auth-init-princ-initial | | GSS_C_MA_AUTH_INIT_INIT | (12) | auth-init-princ-initial |
| GSS_C_MA_AUTH_TARG_INIT | (13) | auth-targ-princ-initial | | GSS_C_MA_AUTH_TARG_INIT | (13) | auth-targ-princ-initial |
| GSS_C_MA_AUTH_INIT_ANON | (14) | auth-init-princ-anon | | GSS_C_MA_AUTH_INIT_ANON | (14) | auth-init-princ-anon |
| GSS_C_MA_AUTH_TARG_ANON | (15) | auth-targ-princ-anon | | GSS_C_MA_AUTH_TARG_ANON | (15) | auth-targ-princ-anon |
| GSS_C_MA_DELEG_CRED | (16) | deleg-cred | | GSS_C_MA_DELEG_CRED | (16) | deleg-cred |
| GSS_C_MA_INTEG_PROT | (17) | integ-prot | | GSS_C_MA_INTEG_PROT | (17) | integ-prot |
| GSS_C_MA_CONF_PROT | (18) | conf-prot | | GSS_C_MA_CONF_PROT | (18) | conf-prot |
| GSS_C_MA_MIC | (19) | mic | | GSS_C_MA_MIC | (19) | mic |
| GSS_C_MA_WRAP | (20) | wap | | GSS_C_MA_WRAP | (20) | wrap |
| 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_PFS | (25) | pfs | | GSS_C_MA_PFS | (25) | pfs |
| GSS_C_MA_COMPRESS | (26) | compress | | GSS_C_MA_COMPRESS | (26) | compress |
| GSS_C_MA_CTX_TRANS | (27) | context-transfer | | GSS_C_MA_CTX_TRANS | (27) | context-transfer |
| <reserved> | (28..) | | | <reserved> | (28..) | |
+-------------------------+---------+-------------------------+ +-------------------------+---------+-------------------------+
skipping to change at page 5, line 39 skipping to change at page 5, line 44
| | NOT be used as a default mechanism. | | | NOT be used as a default mechanism. |
| GSS_C_MA_ITOK_FRAMED | Indicates that the given mechanism's | | GSS_C_MA_ITOK_FRAMED | Indicates that the given mechanism's |
| | initial context tokens are properly | | | initial context tokens are properly |
| | framed as per-section 3.1 of rfc2743. | | | framed as per-section 3.1 of rfc2743. |
| GSS_C_MA_AUTH_INIT | Indicates support for authentication of | | GSS_C_MA_AUTH_INIT | Indicates support for authentication of |
| | initiator to acceptor. | | | initiator to acceptor. |
| GSS_C_MA_AUTH_TARG | Indicates support for authentication of | | GSS_C_MA_AUTH_TARG | Indicates support for authentication of |
| | acceptor to initiator. | | | acceptor to 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. "Initial authentication" |
| | refers to the use of passwords, or keys |
| | stored on tokens, for authentication. |
| | Whether a mechanism supports initial |
| | authentication may depend on IETF |
| | consensus (see Security |
| | Considerations). |
| 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 | | GSS_C_MA_AUTH_INIT_ANON | Indicates support for |
| | GSS_C_NT_ANONYMOUS as an initiator | | | GSS_C_NT_ANONYMOUS as an initiator |
| | principal name. | | | principal name. |
| GSS_C_MA_AUTH_TARG_ANON | Indicates support for | | GSS_C_MA_AUTH_TARG_ANON | Indicates support for |
| | GSS_C_NT_ANONYMOUS as a target | | | GSS_C_NT_ANONYMOUS as a target |
| | principal name. | | | principal name. |
| GSS_C_MA_DELEG_CRED | Indicates support for credential | | GSS_C_MA_DELEG_CRED | Indicates support for credential |
skipping to change at page 7, line 28 skipping to change at page 7, line 39
o GSS_C_MA_CTX_TRANS (some implementations, using implementation- o GSS_C_MA_CTX_TRANS (some implementations, using 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 [RFC4178] provides the following attributes: The SPNEGO mechanism [RFC4178] 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 use of SPNEGO.
All other mechanisms' attributes will be described elsewhere. All other mechanisms' attributes will be described elsewhere.
3.4. New GSS-API Function Interfaces 3.4. 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 and what mechanisms provide what features. mechanism and what mechanisms provide what features.
These new interfaces are all OPTIONAL. These new interfaces are all OPTIONAL.
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, etc.). (concrete, mechanism negotiation pseudo-mechanism, etc.).
3.4.1. GSS_Indicate_mechs_by_attr() 3.4.1. Mechanism Attribute Criticality
Mechanism attributes may be added at any time. Not only may
attributes be added to the list of known mechanism attributes at any
time, but the set of mechanism attributes supported by a mechanism
can be changed at any time.
For example, new attributes might be added to reflect whether a
mechanism's initiator must contact online infrastructure, and/or
whether the acceptor must do so. In this example the Kerberos V
mechanism would gain a new attribute even though the mechanism itself
is not modified.
Applications making use of attributes not defined herein then would
have no way of knowing whether a GSS-API implementation and its
mechanisms know about new mechanism attributes. To address this
problem GSS_Indicate_mechs_by_attr() and GSS_Indicate_mechs_by_attr()
support a notion of critical mechanism attributes. Applications can
search for mechanisms that understand mechanism attributes that are
critical to the application, and the application may ask what
mechanism attributes are understood by a given mechanism.
3.4.2. 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
o critical_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_*
OIDs that the mechanisms indicated in the mechs output parameter
MUST understand (i.e., mechs must know whether critical attributes
are or are not supported)
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER
o minor_status INTEGER, o minor_status INTEGER
o mechs SET OF OBJECT IDENTIFIER -- set of mechanisms that support o mechs SET OF OBJECT IDENTIFIER -- set of mechanisms that support
-- the desired_mech_attrs but not the except_mech_attrs. the given desired_mech_attrs but not the except_mech_attrs, and
all of which understand the given critical_mech_attrs
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates success; the output mechs parameter MAY o GSS_S_COMPLETE indicates success; the output mechs parameter MAY
be the empty set (GSS_C_NO_OID_SET). be the empty set (GSS_C_NO_OID_SET).
o GSS_BAD_MECH_ATTR indicates that at least one mechanism attribute
OID in desired_mech_attrs or except_mech_attrs is unknown to the
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.
GSS_Indicate_mechs_by_mech_attrs() returns the set of mechanism OIDs GSS_Indicate_mechs_by_attrs() returns the set of OIDs corresponding
that offer at least the desired_mech_attrs but none of the to mechanisms that offer at least the desired_mech_attrs but none of
except_mech_attrs. the except_mech_attrs, and which understand all of the attributes
listed in critical_mech_attrs.
When desired_mech_attrs and except_mech_attrs are the empty set this When all three set of OID input parameters 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.
desired_mechs input parameter to a set of a single GSS_C_MA_MECH*
feature applications can obtain the list of all supported mechanisms
of a given type (concrete, etc...).
3.4.2. GSS_Inquire_attrs_for_mech() 3.4.3. 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_*) supported by the mechanism
o known_mech_attrs SET OF OBJECT IDENTIFIER -- set of mech_attrs
OIDs known to the mechanism implementation.
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates success; the output mech_attrs parameter o GSS_S_COMPLETE indicates success; the output mech_attrs parameter
MAY be the empty set (GSS_C_NO_OID_SET). MAY be the empty set (GSS_C_NO_OID_SET).
o GSS_S_BAD_MECH indicates that the mechanism named by the mech o GSS_S_BAD_MECH indicates that the mechanism named by the mech
parameter does not exist or that mech is GSS_C_NO_OID and no parameter does not exist or that mech is GSS_C_NO_OID and no
default mechanism could be determined. default mechanism could be determined.
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.
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.
3.4.3. GSS_Display_mech_attr() 3.4.4. 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 minor_status INTEGER, o major_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
attribute attribute
o long_desc OCTET STRING -- a longer description of the mechanism o long_desc OCTET STRING -- a longer description of the mechanism
attribute attribute
Return major_status codes: Return major_status codes:
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.4.4. New Major Status Values 3.4.5. 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 of the GSS-API [RFC2744] GSS_S_BAD_MECH_ATTR shall For the C-bindings of the GSS-API [RFC2744] GSS_S_BAD_MECH_ATTR shall
have a routine error number of 19 (this is shifted to the left by have a routine error number of 19 (this is shifted to the left by
GSS_C_ROUTINE_ERROR_OFFSET). GSS_C_ROUTINE_ERROR_OFFSET).
3.4.5. C-Bindings 3.4.6. 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_attrs(
OM_uint32 *minor_status, OM_uint32 *minor_status,
const gss_OID_set desired_mech_attrs, const gss_OID_set desired_mech_attrs,
const gss_OID_set except_mech_attrs,
const gss_OID_set critical_mech_attrs,
gss_OID_set *mechs); gss_OID_set *mechs);
OM_uint32 gss_inquire_mech_attrs_for_mech( OM_uint32 gss_inquire_attrs_for_mech(
OM_uint32 *minor_status, OM_uint32 *minor_status,
const gss_OID mech, const gss_OID mech,
gss_OID_set *mech_attrs); gss_OID_set *mech_attrs,
gss_OID_set *known_mech_attrs);
OM_uint32 gss_display_mech_attr( OM_uint32 gss_display_mech_attr(
OM_uint32 *minor_status, OM_uint32 *minor_status,
const gss_OID mech_attr, const gss_OID mech_attr,
gss_buffer_t name, gss_buffer_t name,
gss_buffer_t short_desc, gss_buffer_t short_desc,
gss_buffer_t long_desc); gss_buffer_t long_desc);
Figure 1 Figure 1
4. Requirements for Mechanism Designers 4. Requirements for Mechanism Designers
All future GSS-API mechanism specifications MUST: All future GSS-API mechanism specifications MUST:
o list the set of GSS-API mechanism attributes associated with them o list the set of GSS-API mechanism attributes associated with them
5. IANA Considerations 5. IANA Considerations
The namsepace of programming language symbols with names beginning The namsepace of programming language symbols with names beginning
with GSS_C_MA_* is reserved for allocation by IESG Protocol Action with GSS_C_MA_* is reserved for allocation by IESG Protocol Action.
(probably in the specifications of future GSS-API mechanisms). The IANA should allocate a base OID, as an arc of 1.3.6.1.5.5, for
the set of GSS_C_MA_* described herein, and it should register all of
the GSS_C_MA_* values described in Section 3.2
6. Security considerations 6. Security considerations
This document specifies extensions to a security-related API. It This document specifies extensions to a security-related API. It
imposes new requirements on future GSS-API mechanisms, and the imposes new requirements on future GSS-API mechanisms, and the
specification of future protocols that use the GSS-API should make specification of future protocols that use the GSS-API should make
reference to this document where applicable. The ability to inquire reference to this document where applicable. The ability to inquire
about specific properties of mechanisms should improve security. about specific properties of mechanisms should improve security.
The semantics of each mechanism attribute may include a security
component.
Application developers must understand that mechanism attributes may
be added at any time, both, to the set of known mechanism attributes,
as well as to existing mechanism's sets of supported mechanism
attributes. Therefore application developers using the APIs
described herein must understand what mechanism attributes their
applications depend critically on, and must use the mechanism
attribute criticality features of these APIs.
7. References 7. References
7.1. Normative References 7.1. Normative References
[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. Informative References 7.2. Informative References
 End of changes. 34 change blocks. 
59 lines changed or deleted 109 lines changed or added

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