NETWORK WORKING GROUP N. Williams Internet-Draft Sun Expires: September 25, 2008 March 24, 2008 Namespace Considerations and Registries for GSS-API Extensions draft-ietf-kitten-gssapi-extensions-iana-03.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 September 25, 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 an IANA registry for various GSS-API namespaces. Williams Expires September 25, 2008 [Page 1] Internet-Draft GSS IANA Instructions March 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. IANA Considerations . . . . . . . . . . . . . . . . . . . . 6 8.1. Initial Namespace Registrations . . . . . . . . . . . . . . 6 8.2. Registration Maintenance Guidelines . . . . . . . . . . . . 6 8.2.1. Expert Reviews of Individual Submissions . . . . . . . . . 7 9. Security Considerations . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . 8 10.1. Normative References . . . . . . . . . . . . . . . . . . . 8 10.2. Informative References . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . 8 Intellectual Property and Copyright Statements . . . . . . 9 Williams Expires September 25, 2008 [Page 2] Internet-Draft GSS IANA Instructions March 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 private-use and mechanism-specific extensions to the Generic Security Services Application Programming Interface (GSS- API). As such extensions are designed and standardized (or not), 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 direct the creation of an IANA registry for 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 as part of the RFC publication process. See Section 8.2. 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 o Constant values for each type Williams Expires September 25, 2008 [Page 3] Internet-Draft GSS IANA Instructions March 2008 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. See Section 8.2. 7. Registration Form(s) Registrations for GSS-API namespaces SHALL take the following form: +----------------+--------------------+-----------------------------+ | Registration | Possible Values | Description | | Field | | | +----------------+--------------------+-----------------------------+ | Registration | 'Instance', | Indicates whether this | | type | 'Sub-Namespace' | entry reserves a given | | | | symbol name (and possibly, | | | | constant value), or whether | | | | it reserves an entire | | | | sub-namespace (the name is | | | | a "prefix") or constant | | | | value range. | +----------------+--------------------+-----------------------------+ | Bindings | 'Generic', | Indicates the name of the | | | 'C-bindings', | programming language that | | | 'Java', 'C#', | this registration involves, | | | | is an entry for the generic | | | | abstract GSS-API (i.e., not | | | | specific to any programming | Williams Expires September 25, 2008 [Page 4] Internet-Draft GSS IANA Instructions March 2008 | | | language). | +----------------+--------------------+-----------------------------+ | Object Type | 'Data-Type', | Indicates the type of the | | | 'Function', | object(s) whose symbolic | | | 'Method', | name or constant value this | | | 'Integer', | entry registers. The | | | 'String', 'OID', | possible values of this | | | 'Context Flag', | field depend on the | | | 'Name Type', | programming language in | | | 'Header File | question, therefore they | | | Name', etcetera | are not all specified here. | +----------------+--------------------+-----------------------------+ | Symbol | | values being registered. | +----------------+--------------------+-----------------------------+ | Binding of | | names the abstract API | | | | element of which it is a | | | | binding (OPTIONAL). | +----------------+--------------------+-----------------------------+ | Constant | | The value(s) of the | | Value/Range(s) | or | | | | | (OPTIONAL). | +----------------+--------------------+-----------------------------+ | Description | | Description of object(s) | | | | being registered. | +----------------+--------------------+-----------------------------+ | Registration | Values from | Describes the rules for | | Rules | [RFC2434], such as | allocation of items that | | | 'IESG Approval', | fall in this sub-namespace, | | | 'Expert Review', | for entries with Rgistratio | | | 'First Come First | Type of Sub-namespace | | | Served', 'Private | (OPTIONAL). For private use | | | Use', etcetera. | sub-namespaces the | | | | submitter MUST provide the | | | | e-mail address of a | | | | responsible contact. | +----------------+--------------------+-----------------------------+ | Reference | | Reference to document that | | | | describes the object(s) | | | | being registered, if any | | | | (OPTIONAL). | +----------------+--------------------+-----------------------------+ | Expert | | | +----------------+--------------------+-----------------------------+ | Status | 'Standards-Track', | Status of the registration. | | | 'Informational', | | | | '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, and/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: registration type, progamming language, object type, and symbol name/prefix. 8. 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 will now be the registration authority for the GSS-API name type OID space. 8.1. Initial Namespace Registrations Initial registry content corresponding to the items defined in [RFC2743], [RFC2744], [RFC2853], [RFC1964] and [RFC4121] and others will be supplied during the IANA review portion of the RFC publishing process. The KITTEN WG chairs MUST indicate that such content has been reviewed by the WG and that there is WG consensus that the entries are in agreement with those RFCs. 8.2. Registration Maintenance Guidelines Standards-Track RFCs can create new items with any non-conflicting Symbol Name/Prefix value for this registry by virtue of IESG approval to publish as a Standards-Track RFC. The status of such entries SHALL initially be as specified by the RFC (defaulting to 'Standards- Track'). Standards-Track RFCs can mark existing entries as obsolete or Williams Expires September 25, 2008 [Page 6] Internet-Draft GSS IANA Instructions March 2008 historic, and can even create conflicting entries if explicitly stated (the IESG, of course, should review conflicts very carefully). IANA shall also consider submissions from individuals, and via Informational and Experimental RFCs, subject to Expert Review. IANA SHALL allow such registrations if a) they are not conflicting, and b) if expert review passes. Guidelines for expert reviews are given below. The Status of any such registrations SHALL agree with the Status of the source RFC, or, for individual registrations, 'Other'. 8.2.1. Expert Reviews of Individual Submissions Expert review selection SHALL be as follows. If, at the time that the IANA receives an individual submission for registration in this registry, there is are any IETF Working Groups chartered to produce GSS-API-related documents, then the IANA SHALL ask the chairs of such WGs to be expert reviewers or to name one. If there are no such WGs at that time, then the IANA SHALL ask past chairs of the KITTEN WG and the author/editor of this RFC to act as expert reviewers or name an alternate. Expert reviewers of individual registration submissions with Registration Type == Sub-namespace should check that the registration request has a suitable description (which need not be sufficiently detailsed for others to implement) and that the Symbol Name/Prefix is sufficiently descriptive of the purpose of the sub-namespace or the name of the submitter or associated company. Expert reviewers of individual registration submissions with Registration Type == Instance should check that the Symbol Name falls under a sub-namespace controlled by the submitter and that the Status of the submission is "Informational." Registration of such entries which do not fall under such a sub-namespace may be allowed provided that they correspond to long existing non-standard extensions to the GSS-API and this can be easily checked or demonstrated, otherwise IESG Protocol Action is REQUIRED (see previous section). Also, reviewers should check that any registration of constant values for types which have Standard-Track status have a detailed description that is suitable for other implementors to reproduce, and that they don't conflict with other usages or are otherwise dangerous in the reviewers estimation. 9. Security Considerations This document has no security considerations. Williams Expires September 25, 2008 [Page 7] Internet-Draft GSS IANA Instructions March 2008 10. References 10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. 10.2. Informative References [RFC1964] Linn, J., "The Kerberos Version 5 GSS-API Mechanism", RFC 1964, June 1996. [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. [RFC2853] Kabat, J. and M. Upadhyay, "Generic Security Service API Version 2 : Java Bindings", RFC 2853, June 2000. [RFC4121] Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2", RFC 4121, July 2005. Author's Address Nicolas Williams Sun Microsystems 5300 Riata Trace Ct Austin, TX 78727 US Email: Nicolas.Williams@sun.com Williams Expires September 25, 2008 [Page 8] Internet-Draft GSS IANA Instructions March 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 September 25, 2008 [Page 9]