draft-ietf-kitten-gssapi-naming-exts-01.txt   draft-ietf-kitten-gssapi-naming-exts-02.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: April 17, 2006 October 14, 2005 Expires: December 28, 2006 June 26, 2006
GSS-API Naming Extensions GSS-API Naming Extensions
draft-ietf-kitten-gssapi-naming-exts-01.txt draft-ietf-kitten-gssapi-naming-exts-02.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 April 17, 2006. This Internet-Draft will expire on December 28, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
The Generic Security Services API (GSS-API) provides a simple naming The Generic Security Services API (GSS-API) provides a simple naming
architecture that supports name-based authorization. This document architecture that supports name-based authorization. This document
introduces new APIs that extend the GSS-API naming and authorization introduces new APIs that extend the GSS-API naming and authorization
model. model.
Table of Contents Table of Contents
skipping to change at page 2, line 19 skipping to change at page 2, line 19
3. Name Attribute Sources and Criticality . . . . . . . . . . 3 3. Name Attribute Sources and Criticality . . . . . . . . . . 3
4. Name Attributes/Values as ACL Subjects . . . . . . . . . . 4 4. Name Attributes/Values as ACL Subjects . . . . . . . . . . 4
5. Mapping Mechanism Facilities to Name Attributes . . . . . 4 5. Mapping Mechanism Facilities to Name Attributes . . . . . 4
5.1. Kerberos V and SPKM Authorization-Data . . . . . . . . . . 4 5.1. Kerberos V and SPKM Authorization-Data . . . . . . . . . . 4
5.2. Kerberos V Cross-Realm Transit Paths . . . . . . . . . . . 5 5.2. Kerberos V Cross-Realm Transit Paths . . . . . . . . . . . 5
5.3. PKIX Certificate Extensions . . . . . . . . . . . . . . . 5 5.3. PKIX Certificate Extensions . . . . . . . . . . . . . . . 5
5.3.1. PKIX EKUs . . . . . . . . . . . . . . . . . . . . . . . . 6 5.3.1. PKIX EKUs . . . . . . . . . . . . . . . . . . . . . . . . 6
5.3.2. PKIX Certificate Alternative Names . . . . . . . . . . . . 6 5.3.2. PKIX Certificate Alternative Names . . . . . . . . . . . . 6
5.3.3. Other PKIX Certificate Extensions and Attributes . . . . . 6 5.3.3. Other PKIX Certificate Extensions and Attributes . . . . . 6
5.4. PKIX Certificate CA Paths and Trust Anchors . . . . . . . 6 5.4. PKIX Certificate CA Paths and Trust Anchors . . . . . . . 6
6. GSS_Inquire_name_attribute() . . . . . . . . . . . . . . . 6 6. GSS_Display_name_ext() . . . . . . . . . . . . . . . . . . 6
6.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 7 6.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 7
7. GSS_Display_name_ext() . . . . . . . . . . . . . . . . . . 8 7. GSS_Inquire_name() . . . . . . . . . . . . . . . . . . . . 7
7.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 8 7.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 8
8. GSS_Inquire_name() . . . . . . . . . . . . . . . . . . . . 9 8. GSS_Get_name_attribute() . . . . . . . . . . . . . . . . . 8
8.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 9 8.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 9
9. GSS_Get_name_attribute() . . . . . . . . . . . . . . . . . 10 9. GSS_Set_name_attribute() . . . . . . . . . . . . . . . . . 10
9.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 11 9.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 11
10. GSS_Set_name_attribute() . . . . . . . . . . . . . . . . . 11 10. GSS_Delete_name_attribute() . . . . . . . . . . . . . . . 11
10.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 12 10.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 11
11. GSS_Delete_name_attribute() . . . . . . . . . . . . . . . 12 11. GSS_Export_name_composite() . . . . . . . . . . . . . . . 12
11.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 13 11.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 12
12. GSS_Export_name_composite() . . . . . . . . . . . . . . . 13 12. GSS_Map_name_to_any() . . . . . . . . . . . . . . . . . . 13
12.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 14 12.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 13
13. GSS_Map_name_to_any() . . . . . . . . . . . . . . . . . . 14 13. GSS_Release_any_name_mapping() . . . . . . . . . . . . . . 14
13.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 15 13.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 14
14. GSS_Release_any_name_mapping() . . . . . . . . . . . . . . 15 14. IANA Considerations . . . . . . . . . . . . . . . . . . . 15
14.1. C-Bindings . . . . . . . . . . . . . . . . . . . . . . . . 16 15. Security Considerations . . . . . . . . . . . . . . . . . 15
15. IANA Considerations . . . . . . . . . . . . . . . . . . . 16 16. Normative References . . . . . . . . . . . . . . . . . . . 15
16. Security Considerations . . . . . . . . . . . . . . . . . 17 Author's Address . . . . . . . . . . . . . . . . . . . . . 17
17. Normative References . . . . . . . . . . . . . . . . . . . 17 Intellectual Property and Copyright Statements . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . 19
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
As described in [I-D.GSS-NAMING] the GSS-API's naming architecture As described in [I-D.GSS-NAMING] the GSS-API's naming architecture
skipping to change at page 6, line 38 skipping to change at page 6, line 38
5.3.3. Other PKIX Certificate Extensions and Attributes 5.3.3. Other PKIX Certificate Extensions and Attributes
[Add text...] [Add text...]
5.4. PKIX Certificate CA Paths and Trust Anchors 5.4. PKIX Certificate CA Paths and Trust Anchors
[Add text on how to represent/encode/interpret PKI certificate [Add text on how to represent/encode/interpret PKI certificate
validation CA paths as name attribute values, much as with Kerberos V validation CA paths as name attribute values, much as with Kerberos V
transited paths.] transited paths.]
6. GSS_Inquire_name_attribute() 6. GSS_Display_name_ext()
[NOTE: This function was somewhat controversial at IETF63; we should
decide whether to remove it at IETF64. The controversy was, as I
recall over whether reflection functionality might not be dangerous,
leading to construction of inappropriate ACLs through dumb UIs. For
now I am making some changes to it: adding a NAME object as an input
parameter and some output parameters.]
Inputs:
o name NAME
o attr OBJECT IDENTIFIER
Outputs:
o major_status INTEGER,
o minor_status INTEGER,
o attr_name OCTET STRING, -- display name of the attribute
o attr_description OCTET STRING, -- description of the attribute
o attr_values_ordered BOOLEAN, -- whether the attribute's values are
an ordered set
o attr_is_a_name BOOLEAN, -- whether the attribute's values can be
used as subjects of access control list entries
o attr_is_trust_indicator BOOLEAN -- whether the attribute's values
represent nodes in trust paths
Return major_status codes:
o GSS_S_COMPLETE indicates no error.
o GSS_S_UNAVAILABLE indicates that the given attribute OID is not
known (even if present as a name's attribute).
o GSS_S_FAILURE indicates a general error.
This function outputs a name for the given name attribute,
description for display to users, and indicates whether the
attribute's values are ordered sets, whether the given name
attribute's values are useful as the subject of an access control
list entry and/or whether the given name attribute's values are
useful as indicators of trust (for example, whether they name PKIX
trust anchors).
6.1. C-Bindings
OM_uint32 gss_inquire_name_attribute(
OM_uint32 *minor_status,
gss_name_t name,
gss_OID attr,
gss_buffer_t attr_name,
gss_buffer_t attr_description,
int attr_values_ordered,
int *attr_is_a_name,
int *attr_is_trust_indicator
);
7. GSS_Display_name_ext()
Inputs: Inputs:
o name NAME, o name NAME,
o display_as_name_type OBJECT IDENTIFIER o display_as_name_type OBJECT IDENTIFIER
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
skipping to change at page 8, line 37 skipping to change at page 7, line 21
o GSS_S_UNAVAILABLE indicates that the given name could not be o GSS_S_UNAVAILABLE indicates that the given name could not be
displayed using the syntax of the given name type. displayed using the syntax of the given name type.
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
This function displays a given name using the given name syntax, if This function displays a given name using the given name syntax, if
possible. This operation may require mapping MNs to generic name possible. This operation may require mapping MNs to generic name
syntaxes or generic name syntaxes to mechanism-specific name syntaxes or generic name syntaxes to mechanism-specific name
syntaxes; such mappings may not always be feasible and MAY be inexact syntaxes; such mappings may not always be feasible and MAY be inexact
or lossy. or lossy, therefore this function may fail.
7.1. C-Bindings 6.1. C-Bindings
OM_uint32 GSS_Display_name_ext( OM_uint32 GSS_Display_name_ext(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
gss_OID display_as_name_type, gss_OID display_as_name_type,
gss_buffer_t display_name gss_buffer_t display_name
); );
8. GSS_Inquire_name() 7. GSS_Inquire_name()
Inputs: Inputs:
o name NAME o name NAME
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
skipping to change at page 9, line 44 skipping to change at page 8, line 25
Return major_status codes: Return major_status codes:
o GSS_S_COMPLETE indicates no error. o GSS_S_COMPLETE indicates no error.
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
This function outputs the sets of attributes of a name, that are This function outputs the sets of attributes of a name, that are
authenticated, asserted or critical. It also indicates if a given authenticated, asserted or critical. It also indicates if a given
NAME is an MN or not and, if it is, what mechanism it's an MN of. NAME is an MN or not and, if it is, what mechanism it's an MN of.
8.1. C-Bindings 7.1. C-Bindings
OM_uint32 gss_inquire_name( OM_uint32 gss_inquire_name(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
int name_is_MN, int name_is_MN,
gss_OID *MN_mech, gss_OID *MN_mech,
gss_OID_set *authenticated, gss_OID_set *authenticated,
gss_OID_set *asserted, gss_OID_set *asserted,
gss_OID_set *critical, gss_OID_set *critical,
gss_OID_set *all_attrs gss_OID_set *all_attrs
); );
9. GSS_Get_name_attribute() 8. GSS_Get_name_attribute()
Inputs: Inputs:
o name NAME, o name NAME,
o attr OBJECT IDENTIFIER o attr OBJECT IDENTIFIER
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
skipping to change at page 11, line 10 skipping to change at page 9, line 36
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
This function outputs the value(s) associated with a given GSS name This function outputs the value(s) associated with a given GSS name
object for a given name attribute. object for a given name attribute.
NOTE: This function relies on the GSS-API notion of "SET OF" allowing NOTE: This function relies on the GSS-API notion of "SET OF" allowing
for order preservation; this has been discussed on the KITTEN WG for order preservation; this has been discussed on the KITTEN WG
mailing list and the consensus seems to be that, indeed, that was mailing list and the consensus seems to be that, indeed, that was
always the intention. always the intention.
9.1. C-Bindings 8.1. C-Bindings
The C-bindings of GSS_Get_name_attribute() requires one function call The C-bindings of GSS_Get_name_attribute() requires one function call
per-attribute value, for multi-valued name attributes. This is done per-attribute value, for multi-valued name attributes. This is done
by using a single gss_buffer_t for each value and an input/output by using a single gss_buffer_t for each value and an input/output
integer parameter to distinguish initial and subsequent calls and to integer parameter to distinguish initial and subsequent calls and to
indicate when all values have been obtained. indicate when all values have been obtained.
The 'more' input/output parameter should point to an integer variable The 'more' input/output parameter should point to an integer variable
whose value, on first call to gss_name_attribute_get() MUST be -1, whose value, on first call to gss_name_attribute_get() MUST be -1,
and whose value upon function call return will be non-zero to and whose value upon function call return will be non-zero to
skipping to change at page 11, line 38 skipping to change at page 10, line 16
gss_OID attr, gss_OID attr,
int *authenticated, int *authenticated,
int *negative, int *negative,
int *mapped, int *mapped,
int *critical, int *critical,
gss_buffer_t value, gss_buffer_t value,
gss_buffer_t display_value, gss_buffer_t display_value,
int *more int *more
); );
10. GSS_Set_name_attribute() 9. GSS_Set_name_attribute()
Inputs: Inputs:
o name NAME, o name NAME,
o critical BOOLEAN, o critical BOOLEAN,
o negative BOOLEAN, o negative BOOLEAN,
o attr OBJECT IDENTIFIER, o attr OBJECT IDENTIFIER,
skipping to change at page 12, line 24 skipping to change at page 11, line 5
o GSS_S_UNAVAILABLE indicates that the given attribute OID is not o GSS_S_UNAVAILABLE indicates that the given attribute OID is not
known or could not be set. known or could not be set.
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
NOTE: This function relies on the GSS-API notion of "SET OF" allowing NOTE: This function relies on the GSS-API notion of "SET OF" allowing
for order preservation; this has been discussed on the KITTEN WG for order preservation; this has been discussed on the KITTEN WG
mailing list and the consensus seems to be that, indeed, that was mailing list and the consensus seems to be that, indeed, that was
always the intention. always the intention.
10.1. C-Bindings 9.1. C-Bindings
The C-bindings of GSS_Set_name_attribute() requires one function call The C-bindings of GSS_Set_name_attribute() requires one function call
per-attribute value, for multi-valued name attributes -- each call per-attribute value, for multi-valued name attributes -- each call
adds one value. To replace an attribute's every value delete the adds one value. To replace an attribute's every value delete the
attribute's values first with GSS_Delete_name_attribute(). attribute's values first with GSS_Delete_name_attribute().
OM_uint32 gss_set_name_attribute( OM_uint32 gss_set_name_attribute(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
int critical, int critical,
int negative, int negative,
gss_OID attr, gss_OID attr,
gss_buffer_t value gss_buffer_t value
); );
11. GSS_Delete_name_attribute() 10. GSS_Delete_name_attribute()
Inputs: Inputs:
o name NAME, o name NAME,
o attr OBJECT IDENTIFIER, o attr OBJECT IDENTIFIER,
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
skipping to change at page 13, line 22 skipping to change at page 11, line 48
o GSS_S_UNAVAILABLE indicates that the given attribute OID is not o GSS_S_UNAVAILABLE indicates that the given attribute OID is not
known. known.
o GSS_S_FAILURE indicates a general error. o GSS_S_FAILURE indicates a general error.
Deletion of negative authenticated attributes from NAME objects MUST Deletion of negative authenticated attributes from NAME objects MUST
NOT be allowed. [Do we need a new major status code for "permission NOT be allowed. [Do we need a new major status code for "permission
denied"?] denied"?]
11.1. C-Bindings 10.1. C-Bindings
OM_uint32 gss_delete_name_attribute( OM_uint32 gss_delete_name_attribute(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
gss_OID attr gss_OID attr
); );
12. GSS_Export_name_composite() 11. GSS_Export_name_composite()
Inputs: Inputs:
o name NAME o name NAME
Outputs: Outputs:
o major_status INTEGER, o major_status INTEGER,
o minor_status INTEGER, o minor_status INTEGER,
skipping to change at page 14, line 15 skipping to change at page 12, line 40
This function outputs a token which can be imported with This function outputs a token which can be imported with
GSS_Import_name(), using GSS_C_NT_COMPOSITE_EXPORT as the name type GSS_Import_name(), using GSS_C_NT_COMPOSITE_EXPORT as the name type
and which preserves any name attribute information associated with and which preserves any name attribute information associated with
the input name (which GSS_Export_name() may well not). The token the input name (which GSS_Export_name() may well not). The token
format is no specified here as this facility is intended for inter- format is no specified here as this facility is intended for inter-
process communication only; however, all such tokens MUST start with process communication only; however, all such tokens MUST start with
a two-octet token ID, hex 04 02, in network byte order. a two-octet token ID, hex 04 02, in network byte order.
The OID for GSS_C_NT_COMPOSITE_EXPORT is <TBD>. The OID for GSS_C_NT_COMPOSITE_EXPORT is <TBD>.
12.1. C-Bindings 11.1. C-Bindings
OM_uint32 gss_export_name_composite( OM_uint32 gss_export_name_composite(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
gss_buffer_t exp_composite_name gss_buffer_t exp_composite_name
); );
13. GSS_Map_name_to_any() 12. GSS_Map_name_to_any()
Inputs: Inputs:
o name NAME, o name NAME,
o authenticated BOOLEAN, -- if TRUE no data will be output unless it o authenticated BOOLEAN, -- if TRUE no data will be output unless it
is authenticated is authenticated
o type_id OBJECT IDENTIFIER o type_id OBJECT IDENTIFIER
skipping to change at page 15, line 13 skipping to change at page 13, line 40
information. information.
o GSS_S_FAILURE indicates a general error. The minor status code o GSS_S_FAILURE indicates a general error. The minor status code
may provide additional information. may provide additional information.
Whereas name attribute's values are encoded in some network Whereas name attribute's values are encoded in some network
representation applications often require native, language- and/or representation applications often require native, language- and/or
platform-specific data types. This function provides access to such platform-specific data types. This function provides access to such
types. types.
13.1. C-Bindings 12.1. C-Bindings
typedef struct gss_any *gss_any_t; typedef struct gss_any *gss_any_t;
OM_uint32 gss_map_name_to_any( OM_uint32 gss_map_name_to_any(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
int authenticated, int authenticated,
gss_OID type_id, gss_OID type_id,
gss_any_t output gss_any_t output
); );
Note the new C bindings type, gss_any_t. We define it as a pointer Note the new C bindings type, gss_any_t. We define it as a pointer
to an incompletely declared struct. to an incompletely declared struct.
14. GSS_Release_any_name_mapping() 13. GSS_Release_any_name_mapping()
Inputs: Inputs:
o name NAME, o name NAME,
o type_id OBJECT IDENTIFIER, o type_id OBJECT IDENTIFIER,
o input ANY DEFINED BY type_id o input ANY DEFINED BY type_id
Outputs: Outputs:
skipping to change at page 16, line 13 skipping to change at page 14, line 39
information. information.
o GSS_S_FAILURE indicates a general error. The minor status code o GSS_S_FAILURE indicates a general error. The minor status code
may provide additional information. may provide additional information.
This function releases, if possible, the objects of language- and/or This function releases, if possible, the objects of language- and/or
platform-specific types output by GSS_Map_name_to_any(). If such platform-specific types output by GSS_Map_name_to_any(). If such
types have native release functions applications MAY use either those types have native release functions applications MAY use either those
or this function to release the given object. or this function to release the given object.
14.1. C-Bindings 13.1. C-Bindings
typedef struct gss_any *gss_any_t; typedef struct gss_any *gss_any_t;
OM_uint32 gss_release_any_name_mapping( OM_uint32 gss_release_any_name_mapping(
OM_uint32 *minor_status, OM_uint32 *minor_status,
gss_name_t name, gss_name_t name,
gss_OID type_id, gss_OID type_id,
gss_any_t *input gss_any_t *input
); );
15. IANA Considerations 14. IANA Considerations
This document creates a namespace of GSS-API name attributes. This document creates a namespace of GSS-API name attributes.
Attributes are named by OID, so no single authority might be needed Attributes are named by OID, so no single authority might be needed
for allocation, however, in the interest of providing the community for allocation, however, in the interest of providing the community
with an authority for name attribute OID allocation and a way to find with an authority for name attribute OID allocation and a way to find
the existing set of name attributes, the IANA should establish both, the existing set of name attributes, the IANA should establish both,
a single OID off of which name attributes could be allocated, and a a single OID off of which name attributes could be allocated, and a
registry of known GSS name attributes. registry of known GSS name attributes.
GSS-API name attribute registry entries should contain all the GSS-API name attribute registry entries should contain all the
skipping to change at page 17, line 4 skipping to change at page 15, line 33
o a brief description, in English o a brief description, in English
o whether the attribute is useful as the subject of access control o whether the attribute is useful as the subject of access control
list entries list entries
o whether the attribute is useful as an indicator of trust o whether the attribute is useful as an indicator of trust
o an optional normative reference to documentation for the given o an optional normative reference to documentation for the given
name attribute name attribute
The allocation and registration policy should be first come, first The allocation and registration policy should be first come, first
served. Registry entries' OIDs need not be based on the base OID served. Registry entries' OIDs need not be based on the base OID
given above. given above.
16. Security Considerations 15. Security Considerations
<TBA> <TBA>
[In particular, the status of a name attribute as "authenticated" vs. [In particular, the status of a name attribute as "authenticated" vs.
"asserted" requires close review, particularly with respect to PKIX "asserted" requires close review, particularly with respect to PKIX
certificate extensions.] certificate extensions.]
[Also, we need to work out the security considerations of (and [Also, we need to work out the security considerations of (and
possibly remove) negative attributes.] possibly remove) negative attributes.]
17. Normative References 16. Normative References
[I-D.GSS-NAMING] [I-D.GSS-NAMING]
Hartman, S., "Desired Enhancements to GSSAPI Naming", Hartman, S., "Desired Enhancements to GSSAPI Naming",
draft-ietf-kitten-gss-naming-01.txt (work in progress), draft-ietf-kitten-gss-naming-01.txt (work in progress),
February 2005. February 2005.
[I-D.ietf-krb-wg-kerberos-clarifications] [I-D.ietf-krb-wg-kerberos-clarifications]
Neuman, C., "The Kerberos Network Authentication Service Neuman, C., "The Kerberos Network Authentication Service
(V5)", draft-ietf-krb-wg-kerberos-clarifications-07 (work (V5)", draft-ietf-krb-wg-kerberos-clarifications-07 (work
in progress), September 2004. in progress), September 2004.
skipping to change at page 19, line 41 skipping to change at page 18, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 32 change blocks. 
109 lines changed or deleted 43 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/