draft-ietf-kitten-gssapi-extensions-iana-00.txt   draft-ietf-kitten-gssapi-extensions-iana-01.txt 
NETWORK WORKING GROUP N. Williams NETWORK WORKING GROUP N. Williams
Internet-Draft Sun Internet-Draft Sun
Expires: July 2, 2005 January 2005 Expires: April 19, 2006 October 16, 2005
Namespace Considerations and Registries for GSS-API Extensions Namespace Considerations and Registries for GSS-API Extensions
draft-ietf-kitten-gssapi-extensions-iana-00.txt draft-ietf-kitten-gssapi-extensions-iana-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 July 2, 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 describes the ways in which the GSS-API may be extended This document describes the ways in which the GSS-API may be extended
and directs the creation of IANA registries for various GSS-API and directs the creation of IANA registries for various GSS-API
namespaces. namespaces.
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. Extensions to the GSS-API . . . . . . . . . . . . . . . . . . 3 3. Extensions to the GSS-API . . . . . . . . . . . . . . . . . . . 3
4. Generic GSS-API Namespaces . . . . . . . . . . . . . . . . . . 3 4. Generic GSS-API Namespaces . . . . . . . . . . . . . . . . . . 3
5. Language Binding-Specific GSS-API Namespaces . . . . . . . . . 4 5. Language Binding-Specific GSS-API Namespaces . . . . . . . . . 4
6. Extension-Specific GSS-API Namespaces . . . . . . . . . . . . 4 6. Extension-Specific GSS-API Namespaces . . . . . . . . . . . . . 4
7. Registration Form(s) . . . . . . . . . . . . . . . . . . . . . 4 7. Registration Form(s) . . . . . . . . . . . . . . . . . . . . . 4
8. Initial Namespace Registrations . . . . . . . . . . . . . . . 6 8. Initial Namespace Registrations . . . . . . . . . . . . . . . . 5
9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 9. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
10. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . 6 10. Normative . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . 7
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
There is a need for generic and mechanism-specific extensions to the There is a need for generic and mechanism-specific extensions to the
Generic Security Services Application Programming Interface Generic Security Services Application Programming Interface (GSS-
(GSS-API). As such extensions are designed and standardized, both at API). As such extensions are designed and standardized, both at the
the IETF and elsewhere, there is a non-trivial risk of namespace IETF and elsewhere, there is a non-trivial risk of namespace
pollution and conflicts. To avoid this we set out guidelines for pollution and conflicts. To avoid this we set out guidelines for
extending the GSS-API and create IANA registries of GSS-API extending the GSS-API and create IANA registries of GSS-API
namespaces. namespaces.
The registration of name prefixes and constant value ranges is The registration of name prefixes and constant value ranges is
allowed so as to save the IANA the trouble of registering every allowed so as to save the IANA the trouble of registering every GSS-
GSS-API name and constant, and to allow for reservation of portions API name and constant, and to allow for reservation of portions of
of some GSS namespaces for private extensions or extensions which some GSS namespaces for private extensions or extensions which lack
lack IETF Standards-Track extensions. IETF Standards-Track extensions.
3. Extensions to the GSS-API 3. Extensions to the GSS-API
Extensions to the GSS-API can be categorized as follows: Extensions to the GSS-API can be categorized as follows:
o Generic o Generic
o Implementation-specific o Implementation-specific
o Mechanism-specific o Mechanism-specific
o Language binding-specific o Language binding-specific
o Any combination of two or all three of the last three o Any combination of two or all three of the last three
skipping to change at page 4, line 26 skipping to change at page 4, line 30
6. Extension-Specific GSS-API Namespaces 6. Extension-Specific GSS-API Namespaces
Extensions to the GSS-API may create additional namespaces. Extensions to the GSS-API may create additional namespaces.
Instructions to the IANA should included for the handling of such Instructions to the IANA should included for the handling of such
namespaces. namespaces.
7. Registration Form(s) 7. Registration Form(s)
Registrations for GSS-API namespaces SHALL take the following form: Registrations for GSS-API namespaces SHALL take the following form:
+----------------------+----------------------+---------------------+ <TBD>
| Registration Field | Possible Values | Description |
+----------------------+----------------------+---------------------+
| Registration type | 'Individual', | Indicates whether |
| | 'Prefix', 'Range' | this entry reserves |
| | | a given symbol name |
| | | or constant value |
| | | or whether it |
| | | reserves an entire |
| | | sub-namespace (the |
| | | name is a "prefix") |
| | | or constant value |
| | | range. |
| Bindings | 'Generic', | Indicates the |
| | 'C-bindings', | language bindings |
| | 'Java', 'C#', etc... | that this |
| | | registration is |
| | | for, or, if |
| | | 'Generic', that |
| | | this is an entry |
| | | for the generic |
| | | GSS-API, not |
| | | specific to any |
| | | programming |
| | | language. |
| Object Type | 'Symbol', | Indicates whether |
| | 'Constant-Value' | this registration |
| | | is for a symbol |
| | | (e.g., function, |
| | | constant name(s)) |
| | | or constant value. |
| Object Programming | 'Data-Type', | Indicates the type |
| Type | 'Function', | of the object(s) |
| | 'Method', 'Integer', | whose symbolic name |
| | 'String', 'OID' | or constant value |
| | | is this entry |
| | | registers. |
| Object Name | <Symbol name or name | The name(s) of |
| | prefix> | symbols or values |
| | | being registered. |
| Object Value | <Constant value> or | [Only for |
| | <constant value | Constant-Value |
| | range> | registrations.] The |
| | | value(s) |
| | | registered. |
| Description | <Text> | Description of |
| | | object(s) being |
| | | registered. |
| Reference | <Reference> | Reference to |
| | | document that |
| | | describes the |
| | | object(s) being |
| | | registered. |
| Status | 'Standards-Track', | |
| | 'Informational', | |
| | 'Experimental', | |
| | 'Obsolete' | |
+----------------------+----------------------+---------------------+
The IANA should create a single GSS-API namespace registry, or The IANA should create a single GSS-API namespace registry, or
multiple registries, one for symbolic names and one for constant multiple registries, one for symbolic names and one for constant
values, or it may create a registry per-programming language, at its values, or it may create a registry per-programming language, at its
convenience. convenience.
Entries in these registries should consist of all the fields from Entries in these registries should consist of all the fields from
their corresponding registration entries. their corresponding registration entries.
Entries SHOULD be sorted by object type, proggamming language, symbol Entries SHOULD be sorted by object type, proggamming language, symbol
skipping to change at page 6, line 19 skipping to change at page 5, line 17
<Add registration entries for namespaces (name prefixes) for RFC2743/ <Add registration entries for namespaces (name prefixes) for RFC2743/
RFC2744/RFC2853.> RFC2744/RFC2853.>
<Add registration entries for private namespaces (name prefixes) for <Add registration entries for private namespaces (name prefixes) for
implementation- and/or platform-specific extensions.> implementation- and/or platform-specific extensions.>
9. Security Considerations 9. Security Considerations
This document has no security considerations. This document has no security considerations.
10 Normative 10. Normative
[EXTENDED-INQUIRY] [EXTENDED-INQUIRY]
Williams, N., "Extended Generic Security Service Mechanism Williams, N., "Extended Generic Security Service Mechanism
Inquiry APIs", Inquiry APIs",
draft-ietf-kitten-extended-mech-inquiry-00.txt (work in draft-ietf-kitten-extended-mech-inquiry-00.txt (work in
progress). progress).
[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.
skipping to change at page 6, line 44 skipping to change at page 6, line 13
C-bindings", RFC 2744, January 2000. C-bindings", RFC 2744, January 2000.
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. 15 change blocks. 
83 lines changed or deleted 26 lines changed or added

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