NETWORK WORKING GROUP N. Williams Internet-Draft Sun Expires: August 28, 2008 February 25, 2008 Namespace Considerations and Registries for GSS-API Extensions draft-ietf-kitten-gssapi-extensions-iana-02.txt Status of this Memo By submitting this Internet-Draft, each author represents that any 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 aware will be disclosed, in accordance with Section 6 of BCP 79. 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 28, 2008. Copyright Notice Copyright (C) The IETF Trust (2008). Abstract This document describes the ways in which the GSS-API may be extended and directs the creation of IANA registries for various GSS-API namespaces. Williams Expires August 28, 2008 [Page 1] Internet-Draft GSS IANA Instructions February 2008 Table of Contents 1. Conventions used in this document . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Extensions to the GSS-API . . . . . . . . . . . . . . . . . . . 3 4. Generic GSS-API Namespaces . . . . . . . . . . . . . . . . . . 3 5. Language Binding-Specific GSS-API Namespaces . . . . . . . . . 4 6. Extension-Specific GSS-API Namespaces . . . . . . . . . . . . . 4 7. Registration Form(s) . . . . . . . . . . . . . . . . . . . . . 4 8. Initial Namespace Registrations . . . . . . . . . . . . . . . . 6 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 10. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 11. Normative References . . . . . . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . 8 Williams Expires August 28, 2008 [Page 2] Internet-Draft GSS IANA Instructions February 2008 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 There is a need for generic and mechanism-specific extensions to the Generic Security Services Application Programming Interface (GSS- API). As such extensions are designed and standardized, both at the IETF and elsewhere, there is a non-trivial risk of namespace pollution and conflicts. To avoid this we set out guidelines for extending the GSS-API and create IANA registries of GSS-API namespaces. Registrations of individual items and sub-namespaces are allowed. Each sub-namespace may provide different rules for registration, e.g., for mechanism-specific and private-use extensions. All Standards-Track uses of the GSS-API namespaces will be registered directly with the IANA subsequent to the create of the registries or when the document is published. 3. Extensions to the GSS-API Extensions to the GSS-API can be categorized as follows: o Abstract API extensions o Implementation-specific o Mechanism-specific o Language binding-specific Extensions to the GSS-API may be purely semantic, without effect on the GSS-API's namespaces. Or they may introduce new functions, constants, types, etc...; these clearly affect the GSS-API namespaces. Extensions that affect the GSS-API namespaces should be registered with the IANA as described herein. 4. Generic GSS-API Namespaces The abstract API namespaces for the GSS-API are: o Type names o Function names o Constant names for each type Williams Expires August 28, 2008 [Page 3] Internet-Draft GSS IANA Instructions February 2008 o Constant values for each type o Name types (OID, type name and syntaxes) Additionally we have namespaces associates with the OBJECT IDENTIFIER (OID) type: o Mechanism OIDs o Name Type OIDs 5. Language Binding-Specific GSS-API Namespaces Language binding specific namespaces include: o Header/interface module names o Object classes and/or types o Methods and/or functions o Constant names o Constant values 6. Extension-Specific GSS-API Namespaces Extensions to the GSS-API may create additional namespaces. Instructions to the IANA should included for the handling of such namespaces. 7. Registration Form(s) Registrations for GSS-API namespaces SHALL take the following form: +----------------+----------------------------+---------------------+ | Registration | Possible Values | Description | | Field | | | +----------------+----------------------------+---------------------+ | Registration | 'Instance', | Indicates whether | | type | 'Sub-Namespace' | 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', 'C-bindings', | Indicates the | | | 'Java', 'C#', | that this | Williams Expires August 28, 2008 [Page 4] Internet-Draft GSS IANA Instructions February 2008 | | | registration is | | | | for, or, if | | | | 'Generic', that | | | | this is an entry | | | | for the generic | | | | GSS-API, not | | | | specific to any | | | | programming | | | | language. | +----------------+----------------------------+---------------------+ | Object Type | 'Data-Type', 'Function', | Indicates the type | | | 'Method', 'Integer', | of the object(s) | | | 'String', 'OID', 'Context | whose symbolic name | | | Flag', 'Name Type' | or constant value | | | | this entry | | | | registers. | +----------------+----------------------------+---------------------+ | Symbol | | symbols or values | | | | being registered. | +----------------+----------------------------+---------------------+ | Binding of | | language binding of | | | | the GSS-API, then | | | | this names the | | | | abstract API | | | | element of which it | | | | is a binding | | | | (OPTIONAL). | +----------------+----------------------------+---------------------+ | Constant | or | The value(s) | | Value/Range(s) | | registered | | | | (OPTIONAL). | +----------------+----------------------------+---------------------+ | Description | | Description of | | | | object(s) being | | | | registered. | +----------------+----------------------------+---------------------+ | Registration | 'Protocol Action', 'Expert | Describes the rules | | Rules | Review', | for allocation of | | | 'First-Come-First-Served', | items that fall in | | | 'Closed-For-Registrations' | this sub-namespace, | | | | if this entry is | | | | for a sub-namespace | | | | (OPTIONAL). | +----------------+----------------------------+---------------------+ | Reference | | Reference to | Williams Expires August 28, 2008 [Page 5] Internet-Draft GSS IANA Instructions February 2008 | | | document that | | | | describes the | | | | object(s) being | | | | registered. | +----------------+----------------------------+---------------------+ | Expert | | | +----------------+----------------------------+---------------------+ | Status | 'Standards-Track', | Status of the | | | 'Informational', | registration. | | | 'Experimental', | | | | 'Obsolete', 'Other' | | +----------------+----------------------------+---------------------+ The IANA should create a single GSS-API namespace registry, or multiple registries, one for symbolic names and one for constant values, or it may create a registry per-programming language, at its convenience. Entries in these registries should consist of all the fields from their corresponding registration entries. Entries should be sorted by object type, progamming language, symbol name. 8. Initial Namespace Registrations 9. IANA Considerations This document deals with IANA considerations throughout. Specifically it creates a single registry of various kinds of things, thought the IANA may instead create multiple registries each for one of those kinds of things. Of particular interest may be that IANA Williams Expires August 28, 2008 [Page 6] Internet-Draft GSS IANA Instructions February 2008 will now be the registration authority for the GSS-API name type OID space. 10. Security Considerations This document has no security considerations. 11. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2743] Linn, J., "Generic Security Service Application Program Interface Version 2, Update 1", RFC 2743, January 2000. [RFC2744] Wray, J., "Generic Security Service API Version 2 : C-bindings", RFC 2744, January 2000. Author's Address Nicolas Williams Sun Microsystems 5300 Riata Trace Ct Austin, TX 78727 US Email: Nicolas.Williams@sun.com Williams Expires August 28, 2008 [Page 7] Internet-Draft GSS IANA Instructions February 2008 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). Williams Expires August 28, 2008 [Page 8]