draft-ietf-kitten-extended-mech-inquiry-04.txt   draft-ietf-kitten-extended-mech-inquiry-05.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: September 22, 2008 March 21, 2008 Intended status: Standards Track March 25, 2009
Expires: September 26, 2009
Extended Generic Security Service Mechanism Inquiry APIs Extended Generic Security Service Mechanism Inquiry APIs
draft-ietf-kitten-extended-mech-inquiry-04.txt draft-ietf-kitten-extended-mech-inquiry-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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.
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 Internet- other groups may also distribute working documents as 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 September 22, 2008. This Internet-Draft will expire on September 26, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
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
to reduce instances of hardcoding of mechanism identifiers in GSS to reduce instances of hardcoding of mechanism identifiers in GSS
applications. applications.
These interfaces include: mechanism attributes and attribute sets, a These interfaces include: mechanism attributes and attribute sets, a
skipping to change at page 2, line 28 skipping to change at page 3, line 4
3.4.4. GSS_Display_mech_attr() . . . . . . . . . . . . . . . . . 9 3.4.4. GSS_Display_mech_attr() . . . . . . . . . . . . . . . . . 9
3.4.5. New Major Status Values . . . . . . . . . . . . . . . . . 10 3.4.5. New Major Status Values . . . . . . . . . . . . . . . . . 10
3.4.6. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 10 3.4.6. 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 . . . . . . . . . . . . . . . . . 11 6. Security considerations . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . 12 7. References . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1. Normative References . . . . . . . . . . . . . . . . . . . 12 7.1. Normative References . . . . . . . . . . . . . . . . . . . 12
7.2. Informative References . . . . . . . . . . . . . . . . . . 12 7.2. Informative References . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . 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 9, line 4 skipping to change at page 9, line 4
o critical_mech_attrs SET OF OBJECT IDENTIFIER -- set of GSS_C_MA_* o critical_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 understand (i.e., mechs must know whether critical attributes MUST understand (i.e., mechs must know whether critical attributes
are or are not supported) 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 given desired_mech_attrs but not the except_mech_attrs, and the given desired_mech_attrs but not the except_mech_attrs, and
all of which understand the given critical_mech_attrs all of which understand the given critical_mech_attrs (the caller
must release this output with GSS_Release_oid_set())
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_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_attrs() returns the set of OIDs corresponding GSS_Indicate_mechs_by_attrs() returns the set of OIDs corresponding
to mechanisms that offer at least the desired_mech_attrs but none of to mechanisms that offer at least the desired_mech_attrs but none of
the except_mech_attrs, and which understand all of the attributes the except_mech_attrs, and which understand all of the attributes
skipping to change at page 9, line 30 skipping to change at page 9, line 31
3.4.3. 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_*) supported by the mechanism (GSS_C_MA_*) supported by the mechanism (the caller must release
this output with GSS_Release_oid_set())
o known_mech_attrs SET OF OBJECT IDENTIFIER -- set of mech_attrs o known_mech_attrs SET OF OBJECT IDENTIFIER -- set of mech_attrs
OIDs known to the mechanism implementation. OIDs known to the mechanism implementation (the caller must
release this output with GSS_Release_oid_set()).
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.
skipping to change at page 9, line 49 skipping to change at page 10, line 4
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.4. 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 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
attribute attribute (the caller must release this output with
GSS_Release_buffer())
o long_desc OCTET STRING -- a longer description of the mechanism o long_desc OCTET STRING -- a longer description of the mechanism
attribute attribute (the caller must release this output with
GSS_Release_buffer())
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
skipping to change at page 10, line 46 skipping to change at page 11, line 4
3.4.6. 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_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 except_mech_attrs,
const gss_OID_set critical_mech_attrs, const gss_OID_set critical_mech_attrs,
gss_OID_set *mechs); gss_OID_set *mechs);
OM_uint32 gss_inquire_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); 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
Note that output buffers must be released via gss_release_buffer().
Output OID sets must be released via gss_release_oid_set().
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.
The IANA should allocate a base OID, as an arc of 1.3.6.1.5.5, for The IANA should allocate a base OID, as an arc of 1.3.6.1.5.5, for
skipping to change at page 13, line 4 skipping to change at line 557
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
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
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.
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, THE IETF TRUST 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.
Intellectual Property
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.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 17 change blocks. 
16 lines changed or deleted 29 lines changed or added

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