gss-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

CVS gss/doc/specification


From: gss-commit
Subject: CVS gss/doc/specification
Date: Tue, 15 Feb 2005 17:16:24 +0100

Update of /home/cvs/gss/doc/specification
In directory dopio:/tmp/cvs-serv22725

Added Files:
        draft-ietf-kitten-extended-mech-inquiry-00.txt 
Log Message:
Add.


--- 
/home/cvs/gss/doc/specification/draft-ietf-kitten-extended-mech-inquiry-00.txt  
    2005/02/15 16:16:19     NONE
+++ 
/home/cvs/gss/doc/specification/draft-ietf-kitten-extended-mech-inquiry-00.txt  
    2005/02/15 16:16:19     1.1


NETWORK WORKING GROUP                                        N. Williams
Internet-Draft                                                       Sun
Expires: August 12, 2005                               February 11, 2005


        Extended Generic Security Service Mechanism Inquiry APIs
             draft-ietf-kitten-extended-mech-inquiry-00.txt

Status of this Memo

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   and any of which I become aware will be disclosed, in accordance with
   RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on August 12, 2005.

Copyright Notice

   Copyright (C) The Internet Society (2005).  All Rights Reserved.

Abstract

   This document introduces new application programming interfaces
   (APIs) to the Generic Security Services API (GSS-API) for extended
   mechanism attribute inquiry.  These interfaces are primarily intended
   for use in mechanism composition, but also to reduce instances of
   hardcoding of mechanism identifiers in GSS applications.

   These interfaces include: mechanism attributes and attribute sets, a
   function for inquiring the attributes of a mechanism, a function for
   indicating mechanisms that posses given attributes, and a function
   for displaying mechanism attributes.



Williams                Expires August 12, 2005                 [Page 1]

Internet-Draft         Extended GSS Mech Inquiry           February 2005


Table of Contents

   1.    Conventions used in this document  . . . . . . . . . . . . .  3
   2.    Introduction . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.    New GSS-API Interfaces . . . . . . . . . . . . . . . . . . .  3
   3.1   Mechanism Attributes and Attribute Sets  . . . . . . . . . .  3
   3.2   Determination of Attribute Sets of Composite Mechs . . . . .  4
   3.3   List of Known Mechanism Attributes . . . . . . . . . . . . .  4
   3.4   Mechanism Attribute Sets of Existing Mechs . . . . . . . . .  7
   3.5   New GSS-API Function Interfaces  . . . . . . . . . . . . . .  8
   3.5.1 GSS_Indicate_mechs_by_attr() . . . . . . . . . . . . . . . .  9
   3.5.2 GSS_Inquire_attrs_for_mech() . . . . . . . . . . . . . . . .  9
   3.5.3 GSS_Display_mech_attr()  . . . . . . . . . . . . . . . . . . 10
   3.5.4 New Major Status Values  . . . . . . . . . . . . . . . . . . 10
   3.5.5 C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . . 11
   4.    Requirements for Mechanism Designers . . . . . . . . . . . . 11
   5.    IANA Considerations  . . . . . . . . . . . . . . . . . . . . 11
   6.    Security considerations  . . . . . . . . . . . . . . . . . . 12
   7.    References . . . . . . . . . . . . . . . . . . . . . . . . . 12
   7.1   Normative  . . . . . . . . . . . . . . . . . . . . . . . . . 12
   7.2   Normative  . . . . . . . . . . . . . . . . . . . . . . . . . 12
         Author's Address . . . . . . . . . . . . . . . . . . . . . . 12
         Intellectual Property and Copyright Statements . . . . . . . 13




























Williams                Expires August 12, 2005                 [Page 2]

Internet-Draft         Extended GSS Mech Inquiry           February 2005


1.  Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Introduction


3.  New GSS-API Interfaces

   GSS-API applications face, today, the problem of how to select from
   multiple GSS-API mechanisms that may be available.  For example,
   applications that support mechanism negotiation directly often have
   to be careful not to use SPNEGO to avoid two-layer mechanism
   negotiation, but since SPNEGO may be indicated by
   GSS_Indicate_mechs() and since there's no way to know that a
   mechanism negotiates mechanisms other than to hardcode the OIDs of
   such mechanisms, such applications must hardcode the SPNEGO OID.
   This problem is likely to be exacerbated by the introduction of
   composite mechanisms.

   To address this problem we introduce a new concept: that of mechanism
   attributes.  By allowing applications to query the set of attributes
   associated with individual mechanisms and to find out which
   mechanisms support a given set of attributes we allow applications to
   select mechanisms based on their attributes yet without having to
   hardcode mechanism OIDs.

   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
   mechanisms and attribute sets:

   o  GSS_Indicate_mechs_by_attrs()
   o  GSS_Inquire_attrs_for_mech()
   o  GSS_Display_mech_attr()

3.1  Mechanism Attributes and Attribute Sets

   An abstraction for the features provided by pseudo-mechanisms is
   needed in order to facilitate the programmatic selection of
   mechanisms as well as for the programmatic composition of mechanisms.

   Two data types are needed: one for individual mechanism attributes
   and one for mechanism attribute sets.  To simplify the mechanism
   attributes interfaces we reuse the 'OID' and 'OID set' data types and
   model individual mechanism attribute types as OIDs.




Williams                Expires August 12, 2005                 [Page 3]

Internet-Draft         Extended GSS Mech Inquiry           February 2005


   To this end we define an open namespace of mechanism attributes and
   assign them arcs off of this OID:

   <TBD> [1.3.6.1.5.5.12 appears to be available, registration w/ IANA
   TBD]

3.2  Determination of Attribute Sets of Composite Mechs

   Each mechanism, composite or otherwise, has a set of mechanism
   attributes that it supports as specified.

   The mechanism attribute set of a composite mechanism is to be
   determined by the top-most stackable pseudo-mechanism of the
   composite according to its own attribute set and that of the
   remainder of the composite mechanism stack below it.

   It may well be that some composite mechanisms' attribute sets consist
   of the union of those of their every component, however this need not
   be the case and MUST NOT be assumed.

   Every stackable pseudo-mechanism's specification MUST specify the
   rules for determining the mechanism attribute set of mechanisms
   composed by it.

3.3  List of Known Mechanism Attributes

 +-------------------------+---------+--------------------------------+
 | Mech Attr Name          | OID Arc | Arc Name                       |
 +-------------------------+---------+--------------------------------+
 | GSS_C_MA_MECH_CONCRETE  |     (1) | concrete-mech                  |
 | GSS_C_MA_MECH_STACKABLE |     (2) | pseudo-mech                    |
 | GSS_C_MA_MECH_COMPOSITE |     (3) | composite-mech                 |
 | GSS_C_MA_MECH_NEGO      |     (4) | mech-negotiation-mech          |
 | GSS_C_MA_MECH_GLUE      |     (5) | mech-glue                      |
 | GSS_C_MA_NOT_MECH       |     (6) | not-mech                       |
 | GSS_C_MA_DEPRECATED     |     (7) | mech-deprecated                |
 | GSS_C_MA_NOT_DFLT_MECH  |     (8) | mech-not-default               |
 | GSS_C_MA_ITOK_FRAMED    |     (9) | initial-is-framed              |
 | GSS_C_MA_AUTH_INIT      |    (10) | auth-init-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_TARG_INIT |    (13) | auth-targ-princ-initial        |
 | 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_DELEG_CRED     |    (16) | deleg-cred                     |
 | GSS_C_MA_INTEG_PROT     |    (17) | integ-prot                     |
 | GSS_C_MA_CONF_PROT      |    (18) | conf-prot                      |
 | GSS_C_MA_MIC            |    (19) | mic                            |



Williams                Expires August 12, 2005                 [Page 4]

Internet-Draft         Extended GSS Mech Inquiry           February 2005


 | GSS_C_MA_WRAP           |    (20) | wap                            |
 | GSS_C_MA_PROT_READY     |    (21) | prot-ready                     |
 | GSS_C_MA_REPLAY_DET     |    (22) | replay-detection               |
 | GSS_C_MA_OOS_DET        |    (23) | oos-detection                  |
 | GSS_C_MA_CBINDINGS      |    (24) | channel-bindings               |
 | GSS_C_MA_CBINDINGS_BIDI |    (25) | channel-bindings-bidirectional |
 | GSS_C_MA_CBINDINGS_NEGO |    (26) | channel-bindings-negotiate     |
 | GSS_C_MA_PFS            |    (27) | pfs                            |
 | GSS_C_MA_COMPRESS       |    (28) | compress                       |
 | GSS_C_MA_CTX_TRANS      |    (29) | context-transfer               |
 | <reserved>              |  (30..) |                                |
 +-------------------------+---------+--------------------------------+

                                Table 1

   +---------------------------------+---------------------------------+
   | Mech Attr Name                  | Purpose                         |
   +---------------------------------+---------------------------------+
   | GSS_C_MA_MECH_CONCRETE          | Indicates that a mech is        |
   |                                 | neither a pseudo- mechanism nor |
   |                                 | a composite mechanism.          |
   | GSS_C_MA_MECH_STACKABLE         | Indicates that a mech is a      |
   |                                 | pseudo-mechanism.               |
   | GSS_C_MA_MECH_COMPOSITE         | Indicates that a mech is a      |
   |                                 | composite mechanism.            |
   | GSS_C_MA_MECH_NEGO              | Indicates that a mech           |
   |                                 | negotiates other mechs (e.g.,   |
   |                                 | SPNEGO has this attribute).     |
   | GSS_C_MA_MECH_GLUE              | Indicates that the OID is not   |
   |                                 | for a mechanism but for the     |
   |                                 | GSS-API itself.                 |
   | GSS_C_MA_NOT_MECH               | Indicates that the OID is       |
   |                                 | known, yet also known not to be |
   |                                 | the OID of any GSS-API          |
   |                                 | mechanism (or the GSS-API       |
   |                                 | itself).                        |
   | GSS_C_MA_DEPRECATED             | Indicates that a mech (or its   |
   |                                 | OID) is deprecated and MUST NOT |
   |                                 | 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.              |
   | GSS_C_MA_ITOK_FRAMED            | Indicates that the given        |
   |                                 | mechanism's initial context     |
   |                                 | tokens are properly framed as   |
   |                                 | per-section 3.1 of rfc2743.     |
   | GSS_C_MA_AUTH_INIT              | Indicates support for           |
   |                                 | authentication of initiator to  |



Williams                Expires August 12, 2005                 [Page 5]

Internet-Draft         Extended GSS Mech Inquiry           February 2005


   |                                 | acceptor.                       |
   | GSS_C_MA_AUTH_TARG              | Indicates support for           |
   |                                 | authentication of acceptor to   |
   |                                 | initiator.                      |
   | GSS_C_MA_AUTH_INIT_INIT         | Indicates support for initial   |
   |                                 | authentication of initiator to  |
   |                                 | acceptor.                       |
   | GSS_C_MA_AUTH_TARG_INIT         | Indicates support for initial   |
   |                                 | authentication of acceptor to   |
   |                                 | initiator.                      |
   | GSS_C_MA_AUTH_INIT_ANON         | Indicates support for initiator |
   |                                 | anonymity.                      |
   | GSS_C_MA_AUTH_TARG_ANON         | Indicates support for acceptor  |
   |                                 | anonymity.                      |
   | GSS_C_MA_DELEG_CRED             | Indicates support for           |
   |                                 | credential delegation.          |
   | GSS_C_MA_INTEG_PROT             | Indicates support for           |
   |                                 | per-message integrity           |
   |                                 | protection.                     |
   | GSS_C_MA_CONF_PROT              | Indicates support for           |
   |                                 | per-message confidentiality     |
   |                                 | protection.                     |
   | GSS_C_MA_MIC                    | Indicates support for MIC       |
   |                                 | tokens.                         |
   | GSS_C_MA_WRAP                   | Indicates support for WRAP      |
   |                                 | tokens.                         |
   | GSS_C_MA_PROT_READY             | Indicates support for           |
   |                                 | per-message protection prior to |
   |                                 | full context establishment.     |
   | GSS_C_MA_REPLAY_DET             | Indicates support for replay    |
   |                                 | detection.                      |
   | GSS_C_MA_OOS_DET                | Indicates support for           |
   |                                 | out-of-sequence detection.      |
   | GSS_C_MA_CBINDINGS              | Indicates support for channel   |
   |                                 | bindings.                       |
   | GSS_C_MA_CBINDINGS_BIDI         | Indicates that acceptors        |
   |                                 | unconditionally indicate to     |
   |                                 | initiators whether their        |
   |                                 | channel bindings were matched   |
   |                                 | the acceptors', even when the   |
   |                                 | acceptor applications use       |
   |                                 | GSS_C_NO_CHANNEL_BINDINGS..     |
   | GSS_C_MA_CBINDINGS_NEGO         | Indicates that the mech acts as |
   |                                 | a signal for application        |
   |                                 | support for and willingness to  |
   |                                 | use channel bindings.           |
   | GSS_C_MA_PFS                    | Indicates support for Perfect   |
   |                                 | Forward Security.               |



Williams                Expires August 12, 2005                 [Page 6]

Internet-Draft         Extended GSS Mech Inquiry           February 2005


   | GSS_C_MA_COMPRESS               | Indicates support for           |
   |                                 | compression of data inputs to   |
   |                                 | GSS_Wrap().                     |
   | GSS_C_MA_CTX_TRANS              | Indicates support for security  |
   |                                 | context export/import.          |
   +---------------------------------+---------------------------------+

                                Table 2


3.4  Mechanism Attribute Sets of Existing Mechs

   The Kerberos V mechanism [RFC1964] [CFX] provides the following
   mechanism attributes:

   o  GSS_C_MA_MECH_CONCRETE
   o  GSS_C_MA_ITOK_FRAMED
   o  GSS_C_MA_AUTH_INIT
   o  GSS_C_MA_AUTH_TARG
   o  GSS_C_MA_DELEG_CRED
   o  GSS_C_MA_INTEG_PROT
   o  GSS_C_MA_CONF_PROT
   o  GSS_C_MA_MIC
   o  GSS_C_MA_WRAP
   o  GSS_C_MA_PROT_READY
   o  GSS_C_MA_REPLAY_DET
   o  GSS_C_MA_OOS_DET
   o  GSS_C_MA_CBINDINGS
   o  GSS_C_MA_CTX_TRANS (some implementations, using
      implementation-specific exported context token formats)

   The Kerberos V mechanism also has a deprecated OID which has the same
   mechanism attributes as above, and GSS_C_MA_DEPRECATED.

   [The mechanism attributes of the SPKM family of mechanisms will be
   provided in a separate document as SPKM is current being reviewed for
   possibly significant changes due to problems in its specifications.]

   The LIPKEY mechanism offers the following attributes:

   o  GSS_C_MA_MECH_CONCRETE (should be stackable, but does not compose)
   o  GSS_C_MA_ITOK_FRAMED
   o  GSS_C_MA_AUTH_INIT_INIT
   o  GSS_C_MA_AUTH_TARG (from SPKM-3)
   o  GSS_C_MA_AUTH_TARG_ANON (from SPKM-3)
   o  GSS_C_MA_INTEG_PROT
   o  GSS_C_MA_CONF_PROT
   o  GSS_C_MA_REPLAY_DET



Williams                Expires August 12, 2005                 [Page 7]

Internet-Draft         Extended GSS Mech Inquiry           February 2005


   o  GSS_C_MA_OOS_DET
   o  GSS_C_MA_CTX_TRANS (some implementations, using
      implementation-specific exported context token formats)

      (LIPKEY should also provide GSS_C_MA_CBINDINGS, but SPKM-3

[329 lines skipped]




reply via email to

[Prev in Thread] Current Thread [Next in Thread]